fd part8 integrated hmi en
DESCRIPTION
RTU HMI manualsTRANSCRIPT
-
RTU500 series
RTU500 series Remote Terminal UnitFunction DescriptionPart 8: Integrated HMI
-
RTU500 series Remote Terminal Unit Revision
ABB AG - 1KGT 150 800 V0021
RevisionDocument identity: 1KGT 150 800V002 1Revision: Date: Changes:0 01/2013 Initial version based on 1KGT 150 740 V003 11 05/2013 New layout2 12/2014 New layout
-
Revision RTU500 series Remote Terminal Unit
1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit Contents
ABB AG - 1KGT 150 800 V0021 | I
Contents1 Introduction.................................................................................................................... 1-1
1.1 About the RTU500 series Function Description...................................................1-11.2 Preface................................................................................................................1-11.3 References..........................................................................................................1-1
2 Integrated HMI function..................................................................................................2-12.1 Overview............................................................................................................. 2-12.2 Connecting RTUs to a PC..................................................................................2-12.3 System requirements.......................................................................................... 2-2
3 Organization of the Integrated HMI................................................................................ 3-13.1 Elements of the Integrated HMI function.............................................................3-1
3.1.1 HMI Editor..........................................................................................3-13.1.2 User projects..................................................................................... 3-13.1.3 Component configuration...................................................................3-13.1.4 Deploying user projects..................................................................... 3-13.1.5 Starting HMI applications................................................................... 3-23.1.6 HMI client...........................................................................................3-2
4 Configuration.................................................................................................................. 4-14.1 Initial configuration of the HMI function............................................................... 4-14.2 Configuring the Process Archive functionality......................................................4-24.3 Configuring data points in monitoring direction................................................... 4-2
4.3.1 The Archive /Print tab........................................................................ 4-24.3.2 Configuring commands......................................................................4-4
5 HMI Editor......................................................................................................................5-15.1 Purpose of the HMI Editor..................................................................................5-15.2 Installation........................................................................................................... 5-15.3 Main elements of the HMI Editor........................................................................ 5-1
5.3.1 Project................................................................................................5-15.3.2 Pages.................................................................................................5-15.3.3 Components...................................................................................... 5-2
5.4 Main functions of the HMI Editor........................................................................ 5-25.4.1 Drawing function................................................................................5-25.4.2 Group function...................................................................................5-25.4.3 Changing position and size................................................................5-35.4.4 Text font, text style and text size....................................................... 5-35.4.5 Line style selector.............................................................................. 5-35.4.6 Color picker....................................................................................... 5-45.4.7 Configuration object selector............................................................. 5-45.4.8 Keyboard support.............................................................................. 5-5
5.5 Using the HMI Editor.......................................................................................... 5-5
-
Contents RTU500 series Remote Terminal Unit
II | 1KGT 150 800 V0021 - ABB AG
5.5.1 'File' menu......................................................................................... 5-55.5.2 'Page' menu...................................................................................... 5-65.5.3 'Insert' menu......................................................................................5-75.5.4 'Project menu................................................................................... 5-85.5.5 'Options' menu................................................................................ 5-165.5.6 'Info' menu.......................................................................................5-17
5.6 Properties of the active page............................................................................5-185.7 Manipulating components.................................................................................5-18
6 HMI Library.................................................................................................................... 6-16.1 Static components..............................................................................................6-2
6.1.1 Line component.................................................................................6-26.1.2 Rectangle component........................................................................6-26.1.3 Ellipse component............................................................................. 6-26.1.4 Polygon component...........................................................................6-36.1.5 Label component...............................................................................6-36.1.6 Image component..............................................................................6-4
6.2 Dynamic components......................................................................................... 6-56.2.1 Byte value component....................................................................... 6-56.2.2 Integrated totals component.............................................................. 6-56.2.3 Text field component..........................................................................6-66.2.4 System time component....................................................................6-76.2.5 System event component.................................................................. 6-96.2.6 System event line component..........................................................6-10
6.3 Dynamic components with control....................................................................6-106.3.1 Symbol component..........................................................................6-116.3.2 Tap position component.................................................................. 6-136.3.3 Normalized value component...........................................................6-146.3.4 Bit string component....................................................................... 6-156.3.5 Floating point component................................................................ 6-15
6.4 Link components.............................................................................................. 6-166.4.1 Link label component.......................................................................6-166.4.2 Link button component....................................................................6-17
6.5 Table components............................................................................................ 6-186.5.1 History table component..................................................................6-186.5.2 Process archive list component....................................................... 6-196.5.3 Alarm list component.......................................................................6-226.5.4 Time representation in tables...........................................................6-22
6.6 HMI control components.................................................................................. 6-236.6.1 Control authority component........................................................... 6-236.6.2 Acknowledge audible alarm component.......................................... 6-24
6.7 Trend chart component.................................................................................... 6-246.8 Project-specific library extensions..................................................................... 6-25
7 Component views.......................................................................................................... 7-1
-
RTU500 series Remote Terminal Unit Contents
ABB AG - 1KGT 150 800 V0021 | III
7.1 HMI Editor mode................................................................................................ 7-17.2 Component view editor.......................................................................................7-1
7.2.1 'View' menu.......................................................................................7-27.2.2 Creating a new component view....................................................... 7-27.2.3 Changing the size of a component view............................................ 7-4
7.3 'Insert' menu.......................................................................................................7-47.4 Properties of view items..................................................................................... 7-57.5 Using component views......................................................................................7-6
8 Additional languages...................................................................................................... 8-18.1 Overview............................................................................................................. 8-18.2 Localizing the Integrated HMI: Step-by-step instruction...................................... 8-1
9 HMI runtime system....................................................................................................... 9-19.1 Loading a project into the RTU...........................................................................9-19.2 Starting an HMI application.................................................................................9-1
10 Limitations.................................................................................................................... 10-1
11 Glossary....................................................................................................................... 11-1
-
Contents RTU500 series Remote Terminal Unit
IV | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit IntroductionAbout the RTU500 series Function Description
ABB AG - 1KGT 150 800 V0021 | 1-1
1 Introduction
1.1 About the RTU500 series Function DescriptionThe Function Description consists of several parts:
Document identity Part name Explanation
1KGT 150 793 Part 1: Overview Overview of the RTU500 series and systemarchitecture
1KGT 150 794 Part 2: Rack mounted solutions Description of the RTU500 series rack solu-tions
1KGT 150 795 Part 3: DIN rail solutions Description of the RTU500 series DIN rail so-lutions
1KGT 150 796 Part 4: Hardware modules Overview of the RTU500 series rack and DINrail modules
1KGT 150 797 Part 5: SCADA functions Description of the RTU500 series SCADAfunctions
1KGT 150 798 Part 6: RTU500 functions Description of the RTU500 series functions
1KGT 150 799 Part 7: Archive functions Description of the RTU500 series Archivefunctions
1KGT 150 800 Part 8: Integrated HMI Description of the RTU500 series IntegratedHMI interface
1KGT 159 896 Part 9: Interfaces and Networks Description of the RTU500 series Interfaceand Network functions
Table 1: Parts of the Function Description
1.2 PrefaceThis manual describes the configuration engineering process for the integrated Human MachineInterface (HMI) of the RTU500 series:
Organization of the HMI Configuration HMI Editor Component library Component views Support of additional languages HMI runtime system Limitations of the HMI
1.3 References[1] 1KGT 150 563 Integrated HMI User's
GuideIntroduction into the usage of the integratedHMI
-
Introduction RTU500 series Remote Terminal UnitReferences
1-2 | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit Integrated HMI functionOverview
ABB AG - 1KGT 150 800 V0021 | 2-1
2 Integrated HMI function
2.1 OverviewThe 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 componentsfrom the included HMI Library.
You can use the HMI Editor to connect dynamic components to RTU data points. To support thisfeature, 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 projectfile (see "Fig. 1: Overview", page 1). The HMI project file is an additional configuration file thatneeds to be uploaded to the RTU.
2.2 Connecting RTUs to a PCTo connect an RTU to a PC, use one of the following connection options:
Local area network (LAN) connection Wide area network (WAN) connection Dialed line or modem (PPP) connection Direct serial (PPP) connection USB interface connection (only RTU511)
Library
RTU560
Editor
Client
Library
RTU560
Editor
Client
Figure 1: Overview
-
Integrated HMI function RTU500 series Remote Terminal UnitSystem requirements
2-2 | 1KGT 150 800 V0021 - ABB AG
2.3 System requirementsSystem 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)
-
RTU500 series Remote Terminal Unit Organization of the Integrated HMIElements of the Integrated HMI function
ABB AG - 1KGT 150 800 V0021 | 3-1
3 Organization of the Integrated HMI
3.1 Elements of the Integrated HMI functionThe Integrated HMI function consists of the following elements:
HMI Editor HMI Library User project HMI server HMI application HMI client
3.1.1 HMI EditorThe HMI Editor is an offline program for configuring user-specific pages for the Integrated HMI usingpredefined components from the included HMI Library.
It generates user projects that can be uploaded to the RTU's CompactFlash file system. Userprojects can be deployed as HMI applications.
3.1.2 User projectsA user project consists of one or more pages to which you can add components from the HMILibrary.
3.1.3 Component configurationComponents can be configured with the HMI Editor by the user.
Configuration of components is component-specific. This means that every component type hasits 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 toconnect components to process data configured in RTUtil500. The selection of process data is doneby the object-name of the process data, so no separate addressing has to be done by the user forthis 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 Deploying user projectsTo deploy a user project and start it as an HMI application, the user project needs to be uploadedto the RTU CMU board on which the HMI server is configured. In order to run the HMI application,a matching version of the HMI Library must be also be available on the CMU board.
-
Organization of the Integrated HMI RTU500 series Remote Terminal UnitElements of the Integrated HMI function
3-2 | 1KGT 150 800 V0021 - ABB AG
3.1.5 Starting HMI applicationsDuring startup of an HMI application on a client system, the HMI application automatically runs arequirements check to ensure that the local cache of the client system contains the required versionof the HMI Library and the uploaded user project. If the cached version of the HMI Library or theuploaded user project is out of date, the HMI application will update it.
If the requirements check was successful, the HMI application starts on the client system using theuploaded user project.
3.1.6 HMI clientThe 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 informationto 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 HMIclient is also closed.
-
RTU500 series Remote Terminal Unit ConfigurationInitial configuration of the HMI function
ABB AG - 1KGT 150 800 V0021 | 4-1
4 Configuration
4.1 Initial configuration of the HMI functionThe following initial configuration is required before using the Integrated HMI function in RTU500series:
1. In the Hardware Tree of RTUtil500, add an HMI server to a CMU board.
Figure 2: Using RTUtil500 for initial configuration of the HMI function
2. On the HMI Server tab, enter the required connection information (see "Fig. 3: Configuring theHMI server"). For detailed information, refer to "# Table 2:""Connection parameters of the HMIserver".
Connection parameter Description Default
Port number TCP/IP port number for the communication be-tween the HMI server running on the RTU andthe HMI application running on the local PC
50001
Control authority timeout Timeout time for the local control authority
Table 2: Connection parameters of the HMI server
-
Configuration RTU500 series Remote Terminal UnitConfiguring the Process Archive functionality
4-2 | 1KGT 150 800 V0021 - ABB AG
Figure 3: Configuring the HMI server
4.2 Configuring the Process Archive functionalityIn order to use the Proces Archive functionality within the Integrated HMI, you must also configurea process archive on the same CMU.
Figure 4: Configuring a process archive using RTUtil500
The following limitations apply to the process archive:
Property Parameter range Default
Number of entries per archive 100 100,000 entries each 2,500 entries each
Text size of objects 16 128 characters 32 characters
Text size of values 8 32 characters 16 characters
Table 3: Limitations of the process archive
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 Configuring data points in monitoring direction
4.3.1 The Archive /Print tab
Enabling the Process Archive function
To enable the Process Archive function for a data point in monitoring direction, use the Archivefunction enable option on the Archive / Print tab.
-
RTU500 series Remote Terminal Unit ConfigurationConfiguring data points in monitoring direction
ABB AG - 1KGT 150 800 V0021 | 4-3
If the Process Archive function is enabled for a data point, the data receveiced at this data pointwill be archived.
Figure 5: Enabling the Process Archive function
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.
Figure 6: Configuring a monitoring data point
Alarm list
To configure an alarm value that can be used to generate an alarm entry in the alarm list, enablethe Alarm list option.
Figure 7: Configuring an alarm entry
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 acknowl-edged will remain on the alarm list until acknowledged by the operator.
-
Configuration RTU500 series Remote Terminal UnitConfiguring data points in monitoring direction
4-4 | 1KGT 150 800 V0021 - ABB AG
You can assign one or several of the following alarm states to the Alarm value by enabling thecorresponding option:
Intermediate Off On Indeterminate
ADVICE
Not all value labels are possible for all types of information objects (e.g. with Single point infor-mation SPI). The above example is valid for DPI only.
4.3.2 Configuring commandsIf the Process Archive function is enabled (see "Fig. 5: Enabling the Process Archive function") fora command data point, a record will be created in the event list for each execution of a commandat 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 ONstate.
Use the Text command 'off' field on the Archive / Print tab to define the descriptive text for the OFFstate.
Use the Event class field on the Archive / Print tab to assign a command to a particular digit.
Figure 8: Configuring a command
-
RTU500 series Remote Terminal Unit HMI EditorPurpose of the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-1
5 HMI Editor
5.1 Purpose of the HMI EditorThe HMI Editor is an offline program for configuring user-specific pages for the Integrated HMI usingpredefined components from the included HMI Library.
It generates user projects that can be uploaded to the RTU's Compact Flash file system. Userprojects can be deployed as HMI applications.
5.2 InstallationNo 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: \libDirectory 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: \tmpAutomatic generated directory for temporary storage of files during editing
Path: \setAutomatically generated directory for storage of editor specific settings
File: HMIEditor.jarOffline editor for the Integrated HMI
5.3 Main elements of the HMI Editor
5.3.1 ProjectA user project contains all configured information made by the user about a HMI application. TheHMI Editor can create new user projects, open already existing user projects and save them. Allinformation of a user project is hold within one project file. The file extension of this file is 'jar'.
The absolute path and the filename of a user project will be displayed in the title of the HMI Edi-tor frame. Before saving a user project a backup is made. This backup-file has the file-extension'jar_bak'.
User projects are organized into several entries like pages and components.
5.3.2 PagesPages are used to organize a user project. Pages can be added, deleted, renamed or moved withina user project.
Pages must have the extension '.page'. Otherwise they will not be identified as pages.
-
HMI Editor RTU500 series Remote Terminal UnitMain elements of the HMI Editor
5-2 | 1KGT 150 800 V0021 - ABB AG
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 specifiedas start page of the user project.
5.3.3 ComponentsComponents 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 willnot change their style on the runtime system, while dynamic components will change dependenton the actual state of the process.
The HMI Library is described in chapter "# 6" "HMI Library" of this document.
5.4 Main functions of the HMI EditorThis chapter describes the basic functions of all available components.
5.4.1 Drawing functionIn order to place a component on the actual page of a project, the component is selected in thecomponent tool bar by the left mouse button, and placed into the drawing area. The selected com-ponent is marked by a rectangle and may be manipulated by windows standard functions.
Figure 9: Drawing function
5.4.2 Group functionSeveral components can be grouped to one element by marking all elements with the left mousebutton. All selected elements will be manipulated (Move, Copy, ) in parallel.
Figure 10: Group function
-
RTU500 series Remote Terminal Unit HMI EditorMain functions of the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-3
5.4.3 Changing position and sizeUse one of the following methods to change the position and size of a component:
Edit the values in the Properties dialog of the component. Modify the component in the drawing area using the left mouse button (see "Fig. 11: Changing
position and size").
Figure 11: Changing position and size
5.4.4 Text font, text style and text sizeUse the Properties dialog of a component to change the text font, text style and text size.
The fonts available may vary depending on your Windows installation.
Figure 12: Text font and text size
The following font styles are available:
Normal Bold Italic Bold/Italic
5.4.5 Line style selectorUse the Line style selector in the Properties dialog of a Line component to change the style of lines,rectangles, ellipses and polygons.
The number following the line style specifies the ratio of visible to hidden pixels.
Figure 13: Line style selector
While connecting two bold Line components it may be necessary to change the style of the line endcaps. This is done by the End cap selector.
-
HMI Editor RTU500 series Remote Terminal UnitMain functions of the HMI Editor
5-4 | 1KGT 150 800 V0021 - ABB AG
Figure 14: Line end cap selector
5.4.6 Color pickerUse 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.
Figure 15: Color picker
5.4.7 Configuration object selectorDynamic components are connected to the process data point of the RTU by selecting the Con-figuration object selector in the Properties dialog of the component. The dialog shows a list of allprocess data points, which can be linked to the component type.
-
RTU500 series Remote Terminal Unit HMI EditorMain functions of the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-5
Figure 16: Configuration object selector
5.4.8 Keyboard supportThe following keys are supported by the HMI Editor:
Key Function
Moves a selected component in that direction
Shifts the focus to the next component
Shifts the focus to the previous component
Deletes the active component(s)
5.5 Using the HMI EditorThe HMI Editor has the same look-and-feel as other Microsoft-compatible products. The HMIEditor is operated by pull-down menus placed in the header of the editor screen.
Figure 17: Menu bar
5.5.1 'File' menuThe File menu contains the following options:
Option Action
New project Create a new project
Open project Open an existing project
Save project Save an open project
Save project as Save an open project with another name
Close project Close an open project
Exit Exit the HMI Editor
Table 4: File menu: Available actions
While opening or saving a project, a progress dialog appears on the screen. While the progressdialog is active, no other operation is possible.
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-6 | 1KGT 150 800 V0021 - ABB AG
Figure 18: Progress dialog
5.5.2 'Page' menuThe Page menu is only available if a project is open.
The Page menu contains the following options:
Option Action
New Create a new page
Open Open an existing page
Rename Rename the active page
Close Close the active page
Import Import a page from another project
Export Export the active page
Delete Delete the active page
Table 5: Page menu: Available actions
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.
Figure 19: Empty worksheet
If you open an existing project that contains more than one page, select Open from the Projectmenu, 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 asingle page, multiple pages or all pages to open.
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-7
Figure 20: Project pages dialog
After opening the selected pages, the pages are available in the worksheet.
Figure 21: Available pages in a project
5.5.3 'Insert' menuThe Insert menu is only available if a page is open.
The Insert menu contains the following options:
Option Action
Acknowledge audible alarm component Insert a component of the type Acknowledge audible alarm
Rectangle component Insert a component of the type Rectangle
Line component Insert a component of the type Line
Symbol component Insert a component of the type Symbol
Line component Insert a component of the type Line
Polygon component Insert a component of the type Polygon
Image component Insert a component of the type Image
Text field component Insert a component of the type Text field
History table component Insert a component of the type History table
System event line component Insert a component of the type System event line
Ellipse component Insert a component of the type Ellipse
Normalized value component Insert a component of the type Normalized value
Table 6: Insert menu: Available actions
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-8 | 1KGT 150 800 V0021 - ABB AG
Option Action
Integrated totals component Insert a component of the type Integrated totals
Floating point value component Insert a component of the type Floating point value
Local control authority component Insert a component of the type Local control authority
Byte value component Insert a component of the type Byte value
Bit string component Insert a component of the type Bit string
Tap position component Insert a component of the type Tap position
Label component Insert a component of the type Label
Link button component Insert a component of the type Link button
Trend chart component Insert a component of the type Trend chart
Alarm list component Insert a component of the type Alarm list
Process archive list component Insert a component of the type Process archive list
Link label component Insert a component of the type Link label
System time component Insert a component of the type System time
System event component Insert a component of the type System event
Table 6: Insert menu: Available actions
To insert a component, select the respective option from the Insert menu or select the componentfrom the component tool bar.
Figure 22: Component toolbar
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
Some of these tabs are described in the following sections.
To open the Configure client settings dialog, select Project > Settings.
'Application' tab
Use the Application tab to specify the settings that will apply to the HMI application created fromthe project.
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-9
The Application tab contains the following options:
Option Description
Character set This setting is retrieved via the configuration file. It is read-only. From re-lease 11 on configuration data is stored in UTF-8 format.
Date format and Time format Format of the System Time component (see chapter )
Time format Time format used in Table components (see chapter )
Frame title Title of all pages in this project
Start page Name of the page, that will be shown after start up
Language The dialog language of the runtime system
Table 7: Application tab: Options
Figure 23: Application tab
'Colors' tab
Use the Colors tab to define the color change of dynamic components in the runtime system. Thecolor of dynamic components depends on the state of the connected process object.
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-10 | 1KGT 150 800 V0021 - ABB AG
Figure 24: Colors tab
'Process archive list' tab
Use the Process archive list tab to specify the settings for the process archive list.
The Process archive list tab contains the following options:
Option Description
Type of archive download Synchronization type of process archive entries between RTU and HMIapplication. See chapter "# 6.5.2".
Default sorting order 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 Completedownload. See chapter "# 6.5.2"#.
Table 8: Process archive list tab: Options
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-11
Figure 25: Process archive list tab
'Alarm list' tab
Use the Alarm list tab to specify the settings for the alarm list.
The Alarm list tab contains the following options:
Option Description
Color of alarm class n Properties of the Color of alarm class n type represent the color assign-ment to alarm classes used by alarm list function.
Acknowledge audible alarm without authoriza-tion
If set to true, any user may acknowledge the audible alarm. Otherwise on-ly authorized users can acknowledge it.
The Acknowledge audible alarm component is enabled accordingly.
Activate audible alarm Defines when an audible alarm is played: for coming alarms only or forcoming 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 termi-nated again. For detailed information on importing sound file, see section"Using sounds in a project".
Spontaneous refresh Select if the list is refreshed spontaneously.
The Spontaneous refresh option is always active if an audible alarm isconfigured.
Default sorting order Sorting order if page with alarm list is entered.
Table 9: Alarm list tab: Options
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-12 | 1KGT 150 800 V0021 - ABB AG
Figure 26: Alarm list tab
Using images in a project
The Image component can be used to include images in a project. Images need to be importedbefore they can be used by the Image component.
Use the Image option from the Project menu to import the images you want to use in a project.Supported image file types are GIF and JPG.
Use the Import image dialog to select from the available images.
Figure 27: Import image dialog
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-13
Using sounds in a project
The Alarm list component can be used to include sounds in the alarm lists of a project.
Before a sound can be used by the Alarm list component, the corresponding sound file needs tobe imported into the project and assigned in the project settings.
To import a sound file, proceed as follows:
1. Select Project > Sound > Import. The Import sound dialog opens.2. Select the sound file. The supported sound file type is WAV.
Figure 28: Import sound dialog
You can now use the sound file in components of the Alarm list type. For detailed information, referto 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 thelast configuration.
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-14 | 1KGT 150 800 V0021 - ABB AG
Figure 29: Configuration file dialog
The character set information is set in RTUtil500 and imported into the HMI project. It is needed forconverting special characters when importing object names and displaying archive and event listobject 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 configu-ration, the differences are listed and the user has to accept the selected configuration as the actualconfiguration.
Figure 30: Differences in the configuration
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-15
Consistency check
The system is able to update the links between dynamic components und connected process ob-jects, if the name of a process object was not changed. If the object name of the process object isnot available any more in the selected configuration, the link to this component is deleted. This willbe checked in the Consistency Check dialog.
Archive objects (available for trend chart component) are read and mapped to the object name. Ifarchive object texts are changed this is change is overtaken automatically when the configurationis read.
After finalizing a project, the user has to check his project with the help of the project consistencycheck. This feature will check:
The availability of a link to one start page in a project For all dynamic elements, the necessary links to process objects For all dynamic elements, the necessary links in monitoring direction For all trend chart elements the necessary link to archive objects All links between the pages The links to available images in the image components
It depends on the user to select the necessary tests.
Figure 31: Consistency Check dialog
Any errors found during a consistency are displayed in a new Consistency Check dialog.
-
HMI Editor RTU500 series Remote Terminal UnitUsing the HMI Editor
5-16 | 1KGT 150 800 V0021 - ABB AG
Figure 32: Errors in the consistency check
By double-clicking on one of the error messages in the list, the software will open the related pageof the project and will mark the related component.
5.5.5 'Options' menuThe Options menu contains the following options:
Option Action
Grid Create a new project
Language Open an existing project
Mode Select the Editor mode
Table 10: Options menu: Available actions
Grid
The grid is used to make the drawing more simple. It is useful to connect the components to eachother. 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.
Figure 33: Grid and Snap functions
Language
Use the Language dialog to select the language used by the HMI Editor.
The following languages are available
-
RTU500 series Remote Terminal Unit HMI EditorUsing the HMI Editor
ABB AG - 1KGT 150 800 V0021 | 5-17
English German
Figure 34: Language selection
Restart the HMI Editor to apply the selected language as the active language.
Figure 35: Request to restart the editor
Mode
Use the Mode menu to select the HMI Editor mode.
The following options are available:
Option Action
Page Editor Open the HMI Editor in edit mode
Component View Editor Open the HMI Editor in component view mode
Table 11: Mode menu: Available actions
5.5.6 'Info' menuSelect 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 RTU500 series Remote Terminal UnitProperties of the active page
5-18 | 1KGT 150 800 V0021 - ABB AG
Figure 36: Version information
5.6 Properties of the active pageTo change the properties of the active page, proceed as follows:
Right-click on an empty space of the active page.
The Properties [Page] dialog opens.
Figure 37: Properties [Page] dialog
5.7 Manipulating componentsTo 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.
-
RTU500 series Remote Terminal Unit HMI EditorManipulating components
ABB AG - 1KGT 150 800 V0021 | 5-19
Figure 38: Manipulating components
The following options are available:
Option Action
Cut Copy selected component to clipboard
Copy Copy selected component to clipboard, ignore object link
Copy with object link Copy selected component link to clipboard, include object link
Paste Paste copied component from clipboard
Delete Delete selected component
Bring to front Bring selected component to the front
Send to back Send the selected component to the back
Bring forward Bring selected component one level forward
Send backward Send selected component one level 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 RTU500 series Remote Terminal UnitManipulating components
5-20 | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit HMI Library
ABB AG - 1KGT 150 800 V0021 | 6-1
6 HMI LibraryThe 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.
Figure 39: Components toolbar
-
HMI Library RTU500 series Remote Terminal UnitStatic components
6-2 | 1KGT 150 800 V0021 - ABB AG
6.1 Static components
6.1.1 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.
Figure 40: Line component: Properties dialog
6.1.2 Rectangle component
The Rectangle component generates a rectangle or square at position X/Y with the set widthand height.
Position, size, color, line width, and line style are defined in the Properties dialog. By default, thecomponent is filled if required.
Figure 41: Properties dialog of rectangle component
6.1.3Ellipse 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, thecomponent is filled if required.
-
RTU500 series Remote Terminal Unit HMI LibraryStatic components
ABB AG - 1KGT 150 800 V0021 | 6-3
Figure 42: Ellipse component: Properties dialog
6.1.4 Polygon component
The Polygon component generates a polygon.
The first line has to be dragged, the additional points are added when the left mouse button isclicked. Move the cursor to the start point for closing the polygon.
Points, color, line width, and line style are defined in the Properties dialog. By default, the componentis filled if required.
Figure 43: Polygon component: Properties dialog
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 RTU500 series Remote Terminal UnitStatic components
6-4 | 1KGT 150 800 V0021 - ABB AG
Figure 44: Label component: Properties dialog
6.1.6 Image component
The Image component generates a place maker for a bitmap file at position X/Y with the setwidth and height.
Position, size and the name of the file are defined in the Properties dialog.
Figure 45: Image component: Properties dialog
Images need to be imported before they can be used by the Image component. Supported imagefile types are GIF and JPG.
For detailed information, refer to chapter "# 5.5.4" "'Project menu", section "Using images in aproject".
Figure 46: Placeholder for not linked / linked image
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components
ABB AG - 1KGT 150 800 V0021 | 6-5
6.2 Dynamic components
6.2.1 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.
Figure 47: Byte value component: Properties dialog
The component is linked to a monitoring object of the current RTU configuration. The text dependson the state of this data point and can be configured in the Properties dialog.
Figure 48: Byte value component: Value label selector
ADVICE
Not all value labels are possible for all types of information objects (e.g. with Single point infor-mation SPI).
6.2.2 Integrated totals component
The Integrated totals component generates a numeric field for an integrated total (ITI) at theposition X/Y.
-
HMI Library RTU500 series Remote Terminal UnitDynamic components
6-6 | 1KGT 150 800 V0021 - ABB AG
Position, size, text font, text size, color, number of decimal digits, engineering units, and pulse weightare defined in the Properties dialog.
The component is connected to a integrated total information (ITI) object within the current RTUconfiguration.
Figure 49: Integrated totals component: Properties dialog
6.2.3 Text field component
The Text field component generates a dynamic text string 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. Dependent on thestate of this object the text will change according to the configuration of this process data point.
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components
ABB AG - 1KGT 150 800 V0021 | 6-7
Figure 50: Text field component: Properties dialog
6.2.4 System time component
The System time component generates a field for the current system time of the RTU atposition X/Y.
Position, size, text font, text size, and color are defined in the Properties dialog.
-
HMI Library RTU500 series Remote Terminal UnitDynamic components
6-8 | 1KGT 150 800 V0021 - ABB AG
Figure 51: System time component: Properties dialog
The representation of date and time depends on the client settings. For detailed information, referto chapter "# 5.5.4" "'Project menu", section "'Configure client settings' dialog". At runtime thecomponent 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 systemtime" shows an example of a system time component in the HMI Editor.
Figure 52: Representation of the current system time
The following placeholders are available for date and time format (see chapter "# 5.5.4" "'Projectmenu", section "'Configure client settings' dialog"):
Basic Explanation Example
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 4
EEE Day in week Tue
DDD Day in year 365
Table 12: Placeholders for date and time format
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components
ABB AG - 1KGT 150 800 V0021 | 6-9
Basic Explanation Example
FF Day of week in month 7
Z Time zone GMT
Table 12: Placeholders for date and time format
6.2.5 System event component
The System event component shows the states of the RTU internal system events in graphicalor textual style. The following representations are available:
Fixed text in the language of the running application Colored ellipse with changing colors Colored rectangle with changing colors
Position, size, colors, and type are defined in the Properties dialog.
Figure 53: System event component: Properties dialog
The component can be linked to any system event of an RTU configuration.
Figure 54: System event component: Configuration object chooser
The HMI Editor always displays the Not OK representation.
-
HMI Library RTU500 series Remote Terminal UnitDynamic components
6-10 | 1KGT 150 800 V0021 - ABB AG
Representations only change in the runtime system.
Figure 55: System event component
6.2.6 System event line componentThe System event line component shows the states of the RTU internal system events in graphicstyle as a line.
Position, size, and colors are defined in the Properties dialog.
Figure 56: System event line component: Properties dialog
The component can be linked to any system event in the current RTU configuration.
6.3 Dynamic components with controlDynamic components share a common feature: a command and/or a monitoring process data pointcan be connected to each of them.
If a command process data point is connected to a dynamic component, the following propertieswill be used by that component:
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components with control
ABB AG - 1KGT 150 800 V0021 | 6-11
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 dialogA two-step dialog sequence will be shown (Select and Execute).
Execute dialogA single-step dialog sequence will be shown (Execute only).
No dialogDepending on the command value calculation, either the default value or the toggled value isset. 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 beensent. Responses are displayed in a message box.
Figure 57: Available response combinations
6.3.1 Symbol component
The Symbol component generates a dynamic symbol that changes its style and color de-pending on the current state of a process data point.
The following process data points can be connected to a Symbol component:
SPI Single Point Information DPI Double Point Information SCO Single Command Output DCO Double Command Output
The following symbols are available:
Disconnector (up, down, right, left) Circuit breaker (up, down, right, left) Diamond Square Circle Button
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 toa monitoring object of the actual RTU configuration (see "Fig. 58: Symbol component: : Propertiesdialog"). The color changes according to the settings in "Fig. 24: Colors tab".
-
HMI Library RTU500 series Remote Terminal UnitDynamic components with control
6-12 | 1KGT 150 800 V0021 - ABB AG
Command execution is possible, if a command object is linked to the component. In this case, thebutton 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 willbe used.
In addition to the other control components, the Symbol component offers the Command valuecalculation property. The following values are available for this property:
Default valueThe 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 valueThe current value of the monitoring object is toggled: When it is in the ON state. the commandvalue is OFF, and vice versa. If the current value is invalid, the system uses the default value asdefined in Command default value. The toggled value is preselected in the execution dialog, or set directly when no dialog is se-lected.
Figure 58: Symbol component: : Properties dialog
"Fig. 59: Representation of dynamic system components" shows the different symbols of a dynamiccomponent.
Additional symbols can be created in the Component View Editor (see chapter "# 7.2" ).
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components with control
ABB AG - 1KGT 150 800 V0021 | 6-13
Figure 59: Representation of dynamic system components
6.3.2 Tap position component
The Tap position component generates a numeric symbol that changes its content dependingon the actual state of a process data point.
The following process data points can be connected to a Tap position component:
STI Step Position Information RCO Regulation Command Output
Position, size, color, and font type are defined in the Properties dialog.
Command execution is possible if a command object is linked to the component. In this case, thebutton texts of the command dialogs can be configured using the Command button texts property.If this property is not enabled, the default texts according to the selected application language areused.
-
HMI Library RTU500 series Remote Terminal UnitDynamic components with control
6-14 | 1KGT 150 800 V0021 - ABB AG
6.3.3 Normalized value component
The Normalized value component generates a numeric symbol that changes its content de-pending on the actual state of a process data point.
The following process data points can be connected to a Normalized value component:
AMI Analogue Measured Information DMI Digital Measured Information ASO Analogue Setpoint Output DSO Digital Setpoint Output
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 andminimum values.
The engineering unit is included in the runtime system.
Command execution is possible if a command object is linked to the component.
-
RTU500 series Remote Terminal Unit HMI LibraryDynamic components with control
ABB AG - 1KGT 150 800 V0021 | 6-15
6.3.4 Bit string component
The Bit string component generates a numeric symbol that changes its content depending onthe actual state of a process data point.
The following process data points can be connected to a Bit string component:
BSI Bit String Input BSO Bit String Output
Position, size, color, and font type are defined in the Properties dialog.
The representation of the process data points in monitoring direction can be changed from decimalto hexadecimal.
Command execution is possible, if a command object is linked to the component.
6.3.5 Floating point component
The Floating point component generates a numeric field for a floating point value at positionX/Y.
Position, size, text font, text size, color, number of decimal digits, and engineering unit are definedin the Properties dialog.
The following process data points can be connected to a Floating point component:
MFI (Analog Measured value Floating Input) FSO (Floating Set point command Output)
-
HMI Library RTU500 series Remote Terminal UnitLink components
6-16 | 1KGT 150 800 V0021 - ABB AG
The object in monitoring direction is multiplied with the value of the Conversion factor property atruntime.
Figure 60: Floating point component: Properties dialog
6.4 Link components
6.4.1 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 aredefined in the Properties dialog.
-
RTU500 series Remote Terminal Unit HMI LibraryLink components
ABB AG - 1KGT 150 800 V0021 | 6-17
Figure 61: Link Label component: Properties dialog
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.
Figure 62: Representation of link label
6.4.2 Link button component
The Link button component generates a link-button at position X/Y.
Position, size, text font, text size, color, text, and the link to another page in the current project aredefined in the Properties dialog.
Figure 63: Link Button component: Properties dialog
The value of the Link field must be a valid page in the same project. The file type is .page.
-
HMI Library RTU500 series Remote Terminal UnitTable components
6-18 | 1KGT 150 800 V0021 - ABB AG
"Fig. 64: Link button" shows an example of a link button in the HMI Editor.
Figure 64: Link button
6.5 Table components
6.5.1 History table component
The History table component generates a table at position X/Y.
Position and size are defined in the Properties dialog.
The component is linked to a monitoring object of the actual RTU configuration. The actual stateof this object and all state changes (with date and time) will be recorded while the page containingthe History table component is active.
"Fig. 66: History Table component" shows an example of the component.
Figure 65: History table component: Properties dialog
ADVICE
Immediately after the entering a page with this component, this table will contain only the actualstate of the linked object. State changes will be recorded, as long as the Integrated HMI is runningon the target PC and the link to the RTU is active.
-
RTU500 series Remote Terminal Unit HMI LibraryTable components
ABB AG - 1KGT 150 800 V0021 | 6-19
Figure 66: History Table component
6.5.2 Process archive list component
The Process Archive list component is the visualization of the Process Archive functionality inRTU.
The Process Archive list component can be added to multiple pages of a user project.
The Integrated HMI supports the following process archive types:
Measurement values archive (AMI, DMI, MFI) Counter value archive (ITI) Event archive
The Event Archive may contain the following entries:
Event archive entry Visibility
Single Point Information (SPI) Configurable
Double Point Information (DPI) Configurable
Step Position Information (STI) Configurable
Commands Configurable
System Events Configurable
User Login / Logout Always visible
Table 13: Display of events in a Process Archive list component
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 Archive type to be displayed
Show column of alarm class
Show column of event class
Show column of archive index
Show column of object type
Display the specified column in the process archive list component
Cell font Font that is used to display the data in the table
Table 14: Process Archive list component: Settings properties
-
HMI Library RTU500 series Remote Terminal UnitTable components
6-20 | 1KGT 150 800 V0021 - ABB AG
Property name Description
Alarm transition mode Alarm entries that change their alarm state to ALARM can be coloredaccording to their alarm class. Use the Alarm list tab of the Config-ure 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 ProcessArchive 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 crite-ria are filtered.
Filter settings can be updated at runtime.
Table 14: Process Archive list component: Settings properties
Figure 67: Process Archive list component: Properties dialog
-
RTU500 series Remote Terminal Unit HMI LibraryTable components
ABB AG - 1KGT 150 800 V0021 | 6-21
Figure 68: Filter dialog
Depending on the Process Archive list settings of the project, the component can be used in twoways:
Interval downloadOnly an interval of the process archive content will be downloaded to the HMI application atruntime
Complete downloadThe complete content of the RTU process archive will be downloaded to HMI application atruntime. This mode supports filtering, sorting, and spontaneous updates.
"Fig. 69: Process Archive list component - Interval download" and "Fig. 70: Process Archive listcomponent - Complete download" show examples of Process Archive list components in the HMIEditor.
Figure 69: Process Archive list component - Interval download
Figure 70: Process Archive list component - Complete download
-
HMI Library RTU500 series Remote Terminal UnitTable components
6-22 | 1KGT 150 800 V0021 - ABB AG
6.5.3 Alarm list component
The Alarm list component is placed on pages of a user application.
The position of the Alarm list component and the Alarm transition mode are defined in the Propertiesdialog.
Figure 71: Alarm list component: Properties dialog
Alarm transition modeAlarm entries that change their alarm state to ALARM can be colored according to their alarmclass. Archived process information that changes its alarm state to ALARM can be colored ac-cording to its alarm class. Use the Alarm list tab of the Configure client settings dialog to speci-fy the settings for this function (see "Fig. 26: Alarm list tab").
"Fig. 72: Alarm list component" shows an example of the Alarm list component in the HMI Editor.
Figure 72: Alarm list component
If audible alarms are configured in the alarm list settings, only the spontaneous update button isvisible.
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 Time representation in tablesThe following placeholders are available for date and time format (see chapter "# 5.5.4" "'Projectmenu", section "'Configure client settings' dialog"):
Basic Explanation Example
yy Year 04
Table 15: Placeholders for date and time format
-
RTU500 series Remote Terminal Unit HMI LibraryHMI control components
ABB AG - 1KGT 150 800 V0021 | 6-23
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 4
EEE Day in week Tue
DDD Day in year 365
FF Day of week in month 7
Z Time zone GMT
Table 15: Placeholders for date and time format
6.6 HMI control components
6.6.1 Control authority componentThe Control authority component shows the state of control authority.
The following states are available:
Requested Available Locked (if another party has requested control authority)
The status can be represented by Text, Rectangle, or Rectangle with text.
Position, size, texts, font, and colors are defined in the Properties dialog.
-
HMI Library RTU500 series Remote Terminal UnitHMI control components
6-24 | 1KGT 150 800 V0021 - ABB AG
Figure 73: Control authority component: Properties dialog
6.6.2 Acknowledge audible alarm componentThe Acknowledge audible alarm component allows the user to acknowledge audible alarms.
Figure 74: Acknowledge audible alarm component: Properties dialog
6.7 Trend chart component
The Trend chart component generates a trend chart at position X/Y.
Position and size are defined in the Properties dialog.
The component is linked to a monitoring measurement object of the current RTUtil500 configuration.Available are objects of type AMI, ITI, MFI, or DMI with the Process Archive function enabled.
-
RTU500 series Remote Terminal Unit HMI LibraryProject-specific library extensions
ABB AG - 1KGT 150 800 V0021 | 6-25
Use the Displayed interval property to specify the time period displayed on the x-axis. The followingtime periods are available: Hour, Day and Month. The time period displayed on the chart may beshorter if the linked archive object does not provide a sufficient number of values.
Figure 75: Trend chart component: Properties dialog
The graph is drawn based on the historical values retrieved from the measurement or counter archivelist. The text from the archive object is used to map the values.
Figure 76: Trend chart component
6.8 Project-specific library extensionsThe HMI Editor supports project-specific library extensions. These libraries have the fixed nameHMILibExt.jar and are placed in the \lib subdirectory and on the CompactFlash card of the RTU.
A project-specific library is available if the following icon is displayed in the component tool bar:
-
HMI Library RTU500 series Remote Terminal UnitProject-specific library extensions
6-26 | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit Component viewsHMI Editor mode
ABB AG - 1KGT 150 800 V0021 | 7-1
7 Component viewsThe user is able to create user defined representations for dynamic Symbol components (see chapter"# 6.3.1" "Symbol component") called 'component views.
7.1 HMI Editor modeUse the Options menu button to change the mode of the HMI Editor:
Page Editor to maintain pages Component View Editor to maintain component views
Figure 77: Changing the HMI Editor mode
The Mode menu button is only available if a project is open. The HMI Editor mode is displayed inthe status bar.
You can toggle the modes at any time without losing information. It is not necessary to save theproject before changing to Page Editor mode.
In Page Editor mode, the Page button is displayed. Use the Page button to maintain pages.
Figure 78: Menu and status bar: Page Editor mode
7.2 Component view editorIn Component View Editor mode, the View menu button is displayed.
Figure 79: Menu and status bar: Component View Editor mode
-
Component views RTU500 series Remote Terminal UnitComponent view editor
7-2 | 1KGT 150 800 V0021 - ABB AG
7.2.1 'View' menuThe View menu contains the following options:
Option Action
New Create a new component view
Open Open an existing component view
Rename Rename an existing component view
Close Close the active component view
Import Import a component view to the current project
Export Export a component view from the current project
Delete Delete a component view from the current project
Table 16: View menu: Available actions
Figure 80: View menu
7.2.2 Creating a new component viewSelect New > Symbol from the View menu to create component views for Symbol components.
Figure 81: Creating a component view for symbol components
-
RTU500 series Remote Terminal Unit Component viewsComponent view editor
ABB AG - 1KGT 150 800 V0021 | 7-3
To create a component view, enter the name, e.g. test,and click on New.
Figure 82: Entering the name of a new component view
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 bedisplayed.
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 willbe 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 auto-matically 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 Indeter-minate pages are not used for a single point input (SPI).
For a double-point input (DPI), all pages are used.
Page SPI DPI
Intermediate - x
Off x x
On x x
Indeterminate - x
Table 17: Pages for SPI and DPI
-
Component views RTU500 series Remote Terminal UnitComponent view editor
7-4 | 1KGT 150 800 V0021 - ABB AG
Figure 83: New component view: test.jar
7.2.3 Changing the size of a component viewTo change the size of a component view, right-click on an empty space inside the active page.
To set the page size for all pages of a component view, change the values of the Page size propertyas required.
7.3 'Insert' menuUse the view items of the Insert menu in Component View Editor mode to add component views.The following view items are available:
Rectangle view item Image view item Line view item Ellipse view item Polygon view item
Figure 84: Insert menu: View items
Alternatively, you can can add component views by selecting the view items from the toolbar (seechapter "# 5.5.3" "'Insert' menu").
To draw a component view, place the view item on the page as required.
-
RTU500 series Remote Terminal Unit Component viewsProperties of view items
ABB AG - 1KGT 150 800 V0021 | 7-5
Figure 85: Component view: Example for OFF state
Figure 86: Component view: Example for ON state
7.4 Properties of view itemsThe Dynamic color property is available for all view items.
Figure 87: Properties of a view item
If the Dynamic color property is active (true), the view item displayed at runtime uses the colors de-fined in the project settings (see chapter "# 5.5.4" "'Project menu", section "'Colors' tab"), depend-ing 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 RTU500 series Remote Terminal UnitUsing component views
7-6 | 1KGT 150 800 V0021 - ABB AG
If the Dynamic color property is set to false (inactive), the view item uses the value of the Colorproperty for display at runtime.
The other properties available for view items are identical to the corresponding properties availablefor components (see chapter "Main functions of the HMI Editor").
7.5 Using component viewsTo use a component view, proceed as follows:
1. Switch to Page Editor mode (see chapter "HMI Editor mode").2. Draw a Symbol component.3. Select the symbol type.
Figure 88: Drawing a Symbol component
To change the symbol type, use the Properties dialog and select the required symbol type fromdrop-down list. All component views in the current project are available as symbol types in the drop-down list.
-
RTU500 series Remote Terminal Unit Component viewsUsing component views
ABB AG - 1KGT 150 800 V0021 | 7-7
Figure 89: Changing the symbol type of a Symbol component
Figure 90: Symbol component with component view
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 sizeof the Symbol component.
-
Component views RTU500 series Remote Terminal UnitUsing component views
7-8 | 1KGT 150 800 V0021 - ABB AG
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 samesize 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 corre-sponds to the size of the symbol component.
-
RTU500 series Remote Terminal Unit Additional languagesOverview
ABB AG - 1KGT 150 800 V0021 | 8-1
8 Additional languages
8.1 OverviewThe following HMI software components contain language files:
HMI EditorFile name : HMIEditor.jarLanguage filename structure: editor_xx_YY.properties *)Relative path: com/abb/rtu560/hmieditor
HMI LibraryFile name : lib\HMILib.jarLanguage filename structure: lib_xx_YY.properties *)Relative path: com/abb/rtu560/hmi/application
*) xx = ISO language code and YY = ISO country code
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 availablefor selection in the Language dialog.
8.2 Localizing the Integrated HMI: Step-by-step instructionTo localize the Integrated HMI with additional languages, proceed as follows:
1. Use a ZIP extraction program to open the files.2. Extract the language files from the software components:
editor_en_US.properties from HMIEditor.jarlib_en_US.properties from HMILib.jar
3. Rename the extracted language files using the ISO language and ISO country code of the tar-get language.*)
4. Translate the renamed language files. The language file is a text file that consists of multiplelines, one for each text string. Each line contains a key idenfying the string, an 'equal' sign (=)as a separator, and the string as it appears in the user interface at runtime. For example:...key1=text string 1key2=text string 2...Only translate the text following the 'equal' sign. Do not modify the key!
-
Additional languages RTU500 series Remote Terminal UnitLocalizing the Integrated HMI: Step-by-step instruction
8-2 | 1KGT 150 800 V0021 - ABB AG
5. Encode the translated language files in Unicode format.If the translated language file contains non-Latin-1 characters, convert the translated lan-guage file using the native2ascii utility**):native2ascii
6. Add the translated and encoded language files to the HMI software component.The translated and encoded language files can be added as additional languages to the HMIsoftware components using a ZIP compression program.Ensure that the additional language files contain the correct relative path within the HMI soft-ware component***)
Remarks:
*) The first code is the ISO language code as defined in ISO-639. The code consists of two lower caseletters. 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 oftwo 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). Down-load 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 tothe native encoded characters.Use the following native2ascii command:
native2ascii -reverse
***) To create a ZIP archive with correct relative paths, proceed as follows:
1. On your local file system, create a directory structure containing the required relative paths.2. Copy the translated language files to the correct location inside that folder structure.3. Add the \com directory, including all subdirectories, to the HMI software component.
-
RTU500 series Remote Terminal Unit HMI runtime systemLoading a project into the RTU
ABB AG - 1KGT 150 800 V0021 | 9-1
9 HMI runtime system
9.1 Loading a project into the RTUIn order to run a an HMI application, the HMI Library files and the user project file need to be uploadedto the CMU of the RTU running the the HMI server.
To upload the HMI Library files and the user project file to a CMU, use the Firmware File Manager (forthe libraries) and the Configuration File Manager (for the project) of the RTU500 series Web server.
9.2 Starting an HMI applicationTo start the HMI application, click on the corresponding link in the menu frame (1) or on a link to thisfunction (2, 3) in the hardware tree of the RTU500 series Web server.
After clicking on one of these links, the HMI application will be started on your system if you havesufficient permissions.
Figure 92: Starting the application
You can also create a desktop shortcut for the HMI Editor. For detailed information, refer to [1].
-
HMI runtime system RTU500 series Remote Terminal UnitStarting an HMI application
9-2 | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit Limitations
ABB AG - 1KGT 150 800 V0021 | 10-1
10 LimitationsThe following system requirements apply:
Component Limitations
Operating System Windows 7/XP Professional (SP1),
Windows 2000 Professional (SP3+)Memory >64mb (depending on project size)
Java Java Runtime Environment 1.6 or higher
(also called JRE 6)
Table 18: System requirements
The following limitations apply to the Integrated HMI:
Component Limitations
Max. number of pages 50
Max. number of data points per page 200
Max. number of active clients 4
Refresh of current page < 1 second
Update time for a new page < 2 secondThis time may become longer at first update, if large bitmaps are used.
Execution time for a command < 3 secondsdependent on the actual system load
Table 19: Limitations: Integrated HMI
The following limitations apply to the Alarm list:
Component Limitations
Max. number of data points, to be configuredfor the alarm list.
5.000
Number of alarm lists 1
Number of alarm classes 10
Refresh By operator request or spontaneous.A blinking symbol will signal a new alarm if spontaneous refresh is dese-lected.
Update time < 5 seconds
Table 20: Limitations: Alarm list
The following limitations apply to the Process Archive list:
-
Limitations RTU500 series Remote Terminal Unit
10-2 | 1KGT 150 800 V0021 - ABB AG
Component Limitations
Max. number of data points, to be configuredfor the lists
5.000
Max. number of entries Configurable: 100 ... 100.000
Number of lists 1 list each for events, measurements and counter
Refresh By operator request or spontaneous.A blinking symbol will signal a new event if spontaneous refresh is dese-lected.
Update time < 5 seconds
Table 21: Limitations: Process Archive list
The times specified above refer to a TCP/IP-network connection. If a serial PPP connection is used,the specified times can be longer.
-
RTU500 series Remote Terminal Unit Glossary
ABB AG - 1KGT 150 800 V0021 | 11-1
11 GlossaryAMI Analog Measured value Input
ASO Analog Setpoint command Output
BSI Bit String Input
BSO Bit String Output
CMU Communication and Data Processing Unit
DCO Double Command Output
DMI Digital Measured value Input (8, 16 bit)
DPI Double Point Input
DSO Digital Setpoint command Output (8, 16 bit)
FSO Floating Setpoint Command Output
ITI Integrated Totals Input
MFI Analog Measured value Floating Input
PPP Point to Point Protocol
RCD RTU Configuration Data
RCO Regulation step Command Output
RTU Remote Terminal Unit
SCADA Supervision, Control and Data Acquisition
SCO Single Command Output
SPI Single Point Input or Single point information
STI Step position Input
-
RTU500 series Remote Terminal Unit
2 | 1KGT 150 800 V0021 - ABB AG
-
RTU500 series Remote Terminal Unit
ABB AG - 1KGT 150 800 V0021 | 3
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 bebinding. The Brochure does not claim to be exhaustive. Technical data in the Information are onlyapproximate figures. We reserve the right at any time to make technical changes or modify thecontents of this document without prior notice. The user shall be solely responsible for the use ofany application example or information described within this document. The described examplesand solutions are examples only and do not represent any comprehensive or complete solution. Theuser shall determine at its sole discretion, or as the case may be, customize, program or add valueto the ABB products including software by creating solutions for the end customer and to assesswhether 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 networkinterface. It is the users sole responsibility to provide and continuously ensure a secure connectionbetween the product and users or end customers network or any other network (as the case maybe). The user shall establish and maintain any appropriate measures (such as but not limited tothe installation of firewalls, application of authentication measures, encryption of data, installation ofanti-virus programs, etc) to protect the product, the network, its system and the interface against anykind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft of dataor 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 re-sponsibility for the information contained in this document or for any errors that may appear in thisdocument. ABB AG's liability under or in connection with this Brochure or the files included withinthe Brochure, irrespective of the legal ground towards any person or entity, to which the Brochurehas been made available, in view of any damages including costs or losses shall be excluded. Inparticular 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, lossof use, loss of earnings, cost of capital or cost connected with an interruption of business or oper-ation, third party claims. The exclusion of liability shall not apply in the case of intention or grossnegligence. The present declaration shall be governed by and construed in accordance with thelaws of Switzerland under exclusion of its conflict of laws rules and of the Vienna Convention on theInternational Sale of Goods (CISG).
ABB AG reserves all rights in particular copyrights and other intellectual property rights. Any repro-duction, disclosure to third parties or utilization of its contents - in whole or in part - is not permittedwithout the prior written consent of ABB AG.
Copyright ABB 2015
All rights reserved
1 Introduction1.1 About the RTU500 series Function Description1.2 Preface1.3 References
2 Integrated HMI function2.1 Overview2.2 Connecting RTUs to a PC2.3 System requirements
3 Organization of the Integrated HMI3.1 Elements of the Integrated HMI function3.1.1 HMI Editor3.1.2 User projects3.1.3 Component configuration3.1.4 Deploying user projects3.1.5 Starting HMI applications3.1.6 HMI client
4 Configuration4.1 Initial configuration of the HMI function4.2 Configuring the Process Archive functionality4.3 Configuring data points in monitoring direction4.3.1 The Archive /Print tab4.3.2 Configuring commands
5 HMI Editor5.1 Purpose of the HMI Editor5.2 Installation5.3 Main elements of the HMI Editor5.3.1 Project5.3.2 Pages5.3.3 Components
5.4 Main functions of the HMI Editor5.4.1 Drawing function5.4.2 Group function5.4.3 Changing position and size5.4.4 Text font, text style and text size5.4.5 Line style selector5.4.6 Color picker5.4.7 Configuration object selector5.4.8 Keyboard support
5.5 Us