Óêðà¿íñüêà?
Ðóññêàÿ

Module "Vision" of the subsystem "User Interfaces"

Introduction

Vision module provides a mechanism of the final visualization control area (VCA) into the OpenSCADA. The module is based on the multi-platform library of graphical user interface (GUI) of firm TrollTech — Qt (http://www.trolltech.com/qt ). In its work, the module uses the data of the VCA engine (module VCAEngine).

Visual control area (VCA) is an integral part of the SCADA system. It applies to the client stations with a view to providing accessible information about the object and to for the the issuance of the control actions to the object. In various practical situations and conditions the VCA, based on different principles of visualization may by applied. For example, this may be the library of widgets Qt, GTK+, ~ wxWidgets or hypertext mechanisms based technologies HTML, XHTML, XML, CSS, and JavaScript, or third-party applications of visualization, realized in various programming languages Java, Python, etc. Any of these principles has its advantages and disadvantages, the combination of which could become an insurmountable obstacle to the use of VCA in a practical case. For example, technologies like the Qt library can create highly-reactive VCA, which will undoubtedly important for the operator station for control of technological processes (TP). However, the need for installation of that client software in some cases may make using of it impossible. On the other hand, Web-technology does not require installation on client systems and is extremely multi-platform (it is enough to create a link to the Web-server at any Web-browser) that is most important for various engineering and administrative stations, but the responsiveness and reliability of such interfaces is lower that actually eliminates the using of them at the operator of the TP stations.

OpenSCADA system has extremely flexible architecture that allows you to create external interfaces, including user and in any manner and for any taste. For example, the system configuration OpenSCADA as now available as by means of the Qt library, and also the Web-based.

At the same time creation of an independent implementation of the VCA in different basis may cause the inability to use the configuration of one VCA into another one. That is inconvenient and limited from the user side, as well as costly in terms of implementation and follow-up support. In order to avoid these problems, as well as to create as soon as possible the full spectrum of different types of VCA ïðîåêò ñîçäàíèÿ êîíöåïöèè ÑÂÓ? is established. The result of this project — the direct visualization module (based on the library Qt), direct visualization module WebVision and VCA engine VCAEngine.

1. Purpose

This module of the direct visualization of the VCA is designed for the formation and execution of VCA interfaces among the graphic library Qt. The VCA module provide:

• three levels of complexity in the formation of visualization interface which let organically to develop and apply the tools of the methodology from simple to complex:
  1. formation from the template frames through the appointment of the dynamics (without the graphical configuration);
  2. graphical formation of new frames through the use of already made visualization elements from the library (mimic panel);
  3. formation of new frames, template frames of the visualization elements in the libraries.
• building of the visualization interfaces of various complexity, ranging from simple flat interfaces of the monitoring and finishing with the full-fledged hierarchical interface used in SCADA systems;
• providing of the different ways of formation and configuration of the user interface, based on different graphical interfaces (Qt, Web, Java ...) and also through the standard management interface of OpenSCADA system;
• change of dynamics in the process of execution;
• building of the new template frames on the user level and the formation of the frames libraries, specialized for the area of application (eg the inclusion of frames of parameters, graphs and other items linking them to each other) in accordance with the theory of secondary using and accumulation;
• building of the new user elements of the visualization and the formation of the libraries of frames,specialized for the area of application in accordance with the theory of secondary using and accumulation;
• description of the logic of new template frames and user visualization elements as with the simple links, and also with the laconic, a full-fledged programming language;
• the possibility of the inclusion of the functions(or frames of computing of the functions) of the object model of OpenSCADA to the user elements of the visualization, actually linking the presentation of the algorithm of computing (for example, by visualizing the library of models of devices of TP for following visual modeling TP);
• separation of user interfaces and interfaces of visualization of data provides building the user interface in a single environment, and performance of it in many others (Qt, Web, Java ...);
• the possibility to connect to the performing interface for monitoring and corrective actions (for example, while operator training and control in real time for his actions);
• Visual building of various schemes with the superposition of the logical links and the subsequent centralized execution in the background (visual construction and performance of mathematical models, logic circuits, relay circuits and other proceedings);
• providing of the the functions of the object API to the OpenSCADA system, it can be used to control the properties of the visualization interface from the user procedures;
• building of the servers of frames, of elements of the visualization and of the project of the interfaces of the visualization with the possibility to serve the great number of the client connections;
• simple organization of client stations in different basis (Qt, Web, Java ...) with the connection to the central server;
• full mechanism of separation of privileges between the users which allows to create and execute projects with the various rights of access to its components;
• adaptive formation of alarms and notifications, with the support of different ways of notification;
• support of the user formation of the palettes and font preferences for the visualization of the interface;
• support of the user formation of maps of the events under the various items of equipment management and user preferences;
• support for user profiles, allowing to define various properties of the visualization interface (colors, font characteristics, the preferred maps of events);
• flexible storage and distribution of libraries of widgets, frames, and projects of the visualization interfaces in the databases, supported by OpenSCADA; actually users need only to register the database with data.

2. Tool of the graphical formation of the VCA interface

Development of the VCA interface is performed in a single window, realizing many documents interface (MDI) interface (Fig. 2.a). This approach allows you to simultaneously open multiple frames of various sizes. The following mechanisms for managing the development are used: toolbars, menus and context menus. Most actions are duplicated by different mechanisms, that allows you to quickly find the tool by the preferred method. Navigational interfaces are implemented by the attached windows. Configuration if the toolbars and attached windows is saved on exit and restored at startup that lets you to customize the interface for yourself.

Fig.2.a. The window of the VCA interface development.

Access to major components of the VCA is made by attached windows, in the Figure 2.a these windows are shown on the left side. These windows contain:

• Tree of the widget libraries. Using the navigator you can quickly find the needed widget or library and to do with them necessary operations. The following operations are implemented: add, delete, copy, settings of the widgets and libraries, as well as cleaning and visual editing of the widget. For adaptive management the context menu is supported with the following items:
  • "New library" — creation of the new library.
  • "Add visual item" — adding of the visual element to the library.
  • "Delete visual item" — deleting of the visual element from the library.
  • "Visual item changes clear" — cleaning of the visual element with inheritance of modified properties or setting them by default.
  • "Visual item changes put down" — put down of the visual element changes to the parent, that will used by other inheritances.
  • "Visual item properties" — configuration of the visual element.
  • "Visual item edit" — visual editing of the element.
  • "Visual item cut" — cut/move of the visual element at the time of paste.
  • "Visual item copy" — copy of the visual element at the time of paste.
  • "Visual item paste" — paste of the visual element.
  • "Load from DB" — uploading the data of the visual element from the database.
  • "Save to DB" — saving data of visual element to the database.
  • "Refresh libraries" — performs rereading of the configuration and composition of the libraries of the data model.
• The tree of pages of the project. Provides the mechanism for "Drag and drop" for creation of the user frames based on the elements of libraries. In order to provide the adaptive management the context menu is supported with the following items:
  • "Run project execution" — starting of the execution of the chosen project.
  • "New project" — creation of the new project.
  • "Add visual item" — adding of the visual element to the project/page.
  • "Delete visual item" — deleting of the visual element from the project/page.
  • "Visual item changes clear" — cleaning of the visual element with inheritance of modified properties or setting them by default.
  • "Visual item changes put down" — put down of the visual element changes to the parent, that will used by other inheritances.
  • "Visual item properties" — configuration of the visual element.
  • "Visual item edit" — visual editing of the element.
  • "Visual item cut" — cut/move of the visual element at the time of paste.
  • "Visual item copy" — copy of the visual element at the time of paste.
  • "Visual item paste" — paste of the visual element.
  • "Load from DB" — uploading the data of the visual element from the database.
  • "Save to DB" — saving data of visual element to the database.
  • "Refresh libraries" — performs rereading of the configuration and composition of the libraries of the data model.
• attributes of widgets;
• external links of widgets.

In the main space of the working window the pages of projects, frames of the widgets' libraries, user elements and elements of primitives at the time of their visual editing are placed.

At the top of the working window there is the menu. All the tools needed for development the VCA interfaces are placed in the menu. Menu has the following structure:

• "File" — General operations.
  • "Load from DB" — uploading the data of the visual element from the database.
  • "Save to DB" — saving data of visual element to the database.
  • "Close" — close the editor's window
  • "Quit" — quit from the OpenSCADA system.
• "Edit" — Editing operations of the visual elements.
  • "Make visual item changes UnDo" — make visual item last change undo.
  • "Make visual item changes ReDo" — make repeat for visual item change.
  • "Visual item cut" — cut/move of the visual element at the time of paste.
  • "Visual item copy" — copy of the visual element at the time of paste.
  • "Visual item paste" — paste of the visual element.
• "Project" — Operations over the projects.
  • "Run project execution" — starting of the execution of the chosen project.
  • "New project" — creation of the new project.
  • "Add visual item" — adding of the visual element to the project.
  • "Delete visual item" — deleting of the visual element from the project.
  • "Visual item changes clear" — cleaning of the visual element with inheritance of modified properties or setting them by default.
  • "Visual item changes put down" — put down of the visual element changes to the parent, that will used by other inheritances.
  • "Visual item properties" — configuration of the visual element.
  • "Visual item edit" — visual editing of the element.
• "Widget" — Operations over the widgets and the libraries of widgets.
  • "New library" — creation of the new library.
  • "Add visual item" — adding of the visual element to the library.
  • "Delete visual item" — deleting of the visual element from the library.
  • "Visual item changes clear" — cleaning of the visual element with inheritance of modified properties or setting them by default.
  • "Visual item changes put down" — put down of the visual element changes to the parent, that will used by other inheritances.
  • "Visual item properties" — configuration of the visual element.
  • "Visual item edit" — visual editing of the element.
  • "View" — Management of the arrangement of visual elements on the frame.
    • "Rise widget" — rising the widget to the top.
    • "Lower widget" — lowering the widget to the very bottom.
    • "Up widget" — to rise the widget above.
    • "Down widget" — to lower the widget below.
    • "Align to left" — alignment of the widget to the left.
    • "Align to vertical center" — alignment of the widget vertically to the center.
    • "Align to right" — alignment of the widget to the right.
    • "Align to top" — alignment of the widget to the top.
    • "Align to horizontal center" — horizontal alignment of the widget in the center.
    • "Align to bottom" — alignment of the widget to the bottom.
  • "Library: {Name of the library}" — menu items to access the frames/widgets in the library.
• "Window" — Management of the windows of MDI-interface.
  • "Close" — to close the active window.
  • "Close all" — to close all the windows.
  • "Tile" — to tile all the windows for visibility at the same time.
  • "Cascade" — to cascade all the windows.
  • "Next" — to activate the next window.
  • "Previous" — to activate the previous window.
  • "Widget: {Name of the widget}" — items of activation of the specific window.
• "View" — Management of the visibility of the working window and the toolbars on it.
  • "Visual items toolbar" — visual element toolbar.
  • "Widgets view functions" — the toolbar for management of the visibility and arrangement of widgets on the panels.
  • "Elementary figures tools" — Additional toolbar for the editing the primitive of elementary figures ("ElFigure").
  • "Projects" — attached window of management of projects' tree.
  • "Widgets" — attached window of management of widgets' libraries tree.
  • "Attributes" — attached window of the attributes' manager.
  • "Links" — attached window of the links' manager.
  • "Library: {Name of the library}" — management of the visibility of widgets' libraries toolbars.
• "Help" — Help for OpenSCADA and fro Vision module.
  • "About" — information about this module.
  • "About Qt" — Information about the Qt library, used by this module.
  • "What's this" — query of the description of the elements of the window's interface.

Above, under menu, or on the sides, there are the toolbars. Toolbars can be hidden or located, which is controlled in the menu item "View". The following toolbars are present:

• "Visual items toolbar" — Management toolbar of the visual items:
  • "Run project execution for selected item" — runs the project for execution and activates the selected page of the project.
  • "Load item data from DB" — uploading the data of the chosen elements from the database.
  • "Save item data to DB" — saving data of chosen elements to the database.
  • "New project" — creation of the new project.
  • "New library" — creation of the new library.
  • "Add visual item" — adding of the visual element to the project.
  • "Delete visual item" — deleting of the visual element from the project.
  • "Visual item's properties" — configuration of the visual element.
  • "Visual item edit" — visual editing of the element.
  • "Make visual item changes UnDo" — make visual item last change undo.
  • "Make visual item changes ReDo" — make repeat for visual item change.
  • "Visual item cut" — cut/move of the visual element at the time of paste.
  • "Visual item copy" — copy of the visual element at the time of paste.
  • "Visual item paste" — paste of the visual element.
• "Widgets view functions" — The toolbar of visibility and arrangement management of widgets on the panels:
  • "Rise widget" — rising the widget to the top.
  • "Lower widget" — lowering the widget to the very bottom.
  • "Up widget" — to rise the widget above.
  • "Down widget" — to lower the widget below.
  • "Align to left" — alignment of the widget to the left.
  • "Align to vertical center" — alignment of the widget vertically to the center.
  • "Align to right" — alignment of the widget to the right.
  • "Align to top" — alignment of the widget to the top.
  • "Align to horizontal center" — horizontal alignment of the widget in the center.
  • "Align to bottom" — alignment of the widget to the bottom.
• "Elementary figure tools" — Additional toolbar of the editing of the elementary figures primitive ("ElFig").
  • "Cursor" — return to the cursor for the action over the figures on the widget.
  • "Add line" — adding the line to the elementary figure.
  • "Add arc" — adding the arc to the elementary figure.
  • "Add besier curve" — adding the Bézier curve to the elementary figure.
  • "Connections" — the enabling of the of connections at the elementary figure.
• "Library: {Name of the library}" — Management of the visibility of toolbars of the widget libraries. The contents of the panel depends on the contents of the library and includes call buttons of the library items.
• "QTStarter toolbar" — The toolbar, created by the module of the module of starting the Qt library modules. It contains buttons to start the UI modules of OpenSCADA, based on the Qt Library. With this toolbar you can open multiple copies of the windows of the module or other modules.

At the bottom of the development window of the VCA there is the status line. On the right side of the status line there are indicators of the visual scale of the edited frame, of the mode of changing of the size of the elements, of the mode of the current page of the of the VCA engine station and the user on whose behalf the development of the VCA interface is done. By double-clicking on the indicator of the user it can be changed the current user, enter the new username and password. In the main field of the status line it is displayed various information and assistance messages.

To edit the properties of the visual elements there are two dialogues. The first dialogue allows you to edit the properties of containers of visual elements (widget libraries and projects), figure 2.b. The second dialogue serves to edit the properties of the visual elements, Fig. 2.d. Changes, made in the dialogues, at once, get to the VCA engine. To save these changes to the database or restore from the database it is necessary to use the appropriate tools of the main development window.

Fig.2.b. Dialogue of the editing the properties of the containers of visual elements.

With the help of the main tab of that dialog you can set:

• The state of the elements' container, namely: "Enabled", the database container, date and time for last modification.
• Id, name and description of the container.
• For project:
  • user, group of users and user access, users' group and all other;
  • the period for calculating of the project in the execution.

Fig.2.c. The tab "Diagnostics" of the projects.

From this tab you can select time, or refresh to current, and size for diagnostic messages obtain.

Fig.2.d. Dialogue of editing the properties of visual elements.

With the help of the main tab of that dialog you can set:

• The state of element, namely: "Enabled", the parent widget, date and time for last modification.
• Id, root, path, name and description of the element.

Dialogue of editing the properties of the containers of visual elements contains two tabs: configuration tab of the the main parameters (Fig.2.b) and the configuration tab of the mime-data of the container (Fig. 2.e).

Fig.2.e. Editing tab of the mime-data of the container of visual elements.

Dialogue of the editing the properties of the visual elements contains four tabs: configuration tab of the main parameters (Fig.2.b), the tab of attributes of the element (Fig. 2.f), the tab of the processing of the element (Fig. 2.g) and the tab of links of the elements (Fig.2.h). At different levels of the hierarchy of visual elements any tabs can be available, but some are not.

Fig.2.f. Attributes of the editing dialogue of the properties of the visual element tab.

Fig.2.g. Processing tab of the dialogue of the editing the properties of the visual element.

Fig.2.g. Tab of links of the editing dialog of the properties of visual element.

2.1. Styles

It is known that people can have individual characteristics in the perception of graphical information. If these features are not taken into account it is possible to get the rejection and exclusion of the user to the VC interface. Such rejection and exclusion can lead to fatal errors in the management of TP, as well as traumatize the human by the permanent working with the such interface. In SCADA systems it is accepted the agreement, which regulate the requirements for establishing a unified VC interface which is normally perceived by most of people. The people with some deviations are not taken into account.

To take this into account, and provide the ability to centrally and easily change the visual properties of the interface, the project provides the implementation of visualization interface styles manager.

User can create many styles, each of which will hold the color, font and other properties of the elements of the frame. A simple change of style will quickly transform the VC interface, and the possibility of appointing an individual style to the user will take into account his individual characteristics.

To realize this opportunity, when you create a frame, it is necessary for the properties of color, font and others set the «Config» ( of the table if the «process» tab) in the value of «From style». And in the parameter «Config template» to specify the identifier of the style field. Further, this field will automatically appear in the Style Manager and will be there to change. Style Manager is available on the project configuration page in the tab «Styles» (Figure next). On this tab you can create new styles, delete old ones, change the field of the style and delete unnecessary.

In general the styles are available from the project level. At the level of libraries of widgets you can only define styles fields of widgets. At the project level, at the choice of style it is started the work with styles, which includes access to the fields of styles instead of direct attribute values. In fact, this means that when reading or writing a widget attribute these operations will be carried out with the corresponding field of the chosen style.

When you run the project execution it will be used the set in the project style. Subsequently, the user can select a style from the list of available ones. The user's style will be saved and used next time you run the project.

2.2. Linkage with the dynamics

To provide relevant data in the visualization interface the data of subsystems "Data acquisition (DAQ)" must be used. The nature of these data as follows:

1. parameters that contain some number of attributes;
2. attributes of the parameter can provide information of four types: Boolean, Integer, Real and String;
3. attributes of the parameter can have their history (archive);
4. attributes of the parameter can be set to read, write, and with full access.

Considering the first paragraph it is necessary to allow the possibility of the group of destination links. To do this we use the conception of of the logic level.

In accordance with paragraph 2, links provide transparent conversion of connection types and do not require special configuration.

To satisfy the opportunities for access to archives, in accordance with paragraph 3, links make check of the type of the attribute, and in the case of connection to the "Address", the address of linkage is put into the value.

In terms of the VCA, the dynamic links and configuration of the dynamics are the one process, to describe a configuration of which the tab "Processing" of the widgets is provided (Fig.2.f). The tab contains a table of configuration of the properties of the attributes of the widget and the text of calculation procedure of the widget.

In addition to configuration fields of the attributes the column "Processing" in the table is provided, for selective using of the attributes of the widgets in the computational procedure of the widget, and the columns "Configuration" and "Configuration template", to describe the configuration of links.

The column "Configuration" allows you to specify the linkage type for the attribute of the widget:

• Constant — in the tab of widget links the field for indication of a constant appears, for example of the special color or header for the template frames.
• Input link — linkage with the dynamics for a read-only.
• Output link — linkage with the dynamics just for a writing.
• Full link — complete linkage with dynamic (read/write).
• From style — take the value from the project's style.

The column "Configuration template" makes it possible to describe the groups of dynamic attributes. For example, it may be different types of parameters of subsystem "DAQ" and other widgets of the interface. Furthermore, in the case of correct formation of this field, the mechanism of automatically assign of the attributes with the only indication of the parameter of subsystem "DAQ" or the widget is working, which simplifies and accelerates the configuration process. The value of this column has the following format:

• For constant: direct the attribute value.
• For link: "{parameter}|{identifier}", where:
  • parameter — the group of the attribute;
  • identifier — identifier of the attribute; same the value is compared with the attributes of the DAQ parameters with automatic linkage, after the group link indication.
• For style: identifier-name of the style field.

Installation of the links may be of several types, which are determined by the prefix:

• val: — Direct download of the value through the links mechanism. For example, link: "val:100" loads in the attribute of the widget the value of the 100. It is often used in the case of absence of end point of the link, in order to direct value indicating.
• prm: — Link to the attribute of the parameter or the parameter, in general, for a group of attributes, of subsystem "Data acquisition". For example, the link "prm:/LogicLev/experiment/Pi/var" implements the access of the attribute of the widget to the attribute of the parameter of subsystem "Data acquisition". Sign "(+)" at the end of the address indicate about successful linking and presence of the target. For object's type attributes allowed hierarchical access to the object concrete property by set the path through symbol '#', for example: "prm:/LogicLev/experiment/Pi/var#pr1/pr2".
• wdg: — Link to an attribute of another widget or the widget, in general, for a group of attributes. For example, the link "wdg:/ses_AGLKS/pg_so/pg_1/pg_ggraph/pg_1/a_bordColor" performs the access of the attribute of one widget to the attribute of another one. Supported absolute and relative link's path. Start point of absolute point is root object of module "VCAEngine", then the first item of absolute address is a session or a project identifier. On session side first item is passed then set into a project links there work. For relative links by start point used a widget with the link set. The item ".." of parent node is a special item of the relative links.
• arh: — A special type of link is only available for a particular attribute such as "Address", which allows you to connect directly to the archive values ("arh:CPU_load"). It may be useful to specify the archive as a source of data for primitive "Diagram".

Processing of the links occurs at a frequency of calculating the widget in the following order:

• receiving of the data from input links;
• perform of calculating of the script;
• transmission of the values by the output links.

Fig. 2.g presents the tab with the possibility of group and individual assignment of attributes.

When the widget that contains the configuration of links is placed to the container of widgets, all links of the source widget is added to the list of resulting links of the widgets' container.

The above shows that the links are set by the user in the configuration interface. However, for the possibility of creation of the frames for general use, with the function of providing detailed data of various sources of the same type, a dynamic linkage mechanism is necessary. Such mechanism is provided through a reserved key identifier "<page>" of the group of attributes of links in the frames of general purpose and dynamic linkage with the identifier "<page>" in the process of opening of the frame of general purpose by means of the signal from another widget.

Lets examine the example when we have the frame of general-purpose "Control panel of graph" and a lot of "Graphs" in different tabs. "Control panel of graph" has links with the templates:

• tSek -> "<page>|tSek"
• tSize -> "<page>|tSize"
• trcPer -> "<page>|trcPer"
• valArch -> "<page>|valArch"

At the same time, each widget "Graph" has the attributes tSek, tSize, trcPer and valArch. In the case of a calling of the opening signal of "Control panel of graph" from any widget "Graph" it is happening the linkage of the attributes of the "Control panel of graph" in accordance with the attribute specified in the template with the attribute of the widget "Graph". As a result, all changes in the "Control panel of graph" will be displayed on the graph by means of the link.

In the case of presence of external links to the parameters of subsystem "Data acquisition" in the widget "Graph", the links of "Control panel of graph" will be set on an external source. In addition, if in the "Control panel of graph" will be declared the links to the missing attributes directly in the widget "Graph", it will be made the search for the availability of such attributes from the external source, the first to which the link is directed, performing, thus, the addition of missing links.

To visualize this mechanism the table is cited.

Table. The mechanism of the dynamic linkage.

3. Execution of the VCA interfaces

Execution of the VCA interface is to run a new project session or connect to the existing one on the level of VCA engine. Then the module of direct visualization represents and manages the data of the session. The main window mode of execution mode of this module has the form presented at Fig.3.

Update of the contents of the open pages of the visualization interface with the frequency of the project session execution. In the updating process it is performed:

• request a list of opened pages, with a sign of page modification, at the model and consistency checking of the actually opened pages to that list;
• request of the branch of the modified pages;
• update of the contents of the modified pages and their widgets, in accordance with the received modified data.

At the closure of "RunTime" window closing of the session of the project is done in the VCA engine.

The mechanism of the request of the only modified data is based on an absolute counter of the session execution. If you want to make real changes in the attributes of widgets the memorizing of the value of this counter is done, which allows the identification of modified attributes. This approach can increase productivity and reduce the load on network sharing in the case of access to the VCA engine via network.

Hierarchically the module provides an opportunity to accommodate the project pages in the main execution window (Fig.3), as well as putting them inside of the container widgets, as well as by the opening of additional windows over the main.

When you expand the main execution window, or when moving to the full-screen mode the scaling of the page content of the VCA interface is done, filling the entire space of the window and allowing to execute the projects, developed on one screen resolution, at different resolutions.

The main window consists of menu (top) status line (bottom), and the executable contents of the session between them. Menu in the execution mode is positioned as the OpenSCADA administrator tool, containing the self-system functions and it is available only to privileged users, occupying the group "root". Menu has the following structure:

• "File" — General operations.
  • "Print" — Print:
    • "Page" — page of the user interface;
    • "Diagram" — diagram on the user interface;
    • "Document" — document on the user interface.
  • "Export" — Export:
    • "Page" — page of the user interface;
    • "Diagram" — diagram on the user interface;
    • "Document" — document on the user interface.
  • "Close" — Close the editor window.
  • "Quit" — Quit from the OpenSCADA system.
• "Alarm" — Alarm quittance:
  • "Alarm level" — all alarms;
  • "Light alarm" — lighting notification;
  • "Speaker alarm" — notification with the whistle;
  • "Sound/speech alarm" — sound/speech notivication.
• "View" — Display options of the project session.
  • "Full screen" — Switcher of the full screen execution mode.
• "Help" — Help through the OpenSCADA and Vision module.
  • "About" — Information about this module.
  • "About Qt" — Information about the Qt library, used by the module.

On the right side of the status line the indicators of the time, the current VCA engine station and users on whose behalf the VCA interface is executed, as well as the panel with the alarm quittance buttons, print and export. By double-clicking on the indicator of the user it can be changed by the typing of the new username and password, and by clicking on the quittance button — to quit alarms completely or only the desired notification. In the main field of the status line various messages and assistance messages are displayed.

Fig.3. The main window if the execution mode.

4. Conception of basic elements (primitives)

In this version of that module not all the primitives' images of this project are implemented. In general the project provides the following primitives:

The module of visualizer provides and uses set of specific attributes of the generic means, its information are into next table. Theses attributes create by the visualizer, on its lack, at a first start.

Lets examine the implementation of each primitive.

4.1. Elementary figure primitive (ElFigure)

Support of the following elementary figures is provided: lines, elliptical arcs, Bézier curves and fill of the closed circuit with the color and/or image. For the elementary figures the following operations are provided:

• creation/deleting of the figures;
• copying of the figure(s);
• moving and resizing of the figures by mouse and keyboard;
• possibility to connect the elementary figures to each other, getting more complex figures, for which all the properties of the source elementary figures are available;
• possibility of simultaneous movement of several figures;
• fill of the closed circuit with the color and/or image;
• generation of mouse key events at the time of the mouse-click on the filled spaces;
• scaling;
• rotation;
• mirroring, partial.
  

Figure shows a part of the screen with a frame containing the elementary figures.

The figures underlying this widget, containing the points (the start and end ones) that can be connected with the according points of other figures; and the points with the help of which the geometry of the figure can be changed.

It is possible to add the figure using the mouse:

1. Select the desired figure from the context menu.
2. Set with the left mouse-button start and end points (for line with the SHIFT key hold its orthogonal drawing is made).

The deleting of the figure(s) it is possible by pressing "Del", having selected figure(s).

The copying of the figure(s) it is possible by pressing keys "Ctrl"+"C", having selected figure(s).

Moving/resizing of the figure it is possible by using the mouse or keyboard:

1. Select the figure, by clicking on it with the left mouse button.
2. Drag (with the help of mouse or control keys) the figure or one of its control points in the desired location and release the mouse button (key).

It is possible to move several figures, selected by means of holding "Ctrl" and clicking on the desired figures (this option works when the button Connections (Connections) is disabled) or by mouse selection.

The connection of the figures with each other it is possible by the following way:

1. Press the Connections button.
2. Select one of the figures and move its start or end point to the desired start or end point of the other figure so that it will get to the appeared circle, release the left mouse button. Connected figures are moving as well as the individual, the general point is moved for all connected figures, to which it refers(priority is given to the arc, two arcs can't be connected directly with each other ).

To fill the closed circuit from the figures it is possible with the following way:

1. Press the Connections button.
2. Create the closed circuit.
3. Make the double-click of the left mouse button inside of it.

To delete the fill of the closed circuit it is possible from the context menu of the widget; by braking the closed circuit or by double-click of the left mouse button on the already existing filled space.

Rotation of the figure is made around the center of the widget.

4.2. Text primitive (Text)

Support of the text element with the following properties is provided:

• Font with the properties: type/class of the font, size, bold, italic, strikeout and underline.
• Text color.
• Text orientation.
• Automatic word wrap.
• Alignment of the text horizontally and vertically with all options..
• Displaying the background as the color and/or image.
• Display the border around the text, with the specified color, width and style.
• Formation of the text from the attributes of different types and properties.

Figure 4.2 represents a part of the screen with the frame containing the text examples using various parameters.

4.3. Primitive of the form element (FormEl)

Support of the form elements on the VCA frames is provided. The following form elements are included:

• Line edit — It is represented by the following types: "Text", "Combo", "Integer", "Real", "Time", "Date", "Date and time". All kinds of line editor support the confirmation of entry.
• Text edit — It is the flat-text editor with the confirmation or denial of entry.
• Check box — Provides a field of binary flag.
• Button — Provides the button with the support of: the color of the button, the image of the button, and mode of fixation.
• Combo box — Provides the selection field of the element from the list of the items.
• List — Provides the list box with the control of the current element.
• Tree — Provides the tree element with possibility of an item selection.
• Òàáëèöà — Provides the table element with possibility of a cell, a row or a column selection and a cell content edition.
• Slider — Slider element.
• Scroll bar — Strip of the scroll bar.

The following modes are realized: «Enable» and «Active», as well as transfer of changes and events to the data model of the VCA (engine).

Figure represents a part of the screen with the frame containing the above-listed elements of the form.

4.4. Primitive of the displaying the media materials (Media)

Support of the element of the displaying of media materials with the following properties is provided:

• The indication of the source of media data (images or video material).
• View of the images of most well-known formats with the possibility of inscribing of it in the size of the widget.
• Playback of the simple animated images and video formats with the possibility to control the playback speed.
• Full format video and audio playing by Phonon.
• Displaying of the the background as a color and/or image.
• Display the border around the text, with the specified color, width and style.
• Formation of the active areas and generating the events when they are activated.

Figure represents a part of the screen with the frame containing examples of viewing/playback of media data.

4.5. Primitive of the construction of diagrams/graphs (Diagram)

The diagrams construction element releases for types "Graph", "Spectrum" and "XY" with properties:

• General properties of the diagram types "Graph", "Spectrum" and "XY":
  • possibility for select an archivator, the archive's buffer or all the data at working with archiving data;
  • adapting the parameter's graph to real the data values in way the scales tune, at case the direct values range missing set;
  • controlling by axis ranges in way magnification/mitigation and shifting;
  • wide range scaling and adapting the time axis with automatic fitting the requested data to quality pretty for imaging, or needed for export — by set limited number measurements into pixel;
  • imaging dimensional grid and markers in horizontal and vertical with adapting to the imaging range;
  • tracing mode for current time by periodical update and switching the diagram time to current (time of last data into the archive buffer);
  • horizontal sliding by mouse;
  • scaling of a window selected part, by the mouse.
• Properties of the diagram type "Graph":
  • constructing graphics up to 100 parameters into single diagram as percent scale with possibility to display self axis for selected parameters;
  • constructing graph for: current, archiving and users data;
  • forming intermediate displaying buffer for current only values;
  • support active mode with cursor and getting the values under the cursor;
  • possibility of construction graphics as into both linear, and logarithmic values scale.
• Properties of the diagram type "Spectrum":
  • constructing graphics for frequency spectrum of the parameters up to 100 into single diagram as percent scale with possibility to display self axis for selected parameters;
  • constructing graph for: archiving and users data;
  • support active mode with cursor and getting the values under the cursor.
• Properties of the diagram type "XY":
  • constructing XY graphics up to 50 parameters into single diagram as percent scale with possibility to display self axis for selected parameters;
  • constructing graph for: current, archiving and users data;
  • forming intermediate displaying buffer for current only values;
  • the parameters distributed by pairs at one graph, where paired by axis Y (0,2,4...) and unpaired by axis X (1,3,5...);
  • possibility of construction graphics as into both linear, and logarithmic values scale.

The module of visualizer provides and uses set of specific attributes of the generic means, its information are into next table. Theses attributes create by the visualizer, on its lack, at a first start.

Figure represents a part of the screen with the frame containing examples of the diagrams: "Graph", "Spectrum" and "XY".

4.6. Primitive of the protocol formation (Protocol)

Support of the element of the formation of the protocol with the following properties is provided:

• Formation of the protocol from the archive of messages for the specified time and depth.
• Request of the data from the messages archivers.
• Selection of data from the archives by the level of importance and the category of messages template.
• Support the tracking mode for the appearance of messages in the archive of messages.

Figure represents a part of the screen with the frame containing an example of the protocol.

4.7. Primitive of the report formation (Document)

Support element of the report formation with the following properties is provided:

• Adaptive formation of a document structure based on Hypertext Markup Language. This provides support for the broad features of formatting of the documents.
• Formation of the documents on command or on schedule. It is necessary for creation of reports into the archive and then view the archive.
• Formation of a document in real time mode. It is necessary to form documents completely dynamically, and based on the archives for the specified time.
• Using of the the attributes of the widget for transmission of values and addresses to the archives in the report. It allows you to use the widget of the document as a template when generating reports with other input data.

The basis of any document is XHTML-template. XHTML-template is the tag "body" of the WEB-page which contains the document's static in the standard XHTML 1.0 and elements of the executable instructions in one of the languages of the user programming of OpenSCADA in the form of <?dp {procedure} ?>. The resulting document is formed by the execution of procedures and insert of their result into the document.

The source for values of the executable instructions are the attributes of the widget of the primitive, as well as all the mechanisms of the user programming language. Attributes may be added by the user and they can be linked to the actual attributes or parameters or they can be autonomous, values of which will be formed in the script of the widget. In the case of linked attributes the values can be extracted from the history, archive.

Figure shows the frame containing a sample of the document.

4.8. Primitive of the box container (Box)

Support of the primitive of the container concurrently serves as the project pages is provided. This primitive is the only element-container, which may include links to frames from the library, thereby creating the user elements of desired configuration. Primitive implements the provided by the project properties. The properties of this primitive are:

• Container — Allows you to form the desired objects by grouping in the limits of the primitive.
• Page — Elements constructed on the basis of the primitive may serve as a page of user interface.
• Container of pages — Property of substitution of its own contents by another page in the execution process. Used to create frames on the pages of user interface. For example, the main page of traditional SCADA system with alarm objects is constructed in this way.
• Background — Supports ability to specify the background as color or image.
• Border — Supports the displaying of the border, with the specified color, width and style.

Example of editing of the frame, based on the primitive, is shown in Fig. 2.a, and Fig. 3 shows a page containing the container of the pages, built on the basis of the primitive.

Action source page doesn't exist yet(/Home Page En / Doc / Vision / El Figure?)

6. The overall configuration of the module

To adjust your own behavior in not obvious situations the module provides the ability to customize individual settings through the management interface of the OpenSCADA (Fig. 6). These settings are:

• Module Status: running, the number of available screens in the library of Qt and active main widows list.
• The name of the remote OpenSCADA station with visualization engine VCA and the link to the configuration page of the external OpenSCADA stations.
• Initial user of the configurator — points on behalf of what user to open configurator without requiring the password, for local station. For remote station it is points to an user different from typical one, pointed into the host configuration.
• User password (remote station) — password of user different from typical one, pointed into the host configuration.
• Restore connection timeout, in seconds — points to time of the re-connection of a lost remote connection repeating.
• The lifetime of the pages in the cache. Visualizer provides acceleration of the user interface by placing a previously opened pages in the cache, to control the lifespan of pages in which the property and intended. Specifying a value of zero generally excludes cleaning the cache.
• The projects, by separate symbol ';', for their automatic execution with the launch of the module. To provide the possibility to indicate the opening of the window of the project execution on the desired display of many display systems the recording format of the project "PrjName-1" is provided, where 1 — the number of the target display. For connect to background or other opened session use "ses_{SesID}".

The display selection function possible for non virtual and non repeating desktop, i.e. with using Xinerma or NVidia into proper modes. Technical the function Qt screen() must return different display's widgets to it's number.

• Exit on last run project close — useful for solutions running at once on the interface of the project execution.

Fig.6. The configuration page of the module.