Professional Documents
Culture Documents
Revisions
Revisions ii
HMI 500 – User Manual
Configuration and Use of the Client Component
Document
Name HMI 500 – User Manual – Configuration and Use of the Client
Component
Document Number ASID11000159
Template Modelo para fascículo de Manual
Template Version 1.4
Translated by Maria Eulália Pinto
Reviewed by Helder Magalhães
Approved by Paulo Rodrigues
Total Pages 49
Document iii
HMI 500 – User Manual
Configuration and Use of the Client Component
Table of Contents
1. INTRODUCTION .............................................................................................................. 1
1.1 REQUIREMENTS ............................................................................................................. 1
1.2 SCOPE .......................................................................................................................... 1
1.3 OBJECTIVES .................................................................................................................. 1
2. SUPPORTED PLATFORMS ............................................................................................ 2
3. INSTALLATION AND CONFIGURATION ....................................................................... 3
3.1 INSTALLATION OF THE REQUIRED SOFTWARE TO ACCESS THE SYSTEM ............................ 3
3.1.1 Based on Internet Explorer ................................................................................... 3
3.1.1.1. Installation of the Required Plug-in for Graphics View .............................................. 3
3.1.2 Based on Mozilla Firefox ....................................................................................... 4
3.1.3 Based on Opera .................................................................................................... 4
3.1.4 Based on Safari ..................................................................................................... 4
3.2 CONFIGURATION ............................................................................................................ 5
3.2.1 Based on Internet Explorer ................................................................................... 5
3.2.1.1. Enhanced access to Data Server .............................................................................. 5
3.2.1.2. Printing ...................................................................................................................... 6
3.2.2 Based on Mozilla Firefox ....................................................................................... 7
3.2.2.1. Printing ...................................................................................................................... 7
3.2.3 Based on Opera .................................................................................................... 7
3.2.3.1. User Interface ............................................................................................................ 7
3.2.3.2. Printing ...................................................................................................................... 8
3.2.4 Microsoft Pocket Internet Explorer ........................................................................ 8
4. COMPONENT GENERAL USE ..................................................................................... 10
4.1 SYSTEM LOGIN ............................................................................................................ 10
4.2 SYSTEM AUTHENTICATION ............................................................................................ 10
4.3 APPLICATION GENERAL VIEW ....................................................................................... 11
4.3.1 Main Menu .......................................................................................................... 11
4.3.2 System Summary ................................................................................................ 12
4.4 INFORMATION AND GENERIC ACTIONS ........................................................................... 12
4.4.1 Toolbar ................................................................................................................ 12
4.4.2 Printing ................................................................................................................ 13
4.4.3 Lists Handling ...................................................................................................... 14
4.4.4 Filters................................................................................................................... 15
4.4.5 Visualization of Entities Attributes ....................................................................... 15
4.4.5.1. Value Imposition ...................................................................................................... 16
4.4.6 Sending Controls ................................................................................................. 16
4.4.6.1. Control Inhibition ..................................................................................................... 17
4.4.7 Virtual keyboard .................................................................................................. 17
5. AVAILABLE MODULES ................................................................................................ 19
5.1 ALARM VIEWER............................................................................................................ 19
5.1.1 Accepting Alarms ................................................................................................ 20
5.2 ALARM INHIBITIONS ...................................................................................................... 20
5.2.1 Alarm Inhibition ................................................................................................... 21
5.2.2 Alarm Activation .................................................................................................. 22
Table of Contents iv
HMI 500 – User Manual
Configuration and Use of the Client Component
Table of Contents v
HMI 500 – User Manual
Configuration and Use of the Client Component
1. Introduction
1.1 Requirements
It is assumed that the reader of this document has experience in automation systems
usage (for example, the CLP 500 platform).
1.2 Scope
Remote Units.
1.3 Objectives
Support the user when configuring and using the client component, as well as to aid on
the resolution of common problems.
Introduction 1 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
2. Supported Platforms
The system was tested on the following Web browsers. The ones that are officially
supported are:
1. Microsoft Internet Explorer 9;
2. Microsoft Internet Explorer 8; added by the plug-in for Adobe SVG Viewer 3.03
trends;
3. Mozilla Firefox 3.6
There are other Web browsers, not often tested, for which support is not official and/ or it
is considered experimental:
1. Opera 10;
2. Safari 5;
3. Google Chrome 4 (the restrictions are the same as Safari’s).
The official supported operating system is Microsoft Windows XP, although the Microsoft
Windows 7 and Linux systems are also very often tested.
The PDA version was tested in the following browsers:
1. Android 4 (stock browser);
2. Opera Mobile 9.6;
3. Microsoft Pocket Internet Explorer.
See point 7 to know each Web browser limitations.
Supported Platforms 2 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
3.2 Configuration
The Web browser in use requires some specific configurations to access the server, so
some features work as expected. Not confirming the configurations can lead to negative
and/ or unexpected effects on the client functioning.
It is important to notice that the configurations described on these sections may not have
the desired effect for several reasons:
4. The user may not have permissions to change configurations on the machine
where he’s working;
5. The network environment may not allow the communication on the suggested
configurations;
6. There may be systems in the network path that change data. This is an extremely
rare situation, but, isolated cases may happen.
3.2.1.2. Printing
To print on the several components, it is necessary to check the configuration described
on Figure 7. The configuration is in the same separator of the previous setting (3.2.1.1).
3.2.3.2. Printing
Follow the configuration described on Figure 10 in order to print on the several
components. The configuration is accessed in “File” menu, “Page configuration…” option.
The options window (Figure 16) allows defining the position of the system summary, as
well as choosing between two different themes that slightly change the application general
look. It also enables to activate the virtual keyboard feature () for all the text and
numbering components.
The “About” window (Figure 17) displays some information about the version of the
several components involved as well as configuration databases.
4.4.1 Toolbar
All the modules share a toolbar (Figure 19) which displays the specific options for each
one of the modules. Some of the buttons are common to all modules (for instance, Print,
Options and Help). These perform generic actions and configurations. The Save button is
common only to modules with data lists, enabling to save/ export data in CSV format.
The printing action, when properly configured (3.2.1.2) should print lists, trend graphics
and mimics. The “Options” button must open a configuration window. The “Help” button
opens the respective section from the user manual.
4.4.2 Printing
Besides containing essential information about each module (data of lists, trend graphics
or mimics), the printing option also has a header with important information about the
printing action as represented by Figure 21. The header has some fields, one of them is
the user description optionally filled when starting the printing from the window of Figure
20.
4.4.4 Filters
Filters are used to restrict all data in the lists, so the result would be a subset of available
information. Usually entities and time restrictions are available, but other restrictions might
be applied depending on the context.
The user can select one of several types of entities in the sub-filter and restrict it to
specific hierarchy levels or identifier pattern.
The sub-filter of specific entities (Figure 24) selected using “Choose…” button selects a
limited set of entities. If intended, the separator regarding the required entities type
(discreet, continuous and commands) must be selected, using restrictions of hierarchy
levels and/ or identifier pattern in order to reduce the amount of information.
The time restriction sub-filter reduces the information to a random period, of absolute or
relative reference. The button to select dates opens a useful calendar when inserting
dates.
The actions about the “Tags” option are explained in detail in section 5.10.3.
4.4.5.1. Value Imposition
Through the value imposition the user can “freeze” status refreshing of an entity with a
defined value and besides that, one can turn it invalid. The imposition is done from the
window of Figure 26, opened after window of Figure 25.
The user will have access to different options in the international keyboard with the
selection of Shift and/ or AltGr keys as in the common keyboard.
Accepting the value inserted in the virtual keyboard can be made when selecting the
Accept button or simply pressing any mouse button outside the keyboard area. The cancel
button must be pressed to cancel the option.
5. Available Modules
The “Filter” button allows reducing data that will be presented, as usually the view
applications means the handling of considerable data quantities (see 4.4.4).
Available Modules 19 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
Local Time Date and local time of the event that gave origin to the alarm is logged
in the system.
Source Time Moment where the event that gave origin to the alarm is logged at
acquisition level, when available.
Identifier The entity responsible by the alarm is identified.
Hierarchy Level 1-4 Entity description in the system tree.
Alarm Type Description Text description of the type of the alarm.
Alarm Description Text description of the alarm.
Priority The priority level of the alarm.
Alarm Active Indication that the condition that created the alarm is still active.
Alarm Accepted Indication of alarm acceptance.
Available Modules 20 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
The user can inhibit the alarms in the configuration options (prevent the alarm generation)
by entity or hierarchical level, and besides this, he can disable all the inhibitions (activate
alarm generation).
Table 2. Columns in the Alarm inhibition list
Column Description
Available Modules 21 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
After having selected the entities and/ or hierarchy levels which alarm one intends to
inhibit (see Figure 32), the “OK” or “Apply” buttons should be pressed, so the window of
Figure 33 is shown from where inhibitions are configured.
When configuring the inhibitions the user can associated an expiry date, where the
inhibition is automatically disabled. In case it isn’t defined, the inhibition will remain active
until the user manual intervention.
Then one can see how the user may disable the existing inhibitions.
Available Modules 22 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
Local Time Date and local hour the event is logged on the system.
Source Time Moment in which the event is logged on the acquisition level, when
available.
Identifier Identifies the entity responsible for the event.
Hierarchy Level 1-4 Entity characterization on the system tree.
Event Type Event type occurred on the system.
Event Description The textual description of the event.
Value The entity value in the moment of the event occurrence, together with
engineering units, if appropriate.
Alarm If the entity is on alarm state.
Historic The alarm occurred in the past.
Available Modules 23 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
As exemplified in Figure 35, the window allows monitoring the current status of printers
attached to the system, as well as toggling their state.
Available Modules 24 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
When double-clicking over a line, in case an entity appears from the attribute visualization
window (4.4.5); in case a command is handled, a control execution window appears
(4.4.6).
Available Modules 25 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
Available Modules 26 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
Local Time Date and local hour the event is logged on the system.
Source Time Moment in which the event is logged on the acquisition level, when
available.
Identifier The single identifier of the associated entity.
Hierarchy Level 1-4 Entity characterization on the system tree.
Type Entity type.
Description Entity description.
Value Entity value on the moment of the log.
Archive Type Archive type: periodic or by event.
5.7 Users
This module shows the application users list, specifying the access level of each one.
Available Modules 27 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Columns Description
5.8 Notes
The Notes module creates messages in the system. They are used for several purposes:
communication between users or report of anomalous persistent situations.
Column Description
Local Time Date and local hour the event is logged on the system.
Identifier The single identifier of the associated entity.
Hierarchy Level 1-4 Classification of the entity on the system tree.
Priority Message level of priority (very high or normal, for instance).
User Identification of the user who wrote the note.
Message Message text.
Available Modules 28 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Only local system administrators can remove or edit notes, although it might be possible in
the future for the user to remotely edit and/or delete his notes.
Available Modules 29 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Column Description
Local Time Date and local time the event was logged in the system.
Identifier The single identifier of the associated entity
Description Entity description.
User Identification of the user who inserted the tag.
Message Message text.
Inhibition Indicates if the tag is inhibiting the associated controls.
It is not possible to access the options window from the Synoptic Viewer if the time-slot
configuration between data updating is reserved to the system administrator.
Available Modules 30 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
5.10.3 Tags
Tags are associated to animated areas and they represent a way for the user to create
messages about the synoptic. These can be used for several purposes: communication
between users, report anomalous persistent situations or inhibition the control sending.
5.10.3.1. Symbology
The graphical representation of a tag in a synoptic is:
The tag presents a different color depending on its type: if inhibits a control it will be red,
otherwise yellow will be the predominant color.
5.10.3.2. Adding Tags
The user must first select a device with right mouse button and choose the Tags option
from the window (Attributes window). The result must be similar to the window below.
In order to continue inserting a tag it is necessary to select the Insert option. It will open a
form in the same window (Details section) with all the fields required to create a tag. The
text field must be filled and, if intended, active control inhibition. The insertion will be
complete when the user confirms it by pressing the Confirm button. The complete window
is presented below.
Available Modules 31 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
In sensitive areas with several entities it will be possible to add Tags to entities that don’t
have any configured yet. If all entities have tags, the inserting option will be inactive.
5.10.3.3. Changing a Tag
The user must first select the tag symbol in the synoptic with left mouse button. The
window must be equal to Tags window in basic mode.
In that window, a list of active tags associated to entities of sensitive area will be
displayed. After selecting the intended tag, its data will be displayed in “Details” section
which might be changed then. The changing action will be complete after the “Change”
button is pressed. The window will have the same presentation as this one below:
Data will only be effectively changed if the user has permissions to do it.
5.10.3.4. Removing a Tag
The user must select the tag symbol with left mouse button. Select the tag that is about to
be removed and, in Details section, press the Remove option. The window in that moment
will have the same presentation as Figure 46.
It’s important to say that removing a tag does not mean that its graphical representation is
deleted, once there may be other tags associated to entities belonging to sensitive area.
Available Modules 32 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Thus, the graphical representation will be only deleted from the synoptic when all device
entities don’t have associated tags.
As when changing a tag, also its removal is made by users with the right permissions to
do it.
5.10.4 Navigation
5.10.4.1. Intra-synoptic
The navigation inside the same synoptic is achieved by using the options of the Toolbar.
5.10.4.1.1. Zoom
This feature has two buttons. The “Zoom in” button enlarges the synoptic, while the “Zoom
out” button reduces it.
5.10.4.1.2. Pan
This feature has four buttons. Each one of them enables to move the synoptic (left, right,
up and down).
5.10.4.1.3. Free navigation (zoom and pan)
This option includes the features previously described, zoom and pan. After selected, this
feature will remain active until it’s no longer selected from the toolbar, or the “Zooming
through the window” option is activated.
The synoptic can be moved into another position by keeping pressed the left mouse
button and simultaneously moving it.
By keeping pressed the right mouse button and moving it up and down, the synoptic will
progressively grow larger or smaller.
In case the mouse has a third button with a wheel, it is also used to zoom in or out the
synoptic depending on its direction.
5.10.4.1.4. Zoom window
This option enables to enlarge an area previously selected from the synoptic. Once
selected, this feature will remain active until a zoom in window is created, being
deselected from the toolbar or the “Free navigation” option is activated.
5.10.4.1.5. Reset view
This option resets for initial values all the actions explained before.
5.10.4.1.6. Refresh
This option reloads the current synoptic, that is, it forces data restoration (besides view
restoring).
5.10.4.1.7. Views
This option enables to define, save and apply views in synoptic. A view is a synoptic
visualization area with a set of operations as zoom in/ zoom out and/ or move. In the view
window will be displayed all the views defined by the user, whether existing (embedded) in
the viewed synoptic. The window will be displayed as:
Available Modules 33 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Save views
Place the synoptic in the required area and select the option Capture. The synoptic area
displayed in the screen will be the defined view. After the capture process, the user must
fill the fields Name and Description and press the Save button.
Delete views
In order to delete a view it’s necessary to select the required view and press the Delete
button.
It’s important to refer that only the views defined by the user (saved from the view window)
may be deleted.
Apply views
Select a displayed list view and press the Go to button.
5.10.4.2. Inter-synoptic
Navigation between synoptic depends on how it was designed. Navigation buttons are
easily distinguished from others once navigation is one of their possible actions. In Figure
43 example, grey buttons lead to other synoptic displays (apart from “SE CARRASCAL”
and “AUTOMATISMOS” buttons).
Available Modules 34 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
5.11.1 Configuration
Configure first the entities about to be visualized and their graphic look in order to start a
Trend chart.
5.11.1.1. Line Configuration
Lines are configured from the options window of Figure 50.
The system enables to use historical data in the chart representation. It is assumed that
the entities about to be visualized are configured to be archived by the system
administrator. So, in order to change to historic mode, select the “Reference Type”
verification mark from the “Historic” group (Figure 50) and configure the desired time-slot.
Available Modules 35 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
The Insert option opens a configuration window with the line properties. All the information
for the line configuration is specified from the menu of Figure 51.
Available Modules 36 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
The storage, load and removal of configurations are handled with dialogues similar to
Figure 52. It is possible to create configurations only by the user, like global configurations
accessible by all the system users.
5.11.2 Navigation
The Trend Chart has two distinct modes: as a graphic representation of the entities found
on the server and as surveillance service of the system properties with entities defined in
the database.
With these two modes, there are some complementing tools enabling a better interaction
with the chart.
5.11.2.1. Trend Graphic Mode
Using this mode requires the entity configuration. It can be obtained from an already
saved configuration from the database or from a new one using configuration windows.
So the read values are easier to identify, there’s a tooltip with the exact read value and the
line description. It is displayed when the mouse pointer is over a symbol that identifies the
read value.
The same paradigms of intra synoptic navigation are used (5.10.4.1) allowing a more
detailed view of graphic areas and/or the values driving out to better identify the line
behavior throughout the time.
5.11.2.2. System Surveillance Mode
There is no interactivity in this mode. A pre-defined configuration is represented with
properties that are usually associated with the system (processor consumption or disk
space, for instance). The goal is to aid the system maintenance and/ or diagnosis.
5.12 Reports
The Reports module enables the reports configuration and generation from data in the
system. An example is displayed below.
1 2
a
Available Modules 37 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Available Modules 38 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
6. Troubleshooting
Figure 54. Cleaning the authenticated sessions from the Mozilla Firefox
There is an equivalent option for Opera web browser, accessible from the “Tools” menu,
“Delete Private Data” option, where a configuration similar to Figure 55 is made.
Figure 55. Cleaning the authenticated sessions on the Opera Web browser
Troubleshooting 39 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
On the Safari Web browser, the option is available on the “Edit” menu, “Reset Safari…”
option, where a configuration similar to Figure 56 is made.
Troubleshooting 40 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
7. Known Limitations
This section includes the known system limitations, working as an extra to the
Troubleshooting (6). Solutions are being developed to avoid the limitations here identified,
what gives them a non-definitive nature, although it’s important to refer that most of them
are due to specific technological limitations of the Web browsers.
Known Limitations 41 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
Known Limitations 42 of 42
HMI 500 – User Manual
Configuration and Use of the Client Component
References
[1] HMI 500 – Manual do Integrador de Sistemas – Configuração dos Componentes Cliente e
Servidor
EFACEC Engenharia S. A., Maia, 2009.
[2] CLP 500 – Manual do Utilizador – Unidade Central
EFACEC Sistemas de Electrónica S. A., Maia, 2007.
References I
HMI 500 – User Manual
Configuration and Use of the Client Component
Glossary
ASV Adobe SVG Viewer – SVG viewer from Adobe Systems Incorporated.
Primary Button Left mouse button.
Secondary Button Right mouse button.
CSV Comma-separated values – values separated by comma. Text format for
tabulated data storage.
Firefox Web browser of the Mozilla foundation.
IIS Internet Information Services – Web Server of Microsoft Corporation.
Internet Explorer Web browser from Microsoft Corporation.
Opera Web browser from Opera Software ASA.
RTU Remote Terminal Unit.
SCADA Supervisory Control And Data Acquisition.
SVG Scalable Vector Graphics, Open standard format for 2D graphics.
Tooltip Box appearing over an active area and which typically contains
information associated to that area.
TPU Terminal Protection Unit.
Glossary II