Generic TCP/IP Driver User Manual Schneider Electric
Contents
1. 7TTCP Generic TCP IP Driver Schneider 7TTCP Generic TCP IP Driver User Manual Schneider Electric Denmark A S Schneider Electric IGSS Automation Lautrupvang 1 DK 2750 Ballerup Denmark Phone 45 88 30 20 00 www schneider electric com VAT no DK 73 63 41 13 Schneider Disclaimer The information provided in this documentation contains general descriptions and or technical characteristics of the performance of the products contained therein The documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications It is the duty of any such user or integrator to perform the appropriate and complete risk analysis evaluation and testing of the products with respect to the relevant specific application of use thereof Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein The information contained herein is the property of Schneider electric and is supplied without liability for errors or omissions If you have any suggestions for improvements or amendments or have found errors in this publication please notify us No part of this document may be reproduced in any form or by any means electronic or mechanical including photocopying without express written permission of Schneider Electric All pertinent state regional and local2. After you have created the new node you can configure the node setting the required node options and parameters in the Node Properties Identification and Advanced tab pages in the right pane of the System Configuration form 7TTCP Generic TCP IP Driver Node Parameters The following table describes some of the parameters you can define for the node Field Description IGSS node number The node number which IGSS uses to reference a unique 7TTCPMON application or other node This node number is required when binding an IGSS atom tag to a register in the 7TTCPMON application or the node Any number from the drop down list can be used TCP IP Parameters Local IP Address Only used for multihomed setups and should normally be left empty Remote IP Address The IP address of the 7TTCPMON application or the node Local Socket number port number Only used for multihomed setups and should normally be left empty Remote Socket number port number The port number of the 7TMONTCP application or the node The default value is 12398 Use keep alive Activate keep alive messages if no scan or set output messages within 10 seconds Testing the connection When the PLC and the IGSS Station machine are connected on a network and both are running you can verify the IP address by using the PING command in a command prompt See the example below Example in a comma
3. IGSS has been installed To manually install the 7TTCP interface driver 1 Copy the following files to the IGSS installation folder a 7TTCP dll b 7TTCP dll c CommbDrv reg 2 Locate the CommDrv reg file and double click the file to update the windows registry settings You can also open the Windows Registry Editor and import the file from the Windows Registry Editor Note that double clicking on a REG file in a 64 Bit Windows Operating System will not work please contact IGSS Support for instructions If the files do not exist in the IGSS installation folder run the IGSSUpdateClient to update your IGSS installation and retrieve the files from the IGSS Update server or contact IGSS Support who can send you the files via e mail You can also copy the files from another IGSS installation of the same version although it is advisable to update your IGSS installation in order to ensure you have the most recent versions of the driver files Driver Configuration This section describes how to configure the driver parameters All driver parameters and set up options are configured in the System Configuration form The System Configuration form is opened by clicking the System Configuration button in the IGSS Master Design and Setup tab Note The IGSS configuration must be stopped and restarted for the configured driver parameters to take effect Configuring the driver Once the driver has been added to the station
4. you can configure the driver creating and setting up the interface and nodes of the 7TTCP interface driver zrrop Schneider Generic TCP IP Driver L E ectric In the left pane of the System Configuration form select the station IGSS server or Operator Station with Distributed Driver and expand the driver list under the station Select the Generic TCP IP driver If the Generic TCP IP driver is not present add the driver by right clicking the station and selecting New Driver In the Select Communication Driver form select the 7TTCP Generic TCP IP driver Driver ID 34 r L IGSS System Configuration c programdata 7t igss32 v11 0 test_jan_drv_34_7ttcp test_jan 2 8 File Edit View Tools Help B atima Project name test jan Driver Information Advanced Extemal Types 5 8 SERVER H S Generic TCP IP Driver Driver information Generic TCP IP Driver Driver Id 34 Statistics Top nodes 1 Sub nodes 0 File versions amp Driver DLL File 7TTCP DLL Version 11 00 00 build 15231 Tr Configuration DLL File 7TTCPC DLL Version 11 00 00 build 15231 For Help press F1 A Adding new PLC machines When a new PLC machine is added you can add a new node representing the PLC to the driver in the left pane of the System Configuration form Adding a new Interface Some drivers require you to create an interface per node to contain the node and some drivers only require one
5. C should only be affected marginally provided that the PC NIC throughput is sufficient The IGSS communication engine optimizes communication throughput by seeking to group data whenever possible Therefore if the communication engine is required to read e g DM0001 and DM0031 then it will read data registers DM0001 DM0002 DM0031 as a block This is much more efficient than reading the two data registers using two separate read requests Error Codes This section describes the error codes specific to the IGSS 7TTCP interface driver While troubleshooting communication or addressing problems the Driver Test Application might be useful to display error codes reported by the driver The following table describes some of the possible 7TTCP error codes Error Code Description 0x5501 Name Example 7TOMRTCP DATA BLOCK TOO BIG Cause Example User attempted to read or write a block of more than 256 items Driver only allows up to 256 items in a block 0x4001 Name 7TTCP BIND SOCKET FAILED Cause Unable to open a stream socket Action Check that WinSock is present Subcode windows errorcodes 0x4002 Name 7TTCP BIND SOCKET FAILED Cause Unable to bind to socket Action Check if local IP address and port is used twice in the same configuration Subcode windows errorcodes 0x4003 Name 7TTCP_CONNECT_SOCKET_FAILED Cause Unable to connect to remote node Action verify that the node IP Addre
6. can connect with the following PLC machines 7TTCP Generic TCP IP Driver Schneider An Ethernet port supporting TCP IP UDP IP is required on the PLC machines Please refer to the PLC documentation supplied by the PLC producer for cable setup and wiring instructions Installation The IGSS 7TTCP Interface Driver is assigned the Driver ID 34 in the IGSS program and is displayed in the System Configuration form where it can be selected when setting up the IGSS configuration Once the IGSS program has been installed on the IGSS Server machine and the IGSS Master has been started the configuration which is to use the 7TTCP interface driver can be opened in the IGSS Master and set up in the System Configuration form Automatic Installation The driver is normally installed when IGSS is installed To verify that the driver has been installed correctly open the System Configuration form In the left pane of the System Configuration form select an IGSS station and click Edit New Driver or right click the station and select New Driver The 7TTCP interface driver Driver ID 34 should be found in the list of available drivers in the Select Communication Driver form Select Communication Driver a Select a communication driver to be installed from the list below Then click OK Driver mi 7TAB mi 7TSMAX ID 33 Description Allen Bradley RSLinx interface driver DDE Supermax interfac
7. e driver Saia P8 interface driver Siemens S7 HMI adapter interface driver FT2000 AlarmNet interface driver Dupline Modem Interface D 9091 SattBus 64Kbit s Protocol Driver CMM 7000 Protocol Driver Orum amp Jensen PS4 Protocol Driver 34 Generic TCP IP Driver 35 36 37 38 39 40 41 42 B amp K 1301 IEEE 488 GPIB Interface Driver P Net VIGO Interface Driver Siemens S7 TeleService adapter interface driver FPC Lund Petersen amp Andersen protocol driver Alarmnet driver for Al800 ABB RCOM Extended protocol driver KOYO DirectNet Driver OPC OLE For Process Control Client side driver m If the 7TTCP interface driver is present in the Select Communication Driver form you can proceed to the Driver Configuration chapter rTTOP Schneider Generic TCP IP Driver iP E ectric If the 7TTCP interface driver is not present in the Select Communication Driver form you must install the driver manually See Manual Installation below Manual Installation You can manually install the 7TTCP interface driver if it is not present in the IGSS installation by following the process described below You must stop the IGSS configuration in order to install the driver You must also have Local Administrator rights on the local machine in order to make the necessary changes to the machine registry as well as update files in the Program Files folders if that is where
8. eeeeecceeeeeeeseaeeeeaaeseaaaesaeeeeaaesaaaesaaaeeeaaeseeaaesaeaessaeeeesaeeeeaaesenneneaas 10 PEG SetiD m L 10 Object ConflglratiOn diode terere rade le enean pee En Red appe iaa eadein aana naea da dde e ceu un eodd 11 Format Of na Iz 1 16 ER 12 IMPUt INCSSAG 12 Output message i icr et Hals user 13 Performance and Throughput case ee Lesen 14 Error GOd6S TOUT 14 rTTOP Schneider Generic TCP IP Driver iP E ectric Introduction This document describes how to set up and troubleshoot the IGSS 7TTCP Interface Driver The IGSS program must be installed as an IGSS Server on the machine which is to be the IGSS Server and a functioning network of personal computers and PLC machines must be in place prior to installing and configuring the driver The driver implements the IGSS IP stack over TCP Driver Files The following files are used set up and troubleshoot the IGSS 7TTCP interface driver e 7TTCP DLL Contains the protocol stack required for communication with PLCs using ethernet TCP IP interfaces e 7TTCP DLL Contains the graphical user interface used to configure the 7TTCP interface driver e COMMDRV REG Contains the required information which must be correctly updated in the Windows registry in order for the IGSS program to make use of the driver The files are usually located in the GSS folder
9. ider Generic TCP IP Driver L E ectric LI IGSS System Configuration C IGSS Configs IGSS12Configs DMMO Demo File Edit View Tools Help u ae tim x2 Project name Demo Device Properties DemoStation Gopy Interface Remove Interface Suspend Interface Expand Branch Collapse Branch No driver properties applicable for this driver Each new node is a new PLC driver with first node being numbered 0 Naming Nodes PLCs in the System Configuration form You can add a unique name and description to the node in the Identification tab of the Node parameters in the right pane of the System Configuration form T IGSS System Configuration C IGSS Configs IGSS12Configs DMMO Demo File Edit View Tools Help a aoma 2e E Project name Demo Node Properties Identification Advanced a DemoStation amp Generic TCP IP Driver 7TTCP Name will appear in alarm list Node 0 Simulator PLC Simulator PLC Node 1 amp MODBUS GPRS driver Description Siemens 57 TCP IP protocol driver By or Note that the node name will only be displayed in the System Configuration form and will not be displayed in the Edit Mapping tab of the Object Properties form in the Definition module Note The 7TTCP interface driver can support up to 8 nodes
10. interface containing many nodes The Generic TCP TP Driver Driver ID 34 only requires one interface and since an interface was automatically added when you added the driver you can select the node in the left panel 7TTCP Generic TCP IP Driver Schneider 1 IGSS System Configuration c programdata 7t igss32W1LO test jan_drv_34_Tttep test jan mm a File Edit View Tools Help g 35 Max R Project name test_jan Identification Advanced d SERVER 3 8 Generic TCP IP Driver Connection Properties this node IGSS node number TCP IP parameters Local IP Address 0 0 0 0 7TTCP 5 Specify TCP IP parameters and IGSS node number for mE Remote IP Address 127 0 0 1 Local Socket number port number 0 Remote Socket number port number 12398 Protocol Properties Increase telegram retries if driver generates frequent na communication alarms Normally 3 telegram retries are sufficient Telegram retries 3 V Use keep alive at no messages in 10 sec For Help press Fl S Connection Types Adding a new Node After you have created a new interface you can create a new node To add a new node to a driver in the left pane of the System Configuration form right click the 7TTCP interface under the Generic TCP IP driver and select New Node The new node will be created in the 7TTCP interface zrroP Schne
11. nd prompt C3 ping 192 168 11 55 Note that some firewalls will not allow the ping command and the ping response In these cases the Ping command cannot be utilized for verification of the internet connection Specific Driver Installation The following descriptions are based on one of many installation tools for the PLC You can use other installation tools but be aware that each installation tool may differ from the others in specific areas PLC Setup You must set up a connection for communication to IGSS in the PLC Connection type It is also important to verify that any firewalls and other net connection based security software permit TCP IP communication through the defined port Schneider zrrop Schneider Generic TCP IP Driver ES E ectric Once you have set up the PLC and the Driver Interface Node properties in the System Configuration form in IGSS you can start creating and addressing objects in the IGSS configuration to connect to the PLCs in order to send and retrieve data from them Object Configuration Once the driver and the PLC nodes have been defined IGSS Objects and Atoms can be linked to process variables in the PLC node Various different types of PLC memory can be accessed for read write operations using the driver By using the Edit Mapping tab in the Object Properties form you can specify the binding between the object s atoms and the PLC process variables Start by selec
12. of the IGSS installation Default IGSS installation folder The default IGSS installation folder is e For 32 bit machines C Program Files Schneider Electric IGSS32 lt IGSS Version e For 64 bit machines C Program Files x86 Schneider Electric GSS32 lt IGSS Version gt If you have installed IGSS Version 11 the lt IGSS Version gt folder name will be V11 0 Software Requirements The 7TTCP interface driver is designed to be used with IGSS version 11 or higher The 7TTCPdriver uses the standard Microsoft TCP IP protocol stack The protocol is normally installed in all Microsoft operating systems and can be used as it is DNS and other support protocols are not used by the driver and do not need to be installed or configured The 7TTCPdriver uses the ISO transport layer on top of the TCP IP protocol as it is defined in the RFC This means the TCP IP port must be accessible and opened for use If you are employing a firewall please be aware that the port used for TCP IP communication must be open for bi directional connections If the network addresses from the IGSS program to the PLC machines include more firewall all of these must be configured correctly to allow bi directional TCP IP communication Hardware Requirements The 7TTCP interface driver requires a standard Ethernet Network Interface Controller NIC interface with TCP IP UDP IP installed in the PC which contains the IGSS program The IGSS Generic TCP IP driver
13. safety regulations must be observed when installing and using this product For reasons of safety and to help ensure compliance with documented system data only the manufacturer should perform repairs to components Failure to use Schneider Electric software or approved software with our hardware products may result in injury harm or improper operating results Failure to observe this information can result in injury or equipment damage 02004 2015 Schneider Electric All rights reserved Schneider Electric IGSS Automation Lautrupvang 1 DK 2750 Birker d Denmark Phone 45 88 30 20 00 www schneider electric com VAT no DK 73 63 41 13 7TTCP Schneider Generic TCP IP Driver iP E ectric Contents BIS ET 2 Introduction X 4 Bii Bic T eine 4 Software Requirements 20usnsennnnensnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnsnnnnnnnnnnnnnnnnnnnnnnn nen 4 Hardware Requirements scssi nacian kania nnan ina aaa AARAA NAN EAKA EAEAN EE a 4 Inistallatiol 2 E T A A E E E E V ILE E E E INIM 5 Automatic installation sosse Oa 5 Manual Installationen naa can ala 6 Driver ConflguratiOrn uuo ett een eut Fwd o e netu aaea aaa aE aaaea ak a ai 6 ritenere ES 6 Adding new PEG machines cetero teet ee el 7 Node Parameters u en ae ne le nein 10 Testing The COMMOCUION ess 10 Specific Driver Installation cccccccesceeeeccess
14. sages to and from the 7TTCPMON application or the connected nodes Notice the lowest significant byte is in lowest number in Byte Input message This message is received by the driver 7TTCP and the data is send to the IGSS master TCP Header Byte Description Byte 0 3 Length Length is the total length of the message with the number of bytes Byte 4 7 Opcode Opcode 0 to indicate user data Opcode 1 to indicate keep alive TCP Data Byte Description Byte 8 11 Node number The Node number in IGSS The node number can be seen in the System Configuration form in the IGSS Master Byte 12 15 Data group Data group is 0 at output message At input message value 0 should be used The driver 7TTCP only handles data group 0 Byte 16 19 Word offset The word offset for data group Byte 20 23 Type Type 1 read Type 2 write Byte 24 27 Word length of data Word length 2 number of words of data from data 0 to data n at type 2 Word length number of words to be read at type 1 Byte 28 29 Data 0 Data is filled with the lowest significant byte in the lowest number in Byte If using Data type BYTE in the configuration of objects See 3 1 the highest significant byte is set to O zrrcp Schneider Generic TCP IP Driver iP E ectric Byte n n 1 Data n Output message This message is
15. send from IGSS to the specified node TCP Header Byte Description Byte 0 3 Length Length is the total length of the message with the number of bytes Byte 4 7 Opcode Opcode 0 to indicate user data Opcode 1 to indicate keep alive TCP Data Byte Description Byte 8 11 Node number The Node number in IGSS The node number can be seen in the System Configuration form in the IGSS Master Byte 12 15 Data group Data group is 0 at output message At input message value 0 should be used The driver 7TTCP only handles data group 0 Byte 16 19 Word offset The word offset for data group Byte 20 23 Type Type 1 read Type 2 write Byte 24 27 Word length of data Word length 2 number of words of data from data 0 to data n at type 2 Word length number of words to be read at type 1 Byte 28 29 Data 0 Data is filled with the lowest significant byte in the lowest number in Byte If using Data type BYTE in the configuration of objects See 3 1 the highest significant byte is set to 0 Byte n n 1 Data n zrrop Schneider Generic TCP IP Driver iP E ectric Performance and Throughput The driver is designed for maximum throughput on a LAN WAN network On a standard PC with a standard NIC you should expect a throughput of 20 request response cycles pr second Each PLC node is handled concurrent and independently This means if you add more PLC s to the system then the throughput pr PL
16. ss and Port is correct and that it is online by pinging the device using the IP Address and Port supplied for the node in sysconfig zrrop Schneider Generic TCP IP Driver iP E ectric Subcode windows errorcodes 0x4004 Name 7TTCP SEND SOCKET FAILED Cause Unable to send requests to node Action verify that it is possible to ping the device Subcode windows errorcodes 0x4005 Name 7TTCP RECV SOCKET FAILED FF Cause Session closed by remote node Action None the driver will try to reconnect Subcode windows errorcodes 0x4006 Name 7TTCP RECV SOCKET FAILED 00 Cause Session closed by remote node Action None the driver will try to reconnect Subcode windows errorcodes 0x4007 Name 7TTCP RECV NO MSG Cause Messagepool empty Action Increase number of messages in Driver Setup 0x4008 Name 7TTCP RECV MSG TOO LONG Cause Message longer than 255 bytes received Action Reduce segment size in remote server 0x4009 Name 7TTCP RECV TIMEOUT 0x4009 Cause node has not responded within the specified time Action None driver will retry If the problem persists please contact 7T Support
17. ting an atom and select the 7TTCP interface driver in the Driver drop down list Object Properties test byte Global ma Analog Data Management Definitions Display Layers Edit Mapping Calculation Report Format Symbol Definition Atom PLC Node for object test byte High Alarm High Limit Driver 7TTCP SERVER Zi Actual Value 0 Set Point Node i 7 Low Limit Low Alam PLC Address for Actual Value atom Alam In Alarm Out Data type BYTE m High Scale Low Scale Offset 0 ial Free Value 1 Free Value 2 Free Value 3 Bit Offset Btemaltype FP 16S 1 0 mode in Z Use numeric to scroll to next previous atom Alarm Details Delete Now select the desired PLC node number and continue by setting up PLC device addressing Remember to specify the number register number within the device type rTTOP Schneider Generic TCP IP Driver iP E ectric Note that the corresponding Mnemonic is displayed and updated as you select the appropriate parameters This is a help to make sure you always bind to the correct process variable Continue this process for each atom on the object and save the parameters by clicking the OK button when finished Format of messages The driver is using following data format for sending and receiving mes
Download Pdf Manuals
Related Search