Chipkin.com

Navigation
CAS Modbus TCP Parser.

Have you ever needed to analyze a series of Modbus TCP message?
CAS Modbus TCP Parser

CAS Modbus RTU Parser.

Have you ever needed to analyze a Modbus RTU message?
CAS Modbus RTU Parser

CAS BACnet Explorer

Do you want to know more about your BACnet device on your network ?
CAS BACnet Explorer

Subscribe to our Newsletter
Name
E-mail Address

FS-8704-14 - EtherNet/IP

Up one level

 

FieldServer Driver - Ethernet

FS-8704-14

EtherNet/IP

 
  Text Box: Driver Version: 1.02

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.  EtherNet/IP then makes use of standard Ethernet and TCP/IP technology to transport CIP communications packets.  The result is a common, open application layer on top of open and highly popular Ethernet and TCP/IP protocols.

 

The Driver is able to read/write using the Data Table structure employed by all Logix Series PLC’s.

 

PCCC support is also provided for legacy devices that do not fully support CIP encapsulation.  EIP PCCC Encapsulation was tested at FST factory using PLC5 I785 ENET card.  The following data types were tested:

N

F

S

ODVA Status.

ODVA is an international association comprised of members from the world's leading automation companies.  Collectively, ODVA and its members support network technologies based on the Common Industrial Protocol (CIP™).  These currently include DeviceNet™, EtherNet/IP™, CIP Safety™ and CIP Sync™.  ODVA manages the development of these open technologies, and assists manufacturers and users of CIP-based networks through tools, training and marketing activities.

 

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”

 

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.

 

The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

 

Fieldserver Mode

Nodes

Comments

Client

1

Only 1 Client Node allowed.

Server

32

32 Server Nodes allowed.

Formal Driver Type

Ethernet

Client or Server

Compatibility Matrix

FieldServer Model

Compatible with this driver

FS-X2010

Yes

FS-X2011

Yes

FS-X25

Yes

FS-X30

Yes

FS-X40

Yes

ProtoCessor

Yes

 

Connection Information

Connection type:

Ethernet

Ethernet Speeds Supported

10Base-T, 100Base-T[1]

 

Devices tested

Device

Tested (FACTORY, SITE)

ODVA Conformance Tool (ENetCT Ver A3.5)

FACTORY

FlexLogix PLC/ 1788 - Enet  Ethernet Card

FACTORY

Wago 750-841 Programmable Fieldbus Coupler

FACTORY

Connection configurations

 

 

 

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

Description (or Device Data Type)

Identity – Class Code 0x01

Attributes Supported:

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)

Services Supported:

Get_Attribute_All

Get_Attribute_Single

Message Router – Class Code 0x02

Attributes Supported:

One instance supported (0x01)

Attribute List:

  1. Max Connections

Services Supported:

Get_Attribute_Single

Assembly – Class Code 0x04

Attributes Supported:

Class Instance Support (0x00)

Class Attributes: 0x02 (Max Instance)

Two instances supported (0x0100 and 0x0101)

Attribute List:

  1. Member List
  2. Not Supported
  3. Data

Services Supported:

Get_Attribute_Single

Connection Manager – Class Code 0x06

Forward Open Service

Forward Close Service

Register – Class Code 0x07

Attributes Supported:

Class Instance Support (0x00)

Class Attributes: 0x02 (Max Instance)

Two instances supported (0x01 and 0x02)

Attribute List:

  1. Status Flag
  2. Direction (read/write)
  3. Size of Data (bits)

Services Supported:

Get_Attribute_Single

Discrete Input Point – Class Code 0x08

No visible interface currently

Discrete Output Point – Class Code 0x09

No visible interface currently

Analog Input Point – Class Code 0x0A

Attributes Supported:

Class Instance Support (0x00)

Class Attributes: 0x02 (Max Instance)

Two instances supported (0x01 and 0x02)

Attribute List:

  1. Number of Attributes
  2. Not Supported
  3. Analog value (UINT16)
  4. not supported
  5. Vendor ID

Services Supported:

Get_Attribute_Single

Analog Output Point – Class Code 0x0B

Attributes Supported:

Class Instance Support (0x00)

Class Attributes: 0x02 (Max Instance)

Two instances supported (0x01 and 0x02)

Attribute List:

  1. Number of Attributes
  2. not supported
  3. Analog value (UINT16)
  4. not supported
  5. Vendor ID

Services Supported:

Set_Attribute_Single

Get_Attribute_Single

TCP/IP Interface Object – Class Code 0xF5

Attributes Supported:

One instance supported (0x01)

Attribute List:

  1. Status
  2. Configuration Capability
  3. Configuration Control
  4. Physical Link Object
  5. Interface Configuration
  6. Host Name

Services Supported:

Get_Attribute_Single

EtherNet Link Object – Class Code 0xF6

Attributes Supported:

One instance supported (0x01)

Attribute List:

  1. Interface Speed
  2. Interface Flags
  3. Physical Address
  4. Interface Counters
  5. Media Counters

Services Supported:

Get_Attribute_Single

Data Table Object – Private Object

Attributes Supported:

This object does not support instances or attributes but uses the data table structure, and associated tags, in Logix5000 PLC’s.

Services Supported:

CIP Read Data

Connection Types Supported

Connection Type

Support Details

Unconnected Messages

Unconnected messages are supported to objects mentioned above.

Explicit Messages

Both client and server support Explicit Messages to all supported objects.

Implicit Messages

Implicit Messages are not currently supported.


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)

FieldServer as a Server (Adapter)

Get_Attribute_Single – Service Code 0x0E

Get_Attribute_Single – Service Code 0x0E

Data_Table_Read – Service Code 0x4C

Get_Attribute_All – Service Code 0x01

 

Data_Table_Read – Service Code 0x4C

 

Write (Control) Operations supported

FieldServer as a Client (Scanner)

FieldServer as a Server (Adapter)

Set_Attribute_Single – Service Code 0x10

Set_Attribute_Single – Service Code 0x10

Data_Table_Write – Service Code 0x4D

Data_Table_Write – service code 0x4D

Unsupported Functions and Data Types

Function

Reason

Programming messages

FieldServer is a data transfer device, and as such, programming messages are not required.

All Group Functions. (e.g. Analog Input Group Object)

Possibility of later support.

All Application Specific Data Objects (e.g. AC/DC Drive Object)

Possibility of later support.

 


[1] Not all FieldServer models support 100BaseT.  Consult the appropriate instruction manual for details of the Ethernet speed supported by specific hardware.