Modbus TCP/IP Driver Manual
Page 7 of 23
5 CONFIGURING THE FIELDSERVER AS A MODBUS TCP/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 (see “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a Modbus TCP/IP Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for Modbus TCP/IP communications the following three actions must be taken.
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 server(s) needs to be mapped in the “Client Side Map Descriptors” section. Details on
how to perform these steps can be found in the following sections.
NOTE: In the following tables, * indicates an optional parameter and bold legal values are default.
5.1 Client Side Connection Parameters
Specify which adapter this protocol uses.
Specify protocol used.
Time interval between polls.
0-32000 s, 0.05 s
Specify the maximum messages the driver
can send, before waiting for responses.
0 – 65534
(0 or 1 disables
meaning only 1 active
message at a time)
// Client Side Connections
4 Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports
available on specific hardware.
5 Using Max_Concurrent_Messages value > 1 could improve communication performance, but it also depends on the remote
Server’s implementation. The server might not support multiple messaging, so match this number with the Server's capability.