FieldServer FS-8700-80 User Manual

Driver Version:

1.05

Document Revision:

6

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after November 2011

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-80 McQuay MicroTech® Open Protocol™

A Sierra Monitor Company

McQuay Micro Tech Open Protocol Driver Manual Table of Contents

TABLE OF CONTENTS

1 McQuay Micro Tech Open Protocol Description ............................................................................................. 4

1.1 MicroTech Unit and System Controllers ........................................................................................................ 4

1.1.1 McQuay Equipment Types recognized by the driver. ............................................................................. 4

1.1.2 McQuay equipment not currently recongnized by the driver: ............................................................... 4

1.1.3 McQuay MicroTech network products used in conjunction with the driver: ......................................... 5

1.1.4 About MicroTech Network Architecture ................................................................................................ 6

1.2 Applying a FieldServer gateway to different MicroTech situations ............................................................... 6

1.2.1 Single standalone MicroTech 200 Series unit controller ........................................................................ 6

1.2.2 Multiple standalone MicroTech 200 Series unit controllers ................................................................... 7

1.2.3 Multiple standalone MicroTech “non-200 Series” unit controllers ........................................................ 7

1.2.4 Existing MicroTech network (Custom MicroTech Monitor software, NMP Panel, etc) .......................... 7

1.2.5 Existing MicroTech Open Protocol network ........................................................................................... 9

1.2.6 Replacing a BACdrop Gateway panel .................................................................................................... 9

1.3 MicroTech Communication Port Configuration ........................................................................................... 11

1.4 Reference Documents ................................................................................................................................. 12

2 Driver Features ............................................................................................................................................ 13

3 Driver Scope of Supply ................................................................................................................................. 13

3.1 Supplied by FieldServer Technologies for this driver ................................................................................... 13

3.2 Provided by Supplier of 3rd Party Equipment............................................................................................... 13

4 Hardware Connections ................................................................................................................................. 14

5 Data Array Parameters ................................................................................................................................. 15

6 Configuring the FieldServer as a McQuay Micro Tech Open Protocol Client ................................................. 16

6.1 Client Side Connection Parameters ............................................................................................................. 16

6.2 Client Side Node Parameters ....................................................................................................................... 17

6.3 Client Side Map Descriptors......................................................................................................................... 18

6.3.1 FieldServer Related Map Descriptor Parameters ................................................................................. 18

6.3.2 Driver Related Map Descriptor Parameters ......................................................................................... 18

6.3.3 Timing Parameters ............................................................................................................................... 18

6.3.4 Map Descriptor Example 1 – Read Everything. .................................................................................... 19

6.3.5 Map Descriptor Example 2 – Read a particular Data Field. ................................................................. 19

6.3.6 Map Descriptor Example 3 – Write. ..................................................................................................... 20

7 Configuring the FieldServer as a McQuay Micro Tech Open Protocol Server ................................................ 21

7.1 Server Side Connection Paramaters ............................................................................................................ 21

7.2 Server Side Node Parameters ...................................................................................................................... 22

7.3 Server Side Map Descriptors........................................................................................................................ 22

7.3.1 FieldServer Specific Map Descriptor Parameters ................................................................................. 22

7.3.2 Driver Specific Map Descriptor Parameters ......................................................................................... 23

7.3.3 Timing Parameters ............................................................................................................................... 23

7.3.4 Map Descriptor Example – Strategy 1. ................................................................................................ 24

7.3.5 Map Descriptor Example – Strategy 2. ................................................................................................ 24

Appendix A. Useful Features ................................................................................................................................ 25

Appendix A.1. Scaling .............................................................................................................................................. 25

Appendix A.1.1. User Scaling: ........................................................................................................................... 25

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Table of Contents

Appendix A.1.2. Device Scaling: ....................................................................................................................... 25

Appendix A.2. Direct Addressing ............................................................................................................................. 26

Appendix A.3. Direct Addressing Example 1– Reading direct address. ................................................................... 27

Appendix A.4. Direct Addressing Example 2 – Controlling Bytes per Field – Reading ............................................. 27

Appendix A.5. Advanced Map Descriptor Example 3 – Controlling Bytes per Field – Writing ................................ 28

Appendix B. Troubleshooting ............................................................................................................................... 29

Appendix B.1. Connection Problems ....................................................................................................................... 29

Appendix B.2. Negative Acknowledgement - NAK .................................................................................................. 29

Appendix B.3. Node ID problems............................................................................................................................. 29

Appendix B.4. Server Side Configuration – Consecutive Addresses ........................................................................ 30

Appendix B.5. Configuring the OPM to enable communication between the FieldServer and McQuay devices ... 30

Appendix B.5.1. Configuring multiple McQuay devices to communicate to a FieldServer without an OPM:... 30

Appendix C. Reference ......................................................................................................................................... 32

Appendix C.1. Error Messages ................................................................................................................................. 32

Appendix C.2. Statistics ........................................................................................................................................... 34

Appendix C.3. McQuay Equipment Types recognized by the driver. ...................................................................... 35

Appendix C.4. Device Scaling Method ..................................................................................................................... 35

Appendix C.5. Data Field Name Tables .................................................................................................................... 35

Appendix C.5.1. Equipment Type: 200CFC 200 Series Centrifugal Chiller ......................................................... 35

Appendix C.5.2. Equipment Type: 050RPC Reciprocating Chiller ..................................................................... 37

Appendix C.5.3. Equipment Type: 100CFC 100 Series Centrifugal Chiller ......................................................... 38

Appendix C.5.4. Equipment Type : 001ASC Air Cooled Screw Chiller ................................................................ 40

Appendix C.5.5. Equipment Type : Self-Contained Units (SCUs) ....................................................................... 41

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 4 of 43

Code

Description

200CFC

200 Series Centrifugal Chiller

100CFC

100 Series Centrifugal Chiller

001ASC

Air Cooled Screw Chiller – V2.2 Single Compressor Only

000SCU

Self Contained Unit

0050RPC

Reciprocating Chiller

Rooftop Unit

Water Cooled Screw Chiller

Code

Description

Global Scroll chiller

Unit Ventilator

Water Source Heat Pump (WSHP)

MicroTech 2000 WSHP (through MCG (MicroTech Communications Gateway panel)

1 MCQUAY MICRO TECH OPEN PROTOCOL DESCRIPTION

This document describes the FieldServer driver used to transfer data between a FieldServer and MicroTech® unit
and/or network of controllers manufactured by McQuay International. Transfers are done using the controller's
Data Terminal Communications Protocol. In this document the protocol is referred to as the McQuay MicroTech®
Open Protocol. MicroTech controls are legacy products that may require the use of a FieldServer device in order to
support existing applications in need of unit or network controller replacements and/or integration into a Building
Automation System (BAS).

1.1 MicroTech Unit and Syst em Controllers

McQuay International has provided BAS manufacturers licensed access to stand-alone MicroTech unit controllers.
The network access, which is called Open Protocol™, allows a BAS to monitor status and change limited control
parameters in McQuay International HVAC equipment. Monitoring and controlling MicroTech unit controllers may
have required the use of a MicroTech system panel, depending on the unit type, number of units and other
network requirements. There are multiple combinations of MicroTech unit controllers and/or system panels (i.e.
Open Protocol networks) that could use a FieldServer device. FieldServer-supported devices, McQuay Open
Protocol controller descriptions, and network architecture diagrams are all described in the following section.

The McQuay MicroTech® Open Protocol driver allows the FieldServer to transfer data to and from devices over
either RS-232 or RS-485 using McQuay MicroTech® Open Protocol. The FieldServer can emulate either a Server or
Client.

1.1.1 McQuay Equipm ent Types recogn ized by the driv er.

1.1.2 McQuay equipm ent not currently reco ngnized by the driver:

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 5 of 43

CB

PS

SBC

J1 connector

RJ-45

J22

L2

L1

GRD

“Etherne t” po rt

“Netwo rk” port

“PC” por t

Flash memory chip

Ethernet status LEDs

Speaker

5 Vdc power in

1.1.3 McQuay MicroTech network products us ed in conjunction wit h the driver:

1.1.3.1 MicroTech BACdrop™ panel

The MicroTech BACdrop gateway integrates a MicroTech network into a BACnet™ building automation system
(BAS) facilitating monitoring and control of McQuay International equipment from the BAS. The gateway
translates between BACnet objects on an Ethernet® network and McQuay memory locations on a proprietary
MicroTech network.

The BACdrop gateway is a passive device. It receives, translates, and re-transmits messages including both data
and control signals from one network to the other network in either direction but does not perform any
supervisory control for the various MicroTech controllers connected to it. Figure 1 shows the important features
of the BACdrop panel.

Figure 1. BACdrop Panel

1.1.3.2 OPM – Open Protocol Master Panel

The OPM Panel is used when two or more MicroTech controllers need to be interfaced with a BAS by means of a
single-point connection. The OPM acts as a passive communications link between MicroTech controllers and the
BAS and does not perform any supervisory control for the various MicroTech controllers connected to it. When an
OPM is used, all supervisory control (scheduling, overrides, chiller sequencing) is handled by the BAS. The
maximum number of unit controllers per OPM depends on the BAS. For example, the OPM Panel could combine a
McQuay centrifugal chiller, a McQuay applied rooftop unit, and several unit ventilators into a network that a BAS
could connect to with a single cable. Figure 2 shows the important features of the OPM panel.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 6 of 43

Port A

Port B

HI

LO

F1

L1

Port A Select

1 2 3

3

21

Hex

switches

Communication
ports

Red status

LED

Green
status LED

Figure 2. OPM Panel

1.1.3.3 Alternatives to the OPM Panel

The following MicroTech network controllers, which perform specific supervisory control tasks, can be used as
substitutes for the OPM Panel:

RMC (Remote Monitoring and Control panel – Applied Air product)
CSC (Chiller System Controller panel – chiller product)
RMS (Remote Monitoring and Sequencing panel – chiller product)
LWC (Loop Water Controller – WSHP product)

1.1.4 About M ic roTech Network Architecture

All controllers in a MicroTech network are assigned a level: level 1, level 2, or level 3. All networks must have one
level 1 controller to coordinate communications. Multiple level 2 controllers connect to the level 1 controller with
a communications trunk. A trunk is defined as an isolated section of the daisy-chained network wiring. The
network wiring between all controllers is a trunk. Multiple level 3 controllers can be connected to a level 2
controller with a separate trunk; however, this is typically not done in BACdrop applications. The maximum
allowable length of a communications trunk is 5000 ft (1524 m). See Figures 6 and 7 for examples of field wiring.

1.2 Apply ing a FieldServer gateway to diffe re nt MicroTech situation s

There are multiple scenarios where a FieldServer gateway device may be applied to one or more MicroTech
controllers. The most common are listed below, followed by a brief description of each one.

1.2.1 Single st andalone MicroTech 200 Series unit controller

When a FieldServer device is connected to a single MicroTech unit controller, the FieldServer connects to the “A”
port of the MicroTech controller. The unit controller is typically a level 2 device with a Comm Port Configuration of
“L2 TTY/Slave”. MicroTech Level 2 devices must have an address with a non-zero value to the left of the decimal
point and "00" to the right of the decimal point (for example, 01.00, 02.00, 03.00, etc). For a level 2 device, the left
side (the non-zero portion) of the address is set with the controller's rotary hex switches.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 7 of 43

1.2.2 Multiple st andalone MicroTech 20 0 Series unit controllers

1.2.2.1 MicroTech Addressing and Network Archit ecture

When a FieldServer device is connected to two or more MicroTech controllers, a level 1 MicroTech controller is
required to coordinate communications. Typically the level 1 device in this situation is an Open Protocol Master
Panel (an "OPM"). However, the OPM Panel is no longer available from McQuay, so another MicroTech device
may function as the Level 1 device. A 200 Series MicroTech unit controller (for example, a Self-Contained Unit
(SCU) controller) can be re-configured as a level 1 device. Thus if a site has several SCUs, one of them can be re­configured as level 1 and the FieldServer connects to the "A" port of that unit controller. A Level 2 daisy chain is
then connected from the “B” port of the level 1 SCU to the “B” port of the remaining Level 2 SCU's.

It is also possible to use a supervisory MicroTech network controller as the level 1 device which coordinates
communications between the FieldServer device and multiple level 2 MicroTech controllers. Examples of
supervisory controllers are the RMC, CSC, and RMS panels.

Another alternative is to use an NMP (Network Master Panel) controller. An NMP is the level 1 device used in a
MicroTech network (see Figure 3). The NMP coordinates communications of all level 2 and level 3 MicroTech
controllers in this type of network. The NMP also coordinates unit time scheduling, processes alarms, and does
other functions. If an NMP is used in this way, it is necessary to “corrupt” its checksums so that the NMP
application code no longer runs. The process of corrupting checksums can be performed with MicroTech Monitor®
software using the read/write screen. Please contact the McQuay Controls Customer Support group at 866-462­7829 for more information about using Monitor software.

1.2.3 Multiple st andalone MicroTech “ no n-200 Se ries” unit controllers

If a FieldServer gateway device is applied to a site that has several “standalone” unit controllers that have never

been networked together, there are certain guidelines that must be followed. First, a level 1 device is required to
coordinate the communications between the FieldServer device and the MicroTech unit controllers. Typically an
OPM Panel is used for this purpose. However, the OPM is no longer available from McQuay. If the multiple unit
controllers are “non-200 Series” MicroTech controllers such as Unit Ventilators (UVs) or Water Source Heat Pumps
(WSHPs), a Level 1 MicroTech controller must be added to the network to coordinate communications of the Level
2 UVs or WSHPs.

In addition, network wiring would be required to be installed. The FieldServer would be wired to the “A” port of
the Level 1 device. A “level 2 daisy-chain” would be required from the “B” port of the level 1 device to the “B” port
of each level 2 device. See Figures 6 and 7 for network wiring details.

1.2.4 Existing MicroTech netwo rk (Custom M icroTech Monitor soft ware, NMP Panel, etc)

1.2.4.1 With level 3 devices (Unit Vents or WSHPs)

If a FieldServer gateway device is applied to a site that has an existing “MicroTech network” (meaning that it has
custom MicroTech Monitor software for that site and an NMP Panel) and Unit Vents or WSHPs, changes are
required as follows:

The checksums in the NMP’s application code must be corrupted so that the NMP no longer functions as a

Network Master Panel. The FieldServer device connects to the A port of the NMP.

Level 2 LMPs (Local Master Panel) must be removed from the network.
The RS-485 daisy chain connecting all of the Unit Vents or WSHPs must be connected directly to the “B”

port of the Level 1 NMP.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 8 of 43

T

M

M

S

T

S

T

S

Level 1

Laptop PC

RS 232

RS 485

T

S

Port B

Port A

NMP

LMP

MCG RTU

LWC

Port B

Port A

Port B

Port B

Port B

Port A Port A

Port A

Level 2 Trunk

Level 2

Level 3

T

S

WSHP

Port B

Port A

T

S

WSHP

Port B

Port A

T

S

MT 2000

WSHP
Port B

Port A

T

S

Port B

Port A

MT 2000

WSHP

Different application code must be downloaded into all Unit Vents and WSHPs.

In the case of Unit Vents, the “Level 3 network code” for use in a MicroTech network must be

replaced with “Level 2 standalone” Unit Vent code.

In the case of WSHPs, the “Level 3” code for use in a MicroTech network must be replaced with

“Level 2 standalone” WSHP code.

See Figure 3 for details.

Figure 3. MicroTech Network Configurations with Level 1 NMP Supervisory Controller

Port Configuration

M=Master
S=Slave
T=TTY (for PC connection)

Notes:

A PC running MicroTechMonitor connects to an NMP through it’s a Port configured as “TTY”
The A Port of a Level 2 MCG is configured as “USER” to communicate with the MCG’s SLTA.
MicroTech WSHP’s on a MicroTech network require a LMP (Level 2 Local Master Panel) above them.
MicroTech 2000 WSHP’s with LonWorks code (vs LonMark code) are installed below an MCG.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 9 of 43

1.2.4.2 With no level 3 devices

If a FieldServer gateway device is applied to a site that has an existing “MicroTech network” (meaning that it has
custom MicroTech Monitor software for that site and an NMP Panel) with only level 2 controllers and no level 3
devices (such as Unit Vents or WSHPs), changes are required as follows:

The checksums in the NMP’s application code must be corrupted so that the NMP no longer functions as a

Network master Panel. The FieldServer device connects to the “A” port of the NMP.

No network wiring changes are necessary

1.2.5 Existing MicroTech Open P ro tocol net work

If a FieldServer gateway device is applied to a site that has an existing “Open Protocol network”, the following
assumptions are made:

The site has either an OPM Panel or some other level 1 MicroTech controller that is functioning as an

OPM.

Any Unit Vents or WSHPs in the network are already running the proper “Level 2” application code

required for an “Open Protocol” network.

No network wiring changes are necessary.
See Figure 7 for details

1.2.6 Replacin g a BACdrop Gat eway panel

1.2.6.1 Connected a Single Micro Tech unit controlle r

When a FieldServer device is used to replace a BACdrop panel that has been connected to one MicroTech unit
controller, some re-wiring is necessary. The RS-485 network terminals of the BACdrop panel are connected to the

“B” Port of the MicroTech controller, but the FieldServer connects to the “A” port of the MicroTech controller. The
unit controller will be a level 2 device with a Comm Port Configuration of “L2 TTY/Slave”. MicroTech Level 2

devices must have an address with a non-zero value to the left of the decimal point and "00" to the right of the
decimal point (for example, 01.00). For a level 2 device, the left side (the non-zero portion) of the address is set
with the controller's rotary hex switches.

1.2.6.2 Connected to Multiple MicroTech unit control lers

When a FieldServer device is used to replace a BACdrop panel that has been connected to multiple MicroTech unit
controllers with no Level 1 supervisory panel such as an RMC, CSC, or RMS, a Level 1 device must be added. If the
unit controllers are 200 Series MicroTech, this can be accomplished by re-configuring one of the unit controllers to
be Level 1. The alternative to re-configuring one of the existing unit controllers to be a Level 1 device is to add a
level 1 device such as an OPM, RMC, CSC, or RMS, but this may be difficult because all of these control panels are
obsolete and no longer available. For a typical BACdrop network, the BACdrop panel is the level 1 controller and
the unit controllers are level 2 controllers. See Figures 4 and 6 for details.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 10 of 43

RTU UV

Up to 63 MicroTech
controllers per BACdrop

BACnet on ISO 8802-3 (Ethernet), 10BaseT

MicroTech

BACdrop

(level 1)

Chiller UV UV UVSCU

Level 2

MicroTech

Level 1

BACnet BAS

by others

Main "front end"
PC for BAS

MicroTech network (RS-485)

Chiller

Level 2

MicroTech

Up to 63 MicroTech
controllers per BACdrop

BACnet BAS

by others

BACnet on ISO 8802-3 (Ethernet), 10BaseT

MicroTech

BACdrop

(level 2)

Level 1

ChillerChiller

Main "front end"
PC for BAS

CSC

Chiller

MicroTech network (RS-485)

All data requests from BACnet BAS to
MicroTech level-2 controllers are routed
through level-1 MicroTech controller

Figure 4. MicroTech Architecture

1.2.6.3 Connected to multiple MicroTech unit controllers and a supervisory panel su ch as an RMC,

CSC, or RMS panel
When a FieldServer device will be replacing a BACdrop Gateway panel that was connected to multiple MicroTech
unit controllers with a Level 1 supervisory panel such as an RMC, CSC, or RMS, some re-wiring may be necessary.
The FieldServer device must be wired to the A Port of the Level 1 device. The B Port of the Level 1 device is then
wired to the B Port of all Level 2 devices with a daisy chain. See Figure 5 for details.

Figure 5. Level 2 BACdrop Panel with Level 1 Supervisory Panel

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 11 of 43

TS2

BACdrop

Hot
Neutral

100 – 240 Vac
Power

L2
L1

GRD

Notes:

1. Twisted, shielded pair cable must meet the following
minimum requirements: 300 V, 60°C, 20 AWG, polyethylene
insulated, with a PVC outer jacket and drain wire (Belden
8762 or equivalent). Some local codes may require the use
of plenum rated cable.

2. 10BaseT Ethernet cable. To directly connect a PC to the
Ethernet port, a hub or a special crossover cable must be
used.

3. Cable length must not exceed 5000 ft (1524 m).

4. Standard serial cable. A null modem is not required.

See notes 1 & 3

Self-contained AC

Port B

GND

TB7

Reciprocating

chiller

Port B

139

TB4

Screw chiller

Port B

55

BLK

WHT

B+

B–

138

137

54

53

Comm B

UVC (325)

1

2

PNK

GRY

Comm B

UVC (125)

4

5

PNK

GRY

RJ-45

3rd-party BAS

See note 2

TB1

Centrifugal chiller

(series 200)

Port B

858684

TB2

Applied rooftop

Port B

130

128

129

Legend

Field wiring terminal
Field wiring: discrete

Factory wiring

Field wiring: twisted, shielded pair cable
with drain wire (see note 1)

B+

Crimp or solder splice

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

BLK

WHT

Comm B

UVC (325)

1

2

PNK

GRY

Comm B

UVC (325)

1

2

PNK

GRY

Comm B

UVC (325)

1

2

PNK

GRY

Ethernet

DB9

PC

PC

+

–

GRD

Network

See note 4

Field wiring: 10BaseT Ethernet
Standard serial cable

1.3 MicroTech Comm unicat ion Port Configuration

In addition to the rules about MicroTech architecture and addressing, there is also a critical parameter called the
Comm Port Configuration. The Comm Port Configuration must also be set correctly for a unit controller to be able
to communicate. This comm port configuration for level 1 devices is different to level 2 devices. While it is
necessary to know this for proper unit controller setup and for troubleshooting communication problems, it is not
critical from the FieldServer side for programming or routing.

A level 1 device must have its communication port configuration set up as “Level 1 TTY/Slave”. To change this

configuration, connect to the unit controller with MicroTech Monitor software through the “A” port, proceed to
the “Read/Write” screen, read memory address “0A11”, and change the value to “C1” (Level 1 TTY/Slave). After
doing this, the controller must also have its rotary hex switches set to the Level 1 address of “00” to make the unit
controller’s network address 00.00. Please note that power must be cycled to the controller for this new hex

switch setting to take effect.

Figure 6. MicroTech Network with BACdrop Panel as Level 1 Device

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 12 of 43

Document

Description

Location

IM 474

Open Protocol Master (OPM) Panel

www.mcquay.com

IM 689

BACdrop Gateway for MicroTech

www.mcquay.com

IM 658

Network Master Panel (NMP)

Contact McQuay

CD 573875Y

Microtech Open Protocol Wiring Diagrams

Contact McQuay

IM 444

Remote Monitoring and Control (RMC) Panel

Contact McQuay

IM 498

Remote Monitoring and Sequencing (RMS) Panel

Contact McQuay

IM 618

MicroTech Chiller System Controller (CSC) Panel

Contact McQuay

*Or other Level 1 Device (CSC, etc.)

Figure 7. MicroTech Network with OPM Panel as Level 1 Device

1.4 Reference Documents

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

McQuay Micro Tech Open Protocol Driver Manual Page 13 of 43

FieldServer Technologies Part #

Description

FS-8917-16

RJ45 to terminal connector cable.

Part #

Description

McQuay Motor Mount Connector for Port A connection

2 DRIVER FEATURES

When emulating a Client, the driver enables the FieldServer to request ‘Everything’ from the McQuay, allow
specific fields to be read or written and apply 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.

Arising from a feature of the McQuay MicroTech® 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 that the multi byte value is only
partially correct until all the messages have been completed.

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.

Port expansion is not supported for this driver.
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.

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.

3 DRIVER SCOPE OF SUPPLY

3.1 Sup plied by FieldServ er Technologies for this driver

3.2 Provided by Supplier of 3

rd

Party Equipment

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]