From OpenSCADAWiki
Jump to: navigation, search

Other languages:

The page contains information allowing to receive general representation about functions which OpenSCADA can carry out by the current moment. Functions are grouped on main spheres of application of OpenSCADA. For receiving a picture as a whole of functions planned or make now their are included also. The page also have demands of OpenSCADA for it building and execution.

1 The employment areas of OpenSCADA

Separating to the employment areas was made to simplify perception of the system functionality in light of traditional area for the project OpenSCADA — automation of technological processes. But also there possible mixed and specialized configuring systems for real-time data operation, for example into areas: ERP, Billing, Smart House and etc.

Fig. 1. Roles of the OpenSCADA system.

1.1 System server of SCADA

  • Visual control and management by means of the interfaces:
    • Remote visualization server grounded on visualization and control area (VCA) engine VCAEngine. Module UI.Vision local starting and connecting to the visualization server.
    • Remote WEB interface. By means of a Web-browser, a visualization module WebVision and a module of the core of visual control area VCAEngine.
    • Simple remote Web-interfaces of user. By means of a Web-browser and the UI-module WebUser.
  • Data acquisition (DAQ) from sources:
    • Information about a platform (hardware-software) on which the server works. By means of the DAQ-module System.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition from controllers of firm Siemens of S7 series. By means of the DAQ-module Siemens.
    • Data acquisition of industrial controllers under the protocol ModBus. By means of the DAQ-module ModBus.
    • Data acquisition of industrial controllers under the protocol DCON. By means of the DAQ-module DCON.
    • Formation of derivative structures of parameters on the basis of templates of parameters and data from other sources. By means of the DAQ-module LogicLev.
    • Data acquisition from other servers and PLC, based on OpenSCADA, possibly for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sound controller's input channels. By means of the DAQ-module SoundCard.
    • Data acquisition from hardware of firm ICP DAS. By means of the DAQ-module ICP_DAS.
    • Data acquisition from sources which support protocol OPC-UA. By means of the DAQ-module OPC-UA.
    • Data acquisition from automation of "Big Dutchman" company. By means of the DAQ-module BFN.
    • Data acquisition from sources DAQ-boars on buses ISA, PCI, PCMCIA and USB by means library of the project Comedi and the DAQ-module Comedi.
    • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Making by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also the transport's protocol module User Protocol. Most known protocols implementing on the Users Protocols: SMS, SMTP, Elemer TM510x, EDWARDS TURBOMOLECULAR PUMPS (SCU750), Heat counter computer VKT7, Sycon Multi Drop Protocol, Power supply for turbomolecular pumps (TMP-xx03), Temperature measurement IT-3, OWEN, IVE-452HS-02, OPTRIS CT/CTL, CTR 100-101, IEC-60870-104, I2C Chips (PCF8591, PCF8574, DS3231, AT24CXX), 1Wire Chips by adapters DS9097 and DS9097U (DS1820, DS1820/DS18S20/DS1920, DS1822, DS2413, DS2408, DS2450, DS2438), Low level devices by GPIO (DHT, 1602A), etc.
  • Providing data to upper-level systems:
    • By means of interfaces:
      • Serial interface (RS232, RS485, Modem, ...), by means of the transport module Serial.
      • IP-networks sockets and network level protocols TCP, UDP and Unix, by means of the transport module Sockets.
      • Security sockets layer (SSL), by means of the transport module SSL.
    • By means of protocols:
      • Self OpenSCADA protocol, by means of transport's protocol module SelfSystem.
      • ModBus family protocols (TCP, RTU and ASCII), by means of the transport's protocol module ModBus.
      • "OPC-UA" protocol, by means of the transport's protocol module OPC-UA.
      • Simple special protocols, developed by users by means of the transport's protocol module User Protocol.
  • Implementation of user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving of messages on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
    • In plans. On other server, it is possible for an allocated archiving server, based on OpenSCADA.
  • Archiving values of the collected data by means of mechanisms:
    • Files with double packing: consecutive and standard archiver gzip. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
  • Configuration and management of a server through:
    • The WEB-interface. By means of a Web-browser and the UI-module WebCfgD and WebCfg.
    • From remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol SelfSystem.
  • Data storage of a server in a DB of types:
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • PostgreSQL. By means of the DB-module PostgreSQL.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module [Special:MyLanguage/Modules/FireBird|FireBird]].
    • Directories by LDAP. By means of the DB-module LDAP.
    • In plans. DB accessible on other server based on OpenSCADA.

1.2 Station of the operator of technological process, the board of the dispatcher, the panel of monitoring, etc.

  • Visual control and management by means of the interfaces:
    • Local (fast) interface based on Qt library. By means of the visualization module Vision and the module of a core of the visual control area VCAEngine include ability of visualization from remote engine of VCA, visualization server.
    • Remote WEB interface. By means of a Web-browser, the visualization module WebVision and the module of a core of visual control area VCAEngine.
    • Simple remote Web-interfaces of user. By means of a Web-browser and the UI-module WebUser.
  • Data acquisition (DAQ) from sources:
    • Data acquisition from other servers and PLC, based on OpenSCADA, for data transportation and for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition from sources which support protocol OPC-UA. By means of the DAQ-module OPC-UA.
  • Implementation of user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving messages on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
    • In plans. On other server, it is possible to an allocated archiving server, based on OpenSCADA.
  • Configuration and management of a station through:
    • WEB-interface. By means of a Web-browser and the UI-module WebCfgD or WebCfg.
    • Qt-interface. By means of the UI-module QTCfg.
    • From remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol SelfSystem.
  • Data storage of a station in a DB of types:
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • PostgreSQL. By means of the DB-module PostgreSQL.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module FireBird.
    • Directories by LDAP. By means of the DB-module LDAP
    • In plans. DB accessible on other server based on OpenSCADA.

1.3 Environment of execution of the controllers (PLC)

  • Data acquisition (DAQ) from sources:
    • Cards of data acquisition of firm Diamond Systems. By means of the DAQ-module DiamondBoards.
    • Information about a platform (hardware-software) on which the server works. By means of the DAQ-module System.
    • Data acquisition from sources which support protocol SNMP (Simple Network Management Protoсol). By means of the DAQ-module SNMP.
    • Data acquisition of industrial controllers under the protocol ModBus. By means of the DAQ-module [[Special:MyLanguage/Modules/ModBus|ModBus].
    • Data acquisition of industrial controllers under the protocol DCON. By means of the DAQ-module DCON.
    • Formation of derivative structures of parameters on the basis of templates of parameters and data from other sources. By means of the DAQ-module LogicLev.
    • Data acquisition from other servers and PLC, based on OpenSCADA, possibly for duplication. By means of the DAQ-module DAQGate.
    • Data acquisition from sound controller's input channels. By means of the DAQ-module SoundCard.
    • Data acquisition from hardware of firm ICP DAS. By means of the DAQ-module ICP_DAS.
    • Data acquisition from sources which support protocol OPC-UA. By means of the DAQ-module OPC-UA.
    • Data acquisition from sources DAQ-boars on buses ISA, PCI, PCMCIA and USB by means library of the project Comedi and the DAQ-module Comedi.
    • Data acquisition from different sources, which have utilities for access to it data or it accessibly through simple special network protocols. Making by getting procedure writing on language of user programming by DAQ-module JavaLikeCalc, and also the transport's protocol module User Protocol. Most known protocols implementing on the Users Protocols: SMS, SMTP, Elemer TM510x, EDWARDS TURBOMOLECULAR PUMPS (SCU750), Heat counter computer VKT7, Sycon Multi Drop Protocol, Power supply for turbomolecular pumps (TMP-xx03), Temperature measurement IT-3, OWEN, IVE-452HS-02, OPTRIS CT/CTL, CTR 100-101, IEC-60870-104, I2C Chips (PCF8591, PCF8574, DS3231, AT24CXX), 1Wire Chips by adapters DS9097 and DS9097U (DS1820, DS1820/DS18S20/DS1920, DS1822, DS2413, DS2408, DS2450, DS2438), Low level devices by GPIO (DHT, 1602A), etc.
  • Providing data to upper-level systems:
    • By means of interfaces:
      • Serial interface (RS232, RS485, Modem, ...), by means of the transport module Serial.
      • IP-networks sockets and network level protocols TCP, UDP and Unix, by means of the transport module Sockets.
      • Security sockets layer (SSL), by means of the transport module SSL.
    • By means of protocols:
      • Self OpenSCADA protocol, by means of the transport's protocol module SelfSystem.
      • ModBus family protocols (TCP, RTU and ASCII), by means of the transport's protocol module ModBus.
      • "OPC-UA" protocol, by means of the transport's protocol module OPC-UA.
      • Simple special protocols, developed by users by means of the transport's protocol module User Protocol.
  • Management, regulation and performance of other user calculations in languages:
    • Language of block schemes. By means of the DAQ-module BlockCalc.
    • With the help of Java-like language of a high level. By means of the DAQ-module JavaLikeCalc.
  • Archiving messages on various categories and levels by means of mechanisms:
    • Files in a XML-format or the flat text with packing the out-of-date archives. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module [Special:MyLanguage/Modules/DBArch|DBArch]].
    • In plans. On other server, it is possible to the allocated archiving server, based on OpenSCADA.
  • Archiving of values of the collected data by means of mechanisms:
    • Buffers in memory of the setting depth. By means of the built in archiving mechanism of the values of core OpenSCADA.
    • Files with double packing: consecutive and standard archiver gzip. By means of the archiving module FSArch.
    • In tables of archival DB. By means of the archiving module DBArch.
  • Configuration and management PLC through:
    • The WEB-interface. By means of a Web-browser and the UI-module WebCfgD or WebCfg.
    • From the remote configuration station. By means of the UI-module at configuration station QTCfg and the interface of management OpenSCADA reflected in the protocol [Special:MyLanguage/Modules/SelfSystem|SelfSystem]].
  • Data storage PLC in a DB of types:
    • All data in a configuration file.
    • MySQL. By means of the DB-module MySQL.
    • SQLite. By means of the DB-module SQLite.
    • PostgreSQL. By means of the DB-module PostgreSQL.
    • DBF. By means of the DB-module DBF.
    • FireBird. By means of the DB-module FireBird.
    • Directories by LDAP. By means of the DB-module LDAP
    • In plans. DB accessible on other server based on OpenSCADA.

1.4 Universal OPC-UA server

Due implementation of the protocol OPC-UA into agent mode, OpenSCADA can provide a popular function of the OPC-server to client's protocols, which supports and direct implemented into OpenSCADA. The function common uses on platform MS Windows®, and many SCADA-systems on the platform work exclusively with OPC—servers, as the data sources. Thus OpenSCADA can act as an universal OPC-server on Linux platform (Fig.2).

In plans. With adapting OpenSCADA for work on MS Windows® platform and implementing work with OPC-DA by system DCOM, there will appear possibility for applying OpenSCADA into gate OPC-DA -> OPC-UA role, which means free integration of old systems to the new or accumulation systems.

Fig. 2. OpenSCADA system role as "OPC-UA Server".

The data sources and protocols, which accessible by the unified OPC-UA server:

2 Requirements for OpenSCADA

2.1 Execution

The demands to apparatus for OpenSCADA system execution at different roles viewed into table 1. The demands to programs for OpenSCADA system execution and it modules allow into table 2.

Table 1. The demands to apparatus for OpenSCADA system and it modules.

Role Demands
Server of the SCADA system

CPU: x86_32 (more than i586), x86_64 or ARM, with frequency more to 500 MHz
MEM: 128 MB
HDD: 10 GB include OS and space for archives

Station of the operator of technological process, the board of the dispatcher, the panel of monitoring, etc.

CPU: x86_32 (more than i586), x86_64 or ARM, with frequency more to 1 GHz
MEM: 512 MB
HDD: 4 GB include OS without any archive space

Environment of execution of controllers (PLC)

CPU: x86_32 (more than i586), x86_64 or ARM, with frequency more to 133 MHz
MEM: 32 MB
HDD: 32 MB include OS without any archive space

Table 2. Dependencies of execution of OpenSCADA system and its modules.

Component Description
Dependencies of OpenSCADA system's core
OS Linux Distribution kit of operating system Linux (ALTLinux, SuSELinux, Mandriva, ASPLinux, Fedora, Debian, Ubuntu ...)
"Standard libraries" Standard set of libraries: GLibC (>= 2.3) or uCLibC (>= 0.9.32) and libstdc++ (>= 3.3). Certainly this already allowed into the installed distribution. A special demand is using native thread library NPTL, already used for all modern distributions of Linux.
zlib Compression library.
libpcre Library for use regular expressions, compatible with Perl.
libgd (opt: --enable-LibGD) Graphic library GD version 2, it is desirable that it will be without XPM support (a dependence on library of X-server is excluded) and support for FontConfig.
DB.SQLite module
libsqlite3 Library for access to embedded DB SQLite version 3.
DB.MySQL module
libMySQL Library for access to MySQL DBMS.
DB.PostgreSQL module
libpq Library for access to PostgreSQL DBMS version more 8.3.0.
DB.FireBird module
FirebirdSS FireBird DBMS version 2. Often it is absent in distribution kits of Linux and demands individual loading from an official site (http://www.firebirdsql.org)!
DB.ODBC module
iodbc iODBC Driver Manager library.
DAQ.System module
libsensors (opt: auto) Hardware sensors' library versions 2 and 3.
DAQ.OPC_UA module
libssl Library for codifying OpenSSL.
DAQ.SNMP module
libsnmp Library for access to data of network devices under SNMP protocol.
DAQ.Comedi module
libcomedi Library of realizing support for DAQ-boards different manufacturer on boards ISA, PCI, PCMCIA and USB.
DAQ.SoundCard module
libportaudio Multiplatform library for access to sound controller version 19 and higher (not 18).
Transport.SSL module
libssl Library for codifying OpenSSL.
Modules: UI.QTStarter, UI.QTCfg
libQt4 (libQtGui) or
libQt5 (libQt5Widgets,libQt5PrintSupport)
Library Qt version 4.3 and higher or 5.1 and higher for construction of user graphical interfaces.
UI.Vision module
libQt4 (libQtGui) or
libQt5 (libQt5Widgets,libQt5PrintSupport)
Library Qt version 4.3 and higher or 5.1 and higher for construction of user graphical interfaces.
libQtWebKit or libqt5webkit5 (opt: auto) Library of Web-rendering engine WebKit.
libfftw3 (opt: auto) Library for fast Fourie transfer of signals.
libphonon or libphonon4qt5 (opt: auto) Library for full formatted video and audio playing.
UI.WebCfgD module
libgd (opt: --enable-LibGD) Graphic library GD version 2, it is desirable that it will be without XPM support (a dependence on library of X-server is excluded) and support for FontConfig.
UI.WebVision module
libgd Graphic library GD version 2, it is desirable that it will be without XPM support (a dependence on library of X-server is excluded) and support for FontConfig.
libfftw3 (opt: auto) Library for fast Fourie transfer of signals.
Special.FLibSYS module
libssl (opt: auto) Library for codifying OpenSSL.
libfftw3 (opt: auto) Library for fast Fourie transfer of signals.

* "opt: auto" — provides for disable of using the library at building time on it absence.

2.2 Building

Dependencies of the system OpenSCADA for OpenSCADA core and its modules building are tabulated bellow.

Table 3. Dependencies to build OpenSCADA and its modules.

Component Description
The general requirements of OpenSCADA building
OS Linux Distribution kit of operating system Linux (ALTLinux, SuSELinux, Mandriva, ASPLinux, Fedora, Debian, Ubuntu ...)
g++ Compiler of language C++ version 3.3 and more from a collection of compilers GCC, including library GLibC (>=2.3), uCLibC (>= 0.9.32) or Android BioniC.
autotools (autoconf, automake, libtool, pkg-config) Tools to form a building environment of OpenSCADA. They are necessary only in the case of changing the building environment of OpenSCADA, for example at addition a new module or changing fixed parameters of the building. Automake >= 1.9.
gettext A group of utilities for preparation and compilations of translations of the interface of programs on various languages in conformity with the internationalization standard I18N.
sqlite3 Control utility for DB SQLite3 files management.
zlib (devel) Compression library, a package for development.
libpcre (devel) Library for use regular expressions, compatible with Perl, a package for development.
libgd (devel, opt: --enable-LibGD) Graphic library GD version 2, a package for development, it is desirable that it will be without XPM support (dependence on library of a X-server is excluded) and support of FontConfig. It is used for construction of trends and other images in PNG, GIF and JPEG.
DB.SQLite module
libsqlite3 (devel) Library for access to built in DB SQLite version 3, a package for development.
DB.MySQL module
libMySQL (devel) Library for access to MySQL DBMS, a package for development on language C.
DB.PostgreSQL module
libpq Library for access to PostgreSQL DBMS version more 8.3.0, a package for development.
DB.FireBird module
FirebirdSS FireBird DBMS version 2, a package for development. Often it is absent in distribution kits of Linux and demands individual loading from an official site (http://www.firebirdsql.org)!
DB.ODBC module
iodbc iODBC Driver Manager library, a package for development.
DAQ.JavaLikeCalc module
bison The program for generation parsers on the basis of grammar of the language.
DAQ.System module
libsensors (devel, opt: auto) Hardware sensors' library versions 2 and 3, a package for development.
DAQ.OPC_UA module
libssl (devel) Library for codifying OpenSSL, a package for development.
DAQ.SNMP module
libsnmp (devel) Library for access to data of network devices under SNMP protocol, a package for development.
DAQ.Comedi module
libcomedi (devel) Library of realizing support for DAQ-boards different manufacturer on buses ISA, PCI, PCMCIA and USB, a package for development.
DAQ.SoundCard module
libportaudio (devel) Multiplatform library for access to sound controller, a package for development version 19 and higher (not 18).
Transport.SSL module
libssl (devel) Library for codifying OpenSSL, a package for development.
Modules: UI.QTStarter, UI.QTCfg
libQt4 or libQt5 (devel) Library Qt version 4.3 and higher or 5.1 and higher for construction of user graphic interfaces, a package for development.
UI.Vision module
libQt4 or libQt5 (devel) Library Qt version 4.3 and higher or 5.1 and higher for construction of user graphic interfaces, a package for development.
libQtWebKit or libqt5webkit5 (devel, opt: auto) Library of Web-rendering engine WebKit, a package for development.
libfftw3 (devel, opt: auto) Library for fast Fourie transfer of signals, a package for development.
libphonon or libphonon4qt5 (devel, opt: auto) Library for full formatted video and audio playing, a package for development.
UI.WebCfgD module
libgd (devel, opt: --enable-LibGD) Graphic library GD version 2, a package for development, it is desirable that it will be without XPM support (dependence on library of a X-server is excluded) and support of FontConfig. It is used for construction of trends and other images in PNG, GIF and JPEG.
UI.WebVision module
libgd (devel) Graphic library GD version 2, a package for development, it is desirable that it will be without XPM support (dependence on library of a X-server is excluded) and support of FontConfig. It is used for construction of trends and other images in PNG, GIF and JPEG.
libfftw3 (devel, opt: auto) Library for fast Fourie transfer of signals, package for development.
Special.FLibSYS module
libssl (devel, opt: auto) Library for codifying OpenSSL, a package for development.
libfftw3 (devel, opt: auto) Library for fast Fourie transfer of signals, package for development.

* "opt: auto" — provides for disable of using the library at build time on it absence.