General Information ......................................................................................................................................... 3
Data Sharing ................................................................................................................................................................................3
System Requirements ..................................................................................................................................................................3
Dimensions and Components ......................................................................................................................................................4
Connection and Wiring Information ................................................................................................................ 5
Confi guring the PT-Link II Controller ............................................................................................................... 6
PT-Link II Hardware Connection ..................................................................................................................................................6
Computer IP Address Set-up for Windows NT & XP ....................................................................................................................7
Computer IP Address Set-up for Windows Vista & 7 ...................................................................................................................8
Confi guring the PT-Link DIP Switches .........................................................................................................................................9
Connecting to the PT-Link II .......................................................................................................................................................10
Making Changes to the Confi guration File (confi g.csv) ..............................................................................................................12
Downloading Confi g.csv to the PT-Link II...................................................................................................................................13
Troubleshooting the PT-Link II Controller ..................................................................................................... 14
Addressing WattMaster Devices in a BACnet® Network. ...........................................................................................................14
PT-Link II Board LEDs ................................................................................................................................................................15
Troubleshooting Using RUINET .................................................................................................................................................18
Updating the PT-Link II Controller................................................................................................................. 19
Data Arrays .................................................................................................................................................... 23
Table 3: VCB-X Modular Data Array for Field Server ................................................................................................................23
Table 4: VCM-X Modular Data Array for Field Server................................................................................................................23
Table 5: VCM-X WSHP (Tulsa) & RNE Data Array for Field Server ..........................................................................................24
Table 6: VCM-X WSHP (Coil) Data Array for Field Server ........................................................................................................25
Table 7: VCM-X Data Array for Field Server..............................................................................................................................25
Table 8: SA Controller Data Array for Field Server ....................................................................................................................26
Table 9: VCM Data Array For Field Server ................................................................................................................................26
Appendix A - RJ-45 8P8C Cable for WattMaster Cross Over Networking - WattMaster Part #HZ000136 ............................ 27
Appendix F - VCM-X BACnet Parameters ...................................................................................................... 42
Appendix G - SA Controller BACnet Parameters .......................................................................................... 48
Appendix H - VCM BACnet Parameters ......................................................................................................... 52
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-PTLNK2BTL-TGD-01G Copyright April 2013 WattMaster Controls, Inc.
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.
Page 3
PT-Link II BACnet® Technical Guide
General Information
The OE368-23B-BACNET2, PT -Link II BACnet® provides bi-directional communication between your BACnet® MS/TP protocol network and
up to four* of any of the following types of Orion controllers—RNE,
VCB-X, VCM-X, SA, VCM, MUA II, or VAV/CAV:
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 II BACnet®.
*NOTE: The PT-Link II BACnet® device can be used to con-
nect to four Orion controllers. If more than four Orion
controllers are present in a system, you will need one
or more additional PT-Link II BACnet® devices for
integration with a BACnet® protocol network.
**NOTE: Documentation is available for MUA II/VAV/CA V on
Table 1: PT-Link II BACnet® Interface
Technical Data
System Requirements
Data Sharing
The PT-Link II BACnet® interface provides the following data sharing
capabilities:
• Provides values from points on the Orion side of the
gateway to BACnet
originating from BACnet® objects.
• Allows BACnet
Orion controller side of the PT-Link II BACnet
standard BACnet® write services.
®
devices as if the values were
®
devices to modify point values on the
®
by using
• The PT-Link II BACnet
assembled as surface mount. Surface mount components
are included for your convenience.
• Computer running Microsoft Windows
system.
®
interface is packaged and
TM
operating
• Ethernet Crossover Cable (supplied).
• PT-Link II BACnet software—located on included CD-
ROM and downloadable from www.orioncontrols.com/
software-new.html.
• * RUINET software— located on included CD-ROM and
downloadable from www.orioncontrols.com/software-new.
html.
*NOTE: RUINET is only needed for initial confi guration if you
need to set the address above 255 or if your BACnet
lacks DIP switches. The confi g.csv fi le’s Server_DIP
parameter is initially set to Enabled which allows
the System_Node_ID (BACnet MAC Address) and
Node_ID (Device Instance) to be set using the DIP
Switches on the module.
PT-Link II Interface 3
Revised 10/11/12
Page 4
PT-Link II BACnet® Technical Guide
Setting Up Your PT-Link II
Quick Guide
The following steps will get you up and running in no time:
1. Familiarize yourself with the PT-Link II components (Figure 1).
2. Connect your PT-Link II to the Controller(s) on your system (up
to four) and connect your PT-Link II to the BACnet Network
(Figure 2).
3. If the BACnet address doesn’t need to be any higher than 255,
then you can use the DIP switch settings to confi gure your PT-Link II. Skip to page 9. Set the DIP Switches, wait 4 minutes,
and you’ll be up and running. If the address needs to be higher
than 255, or your BACnet module does not have DIP switches,
continue with Step 4.
4. Copy the contents of the PT Link II CD to your PC’s Desktop.
You can also download the fi les from http://orioncontrols.com/software-new.html under PT-Link II Setup Files. These fi les
include RUINET.
BACnet
Communications
Wiring Terminal
®
2.37
5. Connect your PT-Link II to your computer using an Ethernet
connection (Figures 3 & 4).
6. Change your PCs IP Address. Follow the directions that match
your current operating system - Windows NT, XP, Vista, or 7.
See directions on pages 7 & 8.
7. Obtain the following from your Building Automation System
Integrator: the BACnet MAC address (System Node ID), your
server’s baud rate, and the Client Node ID.
8. Using RUINET, edit the Confi g.csv fi le and verify PT Link II communications. Follow the directions on pages 10-13.
9. If you run into any problems, follow the instructions in the
Troubleshooting section starting on page 14 of this guide.
4.25
1.31
Configuration
DIP Switches
BACnet
®
Protocessor
Module
Ethernet
Port
4.70
4.31
0.27
O
N
2
1
RX TX
www.protocessor.com
485
RSGND
ON
O
N
4
2
3
345
678
1
Protocol Coprocessor
PROTOCESSOR
www.orioncontrols.com
OE368-23B-BACNET
PT-LINK II PROTOCOL
TRANSLATOR
FOR BACNET
LED BLINK CODES (NORMAL)
LOOP
PROTO
LED 1
LED 2
TIMER
WATCH DOG
H-BEAT
WattMaster Label
#LB102082
Rev. 01A
=RAPID BLINK
=RAPID BLINK
=BLINKS QTY
CONTROLLERS
=STEADYBLINK
=STEADYBLINK
= ON SOLID
= STEADY BLINK
GND
+24 VAC
2.61
DRIVER
COMM
R
SH
T
LOOP
PROTO
LED1
LED2
TIMER
W_DOG
H-BEAT
POWER
MADE IN USA
4.82
0.20 Dia.
Local Loop
Communications
Driver Chip
Local Loop
Communications
Wiring Terminal
Communications
LED
Diagnostic
LED #1
Diagnostic
LED #2
Power
LED
Mounting Hole
Typ. 3 PL.
USB
24 VAC Power
Terminal
Port
Figure 1: PT-Link II BACnet® Dimensions and Components
4
Revised 5/11/11
PT-Link II Interface
Page 5
MS/TP Connection
®
BACnet
ToNetwork
RSGND
ON
O
O
N
N
4
2
3
2
345
678
1
1
RX TX
Protocol Coprocessor
www.protocessor.com
PROTOCESSOR
PT-Link Interface
www.orioncontrols.com
OE368-23B-BACNET
PT-LINK II PROTOCOL
TRANSLATOR
FOR BACNET
LED BLINK CODES (NORMAL)
LOOP
=RAPID BLINK
PROTO
=RAPID BLINK
LED 1
=BLINKS QTY
CONTROLLERS
LED 2
=STEADYBLINK
TIMER
=STEADYBLINK
WATCH DOG
= ON SOLID
H-BEAT
=STEADYBLINK
WattMaster Label
GND
#LB102082
Rev. 01A
+24VAC
MS/TP Connection
®
BACnet
ToNetwork
485
DRIVER
COMM
R
SH
T
LOOP
PROTO
LED1
LED2
TIMER
W_DOG
H-BEAT
POWER
MADE IN USA
PT-Link II BACnet® Technical Guide
Connection and Wiring Information
IMPORTANT WIRING NOTE:
Use the Daisy-Chain Topology As Shown in This Diagram.
DO NOT Use a Star Topology with Multiple Units Tied
Directly to the PT-Link II.
Up To 4 Controllers
Can Be Interconnected.
Controller’s Address
Cannot Be Higher Than 16.
Controller
Controller
24 VAC
(10 VA)
Line Voltage
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
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 PTLink Installed.
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.
®
UP
Mode
Selection
NEXT
PREV
STATUS
SETPOINTS
DOWN
CLEAR
ESC
SCHEDULES
ENTER
OVERRIDES
13
2
ALARMS
654
CONFIGURATION
BALANCE - TEST
9
708
DEC
MINUS
ON
-
Modular Service Tool
Typical Terminal Blocks. All
Wiring To Be T To T, SHLD
(G) To SHLD (G) & R To R
T
SHLD
R
24 VAC
(8 VA)
Line Voltage
Controller
24 VAC
(8 VA)
Line Voltage
24 VAC
(8 VA)
Line Voltage
Controller
24 VAC
(8 VA)
Line Voltage
Figure 2: PT-Link II BACnet® InterfaceWiring
PT-Link II Interface
Revised 8/31/11
5
Page 6
PT-Link II BACnet® Technical Guide
Ethernet Cable
Ethernet Hub
Connect Ethernet
Cable To Ethernet
Hub Port
Connect Ethernet
Cables To Ethernet
Hub Ports
Desktop Or Laptop PC
1
2
3
4
Ethernet Cable
Connect Ethernet
Crossover Cable
To PT-Link Ethernet
Port
PT-Link BACnet
485
DRIVER
COMM
R
SH
T
LOOP
PROTO
LED1
LED2
TIMER
W_DOG
H-BEAT
POWER
MADE IN USA
www.orioncontrols.com
WattMaster Label
#LB102082
Rev. 01A
OE368-23B-BACNET
PT-LINK II PROTOCOL
TRANSLATOR
FOR BACNET
+24VAC
GND
LOOP
LED 1
LED 2
=RAPID BLINK
=BLINKS QTY
CONTROLLERS
=STEADYBLINK
PROTO
TIMER
WATCH DOG
H-BEAT
=RAPID BLINK
=STEADYBLINK
= ON SOLID
= STEADY BLINK
LED BLINK CODES (NORMAL)
PROTOCESSOR
ProtocolCoprocessor
www.protocessor.com
1
2
345
678
O
N
O
N
1
2
3
4
ON
RX TX
RSGND
PT-Link II Ethernet Connection
PT-Link II Hardware Connection
You have two options for connecting the PT-Link II to your PC via
Ethernet:
1.) You may connect the PT-Link II directly to your PC by
using a crossover cable (by others) as shown. See Figure 3
for details.
2.) You can also connect both your PC and the PT -Link II to an
Ethernet Hub with standard CAT5 cables. See Figure 4
for details.
Desktop Or Laptop PC
Connect Ethernet
Crossover Cable Directly
To PC Ethernet Card Port
Locate a CAT5 cable and plug one end into your computer’s Ethernet
port (use a crossover cable if connecting directly to the PT-Link II).
If connecting directly, plug the other end of the Cable into the Ethernet
port on the PT -Link II. 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 II to the hub as well.
Power up the PT -Link II by plugging in the power cable. The PT-Link II
may take up to three minutes to power up completely. Once the PT-Link
II is powered up, depending on which type of BACnet module you have,
you should notice that the green GP105 LED remains on or the RUN
LED is blinking continuously on the ProtoCessor Board. See Figure 25 and 27 on pages 16 & 17 for a diagram showing the location of the
ProtoCessor RUN or GP105 LED.
Ethernet Crossover Cable
PT-Link BACnet
485
www.orioncontrols.com
TRANSLATOR
FOR BACNET
=RAPID BLINK
=RAPID BLINK
=BLINKS QTY
=STEADYBLINK
=STEADYBLINK
= ON SOLID
= STEADY BLINK
CONTROLLERS
DRIVER
COMM
R
SH
T
LOOP
PROTO
LED1
LED2
TIMER
W_DOG
H-BEAT
POWER
GND
MADE IN USA
+24VAC
RSGND
ON
O
O
N
N
OE368-23B-BACNET
4
2
345
678
2
3
1
1
PT-LINK II PROTOCOL
RX TX
LED BLINK CODES (NORMAL)
LOOP
ProtocolCoprocessor
www.protocessor.com
PROTO
P
LED 1
ROTO
LED 2
C
TIMER
ESSOR
WATCH DOG
H-BEAT
WattMasterLabel
#LB102082
Rev. 01A
Connect Ethernet
Crossover Cable
To PT-Link Ethernet
Port
Figure 3: Connecting With Crossover Cable
Figure 4: Connecting With Ethernet Cable & Hub
6
Revised 4/25/11
PT-Link II Interface
Page 7
Computer IP Address Set-up for
Windows XP, Vista, and 7
In order for the PT -Link II to communicate properly , it is imperative to set
the IP address of both the PT -Link II 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 confi gure the IP address
for Microsoft® Windows XP, Vista, and 7 operating systems.
Computer IP Address Set-up for Windows
NT & XP
1.) Click <start>; then click<Control Panel>.
2.) Double-click on the Network Connections icon.
The Network Connections Window will appear (Figure 5).
PT-Link II BACnet® Technical Guide
IP Address Confi guration
Figure 6: Local Area Connection Status Window
Figure 5: Network Connections Window
NOTE: If any wireless connections are listed, disable them
by right-clicking the connection and selecting
<Disable>.
3.) In the Network Connections Window, double-click the Local Area Connections entry. The Local Area Connection Status Window will appear (Figure 6).
4.) As shown in Figure 6, click <Properties> in the lower
left of the window. The Local Area Connection Properties Window will appear.
Figure 7: Local Area Connection Properties Window
PT-Link II Interface
5). As shown in Figure 7, in the Connection Items list box,
be sure the Internet Protocol (TCP/IP) is checked. Select the
Internet Protocol (TCP/IP) item to highlight it and then click
<Properties>. The Internet Protocol Properties Window will
appear.
7
Page 8
PT-Link II BACnet® Technical Guide
IP Address Confi guration
Figure 8: Internet Protocol Properties Window
6).Select the radio button in front of Use the following
IP address (Figure 8) and write down the current defaults
so that you can re-enter them when you fi nish confi guring the PT-Link and then typein the following
information:
a.) IP address 192.168.1.5
b.) Subnet mask 255.255.255.0
c.) Default Gateway is blank
7.) Click<OK> until all of the above network confi guration
windows are closed. You may have to reboot the computer
before the new values are valid.
Computer IP Address Set-up for
Windows Vista & 7
1.) Click<start>; then click<Control Panel>.
2.) Click on the Network and Internet icon.
3.) ClickNetwork and Sharing Center.
4.) From the shaded box in the left side of the window, select
Manage Network Connections (Vista) or Change adapter
settings (Windows 7).
5.) Right-click on the Local Area Connection icon and select
<Properties> for the drop down window.
6.) ChooseInternet Protocol Version 4 (TCP/IPv4) by
highlighting it and then click <Properties>. The Internet Protocol Properties Window will appear (Figure 8).
7.) Select the radio button in front of Use the following IP address (Figure 8) and write down the current defaults so that you can re-enter them when you fi nish confi guring the PT-Link and then type in the following
information:
a.) IP address 192.168.1.5
b.) Subnet mask 255.255.255.0
c.) Default Gateway is blank
9.) Click<OK> until all of the above network confi guration
windows are closed. You may have to reboot the computer
before the new values are valid.
8
PT-Link II Interface
Page 9
PT-Link II BACnet® Technical Guide
Confi guring the PT-Link DIP Switches
PT-Link DIP Switch Confi guration
If the BACnet address doesn’t need to be any higher than 255, then
follow these directions to use the DIP Switch settings to confi gure your
PT-Link II. The DIP Switches are shown in Figure 9.
The confi g.csv fi le’s ‘Server_DIP’ parameter will default to ‘Enabled’
which will allow the System_Node_ID (BACnet MAC Address) and
Node_ID (Device Instance) to be set using the DIP Switches on the
module. See Figure 17 on page 12. With this capability, RUINET is
not needed for the initial confi guration. Set the DIP Switches, power up
the PT-Link II, wait 4 minutes, and your PT-Link II BACnet is ready.
FFP-485
DIP
Switch
Bank A
The DIP Switches allow you to set the Baud Rate, Node-ID (Device
Instance), and MAC address on the Field RS-485 protocol as well as to
automatically download confi guration fi les for certain protocols.
The DIP Switches are designated by Bank A & B. Bank A is used to
select both the MAC Address and Device Instance – if using the DIP
switches these will always be the same. The maximum legal value is
255. See Appendix C for each possible combination for the addresses.
Bank B is used to set the Server Baud rate. For setting serial fi eld pro-
tocol baud rate, the DIP Switches B1 – B4 can be set for the following
speeds. See Table 2 for Server Baud rate settings.
NOTE: Y ou must cycle power after making changes to the DIP
NOTE: The preferred method of confi guration is to use the DIP
Switches on the Protocessor board unless your address
setting needs to be greater than 255.
1.) In order to communicate and program the PT-Link II you will
need to install RUINET software on your computer. If you do not
have the software, it is available for downloading at www.orioncontrols.com/software-new.html under PT-Link II Software
WARNING: Make sure to load RUINET onto your hard drive
and run the program from your hard drive. DO NOT under any
circumstances run RUINET from your cd drive.
2.) If RUINET is in the desktop directory (if it isn’t, locate its directory), double-click on RUINET, and the RUINET program should
run. Initially, you might see the screen below (Figure 10).
Figure 10: Update FieldServer Date and Time
3.) Type <Y> to sync the Date/Time on your PC. The following
screen will appear (Figure 11). Press any key to continue.
4.) The following screen may appear (Figure 12). Type <I> for
Specify IP Address and the message “Enter IP Address of the Field
Server to Connect to” will appear on the screen.
Figure 12: RUINET PT-Link Specify IP Address
5.) Type the IP Address of <192.168.1.24> and press <Enter>.
6.) If you have only one PT-Link connected to the network, then RUINET will automatically connect to that particular PT-Link; otherwise,
a menu will appear to allow the selection of the desired PT-Link.
NOTE: If RUINET is unable to establish a connection, there
are a few simple procedures you can perform to try to
determine the problem. T o verify your network cables,
observe the green LED displayed directly above and
to the right of the Ethernet port. This LED should be
on if the 10 BaseT cable is good. Secondly, observe
the red LED displayed directly above and to the left
of the Ethernet port. This LED should be solid while
RUINET is running. If the LEDs are lit as expected,
and RUINET still does not receive replies, then the
netmask is probably incorrect. If this does not help,
then your Ethernet setup on your PC is possibly not
compatible. Ensure that you have an Ethernet adapter
installed in your software confi guration and that it is
confi gured to run the TCP/IP protocol. If you are still
unable to connect, please contact W attMaster Controls.
Figure 11: FieldServer Date and Time Updated
10
Revised 4/25/11
PT-Link II Interface
Page 11
PT-Link II BACnet® Technical Guide
Changing the Confi g.csv File
7.) On subsequent connections, a list of PT-Links that have been recently connected may appear under the message “Recently connected
to FieldServers. Select the required PT-Link by typing the Number or
Letter in the left hand column. (Figure 13).
Figure 13: RUINET PT-Link Selection Menu
8.) Once connected, you will see the RUINET Main Menu (Figure 14).
Unless you need to make changes to the confi g.csv fi le (steps 7 through
15), you are now ready to send and receive fi les to and from the PT -Link.
9.) Type the letter <U> to upload the Confi g fi le (Figure 15), then type
<U> again (Figure 16) for Upload.
Figure 15: RUINET PT-Link Main Menu - Upload
Figure 14: RUINET PT-Link II Main Menu
PT-Link II Interface
Figure 16: RUINET PT-Link Upload
10.) You will get confi rmation that the upload is complete. Type<N>
to open the fi le in Notepad.
WARNING: Only edit the confi g.csv fi le using Notepad. DO
NOT use Excel. Using Excel to edit the confi g.csv fi le will cor-
rupt its contents!
11
Page 12
PT-Link II BACnet® Technical Guide
Changing the Confi g.csv File
11.) Inside the text fi le under ‘Connections’, you must change the
‘Server_DIP’ parameter from ‘Enabled’ to ‘Disabled’ and then you
can use RUINET to confi gure the addresses and baud rate. (See Figure 17).
Figure 17: Changing the ‘Server_DIP’ parameter
12.) Inside the text fi le you can change the System_Node_ID (the
BACnet MAC address) which defaults to 11 (Figure 18). You can
obtain this information from your Building Automation System
(BAS) Integrator.
13.) If the server baud rate needs to be changed, go to the
‘Connections’ section and only change the SERVER_BAUD
(Figure 19). Possible Baud Rate values are (9600, 19200, 38400,
76800). The default Baud Rate is 38400. You can obtain this
information from your BAS Integrator.
Figure 19: Changing the Baud Rate in Notepad
14.) The last change you may need to make is the Node_ID under
‘Client Side Nodes’ which is the BACnet Device Instance Number
(Figure 20). The default is 1.You can obtain this information from
your BAS Integrator.
Figure 18: Changing the BACnet MAC address
12
Revised 4/25/11
Figure 20: Changing the Node ID in Notepad
PT-Link II Interface
Page 13
PT-Link II BACnet® Technical Guide
Verifying PT-Link Communications
15.) Once the changes are made to the text fi le, click
upper left and then click<Save>. Now close the fi le and return to
the RUINET Main Menu.
16.) From the RUINET Main Menu, type<D> to Download the new
confi g.csv fi le to the FieldServer (Figure 21).
<File> in the
Figure 21: Download new Confi g.csv fi le
NOTE: The utility will indicate when downloading is
complete. DO NOT reset the PT-Link until this mes-
sage is displayed, as this will corrupt the PT-Link.
NOTE: The Remote Filename option must always be named
“confi g.csv” for confi gurations; otherwise, it will be
ignored by the PT-Link.
18.) Once the download is complete, restart the PT-Link II by
cycling power or press<Esc> to get back to the RUINET Main Menu
and then type<!> option to save the new confi guration fi le and restart
RUINET. It is possible to do multiple downloads to the PT-Link II
before resetting it. There will be a start-up period where you will be
unable to connect to the PT Link.
19.) From the RUINET Main Menu, type<A> for the Data Array
Overview. The Data Array Overview Screen will display (Figure 23).
17.) At the next screen, (Figure 22), type<D> again.
Figure 22: Download new Confi g.csv fi le
Figure 23: Data Array Overview Screen
20.) This screen (Figure 23) will verify communication to the HVAC
units. Lines 1 & 2 should always be present. After a start-up period
of approximately 4 minutes, you will see 1 additional line for each
HVAC unit. This screen represents the PT Link II communicating
with 1 HVAC unit.
21.) Once these steps have been completed and you have verifi ed
that the reconfi gured PT Link II has established communication to the
HVAC unit(s), it can now be added to the BAS network.
PT-Link II Interface
13
Page 14
PT-Link II BACnet® Technical Guide
Troubleshooting the PT-Link Controller
Addressing WattMaster Devices in a
BACnet
Each PT-Link II BACnet® generates only one BACnet® device regardless of the number of WattMaster controls connected to it. This device
will have all the properties of all the WattMaster controls connected.
The instance of the device is equal to the unit address. The properties
of each control can be differentiated by an offset of 500.
Examples:
1.) Properties of the controller address as 1 will range
from 0 to 499.
2.) Properties of the controller address as 2 will range
from 500 to 999.
3.) Properties of the controller address as 3 will range
from 1000 to 1499.
To search for the instance of a specific property, follow the next
formula:
Property Instance = ((Controller Address – 1) * 500) + Instance
Number from table.
®
Network.
Example:
1.) The PT-Link II BACnet® has a Node ID equal to fi ve.
2.) Two VCM controllers connected and addressed to one and
four.
3.) Searching for the Outdoor Temperature of each controller.
4.) Instance of the Outdoor Temperature in the VCM table
equal to AI: 54.
5.) Client will only see Device 5.
6.) Under Device 5 it will see AI: 54 for the Outdoor
Temperature of the unit addressed as 1 and AI: 1554 for the
Outdoor Temperature of the unit addressed as 4.
NOTE: To simplify the calculation, we recommend that the
WattMaster controllers be addressed in sequential order from one to the last controller without any unused
address(es) in between.
14
PT-Link II Interface
Page 15
Troubleshooting the PT-Link II Controller
PT-Link II Board LEDs
The PT-Link II BACnet® is equipped with LEDs that can be used for
troubleshooting. There are eight LEDs on the PT -Link board. See Figure 24 for the locations of the LEDs on the PT -Link board. The LED descriptions and functions are listed in the following paragraphs.
POWER LED
When the PT-Link II BACnet® is powered up, the “POWER” 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
V AC power must be connected so that all ground wires remain common.
If after making all these checks the “POWER” LED still does not light
up, please contact WattMaster Controls Technical Support at our Toll
Free number—866-918-1100—for assistance.
LOOP LED
When power is applied to the PT-Link II BACnet®, the “LOOP” LED
will also light up. The LED should fl icker rapidly, indicating that the
PT-Link is trying to communicate with the controllers on the loop. A
“fl icker” is defi ned as a brief moment when the LED turns off and
back on. If the “LOOP” LED does not operate as indicated above, fi rst
power down the unit and then reapply power. If this does not work,
please contact WattMaster Controls Technical Support at our Toll Free
number—866-918-1100—for assistance.
PT-Link II BACnet® Technical Guide
LED 1
When power is fi 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 fi nd out which board is not com-
municating is to go to each controller and look at its “COMM” LED. The
“COMM” LED should be solid and will fl icker occasionally indicating
communication with the PT-Link II BACnet®. If the “COMM” LED
does not fl icker, there is no communication with that controller.
LED 2
When power is fi 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 on the PT -Link baseboard and
that the “PWR” LED is lit up on the ProtoCessor Module.
PROTO LED
When the PT-Link II is fi rst powered up, the “PROTO” LED should
blink rapidly and may appear to be on solid. This LED verifi es com-
munication with the board and the ProtoCessor. If the LED doesn’t
light up, check that the ProtoCessor is installed correctly and fi rmly
connected to the Base Board. The “PWR” LED should also be lit on
the ProtoCessor Module.
Figure 24: PT-Link II BACNET® LED Locations
WATCH DOG LED
The “W-DOG” LED is used for troubleshooting by W attMaster Controls
Technical Support. The “W-DOG” LED should always be on solid.
HEARTBEAT LED
The “H-BEAT” LED blinks to show the PT-Link II board software is
running. If the LED doesn’t light up, and all other checks have been
made, please contact W attMaster Controls T echnical Support at our T oll
Free number—866-918-1100—for assistance.
TIMER LED
The “TIMER” LED is used for troubleshooting by W attMaster Controls
Technical Support. The “TIMER” LED should always be blinking
steadily.
PT-Link II Interface
Revised 8/13/12
15
Page 16
PT-Link II BACnet® Technical Guide
Troubleshooting the PT-Link II Controller - OE368-23B-BACnet
ProtoCessor Module LEDs
Refer to Figure 25 for LED locations. NOTE: If your BACnet module
does not have DIP switches, refer to Figure 27 on page 17.
PWR LED
When the PT -Link II is fi rst powered up, the “PWR” green LED should
light up and stay on continuously. If the LED doesn’t light up, check
that the ProtoCessor is installed correctly and fi rmly connected to the
Base Board.
UNUSED LEDs
15 seconds after powering up, the 4 unused LEDs will turn on solid for
5 seconds, then turn off.
RX & TX LEDs
During normal operation, the “RX” LED will fl ash when a message is
received on the fi eld port of the ProtoCessor and the “TX” LED will fl ash when a message is sent on the fi eld port of the ProtoCessor 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. If not, check
the protocol network wiring and the baud rate in the confi guration fi le.
RUN LED
The “RUN” LED will fl ash 20 seconds after power up, signifying normal
operation. The Protocessor will be able to access RUINET once this
LED starts fl ashing. During the fi rst 20 seconds, the LED should be off.
CONFIG ERR LED
The “CONFIG ERR” LED will go on solid 15 seconds after power
up. It will turn off after 5 seconds. A steady amber light will indicate a
confi guration error exists in the active confi guration. See the Error Screen
in the Remote User Interface for a description of the confi guration error.
NODE OFFLINE LED
The “NODE OFFLINE” LED will go on solid 15 seconds after power
up. It will turn off after 5 seconds. If the Node Offl ine LED stays on
solid, a node offl ine condition has occurred.
NOTE: If all of these tests are made and the controller still doesn’t
operate, please contact W attMaster Controls T echnical
Support at our T oll Free number—866-918-1100—for
assistance.
+
–
G
SYS ERR LED
The “SYS ERR” LED will go on solid 15 seconds after power up. It
will turn off after 5 seconds. A steady red light will indicate there is a
system error on the ProtoCessor. If this occurs, immediately report the
related “system error” shown in the error screen of the Remote User
Interface to FieldServer Technologies for evaluation.
COMM ERR
The “COMM ERR” LED will go on solid 15 seconds after power
up. It will turn off after 5 seconds. A steady red light will indicate a
communications problem if there is a confi gured node connected to the
ProtoCessor that is offl ine. To establish the cause of the error, go to the
error screen of the Remote User Interface interface.
RX & TX LEDs
PROTOCESSOR
BACNET
RUN LED
SYS ERR LED
COMM ERR LED
CONFIG ERR LED
NODE OFFLINE LED
PWR LED
Figure 25: PT-Link II BACNET® LED Locations
UNUSED
Figure 26: PT-Link II BACNET® Protocessor Components
16
Revised 11/2/11
PT-Link II Interface
Page 17
Troubleshooting the PT-Link II Controller - OE368-23-BACnet
ProtoCessor Module LEDs
Refer to Figure 27 for LED locations. NOTE: If your BACnet module
has DIP switches, refer to Figure 25 on page 16.
PWR LED
When the PT -Link II is fi rst powered up, the “PWR” LED should light
up and stay on continuously. If the LED doesn’ t light up, check that the
ProtoCessor is installed correctly and fi rmly connected to the Base Board.
GPI05 LED
The “GPI05” LED will light up when the Base Board and the
ProtoCessor Module have established communications. This can
take up to 3 minutes depending on the number of units connected to the
PT -Link II. If it fails to light up after 3 minutes, check that the ProtoCessor is installed correctly and fi rmly to the Base Board.
LB LED
Once the unit is powered up, the “LB” LED must be blinking constantly.
If this LED is constantly on or off, the Module is not working properly
and needs to be replaced.
PT-Link II BACnet® Technical Guide
LA LED
Once the unit is powered up, the “LA” LED must be blinking constantly.
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. If not, check
the protocol network wiring and the baud rate in the confi guration fi le.
D14 & D15 LEDs
The “D14” and “D15” LEDs work together to indicate that communication is being transmitted and received from the USB Port when
performing an update to the PT-Link software.
NOTE: 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 27: PT-Link II BACNET® LED Locations
PT-Link II Interface
17
Page 18
PT-Link II BACnet® Technical Guide
Troubleshooting the PT-Link II Controller
Using RUINET
Before continuing with the troubleshooting, make sure the PT-Link is
connected correctly and the RUINET software is installed, running, and
functioning correctly.
Verifying Proper Communications
From the RUINET Main Screen, press <O> to go the Connection
Overview Screen. This screen supplies information on communication
between the PT-Link and remote devices. A number of aspect screens
are available, and some of the aspect screens have more than one page.
Use the space bar to toggle between aspects and use the <PgUp> and
<PgDn> keys to toggle between pages of the same aspect. The Con-
nection Overview and Settings Aspect Screen is shown in Figure 28.
The main purpose in this screen is to verify that messages and characters
are being transmitted and received. In addition, it shows the number of
communication errors. If the PT-Link connection “03” is the protocol
connection, verify that is communicating appropriately. If it is not, check
that the PT -Link LEDs are working properly , the unit is wired correctly ,
and the PT-Link is confi gured correctly (Baud Rate, Unit Address &
MAC Address). If the number of errors is constantly increasing, move
to the Error Screen by pressing the <Space Bar> 3 times to fi nd out
the cause of the errors. Use the <PgUp> and <PgDn> keys to toggle
between pages of the Error Screen.
Figure 28: Connection Overview Screen
Verifying Proper Values
To verify that the correct values for each unit are being communicated
to the PT-Link, move to the Data Array Overview Screen. To get to the
screen, press <A> from the RUINET Main Menu. See Figure 29 for
screen details.
In the Data Array Overview Screen (Figure 29) you will be able to see
the data arrays of all the units connected to the PT-Link denoted by an
array name “DA_XXX_IY”—Y being the address of the unit minus
one. The Address of the unit is determined by a set of DIP switches.
To view the values being communicated from a specifi c unit, move to
the Data Array Detail Screen (Figure 30) of the unit by entering the
number under which it is listed. For example, for the unit listed in the
third position, enter<03>.
To understand what each value means, look at the Data Array Tables
for the desired unit type, VCM-X, SA, or VCM. You can change the
writable values from this screen by using the modify command. T o use
the modify command, press <M> from the Data Array Detail Screen
and then enter the Offset you want to change followed by a space and
the new value.
Example: T o change the Cooling Supply Setpoint to 60 in the VCM, press
<M>, enter<58 60>, and then press <Enter>. This could be useful to
prove that the unit can take and keep the setpoints properly.
Figure 29: Data Array Overview Screen
18
Figure 30: Data Array Detail Screen
PT-Link II Interface
Page 19
PT-Link II BACnet® Technical Guide
Updating the PT-Link II Controller
Programming the PT-Link II with
BootLoader
The PT-Link II is equipped with the ability to update its software with
the use of a computer. You will need the following before you begin:
• PT-Link II in need of an update (powered up,
no other connections necessary)
• Computer running Microsoft Windows
system
TM
operating
•Prism II software from www.orioncontrols.com/software-
new.html
• Latest version of PT-Link II software (e-mailed from our
tech support staff or downloaded from any of our websites)
and software sheet
•USB Driver Setup.exe fi le from PT-Link II CD or
downloaded from any of our websites.
• USB cable
Follow these simple steps to update the PT-Link II:
1.) Turn on your computer and download the latest Prism II software
from www.orioncontrols.com/software-new.html.
8.) In the Job-Sites Window, from the Serial Port drop down list, select
the correct COM port. If you don’t know the COM port number or if the
number is 10 or higher, follow the directions on pages 19-20.
9.) From Prism II’s Communications tab, select “Flash Selected
Controller.”
10.) The Flash Controller Window will appear.
2.) Either download the PT -Link II update fi le from http://techsupport.
wattmaster.com or save the fi le to your computer from the e-mail you
received from Tech Support. Record the path and name of the fi le for
later use. Also, print the software sheet provided for future reference.
3.) Run the USB Driver Setup.exe fi le (found on the PT-Link II CD or
downloaded from any of our websites) so that Prism can communicate
to the PT Link II. Unzip the fi le to the directory where you saved your
PT-Link II software.
4.) Plug the USB cable into the computer’s and PT-Link II’s USB
ports.
5.) A message will pop-up from the lower menu bar of Windows that
reads, “Found New Hardware.” Click on this message and follow the
instructions that appear to install the USB drivers.
6.) Open Prism II and Login with the password “Flash.” If successful,
“Level 4 Access” will appear at the lower right of the Prism program.
7.) Click on the <Job-Site> icon. The Job-Sites Window will appear.
In the Type of CommLink Dialog Box, select “Hi Speed CommLink.”
11.) From the Flash Controller Window’s Connection tab, select
“Direct”. Keep the Flash Controller Window open.
12.) Cycle power to the PT-Link II and within 5 seconds, click the
<Get Info> button in the Flash Controller W indow. The PT-Link II in-
formation will now appear in the window under the <Get Info> button.
PT-Link II Interface
Revised 3/15/11
19
Page 20
PT-Link II BACnet® Technical Guide
Updating the PT-Link II Controller
13.) The Application ID should be SS1035 and the Application V ersion
should match the software version you will be updating to.
14.) In the HEX File fi eld, enter the path and name of the HEX fi le you
downloaded and/or copied to your hard drive. Use the Browse button
(...) to the right of the fi eld if you need help in locating the fi le.
15.) Now, cycle power to the PT-Link II once again and within 5
seconds click on the <Program HEX> button (shown above). If successful, you should see the Progress Application HEX bar showing the
progress percentage.
16.) When the bar shows 100% completed, verify the PT-Link II’s
software is running by observing the Timer LED blinking.
17.) Verify the PT -Link II’ s Application Version by once again cycling
power to the PT-Link II and within 5 seconds clicking the <Get Info>
button.
18.) Verify all fi elds are correct in the information below the <Get
Info> button and under “Finalization Data.” The “Int Flash Length”
and “Checksum” values should match the values provided with the
software sheet.
20
Revised 1/14/10
PT-Link II Interface
Page 21
Updating the PT-Link II Controller
PT-Link II BACnet® Technical Guide
Finding What COM Port Number the
PT-Link II is Using
1. Left-click on <Start>, located on the bottom
left of the Windows Tool Bar.
2. Select<Control Panel>.
3. Double-click the System Icon.
6. Click on the plus sign next to Ports to see all of the
common ports.
7. Locate the USB Serial Port (COM#). The COM# in
parentheses is the port it is located on. Write this COM
port number down. You will need to know this when
setting up the Prism software.
8. If the COM port number is 10 or greater, go to
“Changing the USB COM Port Number” on page 22.
4. Click the <Hardware> tab.
5. Click the
<Device Manager> button.
PT-Link II Interface
Revised 10/11/12
21
Page 22
PT-Link II BACnet® Technical Guide
Updating the PT-Link II Controller
Changing the USB COM Port Number
When the PT-Link II is fi rst plugged in, it will be assigned a COM port
number to be used for communicating with the Prism software. If the
port number is 10 or greater, it needs to be changed to a value less than
10 to be recognized by Prism.
1. Click<Start>, click<Control Panel>, click
<System>, click the <Hardware> tab, and then
click <Device Manager> to get to the Device
Manager Window.
2. Click on the plus sign next to Ports to see all of the
COM ports.
3. Right-click on “USB Serial Port (COM#)” and select
<Properties>. In the Properties Window, select the
<Port Settings> tab.
4. To assign a port number less than 10, click on
<Advanced>. The Advanced Settings Window
will appear.
5. In the COM Port Number drop box, select which
COM port you wish to use. Make sure you select a
COM port number that is not currently in use (you can
see the ports in use in the Device Manager Window).
Select a port that is less than 10.
NOTE: Windows
that has ever been installed on your computer. So if
there are no available ports below 10, choose a port
number less than 10 for a device listed that you know
you are not currently using.
6. Once you select the correct COM port number, click
<OK> and close any windows opened in the process
of changing the port number. Make note of this number
because you will need it for your Prism setup.
Product Description: ProtoCessors are low cost TTL to RS-485
and Ethernet Embedded Coprocessor
modules enabling OEM’s to rapidly
implement BACnet in their products.
Any third-party vendor can use ProtoCessor
modules to add a BACnet interface to their
devices.
Protocol Conversions: See FieldServer Technologies list of protocol
drivers available to determine available
protocol conversions.
BACnet Standarized Device Profi le (Annex L)
BACnet Application Specifi c Controller (B-ASC)
BACnet Interoperability Building Blocks
Supported (Annex K):
K.1.2 BIBB - Data Sharing - ReadProperty-B (DS-RP-B) K.1.4 BIBB - Data Sharing - ReadPropertyMultiple-B
(DS-RPM-B)
K.1.8 BIBB - Data Sharing - WriteProperty-B (DS-WP-B) K.1.10 BIBB - Data Sharing - WritePropertyMultiple-B
(DS-WPM-B)
K.1.12 BIBB - Data Sharing - COV-B (DS-COV-B) K.2.2 BIBB - Alarm and Event-Notifi cation Internal-B
(AE-N-I-B)
K.2.5 BIBB - Alarm and Event-ACK-B (AE-ACK-B) K.2.11 BIBB - Alarm and Event-Information-B
(AE-INFO-B)
K.5.1 BIBB - Device Management - Dynamic Device
Binding-A (DM-DDB-A)
K.5.2 BIBB - Device Management - Dynamic Device
Binding-B (DM-DDB-B)
K.5.4 BIBB - Device Management - Dynamic Object
Binding-B (DM-DOB-B)
K.5.6 BIBB - Device Management - Device
Communication Control-B (DM-DCC-B)
K.5.12 BIBB - Device Management - Time
Syncronization-B (DM-TS-B)
K.5.22 BIBB - Device Management – List Manipulation-B
(DM-LM-B)
28
Revised 4/25/11
PT-Link II Interface
Page 29
PT-Link II BACnet® Technical Guide
Appendix B
Segmentation Capability: None
Standard Object Types Supported
Device Object Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value Multi State Input Multi State Output Multi State Value Notifi cation Class Object
For all of these properties, the following applies:
1). Does not support BACnet CreateObject
2.) Does not support BACnet DeleteObject
3.) No proprietary properties exist
Data Link Layer Options:
BACnet IP, (Annex J) MS/TP master (Clause 9), baud rate up to 76.8 Kbps MS/TP slave (Clause 9), baud rate up to 76.8 Kbps
Device Address Binding: Not supported
Networking Options:
Router, Clause 6 – List all routing confi gurations,
e.g., ARCNET-Ethernet, Ethernet-MS/TP, etc.
Annex H, BACnet Tunneling Router over IP BACnet/IP Broadcast Management Device (BBMD) Registrations by Foreign Devices
Character Sets Supported:
Where support for multiple character sets is indicated, this does not
imply that they can all be supported simultaneously.
ANSI X3.4 ISO 10646 (UCS-2) IBM/Microsoft DBCS ISO 10646 (ICS-4) ISO 8859-1 JIS C
PT-Link II Interface
Revised 4/25/11
29
Page 30
PT-Link II BACnet® Technical Guide
Appendix C - Node ID (Device Instance) & MAC Address
High Supply Air Cutoff (0),
Low Supply Air Cutoff (1),
High Control Mode Signal Alarm (2),
Low Control Mode Signal Alarm (3),
Digital Compressor Cutoff Alarm (4),
Digital Compressor Lockout Alarm (5),
High Head Pressure (6)
}
VcbxOnBoardRelaysBits ::= BIT STRING {
On Board Relay 1 (0),
On Board Relay 2 (1),
On Board Relay 3 (2),
On Board Relay 4 (3),
On Board Relay 5 (4)
On Board Relay 6 (5)
}
VcbxAlarmGroup1Bits ::= BIT STRING {
Bad Supply Air Sensor (0),
Bad Return Air Sensor (1),
Bad Outside Air Sensor (2),
Bad Space Sensor (3),
Bad Main Expansion Board (4),
Bad Coil Temp Sensor (5),
Bad Co2 Sensor (6),
Bad Discharge Sensor (7),
Bad OA CFM Sensor (8),
Bad Exhaust CFM Sensor (9),
Bad Supply CFM Sensor (10),
Bad Return CFM Sensor (11),
Bad Reheat Module (12),
Bad ModGas Module (13),
Bad Relay Expansion Module (14)
}
NOTE: The following points for the VCM-X Modular, VCM-X
WSHP & RNE Controllers are additional points. All
points and property identifi ers in the VCM-X Con-
troller table (pages 42-47) also apply to the VCM-X
Modular, VCM-X WSHP, and RNE Controllers.
BACnet Properties for VCM-X Modular
ParameterNameObjectDescriptionLimits
Modulating
Compressor 2
Head
Pressure 1
Head
Pressure 2
Condenser
Fan 1
Condenser
Fan 2
Remote VFD
Reset
MdCmp2AI: 206Current position
of the 2nd Stage
of Compressor
Modulation.
HdPr1AI: 207Head Pressure for
1st Compressor
HdPr2AI: 208Head Pressure for
2nd Compressor
CdFan1AI: 209Condenser Fan 1
Signal Status
CdFan2AI: 210Condenser Fan 2
Signal Status
RmVFDPosAV: 258Remote VFD
Position Reset
-1100
BACnet Properties for VCM-X WSHP (Tulsa)
and RNE Controllers
ParameterNameObjectDescriptionLimits
Modulating
Compressor 2
Head Pressure 1HdPr1AI: 207Head Pressure
Head Pressure 2HdPr2AI: 208Head Pressure
Condenser
Fan 1
Condenser
Fan 2
Water Temp. AWaterTpAAI: 220Current water
Water Temp. BWaterTpBAI: 221Current water
Remote VFD
Reset
MdCmp2AI: 206Current position
CdFan1AI: 209 Condenser Fan 1
CdFan2AI: 210 Condenser Fan 2
RmVFDPosAV:
258
of the
2nd Stage of
Compressor
Modulation.
for
1st Compressor
for
2nd Compressor
Signal Status
Signal Status
temperature of
refrigerant for
System A.
temperature of
refrigerant for
System B.
Remote VFD
Position Reset
-1100
BACnet Properties for VCM-X WSHP (Tulsa)
and RNE Controllers
ParameterNameObjectDescriptionLimits
Compressor A1
Low Suction
Pressure Alarm
Compressor A1
Lockout Alarm
Compressor A2
Low Suction
Pressure Alarm
Compressor A2
Lockout Alarm
Compressor B1
Low Suction
Pressure Alarm
Compressor B1
Lockout Alarm
Compressor B2
Low Suction
Pressure Alarm
Compressor 4
Lockout Alarm
A1LSPAlmBI: 222Alarm that
indicates
Suction Pressure
for
Compressor A1
is below the Low
Suction Pressure
Cooling (Heat-
ing) Setpoint.
A1LktAlmBI: 223Alarm that
indicates
Compressor A1
is locked out.
A2LSPAlmBI: 224Alarm that
indicates
Suction Pressure
for
Compressor A2
is below the Low
Suction Pressure
Cooling (Heat-
ing) Setpoint.
A2LktAlmBI: 225Alarm that
indicates
Compressor A2
is locked out.
B1LSPAlmBI: 226Alarm that
indicates
Suction Pressure
for
Compressor B1
is below the Low
Suction Pressure
Cooling (Heat-
ing) Setpoint.
B1LktAlmBI: 227Alarm that
indicates
Compressor B1
is locked out.
B2LSPAlmBI: 228Alarm that
indicates
Suction Pressure
for
Compressor B2
is below the Low
Suction Pressure
Cooling (Heat-
ing) Setpoint.
B2LktAlmBI: 229Alarm that
indicates
Compressor B2
is locked out.
40
Revised 10/11/12
PT-Link II Interface
Page 41
PT-Link II BACnet® Technical Guide
Appendix E - VCM-X Modular and WSHP BACnet Parameters
BACnet Properties for VCM-X WSHP (Tulsa)
and RNE Controllers
ParameterNameObjectDescriptionLimits
Low Water
Temperature 1
Alarm
Low Water
Temperature 2
Alarm
Proof of Water 1
Flow Alarm
Proof of Water 2
Flow Alarm
Module
Communica-
tions Alarm
LWT1AlmBI: 230Alarm that
indicates water
temperature is
below the
Leaving Water
Safety Setpoint
(Heating only)
for System A.
LWT2AlmBI: 231Alarm that
indicates water
temperature is
below the
Leaving Water
Safety Setpoint
(Heating only)
for System B
POWF1Alm BI: 232Alarm that
indicates no
Proof of Water
Flow for System
A (A1/A2)
POWF2Alm BI: 233Alarm that
indicates no
Proof of Water
Flow for System
B (B1/B2)
ComMAlm BI: 234Alarm that
indicates that one
or more Modules
are not
communicating
with the VCM-X
WSHP Control-
ler.
BACnet Properties for VCM-X WSHP (Coil)
ParameterNameObjectDescriptionLimits
Modulating
Compressor 2
Head Pressure 1HdPr1AI: 207 Head Pressure
Head Pressure 2HdPr2AI: 208 Head Pressure
Condenser
Fan 1
Condenser
Fan 2
MdCmp2AI: 206Current
position of the
2nd Stage of
Compressor
Modulation.
for
1st
Compressor
for
2nd
Compressor
CdFan1AI: 209Condenser
Fan 1
Signal Status
CdFan2AI: 210Condenser
Fan 2
Signal Status
BACnet Properties for VCM-X WSHP (Coil)
ParameterNameObject DescriptionLimits
Water Temp. AWaterTpAAI: 220Current water
Remote VFD
Reset
Compressor A
Low Suction
Pressure Alarm
Compressor A
Lockout Alarm
Compressor B
Low Suction
Pressure Alarm
Compressor B
Lockout Alarm
Low Water
Temperature
Alarm
Proof of Water
Flow Alarm
Module
Communica-
tions
Alarm
RmVFDPosAV:
258
A1LSPAlmBI: 222 Alarm that
A1LktAlmBI: 223Alarm that
B1LSPAlmBI: 226 Alarm that
B1LktAlmBI: 227Alarm that
LWT1AlmBI: 230Alarm that
POWF1Alm BI: 232Alarm that
ComMAlmBI: 234Alarm that
temperature.
Remote VFD
Position Reset
indicates
Suction
Pressure for
Circuit A is
below the
Low
Suction Pressure Cooling
(Heating)
Setpoint.
indicates
Circuit A
Compressors
are locked
out.
indicates
Suction
Pressure for
Circuit B is
below the
Low
Suction Pressure Cooling
(Heating)
Setpoint.
indicates
Circuit B
Compressors
are locked
out.
indicates wa-
ter tempera-
ture is below
the Leaving
Water Safety
Setpoint
(Heating
only).
indicates no
Proof of Water
Flow.
indicates that
one or more
Modules are
not commu-
nicating with
the VCM-X
WSHP
Controller.
-1100
PT-Link II Interface
Revised 10/11/12
41
Page 42
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
Alarm
Status
Control
Status
Occupied/
Mode
Enable
Cooling
Setpoint
Mirror
Control
Temperature
Duct Static
Pressure
Economizer
Position
Occupied/
Mode
Enable
Heating
Setpoint
Mirror
Modulating
Gas Valve
Position
On Board
Relays
Outdoor Air
Dewpoint
Outdoor Air
Humidity
Outdoor Air
Temperature
Outdoor Air
Wetbulb
Reheat
Value
Position
Relief
Pressure
Return Air
Temperature
AlmStsAI: 1See Alarm
CtrlStsAI: 4Current operational
ClStAI: 7Occupied/ Mode
CtrlTpAI: 9Current value of the
DuctPrAI: 14Current value of the
EcoPosAI: 16Current position
HtStAI: 31Occupied/ Mode
MdHt-
2Pos
OnRlysAI: 44See page 47.
OaDwptAI: 47Current calculated
OaRhAI: 52Current value of the
OaTpAI: 54Current value of the
OaWtblAI: 55Current calculated
Rt2PosAI: 60Current position of
RfPrAI: 62Current value of the
RaTpAI: 64Current value of the
AI: 38Current position
status.
Enable Cooling
Setpoint Mirror.
control temperature
sensor.
duct static pressure
sensor.
of the economizer
damper.
Enable Heating
Setpoint
Mirror.
of MODGAS II
modulating gas
valve control.
outdoor air
dewpoint added on
version 1.09.
outdoor humidity
sensor.
outdoor tempera-
ture sensor.
value of the outdoor
wetbulb
temperature.
MHGRV modulat-
ing hot gas reheat
valve control.
building pressure
sensor.
return temperature
sensor.
Group Bits on
Limits
page 47.
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
Indoor
Humidity
Space
Temperature
Current
Supply Air
Setpoint
Supply Air
Temperature
Temperature
Demand
VFD
Blower Fan
VFD
Relief Fan
Application
Software
Version
Alarm
Group 1
Alarm
Group 2
Alarm
Group 3
Dewpoint
Setpoint
Mirror
External
Relays 1-2
External
Relays 3-4
Indoor Rh
Setpoint
Mirror
InRhAI: 67Current value of
SpcTpAI: 72Current value of the
SaTpStMAI: 82Current SAT
SaTpAI: 83Current value of the
TpDmndAI: 84Based on the
VfdBw-
Pos
VfdExPosAI: 89Current position of
AppVerAI: 99Current version of
AlrmGrp1 AI: 104See Alarm
AlrmGrp2 AI: 105See Alarm
AlrmGrp3 AI: 106See Alarm
DptStMAI: 110Mirror of the DPtSt
ExRlys12AI: 111See page 47.
ExRlys34AI: 112See page 47.
InRhStMAI: 114Mirror of the
AI: 88Current position of
the indoor humidity
sensor.
space temperature
sensor.
Cooling or Heating
setpoint if there
is no reset source;
Current calculated
SAT setpoint with
Reset Source.
supply air
temperature sensor.
comparison
between the
current Control
Temperature and
the Heating or
Cooling Setpoint
Temperatures. Does
not work for supply
air control
the VFD blower fan
signal.
the VFD relief
fan signal.
the software in the
unit.
Group Bits on
Group Bits on
Group Bits on
“read only.”
InRhSt “read only.”
Limits
page 47.
page 47.
page 47.
42
PT-Link II Interface
Page 43
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
Modulating
Cool
Position
Modulating
Heat
Position
Unit ModeUnitModeAI: 123See page 47.
Return Air
CO
Level
2
Bypass
Damper
Position
Return
Damper
Position
Coil
Temperature
Outdoor Air
CFM
Exhaust
CFM
Supply Air
CFM
Current
Calculated
OA CFM
setpoint
Dewpoint
Setpoint
Occupied/
Mode
Enable
Cooling
Setpoint
MdClPosAI: 115Current position of
MdHtPosAI: 116Current position of
CO2Level AI: 150Current value of the
ByPas-
Dmp
RaDmpAI: 154Current position of
CoilTpAI: 181Current coil
OaCFMAI: 193Current Outdoor
EtCFMAI: 194Current Exhaust
SaCFMAI: 195Current Supply
OACfm-
StM
DptStAV: 13If the outdoor
OcpClStAV: 42If the control tem-
AI: 153Current position of
AI: 205Current calculated
the modulating
cooling signal
(Chilled water or
digital compressor).
the modulating
heating signal (hot
water or SCR heat).
CO2 sensor.
the bypass damper
signal.
the return damper
signal.
temperature reading
added on version
1.09.
Airfl ow
Measurement
Airfl ow
Measurement
Airfl ow
Measurement
Outdoor Air CFM
based on CO
dewpoint rises
above this setpoint,
the unit will
activate the
Dehumidifi cation
perature rises one
degree above this
setpoint, the control
will activate the
cooling demand. If
the control tempera-
ture is the Supply
Air Sensor, then the
cooling demand is
always active.
Demand.
level.
2
Limits
3580
099
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
Occupied/
Mode
Enable
Heating
Setpoint
Outdoor
Air Sensor
Offset
Return
Air Sensor
Offset
Schedule
Force
Space
Sensor
Offset
SAT
Cooling
Setpoint
SAT
Heating
Setpoint
Supply
Air Sensor
Offset
OcpHtStAV: 43If the control
temperature drops
one degree below
this setpoint,
the control will
activate the heating
demand. If the
control
temperature
is the Supply Air
Sensor, then there is
no heating demand.
OaTpOstAV: 53If the Outdoor
Temperature Sensor
is reading
incorrectly, you can
use this option to
enter an offset
temperature to
adjust the Sensor’s
Temperature.
RaTpOstAV: 65If the Return Tem-
perature Sensor is
reading incorrectly,
you can use this
option to enter an
offset temperature
to adjust the Sen-
sor’s T emperature.
SchdFrcAV: 660 = Auto/
Unoccupied Mode
1 = Forced On
2 = Forced Off
SpcTpOstAV: 71If the Space
Temperature
Sensor is reading
incorrectly, you can
use this option to
enter an offset
temperature to
adjust the Sensor’s
Temperature.
SaClStAV: 77Supply Air Setpoint
in Cooling Mode.
SaHtStAV: 78Supply Air Setpoint
in Heating Mode.
SaTpOstAV: 80If the Supply Air
Temperature Sensor
is reading incorrectly, you can use
this option to enter
an offset
temperature to
adjust the Sensor’s
Temperature.
099
-100100
-100100
02
-100100
4080
40200
-100100
Limits
PT-Link II Interface
Revised 11/16/10
43
Page 44
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
Warm Up
Setpoint
Wet Bulb
Setpoint
Coil
Temperature
Setpoint
Relief
Pressure
Setpoint
Indoor
Humidity
Setpoint
Unoccupied
Cooling
Offset
Unoccupied
Heating
Offset
44
WmupStAV: 91In a VAV
application, upon
entering the oc-
cupied mode, the
Warm-up Demand
will be activated
if the return air
temperature falls
one degree below
this setpoint.
WtblStAV: 92The economizer is
enabled if the
outdoor tempera-
ture or wetbulb falls
below this setpoint.
CoilTpStAV: 107This is the coil
suction temperature
target during
dehumidifi cation
mode. Produces
dewpoint in the
supply air
approximately 10°F
above this setpoint.
RfPrStAV: 118This is the target
building pressure
to be maintained
by the VFD Relief
signal.
InRhStAV: 120If the indoor
humidity rises
above this setpoint,
the unit will acti-
vate the Dehumidi-
fi cation Demand.
UnClOstAV: 124During 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 30°F for
these setpoints.
UnHtOstAV: 125During 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 30°F for
these setpoints.
Revised 4/3/13
5090
080
3570
-0.20.2
0100
030
030
Limits
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescription
CO
2
Setpoint
Minimum
Outside Air
Setpoint
Static
Pressure
Setpoint
Preheater
Setpoint
Outdoor
Air CFM
Setpoint
Outdoor Air
CFM Reset
Limit
Supply Air
Cool High
Reset
Supply Air
Heat High
Reset
Cooling
Low Reset
Source
Cooling
High Reset
Source
Heating
Low Reset
Source
Heating
High Reset
Source
CO2StAV: 149When the CO2
MinEcoSt AV: 151This is the
DuctPrStAV: 152This is the target
PreHtSpAV: 196Low Outside Air
OACfmSt AV: 203Minimum desired
OACfmRs AV: 204Maximum desired
SaClRtAV: 324High Supply Air
SaHtRtAV: 325High Supply Air
ClLoRtAV: 326Low Cool Reset
ClHiRtAV: 327High Cool Reset
HtLoRtAV: 328Low Heat Reset
HtHiRtAV: 329High Heat Reset
level rises above
the CO2 Protection
Limit Max Level,
the Economizer’s
Minimum Position
will begin to reset
open proportionally
between the CO
Protection Limit
Max Level Setpoint
and the Reset
Range Setpoint.
minimum position
of the economizer
in the occupied
modes.
duct pressure to be
maintained by the
VFD blower signal.
Ambient
Protection Setpoint
Outdoor Air CFM.
Outdoor Air CFM
when CO
Heating Reset Limit
Source Setpoint
Source Setpoint
Source Setpoint
Source Setpoint
reaches
2
its reset limit.
Cooling Reset
Limit
03000
2
1100
0.013
0100
0.10 K200 K
0.10 K200 K
40150
40150
1150
1150
1150
1150
PT-Link II Interface
Limits
Page 45
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescriptionLimits
Bad Supply
Air Sensor
Sensor
CO
2
Installed
Cooling
Enabled
Economizer
Enabled
Fan Start Up
Delay
Fan
Proving
Alarm
Heating
Enabled
High
Supply Air
Temperature
Alarm
Low Supply
Air
Temperature
Alarm
MODGAS
II
Connected
Proof of
Flow
Confi gured
REHEAT II
Connected
SaTpAlmBI: 2Alarm that
indicates a failure
in the
supply air sensor.
CO2CfgBI: 3Status that
indicates the CO2
function has been
confi gured.
ClEnbl BI: 6Status that indicates
mechanical cooling
is enabled.
EcoEnblBI: 15Status that indicates
the economizer is
enabled.
FanDly BI: 25Status that indicates
the fan is
commanded to run,
but it is in the start
up delay mode.
PofAlmBI: 26Alarm that
indicates a failure
in the fl ow of the
VFD blower.
HtEnblBI: 30Status that
indicates that
mechanical heating
is enabled.
HiSaAlmBI: 33The Supply Air
has risen above
the Hi SAT Cutoff
Setpoint. Heating
stages begin to deac-
tivate and the fan
continues to run.
LoSaAlmBI: 37The Supply Air has
fallen below the Hi
SAT Cutoff Setpoint
and cooling stages
will begin to deactivate. If the unit is in
Economizer, Vent,
or Heating Mode
the Supply Fan will
shut off.
MdHt2InsBI: 39Status that indicates
the MODGAS II
controller is
connected.
PofCfgBI: 57Status that indicates
the proof of fl ow
function has been
confi gured.
Rt2InsBI: 58Status that indicates
the MHGRV
controllers is
connected to the
system.
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescriptionLimits
Mechanical
Cooling
Alarm
Mechanical
Heating
Alarm
Dirty Filter
Detected
Control
Temperature
Cool Failure
Control
Temperature
Heat Failure
Outdoor Air
Temperature
Lost
Smoke
Detected
Alarm
Space
Temperature
Sensor Lost
MchClAlmBI: 94Compressor Relays
are enabled but
the Supply Air
Temperature has
not fallen 5°F w/in
a user-adjustable
time period. This
does not indicate
compressors are
active and will not
shut the unit down.
MchHtAlmBI: 95Heating Mode has
been initiated but
the Supply Air
Temperature has
not risen 5°F w/in
a user-adjustable
time period. This
does not indicate
heat stages are
active and will not
shut the unit down.
DrtFlAlmBI: 96Alarm that indicates
the fi lters are dirty.
CtrlTpCFBI: 108This alarm is
activated if the
control temperature
does not get within
5°F to the occupied
cooling setpoint
in an hour in the
cooling mode. This
alarm is not used
in 100% outside air
units or supply air
control.
CtrlTpHFBI: 109This alarm is
activated if the
control temperature
does not get within
5°F to the occupied
heating setpoint
in an hour in the
heating mode. This
alarm is not used
in 100% outside air
units or supply air
control.
OaTpAlmBI: 117Alarm that
indicates a failure
in the outdoor air
temperature.
SmokeAlmBI: 119Alarm that indicates
the Smoke sensor
has been activated.
SpcTpAlmBI: 101Alarm that indicates
a failure in the
space temperature
sensor.
PT-Link II Interface
45
Page 46
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
BACnet Properties for the VCM-X Controller
ParameterNameObjectDescriptionLimits
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
Expansion
Relay 14
Expansion
Relay 15
Expansion
Relay 16
OnRly1BI: 127Current status of
relay 1.
OnRly2BI: 128Current status of
relay 2.
OnRly3BI: 129Current status of
relay 3.
OnRly4BI: 130Current status of
relay 4.
OnRly5BI: 131Current status of
relay 5.
ExRly1BI: 133Current status of
relay 6.
ExRly2BI: 134Current status of
relay 7.
ExRly3BI: 135Current status of
relay 8.
ExRly4BI: 136Current status of
relay 9.
ExRly5BI: 137Current status of
relay 10.
ExRly6BI: 138Current status of
relay 11.
ExRly7BI: 139Current status of
relay 12.
ExRly8BI: 140Current status of
relay 13.
ExRly9BI: 141Current status of
relay 14.
ExRly10BI: 142Current status of
relay 15.
ExRly11BI: 143Current status of
relay 16.
ExRly12BI: 144Current status of
relay 17.
ExRly13BI: 145Current status of
relay 18.
ExRly14BI: 146Current status of
relay 19.
ExRly15BI: 147Current status of
relay 20.
ExRly16BI: 148Current status of
relay 21.
46
PT-Link II Interface
Page 47
PT-Link II BACnet® Technical Guide
Appendix F - VCM-X BACnet Parameters
VCM-X PT-Link II BACnet®
Property Identifi er:
The PT-Link II BACnet® Link amends the following property identity
to the BACnet® property identifi er.