Fieldserver Hanning Fs 8700 127 Users Manual 127_Hanning_Kahl_HCS R
HCS-R to the manual e140df55-ccdc-41cb-91cd-369591d9a276
2015-02-09
: Fieldserver Fieldserver-Hanning-Fs-8700-127-Users-Manual-551138 fieldserver-hanning-fs-8700-127-users-manual-551138 fieldserver pdf
Open the PDF directly: View PDF 
.
Page Count: 17
| Download | |
| Open PDF In Browser | View PDF |
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 Driver Version: 1.00 Document Revision: 9 FS-8700-127 Hanning & Kahl HCS-R Manual Table of Contents TABLE OF CONTENTS 1. 2. HANNING & KAHL HCS-R DESCRIPTION.................................................................... 3 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: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 1. Page 3 of 17 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: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 2. Page 4 of 17 Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies PART # FS-8915-10 FS-8700-127 Description UTP cable (7 foot) for RS-232 use Driver Manual. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 3. Page 5 of 17 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 (408)-262-2299 FIELDSERVER HANNING KAHL CONNECTION DIAGRAM BASE NAME: FILE NAME: 3.1. FS-8700-127 DATE: 2/12/08 BY: MC Hardware Connection Tips / Hints 1. Loop back RTS CTS if it is required by the other device. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 4. Page 6 of 17 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 Data_Array_Name Data_Array_Format Data_Array_Length Function Provide name for Data Array 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. Legal Values Up to 15 alphanumeric characters Float, Bit, UInt16, SInt16, Byte, 1-10,000 Example // Data Arrays Data_Arrays Data_Array_Name, DA_CURRENT, DI_FromLoop01, DI_OnLoop01, DI_FromLoop02, DI_OnLoop02, DI_FromLoop03, DI_OnLoop03, DI_FromLoop014 DI_OnLoop04, Data_Array_Format, Uint16, Bit, Bit, Bit, Bit, Bit, Bit, Bit, Bit, Data_Array_Length 22 22 22 22 22 22 22 22 22 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 4.2. Page 7 of 17 Client Side Connection Descriptions Section Title Connections Column Title Function Specify which port the device is connected to the FieldServer Port Protocol Specify protocol used Baud* Parity* Data_Bits* Stop_Bits* Handshaking* Poll_Delay* Specify baud rate Specify parity Specify data bits Specify stop bits Specify hardware handshaking Time between internal polls Legal Values P1-P8 1 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 Example // Client Side Connections Connections Port, P8, 4.3. Protocol, HCS-R, Baud, 9600, Parity, None, Handshaking, None, Poll_Delay 0.100s Client Side Node Descriptors Section Title Nodes Column Title Node_Name Node_ID Function Provide name for Node HCS-R station address of physical server Node Legal Values Up to 32 alphanumeric characters 240 (Protocol limit) Protocol Specify protocol used HCS-R HCSR H&K HCS-R Connection Specify which port the device is connected to the FieldServer P1-P8 1 Example // Client Side Nodes Nodes Node_Name, PLC 1, Node_ID, 240, Protocol, HCS-R, Connection 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. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 4.4. Client Side Map Descriptors 4.4.1. FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric characters Map_Descriptor_Name Name of this Map Descriptor Data_Array_Name Name of Data Array where data is to be stored in the FieldServer 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 Function Function Descriptor RDBC, Passive_Client 4.4.2. Map Name of Node to fetch data from HCSR_OnFrom HCSR_Loop Length Data_Type* HCSR_Data_Stages* Column Title Scan_Interval Client Function Node_Name 4.4.3. of Driver Related Map Descriptor Parameters Column Title 2 Page 8 of 17 For Passive_Client Map Descriptor 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 Legal Values One of the Node Names specified in “Client Node Descriptor” above On, From, OnFrom 1,2,3,4 22 or 24, 21 Ana_Input 2 Digi_Input 0,1,2,3 Timing Parameters Function Rate at which data is polled Legal Values ≥0.001s Default for Digi_Input FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com Map Descriptor Example: Read Data Page 9 of 17 Node_name Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_name Node_A, One of the Nodes declared in Client Node Section. This Node will be polled if Function is RDBC Function, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Function, RDBC, RDBC will cause read poll and Passive_Client is used to store data returned by response. Data_Array_Offset, 0, 0, 0, 0, 0, 0, 0, 0, Data_Array_Offset, 0, HCSR_Loop 1 1 2 2 3 3 4 4 Scan_Interval 5 How often (in seconds) to poll target device. Irrelevant if Function is Passive_Client HCSR_Onfrom From On From On From On From On Maximum number of placeholders for data storage. Length 21, 21, 21, 21, 21, 21, 21, 21, Length 22, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com Starting offset in Data Array to hold data Data_Array_Name, DI_FromLoop01, DI_OnLoop01, DI_FromLoop02, DI_OnLoop02, DI_FromLoop03, DI_OnLoop03, DI_FromLoop04, DI_OnLoop04,, Map_Descriptors Map_Descriptor_Name, CMD_FromLoop_01, CMD_OnLoop_01, CMD_FromLoop_02, CMD_OnLoop_02, CMD_FromLoop_03, CMD_OnLoop_03, CMD_FromLoop_4, CMD_OnLoop_04, Name one of the Data Array defined in Data_Array section to store data Data_Array_Name, DA_CURRENT, Map_Descriptors Map_Descriptor_Name, CMD_DI_HCSR_01, 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. 4.5. FS-8700-127 Hanning & Kahl HCS-R Manual Map Descriptor Example: Read Data and Keep History Page 10 of 17 Data_Array_Offset, 0, 0, 0, 0, 0, 0, 0, 0, RDBC will cause read poll and Passive_Client is used to store data returned by response. Length 63, 63, 63, 63, 63, 63, 63, 63, Length 72, HCSR_Loop 1 1 2 2 3 3 4 4 HCSR_Data_Stages 3 3 3 3 3 3 3 3 The number of data stages (data changes) to be kept as history. HCSR_Data_Stages 3 How often (in seconds) to poll target device. Irrelevant if Function is Passive_Client HCSR_Onfrom From On From On From On From On Scan_Interval, 5, Maximum number of placeholders for data storage. Node_name Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_A, Node_name Node_A, One of the Nodes declared in Client Node Section. This Node will be polled if Function is RDBC Function, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Passive_Client, Function, RDBC, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com Name one of the Data Array defined in Data_Array section to store data Data_Array_Name, DI_FromLoop01, DI_OnLoop01, DI_FromLoop02, DI_OnLoop02, DI_FromLoop03, DI_OnLoop03, DI_FromLoop04, DI_OnLoop04,, Map_Descriptors Map_Descriptor_Name, CMD_FromLoop_01, CMD_OnLoop_01, CMD_FromLoop_02, CMD_OnLoop_02, CMD_FromLoop_03, CMD_OnLoop_03, CMD_FromLoop_4, CMD_OnLoop_04, Data_Array_Offset, 0, Starting offset in Data Array to hold data Data_Array_Name, DA_CURRENT, Map_Descriptors Map_Descriptor_Name, CMD_DI_HCSR_01, 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. 4.6. FS-8700-127 Hanning & Kahl HCS-R Manual FS-8700-127 Hanning & Kahl HCS-R Manual 5. Page 11 of 17 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 Port Function Specify which port the device connected to the FieldServer Legal Values is HCS-R HCSR H&K HCS-R 9600 (Vendor Limitation) None (Vendor Limitation) 8 (Vendor Limitation) Protocol Specify protocol used Baud* Parity* Data_Bits* Specify baud rate Specify parity Specify data bits Stop_Bits* Handshaking* Specify stop bits Specify hardware handshaking 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) Server_Hold_Timeout* P1-P8 3 1 None (Vendor Limitation) >1.0s, 2.0s Example // Server Side Connections Connections Port, P8, Protocol, HCS-R, Baud, 9600, Parity, None, Handshaking 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: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 5.2. Page 12 of 17 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 Station address of physical server Node 240 Protocol Specify protocol used HCS-R HCSR H&K HCS-R Server_Hold_Timeout* 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) >1.0s, 2.0s Example // Server Side Nodes Nodes Node_Name, HCSR_01, Node_ID, 240, Protocol HCS-R FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com FS-8700-127 Hanning & Kahl HCS-R Manual 5.3. Page 13 of 17 Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function Map_Descriptor_Name Name of this Map Descriptor Data_Array_Name Name of Data Array where data is to be stored in the FieldServer Data_Array_Offset Starting location in Data Array Function Server_Hold_Timeout* 5.3.2. 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) Legal Values 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 Driver Specific Map Descriptor Parameters Column Title Node_Name Length Data_Type* Function Name of Node to fetch data from Length of Map Descriptor Specify format of the data to serve. Refer to Appendix A Legal Values One of the Node names specified in “Client Node Descriptor” above 22 Digi_Input Ana_Input FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com One of the Data Array name described in Data_Array section. This Data Array holds the data to be served to HCS-R client. Data_Array_Offset, 0, The starting location of data to serve within the Data Array Data_Array_Name, DA_HCSR, Node_Name, HCSR_01, One of the Nodes described in Server Side Node Descriptors section Function, Server, Scada_Hold_Timeout 5 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. Length, 22, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com Map_Descriptors Map_Descriptor_Name, SMD_HCSR_01, Page 14 of 17 Map Descriptor Example. - SMD_HCSR_01 Map Descriptor to Serve HCS-R clients. // Server Side Map Descriptors 5.3.3. FS-8700-127 Hanning & Kahl HCS-R Manual 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 Current Data 0 - 18 19 20 21 nd 2 (Previous) Data 24 – 42 43 44 45 rd 3 (Prior to previous) Data 48 – 66 67 68 69 Appendix A.1.2. Description Data bits ( 0 - 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Loop Number (1,2,3,4) as integer Data bits ( 0 – 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Loop Number (1,2,3,4) as integer Data bits ( 0 – 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Loop Number (1,2,3,4) as integer Data_Type is Digi_Input Data Array Offset (Say 0) Current Data 0 - 18 19 20 21,22,23 Description Data bits ( 0 - 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) 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 nd 2 (Previous) Data 24 – 42 43 44 45 rd 3 (Prior to previous) Data 48 – 66 67 68 69 Data bits ( 0 – 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Loop Number (1,2,3,4) in 3 bits as above Data bits ( 0 – 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) 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: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com 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 Current Data 0 - 18 19 20 nd 2 (Previous) Data 21 – 39 40 41 rd 3 (Prior to previous) Data 42 – 60 61 62 Description Data bits ( 0 – 1) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Data bits ( 0 – 1) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Data bits ( 0 – 1) Receipt ok ( 0 ), Disturbance ( 1 ) 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 Array Offset 0 - 18 19 20 21 Appendix A.2.2. Data_Type is Ana_Input or not specified Description Data bits ( 0 - 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) Loop Number (0,1,2,3) Data_Type is Digi_Input Data Array Offset (say 0) 0 - 18 19 20 21,22 Description Data bits ( 0 - 1 ) Receipt ok ( 0 ), Disturbance ( 1 ) From Loop ( 0 ), On Loop ( 1 ) 2 bits for Loop Number Offsets 21 22 0 0 –Loop 1 1 0 –Loop 2 0 1 –Loop 3 1 1 –Loop 4 . FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.FieldServer.com Tel: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com 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: 408 262-2299 Fax: 408-262-2269 Toll_Free: 888-509-1970 email: support@FieldServer.com
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Count : 17 Producer : PrimoPDF Create Date : 2008:05:05 03:37:18 Modify Date : 2008:05:05 03:37:18 Title : Microsoft Word - FS-8700-127_Hanning_Kahl_HCS-R.doc Creator : PrimoPDF http://www.primopdf.com Author : AdministratorEXIF Metadata provided by EXIF.tools