menu

This article is about configuring the KOMET-Software TSVNCC to deliver internal variables from a Siemens control - independently from a field bus connection.

The configuration files ToolScope.ini/TSVNCC.ini of TSVNCC contains initialization information for the OPCConnector. No licensing is necessary for operation on a ToolScope. Other than the "OPCConnector-ON" setting, you can normally leave the file in its delivery status.

Example:

       [OPC-Connector]

;Mode=OPC   -> Data is read and sent from the OPC-Server

;Mode=Dummy -> Simulated data is sent, no OPC-;connection is established

Mode=OPC

Licensekey=176E-4B-0F41

OPC-Connector-ON=0

OPC-Connector-Port=3000

 

Rows with a leading ; are comments and are not taken into account by the OPCConnector.

The Mode=… line specifies the mode in which the OPCConnector is working.

OPC supplies data from the Siemens control system

Dummy is a test mode which generates data independently          



We recommend that external programmers use this mode as the test mode. Start the OPCConnector in the background in "Dummy" mode and use the dummies running in the background to test the application which is to access the OPCConnector. As soon as your application appears to be working correctly, switch to OPC mode.

           

LicenseKey=… specifies the license key for the OPCConnector. This can be requested from KOMET® BRINKHAUS.

OPC-Connector-ON=… determines whether the OPCConnector in the TSVNCC is activated.

OPC-Connector-Port= … is the port through which the ToolScope connects to the remote access driver

Variable definition in ts_variables.ini

The required OPC variables must be entered in the ts_variables files row by row. The names of these variables can be found in documentation from Siemens, which we cannot supply at this point. A list is provided in the file BTSS_GR.hlp, for example, which is included in the programming package for the Solution Line.

See here for a detailed reference list of variables which are usable for our typical use cases.

Example:

# ---------------------------------------------------------------------------

# In this file, data is defined, which is to be read out by the OPC

# servers.

# Rows that begin with a '#' are comments

# A row that begins with an 'f' or 'F', defines the

# reading frequency in Hertz (example: "f10.0")

# Rows that begin with 's' or 'S' define a String32 dataset

# All other rows define one dataset each, of the type 'double'

# ---------------------------------------------------------------------------

#

f20.0

#

# ---------------------------------------------------------------------------

#

(...)

#/DriveHsa/State/actualCurrent[u1]#s/Channel/ProgramInfo/progName[u1]@Programmname

s/Channel/ProgramInfo/blockNoStr[u1]@BlockNr

(...)

# --------------------------------------------------------------------------

 

The file ovvers several variables as patterns for Copy&Paste-use, which are deleted above "(...)".

Rows with a leading # are comments and are not taken into consideration.

A row that begins with an 'f' or 'F' defines the reading frequency in Hertz (example: "f10.0").

Rows that begin with 's' or 'S' define the output of a character string. A maximum of 32 characters are transferred.

A designator that the OPC-Connector sends as the signal name can be defined for the names of the variables, separated by an "@". If this is omitted, the name (path) of the OPC variables is used instead. Then, an axis name can be assigned, separated by a "$". If this is omitted, "-" is transferred instead.

Rows that begin without one of the above-mentioned codes each define a floating point number (data type Double / IEEE-64bit).

Example of a string:

s/Channel/ProgramInfo/progName[u1]@Programm-Name$-

Example of a floating point number:

Example: /Channel/State/stopCond[u1]@Stopp-Bedingung$Z