The SMC TCP/IP driver allows the FieldServer to transfer data to and from other FieldServers
over Ethernet using SMC TCP/IP protocol. The FieldServer can emulate either a Server or
Client.
The SMC TCP/IP driver can be used for inter-bridge (FieldServer to FieldServer)
communications to perform tasks like mirroring data arrays between FieldServers.
Max Nodes Supported
FieldServer Mode Nodes Comments
Inter-bridge Communications to a virtually unlimited number
Client N/A
of FieldServers. Memory limitations may apply when a
large number of Nodes are used.
Inter-bridge Communications to a virtually unlimited number
Server N/A
of FieldServers. Memory limitations may apply when a
large number of Nodes are used.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4. Configuring the FieldServer as a SMC TCP/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 (See “.csv” sample files
provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a SMC TCP/IP Server.
4.1. Data Arrays/Descriptors
The configuration file tells the FieldServer about its interfaces, and the routing of data
required. In order to enable the FieldServer for SMC TCP/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.
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name
Data_Array_Name
Data_Array_Offset
Function
Name of this Map
Descriptor
Name of Data Array
where data is to be
stored in the
FieldServer
Starting location in Data
Array
Function of Client Map
Descriptor
Up to 32 alphanumeric
characters
One of the Data Array
names from “Data Array”
section above
0 to maximum specified in
“Data Array” section above
RDBC, WRBC, WRBX
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name
Data_Type Data type Register, Coil, AI, DI
Target_DA_Name
Target_DA_Offset
Length Length of Map Descriptor 1 - 340
Name of Node to fetch
data from
Data array on remote
FieldServer
Data array on remote
FieldServer
One of the node names
specified in “Client Node
Descriptor” above
Up to 15 alphanumeric
characters
Up to 15 alphanumeric
characters
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled ≥0.001s
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
5. Configuring the FieldServer as a SMC TCP/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 (See “.csv” sample files
provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a SMC TCP/IP Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for SMC TCP/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 clients 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.
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Adapter Adapter Name N1
Protocol Specify protocol used SMT
Example
// Server Side Connections
Connections
Adapter, Protocol
N1, SMT
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com