Module: | VCAEngine |
Name: | Visual control area engine |
Type: | User Interfaces |
Source: | ui_VCAEngine.so |
Version: | 2.9.0 |
Author: | Roman Savochenko, Maxim Lysenko (2011-2012) |
Description: | The main visual control area engine. |
License: | GPL |
The VCAEngine module provides visual control area engine (VCA) in OpenSCADA system. The module same does not implement the visualization of the VCA, and contains data in accordance with the ideology of "Model/data — Interface". Data visualization of that module is implemented by the visualization modules of VCA, such as Vision and WebVision.
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 project of the creation of the conception of the VCA? is established. The result of this project — the engine module(data model) of the VCA, as well as direct visualization modules Vision and WebVision.
This module of the engine (data model) of the VCA is aimed to create the logical structure of the VCA and the execution of sessions of individual instances of the VCA projects. Also, the module provides all the necessary data to the final visualizers of the VCA, both through local mechanisms of interaction of OpenSCADA, and through the management Interface of OpenSCADA for remote access.
The final version of the VCA module will provide:
Module itself does not contain mechanisms for visual creating interfaces of VCA, such tools can be given by the final visualization modules of the VCA, for example such a tool provides by the module Vision.
Although the mechanisms for the visual formation of the VCA the module doesn't provide the interface, implemented on the basis of the management interface of the OpenSCADA, to manage the logical structure is provided, and thus it is available for use in any system configurator of the OpenSCADA. Dialogues of this interface are considered further in the context of the architecture of the module and its data.
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 2?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 3?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 4?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 5?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 6?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 7?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 8?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 9?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 10?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 12?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 13?)
Action source page doesn't exist yet(/Home Page En / Doc / VC Aconcept / part 4 / part 14?)
Through the management interface of OpenSCADA, components that use it, can be configured from any system configurator OpenSCADA. This module provides an interface to access all the data object of the VCA. Main inset of the configuration page of the module provides access to widgets libraries and projects (Fig. 4.1). The tab "Sessions" provides access to opened sessions of projects (Fig. 4.2).
In addition to the list of open sessions the tab in Figure 4.2 contains a table with a list of sessions that must be created and run at boot time OpenSCADA. Creation of sessions through this tool can be useful for Web-based interface. In this case, when connecting Web-user data is ready and ensures the continuity of the formation of archival documents.
The configuration of container widgets in the face of libraries and widget projects is done through pages in Fig. 4.3 (a project) and Fig.4.5 (a library of widgets). Widgets library contains the widgets, and project — the pages. Both types contain a tab of configuration Mime-data used widgets (Fig.4.6). The project page also contains the tab "Diagnostics" (Fig.4.4) for debug and control all the page's executions by sessions.
From this page you can set:
From this tab you can select time, or refresh to current, and size for diagnostic messages obtain of the sessions of running the project.
From this page you can set:
Configuration of the project's session differs significantly from configuration of the project (Fig. 4.8), but also contains pages of the project.
From this page you can set:
The configuration pages of visual elements, placed in different containers, may be very different, but this difference is the presence or absence of individual tabs. The main tab of visual elements in fact is the same everywhere, differing in one configuration field (Fig. 4.8). The pages contains the tabs of the child pages and embedded widgets. The container widgets contains the tab of the embedded widgets. All visual elements contain attributes tab (Fig. 4.9), except the logical containers of the projects. Elements, at the level of which it is possible to build the user procedure and to determine the links, contain the tabs "Process" (Fig. 4.10) and "Links" (Fig.4.11).
From this page you can set: