FieldServer FS-8704-49 User Manual

Driver Version:

1.07

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8704-49 Data Aire (DAP)

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2001

Document Revision: 9

FS-8700-49_Data_Aire_DAP Table of Contents

TABLE OF CONTENTS

1.

Data Aire Description..................................................................................................... 4

1.1.

Performance Issues - DARTIII only............................................................................ 4

1.2.

Data Alarm Network Module Network LED Operation ................................................ 4

2.

Driver Scope of Supply .................................................................................................. 5

2.1.

Supplied by FieldServer Technologies for this driver.................................................. 5

3.

Hardware Connections .................................................................................................. 6

4.

Configuring the FieldServer as a Data Aire Client ....................................................... 7

4.1.

Data Arrays/Descriptors............................................................................................. 7

4.2.

Client Side Connection Descriptions .......................................................................... 8

4.3.

Client Side Node Descriptors ..................................................................................... 9

4.4.

Client Side Map Descriptors....................................................................................... 9

4.4.1. FieldServer Related Map Descriptor Parameters.................................................... 9

4.4.2. Driver Related Map Descriptor Parameters............................................................10

4.4.3. Timing Parameters ................................................................................................10

4.4.4. Map Descriptor Example 1 - Everything.................................................................11

4.4.5. Map Descriptor: Example 2 – Writing a Set-Point. .................................................11

4.4.6. Map Descriptor: Example 3 – Writing multiple points using one message..............12

Appendix A. Data Tables ....................................................................................................13

Appendix A.1. Data Table 1: Array Locations of ‘Everything’...............................................13

Appendix A.2. Data Table 2 - Point Descriptions.................................................................18

Appendix A.3. Data Table 3 - Unit Types ............................................................................25

Appendix B. Advanced Topics...........................................................................................26

Appendix B.1. Additional Driver Specific Map Descriptor Parameters .................................26

Appendix B.2. DA_Func Parameter - Permitted values.......................................................27

Appendix B.3. DA_Field Parameter - Permitted values. ......................................................28

Appendix B.4. DA_Method Parameter Values and Notes....................................................28

Appendix B.5. Advanced Map Descriptor 1:Collecting Data From Multiple Fileds ...............29

Appendix B.6. Advanced Map Descriptor Example 2:Collecting Error Messages................30

Appendix B.7. Advanced Map Descriptor Example 3: Using Special DA Field ....................30

Appendix B.8. Advanced Map Descriptor Example 4: - Using DA_Assoc............................31

Appendix B.9. Advanced Map Descriptor: Example 5 - Using a special / diagnostic
command.: 31

Appendix B.10. Advanced Map Descriptor: Example 6 – Turning Dap’s On/Off..................32

Appendix C. Troubleshooting Tips....................................................................................33

Appendix C.1. Bad Values ..................................................................................................33

Appendix C.2. Dead Nodes.................................................................................................33

Appendix C.3. Noise ...........................................................................................................33

Appendix C.4. Ignored Messages .......................................................................................33

Appendix C.5. Driver limitation............................................................................................33

Appendix C.6. Baud Rate....................................................................................................33

Appendix C.7. Wiring. .........................................................................................................33

Appendix C.8. Stuck Unit. ...................................................................................................34

Appendix C.9. Number of Units...........................................................................................34

Appendix D. Error Messages .............................................................................................35

Appendix D.1. Exposing Driver Statistics ............................................................................38

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-49_Data_Aire_DAP Table of Contents

Appendix E. Writing data to DAP Devices ........................................................................40

Appendix E.1. Background..................................................................................................40

Appendix E.2. Associated Map Descriptors.........................................................................40

Appendix E.3. Starting/Stopping DAP devices ....................................................................41

Appendix E.4. DAP Unit Errors ...........................................................................................41

Appendix E.5. Using DA_Assoc correctly with Writes/Toggling Values ...............................46

Appendix F. Write Through’s.............................................................................................47

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-49_Data_Aire_DAP Page 4 of 48

1. Data Aire Description

The Data Aire Driver is capable of direct connection to a network of Data Aire DAP devices.
The FieldServer is connected in a RS-485 loop topology. Two FieldServer ports are required
per loop. The driver is an active client. All data is obtained by poll & response.

Connection to a DART is not supported by this driver.

The driver may be configured very simply (See Section 4.4). A number of advanced
configurations are also available and are described in Appendix B. The driver supports the
common message formats for common Data Aire DAP devices. A list of the supported
messages is provided in the manual.

The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.

1.1. Performance Issues - DARTIII only

Data Aire communication is based on a very low baud rate. In addition inter-message timing
constraints and overhead requirements for active messages in a Dart configuration add
significant time to each transaction. It is not possible to write a setpoint to a device until the
device has been successfully read, and the result of the write will not be seen until the next
read is complete. The result of a write may not be seen for some time due to slow
communications and significant inter poll delays.

1.2. Data Alarm Network Module Network LED Operation

DAP-II units communicate with a DART unit by using a Data Alarm Network Module. This
module provides a RS-485 communications link. Installed on the card are several LEDS.
The table below explains how the LEDS appear under normal (correctly functioning)
operation.

LED LED Appearance

The Network Module has a blown fuse detection circuit. If one (or more) of

FUSE

DS1 &
DS3

NETWORK

the fuses has an open circuit, then the FUSE LED will be lit. Normally, this
LED is dark.
Communications signals enter and leave the Network Module. These LEDS
reflect the communications activity. When first powered up, both LED's will
be lit and the illumination will be steady. As the DART communicates with
the network, both LED’s will begin to flicker in unison. All of the Network
Module LED’s will flicker at the same time.
At some point the DART will send a communication message to a specific
network-connected DAP-II that requires a reply to the DART. If the message
is received without error, the DAP-II will reply by engaging a relay on the
Network Module and transmitting a message. When this happens the
NETWORK LED will come on. Whenever a NETWORK LED is seen to
come on it means that the communications into the Network Module is
satisfactory. It is still possible to have a wiring problem downstream of the
module that prevents the message from being received by the DART

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-49_Data_Aire_DAP Page 5 of 48

2. Driver Scope of Supply

2.1. Supplied by FieldServer Technologies for this driver

FieldServer Technologies
PART #

Description

RS-485 connection adapter
FS-8700-49 Driver Manual.

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-49_Data_Aire_DAP Page 6 of 48

P1

A

A

A

3. Hardware Connections

The FieldServer is connected to the DAP devices as shown in connection drawing.

Configure the DAP devices according to manufacturer’s instructions

Dap/Chiller/Dap80

+OUT

-OUT

SHD

Dap/Chiller/Dap80

+IN

-IN

SHD

+OUT

-OUT

SHD

FOR THIS WIRING

ARRANGEMENT THIS

IS THE PRIMARY PORT

+IN

-IN

SHD

TO OTHER DEVICES

RS485

9600 N81

CONFIG PC

(RUISYS)

MODEL 8051

_

_

SYSTEM NODE: 8

GndFG_

+

Power

0V

DC AUX Power

Gnd_+

+

+12V 500m

12V 500m

5V 1.5A

Net 1

Net 2

5V 500 m

FG

Ethernet

10 Base T

Gnd_+

GndFG_

+

R2 R1

RS 485

(Opto - Isolated)

SECONDARY PORT

P8 P7 P6 P5 P4 P3 P2

GROUND 5

DTR 6
RTS 7

Tx 8

RS 232

1 Rx

18

2 CTS
3 DSR
4 GRO UND

R2 R1

RS 485

(Opto - Isolated)

MODEL 8051

MANUAL - DataAire

BASE NAME:

FILE NAME: T28700-49.VSD

DATE: 1/22/01

BY: MN

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-49_Data_Aire_DAP Page 7 of 48

4. Configuring the FieldServer as a Data Aire Client

For a detailed discussion on FieldServer configuration, please refer to the FieldServer
instruction 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 Data Aire 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 Data Aire 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

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

Data_Array_Format

Provide data format. Each Data
Array can only take on one format.

Packed_Bit, Byte,
Packed_Byte,
Swapped_Byte

Number of Data Objects. Must be

Data_Array_Length

larger than the data storage area
required by the Map Descriptors for

1-10,000

the data being placed in this array.

Example

// Data Arrays
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length,
DA_AI_01, UInt16, 200
DA_AO_01, UInt16, 200
DA_DI_01, Bit, 200
DA_DO_01, Bit, 200

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-49_Data_Aire_DAP Page 8 of 48

4.2. Client Side Connection Descriptions

Connections
Column Title Function Legal Values

This is the FieldServer port

Port

connected to the DART’s RS­232 port.
The return loop from the DAP

Secondary_Port*

devices is connected to this
port. (Loop connected to Tx+
& Tx- terminals.

Baud* Specify baud rate

Parity* Specify parity
Data_Bits*

Stop_Bits*

Protocol

Handshaking*

Poll Delay*

Specify data bits

Specify stop bits
Specify protocol used. Either

keyword may be used.
Specify hardware
handshaking

Time between internal polls

Example

// Client Side Connections

Connections
Port, Secondary Port, Protocol, Baud, Parity, Data_Bits, Stop_Bits, Poll_Delay
R1, R2, DAP, 2400, None, 8, 1, 0.100s

P1-P8, R1-R21
(P1-P8) requires 232/485
converter.

P1-P8, R1-R21
(R1-R2) requires 232/485
converter.

2400/96002 (Vendor
Limitation)

None
8

1

DAP, Daire

None

0-32000s, 1s

Use this port identifier in the client side node
configuration described in Section 4.3.

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.

2

DAP V9.5 or later supports 9600

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-49_Data_Aire_DAP Page 9 of 48

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 DAP

Connection

Example

// Client Side Nodes

Nodes
Node_Name Node_ID Protocol Connection
Unit1, 1, DAP, R1

Modbus station address of
physical server node

Specify which port the device is
connected to the FieldServer

1-259

P1-P8, R1-R23

This is the connection to the primary port identified with the
'Port' keyword in the connection configuration described in
Section 4.2

4.4. Client Side Map Descriptors

4.4.1. FieldServer Related Map Descriptor Parameters

Column Title Function Legal Values

Map_Descriptor_Name

Data_Array_Name

Data_Array_Offset

Function

Name of this Map
Descriptor
Name of Data Array
where data is to be
stored in the
FieldServer
Starting location in Data
Array
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, WRBC, WRBX

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-49_Data_Aire_DAP Page 10 of 48

4.4.2. Driver Related Map Descriptor Parameters

Column Title Function Legal Values

Node_Name

Name of Node to fetch data
from

Data_Type Data type Register, Coil, AI, DI

Length Length of Map Descriptor 1

Address Starting address of read block

Only required when the function
is a Read (rdbc).
Tells the driver to poll the

DA_Func*

device for all the data that is
available. The data is device
specific.
Other uses of this parameter
are discussed in Appendix B .
Required when the function is a
write (wrbc) or when the Map
Descriptor is associated with a
write by means of the

DA_Field

DA_Assoc parameter value.
This is the name of the data
field whose value you wish to
set in the device.
Other uses of this parameter
are discussed in Appendix B.
Use to associate passive Map
Descriptors with an active Map
Descriptor. Multiple fields can

DA_Assoc

be associated with one WRBC
Map Descriptor, thus writing
multiple values to one device
using just one message.

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

Not required for client
configuration - used in
simulation configuration only.

Everything – See Appendix A

See Appendix A.2 for a list of
permitted values.

Any positive integer. See
Appendix E

4.4.3. Timing Parameters

Column Title Function Legal Values

Scan_Interval Rate at which data is polled ≥0.1s

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 scan interval is used to

control the minimum time

between poll messages. It

may take several polls /

messages to obtain a

complete data set (the

number is dependent on the

This is how often the data will be written to

the device. Reduce the scan interval when

using a dart. The dart will only take control

of the devices when the network has been

idle for at least 50 seconds. If polls are

generated too often, the dart will never

exercise control.

Tells the

driver that

this Map

Descriptor is

used to (poll

&) store a

complete

data set from

the unit.

to zero and the length to

1300 as this is the max

number of data points

Always set the Address

that can be read

Select the data field from Appendix B.3.

Ensure that the keyword can be written to the

unit type identified as unit1. Example. If unit1 is a Chiller then the above

Map Descriptor will not function correctly as it

can only be used to write to unit types

7,9,14,15.

The node name

connects the Map

Descriptor to a node

definition which in

turn is connected to

a port.

Always leave the

4.4.4. Map Descriptor Example 1 - Everything

It is recommended

that the format of

the Data Array be

FLOAT as the data

read from the unit

consists of bits,

bytes and real

numbers.

The data that is obtained from ‘unit1’ is dependent on the type of device. Irrespective of the device type the arrangement of data,

stored in DA_01, is fixed. If a data field cannot be obtained from ‘unit1’ then the array is left with a zero value for that data field.

FS-8700-49_Data_Aire_DAP Page 11 of 48

The FieldServer listens passively for all possible data from the device called ‘unit1’ and stores the data in an array called ‘DA_01’.

// Client Side Map Descriptors

Map Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Address, Length, DA_Func, Scan_Interval

Read_Node_01, DA_01, 0, RDBC, Unit1, 0, 1300, Everything, 2.5s

4.4.5. Map Descriptor: Example 2 – Writing a Set-Point.

// Client Side Map Descriptors

Map Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Address Length, DA_Field, Scan_Interval

Write_SP_01, DA_SETPOINTS, 0, WRBC, Unit1, 0, 1, nom_h_setpt, 120s

.

address set to zero

and the length as

one

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

The setpoint is

obtained from

this Data Array.

this way the driver will use only one message to write to the device. The

message will be built using both Map Descriptors. This method reduces the

Associate the passive Map Descriptor to the active (wrbc) Map Descriptor. In

communication load. The association is made using the DA_Assoc parameter. Use unique positive

integers. Omitting the DA_Assoc parameter when using ‘passive’ Map

Descriptors will produce ambiguous results.

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.4.6. Map Descriptor: Example 3 – Writing multiple points using one message.

will update two fields, the nom_h_setpt and the t_setpt.

The write Map Descriptor. must precede the passive.

A 'Write' and a passive to the same node. This write

FS-8700-49_Data_Aire_DAP Page 12 of 48

// Client Side Map Descriptors

Map Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name, Address, Length, DA_Field, DA_Assoc, Scan_Interval

Write_Map Descriptor_1, DA_SETPOINTS, 0, WRBC, Unit1, 0, 1, nom_h_setpt, 2, 120s

Additional information is provided in Appendix B

Write_Map Descriptor_1, DA_SETPOINTS, 1, passive, Unit1, 0, 1, t_setpt, 2,

For a Dart, use wrbx instead of wrbc.

FS-8700-49_Data_Aire_DAP Page 13 of 48

Appendix A. Data Tables

Appendix A.1. Data Table 1: Array Locations of ‘Everything’

In the following table the array location indicates the offset in the Data Array at which a data
field can be found. (This offset is relative to the offset specified in the Map Descriptor) The
columns headed 2, 3 … indicate the unit types for which the data fields are available. For
example: The field ‘d_temp’ can be read from unit types 2, 5,6,7,9 but not from any of the
other unit types. It is beyond the scope of this manual to describe each field and to indicate
valid ranges. Such information should be obtained from the Data Aire Corporation.

‘x’ Indicates Read only
‘X’ Indicates a point that can be read & written.
‘w’ Indicates a write only point.

Array

Location

1 1 1 Zone w w w w w w w w w

2 1 1 Inhibit w w w w w w w w w

3 4 1 unitType x x x x x x x x x x

4 2 1 temp x x x x x Dap-Stat

5 2 1 hum x x x x x Dap-Stat

6 2 1 d_temp x x x x x Dap-Stat

7 3 8 mode x x x x x Dap-Stat

23 3 8 hold x x x x x Dap-Stat

39 1 1 cs_on x x x x x Dap-Stat

40 1 1 hs_on x x x x x Dap-Stat

41 1 1 valvePCT x x x x x Dap-Stat

42 1 1 hVlvPCT x x x x x Dap-Stat

43 4 14

57 2 1 hiTemp x x x x x Dap-Stat

58 2 1 loTemp x x x x x Dap-Stat

59 2 1 hiHum x x x x x Dap-Stat

60 2 1 loHum x x x x x Dap-Stat

61 1 1 chilled_water x x x x x Dap-Stat

62 1 1 compressor_config x x x x x Dap-Stat

63 1 1 heat_strip_config x x x x x Dap-Stat

64 1 1 hum_config x x x x x Dap-Stat

65 1 1 csUtilPct x x x x x Dap-Stat

66 1 1 hsUtilPct x x x x x Dap-Stat

67 1 1 valveUtilPct x x x x x Dap-Stat

68 1 1 humUtilPCT x x x x x Dap-Stat

69 1 1 alrm_select_1 x x x x x Dap-Stat

70 1 1 alrm_select_2 x x x x x Dap-Stat

71 1 1 alrm_select_3 x x x x x Dap-Stat

72 1 1 alrm_select_4 x x x x x Dap-Stat

Method

Num

Elements

Data Field 2 3 4 5 6 7 8 9 14 15 Message Type

Errors - see Appendix E.4

for more information

x x x x x Dap-Stat

Dap-Config

Dap-Config

Dap-Unit

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-49_Data_Aire_DAP Page 14 of 48

Array

Location

73 3 56

185 1 1 runtime_c1 x x x x x Dap-Xtra

186 1 1 runtime_c2 x x x x x Dap-Xtra

187 1 1 runtime_c3 x x x x x Dap-Xtra

188 1 1 runtime_c4 x x x x x Dap-Xtra

189 1 1 runtime_ht1 x x x x x Dap-Xtra

190 1 1 runtime_ht2 x x x x x Dap-Xtra

191 1 1 runtime_ht3 x x x x x Dap-Xtra

192 1 1 runtime_hum x x x x x Dap-Xtra

193 1 1 runtime_evap x x x x x Dap-Xtra

194 1 1 runtime_cond x x x x x Dap-Xtra

195 1 1 runtime_dehum x x x x x Dap-Xtra

196 1 1 runtime_esc x x x x x Dap-Xtra

197 1 1 runtime_cwc x x x x x Dap-Xtra

198 4 20 errors x x x x x Dap-Xtra

218 6 10 errage x x x x x Dap-Xtra

258 1 1 version x x x x x Dap-Xtra

259 2 1 tmbmair x x x x x Dap-Xtra

260 2 1 tmbhum x x x x x Dap-Xtra

261 1 1 tmbairdb x x x x x Dap-Xtra

262 6 13 runtimes (as array) x x x x x Dap-Xtra

314 3 80 bitErrors x x x x x Dap-Xtra

474 4 1 adj_rate X X X Dap-Menu

478 1 1 alrm_delay_1 X X X Dap-Menu

479 1 1 alrm_delay_2 X X X Dap-Menu

480 1 1 alrm_delay_3 X X X Dap-Menu

481 4 1 alrm_enable_1 X X X Dap-Menu

482 4 1 alrm_enable_2 X X X Dap-Menu

483 4 1 alrm_enable_3 X X X Dap-Menu

484 4 1 alrm_select_1 X X X Dap-Menu

485 4 1 alrm_select_2 X X X Dap-Menu

486 4 1 alrm_select_3 X X X Dap-Menu

487 1 1 chilled_water X X X Dap-Menu

488 1 1 compressor_config X X X Dap-Menu

489 1 1 c_mode X X X Dap-Menu

490 2 1 fire_lim X X X Dap-Menu

491 1 1 heat_strip_config X X X Dap-Menu

492 1 1 hi_cal X X X Dap-Menu

493 1 1 hi_h_cal X X X Dap-Menu

494 2 1 hi_t_lim X X X Dap-Menu

495 1 1 humid_config X X X Dap-Menu

496 1 1 h_calib X X X Dap-Menu

497 1 1 lead_lag X X X Dap-Menu

Method

Num

Elements

Data Field 2 3 4 5 6 7 8 9 14 15 Message Type

bitErrors - see Appendix

E.4 for more information

x x x x x Dap-Stat

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-49_Data_Aire_DAP Page 15 of 48

Array

Location

498 1 1 loc_h_deadband X X X Dap-Menu

499 1 1 loc_h_setpt X X X Dap-Menu

500 2 1 loc_t_dband X X X Dap-Menu

501 2 1 loc_t_setpt X X X Dap-Menu

502 1 1 lo_cal X X X Dap-Menu

503 1 1 lo_h_lim X X X Dap-Menu

504 2 1 lo_t_lim X X X Dap-Menu

505 1 1 main_int X X X Dap-Menu

506 1 1 passwd_a X X X Dap-Menu

507 1 1 passwd_b X X X Dap-Menu

508 1 1 rst_mode X X X Dap-Menu

509 1 1 s_delay X X X Dap-Menu

510 2 1 t_calib X X X Dap-Menu

511 1 1 voice X X X Dap-Menu

512 1 1 vvrg X X X Dap-Menu

513 1 1 cat1 X X X Dap-Menu

514 1 1 cat2 X X X Dap-Menu

515 1 1 cat3 X X X Dap-Menu

516 2 1 d_calib X X X Dap-Menu

517 2 1 lo_d_lim X X X Dap-Menu

518 1 1 ptc X X X Dap-Menu

519 2 1 supplyT x x x Chiller-Stat

520 2 1 returnT x x x Chiller-Stat

521 4 1 coolOn1 x x x Chiller-Stat

522 4 2 coolOn2 x x x Chiller-Stat

523 4 2 coolOn3 x x x Chiller-Stat

524 2 1 valvePct x x x Chiller-Stat

525 4 1 pumpsOn x x x Chiller-Stat

526 4 1 condOn x x x Chiller-Stat

527 4 1 modFail x x x Chiller-Stat

528 2 1 hiSupT x x x Chiller-Stat

529 2 1 loSupT x x x Chiller-Stat

530 2 1 hiRetT x x x Chiller-Stat

531 2 1 loRetT x x x Chiller-Stat

532 1 1 csUtilPct1 x x x Chiller-Stat

533 1 1 csUtilPct2 x x x Chiller-Stat

534 1 1 csUtilPct3 x x x Chiller-Stat

535 1 1 valveUtilPct x x x Chiller-Stat

536 3 48

584 1 1 mode x x x Chiller-Stat

585 6 11 runtimes x x x Chiller-Xtra

596 3 80 errold x x x Chiller-Xtra

676 6 10 errage x x x Chiller-Xtra

Method

Num

Elements

Data Field 2 3 4 5 6 7 8 9 14 15 Message Type

Errors - see Appendix E.4

for more information

x x x Chiller-Stat

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]