Welcome to the main site of the open SCADA project

OpenSCADA is an open implementation of SCADA (Supervisory Control And Data Acquisition) and HMI (Human-Machine Interface) systems. The main properties of the program are: openness(Opens internal link in current windowGPL,GFDL), modularityscalability and multiplatform. Read more here or learn functional characteristics of the program here.

The site contains materials about OpenSCADA and it serves for granting information on the project, and also for the program development process control, together with the Opens external link in new windowproject's Wiki-resource.


Latest news:

Tuesday 01. October 2019

The complex objects conception in the DAQ is formed and documented

In some cases where an object is only a part of a common automated system and does not require deep detailing to the level of signals and parameters (complex tag) around them, including without the need for archiving, it is convenient to unify them in one representative object of the data source OpenSCADA with appropriate consolidated view and object control as a set of simple attributes with violation elements.

The conception is represented currently by the two direct DAQ-templates "SNMP", "UPS" and the representative widget "Object properties" of the "Main elements library of the user interface".

Category: Display only category:NewsDisplay only category:Development

Friday 20. September 2019

The main elements library of the user interface appended for the extended alarms control frames

The alarm frames serves:

  • Alarms — active (alarmsAct) — to dynamically display the active violations in a tabular form and to highlight them in color and text
  • Alarms — state (alarmsSt) — to display the violations history and to update their dynamically for the current time in a full-format tabular form, to highlight them in color and text and the possibility of multilevel filtering
  • Alarms — report (alarmsStReport) — to display a report document based on a list of violations received from the previous full-format frame of presenting the violations history.

The violations are obtained from the buffer of current-active violations of OpenSCADA and archive(s). In fact, the element implements the primitive "Protocol" functions for violations and extension opportunities.

The main user extension is the ability to define visible table fields from a list of options: atm, qttm, nrmtm, lev, cat, mess, prm, dscr, dscrCust{N}, alrm, cmnt.

Category: Display only category:NewsDisplay only category:Development

Tuesday 20. August 2019

The main elements library of the user interface appended for the "Users manager" frame

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

  • forming a list of controlled users;
  • the ability to view and change user information for: name, full name, description, password and groups;
  • adding new and deleting existing users.

Category: Display only category:NewsDisplay only category:Development

Thursday 15. August 2019

The root page frame of the main elements library of the user interface is significantly expanded and documented

The frame "Root page" is a base element of most interfaces built in OpenSCADA and it was completely documented and significantly expanded for:

  • dynamization of forming the signal object buttons from one base button, with the result possibility of forming very number of signal objects, up to 100 for short names.
  • dynamization and unification of the types of view to their abstract encoding as "viewN", with the result possibility to appoint any other mean to the type of view.
  • correct cleaning the control panels container.

Category: Display only category:NewsDisplay only category:Development

Monday 12. August 2019

Analysis of the memory consumption and efficiency of the UI module WebVision in the busy environments

The module UI.WebVision was observed in extra memory consumption on a real big task working on Debian 9.

There were performed several actions of measuring about this module work on different Debian versions: 7, 8, 9, 10; where we have seen the clear degradation of effectivity of the memory allocation on Debian versions from 8.

Contacting the Debian community we revealed this problem as a disadvantage of GLibC in implementing memory arenas, which can be highly fragmentated in program environments what actively recreating the threads, due to linking the arenas to threads.

So, to fix this behaviour, we need to set the environment variable MALLOC_ARENA_MAX=1, what was be done for all live disks of the automation Linux distributive.

Category: Display only category:NewsDisplay only category:Development