Summary of the content on the page No. 1
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-60 Gardner Denver Auto Sentry
ES/RS2000
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Summary of the content on the page No. 2
FS-8700-60 Gardner Denver Manual Table of Contents TABLE OF CONTENTS 1. Gardner Denver Auto Sentry ES/RS2000 Description....................................... 1 2. Driver Scope of Supply........................................................................................ 2 1.01 Supplied by FieldServer Technologies for this driver ....................................... 2 rd 1.02 Provided by the Supplier of 3 Party Equipment.............................................. 2 rd 2.1
Summary of the content on the page No. 3
FS-8700-60 Gardner Denver Manual Page 1 of 11 1. Gardner Denver Auto Sentry ES/RS2000 Description The Gardner Denver Auto Sentry ES/RS2000 driver allows the FieldServer to transfer data from devices over either RS-232 or RS-485 using Gardner Denver Auto Sentry ES/RS2000 protocol. The driver can be configured to communicate with ES Controllers with software versions V2.0X, V2.1X and RS2000 Controllers with software versions V4.0X The client driver implements the following fun
Summary of the content on the page No. 4
FS-8700-60 Gardner Denver Manual Page 2 of 11 2. Driver Scope of Supply 1.01 Supplied by FieldServer Technologies for this driver FieldServer Technologies Description PART # FS-8915-10 UTP cable (7 foot) for RS-232 use FS-8917-03 RJ45 to DB9M connector adapter FS-8700-60 Driver Manual rd 1.02 Provided by the Supplier of 3 Party Equipment rd 2.1.1. Required 3 Party Hardware Part # Description - ES/RS2000 controller rd 2.1.2. Required 3 Party Software None. rd 2.1.3. R
Summary of the content on the page No. 5
FS-8700-60 Gardner Denver Manual Page 3 of 11 3. Hardware Connections The FieldServer is connected to the ES/RS2000 Controller as shown in the connection drawing below: Configure the ES/RS2000 Controller according to manufacturer’s instructions. 1.03 Hardware Connection Tips / Hints If inter-controller communications are set up for the controller, connect to the RS-232 port only. If inter-controller communications are not used, connect to either the RS- 232 or RS-485 po
Summary of the content on the page No. 6
FS-8700-60 Gardner Denver Manual Page 4 of 11 4. Configuring the FieldServer as a Gardner Denver Auto Sentry ES/RS2000 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 parame
Summary of the content on the page No. 7
FS-8700-60 Gardner Denver Manual Page 5 of 11 1.05 Client Side Connection Descriptions Section Title Connections Column Title Function Legal Values Specify which port the device 1 Port is connected to the P1-P8, R1-R2 FieldServer Protocol Specify protocol used Gardner_Denver Baud* Specify baud rate 1200, 9600 (match to Controller) Parity* Specify parity None Data_Bits* Specify data bits 7 Stop_Bits* Specify stop bits 1 Specify hardware Handshaking* None handshaking
Summary of the content on the page No. 8
FS-8700-60 Gardner Denver Manual Page 6 of 11 1.06 Client Side Node Descriptors Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Node_Name Provide name for node characters Unit number connected to an Node_ID 1-8 ES/RS2000 controller Protocol Specify protocol used Gardner_Denver Specify which port the device is 1 Connection P1-P8, R1-R2 connected to the FieldServer Sets the protocol to be used for ES V2.0X Node_Type* different Controller so
Summary of the content on the page No. 9
FS-8700-60 Gardner Denver Manual Page 7 of 11 4.1.2. Driver Related Map Descriptor Parameters Column Function Legal Values Title Name of Node to fetch data One of the node names specified Node_Name from in “Client Node Descriptor” above Service_Data, Operating_Mode, Gar_cmd Data poll commands Operating_Data Available with Service_Data: All, Advisories, Shutdown_codes, Hourmeter_shutdown, Hourmeter_total, Hourmeter_loaded, Hourmeter_temp, Data fields in a data poll Hour
Summary of the content on the page No. 10
FS-8700-60 Gardner Denver Manual Page 8 of 11 4.1.4. Map Descriptor Example 1 – Polling all available Controller Data Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Gar_cmd, Gar_data, Scan_Interval GD_MBA1, DA_Service_Data, 0, RDBC, Node_1, Service_Data, All, 1.0s GD_MBA2, DA_Oper_Mode, 0, RDBC, Node_1, Operating_Mode, All, 1.0s GD_MBA3, DA_Oper_Data, 0, RDBC, Node_1, Operating_Data, All, 1.0s Note the active Read Block Continuous
Summary of the content on the page No. 11
FS-8700-60 Gardner Denver Manual Page 9 of 11 4 4 Motor current amps 4.1.5. Map Descriptor Example 2 - Polling only specific data items Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Gar_cmd, Gar_data, Scan_Interval GD_MBA1, DA_Hourmeter, 0, RDBC, Node_1, Service_Data, Hourmeter_total, 1.0s GD_MBA2, DA_Oper_Mode, 0, RDBC, Node_1, Operating_Mode, Oper_mode, 1.0s GD_MBA3, DA_Motor_Amps, 0, RDBC, Node_1, Operating_Data, Motor_current, 1.0s N
Summary of the content on the page No. 12
FS-8700-60 Gardner Denver Manual Page 10 of 11 Appendix 1. Advanced Topics Appendix 1.1. Can I use only Passive Client mapdescs ? No. A passive client map descriptor must be used after an active RDBC map descriptor. The driver uses the active map descriptors to poll the Controller and then searches for Passive Client map descriptors with matching Node_Name and Gar_Cmd fields. It then stores the data items as specified by the Gar_data field from the data collected by the preceding
Summary of the content on the page No. 13
FS-8700-60 Gardner Denver Manual Page 11 of 11 Appendix 2. Revision History Driver Doc. Date Resp Format Comment Ver. Rev. 9/2/02 JDM 1.00a 1 Applying new template. 4/12/04 DR DR 1.02b 2 Updated 7/12/04 DR DR 1.03a 3 Updated connection diagram Redrew connection diagram. 7/16/04 Meg Meg 1.03a 4 Reformatted document. Replaced connection diagram with 8/24/04 Meg Meg 1.03a 5 original created by Deon. 12/29/04 JD 1.03a 6 Releasing FieldServer Technologies 1991 Tarob Court
