Trace mode 6 description. SCADA TRACE MODE. Download SCADA system. Communication Configuration Window

If you are the legal owner of Trace Mode and have registered your version on the website http://www.adastra.ru/, then from time to time you receive a newsletter with campaign news.

Among other things, invitations are received to participate in the SCADA championship. Usually I ignored these invitations, but this time I decided to take part. Just for the sake of interest in the process of holding the event and the level of tasks. Moreover, you don’t need to go anywhere - the first 2 rounds of the championship are held online. And if you are lucky enough to reach the finals, all expenses for the trip to Moscow will be paid by Adastra.

Let's imagine a project in TM, the screen of which displays a single value - the reading from the sensor. For example, air temperature. The value is given with one decimal place: 15.6 ºC, 33.8 ºC, -0.7 ºC, etc.
And then, at one fine moment, you see the value -0.0 ºC on the screen...

The essence of the problem.
We all know that zero is never negative. It can't be positive either. Zero is an unsigned number.
Therefore, displaying the value -0 or -0.0 or -0.00 on the screen is a sign of unprofessionalism, if not stupidity:

In TM 6.08 you can round the Real channel value Float (Attribute R, 0) in 2 ways:

1. In the “Text” GE (which is tied to the real value of the channel), set the formatting to C format. For example, “%.1f” - output the value with 1 decimal place, “%.2f” - output the value with 2 decimal places, etc.

But in this case the value is rounded only when displayed. This means that R will not be rounded.
For example, R = 0.087 with formatting = "%.1f" on the "Text" GE will be displayed as 0.1

I found a problem with the built-in OPC server TraceMode 6.08. Well, how I found it... I wasn’t looking for problems, she found me herself:

According to the project, a USB/RS485 signal converter (hereinafter referred to as P) is used to access the Adam 4017+ and 4055 modules. The converter model is not important - they all behave the same.

Problem:
1. If, when starting the program P already connected to the computer, data is displayed, reliability = 0. Data from the calibrator to the analog input module is received with some noise - the value of the analog signal floats +-0.004 mA, which is quite normal. Thanks to this, it is clear that the reception is progressing:

I admit, my friends, I’m already sick of the leader of SCADA systems in Russia - TraceMode 6.

Now let's talk about trends in TraceMode. A trend is a graph on which channels are displayed as curves.

In TM6 the trends are in complete order - they exist. The trend has a lot of options and settings and most of them even work.

Except for one, but very important:

Epigraph:

If you have a glitch in your program, do not rush to fix it.

Just describe it in the manual as a feature of the work.

It was this expression that came to mind when I discovered the LocalList channel in TraceMode 6.08. True, some of the “operating features” of the channel are neither described in the printed programmer’s manual nor in the TM6 help. Thanks to the guys from technical support - they suggested it, I wouldn’t have thought of it myself...

I've been writing for quite some time now new project on TraceMode 6.
Because This is my first experience of creating a project on TM6, quite predictably I encountered many problems and ambiguities. As always, you find the most mysterious things in new systems being mastered where you least expect them.

Integrated SOFTLOGIC-SCADA/HMI-MES-EAM-HRM system TRACE MODE® 6 created in order to facilitate the work of process control and process control systems developers, therefore it includes proprietary technologies for automating project development, united by a common name - auto-building.

Autobuilding® is a set of automatic procedures for the formation of various elements of the process control system project. Automatic construction relieves the process control system developer from the most routine work, reduces project development time, and reduces the likelihood of introducing errors that occur during manual operations.

It can be said that autobuilding is the automation of automation.

The use of auto-building does not exclude the possibility of manual binding; it is a kind of macro tool that works for a person, but under his full control. Auto-building does not leave anything behind the scenes; the results of auto-building can always be viewed and, if necessary, canceled or adjusted.

There are several main types of auto-building:

• Automatic construction of data sources for programmable logic controllers (PLC) and object communication devices (OCD) according to a known configuration;
• Automatic construction of TRACE MODE channels based on data sources;
• Auto-building and auto-binding of channels from the argument editor;
• Automatic construction of connections ;
• Automatic construction of connections server-server;
• Auto-building based on library objects;
• Auto-building SQL queries;
• Auto-building connections with the OPC server;
• Import/export of channel database via ODBC.

Auto-building data sources implemented directly in the project editor. By selecting the type of controller (PLC) and its configuration in the context menu system, the process control system developer creates a description of the structure of the hardware part of the project. In this case, exactly as many I/O signals will be automatically built as actually exist for the selected configuration of a given controller type. The auto-construction of data sources for distributed devices and input/output cards installed in industrial computers is similarly implemented.

Automatic construction of TRACE MODE channels based on data sources usually used immediately after auto-building the sources themselves. This type of auto-building is implemented by simple drag-and-drop (using the Drag and Drop) icons of the data source into the node of the associated real-time monitor (main TRACE MODE server) or SOFTLOGIC controller controlled by Micro RTM. Auto-built channels based on data sources are ready for use. In fact, to create a simple human-machine interface (HMI) of an information system, all that remains is to configure the communication ports of the node and create a mnemonic diagram.

There is another way to auto-build a project for development “from graphics”. If a developer wants to first draw HMI mnemonic diagrams, and only then select the necessary equipment, then he will find it useful auto-building channels from the argument editor.

In the TRACE MODE® 6 SCADA system, all data between channels, screens, programs and other components is transmitted through arguments. This allows you to use the same component multiple times. For example, if 40 boiler houses of the same type are being automated in a project, then there is no need to edit 40 mnemonic diagrams separately. It is enough to create one screen and 40 calls this screen. Each call is assigned to specific channels via dialing screen template arguments. To avoid the tedious manual binding of channels to the arguments of each of the 40 calls, the process control system developer can use the procedure for auto-building and auto-binding channels from the screen call argument editor. When executed, for each argument in the selected TRACE MODE node, a channel of the appropriate type will be created with a name that matches the name of the argument.

In this case, the development of a project “from graphics” is completed by linking channels auto-built based on arguments to data sources. Similarly, you can start development by programming algorithms in the languages ​​of the IEC 61131-3 standard; auto-building based on program template arguments is performed in exactly the same way, so in the example discussed above, it makes sense to use the same set of screen and program arguments for a typical boiler room.

However, using only the three types of auto-construction described above, it will not be possible to completely avoid routine operations of the same type. In any case, separately for each boiler room you will have to resort to all the auto-construction procedures used. The conclusion suggests itself: a unified mechanism is needed to fully describe all aspects of one automation object, including data sources, an algorithm, and a mnemonic diagram. And this mechanism is in the SCADA system TRACE MODE® 6 exists. It is implemented in the form custom object libraries. Each user object is similar in structure to a separate TRACE MODE project; it includes data sources, a channel database, programs, screens and other components. Having described one “Boiler room” object, the developer can create 40 of its instances and be sure that all information connections in each boiler room are correctly created according to the object model; all that remains is to edit it using the group editing individual controller number for each boiler room and create an overview screen.

All these auto-construction methods, together with object libraries, form a comprehensive set of tools for quickly creating a single-node SCADA project of the TRACE MODE system, i.e. when there is only one server in the process control system. And what about the construction of distributed computing systems, large process control systems and process control systems of the enterprise scale?

Of course, for large distributed projects, the need to automate the process of developing process control systems is even higher than in the case of small systems. They come to help auto-building connections SOFTLOGIC controller - server And auto-building connections server-server . Both of these types of autobuilding are used to create connections between components of different project nodes, while there is no difference between the connection with the SOFTLOGIC controller and the connection with the server. Therefore, we can talk about a single mechanism .

TRACE MODE® compares favorably with other SCADA systems due to its unified project information space. This means that the program, for example, can be called in the controller, and the arguments for it are taken directly from the operator station. Or, conversely, the operator station's mimic diagram takes data directly from the controller. That is, to create a connection in a distributed process control system, it is not necessary to create extra channels. Bindings are carried out directly, bypassing intermediate links of information transfer. In fact, intermediate links certainly exist, but they are created, bound, unlinked and deleted automatically. This is the basis auto-building connections of a distributed project.

In addition, if the developer still wants to transfer data between nodes explicitly, then he can simply drag a group of channels from the source node to the receiver node using the Drag-n-Drop method, and new channels will be automatically built and linked in the receiver node , receiving information over the network from the source node. This method is justified if, for example, these channels must be archived at the receiving node or need to be provided with access from other applications via OPC or DDE.

Auto-building based on library objects allows replicate ready-made project components, including nodes, algorithms and graphic screens.

Other types of autobuilding are used to simplify setting up links with external DBMS and other applications.

For integration with external DBMS, the TRACE MODE® 6 SCADA system has built-in support for the SQL query language. SQL queries are created and edited in a special editor of the instrumental system. In addition to manual editing and interactive debugging capabilities, this editor provides SQL Query Auto-Build Wizard. It allows you to connect to a real database and create an SQL query simply by selecting the query type, tables and data fields with the mouse, and if necessary - additional conditions samples.

The OPC interface, developed since 1996 by the independent organization OPC Foundation, is becoming a popular standard for information exchange in the field of process control systems. TRACE MODE® 6 can perform both client and server OPC functions. The OPC TRACE MODE 6 server is created in the same way as a new node in the project tree, the same procedure applies to it auto-building connections of a distributed project using the Drag-n-Drop method, no additional effort is required from the developer.

Binding of OPC tags in TRACE MODE® 6 SCADA system can be easily automated using auto-building connections with the OPC server. This type of auto-build allows you to create a data source for each OPC tag of the selected OPC server. Unnecessary sources can be easily removed from the project. A universal procedure for auto-building channels by data sources can be applied to created OPC data sources.

Import and export of project channel database via ODBC can be used to use alternative project development tools. The most obvious example here is the use of MS Access or MS Excel to edit the SCADA channel database of the TRACE MODE® 6 system. Import and export of the channel database via ODBC is flexibly configured for a specific task, and the use of signal encodings in the KKS standard allows you to export and import not only simple tables, but also tree structures of technological objects.

The integrated development environment SOFTLOGIC-SCADA/HMI-MES-EAM-HRM of the TRACE MODE® 6 system is equipped with all the necessary functions for auto-building a process control system project. The most routine operations that tire the developer, take up his time and effort, and often provoke ridiculous errors, are successfully automated in the TRACE MODE® 6 SCADA system.

The combination of advanced auto-building® and powerful debugging tools makes the TRACE MODE® 6 SCADA system a benchmark for the reliability of modern process control systems development tools.

During 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 instructions of the teacher. Let's move on directly to creating the TRACE MODE project.

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

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

Integrated development environment TRACE MODE 6

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

To solve our problem, only two layers will be enough - “System” and “Sources/Receivers”. In the “System” layer, the “RTM” (Real Time Machine) node has already been created, 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 up a context menu in which we will go to the “Create group\PLC” path (Figure 3.). A folder named “PLC_1” will appear in this layer. You need to right-click on this folder and create the group “Siemens_PPI_Group” (Figure 4).

Creating a group in the “Sources/Sinks” layer

Creating a group "Siemens_PPI_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” - to write 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.

Components of the Siemens_PPI_Group

Double-click on the “Siemens_PPI_MW2_R” component to open its properties window (Figure 6).

Properties window for the component “Siemens_PPI_MW1_R”

Fill in the fields as follows:

• name: Siemens_PPI_MW2_R;
• port: 0 (“0” corresponds to COM1, “1” corresponds to COM2, etc.);
• address: 2 (PLC address on the PPI network);
• offset: 0x2 (to read MW2 address);
• area: Markers(WORD);

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

• 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 into the Trace Mode environment).

Next, we will create the corresponding channels for the components. To do this, open an additional navigator window (Figure 7).

Automatic channel creation

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

Double-click to open the “Screen#1:1” component, which belongs to the “RTM_1” node of the “System” layer. There is a rich graphics toolbar to choose from, including control elements, various types of lines and geometric shapes, as well as trends, charts and dial gauges.

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 the "Text" type. To do this, click on the toolbar icon, 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 a 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 SIMATIC S7-200 PLC”. Using the appropriate fields, we will change the color and font of the text, as well as the color of the outline and fill (Figure 9).

Graphic element properties window

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

Screen Arguments Window

Next, we will bind the 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 this, the properties window of the graphic element automatically opens, where in the “Text” column “Indication type - Value” and “Binding - name of the corresponding argument” appear (Figure 11).

Bind 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 the properties window of the graphic element and go to the “Events” tab (Figure 12). It is possible to set the system's reaction to two types of events - clicking the mouse on a graphic element and releasing it. Select pressing, right-click on “MousePress” and select “Pass Value” in the context menu that appears.

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

“Events” tab of the graphic element properties window

Call up the properties menu of the graphic object “Light Bulb” by double-clicking the left mouse button on this object. Let's fill in the values ​​as follows (Figure 13): binding:<2>ARG_002; type of indication: Arg = Const; inversion: True; constant: 256.

Properties window for the graphic element “Light Bulb”

At the initial moment the light is off (red). When the binding value is equal to the constant value, the light will light up (turn green). Applying a signal to the I0.0 controller input 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 “Sources\Receivers” layer. To do this, in the project navigator, go to the “System” layer, node “RTM_1”, “Screen#1:1”. Right-click on the “Screen#1:1” component and select “Properties” from 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 “Binding” column opposite the corresponding argument to open the connection configuration window (Figure 5.16). In this window, for the first and third arguments, select the corresponding 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 choice made, you need to click the “Binding” button. Save the created project: “File\Save”. Let's return to the "Project Navigator" window, which can be called up from the main "View" menu. Select the “RTM_1” node of the “System” layer and click the “Save for RTM” button in 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 (C:\Program Files\AdAstra ResearchGroup\Trace Mode IDE 6Base\Drivers_with_Setup\Siemens\PPI\ ). This directory contains the executable file and the configuration file itself. Let's launch 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. Re-declaring the same port will result in an error message when attempting 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. The default is 8 bits.

4. Transmission parity (Parity), can take the values ​​None, Odd or Even. The default PPI for network devices is Even.

5. Number of stop bits: 1 or 2. Default is 1 stop bit.

6. Timeout time for this serial port (in ms). Default - 1000 ms;

7. Flow control. The converter used may require flow control. For it to work correctly, you must correctly specify the signals (RTS, DTR) that will be sent before each parcel and removed after it is sent.

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

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

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

The “Keep an event log” option provides the ability to conveniently debug the system. Along the specified path, 2 files will be created - PPImedia.log and PPIproto.log - in which the driver operation log and failure messages and their possible reasons. The specified directory must already exist before Trace Mode is launched. After successfully configuring the system, this option can be disabled, reducing the cost of time and disk space.

So, the configuration file has been 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 launch our project by clicking the "Run\Stop" button or use the Ctrl+R key combination. If all settings have been made correctly, the appearance of 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 - the color of the light bulb changes 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 the controller will generate different control actions depending on it.

Laboratory work No. 2.

Creating an operator interface and control model in a tool environment TRACE MODE 6

1. Goal of the work

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

1. Tasks

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

1. 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 graphic operator screen templates, development of program templates, description of sources/receivers, etc.;
  • configuration of information flows;
  • selection of ACS hardware (computers, controllers, etc.);
  • creating nodes in a layer System and their configuration;
  • distribution of channels created in various layers of the structure across nodes and configuration of interfaces for interaction of components in information flows;
  • saving the project into a single file for later editing;
  • export of nodes to sets of files for subsequent launch under the control of TRACE MODE monitors.

The listed procedures (with the exception of the final 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), you can configure channels and information flows after distributing the channels to nodes, etc.

3.1. Classification of project structure objects.

3.1.1. Classification of components.

According to their 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 across nodes in the layer System mandatory otherwise they will not be exported for RTO;
• templates components that, when working in real time, can be called by channels with parameter transfer. The transfer of parameters is configured when developing a project in the IS by binding template arguments to channels or sources/receivers;
• sources/receiverstemplates for exchange channels with various devices and applications. Here, devices are understood as 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 to develop graphic screen templates;
• graphic objectscomponents, which in general represent several graphic elements (from those available in the data presentation editor), grouped into one. Graphic objects can be used to develop graphic screen templates;
• serial portsCOM port parameters;
• message dictionariessets of messages generated when various events occur;
• terminals these components, which describe electrical contacts (for example, wiring cabinets), are elements of the electrical connection diagram of the automated control system.

3.1.2. Layer classification.

The predefined layers of the project structure have the following purposes:

• Resources to create custom sets of texts, images and video clips, as well as graphic objects;
• Program Templatesto create program templates;
• Screen Templates to create templates for graphic screens, graphic panels and mnemonic diagrams;
• Database Link Templatesto create templates for connections with databases;
• Document templatesto 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 various 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 on 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/Receiversfor creating built-in generators, templates for exchange channels with various devices and software applications, as well as for configuring TRACE MODE 6 system variables,
• Technology to develop a project based on technology (i.e., grouping components based on their belonging to technological object). In this layer, the channel encoding is built automatically, inheriting the encoding of all higher-level objects into which the channel is included. 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 interacting with the technological database are defined for this layer;
• Topology to develop a project based on topology (i.e., grouping components by location);
• instrumentation and automation to describe the electrical connections of the automated control system;
• Component Librariesto create libraries of objects design solutions for individual tasks. This layer contains the predefined groups System and User.

3.1.3. Classification of nodes.

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

In general, nodes can run under the control of different monitors.

Typically, the node runs on separate hardware. If two or more nodes are running on one hardware, it must be equipped with an appropriate number of network cards.

Node parameters are set in the corresponding node parameters editor.

Types of nodes:

• RTM . The RTM node is designed to run on a computer under the control of executive modules of the RTM family (MRV) monitors with support for displaying operator graphic screens, support for exchange via a serial interface and network with various equipment and recalculation of channels of all classes, except for T-FACTORY channels.
• T-FACTORY . The T-FACTORY node is designed to run monitors on a computer under the control of executive modules of the T-FACTORY family of monitors to solve automated control system problems.
• MicroRTM . The MicroRTM node is designed to run on a computer or controller controlled by the Micro RTM family of execution modules. The main difference between these monitors and MPBs is the lack of support for displaying graphic screens.
• Logger . The Logger node is designed to be launched on a computer under the control of the Logger executive module (recorder) - 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 controller under the control of executive modules of the Embedded RTM family of monitors that support graphic panels, support exchange with equipment using various protocols, and perform channel recalculation.
• NanoRTM . The NanoRTM node is designed to run in a controller under the control of the Nano RTM monitor executive module, 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 under the control of executive modules, which, unlike RTM, do not recalculate channels intended for working with data. Consoles allow you to receive data from other project nodes over the network, display them on graphic screens and control the technological process from graphics. Consoles cannot communicate with T-FACTORY nodes.
• TFactory_Console . The TFactory_Console node is designed to run on a computer under the control of executive modules, similar to consoles, but, in addition, capable of interacting with T-FACTORY nodes.
• EmbeddedConsole . This node runs on monitors that only support graphics panels.

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

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

The operating algorithm of any TRACE MODE monitor is to analyze the channels and variable structures created both during project development in the 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: recording the values ​​of the channel variables in 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 general, writing a value to a channel means assigning a value to a variable (attribute)Input value this channel.

Two important properties can be configured for a channel: Communication and Calling.

The first property means the ability of the channel 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 by passing the necessary parameters to it (for a CALL class channel, the call property has extended functions). Based on the property, the call is implemented, for example, a graphical operator interface, exchange with a database, etc.

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

The class of a channel determines its general purpose. For example, a channel of the FLOAT class is intended for operations with 4byte real numbers, a channel of the Unit of Equipment class is intended for accounting for a piece 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 specific values ​​are called flags. An example of a flag is the channel type, which takes two values: INPUT (numeric channels of type INPUT are intended to receive data from sources) and OUTPUT (numeric channels of type OUTPUT are intended to transmit their value to receivers). The attributes that are used to pass values ​​when calling a 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). Attribute identifiers are its index and, in some cases, a short name.

Channels contain predefined algorithms (some of which 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 the attribute Change time monitor records attribute change timeReal channel value(according to the clock readings of the device on which the monitor is running).

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 channel processing after its recalculation is performed at certain conditions. When recalculating the channel base, recalculation of a specific channel is also performed under certain conditions.

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

Channel is a structure consisting of a set of variables and procedures, which has settings for external data, identifiers and the period for recalculating 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 board located in the first controller footprint would be AI_-pe01-0005. In addition, each channel has a numeric identifier that is used internally to refer to that channel. Among the channel variables, there are four main values: input (In), hardware (A), real (R) and output (Q). Using settings, the input value of the channel is associated with the data source, and the output value with the receiver.

Depending on the direction of movement of information, i.e. from external sources (data from controllers, USO or system variables) into 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 sent to the channel input and then converted into hardware and real values. The hardware value for INPUT type channels 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, correction of the temperature of cold junctions of thermocouples, etc.). Output values ​​are not used on INPUT 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 channel output values. For channels of the OUTPUT type, their input value is formed in one of the following ways:

• control procedure for 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 the OUTPUT type, the hardware value is obtained from the real one by the translation procedure. Hardware channel values ​​have this name because they are convenient for obtaining the values ​​of unified signals with which input/output equipment operates (4-20 mA, 0-10 V, etc.). Real values ​​are intended to store the values ​​of monitored parameters or control signals in real units (for example, kg/hour, O 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 and content of the procedures may vary depending on the type of channel (input or output, analog or discrete). The set of procedures in the channel depends on the data format. Channels that operate with analog variables use the following procedures:scaling, broadcasting, filtering and control . Channels processing 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 type of channel:

• for INPUT type channelsthe input value is multiplied by a given factor and the offset value is added to the resulting result. The result is assigned to the channel's hardware value;
• for channels of type OUTPUTAn offset value is added to the hardware value, then this sum is multiplied by a specified multiplier, and the result is assigned to the channel's output value.

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 for weekends vice versa. To do this, the program is called. The program to be called is selected when setting up the procedure.

When setting up a 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 integration of sensor readings.

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

• suppression of random bursts in the measurement path;
• scale control monitoring the exit of the real channel value beyond the established scale limits.

For channels of type OUTPUTThis procedure generates the real value from the input value. The following operations are performed:

• limiting the rate of change of the real value;
• suppression of small fluctuations in channel value;
• exponential smoothing;
• scale control cutting off the control value to the boundaries 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. The values ​​and attributes of any channels from the current database can be passed to the program as arguments. These arguments can be either input or generated. Formally, the control procedure is associated with the channel only by a recalculation cycle. She may not participate in the formation of its meanings at all, but manage other channels. This situation is often observed when using the procedure Control on channels of the INPUT type.

Monitor is a multi-threaded process. Thread priorities are set by default, but they can be changed. The main thread that runs cyclically is the thread CALC . Each cycle of this thread includes the following stages executed sequentially:

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

If the SV flag is not cleared in the main thread, it is a sign that the channel needs to be recalculated in the corresponding thread.

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

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

• in MS Windows at least 0.01c;
• in MS Windows CE no less than 0.001s.

By default, the timer resolution is 0.055 s, period 10.

3.3 Graphical interface development.

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

The operator's graphical interface is implemented in several forms:

• in the form of a set of graphic screens, the templates of which are developed in the Data Presentation Editor (RDE), for nodes that are executed by monitors on hardware that has 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, templates for which are developed in eRPD (modification of 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). Having selected the required project node, you can edit its graphical base. This database includes all graphic fragments that are displayed on the monitor of a given operator station.

RPD and eRPD contain a large number of built-in graphic elements (GE and USE, respectively) that 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, which can be used in developing a graphical operator interface. Resources can be created by the user.

The totality of all screens for data presentation and supervisory control included in the graphical databases of project nodes constitute its graphical part. Screens in the graphical databases 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, in one group you can collect mnemonic diagrams, in another regulator settings screens, in a third overview screens, etc. Only one screen can be displayed on the monitor at a time, each of them is a fixed-size graphic space on which static drawing and display forms are placed. It has its own name and a set of attributes (settings). These attributes include: Size, Background Color, Wallpaper, Access Rights, Alarm Report View Window Specification.

The development of graphic screens is carried out by placing graphic elements on them. There are static and dynamic elements. Static elements do not depend on the values ​​of controlled parameters, and no actions to manage the information displayed on the screen are tied to them. These elements are used to develop the static part of graphic screens, for example, to display filled containers, boilers, motors, etc. That's why 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 display forms are used to control channel attribute values ​​or information displayed on the screen. Some forms can also combine both functions.

On the screens you can place complexes of static and dynamic elements, designed as graphic objects, used to replicate ready-made solutions in the field of creating an operator interface.Graphic objectis a set of display forms and drawing elements, which is designed as a single graphic element. Standard graphic fragments designed as objects can be inserted into the screens of graphic databases of any projects.

There are two types of graphic objects: “Object” and “Block”. The first of them can refer to 256 channels, and the second can only refer to one.

To create and edit objects, the same windows are used as when working with screens. Object development is identical to the screen development process. The only difference is in setting up the display forms for channels. In an object, display forms are associated with its internal channels. When placing an object on the screen, these channels are adjusted to the real channels of the edited node.

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.

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

3.4. Algorithm programming.

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

For mathematical data processing, TRACE MODE 6 provides the following tools:

• 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 languages ​​ST (Structured Text), SFC (Sequential Function Chart), FBD (Function Block Diagram), LD (Ladder Diagram) and IL (Instruction List) of the IEC61131-3 standard. Programs developed in the IS allow the use of functions from external libraries (DLLs).

These tools provide the ability to mathematically process data at any link in 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 the 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 the Techno LD, Techno SFC and Techno FBD languages ​​are translated into Techno ST before compilation. Before compilation, IL programs are partially translated into ST and partially into assembler. It follows, for example, that Techno ST keywords 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:

• execute command Compile from the Program menu (or press the F7 key or press the LK on the icon Compilation (F 7) debugger toolbar) this command creates only code for debugging the program in the IS. Debugging code is saved in a subdirectory created in the %TRACE MODE 6 IDE%\tmp directory. If the compiler detects errors, it displays appropriate messages in a window that opens automatically in this case. If the compilation was successful, the message window does not open;
• Export the project Using this command, both debug and executable code is created in the node folder containing the program call channel. If errors are detected in the program, a message is displayed indicating that it cannot be exported.

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

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

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

1. Description of the software systems used

The TRACE MODE 6 tool system is launched by double-clicking the left mouse button on the Windows desktop icon or from the “START/All Programs/” menu Trace Mode 6/ TRACE MODE IDE 6".

The end result of the TRACE MODE 6 instrumental system is a set of files intended for executing ACS tasks in real-time monitors on workstations and controllers. In the laboratory work, a profiler with support for graphic screens will be used as an RTM for the automated workplace. 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 a menu File , View , Windows and Help , and the toolbar.

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

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

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

The tools of all editors and IS windows are equipped with tooltips.

For the task general settings IS and template editors have a dialog that opens on command IS Settings File menu.

Saving a project for editing is performed using the 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 subsequent editing in the IS. When these commands are executed, 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 executed again 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 the 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 by "_" characters). Files of nodes that have the same names in the IS are exported to one folder.

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

By command Save node for RTM from the Project menu or the navigator context menu, the selected node is exported to an arbitrary folder, and during repeated export, backup copies of the node are not created.

1. Security measures

During laboratory work you must:

• follow the rules for turning computer equipment on and off;
• 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 the m pewter;
• If a malfunction is detected in the operation of the equipment or a violation of safety regulations, inform the management O laboratory supervisor;
• Do not attempt to troubleshoot equipment malfunctions on your own;
• After finishing work, tidy up your work area.

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

1. Exercise

6.1. Create an operator interface for a control system containing one workstation node, model control object, PID controller, 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 tools and graphic elements.

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

6.3. Realize the operation of the control system in real time, remove the transient response of the control object as a reaction to a stepwise change in the set point.

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

Table 1. Options for tasks on control object parameters

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

1. Methodology for completing the task

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

7.1.1. Create a new standard project.

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

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

7.1.4. In the Resources layer, create the Graphics_elements group. Create a Graphic_object in this group. Using available graphic tools, create a conditional image of the control object, consisting of at least two volumetric figures with a superimposed texture.

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

• elements for entering values ​​and displaying setpoint values,
• regulator image,
• image of the control object,
• lines of communication between them,
• elements for entering values ​​and displaying values ​​of controller parameters,
• elements for displaying control values ​​and the 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. Follow the help section QUICK START PART ONE.

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

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

7.2.2. Explore the help section 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 O.B.J. parameters of the control object transmission coefficient, time constant, delay set by constants in accordance with the task option. For block noise parameter O.B.J. use 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.

1. Requirements for the content and format of the report

The laboratory report must contain:

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

1. Control 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 of the composition FBD can it be used to simulate control systems?

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

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

9.7. How is the system launched in real time?

1. Criteria for assessing the performance of laboratory work

Laboratory work is considered completed if:

• the student completed all tasks in accordance with the presentation new technique;
• the results of the work, presented in the form of reports e that meet the requirements imposed on them;
• the student answered everything correctly Control questions and can interpret the results obtained.

1. Literature

Analog (FLOAT)

Source

move

Scaling

Hardware

Broadcast

Filtration

Real

Control

Control

Real

Broadcast

Hardware

Logical processing

Entrance

Source

Discrete (HEX)

Real

Broadcast

Hardware

Logical processing

Exit

Receiver

Discrete (HEX)

Control

Entrance

Filtration

Real

Broadcast

Hardware

Scaling

Exit

Analog (FLOAT)

Control

Entrance

Instrumentation system TRACE MODE® 6 is a universal tool for developing and debugging applications for automated process control systems ( APCS) and production management ( ASUP).

The TRACE MODE 6 instrument system consists of integrated development environment and real-time debug monitor - profiler.

The TRACE MODE 6 integrated development environment is a single software shell that combines all the main components of the tool system:

TRACE MODE 6 integrated development environment has built-in more than ten editors, which automatically open when you call one or another project component. Among them:

In addition, the TRACE MODE integrated development environment (professional line) contains extensive libraries of ready-made components and algorithms:

Control algorithms at all levels of the automated control system are programmed in the same languages ​​of the IEC 61131-3 standard. Connections between components of different levels, for example, between a SOFTLOGIC controller and an APCS server or between two servers are created automatically using a unique auto-building technology within a single distributed ACS project, so calculations can be easily transferred from a computer to a controller or vice versa. All editors are tightly integrated with powerful debugging tools to achieve maximum comfort development of complex distributed automated process control systems and automated control systems.

All project components - screens, programs, SQL queries, document templates, TRACE MODE channels and data sources are interconnected through arguments. Arguments allow you to achieve maximum flexibility when creating connections between individual components. For example, data from a program in a controller could be directly related with the screen display of the operator station or with the MES production planning form, it is not necessary to create additional channels for this.

The tool system comes with a set of free drivers for more than 2589 controllers and I/O boards. Data sources - signals from the device and controllers are created and configured in the system automatically using auto-building. This allows you to avoid manual binding errors and significantly reduce project development time.

The integrated development environment allows gradually increase ICS functionality, starting with simple monitoring and visualization technological process on one SCADA/HMI PC and ending with the implementation of complex control loops, the organization of distributed computing, the connection of additional workstations and economic modules: accounting and Maintenance Equipment Management (EAM), Human Resource Management (HRM) and Manufacturing Execution Management (MES). At the same time, the developer will not experience any psychological discomfort when moving, for example, from programming the SCADA/HMI operator interface to SOFTLOGIC controllers or EAM, because the editors, debugging tools and programming languages ​​are the same.

The TRACE MODE 6 integrated development environment is aimed at a wide range of specialists and can adapt to the qualifications of the process control system and process control system developer. When creating a project, you can choose a development style: simple, standard or advanced.

The integrated development environment TRACE MODE 6 can be launched in parallel with the executive module - Real Time Monitor (RTM) on one PC, which very comfortably for support of small automated process control systems.

The edited project can be automatically updated on remote SCADA/HMI, MES, EAM, HRM servers and SOFTLOGIC controllers.

The TRACE MODE 6 development tool system is equipped with a special real-time debug monitor - profiler. This is a type of TRACE MODE executive module designed for debugging a process control system project in real time. The profiler differs from a regular RTM in that it logs all its actions in a text file. The profiler is a standalone application, but a project can be launched in it from the TRACE MODE 6 integrated development environment by pressing one button on the toolbar.

Like all TRACE MODE programs, the integrated development environment is divided into basic and professional lines. Baseline Instrumentation System free- it can be downloaded/ordered on the website.

Integrated development environment TRACE MODE 6 is a unique combination of the richest functionality and intuitiveness interface. Practice shows that using an integrated development environment can save up to 30% of working time compared to using separate SCADA/HMI editors and controller programming systems. And the integration of economic modules T-FACTORY and SCADA of the TRACE MODE system opens up previously unavailable opportunities for optimizing production as a whole.