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
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 functionality:
• Polls controllers for service and maintenance data.
• Polls controllers for operating mode data.
• Polls controllers for operating data.
The driver can poll up to 8 units connected to one ES/RS2000 Controller. It always sets
the active unit on the ES/RS2000 Controller before polling for data even if consecutive
polls are for the same unit. This is done to prevent synchronization problems.
Gardner Denver ES/RS2000 Controllers implements three message types for which the
driver can poll. The driver does not validate the message data fields for correct values
although it does validate data field lengths For example, shutdown codes reported by
V2.1 ES Controllers range from 0 to 27. If a code of 28 is reported, the driver will not
flag it as an error since codes have to be interpreted by the operator. However, a
message length longer than 2 digits will be reported as an error.
Max Nodes Supported
FieldServer Mode Nodes
Comments
A client node can communicate with up to 8 units
connected to a ES/RS2000 Controller
Client
1
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
PART #
Description
FS-8915-10
FS-8917-03
FS-8700-60
UTP cable (7 foot) for RS-232 use
RJ45 to DB9M connector adapter
Driver Manual
1.02
Provided by the Supplier of 3rd Party Equipment
2.1.1.
Required 3rd Party Hardware
Part #
Description
-
ES/RS2000 controller
2.1.2.
Required 3rd Party Software
None.
2.1.3.
Required 3rd Party Configuration
The ES/RS2000 Controller must be set up in the correct mode to support either
RS-232 or RS-485 communications to an external monitoring system. Please
refer to manufacturer’s setup instructions.
2.1.4.
Optional Items
PART #
Vendor/Manufacturer
Description
485LDRC B&B Electronics
RS-232/RS-485 converter
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 port of the Controller.
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 parameters necessary for configuring the FieldServer
to communicate with a Gardner Denver Auto Sentry ES/RS2000 Controller.
1.04
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 Gardner Denver Auto Sentry
ES/RS2000 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
Provide data format. Each Data Float, UInt16, Uint32,
Data_Array_Format
Data_Array_Length
Array can only take on one
format.
Byte, Packed_Byte,
Swapped_Byte
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,
DA_Service_Data,
DA_Oper_Mode,
DA_Oper_Data,
Data_Format,
Uint32,
UInt16,
Data_Array_Length,
38
3
Uint16,
5
FS-8700-60 Gardner Denver Manual
Page 5 of 11
1.05
Client Side Connection Descriptions
Section Title
Connections
Column Title
Function
Specify which port the device
is connected to the
FieldServer
Legal Values
P1-P8, R1-R21
Port
Protocol
Baud*
Parity*
Specify protocol used
Specify baud rate
Specify parity
Gardner_Denver
1200, 9600 (match to Controller)
None
Data_Bits*
Stop_Bits*
Specify data bits
Specify stop bits
7
1
Specify hardware
handshaking
Handshaking*
None
Poll_Delay*
Timeout*
Time between internal polls
Time to wait for response
> = 0.2s
> = 0.6s
Example
// Client Side Connections
Connections
Port,
Protocol
Gardner_Denv
er
P1,
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-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
characters
Node_Name
Provide name for node
Unit number connected to an
ES/RS2000 controller
Specify protocol used
Specify which port the device is
connected to the FieldServer
Node_ID
Protocol
1-8
Gardner_Denver
P1-P8, R1-R21
Connection
Sets the protocol to be used for ES V2.0X
Node_Type*
different Controller software
versions
ES V2.1X
RS2000 V4.0X
Example
// Client Side Nodes
Nodes
Node_Name,
Node_1,
Node_2,
Node_ID,
1,
2,
Protocol,
Gardner_Denver,
Gardner_Denver,
Connection
P1
P1
1.07
Client Side Map Descriptors
4.1.1.
FieldServer Related Map Descriptor Parameters
Column Title
Function
Name of this Map
Descriptor
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array
where data is to be
One of the Data Array
names from “Data Array”
Data_Array_Name
stored in the FieldServer section above
Starting location in Data
Array
Function of Client Map
Descriptor
0 to maximum specified in
“Data Array” section above
Data_Array_Offset
Function
RDBC, Passive_Client
FS-8700-60 Gardner Denver Manual
Page 7 of 11
4.1.2.
Column
Driver Related Map Descriptor Parameters
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,
Operating_Data
Gar_cmd
Data poll commands
Available with Service_Data: All,
Advisories, Shutdown_codes,
Hourmeter_shutdown,
Hourmeter_total,
Hourmeter_loaded,
Hourmeter_temp,
Hourmeter_tmp_st, Last_maint_A,
Last_maint_B, Oilage
Data fields in a data poll
command response
message. Can be used to
poll for all or specific data
or just isolate specific items
in a “All” poll.
Gar_data
Available with Operating_Mode:
All, Oper_mode, Seq_number,
Oper_state
Available with Operating_Data: All,
System_pressure, Filter_pressure,
Discharge_temp, Reservoir_temp,
Motor_current
4.1.3.
Timing Parameters
Legal
Values
Column Title
Function
Rate at which data is polled. Note that the
Scan_Interval Poll_Delay Connection parameter affects the
effective scan interval.
≥0.1s
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,
GD_MBA1,
GD_MBA2,
Data_Array_Name,
DA_Service_Data,
DA_Oper_Mode,
DA_Oper_Data,
Data_Array_Offset,
Function, Node_Name, Gar_cmd,
Gar_data, Scan_Interval
0,
0,
0,
RDBC,
RDBC,
RDBC,
Node_1,
Node_1,
Node_1,
Service_Data,
Operating_Mode,
Operating_Data,
All,
All,
All,
1.0s
1.0s
1.0s
GD_MBA3,
Note the active Read Block Continuous map descriptor
function responsible for polling the Controller.
The Gar_data field is set to “All”
indicating that all available data is
polled for.
The Gar_cmd field indicates the poll
is for Operating Data.
Data will be stored as follows:
Offset
Description
Units
DA_Service_Data
0
Advisories
see ES/RS2000 Controller spec
1-20
21
22
23-28
29-34
35
10x (Shutdown code / Hourmeter reading) pairs
Current total runtime hourmeter reading
Current loaded runtime hourmeter reading
6x Current temp hourmeters [H1] – [H6]
6x Stored temp hourmeters [OH1] – [OH6]
Last maintenance A
see ES/RS2000 Controller spec
Hours
Hours
Hours
Hours
Hours
36
Last maintenance B
Hours
37
Oilage
Unknown, see ES/RS2000 controller spec
Operating mode data
0
1
2
Operating mode indication
Sequence number2
see ES/RS2000 Controller spec
see ES/RS2000 Controller spec
see ES/RS2000 Controller spec
Unit operating state3
Operating data
0
1
2
3
System pressure
Filter pressure
Discharge temperature
Reservoir temperature
divide by 16 for pressure in psig
divide by 16 for pressure in psig
divide by 16 for temperature in degrees F
divide by 16 for temperature in degrees F
2
ES V2.0X Controllers do not respond with this field
ES V2.0X Controllers do not respond with this field
3
FS-8700-60 Gardner Denver Manual
Page 9 of 11
4
Motor current4
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,
GD_MBA2,
GD_MBA3,
DA_Hourmeter,
DA_Oper_Mode,
DA_Motor_Amps,
0,
0,
0,
RDBC,
RDBC,
RDBC,
Node_1,
Node_1,
Node_1,
Service_Data,
Operating_Mode, Oper_mode,
Operating_Data, Motor_current,
Hourmeter_total, 1.0s
1.0s
1.0s
Note the active Read Block Continuous map
descriptor function responsible for polling the
Controller.
The Gar_data field is set to
“Motor_current” indicating that only this
data item will be stored.
The Gar_cmd is set to indicate Operating
Data must be polled for.
4.1.6.
Map Descriptor Example 3 - Polling all data and isolating specific data items
Map_Descriptor_Name,
GD_MBA1,
GD_MBA2,
Data_Array_Name,
DA_Service_Data,
DA_Oilage,
Data_Array_Offset,
Function,
RDBC,
Passive_Client,
Passive_Client,
Node_Name,
Node_1,
Node_1,
Gar_cmd,
Gar_data,
All,
Oilage,
Scan_Interval
1.0s
-
-
0,
0,
0,
Service_Data,
Service_Data,
Service_Data,
GD_MBA3,
DA_Hourmeter,
Node_1,
Hourmeter_total,
GD_MBA4,
GD_MBA5,
DA_Oper_Mode,
DA_Oper_State,
0,
0,
RDBC,
Passive_Client,
Node_1,
Node_1,
Operating_Mode,
Operating_Mode,
All,
Oper_state,
1.0s
-
GD_MBA6,
GD_MBA7,
DA_Oper_Data,
DA_Disch_Temp,
0,
0,
RDBC,
Passive_Client,
Node_1,
Node_1,
Operating_Data,
Operating_Data,
All,
1.0s
-
Discharge_temp,
Note the use of the passive map descriptor function. This map descriptor
does not poll but receives data from the active map descriptor since the
Gar_cmd and Node_Name fields match.
Note, the Gar_cmd
indicates polling for
Operating data.
Note that a specific data item,
“Discharge_temp” is isolated here by
still using the same Gar_cmd as the
active map descriptor.
4
RS2000 V4.0X Controllers set this field to zero
FS-8700-60 Gardner Denver Manual
Appendix 1. Advanced Topics
Page 10 of 11
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 active map descriptor.
Appendix 1.2.
Data length of specific polls versus “All” data polls
The length of the data packet retrieved from the Controller during a poll is always
fixed for each of the three types of data polls. When specifying a specific Gar_data
item on a RDBC active map descriptor, the driver still gets all data of Gar_cmd type
from the controller in a single poll, but only stores the data item in question.
FS-8700-60 Gardner Denver Manual
Page 11 of 11
Appendix 2. Revision History
Driver
Doc.
Rev.
1
2
3
Date
Resp Format
Comment
Ver.
9/2/02
4/12/04 DR
7/12/04 DR
JDM
1.00a
1.02b
1.03a
Applying new template.
Updated
DR
DR
Updated connection diagram
Redrew connection diagram.
Reformatted document.
Replaced connection diagram with
original created by Deon.
Releasing
7/16/04 Meg Meg
1.03a
4
8/24/04 Meg Meg
12/29/04 JD
1.03a
1.03a
5
6
|