Bacnet® Link Technical Guide

www.orioncontrols.com

BACnet® Link Technical Guide

Revision- 02B - August 2005 Table Of Contents General Information ...... 3 Data Sharing ...... 3 Scheduling ...... 3 Hardware Specifications ...... 3 Connection and Wiring Information ...... 4 Troubleshooting Information ...... 5 General Information ...... 5 Using LED’s To Verify Operation ...... 5 Programming- General Information ...... 6 BACnet® Link Overview ...... 6 BACnet® Link Device Object ...... 6 WattBacObjectTypes ...... 6 Local Address (MAC address) ...... 6 BACnet® Services Supported ...... 6 MS/TP LAN Baud Rate ...... 6 Programming - Standard Objects ...... 7 General Information ...... 7 Parameters ...... 7 Instance Number Base ...... 7 MUA II Instance Number Base ...... 7 MUA II BACnet® Property Identifier ...... 8 VAV/CAV Instance Number Base ...... 9 VAV/CAV BACnet® Property Identifier ...... 9 CW/HW Instance Number Base ...... 10 CW/HW BACnet® Property Identifier ...... 11 Parameter Instance Numbers ...... 12 Programming - Proprietary Objects ...... 13 BACnet® Link Overview ...... 13 MUA II Object ...... 13 MUA II Property Identifier ...... 14 VAV/CAV Object ...... 15 VAV/CAV Property Identifier ...... 16 CW/HW Object ...... 17 CW/HW Property Identifier ...... 18 Proprietary Object Instance Numbers...... 19 Appendix 1 ...... 20 BACnet® Link Protocol Implementation Conformance Statement ...... 20

WattMaster Controls Inc. 8500 NW River Park Drive · Parkville , MO 64152 Toll Free Phone: 866-918-1100 PH: (816) 505-1100 · FAX: (816) 505-1101 · E-mail: [email protected] Visit our web site at www.orioncontrols.com Form: OR-BACNET-TGD-02B Copyright 2005 WattMaster Controls, Inc. AAON® is a registered trademark of AAON, Inc., Tulsa, OK. BACnet® is a registered trademark of ASHRAE Inc., Atlanta, GA. WattMaster Controls, Inc. assumes no responsibility for errors, or omissions. This document is subject to change without notice. Technical Guide General Information The OE367-22 BACnet® Link provides bi-directional translation of Hardware Specifications data and information between BACnet® devices and Orion VAV/CAV, CW/HW and MUA II unit controllers. Table 1 below contains the hardware specifications for the BACnet® Link interface. Up to 16 total, Orion VAV/CAV, CH/HW, MUA II or any combination of these controllers may be connected to each BACnet® Link. Up to 4 BACnet® Links can be used on a Orion Controls system allowing for Technical Data a maximum of 64 total controllers to be used. BACnet Loop RS-485, Auto Detect Host Matching - 9600, 19200, 38400, Data Sharing 76800 Baud Rates RS-485, 9600 Baud The BACnet® Link interface provides the following data sharing capa- Controller Loop bilities: Protocol (BACnet Loop) MS/TP Lan • Provides values from points on the Orion side of the Protocol HSI Open Protocol (WattMaster Loop) Token Passing gateway to BACnet® devices as if the values were originating from BACnet® objects. Power Input Voltage 24 VAC • Allows BACnet® devices to modify point values on the Power Consumption 10 VA Maximum Orion controller side of the BACnet® Link by using Operating Temp 10°F to 149°F ® standard BACnet write services Operating Humidity 90% RH Non-Condensing Scheduling Weight 8 oz

• Ability to allow BACnet® devices to send Schedule events to the Orion controller side of the gateway by using Table 1: BACnet® Link Interface Technical Data standard BACnet® services

0.20 Dia. Mounting Hole Typ. 4 PL. Address Switch

0.25” Mounting Backplate EPROM Chip RAM Chip Pin 1 Indicator Pin 1 Indicator R1 R3 TRANSLATOR BOARD YS101928 SERIAL # REV 0 ADDR. EPROM RAM JP1 U3 U5 C1 C2 2 1 U4 C3 Network (MSTP) C4 Local Loop R5

Communications X1 U1 Communications EEPROM Wiring Terminal C5 Wiring Terminal

U2 LOCAL NET- C6 WORK LOOP LOOP R4 Local Loop U6 R (+) Communications T Driver Chip Network SHLD SHLD RN1 Driver Chip C7 T (-) 24 VAC Power R C8 C10 JP2 Terminals U8

4.50" X2

4.00” VCC VBAT DRIVER R2 C9 U9

DRIVER C11

L1 R6 R7 R8 R9 R12

WDOG U10 C13 Q1 C12 JP3 TB3 U7 D1 GND TERM. R13

C14 C16 +24VAC

R16 C17 JP4 R18 R10 R11 R15 R14 RN2 R19 R17 R22 D2 R21 U11 R20 D3 COMM NET COMM LOOP E 1 LED 2 LED 3 LED 4 LED PWR C19 R23 Network Communications LED Power Local Loop LED Communications LED 7.00" 0.25”

7.50"

Figure 1: BACnet® Link Board Components and Dimensions

BACnet® Link Interface 3 Technical Guide Connection and Wiring Information

BACnet Link Interface

BACnet MS/TP VAV/CAV or MUA II Unit Controller VAV/CAV or MUA II Unit Controller VAV/CAV or MUA II Unit Controller LAN Connection To BACnet Network

24 VAC (10 VA) Line Voltage

T SHLD 24 VAC 24 VAC 24 VAC R (8 VA) (8 VA) (8 VA) Typical Terminal Blocks. All Line Voltage Line Voltage Line Voltage Wiring To Be T To T, SHLD (G) To SHLD (G)&RToR VAV/CAV or MUA II Unit Controller VAV/CAV or MUA II Unit Controller VAV/CAV or MUA II Unit Controller

UP Mode Selection

STATUS PREV NEXT

SETPOINTS ESC DOWN CLEAR

SCHEDULES

ENTER

OVERRIDES

ALARMS 132

CONFIGURATION 4 5 6

BALANCE - TEST 7 8 9

ON DEC 0 MINUS-

Modular Service Tool

All Programming Of Unit Controllers Must Be Done With The Modular Service Tool 24 VAC 24 VAC 24 VAC (8 VA) (8 VA) (8 VA) Line Voltage Line Voltage Line Voltage

To Next VAV/CAV or MUA II Controller On Loop Up To 16 Controllers Can Be Interconnected

Figure 2: BACnet® Link Interface Wiring

Figure 3: BACnet® Link Interface Address Switch Setting

4 BACnet® Link Interface Technical Guide Troubleshooting Information General Information This LED is used to indicate the number of controllers the BACnet® Link is communicating with. The BACnet® Link is designed to only work with the following Orion controllers. LED 1 This LED is not currently used. VAV/CAV Controller (SS1003, SS1012, Y200235, Y200301) MUA II Controller (SS1004, Y200231, Y200306, Y200405) PWR LED Operations When the BACnet® Link is powered up, the “PWR” LED should light CW/HW Controller (Y200311) up and stay on continuously. If it does not light up, check to be sure that you have 24 VAC connected to the board, that the wiring connec- To determine what controller you have you must look at the label lo- tions are tight and that they are wired for correct polarity. The 24 cated on the controller E-prom. If the controller label does not match VAC power must be connected so that all ground wires remain com- any of the SS or Y numbers listed above, your controller will not work mon. If after making all these checks the PWR LED does not light up, with the BACnet® Link. please contact WattMaster technical support for assistance.

Using LED’s To Verify Operation LOOP COMM LED Operations The BACnet® Link is equipped with LED’s that can be used for trouble- When power is applied to the BACnet® Link the “LOOP COMM” shooting. There are seven LED’s on the BACnet® Link. Five of these LED will also light up. The LED should flicker rapidly indicating LED’s are used in troubleshooting. The LED’s and their uses are as that the BACnet® Link is trying to communicate with the controllers follows: on the loop. A “flicker” is defined as a brief moment when the LED turns off then back on. If the LOOP COMM LED does not operate as indicated above, first power down the unit and then reapply power. If PWR this does not work, then contact WattMaster technical support for as- This LED will light up to indicate that 24 VAC power has been ap- sistance. plied to the controller. LED 2 Operations LOOP COMM When power is first applied, “LED 2” will be off temporarily then will This LED will light up to indicate communication with the controllers blink one time for each controller it is communicating with. For ex- on the loop. ample, if you have 10 controllers on the loop connected to the BAC- net® Link then LED 2 will blink 10 times. If the amount of blinks NET COMM does not match the number of controllers connected to the loop, it This LED will light up to indicate communication with the BACnet® indicates there is a communications problem. The best way to find router. out which board is not communicating is to go to each controller and look at its COMM LED. The LED should be solid and will flicker LED 4 occasionally indicating communication with the BACnet® Link. If This LED is not currently used. the COMM LED does not flicker, there is no communication with that controller. LED 3 This LED is also used to indicate communication with the BACnet® NET COMM LED Operations router. The “NET COMM” LED works the same way as the LOOP COMM LED but it indicates that the BACnet® Link is trying to communicate LED 2 with the BACnet® router. LED 3 Operations When power is first applied , “LED 3” will be off temporarily and then will blink slowly indicating communication with the BACnet® router. If LED 3 does not blink, this means it is not communicating with the BACnet® router. The first thing to check is the wiring between the BACnet® Link and the BACnet® router. Make sure that T is wired to the (-) terminal of the router and R is wired to the (+) terminal of the router.

If all of these tests are made and the controller still doesn’t operate, please contact WattMaster Controls Technical Support at our Toll Free number, 866-918-1100 for assistance.

Figure 4 BACnet® Link LED Locations BACnet® Link Interface 5 Technical Guide Programming- General Information BACnet® Link Overview Local Address (MAC address) The BACnet® Link provides the communications interface between the The BACnet® Link’s Local Address (MAC address) on the MS/TP Orion system and a BACnet® network. One BACnet® Link can support LAN is determined by the address jumper on the device. The Local up to sixteen controllers. The BACnet® Link connects to the BACnet® Address is always the address jumper plus 32. Therefore, the network using Master-Slave/Token Passing (MS/TP) LAN data link BacnetOrionInterface device’s Local Address (MAC address) can be protocol. set to address 32, 33, 34 or 35. See Figure 3 for address switch setting information. The BACnet® Link supports 3 different controller types (device objects). These are the Orion MUA II, VAV/CAV and the CW/HW con- BACnet® Services Supported trollers. The BACnet® Link supports the following BACnet® services: BACnet® Link Device Object ReadProperty Service ReadPropertyMultiple Service ® The information that follows describes the characteristics of the BACnet WriteProperty Service Who-Has and I-Have Service Link Device Object. The properties for the BACnet® Link Device Ob- Who-Is and I-Am Service ject are listed in Table 2. MS/TP LAN Baud Rate Object Name The Object Name is a 15 byte character string that can be set through The OE367-22 BACnet® Link (Device Object) is able to detect the Baud the BACnet® front end. rate of the host BACnet® MS/TP LAN and automatically adjust its Baud rate to match the host. The BACnet® Link will then operate at the host’s Instance Number Baud rate of 9600, 19200, 38400 or 76800 Baud as required. The Instance Number of the Device Object is determined by the address jumper setting on the BACnet® Link. The BACnet® Link has two BACnet® Link Device Object Properties address jumpers which allows the addressing number range to be from Read 0 to 3. The Instance Number of the Device Object would be the jumper Property Identifier Property Data Type or ® number plus 600192. This means there can be only four BACnet Links Write (Device Objects) on the entire local BACnet® system installation. APDU_Timeout Unsigned R/O Location and Description Application_Software_Version CharacterSting R/O The Location and Description are 15 bytes character strings that can Data_Base_Revision Unsigned R/O be set through BACnet®. Description CharacterSting R/W Firmware_Revision CharacterSting R/O Local Time and Date Local_Date Date R/W The BACnet® Link (Device Object) does not have a hardware real time Local_Time Time R/W clock. It does however keep a software timer running once the time and date has been set through the BACnet® front end (by others). Since this Location CharacterSting R/W is a software timer, if the BACnet® Link loses power, the time will be Max_APDU_Length_Accepted Unsigned R/O lost or incorrect and will need to be reset. Max_Master Unsigned R/O WattBacObjectTypes Max-Info_Frames Unsigned R/O Model_Name CharacterSting R/O ® The BACnet Link (Device Object) amends the following object type Number_Of_APDU_Retried Unsigned R/O to BACnet®’s object type, BACnetObjectType. Object_Identifier BACnetObjectIdentifier R/O WattBacObjectTypes := Enumerated { Object_List BACnetARRAY[N] R/O CwHw (259) Object_Name CharacterString R/W MuaII (258) Object_Type BACnetObjectType R/O VavCav (257) Protocol_Conformance_Class Unsigned(1..6) R/O } Protocol_Object_Types_Supported BACnetObjectTypesSupported R/O ® If any of these WattBacObjectTypes conflict with other custom BACnet Protocol_Services_Supported BACnetServicesSupported R/O object types on your BACnet® system, please contact WattMaster controls. Protocol_Version Unsigned R/O Segmentation_Supported BACnetSegmentation R/O System_Status BACnetDeviceStatus R/O Vendor_Identifier Unsigned16 R/O Vendor_Name CharacterString R/O

Table 2: BACnet® Link Device Object Properties 6 BACnet® Link Interface Technical Guide Programming - Standard Objects General Information MUA II Instance Number Base The BACnet® Link provides additional shadowing Analog Input Ob- Instance Number Base For MUA II Controller jects and Analog Value Objects for read/write parameters of the MUA II, VAV/CAV and CW/HW controllers. Instance Represented Limits Parameter Number By Base Object Note: The BACnet® Link does not implement any operational Alarm Status 14 Analog Input function for the Analog Input Object or the Analog Value Control Status 12 Analog Input Object but only uses the Current Value property of the Cooling Deadband 20 Analog Value 2 20 Analog Input/Value Object as a vehicle to convey one Current Mode 11 Analog Input specified parameter of the MUA II, VAV/CAV or CW/ Dew Point Reset Limit 27 Analog Value 40 DP Spt. HW controller. Dewpoint Setpoint 22 Analog Value 40 80 Enthalpy Deadband 23 Analog Value 3 20 Read Only Parameters are represented by Analog Input Objects and External Heat Position 15 Analog Input Setpoint Parameters are represented by Analog Value Objects. External Heat Proportion 30 Analog Value 1 30 Band Parameters External Relay Group #1 34 Analog Input Parameters for (1) MUA II controller are represented by 36 Analog External Relay Group #2 35 Analog Input Input/Value Objects. External Relay Group #3 36 Analog Input Heating Deadband 21 Analog Value 2 20 Parameters for (1) VAV/CAV controller are represented by 52 Analog Modulate Gas Valve 17 Analog Input Input/Value Objects. Position On Board Relay Group 33 Analog Input Parameters for (1) CW/HW controller are represented by 54 Analog Outdoor Air Cooling 3 Analog Input Input/Value Objects. Setpoint Outdoor Air Dew Point 5 Analog Input Instance Number Base Outdoor Air Dew Point 6 Analog Input Setpoint Each Analog Input/Value Object has an unique Object Instance Num- Outdoor Air Enthalpy 8 Analog Input ber Base that can be used to identify which parameter the object repre- sents. The unique Object Instance Numbers are calculated from for- Outdoor Air Enthalpy 10 Analog Input Deadband mula based on the Instance Number Base which are defined in the tables that follow. Outdoor Air Enthalpy 9 Analog Input Setpoint Outdoor Air Heating 4 Analog Input Setpoint Outdoor Air Humidity 7 Analog Input Outdoor Air Temperature 2 Analog Input Reheat Value Position 18 Analog Input Schedule Force 32 Analog Value 0 2 Space Humidity 13 Analog Input Space Humidity At Max 28 Analog Value 0 100 Supply Space Humidity At Min 29 Analog Value 0 100 Supply Space Temperature 16 Analog Input Space Temperature At 25 Analog Value 40 100 Max Supply Space Temperature At Min 26 Analog Value 40 100 Supply Supply Air Reset Limit 24 Analog Value SA SA Spt. Spt. + 50 Supply Air Setpoint 31 Analog Value 50 90 Supply Air Setpoint Mirror 1 Analog Input Supply Air Temperature 19 Analog Input

Table 3: Instance Number Base Data For MUA II

BACnet® Link Interface 7 Technical Guide Programming - Standard Objects

MUA II BACnet® Property Identifier MuaIIOnBoardRelayBits ::= BIT STRING { OnBoardRelay1 (0), The BACnet® Link amends the following property identity to BACnet®’s property identifier. OnBoardRelay2 (1), OnBoardRelay3 (2), BACnetPropertyIdentifier : OnBoardRelay4 (3), OnBoardRelqy5 (4), WattBacScheduleState ::= ENUMERATED { } NormalOperation (0), ForceOccupied (1), MuaIIExRelayGroup1Bits ::= BIT STRING { ForceUnoccupied (2) ExpansionBoard1Relay1 (0), } ExpansionBoard1Relay2 (1), MuaIIControlMode ::= ENUMERATE { ExpansionBoard1Relay3 (2), Unoccupied (0), ExpansionBoard1Relay4 (3), RemoteContactOccupied (1), } NormalScheduleOccupied (2), HolidayModeActive (3), MuaIIExRelayGroup2Bits ::= BIT STRING { ScheduleForceOccupied (4), ExpansionBoard2Relay1 (0), ScheduleForceUnoccupied (5), ExpansionBoard2Relay2 (1), CurrentOutputForceMode (6), ExpansionBoard2Relay3 (2), PushButtonOverride (7) ExpansionBoard2Relay4 (3), } }

MuaIIControlStatusBits ::= BIT STRING { MuaIIExRelayGroup3Bits ::= BIT STRING { CoolingDemand (0), ExpansionBoard3Relay1 (0), HeatingDemand (1), ExpansionBoard3Relay2 (1), DehumidificationDemand (2), ExpansionBoard3Relay3 (2), FanInStartUpDelay (3), ExpansionBoard3Relay4 (3), ProofOfFlow (4), } SpaceHumiditySensorInstalled (5), SpaceTemperatureSensorInstalled (6), MuaIIAlarmBits ::= BIT STRING { ExternalHeatConfig (7), BadSupplyAirTemperatureSensor (0), ReheatRelayConfig (8), NoOutdoorAirTemperatureAvailable (1), ModGasIIConnected (9), MissingHumiditySensor (2), ReheatIIConnected (10), FanProvingAlarm (3), } LowSupplyAirTemperature (4), HighSupplyAirTemperature (5), }

8 BACnet® Link Interface Technical Guide

VAV/CAV Instance Number Base VAV/CAV BACnet® Property Identifier The BACnet® Link amends the following property identity to BACnet®’s Instance Number Base For VAV/CAV Controller property identifier. Instance Represented Limits Parameter Number By BACnetPropertyIdentifier : Base Object Alarm Status 17 Analog Input WattBacScheduleState ::= ENUMERATED { CO2 Setpoint 42 Analog Value 0 8000 NormalOperation (0), Configuration 13 Analog Input ForceOccupied (1), Control Mode 11 Analog Input ForceUnoccupied (2) Control Status 12 Analog Input } Control Temperature 19 Analog Input VavCavControlMode ::= ENUMERATE { Cooling Setpoint 1 Analog Input Unoccupied (0), Duct Static Pressure 9 Analog Input RemoteContactOccupied (1), Duct Static Setpoint 38 Analog Value 0.01 3 NormalScheduleOccupied (2), Economizer Position 14 Analog Input PushButtonOrZoneOverride (3), External Relay Group #1 35 Analog Input HolidayModeActive (4), External Relay Group #2 36 Analog Input UnoccupiedZoneDemand (5), External Relay Group #3 37 Analog Input RemoteScheduleOverride (6), Heating Setpoint 2 Analog Input CurrentOutputForceMode (7), Minimum Outside Air 39 Analog Value 1 99 SATHighOrLowCutOff (8), Setpoint CO2OverrideInProgress (9), Occupied Cooling Setpoint 32 Analog Value 0 90 PurgeModeActive (10) Occupied Heating Setpoint 20 Analog Value 0 90 } On Board Relay Group 34 Analog Input Outdoor Air Humidity 10 Analog Input VavCavControlStatusBits ::= BIT STRING { Outdoor Air Sensor Offset 31 Analog Value -10 10 AhuControlEconomizer (0), Outdoor Air Temperature 8 Analog Input NoOutdoorAirTempSensor (1), Outdoor Air Wetbulb 3 Analog Input CarbonDioxiodeSensorPresent (2), Relief Pressure 18 Analog Input HeatCoolStagingDisabled (3), Relief Pressure Setpoint 40 Analog Value -0.3 0.3 DehumidificationMode (4), Return Air CO2 Level 41 Analog Input ModGasIIConnected (5), Return Air Sensor Offset 30 Analog Value -10 10 ReheatIIConnected (6), Return Air Temperature 7 Analog Input } Schedule Force 33 Analog Value 0 2 VavCavConfigurationBits ::= BIT STRING { Space Sensor Offset 28 Analog Value -10 10 CoolingDemand (0), Space Temperature 5 Analog Input HeatingDemand (1), Staging Deadband 23 Analog Value 0 10 CoolingEnabled (2), Supply Air Cooling Setpoint 25 Analog Value 50 70 HeatingEnabled (3), Supply Air Heating Setpoint 26 Analog Value 0 300 EconomizerEnabled (4), Supply Air Sensor Offset 29 Analog Value -10 10 FanInStartUpDelay (5), Supply Air Temperature 6 Analog Input WarmUpModeActive (6), Temperature Demand 4 Analog Input ProofOfFlow (7), Unoccupied Cooling Setpoint 21 Analog Value 0 30 HumidistatContact (8), Unoccupied Heating Setpoint 22 Analog Value -30 0 ProofOfFlowConfig (9), VFD Blower Fan 15 Analog Input ConstantVolumeConfig (10), VFD Exhaust Fan 16 Analog Input HeatWheelConfig (11), Warm Up Setpoint 27 Analog Value 50 90 HumiditySensorConfig (12), Wetbulb Setpoint 24 Analog Value 0 80 WetBulbSensorConfig (13), ReliefPressureConfig (14) Table 4: Instance Number Base Data For VAV/CAV } BACnet® Link Interface 9 Technical Guide Programming - Standard Objects CW/HW Instance Number Base VavCavOnBoardRelayBits ::= BIT STRING { OnBoardRelay1 (0), Instance Number Base For CW/HW Controller OnBoardRelay2 (1), Instance Represented Limits OnBoardRelay3 (2), Parameter Number By OnBoardRelay4 (3), Base Object OnBoardRelqy5 (4), Alarm Status 17 Analog Input } CO2 Setpoint 42 Analog Value 0 8000 Cold Water Position 44 Analog Input VavCavExRelayGroup1Bits ::= BIT STRING { Configuration 13 Analog Input ExpansionBoard1Relay1 (0), Control Mode 11 Analog Input ExpansionBoard1Relay2 (1), Control Status 12 Analog Input ExpansionBoard1Relay3 (2), Control Temperature 19 Analog Input ExpansionBoard1Relay4 (3), Cooling Setpoint 1 Analog Input ExpansionBoard2Relay1 (4), Duct Static Pressure 9 Analog Input ExpansionBoard2Relay2 (5), Duct Static Setpoint 38 Analog Value ExpansionBoard2Relay3 (6), Economizer Position 14 Analog Input ExpansionBoard2Relay4 (7), External Relay Group #1 35 Analog Input } External Relay Group #2 36 Analog Input HCW Configuration 45 Analog Value 0 31 VavCavExRelayGroup2Bits ::= BIT STRING { Heating Setpoint 2 Analog Input ExpansionBoard3Relay1 (0), Hot Water Position 43 Analog Input ExpansionBoard3Relay2 (1), Minimum Outside Air 39 Analog Value 0.01 3 ExpansionBoard3Relay3 (2), Setpoint ExpansionBoard3Relay4 (3), Occupied Cooling Setpoint 32 Analog Value 0 90 } Occupied Heating Setpoint 20 Analog Value 0 90 On Board Relay Group 34 Analog Input VavCavExRelayGroup3Bits ::= BIT STRING { Outdoor Air Humidity 10 Analog Input ExpansionBoard4Relay1 (0), Outdoor Air Sensor Offset 31 Analog Value -10 10 ExpansionBoard4Relay2 (1), Outdoor Air Temperature 8 Analog Input ExpansionBoard4Relay3 (2), Outdoor Air Wetbulb 3 Analog Input ExpansionBoard4Relay4 (3), Relief Pressure 18 Analog Input } Relief Pressure Setpoint 40 Analog Value 1 99 Return Air CO2 Level 41 Analog Input -0.3 0.3 VavCavAlarmBits ::= BIT STRING { Return Air Sensor Offset 30 Analog Value -10 10 BadSpaceTempSensor (0), Return Air Temperature 7 Analog Input FanProvingAlarm (1), Schedule Force 33 Analog Value 0 2 MechanicalCoolingAlarm (2), Space Sensor Offset 28 Analog Value -10 10 MechanicalHeatingAlarm (3), Space Temperature 5 Analog Input DirtyFilterDetected (4), Staging Deadband 23 Analog Value 0 10 HighSpaceTempAlarm (5), Supply Air Cooling Setpoint 25 Analog Value 50 70 LowSpaceTempAlarm (6), Supply Air Heating Setpoint 26 Analog Value 0 300 } Supply Air Sensor Offset 29 Analog Value -10 10 Supply Air Temperature 6 Analog Input Temperature Demand 4 Analog Input Unoccupied Cooling Setpoint 21 Analog Value 0 30 Unoccupied Heating Setpoint 22 Analog Value -30 0 Vfd Blower Fan 15 Analog Input Vfd Exhaust Fan 16 Analog Input Warm Up Setpoint 27 Analog Value 50 90 Wetbulb Setpoint 24 Analog Value 0 80 Table 5: Instance Number Base Data For CW/HW

10 BACnet® Link Interface Technical Guide

CW/HW BACnet® Property Identifier CwHwOnBoardRelayBits ::= BIT STRING { OnBoardRelay1 (0), ® The BACnet Link amends the following property identity to BACnet®’s OnBoardRelay2 (1), property identifier. OnBoardRelay3 (2), BACnetPropertyIdentifier : OnBoardRelay4 (3), WattBacScheduleState ::= ENUMERATED { OnBoardRelqy5 (4), NormalOperation (0), } ForceOccupied (1), CwHwExRelayGroup1Bits ::= BIT STRING { ForceUnoccupied (2) ExpansionBoard1Relay1 (0), } ExpansionBoard1Relay2 (1), CwHwControlMode ::= ENUMERATE { ExpansionBoard1Relay3 (2), Unoccupied (0), ExpansionBoard1Relay4 (3), RemoteContactOccupied (1), ExpansionBoard2Relay1 (4), NormalScheduleOccupied (2), ExpansionBoard2Relay2 (5), PushButtonOrZoneOverride (3), ExpansionBoard2Relay3 (6), HolidayModeActive (4), ExpansionBoard2Relay4 (7), UnoccupiedZoneDemand (5), } RemoteScheduleOverride (6), CwHwExRelayGroup3Bits ::= BIT STRING { CurrentOutputForceMode (7), ExpansionBoard3Relay1 (0), SATHighOrLowCutOff (8), ExpansionBoard3Relay2 (1), CO2OverrideInProgress (9), ExpansionBoard3Relay3 (2), PurgeModeActive (10) ExpansionBoard3Relay4 (3), } } CwHwControlStatusBits ::= BIT STRING { CwHwAlarmBits ::= BIT STRING { AhuControlEconomizer (0), BadSpaceTempSensor (0), NoOutdoorAirTempSensor (1), FanProvingAlarm (1), CarbonDioxiodeSensorPresent (2), MechanicalCoolingAlarm (2), HeatCoolStagingDisabled (3), MechanicalHeatingAlarm (3), DehumidificationMode (4), DirtyFilterDetected (4), ModGasIIConnected (5), HighSpaceTempAlarm (5), ReheatIIConnected (6), LowSpaceTempAlarm (6), } } CwHwConfigurationBits ::= BIT STRING { CwHwConfigBits ::= BIT STRING { CoolingDemand (0), EnableChillerWater (0), HeatingDemand (1), ChillerWaterReverseActing (1), CoolingEnabled (2), EnableHotWater (2), HeatingEnabled (3), HotWaterReverseActing (3), EconomizedEnabled (4), EnableHotWaterOnDehumidification (4), FanInStartUpDelay (5), } WarmUpModeActive (6), ProofOfFlow (7), HumidistatContact (8), ProofOfFlowConfig (9), ConstantVolumeConfig (10), HeatWheelConfig (11), HumiditySensorConfig (12), WetBulbSensorConfig (13), ReliefPressureConfig (14) }

BACnet® Link Interface 11 Technical Guide Programming - Standard Objects Parameter Instance Numbers mation. Be sure to use the BACnet® Link Loop Address not the “MAC” address. Possible valid BACnet® Link Loop Address addresses are 0 Instance Number Calculation through 3. The Instance Number for a controller parameter is determined by using the BACnet® Link Loop Address for the controller, the MUA II, VAV/ Proceed by determining the address switch setting of the controller you CAV or CW/HW controllers address switch setting and the Instance wish to calculate. This is accomplished by verifying the address switch Number Base of the desired Parameter you wish to calculate for that setting for the desired controller. Possible valid controller addresses are controller.. 1 through 32.

In order to calculate the Instance Number for the desired Parameter you Look up the Instance Number Base for the controller and specific pa- must use the WattMaster base address (600191) as a starting point. rameter you desire from the Instance Number Base Table for that controller. See Table 3 through Table 5. Next you must determine the BACnet® Link Loop Address for the controller you wish to calculate. This is determined by looking at the BAC- Use the numbers that you just determined to calculate the Instance Num- net® Link Loop Address switch setting for the loop the desired control- ber for the desired parameter using the formula below. Please see the ler is installed on. See Figure 3 for Loop Address switch setting infor- examples that follow the formula.

Parameter Instance Number Calculation Examples

Controller BACnet Controller Parameter Parameter Instance Number Parameter Type & Link Address Instance Calculation Instance Parameter Loop Number Number Address Base

MUA II 0 1 11 600191 +((0 * 16 + 1-1) * 64) + 11) = 600202 600202 Current Mode

MUA II 3 3 14 600191 + ((3 * 16 + 3-1) * 64) + 14) = 603405 603405 Alarm Status

VAV/CAV 1 14 11 600191 + ((1 * 16 + 14-1) * 64) + 11) = 602058 602058 Control Mode

VAV/CAV 2 15 17 600191 + ((2 * 16 + 15-1) * 64) + 17) = 603125 603125 Alarm Status

Table 6: Parameter Instance Number Calculations

12 BACnet® Link Interface Technical Guide Programming - Proprietary Objects

® BACnet Link Overview Properties For The MUA II Controller The BACnet® Link provides the communications interface between the Property Read ® ® Property Name Property Data Type Identifier Or Orion system and a BACnet network. One BACnet Link can support Write up to sixteen controllers. The BACnet® Link connects to the BACnet® network using Master-Slave/Token Passing (MS/TP) LAN data link Alarm_Status MuaIIAlarmBits 1024 R/O protocol. Complete information regarding the BACnet® Link device Application_Software_Version Unsigned 11 R/O object can be found on pages 3 through 5 of this manual. Control_Status MuaControlBits 1025 R/O Cooling_Deadband Unsigned 1026 R/W The BACnet® Link supports 3 different controller types (objects). These are the Orion MUA II, VAV/CAV and the CW/HW controllers. The Dew_Point_Reset_Limit Unsigned 1029 R/W sections that follow describe the properties for each controller (device Dew_Point_Setpoint Unsigned 1030 R/W object). Enthalpy_Deadband Unsigned 1033 R/W MUA II Object Enthalpy_Unit BACnetEngineeringUnits 1082 R/O External_Heat_Position Real 1035 R/O The information that follows describes the characteristics of the MUA II Object. The properties for the MUA II Object are listed in Table 7. External_Heat_Proportion_Band Unsigned 1034 R/W Heating_Deadband Unsigned 1036 R/W Object Name Humidity_Unit BACnetEngineeringUnits 1084 R/O The Object Name for the MUA II controller is a 15 byte character string Modulate_Gas_Valve_Position Unsigned 1038 R/O that can be set through the BACnet® front end. Object_Identifier BACnetObjectIdentifier 75 R/O Object Type Object_Name CharacterString 77 R/W The Object Type of the MUA II controller is MuaII or 258. Object_Type WattBacObjectTypes 79 R/O Outdoor_Air_Cooling_Setpoint Real 1041 R/O Object Instance Number Outdoor_Air_Dew_Point Real 1045 R/O The Instance Number of the MUA II Object is determined by two vari- Outdoor_Air_Dew_Point_Setpoint Real 1046 R/O able values. The first variable is the loop address setting on the BAC- Outdoor_Air_Enthalpy Real 1047 R/O net® Link for the specific loop the MUA II controller resides on and the second is the MUA II controller address. The BACnet® Link loop ad- Outdoor_Air_Enthalpy_Deadband Real 1049 R/O dress can be either 0, 1, 2 or 3. See Figure 3 at the front of this manual Outdoor_Air_Enthalpy_Setpoint Real 1048 R/O for detailed information on the BACnet® Link loop address jumper set- Outdoor_Air_Heating_Setpoint Real 1042 R/O tings. Outdoor_Air_Humidity Real 1050 R/O The second variable value used to calculate the Object Instance number Outdoor_Air_Temperature Real 1052 R/O is the MUA II controller address and is determined by the address switch Position_Unit BACnetEngineeringUnits 1085 R/O settings on the MUA II controller. Valid address settings are 1 through 16. Reheat_Value_Position Unsigned 1054 R/O Relays MuaIIRelayBits 1055 R/O See Table 10 at the end of this chapter for complete Object Instance Schedule_Force WattBacScheduleState 1059 R/W Number calculation information Space_Humidity Real 1060 R/O Object Properties Space_Humidity_At_Max_Supply Unsigned 1061 R/W The information and tables that follow detail the properties and prop- Space_Humidity_At_Min_Supply Unsigned 1062 R/W erty identifiers for the MUA II Object. Space_Temperature Real 1064 R/O Space_Temperature_At_Max_Supply Unsigned 1065 R/W Space_Temperature_At_Min_Supply Unsigned 1066 R/W Supply_Air_Reset_Limit Unsigned 1070 R/W Supply_Air_Setpoint Unsigned 1072 R/W Supply_Air_Setpoint_Mirror Real 1081 R/O Supply_Air_Temerature Real 1073 R/O Temperature_Unit BACnetEngineeringUnits 1086 R/O

Table 7: MUA II Object Properties

BACnet® Link Interface 13 Technical Guide Programming - Proprietary Objects MUA II Property Identifier MuaIIRelayBits ::= BIT STRING { OnBoardRelay1 (0), BacnetOrionInterface device amends the following property identity to OnBoardRelay2 (1), BACnet®’s property identifier BACnetPropertyIdentifier: OnBoardRelay3 (2), WattBacScheduleState ::= ENUMERATED { OnBoardRelay4 (3), NormalOperation (0), OnBoardRelqy5 (4), ForceOccupied (1), ExpansionBoard1Relay1 (8), ForceUnoccupied (2) ExpansionBoard1Relay2 (9), } ExpansionBoard1Relay3 (10), ExpansionBoard1Relay4 (11), MuaIIControlMode ::= ENUMERATE { ExpansionBoard2Relay1 (16), Unoccupied (0), ExpansionBoard2Relay2 (17), RemoteContactOccupied (1), ExpansionBoard2Relay3 (18), NormalScheduleOccupied (2), ExpansionBoard2Relay4 (19), HolidayModeActive (3), ExpansionBoard3Relay1 (24), ScheduleForceOccupied (4), ExpansionBoard3Relay2 (25), ScheduleForceUnoccupied (5), ExpansionBoard3Relay3 (26), CurrentOutputForceMode (6), ExpansionBoard3Relay4 (27), PushButtonOverride (7) }

MuaIIControlBits ::= BIT STRING { MuaIIAlarmBits ::= BIT STRING { MuaIIControlModeBit0 (0), BadSupplyAirTemperatureSensor (0), MuaControlModeBit0 (1), NoOutdoorAirTemperatureAvailable (1), MuaControlModeBit0 (2), MissingHumiditySensor (2), CoolingDemand (3), FanProvingAlarm (3), HeatingDemand (4), LowSupplyAirTemperature (4), DehumidificationDemand (5), HighSupplyAirTemperature (5), FanInStartUpDelay (6), } ProofOfFlow (7), SpaceHumiditySensorInstalled (8), SpaceTemperatureSensorInstalled (9), ExternalHeatConfig (10), ReheatRelayConfig (11), ModGasIIConnected (12), ReheatIIConnected (13), }

14 BACnet® Link Interface Technical Guide

VAV/CAV Object Object Properties For The VAV/CAV Controller The information that follows describes the characteristics of the VAV/ Property Read CAV Object. The properties for the VAV/CAV Object are listed in Table Property Name Property Data Type Identifier Or Wr ite 8. Alarm_Status VavAlarmBits 1024 R/O Object Name Application_Software_Version Unsigned 11 R/O The Object Name for the VAV/CAV controller is a 15 byte character CO2_Setpoint Real 1094 R/O string that can be set through the BACnet® front end. Control_Status VavControlBits 1025 R/O Control_Temperature Real 1028 R/O Object Type Cooling_Setpoint Real 1027 R/O The Object Type of the VAV/CAV controller is VavCav or 257. Duct_Static_Pressure Real 1090 R/O Duct_Static_Setpoint Real 1031 R/W Object Instance Number Economizer_Position Real 1032 R/O Fan_Speed_Unit BACnetEngineeringUnits 1083 R/O The Instance Number of the VAV/CAV Object is determined by two Heating_Setpoint Real 1037 R/O variable values. The first variable is the loop address setting on the BACnet® Link for the specific loop the VAV/CAV controller resides on Humidity_Unit BACnetEngineeringUnits 1084 R/O and the second is the VAV/CAV controller address. The BACnet® Link Min_Outside_Air_Setpoint Real 1091 R/W loop address can be either 0, 1, 2 or 3. See Figure 3 at the front of this Object_Identifier BACnetObjectIdentifier 75 R/O manual for detailed information on the BACnet® Link loop address Object_Name CharacterString 77 R/W jumper settings. Object_Type WattBacObjectTypes 79 R/O The second variable value used to calculate the Object Instance number Occupied_Cooling_Setpoint Unsigned 1039 R/W is the VAV/CAV controller address and is determined by the address Occupied_Heating_Setpoint Unsigned 1040 R/W switch settings on the VAV/CAV controller. Valid address settings are 1 Outdoor_Air_Humidity Real 1050 R/O through 16. Outdoor_Air_Sensor_Offset Real 1051 R/W Outdoor_Air_Temperature Real 1052 R/O See Table 10 at the end of this chapter for complete Object Instance Number calculation information Outdoor_Air_Wetbulb Real 1053 R/O Position_Unit BACnetEngineeringUnits 1085 R/O Object Properties Relays VavRelayBits 1055 R/O The information and tables that follow detail the properties and prop- Relief_Pressure Real 1056 R/O erty identifiers for the VAV/CAV Object. Relief_Pressure_Setpoint Real 1092 R/W Return_Air_CO2_Level Real 1093 R/O Return_Air_Sensor_Offset Real 1058 R/W Return_Air_Temperature Real 1057 R/O Schedule_Force WattBacScheduleState 1059 R/W Space_Sensor_Offset Real 1063 R/W Space_Temperature Real 1064 R/O Staging_Deadband Integer 1067 R/W Supply_Air_Cooling_Setpoint Unsigned 1068 R/W Supply_Air_Heating_Setpoint Unsigned 1069 R/W Supply_Air_Sensor_Offset Real 1071 R/W Supply_Air_Temperature Real 1073 R/O Temperature_Demand Real 1074 R/O Temperature_Unit BACnetEngineeringUnits 1086 R/O Unoccupied_Coolting_Setpoint Unsigned 1075 R/W Unoccupied_Heating_Setpoint Unsigned 1076 R/W Vfd_Blower_Fan Real 1077 R/O Vfd_Exhaust_Fan Real 1078 R/O Warm_Up_Setpoint Unsigned 1079 R/W Wetbulb_Setpoint Unsigned 1080 R/W

Table 8: VAV/CAV Object Properties

BACnet® Link Interface 15 Technical Guide Programming - Proprietary Objects VAV/CAV Property Identifier VavCavRelayBits ::= BIT STRING { OnBoardRelay1 (0), BacnetOrionInterface device amends the following property identity to OnBoardRelay2 (1), BACnet®’s property identifier BACnetPropertyIdentifier: OnBoardRelay3 (2), WattBacScheduleState ::= ENUMERATED { OnBoardRelay4 (3), NormalOperation (0), OnBoardRelqy5 (4), ForceOccupied (1), ExpansionBoard1Relay1 (8), ForceUnoccupied (2) ExpansionBoard1Relay2 (9), } ExpansionBoard1Relay3 (10), ExpansionBoard1Relay4 (11), VavCavControlMode ::= ENUMERATE { ExpansionBoard2Relay1 (12), Unoccupied (0), ExpansionBoard2Relay2 (13), RemoteContactOccupied (1), ExpansionBoard2Relay3 (14), NormalScheduleOccupied (2), ExpansionBoard2Relay4 (15), PushButtonOrZoneOverride (3), ExpansionBoard3Relay1 (16), HolidayModeActive (4), ExpansionBoard3Relay2 (17), UnoccupiedZoneDemand (5), ExpansionBoard3Relay3 (18), RemoteScheduleOverride (6), ExpansionBoard3Relay4 (19), CurrentOutputForceMode (7), ExpansionBoard4Relay1 (24), SATHighOrLowCutOff (8), ExpansionBoard4Relay2 (25), CO2OverrideInProgress (9), ExpansionBoard4Relay3 (26), PurgeModeActive (10) ExpansionBoard4Relay4 (27), } }

VavCavControlBits ::= BIT STRING { VavCavAlarmBits::= BIT STRING { VavControlModeBit0 (0), BadSpaceTempSensor (0), VavControlModeBit0 (1), FanProvingAlarm (1), VavControlModeBit0 (2), MechanicalCoolingAlarm (2), VavControlModeBit0 (3), MechanicalHeatingAlarm (3), AhuControlEconomizer (4), DirtyFilterDetected (4), NoOutdoorAirTempSensor (6), HighSpaceTempAlarm (5), CarbonDioxiodeSensorPresent (7), LowSpaceTempAlarm (6), HeatCoolStagingDisabled (11), } DehumidificationMode (12), ModGasIIConnected (13), ReheatIIConnected (14), CoolingDemand (16), HeatingDemand (17), CoolingEnabled (18), HeatingEnabled (19), EconomizedEnabled (20), FanInStartUpDelay (21), WarmUpModeActive (22), ProofOfFlow (23), HumidistatContact (24), ProofOfFlowConfig (25), ConstantVolumeConfig (26), HeatWheelConfig (27), HumiditySensorConfig (28), WetBulbSensorConfig (29), ReliefPressureConfig (30) }

16 BACnet® Link Interface Technical Guide

CW/HW Object Object Properties For The CW/HW Controller Property Read The information that follows describes the characteristics of the CW/ Property Name Property Data Type Identifier Or HW Object. Properties for the CW/HW Object are listed in Table 9. Write Alarm_Status CwHwAlarmBits 1024 R/O Object Name Applilcation_Software_Version Unsigned 11 R/O The Object Name for the CW/HW controller is a 15 byte character CO2_Setpoint Real 1094 R/O string that can be set through the BACnet® front end. Cold_Water_Position Real 1088 R/O Control_Status CwHwControlBits 1025 R/O Object Type Control_Temperature Real 1028 R/O Cooling_Setpoint Real 1027 R/O The Object Type of the CW/HW controller is CwHw or 259. Duct_Static_Pressure Real 1031 R/O Duct_Static_Setpoint Real 1090 R/W Object Instance Number Economizer_Position Real 1032 R/O The Instance Number of the CW/HW Object is determined by two vari- Fan_Speed_Unit BACnetEngineeringUnits 1083 R/O Hcw_Configuration HcwConfigBits 1089 R./W able values. The first variable is the loop address setting on the BAC- Heating_Setpoint Real 1037 R/O net® Link for the specific loop the CW/HW controller resides on and Hot_Water_Position Real 1087 R/O the second is the CW/HW controller address. The BACnet® Link loop Humidity_Unit BACnetEngineeringUnits 1084 R/O address can be either 0, 1, 2 or 3. See Figure 3 at the front of this Min_Outside_Air_Setpoint Real 1091 R/W ® manual for detailed information on the BACnet Link loop address Object_Identifier BACnetObjectIdentifier 75 R/O jumper settings. Object_Name CharacterString 77 R/W Object_Type WattBacObjectTypes 79 R/O The second variable value used to calculate the Object Instance number Occupied_Cooling_Setpoint Unsigned 1039 R/W is the CW/HW controller address and is determined by the address switch Occupied_Heating_Setpoint Unsigned 1040 R/W settings on the CW/HW controller. Valid address settings are 1 through Outdoor_Air_Humidity Real 1050 R/O 16. Outdoor_Air_Sensor_Offset Real 1051 R/W Outdoor_Air_Temperature Real 1052 R/O See Table 10 at the end of this chapter for complete Object Instance Outdoor_Air_Wetbulb Real 1053 R/O Number calculation information Position_Unit BACnetEngineeringUnits 1085 R/O Relays CwHwRelayBits 1055 R/O Object Properties Relief_Pressure Real 1056 R/O Relief_Pressure_Setpoint Real 1092 R/W The information and tables that follow detail the properties and prop- Return_Air_CO2_Level Real 1093 R/O erty identifiers for the CW/HW Object. Return_Air_Sensor_Offset Real 1058 R/W Return_Air_Temperature Real 1057 R/O Schedule_Force WattBacScheduleState 1059 R/W Space_Sensor_Offset Real 1063 R/W Space_Temperature Real 1064 R/O Staging_Deadband Integer 1067 R/W Supply_Air_Cooling_Setpoint Unsigned 1068 R/W Supply_Air_Heating_Setpoint Unsigned 1069 R/W Supply_Air_Sensor_Offset Real 1071 R/W Supply_Air_Temperature Real 1073 R/O Temperature_Demand Real 1074 R/O Temperature_Unit BACnetEngineeringUnits 1086 R/O Unoccupied_Coolting_Setpoint Unsigned 1075 R/W Unoccupied_Heating_Setpoint Unsigned 1076 R/W Vfd_Blower_Fan Real 1077 R/O Vfd_Exhaust_Fan Real 1078 R/O Warm_Up_Setpoint Unsigned 1079 R/W Wetbulb_Setpoint Unsigned 1080 R/W

Table 9: CW/HW Object Properties

BACnet® Link Interface 17 Technical Guide Programming- Proprietary Objects CW/HW Property Identifier CwHwRelayBits := BIT STRING { OnBoardRelay1 (0), BacnetOrionInterface device amends the following property identity to OnBoardRelay2 (1), BACnet®’s property identifier BACnetPropertyIdentifier: OnBoardRelay3 (2), OnBoardRelay4 (3), WattBacScheduleState ::= ENUMERATED { OnBoardRelqy5 (4), NormalOperation (0), ExpansionBoard1Relay1 (8), ForceOccupied (1), ExpansionBoard1Relay2 (9), ForceUnoccupied (2) ExpansionBoard1Relay3 (10), } ExpansionBoard1Relay4 (11), CwHwControlMode ::= ENUMERATE { ExpansionBoard2Relay1 (12), Unoccupied (0), ExpansionBoard2Relay2 (13), RemoteContactOccupied (1), ExpansionBoard2Relay3 (14), NormalScheduleOccupied (2), ExpansionBoard2Relay4 (15), PushButtonOrZoneOverride (3), ExpansionBoard3Relay1 (16), HolidayModeActive (4), ExpansionBoard3Relay2 (17), UnoccupiedZoneDemand (5), ExpansionBoard3Relay3 (18), RemoteScheduleOverride (6), ExpansionBoard3Relay4 (19), CurrentOutputForceMode (7), ExpansionBoard4Relay1 (24), SATHighOrLowCutOff (8), ExpansionBoard4Relay2 (25), CO2OverrideInProgress (9), ExpansionBoard4Relay3 (26), PurgeModeActive (10) ExpansionBoard4Relay4 (27), } }

CwHwControlBits ::= BIT STRING { CwHwAlarmBits ::= BIT STRING { VavControlModeBit0 (0), BadSpaceTempSensor (0), VavControlModeBit0 (1), FanProvingAlarm (1), VavControlModeBit0 (2), MechanicalCoolingAlarm (2), VavControlModeBit0 (3), MechanicalHeatingAlarm (3), AhuControlEconomizer (4), DirtyFilterDetected (4), NoOutdoorAirTempSensor (6), HighSpaceTempAlarm (5), CarbonDioxiodeSensorPresent (7), LowSpaceTempAlarm (6), HeatCoolStagingDisabled (11), } DehumidificationMode (12), CwHwConfigBits ::= BIT STRING { ModGasIIConnected (13), EnableChillerWater (0), ReheatIIConnected (14), ChillerWaterReverseActing (1), CoolingDemand (16), EnableHotWater (2), HeatingDemand (17), HotWaterReverseActing (3), CoolingEnabled (18), EnableHotWaterOnDehumidification (4), HeatingEnabled (19), } EconomizedEnabled (20), FanInStartUpDelay (21), WarmUpModeActive (22), ProofOfFlow (23), HumidistatContact (24), ProofOfFlowConfig (25), ConstantVolumnConfig (26), HeatWheelConfig (27), HumiditySensorConfig (28), WetBulbSensorConfig (29), ReliefPressureConfig (30) } 18 BACnet® Link Interface Technical Guide

Proprietary Object Instance Numbers “MAC” address. Possible valid BACnet® Link Loop Address addresses are 0 through 3. Instance Number Calculation The Instance Number for a Proprietary Object is determined by using Proceed by determining the address switch setting of the controller you the BACnet® Link Loop Address for the controller and the MUA II, wish to calculate. This is accomplished by verifying the address switch VAV/CAV or CW/HW controllers address switch setting. setting for the desired controller. Possible valid controller addresses are 1 through 16. In order to calculate the Instance Number for the Proprietary Object you must use the WattMaster base address (600191) as a starting point. Use the numbers that you just determined to calculate the Instance Num- ber for the Proprietary Object using the formula below. Please see the Next you must determine the BACnet® Link Loop Address for the con- examples that follow the formula. troller you wish to calculate. This is determined by looking at the BACnet® Link Loop Address switch setting for the loop the desired controller is installed on. See Figure 3 for Loop Address switch setting information. Be sure to use the BACnet® Link Loop Address not the

Proprietary Object Instance Number Calculation Examples

Controller BACnet Link Controller Proprietary Object Proprietary Object Type Loop Address Instance Number Instance Number Address Calculation

MUA II 0 1 600191 + (0 * 16) + 1 = 600192 600192

CW/HW 3 4 600191 + (3 * 16) + 4 = 600243 600243

VAV/CAV 1 12 600191 + (1* 16) + 12 = 600219 600219

MUA II 2 7 600191 + (2* 16) + 7 = 600230 600230

Table 10: Proprietary Instance Number Calculation Examples

BACnet® Link Interface 19 Technical Guide Appendix 1 BACnet® Link Protocol Implementation Standard Object Details Conformance Statement BACnet® Link has the following properties available. BACnet® Link Basic Information BACnet® Link Object Properties BACnet® Link is a device which provides an interface between the WattMaster Controls Orion System and the BACnet® network. One Property Read or Limits, Value, Comment Write BACnet® Link can connect up to sixteen Orion VAV/CAV, MUA II or CW/HW controllers. The BACnet® Link connects to the BACnet® net- APDU Timeout R/O work through MS/TP as data link/physical layer. Application Software R/O Version Data Base Revision R/O BACnet® Interoperability Building Blocks Description R/W 15 ® ® BACnet Link supports the following BACnet interoperability Build- Firmware Revision R/O ing Blocks Local Date R/W Software Timer • Data Sharing-ReadProperty-B (DS-RP-B) Local Time R/W Software Timer Tested with Cimetric’s BACnet® Explorer Location R/W 15 Max APDU Length R/O 204 • Data Sharing-ReadPropertyMultiple-B (DS-RPM-B) Accepted Not tested Max Info Frames R/O • Data Sharing-WriteProperty-B (DS-WP-B) Max Master R/O Model Name R/O Tested with Cimetric’s BACnet® Explorer Number Of APDU R/O Retried BACnet® Device Profile Object Identifier R/O 600192 Plus Switch BACnet® Link conforms to the following device profile. Object List R/O Object Name R/W 15 Object Type R/O 8 • BACnet® Application Specific Controller (B-ASC) Protocol Conformance R/O 2 ® Tested with Cimetric’s BACnet Explorer Class Protocol Object Types R/O Non Standard Application Services Supported BACnet® Link does not support any non-standard application services.. Protocol Services R/O Supported Protocol Version R/O BACnet® Link Objects Segmentation R/O No BACnet® Link provides the following objects. Supported System Status R/O • Standard Objects Vendor Identifier R/O Vendor Name R/O WattMaster • Device object • Analog Input object Table 11: BACnet® Link Device Object Properties • Analog Value object • Proprietary object • VAV/CAV object • MUA II object • CW/HW object

20 BACnet® Link Interface Technical Guide

Proprietary Object Details Analog Value Object Properties BACnet® Link has the following proprietary object properties avail- Property Read or Limits, Value, Comment able. Write Event State R/O Not Implemented MUA II Object Properties Object Identifier R/O Object Name R/W 15 Property Read Limits, Value, Object Type R/O 2 or Comment Out of Service R/O Not Implemented Write Present Value R/O Alarm Status R/O Status Flags R/W Not Implemented Application Software Version R/O Units R/O Control Status R/O Cooling Deadband R/W 2 20 Table 12: Analog Value Object Properties Dew Point Reset Limit R/W Dew Point Setpoint R/W 40 80 Enthalpy Deadband R/W 3 20 Enthalpy Unit R/O 24 External Heat Position R/O Analog Input Object Properties External Heat Proportion Band R/W 1 30 Property Read or Limits, Value, Comment Heating Deadband R/W 2 20 Write Humidity Unit R/O 29 Event State R/O Not Implemented Modulate Gas Valve Position R/O Object Identifier R/O Object Identifier R/O Object Name R/W 15 Object Name R/W 15 Object Type R/O 0 Object Type R/O 258 Out of Service R/O Not Implemented Outdoor Air Cooling Setpoint R/O Present Value R/O Outdoor Air Dew Point R/O Status Flags R/W Not Implemented Outdoor Air Dew Point Setpoint R/O Units R/O Outdoor Air Enthalpy R/O Outdoor Air Enthalpy Deadband R/O Table 13: Analog Input Object Properties Outdoor Air Enthalpy Setpoint R/O Outdoor Air Heating Setpoint R/O Outdoor Air Humidity R/O Outdoor Air Temperature R/O Position Unit R/O 98 Reheat Value Position R/O Relays R/O Schedule Force R/W 0 2 Space Humidity R/O Space Humidity At Max Supply R/W 0 100 Space Humidity At Min Supply R/W 0 100 Space Temperature R/O Space Temperature At Max Supply R/W 40 100 Space Temperature At Min Supply R/W 40 100 Supply Air Reset Limit R/W Supply Air Setpoint R/W 50 90 Supply Air Setpoint Mirror R/O Supply Air Temperature R/O Temperature Unit R/O 64

Table 14: MUA II Object Properties

BACnet® Link Interface 21 Technical Guide Appendix 1

VAV/CAV Object Properties CW/HW Object Properties Property Read Limits, Value, Property Read Limits, Value, or Comment or Comment Write Write Alarm Status R/O Alarm Status R/O Application Software Version R/O Application Software Version R/O CO2 Setpoint R/O 0 8000 CO2 Setpoint R/W 0 8000 Control Status R/O Cold Water Position R/O Control Temperature R/O Control Status R/O Cooling Setpoint R/O Control Temperature R/O Duct Static Pressure R/O Cooling Setpoint R/O Duct Static Setpoint R/W 0.01 3 Duct Static Pressure R/O Economizer Position R/O Duct Static Setpoint R/W 0.01 3 Fan Speed Unit R/O 98 Economizer Position R/O Fan Speed Unit R/O 98 Heating Setpoint R/O HCW Configuration R/W Humidity Unit R/O 29 Heating Setpoint R/O Min Outside Air Setpoint R/W 1 99 Hot Water Position R/O Object Identifier R/O Humidity Unit R/O 29 Object Name R/W 15 Min Outside Air Setpoint R/W 1 99 Object Type R/O 257 Object Identifier R/O Occupied Cooling Setpoint R/W 0 90 Object Name R/W 15 Occupied Heating Setpoint R/W 0 90 Object Type R/O 259 Outdoor Air Humidity R/O Occupied Cooling Setpoint R/W 0 90 Outdoor Air Sensor Offset R/W -10 10 Occupied Heating Setpoint R/W 0 90 Outdoor Air Temperature R/O Outdoor Air Humidity R/O Outdoor Air Wetbulb R/O Outdoor Air Sensor Offset R/W -10 10 Position Unit R/O 98 Outdoor Air Temperature R/O Relays R/O Outdoor Air Wetbulb R/O Relief Pressure R/O Position Unit R/O 98 Relief Pressure Setpoint R/W -0.3 0.3 Relays R/O Return Air CO2 Level R/O Relief Pressure R/O Return Air Sensor Offset R/W -10 10 Relief Pressure Setpoint R/W -0.3 0.3 Return Air Temperature R/O Return Air CO2 Level R/O Schedule Force R/W 0 2 Return Air Sensor Offset R/W -10 10 Space Sensor Offset R/W -10 10 Return Air Temperature R/O Space Temperature R/O Schedule Force R/W 0 2 Stagint Deadband R/W 0 10 Space Sensor Offset R/W -10 10 Supply Air Cooling Setpoint R/W 50 70 Space Temperature R/O Supply Air Heating Setpoint R/W 0 300 Stagint Deadband R/W 0 10 Supply Air Sensor Offset R/W -10 10 Supply Air Cooling Setpoint R/W 50 70 Supply Air Temperature R/O Supply Air Heating Setpoint R/W 0 300 Temperature Demand R/O Supply Air Sensor Offset R/W -10 10 Temperature Unit R/O 64 Supply Air Temperature R/O Unoccupied Cooling Setpoint R/W 0 30 Temperature Demand R/O Unoccupied Heating Setpoint R/W -30 0 Temperature Unit R/O 64 VFD Blower Fan R/O Unoccupied Cooling Setpoint R/W 0 30 VFD Exhaust Fan R/O Unoccupied Heating Setpoint R/W -30 0 Warm Up Setpoint R/W 50 90 Vfd Blower Fan R/O Wetbulb Setpoint R/W 0 80 Vfd Exhaust Fan R/O Warm Up Setpoint R/W 50 90 Table 15: VAV/CAV Object Properties Wetbulb Setpoint R/W 0 80 Table 16: CW/HW Object Properties

22 BACnet® Link Interface Technical Guide

List Of All Property Identifiers For Proprietary Objects List Of All Property Identifiers For Proprietary Objects Property Property Name Read Or Write Property Property Name Read Or Write Identifier Identifier 1024 Alarm_Status R/O 1060 Space_Humidity R/O 1025 Control_Status R/O 1061 Space_Humidity_At_Max_Supply R/W 1026 Cooling_Deadband R/W 1062 Space_Humidity_At_Min_Supply R/W 1027 Cooling_Setpoint R/O 1063 Space_Sensor_Offset R/W 1028 Control_Temperature R/O 1064 Space_Temperature R/O 1029 Dew_Point_Reset_Limit R/W 1065 Space_Temperature_At_Max_Supply R/W 1030 Dew_Point_Setpoint R/W 1066 Space_Temperature_At_Min_Supply R/W 1031 Duct_Static_Setpoint R/W 1067 Staging_Deadband R/W 1032 Economizer_Position R/O 1068 Supply_Air_Cooling_Setpoint R/W 1033 Enthalpy_Deadband R/W 1069 Supply_Air_Heating_Setpoint R/W 1034 External_Heat_Proportion_Band R/W 1070 Supply_Air_Reset_Limit R/W 1035 External_Heat_Position R/O 1071 Supply_Air_Sensor_Offset R/W 1036 Heating_Deadband R/W 1072 Supply_Air_Setpoint R/W 1037 Heating_Setpoint R/O 1073 Supply_Air_Temerature R/O 1038 Modulate_Gas_Valve_Position R/O 1074 Temperature_Demand R/O 1039 Occupied_Cooling_Setpoint R/W 1075 Unoccupied_Coolting_Setpoint R/W 1040 Occupied_Heating_Setpoint R/W 1076 Unoccupied_Heating_Setpoint R/W 1041 Outdoor_Air_Cooling_Setpoint R/O 1077 Vfd_Blower_Fan R/O 1042 Outdoor_Air_Heating_Setpoint R/O 1078 Vfd_Exhaust_Fan R/O 1043 Not Used ----- 1079 Warm_Up_Setpoint R/W 1044 Not Used ----- 1080 Wetbulb_Setpoint R/W 1045 Outdoor_Air_Dew_Point R/O 1081 Supply_Air_Setpoint_Mirror R/O 1046 Outdoor_Air_Dew_Point_Setpoint R/O 1082 Enthalpy_Unit R/O 1047 Outdoor_Air_Enthalpy R/O 1083 Fan_Speed_Unit R/O 1048 Outdoor_Air_Enthalpy_Setpoint R/O 1084 Humidity_Unit R/O 1049 Outdoor_Air_Enthalpy_Deadband R/O 1085 Position_Unit R/O 1050 Outdoor_Air_Humidity R/O 1086 Temperature_Unit R/O 1051 Outdoor_Air_Sensor_Offset R/W 1087 Hot_Water_Position R/O 1052 Outdoor_Air_Temperature R/O 1088 Cold_Water_Position R/O 1053 Outdoor_Air_Wetbulb R/O 1089 Hcw_Configuration R./W 1054 Reheat_Value_Position R/O 1090 Duct_Static_Pressure R/O 1055 Relays R/O 1091 Min_Outside_Air_Setpoint R/W 1056 Relief_Pressure R/O 1092 Relief_Pressure_Setpoint R/W 1057 Return_Air_Temperature R/O 1093 Return_Air_CO2_Level R/O 1058 Return_Air_Sensor_Offset R/W 1094 CO2_Setpoint R/O 1059 Schedule_Force R/W

Table 17: List Of All Property Identifiers

BACnet® Services BACnet® Data Link Layer Objects cannot be dynamically created or deleted by using BACnet® BACnet® Link supports the following data link layer. ® Services with the BACnet Link . • Master-Slave/Token Passing (MS/TP) LAN Data Link Protocol ® BACnet Segmented Requests • Tested with Allertons BACtalk® Router 200 BACnet® Link does not support segmented requests.

BACnet® Segmented Responses BACnet® Link does not support segmented responses. BACnet® Link Interface 23 Form: OR-BACNET-TGD-02B Printed in the USA August 2005 All rights reserved Copyright 2005 WattMaster Controls Inc. • 8500 NW River Park Drive • Parkville, Mo. • 64152 Phone (816) 505-1100 www.orioncontrols.com Fax (816) 505-1101