A Sierra Monitor Company Driver Manual (Supplement to the FieldServer Instruction Manual) FS-8704-14 EtherNet/IP APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after January 2009 Driver Version: Document Revision: 1.
FS-8704-14 EtherNet/IP Manual Table of Contents TABLE OF CONTENTS 1 EtherNet/IP Description ................................................................................................................................. 4 1.1 ODVA Status...................................................................................................................................................4 2 Driver Scope of Supply ..............................................................................................
FS-8704-14 EtherNet/IP Manual Table of Contents Appendix B. Troubleshooting Tips ....................................................................................................................... 29 Appendix B.1. Firmware Update Downloading .......................................................................................................29 Appendix B.2. Connection information – Allen Bradley Message Blocks ................................................................29 Appendix B.3.
FS-8704-14 EtherNet/IP Manual 1 Page 4 of 30 ETHERNET/IP DESCRIPTION The Ethernet IP driver allows the FieldServer to transfer data to and from devices over Ethernet using the EtherNet/IP protocol. The FieldServer can emulate either a Server or Client. EtherNet/IP uses CIP (Control and Information Protocol), the common network, transport and application layers also shared by ControlNet and DeviceNet.
FS-8704-14 EtherNet/IP Manual 3 Page 5 of 30 HARDWARE CONNECTIONS 1 It is possible to connect an EtherNet/IP device to either port N1 or N2 on the FieldServer. These ports must just be configured to use EtherNet/IP in the configuration file. Remote Ethernet/IP Device Hub/Router FieldServer Part # 8915-10 UTP cable Connect to an Ethernet Port on the FieldServer 8 1 FieldServer N1 1 Not all ports shown are necessarily supported by the hardware.
FS-8704-14 EtherNet/IP Manual 4 Page 6 of 30 CONFIGURING THE FIELDSERVER AS AN ETHERNET/IP CLIENT For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer. This section documents and describes the parameters necessary for configuring the FieldServer to communicate with an EtherNet/IP Server. 4.
FS-8704-14 EtherNet/IP Manual 4.2 Page 7 of 30 Client Side Connection Descriptions Section Title Adapter Column Title Adapter Protocol Example Function Adapter Name Specify protocol used Legal Values 2 N1, N2 EtherNet/IP // Client Side Connections Adapters Adapter N1 4.
FS-8704-14 EtherNet/IP Manual 4.4 Page 8 of 30 Client Side Map Descriptors 4.4.
FS-8704-14 EtherNet/IP Manual Page 9 of 30 4.4.3 Driver Related Map Descriptor Parameters – Data Table Read/Write. Column Title Function EIP_Service The action to be performed. EIP_Con_Typ The type of data transfer required. EIP_Path * EIP_Tag_Name EIP_Data_Type* Length EIP_Structure_Handle* Used to stipulate the path to the CPU in certain PLC’s. Paths vary and are dependent on the structure of the network. Tag name expressed in PLC program.
FS-8704-14 EtherNet/IP Manual Page 10 of 30 4.4.4 Driver Related Map Descriptor Parameter s – PCCC Column Title Function EIP_Service Action to be performed EIP_Con_Typ The type of data transfer required EIP_Path * Used to stipulate the path to the CPU in certain PLC’s. Paths vary and are dependent on the structure of the network. File_Type Allen Bradley file type File_Number Allen Bradley file number Number of data elements to be mapped.
FS-8704-14 EtherNet/IP Manual Page 11 of 30 4.4.6 Map Descriptor Example 1: Unconnected Messages // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name CMD_PRO_03 CMD_PRO_02 ,Scan_Interval ,0s ,0s ,Data_Array_Name ,DA_AI_01 ,DA_AI_01 ,Data_Array_Offset ,0 ,1 ,Function ,Rdbc ,Rdbc ,EIP_Con_Typ ,Unconnected ,Unconnected ,Node_Name ,EIP_01 ,EIP_01 ,EIP_Class ,10 ,10 , ,Address ,1 ,2 ,EIP_Attribute ,3 ,3 ,EIP_Service ,Get_Attrib ,Get_Attrib ,Length ,1 ,1 4.4.
FS-8704-14 EtherNet/IP Manual 5 Page 12 of 30 CONFIGURING THE FIELDSERVER AS AN ETHERNET/IP SERVER For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer. This section documents and describes the parameters necessary for configuring the FieldServer to communicate with an EtherNet/IP Client.
FS-8704-14 EtherNet/IP Manual 5.2 Page 13 of 30 Server Side Node Descriptors 3 Section Title Nodes Column Title Function Node_Name Provide name for Node Protocol Specify protocol used Specifies time FieldServer will reserve server side connection while waiting for the Client side to update data. Server_Hold_Timeout* Legal Values Up to 32 alphanumeric characters EtherNet/IP >1.0s Example // Server Side Nodes Nodes Node_Name EIP_01 5.3 ,Protocol ,EtherNet/IP Server Side Map Descriptors 5.3.
FS-8704-14 EtherNet/IP Manual Page 14 of 30 5.3.2 Server Specific Map Descriptor Parameters – Unconnected Messages Column Title EIP_Service Function The action to be performed. EIP_Class Class to be served. EIP_Attribute Attribute associated with the class served. Length Number of data elements to be mapped. If the number of data elements exceeds the Map Descriptor length, the list of data elements will be truncated and an error message will be printed once per Map Descriptor.
FS-8704-14 EtherNet/IP Manual Page 15 of 30 5.3.4 Driver Related Map Descriptor Parameter s – PCCC Column Title EIP_Con_Typ Function The type of data transfer required EIP_Service Action to be performed File_Type Allen Bradley file type File_Number Allen Bradley file number Number of data elements to be mapped. If the number of data elements exceeds the Map Descriptor length, the list of data elements will be truncated and an error message will be printed once per Map Descriptor.
FS-8704-14 EtherNet/IP Manual Page 16 of 30 5.3.5 Map Descriptor Example 1: Unconnected Messages // Server Side Map Descriptors Map_Descriptors Map_Descriptor_Name SMD_PRO_01 SMD_PRO_02 ,Data_Array_Name ,DA_AI_01 ,DA_AI_01 ,Data_Array_Offset ,0 ,1 ,Function ,Server ,Server ,Node_Name ,EIP_01 ,EIP_01 ,EIP_Class ,10 ,10 ,Address ,1 ,2 ,EIP_Attribute ,3 ,3 ,EIP_Service ,Get_Attrib ,Get_Attrib ,Length ,1 ,1 5.3.
FS-8704-14 EtherNet/IP Manual Page 17 of 30 Appendix A. Advanced Topics Appendix A.1. General Notes The connection type does not need to be specified in the Server side Map Descriptor, but must be stipulated on the Client side of the driver. Data_Table_Read as a service can only be used when creating an explicit connection. Appendix A.2. FieldServer as an Adapter and Scanner.
FS-8704-14 EtherNet/IP Manual Appendix A.5.1. Page 18 of 30 FieldServer Configuration File The configuration file used for this example is configured with the following Connection, Node and Map Descriptor Parameters: // Data Arrays // Data_Arrays Data_Array_Name DA_Read DA_Write ,Data_Format ,Float ,Float ,Data_Array_Length ,100 ,100 // Server Side Connections // Connections Adapter ,Protocol ,Turnaround_delay N1 ,Ethernet/IP ,0.
FS-8704-14 EtherNet/IP Manual Appendix A.5.2. Page 19 of 30 The PLC Program The PLC program example below shows the minimum steps necessary to program communications with the FieldServer. Depending on the real intended application, additional steps may be necessary for completeness. Step 1 Configure Tags in the PLC for storing FieldServer read and write data: Tag Length Must be equal to or greater than the number of points being written/read Avoid Using UDT Types.
FS-8704-14 EtherNet/IP Manual Page 20 of 30 Step 4 Configure the Properties for the two Message Blocks by clicking on the “…” button: Read Message Block: Remote FieldServer Tag Configured in the FieldServer (see example above) Number of points transferred from FieldServer to PLC regardless of Tag and Array Sizes Local PLC Tag configured in the PLC Tag List (see example above) Write Message Block: Local PLC Tag configured in the PLC Tag List (see example above) Number of points transferred from PLC to F
FS-8704-14 EtherNet/IP Manual Page 21 of 30 Appendix A.6. Configuring a FieldServer to read and write Data to and from a PLC. This example makes use of the Data Table Read/Write method for passing data between the FieldServer and an Allen Bradley PLC. The example shows configuration of a ControlLogix PLC, but all RockWell PLC’s that support Ethernet IP communications and Data Table Read/Write operations in Message blocks should be able to communicate this way. .
FS-8704-14 EtherNet/IP Manual Appendix A.6.1. // Data Arrays // Data_Arrays Data_Array_Name DA_Read DA_Write Page 22 of 30 FieldServer Configuration File ,Data_Format ,Float ,Float // Client Side Connections // Connections Adapter N1 // Client Side Nodes // Nodes Node_Name EIP_01 ,Data_Array_Length ,50 ,50 ,Protocol ,Ethernet/IP These are the PLC Tag names that will be accessed in the PLC. The names must match the PLC tag name exactly. ,IP_Address ,192.168.1.
FS-8704-14 EtherNet/IP Manual Appendix A.6.2. Page 23 of 30 The PLC Program The PLC program example below shows the minimum steps necessary to program communications with the FieldServer. Depending on the real intended application, additional steps may be necessary for completeness. When the FieldServer is polling the PLC, all that is needed is to configure the tags being accessed: Avoid Using UDT Types.
FS-8704-14 EtherNet/IP Manual Page 24 of 30 Example: Consider a situation where a customer defines a a type in RSlogix SSS_SINT3 with 3 members of each type SINT.
FS-8704-14 EtherNet/IP Manual Page 25 of 30 Appendix A.8. Classes and Attributes Supported EtherNet/IP is an object orientated protocol. The Object Oriented structure therefore allows for classes, instances, attributes and services. The ‘data types’ listed below are to be considered as the objects supported in the protocol. Each of these has attributes that have been supported to differing degrees.
FS-8704-14 EtherNet/IP Manual FieldServer Data Type Analog Input Point – Class Code 0x0A Analog Output Point – Class Code 0x0B TCP/IP Interface Object – Class Code 0xF5 EtherNet Link Object – Class Code 0xF6 Data Table Object – Private Object Page 26 of 30 Description (or Device Data Type) Attributes Supported: Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Two instances supported (0x01 and 0x02) Attribute List: Number of Attributes Not Supported Analog value (UINT16) not supporte
FS-8704-14 EtherNet/IP Manual Page 27 of 30 Appendix A.9.
FS-8704-14 EtherNet/IP Manual Err Code 0011 0012 0013 0014 0015 001A 001B 001C 001D 001E 001F Extd Err Code 0203 0022 0025 0026 0027 0028 0029 00D1 00FB 00FC 00FD 00FE 00FF 2001 2002 2018 201B 201C 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 210A 210B 210E 210F 2110 2111 2112 2113 2114 Description Reply will not fit Fragment primitive Insufficient command data Attribute not supported Too much data Bridge request too large Bridge response too large Attribute list shortage Invalid attribute list Embe
FS-8704-14 EtherNet/IP Manual Page 29 of 30 Appendix B. Troubleshooting Tips Appendix B.1. Firmware Update Downloading If you are trying to update firmware and continuously get failed messages it might be due to the traffic on the N1 or N2 ports. EtherNet/IP is a high traffic protocol and once a connection is created continuous data transfer occurs. In this situation the best way to download new firmware would be to manually disconnect the scanner or adapter that the FieldServer is connected to.
FS-8704-14 EtherNet/IP Manual Page 30 of 30 Appendix C. Error Messages Message "EIP:#01 FYI. %d out of %d data elements will be stored" "MD=%s, data_type=0x%04X, raw bytes=%d" Description If the number of data elements exceeds the Map Descriptor length only the number of data elements corresponding to the Map Descriptor will be stored. This message will print once per Map Descriptor. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.
