FieldServer FS-8704-14 EtherNet Release note

A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after November 2011
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8704-14 EtherNet/IP
Driver Version:
1.05
Document Revision:
2

FS-8704-14 EtherNet/IP Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
TABLE OF CONTENTS
1EtherNet/IP Description.................................................................................................................................4
1.1 ODVA Status...................................................................................................................................................4
2Driver Scope of Supply ...................................................................................................................................4
2.1 Supplied by FieldServer Technologies for this driver.....................................................................................4
3Hardware Connections................................................................................................................................... 5
4Data Array Parameters...................................................................................................................................6
5Configuring the FieldServer as an EtherNet/IP Client ..................................................................................... 7
5.1 Client Side Connection Descriptions..............................................................................................................7
5.2 Client Side Node Descriptors .........................................................................................................................7
5.3 Client Side Map Descriptors...........................................................................................................................8
5.3.1 FieldServer Related Map Descriptor Parameters ...................................................................................8
5.3.2 Driver Related Map Descriptor Parameters –Unconnected Messages .................................................8
5.3.3 Driver Related Map Descriptor Parameters –Data Table Read/Write. .................................................9
5.3.4 Driver Related Map Descriptor Parameters –PCCC.............................................................................10
5.3.5 Timing Parameters...............................................................................................................................10
5.3.6 Map Descriptor Example 1: Unconnected Messages...........................................................................11
5.3.7 Map Descriptor Example 2: Data Table Messages ..............................................................................11
5.3.8 Map Descriptor Example 3: PCCC Messages........................................................................................11
6Configuring the FieldServer as an EtherNet/IP Server .................................................................................. 12
6.1 Server Side Connection Descriptors ............................................................................................................12
6.2 Server Side Node Descriptors3.....................................................................................................................12
6.3 Server Side Map Descriptors........................................................................................................................13
6.3.1 FieldServer Specific Map Descriptor Parameters .................................................................................13
6.3.2 Server Specific Map Descriptor Parameters –Unconnected Messages ...............................................13
6.3.3 Server Specific Map Descriptor Parameters –Data Table Read/Write................................................14
6.3.4 Driver Related Map Descriptor Parameters –PCCC.............................................................................14
6.3.5 Map Descriptor Example 1: Unconnected Messages...........................................................................15
6.3.6 Map Descriptor Example 2: Data Table Messages ..............................................................................15
6.3.7 Map Descriptor Example 3: PCCC Messages........................................................................................15
Appendix A. Advanced Topics.............................................................................................................................. 16
Appendix A.1. General Notes ..................................................................................................................................16
Appendix A.2. FieldServer as an Adapter and Scanner............................................................................................16
Appendix A.3. Common Paths .................................................................................................................................16
Appendix A.4. Setting the Data Type for stored data. .............................................................................................16
Appendix A.5. Configuring a PLC to read and write data to and from FieldServer..................................................16
Appendix A.5.1. FieldServer Configuration File ................................................................................................17
Appendix A.5.2. The PLC Program ....................................................................................................................18
Appendix A.6. Configuring a FieldServer to read and write Data to and from a PLC. .............................................20
Appendix A.6.1. FieldServer Configuration File ................................................................................................21
Appendix A.6.2. The PLC Program ....................................................................................................................22
Appendix A.7. Read/write structures and value of EIP_Structure_Handle : ...........................................................22
Appendix B. Troubleshooting............................................................................................................................... 24
Appendix B.1. Firmware Update Downloading .......................................................................................................24

FS-8704-14 EtherNet/IP Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
Appendix C. Vendor Information ......................................................................................................................... 25
Appendix C.1. ControlLogix......................................................................................................................................25
Appendix C.2. Connection information –Allen Bradley Message Blocks ................................................................25
Appendix C.3. FieldServer not recognised by RSlinx................................................................................................25
Appendix D. Reference ........................................................................................................................................ 26
Appendix D.1. Error Messages.................................................................................................................................26
Appendix D.2. Classes and Attributes Supported ....................................................................................................26
Appendix D.3. Error Codes.......................................................................................................................................29

FS-8704-14 EtherNet/IP Manual Page 4 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
1ETHERNET/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. 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 the FST factory using a PLC5 I785 ENET card. The following data types were tested:
N
F
S
The Driver also supports PCCC communication on SLC and MicroLogix (Tested on MicroLogix 1400 Device)
Fragmented Services (0x52) is not supported by this driver.
The information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer.
1.1 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”
2DRIVER SCOPE OF SUPPLY
2.1 Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
Description
FS-8915-10
UTP cable (7 foot) for Ethernet connection
FS-8704-14
Driver Manual

FS-8704-14 EtherNet/IP Manual Page 5 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
3HARDWARE CONNECTIONS
It is possible to connect an EtherNet/IP device to either port N1 or N21on the FieldServer. These ports must just
be configured to use EtherNet/IP in the configuration file.
FieldServer
FieldServer Part #
8915-10
UTP cable
Connect to an Ethernet Port
on the FieldServer
N1
18
Hub/Router
Remote Ethernet/IP
Device
1Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.

FS-8704-14 EtherNet/IP Manual Page 6 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
4DATA 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.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Data_Array_Name
Provide name for Data Array
Up to 15
alphanumeric
characters
Data_Array_Format
Provide data format. Each Data Array can only take on one
format.
FLOAT, BIT, UInt16,
SInt16, Byte.
Data_Array_Length
Number of Data Objects. Must be larger than the data storage
area required by the Map Descriptors for the data being placed in
this array.
1-10, 000
Example
// Data Arrays
Data_Arrays
Data_Array_Name
, Data_Array_Format
, Data_Array_Length
DA_AI_01
, UInt16
, 200
DA_AO_01
, UInt16
, 200
DA_DI_01
, Bit
, 200
DA_DO_01
, Bit
, 200

FS-8704-14 EtherNet/IP Manual Page 7 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
5CONFIGURING 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.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for EtherNet/IP communications, the driver independent FieldServer buffers need to be declared in
the “Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section,
and the data required from the servers needs to be mapped in the “Client Side Map Descriptors” section. Details
on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
5.1 Client Side Connection Descriptions
Section Title
Adapter
Column Title
Function
Legal Values
Adapter
Adapter Name
N1, N22
Protocol
Specify protocol used
EtherNet/IP
Example
// Client Side Connections
Adapters
Adapter
, Protocol
N1
, EtherNet/IP
5.2 Client Side Node Descriptors3
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for node
Up to 32 alphanumeric characters
IP_Address
Address of Server
Any valid address on subnet
Protocol
Specify protocol used
EtherNet/IP
Adapter
Specify port Adapter used
N1, N22
Plc_Type*
Specify the type of remote PLC. Only
required for PCCC Services
MicroLogix, SLC5, PLC5
2Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
3Only one explicit connection is created per node. All explicit Map Descriptors attached to that node will use the same explicit connection.

FS-8704-14 EtherNet/IP Manual Page 8 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
Example
// Client Side Nodes
Nodes
Node_Name
, IP_Address
, Adapter
, Protocol
PLC 1
, 192.168.1.174
, N1
, EtherNet/IP
5.3 Client Side Map Descriptors
5.3.1 FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Map_Descriptor_Name
Name of this Map Descriptor
Up to 32 alphanumeric characters
Data_Array_Name
Name of Data Array where data is to be
stored in the FieldServer
One of the Data Array names from
Section 4
Data_Array_Offset
Starting location in Data Array
0 to (Data_Array_Length -1) as specified
in Section 4.
Function
Function of Client Map Descriptor
Rdbc, Wrbc, Wrbx
5.3.2 Driver Related Map Descriptor Parameters –Unconnected Messages
Column Title
Function
Legal Values
EIP_Service
The action to be performed.
Get_Attrib, Set_Attrib
EIP_Class
Class to be polled.
One of the classes supported by
the driver. Refer to Appendix A.4
EIP_Attribute
Attribute associated with the class given.
See particular attributes of each
class. Refer to Appendix A.4
EIP_Con_Typ
The type of data transfer required. Also referred to as the
“Transport Method”
Unconnected
Explicit
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.
Any space delimited numerical
value. Refer to vendor’s device
documentation. Also see
Appendix A.3, 0 0
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. Refer to Appendix D for
further information.
For any given Map Descriptor
there can be 200 Floats, 400
Integers or 800 Bytes
Address
Instance of the class to be polled.
Depends on the supported
instances for each class.

FS-8704-14 EtherNet/IP Manual Page 9 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
5.3.3 Driver Related Map Descriptor Parameters –Data Table Read/Write.
Column Title
Function
Legal Values
EIP_Service
The action to be performed.
Data_Table_Read,
Data_Table_Write
EIP_Con_Typ
The type of data transfer required.
Explicit
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.
Any space delimited
numerical value. Refer to
vendor’s device
documentation. Also see
Appendix A.3, 0 0
EIP_Tag_Name
Tag name expressed in PLC program. The data type of
this parameter is used to set the data format of the Data
Array if the EIP_DATA_TYPE parameter is not specified.
Maximum length 48
characters.
EIP_Data_Type*
If the parameter is specified, the data will be stored in
the specified format which may be different to the
format of the tag being polled. If the parameter is not
set, the Data Type of the Data Array will be used. This
parameter is only applicable to Data Table Write when
FieldServer is the Client. The Data Type of the Data
Array will be used for Data Table Reads when the
FieldServer is the Client. Refer to Appendix A.4 for more
information.
Float, Uint16, Uint32, Bit,
Byte, Boolean, -
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. See
Appendix D for further information.
For any given Map
Descriptor there can be 200
Floats, 400 Integers or 800
Bytes
EIP_Structure_Handle*
This parameter is required to read/write structures. The
driver supports read/write structures having members of
same type, i.e. all members are of type Byte, UINT16,
UINT32 or Float etc
When this parameter is defined, the number of structure
members must be specified as the length of the Map
Descriptor. Refer to Appendix A.7 for more information.
Any 16bit Integer number
(e.g. 59592), 0

FS-8704-14 EtherNet/IP Manual Page 10 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
5.3.4 Driver Related Map Descriptor Parameters –PCCC
Column Title
Function
Legal Values
EIP_Service
Action to be performed
Exec_PCCC (Encapsulation using
Allen Bradley PCCC)
EIP_Con_Typ
The type of data transfer required
Explicit
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.
Any space delimited numerical
value. Refer to vendor’s device
documentation. Also see
Appendix A.3, 0 0
File_Type
Allen Bradley file type
N Integer
F Float
O Output
B Boolean
I Input
S Status
File_Number
Allen Bradley file number
Any valid numerical value
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. Refer to Appendix D for
further information.
For any given Map Descriptor
there can be 200 Floats, 400
Integers or 800 Bytes
Address
Address in the file
Any valid numerical value
between 0 to 255
5.3.5 Timing Parameters
Column Title
Function
Legal Values
Scan_Interval
Rate at which data is polled
≥0.001s

FS-8704-14 EtherNet/IP Manual Page 11 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: supp[email protected]
5.3.6 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
, 0
, Rdbc
, Unconnected
, EIP_01
, 10
, 1
, 3
, Get_Attrib
, 1
CMD_PRO_02
, 0s
, DA_AI_01
, 1
, Rdbc
, Unconnected
, EIP_01
, 10 ,
, 2
, 3
, Get_Attrib
, 1
5.3.7 Map Descriptor Example 2: Data Table Messages
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Scan_Interval
, Data_Array_Name
, Data_Array_Offset
, EIP_Con_Typ
, Node_Name
, Function
, EIP_Service
, EIP_Path
, EIP_Tag_Name
, Length
Cmd_Pro_09
, 0s
, DA_AI_05
, 0
, Explicit
, EIP_01
, Rdbc
, Data_Table_Read
, 1 1
, analog_in_3
, 2
Cmd_Pro_10
, 0s
, DA_AI_06
, 0
, Explicit
, EIP_01
, Rdbc
, Data_Table_Read
, 1 1
, analog_in_4
, 2
5.3.8 Map Descriptor Example 3: PCCC Messages
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset,
, Function
, EIP_Con_Typ
, Node_Name
, EIP_Service
, EIP_Path
, File_Type
File_Number
, Address
, Length
CMD_01
, DA_F_01
, 0,
, Rdbc
, Explicit
, EIP_01
, Exec_PCCC
, 1 0
, F
8,
, 30
, 10

FS-8704-14 EtherNet/IP Manual Page 12 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
6CONFIGURING 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.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for EtherNet/IP communications, the driver independent FieldServer buffers need to be declared in
the “Data Arrays” section, the FieldServer virtual node(s) needs to be declared in the “Server Side Nodes” section,
and the data to be provided to the Client needs to be mapped in the “Server Side Map Descriptors” section.
Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
6.1 Server Side Connection Descriptors
Section Title
Connections
Column Title
Function
Legal Values
Adapter
Adapter Name
N1, N24
Protocol
Specify protocol used
EtherNet/IP
Example
// Server Side Connections
Adapters
Adapter
, Protocol
N1
, EtherNet/IP
6.2 Server Side Node Descriptors3
Section Title
Nodes
Column Title
Function
Legal Values
Node_Name
Provide name for Node
Up to 32 alphanumeric
characters
Protocol
Specify protocol used
EtherNet/IP
Server_Hold_Timeout*
Specifies time FieldServer will reserve server side connection
while waiting for the Client side to update data.
>1.0s
4Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.

FS-8704-14 EtherNet/IP Manual Page 13 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
Example
// Server Side Nodes
Nodes
Node_Name
, Protocol
EIP_01
, EtherNet/IP
6.3 Server Side Map Descriptors
6.3.1 FieldServer Specific Map Descriptor Parameters
Column Title
Function
Legal Values
Map_Descriptor_Name
Name of this Map Descriptor
Up to 32 alphanumeric
characters
Data_Array_Name
Name of Data Array where data is to be stored in the
FieldServer
One of the Data Array names
from Section 4
Data_Array_Offset
Starting location in Data Array
0 to (Data_Array_Length -1)
as specified in Section 4.
Function
Function of Server Map Descriptor
Passive
Server_Hold_Timeout*
Specifies the length of time that the FieldServer will
reserve the Server side connection while waiting for
the Client side to update data in Data Array (if
necessary)
>1.0s
6.3.2 Server Specific Map Descriptor Parameters –Unconnected Messages
Column Title
Function
Legal Values
EIP_Service
The action to be performed.
Get_Attrib, Set_Attrib
EIP_Class
Class to be served.
One of the classes
supported by the driver. .
Refer to Appendix A.4
EIP_Attribute
Attribute associated with the class served.
See particular attributes
of each class. Refer to
Appendix A.4
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. Refer to Appendix D for further
information.
For any given Map
Descriptor there can be
200 Floats, 400 Integers or
800 Bytes
Address
Instance of the class to be served.
Depends on the
supported instances for
each class.

FS-8704-14 EtherNet/IP Manual Page 14 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
6.3.3 Server Specific Map Descriptor Parameters –Data Table Read/Write.
Column Title
Function
Legal Values
EIP_Service
The action to be performed.
Data_Table_Read,
Data_Table_Write
EIP_Tag_Name
Tag name expressed in PLC program. The data type of this
parameter is used to set the data format of the Data Array
if the EIP_Data_Type parameter is not specified.
Maximum length 48
characters.
EIP_Data_Type*
If set, the data will be stored in the specified format which
may be different to the format of the tag being polled. If
the parameter is not set, the data type of the Data Array
will be used. This is only applicable to Data Table Read
when FieldServer is the Server. Refer to Appendix A.4 for
further information.
Float, Uint16, Uint32, Bit,
Byte, Boolean, -
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. Refer to
Appendix D for further information.
For any given Map
Descriptor there can be
200 Floats, 400 Integers
or 800 Bytes
EIP_Structure_Handle*
This parameter is required only for read structures i.e.
where EIP_Service is Data_Table_Read. The driver
supports read structures having members of same type,
i.e. all members are of type Byte, Uint16, Uint32 or Float
etc. When this parameter is defined, the number of
structure members must be specified as the length of the
Map Descriptor.
Any 16bit Integer number
e.g. 59592, 0
6.3.4 Driver Related Map Descriptor Parameters –PCCC
Column Title
Function
Legal Values
EIP_Con_Typ
The type of data transfer required
Explicit
EIP_Service
Action to be performed
EXEC_PCCC (Encapsulation
using Allen Bradley PCCC)
File_Type
Allen Bradley file type
N Integer
F Float
O Output
B Boolean
I Input
S Status
File_Number
Allen Bradley file number
Any valid numerical value
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. Refer to Appendix D for further
information.
For any given Map
Descriptor there can be 61
Floats, 122 Integers or 244
Bytes. .
Address
Address in the file
Any valid numerical value
between 0 to 255

FS-8704-14 EtherNet/IP Manual Page 15 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
6.3.5 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
, 0
, Passive
, EIP_01
, 10
, 1
, 3
, Get_Attrib
, 1
SMD_PRO_02
, DA_AI_01
, 1
, Passive
, EIP_01
, 10
, 2
, 3
, Get_Attrib
, 1
6.3.6 Map Descriptor Example 2: Data Table Messages
// Server Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Node_Name
, Function
, EIP_Service
EIP_Tag_Name
, Length
SMD_PRO_09
, DA_AI_05
, 0
, EIP_01
, Passive
, Data_Table_Read
, Analog_in_3
, 2
SMD_PRO_10
, DA_AI_06
, 0
, EIP_01
, Passive
, Data_Table_Read
, Analog_in_4
, 2
6.3.7 Map Descriptor Example 3: PCCC Messages
// Server Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Function
, EIP_Con_Typ
, Node_Name
, EIP_Service
, File_Type
, File_Number
, Address
, Length
SRV_AI_01
, DA_F_01
, 0
, Passive
, Explicit
, EIP_01
, Exec_PCCC
, F
, 8
, 30
, 20

FS-8704-14 EtherNet/IP Manual Page 16 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
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.
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. Consequently this functionality is not possible on an FS-X20 platform.
Appendix A.3. Common Paths
Device
Typical Path
Direct AB
1 0
AB ENI module
3 1
AB ControlLogix 1756-L55 (With network card 1756-ENBT/A)
1 1 or 1 0
CompactLogix ENI (1769-L31 using the 1761-NET-ENI)
3 1
CompactLogix Direct Connection (P/N 1769-L35E)
1 1 or 1 0
Appendix A.4. Setting the Data Type for stored data.
The default Data Type of stored data is determined by the Data Type of the Data Array. It is possible to configure
the driver to store the data as a different type. This can be achieved by specifying the data type under the
parameter EIP_Data_Type.
Note that the EIP_DATA_TYPE parameter has meaning only for DATA_TABLE_WRITE where the FieldServer is the
Client and for DATA_TABLE_READ where the FieldServer is the Server.
Appendix A.5. Configuring a PLC to read and write data to and from FieldServer
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. The Map Descriptors create an explicit connection to the Server and then transfer data in
the data table format. The EIP_Tag_Name field contains the tag name polled from the client. DATA_TABLE_READ
and DATA_TABLE_WRITE are the only legal values for EIP_SERVICE.
Note that this is by far the preferred method for communicating with Allen Bradley PLC’s due to its ease of
configuration, quantity of data that can be transferred and speed of transfer.

FS-8704-14 EtherNet/IP Manual Page 17 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
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
//
Connections
Adapter
, Protocol
, Turnaround_delay
N1
, Ethernet/IP
, 0.01s
// Server Side Nodes
//
Nodes
Node_Name
, Protocol
EIP_01
, Ethernet/IP
// Server Side Map Descriptors
//
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Data_Array_Offset
, Node_Name
, Function
, EIP_SERVICE
, EIP_TAG_NAME
, Length
FS_TO_PLC_DATA
, DA_Read
, 0
, EIP_01
, Passive
, DATA_TABLE_READ
, Read_Data
, 20
PLC_TO_FS_DATA
, DA_Write
, 0
, EIP_01
, Passive
, DATA_TABLE_WRITE
, Write_Data
, 20
Number of data points made available
for reading or writing within the Tag.
“FieldServer “Tag names that will be called in the PLC Message Block. The
names must match what is written in the Message block in the PLC exactly.
Note: The corresponding PLC Tag Name can be different and probably will
be. See Message Block Below.

FS-8704-14 EtherNet/IP Manual Page 18 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
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:
Step 2: Configure Message Tags for storage of Message Block data:
Step 3: Write Ladder Logic to exercise a Read and Write Message Block
NOTE: It is important to use the Ladder logic to ensure that only one Message block can be executing at any time.
Tag Length Must be equal to or greater than
the number of points being written/read
MESSAGE Data Type must be used.
Avoid Using UDT Types. The Data will
be read but the exact placement of
the data in the Tags and Arrays will be
hard to determine
Note that this logic shown will cause the PLC to poll the FieldServer at a
very high speed. This may overload network traffic - logic that schedules
the communication at a slower rate is generally more advisable.

FS-8704-14 EtherNet/IP Manual Page 19 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
Step 4: Configure the Properties for the two Message Blocks by clicking on the “…” button:
Read Message Block:
Write Message Block:
Communication Tab for both Message Blocks:
Notes:
1) A message block only executes on the leading edge of a rung condition
2) No more than one message block executes at a time.
Step 5: Download the program and set the PLC to Run Mode.
Remote FieldServer Tag Configured in the FieldServer (see
example above)
Local PLC Tag configured in the PLC Tag List (see example above)
Local PLC Tag configured in the PLC Tag List (see example above)
Remote FieldServer Tag configured in the FieldServer (see example above)
Number of points transferred from FieldServer
to PLC regardless of Tag and Array Sizes
Number of points transferred from PLC to FieldServer
regardless of Tag and Array Sizes
EIP_Card is the name of the Ethernet ENBT Card in the
ControlLogix Rack.
“2” refers to the port number on the ENBT Card.
192.168.1.75 is the IP Address of the FieldServer.
The Tag Tab requires no configuration.

FS-8704-14 EtherNet/IP Manual Page 20 of 30
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]
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. . These map descriptors will create an explicit connection to the server and will then
transfer data in the data table format. The EIP_Tag_Name field contains the tag name referenced in the server
and the EIP_Path field represents the path (through different ports) to the server. Each port jump is separated by a
space. This field generally holds a backplane/cpu slot combination. DATA_TABLE_READ and DATA_TABLE_WRITE
are the only legal values for EIP_SERVICE.
Note that this is by far the preferred method for communicating with Allen Bradley PLC’s due to it’s ease of
configuration, quantity of data that can be transferred and speed of transfer.
When the FieldServer is the active component as shown below (i.e: the FieldServer Polls the PLC and not the other
way around), then very little programming is needed in the PLC, other than the Tag Creation and setting the PLC IP
Address.