5 Commissioning the PLC programming environment5.2 For Modbus/TCPSmartWire-DT Gateway EU5C-SWD-EIP-MODTCP 08/17 MN120003Z EN www.eaton.com 495.2 For Modbus/TCP5.2.1 What the SWD-Assist text file looks likeThe SmartWire-DT I/O data is mapped to 16-bit Modbusregisters￫ Chapter 7 "Modbus/TCP – SmartWire-DT implementation“, page72.In order to make it easier to identify the I/O data in the PLC programmingenvironment, 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 ofa table in a TXT file. It can be edited further directly in a PLC programmingenvironment or in a spreadsheet program such as Microsoft Excel.The table below shows how device names are used in I/O addresses andsymbolic names in the TXT file.Figure 32: I/O data for Modbus/TCP; sample extract from a TXT fileThe 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 anoutput (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 thespecific input/output data• The specific input/output data's data type• A description of the specific input/output dataIf this information is used in order to generate input/output variables, the var-ious definition access methods of the PLC programming environment beingused must be taken into account.
