Specifications
34
The aim of this chapter is to provide key information for conguring the various system components ( PLC, mo-
tor control devices, SCADA and HMI application). The main purpose is to build a consistent system congura-
tion with the description of all data exchanged between key solution components.
The conguration of the system comprises the following stages:
Conguration of data to be exchanged periodically between PLC application and motor control devices b
Different cases of I/O scanning communication service will be described in the following chapters.
Conguration of data and data type to be used both in PLC and SCADA applications b
A recommendation is provided to allow a unique conguration of data in both tools.
Conguration of data and data type to be used both in PLC and HMI applications b
A recommendation is provided to facilitate the conguration of data in both tools.
Purpose
PLC and motor control device conguration
PLC application exchanges every Scan time input and output data with the motor control devices.
The I/O scanning communication service is used on Ethernet to perform this periodic communication.
To dene the I/O scanning service conguration in Unity it is necessary to identify the data to be exchanged
with each motor control device. In the solution platform, described in chapter 7, three types of communication
architecture are used, that imply different characteristics in I/O scanning parameters.
Direct starter TeSys-U, TeSys D or variable speed drive ATV31 connected on Advantys STB with an Ethernet 1
NIM (Network Interface Module) STB_NIP2212
Soft starter ATS_48 or TeSys T connected behind an Ethernet gateway to Modbus serial line (TSXETG100) 2
Variable speed drive ATV_61 connected directly on Ethernet3
ATV61
ETG100
ATS48
TeSys T TeSys U
Ethernet Modbus
on TCP IP
STB
ATV31
TeSys D
PLC
I/O scanning
1
2
3
Principle
4-Conguration
Introduction