FS-8704-14 EtherNet/IP Manual
Page 7 of 30
FieldServer Technologies
1991 Tarob Court Milpitas, California 95035 USA
Web
: www.fieldserver.com
Tel
: (408) 262 2299
Fax
: (408) 262 2269
Toll Free
: (888) 509 1970
5
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.
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, N2
2
Protocol
Specify protocol used
EtherNet/IP
Example
// Client Side Connections
Adapters
Adapter
, Protocol
N1
, EtherNet/IP
5.2
Client Side Node Descriptors
3
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, N2
2
Plc_Type*
Specify the type of remote PLC. Only
required for PCCC Services
MicroLogix, SLC5,
PLC5
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
3
Only one explicit connection is created per node. All explicit Map Descriptors attached to that node will use the same explicit connection.