Projects news:
The main library of the DAQ-source templates appended for a template of the notification by SMS, EMail(SMTP)
The complex template of the notification contains of parts of the dispatcher and the output user protocol of notification by EMail(SMTP) and SMS.
THE DISPATCHER can be performed for pointed messages of the message buffer of OpenSCADA and applied on the Logical level or the controller object of the module JavaLikeCalc.
THE OUTPUT USER PROTOCOL PART "SMS" provides operations with SMS by a GSM-modem connected as serial device. For now, there supported only sending SMS messages to a number of remote cell phone or GSM-modem. For sending there are supported: ECHO disable, PIN check and set, sending in PDU and the Text mode.
THE OUTPUT USER PROTOCOL PART "SMTP" provides operations with a SMTP-server for delivering EMails by their sending through TCP-Socket or SSL. For now, there are supported: TCP, SSL, AUTH, topic encoding for UTF-8.
Sponsored by: SVItoVYR LTD
The complex objects conception in the DAQ is formed and documented
In some cases where an object is only a part of a common automated system and does not require deep detailing to the level of signals and parameters (complex tag) around them, including without the need for archiving, it is convenient to unify them in one representative object of the data source OpenSCADA with appropriate consolidated view and object control as a set of simple attributes with violation elements.
The conception is represented currently by the two direct DAQ-templates "SNMP", "UPS" and the representative widget "Object properties" of the "Main elements library of the user interface".
The main elements library of the user interface appended for the extended alarms control frames
The alarm frames serves:
- Alarms — active (alarmsAct) — to dynamically display the active violations in a tabular form and to highlight them in color and text
- Alarms — state (alarmsSt) — to display the violations history and to update their dynamically for the current time in a full-format tabular form, to highlight them in color and text and the possibility of multilevel filtering
- Alarms — report (alarmsStReport) — to display a report document based on a list of violations received from the previous full-format frame of presenting the violations history.
The violations are obtained from the buffer of current-active violations of OpenSCADA and archive(s). In fact, the element implements the primitive "Protocol" functions for violations and extension opportunities.
The main user extension is the ability to define visible table fields from a list of options: atm, qttm, nrmtm, lev, cat, mess, prm, dscr, dscrCust{N}, alrm, cmnt.
Sponsored...
The main elements library of the user interface appended for the "Users manager" frame
The element-frame 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.
The root page frame of the main elements library of the user interface is significantly expanded and documented
The frame "Root page" is a base element of most interfaces built in OpenSCADA and it was completely documented and significantly expanded for:
- dynamization of forming the signal object buttons from one base button, with the result possibility of forming very number of signal objects, up to 100 for short names.
- dynamization and unification of the types of view to their abstract encoding as "viewN", with the result possibility to appoint any other mean to the type of view.
- correct cleaning the control panels container.
Analysis of the memory consumption and efficiency of the UI module WebVision in the busy environments
The module UI.WebVision was observed in extra memory consumption on a real big task working on Debian 9.
There were performed several actions of measuring about this module work on different Debian versions: 7, 8, 9, 10; where we have seen the clear degradation of effectivity of the memory allocation on Debian versions from 8.
Contacting the Debian community we revealed this problem as a disadvantage of GLibC in implementing memory arenas, which can be highly fragmentated in program environments what actively recreating the threads, due to linking the arenas to threads.
So, to fix this behaviour, we need to set the environment variable MALLOC_ARENA_MAX=1, what was be done for all live disks of the automation Linux distributive.
The graphics group frames of the main elements library of the user interface appended for the graphic parameter calculation
The element 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.
API of the unified implementation of the DAQ-templates
API of the unified implementation of the DAQ-templates has been implemented, applied and substantially tested.
Currently, this API is applied on the primary modules of the subsystem "Data acquisition", that is LogicLev, ModBus, Siemens, and as an optional feature for the controller object of the JavaLikeCalc module. From modules of other subsystems to the templates support, the protocol modules UserProtocol, ModBus and the graphical interface module WebUser have been adapted. Moreover, the use of templates in the modules UserProtocol and WebUser conceptually improved their functions and expanded the ability to create complex templates.[more]
Completed full revision of the most significant and largest document "Program manual"
The document "Program manual" is the most significant and largest document of OpenSCADA and it was completed for its full revision on the new Knowledge Base (Wiki) of OpenSCADA. At the way the document was translated to Ukrainian and appended by the part "Startup and execution".
That is the releasing of the OpenSCADA version 0.9 LTS is also official started, the schedule-task of the process was prepared and it completion planned to 01.05.2018.
OpenSCADA projects integration to the OpenSCADA core and UI.QTStarter
To unify and expand the functionality, and "openscada_start" script exploitation experience, the essence of the project was integrated into the OpenSCADA core and the module UI.QTStarter of the local graphical interfaces execution. Therefore, the OpenSCADA core, namely the primary "openscada" binary file, involves determining the configuration file, the data folder and the name by the specified project name and switching to that configuration. Creating the interface elements for selecting and creating new projects implements the UI.QTStarter local graphical interface module. Administrative functions of the project manager are moved to a separate command line script "openscada-proj" because of the specificity of these operations to the software platform, and therefore the need for a simple adaptation to this specificity.
The UI.QTStarter module also was significantly refactored and expanded for starting and collapsing to the system tray and for the custom control of the Look and Feels of the Qt interfaces.