Difference between revisions of "Translations:Documents/Program manual/403/uk"

Let's start the observing with configuration of the OpenSCADA system parameters that are placed in the six tabs of the root page of the station:
* The tab "Station" contains basic information and configuration fields of the station, Figure 4a. List the fields provided and comment on them:
** ''Station'' — contains information about the station's identifier and indicates the localized station's name. The identifier is specified by the command line parameter "--station"; when loading it is sought a section in the configuration file appropriate to the station identifier, and if not detected, it uses the first available one. The name is specified by the command line parameter "--statName".
** ''Configuration file'' — contains information about the configuration file used by the program. Set by the command-line parameter "--config" or the project.
** ''Work directory'' — contains information of the working directory of the station. This is used in relative addressing of objects in the file system, for example, database files. This is installed by [[#Projects|the project manager]] at startup or directly in [[#CfgFilePrm|configuration the program launch]].
** ''Modules directory'' — contains information of directories of modules of OpenSCADA, separated by ';', they can include a files' template in the end (/my/modules/path/lib*.so). [[file:at.png]] If the value of this field is incorrect then when the program is started, the program ends with a message in the console that the configuration is incorrect.
** ''Icons directory'' — contains information of directories of the program icons, separated by ';'. [[file:at.png]] If the configuration navigation tree have no icons then the value of this field is incorrect.
** ''Documents directory'' — contains information of directories of the program documents, separated by ';'. [[file:at.png]] If you can not to call local documents then the value of this field is incorrect or the documentation is not installed.
** ''Work DB'' — indicates the working Data Base, that is the Data Base part of the combined storage ('''Generic Storage''') used to store main data of the program; which may be the '''[[#CfgFilePrm|Configuration File]]''' (<cfg>) also for excluding completely the Data Base from the data storage.
** ''Save the program at exit, with the period'' — points to the need to save the changed data at finishing of the program and indicates the periodicity in seconds with which to save the changed program's data.
** ''Set modification for the calculated objects'' — most suitable for the production systems together with the previous configuration properties, for the calculation context saving. But it is inconvinient in the development mode, all time reminding for the saving need.
** ''Messages'' — indicates the level of messages beginning from which they are to be processed and directions of the messages sending. Messages below this level will be ignored. The level "Debug (0)" have special sense, it set will enable debug messages generation by different parts of the program. To control the parts debug messages generation you can use the tab "Debug" (Fig.4d), which will be appeared in this case. The directions indicate the need of the message sending to the system logger, to the standard output, error and to the archive:
*** the system logger is a mechanism of operation system for work with messages of the system and software; when this option is enabled the possibility appears to manage and control the OpenSCADA messages by the mechanisms of OS;
*** the standard output and error direct the messages to console in the corresponded level; or to the standard log for some specific embedded systems;
*** the archive of OpenSCADA messages is represented by the message buffer; [[file:at.png]] this option is usually enabled and its disabling leads to the actual disabling of the archiving at the station; saving the message buffer to the storage is carried out by the appropriate message archiver whose creation and configuration can be found in detail in [[#CfgArch|the configuration section of the subsystem "Archives-History"]].
** ''Environment'' — section of the environment information and configuration:
*** ''Program'' — contains information of the program name and version. Usually it is OpenSCADA or name of a solution based on OpenSCADA.
*** ''System'' — contains information of name and version of the Operational System (OS), OS kernel on which the program is executed.
*** ''System time'' — contains information of the actual system time with the timezone.
*** ''System planning clock'' — contains information of the used tasks planning clock and its resolution on the operation system. It allows you to orient with the minimum interval of time of periodic tasks, for example, for tasks of the data acquisition.
*** ''System user'' — contains information of the user from whose the program is executed in OS.
*** ''Language'' — contains information about the charset in which text messages are stored within the program and indicates the complete locale information with language, country and charset in the view "en_GB.UTF-8". [[file:at.png]] Changing the complete locale here is acceptable and it is stored in the "Lang" field of the Configuration File, but it leads to change of messages' language for the interface and dynamic messages without restarting. For cleaning the "Lang" field you can just set here an empty value! [[file:at.png]] In the [[#ConfigTr|MULTILANGUAGE-DYNAMIC mode]] language is taken not only from this field and the language is depended from the user execution context, which can overwrite this field to the context value according to the order:
**** directly specified language (or locale) of the WEB-Browser or language-locale of the remote interface of the Qt-Modules;
**** language of the used local user or "root";
**** taken from non empty the "Lang" field of the Configuration File;
**** value of the environment variable "LANG".
*** ''Host name'' — contains information of the machine name that runs the station.
*** ''CPU'' — contains the CPU operative information and indicates the main CPUs set for use by OpenSCADA tasks. The CPU information represents the accessible CPU/core number and the frequency, which runs the program. Value of frequency is checked every 10 seconds (for X86) and allows you to monitor its change by the power management mechanisms for example. The main CPUs set contains in round brackets a list of used currently CPUs.
*** ''Number of phases of the task invoking'' — to set up phasing of the task invoking in the determined phases number, <= 0 to set optimal, 1 to disable the tasks phasing.
* The tab "Subsystems" contains the list of subsystems (Fig.4b) and allows you to jump directly to them using the context menu.
* The tab "Redundancy" (Fig.4c) contains the configuration of redundancy of the station with the following settings:
** ''Status'' — contains information on the redundancy mechanism, that is current and maximum time spent on the execution of one cycle of the task of redundancy processing.
** ''Station level'' — indicates the level of the station in a scheme of redundancy (0-255).
** ''Redundant task period, seconds'' — indicates the period of execution of the redundancy task in seconds (1-255).
** ''Restore connection timeout, seconds'' — indicates over the which period of time to attempt to reconnect with a lost redundant station in seconds (0-255).
** ''Local primary commands transfer'' — enables of local primary commands transfer to redundant stations for the local changes automatic sync.
** ''Stations'' — contains a table with information about the redundant stations. The stations can be added and removed via contextual menu. Id of the added stations is to be chosen from [[#Transports|the list of available OpenSCADA stations]]. Presence into the table at last one enables the redundancy in whole and opens access to pages of the redundancy configuration at level of the subsystems, if a subsystem supports the redundancy. The table provides the following information about the station:
*** ''Identifier'' — Identifier of the OpenSCADA station, should be changed after the addition by choosing from the list of available ones;
*** ''Name'' — name of the OpenSCADA station;
*** ''Live'' — sign of establishing of a connection with the redundant station;
*** ''Level'' — level of the remote station in the redundancy scheme;
*** ''Counter'' — requests' counter to the redundant station or waiting time, in the case of the absence of connection.
** ''Go to remote stations list configuration'' — command to go to the configuration page of the remote OpenSCADA stations in the subsystem "Transports".
* {{Anch|ConfigTr|The tab "Translations" contains elements of the manager of central translation of text messages}} of the program (Fig.4f) and activates at the multi-language mode enabling by the base language of text variables set:
: [[file:at.png]] You can learn more about the details and specifics of creating multilingual projects in the appropriate "[[Special:MyLanguage/Documents/How_to/Create_multi_language_project|How To]]".
:* ''Status'' — current status of the project messages translation, where can be:
::* "SINGLELANGUAGE, only use the already multilanguage DBs with their modification";
::* "MULTILANGUAGE, creating or modification the configuration DBs as multilanguage ones with the pointed base language '{language}';
::* "MULTILANGUAGE-DYNAMIC, and dynamic translation".
:* ''Base language - locales list'' — enables the multilingual support for text variables in the configuration DBs by entry the base language and the project whole locales (like to "en_US.UTF-8") list (optional) separated by ';'. Further for the text variables in the non basic language in the tables of the database it will be created separate columns. Under the text variables the all text fields of configurator, which can be translated in another language, are meant. Numbers and other special symbols are not in their count and are not translated. The whole locales list is not an obligatory part and used mostly for conversion the language code to whole locale for system functions and in the locale selection lists.
:: [[file:at.png]] You can entry here other language besides English(en) as the base, but take in your mind that all standard OpenSCADA libraries formed for the base language English(en), so other base languages will break these DBs at change!
:* '', dynamic translation'' — planed state of the dynamic text messages translation. The dynamic text messages translation causes the text messages translation cache enabling and requests to the translations to the DB depends to the OpenSCADA part's language, mostly for multi-language dynamic user interfaces when user has self-preferred language and users of the program a lot, as a rule, are end-users-operators.
:* ''Enable the manager'' — enables the generic translation manager which cause full reloading for all built messages obtain, however this does not form the full messages index by deny to reload some objects during their execution. For the full messages index loading you ought to save the manager into the enabled mode and to restart OpenSCADA. Ongoing next start the program will form the full messages index.
:* ''Languages of managing'' — list of the processing languages separated by the character ';'. If the translations for the specified language in the source are presented then the language column will contain them otherwise it will be empty.
:* ''Source filter'' — source filter of limiting the manager work in some DBs, the source just must contain such substring.
:* '', check/fix'' — enable for checking the base messages translation equality in different sources and fixing by: propagation the translations to empty sources, clearing the double to base translations. And the separated-second check for fixing by merging the base messages as the translations, since this operation can be some wrong in complex environments.
:* '', pass'' — pass the specified number of the table items from the top, useful for very big projects which are limited in time of the table complete processing.
:* ''Messages'' — same the messages table with columns: the base language, managing translation languages, the message sources. To modify there are allowed the languages columns and at result the changes will be set to the message sources.
* The tab "Tasks" contains a table with opened tasks of OpenSCADA components (Fig.4d). From the table you can get several information about the tasks, and also assign CPUs used by the tasks of multiprocessing systems and set the task invoking phase.
* The tab "Debug" contains elements for control to debug (Fig.4e) and activates at select the messages level "Debug (0)" or at the objects counters using.