FieldServer Driver - Ethernet FS EtherNet/IP

Transcription

1 FieldServer Driver - Ethernet FS EtherNet/IP Description The EtherNet/IP driver allows the FieldServer to transfer data to and from an EtherNet/IP enabled device. This driver encapsulates the Control and Information Protocol (CIP). CIP is a peer to peer object orientated protocol that provides connection between industrial devices and higher level devices. The driver can act as both a client and server. Fieldserver Mode Nodes Comments Client 1 Only 1 Client Node allowed. Server Server Nodes allowed. Note: It is possible for the FieldServer to act as a scanner and an adapter at the same time so long as they are configured on different ports. Consequently this functionality is not possible on an FS- X20 platform. ODVA status FieldServer Technologies is an ODVA member and our device is ODVA tested to be Ethernet/IP Compliant. Vendor Code 875 Product Type Code 12 or Communications Adapter EIP PCCC Encapsulation Tested at FST factory using PLC5 I785 ENET card. Following data types tested: N F S Formal Driver Type Ethernet Client or Server Driver Version: 1.00 Document Revision: 16 Page 1 of 8

2 Compatibility Matrix FieldServer Model FS-X2010 FS-X2011 FS-X40 Compatible with this driver Yes Yes Yes Connection Information Connection type: Ethernet Ethernet Speeds Supported 10Base-T, 100Base-T 1 Devices tested Device ODVA Conformance Tool (ENetCT Ver A3.5) FlexLogix PLC/ Enet Ethernet Card Wago Programmable Fieldbus Coupler Tested (FACTORY, SITE) FACTORY FACTORY FACTORY 1 Not all FieldServer models support 100BaseT. Consult the appropriate instruction manual for details of the Ethernet speed supported by specific hardware. Page 2 of 8

3 Connection configurations Controller SITE ETHERNET FS Ethernet Interface FS (408) FIELDSERVER BACNET ETHERNET CONNECTION DIAGRAM BASE NAME: FILE NAME: FS DATE: 6/29/04 BY: MC Page 3 of 8

4 Communications functions - Supported functions at a glance: 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. Data Types Supported FieldServer Data Type Identity Class Code 0x01 Message Router Class Code 0x02 Assembly Class Code 0x04 Connection Manager Class Code 0x06 Description (or Device Data Type) One instance supported (0x01) Attributes List: 1. Vendor ID 2. Device Type 3. Product Code 4. Device Revision 5. Status 6. Serial Number 7. Device Description (text) Get_Attribute_All One instance supported (0x01) 1. Max Connections Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Two instances supported (0x0100 and 0x0101) 1. Member List 2. Not Supported 3. Data Forward Open Service Forward Close Service Page 4 of 8

5 FieldServer Data Type Register Class Code 0x07 Discrete Input Point Class Code 0x08 Discrete Output Point Class Code 0x09 Analog Input Point Class Code 0x0A Analog Output Point Class Code 0x0B Description (or Device Data Type) Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Two instances supported (0x01 and 0x02) 4. Status Flag 5. Direction (read/write) 6. Size of Data (bits) No visible interface currently No visible interface currently Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Two instances supported (0x01 and 0x02) 1. Number of Attributes 2. Not Supported 3. Analog value (UINT16) 4. not supported 5. Vendor ID Class Instance Support (0x00) Class Attributes: 0x02 (Max Instance) Two instances supported (0x01 and 0x02) 1. Number of Attributes 2. not supported 3. Analog value (UINT16) 4. not supported 5. Vendor ID Set_Attribute_Single Page 5 of 8

6 FieldServer Data Type TCP/IP Interface Object Class Code 0xF5 EtherNet Link Object Class Code 0xF6 Data Table Object Private Object Description (or Device Data Type) One instance supported (0x01) 1. Status 2. Configuration Capability 3. Configuration Control 4. Physical Link Object 5. Interface Configuration 6. Host Name One instance supported (0x01) 1. Interface Speed 2. Interface Flags 3. Physical Address 4. Interface Counters 5. Media Counters This object does not support instances or attributes but uses the data table structure, and associated tags, in Logix5000 PLC s. CIP Read Data Connection Types Supported Connection Type Unconnected Messages Explicit Messages Implicit Messages Support Details Unconnected messages are supported to objects mentioned above. Both client and server support Explicit Messages to all supported objects. Implicit Messages are not currently supported. Page 6 of 8

7 Read Operations supported The functions below are supported to varying degrees by the objects above. The exact support for functions is mentioned in the table above. FieldServer as a Client (Scanner) Service Code 0x0E Data_Table_Read Service Code 0x4C FieldServer as a Server (Adapter) Service Code 0x0E Get_Attribute_All Service Code 0x01 Data_Table_Read Service Code 0x4C Write (Control) Operations supported FieldServer as a Client (Scanner) Set_Attribute_Single Service Code 0x10 Data_Table_Write Service Code 0x4D FieldServer as a Server (Adapter) Set_Attribute_Single Service Code 0x10 Data_Table_Write service code 0x4D Unsupported Functions and Data Types Function Programming messages All Group Functions. (e.g. Analog Input Group Object) All Application Specific Data Objects (e.g. AC/DC Drive Object) PCCC support Reason FieldServer is a data transfer device, and as such, programming messages are not required. Possibility of later support. Possibility of later support. PCCC encapsulation (for PLC5 and SLC) is currently unsupported in this driver. Page 7 of 8

8 THIS PAGE INTENTIONALLY LEFT BLANK. Page 8 of 8