Académique Documents
Professionnel Documents
Culture Documents
Revision
Revision
Document identity:
Revision:
Date:
0
01/2013
1
05/2013
2
12/2014
Revision
Contents
Contents
1
Introduction.................................................................................................................... 1-1
1.1
1.2
Preface................................................................................................................1-1
1.3
References.......................................................................................................... 1-1
Overview............................................................................................................. 2-1
2.2
2.3
HMI Editor..........................................................................................3-1
3.1.2
3.1.3
Component configuration...................................................................3-1
3.1.4
3.1.5
3.1.6
HMI client...........................................................................................3-2
Configuration.................................................................................................................. 4-1
4.1
4.2
4.3
4.3.2
Configuring commands......................................................................4-4
HMI Editor......................................................................................................................5-1
5.1
5.2
Installation........................................................................................................... 5-1
5.3
5.4
5.5
5.3.1
Project................................................................................................5-1
5.3.2
Pages.................................................................................................5-1
5.3.3
Components...................................................................................... 5-2
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
Contents
5.5.2
5.5.3
'Insert' menu......................................................................................5-7
5.5.4
5.5.5
5.5.6
'Info' menu.......................................................................................5-17
5.7
6.2
6.3
6.4
6.5
6.6
5.6
6.1
5.5.1
Static components..............................................................................................6-2
6.1.1
Line component.................................................................................6-2
6.1.2
Rectangle component........................................................................6-2
6.1.3
6.1.4
Polygon component...........................................................................6-3
6.1.5
6.1.6
Image component..............................................................................6-4
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
Symbol component..........................................................................6-11
6.3.2
6.3.3
6.3.4
6.3.5
6.4.2
6.5.2
6.5.3
6.5.4
6.6.2
6.7
6.8
Contents
7.1
7.2
7.2.2
7.2.3
7.3
'Insert' menu.......................................................................................................7-4
7.4
7.5
Overview............................................................................................................. 8-1
8.2
9.2
10
Limitations.................................................................................................................... 10-1
11
Glossary....................................................................................................................... 11-1
Contents
Introduction
About the RTU500 series Function Description
1 Introduction
1.1
Part name
Part 1: Overview
Explanation
Overview of the RTU500 series and system
architecture
1.2
Preface
This manual describes the configuration engineering process for the integrated Human Machine
Interface (HMI) of the RTU500 series:
1.3
References
[1]
Introduction
References
Overview
The Integrated HMI function consists of the following software components:
HMI Editor (for offline configuration)
HMI runtime system (installed on the RTU)
The HMI Editor allows you to create customer-specific HMI pages using predefined components
from the included HMI Library.
You can use the HMI Editor to connect dynamic components to RTU data points. To support this
feature, the HMI Editor reads the list of data points from the RTUtil500 configuration file.
For each Integrated HMI function of the RTU500 series, the HMI Editor generates an HMI project
file (see "Fig. 1: Overview", page 1). The HMI project file is an additional configuration file that
needs to be uploaded to the RTU.
2.2
Connecting RTUs to a PC
To connect an RTU to a PC, use one of the following connection options:
Editor
Library
Client
RTU560
Figure 1: Overview
2.3
System requirements
System requirements for the local PC:
Microsoft Windows compatible operating system
Microsoft Internet Explorer (recommended) or other Web browser
Java Runtime Environment (available on the RTUtil500 installation CD)
3.1.1
HMI Editor
HMI Library
User project
HMI server
HMI application
HMI client
HMI Editor
The HMI Editor is an offline program for configuring user-specific pages for the Integrated HMI using
predefined components from the included HMI Library.
It generates user projects that can be uploaded to the RTU's CompactFlash file system. User
projects can be deployed as HMI applications.
3.1.2
User projects
A user project consists of one or more pages to which you can add components from the HMI
Library.
3.1.3
Component configuration
Components can be configured with the HMI Editor by the user.
Configuration of components is component-specific. This means that every component type has
its own configuration facilities.
The components available in the HMI Library are described in chapter "# 6" "HMI Library".
The HMI Editor provides also an interface to RTU configuration file (*.rcd) so that it is possible to
connect components to process data configured in RTUtil500. The selection of process data is done
by the object-name of the process data, so no separate addressing has to be done by the user for
this function. Modifications to the RTU configuration do not influence a link to a process data point,
until the process data is deleted.
3.1.4
3.1.5
3.1.6
HMI client
The HMI application includes an HMI client.
The HMI client automatically initiates the communication session with the HMI server on the RTU.
Once the connection is established, it retrieves dynamic information of linked process data points.
If updates of the requested process data are available, the HMI server sends the updated information
to the HMI client. The HMI client distributes the updated information within the HMI application.
If an HMI application is closed, the communication session between the HMI server and the HMI
client is also closed.
Configuration
Initial configuration of the HMI function
4 Configuration
4.1
2.
On the HMI Server tab, enter the required connection information (see "Fig. 3: Configuring the
HMI server"). For detailed information, refer to "# Table 2:""Connection parameters of the HMI
server".
Connection parameter
Description
Default
Port number
50001
Configuration
Configuring the Process Archive functionality
4.2
Parameter range
Default
16 128 characters
32 characters
8 32 characters
16 characters
The HMI server can run on any CMU of the RTU500 series.
Use a network-based TCP/IP connection for best performance results.
4.3
4.3.1
Configuration
Configuring data points in monitoring direction
If the Process Archive function is enabled for a data point, the data receveiced at this data point
will be archived.
Defining the object text and event class for a data point
Use the Object text field on the Archive / Print tab to define the object text for a data point.
Use the Event class field on the Archive / Print tab to assign a data point to a particular digit.
Alarm list
To configure an alarm value that can be used to generate an alarm entry in the alarm list, enable
the Alarm list option.
A data point can be assigned to one out of 10 alarm classes. Select the required Alarm class.
If the Acknowledgement required option is enabled, any alarms which have not yet been acknowledged will remain on the alarm list until acknowledged by the operator.
Configuration
Configuring data points in monitoring direction
You can assign one or several of the following alarm states to the Alarm value by enabling the
corresponding option:
Intermediate
Off
On
Indeterminate
ADVICE
Not all value labels are possible for all types of information objects (e.g. with Single point information SPI). The above example is valid for DPI only.
4.3.2
Configuring commands
If the Process Archive function is enabled (see "Fig. 5: Enabling the Process Archive function") for
a command data point, a record will be created in the event list for each execution of a command
at this data point.
Use the Object text field on the Archive / Print tab to define the object text for a data point.
Use the Text command 'on' field on the Archive / Print tab to define the descriptive text for the ON
state.
Use the Text command 'off' field on the Archive / Print tab to define the descriptive text for the OFF
state.
Use the Event class field on the Archive / Print tab to assign a command to a particular digit.
HMI Editor
Purpose of the HMI Editor
5 HMI Editor
5.1
5.2
Installation
No installation is required to set up the HMI Editor. Simply copy the editor to a free target directory.
The directory structure of the HMI Editor is as follows:
Path: \lib
Directory where the HMI libraries have to be located:
HMILib.jar
HMILibExt.jar (project specific, see chapter "# 6.8" "Project-specific library extensions")
HMILibInterface.jar
jnlp.jar
Path: \tmp
Automatic generated directory for temporary storage of files during editing
Path: \set
Automatically generated directory for storage of editor specific settings
File: HMIEditor.jar
Offline editor for the Integrated HMI
5.3
5.3.1
5.3.2
Pages
Pages are used to organize a user project. Pages can be added, deleted, renamed or moved within
a user project.
Pages must have the extension '.page'. Otherwise they will not be identified as pages.
HMI Editor
Main elements of the HMI Editor
Open a page using the HMI Editor means to open it for editing in the editors workplace.
To close a page means to hide the selected page.
Pages can be interlinked using link components (see chapter "# 6.4"). One page has to be specified
as start page of the user project.
5.3.3
Components
Components are placed on the pages of the project.
These components are elements of the HMI Library.
The selected component can be changed in position, size, color and style. Static components will
not change their style on the runtime system, while dynamic components will change dependent
on the actual state of the process.
The HMI Library is described in chapter "# 6" "HMI Library" of this document.
5.4
5.4.1
Drawing function
In order to place a component on the actual page of a project, the component is selected in the
component tool bar by the left mouse button, and placed into the drawing area. The selected component is marked by a rectangle and may be manipulated by windows standard functions.
5.4.2
Group function
Several components can be grouped to one element by marking all elements with the left mouse
button. All selected elements will be manipulated (Move, Copy, ) in parallel.
5.4.3
HMI Editor
Main functions of the HMI Editor
5.4.4
5.4.5
Normal
Bold
Italic
Bold/Italic
While connecting two bold Line components it may be necessary to change the style of the line end
caps. This is done by the End cap selector.
HMI Editor
Main functions of the HMI Editor
5.4.6
Color picker
Use the Color picker in the Properties dialog of a component to specify the color of the component.
Use one of the following methods to set the color:
Specify the color values for Red, Green and Blue.
Use the Select function to select from a palette of available colors.
5.4.7
HMI Editor
Main functions of the HMI Editor
5.4.8
Keyboard support
The following keys are supported by the HMI Editor:
Key
5.5
Function
<Cursor keys>
<Tab>
<Shift><Tab>
<Del>
5.5.1
'File' menu
The File menu contains the following options:
Option
Action
New project
Open project
Save project
Save project as
Close project
Exit
While opening or saving a project, a progress dialog appears on the screen. While the progress
dialog is active, no other operation is possible.
HMI Editor
Using the HMI Editor
5.5.2
'Page' menu
The Page menu is only available if a project is open.
The Page menu contains the following options:
Option
Action
New
Open
Rename
Close
Import
Export
Delete
After opening a new page, an empty worksheet is displayed to which you can add components
(see chapter "# 6"#).
Use the Options dialog to configure the layout of this worksheet.
If you open an existing project that contains more than one page, select Open from the Project
menu, browse to the project file you want to open and click OK.
The Project pages dialog opens with a list of all pages available in this project. You can select a
single page, multiple pages or all pages to open.
HMI Editor
Using the HMI Editor
After opening the selected pages, the pages are available in the worksheet.
5.5.3
'Insert' menu
The Insert menu is only available if a page is open.
The Insert menu contains the following options:
Option
Action
Rectangle component
Line component
Symbol component
Line component
Polygon component
Image component
Ellipse component
HMI Editor
Using the HMI Editor
Option
Action
Label component
To insert a component, select the respective option from the Insert menu or select the component
from the component tool bar.
5.5.4
'Project menu
'Configure client settings' dialog
Any settings that apply to the entire project are specified in the Configure client settings dialog.
This dialog contains four tabs:
Alarm list
Application
Colors
Process archive list
'Application' tab
Use the Application tab to specify the settings that will apply to the HMI application created from
the project.
HMI Editor
Using the HMI Editor
Description
Character set
This setting is retrieved via the configuration file. It is read-only. From release 11 on configuration data is stored in UTF-8 format.
Time format
Frame title
Start page
Language
'Colors' tab
Use the Colors tab to define the color change of dynamic components in the runtime system. The
color of dynamic components depends on the state of the connected process object.
HMI Editor
Using the HMI Editor
Description
Sorting order if page with process archive list is entered. See chapter "#
6.5.2".
Spontaneous refresh
Select if the list is refreshed spontaneously. This is only valid for Complete
download. See chapter "# 6.5.2"#.
HMI Editor
Using the HMI Editor
Description
Properties of the Color of alarm class n type represent the color assignment to alarm classes used by alarm list function.
If set to true, any user may acknowledge the audible alarm. Otherwise on-
tion
Defines when an audible alarm is played: for coming alarms only or for
coming and fleeting alarms.
This option can only be selected if an audible alarm is selected.
Audible alarm
Select the sound to be played when an alarm is activated and/or terminated again. For detailed information on importing sound file, see section
"Using sounds in a project".
Spontaneous refresh
HMI Editor
Using the HMI Editor
HMI Editor
Using the HMI Editor
Select Project > Sound > Import. The Import sound dialog opens.
Select the sound file. The supported sound file type is WAV.
You can now use the sound file in components of the Alarm list type. For detailed information, refer
to the section "'Alarm list".
Configuration file
The configuration file of RTUtil500 needs to be assigned to the active project. Select Project >
Configuration file to open the Configuration file dialog.
If the project was previously assigned to a configuration, the Configuration file dialog displays the
last configuration.
HMI Editor
Using the HMI Editor
The character set information is set in RTUtil500 and imported into the HMI project. It is needed for
converting special characters when importing object names and displaying archive and event list
object archive texts. This value is READ-ONLY in the HMI project.
In case of important differences between the last used configuration and the new selected configuration, the differences are listed and the user has to accept the selected configuration as the actual
configuration.
HMI Editor
Using the HMI Editor
Consistency check
The system is able to update the links between dynamic components und connected process objects, if the name of a process object was not changed. If the object name of the process object is
not available any more in the selected configuration, the link to this component is deleted. This will
be checked in the Consistency Check dialog.
Archive objects (available for trend chart component) are read and mapped to the object name. If
archive object texts are changed this is change is overtaken automatically when the configuration
is read.
After finalizing a project, the user has to check his project with the help of the project consistency
check. This feature will check:
Any errors found during a consistency are displayed in a new Consistency Check dialog.
HMI Editor
Using the HMI Editor
By double-clicking on one of the error messages in the list, the software will open the related page
of the project and will mark the related component.
5.5.5
'Options' menu
The Options menu contains the following options:
Option
Action
Grid
Language
Mode
Grid
The grid is used to make the drawing more simple. It is useful to connect the components to each
other. If necessary, the grid can be turned off.
Grid is the visible part on the screen, the gap between the lines is calculated in pixels.
Snap is an additional invisible grid.
Normally Snap is less or equal to Grip, respectively Grip is a multiple of Snap.
Language
Use the Language dialog to select the language used by the HMI Editor.
The following languages are available
HMI Editor
Using the HMI Editor
English
German
Restart the HMI Editor to apply the selected language as the active language.
Mode
Use the Mode menu to select the HMI Editor mode.
The following options are available:
Option
Action
Page Editor
5.5.6
'Info' menu
Select Info > About to open the About dialog.
The About dialog will show the actual version of the HMI Editor and the used libraries.
HMI Editor
Properties of the active page
5.6
5.7
Manipulating components
To manipulate a component placed on the active page, proceed as follows:
1 Right-click on the component.
A context menu opens to manipulate the selected component.
HMI Editor
Manipulating components
Action
Cut
Copy
Paste
Delete
Bring to front
Send to back
Bring forward
Send backward
When you try copying a linked component, the following actions are available:
Delete the link in the component
Keep the link in the new component
HMI Editor
Manipulating components
HMI Library
6 HMI Library
The HMI Library consists of the following files:
HMILib.jar
HMILibInterface.jar
(project specific) HMILibExt.jar
These files contain all components that can be inserted into a page of a user project.
The HMI Library contains the following component types:
Static components
Line
Rectangle
Ellipse
Polygon
Label
Image
Dynamic components
Byte value
Integrated totals
Text field
System time
System event
System-event line
User definable Libraries
Dynamic components with control
Symbol
Tap position
Normalized value
Bit string
Floating point
Page link components
Tables
History table
Process archive list
Alarm list
HMI control components
Acknowledge audible alarm component
Local control authority
Chart components
Trend chart
Use the Components toolbar or the Insert menu to select components.
HMI Library
Static components
6.1
6.1.1
Static components
Line component
The Line component generates a line from position X1/Y1 to position X2/Y2.
Position, line color, line width, line style, and line end cap style are defined in the Properties dialog.
6.1.2
Rectangle component
The Rectangle component generates a rectangle or square at position X/Y with the set width
and height.
Position, size, color, line width, and line style are defined in the Properties dialog. By default, the
component is filled if required.
6.1.3
Ellipse component
The Ellipse component generates a circle or an ellipse at position X/Y with the set width and height.
Position, size, color, line width, and line style are defined in the Properties dialog. By default, the
component is filled if required.
HMI Library
Static components
6.1.4
Polygon component
6.1.5
Label component
The Label component generates a static text field at the position X/Y.
Position, size, text font, text size, text color, and text string are defined in the Properties dialog.
HMI Library
Static components
6.1.6
Image component
The Image component generates a place maker for a bitmap file at position X/Y with the set
width and height.
Position, size and the name of the file are defined in the Properties dialog.
Images need to be imported before they can be used by the Image component. Supported image
file types are GIF and JPG.
For detailed information, refer to chapter "# 5.5.4" "'Project menu", section "Using images in a
project".
6.2
6.2.1
HMI Library
Dynamic components
Dynamic components
Byte value component
The Byte value component generates a dynamic text filed at the position X/Y.
Position, size, text font, text size, and color are defined in the Properties dialog.
The component is linked to a monitoring object of the current RTU configuration. The text depends
on the state of this data point and can be configured in the Properties dialog.
ADVICE
Not all value labels are possible for all types of information objects (e.g. with Single point information SPI).
6.2.2
The Integrated totals component generates a numeric field for an integrated total (ITI) at the
position X/Y.
HMI Library
Dynamic components
Position, size, text font, text size, color, number of decimal digits, engineering units, and pulse weight
are defined in the Properties dialog.
The component is connected to a integrated total information (ITI) object within the current RTU
configuration.
6.2.3
HMI Library
Dynamic components
6.2.4
The System time component generates a field for the current system time of the RTU at
position X/Y.
Position, size, text font, text size, and color are defined in the Properties dialog.
HMI Library
Dynamic components
The representation of date and time depends on the client settings. For detailed information, refer
to chapter "# 5.5.4" "'Project menu", section "'Configure client settings' dialog". At runtime the
component is updated once every second, and may be used as a watchdog.
"Fig. 52: Representation of the current system time""Fig. 52: Representation of the current system
time" shows an example of a system time component in the HMI Editor.
The following placeholders are available for date and time format (see chapter "# 5.5.4" "'Project
menu", section "'Configure client settings' dialog"):
Basic
Explanation
yy
Year
04
yyyy
Year
2004
MM
Month in year
12
MMM
Month in year
Jul
dd
Day in month
31
HH
Hour (0 23)
23
KK
Hour (0 11)
11
mm
Minute in hour
59
ss
Second in minute
59
aaa
AM / PM
AM
ww
Week in year
52
WW
Week in month
EEE
Day in week
Tue
DDD
Day in year
365
Example
HMI Library
Dynamic components
Basic
Explanation
Example
FF
Time zone
GMT
6.2.5
Position, size, colors, and type are defined in the Properties dialog.
HMI Library
Dynamic components
6.2.6
The component can be linked to any system event in the current RTU configuration.
6.3
HMI Library
Dynamic components with control
The 'Direct execute' or 'Select before operate' command execution mode can be selected.
A command dialog sequence can contain the following values:
Select and Execute dialog
A two-step dialog sequence will be shown (Select and Execute).
Execute dialog
A single-step dialog sequence will be shown (Execute only).
No dialog
Depending on the command value calculation, either the default value or the toggled value is
set.
The user cannot modify the command default value at runtime.
No information dialog will be shown.
Display of command activation response
This option allows to configure the responses that are displayed after a command has been
sent. Responses are displayed in a message box.
6.3.1
Symbol component
The Symbol component generates a dynamic symbol that changes its style and color depending on the current state of a process data point.
The following process data points can be connected to a Symbol component:
Position, size, color, line width, and symbol type are defined in the Properties dialog.
In order to change style and color of the symbol at runtime, it is necessary to link the component to
a monitoring object of the actual RTU configuration (see "Fig. 58: Symbol component: : Properties
dialog"). The color changes according to the settings in "Fig. 24: Colors tab".
HMI Library
Dynamic components with control
Command execution is possible, if a command object is linked to the component. In this case, the
button texts of the command dialogs can be configured with the Command button texts property.
If this property is not enabled, the default texts according to the selected application language will
be used.
In addition to the other control components, the Symbol component offers the Command value
calculation property. The following values are available for this property:
Default value
The default value as defined in Command default value is preselected in the execution dialog,
or set directly when no dialog is selected.
Toggle monitoring object value
The current value of the monitoring object is toggled: When it is in the ON state. the command
value is OFF, and vice versa. If the current value is invalid, the system uses the default value as
defined in Command default value.
The toggled value is preselected in the execution dialog, or set directly when no dialog is selected.
"Fig. 59: Representation of dynamic system components" shows the different symbols of a dynamic
component.
Additional symbols can be created in the Component View Editor (see chapter "# 7.2" ).
HMI Library
Dynamic components with control
6.3.2
HMI Library
Dynamic components with control
6.3.3
Position, size, color, and font type are defined in the Properties dialog.
The process data points in monitoring and command direction can be scaled using maximum and
minimum values.
The engineering unit is included in the runtime system.
Command execution is possible if a command object is linked to the component.
6.3.4
HMI Library
Dynamic components with control
6.3.5
HMI Library
Link components
The object in monitoring direction is multiplied with the value of the Conversion factor property at
runtime.
6.4
6.4.1
Link components
Link label component
The Link label component generates a link-label at the position X/Y.
Position, size, text font, text size, color, text, and the link to another page in the current project are
defined in the Properties dialog.
HMI Library
Link components
The value of the Link field must be a valid page in the same project. The file type is .page.
"Fig. 62: Representation of link label" shows an example of a link label in the HMI Editor.
6.4.2
The value of the Link field must be a valid page in the same project. The file type is .page.
HMI Library
Table components
"Fig. 64: Link button" shows an example of a link button in the HMI Editor.
6.5
6.5.1
Table components
History table component
ADVICE
Immediately after the entering a page with this component, this table will contain only the actual
state of the linked object. State changes will be recorded, as long as the Integrated HMI is running
on the target PC and the link to the RTU is active.
HMI Library
Table components
6.5.2
Visibility
Configurable
Configurable
Configurable
Commands
Configurable
System Events
Configurable
Always visible
Use the following settings properties to customize the Process Archive list component (see "Fig. 67:
Process Archive list component: Properties dialog"):
Property name
Description
Archive type
HMI Library
Table components
Property name
Description
Alarm entries that change their alarm state to ALARM can be colored
according to their alarm class. Use the Alarm list tab of the Configure client settings dialog to speficy the settings for this function (see
"Fig. 26: Alarm list tab").
Default filter
Use the the Filter dialog to set predefined filter criteria for the Process
Archive list component (see "Fig. 68: Filter dialog").
The following filter criteria are available:
Start time
End time
Object text
Event class
Alarm class
Qualifier
By selecting Exclude checkbox lines NOT matching the entered criteria are filtered.
Filter settings can be updated at runtime.
HMI Library
Table components
Depending on the Process Archive list settings of the project, the component can be used in two
ways:
Interval download
Only an interval of the process archive content will be downloaded to the HMI application at
runtime
Complete download
The complete content of the RTU process archive will be downloaded to HMI application at
runtime.
This mode supports filtering, sorting, and spontaneous updates.
"Fig. 69: Process Archive list component - Interval download" and "Fig. 70: Process Archive list
component - Complete download" show examples of Process Archive list components in the HMI
Editor.
HMI Library
Table components
6.5.3
If audible alarms are configured in the alarm list settings, only the spontaneous update button is
visible.
The RTUtil500 configuration defines which process data points will be allowed to generate an alarm.
For more details see chapter "Configuring data points in monitoring direction".
6.5.4
Explanation
Example
yy
Year
04
HMI Library
HMI control components
Basic
Explanation
Example
yyyy
Year
2004
MM
Month in year
12
MMM
Month in year
Jul
dd
Day in month
31
HH
Hour ( 0 23 )
23
KK
Hour ( 0 11)
11
mm
Minute in hour
59
ss
Second in minute
59
SSS
Millisecond
123
aaa
AM / PM
AM
ww
Week in year
52
WW
Week in month
EEE
Day in week
Tue
DDD
Day in year
365
FF
Time zone
GMT
6.6
6.6.1
HMI Library
HMI control components
6.6.2
6.7
HMI Library
Project-specific library extensions
Use the Displayed interval property to specify the time period displayed on the x-axis. The following
time periods are available: Hour, Day and Month. The time period displayed on the chart may be
shorter if the linked archive object does not provide a sufficient number of values.
The graph is drawn based on the historical values retrieved from the measurement or counter archive
list. The text from the archive object is used to map the values.
6.8
HMI Library
Project-specific library extensions
Component views
HMI Editor mode
7 Component views
The user is able to create user defined representations for dynamic Symbol components (see chapter
"# 6.3.1" "Symbol component") called 'component views.
7.1
The Mode menu button is only available if a project is open. The HMI Editor mode is displayed in
the status bar.
You can toggle the modes at any time without losing information. It is not necessary to save the
project before changing to Page Editor mode.
In Page Editor mode, the Page button is displayed. Use the Page button to maintain pages.
7.2
Figure 79: Menu and status bar: Component View Editor mode
Component views
Component view editor
7.2.1
'View' menu
The View menu contains the following options:
Option
Action
New
Open
Rename
Close
Import
Export
Delete
7.2.2
Component views
Component view editor
To create a component view, enter the name, e.g. test,and click on New.
The following conditions and limitations apply to the name of a new component view:
It must be unique. If there is another component view with this name, an error message will be
displayed.
It must not contain any \ characters. If the new name of the component view contains any \
characters, an error message will be displayed.
It should have a .jar file extension. If a different file extension is used, an error message will
be displayed. If no file extension is used, the .jar extension will be automatically added, e.g.
test.jar
It will be displayed in the status bar.
By default, when you create a new component view for symbol components, the HMI Editor automatically creates four pages.
The pages of the component view represent the states of the dynamic symbol component.
For a single-point input (SPI), only the Off and On pages are relevant. The Intermediate and Indeterminate pages are not used for a single point input (SPI).
For a double-point input (DPI), all pages are used.
Page
SPI
DPI
Intermediate
Off
On
Indeterminate
Component views
Component view editor
7.2.3
7.3
'Insert' menu
Use the view items of the Insert menu in Component View Editor mode to add component views.
The following view items are available:
Alternatively, you can can add component views by selecting the view items from the toolbar (see
chapter "# 5.5.3" "'Insert' menu").
To draw a component view, place the view item on the page as required.
Component views
Properties of view items
7.4
If the Dynamic color property is active (true), the view item displayed at runtime uses the colors defined in the project settings (see chapter "# 5.5.4" "'Project menu", section "'Colors' tab"), depending on the qualifiers of the linked object. If no qualifiers are applied to the linked object at runtime,
the view item s displayed using the value of the Color property as the default color.
Component views
Using component views
If the Dynamic color property is set to false (inactive), the view item uses the value of the Color
property for display at runtime.
The other properties available for view items are identical to the corresponding properties available
for components (see chapter "Main functions of the HMI Editor").
7.5
To change the symbol type, use the Properties dialog and select the required symbol type from
drop-down list. All component views in the current project are available as symbol types in the dropdown list.
Component views
Using component views
To change the size of the Symbol component, set the Bounds property in the Properties dialog.
The component view will be displayed in relation to the size of the component view and the size
of the Symbol component.
Component views
Using component views
Figure 91: Changing the size of the symbol with component view
In the example shown in "Fig. 91: Changing the size of the symbol with component view""Fig. 91:
Changing the size of the symbol with component view", the left symbol component has the same
size as the component view. The component view is displayed in the same size as drawn by the user.
The right symbol component has a smaller size. The display of the applied component view corresponds to the size of the symbol component.
Additional languages
Overview
8 Additional languages
8.1
Overview
The following HMI software components contain language files:
HMI Editor
File name : HMIEditor.jar
Language filename structure: editor_xx_YY.properties *)
Relative path: com/abb/rtu560/hmieditor
HMI Library
File name : lib\HMILib.jar
Language filename structure: lib_xx_YY.properties *)
Relative path: com/abb/rtu560/hmi/application
*)
Basic languages included in released versions are English (en_US) and German (de_DE).
Additional languages may be added to a released version.
Missing texts will be displayed as text of the missing key with leading and trailing exclamation marks
(e.g. !MainFrame.title !).
Additional languages are automatically detected by the HMI Editor at runtime, and made available
for selection in the Language dialog.
8.2
3.
4.
Additional languages
Localizing the Integrated HMI: Step-by-step instruction
5.
6.
Remarks:
The first code is the ISO language code as defined in ISO-639. The code consists of two lower case
letters. For detailed information, refer to http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt.
*)
The second code is the ISO country code as defined in ISO-3166. The code consists of
two capital letters. For detailed information, refer to http://www.chemie.fu-berlin.de/diverse/doc/
ISO_3166.html.
The native2ascii utility is provided by Oracle as part of the Java development Kit (JDK). Download the utility from the Internet and store it in the \bin-directory of the JDK.
**)
In the event of an update, it might be necessary to decode the Unicode escape characters back to
the native encoded characters.Use the following native2ascii command:
native2ascii -reverse <name of the Unicode file> <name of the native file>
***)
1.
2.
3.
9.2
You can also create a desktop shortcut for the HMI Editor. For detailed information, refer to [1].
Limitations
10 Limitations
The following system requirements apply:
Component
Limitations
Operating System
Java
Limitations
50
200
< 1 second
< 2 second
This time may become longer at first update, if large bitmaps are used.
< 3 seconds
dependent on the actual system load
Component
Limitations
5.000
10
Refresh
Update time
< 5 seconds
Limitations
Component
Limitations
5.000
Number of lists
Refresh
Update time
< 5 seconds
The times specified above refer to a TCP/IP-network connection. If a serial PPP connection is used,
the specified times can be longer.
Glossary
11 Glossary
AMI
ASO
BSI
BSO
CMU
DCO
DMI
DPI
DSO
FSO
ITI
MFI
PPP
RCD
RCO
RTU
SCADA
SCO
SPI
STI
Note:
The specifications, data, design or other information contained in this document (the Brochure)
- together: the Information - shall only be for information purposes and shall in no respect be
binding. The Brochure does not claim to be exhaustive. Technical data in the Information are only
approximate figures. We reserve the right at any time to make technical changes or modify the
contents of this document without prior notice. The user shall be solely responsible for the use of
any application example or information described within this document. The described examples
and solutions are examples only and do not represent any comprehensive or complete solution. The
user shall determine at its sole discretion, or as the case may be, customize, program or add value
to the ABB products including software by creating solutions for the end customer and to assess
whether and to what extent the products are suitable and need to be adjusted or customized.
This product is designed to be connected to and to communicate information and data via a network
interface. It is the users sole responsibility to provide and continuously ensure a secure connection
between the product and users or end customers network or any other network (as the case may
be). The user shall establish and maintain any appropriate measures (such as but not limited to
the installation of firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc) to protect the product, the network, its system and the interface against any
kind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft of data
or information. ABB AG is not liable for any damages and/or losses related to such security breaches,
any unauthorized access, interference, intrusion, leakage and/or theft of data or information.
ABB AG shall be under no warranty whatsoever whether express or implied and assumes no responsibility for the information contained in this document or for any errors that may appear in this
document. ABB AG's liability under or in connection with this Brochure or the files included within
the Brochure, irrespective of the legal ground towards any person or entity, to which the Brochure
has been made available, in view of any damages including costs or losses shall be excluded. In
particular ABB AG shall in no event be liable for any indirect, consequential or special damages,
such as but not limited to loss of profit, loss of production, loss of revenue, loss of data, loss
of use, loss of earnings, cost of capital or cost connected with an interruption of business or operation, third party claims. The exclusion of liability shall not apply in the case of intention or gross
negligence. The present declaration shall be governed by and construed in accordance with the
laws of Switzerland under exclusion of its conflict of laws rules and of the Vienna Convention on the
International Sale of Goods (CISG).
ABB AG reserves all rights in particular copyrights and other intellectual property rights. Any reproduction, disclosure to third parties or utilization of its contents - in whole or in part - is not permitted
without the prior written consent of ABB AG.