4 Data Array Parameters ................................................................................................................................... 5
5 Configuring theFieldServer as a DH+ Client .................................................................................................... 6
5.1Driver Specific FieldServer Parameters ........................................................................................................ 6
5.2Client Side Connection Parameters .............................................................................................................. 6
5.3Client Side Node Parameters ....................................................................................................................... 7
5.4Client Side Map Descriptor Parameters ....................................................................................................... 7
5.4.1 FieldServer Related Map Descriptor Parameters ..................................................................................... 7
5.4.2 Driver Related Map Descriptor Parameters ............................................................................................. 8
5.4.3 Map Descriptor Example .......................................................................................................................... 9
6 FieldServer as a DH+ Server .......................................................................................................................... 10
6.1Driver Specific FieldServer Parameters ...................................................................................................... 10
6.2Server Side Connection Parameters ........................................................................................................... 10
6.3Server Side Node Parameters .................................................................................................................... 11
6.4Server Side Map Descriptor Parameters .................................................................................................... 11
6.4.1 FieldServer Specific Map Descriptor Parameters ................................................................................... 11
6.4.2 Driver Specific Map Descriptor Parameters ........................................................................................... 12
6.4.3 Map Descriptor Example ........................................................................................................................ 13
Appendix A. Useful Features ................................................................................................................................ 14
Appendix B. Troubleshooting ............................................................................................................................... 15
Appendix B.4. DH+ as FieldServer Server ................................................................................................................ 15
Appendix C. Reference ......................................................................................................................................... 16
Appendix C.1. Command Support ........................................................................................................................... 16
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Template loaded if no custom configuration ordered, otherwise Custom
configuration loaded.
Part #
Description
AB DH+ compatible PLC, e.g. SLC5/03, PLC 5/40, etc
1
DH+ Client, e.g. RSView, Wonderware, Intellution FIX, GE Cimplicity, etc.
2
FS-23083
DH+ configuration cable3. Refer to Appendix A.1
Part #
Description
DL2.exe
Runs on a PC. Used only if a change to DH+ parameters (Station address, baud etc) required. Requires
DH+ configuration cable (not supplied)3 Refer also to Appendix A.1
1 ALLEN BRADLEY DH+ DESCRIPTION
The DH+ driver allows the FieldServer to transfer data to and from devices using DH+ protocol. The
Communications Adapter card is included with the FieldServer. 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.
2 DRIVER SCOPE OF SUPPLY
2.1 Supplied by Fiel dSe rver Technolo gies fo r this Driver
2.2 Provided by the supplier of 3
2.2.1 Hardware
2.2.2 Required 3
rd
Party Software
rd
Party Equipme nt
1
If FieldServer used as Allen Bradley DH+ Client
2
If FieldServer used as Allen Bradley DH+ Server
3
Used only if a change to DH+ parameters (Station address, baud etc) required.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
// 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
4 DATA 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.
Example
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify baud rate. This is an Internal baud rate and is not the DH+ Baud rate which
gets set using the card's DL2 software.
300 to
115200
5 CONFIGURING THEFIELDSERVER AS A DH+ CLI ENT
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 DH+ Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for DH+ 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 Driver Specific FieldServer Param eters
Example
5.2 Client Side Connect ion Parameters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The Driver is not able to split data between 2 Data Arrays when writing, or to read a Server mapping that is
discontinuous.
For example, on the Server Side:
If:
Server map 1: N21: 0-31
Server map 2: N21: 32-100
This will panic the FieldServer and crash RS view as the DH+ will attempt to map N21: 0-100. If set up as Server
Map 1: N21: 0-100, no problems are experienced.
Appendix B.2. Reading B File Types
It is advisable to read all data from one B type file into the same data array in one contiguous read if possible.
Doing otherwise may result in problems when reading these points.
Appendix B.3. Checksum
When selecting checksum options for DH+ devices communicating to the FieldServer, take note that BCC (Block
Check Sum) is supported, whereas CRC (Cyclic Redundancy Check) is not.
Appendix B.4. DH+ as FieldServer Server
If the FieldServer is to be polled by the DH+ network, then it is important to declare the station address in the
“FieldServer” portion of the configuration file. Refer to Section 6.1. This sets the FieldServer address to 11. The
Node_ID on the Server side must then be the same as the station address declared.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com