Press ESC to close · Ctrl+K to open
Home › SCADA › INTOUCH › Article

Intouch Edge HMI - Intouch Machine Edition - InduSoft Web Studio - Vijeo XL - Communication S7-1500

Jose Manuel Luque
Intouch Edge HMI Intouch SCADA

Intouch Edge HMI - Intouch Machine Edition - InduSoft Web Studio - Vijeo XL - Communication S7-1500

Once we have seen that all the mentioned software are part of InduSoft Web Studio, we will see how to configure the communication with a Siemens S7-1500, but I have chosen Intouch Edge HMI.

 

Within the graphical interface, we have four main tabs (Global - Graphics - Tasks - Comm).

It is clear that we are going to the Comm tab.

 

And we are going to add a new Driver.

 

We have a pop-up window where all available drivers appear; there are more than 200 available drivers. If you need to download one, it can be done from the Indusoft website.

Since we are going to communicate with an S7-1500, we will use the SITIA Driver.

 

Once the Driver is added, the Driver Data Sheet is automatically created, where we will configure our variables. The process is very easy, and there are several ways to do it.

We have the Tag Name column, which is where we will define the Intouch variable. If it is not created, it can be created from here, as can be seen in the following image.

 

Next to the Tag Name column is the Station column; here we will define the IP address of our PLC.

Now we need to link the Tag we created (Tag Name) from the PLC (Station) with the I/O Address variable. In this column, we will define the name of the Tag we assigned in our TIA Portal project.

With this, we have finished configuring the communication.

 

To test its operation, I created a display where we will link our Tags, a Start button, and a Stop button with their corresponding associated events to write and reset the tag. In short, the example of a Stop/Start.

 

Before starting the Runtime, we will enable in Log the options for Field Read Commands and Field Write Commands; this will help us check the communications.

 

We start the Runtime, and as can be seen, the communication is perfect.

 

And if we write a Tag, it is confirmed in the Log that the read/write is OK!

 

As additional information, it is advisable that the Driver Runtime service is configured as Automatic, and when the Runtime starts, the Service automatically starts and functions...

 

January 29, 2019