1. Manuals
  2. Brands
  3. SMC Sierra Monitor Manuals
  4. Server
  5. FS-8704-14
  6. Driver manual

SMC Sierra Monitor FS-8704-14 Driver Manual

Fieldserver ethernet/ip
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
FieldServer
FS-8704-14 EtherNet/IP
Driver Manual
(Supplement to the FieldServer Instruction Manual)
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 2018.
Driver Version:
1.12
Document Revision: 4.D

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FS-8704-14 and is the answer not in the manual?

Questions and answers

Related Manuals for SMC Sierra Monitor FS-8704-14

Summary of Contents for SMC Sierra Monitor FS-8704-14

  • Page 1 FieldServer FS-8704-14 EtherNet/IP Driver Manual (Supplement to the FieldServer Instruction Manual) APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after May 2018. Driver Version: 1.12 Document Revision: 4.D...
  • Page 2 EtherNet/IP Driver Manual Technical Support Please call us for any technical support needs related to the FieldServer product. Sierra Monitor Corporation 1991 Tarob Court Milpitas, CA 95035 Website: www.sierramonitor.com U.S. Support Information: +1 408 964-4443 +1 800 727-4377 Email: support@sierramonitor.com EMEA Support Information: +44 2033 1813 41 Email:...

  • Page 3: Table Of Contents

    EtherNet/IP Driver Manual TABLE OF CONTENTS EtherNet/IP desciription ........................5 Driver Scope of Supply ........................5 Supplied by Sierra Monitor Corporation ..................5 Hardware Connections ........................6 Data Array Parameters ........................7 Configuring the FieldServer as an EtherNet/IP Client..............8 Client Side Connection Parameters ....................
  • Page 4 EtherNet/IP Driver Manual Appendix C Vendor Information ......................38 Appendix C.1 ControlLogix ........................38 Appendix C.2 Connection Information – Allen Bradley Message Blocks ..........38 Appendix C.3 FieldServer Not Recognized by RSlinx ................38 Appendix C.4 Using EIP Data_Types with RSLogix ................38 Appendix D Reference ..........................

  • Page 5: Ethernet/Ip Desciription

    EtherNet/IP Driver Manual ETHERNET/IP DESCIRIPTION The EtherNet/IP (EIP) 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.

  • Page 6: Hardware Connections

    EtherNet/IP Driver Manual HARDWARE CONNECTIONS 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 Switch FieldServer Part # 8915-10 UTP cable Connect to an Ethernet Port...

  • Page 7: Data Array Parameters

    EtherNet/IP Driver Manual DATA ARRAY PARAMETERS Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data.

  • Page 8: Configuring The Fieldserver As An Ethernet/Ip Client

    EtherNet/IP Driver Manual CONFIGURING THE FIELDSERVER AS AN ETHERNET/IP CLIENT For detailed information on FieldServer configuration, 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.

  • Page 9: Client Side Node Parameters

    EtherNet/IP Driver Manual Client Side Node Parameters Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Node_Name Provide name for node. characters. IP_Address Address of Server. Any valid address on subnet. Protocol Specify protocol used. EtherNet/IP Adapter Specify port Adapter used.

  • Page 10: Driver Related Map Descriptor Parameters - Unconnected Messages

    EtherNet/IP Driver Manual Driver Related Map Descriptor Parameters – Unconnected Messages 5.3.2 Column Title Function Legal Values EIP_Service The action to be performed. Get_Attrib, Set_Attrib 0-65535, default 0 (refer to EIP_Class Class to be polled. Appendix D.2 for commonly used classes) 0-255, default 0 (refer to EIP_Attribute Attribute associated with the class given.

  • Page 11: Driver Related Map Descriptor Parameters - Data Table Read/Write

    EtherNet/IP Driver Manual Driver Related Map Descriptor Parameters – Data Table Read/W rite 5.3.3 Column Title Function Legal Values Data_Table_Read, EIP_Service The action to be performed. Data_Table_Write EIP_Con_Typ The type of data transfer required. Explicit, UnConnected Any space delimited numerical Used to stipulate the path to the CPU in value.

  • Page 12: Driver Related Map Descriptor Parameters - Pccc

    EtherNet/IP Driver Manual Driver Related Map Descriptor Parameters – PCCC 5.3.4 Column Title Function Legal Values Exec_PCCC (encapsulation EIP_Service Action to be performed. using Allen Bradley PCCC) EIP_Con_Typ The type of data transfer required. Explicit Any space delimited Used to stipulate the path to the CPU in certain numerical value.

  • Page 13: Map Descriptor Example 1: Unconnected Messages

    EtherNet/IP Driver Manual 5.3.7 Map Descriptor Example 1: Unconnected Messages // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name , Scan_Interval , Data_Array_Name , Data_Array_Offset , Function , EIP_Con_Typ , Node_Name , EIP_Class , Address , EIP_Attribute , EIP_Service , Length CMD_PRO_03 , 0s , DA_AI_01 , Rdbc...

  • Page 14: Configuring The Fieldserver As An Ethernet/Ip Server

    EtherNet/IP Driver Manual CONFIGURING THE FIELDSERVER AS AN ETHERNET/IP SERVER For detailed information on FieldServer configuration, 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.

  • Page 15: Server Side Map Descriptor

    EtherNet/IP Driver Manual Server Side Map Descriptor 6.3.1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric Map_Descriptor_Name Name of this Map Descriptor. characters Name of Data Array where data is to be stored One of the Data Array Data_Array_Name in the FieldServer.

  • Page 16: Server Specific Map Descriptor Parameters - Data Table Read/Write

    EtherNet/IP Driver Manual Server Specific Map Descriptor Parameters – Data Table Read/W rite 6.3.3 Column Title Function Legal Values Data_Table_Read, Data_Table_Write NOTE: Separate Map EIP_Service The action to be performed. Descriptors need to be configured for each service. Tag name expressed in PLC program. The data type of this parameter is used to set the data Maximum length...

  • Page 17: Driver Related Map Descriptor Parameters - Pccc

    EtherNet/IP Driver Manual Driver Related Map Descriptor Parameters – PCCC 6.3.4 Column Title Function Legal Values EIP_Con_Typ The type of data transfer required. Explicit EXEC_PCCC EIP_Service Action to be performed. (encapsulation using Allen Bradley PCCC) N Integer F Float O Output File_Type Allen Bradley file type.

  • Page 18: Map Descriptor Example 1: Unconnected Messages

    EtherNet/IP Driver Manual 6.3.6 Map Descriptor Example 1: Unconnected Messages // Server Side Map Descriptors Map_Descriptors Map_Descriptor_Name , Data_Array_Name Data_Array_Offset Function Node_Name EIP_Class Address EIP_Attribute EIP_Service Length SMD_PRO_01 , DA_AI_01 , Passive , EIP_01 , 10 , Get_Attrib SMD_PRO_02 , DA_AI_01 , Passive , EIP_01 , 10 , Get_Attrib...

  • Page 19: Appendix A Useful Features

    EtherNet/IP Driver Manual APPENDIX A USEFUL FEATURES 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 It is possible for the FieldServer to act as a scanner and an adapter at the same time so long as the scanner and adapter are configured on different ports.

  • Page 20: Appendix A.5.1 Fieldserver Configuration File

    EtherNet/IP Driver Manual Appendix A.5.1 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 , Data_Format , Data_Array_Length DA_Read , Float , 100 DA_Write , Float , 100 Server Side Connections...

  • Page 21: Appendix A.5.2 The Plc Program

    EtherNet/IP Driver Manual Appendix A.5.2 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 Avoid using UDT Types.
  • Page 22 EtherNet/IP Driver Manual 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.

  • Page 23: Appendix A.6 Configuring A Fieldserver To Read/Write Data To/From A Plc With Explicit Messaging

    EtherNet/IP Driver Manual Appendix A.6 Configuring a FieldServer to Read/Write Data to/from a PLC with Explicit Messaging 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.

  • Page 24: Appendix A.6.1 Fieldserver Configuration File

    EtherNet/IP Driver Manual Appendix A.6.1 FieldServer Configuration File Data Arrays Data_Arrays Data_Array_Name , Data_Format , Data_Array_Length DA_Read , Float , 50 DA_Write , Float , 50 Client Side Connections Connections Adapter , Protocol , EtherNet/IP These are the PLC Tag names that will Client Side Nodes be accessed in the PLC.

  • Page 25: Appendix A.6.2 The Plc Program

    EtherNet/IP Driver Manual Appendix A.6.2 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. Tag Length must be equal to or greater than the Avoid Using UDT Types.
  • Page 26 EtherNet/IP Driver Manual Example: Consider a situation where a customer defines a type in RSlogix SSS_SINT3 with 3 members of each type SINT. SSS_SINT3 SINT room1_temp SINT room2_temp SINT room3_temp Now he has his own type SSS_SINT3 and he can define tags: TAG_3ROOM_TEMPS of type SSS_SINT3 // Read/write structures Map_Descriptors Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , EIP_CON_TYP , Node_Name , EIP_SERVICE...

  • Page 27: Appendix A.8 Implicit Messaging

    EtherNet/IP Driver Manual Appendix A.8 Implicit Messaging Appendix A.8.1 Configuring a PLC to Read and W rite D ata to and from the FieldServer Implicit messaging uses the User Datagram Protocol (UDP/IP) to produce/consume data over the EtherNet/IP network. Implicit messages are not regular poll/response messages. Implicit connections are time critical, scheduled and use a requested packet interval (RPI) to specify the rate at which data updates.

  • Page 28: Appendix A.8.1.1 Fieldserver Configuration File

    EtherNet/IP Driver Manual Appendix A.8.1.1 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 , Data_Format , Data_Array_Length DA_INPUTS , Uint16 , 100 DA_OUTPUTS , Uint16 , 100 Server Side Connections...

  • Page 29: Appendix A.8.1.2 The Plc Setup

    EtherNet/IP Driver Manual Appendix A.8.1.2 The PLC Setup The PLC (192.168.1.60) should be connected to the FieldServer (192.168.1.24). To start Implicit Communications, use the following 3 steps: • Add a “Generic Ethernet Module”. • Configure the Connection Parameters as per the screenshot below. •...

  • Page 30: Appendix A.8.2 Eds Aop

    EtherNet/IP Driver Manual Appendix A.8.2 EDS AOP Use Studio 5000 Logix Designer to do the following: Choose the device to add to a project, the AOP, pick the implicit I/O sizes and the I/O SINT arrays. Page 30 of 42...
  • Page 31 EtherNet/IP Driver Manual Page 31 of 42...
  • Page 32 EtherNet/IP Driver Manual Page 32 of 42...

  • Page 33: Appendix A.9 Configuring The Plc With A Fieldserver Eds File

    EtherNet/IP Driver Manual Appendix A.9 Configuring the PLC with a FieldServer EDS File 1. Save the fserver.eds file on the local PC. 2. Launch Studio5000. 3. Click on the Tools dropdown menu and select the EDS Hardware Installation Tool. 4. Follow the instructions and select the fserver.eds file. 5.
  • Page 34 EtherNet/IP Driver Manual 6. Select the “FieldServer EIP Adapter” entry and press the Create button. 7. On the General tab, specify the module name (any string) and enter the IP Address of the FieldServer. Then press the Change button under the “Module Definition” heading. Page 34 of 42...
  • Page 35 EtherNet/IP Driver Manual 8. In the Module Definition window, click on the “SINT” dropdown menu and select the correct format to match the size/format of the FieldServer configuration. NOTE: By default, Studio5000 will create tags in SINT format. 9. Click on the numbers under the Size header to change the size. 10.
  • Page 36 EtherNet/IP Driver Manual 11. Once all desired settings are configured in the New Module window, click OK. This will create the FieldServer module under the Ethernet tree. And Studio5000 will create the corresponding tags. 12. Finally, download the project to the PLC. Page 36 of 42...

  • Page 37: Appendix B Troubleshooting

    EtherNet/IP Driver Manual APPENDIX B TROUBLESHOOTING 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.

  • Page 38: Appendix C Vendor Information

    EtherNet/IP Driver Manual APPENDIX C VENDOR INFORMATION Appendix C.1 ControlLogix If EIP Error Code 100 is experienced when using a ControlLogix PLC Message block to read and write data to and from the FieldServer, it may be possible to resolve this error by choosing to cache the connection in the message block settings.

  • Page 39: Appendix D Reference

    EtherNet/IP Driver Manual APPENDIX D REFERENCE Appendix D.1 Error Messages Message Description "EIP:#01 FYI. %d out of %d data If the number of data elements exceeds the Map Descriptor length elements will be stored" only the number of data elements corresponding to the Map "MD=%s, data_type=0x%04X, Descriptor will be stored.
  • Page 40 EtherNet/IP Driver Manual FieldServer Data Type Description (or Device Data Type) Attributes Supported Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Services Supported Two instances supported (0x01 and 0x02) Register – Class Code 0x07 Get_Attribute_Single Attributes List: • Status Flag •...

  • Page 41: Appendix D.3 Error Codes

    EtherNet/IP Driver Manual Appendix D.3 Error Codes General Extended Description Status Status 0x01 0x0100 Connection in Use or Duplicate Forward Open. 0x01 0x0103 Transport Class and Trigger combination not supported. 0x01 0x0106 Ownership conflict 0x01 0x0107 Connection not found at target application. Invalid Connection Type.
  • Page 42 EtherNet/IP Driver Manual General Extended Description Status Status Invalid connection number specified by the Get_Connection_Data service. This is 0x03 also returned by the Search_Connection_Data service if the specified connection is not found. Segment Type in path is invalid. The Extended Status shall be the word offset (0 based) to the word in the path where the error occurred.

Table of Contents