5 Commissioning the PLC programming environment
5.2 For Modbus/TCP
SmartWire-DT Gateway EU5C-SWD-EIP-MODTCP
08/17 MN120003Z EN
www.eaton.com
49
5.2 For Modbus/TCP
5.2.1 What the SWD-Assist text file looks like
The SmartWire-DT I/O data is mapped to 16-bit Modbus
registers
Chapter 7 "Modbus/TCP – SmartWire-DT implementation“, page
In order to make it easier to identify the I/O data in the PLC programming
environment, SWD-Assist generates a TXT file with all I/O data for the corre-
sponding Modbus/TCP information. This information is stored in the form of
a table in a TXT file. It can be edited further directly in a PLC programming
environment or in a spreadsheet program such as Microsoft Excel.
The table below shows how device names are used in I/O addresses and
symbolic names in the TXT file.
Figure 32:
I/O data for Modbus/TCP; sample extract from a TXT file
The following information is included:
•
The symbolic name -in the "Name" column, made up of:
•
The gateway's device name ("ModTCP" in this example)
•
The module's device name; "PKEn1" for the SmartWire-DT-PKE con-
nection in this example
•
A code used to indicate whether the address is for an input (I) or an
output (Q)
•
An individual code for the specific I/O data,
e.g., "C" for the feedback signal for the contactor position
•
The name of the input/output
•
The address of the Modbus register
•
The bit position within the word and the bit length of the
specific input/output data
•
The specific input/output data's data type
•
A description of the specific input/output data
If this information is used in order to generate input/output variables, the var-
ious definition access methods of the PLC programming environment being
used must be taken into account.
