From OpenSCADAWiki
Jump to: navigation, search
Other languages:
Constr.png Moving from the old Wiki, appending, the translation checking and actualizing
Name Version License Source Languages Author Description
Main elements library of the user interface 1.5 GPLv2 vcaBase.db (SQL, GZip) > VCA.wlb_Main en, uk, ru Roman Savochenko
  Maxim Lysenko (2011-2012)
Provides the library of the main elements of the user interface of common and the industrial automation.

The library is created to provide main elements of the user interface. The library is built on the basis primitives of the widgets and the internal programming language JavaLikeCalc.

For connection the library to a project of the OpenSCADA station you can obtain the database file as:

  • supplied with a ready and proper package of the Linux distribution like to "openscada-libdb-main", "openscada-LibDB.Main";
  • directly taken for most actual one from the subversion repository and converted to the DB SQLite file in the way:
$ wget http://oscada.org/svn/trunk/OpenSCADA/data/LibsDB/vcaBase.sql
$ sqlite3 -init vcaBase.sql vcaBase.db .exit

The library contains about two dozen graphic elements, often need when forming the user interface of the automation of technological and common processes. Names and text options are available in three languages: English, Ukrainian and Russian.

1 Widgets — graphical elements

1.1 Analog show (anShow)

1.1 GPLv2 * en, uk, ru Roman Savochenko

The element on Figure 1.1 is used to display the current value of the analog parameter and the regulator mode, if the parameter is a regulator. Also this element generates notifications of violations on the corresponding parameter settings. The element commonly uses and represents the representative structure of the "Analog signal" DAQ-template.

Fig.1.1. The "Analog show" widget in the development and the runtime modes (left to right).

Using — development
This widget can be used by the developer to create mnemonic schemes with displaying of values of the analog parameters and PID-regulators. To use it you need to add this widget to a mnemonic scheme, adjust for the horizontal, vertical size, by scaling, and link to the data source parameter.

Using — runtime
In the runtime mode, in the main field of the element, there are displayed the parameter name, the regulator mode (only for the regulators) and the current value-variable of this parameter; which, depending on the presence of a violation, are displayed in the color style: labColorGood, labColorWarning, labColorAlarm; and in which value the image of the inquieted parameter may blink. At the hardware errors and non validity the data, the last value is grayed out and crossed out.

In the active mode of the element you can obtain the parameter passport clicking the right mouse button on the body of the widget. The passport will present all properties of the parameter. Pressing the left mouse button in the widget body will cause to appear for control panel of the parameter, and the selection of this widget will be displayed with the blinking frame.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
pErr Parameter: error String Input link Parameter|err Code and text of the parameter error. It is used to generate alarm. The following error codes are processed:
  • 1,2 — failure, parameter is not valid, be shown in gray and cross out besides the case with redEVAL;
  • 3,4 — above and below the alarm limit, be shown in the styled color labColorAlarm;
  • 5,6 — above and below the warning limit, be shown in the styled color labColorWarning;
  • 10,11 — the user alarm codes of the statuses warning and alarm, be sown accordingly in the styled color labColorWarning and labColorAlarm.
pModeA Parameter: regulator mode: auto Boolean Input link Parameter|auto The large letter "A" is displayed on the left when the value checked.
pModeC Parameter: regulator mode: cascade Boolean Input link Parameter|casc The large letter "C" is displayed on the left when the value checked.
pName Parameter: name String Input link Parameter|NAME Short name of the parameter displayed over the value and inserted to the alarm messages.
pPrec Parameter: precision Integer Input link Parameter|prec Number signs after the dot, for positive values, and precision (signs in whole), for negative, to display the real end variable on the screen.
pVal Parameter: value Real Input link Parameter|var Engineeric real value of the parameter
redEVAL Red parameter name in case of failure Boolean Constant By default, the color of the parameter's name for the "failure" state (EVAL value) is gray. But some critical for the process parameters must have the "failure" state displayed with the red parameter's name.
spName Speech name String Constant The parameter name for speech synthesis during the formation of alarm messages taking into account accents of words, pauses, etc. Empty value disables the speech notification!

1.2 Analog show 1 (anShow1), Analog show 1 (short) (anShow1s)

1.1 GPLv2 * en, uk, ru Roman Savochenko

The element on Figure 1.2 is used to display the current value of the analog parameter and a short prefix of the measured value type. Also this element generates notifications of violations on the corresponding parameter settings. The element commonly uses and represents the representative structure of the "Analog signal" DAQ-template.

These two elements differ only in their initial horizontal size, that is, the second "Analog show 1 (short)" is a short version for very short cases and it is directly inherited from the first one.

Fig.1.2. The "Analog show 1" widget in the development and runtime modes (left to right).

Using — development
This widget can be used by the developer to create mnemonic schemes with displaying of values of the analog parameters with a prefix and/or as an element of the static screen table. To use it you need to add this widget to a mnemonic scheme, adjust for the horizontal, vertical size, by scaling, and link to the data source parameter.

Using — runtime
In the runtime mode, in the main field of the element, there are displayed the short prefix and the current value-variable of this parameter; which, depending on the presence of a violation, are displayed in the color style: labColorGood, labColorWarning, labColorAlarm; and in which value the image of the inquieted parameter may blink. At the hardware errors and non validity the data, the last value is grayed out and crossed out.

In the active mode of the element you can obtain the parameter passport clicking the right mouse button on the body of the widget. The passport will present all properties of the parameter. Pressing the left mouse button in the widget body will cause to appear for control panel of the parameter, and the selection of this widget will be displayed with the blinking frame.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
pErr Parameter: error String Input link Parameter|err Code and text of the parameter error. It is used to generate alarm. The following error codes are processed:
  • 1,2 — failure, parameter is not valid, be shown in gray and cross out;
  • 3,4 — above and below the alarm limit, be shown in the styled color labColorAlarm;
  • 5,6 — above and below the warning limit, be shown in the styled color labColorWarning;
  • 10,11 — the user alarm codes of the statuses warning and alarm, be sown accordingly in the styled color labColorWarning and labColorAlarm.
pNAME Parameter: name String Input link Parameter|NAME Short name of the parameter inserted to the alarm messages.
prec Parameter: precision Integer Input link Parameter|prec Number signs after the dot, for positive values, and precision (signs in whole), for negative, to display the real end variable on the screen.
pVal Parameter: value Real Input link Parameter|var Engineeric real value of the parameter
spName Speech name String Constant The parameter name for speech synthesis during the formation of alarm messages taking into account accents of words, pauses, etc. Empty value disables the speech notification!
pName Short name String Constant Short name-prefix value
pNameSz Short name size Integer Constant Size of the short name-prefix in pixels, use the zero value to disable the field


1.3 Text label (TextLab)

1.0 GPLv2 * en, uk, ru Roman Savochenko

The element on Figure 1.3 is used to display the dynamic text labels, which form on basis of the discrete signals. Also this element generates notifications of violations on the locally defined condition, the attribute ntf. The element commonly uses and represents the representative structure of DAQ-templates of the discrete block and the code state.

Fig.1.3. The widget "Text label" in the development and runtime modes (left to right).

Using — development
This widget can be used by the developer to create mnemonic schemes with displaying of text labels and/or as an element of the static screen table. To use it you need to add this widget to a mnemonic scheme, adjust for the horizontal, vertical size and link to the data source parameter.

Using — runtime
In the runtime mode, in the main field of the element, there are displayed the text label, what related to values of the discrete signals of the parameter and the attribute digStts configuration; where the background, depending to availability of a violation related to the attribute ntf condition, sets to the violation color; and to what the inquieted parameter may blink. At the hardware errors and non validity the data, the background shows in the gray color.

In the active mode of the element you can obtain the parameter passport clicking twice the left mouse button on the body of the widget. The passport will present all properties of the parameter. Pressing the left mouse button in the widget body will cause to appear for control panel of the parameter, and the selection of this widget will be displayed with the blinking frame. The commands are duplicated in the context menu that appears when the right mouse button is pressed in the widget area.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
NAME Parameter: name String Input link Parameter|NAME Short name of the parameter inserted in the notification of violation and actions of the user operator.
DESCR Parameter: description String Input link Parameter|DESCR Description or long name of the parameter inserted in the notification of actions of the user operator.
st_open Parameter: status-open Boolean Input link Parameter|st_open The state "Opened" of the parameter or the common state of the switch at missing the state signal "Closed".
st_close Parameter: status-close Boolean Input link Parameter|st_close The state "Closed" of the parameter
st_text Parameter: status (text) String Input link Parameter|st_text Text of the parameter state, at the mode "Code state"
digStts Parameter: statuses String Input link Parameter|digStts Configuration of the parameter statuses with the structure {openedLabel}-{color};{closedLabel}-{color}, for the discrete block.
com Parameter: command Boolean Full link Parameter|com The command "Open" of the parameter or the common command of the switch at missing the command signal "Close".
close Parameter: close Boolean Full link Parameter|close The command "Close" of the parameter.
stop Parameter: stop Boolean Full link Parameter|stop The command "Stop" of the parameter.
com_text Parameter: command text (from digComs) String Full link Parameter|com_text Text of the parameter command, at the mode "Code state"
digComs Parameter: commands String Input link Parameter|digComs Configuration of the parameter commands with the structure {openLabel}-{color};{closeLabel}-{color}, for the discrete block, and {com1Label}-{color};{com2Label}-{color};...;{comNLabel}-{color}, for the code status.
ntf Notification "{st}:{modes}:{Speech text}" String Constant Configuration of the notification forming at the status (st) [0|1] and the notification modes-methods (modes), as a string of the digital methods, and by the speech, if pointed such method.


1.4 Image label (ImgLab)

1.0 GPLv2 * en, uk, ru Roman Savochenko

The element on Figure 1.4 is used to display the dynamic image labels, which form on basis of the discrete signals. Also this element generates notifications of violations on the locally defined condition, the attribute ntf. The element commonly uses and represents the representative structure of DAQ-templates of the discrete block and the code state.

Fig.1.4. The widget "Image label" in the development and runtime modes (left to right).

Using — development
This widget can be used by the developer to create mnemonic schemes with displaying of image labels and/or as an element of the static screen table. To use it you need to add this widget to a mnemonic scheme, adjust for the horizontal, vertical size and link to the data source parameter.

Using — runtime
In the runtime mode, in the main field of the element, there are displayed the image label, what related to values of the discrete signals of the parameter and the attribute imgs configuration; where the background, depending to availability of a violation related to the attribute ntf condition, sets to the violation color; and to what the inquieted parameter may blink. At the hardware errors and non validity the data, the background shows in the gray color.

In the active mode of the element you can obtain the parameter passport clicking twice the left mouse button on the body of the widget. The passport will present all properties of the parameter. Pressing the left mouse button in the widget body will cause to appear for control panel of the parameter, and the selection of this widget will be displayed with the blinking frame. The commands are duplicated in the context menu that appears when the right mouse button is pressed in the widget area.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
NAME Parameter: name String Input link Parameter|NAME Short name of the parameter inserted in the notification of violation and actions of the user operator.
DESCR Parameter: description String Input link Parameter|DESCR Description or long name of the parameter inserted in the notification of actions of the user operator.
st_open Parameter: status-open Boolean Input link Parameter|st_open The state "Opened" of the parameter or the common state of the switch at missing the state signal "Closed".
st_close Parameter: status-close Boolean Input link Parameter|st_close The state "Closed" of the parameter
st_img Parameter: status "{img}:{bCol}:{blink}" String Input link Parameter|st_text Image of the parameter state, at the mode "Code state", where:
  • img — image name, see the image attributes;
  • bCol — background color;
  • blink — blink sign [0|1] of the background.
imgs Images, for "{openedImage}-{bCol}:{closedImage}-{bCol}:{EVAL}-{bCol}" String Constant Configuration of the parameter statuses with the structure {openedLabel}-{color};{closedLabel}-{color};{EVALLabel}-{color}, for the discrete block.
digStts Parameter: statuses String Input link Parameter|digStts Standard configuration of the parameter statuses with the structure {notUsed}-{openedColor};{notUsed}-{closedColor}', for the discrete block and missing of the attribute imgs.
com Parameter: command Boolean Full link Parameter|com The command "Open" of the parameter or the common command of the switch at missing the command signal "Close".
close Parameter: close Boolean Full link Parameter|close The command "Close" of the parameter.
stop Parameter: stop Boolean Full link Parameter|stop The command "Stop" of the parameter.
com_text Parameter: command text (from digComs) String Full link Parameter|com_text Text of the parameter command, at the mode "Code state"
digComs Parameter: commands String Input link Parameter|digComs Configuration of the parameter commands with the structure {openLabel}-{color};{closeLabel}-{color};{stopLabel}-{color}, for the discrete block, and {com1Label}-{color};{com2Label}-{color};...;{comNLabel}-{color}, for the code status.
ntf Notification "{st}:{modes}:{Speech text}" String Constant Configuration of the notification forming at the status (st) [0|1] and the notification modes-methods (modes), as a string of the digital methods, and by the speech, if pointed such method.


1.5 Alarms: active (alarmsAct)

1.1 GPLv2 * en, uk, ru Roman Savochenko

Constr.png Waiting to form ...


1.6 Object properties (objProps)

1.1 GPLv2 * en, uk, ru Roman Savochenko

Constr.png Waiting to form ...


1.7 Calendar (calendar)

1.0 GPLv2 * en, uk, ru Roman Savochenko

Constr.png Waiting to form ...


2 Root page (SO) (RootPgSo)

2.2 GPLv2 * en, uk, ru Roman Savochenko

The element-frame, shown in Figure 2a, serves as the basis for the user interfaces creating, initially for control the technological processes, grounded on the signal objects (SO).

The root page contains four areas:

  • signal objects area of the buttons-indicators (top);
  • navigation area by types of view (right-top);
  • container of the main frames of the user interface (in the center);
  • container of the control panels (right-bottom).

Signal objects area of the buttons-indicators provides information on the presence of violations in the signal object and for switching between them.

To show the signal objects selection the background color is used, by the styles: backColorButton and backColorButtonSel. And the violations are displayed in the color of the text according to the styles: labColorGood, labColorWarning, labColorAlarm; and in which value the text of the inquieted signal object may blink.

Buttons are currently generated dynamically by copying the first and only, according to the virtual pages of the signal objects in the project tree, with the serial digital identification from 1. The limitation on the number of buttons or signal objects is only the total length of the names of the signal objects that can be placed in two rows of these buttons. That is, for short names we can get up to near 100 signal objects. If the signal object is one, even this single base button is hidden.

Navigation area by types of view — indication of the choice and selection of the type of view, such as: "Mnemonic schemes", "Graph groups", "Contour groups", "Documents" and more; and the listing buttons or the direct selection combobox of the frames into the signal object.

The buttons area of the types of view is dynamic, in the sense of occupying the space of the missing ones, and the meaning of the types of view themselves are configured to different from the default value, i.e. there are two main types of view (view1 and view2), three auxiliary (view3, view4 and view5), as well as one common to the whole interface (view6).

Below are also the buttons of quietation those appear in the event of violations, and at the top is a customizable logo.

Container of the main frames of the user interface — the area of the container for inclusion in it of the basic frames by their choice of buttons of types of view or change of the signal object.

Container of the control panels — container area to include control panels of various objects in the container area of the main frames, for example — panel of the parameter, document, graph and more.

Under the control panels container placed a button to start the demo mode — mode in which performed periodic switching for representative frames, changing regimes and other operations by a scenario.

Fig.21. The "Root page (SO)" frame in the development mode.

Using — development
This widget can be used only in the root page mode that should be placed in the project's tree as an element "so". Additionally, around the main page should be made following tree hierarchy:

/control/* — logical container, contains a variety of control panels;
/so/ — this frame as a container, contains of logical containers of the signal objects:
{n}/ — logical container of the signal object n (1...), contains logical containers and templates of the types of view:
[view1|mn]/* — the type of view 1 (typically and early it is the mnemonic schemes), contains a lot of pages of the end frames;
[view2|ggraph]/* — the type of view 2 (typically and early it is a template of the graphics group), contains a lot of pages of the end frames;
[view3|gcadr]/* — the type of view 3 (typically and early it is a template of the contours group), contains a lot of pages of the end frames;
[view4|gview]/* — the type of view 4 (typically and early it is a template of the overview frames panel), contains a lot of pages of the end frames;
[view5|doc]/* — the type of view 5 (typically and early it is a logical container of the documents), contains a lot of pages of the end frames;
greg/* — the specific page template of the PID-regulator configuration, contains a lot of pages of the end PID-regulators configuration, statically connected and which are call only by the "PID" button of the element cadre.
[view6|rg]/ — logical container of the global type of view 6 (typically and early it is the result graphics — common graphs for the entire interface):
[view6|rg]/* — the type of view 6 (typically and early it is a template of the result graphics), contains a lot of pages of the end frames.

At.png Identifiers of the pages of the types of view, specified as [view1|mn], must be specified in the tree either in the new scheme "view1" or in the old scheme "mn". Mixing is not supported!

As the text of the signal object buttons, there are used name of the logical container with the corresponding n identifier. The description of this container also takes the text of the tooltip to this button if it is not empty. Description of the container also taken into tooltip for this button, if it is not empty.

All further adjustments and edits around this frame must be made for its copy-link in the project tree, and it is strongly not recommended to edit it in the library, otherwise you will lose the ability to update the library or these changes when updating it!

The text and the tooltip of the buttons of the types of view are directly changed in the corresponding properties of these widgets. The fast keys of the type of view are taken from the toolbar brackets, such as "Graphs (Ctrl+G)", and processed accordingly. To change the image of the type of view, it is enough to override the icon of the corresponding view, such as "view1", by loading the image with the appropriate name in the project Mime-data.

You can change the image of the logo in the same way as the image of the type of view, that is, upload a new image called "logo" to the project's Mime-data, and then adjust the geometry of the logo widget to the desired proportions. You can move the image widget to the left by moving the signal object button to the right by the size of the logo. If you do not need the logo at all then to nullify the widget width, but do not remove it!

Potentially, you can also move the navigation bar and the control panel container to the left by moving the main frame container, and maybe the signal object button, to the right.

If necessary, the root page can be appended with additional elements that do not require special processing, that is, changes to the initial procedure of the frame, that is no longer using but editing. For example, the root page is often appended by the generic table of active violations, that can be placed under the main frame container at its entire width, reducing its height by the desired size of the table. At.png It should be noted here that reducing the size of this container, like any other, will lead to the appearance of scrollbars and-or will require adjusting the frames of placement in the container. In the example above, this may not be necessary given the extension of the container to unused button rows of the signal objects.

In the absence of the Demo-mode, you may turn off the Demo launch button and expand the control panel.

Using — runtime
When starting the frame in the runtime mode, there are first constructed the buttons of the signal objects, which are formed in two rows, after which the container of the main frames expands up for one row if there is enough one, or for two if the signal object is one. Next, there are formed buttons of the types of view, present of which are activated and expanded to fill the space of the missing ones.

After the dynamic forming, the frame periodically controls the frame change in the main frame container, which is displayed by the corresponding background color in a button of the signal object and the type of view to which the frame belongs. Between the listing buttons, information about the total number of frames and the current position is updated, and the buttons themselves are activated according to the possibility of listing in the current frame position. For the combobox of direct frames selection from list, respectively, the current list of frames is formed and the name of the current one is set. It also monitors the status of violation-notification of the signal objects, which is accordingly displayed by the text color of the buttons of the signal object and its flashing, as well as the quietation buttons are activated or deactivated.

Changing of the frame in the control panel container are not tracked and their are generally called from the main frame interface, unless it is cleared by changing the main frame by opening the panel-terminator.

From the basic actions, the frame allows the user to select the signal object, the type of view and the corresponding frame. By pressing the button of the signal object, the type of view, directly selecting in the combobox or listing; resulting in a call to the corresponding frame in the main frame container. From the ancillary actions, the user can quiet the violation-notification and start the Demo-mode, if one provided. The default frame setting involves servicing a number of hotkeys, such as Ctrl+[1...0] to call the signal objects 1 to 10, and Ctrl+[MGCVDR] to call appropriate types of view.

Figure 2b shows an example of this element in the runtime mode.

Fig.2b. The "Root page (SO)" frame in the runtime mode.

Linking and configuring the attributes

Identifier Name Type Description
demoPlayProc Procedure of the Demo play Text A procedure on the JavaLikeCalc language to play some demo. Enables the Demo-mode button in the runtime mode. To an example of such procedure see the demo-projects AGLKS and Boiler!
The visualizer specific attributes common for both UI.Vision (more) and UI.WebVision (more)
keepAspectRatio Keep aspect ratio on scale Boolean Keep aspect ratio of the pages on scale.
stBarNoShow Do not show the status bar Boolean Hide the status bar of the main window.
The visualizer specific attributes for UI.Vision (more)
runWin Run window Integer numbers selection Setting the mode of the main window execution:
  • "Original size (0)".
  • "Maximize (1)".
  • "Full screen (2)".
statLine Status line items Text Text field with description of the status line items.
winPosCntrSave Windows position control and save Boolean Enabling the windows position control and save.
Main procedures of the notification mechanism
notify2 Notification: type 2 (TextSpeech) Text
notifyVisVision0 Notification: Vision type 0 (Light) Text
notifyVisVision1 Notification: Vision type 1 (Buzzer) Text
notifyVisVision2 Notification: Vision type 2 (TextSpeech) Text

3 Main cadres

3.1 Graphics group (grpGraph), Graphics group 10 (grpGraph10)

1.4 GPLv2 * en, uk, ru Roman Savochenko

The element-frame, shown in Figure 3.1a, is provided for simultaneous observation of trends and control the parameters in the signal object, includes both instances of the widget "Graphics group element (ElViewGraph)" of each parameter (up to 8 or 10) and the widget "Diagram" to monitor the parameters' trends and browsing history, and also the scroll bar for fast navigation on allowed history of selected parameters for show.

Fig.3.1a. The "Graphics group" widget in the development mode.

Using — development
The widget is designed to perform the role of page-template, and should therefore be placed directly in the project's tree. In the project-template "Signal groups", for each signal object, this widget-frame is included in the role of a template that allows you to create on its basis a set of pages of the graphics group. To each widget-frame can be connected up to eight-ten parameters, setting the links. Trends, for which there are not set the links, will be hidden at runtime or allowed for user's selection at case of presence the list of the parameters to select in the attribute "Select: parameters accessible to select" (the list format described in the parameters selection dialog).

Using — runtime
In the runtime mode, the trends, for which links have been set, are displayed. Control of the parameters from the graphics group element, described in detail in the section of the "Graphics group element (ElViewGraph)" widget. Additionally you can control the display properties of graphs, for what, together this page, there automatically opens the graph control panel or you have to click the left mouse button in the graph area.

Figure 3.1b shows an example of this element in the runtime mode.

Fig.3.1b. The "Graphics group" widget in the runtime mode.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
name Name String Constant Group name
allowSelLst Select: parameters accessible to select Text No Place here the parameters for selection by the user in a list of the DAQ-paths to them (for more details see the "Graph parameter selection" dialog):
/LogicLev/proc/prm_CPU/prm_load
/LogicLev/proc/prm_MEM/prm_use
/LogicLev/proc/prm_CPU/prm_T 
perUserSel Select: save the selection per user Boolean No Set to save the user selection separately
Element {n} from 1 to 8(10)
el{n} List of the linking parameters corresponds to the list of the "Graphics group element (ElViewGraph)" widget


3.1.1 Graphics group element (ElViewGraph)

1.3 GPLv2 * en, uk, ru Roman Savochenko

Element, shown in Figure 3.1.1a, is provided to create graphics groups. Element contains information about a parameter, the regulator mode, if the parameter is such, the units of analog parameter, as well as the color corresponding to the parameter's trend. The element commonly uses and represents the representative structure of the DAQ-templates "Analog signal" and "Discrete block".

Fig.3.1.1a. The "Graphics group element" widget in the development mode.

Using — development
Though this widget is not intended for independent use, in isolation from the graphics groups, it can be used, for example, placing it to the mnemonic scheme and linking with the data source parameter.

Using — runtime
In the runtime mode, in the main field of the element, there are displayed the parameter name, the regulator mode (only for the regulators), the current value-variable and the unit of this parameter; which, depending on the presence of a violation, are displayed in the color style: labColorGood, labColorWarning, labColorAlarm. At the hardware errors and non validity the data, the last value is grayed out.

Except the available visual data, a number of control elements are provided:

  • "Selection" — at pressing the left mouse button in the widget area, in the right side will appear the control panel, and the widget selection will be displayed by the border flashing.
  • "Hide/Show" — double-clicking in the widget area toggles the show-hiding of the item's graph.
  • "Context menu functions" — a number of functions are provided through the context menu:
    • "Passport" — getting the passport of the parameter, which will present all it properties.
    • "Hide/Show" — toggling the display or hiding of a graph of this element, similar to a double click.
    • "Show one" — single graph display of the selected parameter in its native scale by hiding the rest of the items in the group.
    • "Show all" — display all parameter graphs in the group.
    • "Calculating" — calling the calculating dialog above the visible data of the selected parameter.
    • "Select" — calling the selection dialog of parameter from the list of ones available for selection, the attribute "Select: parameters accessible to select" of the owner cadre. This item is only available if a selection list is available.

The widget saves of a user selected parameter in the session table of the project and loads the parameter at next run, include the trend color which default value typically takes from a style.

Figure 3.1.1b shows various examples of this element in the runtime mode.

Fig.3.1.1b. The "Graphics group element" widget in the runtime mode.

Linking and configuring the attributes

Identifier Name Type Configuration Configuration template Description
name Name String Input link Parameter|NAME Parameter name-code, to display in the name field.
dscr Description Text Input link Parameter|DESCR Parameter description, to place in the tooltip and statusbar.
addr Address Address Input link Parameter|var Address to the parameter attribute for the trend building.
color Graphic color String No Working color of the trend
colorDef Default color from the style String No Default color of the trend on the cadre level
Analog parameters
ed Dimension String Input link Parameter|ed
prec Precision Integer Input link Parameter|prec Number signs after the dot, for positive values, and precision (signs in whole), for negative, to display the real end variable on the screen.
log Logarithmic scale Boolean Input link Parameter|log
max Maximum Real Input link Parameter|max Upper limit value of the parameter.
min Minimum Real Input link Parameter|min Minimum limit values of the parameter.
aMax Border up alarm Real Input link Parameter|aMax
aMin Border down alarm Real Input link Parameter|aMin
wMax Border up warning Real Input link Parameter|wMax
wMin Border down warning Real Input link Parameter|wMin
pModeA Regulator mode: auto Boolean Input link Parameter|auto The regulator mode "Automatic".
pModeC Regulator mode: cascade Boolean Input link Parameter|casc The regulator mode "Cascade".
Discrete parameters
digComs Digital: commands String Constant Names and colors of the buttons of the commands are in the format {On}[-color]:{Off}[-color][:{Stop}[-color]]. Default colors are: green, red and yellow.
digStts Digital: states String Constant Names and colors of the labels of the states are in the format {On}[-color]:{Off}[-color]. Default colors are: green and red.
digRevers Digital: reversion Boolean Constant Discrete signal reverse.


3.1.2 Graph parameter selection (graphSelPrm)

1.4 GPLv2 * en, uk, ru Roman Savochenko

The element, shown in Figure 3.1.2, implements a dialog of selection the data source, often the archive ones, for the trend formation in the "Graphics group" frame. Selection is provided from the list, specified in the attribute "Select: parameters accessible to select (allowSelLst)" of the frame-initiator. For the selected source you can specify the name, scale, logarithmic scale, dimension and the color of the trend.

In the "Select: parameters accessible to select (allowSelLst)" attribute the data sources should be placed in the following way:

  • {DAQ_Arh_addr}[:Name[:min:max[:dim]], where:
    • "DAQ_Arh_addr" — address of the parameter, for the group linking, or address of the attribute with data from the "Data acquisition (DAQ)" subsystem, as well as the address of the values' archive, for example:
      • /LogicLev/experiment/prm_F3 — address of the "F3" parameter ;
      • /DAQ/System/AutoDA/prm_CPULoad/load — address of the "load" attribute of the "CPULoad" parameter;
      • /Archive/va_LC21_1_var — address of the "LC21_1_var" archive.
    • "Name" — name of the source to display. At the group linking the name will be taken from the "NAME" attribute.
    • "min", "max" — display scale. At group linking the scale will be taken from the "min" and "max" attributes, respectively. In the case of the scale absence (min >= max) the auto-scale will be enabled.
    • "dim" — dimension (measuring unit) of the parameter to display. At the group linking it will be taken from the "ed" attribute.
  • <varhs> — template of the group selection, if you specify it all available archives in the system will be included into the selection list.

Examples of the "Select: parameters accessible to select (allowSelLst)" attribute's content:

/System/AutoDA/prm_CPULoad/load:CPU Load:0:100:%
/LogicLev/experiment/prm_F3
<varhs>
Fig.3.1.2. The "Graph parameter selection" frame in the development and runtime mode.

Using — development
This frame should be placed to the panels' logical container of the project tree. The "Select: parameters accessible to select (allowSelLst)" attribute must be defined to a list of sources according to the rules described above in the "Graphics groups", which should provide the selection of the sources by the user. As a result, the "Select" item will appear in the context menu of the Graphics group element.

Using — runtime
Calling the dialogue is made by the "Select" item of the Graphics group element context menu. The dialogue provides the user to the possibility of selection the data source from the list, as well as an indication of its basic parameters: name, scale, logarithmic scale, dimension and the color of the trend. When you accept the dialogue the selected parameters are applied to the graphics group element chart, replacing the links. The "<Clear>" item selection and applying causes to clearing all the links and the graph's item. Into a text field under the list you can rapidly find any needed parameter.


3.1.3 Graph parameter calculation (graphCalc)

1.0 GPLv2 * en, uk, ru Roman Savochenko

The element, shown in Figure 3.1.3, implements a dialog of user calculation of the selected graph parameter for the graphically visible data. The user is given an option to select calculations from the built-in library, the privileged user ("root" or in the "ITW" group) has the opportunity to edit or write their own calculation procedure.

In general, the built-in library currently contains the following functions of the user calculation:

  • Sum, at hour.
  • Average and range.
Fig.3.1.3. The "Graph parameter calculation" frame in the development and runtime mode.

Using — development
This frame should be placed to the panels' logical container of the project tree.

Using — runtime
Calling the dialogue is made by the "Calculation" item of the Graphics group element context menu. The dialog gives the user the choice of the function of calculation the visible data of the selected parameter and the ability to edit-write their own function, for the privileged user. The calculation result is located in the corresponding text box.


3.2 Contours group (grpCadr)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 5, provides for simultaneous monitoring and control of several contours up to eight, includes both instances of the widget "Element cadr for each contour, and a widget "Diagram" to monitor the trends of the contours and viewing history .

Fig.5. The "Contours group" widget in the development mode.

Using — Development
This widget is designed to perform the role of page-template, and should therefore be placed directly in the project's tree. The project-template "signal groups" for each signal object that widget-frame is included in the role of a template that allows you to create on its basis a set of pages of groups of contours. For each widget-frame, it can be connected up to eight parameters by setting the links. Contours for which there is no set links will be hidden at runtime.

Using — Runtime
In runtime mode, the contours and trends, for which links have been set, are displayed. Control of the parameters by contours, respectively described in detail in the section of the "Element cadr (ElCadr)" widget. In addition to this you can control the trends display properties, which requires the left mouse button to click in the trend's area and by means of appeared trend's control panel to make the necessary actions.

Figure 6 is an example of this element in the runtime mode.

Fig.6. The "Contours group" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
grpName Group name String Constant Group's name
Element {n} from 1 to 8.
el{n} The list of linking parameters corresponds to the list of the "Element cadr (ElCadr)" widget

3.3 Overview frames panel (ViewCadr)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 9, serves to show the current trends for the parameters of the signal object up to 24 pieces, supports scaling elements depending on their number. Consists of widgets "views page's element (ElViewCadr)".

Fig.9. The "Overview frames panel" widget in the development mode.

Using — Development
This widget is designed to perform the role of template-page, and should therefore be placed directly in the project's tree. The project-template "signal groups" for each signal object that widget-frame is included in the role of a template that allows you to create on its basis a set of pages of groups of overview frames panel. To each widget-frame can be connected to the 24-parameter by setting the links. Trends for which there is no set links will be hidden at runtime, and when it is necessary the expansion and scaling of linked ones will be done to fill the area of the widget.

Using — Runtime
In the runtime mode the trends' contours are displayed, for which links have been set. Control of the parameters from contours, respectively described in details in the section "views page's element (ElViewCadr)" widget.

Figure 10 shows an example of this element in the runtime mode.

Fig.10. The "Overview frames panel" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
name Name String Constant Frame's name
Element {r}_{c}, where {r} - rows from 1 to 4 and {c} - columns from 1 to 6.
el{r}_{c} The list of linked parameters corresponds to the list of ones of the "Views page's element (ElViewCadr)" widget

3.3.1 Views page's element (ElViewCadr)

Element, shown in Fig. 7, serves as the basis for overview frames panel and is not usually used independently. Element reflects the text information about a parameter in the form of the name and value, and a graph (trend) of the parameter for a small (adjustable) period of time to observe the current trend of the parameter with auto-scaling on the value's scale.

Fig.7. The "Views page's element" widget in the development mode.

Using — Development
Though this widget is not intended for independent use, in isolation from overview frames panel, it can be used, for example, by placing it to the mimic and linking with the data source parameter.

Using — Runtime
At runtime mode, you can obtain the passport for parameter by clicking the right mouse button on the body of the widget. The passport will present all the properties of the parameter. Pressing the left mouse button in the body of the widget the control panel will appear parameter, and the selection of this widget will be displayed with blinking frame.

Figure 8 shows various examples of this element in the runtime mode.

Fig.8. The "Views page's element" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
name Name String Input link Parameter|NAME Parameter name, code, for display in the name's field.
addr Address Address Input link Parameter|var Address to the attribute of the parameter's values for trend's building.
var Variable Real Input link Parameter|var Direct value of the parameter to display in value's field.

3.4 Result graphics (ResultGraph)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 17, is used to display the trends of the parameters of the whole visualization project.

Fig.17. The "Result graphics" widget in the development mode.

Using — Development
This widget is designed to perform the role of page-template, and should therefore be placed directly in the project's tree. In the project-template "signal groups" on the root page level there is special virtual page "Result graphics" with the result graphics template, that allows you to create on its basis a set of pages of result graphics. To each widget-frame can be connected to the 16*5 parameters by setting the links. Trends, for which there is no set links, will be hidden at runtime, and when it is necessary the expansion and scaling of linked ones will be done to fill the area of the widget.

Using — Runtime
In runtime the contours of the trends, for which the links are set, are displayed.

Figure 18 shows an example of this element in the runtime mode.

Fig.18. The "Result graphics" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
grpName Group name String Constant Group name
Element {n} from 1 to 16.
el{n} The list of linking parameters corresponds to the list of the "Result graphic's element (ResultGraphEl)" widget.

3.4.1 Result graphic's element (ResultGraphEl)

Element, shown in Figure 15, is provided to create result graphics. Element allows you to display trends on the five parameters for a specified period of time till the current time.

Fig.15. The "Result graphic's element" widget in the development mode.

Using — Development
Though this widget is not intended for independent use, in isolation from result graphics, it can be used, for example, by placing it to the mimic and linking with the data source parameter.

Figure 16 shows an example of this element in the runtime mode.

Fig.16. The "Result graphic's element" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
title Title String Constant It is displayed above the graph. If the title is missing the trend's field will expand up.
Trend {n} from 1 to 5.
p{n}_addr Parameter{n}:address Address Input link Parameter_{n}|var Address to the value's attribute for {n} trend's building.
p{n}_clr Parameter{n}:color Color Constant Parameter_{n}
p{n}_max Parameter{n}:maximum Real Input link Parameter_{n}|max Upper limit of the trend.
p{n}_min Parameter{n}:minimum Real Input link Parameter_{n}|min Lower limit of the trend.
p{n}_name Parameter{n}:name String Input link Parameter_{n}|NAME The short name of the parameter to display in the field on the left.

3.5 Regulator's control panel (cntrRegul)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 19, is used for adjustment of PID regulator, includes information about the parameter-regulator, fields of the regulator's settings, and the "Diagram" widget to monitor the trends of the regulator and browsing history.

Fig.19. The "Regulator's control panel" widget in the development mode.

Using — Development
This widget can be used as a panel, called from the control of panel of the parameters "ElCadr", as well as a template-page. Widget should be placed directly in the project's tree, namely to the panels' container, where the dynamic linking will be implemented to the regulator's parameter. To create the static list of the regulator's settings contours, with the possibility of paging in it, you must place them in a container of regulator's contours "greg" of each signal object and statically link them with the corresponding parameter, and to ensure equality of the panel's ID and linked parameter.

Using — Runtime
In the runtime mode the following fields are displayed:

  • name of the regulator's parameter;
  • field with the properties of regulator consisting of: identifier, name, description, units, set point, variable output, scale and mode;
  • coefficients of regulator's settings: Kp, Ki, Ti, Kd, Td, Tzd, Zi, H1, H2, K1, K2, K3, K4, Tpl, Tml и Rfkt.
  • area of the diagram with displaying trends: variable (green), set point (blue), the analog output (cyan), regulator's mode "Automatic" (magenta) and digital outputs.

Users have the ability to change the PID regulator's coefficients: mode, set point, out and immediately to see the reaction on the diagram. In addition, the user can learn the history of the regulator, which requires the left mouse button click in the graph area and by means of appeared trend's control panel to make the necessary navigation actions. To return the control panel of the parameter the left mouse button to click in an empty area of the frame is required.

Figure 20 shows an example of this element in the runtime mode.

Fig.20. The "Regulator's control panel" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
SHIFR Code String Input link Parameter|SHIFR
NAME Name String Input link Parameter|NAME
DESCR Description String Input link Parameter|DESCR
max Scale maximum Real Input link Parameter|max
min Scale minimum Real Input link Parameter|min
ed Units String Input link Parameter|ed
prec Precision Integer Input link Parameter|prec Number of decimal places in value and set point of the PID.
var Variable String Input link Parameter|var
var_addr Variable address Address Input link Parameter|var Address for the trend's building of the value.
PID - regulator
auto_addr Mode Address Input link Parameter|auto Address for the "Automate" mode trend's building.
sp Set point Real Input link Parameter|sp
sp_addr Set point address Address Input link Parameter|sp Address for the trend's building of the set point.
out Out Real Input link Parameter|out
out_addr Out address Address Input link Parameter|out Address for the trend's building of the analog output.
Hdwn Bottom output border Real Full link Parameter|Hdwn Restricting the values of the analog output on the bottom.
Hup Top output border Real Full link Parameter|Hup Restricting the values of the analog output on the top.
Kp Gain coefficient Real Full link Parameter|Kp
Ki Coeff. of integration Real Full link Parameter|Ki
Ti Integration time Real Full link Parameter|Ti
Kd Coeff. of differential Real Full link Parameter|Kd
Td Differentiation time Real Full link Parameter|Td
Tzd Differential part lag time Real Full link Parameter|Tzd
Zi Insensitivity area Real Full link Parameter|Zi
K1 Input 1 coefficient Real Full link Parameter|K1
K2 Input 2 coefficient Real Full link Parameter|K2
K3 Input 3 coefficient Real Full link Parameter|K3
K4 Input 4 coefficient Real Full link Parameter|K4
Pulse PID - regulator
impQup_addr Address of impulse output up Address Input link Parameter|impQup Address for the trend's building of the pulse output "Up".
impQdwn_addr Address of impulse output down Address Input link Parameter|impQdwn Address for the trend's building of the pulse output "Down".
KImpRfact Rate factor Real Full link Parameter|KImpRfact The asymmetry in the generation of pulse-width up and down.
TImpMin Minimal impulse time Integer Full link Parameter|TImpMin There will be generated impulses, starting with the specified width.
TImpPer Impulses period Integer Full link Parameter|TImpPer Frequency of repetition of pulse generation.

3.6 Alarms: state (alarmsSt)

1.2 GPLv2 * en, uk, ru Roman Savochenko

Constr.png Waiting to form ...


3.7 Users manager (userManager)

1.2 GPLv2 * en, uk, ru Roman Savochenko

The element-frame, shown in Figure 3.7a, serves to control users from the user interface itself. That is, typically this feature is provided to the SCADA programmer at the Security subsystem configuration, but sometimes there is a need to provide this capability from the user interface and with a few restrictions on controlled users and their groups that this frame performs and generally provides:

  • forming a list of controlled users;
  • the ability to view and change user information for: name, full name, description, password and groups;
  • adding new and deleting existing users.
Fig.3.7a. The "Users manager" widget in the development mode.

Using — development
The widget is designed to perform the role of page, and should therefore be placed directly in the project's tree. Additionally, some attribute configuration is required, below, and no links are provided.

Using — runtime
In the runtime mode, a list is formed with available users and, at their selection, on the right displayed their information that can be changed. The user can be added and removed by the appropriate interface commands under the list of users.

Figure 3.7b shows an example of this element in the runtime mode.

Fig.3.7b. The "Users manager" widget in the runtime mode.

Linking and configuring the attributes

Identifier Name Type Description
owner Owner String Owner and group of the frame that have access to it, typically "root:Security" — to allow the frame to be accessed, the user must be included in the "Security" group.
perm Access Integer numbers selection Frame access rules, typically "RWRW__" — the frame is viewable and controllable only for "root" and users in the "Security" group.
denyUsers Deny to control: users, separated by ';' String A list of do not controlled users, typically "root;".
denyGroups Deny to control: groups, separated by ';' String A list of do not controlled groups, typically "root;users;Archive;BD;DAQ;ModSched;Protocol;Security;Special;Transport;UI;".
newUseGrps Groups of new created user String Groups to which the user is automatically included, after creation, are typically "UI;Guest".
storeDB DB of saving new users String Database of storage of newly created users, by default — the work one.

4 Common panels

4.1 Element cadre (ElCadr)

Constr.png Waiting for the translation and actualizing ...

The element, shown in Fig. 3, is essentially a universal control panel of various devices:

  • analogue: indications, manual input values and regulators (analog and pulse);
  • discrete: valves, automatic shut off valves, motors, fans and switches.
Fig.3. The "Element cadr" widget in the development mode.

Using — Development
This widget is not intended for special placement and configuration of the user, as laid down in the "Signal groups" template and if the new project is created from this template, the call of the widget is done automatically, with its display in the control panel area when you select a widget of the parameter, which provides the parameter's control, for example, previously considered "anShow".

Using — Runtime
Figure 4 shows various examples of this element in the runtime mode.

Fig.4. The "Element cadr" widget in the runtime mode.

Modes:

  • Indications of the analog parameter. In this mode, there is no any control, and there are only units displaying, the value's histogram and the name of the parameter.
  • Manual input of an analog parameter. In addition to displaying indications of analog parameters the buttons to enter a new value are displayed. Enter of the value is displayed in the field at the top, in the white rectangle. To validate the input, press the left mouse button in the area of white rectangle. Without validation the typed value will be reset after a few seconds.
  • PID regulator's mode. To the value of a variable and its histogram are added values and histograms of set point and out of the PID regulator, the buttons to enter a new value of the set point or out, as well as the mode adjustment button and the field to display the current mode. Also, for the user with appropriate privileges it is available the button to go to the frame to set the coefficients of PID regulator. In the case of pulsed PID instead of histogram of the analog output it is displayed the status of pulse output with the help of triangles "Up" and "Down" and the manual entry of output leads to direct formation of pulse, respectively down or up.
  • Mode of a discrete device. In this mode the name of the parameter and the field of discrete building of the parameter are displayed. The field of discrete building contains the current state of discrete device on the left and the buttons of commands on the right. There are two states of the device: "Open", "Closed" and the three commands: "Open", "Close", "Stop". The names of states and commands can be adjusted during set up. Changing the state of the logic device is determined by pressing the corresponding command.

Every action on this panel (change of PID set point, state of the discrete parameter ...) is recorded in the actions log by the generation of appropriate messages.

For any displayed or controlled parameter the passport can be obtained in runtime mode by clicking the right mouse button on the contour field. The passport will present to all the properties of the parameter.

Linking attributes

ID Parameter Data type Config Config template Description
prmId Parameter:identifier String Input link Parameter|SHIFR Parameter's identifier is used to place the record the operator's actions to the report.
prmShifr Parameter:code String Input link Parameter|NAME Short name of the parameter, code. It is placed below the frame.
prmDescr Parameter:description String Input link Parameter|DESCR Description of the parameter is used to place the record the operator's actions to the report.
prmColor Parameter:border color String Input link Parameter|color Sets the border color of the contour.
Parameters of Analog Device
prmDemention Parameter:dimension variable String Input link Parameter|ed
prmPrec Precision Integer Input link Parameter|prec Number of decimal places in parameter, step change for the manual input of values, as well as set point and out of the PID regulator.
prmVar Parameter:variable Real Full link Parameter|var Directly to the analog value of the parameter.
max Parameter:maximum Real Input link Parameter|max Upper limit value of the parameter.
min Parameter:minimum Real Input link Parameter|min Minimum limit values of the parameter.
prmAMax Upper alarm border Real Input link Parameter|aMax
prmAMin Lower alarm border Real Input link Parameter|aMin
prmWMax Upper warning border Real Input link Parameter|wMax
prmWMin Lower warning border Real Input link Parameter|wMin
Manual Analog Input
prmVarIn Parameter:variable input Real Full link Parameter|varIn Output for manual input of an analog value of the parameter. The presence of this parameter is an indication that the parameter - is determined as "Manual analog input.
PID regulator
prmAnalog Parameter:analog regulator Boolean Input link Parameter|analog Sign of the analog regulator, in case of the absence of this parameter the regulator is an analog one.
prmAuto Parameter:automate Boolean Full link Parameter|auto Mode of the regulator, "Automatic".
prmCasc Parameter:Cascade Boolean Full link Parameter|casc Mode of the regulator, "Cascade".
prmSp Parameter:set point Real Full link Parameter|sp PID regulator's set point, it can be set by the user.
prmImpQdwnTm Parameter:imp. out down Boolean Input link Parameter|impQdwn Output "Down" for impulse regulator.
prmImpQupTm Parameter:imp. out up Boolean Input link Parameter|impQup Output "Up" for impulse regulator.
prmOut Parameter:output Real Full link Parameter|out Analog PID regulator output for display and manual input of the output value of PID in manual mode.
prmManIn Parameter:manual input Real Full link Parameter|manIn Manual input of the new output value of PID regulator in manual mode.
Parameters of discrete devices
prmCom Parameter: Command - "Open" Boolean Full link Parameter|com
prmClose Parameter: Command - "Close" Boolean Full link Parameter|close
prmStop Parameter: Command - "Stop" Boolean Full link Parameter|stop
prmOpenSt Parameter: State - "Opened" Boolean Input link Parameter|st_open
prmCloseSt Parameter: State - "Closed" Boolean Input link Parameter|st_close
digComs Parameter:digital commands String Input link Parameter|digComs Names and colors of buttons of commands in the format: {On}[-color]:{Off}[-color][:{Stop}[-color]]. Default colors are: green, red and yellow.
digStts Parameter:digital states String Input link Parameter|digStts Names and colors of labels of states in the format: {On}[-color]:{Off}[-color]. Default colors are: green and red.

4.2 Passport, extended (cntrPaspExt)

1.2 GPLv2 * en, uk, ru Roman Savochenko

Extended passport of the standard parameters with functions:

  • Table of attributes of the parameter with their edition for editable ones.
  • Trends for standard and key attributes: var, sp, out, auto, com, st_open, ...
  • Table of the current data.

Constr.png Waiting to form ...

4.3 Passport (cntrPasp)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 23, is provided for displaying the parameter's passport: detailed information, including code, description, units, alarm borders, etc. Document is generated entirely dynamically.

Using — Development
This element should be placed in a logical container of the project's tree. In development mode, the widget is a blank "Document", and therefore the only screen shot with this widget in the runtime mode of the project is provided. Linking with the parameter is made dynamically when you call "Passport" for the visual elements of the parameter.

Using — Runtime
Calling the passport is made from the visual elements of parameter, for example: by right click of the mouse on the element "analog parameter" (anShow) and on the field of the "element cadr" widget (ElCadr) . After a call the separate window of the widget-passport with a list of all properties and values of the parameter as a table is opened.

Fig.23. The "Passport" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
pName Parameter's name Address Input link Parameter|NAME Address to the parameter's name to refer to the parameter entirely and get all of its properties

4.4 Graphics group panel (grph_panel)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 26, serves to control the "Diagram" widget, it allows you to view trends' history for the required period of time and the desired resolution, the scale, the selection of archiver for display and there are supported trends' presentation in a range of present frequencies or XY.

Fig.26. The "Graphics group panel" widget in the development and runtime modes (left to right).

Using — Development
This element should be placed in the logical container of the project's tree. Linking with the parameter is dynamic when called from a diagram element.

Using — Runtime
Calling the panel is made from the diagram elements. The panel provides the following tools:

  • the diagram graphics mode selection: "Graph", "Spectrum of frequencies", "XY";
  • time selection of the diagram formation;
  • navigation through the diagram for the one or five sizes;
  • adjustment of the diagram generation time to the current time;
  • information about the time or frequency in the current cursor's position;
  • selection of the trend's formation size;
  • selection of the archive, used for the trends' presentation;
  • control the vertical and horizontal scale of the presentation: zoom in and out the scale, shift the scale up and down, the scale returns to its original value;
  • switching of the scale mode by the window drawn by the mouse.

Linking attributes

ID Parameter Data type Config Config template Description
tSek Trend time DateTime Full link <page>|tSek
tSize Trend size Real Full link <page>|tSize Temporal size of the trend in the history from the time of the trend.
trcPer Trace period Integer Full link <page>|trcPer Renewal period of the trend.
type Type Integer Full link <page>|type Trend's type: "Graph", "Spectrum of frequencies", "XY".
valArch Archiver String Full link <page>|valArch
curSek Cursor DateTime Full link <page>|curSek Time of the cursor.
curUSek Cursor, usec Integer Full link <page>|curUSek Time of cursor, microseconds.
sclVer Vertical scale Real Full link <page>|sclVerScl The percentage of vertical scale.
sclVerOff Vertical scale offset Real Full link <page>|sclVerSclOff Percentage of the offset on the vertical scale.
sclHor Horizontal scale Real Full link <page>|sclHorScl The percentage of horizontal scale.
sclHorOff Horizontal scale offset Real Full link <page>|sclHorSclOff Percentage of the offset on the horizontal scale.
sclWin Scale by window Boolean Full link <page>|sclWin Switching to the scaling by window mode.
sclWinCtx Scale: by window save context Object Input link <page>|sclWinCtx The context of saving of the original scale parameters for return.

4.5 Document panel (doc_panel)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 24, is used to manage documents and navigate through their histories. The element supports dynamic and archival documents.

Fig.24. The "Document panel" widget in the development mode.

Using — Development
This element should be placed in a logical panels' container of the project's tree. Linking with the parameter is dynamic when called from the document's element.

Using — Runtime
Call of the panel is made from elements of the document. The panel provides tools that are somewhat different for dynamic and archival documents.

For dynamic document the following tools are provided:

  • selection the time of the document's formation;
  • selection the size of the document's formation;
  • navigation through the document for one or five sizes of it;
  • adjustment the time of generation of the document at the current time.

Archival document provides only navigation through documents in the archive by listing them, and display current and overall documents.

Figure 25 shows examples of this element in the runtime mode: dynamic (left) and archival (right).

Fig.25. The "Document panel" widget in the runtime mode.

Linking attributes

ID Parameter Data type Config Config template Description
Dynamic document
time Document time DateTime Full link <page>|time
bTime Document begin DateTime Full link <page>|bTime
doc Document String Full link <page>|doc
Archive document
n Archive size Integer Full link <page>|n
vCur View cursor Integer Full link <page>|vCur
aCur Archive cursor Integer Input link <page>|aCur
aSize Archive size Integer Input link <page>|aSize

4.6 Acception (accept)

Constr.png Waiting for the translation and actualizing ...

The "Acception" element, presented in Figure 32 implements a simple operations' acception dialog. The element contains a message with a question and two buttons "Apply" and "Cancel". The dialogue, for example, is used in the frame Prescription: editing to accept the deleting operation.

Fig.32. The "Accept" frame in the development and runtime mode.

Using — development
This widget can be used by the developer to create dynamic interaction frames in operations that require acception by the user. To use it you should add this item to the panels' logical container of the project's tree. For interaction this widget is opened by the frame-initiator the result of it is dynamic linkage of the dialogue with the "event" and "mess" attributes of the frame-initiator. The question message is taken from the "mess" attribute, and the "dlg_Apply" signal is transmitted to the "event" at acception.

Using — Runtime
Calling the dialogue is made from the frame-initiator, and closing is made by pressing any button of the dialog. If you click the "Apply" button the "dlg_Apply" signal will be sent to the frame-initiator, by which it can perform the desired actions.

Linking parameters

ID Parameter Data type Config Config template Description
elEvent Element:event String Full link <page>|event It is used to send the "dlg_Apply" event if accepted.
elMess Element:message String Input link <page>|mess Source of the question message in the dialogue.


4.7 Select item into tree (treeSelect)

1.0 GPLv2 * en, uk, ru Roman Savochenko

Constr.png Waiting to form ...

4.8 Terminator panel (terminator)

Constr.png Waiting for the translation and actualizing ...

Element, shown in Figure 27, serves to fill the empty place when no item is selected for control.

Fig.27. The "Terminator panel" widget.

Using — Development
This element should be placed in the logical container of the project's tree.

Using — Runtime
Calling the panel is made from root page "RootPgSo" by changing the signal object or presentation mode.