Configuring Intouch Communication via Modbus TCP

This article offers those who are mastering the classic InTouch R14 step-by-step instructions for setting up communication with devices using the Modbus TCP protocol

I will try to explain those features of the settings that can put a novice developer in a difficult situation.

1. Licensing
The Klinkmann company supports the developers of its products by issuing full-fledged, but temporary licenses, each of which is valid for a little less than a month. After this period, both the development system and the runtime stop working. You need to re-request and update license files.

Usually three files are issued. All of them must be installed in the ArchestrA License Manager. It looks like this:

The absence of a license or an incorrectly installed license may be the reasons for the lack of communication. After installing the licenses, it is advisable to reboot.

2. Download and install the integration package Server DA (DASMBTCP)

Detailed setup instructions in the video example:

3. As a MODBUS TCP emulator, I usually use a product from Modbus Tools (Modbus Pool & Modbus Slave)

We immediately set up data exchange to make sure that everything is working with the Modbus TCP protocol and data is being exchanged.

Attention!!!

ID set 255. Otherwise it will not work. I have not yet found where to change this value in the driver properties. If your Slave device is with a different ID, then a working connection will not be achieved.

We disable Modbus Pool, we do not need the port to be busy at the beginning of the connection.

4. Configure the Server DA driver (DASMBTCP)

We pay attention to the port number (for example, indicated 503)!

Here we form a general list of tags that will exchange data with the PLC

Help describes the signs that we have the opportunity to specify for the correct receipt of data

5. Indication of parameters on the video frame

Go to WindowMaker

Creating an Access Name that will be associated with our topic and server

Next, we create the required number of tags associated with the Access Name

Then, create dynamic text on the video frame

Linking it with the tag we need

6. We start the system Online (Runtime)

If no error is made anywhere, then values similar to those set in Modbus Slave should appear.

I experimented a bit with disabling the drivers manually. I found out that when the connection is lost, the values \u200b\u200bremain on the screen unchanged, without giving any sign of an error. This is certainly not suitable for industrial operation. I will look for how to implement it differently, for example, replacing values with pound signs. I will add to this article later, when I find a solution.

#configurationmodbas, #intouchconfiguration, #driverintouch