com
Table Of Contents
General Information......................................................................................................................................... 3 Data Sharing ................................................................................................................................................................................3 Scheduling....................................................................................................................................................................................3 Hardware Specications ..............................................................................................................................................................3 Connection and Wiring Information ................................................................................................................ 4 Conguring the PT-Link Controller .................................................................................................................. 5 PT-Link Hardware Connection .....................................................................................................................................................5 Computer IP Address Set-up for Windows 98, NT, and XP..........................................................................................................5 Connecting to the PT-Link ............................................................................................................................................................7 Making Changes to the Conguration File (cong.csv) ................................................................................................................7 Uploading Cong.csv from the PT-Link ........................................................................................................................................7 Modifying Cong.csv ....................................................................................................................................................................8 Downloading Cong.csv to the PT-Link......................................................................................................................................10 Addressing WattMaster Devices in a BACnet Network. ........................................................................................................... 11 PT-Link Board LEDs ................................................................................................................................................................... 11 ProtoCessor Module LEDs .........................................................................................................................................................12 Using RUINET ............................................................................................................................................................................13 Verifying Proper Communications ..............................................................................................................................................13 Verifying Proper Values ..............................................................................................................................................................13 Data Arrays .................................................................................................................................................... 14 Table 2: MUA II Data Array For Field Server ..............................................................................................................................14 Table 3: VAV/CAV Data Array For Field Server ..........................................................................................................................14 Table 4: VCM Data Array For Field Server .................................................................................................................................15 Appendix A ..................................................................................................................................................... 16 Figure 23: RJ-45 8P8C Cable for WattMaster Cross Over Networking - WattMaster Part #HZ000136.....................................16 Appendix B ..................................................................................................................................................... 17 ProtoCessor Driver - (PICS) BACnet Protocol Implementation Conformance Statement..........................................................17 Appendix C - VCM BACnet Parameters ......................................................................................................... 18 VCM PT-Link-BACnet Property Identier:.................................................................................................................................22 Appendix D - MUA II BACnet Parameters...................................................................................................... 24 MUA II PT-Link-BACnet Property Identier ...............................................................................................................................26 Appendix E - VAV/CAV BACnet Parameters .................................................................................................. 28 VAV/CAV PT-Link-BACnet Property Identier ...........................................................................................................................31
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: mail@wattmaster.com Visit our web site at www.orioncontrols.com Form: OR-PTBACNET-TGD-01F Copyright 2007 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.
General Information
The OE368-22-BACNET, PT-Link-BACnet provides bi-directional communication between your BACnet protocol network and up to four of any of the following types of Orion controllersMUA II, VAV/CAV or VCM: MUA II Controller (Y200405) VAV/CAV Controller (Y200301) VCM Controller (SS1016, Y200409, Y200616) NOTE: The PT-Link-BACnet device can be used to connect to only four Orion controllers. If more than four Orion controllers are present in a system, you will need one or more additional PT-Link-BACnet devices for integration with a BACnet protocol network. To determine what controller you have, you must look at the label located on the controller EPROM. If the controller label does not match any of the SS or Y numbers listed above, your controller will not work with the PT-Link-BACnet.
Scheduling
Ability to allow BACnet devices to send Schedule events to the Orion controller side of the gateway by using standard BACnet services.
Hardware Specications
Table 1 contains the hardware specications for the PT-Link-BACnet interface.
Technical Data
BACnet-Mstp Loop 9600, 19200, 38400, 76800 Mbps Controller Loop RS-485, 9600 Baud Rate Network Protocol Protocol (WattMaster Loop) Power Input Voltage Power Consumption Operating Temp Operating Humidity Weight BACnet HSI Open Protocol Token Passing 24 VAC 10 VA Maximum 10F to 149F 90% RH Non-Condensing 8 oz.
Data Sharing
The PT-Link-BACnet interface provides the following data sharing capabilities:
Provides values from points on the Orion side of the gateway to BACnet devices as if the values were originating from BACnet objects. Allows BACnet devices to modify point values on the Orion controller side of the PT-Link-BACnet by using standard BACnet write services.
0.20 Dia. Mounting Hole Typ. 4 PL. EEPROM Chip Mounting Backplate
EEPROM U1 C2 EPROM
RAM
SERIAL #
C1
PROTOCESSOR
LOCAL C7 C8 U6 C10
R
U4
SH T
U5 L1 C14 U7 TB1
11.0592 C12
BACnet
TB3
Protocessor Module
U12 C9
LED2 LED1 LOOP PWR
Diagnostic LED #2
BACnet
Communications Wiring Terminal
Diagnostic LED #1
7.00" 7.50"
0.25
PT-Link Interface
4.00
4.50"
0.25
C5 C6 485 DRIVER
C4 U8
R3
X1
TRANSLATOR MODULE
RN1
R4
SF000103
PAL
U10
R9 R8 R7 R6
U11
D3 R23 C18
T SHLD R
Caution: The BACnet Communication Terminal Block Must Be Disconnected Before Connecting The Modular Service Tool. After Programming The Controller(s), Disconnect The Service Tool and Then Reconnect The Communication Terminal Block. Note: All Programming Of Controllers Must Be Done Using The Modular Service Tool. The Modular System Manager Should Not Be Used On A System That Has A PT-Link Installed.
Typical Terminal Blocks. All Wiring To Be T To T, SHLD (G) To SHLD (G) & R To R
Mode Selection
UP
STATUS
PREV
NEXT
ALARMS
1 4 7
DEC
2 5 8 0
3 6 9
MINUS
CONFIGURATION
BALANCE - TEST
ON
Wiring Notes: 1.) All wiring to be in accordance with local and national electrical codes and specifications. 2.) All communication wiring to be 18 gauge minimum, 2 conductor twisted pair with shield. Use Belden #82760 or equivalent.
PT-Link Interface
Locate a CAT5 cable and plug one end into your computers Ethernet port (use a crossover cable if connecting directly to the PT-Link). If connecting directly, plug the other end of the Cable into the Ethernet port on the PT-Link. If connecting through an Ethernet Hub, plug the other end of the PC cable into the hub, and use a second CAT5 cable to connect the PT-Link to the hub as well. Power up the PT-Link by plugging in the power cable. The PT-Link may take up to three minutes to power up completely. Once the PT-Link is powered up, you should notice that the green GPI05 LED light on the ProtoCessor Board remains on continuously. See Figure 19 for a diagram showing the location of the ProtoCessor GPI05 LED.
In order for the PT-Link to communicate properly, it is imperative to set the IP address of both the PT-Link as well as the computer to be within the same netmask. You need to change the IP address on your computer. The following instructions will explain how to congure the IP address for Microsoft Windows 98 and Microsoft Windows NT and XP computers.
EPROM
RAM
SERIAL #
C4
PROTOCESSOR
R3
X1 C5
TRANSLATOR MODULE
C9
EEPROM
C4
C6
LOCAL C7 C8 U6 C10
PAL
R
U4
RN1
C12 U9
C20
R4
SH T
U5 L1 C14
R9 R8 R7 R6
SF000103
U7
TB1
485 DRIVER
U10
11.0592
TB3
GND +24VAC
U11
R23
C18
R17
P1
7.) You might have to reboot the computer before the IP address is valid.
Ethernet Hub Ethernet Cable
1 2 3 4
Ethernet Cable
EPROM
RAM
SERIAL #
PROTOCESSOR
C5
PT-Link Interface
TRANSLATOR MODULE
C9
C6
LOCAL C7 C8 U6 C10
PAL
R
U4
RN1
C12 U9
C20
R4
SH T
U5 L1 C14
R9 R8 R7 R6
SF000103
U7
TB1
485 DRIVER
U10
11.0592
TB3
GND +24VAC
U11
R23
C18
R17
P1
PT-Link Interface
Select the required PT-Link by typing the Number or Letter in the left hand column. You should now have a menu that looks like Figure 10. You are now ready to send and receive les to and from the PT-Link.
PT-Link Interface
Modifying Cong.csv
Make sure to upload the conguration le (cong.csv) from the PTLink control using the instructions in the previews section. After the conguration le has been uploaded open, the le using Microsoft Notepad. Now you are ready to make modications to the conguration. See Figures 13, 14 and 15 for a view of the section of code related to the Conguration of the PT-Link.
NOTE: For information on how the client will see the Orion units, see the next section.
PT-Link Interface
Figure 14: Changing the Unit Address Changing the MAC Address
To change the MAC Address, execute the instructions that follow and see Figure 15 for an example. 1.) Open the conguration le. 2.) Locate the Common Information section. 3.) Locate the System_Node_ID column. 4.) Change the System_Node_ID valued to the desired value. 5.) Save the conguration le with the new changes. 6.) Download the modied conguration le to the PT-Link. 7.) Restart the PT-Link.
PT-Link Interface
NOTE: The Remote Filename option must always be named cong.csv for congurations; otherwise, they will be ignored by the PT-Link.
From the Main Menu, type D. The menu shown in Figure 17 will appear.
10
PT-Link Interface
LOOP LED
When power is applied to the PT-Link-BACnet, the LOOP LED will also light up. The LED should icker rapidly, indicating that the PT-Link is trying to communicate with the controllers on the loop. A icker is dened as a brief moment when the LED turns off and back on. If the LOOP LED does not operate as indicated above, rst power down the unit and then reapply power. If this does not work, please contact WattMaster Controls Technical Support at our Toll Free number866918-1100for assistance.
LED 1
When power is rst applied, LED 1 will be off temporarily and then will blink one time for each controller it is communicating with. For example, if you have 4 controllers on the loop connected to the PT-Link, LED 1 will blink 4 times. If the amount of blinks does not match the number of controllers connected to the loop, it indicates there is a communications problem. The best way to nd out which board is not communicating is to go to each controller and look at its COMM LED. The COMM LED should be solid and will icker occasionally indicating communication with the PT-Link-BACnet. If the COMM LED does not icker, there is no communication with that controller.
LED 2
When power is rst applied, LED 2 will be off temporarily and then will blink slowly indicating that the PT-Link baseboard is communicating with the Protocessor Module. If LED 2 does not blink, check that the Protocessor Module is installed correctly in the PT-Link baseboard.
LED2 LED1
PWR LOOP
PWR LED
When the PT-Link-BACnet is powered up, the PWR LED should light 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 connections are tight, and that they are wired for correct polarity. The 24 VAC power must be connected so that all ground wires remain common. If after making all these checks the PWR LED still does not light up, please contact WattMaster Controls Technical Support at our Toll Free number866-918-1100for assistance.
PT-Link Interface
11
Protocessor BACnet
LA LB GPI05 TX PWR RX
GPI05 LED
The GPI05 LED will light up when the Base Board and the ProtoCessor Module have established communications. See Figure 19. This can take up to 3 minutes depending on the number of units connected to the PT-Link. If it fails to light up after 3 minutes, check that the ProtoCessor is installed correctly and rmly to the Base Board.
LB LED
Once the unit is powered up, the LB LED must be blinking constantly. See Figure 19. If this LED is constantly on or off, the Module is not working properly and needs to be replaced.
LA LED
Once the unit is powered up, the LA LED must be blinking constantly. See Figure 19. If this LED is constantly on or off, the Module is not working properly and needs to be replaced.
TX & RX LEDs
The TX and RX LEDs work together to indicate that communication is being established with the desired protocol network. If both LEDs are blinking, then communication is working properly. See Figure 19. If not, check the protocol network wiring and the baud rate in the conguration le. If all of these tests are made and the controller still doesnt operate, please contact WattMaster Controls Technical Support at our Toll Free number866-918-1100for assistance.
12
PT-Link Interface
PT-Link Interface
13
Data Arrays
MUA II Data Arrays For Field Server 1 2 3 4 5
SaTpStM OaEtpSt PofCfg ExRlys1 PofAlm ClDb InRhMax OnRly4 ExRly7 ExRly15 OaTp OaEtpDb InRhIns ExRlys2 LoSaAlm HtDb InRhMin OnRly5 ExRly8 ExRly16 OaClSt CtrlSts SpcTpIns ExRlys3 HiSaAlm DptSt ExHtPBd ExRly1 ExRly9 OaHtSt CtrlMod ExHtCfg InRh ExHtPos EtpDb SaTpSt ExRly2 ExRly10 OaDwpt ClDnmd RtRlyCfg AlmSts SpcTp SaRstSt SchdFrc ExRly3 ExRly11
Offset 0 8 16 24 32 40 48 56 64 72
0
AppVer OaEtp FanDly OnRlys RhAlm SaTp DptRstLt OnRly3 ExRly6 ExRly14
6
OaDwptSt HtDmnd MdHt2Ins SaTpAlm MdHt2Pos SpcTpMax OnRly1 ExRly4 ExRly12
7
OaRh DehmDmnd Rt2Ins OaTpAlm Rt2Pos SpcTpMin OnRly2 ExRly5 ExRly13
Offset 0 8 16 24 32 40 48 56 64 72 80 88
0
AppVer OaTp HtClDsbl HtEnbl HtPmpCfg EcoPos HiSpcAlm StgDb OaTpOst ExRly2 ExRly10 MinEcoSt
6
SaTp OaTpAlm HtDmnd PofCfg ExRlys3 MchHtAlm UnClSt SaTpOst OnRly5 ExRly8 ExRly16
7
RaTp CO2Cfg ClEnbl CavCfg ExRlys4 DrtFlAlm UnHtSt RaTpOst ExRly1 ExRly9 DuctPrSt
14
PT-Link Interface
Data Arrays
VCM Data Arrays For Field Server 2 3 4
HtSt OaRh EcoEnbl ExRlys12 AlrmGrp3 SmokeAlm DptStM UnHtOst OaTpOst OnRly2 ExRly5 ExRly13 RaDmp OaWtbl UnitMode FanDly ExRlys34 SaTpAlm LoSaAlm MdClPos WtblSt CoilTpSt OnRly3 ExRly6 ExRly14 RfPr TpDmnd CtrlSts WmupDmnd EcoPos OpTpAlm HiSaAlm MdHtPos SaClSt DptSt OnRly4 ExRly7 ExRly15
Offset 0 8 16 24 32 40 48 56 64 72 80 88 96
0
AppVer OaTp ClEnbl Rt2Ins AlrmGrp1 PofAlm InRh OcpHtSt SaTpOst SchdFrc ExRly3 ExRly11 CO2Level
1
ClSt DuctPr HtEnbl OnRlys AlrmGrp2 DrtFlAlm InRhStM UnClOst RaTpOst OnRly1 ExRly4 ExRly12 ByPasDmp
5
SpcTp ClDmnd PofCfg VfdBwPos SpcTpAlm CtrlTpCF MdHt2Pos SaHtSt InRhSt OnRly5 ExRly8 ExRly16
6
SaTp HtDmnd CO2Cfg VfdExPos MchClAlm CtrlTpHF Rt2Pos WmupSt DuctPrSt ExRly1 ExRly9 CO2St
7
RaTp DehmDmnd MdHt2Ins AlrmSts MchHtAlm CtrlTp OcpClSt SpcTpOst RfPrSt ExRly2 ExRly10 MinEcoSt
PT-Link Interface
15
Appendix A
Use the standard EIA/TIA color code for "CROSS OVER CABLE" as shown. It is not the same as a standard Cat 5 patch cabling. The outer cable jacket should Be "Orange" in color. This is not a straight thru pin 1 to pin 1 cable.
Figure 23: RJ-45 8P8C Cable for WattMaster Cross Over Networking - WattMaster Part #HZ000136
16
PT-Link Interface
Appendix B
ProtoCessor Driver - (PICS) BACnet Protocol Implementation Conformance Statement
BACnet Protocol
Date: Vendor Name: Product Name: Product Model Number: Product Description:
July 13, 2006 FieldServer Technologies FieldServer ASP-485 ProtoCessor This software product will provide bi-directional communication between various RTU, DCS, SCADA and PLC using most common protocols and a BACnet system. The FieldServer can perform protocol conversion (as opposed to routing) between the different BACnet Data Link Layer options. This is arranged by way of static mappings. See FieldServer Technologies list of protocol drivers available to determine available protocol conversions.
Protocol Conversions:
ANSI X3.4
ISO 10646 (UCS-2) IBM/Microsoft DBCS ISO 10646 (ICS-4) ISO 8859-1 JIS C
PT-Link Interface
17
VfdExPos
AI: 89
ClSt DuctPr
AI: 7 AI: 14
MdHt2Pos
AI: 38
Rt2Pos
AI: 60
Alarm Group 1 Alarm Group 2 Alarm Group 3 Dewpoint Setpoint Mirror Indoor RH Setpoint Mirror Modulating Cool Position
AlrmGrp1
AI: 104
AlrmGrp2
AI: 105
AlrmGrp3
AI: 106
DptStM
AI: 110
OaTp
AI: 54
InRhStM
AI: 114
OaWtbl
AI: 55
MdClPos
AI: 115
RfPr
AI: 62
CO2Level RaTp
MdHtPos
AI: 116
SpcTp
AI: 72
SaTp
AI: 83
ByPasDmp
AI: 153
RaDmp
AI: 154
18
PT-Link Interface
SaTpStM
AI: 82
CoilTp
AI: 181
CO2 Setpoint
CO2St
AO: 149
-100
100
RfPrSt
AO: 118
-0.2
0.2
DuctPrSt
AO: 152
RaTpOst
AO: 65
-100
100
MinEcoSt
AO: 151
100
OcpClSt
AO: 42
100
Schedule Force
SchdFrc
AO: 66
SpcTpOst
AO: 71
-100
100
SaClSt
AO: 77
40
80
PT-Link Interface
19
This is the supply air target temperature during the heating mode.
If the Supply Air Temperature Sensor is reading incorrectly, you can use this option to enter an offset temperature to adjust the Sensors Temperature. During the Unoccupied Mode of Operation, this Setpoint spreads the Occupied Cooling Setpoint out by a user adjustable amount. If you do not want Cooling to operate during the Unoccupied Mode, use the default setting of 30F for these setpoints. During the Unoccupied Mode of Operation, this Setpoint spreads the Occupied Heating Setpoint out by a user adjustable amount. If you do not want Heating to operate during the Unoccupied Mode, use the default setting of 30F for these setpoints. If the outdoor dewpoint rises above this setpoint, the unit will activate the Dehumidication Demand.
SaTpOst
AO: 80
-100
100
InRhSt
AO: 120
100
UnClOst
AO: 124
Warm Up Setpoint
WmupSt
AO: 91
50
90
UnHtOst
AO: 125
30
WtblSt
AO: 92
80
SaTpAlm
BI: 2
CO2Cfg
BI: 3
ClDmnd
BI: 5
Dewpoint Setpoint
DptSt
AO: 13
ClEnbl
BI: 6
EcoEnbl
BI: 15
FanDly
BI: 25
20
PT-Link Interface
HtDmnd
BI: 29
HtEnbl
BI: 30
HiSaAlm
BI: 33
LoSaAlm
BI: 37
CtrlTpHF
BI: 109
MdHt2Ins
BI: 39
PofCfg
BI: 57
Rt2Ins
BI: 58
OaTpAlm
BI: 117
WmupDmnd
BI: 90
MchClAlm
BI: 94
SmokeAlm
BI: 119
SpcTpAlm
BI: 101
PT-Link Interface
21
BACNETPropertyIdentier :
WattBACNETScheduleForce ::= ENUMERATED { NormalOperation (0), ForceOccupied (1), ForceUnoccupied (2) } VcmUnitMode ::= ENUMERATED { Unoccupied RemoteContactOccupied NormalScheduleOccupied PushButtonOrZoneOverride HolidayModeActive UnoccupiedZoneDemand RemoteScheduleOverride CurrentOutputForceMode SATHighOrLowCutOff CO2OverrideInProgress PurgeModeActive } VcmControlStatusBits ::= BIT STRING { AhuControlEconomizer NoOutdoorAirTempSensor CarbonDioxideSensorPresent HeatCoolStagingDisabled DehumidicationMode ModGasIIConnected ReheatIIConnected } VcmOnBoardRelaysBits ::= BIT STRING { OnBoardRelay1 OnBoardRelay2 OnBoardRelay3 OnBoardRelay4 OnBoardRelay5 }
(0), (1), (2), (3), (4), (5), (6), (7), (8), (9), (10)
22
PT-Link Interface
PT-Link Interface
23
Rt2Pos
AI: 60
InRh SpcTp
AI: 67 AI: 72
ExRlys1
AI: 18
SaTpStM
AI: 82
ExRlys2
AI: 19
SaTp
AI: 83
ExRlys3
AI: 20
ClDb
AO: 98
MdHt2Pos
AI: 38
OnRlys OaClSt
AI: 44 AI: 45
40
DP Spt.
OaDwpt OaDwptSt
AI: 47 AI: 48
Dewpoint Setpoint
DptSt
AO: 13
40
80
OaEtp OaEtpDb
AI: 49 AI: 51
Enthalpy Deadband
EtpDb
AO: 17
20
OaEtpSt
AI: 50
ExHtPBd
AO: 23
30
OaHtSt
AI: 46
OaRh
AI: 52
24
PT-Link Interface
Bad Supply Air Sensor 0 2 Cooling Demand Dehumidication Demand 0 100 External Heat Congured
SaTpAlm
BI: 2
Schedule Force
SchdFrc
AO: 66
BI: 5 BI: 10
InRhMax
AO: 68
BI: 22
Fan Start Up Delay 0 100 Fan Proving Alarm Heating Demand High Supply Air Temperature
FanDly
BI: 25
InRhMin
AO: 69
PofAlm
BI: 26
HtDmnd HiSaAlm
BI: 29 BI: 33
SpcTpMax
AO: 74
40
100
SpcTpMin
AO: 75
40
100
RhAlm
BI: 36
LoSaAlm
BI: 37
MODGAS II Connected SA Spt. SA Spt. + 50 No Outdoor Air Temperature Proof of Flow Congured
MdHt2Ins
BI: 39
SaRstSt
AO: 79
OaTpAlm
BI: 40
PofCfg
BI: 57
PT-Link Interface
25
Reheat Relay Congured Indoor Humidity Sensor Installed Space Temperature Sensor Installed On Board Relay 1 On Board Relay 2 On Board Relay 3 On Board Relay 4 On Board Relay 5 Expansion Relay 1 Expansion Relay 2 Expansion Relay 3 Expansion Relay 4 Expansion Relay 5 Expansion Relay 6 Expansion Relay 7 Expansion Relay 8 Expansion Relay 9 Expansion Relay 10 Expansion Relay 11 Expansion Relay 12 Expansion Relay 13
RtRlyCfg
BI: 59
InRhCfg
BI: 70
SpcTpIns
BI: 73
OnRly1 OnRly2 OnRly3 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6 ExRly7 ExRly8 ExRly9 ExRly10 ExRly11 ExRly12 ExRly13
BI: 127 BI: 128 BI: 129 BI: 130 BI: 131 BI: 133 BI: 134 BI: 135 BI: 136 BI: 137 BI: 138 BI: 139 BI: 140 BI: 141 BI: 142 BI: 143 BI: 144 BI: 145
BACNETPropertyIdentier :
WattBACNETScheduleForce ::= ENUMERATED { NormalOperation (0), ForceOccupied (1), ForceUnoccupied (2) } MuaIIControlMode ::= ENUMERATED { Unoccupied RemoteContactOccupied NormalScheduleOccupied HolidayModeActive ScheduleForceOccupied ScheduleForceUnoccupied CurrentOutputForceMode PushButtonOverride } MuaIIOnBoardRelaysBits ::= BIT STRING { OnBoardRelay1 OnBoardRelay2 OnBoardRelay3 OnBoardRelay4 OnBoardRelay5 }
26
PT-Link Interface
PT-Link Interface
27
TpDmnd
AI: 84
ClSt DuctPr
AI: 7 AI: 14
VfdExPos
AI: 89
CO2St
AO: 149
EcoPos
AI: 16
0.01
OaTp
AI: 54
MinEcoSt
AO: 151
99
OaWtbl
AI: 55
OcpClSt
AO: 42
90
Relief Pressure Return Air CO2 Level Return Air Temperature Space Temperature
RfPr
AI: 62
CO2Level RaTp
SpcTp
AI: 72
28
PT-Link Interface
OaTpOst
AO: 53
-10
10 Supply Air Cooling Setpoint Supply Air Heating Setpoint SaClSt AO: 77
50
70
SaHtSt
AO: 78
300
RfPrSt
AO: 118
-0.3
0.3
SaTpOst
AO: 80
-10
10
RaTpOst
AO: 65
-10
10
UnClSt
AO: 86
30
Schedule Force
SchdFrc
AO: 66
SpcTpOst
AO: 71
-10
10
UnHtSt
AO: 87
-30
PT-Link Interface
29
RhCfg
BI: 35
MdHt2Ins
BI: 39
Wetbulb Setpoint
WtblSt
AO: 92
80 No Outdoor Air Temperature Fan Proving Alarm Proof of Flow Congured REHEAT II Congured OaTpAlm BI: 40
AhuEco
BI: 55
PofAlm
BI: 26
CO2Cfg
BI: 3
PofCfg
BI: 57
Cooling Demand Cooling Enabled Constant Volume Congured Dehumidication Mode Economizer Enabled Fan Start Up Delay
ClDmnd
BI: 5
Rt2Ins
BI: 58
ClEnbl
BI: 6
CavCfg
BI: 8
Relief Pressure Congured Warm Up Mode Active Wet Bulb Sensor Congured
RfPrCfg
BI: 63
WmupDmnd
BI: 90
DehmMod
BI: 11
WtblCfg
BI: 93
EcoEnbl
BI: 15
FanDly
BI: 25
MchClAlm
BI: 94
Heat / Cool Staging Disabled Heating Demand Heating Enabled Heat Pump Congured
HtClDsbl
BI: 27
HtDmnd
BI: 29
HtEnbl
BI: 30
HtPmpCfg
BI: 32
30
PT-Link Interface
SpcTpAlm
BI: 101
HiSpcAlm
BI: 102
LoSpcAlm
BI: 103
On Board Relay 1 On Board Relay 2 On Board Relay 3 On Board Relay 4 On Board Relay 5 Expansion Relay 1 Expansion Relay 2 Expansion Relay 3 Expansion Relay 4 Expansion Relay 5 Expansion Relay 6 Expansion Relay 7
OnRly1 OnRly2 OnRly3 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6 ExRly7
BI: 127 BI: 128 BI: 129 BI: 130 BI: 131 BI: 133 BI: 134 BI: 135 BI: 136 BI: 137 BI: 138 BI: 139
BACNETPropertyIdentier :
WattBACNETScheduleForce ::= ENUMERATED { NormalOperation (0), ForceOccupied (1), ForceUnoccupied (2) } VavCavControlMode ::= ENUMERATED { Unoccupied RemoteContactOccupied NormalScheduleOccupied PushButtonOrZoneOverride HolidayModeActive UnoccupiedZoneDemand RemoteScheduleOverride CurrentOutputForceMode SATHighOrLowCutOff CO2OverrideInProgress PurgeModeActive }
(0), (1), (2), (3), (4), (5), (6), (7), (8), (9), (10)
PT-Link Interface
31
(0), (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11), (12), (13), (14)
32
PT-Link Interface
Notes
PT-Link Interface
33
Notes
34
PT-Link Interface
Notes
PT-Link Interface
35
WattMaster Controls, Inc. 8500 NW River Park Drive Parkville, MO 64152 Phone (816) 505-1100 www.orioncontrols.com Fax (816) 505-1101