manualshive.com logo in svg

FieldServer FS-8700-80, Driver Manual, Page: 4 / 43

Share
Download
FieldServer FS-8700-80 Driver Manual Download Page 4

McQuay Micro Tech Open Protocol Driver Manual   

 

 

 

 

Page 4 of 43

 

FieldServer Technologies

 1991 Tarob Court Milpitas, California 95035 USA   

Web

: www.fieldserver.com 

Tel

: (408) 262 2299   

Fax

: (408) 262 2269   

Toll Free

: (888) 509 1970   

email

: [email protected] 

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 System 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 Equipment Types recognized by the driver. 

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 

1.1.2

 

McQuay equipment not currently recongnized by the driver:  

Code  Description 

 

Global Scroll chiller 

 

Unit Ventilator 

 

Water Source Heat Pump (WSHP) 

 

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

Summary of Contents for FS-8700-80

Page 1: ...nt Revision 6 A Sierra Monitor Company 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 ...

Page 2: ...icroTech 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 3 rd 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...

Page 3: ... 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 ...

Page 4: ...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 de...

Page 5: ...rm 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 CB PS SBC J1 connector RJ 45 J22 L2 L1 GRD Ethernet port Network port PC port Flash memory chip Ethernet status LEDs Speaker 5 Vdc power in 1 1 3 2 OPM Open Protocol Master Panel The OPM Panel is used when two or more MicroTech controlle...

Page 6: ...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 wiri...

Page 7: ... 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 standalone MicroTech non 200 Series unit controllers If a FieldServer gateway device is applied to a site that has several standalone u...

Page 8: ...3 for details Figure 3 MicroTech Network Configurations with Level 1 NMP Supervisory Controller 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 Port Configuration M Mas...

Page 9: ...e MicroTech unit controller 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...

Page 10: ... 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 ...

Page 11: ...ntroller 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 TS2 BACdrop Hot Neutral 100 240 V ac 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 a...

Page 12: ...ce 1 4 Reference Documents 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 McQua...

Page 13: ...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 f...

Page 14: ...9 Toll Free 888 509 1970 email support fieldserver com 4 HARDWARE CONNECTIONS The FieldServer is connected to the McQuay device as shown below Configure the McQuay device according to manufacturer s instructions FS 8917 16 RJ45 04 BLUE WHITE RJ45 08 ORANGE WHITE SERIES 200 CONTROLLER FS COM RJ45 01 BROWN FS Tx FS Rx FieldServer Connect to one of the RS 232 Ports on the FieldServer P1 1 8 ...

Page 15: ...te correct storage of the relevant data Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format FLOAT BIT UInt16 SInt16 Packed_Bit Byte Packed_Byte Swapped_Byte Data_Array_Length Number of Data Objects Must be larger than the data stora...

Page 16: ...e 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 valu...

Page 17: ...r P1 P8 R1 R22 PLC_Type The name of the McQuay Equipment type being polled The equipment type must be known for the driver to operate correctly 200CFC 100CFC 050RPC 001ASC 000SCU Type Unknown Password Maximum of 8 characters Ascii characters only Node_Hi Specify the rotary Hi address switch setting of the Mcquay controller 0 to F Node_Lo Specify the rotary Lo address switch setting of the Mcquay c...

Page 18: ...e number of data elements to be read Any positive integer 1 Field_Name 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 2 for further information A field name from Appendix C 3 Everything Device_Scali...

Page 19: ...riptor Example 2 Read a particular Data Field This example illustrates how to read data for one particular field of interest The data is read every 2 0 seconds and the value obtained is stored in the Data Array named DA_OPERATIONAL_MODES at location 10 Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Scan_Interval Node_Name Length Field_Name Chiller10_Op_Mode DA_OPERATIONAL_MODES 10 ...

Page 20: ... generated each time the data at index 0 in the Data Array changes When writing multibyte fields several messages are required to transfer the byte values to the McQuay devices Note that Device_Scaling has no meaning when writing to a McQuay device The user must ensure that valid numbers are written to the data fields Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Length ...

Page 21: ...t Specify which port the device is connected to the FieldServer P1 P8 R1 R2 3 Baud Specify baud rate 300 1200 2400 4800 9600 Vendor limitation Parity Specify parity Even Vendor limitation Data_Bits Specify data bits 7 Vendor limitation Stop_Bits Specify stop bits 1 Vendor limitation Protocol Specify protocol used MCQ McQuay Example Server Side Connections Connections Port Baud Parity Data_Bits Pro...

Page 22: ...PLC_Type This parameter has no meaning for a Server but it must be specified to allow the driver to complete its configuration file validation 200CFC 100CFC 050RPC 001ASC 000SCU Type Unknown Password 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 Node_Hi Specify the rotary Hi a...

Page 23: ... 0 to Data_Array_Length 1 as specified in Section 5 Function Function of Client Map Descriptor Passive 7 3 2 Driver Specific Map Descriptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from One of the Node Names specified in Section 7 2 Length Length of Map Descriptor 1 10000 Address Starting address of read block Addresses cannot be specified in hexadecimal f...

Page 24: ... 5 Map Descriptor Example Strategy 2 In this example the memory being emulated is divided into chunks to avoid having a large sparse array When a poll is received the driver looks through the Map Descriptors and finds one with a matching Node and one whose address and length cover the poll s address Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Address Length Chiller1_em...

Page 25: ...ser 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 6 3 2 Note that this parameter needs to be used in conjunction with Field_Name There are 5 device scaling methods Refer to Appendix C 4 and Appendix C 5 for information on the application of these parameters Note that when device scaling is a...

Page 26: ...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 r...

Page 27: ...rver combines the 4 values into a single value and stores this single value in a single Data Array element The driver reads address 4096 and gets a value Call this value v0 The driver reads address 4097 and gets a value Call this value v1 The driver reads address 4098 and gets a value Call this value v2 The driver reads address 4099 and gets a value Call this value v3 When the 4 th address has bee...

Page 28: ... the FieldServer s Data Arrays The value v0 value_extracted_from_DA AND 0xff The value v1 value_extracted_from_DA shift right by 8 AND 0xff The driver writes value v0 to address 4096 The driver writes value v1 to address 4097 Map_Descriptor_Name Data_Array_Name Data_Array_Offset Node_Name Address Length Bytes_Per_Field Scan_Interval Function Chiller1_emulation DA_CHILLER1 0 Chiller1 4096 1 2 1 0s ...

Page 29: ... 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 Devic...

Page 30: ...emp DA_AI_01 02 Passive Node_A 1063 1 Space Temp DA_AI_01 03 Passive Node_A 1066 1 Control Temp Part 1 DA_AI_01 04 Passive Node_A 1074 1 Appendix B 5 Configuring the OPM to enable communication between the FieldServer and McQuay devices Appendix B 5 1 Configuring multiple McQuay devices to communicate to a FieldServer without an OPM The FieldServer will be wired to a Level 1 Microtech controller a...

Page 31: ...nter b00 00 to change the Box Address Node_HI and Node_LO to 00 9 Enter w0A11 C1 to write C1 to memory address 0A11 This will set up the comm port configuration with Port A as TTY and Port B as Master 10 Test if the wiring to the daisy chained devices is correct by doing the following o To read from a controller with the rotary hex switches set to 01 change the box address to 01 00 and enter r0A11...

Page 32: ...he limit is reached call support McQuay 5 Err Node d has more than one password 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 th...

Page 33: ...l Maybe password or Node_ID 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 Node_ID route or password has been incorrectly specified in the configuration file Verify these settings The message is printed once and suppressed for subsequent occurrences Refer to Appendix B 2 McQuay 28 Err Device responded with a NAK...

Page 34: ...tiplying the port number by 50 and then using the location offset indicated in the table below Location Statistic 0 MCQ_STAT_PASSWORD 10 MCQ_STAT_NAK 11 MCQ_STAT_NOISE 12 MCQ_STAT_NOISE_CODE 13 MCQ_STAT_NON_ASCII_CHARS 14 MCQ_STAT_BAD_START_BYTE 15 MCQ_STAT_OTHER_CMPLT_ERR 16 MCQ_STAT_CLIENT_BYTES_RCVD Location Statistic 17 MCQ_STAT_CLIENT_FRAGS_RCVD 18 MCQ_STAT_CLIENT_MSGSS_RCVD 19 MCQ_STAT_CLIEN...

Page 35: ... 2 5 X 100 6 X 100 10 7 X 5 20 8 X 5 55 9 X 5 10 X 5 100 11 X 51 419 51 12 X 125 500 13 X 0 02 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 Appendix C 5 Dat...

Page 36: ...enser Pump 2 Operating Hours 2 0x085D 1 42 r Condenser Refrigerant Pressure 2 0x0440 2 44 r Condenser Refrigerant Temperature 2 0x0466 3 46 r Condenser Subcooling Temperature 2 0x0480 2 48 r Condenser Water Flow Rate 2 0x0452 1 50 r Condenser Water Flow Status 1 0x045F 1 51 r Condenser Water Rate Sensor 1 0x083D 1 52 r Condenser Water Temperature Delta 2 0x0488 2 54 r Condenser Water Temperature E...

Page 37: ...Outdoor Air Temperature BAS 1 0x0473 5 117 b Master Slave Setpoint 1 0x093C 1 118 b Lead Lag Mode Setpoint 1 0x093D 1 119 b Enable Lag Setpoint 1 0x093E 1 120 b Disable Lag Setpoint 1 0x093F 1 121 b Lag Standby Setpoint 1 0x0942 1 122 b Lead Lag Switch Setpoint Day 1 0x0948 1 123 b Lead Lag Switch Setpoint Hour 1 0x0949 1 124 r Lead Lag Status 1 0x0401 1 125 r Lead Unit 1 0x0402 1 126 r Lead Unit ...

Page 38: ...cuit 2 Superheat Temperature 2 0x0495 2 53 r Compressor 1 Operating Hours 2 0x0862 1 55 r Compressor 1 Starts 2 0x086A 1 57 r Compressor 2 Operating Hours 2 0x0864 1 59 r Compressor 2 Starts 2 0x086C 1 61 r Compressor 3 Operating Hours 2 0x0866 1 63 r Compressor 3 Starts 2 0x086E 1 65 r Compressor 4 Operating Hours 2 0x0868 1 67 r Compressor 4 Starts 2 0x0870 1 69 r Condenser Entering Water Temper...

Page 39: ...x0401 1 26 r Entering Evaporator Water Temp Hi Resolution 1 0x041A 1 27 r Entering Water Reset 1 0x0438 1 28 r Evaporator Low Pressure Switch 1 0x050E 1 29 r Evaporator Pump 1 0X021B 1 30 r Evaporator Refrigerant Pressure 1 0x0410 1 31 r Evaporator Refrigerant Temp Lo Resolution 1 0x0402 1 32 r Evaporator Refrigerant Temp Hi Resolution 1 0x041B 7 33 r Evaporator Water Flow Switch 1 0X050F 1 34 r H...

Page 40: ... Clear Current Fault 1 0X042A 1 83 b Comm Port Baud Rate 1 0x0801 1 84 b Correct Checksum 1 0x0800 1 85 b Leaving Evaporator Temperature Setpoint 1 0x0900 7 86 b Maximum Chilled Water Reset Setpoint 1 0x0820 9 87 b Network Amp Reset 1 0x0450 1 88 b Network Chilled Water Reset 1 0X044F 1 89 b Network Start Stop 1 0x0451 1 90 b Reset Option 1 0x0822 1 91 b Soft Reset 1 0x0204 1 92 b Start Mode 1 0x0...

Page 41: ...etwork Command 1 0x044F 1 48 b Network Demand Limit 1 0x044D 1 49 b Network Evaporator Leaving Water Temp Reset 1 0x044E 1 50 b Reset Option Setpoint 1 0x090B 1 Appendix C 5 5 Equipment Type Self Contained Units SCUs Array Location Read Write Both Field Name Number of Bytes Base Address Device Scaling Method9 1 r Air Velocity 1 0x0434 11 2 r Airflow Status 1 0x045C 1 3 r Current Alarm 1 0x0801 1 4...

Page 42: ... 1 59 r Supply Fan Status 1 0x045E 1 60 r Unit Enabled Status 1 0x0488 1 61 r Unit Status 1 0x043D 1 62 r Variable Inlet Vane Position 1 0x0436 1 63 r Water Flow Required 1 0x0445 1 64 r Water Flow 1 0x045B 1 65 r Water Pump Start Stop 1 0x0461 1 66 b Building Static Pressure Setpoint 1 0x0923 12 67 b Clear Alarm 1 0x04CE 1 68 b Clear Alarm Buffer 1 0x048A 1 69 b Control Mode 1 0x044F 1 70 b Contr...

Page 43: ...Humidity Deadband 1 0x094C 1 93 b Humidity Setpoint 1 0x094B 1 94 b Low Entering H20 Comp Lockout Differential 1 0x092C 1 95 b Low Entering Water Compressor Lockout Setpoint 1 0x092B 1 96 b Min Vane Position Fan Speed 1 0x0951 1 97 b Minimum Outdoor Air Damper Position 1 0x0934 1 98 b Minimum Supply Air Temperature Control 1 0x0919 1 99 b Unoccupied Cooling Space Differential 1 0x0904 1 100 b Unoc...

Reviews:

No comments