FieldServer Hanning FS-8700-127 Release note

-
A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1 2001
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-127 Hanning & Kahl
HCS-R
Driver Version:
1.00
Document Revision: 9

FS-8700-127 Hanning & Kahl HCS-R Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
TABLE OF CONTENTS
1. HANNING & KAHL HCS-R DESCRIPTION.................................................................... 3
2. DRIVER SCOPE OF SUPPLY ........................................................................................ 4
2.1. Supplied by ieldServer Technologies for this driver.................................................. 4
3. HARDWARE CONNECTIONS........................................................................................ 5
3.1. Hardware Connection Tips / Hints.............................................................................. 5
4. CONFIGURING THE FIELDSERVER AS A HCS-R CLIENT.......................................... 6
4.1. Data Arrays/Descriptors............................................................................................. 6
4.2. Client Side Connection Descriptions .......................................................................... 7
4.3. Client Side Node Descriptors ..................................................................................... 7
4.4. Client Side Map Descriptors....................................................................................... 8
4.4.1. FieldServer Related Map Descriptor Parameters.................................................... 8
4.4.2. Driver Related Map Descriptor Parameters............................................................. 8
4.4.3. Timing Parameters ................................................................................................. 8
4.5. Map Descriptor Example: Read Data......................................................................... 9
4.6. Map Descriptor Example: Read Data and Keep History............................................10
5. CONFIGURING THE FIELDSERVER AS A HCS-R SERVER .......................................11
5.1. Server Side Connection Descriptors .........................................................................11
5.2. Server Side Node Descriptors...................................................................................12
5.3. Server Side Map Descriptors ....................................................................................13
5.3.1. FieldServer Specific Map Descriptor Parameters...................................................13
5.3.2. Driver Specific Map Descriptor Parameters ...........................................................13
5.3.3. Map Descriptor xample. - SMD_HCSR_01 Map Descriptor to Serve HCS-R
clients. 14
APPENDIX A. ADVANCED TOPICS .....................................................................................15
Appendix A.1. 1. How Client Stores Data:...........................................................................15
Appendix A.1.1. Data_Type is Ana_Input or not specified................................................15
Appendix A.1.2. Data_Type is Digi_Input.........................................................................15
Appendix A.2. 2. How Server expects Data:........................................................................16
Appendix A.2.1. Data_Type is Ana_Input or not specified................................................16
Appendix A.2.2. Data_Type is Digi_Input.........................................................................16

FS-8700-127 Hanning & Kahl HCS-R Manual Page 3 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
1. Hanning & Kahl HCS-R Description
The Hanning & Kahl HCS-R driver allows the transfer of data from devices over RS-232 HCS-R
protocol. Data is read from HCS-R and current data stored in a specified memory area. The
driver can store the data with its loop data status distinct memory areas depending on wheter
the data is on loop or from loop. The driver is based on section 10.5 of Hanning & Kahl - part
number 40801121. The ieldServer can act as a Client or Server.
Max Nodes Supported
FieldServer Mode Nodes Comments
Client 1 Only 1 virtual client per port allowed on multidrop systems,
Server 1 This is a protocol limit, maximum devices can be polled by Client

FS-8700-127 Hanning & Kahl HCS-R Manual Page 4 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART # Description
S-8915-10 UTP cable (7 foot) for RS-232 use
S-8700-127 Driver Manual.

FS-8700-127 Hanning & Kahl HCS-R Manual Page 5 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
3. Hardware Connections
The ieldServer is connected to the Hanning & Kahl HCS-R as shown in connection drawing.
Configure the HCS-R according to manufacturer’s instructions
DATE: 2/12/
08
BY: MC
(408)-262-2299
BASE NAME: FS-8700-127
FILE NAME:
FIELDSERVER
HANNING KAHL
CONNECTION DIAGRAM
S-8917-02
HCS-R
(Hanning Communication System)
RS-232
RJ45 CAT 5 Cable
8917-02 WIRE LIST
CTS
RTS
Tx
GND
Rx
FUNCTION
RJ45-08
RJ45-04
RJ45-01
FROM
DB9F-08
DB9F-07
DB9F-02
DB9F-05
DB9F-03
TO
3.1. Hardware Connection Tips / Hints
1. Loop back RTS CTS if it is required by the other device.

FS-8700-127 Hanning & Kahl HCS-R Manual Page 6 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
4. Configuring the FieldServer as a HCS-R Client
or a detailed discussion on ieldServer configuration, please refer to the ieldServer
Configuration Manual. The information that follows describes how to expand upon the factory
defaults provided in the configuration files included with the ieldServer (See “.csv” sample files
provided with the ieldServer).
This section documents and describes the parameters necessary for configuring the ieldServer
to communicate with a HCS-R Server.
4.1. Data Arrays/Descriptors
The configuration file tells the ieldServer about its interfaces, and the routing of data
required. In order to enable the ieldServer for HCS-R communications, the driver
independent ieldServer 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 Up to 15 alphanumeric
characters
Data_Array_ ormat Provide data format. Each Data Array can
only take on one format.
loat, 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
Example
// Data Arrays
Data_Arrays
Data_Array_Name, Data_Array_ ormat, Data_Array_Length
DA_CURRENT, Uint16, 22
DI_ romLoop01, Bit, 22
DI_OnLoop01, Bit, 22
DI_ romLoop02, Bit, 22
DI_OnLoop02, Bit, 22
DI_ romLoop03, Bit, 22
DI_OnLoop03, Bit, 22
DI_ romLoop014 Bit, 22
DI_OnLoop04, Bit, 22

FS-8700-127 Hanning & Kahl HCS-R Manual Page 7 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
4.2. Client Side Connection Descriptions
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the device is
connected to the ieldServer P1-P8
1
Protocol Specify protocol used
HCS-R
HCSR
H&K HCS-R
Baud* Specify baud rate 9600 (Vendor limitation)
Parity* Specify parity None (Vendor limitation)
Data_Bits* Specify data bits 8 (Vendor limitation)
Stop_Bits* Specify stop bits 1 (Vendor limitation)
Handshaking* Specify hardware handshaking None (Vendor limitation)
Poll_Delay* Time between internal polls 0-32000 seconds, 0.05 seconds
Example
// Client Side Connections
Connections
Port, Protocol, Baud, Parity, Handshaking, Poll_Delay
P8, HCS-R, 9600, None, None, 0.100s
4.3. Client Side Node Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for Node Up to 32 alphanumeric characters
Node_ID HCS-R station address of physical
server Node 240 (Protocol limit)
Protocol Specify protocol used
HCS-R
HCSR
H&K HCS-R
Connection Specify which port the device is
connected to the ieldServer P1-P8
1
Example
// Client Side Nodes
Nodes
Node_Name, Node_ID, Protocol, Connection
PLC 1, 240, HCS-R, P8
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.

FS-8700-127 Hanning & Kahl HCS-R Manual Page 8 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
4.4. Client Side Map Descriptors
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric
characters
Data_Array_Name
Name of Data Array where data
is to be stored in the
ieldServer
One of the Data Array names
from “Data Array” section above
Data_Array_Offset Starting location in Data Array 0 to maximum specified in
“Data Array” section above
unction unction of Client Map
Descriptor RDBC, Passive_Client
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data from
One of the Node Names
specified in “Client Node
Descriptor” above
HCSR_On rom
or Passive_Client Map Descriptor
specify whether data rom Loop or
On Loop should be stored.
On, rom, On rom
HCSR_Loop
or Passive_Client Map Descriptor
specify loop number for which data
should be stored.
1,2,3,4
Length
Length of Map Descriptor
22 (min) for RDBC Map Descriptor:
24 if data_type is Dig_Input
21 for Passive_Client Map
Descriptor.
It also depends upon
HCSR_Data_Stages parameter
Refer to Appendix A
22 or 24, 21
Data_Type* Specify how data will be stored.
Refer to Appendix A
Ana_Input
Digi_Input
2
HCSR_Data_Stages*
Specify the number of stages to
keep history of data changes.
0 and 1 means no history
01,2,3
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled ≥0.001s
2
Default for Digi_Input

FS-8700-127 Hanning & Kahl HCS-R Manual Page 9 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
4.5. Map Descriptor Example: Read Data
The CMD_DI Map Descriptor polls HCS-R Node_A (described in Client Side Node Descriptors sections) every 5 seconds.
The other Map Descriptors are used to store the data for various loops. Refer to Appendix A for data storage format.
Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, unction, Node_name Length Scan_Interval CMD_DI_HCSR_01, DA_CURRENT, 0, RDBC, Node_A, 22, 5 Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, unction, Node_name Length HCSR_Onfrom HCSR_Loop CMD_ romLoop_01, DI_ romLoop01, 0, Passive_Client, Node_A, 21, rom 1 CMD_OnLoop_01, DI_OnLoop01, 0, Passive_Client, Node_A, 21, On 1 CMD_ romLoop_02, DI_ romLoop02, 0, Passive_Client, Node_A, 21, rom 2 CMD_OnLoop_02, DI_OnLoop02, 0, Passive_Client, Node_A, 21, On 2 CMD_ romLoop_03, DI_ romLoop03, 0, Passive_Client, Node_A, 21, rom 3 CMD_OnLoop_03, DI_OnLoop03, 0, Passive_Client, Node_A, 21, On 3 CMD_ romLoop_4, DI_ romLoop04, 0, Passive_Client, Node_A, 21, rom 4 CMD_OnLoop_04, DI_OnLoop04,, 0, Passive_Client, Node_A, 21, On 4
Name one of the Data Array defined in Data_Array section to store data
Starting offset in Data Array to hold data
One of the Nodes declared in Client Node Section. This Node will be polled if unction is
RDBC
How often (in seconds) to poll target device. Irrelevant if unction is Passive_Client
Maximum number of placeholders for data storage.
RDBC will cause read poll and Passive_Client is used to store data returned by response.

FS-8700-127 Hanning & Kahl HCS-R Manual Page 10 of 17
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www. ieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@ ieldServer.com
4.6. Map Descriptor Example: Read Data and Keep History
This Map Descriptor allows the storage of data history up to HCSR_Data_Stages. Data will be shifted to next Stage only if the data is changed. The driver divides the Data Array into sections corresponding to the number of HCSR_Data_Stages. Current data (stage1) will be stored in the first section and oldest (last stage) data will be stored in the last section in the Data array. Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, unction, Node_name Length Scan_Interval, HCSR_Data_Stages CMD_DI_HCSR_01, DA_CURRENT, 0, RDBC, Node_A, 72, 5, 3 Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, unction, Node_name Length HCSR_Onfrom HCSR_Loop HCSR_Data_Stages CMD_ romLoop_01, DI_ romLoop01, 0, Passive_Client, Node_A, 63, rom 1 3 CMD_OnLoop_01, DI_OnLoop01, 0, Passive_Client, Node_A, 63, On 1 3 CMD_ romLoop_02, DI_ romLoop02, 0, Passive_Client, Node_A, 63, rom 2 3 CMD_OnLoop_02, DI_OnLoop02, 0, Passive_Client, Node_A, 63, On 2 3 CMD_ romLoop_03, DI_ romLoop03, 0, Passive_Client, Node_A, 63, rom 3 3 CMD_OnLoop_03, DI_OnLoop03, 0, Passive_Client, Node_A, 63, On 3 3 CMD_ romLoop_4, DI_ romLoop04, 0, Passive_Client, Node_A, 63, rom 4 3 CMD_OnLoop_04, DI_OnLoop04,, 0, Passive_Client, Node_A, 63, On 4 3
Name one of the Data Array defined in Data_Array section to store data
Starting offset in Data Array to hold data
One of the Nodes declared in Client Node Section. This Node will be polled if unction is
RDBC
How often (in seconds) to poll target device. Irrelevant if unction is Passive_Client
Maximum number of placeholders for data storage.
RDBC will cause read poll and Passive_Client is used to store data returned by response.
The number of data stages (data changes) to be kept as history.