The DF1 driver allows the FieldServer to transfer data to and from devices over RS-232 using
DF1 protocol. The FieldServer can emulate either a Server or Client.
The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
It is possible to connect an Allen Bradley PLC to any of the RS-232 ports. These ports simply
need to be configured for an Allen Bradley PLC in the configuration file.
ALLEN BRADLEY PLC
COMM 2
FS8917-06
RJ45 CAT 5 Cable
FS8915-10
8917-06 WIRE LIST
FUNCTIONFROMTOCOLOUR
RxRJ45-01DB9F-03WHITE
GNDRJ45-04DB9F-05GREEN
TxRJ45-08DB9F-02BLUE
FIELDSERVER
DF1
CONNECTION DIAGRAM
BASE NAME:
FILE NAME:
(408)-262-2299
DATE: 4/20/04
BY: MC
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
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 FS).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a DF1 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 DF1 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.
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array
Data_Format Provides data format INT16, INT32, BIT, FLOAT
Data_Array_Length Number of Data Objects 1-10,000
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
Data_Array_Name
Data_Array_Offset Starting location in Data Array
Function
data is to be stored in the
FieldServer
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
File_Type File type in PLC N, F, B, I, O5
File_Number File Number in PLC 0-255
Address Starting address of read block 0 – 255
Data_Array_Low_Scale* Scaling zero in Data Array
Data_Array_High_Scale* Scaling max in Data Array
Node_Low_Scale*
Node_High_Scale*
Name of Node to fetch data
from
Scaling zero in Connected
Node
Scaling max in Connected
Node
One of the node names
specified in “Client Node
Descriptor” above
-32767 to 32767, 0
-32767 to 32767, 100
-32767 to 32767, 0
-32767 to 32767, 100
5
Not all PLC’s can support all File_Types. Refer to DFS for further information.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
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” files on the
driver diskette).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a DF1 Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for DF1 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.
RS View has been known to crash if it tries to read a Server mapping that is discontinuous.
e.g. Server map 1: N21: 0-31
Server map 2: N21: 32-100
This will panic the FieldServer and crash RS view as the DF1 will attempt to map N21: 0-100
If set up as:
Server Map 1: N21: 0-100 No problems are experienced
Appendix A.2. Checksum
You can now specify a checksum parameter for the serial connection.
The heading keyword is "Checksum" and the possible values are
The following commands are supported by the FieldServer for the various PLC types:
PLC_Type File_Type FNC Read FNC Write
N 1 Range Read 0 Range Write N7: 3, L5
PLC3
PLC5
SLC5
F 1 Range Read 0 Range Write F12: 3, L5
B 1 Range Read 2 Bit Write B3/4: 5, l5
N 1 Range Read 0 Range Write N7: 3 , L5
F 1 Range Read 67 Typed Write F12: 3, L5
B 1 Range Read 26 Read Modify Write B3/4: 5, L5