FieldServer FS-8700-127, HCS-R User Manual

-

Driver Version:

1.00

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-127 Hanning & Kahl

HCS-R

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2001

Document Revision: 9

FS-8700-127 Hanning & Kahl HCS-R Manual Table of Contents

TABLE OF CONTENTS

1.

HANNING & KAHL HCS-R DESCRIPTION.................................................................... 3

2.

DRIVER SCOPE OF SUPPLY ........................................................................................ 4

2.1.

Supplied by FieldServer 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 Example. - 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

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 3 of 17

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 FieldServer 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

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 4 of 17

2. Driver Scope of Supply

2.1. Supplied by FieldServer Technologies for this driver

FieldServer Technologies
PART #

FS-8915-10 UTP cable (7 foot) for RS-232 use
FS-8700-127 Driver Manual.

Description

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 5 of 17

08

3. Hardware Connections

The FieldServer is connected to the Hanning & Kahl HCS-R as shown in connection drawing.

Configure the HCS-R according to manufacturer’s instructions

HCS-R

(Hanning Communication System)

RS-232

FS-8917-02

8917-02 WIRE LIST

FUNCTION

Rx

GND

Tx
RTS
CTS

FROM
RJ45-01
RJ45-04
RJ45-08

TO
DB9F-03
DB9F-05
DB9F-02
DB9F-07
DB9F-08

RJ45 CAT 5 Cable

3.1. Hardware Connection Tips / Hints

1. Loop back RTS CTS if it is required by the other device.

FIELDSERVER

HANNING KAHL

CONNECTION DIAGRAM

BASE NAME: FS-8700-127
FILE NAME:

(408)-262-2299

DATE: 2/12/
BY: MC

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 6 of 17

4. Configuring the FieldServer as a HCS-R 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 HCS-R 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 HCS-R 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_Array_Format

Data_Array_Length

Provide data format. Each Data Array can
only take on one format.
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.

Example

// Data Arrays
Data_Arrays
Data_Array_Name, Data_Array_Format, Data_Array_Length
DA_CURRENT, Uint16, 22
DI_FromLoop01, Bit, 22
DI_OnLoop01, Bit, 22
DI_FromLoop02, Bit, 22
DI_OnLoop02, Bit, 22
DI_FromLoop03, Bit, 22
DI_OnLoop03, Bit, 22
DI_FromLoop014 Bit, 22
DI_OnLoop04, Bit, 22

Up to 15 alphanumeric
characters
Float, Bit, UInt16, SInt16,
Byte,

1-10,000

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 7 of 17

4.2. Client Side Connection Descriptions

Section Title

Connections

Column Title Function Legal Values

Port

Protocol Specify protocol used

Baud* Specify baud rate
Parity* Specify parity
Data_Bits* Specify data bits
Stop_Bits* Specify stop bits
Handshaking* Specify hardware handshaking
Poll_Delay* Time between internal polls

Example

// Client Side Connections

Connections
Port, Protocol, Baud, Parity, Handshaking, Poll_Delay
P8, HCS-R, 9600, None, None, 0.100s

Specify which port the device is
connected to the FieldServer

P1-P81

HCS-R
HCSR
H&K HCS-R

9600 (Vendor limitation)
None (Vendor limitation)
8 (Vendor limitation)
1 (Vendor limitation)
None (Vendor limitation)
0-32000 seconds, 0.05 seconds

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

Protocol Specify protocol used

Connection

Example

// Client Side Nodes

Nodes
Node_Name, Node_ID, Protocol, Connection
PLC 1, 240, HCS-R, P8

HCS-R station address of physical
server Node

Specify which port the device is
connected to the FieldServer

240 (Protocol limit)

HCS-R
HCSR
H&K HCS-R

P1-P81

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.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 8 of 17

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

Name of Data Array where data

Data_Array_Name

Data_Array_Offset Starting location in Data Array

Function

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, Passive_Client

4.4.2. Driver Related Map Descriptor Parameters

Column Title Function Legal Values

One of the Node Names

Node_Name Name of Node to fetch data from

For Passive_Client Map Descriptor

HCSR_OnFrom

HCSR_Loop

Length

Data_Type*

HCSR_Data_Stages*

specify whether data From Loop or
On Loop should be stored.
For Passive_Client Map Descriptor
specify loop number for which data
should be stored.
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
Specify how data will be stored.
Refer to Appendix A
Specify the number of stages to
keep history of data changes.
0 and 1 means no history

specified in “Client Node
Descriptor” above

On, From, OnFrom

1,2,3,4

22 or 24, 21

Ana_Input

Digi_Input2

0,1,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

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

How often (in

seconds) to poll

target device.

Irrelevant if

Function is

Passive_Client

Maximum

number of

placeholders for

data storage.

One of the

Nodes declared

in Client Node

Section. This

Node will be

polled if

Function is

RDBC will cause

read poll and

Passive_Client is

used to store data

returned by

response.

Starting offset

in Data Array

to hold data

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

4.5. Map Descriptor Example: Read Data

FS-8700-127 Hanning & Kahl HCS-R Manual Page 9 of 17

The other Map Descriptors are used to store the data for various loops. Refer to Appendix A for data storage format.

The CMD_DI Map Descriptor polls HCS-R Node_A (described in Client Side Node Descriptors sections) every 5 seconds.

Map_Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, 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, Function, Node_name Length HCSR_Onfrom HCSR_Loop

CMD_FromLoop_01, DI_FromLoop01, 0, Passive_Client, Node_A, 21, From 1

CMD_OnLoop_01, DI_OnLoop01, 0, Passive_Client, Node_A, 21, On 1

CMD_FromLoop_02, DI_FromLoop02, 0, Passive_Client, Node_A, 21, From 2

CMD_OnLoop_02, DI_OnLoop02, 0, Passive_Client, Node_A, 21, On 2

CMD_FromLoop_03, DI_FromLoop03, 0, Passive_Client, Node_A, 21, From 3

CMD_OnLoop_03, DI_OnLoop03, 0, Passive_Client, Node_A, 21, On 3

CMD_FromLoop_4, DI_FromLoop04, 0, Passive_Client, Node_A, 21, From 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

The number of

data stages

(data changes)

to be kept as

history.

How often (in

seconds) to poll

target device.

Irrelevant if

Function is

Passive_Client

Maximum

number of

placeholders for

data storage.

One of the

Nodes declared

in Client Node

Section. This

Node will be

polled if

Function is

Starting offset

in Data Array

to hold data

RDBC will cause read poll

and Passive_Client is used

to store data returned by

response.

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Name one of

the Data Array

defined in

Data_Array

section to store

4.6. Map Descriptor Example: Read Data and Keep History

FS-8700-127 Hanning & Kahl HCS-R Manual Page 10 of 17

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, Function, 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, Function, Node_name Length HCSR_Onfrom HCSR_Loop HCSR_Data_Stages

CMD_FromLoop_01, DI_FromLoop01, 0, Passive_Client, Node_A, 63, From 1 3

CMD_OnLoop_01, DI_OnLoop01, 0, Passive_Client, Node_A, 63, On 1 3

CMD_FromLoop_02, DI_FromLoop02, 0, Passive_Client, Node_A, 63, From 2 3

CMD_OnLoop_02, DI_OnLoop02, 0, Passive_Client, Node_A, 63, On 2 3

CMD_FromLoop_03, DI_FromLoop03, 0, Passive_Client, Node_A, 63, From 3 3

CMD_OnLoop_03, DI_OnLoop03, 0, Passive_Client, Node_A, 63, On 3 3

CMD_FromLoop_4, DI_FromLoop04, 0, Passive_Client, Node_A, 63, From 4 3

CMD_OnLoop_04, DI_OnLoop04,, 0, Passive_Client, Node_A, 63, On 4 3

data

FS-8700-127 Hanning & Kahl HCS-R Manual Page 11 of 17

5. Configuring the FieldServer as a HCS-R 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 Hanning & Kahl HCS-R Client.

The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for HCS-R 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

Port

Protocol

Baud* Specify baud rate
Parity* Specify parity
Data_Bits*

Stop_Bits*

Handshaking* Specify hardware handshaking

Server_Hold_Timeout*

Specify which port the device is
connected to the FieldServer

Specify protocol used

Specify data bits

Specify stop bits

Specifies the time that the FieldServer
will reserve the Server side connection
while waiting for the Client side to
update data in Data_Array (if
necessary)

P1-P83

HCS-R
HCSR
H&K HCS-R

9600 (Vendor Limitation)
None (Vendor Limitation)

8 (Vendor Limitation)

1
None (Vendor Limitation)

>1.0s, 2.0s

Example

// Server Side Connections

Connections
Port, Protocol, Baud, Parity, Handshaking
P8, HCS-R, 9600, None, None

3

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction

manual for details of the ports available on specific hardware.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 12 of 17

5.2. Server Side Node Descriptors

Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for Node

Node_ID

Protocol Specify protocol used

Server_Hold_Timeout*

Station address of physical server
Node

Specifies the time that the
FieldServer will reserve the Server
side connection while waiting for
the Client side to update data in
Data_Array (if necessary)

Example

// Server Side Nodes

Nodes
Node_Name, Node_ID, Protocol
HCSR_01, 240, HCS-R

Up to 32 alphanumeric
characters

240

HCS-R
HCSR
H&K HCS-R

>1.0s, 2.0s

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 13 of 17

5.3. Server Side Map Descriptors

5.3.1. FieldServer Specific 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

Server_Hold_Timeout*

data is to be stored in the
FieldServer

Function of Server Map
Descriptor
Specifies the time that the
FieldServer will reserve the
Server side connection while
waiting for the Client side to
update data in Data_Array (if
necessary)

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

Server

>1.0s, 2.0s

5.3.2. Driver Specific Map Descriptor Parameters

Column Title Function Legal Values

Node_Name

Length Length of Map Descriptor 22

Data_Type*

Name of Node to fetch data
from

Specify format of the data to
serve.
Refer to Appendix A

One of the Node names
specified in “Client Node
Descriptor” above

Digi_Input
Ana_Input

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

The number of items

within the Data Array

which will be used to

prepare the response

to the HCS-R client.

See Appendix A for

more detail.

One of the Nodes

described in

Server Side Node

Descriptors

section

The starting location

of data to serve

within the Data Array

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

5.3.3. Map Descriptor Example. - SMD_HCSR_01 Map Descriptor to Serve HCS-R clients.

One of the Data

described in

Data_Array

section. This Data

FS-8700-127 Hanning & Kahl HCS-R Manual Page 14 of 17

// Server Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Length, Scada_Hold_Timeout

SMD_HCSR_01, DA_HCSR, 0, Server, HCSR_01, 22, 5

Array name

data to be served

Array holds the

FS-8700-127 Hanning & Kahl HCS-R Manual Page 15 of 17

Appendix A. Advanced Topics

Appendix A.1. 1. How Client Stores Data:

The HCS will be polled by an RDBC Map Descriptor and data will be stored in the
DA_Current Data Array in the following fashion if parameter HCSR_Data_Stages >1:

• New data is stored as current data.

• If data is changed, last current data is moved to 2nd Stage, 2nd Stage data is moved

to 3rd stage and 3rd stage data is lost.

Appendix A.1.1. Data_Type is Ana_Input or not specified

Data Array Offset Description

Current Data

0 - 18 Data bits ( 0 - 1 )
19 Receipt ok ( 0 ), Disturbance ( 1 )
20 From Loop ( 0 ), On Loop ( 1 )
21 Loop Number (1,2,3,4) as integer

2nd (Previous) Data

24 – 42 Data bits ( 0 – 1 )
43 Receipt ok ( 0 ), Disturbance ( 1 )
44 From Loop ( 0 ), On Loop ( 1 )
45 Loop Number (1,2,3,4) as integer

3rd (Prior to previous) Data

48 – 66 Data bits ( 0 – 1 )
67 Receipt ok ( 0 ), Disturbance ( 1 )
68 From Loop ( 0 ), On Loop ( 1 )
69 Loop Number (1,2,3,4) as integer

Appendix A.1.2. Data_Type is Digi_Input

Data Array Offset (Say 0) Description

Current Data

0 - 18 Data bits ( 0 - 1 )
19 Receipt ok ( 0 ), Disturbance ( 1 )
20 From Loop ( 0 ), On Loop ( 1 )
21,22,23 3 bits for Loop Number

Offsets
21 22 23
1 0 0 –Loop 1
0 1 0 –Loop 2
1 1 0 –Loop 3
0 0 1 –Loop 4

2nd (Previous) Data

24 – 42 Data bits ( 0 – 1 )
43 Receipt ok ( 0 ), Disturbance ( 1 )
44 From Loop ( 0 ), On Loop ( 1 )
45 Loop Number (1,2,3,4) in 3 bits as above

3rd (Prior to previous) Data

48 – 66 Data bits ( 0 – 1 )
67 Receipt ok ( 0 ), Disturbance ( 1 )
68 From Loop ( 0 ), On Loop ( 1 )
69 Loop Number (1,2,3,4) in 3 bits as above

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 16 of 17

The same data will be stored in a Loop based Data Array which will then have the last
known data for each loop

Data Array Offset Description
Current Data

0 - 18 Data bits ( 0 – 1)
19 Receipt ok ( 0 ), Disturbance ( 1 )
20 From Loop ( 0 ), On Loop ( 1 )

2nd (Previous) Data

21 – 39 Data bits ( 0 – 1)
40 Receipt ok ( 0 ), Disturbance ( 1 )
41 From Loop ( 0 ), On Loop ( 1 )

3rd (Prior to previous) Data

42 – 60 Data bits ( 0 – 1)
61 Receipt ok ( 0 ), Disturbance ( 1 )
62 From Loop ( 0 ), On Loop ( 1 )

Appendix A.2. 2. How Server expects Data:

The Server expects data in the following format in order to constitute its response to HCS-R
Clients.

Appendix A.2.1. Data_Type is Ana_Input or not specified

Data Array Offset

0 - 18 Data bits ( 0 - 1 )
19 Receipt ok ( 0 ), Disturbance ( 1 )
20 From Loop ( 0 ), On Loop ( 1 )
21 Loop Number (0,1,2,3)

Description

Appendix A.2.2. Data_Type is Digi_Input

Data Array Offset (say 0)

0 - 18 Data bits ( 0 - 1 )
19 Receipt ok ( 0 ), Disturbance ( 1 )
20 From Loop ( 0 ), On Loop ( 1 )

2 bits for Loop Number
Offsets
21 22

21,22

0 0 –Loop 1
1 0 –Loop 2
0 1 –Loop 3
1 1 –Loop 4

.

Description

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8700-127 Hanning & Kahl HCS-R Manual Page 17 of 17

THIS PAGE INTENTIONALLY LEFT BLANK

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]