Orion BACnet Link User Manual

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: [phone]
PH: [phone] · FAX: [phone] · E-mail: [e-mail]
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.

General Information

Technical Guide

The OE367-22 BACnet® Link provides bi-directional translation of
data and information between BACnet® devices and Orion VAV/CAV,
CW/HW and MUA II unit controllers.

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
a maximum of 64 total controllers to be used.

Data Sharing

The BACnet® Link interface provides the following data sharing capa­bilities:

• Provides values from points on the Orion side of the

gateway to BACnet
originating from BACnet

• Allows BACnet

Orion controller side of the BACnet
standard BACnet® write services

®

devices as if the values were

®

objects.

®

devices to modify point values on the

®

Link by using

Scheduling

®

services

®

devices to send Schedule events

• Ability to allow BACnet

to the Orion controller side of the gateway by using
standard BACnet

Hardware Specifications

Table 1 below contains the hardware specifications for the BACnet
Link interface.

Technical Data

BACnet Loop

Controller Loop
Protocol (BACn et Loop)
Protocol

(Wa ttMa ster L o o p)
Power Input Voltage
Power Consumption
Operating Temp
Operating Humidity
Weight

Table 1: BACnet® Link Interface Technical Data

RS-485, Auto Detect Host
Matching - 9600, 19200, 38400,
76800 Baud Rates

RS-485, 9600 Baud
MS/TP Lan
HSI Open Protocol

Token Passing
24 VAC
10 VA Maximum
10°F to 149°F
90% RH N on-Condensing
8 oz

®

4.50"

0.25”

4.00”

Network (MSTP)
Communications
Wiring Terminal

Network
Driver Chip

0.20 Dia.
Mounting Hole
Typ. 4 P L.

NET-

WORK

LOOP R4

C9

DRIVER

U7

TERM.

Mounting
Backplate

ADDR.

2

C4

U1

EEPROM

T

SHLD

R

C10

C12

R15

R11

R10

R18

JP4

Network
Communications
LED

R1

R3

JP1

1

U6

X2

RN2

LED 1

LED 2

LED 3

Local Loop
Communications
LED

Address Switch

EPROM Chip
Pin 1 Indicator

TRANSLATOR BOARD
YS101928

REV 0

C2

U2

RN1

U9

NET

COMM

LED 4

C3

C7

LOOP

COMM

PWR

7.00"

U3

C8

EPROM

Q1

R13

Power
LED

RAM Chip
Pin 1 Indicator

RAM

JP2

VCC VBAT

R16

R2

C11

WDOG

U10

JP3

C14

R14

R17

D2

R20

SERIAL #

U5

R12

C17

C1

U4

R19

R21

R5

X1

C5

LOCAL

C6

LOOP

R

SHLD

T

L1

R6

R7

R8

R9

D1

GND

C16

+24VAC

R22

U11
D3

R23

(+)

(-)

U8

DRIVER

C13

TB3

C19

Local Loop
Communications
Wiring Terminal

Local Loop
Communications
Driver Chip

24 VAC Power
Terminals

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
LAN Connection
To BACnet
Network

Line Voltage

VAV/CAV or MUA II Unit Controller

24 VAC
(10 VA)

VAV/CAV or MUA II Unit Controller

VAV/CAV or MUA II Unit Controller

T
SHLD
R

Mode

Selection

STATUS

SETPOINTS

SCHEDULES

OVERRIDES

ALARMS

CONFIGURATION

BALANCE-TEST

ON

UP

PREV

DOWN

ESC

ENTER

13

2

708

DEC

Typical Terminal Blocks. All
Wiring To Be T To T, SHLD
(G) To SHLD (G)&RToR

NEXT

CLEAR

654

9

MINUS

-

Modular Service Tool

All Programming Of Unit Controllers

Must Be Done With The Modular Service Tool

Figure 2: BACnet® Link Interface Wiring

24 VAC
(8 VA)

Line Voltage

VAV/CAV or MUA II Unit Controller

24 VAC
(8 VA)

Line Voltage

24 VAC
(8 VA)

Line Voltage

VAV/CAV or MUA II Unit Controller

24 VAC
(8 VA)

Line Voltage

To Next VAV/CAV or MUA II

Controller On Loop

Up To 16 Controllers

Can Be Interconnected

24 VAC
(8 VA)

Line Voltage

VAV/CAV or MUA II Unit Controller

24 VAC
(8 VA)

Line Voltage

Figure 3: BACnet® Link Interface Address Switch Setting

4

BACnet® Link Interface

Troubleshooting Information

Technical Guide

General Information

The BACnet® Link is designed to only work with the following Orion
controllers.

VAV/CAV Controller (SS1003, SS1012, Y200235, Y200301)
MUA II Controller (SS1004, Y200231, Y200306, Y200405)
CW/HW Controller (Y200311)

To determine what controller you have you must look at the label lo­cated on the controller E-prom. If the controller label does not match
any of the SS or Y numbers listed above, your controller will not work
with the BACnet® Link.

Using LED’s To Verify Operation

The BACnet® Link is equipped with LED’s that can be used for trouble­shooting. There are seven LED’s on the BACnet® Link. Five of these
LED’s are used in troubleshooting. The LED’s and their uses are as
follows:

PWR

This LED will light up to indicate that 24 VAC power has been ap­plied to the controller.

LOOP COMM

This LED will light up to indicate communication with the controllers
on the loop.

NET COMM

This LED will light up to indicate communication with the BACnet®
router.

LED 4

This LED is not currently used.

LED 3

This LED is also used to indicate communication with the BACnet®
router.

LED 2

This LED is used to indicate the number of controllers the BACnet®
Link is communicating with.

LED 1

This LED is not currently used.

PWR LED Operations

When the BACnet® Link 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 connec­tions are tight and that they are wired for correct polarity. The 24
VAC power must be connected so that all ground wires remain com­mon. If after making all these checks the PWR LED does not light up,
please contact WattMaster technical support for assistance.

LOOP COMM LED Operations

When power is applied to the BACnet® Link the “LOOP COMM”
LED will also light up. The LED should flicker rapidly indicating
that the BACnet® Link is trying to communicate with the controllers
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
this does not work, then contact WattMaster technical support for as­sistance.

LED 2 Operations

When power is first applied, “LED 2” will be off temporarily then will
blink one time for each controller it is communicating with. For ex­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
does not match the number of controllers connected to the loop, it
indicates there is a communications problem. The best way to find
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
occasionally indicating communication with the BACnet® Link. If
the COMM LED does not flicker, there is no communication with that
controller.

NET COMM LED Operations

The “NET COMM” LED works the same way as the LOOP COMM
LED but it indicates that the BACnet® Link is trying to communicate
with the BACnet® router.

Figure 4 BACnet® Link LED Locations

BACnet® Link Interface

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 be­tween 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 W attMaster Controls Technical Support at our T oll Free
number, 866-918-1100 for assistance.

5

Technical Guide

Read

Programming- General Information

BACnet® Link Overview

The BACnet® Link provides the communications interface between the
Orion system and a BACnet® network. One BACnet® Link can support
up to sixteen controllers. The BACnet
network using Master-Slave/Token Passing (MS/TP) LAN data link
protocol.

The BACnet® Link supports 3 different controller types (device ob­jects). These are the Orion MUA II, VAV/CAV and the CW/HW con­trollers.

®

Link connects to the BACnet

BACnet® Link Device Object

The information that follows describes the characteristics of the BACnet
Link Device Object. The properties for the BACnet® Link Device Ob­ject are listed in Table 2.

Object Name

The Object Name is a 15 byte character string that can be set through
the BACnet® front end.

Instance Number

The Instance Number of the Device Object is determined by the ad­dress jumper setting on the BACnet® Link. The BACnet® Link has two
address jumpers which allows the addressing number range to be from
0 to 3. The Instance Number of the Device Object would be the jumper
number plus 600192. This means there can be only four BACnet® Links
(Device Objects) on the entire local BACnet® system installation.

Location and Description

The Location and Description are 15 bytes character strings that can
be set through BACnet®.

Local Time and Date

The BACnet® Link (Device Object) does not have a hardware real time
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
is a software timer, if the BACnet® Link loses power, the time will be
lost or incorrect and will need to be reset.

WattBacObjectTypes

The BACnet® Link (Device Object) amends the following object type
to BACnet®’s object type, BACnetObjectType.

WattBacObjectTypes := Enumerated {

CwHw (259)
MuaII (258)
VavCav (257)

}

If any of these W attBacObjectT ypes conflict with other custom BACnet
object types on your BACnet® system, please contact WattMaster con­trols.

Local Address (MAC address)

The BACnet® Link’s Local Address (MAC address) on the MS/TP
LAN is determined by the address jumper on the device. The Local

®

Address is always the address jumper plus 32. Therefore, the
BacnetOrionInterface device’s Local Address (MAC address) can be
set to address 32, 33, 34 or 35. See Figure 3 for address switch setting
information.

BACnet® Services Supported

The BACnet® Link supports the following BACnet® services:

®

ReadProperty Service ReadPropertyMultiple Service
WriteProperty Service Who-Has and I-Have Service
Who-Is and I-Am Service

MS/TP LAN Baud Rate

The OE367-22 BACnet® Link (Device Object) is able to detect the Baud
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
Baud rate of 9600, 19200, 38400 or 76800 Baud as required.

BACnet® Link De vice Object Pr oper ties

Pr oper ty Identifie r Property Data Type

APD U _Timeout Unsigned R/O
Application_Software_Version CharacterSting R/O
Data_Base_R evision Unsigned R/O
Description CharacterSting R/W
Firmware_R evision CharacterSting R/O
Lo c a l _ Date Da te R/ W
Local_Time Time R/W
Location CharacterSting R/W
Max_ APD U _Length_A ccepted Unsigned R/O
Max_ M aster Unsigned R/O
Max-Info_Fram es Unsigned R/O
Mod el_Nam e CharacterSting R/O
Num ber_Of_A PD U_R etried Unsigned R/O
Object_Identifier BACnetO bjectIdentifier R/O
Object_List BACnetA RR AY [N] R/O
Object_Nam e C haracterString R/W
Object_Type BAC netObjectType R/O
Protocol_Conformance_C lass Unsigned(1..6) R/O
Protocol_Object_Types_Supported BAC netObjectTypesSupported R/O

®

Protocol_Services_Supported BAC netServicesSupported R/O
Protocol_Version Unsigned R/O
Segm entation_Supported BACnetSegm entation R/O
System_Status BAC netDeviceStatus R/O
Vendor_Identifier Unsigned16 R /O
Vendor_N ame CharacterString R/O

or

Write

6

Table 2: BACnet® Link Device Object Properties

BACnet® Link Interface

Programming - Standard Objects

Technical Guide

General Information

The BACnet® Link provides additional shadowing Analog Input Ob­jects and Analog V alue Objects for read/write parameters of the MUA

II, VAV/CAV and CW/HW controllers.

Note: The BACnet® Link does not implement any operational

function for the Analog Input Object or the Analog Value
Object but only uses the Current Value property of the
Analog Input/Value Object as a vehicle to convey one
specified parameter of the MUA II, VAV/CAV or CW/
HW controller.

Read Only Parameters are represented by Analog Input Objects and
Setpoint Parameters are represented by Analog Value Objects.

Parameters

Parameters for (1) MUA II controller are represented by 36 Analog
Input/Value Objects.

Parameters for (1) VAV/CAV controller are represented by 52 Analog
Input/Value Objects.

Parameters for (1) CW/HW controller are represented by 54 Analog
Input/Value Objects.

Instance Number Base

Each Analog Input/Value Object has an unique Object Instance Num­ber Base that can be used to identify which parameter the object repre­sents. The unique Object Instance Numbers are calculated from for­mula based on the Instance Number Base which are defined in the tables
that follow.

MUA II Instance Number Base

Instance Number Base For MUA II Controller

Spt.

Limits

SA Spt.

+ 50

Parameter

Alarm Status 14 Analog Input
Control Status 12 Analog Input
Cooling Deadband 20 Analog Value 2 20
Current Mode 11 Analog Input
Dew Point Reset Limit 27 Analog Value 40 DP Spt.
Dewpoint Setpoint 22 Analog Value 40 80
Enthalpy Deadband 23 Analog Value 3 20
External Heat Position 15 Analog Input
External Heat Proportion

Band
External Relay Group #1 34 Analog Input
External Relay Group #2 35 Analog Input
External Relay Group #3 36 Analog Input
Heating Deadband 21 Analog Value 2 20
Modulate Gas Valve

Position
On Board Relay Group 33 Analog Input
Outdoor Air Cooling

Setpoint
Outdoor Air Dew Point 5 Analog Input
Outdoor Air Dew Point

Setpoint
Outdoor Air Enthalpy 8 Analog Input
Outdoor Air Enthalpy

Deadband
Outdoor Air Enthalpy

Setpoint
Outdoor Air Heating

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

Supply
Space Humidity At Min

Supply
Space Temperature 16 Analog Input
Space Temperature At

Max Supply
Space Temperature At Min

Supply
Supply Air Reset Limit 24 Analog Value SA

Supply Air Setpoint 31 Analog Value 50 90
Supply Air Setpoint Mirror 1 Analog Input
Supply Air Temperature 19 Analog Input

Instance

Number

Base

30 Analog Value 1 30

17 Analog Input

10 Analog Input

28 Analog Value 0 100

29 Analog Value 0 100

25 Analog Value 40 100

26 Analog Value 40 100

Represented

By

Object

3 Analog Input

6 Analog Input

9 Analog Input

4 Analog Input

BACnet® Link Interface

Table 3: Instance Number Base Data For MUA II

7

Technical Guide

Programming - Standard Objects

MUA II BACnet® Property Identifier

The BACnet® Link amends the following property identity to BACnet®’s
property identifier.

BACnetPropertyIdentifier :

WattBacScheduleState ::= ENUMERATED {

NormalOperation (0),

ForceOccupied (1),

ForceUnoccupied (2)

}

MuaIIControlMode ::= ENUMERATE {

Unoccupied (0),

RemoteContactOccupied (1),

NormalScheduleOccupied (2),

HolidayModeActive (3),

ScheduleForceOccupied (4),

ScheduleForceUnoccupied (5),

CurrentOutputForceMode (6),

PushButtonOverride (7)

}

MuaIIControlStatusBits ::= BIT STRING {

CoolingDemand (0),

HeatingDemand (1),

DehumidificationDemand (2),

FanInStartUpDelay (3),

ProofOfFlow (4),

SpaceHumiditySensorInstalled (5),

SpaceTemperatureSensorInstalled (6),

ExternalHeatConfig (7),

ReheatRelayConfig (8),

ModGasIIConnected (9),

ReheatIIConnected (10),

}

MuaIIOnBoardRelayBits ::= BIT STRING {

OnBoardRelay1 (0),
OnBoardRelay2 (1),
OnBoardRelay3 (2),
OnBoardRelay4 (3),
OnBoardRelqy5 (4),
}

MuaIIExRelayGroup1Bits ::= BIT STRING {

ExpansionBoard1Relay1 (0),
ExpansionBoard1Relay2 (1),
ExpansionBoard1Relay3 (2),
ExpansionBoard1Relay4 (3),
}

MuaIIExRelayGroup2Bits ::= BIT STRING {

ExpansionBoard2Relay1 (0),
ExpansionBoard2Relay2 (1),
ExpansionBoard2Relay3 (2),
ExpansionBoard2Relay4 (3),
}

MuaIIExRelayGroup3Bits ::= BIT STRING {

ExpansionBoard3Relay1 (0),
ExpansionBoard3Relay2 (1),
ExpansionBoard3Relay3 (2),
ExpansionBoard3Relay4 (3),
}

MuaIIAlarmBits ::= BIT STRING {

BadSupplyAirTemperatureSensor (0),
NoOutdoorAirTemperatureAvailable (1),
MissingHumiditySensor (2),
FanProvingAlarm (3),
LowSupplyAirTemperature (4),
HighSupplyAirTemperature (5),
}

8

BACnet® Link Interface