A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-80 McQuay Micro Tech
Open Protocol
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version:
1.03
Document Revision:
2
McQuay Micro Tech Open Protocol Driver Manual
Page 3 of 35
1.
McQuay Micro Tech Open Protocol Description
This document describes the FieldServer driver used to transfer data between a FieldServer and
MicroTech® controllers. Transfers are done using the controller's Data Terminal Communications
Protocol. In this document the protocol is referred to as the McQuay Micro Tech Open Protocol.
The McQuay Micro Tech Open Protocol driver allows the FieldServer to transfer data to and from devices
over either RS-232 or RS-485 using McQuay Micro Tech Open Protocol. The FieldServer can emulate
either a Server or Client.
When emulating a Client, the driver enables the FieldServer to request ‘Everything’ from the McQuay
device as well as a number of advanced options which allow specific fields to be read or written and
device scaling to be applied.
When emulating a Server, the driver provides an emulation of the byte memory of a device and responds
to read and write requests.
The following important points and limitations should be noted before proceeding with this manual.
1. Arising from a feature of the McQuay Micro Tech Open Protocol is the peculiarity, that when a multi-
byte value is written to a McQuay device, the write is done one byte at a time (one byte of data can
be transferred per poll/response message pair) allowing for the possibility (at least for a short period)
that the multi byte value is only partially correct until all the messages have been completed.
2. The vendor equipment is limited to a maximum of 9600 baud. Given that each message packet can
only transfer one byte of data and that some data of interest is multi-byte, users of this protocol
should expect low data transfer rates.
3. Port expansion is not supported for this driver.
4. A document identified as Ed15050 MicroTech Network Operations contains important information
regarding the connection requirements of 3rd party equipment such as the FieldServer to a Microtech
network. The document also defines a number of limitations for such connections. The following
quotations from this document outline some of this information.
McQuay Micro Tech Open Protocol Driver Manual
Page 4 of 35
PC Connection
The PC connection to a MicroTech controller is through an available port A that is configured as TTY.
It is best to connect the PC to a level-1 controller because data transmission is the fastest. However,
a PC can be connected to any level-2 controller that does not have level-3 controllers connected to it
or to any MicroTech level-3 controller. Regardless of where you connect the PC, you have access to
the entire network.
You can connect two or more PCs to the network, but only one PC can be connected to a particular
controller. The PC that you use most often should be connected to the level-1 controller for best
performance. For example, you may have one PC that you use on site and another PC that you use
off site. In this situation, you may want to connect the on-site PC to the level-1 controller and the
modem for the off-site PC to a level-2 or level-3 controller.
If a PC is connected to a level-2 controller, a level-1 controller must poll that level-2 controller
connected to the PC so that the PC has access to the entire network. Defining a level-2 controller in
the level-1 controller Server list causes the level-1 controller to poll the level-2 controller.
Port Configuration: The communications port that the PC is connected to must be configured as a
TTY port. The default port configuration for most MicroTech controllers sets port A as TTY. The port
configuration is a software setting.
A separate software setting defines the communications rate of each port. In most controllers, the
default rate is 9600 bps.
TTY: A TTY port is used to connect a PC for monitoring purposes. It uses the RS-232C interface
standard and the Data Terminal Communications protocol.
5. The following quote from “MicroTech® Data Terminal Communication Packets, Open Protocol™ Data
Communications Information Packet ” highlights an important limitation of the protocol.
Data terminal communications may be sent via RS-232C or RS-485. Regardless of the electrical
standard used for communications, this protocol is a single ended type (i.e., communications to one
MicroTech controller maximum).
6. Each MicroTech controller is shipped from the factory with a unique job site password. The
passwords are provided by the McQuay International representative at the time of startup.
7. The driver does not validate passwords when configured as a Server. This means that requests to
read or write data will succeed even if the password supplied with the request is incorrect.
McQuay Micro Tech Open Protocol Driver Manual
Page 5 of 35
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
FS-8917-16
DESCRIPTION
RJ45 to terminal connector cable.
2.2.
Provided by Supplier of 3rd Party Equipment
PART #
DESCRIPTION
McQuay Motor Mount Connector for Port A connection
3.
Hardware Connections
The FieldServer is connected to the McQuay device as shown below.
Configure the McQuay device according to manufacturer’s instructions.
SERIES 200 CONTROLLER
RJ45-04
BLUE/WHITE
RJ45-08
ORANGE/WHITE
RJ45-01
BROWN
FS-8917-16
Connect to one of the RS-232
Ports on the FieldServer
8
1
FieldServer
P1
McQuay Micro Tech Open Protocol Driver Manual
Page 6 of 35
4.
Configuring the FieldServer as a McQuay Micro Tech Open Protocol 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 McQuay Micro Tech Open Protocol Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for McQuay Micro Tech Open Protocol 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.
4.1.
Data Arrays
Section Title
Data_Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Float, Bit, UInt16, SInt16,
Provide data format. Each Data Array can Packed_Bit, Byte,
Data_Format
only take on one format.
Packed_Byte,
Swapped_Byte
Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.
Data_Array_Length
1-10,000
Example
// Data Arrays
//
Data_Arrays
Data_Array_Name
DA_AI_01
DA_AO_01
DA_DI_01
,Data_Format
,UInt16
,UInt16
,Bit
,Data_Array_Length
,200
,200
,200
,200
DA_DO_01
,Bit
McQuay Micro Tech Open Protocol Driver Manual
Page 7 of 35
4.2.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Function
Specify which port the device is
connected to the FieldServer
Legal Values
P1-P8, R1-R21
Port
300, 1200, 2400, 4800 and 9600
baud (Vendor limitation).
Even (Vendor limitation)
7 (Vendor limitation)
1
MCQ, McQuay
None
0-32000 seconds, 1 second
Baud*
Specify baud rate
Parity*
Specify parity
Specify data bits
Specify stop bits
Specify protocol used
Specify hardware handshaking
Time between internal polls
Data_Bits*
Stop_Bits*
Protocol
Handshaking*
Poll Delay*
Example
// Client Side Connections
Connections
Port
P1
,Baud
,9600
,Parity
,Even
,Data_Bits
,7
,Protocol
,McQuay
,Handshaking ,Poll_Delay
,None ,0.100s
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.
McQuay Micro Tech Open Protocol Driver Manual
Page 8 of 35
Legal Values
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Function
Provide name for Node
Up to 32
alphanumeric
characters
Node_Name
Network address of the device being polled. If the
network address field is set to $00FF, the controller will
respond to the packet without regard to its own internal
network address
Node_ID
Route
0-255
This parameter must be used If units are connected to
the FieldServer via a routing device e.g. OPM. The
network address consists of the OPM address and the
unit address.
Protocol
Port
Specify protocol used
Specify which port the device is connected to the
FieldServer
MCQ, McQuay
P1-P8, R1-R22
200CFC,
100CFC,
050RPC,
001ASC,
000SCU,
The name of the McQuay Equipment type being polled.
Select one from the list on the left. The equipment type
must be known for the driver to operate correctly.
PLC_Type
Password
Type-Unknown
Ascii characters
only.
Maximum of 8 characters.
Example 1 of 2
// Client Side Nodes
// (No routing device used)
Nodes
Node_Name
Chiller
,Node_ID
,1
,Protocol
,McQuay
,Port
,P1
,Password
,Abcdefgh
,PLC_Type
,200CFC
Example 2 of 2
// Client Side Nodes
// (Routing device with address 3 used)
Nodes
Node_Name
Chiller1
,Node_ID
,66
,Route
,3
,Protocol
,McQuay
,Port
,P1
,Password
,Abcdefgh
,PLC_Type
,200CFC
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
McQuay Micro Tech Open Protocol Driver Manual
Page 9 of 35
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of this Map Descriptor
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_Name
0 to maximum specified in
“Data Array” section above
Data_Array_Offset
Function
Starting location in Data Array
Function of Client Map
Descriptor
Rdbc, Wrbc, Wrbx
4.4.2.
Driver Related Map Descriptor Parameters
Function
Column Title
Legal Values
One of the node
names specified in
“Client Node
Node_Name
Length
Name of Node to fetch data from
Descriptor” above
Length of Map Descriptor. Only one data field can be
read or written per poll/response sequence, thus driver
assumes a length of 1.
Set to 1 except
when reading a
direct address.
The name of the data field of interest. Each address
with meaningful data in the McQuay device has a
name. The field names are defined in a specification
for each device type. If the field name is unknown, the
Address can be defined. Refer to Appendix A.4 for
further information.
‘Everything’ or
select a field name
from Table 2
Field_Name
If set to No then the driver stores the raw values, if set
to Yes, the data is scaled before storing. The device
Device_Scaling
Yes, No
scaling applied is shown in Table 1. Note that
‘Device_Scaling’ has no meaning when writing to a
McQuay device.
4.4.3.
Timing Parameters
Column Title
Scan_Interval
Function
Rate at which data is polled
Legal Values
>0.1s
McQuay Micro Tech Open Protocol Driver Manual
Page 12 of 35
5.
Configuring the FieldServer as a McQuay Micro Tech Open Protocol Server
5.1.
Server Side Connection Descriptors
Section Title
Connections
Column Title
Function
Specify which port the device is
connected to the FieldServer
Legal Values
P1-P8, R1-R23
Port
300, 1200, 2400, 4800 and 9600
baud (Vendor limitation)
Baud*
Specify baud rate
Parity*
Specify parity
Even (Vendor limitation)
Data_Bits*
Specify data bits
7 (Vendor limitation)
Stop_Bits*
Protocol
Specify stop bits
1
Specify protocol used
Specify hardware handshaking
MCQ, McQuay
None
Handshaking*
Example
// Server Side Connections
Connections
Port
P1
,Baud
,9600
,Parity
,Even
,Data_Bits
,7
,Protocol
,McQuay
,Handshaking ,Poll_Delay
,None
,0.100s
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.
McQuay Micro Tech Open Protocol Driver Manual
Page 13 of 35
5.2.
Server Side Node Descriptors
Section
Title
Nodes
Column
Title
Function
Legal Values
Up to 32
Node_Name Provide name for node
Network address of the device being polled. If the network
alphanumeric
characters
Node_ID
address field is set to $00FF, the controller will respond to the
packet without regard to its own internal network address
This parameter must be used If units are connected to the
FieldServer via a routing device e.g. OPM. The network address
consists of the OPM address and the unit address.
0-255
Route
Protocol
Specify protocol used
MCQ, McQuay
P1-P8, R1-R24
Specify which port the device is connected to the FieldServer.
This parameter is optional for Server side nodes. The reason is
that when a poll is received on any port an attempt will be made
to match it against any Map Descriptor/node irrespective of the
port. If emulating more than one node with the same address,
however, the Nodes must be linked to specific ports.
Port*
200CFC,
100CFC,
050RPC,
001ASC,
000SCU,
This parameter has no meaning for a Server but it must be
specified to allow the driver to complete its configuration file
validation.
PLC_Type
Type-Unknown
This parameter is ignored for a Server. Although every poll
contains a password, this driver does no password validation
when configured as a Server.
Ascii characters
only.
Password*
Example
// Server Side Nodes
Nodes
Node_Name
FieldServer
,Node_ID
,11
,Protocol
,McQuay
,PLC_Type
,200CFC
4
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
McQuay Micro Tech Open Protocol Driver Manual
Page 14 of 35
5.3.
5.3.1.
Server Side Map Descriptors
FieldServer Specific Map Descriptor Parameters
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of this Map Descriptor
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_Name
0 to maximum specified in
“Data Array” section above
Data_Array_Offset
Function
Starting location in Data Array
Function of Client Map
Descriptor
Passive
5.3.2.
Driver Specific Map Descriptor Parameters
Column Title
Function
Legal Values
One of the node names
specified in “Client Node
Descriptor” above
Name of Node to fetch data
from
Node_Name
This commonly used Field Server parameter has no meaning for
this driver.
Data_Type
Length
Length of Map Descriptor
1-10000
Starting address of read block
Address
1 (Any positive integer)
Addresses cannot be specified
in hexadecimal format.
5.3.3.
Timing Parameters
Column Title
Function
Legal Values
Specifies time Server side
waits before responding to
Client that node is offline on
FieldServer Client side.
Scada_Hold_Timeout
>1.0s
McQuay Micro Tech Open Protocol Driver Manual
Appendix A. Advanced Topics
Page 17 of 35
Appendix A.1.
User Scaling:
Scaling
The user can specify scaling in the configuration file which allows a value to be scaled before being
stored in a Data Array or after being extracted from a data for writing to McQuay device. This scaling
is specified by using the following keywords in Map Descriptor definition.
Data_Array_Low_Scale,
Data_Array_High_Scale,
Device_Low_Scale,
Device_High_Scale…..
Device Scaling:
The raw values read from a McQuay device may be treated as raw values or they may be scaled.
Device scaling is the term used to describe the hard-coded scaling specified by McQuay for each
data field. By applying device scaling the user can avoid details or knowledge of the scaling and used
the converted value directly.
If this scaling is required then use the Device_Scaling parameter (see 4.4.2)
There are 5 device scaling methods. X refers to the raw value obtained from the McQuay device.
The method that will be applied to each field is shown in the following table.
Table 1 – Device Scaling Method applied to each Field
Method Id.
Device Scaling Method
X
X / 10
( X – 1000 ) / 10
X / 2
X - 100
( X – 100 ) / 10
( X / 5 ) + 20
( X / 5 ) + 55
( X / 5 )
1
2
3
4
5
6
7
8
9
10
( X / 5 ) - 100
Note that when device scaling is applied it is applied without consideration of the raw value. Where
the raw value has a special meaning (available in the McQuay packet documents for the equipment
type of interest); this driver does not apply any special consideration to these special values.
As a Client: - Device and User scaling may be applied.
As a Server. Device Scaling and User scaling is not applied. The raw value written to any data
location is stored as is and the raw value read from a Data Array used in formatting the response to
a read.
McQuay Micro Tech Open Protocol Driver Manual
Data Field Name Tables♣
Page 18 of 35
Appendix A.2.
If you do not know the field name it is possible to read the device by specifying the address only.
More information is provided in Appendix A.4
Table 2 – Equipment Type: 200CFC 200 Series Centrifugal Chiller
Read/
Write/ Field Name
Both
Device
Array
Location
Number Base
of Bytes Address
Scaling
Method5
1
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
Model
3
1
1
2
1
1
1
2
2
1
2
2
2
2
2
2
1
2
2
2
1
2
2
2
2
2
2
1
1
2
2
0x0A08
0x0A0B
0x0A0C
0x0A0D
0x0A0F
0x084B
0x040C
0x046A
0x044C
0x044A
0x085F
0x0851
0x043A
0x046E
0x046C
0x0484
0x083F
0x048A
0x0454
0x0456
0x0425
0x085A
0x085D
0x0440
0x0466
0x0480
0x0452
0x045F
0x083D
0x0488
0x0436
1
1
1
1
1
1
1
2
1
1
1
1
3
2
2
2
1
2
3
3
1
1
1
2
3
2
1
1
1
2
3
4
Refrigerant
5
Units of Measure
6
Software Version
8
Software Revision
11
12
13
15
17
18
20
22
24
26
28
30
31
33
35
37
38
40
42
44
46
48
50
51
52
54
Chiller Unit Temperature Type
Communication Status
Compressor Lift Pressure
Compressor Motor Current
Compressor Motor Current Percent
Compressor Number of Starts
Compressor Operating Hours
Compressor Suction Temperature
Compressor Superheat - Discharge
Compressor Superheat -Suction
Condenser Approach Temperature
Condenser Heat Recovery Unit Present
Condenser Heat Recovery Temperature - Delta
Condenser Heat Recovery Water Temp. - Entering
Condenser Heat Recovery Water Temp. - Leaving
Condenser Pump Status
Condenser Pump # 1 Operating Hours
Condenser Pump # 2 Operating Hours
Condenser Refrigerant Pressure
Condenser Refrigerant Temperature
Condenser Subcooling Temperature
Condenser Water Flow Rate
Condenser Water Flow Status
Condenser Water Rate Sensor
Condenser Water Temperature - Delta
Condenser Water Temperature - Entering
♣ Additional information may be obtained from McQuay International. Request the following document.
MicroTech® Series 200 Centrifugal Chiller Data Communications Packet for Open Protocol™
Cent2_22.doc
5 See Appendix A.1.
McQuay Micro Tech Open Protocol Driver Manual
Page 19 of 35
Read/
Array
Device
Number Base
of Bytes Address
Write/ Field Name
Location
Scaling
Both
Method5
56
58
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
b
b
b
b
Condenser Water Temperature - Leaving
Cooling Tower Control
2
1
1
1
2
2
1
2
2
2
2
2
1
1
2
2
2
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
1
1
1
1
1
1
1
1
0x0434
0x0926
0x049A
0x049B
0x043E
0x0482
0x0423
0x0854
0x0857
0x0438
0x0464
0x0450
0x045E
0x083C
0x0486
0x0432
0x0430
0x1C00
0x0861
0x0862
0x0863
0x0864
0x0865
0x0866
0x0867
0x0868
0x0869
0x086A
0x043C
0x0446
0x0468
0x04AC
0x0442
0x0444
0x0474
0x083E
0x044B
0x0420
0x0475
0x041E
0x0477
0x0476
3
1
1
1
3
2
1
1
1
2
3
1
1
1
2
3
3
1
1
1
1
1
1
1
1
1
1
1
3
2
2
2
3
3
2
1
1
1
1
1
1
4
59
Cooling Tower Stage
60
Cooling Tower Valve Position
Discharge Refrigerant Temperature
Evaporator Approach Temperature
Evaporator Pump Status
Evaporator Pump #1 Operating Hours
Evaporator Pump #2Operating Hours
Evaporator Refrigerant Pressure
Evaporator Refrigerant Temperature
Evaporator Water Flow Rate
Evaporator Water Flow Status
Evaporator Water Rate Sensor
Evaporator Water Temperature - Delta
Evaporator Water Temperature - Entering
Evaporator Water Temperature - Leaving
Fault - Current Active
61
63
65
66
68
70
72
74
76
77
78
80
82
84
85
Last Start Hour
86
Last Start Minute
87
Last Start Month
88
Last Start Date
89
Last Start Year
90
Last Stop Hour
91
Last Stop Minute
92
Last Stop Month
93
Last Stop Date
94
Last Stop Year
95
Liquid Line Refrigerant Temperature
Oil Pressure - Feed
97
99
Oil Pressure - Net
101
103
105
107
108
109
110
111
112
113
114
Oil Pressure - Vent
Oil Temperature - Feed
Oil Temperature - Sump
Outdoor Air Temperature - Network
Refrigerant Detection Sensor
Refrigerant Leak Detection Limit
Unit Status
Capacity Limit Percent
Clear Current Fault
Chiller Operation Mode
Chilled Water Temperature Setpoint
McQuay Micro Tech Open Protocol Driver Manual
Page 20 of 35
Read/
Array
Device
Number Base
of Bytes Address
Write/ Field Name
Location
Scaling
Both
Method5
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
b
b
b
b
b
b
b
b
b
r
Communications Signal
Outdoor Air Temperature - BAS
Master/Server Setpoint
Lead/Lag Mode Setpoint
Enable Lag Setpoint
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0x047D
0x0473
0x093C
0x093D
0x093E
0x093F
0x0942
0x0948
0x0949
0x0401
0x0402
0x0403
0x0404
0x0405
0x0406
0x0407
0x0408
0x900
1
5
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
4
4
Disable Lag Setpoint
Lag Standby Setpoint
Lead/Lag Switch Setpoint (Day)
Lead/Lag Switch Setpoint (Hour)
Lead/Lag Status
r
Lead Unit
r
Lead Unit Status
r
Lag Unit Status
r
Lead Motor Current
r
Lag Motor Current
r
Lead Status
r
Lag Status
b
b
r
Chiller Control mode
Chilled Water Temperature Local Setpoint
Chilled Water Temperature – Active Setpoint
0x901
0x905
Table 3 - Equipment Type: 050RPC Reciprocating Chiller
Read/
Device
Array
Number Base
of BytesAddress
Write/Field Name
Location
Scaling
Both
Method6
3
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
Circuit #1 Condenser Approach Temperature
Circuit #1 Condenser Pressure
2
2
2
2
2
2
1
2
2
1
1
2
2
2
2
0x0497
0x0467
0x0822
0x0820
0x0826
0x0824
0x0831
0x0463
0x0479
0x0833
0x0428
0x049B
0x0475
0x0493
0x0499
2
2
2
2
6
6
1
2
6
1
1
2
6
2
2
5
7
Circuit #1 Alarm Conditions: Condenser Pressure
Circuit #1 Alarm Conditions: Evaporator Pressure
Circuit #1 Alarm Conditions: Liquid Line Temp
Circuit #1 Alarm Conditions: Suction Temperature
Circuit #1 Current Alarm
9
11
13
14
16
18
19
20
22
24
26
28
Circuit #1 Evaporator Pressure
Circuit #1 Liquid Line Temperature
Circuit #1 Previous Alarm
Circuit #1 Status
Circuit #1 Subcooling Temperature
Circuit #1 Suction Temperature
Circuit #1 Superheat Temperature
Circuit #2 Condenser Approach Temperature
6 See Appendix A.1
.
McQuay Micro Tech Open Protocol Driver Manual
Page 21 of 35
Read/
Array
Device
Number Base
of BytesAddress
Write/Field Name
Location
Scaling
Both
Method6
30
32
34
36
38
39
41
43
44
45
47
49
51
53
55
57
59
61
63
65
67
69
71
73
75
76
78
79
80
81
82
83
84
85
86
87
88
89
90
91
r
r
Circuit #2 Condenser Pressure
Circuit #2 Alarm Conditions: Condenser Pressure
Circuit #2 Alarm Conditions: Evaporator Pressure
Circuit #2 Alarm Conditions: Liquid Line Tempe
Circuit #2 Alarm Conditions: Suction Temperature
Circuit #2 Current Alarm
2
2
2
2
2
1
2
2
1
1
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
0x0469
0x082A
0x0828
0x082E
0x082C
0x0832
0x0465
0x047B
0x0834
0x0429
0x049D
0x0477
0x0495
0x0862
0x086A
0x0864
0x086C
0x0866
0x086E
0x0868
0x0870
0x0470
0x0472
0x046E
0x0461
0x08B4
0x047D
0x042B
0x0474
0x0427
0x091A
0x091B
0x097D
0x090D
0x0905
0x090C
0x044F
0x044D
0x044E
0x090B
2
2
2
6
6
1
2
6
1
1
2
6
2
1
1
1
1
1
1
1
1
6
6
6
6
1
6
1
1
1
1
1
1
4
4
4
1
1
1
1
r
r
r
r
r
Circuit #2 Evaporator Pressure
Circuit #2 Liquid Line Temperature
Circuit #2 Previous Alarm
r
r
r
Circuit #2 Status
r
Circuit #2 Subcooling Temperature
Circuit #2 Suction Temperature
Circuit #2 Superheat Temperature
Compressor #1 Operating Hours
Compressor #1 Starts
r
r
r
r
r
Compressor #2 Operating Hours
Compressor #2 Starts
r
r
Compressor #3 Operating Hours
Compressor #3 Starts
r
r
Compressor #4 Operating Hours
Compressor #4 Starts
r
r
Condenser Entering Water Temperature
Condenser Leaving Water Temperature
Evaporator Entering Water Temperature
Evaporator Leaving Water Temperature
Heat/Cool Switch
r
r
r
r
r
OaT
r
Stage of Capacity
r
Unit % RLA
r
Unit Status
b
b
b
b
b
b
b
b
b
b
Clear Circuit #1 Alarm
Clear Circuit #2 Alarm
Condenser Leaving Water Temperature Setpoint
Evaporator Entering Water Temperature Setpoint
Evaporator Leaving Water Temperature Setpoint
Maximum Water Reset Setpoint
Network Command
Network Demand Limit
Network Leaving Water Temperature Reset
Reset Option Setpoint
McQuay Micro Tech Open Protocol Driver Manual
Page 22 of 35
Table
Array
4
- Equipment Type: 100CFC 100 Series Centrifugal Chiller
Read/
Write/Field Name
Both
Device
Number Base
of BytesAddress
Scaling
Location
Method7
1
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
Alarm Contact
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0x0217
0x0418
0x0420
0x0423
0x0407
0x0403
0x041C
0X021C
0x0411
0x0408
0X050F
0x0218
0x0219
0x0428
0x0834
0x0835
0x0836
0x0837
0x0838
0x0839
0x083A
0x083B
0x0405
0x041E
0x0401
0x041A
0x0438
0x050E
0X021B
0x0410
0x0402
0x041B
0X050F
0X050E
0x0212
0x0406
0x041F
0x0400
1
1
7
1
1
1
7
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
8
1
1
1
1
1
1
1
7
1
1
1
1
8
1
2
Approach Condenser
3
Calculated Leaving Evaporator Temp Setpoint
Calculated Network Amp Limit Setpoint
Compressor Discharge Temp.
Compressor Suction Temp. - Lo Resolution
Compressor Suction Temp. - Hi Resolution
Condenser Pump
4
5
6
7
8
9
Condenser Refrigerant Pressure
Condenser Refrigerant Temp.
Condenser Water Flow Switch
Cooling Tower Stage 1
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Cooling Tower Stage 2
Current Fault
Fault Last
Fault 2
Fault 3
Fault 4
Fault 5
Fault 6
Fault 7
Fault 8
Entering Condenser Water Temp. - Lo Resolution
Entering Condenser Water Temp. - Hi Resolution
Entering Evaporator Water Temp. - Lo Resolution
Entering Evaporator Water Temp. - Hi Resolution
Entering Water Reset
Evaporator Low Pressure Switch
Evaporator Pump
Evaporator Refrigerant Pressure
Evaporator Refrigerant Temp. - Lo Resolution
Evaporator Refrigerant Temp. - Hi Resolution
Evaporator Water Flow Switch
High Discharge Pressure Switch
Hot Gas Solenoid
Leaving Condenser Water Temp. - Lo Resolution
Leaving Condenser Water Temp. - Hi Resolution
Leaving Evaporator Water Temp. - Lo Resolution
7 See Appendix A.1
.
McQuay Micro Tech Open Protocol Driver Manual
Page 23 of 35
Read/
Array
Device
Number Base
of BytesAddress
Write/Field Name
Location
Scaling
Both
Method7
39
40
41
42
43
44
45
46
47
48
49
50
51
52
54
55
56
58
59
60
61
62
63
64
65
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
b
b
b
Leaving Evaporator Water Temp. - Hi Resolution
LED Front Panel
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
1
2
1
1
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0x0419
0x021F
0x0412
0x0216
0x0404
0x041D
0x0417
0x0211
0x043B
0X043D
0x0901
0X043C
0x0213
0x021E
0x0435
0x040C
0x050E
0X0432
0X040D
0x0409
0x0415
0x0215
0X050E
0X021D
0X040A
0x0430
0X050E
0X043E
0x0439
0X040B
0X050F
0X043A
0X050F
0X050F
0x0416
0X050E
0x0424
0x0210
0X050F
0x0214
0X042A
0x0801
0x0800
7
1
1
1
1
8
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Lift Pressure
Liquid Injection Solenoid
Liquid Line Refrigerant Temp. - Lo Resolution
Liquid Line Refrigerant Temp. - Hi Resolution
Liquid Subcool
Load Solenoid
Low Evaporator Pressure Limit
Manual Amp Limit
Manual Amp Limit Setpoint
Maximum Amp Limit
Motor Control Latch Relay
Motor Control Relay
Motor Current Amps
Motor Current Percent
Motor Temperature Switch
Number of Starts
Oil Delta Pressure
Oil Feed Temp.
Oil Gage Pressure
Oil Heater
Oil Pressure Differential Switch
Oil Pump
Oil Sump Temp.
Operating Hours
Panel Rocker Switch
Remote Amp Limit
Remote Chilled Water Reset
Remote Reset or Amp Limit Signal
Remote Start/Stop Switch
Soft Load Limit
Starter Fault Switch
Starter Transition Switch
Superheat
Surge Guard Switch
Unit Status
Unload Solenoid
Vanes Closed Switch
Watchdog Output
Clear Current Fault
Comm Port Baud Rate
Correct Checksum
McQuay Micro Tech Open Protocol Driver Manual
Page 24 of 35
Read/
Array
Device
Number Base
of BytesAddress
Write/Field Name
Location
Scaling
Both
Method7
85
86
87
88
89
90
91
92
93
94
b
b
b
b
b
b
b
b
b
b
Leaving Evaporator Temperature Setpoint
Maximum Chilled Water Reset Setpoint
Network Amp Reset
1
1
1
1
1
1
1
1
1
1
0x0900
0x0820
0x0450
0X044F
0x0451
0x0822
0x0204
0x0824
0x0826
0x0827
7
9
1
1
1
1
1
1
9
9
Network Chilled Water Reset
Network Start Stop
Reset Option
Soft Reset
Start Mode
Startup Differential Temp.
Shutdown Differential Temp.
Table 5 - Equipment Type : 001ASC Reciprocating Chiller
Read/
Device
Array
Number Base
of Bytes Address
Write/Field Name
Location
Scaling
Both
Method8
1
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
Active Chilled Water Temperature Setpoint
Ckt#1 Condenser Pressure
1
2
1
2
2
2
1
2
2
2
1
1
2
2
1
2
2
2
2
2
2
2
2
1
1
0x045A
0x0467
0x1F13
0x1F09
0x1F0F
0x1F07
0x1F14
0x1F0D
0x1F11
0x1F0B
0x08B9
0x1F02
0x0463
0x0479
0x0428
0x04DF
0x0475
0x04D7
0x0862
0x086A
0x046E
0x0461
0x047D
0x042B
0x0427
4
2
2
4
Ckt#1 Alarm Conditions: Capacity
Ckt#1 Alarm Conditions: Condenser Pressure
Ckt#1 Alarm Conditions: Evap Leaving Water Temp
Ckt#1 Alarm Conditions: Evap Pressure
Ckt#1 Alarm Conditions: Fan Stage
Ckt#1 Alarm Conditions: Liquid Line Temperature
Ckt#1 Alarm Conditions: Outside Air Temp
Ckt#1 Alarm Conditions: Suction Temperature
Ckt#1 Current Alarm
1
5
2
7
1
9
2
11
12
14
16
18
19
20
22
24
25
27
29
31
33
35
37
39
41
42
1
10
10
10
1
Ckt#1 Current Alarm HourMinuteMonthDateYear
Ckt#1 Evaporator Pressure
1
2
Ckt#1 Liquid Line Temperature
Ckt#1 Status
10
1
Ckt#1 Subcooling Temperature
Ckt#1 Suction Temperature
2
10
2
Ckt#1 Superheat Temperature
Compressor #1 Operating Hours
Compressor #1 Starts
1
1
Evaporator Entering Water Temperature
Evaporator Leaving Water Temperature
Outdoor Air Temperature
10
10
10
1
Stage of Cooling
Unit Status
1
8 See Appendix A.1
.
McQuay Micro Tech Open Protocol Driver Manual
Page 25 of 35
Read/
Array
Device
Number Base
of Bytes Address
Write/Field Name
Location
Scaling
Both
Method8
43
44
45
46
47
48
49
50
b
b
b
b
b
b
b
b
Clear Ckt#1 Alarm
1
1
1
1
1
1
1
1
0x091A
0x090D
0x0905
0x090C
0x044F
0x044D
0x044E
0x090B
1
2
2
2
1
1
1
1
Evaporator Entering Water Temperature Setpoint
Evaporator Leaving Water Temperature Setpoint
Maximum Chilled Water Reset Setpoint
Network Command
Network Demand Limit
Network Evaporator Leaving Water Temp Reset
Reset Option Setpoint
Table 6 - Equipment Type : Self-Contained Units (SCUs)
Read/
Device
Array
Number Base
of Bytes Address
Write/Field Name
Location
Scaling
Both
Method9
1
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
r
Air Velocity
1
1
1
1
1
1
2
1
2
1
2
1
2
1
2
1
2
1
1
1
1
1
1
1
2
1
1
0x0434
0x045C
0x0801
0x1301
0x0435
0x081C
0x08AF
0x081D
0x08B2
0x081E
0x08B5
0x081F
0x08B8
0x0820
0x08BB
0x0821
0x08BE
0x0432
0x043F
0x044A
0x042F
0x0435
0x0434
0x045A
0x08C4
0x042E
0x042C
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
Airflow Status
3
Current Alarm
4
Previous Alarm
5
Building Static Pressure
Compressor #1 Alarm
Compressor #1 Operating Hours
Compressor #2 Alarm
Compressor #2 Operating Hours
Compressor #3 Alarm
Compressor #3 Operating Hours
Compressor #4 Alarm
Compressor #4 Operating Hours
Compressor #5 Alarm
Compressor #5 Operating Hours
Compressor #6 Alarm
Compressor #6 Operating Hours
Control Temperature
6
7
9
10
12
13
15
16
18
19
21
22
24
25
26
27
28
29
30
31
33
34
Cool Stage
Cooling Control Status
Dew Point Temperature
Duct Static Pressure #1
Duct Static Pressure #2
Economizer Enable
Economizer Operating Hours
Economizer Position
Entering Water Temperature
9 See Appendix A.1
.
McQuay Micro Tech Open Protocol Driver Manual
Page 26 of 35
Read/
Array
Device
Number Base
of Bytes Address
Write/Field Name
Location
Scaling
Both
Method9
35
37
39
40
41
42
43
45
46
47
48
49
50
51
52
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
r
r
Fan - High Speed Operating Hours
Fan - Low Speed Operating Hours
Fan Operation
2
2
1
1
1
1
2
1
1
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0x08AC
0x08A9
0x0462
0x0436
0x043E
0x044C
0x08C1
0x042D
0x042B
0x0436
0x04BB
0x0470
0x045F
0x0429
0x08C7
0x0431
0x0431
0x0428
0x042A
0x0427
0x045E
0x0488
0x043D
0x0436
0x0445
0x045B
0x0461
0x0923
0x04CE
0x048A
0x044F
0x0926
0x088D
0x0907
0x0878
0x090E
0x094E
0x0949
0x094D
0x0917
0x089B
0x0932
0x0931
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
r
r
Fan Speed
r
Heat Stage
r
Heating Control Status
Heating Operating Hours
Leaving Water Temperature
Mixed Air Temperature
Motor Amps
r
r
r
r
r
Motor Speed
r
Network Communications Status
Outdoor Air Damper Status
Outdoor Air Temperature
Override Hours
r
r
r
r
Refrigerant Pressure
r
Relative Humidity
r
Return Air Temperature
Space Temperature
r
r
Supply Air Temperature
Supply Fan Status
r
r
Unit Enabled Status
r
Unit Status
r
Variable Inlet Vane Position
Water Flow Required
r
r
Water Flow
r
Water Pump Start/Stop
Building Static Pressure Setpoint
Clear Alarm
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
Clear Alarm Buffer
Control Mode
Control Temperature Source
Cooling Control Deadband
Cooling Control Setpoint
Cooling Supply Deadband
Cooling Supply Setpoint
Dew Point Deadband
Dew Point Sensor Type
Dew Point Setpoint
Duct Static Pressure Setpoint
Duct Static/Building Static Pressure Deadband
Economizer (Air) Changeover Differential
Economizer (Air) Changeover Temperature Setpoint
McQuay Micro Tech Open Protocol Driver Manual
Page 27 of 35
Read/
Array
Device
Number Base
of Bytes Address
Write/Field Name
Location
Scaling
Both
Method9
82
83
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
b
Economizer (Air) Method
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0x083B
0x091A
0x0939
0x08E1
0x093A
0x0894
0x0905
0x0871
0x0914
0x0947
0x094C
0x094B
0x092C
0x092B
0x0951
0x0934
0x0919
0x0904
0x0903
0x0902
0x0901
0x0444
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Economizer (Water) Changeover Temperature Offset
Fan On Heating Setpoint
84
85
Head Pressure Deadband
86
Head Pressure Setpoint
87
Heating Control Deadband
88
Heating Control Setpoint
89
Heating Supply Deadband
90
Heating Supply Setpoint
91
Humidity Control Type
92
Humidity Deadband
93
Humidity Setpoint
94
Low Entering H20 Comp. Lockout Differential
Low Entering Water Compressor Lockout Setpoint
Min Vane Position/Fan Speed
Minimum Outdoor Air Damper Position
Minimum Supply Air Temperature Control
Unoccupied Cooling Space Differential
Unoccupied Cooling Space Setpoint
Unoccupied Heating Space Differential
Unoccupied Heating Space Setpoint
Water Flow Signal
95
96
97
98
99
100
101
102
103
Appendix A.3.
McQuay Equipment Types recognized by the driver.
Code
Description
200CFC
100CFC
001ASC
000SCU
0050RPC
200 Series Centrifugal Chiller
100 Series Centrifugal Chiller
Air Screw Chiller
Self Contained Unit
Reciprocating Chiller
Appendix A.4.
Direct Addressing
Direct addressing allows data to be read from the McQuay device when the field name is unknown.
McQuay specifies the addresses in hexadecimal notation but they must be specified in the CSV file in
decimal format. For example, to read McQuay address 0x0400, the address in the CSV file must be
entered as 1024.
If reading multiple addressing at once (i.e. if the length is greater than 1) it may be necessary to
adjust the timeout for the Map Descriptor.
It is possible to read multiple addresses using one Map Descriptor; however, it is only possible to
write to a single address.
The following Map Descriptor parameters will need to be defined in addition to those described in
section 4.4.
McQuay Micro Tech Open Protocol Driver Manual
Page 28 of 35
5.3.6.
Driver Related Map Descriptor Parameters
Normally this
field is set to
1 or omitted.
The address in the McQuay device that contains the data of
interest.
Address*
This parameter is used with direct addressing. When
reading, up to 4 consecutive address locations in the
McQuay device can be combined and stored in a single
Data Array element. When writing, one value from the
Data Array may be sent to up to 4 consecutive address
locations in the McQuay device.
Bytes_Per_Field*
1,2,3,4
Refer to examples on the following pages.
McQuay Micro Tech Open Protocol Driver Manual
Page 31 of 35
Appendix A.8.
Statistics
The driver reports statistics according to the FieldServer standards. The following notes describe
some aspects of standard statistic reporting which are peculiar to this driver.
NAK
CHECKSUM
NOISE
NO START
PROTOCOL
Each time a negative acknowledgement message is received.
Each time that a message is received that contains a non-ASCII character.
An acknowledgement message contains an unrecognized code.
Each time a message is received that doesn’t begin with a space.
All other errors are reported as protocol errors
In addition to the standard FieldServer communication statistics described above and in the
FieldServer User’s Manual, this driver can also expose some driver statistics by writing data to a Data
Array. A special Map Descriptor is required. The driver recognizes the Map Descriptor by its name
which must be "McQuay-stats”.
The driver stores the following data. The location in the Data Array is obtained by multiplying the
port number by 50 and then using the location offset indicated in the table below.
Location
0
Statistic
MCQ_STAT_PASSWORD
10
MCQ_STAT_NAK
11
MCQ_STAT_NOISE
12
MCQ_STAT_NOISE_CODE
13
MCQ_STAT_NON_ASCII_CHARS
MCQ_STAT_BAD_START_BYTE
MCQ_STAT_OTHER_CMPLT_ERR
MCQ_STAT_CLIENT_BYTES_RCVD
MCQ_STAT_CLIENT_FRAGS_RCVD
MCQ_STAT_CLIENT_MSGSS_RCVD
MCQ_STAT_CLIENT_BYTES_SENT
MCQ_STAT_CLIENT_FRAGS_SENT
MCQ_STAT_CLIENT_MSGSS_SENT
MCQ_STAT_SERVER_BYTES_SENT
MCQ_STAT_SERVER_MSGSS_SENT
MCQ_STAT_SERVER_NAKS_SENT
14
15
16
17
18
19
20
21
22
23
24
The following example shows how this special Map Descriptor can be configured. You can copy this
section of text directly into your CSV file.
McQuay Micro Tech Open Protocol Driver Manual
Page 33 of 35
Appendix B. Error Messages
Those messages marked with an * are only printed once even if they occur repeatedly.
Error Message
Action
The length of the Map Descriptor used to expose driver statistics is
too short. Set the length to at least 1000. You can ignore this
message – the driver will abandon excess statistics.
McQuay:#1 FYI. The MapDesc
called <%s> is too short
McQuay:#2 FYI. You could
have used a MapDesc called
<%s> to expose diagnostic info.
You can safely ignore this message. It is a prompt. Refer to
Appendix A.8.
This is a reminder that a password is expected when a node is
defined. Refer to sections 4.3 or 5.2. Even though password
checking is not enforced when the driver is configured as a Server,
the driver expects one to be defined for every node.
McQuay:#3 FYI. Normally
passwords are defined for each
node.
McQuay:#4 Err. Node list if full. A maximum of 100 McQuay device nodes can be configured per
Max=%d
FieldServer. If the limit is reached, call support.
A node has been provided with two passwords. This is either a
configuration error or two nodes with the same address are
connected to different ports. The driver can only store one password
per node address and cannot use the port number to differentiate
them. Re-program the McQuay devices to have the same passwords
if they have the same addresses.
McQuay:#5 Err. Node=%d has
more than one password.
Device Scaling is being applied and the driver doesn’t know how to
scale a variable. Please submit your configuration file with your
request for support.
*McQuay:#9 FYI. Device
scaling method unknown.
The driver doesn’t recognize the equipment type specified using the
PLC_Type parameter in the configuration file. Refer to Appendix A.3
for a list of valid equipment types.10
McQuay:#10 Err. Node=%s.
Equip. type not recognized.
McQuay:#11 Err. Node=%s.
Equip. Type not specified.
McQuay:#13 Err.
MapDesc=%s. Field Name
unknown.
Refer to Sections 4.3, 5.2. and Appendix A.310
Refer to Appendix A.2 for a list of valid field names. Refer also to
Sections 4.4 or 5.3.
McQuay:#14 Err.
Corrective action is required. When writing to a McQuay device using
direct addressing the length may only be 110
MapDesc=%s. Max Len=1 for
Writes with direct addr.
McQuay:#15 Err.
MapDesc=%s. Field
Name/Address Required.
Neither a field name nor an address was specified. The driver does
not know what location to read. Specify a field name from Appendix
A.2.10
Each Map Descriptor must be connected to a node. This is done by
McQuay:#16 Err.
MapDesc=%s. No Node.
specifying a node name. 10
The offset added to the length of the Map Descriptor extends beyond
the Data Array. Increase the Data Array length. 10
McQuay:#17 Err.
MapDesc=%s. Md too short.
McQuay:#18 Err.
MapDesc=%s. Cannot write
'Everything'.
When using ‘everything’ as a field name the Map Descriptor function
must be Rdbc or Rdb as this is a read only function.10
McQuay:#19 do diagnostic 3
McQuay:#20 do diagnostic 1
McQuay:#21 do diagnostic 2
Call FieldServer Technical Support. A developer diagnostic has been
called and should not have been.
10
Correct the configuration by editing the CSV file and downloading it to the FieldServer, then reset the
FieldServer for the changes to take effect.
McQuay Micro Tech Open Protocol Driver Manual
Page 34 of 35
Error Message
Action
McQuay:#22 Err. Illegal
Node_ID [%d] - Set to 1
Check configuration file, a Node_ID is out of range. 11
If the Node_ID is greater than 255 then this message is printed. In
versions of the driver prior to 1.02 this was permitted and these
configurations will operate correctly. In versions since 1.02a the route
parameter is used to provide the routing device’s address. Convert
the Node_ID as follows. Divide the old Node_ID by 256. Set the
Node_ID equal to remainder and set the route equal to the quotient.
Example; Old Node_ID = 834. 834 div 256 = 3 remainder 66.
Therefore Route=3 and Node_ID=66.
McQuay:#23 FYI. Config
requires non-critical update.
Read Manual.
If the Node_ID is > 255 and the Route is specified too then this error
is printed. The Node_ID should be a number in the range 0 to
255.Error! Bookmark not defined.
McQuay:#24 Err. Illegal
Node_ID/Route
McQuay:#25 Err. Max Len=1
when Bytes_Per_Field > 1.
MD=%s.
The length parameter must be set to 1 when a Map Descriptor has
the Bytes_Per_Field parameter specified10
Legal values for the Bytes_Per_Field parameter are whole numbers
in the range 1 to 4 inclusive. 10
McQuay:#26 Err. Max
Bytes_Per_Field=4. MD=%s.
This message is printed if a NAK response is received in the first few
polls to a node. The driver guesses that the reason is that the
McQuay:#27* Err.
Response=NAK. Read Manual. Node_ID/route or password has been incorrectly specified in the
Maybe password or Node_ID
configuration file. Verify these settings. The message is printed once
and suppressed for subsequent occurrences. Refer to Appendix C.2
The message is printed and then suppressed for subsequent
occurrences, but the NAK stat is incremented for each occurrence.
The driver is reporting that the McQuay device responded with a NAK
under different circumstances from msg#27 which is printed if the
NAK is received during the first few polls. The message indicates that
the McQuay device could not respond. If the NAK's are occasional,
assume that noise has corrupted an occasional message. If they
occur frequently assume a systematic or connection error. Refer to
Error! Reference source not found. and Appendix C.2.
McQuay:#28* Err. Device
responded with a NAK.
11
Correct the configuration by editing the CSV file and downloading it to the FieldServer, then reset the
FieldServer for the changes to take effect.
McQuay Micro Tech Open Protocol Driver Manual
Appendix C. Troubleshooting
Page 35 of 35
Appendix C.1.
Connection Problems
The driver produces a timeout each time a message is sent. If the number of timeouts is the same as
the number of messages sent then you know that the McQuay device has never sent a response.
The following reasons may be applicable:
•
•
•
Incorrect connection settings - the messages sent by the FieldServer cannot be interpreted by the
McQuay device.
Incorrect connection wiring – the McQuay device may require a jumper on its serial port to deflect
hardware handshaking. Refer to the vendor manual.
Serial port failure – If the Tx LED is not flashing each time a message is sent, the port is not
working
•
•
The McQuay device is off.
If the Node_ID and Route are incorrect, the McQuay device will not respond at all.
Appendix C.2.
Negative Acknowledgement - NAK
The Server sends a NAK message and increments the NAK stat each time a poll is unsuccessful. An
occasional NAK may indicate a corrupted message. If the number of NAK's is the same as the
number of transmitted messages to a Node, however, one of the following problems could apply:
•
Bad Password - the password specified in the "read" command did not match any of the access
level passwords stored in the MicroTech controller to which the terminal is connected. Call FST
Tech support for default passwords or call your Vendor. FST recommends checking the
password first as in almost all reports the problem was resolved by changing the password.
Device has been polled with an invalid command code.
Bad Node_ID / Route parameters for the node.
The MCQ device received the message and thought it was badly formatted. This is unlikely on a
repeated basis unless the connection settings were slightly wrong.
•
•
•
•
•
The packet structure was invalid
The packet was received with a parity or framing error
Appendix C.3.
Node ID problems
If the Node is incorrectly specified, the FieldServer will not get a response from the McQuay unit. The
ID used to communicate with the McQuay unit needs to be determined. This may not be the same as
shown on the Rotary switches of the unit. Note that McQuay uses Hexadecimal notation for
addressing, therefore, if connection to the Unit is with address 0201, this is in Hex and the Node ID
for the FieldServer configuration needs to be 513.
Appendix C.4.
Server Side Configuration – Consecutive Addresses
Some variables have their values stored in two consecutive address locations. When the Client polls
for the value it actually sends two read messages – one for each address. When configuring the
Server side, therefore, it is necessary to define two Map Descriptors for variables which require two
consecutive addresses.
Map_Descriptors
Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length
Supply Fan Status
Supply Temp
Space Temp
,DA_AI_01
,DA_AI_01
,DA_AI_01
,DA_AI_01
,01
,02
,03
,04
,Passive
,Passive
,Passive
,Passive
,Node_A
,Node_A
,Node_A
,Node_A
,1118
,1063
,1066
,1074
,1
,1
,1
,1
Control Temp Part 1
|