|System||System DA||2.3||GPL2||daq_System.so||en,uk,ru,de||x86,x86_64,ARM||DAQ|| Roman Savochenko
Maxim Lysenko (2009) — the page translation
|Provides data acquisition from the OS. Supported OS Linux data sources: HDDTemp, Sensors, Uptime, Memory, CPU, UPS etc.|
The module is a kind of gateway between OpenSCADA and OS (operating system). The module receives data from various data sources of the OS and allows to manage components of the OS.
The module provides the ability to automatically search for the supported and active data sources with the establishment of parameters for access to them as well as the implementation of the function of the horizontal reservation, that is working in conjunction with the remote station of the same level.
1 The controller object of the data
To add a data source of the operating system there is created and configured the controller object in OpenSCADA. Example of the configuration tab of the controller object of the given type shown in Fig. 1.
From this tab you can set:
- The state of the controller object, as follows: Status, "Enabled","Running" and the name of the database containing the configuration.
- Id, name and description of the controller.
- The state in which the parameter object to be switched at boot time: "Enabled", "Running".
- Automatic search of active data sources and the creation of parameters for them for modes: "Manual", "Fast sources", "Slow sources", "All sources".
- Name of the table to store the configuration of the controller parameters.
- The acquisition schedule policy and the priority of the task of data acquisition.
Module System provides only one type of parameters — "All parameters". Additional configuration fields of the parameters of the module (Fig. 2) are:
- part of the system;
- optional (depending on the data source).
The table below there is a list of supported data sources of the operating system, the value of the additional configuration field and attributes of the parameters.
|Data source||Value of the additional configuration field||Attributes of the parameter||Demands|
|Processor unit (CPU)||Name/number of the process. It can be a number of processor or to be "in general" for all processors <gen>.||
|Memory (MEM)||Not used||
|Sensors (sensors)||Not used||Attributes are defined by sensors that are available on the motherboard. For each sensor the unique attribute is created.||The library libsensors or program mbmon is used. Higher priority in the use is given to the library libsensors, because mbmon has problems on multicore architectures.|
|HDD temperature (hddtemp)||HDD. Disks, available in the system.||
||It must be installed configured and running as a service program hddtemp|
|Uptime (uptime)|| Uptime:
|HDD Smart (hddsmart), slow||Disk. Disks, available in the system.||Attributes are defined by SMART-fields available for this disc. For each field the unique attribute is created.||It must be installed and available smartctl utility.|
|HDD statistics (hddstat)||Disk or partition. Disks or partitions, available in the system.||
|Net statistics (netstat)||Network interface. Network interfaces, available in the system.||
|UPS (NUT) (ups), slow||UPS. Accessible into the system or the network UPS.||Attributes are defined by provided the UPS fields. For each field the unique attribute is created.||Into the system or the network (is not detected automatic and the address you need set directly) must be accessible the demon NUT "upsd".|
|File system (FS)||File Systems. Mounted file systems.||
|Qt sensors (QSensor)||The type of sensor in the list, which is determined by the source and which may be: QAccelerometer, QAmbientLightSensor, QCompass, QIRProximitySensor, QLightSensor, QMagnetometer, QOrientationSensor, QProximitySensor, QRotationSensor, QTapSensor.||