Introduction

This release is a planned one of a working version of OpenSCADA, which are usually made at intervals of 3-4 months. The main purpose of this release is the stabilization and testing of key functions before releasing the next long term support (LTS) version of OpenSCADA 0.8.0. In addition to the main purposes within the limits of this release a great work for stabilization, cleaning the source code, full empowerment and testing on the embedded and mobile ARM devices is made.

This document is the processing (compilation) of <ChangeLog> document of the OpenSCADA system of 0.7.2 version, which is designed for briefly and clearly covering the new features and changes of the OpenSCADA system. To get acquainted with all the changes in the OpenSCADA system it is possible in the file ChangeLog from the distribution kit of the system, or here: http://oscada.org/websvn/filedetails.php?repname=OpenSCADA&path=%2Ftrunk%2FOpenSCADA%2FChangeLog .

The key features of this version are:

• Implementation of planned tasks.
• Optimization, increasing of stability, sustainability and system performance.
• Improvement and stabilization of the graphics subsystem.
• Expansion of user programming API.
• System-wide expansions.
• Publication of OpenSCADA solutions.

New and updated modules:

• Archive.DBArch (0.9.5) — The limits for requesting data on the request time are added as well as some more extensions.
• Archive.FSArch (1.5.0) — The files' indexes of the values' archives read performance is increased. The adaptation of storing and reading the floating to the ARM FPA is made. The limits for requesting data on the request time are added. Some extensions. A significant stabilization.
• DB.FireBird (0.9.7) — Stabilization.
• DB.MySQL (1.7.1) — Stabilization.
• DB.PostgreSQL (0.9.2) — Stabilization.
• DB.SQLite (1.6.4) — Stabilization.
• DAQ.BFN (0.5.1) — Stabilization.
• DAQ.BlockCalc (1.5.0) — The CRON scheduling of calls is added. The start and stop blocks' call is added. Stabilization.
• DAQ.DAQGate (0.9.5) — The CRON scheduling of calls is added. Stabilization.
• DAQ.DCON (0.5.1) — Stabilization.
• DAQ.DiamondBoards (1.2.5) — The ability to change the parameter's type is added. Stabilization.
• DAQ.ICP_DAS (0.8.0) — The "ICP DAS" API library libi8k.a for the ARM architecture is added, the ability to build the module for ARM is added. Stabilization.
• DAQ.JavaLikeCalc (1.9.5) — The direct, dynamic call of library functions is added. The direct association of string constants is added. The conditional call of the expression's arguments ( the second argument) with the logical operators ||(OR) and &&(AND) is added. The significant stabilization. Some extensions.
• DAQ.LogicLev (1.2.0) — Stabilization. The ability to change the parameter's type is added. The CRON scheduling of calls is added. Some extensions.
• DAQ.ModBus (1.2.0) — The support for "Logical" parameter's type is added for the working with template of the parameter, and also the functions of the user's API to send arbitrary, non-standard ModBus requests from the templates are added. The function is added and used the formation of alleged violations of the controller. The support of the function for group record (0x0F, 0x10) is added. The significant stabilization.
• DAQ.OPC_UA (0.6.2) — Stabilization. The adaptation of storing and reading the floating to the ARM FPA.
• DAQ.SNMP (0.6.1) — Stabilization. Some improvements.
• DAQ.Siemens (1.3.0) — Significant stabilization. Library LibnoDave is updated to the 0.8.4.6 version. The CRON scheduling of calls is added. The reconnection function for the "Industrial Ethernet" connections is added. Some extensions.
• DAQ.System (1.7.5) — Stabilization. The CRON scheduling of calls is added.
• Transport.SSL (1.0.0) — Stabilization. Some improvements.
• Transport.Serial (0.7.3) — Stabilization.
• Transport.Sockets (1.5.0) — Significant stabilization.
• Protocol.HTTP (1.6.0) — The support of user's templates for internal contents of the module is added. The generation of the user's authentication messages is added. The support of all major versions of the completion the string during HTTP-request parsing is added.
• Protocol.ModBus (0.6.3) — Stabilization. Some improvements.
• Protocol.OPC_UA (0.6.2) — Stabilization.
• Protocol.SelfSystem (0.9.5) — Stabilization.
• Protocol.UserProtocol (0.6.2) — Stabilization.
• Special.FLibComplex1 (1.1.0) — The direct, dynamic call of library functions is added.
• Special.FLibMath (0.6.0) — The direct, dynamic call of library functions is added.
• Special.FLibSYS (1.0.0) — The direct, dynamic call of library functions is added.
• UI.QTCfg (2.1.0) — Stabilization. Significant extensions and improvements. The implementation of a number of features to enhance comfort.
• UI.QTStarter (1.6.2) — Stabilization. The font of message in splash is fixed at 10 pixels to ensure the uniform representation.
• UI.VCAEngine (1.2.0) — Stabilization. Significant extensions and improvements.
• UI.Vision (1.2.0) — Significant stabilization. Significant extensions and improvements.
• UI.WebCfg (1.5.6) — Stabilization.
• UI.WebCfgD (0.8.0) — Stabilization. Significant extensions and improvements.
• UI.WebUser (0.6.2) — Stabilization.
• UI.WebVision (1.0.0) — Significant stabilization. Significant extensions and improvements.

1 Implementation of planned tasks

In accordance with the plane of the release there were made the following tasks:

• The implementation of the undo/redo editing changes mechanism in the Vision. — As part of the widget's visual editing window the multi-level changes' undo/redo mechanism is implemented for all basic operations: a visual changes in the geometry, changing the value of the widget's attribute, add/remove the widget, copy the widget and editing the widgets, based on the primitive "ElFigure".
• Adaptation of OpenSCADA to work on the ARM hardware platform. — In addition to the primary adaptation, in the last release for the N800 tablet (http://wiki.oscada.org/Works/Tests/ARM ) the build and adaption of OpenSCADA for the complex (very old) program environment of the LP-5451 controller was made, and also the builds for the SMH2Gi controller and for the Nokia smartphones: N900, N950, N9 were made. As part of the build and adaptation to different mobile devices the following tasks were implemented:
  • DAQ.ICP_DAS: The "ICP DAS" API library libi8k.a for the ARM architecture is added, the ability to build the module for ARM is added.
  • SYS, DAQ.OPC_UA: The system functions floatLE(), floatLErev(), doubleLE(), doubleLErev() are added to convert the storage format of a real number on different architectures.
  • SYS: The adaptation is made to build with the GLibC version less than 2.5 (2.3.2).
  • Archive.FSArch:
    • The LE format real number storage in the archive on the ARM architecture is fixed.
    • The algorithm of the quickly count the number of bits uses the function of not aligned reading TSYS::getUnalign32().
    • The encoding field size in the plane archive of messages expanded from 9 to 99 characters.

2 Optimization, stability, sustainability and system performance increasing

During the work on this version, as well as during its practical adaptation, it was discovered and corrected in a total of about 170 error. Also the work on cleaning code from the compiler's warnings with the "-Wall" flag was continued.

Lets list the most significant errors correction of which significantly affected the increasing of stability:

• SYS:
  • The unscheduled calls on the schedule, related to desync of the functions values time() and clock_gettime(CLOCK_REALTIME,&sp_tm), are fixed.
  • The checking and waiting for threads to access due to the overlapping with the previous, eponymous one's stop.
  • The waiting for initialization of the disconnectable tasks is disabled in order to prevent freezing in anticipation of rapidly closing tasks.
  • The work of not aligned reading functions getUnalign*() is fixed on the ARM. The Problem is detected on PXA270.
• Archive.FSArch:
  • The reading data from the archive's buffer in accordance with the buffer's size in the algorithm of fast calculation of the bits' number is fixed.
  • The placement of the offset in the cache from the algorithm of fast calculation of the bits' number is fixed.
  • The incorrect handling of the end of not aligned blocks of the fast algorithm for calculation of the bits' number is fixed.
  • The exclusive resource to the calcVlOff() function's call is added in order to prevent the incorrect operation with cache.
• Transport, DAQ.AMRDevs, DAQ.DCON, DAQ.ICP_DAS, DAQ.ModBus, DAQ.OPC_UA, Protocol.HTTP: The usage of the TTransportOut::messIO() function at the request of the tail and getting the zero response is fixed.
• DAQ.ModBus, Transport.Serial, UI.WebCfg, UI.WebCfgD, UI.WebUser, UI.WebVision: The incorrect using of the string terminator '\n' for a variety of software platforms UNIX, MAC, DOS/Windows is fixed by replacing it with "\x0A".
• Transport.*: The using of unsigned type in the return of the read() and write() functions is fixed. The resources for the counters of the i/o requests are added.
• Transport.Sockets: The missing of the initialization of the size of the return value of the getsockopt() function is fixed.
• DAQ.JavaLikeCalc: The crash of the replace() function of the "RegExp" object is fixed.
• DAQ.Siemens: The receiving and recording the values of real types is fixed. The reconnect in the case of error is fixed. The using of the size property of the integer, real and string is fixed. The cleaning of the parameter's links at its disabling is added.
• UI.Vision, UI.WebVision: The access abroad the vector's size during the rendering of the primitives "FormEls" graphics is fixed.
• UI.VCAEngine: The possibility of changes' loss in the visualization server is precluded when displayed in the visualizers by preliminary saving the value of clock counter in the "openList" service request.
• UI.WebVision:
  • The opening and replacing the root page is fixed.
  • The handling of nested pages' scale is fixed, taking into account the scale of the root one.

Optimization and performance improvement:

• SYS: The mechanism of the "ResString" object resource is replaced from the RW-locks with mutex in order to improve performance and reduce memory consumption.
• Archive.FSArch: The processing of the values' archive index table is significantly accelerated through the use of fast algorithm for computing the number of bits in a 32-bit integer.
• UI.WebCfgD: The group request of the page's contents is used to greatly improve the performance on slow and high latency channels.
• UI.Vision: The rendering performance of the fills of the "ElFigure" primitive is improved.
• UI.VCAEngine:
  • The measures to increase the speed of project's session initiation are implemented: the initialization of the basic attributes because of their subsequent inheritance is skipped.
  • The translation of certain messages of the runtime session is removed.
  • The enabling of only the necessary pages at startup of the session is implemented. Other pages of the running session are enabled when accessed. This has greatly increase the speed of session's startup, as well as reduce the dependence of the starting speed on the complexity of the visualization project.
  • Implementation of the archive mode of the "Document" primitive is changed to direct work with the database, which let to expand the depth of the archive up to the 1000000 documents, and without prejudice to the RAM.

3 Improvement and stabilization of the graphics subsystem

The notable work was made within the graphics system, namely in the VCA engine modules UI.VCAEngine, visualizers UI.Vision and UI.WebVision, as well as in the configurators. The changes were provided for stabilization, the optimization of memory consumption and improvement of user's properties.

Improvements of the graphics subsystem:

• UI.VCAEngine, UI.Vision, UI.WebVision:
  • The handling abroad the array (vector) in the construction of trends of the "Diagram" primitive is fixed.
  • The width property of trend of the "Diagram" primitive is added and implemented.
  • The periodic inspection of the widgets' tree of the page is added in order to detect the fact of widgets' removing by requesting the complete list of widgets.
  • The display of trends, graphics group of the "Diagram" primitive in the scale of values is implemented in the case of differences between the scales of all graphs not more than 20%.
  • The ability to select the confirmation mode for the items of the line and text editing of the primitive "FormEl".
  • The possibility of loosing of some changes in the model, when displayed in the visualizers is fixed.
  • The property of the values' count of the one pixel in the trends of the "Diagram" primitive is added and implemented in order to control granularity of export to CSV etc.
  • The logarithmic scale of values for the trends of "Diagram" is implemented.
  • The storage of aspect ratio property of the main page during the maximization of the main window of the project's session execution is added and implemented.
• UI.VCAEngine:
  • The enabling of project's session pages when it is really necessary is implemented in order to speed up the startup and optimize memory usage.
  • The "Document" primitive is remade for keeping the archives fully in the database, as well as the function of user API to access the elements of the archive is added.
  • The periodic (30 minutes) check and the closing of the unused (orphaned) projects' sessions are added.
  • The previous one (controversial) rollback mechanism of nested widgets deleting is removed and it is replaced by the full-fledged rollback mechanism in the UI.Vision visualizer.
  • Optimization of memory usage by the session's elements up to 20% is implemented.
  • The support of the first, out of date, version of the database structure of the visual area is removed.
  • The restriction on the time of the document's generation in the "Document" primitive in 5 seconds is added.
  • The support of the attribute's type "Object" and "Text" is added.
  • The forced initialization of new user's attributes in EVAL is disabled.
  • The "Document" primitive is switched to XML parsing in order to fully preserve the XHTML markup.
  • The display of the correct status of the links in the form of "(+)" at the end of the line is added.
• UI.Vision:
  • The implementation of the full-fledged undo and redo the changes in visual editing widgets is added.
  • Improvements in the sensitivity and updating the changes in the project's session: the rendering performance of the "ElFigure" primitives is optimized, handling of the changes in the "geomZ" level of the widget is added.
  • The export to CSV format from the "Diagram" and "Document" primitives is added.
  • The limit on the size of the input dialogs is added and an adaptive determination of their sizes by their contents is added.
  • The rules' execution mechanism for syntax highlighting is completely rewritten.
  • The new session creation after the restoration of remote connection and absence of the previous session is added.
  • Window background for the editable widget is set to QT::Dense7Pattern template to eliminate the possible of overlapping by color.
  • The event handling of the widget's selecting when press in the scroll area, but outside of the widget is added.
  • "Elementary figure" primitive:
    • The reorganization of the operations of the Properties dialog and context menu with dynamic and static properties is completed.
    • In the process of addition the figure its rendering when moving the mouse cursor is implemented.
• UI.WebVision:
  • The handling of nested frames scale is fixed, as well as the mechanism of formation-enabling of scroll is revised.
  • The function of the images conversion on the server's side is added. Conversion function is used for resizing and discoloration the images of inactive buttons.
  • The opening of small windows of the nested pages as the DIV-blocks is implemented, it solves the problem of lock and the long opening of the external windows in many browsers.
  • The main page of the interface is centered in the browser's window.
• UI.QTCfg:
  • The restriction on the height of the rows of tables at half the height of the table is added.
  • The limit on the size of the input dialogue is added, and the adaptive determination of its size on its contents is added.
  • For the elements available to adjust their height by the user, for the work elsewhere, the fixed style "StyledPanel" is set.
  • The function of full text editing of table's cells is added.
  • Playback engine of the syntax highlight rules is completely rewritten to simplify it and to avoid hidden errors.
• UI.WebCfgD:
  • The brightness of decolorized-passive buttons is reduced.
  • All dialogs windows are implemented as DIV-blocks in order to avoid problems and delays in opening external windows in different browsers.
  • The group request the page's contents is used for the significant improvement of the performance on slow and high latency channels.
  • The information in the status bar about the current user and the possibility of its change are added.
  • The adaptation to work in full screen width is made.

4 Extension of the user programming API

It was continued the development of object API of the user programming, which provides the integration of user's functions into the object's tree of OpenSCADA. In addition, a number of changes was made to the existing library of the user's API functions.

In particular the following changes were made:

• SYS:
  • The functions to work with files are added: SYS.fileRead() and SYS.fileWrite().
  • The getElementBy() function is added to the XMLNodeObj object's API to search for embedded nodes by attribute's value.
  • The function of encoding the text between different character encodings is added.
  • The NodeObj.nodePath() function is added.
• TConfig, TBD, TTransportIn, TTransportOut, TUser, TGroup, TPrmTmplLib, TPrmTempl, TParamContr, TController, TVArchive, TVArchivator, TMArchivator: The following functions of the user API are added: cfg() and cfgSet() to access the configuration of the objects (stored in the database).
• DAQ:
  • The TController::alarmSet() function is added to generate the typical alarms in the controller's object of the "Data acquisition" subsystem's modules.
  • The SYS.DAQ["Modul"]["Controller"]["Parameter"]["Attribute"].arch() function is added to directly access the object's archive associated with the attribute of the parameter.
  • The following functions of the user API are added: enable() and start() for the direct monitoring of the controller's object.
• DAQ.JavaLikeCalc, Special.FLibComplex1, Special.FLibMath, Special.FLibSYS: The function for the dynamic call of the library functions is added: SYS.DAQ.JavaLikeCalc["lib_{Lib}"].funcId(prms, ...).
• Archive: The following functions of the user API are added: status(), end() and begin() for access to the state and properties of an object of the messages' archiver.
• DAQ.JavaLikeCalc:
  • The isEVal() function for the "null" data type is added, which always returns "true".
  • The call() function of the user API is added to the objects of the library functions.
• DAQ.ModBus: The messIO() function of the user API is added in the "ModBus" controller's object in order to provide an opportunity to send custom ModBus-queries directly from the template of the parameter.

5 System-wide expansions

To the system-wide API of the OpenSCADA system there have been made the significant changes and extensions with the purpose of the general stabilization and expansion:

• SYS:
  • The storage object of the string with the "ResString" resource is significantly expanded for the clear conversion from/to std::string type.
  • The ability to save to the configuration file is added:
    • The database prefix "<cfg>" is added for presentation of the configuration file as a source of load/store configuration.
    • The TDBS::dataSeek() and TDBS::dataDel() functions are updated for the strict processing the configuration file.
    • The chkSelDB() function is adapted to support the record to the configuration file.
    • The storage of large and multi-line field values in the text box of the individual tag of the configuration file is added.
  • The "long long" type, usually a 64-bit integer is replaced everywhere by the "int64_t" on all architectures.
  • The objects of the OpenSCADA treads are rigidly linked with their thread. The load and periodic threads' calls statistics is added.
  • The possibility of checking the loaded objects for their absence in the database and deleting is added. Check function is activated only in the case of direct loading from the database.
  • The perSYSCall() system periodic function for the call of subsystems' and their modules' objects is added. It is used for service purposes of unloaded and rare task of the modules and subsystems.
  • The test function of the expression by the template is moved to the TRegExp object.
  • SYS.XMLNode:
    • The code of "Expat" XML-parser using is completely removed.
    • The ability to load text parts of the tag to the separate specific tags in full mode is added. It is designed for full storage the configuration of the tag.
    • The ability to load and store the comments blocks into the separate specific tags in full mode is added.
• DOC:
  • Check and repair the English texts in the OpenSCADA core is made. The translations for the OpenSCADA core to German, Russian and Ukrainian languages are updated.
  • Check and repair the English texts in the OpenSCADA modules is made. The translations for the OpenSCADA modules to German, Russian and Ukrainian languages are updated.
  • The all key documents in accessible languages are updated: openscada.pdf, build.pdf, properties.pdf, "OpenSCADA API", "About OpenSCADA", "TechApp Library", "Quick Start", "WLib Main", "WLib Mnemo Elements".
• Libraries databases:
  • The library of the main visual elements is appended by the frames of the implementation of editing and execution of "Prescriptions" - "User's programs".
  • The library of the electrical elements is added to the kit of libraries package.
  • The frame of the main page is appended by the mechanism of "playing" the models of technological processes (TP).
  • The industrial boiler unit(RUS) model is translated to English and Ukrainian languages.
• DB: The time limit of 5 seconds and the field of specifying the starting offset are added for the request of the large tables' contents.
• DAQ: The ability to select the type of the "object" template's attribute is added. It is made primarily to store internal data in the object and can not be used as the type of parameter's attribute of data source controller's object.
• TArchives: The ability to use regular expressions when searching by category using "/match/" is added.
• Transport: Types of formats for outgoing requests are expanded with versions of the text with a different end of line: LF, CR, CR/LF.
• DAQ, DAQ.DiamondBoards, DAQ.ModBus, DAQ.LogicLev: The ability to change the type of the parameter for the disabled parameters of multi-type modules of "Data acquisition" subsystem is added.
• DAQ.LogicLev, DAQ.Siemens, DAQ.ModBus: In the case of the scheduled execution the time after the last calculation in the negative value is written to the "f_frq" attribute. The initialization and stop calls are added during enabling/disabling of the parameter.
• TArchives, Archive.DBArch, Archive.FSArch: The time border when requesting messages from the archive is added.
• SYS.TConfig, Archives, DAQ, Security, Transports, Archive.*, DAQ.*, Protocol.UserProtocol, Transport.*, UI.VCAEngine, UI.WebUser: Keeping the string configuration fields is moved to the "ResString" object of the resource string.

6 Publication of OpenSCADA solutions

During the work on this version the solutions, based on the OpenSCADA, have been presented at various conferences and exhibitions:

• FOSS Sea 2011 — the report about the solutions, based on the OpenSCADA was read at the conference and in the hall there was made the mini-stand with the live solutions, based on OpenSCADA.
• International Innovation Forum 2011 — at the stand of "DІYA" Ltd and Dneprodzerzhinsk State University (DSTU) the equipment and materials on the solution, based on OpenSCADA were presented.
• 10 Ukrainian Conference for Free Software Developers and Users — the report about the solutions, based on the OpenSCADA was read at the conference and in the hall there was made the mini-stand with the live solutions, based on OpenSCADA.
• Qt Developer Days 2011 in Munich and San Francisco: there were made the demonstration of OpenSCADA solutions Dynamic model of the DMKD multifuel steam boiler unit №9 on the PC and The dynamic model of real-time of the Anastasievskaja GLKS on Nokia N9 in the Qt Demo Pavilion.

Conclusion

This release of OpenSCADA actually finishes the work on adaptation to the ARM hardware architecture, which will be verified in the provision and publication of the official release 0.7.2 builds for mobile devices.

Although this release was delayed and a few late but it still was carefully prepared and will be a good basis for finishing the project's code base for the upcoming responsible release 0.8.0 LTS. In addition, this release can be used for widespread implementation in critical applications, followed by a smooth transition to 0.8.0 LTS after its release.

Subsequent development efforts will be directed to the completion of planned tasks and preparation for release the OpenSCADA long term support (LTS) version 0.8.0.

Changes

• 24.10.2010 - Production release 0.7.0.
• 19.12.2010 - The first planed update of production release. Fixed about 30 bugs.
• 01.03.2011 - The second planed update of production release. Fixed more 30 bugs.
• 09.05.2011 - The third planed update of production release. Fixed more 30 bugs.
• 09.07.2011 - The fourth planed update of production release. Fixed more 15 bugs and append some improve.
• 12.10.2011 - The fifth planed update of production release. Fixed more 50 bugs and append some improve.

Introduction

The release of an open SCADA (Supervisory control and data acquisition) system of version 0.7.0 is the first stable, industrial release, which is associated with the completion of beta testing that began from version 0.6.4.

The main purpose of this release is providing the community of users and developers of free software with the platform for the solutions of complex automation systems and related solutions, as well as providing commercial services on the basis of the OpenSCADA project.

This release is the first stable release, for which technical support is available from the developers and for which it is planned to release fixes during a long time.

This document is the processing (compilation) of <ChangeLog> document of the OpenSCADA system version 0.6.4, which is designed to cover brief and clear the new features of the OpenSCADA system. To get acquainted with all the changes in the OpenSCADA system it is possible in the file ChangeLog from the distribution kit of the system, or here (RU): http://wiki.oscada.org/Works/ChangeLog.

The key features of this version are:

• Implementation of planned tasks.
• Optimization, increasing of stability, sustainability and system performance.
• Improvement and stabilization of the VCA.
• Formation and stabilization of the user programming API.
• System-wide expansions.
• Significant improvements and fixes of individual modules.
• Formation of the documentation and translations of documentation and interface.
• Unification of the demo database.

New and updated modules:

• Archive.FSArch - 1.3.1 -> 1.4.1, fixes and enhancements to improve performance;
• Archive.DBArch - 0.9.0 -> 0.9.2, fixes and some improvements;
• DB.DBF - 2.0.1 -> 2.0.2, fixes;
• DB.MySQL - 1.6.1 -> 1.6.2, some improvements;
• DB.SQLite - 1.6.1 -> 1.6.2, improvements;
• DB.FireBird - 0.9.1 -> 0.9.5, significant improvements;
• DB.PostgreSQL - 0.9.0, new module;
• DAQ.DiamondBoards - 1.2.0 -> 1.2.1, API change adaptation;
• DAQ.System - 1.7.0 -> 1.7.2, code cleanup and API change adaptation;
• DAQ.BlockCalc - 1.2.1 -> 1.4.0, improvements and fixes;
• DAQ.JavaLikeCalc - 1.5.0 -> 1.8.0, significant improvements, bug fixes and optimization;
• DAQ.LogicLev - 1.0.1 -> 1.1.2, improvements and fixes;
• DAQ.SNMP - 0.4.0 -> 0.4.1, API change adaptation;
• DAQ.Siemens - 1.2.1 -> 1.2.3, fixes and API change adaptation;
• DAQ.ModBus - 1.0.1 -> 1.1.1, improvements and fixes;
• DAQ.DCON - 0.3.0 -> 0.3.3, improvements and fixes;
• DAQ.ICP_DAS - 0.5.0 -> 0.7.2, significant improvements and fixes;
• DAQ.DAQGate - 0.8.0 -> 0.9.1, significant improvements and fixes;
• DAQ.SoundCard - 0.6.0 -> 0.6.1, API change adaptation;
• DAQ.OPC_UA - 0.6.0, mew module;
• Transport.Sockets - 1.4.0 -> 1.4.5, improvements and fixes;
• Transport.SSL - 0.8.2 -> 0.9.5, improvements and fixes;
• Transport.Serial - 0.5.0 -> 0.7.1, significant improvements and fixes;
• Protocol.HTTP - 1.4.1 -> 1.5.0, significant improvements;
• Protocol.SelfSystem - 0.9.1 -> 0.9.3, fixes and API change adaptation;
• Protocol.UserProtocol - 0.6.0, new module;
• Protocol.ModBus - 0.5.0 -> 0.6.1, improvements and fixes;
• Protocol.OPC_UA - 0.6.0, new module;
• Special.FLibComplex1 - 1.0.4 -> 1.0.6, improvements and fixes;
• Special.FLibMath - 0.5.1 -> 0.5.2, API change adaptation;
• Special.FLibSYS - 0.9.0 -> 0.9.2, improvements and fixes;
• Special.SystemTests - 1.3.7 -> 1.5.0, remaking and the unification of the tests;
• UI.QTStarter - 1.5.3 -> 1.6.0, improvements;
• UI.QTCfg - 1.8.1 -> 1.9.0, significant improvements and fixes;
• UI.WebCfg - 1.5.3 -> 1.5.4, fixes and API change adaptation;
• UI.WebCfgD - 0.6.2 -> 0.6.5, fixes;
• UI.VCAEngine - 0.9.0 -> 1.0.0, significant improvements, bug fixes and optimization;
• UI.Vision - 0.9.0 -> 1.0.0, significant improvements, bug fixes and optimization;
• UI.WebVision - 0.7.0 -> 0.9.0, significant improvements and fixes;
• UI.WebUser - 0.6.0, new module;

1 Implementation of planned tasks

In accordance with the plan of release the following tasks were implemented:

• Implementation of the primitives "Link" and "Function" of the VCA. - In a view of the unprincipled to the industrial release and unclaimed at the moment, this task has been moved beyond the first industrial release.
• The stabilization and release of industrial branch of OpenSCADA. - The big work on stabilization and optimization of the industrial release was done, as detailed in the next section.
• Implementation of the database ODBC module, PostgresSQL and transport module of the DB. - Maxim Lysenko has done the implementation of the "PostgreSQL" DB module. Implementation of the database module "ODBC" was considered inappropriate, because the "ODBC" technology is actually the interface of SQL-queries that do not address specific SQL-dialects of the real database, and therefore can not be right, without regard to the type of database, used in solving OpenSCADA basic tasks. The prospect of using "ODBC" is to implement access to the database that have no "native" API of direct access to the database, but there is the ODBC driver, or to provide a simple interface of SQL-queries in OpenSCADA. The implementation of the transport module of DB was moved beyond the first industrial release.
• Implementation of the new mechanism/module of OpenSCADA system's test. - To perform the intra-system tests of OpenSCADA the mechanism of testing module was implemented as the user's API functions, which on the one hand retains the possibility of an autonomous call of static tests and on the other it provides an opportunity to call tests one by one, manually, as well as from user's scripts in any order and with the necessary number of individual tasks.

2 Optimization, increasing of stability, sustainability and system's performance.

During the work on this version, as well as its practical adaptation, it was found and corrected in a total of about 200 errors.

In addition to correcting of big number of errors it had been done the work on optimization of the various OpenSCADA's components. Especially, notable optimization was made in the Visual Control Area (VCA) and its visualizers.

Lets list the most significant errors, correction of which significantly affected the increasing of stability:

• System-wide:
  • The incorrect setting of policy for real-time threads is fixed. It has not been set the PTHREAD_EXPLICIT_SCHED thread flag.
  • The control of dual capture of the resource in the single thread and capture the resource by timeout.
  • Mechanism to prevent the multiple startup is corrected for verification of PID of the blocked process due to removal by the system the lock-files in the directory /tmp.
  • The packing of classes structure's data using the # pragma pack (push, 1) is disabled because of the appearance of implicit buzz bug of one of the threads and blocking the rest on the OpenSCADA firmware of LP8x81 PLC.
  • Initialization and updating code of modules is updated to avoid the double initialization of shared libraries.
  • The function of the task creation is corrected to prevent crashing when creating the automatically closed tasks during the rapid closing.
  • The hang of function cron() is fixed at reason zero scheduling set.
• Transports:
  • Serial, DAQ.DCON, DAQ.ModBus: Transport of the serial interface is optimized, is made the typical one and is corrected for several errors. The transport's clients are adapted to use the new mechanism.
  • Sockets, SSL: The possibility of incomplete recording by the write() function is fixed. When writing to the socket, this function writes only the part of the size of its buffer (50k). For complete record of large messages the repeat of record is added.
  • Transport.SSL: It is finally fixed the waiting for data response from the server by waiting the data processing in the BIO_read() functions.
  • Transport.Sockets: The processing of null result of the waiting the tail of messages is fixed to avoid hangs on the queries in DAQ.System.HDDTemp.
  • Transport.Serial: CSTOPB flag using for stop bits number set is fixed.

  * Data acquisition:

  • ModBus: The loss of resources during the data acquisition if fixed. For this reason it is excluded the possibility of assigning the string directly to the object of the resource string.
  • JavaLikeCalc: The using of functions for the parameters of the DAQ controllers from the IO functions for first use is fixed.
  • DAQ, BlockCalc, JavaLikeCalc, LogicLev, Siemens: The receiving of the erroneous data on the redundancy scheme in the nonredundant tasks and with the absence of redundant stations is fixed.
• Protocol.HTTP, UI.WebCfg, UI.WebCfgD, UI.WebUser, UI.Vision: The value of the HTTP-parameter "Content-Type" is fixed for the "Charset" element.
• UI.VCAEngine: The crash of the VCA when changing the mutable attributes, that are multiply inherited, is fixed.

Optimization and performance improvement:

• SYS.XML: Conversion function of an XML tree into a string is optimized over the time.
• SYS.Archive: The mechanism for adaptive generation of requests to the archives of various qualities in the case of a general request is added. It prevents the long processing time in the case of requesting the large intervals of time and the availability of lower quality archives.
• DAQ, DAQ.DAQGate: Optimization of request between redundant stations over the requests' size and time is done. Only archive attributes of DAQ parameters and attributes, planned to request, are requested.
• Archive.FSArch: The creation of information files of the packaged archives without storing these data in the database is added. This feature allows quick connection of large archives to other stations.
• UI.Vision: In the "ElFigure" primitive for the drawing it is used QPixmap instead of QImage, it greatly improved the performance.
• UI.Vision: To construct the image of the "Diagram" primitive the QImage is used instead of QPicture, it greatly improved the performance.
• TFunction, DAQ.JavaLikeCalc: The enclosed context of the functions is added in order to improve the performance of external calls.

Optimization of the memory usage:

• SYS: The system is switched to the traditional "map" instead of "hash_map" for all objects in order to reduce memory consumption.
• UI.VCAEngine: The object of the "Attr" attribute is divorced from the "TCntrNode" object in order to reduce memory consumption by up to 25%.

3 Improvement and stabilization of the VCA.

Notable changes were made in the visual control area (VCA), namely, in the VCA engine (UI.VCAEngine) modules: UI.Vision and UI.WebVision visualizers. These changes were aimed at stabilizing, optimization of memory consumption and improvement of user's properties of VCA.

Improvements of the VCA:

• The full support for vertical scaling of the diagrams is added.
• The support for alpha channel in color attributes of all primitives is added.
• UI.VCAEngine:
  • It is included and made safe the inheritance of the description of mutable attributes.
  • The new user's API functions for the sessions are added: wdgAdd(), wdgDel(), link() and linkSet(). Addition of these functions allowed to implement the concept of a fully dynamic formation of the user interface.
  • Properties of access rights to the widget are implemented by the attributes "owner" and "perm" to increase the flexibility of control.
  • The mechanism for automatically creating and running session at startup is added.
• UI.Vision:
  • In the attributes inspector the ability of group setting of same attributes of various widgets is added. Setting is done in the group container of the properties of attributes' inspector that appears when you select multiple widgets simultaneously.
  • In the "ElFigure" primitive for the drawing the QPixmap is used instead of QImage, it greatly improved the performance.
  • To construct the image of the "Diagram" primitive The QImage is used instead of QPicture, it greatly improved performance.
  • The support of properties of the user interface is added. The control and changing of the toolbar icons' size is added.
  • The ability to copy the values of attributes and links through the context menu of attributes' and links' inspectors is added.
  • The search function in the "TextEdit" element is added.
• UI.WebVision:
  • The support of turning the "Text" primitive is added.
  • The generation of the basic mouse events is added. For processing of some events the stack of processing functions is added.
  • For the sender-user the access to its session and control is adapted.

4 Formation and stabilization of API of user's programming.

Extensively it has been made the formation of new object API of the user's programming, which provides the integration of user's functions in the objects' tree of OpenSCADA. In addition, a number of changes to the existing library of functions of the user's API was made.

In particular the following changes were done:

• SYS:
  • SYS, Special.FLibSYS: XMLNodeObj object of the user's API moved into the OpenSCADA core (tvariant.h and tvariant.cpp files).
  • User's system API of OpenSCADA based on the TCntrNodeObj object is expanded to control the user's access rights.
  • TAreaObj object is renamed to TArrayObj.
  • Properties of objects, functions' calls and exceptions' processing of user's API are unified.
  • SYS.TVarObj: The propList() function is added to provide an ability to scan the attributes.
• DAQ.JavaLikeCalc:
  • Functions of the user's API: insert(), replace(), toReal(), toInt(), parse(), parsePath() and path2sep() are added in the object of the string type value.
  • The isEVal() function is added to basic types in order to detect the EVAL-values.
• Special.FLibComplex1: PID function is expanded with new parameters: Kd, Tzd and followSp. The Tf parameter is removed.
• Object API of the user's programming:
  • SYS: User's API functions: system(), message(), XMLNode(), cntrReq(), time(), localtime(), strftime(), strptime(), cron(), messDebug(), messInfo(), messNote(), messWarning(), messErr(), messCrit(), messAlert(), messEmerg() и strFromCharCode() are added to the root object of the OpenSCADA core.
  • DB: SQLReq() user's API function is added to the database object.
  • Transport: messIO() user's API function is added to the object of the outgoing transport.
  • UI.VCAEngine:
    • User's API functions: user(), alrmSndPlay() and alrmQuittance() are added to the session's object of the project.
    • To the "Widget" object the functions of user's API were added: ownerSess(), ownerPage(), ownerWdg(), attrPresent(), attr(), attrSet(), wdgAdd(), wdgDel(), link() and linkSet().
    • The special attribute "this" is added into all VCA's scripts to access the widget's object and further calling of its functions of user's API.
  • Archives: messGet() user's API function is added to the object of subsystem "Archives".
  • DAQ.Value: The functions of user's API get() and set() of the attribute are added.

5 System-wide expansions.

To the system-wide API of OpenSCADA system there have been made the significant changes and expansions in order to improve the functionality and overall stabilization:

• SYS:
  • The mechanism to prevent re-run is added to the scripts: demo-start and user-start.
  • The global functions to create (register) taskCreate () and to close taskDestroy () of the treads are added. All components of OpenSCADA use new API.
  • The debian/* files for support the building of Debian packages are added.
  • The strParse() function is added for the expansion of the strSepParse() function in order to support of multi-character separators and for the integration of single-character ones.
  • The infrastructure of the debugging counters is added.
  • The ability to assign processors to the threads of OpenSCADA on multi-processor systems and multi-core processors is added.
  • The task manager is added. The id field of the thread's process is added to the task manager.
  • To implement specific functions the wrapper on the tasks of OpenSCADA is added. The "TError" exceptions' processing is added for the tasks inside the wrapper.
  • The core's code of the OpenSCADA is placed in the "OSCADA" scope. Version of the OpenSCADA's сore library is increased to 1:0:0.
  • The rules of access to all elements of the control interface are unified.
  • The check for a version 2.0 of the libtool library is added. It is enabled the building of only shared libraries for modules.
  • The ID of the module is placed in the class of the constructor to simplify initialization of translating the text messages of the modules.
  • For all translations the parameters "-C --no-location --no-wrap -k_" of the xgettext utility are used. It is used for cleaning the garbage from the translation files.
  • API versions of the all modular sub-systems are set to 5.
• SYS.Function, DAQ.BlockCalc, DAQ.LogicLev, UI.VCAEngine: The mechanism for changes' monitoring in the parameters of "DAQ" subsystem's controller is added.
• DB:
  • The automatic opening of the available tables on request to them is added.
  • The transaction control is added to the function sqlReq(), as well as the function transCloseCheck() is added.
• TFunction, DAQ.JavaLikeCalc: The enclosed сontext of functions is added in order to improve the performance of external calls.
• DAQ: The error code is added to the state of the controller, which allows us to identify state and display it.
• Protocol, Transport, DAQ.ModBus, Protocol.UserProtocol: The function itemListIn() is added to select elements of a protocol. The module's API of the subsystem is changed to 3. The selection of protocol's elements via the function TProtocol::itemListIn() is added.

6 Significant improvements and fixes of the individual modules.

While working on this industrial release the significant changes, improvements and stabilization were made with the individual modules of OpenSCADA:

• DB.MySQL:
  • The support for unbounded values of "Real" and "Integer" data types is added.
  • The conversion of EVAL for the real type is added.
• DB.SQLite: The transaction mechanism is improved to support user's SQL-queries and closing the old transactions.
• DB.FireBird: The support for multilingual text variables is added. The support of transactions is unified.
• DAQ:
  • DAQGate: The support of ability to request the individual attributes is added. It is used to request the archived and often requested attributes. All other attributes are requested with the period of synchronization by a full request. It is used to reduce the workload and time in exchange of DAQGate with a remote OpenSCADA station.
  • ICP_DAS: The status of the DIP-switch for LP-8781 PLC is added. The functions to send the messages via the serial interface are moved into the general serReq() function and all requests use it.
  • ModBus: The suffixes "i2, i4, f, b0" are added to the registers (R and RI) for flexible access through a variety of data types.
  • JavaLikeCalc:
    • The support of the review loop "for( <i> in <obj> ) <code>;" to scan the object's properties is added.
    • Properties of objects, functions' calls and exceptions' processing of user's API are unified.
• Transport:
  • Serial:
    • The ability to select the type of the thread's control is added. It is supported the hardware (CRTSCTS) and software (IXON IXOFF) thread's control.
    • The support of the modem mode for all input and output transports is added.
  • SSL:
    • The support of KeepAlive limits is added. The support of reconnection after the connection loss for prevention the loss of messages is added.
    • The getting of the sender's address is added.
  • SSL, Sockets: In the outgoing transport it is added the timings for the individual connection time and time of the subsequent responses control.
  • Protocol.HTTP:
    • The function of the outgoing protocol is added.
    • The support of automatic login is added.
• Archive.FSArch: The creation of information files of packaged archives is added without storing these data in the database. This feature allows quick connection of large archives to other stations.
• UI.QTCfg:
  • The adjustment of rows for tables after adding the new rows is added. The support for copying the contents of the table to the clipboard is added.
  • The search function in the "TextEdit" element is added.
  • The ability to copy the list of selected nodes is added.

7 Formation of the documentation, translation of documentation and interface.

Since this release is positioned as an industrial release with a prolonged period of support, it was finished writing the documentation in Russian and translation into English of all the main documentation. In addition, the translation of the user's interface into English, Russian, Ukrainian and German languages is completed:

• The README translation into Ukrainian is added.
• The translation of the DAQ document and the summarizing document into English is done.
• The document "Quick Start" is added.
• The translation of the document "Quick Start" into English language is added.
• General document "OpenSCADA" in English is updated to include the following parts: "Quick Start" and DAQ.OPC_UA.
• The interface translation of the system core to Russian, Ukrainian and German languages is updated.
• For all translations the parameters "-C - no-location - no-wrap-k_" of the xgettext utility are used. It is used for cleaning the garbage from the translation files.

8 Unification of the demonstration database.

During the preparation of the industrial release, considerable attention was paid to improving the demo database as a vivid demonstration of the OpenSCADA system:

• Significant upgrade to support new features and include new improvements from the automation control system of ball mills.
• The support of user's calling of the demonstration database in the full mode on the record is added.
• The scaling of existing elements in the case of absence of rows and/or columns for the overview frame and the result graphics is added.
• It is updated to include new models of machines of technological processes and for adapt all the other models.
• It is updated for:
  • Addition of the signaling objects of the compressors: KM201, KM301, KM202 and KM302.
  • Support of the manual input of variables from the control panel.
  • Translation's update.
  • Fixing of the several bugs.
• Script of the main page of the project is rewritten to use new functions of the user's API.
• The new mechanism to access user's interface elements is used. The real read access for a simple user ("user") is provided.

9 Solutions, based on OpenSCADA

Actually the whole range of automation solutions is built on the basis of OpenSCADA project, which clearly demonstrates the capabilities and is the signal of readiness of the system for the wide industrial application.

In general, on the basis of OpenSCADA the authors of the project solved the following tasks: the full dynamic simulation (modeling) of technological processes (TP), process control at the level of the programmable logic controller (PLC) and formation of HMI of the TP.

Modelling of the TP is presented by the solutions: "Library of models of technological devices", "The dynamic model of real-time of the Anastasievskaja GLKS" and "The dynamic model of the steam boiler number 9 DMKD" . Besides the solution "The dynamic model of real-time of the Anastasievskaja GLKS" was the basis for the demonstration project database and it is distributed with all distributions of OpenSCADA.

The scope of process control at the level of the programmable logic controller (PLC) is presented by the solution "OpenSCADA into programmable logic controller (PLC)" and "Runtime of the PLC LP-8x81 of the ICP DAS company based on the OpenSCADA".

The scope of the formation of the TP HMI is presented by the solutions: "Library of the graphic elements of the user's interfaces" and " ACS TP of the ball mills "ШБМ 287/410" of the boiler "БКЗ 160–100 ПТ" ".

One should also note the presence of a number of solutions that are not included in the list above, and made by the developers of the system for the third parties or directly by the users.

Conclusion

OpenSCADA system is ready for practical use in harsh industrial conditions and to perform a wide range of automatic process control tasks.

With the purpose to provide the quality service based on the OpenSCADA solutions, as well as for development in the direction of support the specialized equipment, protocols and interfaces, developers are actively working on the formation the policy of providing the services on the commercial basis. The list of commercial services will include: technical support, consultations and targeted development of extensions, integration and implementation of solutions, and development of customized solutions and products, based on OpenSCADA.

The 0.7.0 version provides the OpenSCADA solutions only for the Linux x86 and x86_64 platforms. To implement the support of other hardware and software platforms, planned by the project, the work will continue. So, for version 0.8.0 it is planned to expand the support of hardware platforms, at least of the ARM platform, as the representative of RISC architecture.

In the appearance of the first industrial version of OpenSCADA actively participated the following people:

• Roman Savochenko: The main works on the projecting, development, documentation's writing and testing.
• Maxim Lysenko: Development of the "ElFigure" VCA primitive, creation of the DB module "PostgreSQL" and translation of the main part of documentation into English.
• Yashina Ksenia: Development of the "ElFigure" VCA primitive.
• Попкова Ирина: Translation of the system interface of OpenSCADA and its modules into German language.
• Almaz Kharimov: Development of the DCON Protocol module and active testing of the system.
• Popkov Aleksey: Active testing and participation.
• Many other OpenSCADA users, via extensive testing.

• Dynamic models of of technological processes and their control systems: Gas compressor station for six compressors, steam multifuel boiler unit BKZ-160.
• The model and controller (ICP_DAS) of the ACS of ball mill for coal grinding for the boilers of thermal power station.
• OpenSCADA on the mobile devices: Nokia N800, N950.
• OpenSCADA on the industrial controllers: ICP_DAS LP-8781, LP-5141.

ICP_DAS

Until the last moment there were a number of reasons that prevent the creation of an OpenSCADA build for ARM-controllers of the ICP DAS:

• absence of the ARM-controller;
• unavailability of OpenSCADA to work on ARM-architecture;
• extremely outdated Linux environment on the ARM-controllers of "ICP DAS".

At the moment, all of these obstacles have been eliminated. So, thanks to Peter Litkovets we got the LP-5141 controller, and by this time OpenSCADA was largely already adapted to work on ARM-architecture, through processing and stabilization on the handheld computer of Nokia company - N800. Later during the same work with the LP-5141 controller it has been eliminated the last obstacle by updating the original software environment while maintaining the original functionality.

In general, the goal of this project is to develop the mechanisms and the creation of OpenSCADA building for the ARM family of the controllers of "ICP DAS" company, as well as the creation of a firmware for the "ICP DAS" controllers, which will fall into the hands of OpenSCADA developers.

1. PLC LP-5141

PLC is designed in the monoblock form-factor that does not include built-in computer-process interface, and the connection of the external one is made through the built in RS-485, for example, in the form of modules I-7000 of the the "ICP DAS" company.

CPU of the controller has the following specifications:

2. Software environment based on OpenSCADA.

Software environment, based on the Linux operating system for ARM controllers of ICP DAS usually includes: the Linux kernel 2.6.19, GLibC 2.2.5 and GCC 2.95. To build a third-party software the ICP DAS provides an SDK with the cross-compiler, set of libraries and headers for them (Linux toolchain). As you can see, the version of GCC and are very old, namely it is the 2001 year. OpenSCADA building in this environment is actually impossible. If the using of the GLibC of 2.2.5 version is still possible, the GCC of version 2.95 has the C++ compiler, which crashes during the building of the OpenSCADA code, and the standard C++ library or STL is extremely limited and it requires the significant and senseless adaptation. For this reason, it is necessary to update the original software environment to version for at least 3 of GCC compiler and C++ library.

Because internal flash memory has a relatively small capacity (64 MB), and a full rebuild of the original software environment of the controller - a very laborious process, it was decided to ensure the compatibility of the basic libraries of old and new environments. Namely, the ability to use libraries like fontconfig, i8k from the source environment and the work of the source environment programs with the new libraries.

In the process of selecting a new software environment for the PXA-270 processor of the "ICP DAS" controller several options have been tried because some of them had one or other disadvantages:

• crosstool-0.43 — interesting but outdated project (latest version is 2006 year) to build a Linux cross environment for the necessary equipment. It was postponed after several unsuccessful attempts to build a new environment to work with "Software FP" and "VFP". As it turned out subsequently for the original environment object files the information about the presence there "Software FP" and "VFP" is incorrectly displayed, when in fact the operations with real numbers there are made through "FPA". Consequently, we may later return to this version.
• PXA-Linux Project — a project to create an independent set of Linux tools for building for the PXA processor. It has the binary building 02-25-2005/bin/arm-linux-toolchain-bin-12-15-04-driscoll.tar.gz. It turned out that this building was built with the "Software FP" and "VFP", and also has a problem in the form of disabling of set of expansions for the gcc compiler, for example: __attribute__((packed)).
• binary build of the cross compilation tools (arm-linux-gcc-3.4.1.tar.gz) from the firm "Voipac" for their own equipment on the PXA-270 processor. This set approached perfectly for all parameters and the subsequent building was done using it.

The resulting environment of the controller with OpenSCADA was formed by replacing the original environment core libraries on the libraries from the "Voipac" set of tools, building of the OpenSCADA and placing the OpenSCADA files to source environment tree.

OpenSCADA was built with disabling of the number of libraries and modules. So, it were build and tested the following modules and functions of OpenSCADA:

• OpenSCADA core — built with the LibGD2 library (the work is checked). In the process of checking and adaptation the functions of storage the OpenSCADA configuration in the configuration file are expanded.
• DB.SQLite — SQLite DB (the work is checked). The library and module of OpenSCADA to work with SQLite database are built. During the check process the error of GLibC 2.3.2, related to the lack of check on inter-locking of "rw"-resources is found and eliminated.
• DB.DBF — DBF DB (the work is checked). Module to work with DBF-files of version 3.
• Transport.Sockets — The module the the TCP, UDP and Unix sockets' transport (the work is checked). In the process of TCP-sockets using it was found and corrected the structure's of check the socket's status not initialization.
• Transport.SSL — Transport module of the secure socket layer: SSL, TLS (the work is checked).
• Transport.Serial — Transport module of serial interfaces (the work is checked). It was found that for some reason COM3 is located on the device /dev/ttySA3.
• Protocol.SelfSystem — The module of the own OpenSCADA protocol (the work is checked).
• Protocol.HTTP — The module of the HTTP protocol implementation (the work is checked).
• Protocol.ModBus — The module of the ModBus protocol implementation (the work is checked). The configuration of the station as a data server through the ModBus protocol.
• Protocol.OPC_UA — The module of the OPC UA protocol implementation (the work is checked). The configuration of the station as a data server through the OPC UA protocol . There was a problem of difference of real number representation on x86 and ARM FPA!
• Protocol.UserProtocol — The module of free implementation by the user of simple protocols using the programming language of OpenSCADA (the work is checked).
• DAQ.System — The module of the operating system data (the work is checked). It is built without the LibSensors library using.
• DAQ.JavaLikeCalc — The module of implementation of user Java-like language and calculations based on it (the work is checked).
• DAQ.BlockCalc — The module of implementation of block computing (the work is checked).
• DAQ.LogicLev — The module of implementation of the logic level data sources (the work is checked).
• DAQ.ModBus — The module of working with data sources via the ModBus protocol (the work is checked).
• DAQ.DCON — The module of working with data sources via the DCON protocol (the work is checked). For example, with the devices ICP_DAS I-7000. It was found and fixed the crash when receiving a negative response size. The result of the answer is now always returned >=0.
• DAQ.ICP_DAS — The module of the ICP_DAS data sources (there is no equipment to check). Serial series: I-87000 and I-7000; Parallel (quick): series I-8000. The module is built with a library libi8k.a for ARM-architecture.
  
• DAQ.DAQGate — The module of implementation of the locking of data sources from other OpenSCADA stations (the work is checked).
• DAQ.OPC_UA — The module of working with data sources via the OPC_UA protocol (the work is checked). There was a problem of difference of real number representation on x86 and ARM FPA - the conversion when transmitting is added!
• DAQ.Siemens — The module of the working with the Siemens controllers via Industrial Ethernet (ISO_TCP) (the work is checked).
• DAQ.SNMP — The data acquisition module of the network equipment via SNMP (the work is checked).
• Archive.DBArch — The module of the database archiving (the work is checked).
• Archive.FSArch — The module of the file system archiving (the work is checked). There was a problem during the verifying of the archive, giving the following message at startup: "Error archive file structure: <ARCHIVES/VAL/1s/CPULoad_load 2011-09-12 17:47:17.val>. Margin = -8 byte. Will try fix it!". As a result, it was found that the algorithm of fast bits' counting is not aligned to 4 bytes when reading the memory buffer - it is fixed.
• UI.WebCfg — The Web configurator module of OpenSCADA (the work is checked).
• UI.WebCfgD — The dynamic Web configurator module of OpenSCADA (the work is checked).
• UI.VCAEngine — The visualization engine module (the work is checked).
• UI.WebVision — The module of the user interfaces visualizer in the UI.VCAEngine by means of the Web-interface (the work is checked).
• UI.WebUser — The module of free user's visualization by means of the Web-interface (the work is checked).
• Special.FLibComplex1 — The library of compatibility functions with Complex1 ("DIYA" LTD) (the work is checked). It is used for the block programming.
• Special.FLibMath —The library of standard mathematical functions (the work is checked).
• Special.FLibSYS — The library of system expansion functions of OpenSCADA (the work is checked).

For the purpose of convenient distribution and use of the resulting OpenSCADA build for ARM-controllers of "ICP DAS" the parsing of the firmwares format for these controllers and the formation of a new one, including OpenSCADA were completed. The firmware of the "ICP DAS" ARM-controllers is a binary file with a name like "lp5x4x_1.1.bin". Structurally, this file contains the kernel and root file system - JFFS2. You can get their exact location by using the commands in the original environment of the controller, for example, for LP-5141:

From the obtained result of the command you can conclude that the connection point of the image kernel and filesystem is placed at 0x280000 offset of the firmware file, and the size of the erase flash block is 0x80000 (512kB). With this information we can extract the firmware and make changes to the image of its file system:

Thus we get the new firmware with OpenSCADA in the file lp5x4x_oscada_1.0.bin, which can be downloaded to the controller in the standard way, described in the "ICP DAS" documentation.

3. Remarks

As it turned out that the operations with real numbers are performed by the FPA co-processor instructions (Float Point Acceleration), which is not present in this processor, and calls of the commands themselves are made through an imitation of an exception in the Linux kernel, then the performance of mathematical calculations is extremely low, even compared to the direct "Software FP", "VFP". For example, the calculation of a single operation sin(pi) is about ~200 ms, compared to ~20 ms for N800 with VFP and ~2 ms at x86, detailed in next table. So, this controller shouldn't be considered as the platform for at least any serious calculations! Moreover, the real numbers when working with FPA are stored in a different way - namely, the special big-endian, which requires a transformation in the case of the binary external exchange to the typical little-endian representation, for example for DAQ.OPC_UA.

A significant difference in computing time on an ARM with a direct call to the mathematical operations and from a virtual machine JavaLikeCalc may be related to unaligned reading from the memory when reading the instructions the virtual machine, with which it makes sense to find out later and maybe somehow compensate.

In the initial configuration the COM1 port (/dev/ttySA0) is used as a console, which is initialized by the kernel command "console=/dev/ttySA0". However, after adjustment this is not necessary and is often desirable to release another one COM-port for other purposes. It is possible to release COM1 from work for a console by reassigning the other device for this role, for example by: $busybox setconsole /dev/tty1. However, this method does not fully release the COM-port and requests are lost, reading by the parallel connection.

4. Conclusion

The result was the building of OpenSCADA for Linux controllers of ARM-architecture of "ICP DAS" company. The building can be loaded directly on any Linux-ARM controller, unpacking it at the root of the original operating system. In this case, however, the duplicates of the old core libraries (/lib/*) will remain, which can be removed after a successful restart.

For family of controllers LP-5x4x the firmware with the building OpenSCADA was created, which can be downloaded in the standard for these controllers way, which is described in the original "ICP DAS" documentation. Firmware for LP-5x4x can possible fit for the LP-5x3x, but it is not checked!

• Dynamic models of of technological processes and their control systems: Gas compressor station for six compressors, steam multifuel boiler unit BKZ-160.
• The model and controller (ICP_DAS) of the ACS of ball mill for coal grinding for the boilers of thermal power station.
• OpenSCADA on the mobile devices: Nokia N800, N950.
• OpenSCADA on the industrial controllers: ICP_DAS LP-8781, LP-5141.

The area of the automation object - 300 m2. The air temperature in rooms intended for the server, sensors and actuators placement from 10 to 25 degrees Celsius. The air temperature outside the premises where the sensors and actuators are placed: from - 30 to 30 ° C.

The levels of pollution, humidity, light, noise and ionizing radiation correspond to sanitary and epidemiological requirements for residential buildings and premises (САНПИН 2.1.2.1002-00).

At the object there is electromagnetic radiation induced by the appliances, as well as by means of different equipment (Bluetooth, Wi-Fi, GSM).

The "Smart house. Control Server" system is a hardware-software module, which is the main control center of the automation object. The server receives and processes signals from various sensors, generates and transmits signals to control actuators, communicating with the user via GSM. Management of the system is made via the web interface.

The "Smart house. Control Server" system includes the following subsystems:

1. Access control subsystem.
2. Lighting control subsystem.
3. Climate control subsystem.
4. Water network control subsystem.
5. Household and multimedia devices control subsystem.
6. Subsystem of the processing the information from the sensors.
7. Subsystem for the providing the interaction with the user through the Web-interface and via GSM.
8. Authorization subsystem.
9. The reporting subsystem.
10. Configuration subsystem provides mechanisms to add, remove or edit information in the used database for the 1-8 subsystems.

The block diagram of the house automation system is shown in Figure 1.

To control the various hardware of the house it was designed the hub and built the wireless network ZigBee of the devices for the equipment control. Overall equipment control, as well as providing the Web-based user interface and other methods of notification are made by the dedicated server of house automation. The hub if the ZigBee network is connected to the server through the RS-232 and ModBus/RTU protocol. Alarms in the automatics' control area will be sent to the user via SMS-notifications through the connected GSM-modem.

Wireless controller has the following specifications:

• The presence of the ZigBee transceiver;
• ZigBee protocol data rate of at least 200 kb/s;
• Availability of USB or COM - port to connect to the server;
• Power supply 220 V.

GSM-module has the following specifications (Siemens TC65):

• Support of GSM-900;
• Availability of USB or COM - port to connect to the server;
• Support of AT standard commands of the GSM 07.05 GSM 07.07;
• Power supply 220 V.

The hardware of the server:

• processor of x86_32 or x86_64 architecture (not less than Intel Core2Duo);
• 2GB DDR3 RAM;
• presence of at least three USB - ports.

As a software environment, to serve the house automation functions — "Smart House" an open SCADA system OpenSCADA is used, in the environment of which it is designed the Web-based user interface "Smart House", and implemented the interrogation and control of devices via ZigBee concentrator.

2. Automation system

OpenSCADA system has several ways of forming visualization user interfaces, stating from integrated development tools of standard interfaces of controls the various areas of automation and ending by the low-level mechanisms of libraries and interfaces of graphic concepts.

The integrated interfaces of OpenSCADA are:

• The "UI.VCAEngine" module — visualization engine to build a unified interfaces and presentations (final visualization) using different types of graphical interfaces, as well as with the ability to work as a server of visualization interface.
• The "UI.Vision" module — "UI.VCAEngine" visualizer and the GUI development interface based on the QT4 library.
• The "UI.WebVision" module — "UI.VCAEngine" visualizer based on the Web-interfaces: XHTML, XML, CSS, JavaScript, DOM and AJAX.

The low-level mechanisms of constructing the user interfaces include any other graphics libraries, which have a rapid development tools of the user interface. The co-operation with OpenSCADA is produced as with data source and with the interface of the unified control of the equipment under different protocols.

In order to provide the ability of user's Web-interfaces formation directly in the OpenSCADA, the module "UI.WebUser" module is provided. Overall, the OpenSCADA contains all the basic functions of a typical Web-server, as follows:

• Acception of the client connections over standard transport protocols: TCP, UDP, Unix, as well as over the protected connections SSL и TLS.
• Support of the basic HTTP protocol functions: GET and POST.
• Dynamic creation of user-generated content through an internal JavaScript (JavaLikeCalc) language in the form of the flows with the contents: HTML, XHTML, XML, CSS, JavaScript languages, images of different formats, etc.

Consequently, for the construction of any user control interface it is enough to have installed OpenSCADA system with the following modules: Transport.Sockets,Transport.SSL, Protocol.HTTP and UI.WebUser.

2.1. The structure and location of files

In order to reduce the load on the fully dynamic formation of the user interface, as well as to facilitate the future expansion and modification of style the Web-interface was divided into static and dynamic parts.

The static part consists of a set of template HTML-files with labels of the dynamics placement and resource files: CSS, JavaScript and images. In general, the static part is represented by files, which are described in the table below:

The dynamic part is implemented by the scripts in the internal language of OpenSCADA - JavaLikeCalc, which are described in the table below:

In general, the algorithm processing the requests to the pages is(on the example of localhost/WebUser/temperature):

• request is received in the script /sub_UI/mod_WebUser/hs from the transport /sub_Transport/mod_Sockets/in_WEB_1, by means of the Protocol.HTTP protocol module;
• the template file is loaded temperature.html;
• the script of the "devMon" page is being looking for (/sub_DAQ/mod_JavaLikeCalc/lib_web/devMon). If the script argument is missing the script search is made by the name of the page (/sub_DAQ/mod_JavaLikeCalc/lib_web/temperature);
• the transfer of the page's template to the found script for the formation of dynamics is made;
• the result of the page's script execution is placed to the main template;
• if the page's script is not found, the page's template puts its contents directly into the main template.

2.2. Devices Manager

The Devices Manager is available only for root and builds the form for edit, and and remove devices of two types: binary and decimal.

The created device are placed in the attributes list of the parameter of the specifically taken subsystem of "ZigBee" controller of the data source module "ModBus" (/sub_DAQ/mod_ModBus/cntr_ZegBee/). Recording format of an attribute is as follows:

• «R:0:r:cond:Airconditioning:bin:10:Enabled:0:Disabled:(120|100)» — for binary sensor:
  • R — ModBus register;
  • 0 — ModBus register address;
  • r — read only;
  • cond — ID of an attribute-senso;
  • Airconditioning — sensor's name;
  • bin — sensor's type - "Binary";
  • 10 — the first value;
  • Enabled — the name of the first value;
  • 0 — the second value;
  • Disabled — the name of the second value;
  • (120|100) — location coordinates ({x}|{y}) of the sensor in the scheme of premises.
• «R:3:rw:tGhost1:The temperature in the living room 1:dec:deg. С:y=2*x;:(120|100)» — for the decimal sensor:
  • rw — read only;
  • dec — sensor's type - "Decimal";
  • deg. C — unit of the variable;
  • y=2*x; — conversion formula for the received variable for display;
  • (120|100) — location coordinates ({x}|{y}) of the sensor in the scheme of premises.

In addition to direct sensors the configuration and formation of alarms is made in the form of text procedure. The program of formation is placed in the "var" attribute of the alarms controller parameter /sub_DAQ/mod_JavaLikeCalc/cntr_alarms/prm_rules. The "var" attribute contains the following XML tree:

According to the XML-tree the formation of alarms and sending SMS-notifications to the subscribed users is made in the controller's task/sub_DAQ/mod_JavaLikeCalc/cntr_alarms, which is executed with a period of 1 minute.

SMS-notifications are sent via the serial transport /sub_Transport/mod_Serial/out_GSM and through the user's SMS-protocol (/sub_Protocol/mod_UserProtocol/up_SMS).

You can also select the delayed giving of the control action. To do this, the user sets the right time, in the form of: {Min}:{Sec}. Processing of the delayed control is made in the controller /sub_DAQ/mod_JavaLikeCalc/cntr_timers by setting the "var" attribute of the "rules" parameter with the help of requests in the XML tree:

2.3. Subsystems

All visualization subsystems are served by the /sub_DAQ/mod_JavaLikeCalc/lib_web/devMon script. This script process the requests from the script of the dynamic visualization of Web-browser and receive the data on the subsystem's devices, required for visualization. Data about the devices are transferred in accordance with the privileges of the logged user.

The configuration of sensors is read from the parameter corresponding to the "ZigBee" controller's subsystem (/sub_DAQ/mod_ModBus/cntr_ZegBee). The values are read and written to the attributes of the sensors of these parameters or through the controller or delayed management.

The task of the "ZigBee" controller is executed with the period of 1 second, in the process of which the request of the the current values of all configured sensors is made. Record of the the values is made on the fact of modification, regardless of the periodic polling task or through the delayed management controller in the case of installation of nonzero timer.

Connection to the "ZigBee" controller is made via serial outgoing transport /sub_Transport/mod_Serial/out_ZegBee.

2.4. Users manager

Users manager is intended to create, delete and edit accounts of ordinary users.

Users are divided into administrators and ordinary users. Identification of the user as an administrator in the OpenSCADA system is made by turning it into the "WebRoot" group (/sub_Security/grp_WebRoot). An ordinary user is included into the "Web" group (/sub_Security/grp_Web).

In OpenSCADA system, each user (/sub_Security/usr_test1/) has a text description field, which in this case serves to store its special settings in the following way:

In the case of an administrator's account the records of an access rights to the subsystems are not available, but there are system-wide settings such as the lifetime of the session (/sub_Protocol/mod_HTTP).

2.5. Messages

The message list is formed based on the active list of alarms in their categories "ALARM:House:*" in tabular form, with the time, category, level and the alarm message.

2.6. Reports

During the report's generating the time range is indicated and messages' types are select. The generation of message for the following types is provided:

• "System events" — includes messages about login and logout users on the resource by means of the massages category "/\/sub_Protocol\/mod_HTTP\//".
• "Monitoring and management subsystems' events" — includes alarms and record the new values of the sensors through the categories of messages «/(ALARM|SET)\:House\/:».

The protocol is formed as a table with the time, category, level and message of the alarm, which is also recorded in the separate report file, later available on the link to the separate opening.

Introduction

This release is a planned one of a working version of OpenSCADA, which are usually made at intervals of 3-4 months. The main purpose of this release is the implementation of commercial service on the OpenSCADA basis and adaptation to the ARM hardware. In addition to the main purposes within the limits of this release a great work for stabilization, cleaning the source code, as well as for the full empowerment is made.

This document is the processing (compilation) of <ChangeLog> document of the OpenSCADA system of 0.7.1 version, which is designed for briefly and clearly covering the new features and changes of the OpenSCADA system. To get acquainted with all the changes in the OpenSCADA system it is possible in the .file ChangeLog from the distribution kit of the system, or here: http://oscada.org/websvn/filedetails.php?repname=OpenSCADA&path=%2Ftrunk%2FOpenSCADA%2FChangeLog .

The key features of this version are:

• Implementation of planned tasks.
• Optimization, increasing of stability, sustainability and system performance.
• Improvement and stabilization of the graphics subsystem.
• Formation and stabilization of user programming API.
• System-wide expansions.

New and updated modules are:

• Archive.FSArch (1.4.5) - Significant stabilization.
• DB.MySQL (1.7.0) - Stabilization. The ability to specify connection timeouts is added.
• DB.SQLite (1.6.3) - Stabilization.
• DB.FireBird (0.9.6) - Stabilization.
• DB.PostgreSQL (0.9.1) - Stabilization.
• DAQ.DiamondBoards (1.2.2) - Stabilization.
• DAQ.System (1.7.3) - Stabilization. Dependence on the library "Libsensors" is made optional.
• DAQ.BlockCalc (1.4.1) - Stabilization. The syntax highlighting is added.
• DAQ.JavaLikeCalc (1.9.0) - Stabilization. The syntax highlighting is added. The adaptation to the ARM architecture hardware is made. The implementation of regular expressions and a number of extensions of user API is added. The ability to write characters in a string using octal "\041" and hex "\x21" numbers is added.
• DAQ.LogicLev (1.1.3) - Stabilization. Certain extension.
• DAQ.SNMP (0.6.0) - Stabilization. Implementation of the full support of the client-side of protocol. The support for all types of values is added. The support for writing values is added. Errors handling is improved. Additional connection configuration options are added.
• DAQ.Siemens (1.2.4) - Stabilization.
• DAQ.ModBus (1.1.2) - Stabilization. The syntax highlighting of the attributes' list is added. Some improvements.
• DAQ.DCON (0.5.0) - The module is completely rewritten for support of mixed modules by selecting the query command.
• DAQ.ICP_DAS (0.7.3) - Stabilization.
• DAQ.DAQGate (0.9.2) - Stabilization. The parameters' cache for their initialization during the autonomous operation is added.
• DAQ.SoundCard (0.6.2) - Stabilization.
• DAQ.OPC_UA (0.6.1) - Stabilization. he syntax highlighting of the attributes' list is added.
• DAQ.BFN (0.5.0) - New module.
• Transport.Sockets (1.4.6) - Stabilization.
• Transport.SSL (0.9.6) - Stabilization.
• Transport.Serial (0.7.2) - Stabilization. During initialization of the port the previous settings are used and an opportunity to omit some of the settings is implemented.
• Protocol.ModBus (0.6.2) - Stabilization. Some improvements.
• Protocol.OPC_UA (0.6.1) - Stabilization.
• Protocol.HTTP (1.5.1) - Stabilization. The support for HTTP variable "Transfer-Encoding = chunked" in the outgoing transport is added.
• Protocol.SelfSystem (0.9.4) - Stabilization.
• Protocol.UserProtocol (0.6.1) - The syntax highlighting is added.
• Special.SystemTests (1.5.1) - Some improvements.
• UI.QTStarter (1.6.1) - Stabilization. Adaptation for the ARM.
• UI.QTCfg (2.0.0) - Stabilization. The group request to the control interface is used to optimize the remote access to OpenSCADA stations. Adaptation for the ARM. The function for the manual change the height of the elements of the text and tables (grabbed the bottom edge and dragging) is added. The multi-level syntax highlighting is added.
• UI.WebCfg (1.5.5) - Stabilization.
• UI.WebCfgD (0.6.6) - Stabilization.
• UI.VCAEngine (1.1.0) - Stabilization. The tooltip for the attributes of widget's primitives is added. The syntax highlighting to the text attributes of widget's primitives is added.
• UI.Vision (1.1.0) - Significant stabilization. Notable improvements. Adapted for the ARM. The display and restoration of lost communication are added during the remote execution of the session. The separate full-text editor for text attributes is added. The tooltip for the attributes of widget's primitives is added. The syntax highlighting for text attributes of the widgets primitives is added. The dialog of the set properties adjustment of separately selected figures is added.
• UI.WebVision (0.9.1) - Significant stabilization. Small improvements.
• UI.WebUser (0.6.1) - Stabilization. The syntax highlighting of the procedures is added.

1 Implementation of planned tasks

In accordance with the plane of the release there were made the following tasks:

• Formation of the provision of commercial services based on OpenSCADA. - The concept is built and the mechanisms are created to provide commercial services by the developers based on OpenSCADA (http://oscada.org/en/services ).
• Adaptation of OpenSCADA to work on the ARM hardware platform. - The building, adaptation and full testing of OpenSCADA on the ARM architecture is made on the N800 Internet tablet of the Nokia company (http://wiki.oscada.org/Works/Tests/ARM (RU)). As well as private activities for adaptation:
  • SYS: Functions' prototypes TMess::put(), TMess::get(), TCntrNode::grpSize(), TCntrNode::grpId(), TCntrNode::grpAt() are changed to correct the usage of an unsigned type "char" on the ARM as a signed.
  • SYS.TVariant, DAQ.AMRDevs, DAQ.OPC_UA: The not aligned access to data is fixed.
  • SYS.TCntrNode: The usage of an unsigned type "char" on the ARM as a signed is fixed.
  • Archive: Functions' prototypes TArchiveS::messPut() and TArchiveS::messGet() are changed to correct variable of the message level as a signed number.
  • DAQ.JavaLikeCalc: Virtual Machine is rewritten for direct using the structures of commands to avoid alignment problems, as well as for some increasing of productivity.
  • DAQ.Siemens: The problem of the NoDave library for a global packing structures command calling "#pragma pack(1)" is fixed.
  • UI.QTCfg: The short time sleep after closing all windows in the switch off function is added. In order to provide the time for the object of all the windows to be finally destroyed and to prevent crashing.

2 Optimization, stability, sustainability and system performance increasing

During the work on this version, as well as its practical adaptation, it was discovered and corrected in a total of about 90 errors. In general, work has been done on cleaning code from the compiler's warnings with the "-Wall" flag:

• unused variables removing;
• adding the return in the all functions;
• initialization of variables with the possibility of their undefined using;
• exception of the incomplete handling of the enumeration types in the select operation;
• comparison between signed with unsigned integer.

Lets list the most significant errors correction of which significantly affected the increasing of stability:

• System-wide:
  • The command of the building system "$ make dist" is corrected and adapted to correct creation of the OpenSCADA distributions.
  • The TSYS::cron() function to call on the schedule is repeatedly corrected.
  • The variable type to store the result of the find() function, the string, is everywhere changed to the correct one "size_t".
  • Function: The possibility of a memory leak when attempting to set the object to a non-object function's parameter is excluded.
• Data bases:
  • DB.PostgreSQL: The handling of database address to determine the empty fields is fixed.
• Transports and protocols:
  • Transport: The loading of transports from the database is fixed, if there are records about the transport the module of which is missing.
  • Transport.Serial: O_NONBLOCK flag is set to open() function of a serial device to prevent the blocking of port's opening on some USB-> RS485 converters.
  • Transport.Sockets, Transport.SSL: The clearing of the input buffer is added to prevent re-use on high latency channels after timeout.
  • Transport.Sockets: The closing of the client connection by the time out of the lifetime for connections in the case of the data absence is fixed.
  • Transport.Sockets: Unix-socket is set to nonblocking mode by the O_NONBLOCK flag. The generating of the error messages for outgoing transports is fixed.
  • Protocol.HTTP, UI.WebCfg, UI.WebCfgD, UI.WebVision, UI.WebUser: The parsing of POST-request elements is fixed by the for parsing all the attributes of each element.
• Data acquisition and archives:
  • Archive: The using of the buffer with a soft grid with low-and high-resolution time in the archives of values is fixed.
  • Archive.FSArch: The creation of messages archive's files when you place a set of old messages is fixed. The parameter to prevent duplicates is added.
  • Archive.FSArch: The result of the fgetc() function is recorded in an integer variable instead of a character one that has corrected the discovery of "EOF".
  • DAQ.System: The crash when exiting to the "Hddtemp" source is fixed.
  • DAQ.ModBus: The setting of values of the parameter's attributes mode is changed to active and the error handling is improved.
  • DAQ.JavaLikeCalc: The check of the index when accessing the character of the string on the index is added, in order to prevent the out of range situation.
• Visualization Interface:
  • UI.VCAEngine: The blocking of the session for dynamically active projects with dynamic access to their own widget's attributes is fixed.
  • UI.Vision: The crash of the session for projects with an execution period of more than 500 ms is fixed.
  • UI.Vision: The fine-tuning of the coordinates of the "Elementary figure" primitive shapes is implemented to the remainder of the widget's position.
  • UI.Vision: Scaling the text primitive "Text" is changed to change the font size instead of scaling the final image, which increased the overall quality of the display font.
  • UI.Vision, UI.WebVision: The resolution of the coordinates is increased of all the widgets to three decimal places, in order to ensure proper positioning on a large scales.
  • UI.WebVision, UI.Vision: The redraw of the primitive "Elementary figure" is fixed when the scale is changed.
  • UI.WebVision: The validation of figures' points for their getting to the display area of the primitive "Elementary figure" is removed. This function is shifted to the GD library.
  • UI.WebVision: The possibility of crashing for primitives "Diagram" or "ElFigure" is excluded in the case of transmission of incorrect values of attributes of the image "xSc" or "ySc" from a Web-browser.

Optimization and performance improvement :

• UI.WebCfgD: The resizing of icons on the server side is added to reduce traffic.
• UI.QTCfg: The group request to the control interface is used for performance improvement on slow and high latency connections.
• UI.QTCfg: The multiple query of the elements of selectable table columns is excluded.

3 Improvement and stabilization of the graphics subsystem

The notable work was made within the graphics system, namely in the VCA engine modules UI.VCAEngine, visualizers UI.Vision and UI.WebVision, as well as in the configurators. The changes were provided for stabilization, the optimization of memory consumption and improvement of user's properties.

Improvements of the graphics subsystem:

• SYS, DAQ.JavaLikeCalc, UI.QTCfg, UI.VCAEngine, UI.Vision: The API of syntax highlighting is added. On the basis of this API the syntax highlighting is added to:
  • DAQ.BlockCalc: syntax highlighting in description of the parameters' attributes.
  • DAQ.JavaLikeCalc: syntax highlighting for the compiler of the JavaLikeCalc.JavaScript language, as well as for all text fields using the language inside the module.
  • DAQ.ModBus, DAQ.OPC_UA: syntax highlighting of the attributes' list.
  • Protocol.UserProtocol: syntax highlighting to the text of the protocol's procedures.
  • UI.QTCfg: multilevel syntax highlighting displaying, transmitted from the data model in the form of the rules of regular expressions.
  • UI.VCAEngine: syntax highlighting for text attributes of the widget's primitives for which this is necessary.
  • UI.Vision: syntax highlighting for text attributes of the widget's primitives, as well as for the texts of the widgets' programs.
  • UI.WebUser: syntax highlighting in the procedures for constructing the Web-based interface.
• UI.QTCfg:
  • The ability to manual change the height of the text and table fields. Change is made by grasping and dragging the bottom edge of the field.
  • Group request "CntrReqs" is used to query the page's context.
• UI.VCAEngine: The specific properties of the attributes of primitives are added, such as help and syntax highlighting.
• UI.Vision:
  • The display of help for the widget's attributes is added.
  • The display of message about loss of connection with the visualization server and its recovery is added for remote visualization.
  • For the "Elementary figure" primitive the dialog to set properties for the separately selected figures is added.
  • The separate full-text editor for text attributes is added.
• UI:WebVision: The support for gif and jpg images in the elements of the "Elementary figure" primitive is added.

4 Formation and stabilization of the user programming API

It was continued the development of object API of the user programming, which provides the integration of user's functions in the object's tree of OpenSCADA. In addition, a number of changes was made to the existing library of the user's API functions.

In particular the following changes were made:

• SYS: User's API for the TArrayObj object is extended for the possibility of using object properties if the properties are not the numbers.
• SYS: In the object tree of OpenSCADA of the user's API the SYS.Security.access() function is added to control user access to OpenSCADA resources with the necessary privileges.
• SYS, DAQ.JavaLikeCalc: The implementetion of the support for regular expressions of user's API, based on PCRE, through the TRegExp object is added. The interface of functions RegExp.exec() and RegExp.test() is implemented in the standard for the JavaScript language. The "new RegExp()" initialization of the TRegExp object is implemented for the DAQ.JavaLikeCalc. The additional functions using RegExp: int search(); Array match(); Array split(RegExp pat, int limit); string replace(string substr, string str); string replace(RegExp pat, string str) are implemented for DAQ.JavaLikeCalc.
• TFunction, DAQ.JavaLikeCalc: The user's API object "TFuncArgObj" is added for function arguments get.
• DB: The following functions of the user's API are added: fieldStruct(), fieldSeek(), fieldGet(), fieldSet() and fieldDel() for thetable object to provide the user access to the database through the database interface OpenSCADA.
• DAQ.JavaLikeCalc: The built-in function typeof() to check the value's type is added.

5 System-wide expansions

To the system-wide API of the OpenSCADA system there have been made the significant changes and extensions with the purpose of the general stabilization and in view of the general measures for cleaning the source code and reorganizing the sources' tree:

• SYS:
  • The new structure of the sources tree is implemented.
  • All the resources of the project are moved to the separate archive.
  • To create sources' and resources' archives you can use the command "$ make dist-lzma" and "$ make dist-reslzma".
  • Documentation is made the static for modules and is divided by languages. For each documentation language it is formed the separate package. In the documentation of each language it is created an index file for the entire list of local and network documentation. The total list of local documentation is greatly expanded with new documents, as well as with the supported network documentation.
  • The packages of librarian databases are added: *-LibDB.Main and *-LibDB.VCA, they are placed to data/LibsDB.
  • Instead of the DemoDB package the packages of the "AGLKS" and "Boiler" models are added and placed to the data/ModelsDB.
  • Configuration files to build RPM and DEB packages have been updated.
  • Dependence on the library PCRECPP is globally replaced by PCRE.
  • The new function TSYS::time2str() is added to convert time intervals into a string like "1hour 23min 10sec". This function is used everywhere.
  • The implementation of own XML-parser is added, instead of Expat. The own XML-parser solves the problem of supporting different character sets other than UTF, as well as the problem of safe handling the situation of the characters presence that are not valid for the current character encoding.
• SYS.TMess: Common control interface messages are moved into one TMess::lab* function.
• Transport, Transport.*: The function TTransportS::traf2str() is added to convert the value of the traffic's counter to the string like "12.5KiB".

Conclusion

The OpenSCADA system gets the push for the implementation of real hardware multiplatform, whereby the project's code has been largely cleaned up and made multiplatform. These developments will enable the project to continue moving toward the hardware multiplatform, as well as the implementation of the program multiplatform that is scheduled after the next LTS release 0.8.0.

Work also is continued on improving the overall functionality, simplicity and ease of using with the general improvement of the quality of service based on the OpenSCADA system.