A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-12 AB DH+
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
FS-8700-12_DH+ Manual
Page 3 of 14
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.
FS-8700-12_DH+ Manual
Page 4 of 14
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this Driver
SMC PART #
FS-SPA23027
DESCRIPTION
DH+ cable
2.2.
2.2.1.
Provided by the supplier of 3rd Party Equipment
Hardware
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
1 If FieldServer used as Allen Bradley DH+ Client
2 If FieldServer used as Allen Bradley DH+ Server
FS-8700-12_DH+ Manual
Page 5 of 14
3.
Hardware Connections
Configure the PLC according to manufacturer’s instructions and configure checksum to use
BCC checksum, not CRC.
FS-8700-12_DH+ Manual
Page 6 of 14
4.
Configuring theFieldServer as a DH+ 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 FS).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a DH+ 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 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.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Float, Bit,
UInt16, SInt16,
Uint32, Sint32,
Packet_Bit, Byte,
Packet_Byte,
Swapped_Byte
1-10,000
Data_Format
Provides data format
Data_Array_Length
Number of Data Objects
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
DA_AI_01,
DA_AO_01,
DA_DI_01,
Data_Format,
Data_Array_Length
200
200
200
200
Float,
Float,
Bit,
DA_DO_01,
Bit,
FS-8700-12_DH+ Manual
Page 7 of 14
4.2.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Port
Protocol
Function
Port name
Specify protocol used
Legal Values
DH+
AB_DH+
Example
// Client Side Connections
Connections
Port,
DH+,
Protocol
AB_DH+
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Node_Name
Provide name for node
Node ID of physical server node
(PLC)
Node_ID
1-255
Protocol
PLC_Type
Specify protocol used
Specify PLC Type Being Polled
AB_DH+
PLC3, PLC5, SLC5
Example
// Client Side Nodes
Nodes
Node_Name,
PLC 1,
Node_ID,
1,
Protocol,
AB_DH+,
PLC_Type,
SLC5,
Port
DH+
FS-8700-12_DH+ Manual
Page 8 of 14
4.4.
Client Side Map Descriptors
Section Title
Map_Descriptors
Column Title
Function
Name of this Map
Descriptor
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where One of the Data Array
Data_Array_Name
data is to be stored in the
FieldServer
names from “Data Array”
section above
0 to maximum specified
in “Data Array” section
above
Starting location in Data
Array
Data_Array_Offset
Function
Function of Client Map
Descriptor
RDBC, WRBC, WRBX
One of the node names
specified in “Client Node
Descriptor” above
Name of Node to fetch
data from
Node_Name
File_Type
File type in PLC
N, B
File_Number
File Number in PLC
0-255
Starting address of read
block
Address
0 – 255
Length
Length of read block
1-255
-32767 to 32767, default
0
Data_Array_Low_Scale*
Scaling zero in Data Array
-32767 to 32767, default
100
Data_Array_High_Scale*
Scaling max in Data Array
Scaling zero in Connected -32767 to 32767, default
Node
Scaling max in Connected -32767 to 32767, default
Node
100
Node_Low_Scale*
Node_High_Scale*
0
FS-8700-12_DH+ Manual
Page 9 of 14
4.4.1.
Map Descriptor Example
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
CMD_AI_01,
CMD_AO_01,
Data_Array_Name,
DA_AI_01,
DA_AO_01,
Data_Array_Offset,
0,
0,
Function Node_Name File_Type, File_Number,
Address, Length Scan_Interval
Rdbc
Rdbc
PLC 1
PLC 1
N
N
10
11
0
0
16
16
1.0s
1.0s
Map_Descriptors
Map_Descriptor_Name,
CMD_DI_01,
Data_Array_Name,
DA_DI_01,
DA_DO_01,
Data_Array_Offset,
0,
0,
Function Node_Name File_Type, File_Number,
Address, Length Scan_Interval
Rdbc
Rdbc
PLC 1
PLC 1
B
B
12
13
0
0
16
16
1.0s
1.0s
CMD_DO_01,
FS-8700-12_DH+ Manual
Page 10 of 14
5.
FieldServer as a DH+ Server
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title
Port
Protocol
Function
Port name
Specify protocol used
Legal Values
DH+
AB_DH+
Example
// Server Side Connections
Connections
Port,
DH+,
Protocol
AB_DH+
5.2.
Server Side Node Descriptors
Section Title
Nodes
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Node_Name
Provide name for node
Node ID of virtual server node
(FieldServer)
Node_ID
1-255
Protocol
Specify protocol used
AB_DH+
PLC_Type
Specify PLC Type Being Polled
PLC3, PLC5, SLC5
Example
// Server Side Nodes
Nodes
Node_Name,
DHP_Srv_11,
Node_ID,
11,
Protocol,
AB_DH+,
PLC_Type
SLC5
FS-8700-12_DH+ Manual
Page 11 of 14
5.3.
Server Side Map Descriptors
Section Title
Map_Descriptors
Column Title
Function
Name of this Map
Descriptor
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where One of the Data Array
Data_Array_Name
data is to be stored in the
FieldServer
names from “Data Array”
section above
0 to maximum specified
in “Data Array” section
above
Starting location in Data
Array
Data_Array_Offset
Function
Function of Client Map
Descriptor
Server
One of the node names
specified in “Client Node
Descriptor” above
Name of Node to fetch
data from
Node_Name
File_Type
File type in PLC
N, B
File_Number
File number in PLC
0-255
Starting address of read
block
Length of read block
Address
0 - 255
1 - 255
Length
Data_Array_Low_Scale*
Scaling zero in Data Array -32767 to 32767, 0
Data_Array_High_Scale*
Scaling max in Data Array -32767 to 32767, 100
Scaling zero in Connected
-32767 to 32767, 0
Node
Node_Low_Scale*
Scaling max in Connected
-32767 to 32767, 100
Node
Node_High_Scale*
FS-8700-12_DH+ Manual
Map Descriptor Example
Page 12 of 14
// Server Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Data_Array_Name,
Data_Array_Offset,
Function,
Node_Name,
File_Type,
File_Number,
Address,
Length,
Data_Array_Low_Scale,
Data_Array_High_Scale,
Node_Low_Scale,
Node_High_Scale
SMD_AI_01,
SMD_AO_01,
DA_AI_01,
DA_AO_01,
0,
0,
Server,
Server,
DHP_Srv_11,
DHP_Srv_11,
N,
N,
10,
11,
0,
0,
200,
200,
0,
0,
100,
100,
0,
0,
100
100
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, File_Type, File_Number, Address, Length
SMD_DI_01,
SMD_DO_01,
DA_DI_01,
DA_DO_01,
0,
0,
Server,
Server,
DHP_Srv_11, B,
DHP_Srv_11, B,
12,
13,
0,
0,
200
200
FS-8700-12_DH+ Manual
Page 13 of 14
6.
Driver Notes
6.1. Continuous Map Descriptors
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 DH+ will attempt to map N21:
0-100
If set up as:
Server Map 1: N21: 0-100
No problems are experienced
6.2.
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.
6.3.
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.
e.g. FieldServer
Title,
System_Station_Address
11
DCC099 Primserv.csv v3.00u,
This sets the FieldServer address to 11. The Node_ID on the server side must then be the
same as the station address declared.
6.4.
Command Support
The following commands are supported by the FieldServer for the various PLC types:
Typical
Command
PLC_Type File_type FNC Read
FNC Write
N
F
B
N
F
B
1
1
1
1
1
1
Range Read
Range Read
Range Read
Range Read
Range Read
Range Read
Protected Typed
Logical Read
Protected Typed
Logical Read
Protected Typed
Logical Read
Protected Typed
Logical Read
Protected Typed
Logical Read
0
0
2
0
67
26
Range Write
Range Write
Bit Write
Range Write
N7: 3, L5
F12: 3, L5
B3/4: 5, l5
N7: 3 , L5
F12: 3, L5
B3/4: 5, L5
PLC3
PLC5
Typed Write
Read Modify Write
Protected Typed
Logical Write
Protected Typed
Logical Write
Protected Typed
Logical Write
N
F
B
I
A2
A2
A2
A2
A2
AA
AA
AB
-
N7: 3, L5
B3/4: 5, L7
B3/4: 5, L8
I: 13, L5
SLC5
-
-
O
-
O: 13, L5
FS-8700-12_DH+ Manual
Page 14 of 14
7.
Revision History
Driver
Version
Document
Revision
Date
Resp
Comment
11/28/03
2/18/04
1
2
MF
JD
Updated formatting
Releasing
|