Controlling the camera in the trace mode program. SCADA TRACE MODE. Download SCADA-system. Screen Arguments window

In the course of this laboratory work, the student must master the sequence of creating a project in the Trace Mode Scada system and create his own project according to the individual task of the teacher. Let's proceed directly to the creation of the TRACE MODE project.

You can open the program window by double-clicking on the corresponding icon on the Windows desktop or by finding the program in the Start menu.

To create a project, select the "File \ New" item, select the "Simple" project type in the window that appears and click the "Create" button (Figure 1).

Integrated Development Environment TRACE MODE 6

After that, the project navigator window will automatically be filled with the minimum required layers (Figure 2).

To solve our problem, only two layers will be enough - these are “System” and “Sources / Receivers”. The "RTM" (Real Time Machine) node has already been created in the "System" layer, inside which there is a "Channels" folder and a graphic screen.

Project navigator

Let's start by creating a signal source. To do this, right-click on the "Sources / Receivers" layer, thereby calling the context menu, in which we will go along the path "Create group\PLC" (Figure 3.). A folder called "PLC_1" will appear in this layer. You need to right-click on this folder and create a group "Siemens_PPI_Group" (Figure 4).

Creating a Group in the Sources/Destinations Layer

Creation of the "Siemens_PPI_Group" group

In the "Siemens_PPI_Group" group, we will create three components:

- "Siemens_PPI_MW2_R" - for reading the 2nd word from the Memory Word memory area;

- "Siemens_PPI_MW2_W" - for writing the 2nd word of the Memory Word memory area;

- "Siemens_PPI_DW0" - for reading the zero word of the Discrete memory area.

The screen form of the Siemens_PPI_Group components is shown in Figure 5.

Siemens_PPI_Group components

By double clicking on the “Siemens_PPI_MW2_R” component, we will open its properties window (Figure 6).

Component properties window "Siemens_PPI_MW1_R"

Fill in the fields as follows:

name: Siemens_PPI_MW2_R;
port: 0 ("0" corresponds to COM1, "1" - COM2, etc.);
address: 2 (PLC address in PPI network);
offset: 0x2 (for reading MW2 address);
scope: Markers(WORD);

For the "Siemens_PPI_MW2_W" component, the parameters are exactly the same. Only the direction - Output will change (i.e. writing data to the PLC from the Trace Mode environment). The following are the parameters for the "Siemens_PPI_DW0" component:

name: Siemens_PPI_MW2_R;
port: 0;
address: 2;
offset: 0x0 (read from address zero);
area: Discrete Input (WORD);
direction: Input (i.e. reading data from the controller to the Trace Mode environment).

Next, let's create the appropriate channels for the components. To do this, open an additional navigator window (Figure 7).

Automatic creation of channels

In the upper window, open the "Channels" group belonging to the "RTM_1" node of the "System" layer, and in the lower window - the "Siemens_PPI_Group_1" group, belonging to the group"PLC_1" of the "Sources/Destinations" layer. To automatically create channels, we will use the Drag-and-Drop method, simply drag and drop all components except “Siemens_PPI_MW2_W” into the “Channels” group.

Double-click to open the "Screen#1:1" component belonging to the "RTM_1" node of the "System" layer. There is a rich graphics toolbar to choose from, including controls, different kinds lines and geometric shapes, as well as trends, charts and pointers.

It is also possible to insert images created by the user into the project, which, in turn, can perform control functions or indications.

Let's create three elements of type "Text". To do this, click on the icon of the toolbar, left-click in the selected location of the graphic field and, without releasing, stretch the object to the desired size. In the same way, we will create a button and a light bulb (Figure 8).

Creating a GUI

In the first text field, enter the name, to do this, call the properties window by double-clicking the left mouse button on the text field. In the "Text" column, enter "Data exchange with the SIMATIC S7-200 PLC". Using the appropriate fields, change the color and font of the text, as well as the color of the outline and fill (Figure 9).

Graphic element properties window

Let's call the "Screen Arguments" window from the main menu "View". Using the "Create Argument" button, we will create three arguments, according to the number of channels. Change the data type of all arguments to "INT", and for the second argument, change the type to "OUT". We will leave the names of the arguments unchanged (Figure 10).

Screen Arguments window

Next, we will bind screen arguments to graphic elements. To do this, use the Drag-and-Drop method to drag the first and third arguments onto the text fields. After that, the properties window of the graphic element automatically opens, where in the column "Text" appears "Type of indication - Value" and "Binding - name of the corresponding argument" (Figure 11).

Binding a Screen Argument to a Graphic Element

Now let's create an event for clicking the "Change MW2 value" button. To do this, double-click to open the properties window of the graphic element and go to the "Events" tab (Figure 12). It is possible to set the reaction of the system to two types of events - mouse click on the graphic element and release. Select click, right-click on “MousePress” and select “Pass Value” from the context menu that appears.

A sub-item with the same name will appear with its properties. Select: "Transfer type - Enter and transfer." In the "Result" property, click on the empty column of the "Value" column. The screen argument table will appear. Select the second argument (ARG_001) and click the Finish button.

"Events" tab of the graphic element's properties window

Let's call the properties menu of the graphic object "Light bulb" by double-clicking the left mouse button on this object. Fill in the values as follows (Figure 13): binding:<2>ARG_002; display type: Arg = Const; invert: True; constant: 256.

Properties window for the “Light bulb” graphic element

At the initial moment, the light is off (red). When the binding value is equal to the constant value, the light will turn on (turn green). Applying a signal to the controller input I0.0 will set the value of the zero word of the Discrete Input memory area to 256, which will turn on the light bulb. Thus, the “I0.0” toggle switch on the front panel of the laboratory bench can control the light bulb on the computer screen.

Now you need to create a binding of the screen arguments to the channels and components of the layer "Sources \ Receivers". To do this, in the project navigator, go to the "System" layer, the "RTM_1" node, "Screen # 1: 1" along the path. Right-click on the "Screen#1:1" component and select the "Properties" item in the context menu that appears (Figure 14).

Calling the "Display Properties" window

In the screen properties window that opens, go to the "Arguments" tab (Figure 15).

Arguments tab of the Display Properties window

To create a binding, for each argument, double-click on the empty column "Binding" opposite the corresponding argument to open the connection configuration window (Figure 5.16). In this window, for the first and third arguments, select the appropriate channels (System\RTM_1\Channels), i.e. "Siemens_PPI_MW2_R" and "Siemens_PPI_DW0".

And for the second argument, select "Siemens_PPI_MW2_W", but directly from the "Sources / Receivers" layer (\PLC_1\Siemens_PPI_Group_1\ Siemens_PPI_MW2_W).

Communication Configuration window

After each selection made, you need to press the "Binding" button. Save the created project: "File\Save". Let's return to the "Project Navigator" window, it can be called from the main "View" menu. Select the "RTM_1" node of the "System" layer and press the "Save for RTM" button of the "Project" main menu. When saving a project for a real-time monitor, a node folder "RTM_1" is created in the project folder.

This completes the creation of the graphical interface, but before starting the execution environment, it is necessary to create a COM port configuration file for the correct operation of the driver, which allows data exchange between Trace Mode and PLC SIMATIC S7-200. Let's open the program for creating a COM port configuration file, which comes with the basic version of Trace Mode 6 and is located in the folder where this SCADA system is installed (С:\Program Files\AdAstra ResearchGroup\Trace Mode IDE 6Base\Drivers_with_Setup\Siemens\PPI\ ). This directory contains the executable file and the actual configuration file. Run the executable file PPIconfig.exe (Figure 17).

Port configuration window

In the list of ports, each line consists of eight parameters:

1. COM port number. Redeclaring the same port will result in an error message when trying to save the configuration.

2. Data transfer rate (Baud Rate), from 300 bps to 115200 bps. For PPI network devices, the default is 9600 bps.

3. Number of data bits (Data Bits). The default is 8 bits.

4. Parity check (Parity), can be None, Odd or Even. The default for PPI network devices is Even.

5. Number of stop bits (Stop Bits): 1 or 2. Default 1 stop bit.

6. Timeout time for this serial port (in ms). The default is 1000ms;

7. Flow control. The converter used may require flow control. For its correct operation, it is necessary to correctly specify the signals (RTS, DTR) that will be given before each message and removed after it is sent.

8. Trace Mode address in the PPI network. According to the principles of data exchange in the PPI network, each device must have a unique address.

The specified parameters of the serial port must match the corresponding parameters of all other devices in this PPI network segment. Otherwise, the driver will not be able to communicate or the received data will not correspond to reality and may lead to unpredictable system failures.

To create a new record, click the "Add" button, the "Delete" button will delete the record, the "Edit" button or double-click on the list item will open the window for editing the record parameters (Figure 18).

The option "Keep an event log" provides the ability to conveniently debug the system. 2 files will be created along the specified path - PPImedia.log and PPIproto.log - in which the protocol of the driver operation and messages about failures and their possible causes will be saved, respectively. The specified directory must exist before starting Trace Mode. After successfully configuring the system, this option can be disabled, reducing the time and disk space costs.

So, the configuration file is created. Let's return to the Trace Mode development environment window. In the project navigator, select the "RTM_1" node of the "System" layer and launch the profiler by pressing the button. The runtime window will open. In this window, we see the graphical interface we created and the runtime control buttons: "Open", "Start\Stop" and "Full Screen".

Let's start our project by pressing the "Start\Stop" button or use the key combination Ctrl + R. If all the settings have been made correctly, then the screen form will correspond to that shown in Figure 19.

The final screen form of the project for data exchange between the PLC and Trace Mode

Switch the I0.0 toggle switch on the front panel and check the indication - changing the color of the light bulb from red to green. Click on the "Change MW2 value" button and in the window that appears, enter a new value, click "Finish". Verify that the value in the text box has changed. You can use this value in your PLC program, and depending on it, the controller will generate different control actions.

SCADA TRACE MODE(Adastra, Moscow) - This the most bought in Russia domestic software system for automation of technological processes ( APCS), telemechanics, dispatching, resource accounting (ASKUE, ASKUG) and building automation.

TRACE MODE works under Windows and linux, is used in more than 30 countries of the world, in 40 industries and has largest (53000 PCS.) number of installations in Russia.

A free tool SCADA system TRACE MODE on 64000 IO can be freely download with .

Benefits of SCADA TRACE MODE

SCADA TRACE MODE - unconditional technology leader– the main technologies used in SCADA for the first time applied in TRACE MODE.
SCADA TRACE MODE has the largest number of implementations in Russia.
The program includes built-in drivers for more than 2588 PLC and USO. All drivers are supplied immediately and for free. No need to buy an OPC server!
A single programming tool for controllers and operator workstations with project autobuilding technology.
Scalability 16 to 1,000,000 I/O points. Special working technologies with big projects.
Free instrumental system with unlimited time of use and with drivers for more than 2588 PLC and USO can be downloaded from the site. Download SCADA TRACE MODE .
System development tools telemechanics.
The most fast real time system.
The fastest DBMS RT (over 1,000,000 records per second).
high reliability. 100% reservation controllers, networks, interfaces, archives, workstations with shockless restart.
The biggest libraries finished components (more than 1000 pcs.).
Adaptive self-tuning of PID controllers based on the original Russian patented technology.
Does not use obsolete OPC and DCOM standards as internal interfaces.
The biggest free library educational films.
Made in Russia. Completely in Russian.

SCADA TRACE MODE was developed by AdAstra (Moscow), the only company in Russia 100% software company in the field of SCADA.

Basic and professional lines SCADA TRACE MODE

Any project developed in the basic version can be converted into a professional.

How to start working with TRACE MODE?

It's simple. Just download free baseline TRACE MODE instrumentation system with a set of ready-made drivers for more than 2588 PLC and USO. We recommend that you watch the tutorial videos on connecting controllers for beginners and connect to your PLC.

Users of the free version of SCADA TRACE MODE and ask questions to our engineers.

Work with peace of mind in the free baseline tool system - You don't have to buy more expensive execution modules - we convert a project developed in the free baseline version to a professional format when you purchase a professional tool system.

Attention!On the SCADA TRACE MODE YouTube channel You will find more 140 video lessons for mastering SCADA TRACE MODE.

Subscribe to the TRACE MODE channel on YouTube!

The article discusses the properties of SCADA Trace Mode 6, which simplify the development of APCS projects. Examples of building automation and ACS of the power unit are given.

Adastra Research Group, LTD., Moscow

Integrated SOFTLOGIC-SCADA-system Trace Mode 6 of the Russian company AdAstra Research Group, Ltd. For more than 15 years, it has been the best-selling software for process automation in Russia and the CIS. The unique combination of properties of the Trace Mode 6 system makes it the basis of modern process control systems for optimal process control.

The integrated platform for production control Trace Mode 6 consists of an Integrated Development Environment in which the creation of ACS projects and a set of executive modules that ensure the functioning of the system in real time. The integrated environment includes a full set of development tools for process automation systems (APCS), namely the tools for creating:

Operator interface (SCADA/HMI);

Distributed operator complexes;

Industrial real-time database;

Software for industrial controllers (SOFTLOGIC).

A huge advantage of the Trace Mode 6 software package is a large library of built-in drivers, which comes free of charge even with the basic version of the system. Support for a large number of equipment from both domestic and foreign manufacturers allows you to create highly reliable process control systems in a distributed architecture. An excellent example of this thesis is the ADCS of an Intel office building, which was developed on the basis of the Trace Mode 6 SCADA system by the specialists of the company “Protekt”, Nizhny Novgorod.

Rice. A feature that allows you to create both single and double reserves for a project node with one click of the mouse

The Intel office building automation system covers the following devices: chillers, dry coolers, refrigeration station, pump frequency converters, exhaust fans, central air conditioners, fan coil units.

At the hardware level of the system, the following equipment was used:

I/O modules by Advantech;

Temperature/humidity transducers from Sauter and S+S Regeltechnik;

Jola liquid leakage sensors and relays;

Electrical energy meters SET 4TM;

Temperature, humidity, pressure sensors, electric drives of control valves, as well as controllers in the refrigeration, ventilation and air conditioning system from York;

Frequency converters from Schneider Electric.

According to the reviews of the specialists of the company "Protekt": "The use of SOFTLOGIC-SCADA-system Trace Mode 6 with advanced support information exchange with equipment of various brands allowed us to comprehensively solve the issue of building an automated control system and ensured comfortable operation of the engineering systems of the building.”

Important role In ensuring the reliability of APCS, technical means play to prevent emergency situations and minimize losses from failures in the operation of APCS. These functions can be divided into several groups:

Protection against accidental errors at the stage of development of process control systems;

Timely failure diagnostics;

Hot redundancy of APCS components and assemblies;

Automatic recovery after failures;

Protection against unauthorized access and unskilled user actions - the so-called human factor.

From the list of these functions, the most important is the hot standby of components and nodes of industrial control systems. The redundancy of elements of the created APCS systems is dictated either by existing regulatory industry documents (for example, for objects potentially hazardous to environment and / or production personnel - Atomic industry, chemistry, military-industrial complex), or the nature of the flow of the technological process, the violation of which can lead to serious economic losses (electric power industry, metallurgy, etc.). Trace Mode 6 has a unique feature that allows you to create both single and double fallback for a project node with a single mouse click. Moreover, an identical node is created with the preservation of all internal and external links of channels with data sources. Trace Mode 6 is designed with all reliability requirements in mind and supports various types of hardware and software redundancy at all levels - from a single sensor to an enterprise-wide archive server.

Rice. Built-in driver library that comes free even with the basic version

The reliability and fault tolerance of an automation system depends on its hardware and software components, personnel discipline, security policy, etc. Ways to improve the reliability of automated control systems by means of hardware are more obvious and, as a rule, lead to a rise in the cost of the system. In the same time software affects the reliability of process control systems no less than sensors, controllers or servers. At the same time, the often high cost of a SCADA system does not guarantee the availability of the necessary fault tolerance and redundancy functions in it.

The solution of large-scale automation tasks in Trace Mode 6 is facilitated by unique technologies that improve developer productivity. Among them:

Integrated Development Environment;

Unified database of a distributed project;

Group editing;

Rich libraries of free drivers, algorithms and graphic objects;

Project autobuild.

One of the projects where Trace Mode technologies made it possible to implement a project of a highly reliable process control system in the shortest possible time (the beginning of designing is January 2007) was the process control system for the second power unit with a capacity of 215 MW at the Pskovskaya GRES (branch of OAO OGK-2). Already in August 2007, the system was successfully put into trial operation by the specialists of the Russian company CJSC PIK “ZEBRA” under the technical guidance of JSC “Engineering Center UES - Firma ORGRES” (Moscow). At the hardware level of the automated process control system, the PTK KRUIZ manufactured by CJSC PIK ZEBRA was used (Journal “ISUP” 2(14)_2007).

Work on the creation of automated process control systems was carried out as part of the second stage of automation of control and management systems for power units at the Pskovskaya GRES (Order of RAO UES of Russia dated September 18, 2002 No. 824). The first stage was completed in December 2004 with the commissioning of the automated process control system for the first power unit of the Pskovskaya GRES, also developed on the basis of the PTK KRUIZ and SCADA Trace Mode.

The objects of control and management of the automated process control system were the main and auxiliary equipment of power unit No. 2, as well as the general station heating equipment.

In addition to the APCS itself, the automation project for the second power unit of the Pskovskaya GRES (OGK 2) included the commissioning of a full-scale power unit simulator designed to effective learning and training of OGK personnel 2.

A fundamentally new approach to the automation of industrial facilities has become the creation of functional group control (FGU) programs that perform sets of typical technological operations, which makes work easier. operating personnel GRES.

CJSC PIK “ZEBRA” has long and successfully applied the technologies of integrated and group development of large-scale process control systems implemented in Trace Mode, which allows you to create projects using a single toolkit in a short time, and has the privileged status of an Authorized System Partner of AdAstra Research Group, Ltd.

Laboratory work number 2.

Creation of the operator interface and control model in the work environment TRACE MODE 6

Objective

Studying the principles of developing an operator interface and modeling a facility management system TRACE MODE 6 SCADA systems.

Tasks

Creating a project for a dynamic object control system using an integrated development system TRACE MODE 6, simulation of the operation of the control system using the real-time debug monitor.

Theoretical part

Project development in the TRACE MODE 6 integrated environment (IS) includes the following procedures:

creating a project structure in the navigator;
- configuration or development of structural components - for example, development of templates for graphic operator screens, development of program templates, description of sources / receivers, etc.;
- configuring information flows;
- selection of ACS hardware (computers, controllers, etc.);
- creating nodes in a layer System and their configuration;
- distribution of channels created in different layers of the structure, by nodes and configuration of interfaces for the interaction of components in information flows;
- saving the project into a single file for subsequent editing;
- export of nodes to file sets for subsequent launch under the control of TRACE MODE monitors.

The listed procedures (with the exception of the last two) and the operations included in them can be performed in any order. For example, you can start developing a project by developing templates for operator graphic screens, by creating nodes and their channels in the layer System (if the ACS hardware is known in advance), channels and information flows can be configured after channels are distributed among nodes, etc.

3.1. Classification of project structure objects.

3.1.1. Classification of components.

According to the functional purpose, the project components belong to one of the following types:

channels - components that determine the algorithm of the project. Channels can be created in different layers, but their final distribution over the nodes in the layer System mandatory - otherwise they will not be exported for RTM;
templates – components that can be called by channels with parameter transfer during real-time operation. The transfer of parameters is configured when developing a project in IS by binding template arguments to channels or sources / receivers;
sources/sinks– templates of exchange channels with various devices and applications. Devices here mean controllers, as well as external and internal modules/boards for various purposes, exchange with which is supported by TRACE MODE monitors (including through drivers). TRACE MODE system variables and built-in generators are also created in the IC as sources/sinks;
resource sets - sets of texts, images and video clips that can be used in the development of templates for graphic screens;
graphic objects- components that are general case several graphic elements (from those available in the data view editor) grouped into one. Graphical objects can be used in the development of templates for graphical screens;
serial ports– parameters of COM ports;
message dictionaries– sets of messages generated when various events occur;
terminals – these components describing electrical contacts (for example, installation cabinets) are elements of the electrical connection diagram of the automated control system.

3.1.2. Layer classification.

The predefined project structure layers have the following purpose:

Resources – to create custom sets of texts, images and video clips, as well as graphic objects;
Program Templates– to create program templates;
Screen Templates – to create templates for graphic screens, graphic panels and mnemonic diagrams;
Database Link Templates– to create database link templates;
Document Templates– to create document templates (reports);
Channel database – this layer is the repository of all project channels. You can perform operations with channels (including creating them) in different layers, but in all cases these operations are actually implemented in the Channel Base layer. In any other layer where a command is executed to perform an operation with a channel, its result is only displayed - therefore, there are commands for deleting and destroying channels;
System – for configuring nodes and their components (a node is created as the root group of this layer);
Sources/Destinations– to create built-in generators, templates for exchange channels with various devices and software applications, as well as to configure TRACE MODE 6 system variables,
Technology - to develop a project from technology (i.e. with a grouping of components based on their belonging to a technological object). In this layer, the channel encoding is built automatically with the inheritance of the encoding of all higher-level objects that the channel belongs to. When debugging a project, the Technology layer can play the role of a node - a command is defined for itSave Node for RTM. In addition, commands for interaction with the technological database are defined for this layer;
Topology - to develop a project from the topology (i.e. with a grouping of components by location);
I&C - to describe the electrical connections of the automated control system;
Component Libraries- to create libraries of objects - design solutions for individual tasks. This layer contains the predefined groups System and User.

3.1.3. Node classification.

Project nodes are created as root groups of the System layer. The predefined node name indicates the monitor family for which the node is intended. A node can contain only those components that are supported by the monitors of the corresponding family.

In general, nodes can run under different monitors.

Typically, a node runs on separate hardware. In the case of running two or more nodes on the same hardware, it must be equipped with the appropriate number of network cards.

Node parameters are set in the corresponding node parameter editor.

Node types:

RTM . The RTM node is designed to run on a computer controlled by executive modules of the RTM family (RTM) - monitors with support for displaying graphic operator screens, support for exchange over a serial interface and network with various equipment and performing recalculation of channels of all classes, except for T-FACTORY channels.
T-FACTORY . The T-FACTORY node is designed to run on a computer controlled by executive modules of the T-FACTORY family - monitors for solving APCS tasks.
MicroRTM . The MicroRTM node is designed to run on a computer or in a controller under the control of the Micro RTM family of executive modules. The main difference between these monitors and RTMs is the lack of support for displaying graphic screens.
logger . The Logger node is designed to run on a computer controlled by the Logger executive module (registrar) - a monitor capable of maintaining archives through the channels of all project nodes.
EmbeddedRTM . The EmbeddedRTM node is designed to run on a computer or in a controller under the control of executive modules of the Embedded RTM family - monitors with support for graphic panels, support for exchanging with equipment using various protocols and performing channel recalculation.
NanoRTM . The NanoRTM node is designed to run in a controller under the control of the Nano RTM executive module, a monitor similar to Micro RTM, but designed to work with a small number of channels.
Console . The Console node is designed to run on a computer controlled by executive modules, which, unlike RTM, do not recalculate channels intended for working with data. Consoles allow you to receive data from other nodes of the project over the network, display them on graphic screens and manage technological process from graphics. Consoles cannot interact with T-FACTORY nodes.
TFactory_Console . The TFactory_Console node is designed to run on a computer running execution modules similar to consoles, but, in addition, capable of interacting with T-FACTORY nodes.
EmbeddedConsole . This node runs on monitors that only support graphical panels.

3.2. The principle of operation of the monitor. TRACE MODE 6 channel.

At startup, the monitor reads the node parameters set during the project development in the IS, as well as the parameters of other nodes for correct interaction with them.

The operation algorithm of any TRACE MODE monitor consists in the analysis of channels - structures of variables created both during project development in IS and in real time. Depending on the class and configuration of the channel, based on the results of its analysis, the monitor performs one or another operation - writing the values of the channel variables to the archive, requesting the value of the data source via the specified interface and writing this value to the channel, calling the operator's graphic screen on the display, etc. .

In the general case, writing a value to a channel means assigning a value to a variable (attribute)Input value this channel.

There are two important properties that can be configured for a channel − Communication and Challenge.

The first property means the channel's ability to receive data from sources and transmit data to receivers - in other words, using this property, you can configure the information flows of the automated control system.

The second property means the channel's ability to call (implement) a template with the necessary parameters passed to it (for a channel of the CALL class, the call property has extended functions). Based on the property, the call is implemented, for example, a graphical operator interface, exchange with the database, etc.

The set of channels of a node is called the channel base of this node.

The class of a channel defines its general purpose. For example, a channel of the FLOAT class is intended for operations with 4-byte real numbers, a channel of the class Unit of equipment is for accounting for a unit of equipment, planning and monitoring its maintenance. When developing a project, only channels of predefined classes can be created.

The variables included in a channel are called its attributes. Channel attributes have different purposes and different data types. Boolean attributes and attributes that can only take two specified values are called flags. An example of a flag is a channel type that takes two values - INPUT (numeric channels of the INPUT type are intended to receive data from sources) and OUTPUT (numeric channels of the OUTPUT type are intended to transmit their value to receivers). The attributes that are used to pass values when calling the template are called channel arguments. Attributes are provided with numerical indexes (attribute indexing starts from 0, argument indexing starts from 1000). Attributes have a full name and a short name (mnemonic notation). Attribute identifiers are its index and, in some cases, a short name.

Channels contain predefined algorithms (some of them can be configured by the user), according to which some channel attributes are set or calculated by the monitor depending on the state or value of other attributes. For example, for most channels in the attribute Change time monitor records attribute change timeThe real value of the channel(based on the clock of the device running the monitor).

The execution of the channel's internal algorithms and the analysis of its attributes by the monitor is called channel recalculation.

Based on the results of the attribute analysis, the monitor performs the actions specified using the channel (for example, calling a template), this procedure is called channel processing. The processing of the channel after its recalculation is performed under certain conditions. When recalculating the channel base, the recalculation of a specific channel is also performed under certain conditions.

Channels of the same class have an identical set of attributes and predefined processing algorithms. There are also attributes that all channels have, regardless of their class (such attributes have the same index in all channels).

A channel is a structure consisting of a set of variables and procedures that has settings for external data, identifiers, and a recalculation period for its variables. Channel identifiers are: name, comment and encoding. For example, the name of the channel associated with the fifth channel of the analog input card located in the first seat controller will be AI_-pe01-0005. In addition, each channel has a numeric identifier used internally to refer to that channel. There are four main values among channel variables: input (In), hardware (A), real (R) and output (Q). With the help of settings, the input value of the channel is associated with the data source, and the output value is associated with the receiver.

Depending on the direction of information movement, i.e. from external sources (data from controllers, interrogators or system variables) to a channel or vice versa, channels are divided into:

input (INPUT type) (Fig. 2.1),
output (type OUTPUT) (Fig. 2.2).

Rice. 2.1. Channel type INPUT

The input channel (Fig. 1.2) requests data from an external source (controller, another RTM, etc.) or the value of system variables (error counter, archive length, etc.). The resulting value is fed to the channel input and then converted into hardware and real values. The hardware value of channels of the INPUT type is formed by scaling (logical processing for discrete channels) of the input values. The procedures used provide primary data processing (correction of sensor errors, scaling, temperature correction of cold junctions of thermocouples, etc.). Output values are not used in INPUT type channels.

Rice. 2.2. Channel type OUTPUT

The output channel (Fig. 2.2) transmits data to the receiver. The receiver can be external (the value of a variable in the controller, in another RTM, etc.) or internal - one of the system variables (the number of the sound file being played, the number of the screen displayed on the monitor, etc.). Both external and internal data sinks are associated with the output values of the channels. For channels of the OUTPUT type, their input value is formed in one of the following ways:

the procedure for managing this channel;
procedures for managing or broadcasting other channels;
metaprogram in Techno IL language;
remote node channel (for example, over a network);
operator using control graphic forms.

For channels of type OUTPUT, the hardware value is obtained from the actual translation procedure. The hardware values of the channels have such a name, since it is convenient to obtain the values of unified signals with which the input / output equipment works (4-20 mA, 0-10 V, etc.). Real values are intended to store the values of controlled parameters or control signals in real units (for example, kg/h, about C, %, etc.). The output value is only defined for channels of type OUTPUT. It is calculated from the hardware value.

Data from external devices is written to channels, data from channels is sent to external devices. The operator enters control signals into the channels. Values from channels are written to archives, operator reports, etc. Channels perform data transformation. By changing the values on the system channels, you can control the information displayed on the screen, sound signals, etc., i.e. the whole system.

The input value of the channel is converted into hardware, real and output using procedures. The channel procedures are:

scaling (multiply and offset),
filtering (peak suppression, aperture and smoothing),
logical processing (preset, inversion, compatibility control),
translation (calling an external program),
control (call of an external program).

The order of the sequence and the content of the procedures may vary depending on the type of channel (input or output, analog or discrete). The set of procedures in a channel depends on the data format. Analog variable channels use the following procedures:scaling, translation , filtering and control . Channels that process discrete parameters uselogical processing, broadcast and control .

Procedure scalingonly used on channels that work with analog variables. It includes two operations: multiplication and shift . The sequence of these operations varies depending on the channel type:

for INPUT channelsthe input value is multiplied by the given multiplier and the offset value is added to the result. The result is assigned to the hardware value of the channel;
for channels of the OUTPUT typethe offset value is added to the hardware value, then this sum is multiplied by the specified multiplier, and the result is assigned to the output value of the channel.

Broadcast procedure defined for all channels, regardless of their type and type of presentation. For input channels, the translation procedure transforms hardware value to real and vice versa for weekends. To do this, the program is called. The called program is selected when setting up the procedure.

When setting up the procedure, the input and output arguments of the selected program are associated with the attributes of the current channel, as well as any other channels from the current database. Therefore, the translation procedure of one channel can also be used to generate the values of other channels.

An example of using the translation procedure is the integration of sensor readings.

Filtration – a procedure that is present only for analog channels. The set of operations it performs differs for input and output channels. For INPUT channelsfiltering is performed after the translation procedure until the real value is formed. Filtering includes the following operations:

suppression of random bursts in the measurement path;
scale control - tracking the output of the real value of the channel beyond established boundaries scales.

For channels of type OUTPUTthis procedure generates a real value from the input value. In this case, the following operations are performed:

limiting the rate of change of the real value;
suppression of small fluctuations in the channel value;
exponential smoothing;
scale control – cutting the value of the control action to the limits of the channel scale.

Control – a procedure that is defined for all channels. It implements the control function. With its help, you can call a program in which you can program the required control algorithms. Values and attributes of any channels from the current database can be passed as arguments to the program. These arguments can be either input or generated. Formally, the control procedure is associated with the channel only by the recalculation cycle. It may not participate in the formation of its values at all, but manage other channels. This situation is often observed when using the procedure Control on INPUT channels.

The monitor is a multi-threaded process. Thread priorities are set by default, but you can change them. The main thread that runs cyclically is the thread CALC . Each cycle of this flow includes the following sequential steps:

sequential analysis of all enabled channels of the node (in ascending order of ID) and setting the SV flag (not available to the user) to channels that require recalculation;
recalculation of all channels (except CALL channels) of the INPUT type, which should be recalculated in the main stream, and, in some cases, processing of these channels;
reset the SV flag;
recalculation and processing of channels of the CALL class of the main stream;
recalculation of channels of the OUTPUT type, which should be recalculated in the main stream, and analysis of their output value. Set the Q flag to channels whose output value has changed.

An SV flag not cleared in the main stream is a sign of the need to recalculate the channel in the corresponding stream.

The CALC cycle time (the time allowed for the tasks of the main thread to execute once) is configured using two parameters that are set in the section Basic tab recalculation node editor. Parameter Permission sets the resolution of the timer in seconds (value tick ), Period parameter – recalculation period in units tick. The product of these parameters determines the CALC cycle time in seconds.

Timer resolution ( tick ) can vary within the following limits:

in MS Windows - not less than 0.01c;
in MS Windows CE - at least 0.001s.

The default timer resolution is 0.055 s, period is 10.

3.3 Development of a graphical interface.

TRACE MODE 6 provides a graphical representation of the progress of the process, as well as process control using graphical tools.

The graphical operator interface is implemented in several forms:

in the form of a set of graphic screens, the templates of which are developed in the data representation editor (RPD), for nodes that are executed by monitors on hardware that have sufficient performance and other necessary characteristics (for example, when using volumetric graphics, the video system requires support for OpenGL 1.1);
in the form of a set of graphic panels, the templates of which are developed in the eRPD (modification of the RPD), for nodes that are executed by monitors on hardware with limited performance (for example, in controllers with Windows CE OS).

The project structure created in the channel database editor is loaded into the RPD (eRPD). By selecting the required project node, you can edit its graphic base. This base includes all graphic fragments that are displayed on the monitor of this operator station.

RPD and eRPD contain a large number of built-in graphic elements (respectively, the GE and the USE), which allow you to depict almost any technical process, display all the necessary information about the progress of its implementation, and also manage the technical process. In addition, TRACE MODE 6 includes a large number of resources - texts, images, video clips, various graphic objects - that can be used in the development of the operator's graphical interface. Resources can be created by the user.

The totality of all screens for data presentation and supervisory control included in the graphic bases of the project nodes make up its graphical part. Screens in the graphic bases of project nodes are divided into groups. Each group has its own name. Grouping screens is convenient to use based on their functional purpose. For example, mnemonic diagrams can be collected in one group, controller settings screens in another, overview screens in a third, etc. Only one screen can be displayed on the monitor at a time, each of them is a fixed-size graphic space on which a static picture and display forms are placed. It has its own name and set of attributes (settings). These attributes include: Size, Background color, Wallpaper, Permissions, Specification of the alarm report viewing window.

The development of graphic screens is carried out by placing graphic elements on them. Distinguish between static and dynamic elements. Static elements do not depend on the values of controlled parameters, and no actions are attached to them to control the information displayed on the screen. These elements are used to develop the static part of the graphic screens, for example, to display containers being filled, boilers, motors, etc. Therefore, they are called drawing elements.

Dynamic elements are called display forms. These elements are associated with channel attributes to display their values on the screen. In addition, some of the display forms are used to control channel attribute values or display information. Some forms may also combine both functions.

On the screens, you can place complexes of static and dynamic elements designed as graphic objects used for replication ready-made solutions in the operator interface creation area.Graphic objectis a set of display forms and drawing elements, which is designed as a single graphic element. Typical graphical fragments designed as objects can be inserted into screens of graphic bases of any projects.

There are two types of graphical objects: "Object" and "Block". The first one can refer to 256 channels, while the second can only refer to one.

To create and edit objects, the same windows are used as when working with screens. Developing objects is identical to the process of developing a screen. The difference lies only in setting the display forms for channels. In an object, the display forms are associated with its internal channels. These channels, when placing an object on the screen, are tuned to the real channels of the node being edited.

TRACE MODE allows you to perform a number of operations with graphic objects: copying, saving and pasting into other projects or graphic databases of the same project, output to separate windows on other screens, etc.

Graphics libraries are used to store graphic objects. Each library has a name and a list of objects included in it. In order to use the created library in the future, it must be saved in a file. To gain access to a previously saved library, you must load it into the data view editor.

3.4. Algorithm programming.

Any automated control system requires mathematical data processing - as in measuringinformation flows (sensor => USO => controller => operator station), and in control (operator station => controller => actuating device).

TRACE MODE 6 provides the following tools for mathematical data processing:

internal algorithms of numerical channels;
programs. For the development of programs in IS built-in languages Techno ST, Techno SFC, Techno FBD, Techno LD and Techno IL , which are modifications of the ST (Structured Text), SFC (Sequential Function Chart), FBD (Function Block Diagram), LD (Ladder Diagram) and IL (Instruction List) languages of the IEC61131-3 standard. Programs developed in IS allow using functions from external libraries (DLL).

These tools provide the possibility of mathematical data processing in any link of the information flow.

Programs and some of their components (functions, SFC steps and transitions, etc.) can be developed in any of the built-in languages in an appropriate editor, and the languages for the program and its components are selected independently.

To create and edit the properties of arguments, variables, functions and structural types of the program, as well as to use functions from external libraries in the program, special table editors are built into the project's integrated development environment.

TRACE MODE 6 also has tools for debugging programs.

The main programming language of TRACE MODE 6 is Techno ST. Programs developed in Techno LD, Techno SFC and Techno FBD are translated into Techno ST before compilation. IL programs are partially translated into ST before compilation, and partially into assembler. It follows, for example, that the keywords Techno ST are the same for all other languages.

The program can only be used after it has been successfully compiled. To compile a program, do one of the following:

run command Compile from the Program menu (or press the F7 key or press the LK on the icon Compilation (F7) debugger toolbar) - this command creates only code for debugging the program in the IS. The debug code is stored in a subdirectory created under the %TRACE MODE 6 IDE%\tmp directory. If the compiler finds errors, it displays the corresponding messages in a window, which in this case opens automatically. If the compilation was successful, the message box does not open;
execute project export – this command creates both debug and executable code in the folder of the node containing the program call channel. If errors are found in the program, a message is displayed stating that it cannot be exported.

To execute a program in real time, a CALL class channel with the Program call type must be created in the node and configured to call the program template.

A similar CALL channel of the INPUT type is processed with its own recalculation period in the corresponding stream.

A similar CALL channel of the OUTPUT type is processed, in particular, when using the control function Run graphic element.

Description of the software systems used

The TRACE MODE 6 tool system is launched by double-clicking the left mouse button (LC) on the Windows desktop icon or from the Start/All Programs/ Trace Mode 6/ TRACE MODE IDE 6".

The end result of the work of the TRACE MODE 6 instrumental system is a set of files intended for the execution of ACS tasks in real-time monitors on workstations and in controllers. In the laboratory work, a profiler with support for graphic screens will be used as an RTM for the workstation. rtc.exe , located in the directory of the TRACE MODE 6 tool system. The profiler allows you to run one node of the developed project on a computer with the tool system installed.

The IC shell has a main menu that includes the menu File , View , Windows and Help , and the toolbar.

Editors built into IS have their own menus and toolbars, which, when these editors are opened, are partially or completely added to those available in IS. When opening the editor, it is also possible to modify the list of IS menu commands.

If multiple editors are open, the toolbars and IS menus correspond to the editor whose window is currently active.

The IC shell menu and toolbar are available in all cases.

The tools of all editors and IP windows are provided with tooltips.

To set the general settings of the IS and template editors, a dialog is intended that opens by the command IS Settings File menu.

Saving a project for editing is done by command Save (Ctrl - S ) or Save As (Ctrl - Shift - S ) from the File menu . The project is saved in a binary file with the prj extension for further editing in the IS. When these commands are executed, the custom component libraries are saved to the tmdevenv.tmul file (in the IS directory). The IS provides for the backup of the previous version of the prj and tmul files - when the command is repeated Save the extensions of previously saved files are changed to ~prj and ~tmul respectively.

Saving a project for launch is done by commandSave for MRV File menu or by pressing a similar button on the IS toolbar. All nodes are exported to file sets for their subsequent copying to hardware, on which they must be executed under the control of TRACE MODE monitors. Before exporting nodes, the project must be saved to a prj file.

When executing the commandSave for MRVa subdirectory is created in the directory containing the prj file<имя файла prj без расширения>, in which a folder with a set of files is created for each node. The node folder has the name specified for the node when it was configured in the IS (with spaces replaced with "_" characters). Files of nodes having the same names in the IS are exported to one folder.

Necessary condition export of a node is the presence of at least one channel in it.

On command Save Node for RTM from the Project menu or the context menu of the navigator, the selected node is exported to an arbitrary folder, while the second export does not create backup copies of the node.

Security measures

During the laboratory work it is necessary:

observe the rules for switching on and off computer science;
do not connect cables, connectors and other equipment to the computer yu teru;
when the mains voltage is on, do not disconnect, connect or touch the cables connecting various devices to m pewter;
in the event of a malfunction in the operation of the equipment or a violation of safety regulations, inform the supervisor about laboratory worker;
do not try to fix malfunctions in the operation of the equipment on your own;
Tidy up your workspace when you're done.

ATTENTION! When working at a computer, you need to m thread: life-threatening voltage is connected to each workplace. Therefore, during work, you must be extremely careful and comply with all safety requirements. oh sti!

Exercise

6.1. Create an operator interface for a control system containing one AWS node, a control object model, a PID controller, a comparison element for implementing negative feedback, elements for setting the setpoint and parameters of the PID controller, as well as elements for displaying values using various operator interface and graphical tools elements.

6.2. Include a program in the system in the language FBD to implement a dynamic model of the control system.

6.3. Realize the functioning of the control system in real time, remove the transient response of the control object as a reaction to a step change in the setpoint.

6.4. Variants of tasks for the parameters of the control object are given in Table 1.

Table 1. Variants of tasks for the parameters of the control object

Variant number	Transfer ratio K	Time constant T	Delay N	SNS interference
				addition to the output signal of a random value in the range from 0 to 1%
				formation of a peak with a value of 25% of the output value with a probability of 0.01
				random increase in gain in the range from 0 to 2%
				random increase in time constant in the range from 0 to 2%
				random change by 1 lag
				adding a sinusoidal signal with an amplitude of 2% of the output value to the output

Methodology for completing the task

7.1. To fulfill clause 6.1. do the following tasks.

7.1.1. Create a new standard project.

7.1.2. Study the help section QUICK START - PART TWO - Creating workstation screens.

7.1.3. In the Resources layer, create a Pictures group. In this group, create an Image_Library component and import several textures into it.

7.1.4. In the Resources layer, create a Graphic_Elements group. In this group, create a Graphic_object. Using the available graphic tools, create a conditional image of the control object, consisting of at least two three-dimensional figures with a superimposed texture.

7.1.5. In the System layer, create a node RTM , in which to create the Screen component. Place the graphical elements of the operator interface on the screen:

elements for entering values and displaying setpoint values,
regulator picture,
control object image,
communication lines between them
elements for entering values and displaying values of controller parameters,
elements for displaying control values and output coordinates of the object in numerical form and in the form of graphs.

Create the necessary arguments and auto-build channels based on them. Refer to the help section QUICK START - PART ONE.

7.2. To complete paragraph 6.2 of the task, do the following.

7.2.1. In the RTM node create the Program component and set the programming language for it FBD.

7.2.2. Explore the help topic Programming Algorithms - Editing FBD -programs. Read the description FBD -blocks. Explore blocks PID and OBJ (Section "Regulation").

7.2.3. Using Subtraction blocks, PID, OBJ , make a model of the control system. Create the necessary program arguments, bind them to channels. Perform binding of input and output signals of the blocks. For block OBJ control object parameters - transmission coefficient, time constant, delay - set as constants in accordance with the task option. For block noise parameter OBJ use the constant 0.

7.3. To complete paragraph 6.3 of the task, do the following.

7.3.1. Connect the blocks according to the "setpoint - control object" scheme (without a regulator and without feedback).

7.3.2. Compile the program and correct if there are errors. Start project execution using RTM.

7.3.3. Enter a non-zero setpoint value and obtain the transient response of the control object. Take a screenshot of the transient response.

Requirements for the content and design of the report

The lab report should contain:

brief theoretical information;
formulation of tasks for laboratory work;
description of the work sequence;
images of working windows obtained as a result of modeling the system operation;
conclusions from the laboratory work.

test questions

9.1. What opportunities does SCADA-system Trace Mode to create an operator interface?

9.2. What are the main types of resources that can be used to create an operator interface in the system trace mode?

9.3. What is a programming language FBD?

9.4. What are the main blocks from the composition FBD can be used to model control systems?

9.5. What parameters should be set for the control object model?

9.6. What parameters should be set for the PID controller model?

9.7. How is the system launched in real time?

Criteria for assessing the performance of laboratory work

Laboratory work is considered completed if:

the student completed all tasks in accordance with the n noy method;
the results of the work, presented in the form of a report e that correspond to the requirements presented to them;
student answered correctly test questions and can interpret the results.

Literature

Analog (FLOAT)

Source

move

Scaling

Hardware

Broadcast

Filtration

Real

Control

Real

Broadcast

Hardware

Logic Processing

Entrance

Source

Discrete (HEX)

Real

Broadcast

Hardware

Logic Processing

Output

Receiver

Discrete (HEX)

Control

Entrance

Filtration

Real

Broadcast

Hardware

Scaling

Output

Analog (FLOAT)

Control

Entrance

It might be useful to read: