If the device is connected to the computer via a local network or over the Internet, you need to install Advanced TCP/IP Data Logger (see the top link).
You also need to install the "Binary parsers" module, which enables the logger to work with VKT-7. The module will send data requests to the heat calculator unit on a schedule, process its responses, and prepare data for exporting.
1. Configure the heat calculator unit connection, that is, COM port or TCP connection parameters (figures 1 and 2).
2. Select the parser module for the VKT-7 device in the program's settings. If the heat calculator unit is connected to the computer via a COM port, you also need to select the respective data request module (figure 3; the module is not shown).
Figure 1.3 Selecting a parser module for VKT-7
Data reading settings
You can specify the heat calculator unit's port number and device ID, which can be used when exporting data or writing data to a database (figure 1).
Set up a data reading schedule in the parser module's settings (figures 2 and 3). You can set up a separate schedule for each data type (current, hourly, daily, or accumulated data).
Figure 2.2 VKT-7. Current data
Figure 2.3 VKT-7. Accumulated data
Writing data to a database
You can use the "ODBC Database" data export module to write data to a database. The module can write data to almost any database, provided that there is a respective ODBC driver.
You can write data from multiple heat calculator units to a single database table. In that case, each row will contain a unique device ID and a port number.
1. Manually create a table with the necessary rows and columns (fields) in your database. Below you can find some table-creating scripts that we recommend to use.
CREATE TABLE dbo.[DATA] (
[ID] decimal(10,0) IDENTITY(1,1) NOT NULL,
[DATE_TIME_STAMP] datetime NULL,
[DATA_SOURCE_NAME] nvarchar(32) NULL,
[DEVICE_ID] nvarchar(32) NULL,
[DEVICE_NAME] nvarchar(32) NULL,
[DEVICE_DESC] nvarchar(32) NULL,
[TIMESTAMP] datetime NULL,
[TIMESTAMP_UTC] datetime NULL,
[SERIAL_NO] nvarchar(32) NULL,
[DATA_TYPE] int NULL,
[EVENT_ID] int NULL,
[DATABASE_NO] int NULL,
[SYSTEM_NO] int NULL,
[T1] real NULL,
[T2] real NULL,
[T3] real NULL,
[V1] real NULL,
[V2] real NULL,
[V3] real NULL,
[M1] real NULL,
[M2] real NULL,
[M3] real NULL,
[P1] real NULL,
[P2] real NULL,
[Mg] real NULL,
[QO] real NULL,
[QG] real NULL,
[DT] real NULL,
[TX] real NULL,
[TA] real NULL,
[BHP] real NULL,
[G1] real NULL,
[G2] real NULL,
[G3] real NULL,
[EVENT] real NULL,
[EVENT_TIME] real NULL,
[DI] real NULL,
CONSTRAINT [PK_DATA] PRIMARY KEY ([ID] ASC)
WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
2. Open the data export module's settings and enable writing to the database. Then switch to the "Connection" tab, click the "Configure" button, and create a connection to your database (figures 1 - 3).
3. Switch to the "Binding" tab, import the table structure from the database, and bind the parser variables to the respective columns (fields). Then delete all the unbound columns for which there is a default value in the table-creating script (figures 4 and 5).
Logging data to a plain-text file
Our program can log all the collected and processed data to plain-text files in addition to writing data to a database. You can use such log files as backup copies or keep them for later analysis. Our program can automatically create a new log file every day, every week, or every month (figures 1 and 2).
Figure 4.1 Data output settings for VKT-7
Figure 4.2 Data output settings for VKT-7
Our program has a built-in OPC DA2 server that allows you to retrieve and view the last-read current or accumulated values at any time. The recommended OPC server settings are shown in figures 1 and 2.
Figure 5.1 Enabling the OPC server VKT-7
Figure 5.2 VKT-7. An example of data received.
To make data viewing easier, you can use different tag groups for current data and accumulated data. To do it, you can specify a data grouping rule for the OPC server. In the example, the data are grouped by serial number and data type.