Orion Control Systems PT-Link-LON OE368-23-LON Quick start guide

PT-Link-LON®
Technical Guide
www.orioncontrols.com
VCM-X Controller Code: SS1026 & Y200920 Version 2.0 and up;
VCM-X Modular Controller Code: SS1030 & SS1034
VCM-X WSHP Controller Code: SS1032 & SS1033
SA Controller Code: Y200921
VCM Controller Code: SS1016, Y200409, Y200616, Y200822

Table of Contents
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-PTLNKLON-TGD-01N Copyright 2010 WattMaster Controls, Inc.
LON®and LONWorks® are registered trademarks of Eschelon Corporation.
WattMaster Controls, Inc. assumes no responsibility for errors, or omissions.
This document is subject to change without notice.
General Information......................................................................................................................................... 3
Data Sharing ................................................................................................................................................................................3
Hardware Specifications ..............................................................................................................................................................3
System Requirements..................................................................................................................................................................3
Dimensions and Components......................................................................................................................................................4
Quick Guide...................................................................................................................................................... 4
Connection and Wiring Information ................................................................................................................ 5
Configuring the PT-Link Controller.................................................................................................................. 6
PT-Link Hardware Connection .....................................................................................................................................................6
Computer IPAddress Set-up for Windows NT & XP....................................................................................................................7
Computer IPAddress Set-up for Windows Vista & 7 ...................................................................................................................8
Running RUINET..........................................................................................................................................................................9
Uploading Config.csv to the PT-Link..........................................................................................................................................10
Downloading Config.csv to the PT-Link......................................................................................................................................11
Implicit and Explicit Addressing ................................................................................................................... 12
Troubleshooting the PT-Link Controller........................................................................................................ 14
PT-Link Board LEDs...................................................................................................................................................................14
ProtoCessor Module LEDs.........................................................................................................................................................15
Troubleshooting Using RUINET.................................................................................................................................................16
Verifying Proper Communications..............................................................................................................................................16
Verifying Proper Values..............................................................................................................................................................16
Data Arrays.................................................................................................................................................... 17
Table 2: VCM-X Modular Data Array for Field Server................................................................................................................17
Table 3: VCM-X WSHP (Tulsa) Data Array for Field Server......................................................................................................17
Table 4: VCM-X WSHP (Coil) DataArray for Field Server........................................................................................................18
Table 5: VCM-X Data Array for Field Server..............................................................................................................................18
Table 6: SA Controller Data Array for Field Server....................................................................................................................19
Table 7: VCM Data Array For Field Server................................................................................................................................19
Appendix A..................................................................................................................................................... 20
Figure 25: RJ-45 8P8C Cable for WattMaster Cross Over Networking - WattMaster Part #HZ000136.....................................20
Appendix B..................................................................................................................................................... 21
External Interface Files (XIF Files).............................................................................................................................................21
Appendix C - VCM-X Modular and VCM-X WSHP BACnet Parameters.......................................................... 22
Appendix D - VCM-X BACnet Parameters...................................................................................................... 24
Appendix E - SA Controller BACnet Parameters........................................................................................... 30
Appendix F - VCM BACnet Parameters ......................................................................................................... 34

PT-Link Interface 3
PT-Link-LON®Technical Guide
The OE368-23-LON, PT-Link-LON, provides bi-directional commu-
nication between ONE* of the following types of Orion controllers—
VCM-X, SA, VCM, MUAII, or VAV/CAV:
VCM-X Controller (SS1026, SS1030, SS1032,
SS1033, SS1034, Y200920)
SA Controller (Y200921)
VCM Controller (SS1016, Y200409, Y200616, Y200822)
** MUA II Controller (Y200405); VAV/CAV Controller
(Y200301)
To determine what controller you have, you must look at the label lo-
cated 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-LON®.
*NOTE: The PT-Link-LON device can be used to connect to only
one Orion controller. If more than one Orion controller is
present in a system,each onewill require aPT-Link-LON
device for integration with a LON protocol network.
**NOTE: Documentation is available for MUAII/VAV/CAV on
our Orion Controls website: www.orioncontrols.com/
literature-new.html
Data Sharing
The PT-Link-LON interface provides the following data sharing ca-
pabilities:
• Provides values from points on the Orion side of the
gateway to LON®devices as if the values were
originating from LON®objects.
• Allows LON®devices to modify point values on the
Orion controller side of the PT-Link-LON®by using
standard LON®write services.
Hardware Specifications
Table 1 contains the hardware specifications for the PT-Link-LON®
interface.
Technical Data
LON® Loop TP/FT-10 (78 Kps)
Controller Loop RS-485, 9600 Baud Rate
Network Protocol LONWorks®
Protocol
(WattMaster Loop) HSI Open Protocol Token Passing
Power Input Voltage 24 VAC
Power Consumption 10 VA Maximum
Operating Temp 10°F to 149°F
Operating Humidity 90% RH Non-Condensing
Weight 4.7 oz.
Table 1: PT-Link-LON®Interface Technical Data
System Requirements
• The PT-Link-LON®interface is packaged and assembled
as surface mount. Surface mount components are included
for your convenience.
• Computer running Microsoft WindowsTM operating
system.
• Ethernet Crossover Cable (supplied).
• PT-Link LON & RUINET software—included on
CD-ROM and also downloadable from www.orioncontrols.
com/software-new.html.
General Information

PT-Link-LON®Technical Guide
PT-Link Interface
4
Figure 1: PT-Link-LON®Dimensions and Components
Setting Up Your PT-Link
Quick Guide
The following steps will be get you up and running in no time:
1. Familiarize yourself with the PT-Link components (Figure 1).
2. Connect your PT-Link to the Controller on your system (only
one) and connect your PT-Link to the LON Network
(Figure 2).
3. Copy the contents of the PT Link CD to your PC’s Desktop.
You can also download the files from http://orioncontrols.com/
software-new.html under PT-Link Setup Files.
4. Connect your PT-Link to your computer using an
Ethernet connection (Figures 3 & 4).
5. Change your PCs IPAddress. Follow the directions that match
your current operating system - Windows NT, XP, Vista, or 7.
See directions on pages 7 & 8.
6. Using RUINET, edit the Config.csv file and verify PT Link com-
munications. Follow the directions on pages 9-13.
7. If you run into any problems, follow the instructions in the
Troubleshooting section starting on page 14 of this guide.

PT-Link Interface
PT-Link-LON®Technical Guide
5
Connection and Wiring Information
Figure 2: PT-Link-LON®Interface Wiring

PT-Link-LON®Technical Guide
PT-Link Interface
6
PT-Link Hardware Connection
You have two options for connecting the PT-Link to your PC via Eth-
ernet:
1.) You may connect the PT-Link 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 to an
Ethernet Hub with standard CAT5 cables. See Figure 4
for details.
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).
If connecting directly, plug theother end of theCable 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 on page 12 for a diagram showing the location of the ProtoCessor
“GPI05” LED.
PT-Link Ethernet Connection
Figure 4: Connecting With Ethernet Cable & Hub
Figure 3: Connecting With Crossover Cable

PT-Link Interface
PT-Link-LON®Technical Guide
7
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).
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).
Figure 6: Local Area Connection Status Window
Figure 7: Local Area Connection Properties Window
Computer IP Address Set-up for
Windows XP, Vista, and 7
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 IPaddress on your computer.
The following instructions will explain how to configure the IPaddress
for Microsoft®Windows XP, Vista, and 7 operating systems.
IP Address Configuration
4.) As shown in Figure 6, click <Properties> in the lower
left of the window. The Local Area Connection Properties Win-
dow will appear.
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.
Figure 5: Network Connections Window

PT-Link-LON®Technical Guide
PT-Link Interface
8
Configuring the PT-Link Controller
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 finish configuring
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
7.) Click <OK> until all of the above network configuration
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.) Click Network 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.) Choose Internet 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 finish configuring
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 configuration
windows are closed. You may have to reboot the computer
before the new values are valid.
Figure 8: Internet Protocol Properties Window

PT-Link Interface
PT-Link-LON®Technical Guide
9
Connecting To The PT-Link
1.) In order to communicate and program the PT-Link 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 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 direc-
tory), double-click on RUINET, and the RUINET program should
run. Initially, you might see the screen below (Figure 9). Type <I> for
Specify IPAddress and the message “Enter IPAddress of the Field
Server to Connect to” will appear on the screen.
3.) Type the IPAddress of <192.168.1.24> and press <Enter>.
4.) If you have only one PT-Link connected to the network, then RUI-
NET 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. To 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 prob-
ably 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
configuration and that it is configured to run the TCP/IP
protocol. If you are still unable to connect, please contact
WattMaster Controls.
Running RUINET
Figure 9: RUINET PT-Link Specify IP Address
5.) On subsequent connections, a list of PT-Links that have been re-
cently 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 10).
6.) Once connected, you will see theRUINET Main Menu (Figure 11).
Unless you need to make changes to the config.csv file (see steps 9-13),
you are now ready to send and receive files to and from the PT-Link.
NOTE: If you are installing a LON PT Link and the LON BAS
is using implicit addressing, no changes need to be made
to the config.csv file and you can skip to step 14.
Figure 10: RUINET PT-Link Selection Menu
Figure 11: RUINET PT-Link Main Menu

PT-Link-LON®Technical Guide
PT-Link Interface
10
Figure 13: RUINET PT-Link Upload
8.) You will get confirmation that the upload is complete. Type <N>
to open the config.csv file in Notepad.
7.) Type the letter <U> to upload the Config file (Figure 12), then type
<U> again (Figure 13) for Upload.
Changing the Config.csv File
Figure 12: RUINET PT-Link Main Menu - Upload
WARNING: Only edit the config.csv file using Notepad. DO
NOT use Excel. Using Excel to edit the config.csv file will cor-
rupt its contents!
9.) Follow the directions under “Explicit and Implicit Addressing”
on pages 12 & 13 to make changes to the config.csv file.
NOTE: The PT-Link contains an external interface file otherwise
called an XIF file (fserver.xif). The XIF file includes
information such as SNVT names and LON network
information. This file can be uploaded for use with LON
programmingsoftware.Whenuploaded, thesefiles canbe
located in thesame directory thatthe RUINETexecutable
file is stored and run from. Be sure when uploading that
the correct file is specified in the upload window. Refer
to Figures12 &13 for screen details. Refer toAppendix
B for details on uploading XIF files. 10.) Once the changes are made to the config.csv file, click <File>
in the upper left and then click <Save>. Now close the file and
return to the RUINET Main Menu.
11.) From the RUINET Main Menu, type <D> to Download the new
config.csv file to the FieldServer (Figure 17).
Figure 14: Download new Config.csv file

PT-Link Interface
PT-Link-LON®Technical Guide
11
12.) At the next screen, (Figure 18), type <D> again.
Figure 15: Download new Config.csv file
NOTE: The utility will indicate when downloading is
complete. DONOT reset the PT-Link until this message
is displayed, as this will corrupt the PT-Link.
NOTE: The Remote Filename option must always be named
“config.csv” for configurations; otherwise, they it will
be ignored by the PT-Link.
13.) Once the download is complete, restart the PT-Link by cycling
power or press <Esc> to get back to the RUINET Main Menu and
then type <!> option to save the new configuration file and restart
RUINET. It is possible to do multiple downloads to the PT-Link
before resetting it. There will be a start-up period where you will be
unable to connect to the PT Link.
14.) From the RUINET Main Menu, type <A> for the Data Array
Overview. The Data Array Overview Screen will display (Figure 16).
Changing the Config.csv File
Figure 16: Data Array Overview Screen
15.) This screen (Figure 16) 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 2 additional lines as shown.
This screen represents the PT Link communicating with 1 HVAC unit.
16.) Once these steps have been completed and you have verified
that the reconfigured PT Link has established communication to the
HVAC unit, it can now be added to the BAS network.

PT-Link-LON®Technical Guide
PT-Link Interface
12
Implicit Addressing
Explicit and Implicit Addressing
Clients can address the PT-Link using explicit or implicit addressing.
Clients using explicit addressing obtain their data transfer parameters
directly from the PT-Link-LON configuration file (config.csv). Implicit
addressingisusedwhenaNetworkManagementToolsuchasLonMaker®
is used to connect a PT-Link-LON to other LonWorks nodes—the
PT-Link-LON is assigned its data transfer (binding) parameters by the
Network Management Tool.
NOTE: The PT-Link-LON is configured from the factory to use
implicit addressing.
Implicit Addressing — Network Manager assigns addresses for
communication and ensures (via address tables in the devices) that
communication connections are known.
Explicit Addressing — Device knows the address of the point in
the remote device and communicates directly without the assistance of
the Network Manager.
Implicit Addressing Commissioning Using
LonMaker
1.) Ensure that the correct firmware and latest configuration is
loaded on the PT-Link-LON.
NOTE: Each change in the PT-Link-LON requires re-commis-
sioning of the PT-Link-LON in LonMaker.
2.) Ensure that the PT-Link-LON and the LonMaker machine
are on the same network.
3.) Open the existing Network in LonMaker or create a new
Network.
4.) Click on Create New Network and follow the network
wizard, making the following selections:
Network Interface: Choose Network Attached
Management Mode: Choose Onnet unless you are
working offline
Registered Plug-ins required: None
5.) Once Visio is open with the Network showing, drag a new
device onto the drawing from the toolbox.
6.) Follow the Device Network, making the following
selections:
Enter Device Name:Choose commission device
Specify Device Template:Choose upload from device
Specify Device Channel:Choose Auto Detect
Specify Device Properties:Leave as is (Ping is optional)
Identify Device:Choose service pin
Device Application Image:Leave unchecked
Initial State: Leave as is
7.) Press the service pin on the PT-Link-LON when asked to
do so, and the PT-Link-LON will be commissioned.
8.) Drag a new function block onto the drawing from the
toolbox. Give the function block a name and ensure that it
is allocated to the PT-Link-LON device.
9.) Once the function block is on the drawing, you can drag
input and output variables onto the function block. When
you do this, LonMaker will show you the variables
available for binding. Click on the variables you require
(or use the select “all” option), and they will be
commissioned onto the function block.
10.) You are now ready to connect these variables to other
devices by dragging connections from the toolbox and
connecting the variables.

PT-Link Interface
PT-Link-LON®Technical Guide
13
Explicit Addressing & Domain Table Setup
To use explicit addressing, the client needs to change the factory settings
contained in the PT-Link-LON’s configuration file (config.csv). The
following are the steps to change the configuration file from implicit to
explicit addressing:
1.) Upload and open the config.csv file.
2.) Locate the “Connections” section.
3.) Locate the “Lonworks_Server” column and change the
value from “Implicit” shown in Figure 17 to “Explicit”
shown in Figure 18. You should also change the “Lon
works _Input” and “Lonworks_Outputs” from Update to
Polled.
In addition, the PT-Link-LON must have its domain, subnet, and node
IDs set. This feature is enabled in the configuration file by filling out
the Title and System_Address fields of the PT-Link-LON parameters
as follows:
//==================================================
//
// Common Information
//
Bridge
System_Address ,Title
23 ,”:D48:S01:Wattmaster Explicit Lon v1.00d”
Figure 19: PT-Link-LON Domain and Subnet Setting
The Title field must start with “:D”, followed by the domain_id in
hexadecimal notation, followed by “:S”, followed by the subnet_id in
hexadecimal notation, and enclosed by “:”. The domain length is auto-
matically determined by the number of digits in the [domain_id] field.
With 2 hexadecimaldigits constituting1 byte, “:D123456:”,for example,
would have a length of 3.
Once the domain table has been set, the “:Dxx:Sxx:” part of the Title
field will be removed.
Now the Title field will be left with [Title continued…] which may be
the Node self documentation string or any title.
Explicit Addressing
Figure 17: PT-Link-LON Implicit Configuration
Figure 18: PT-Link-LON Explicit Configuration

PT-Link-LON®Technical Guide
PT-Link Interface
14
Troubleshooting the PT-Link Controller
PT-Link Board LEDs
The PT-Link-LON®is equipped with LEDs that can be used for trouble-
shooting. There are eight LEDs on the PT-Link board. SeeFigure20 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-LON®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 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 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-LON®, the “LOOP” LED will
also light up. The LED should flicker rapidly, indicating that the PT-Link
is trying to communicate with the controllers on the loop.A“flicker” is
defined as a brief moment when the LED turns off and back on. If the
“LOOP” LED does not operate as indicated above, first 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.
LED 1
When power is first 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 com-
munications problem. The best way to find out which board is not com-
municatingis togo to eachcontroller and lookat its“COMM” LED.The
“COMM” LED should be solid and will flicker occasionally indicating
communicationwith thePT-Link-LON®.If the “COMM” LED does not
flicker, there is no communication with that controller.
LED 2
When power is first applied, “LED 2” will be off temporarily and then
will blink slowlyindicating thatthe PT-Link baseboard iscommunicating
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 is first powered up, the “PROTO” LED should light
up and stay on continuously. If the LED doesn’t light up, check that the
ProtoCessoris installed correctlyand firmly connected to theBase Board.
The “PWR” LED should also be lit on the ProtoCessor Module.
TIMER LED
The “TIMER” is used for troubleshooting by WattMaster Controls
Technical Support.
Figure 20: PT-Link-LON® LED Locations
WATCH DOG LED
The“W-DOG”LED is usedfor troubleshooting byWattMaster Controls
Technical Support.
HEARTBEAT LED
The “H-BEAT” LED blinks to show there is communication between
the controllers and the PT-Link. If the LED doesn’t light up, and all other
checks have been made, please contact WattMaster Controls Technical
Support at our Toll Free number—866-918-1100—for assistance.

PT-Link Interface
PT-Link-LON®Technical Guide
15
Troubleshooting the PT-Link Controller
Figure 21: PT-Link-LON® LED Locations
ProtoCessor Module LEDs
PWR LED
When the PT-Link is first powered up, the “PWR” LED should light up
and stay on continuously. See Figure 21. If the LED doesn’t light up,
check that the ProtoCessor is installed correctly and firmly connected
to the Base Board.
GPI05 LED
The “GPI05” LED will light up when the Base Board and the ProtoCes-
sor Module have established communications. SeeFigure 21.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 firmly to the Base Board.
LON LED
Once the unit is powered up, the “LON” LED will blink continuously
until the PT-Link has been commissioned. Once commissioned, the
“LON” LED will remain off.
LA LED
Once the unit is powered up, the “LA” LED must be blinking constantly.
See Figure 21. 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 worktogether to indicatethat communication
is being established with the desired protocol network. If both LEDs
are blinking, then communication is working properly. See Figure
21. If not, check the protocol network wiring and the baud rate in the
configuration file.
D14 & D15 LEDs
The “D14” and “D15” LEDs work together to indicate that commu-
nication is being transmitted and received from the USB Port when
performing an update to the PT-Link software.
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.

PT-Link-LON®Technical Guide
PT-Link Interface
16
Using RUINET
Figure 23: Data Array Overview Screen
Figure 22: Connection Overview Screen
Figure 24: Data Array Detail Screen
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 Connec-
tion Overview and Settings Aspect Screen is shown in Figure 22.
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 iscommunicating appropriately. If it isnot, check
that the PT-Link LEDs are working properly, the unit is wired correctly,
and the PT-Link is configured correctly. If the number of errors is con-
stantly increasing, move to the Error Screen by pressing the <Space
Bar> 3 times to find out the cause of the errors. Use the <PgUp> and
<PgDn> keys to toggle between pages of the Error 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 23 for
screen details.
In the Data Array Overview Screen (Figure 23) 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”—Ybeing 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 specific unit, move to
the Data Array Detail Screen (Figure 24) 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. To 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:To change theCooling Supply Setpointto 60 intheVCM,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.

PT-Link Interface
PT-Link-LON®Technical Guide
17
VCM-X Modular & VCM-X WSHP (Tulsa) Data Arrays
Table 3: VCM-X WSHP (Tulsa) Data Array For Field Server
Table 2: VCM-X Modular Data Array For Field Server
VCM-X Modular Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt OaWtbl TpDmnd SpcTp SaTp RaTp
8OaTp DuctPr OaRh UnitMode CtrlSts ClEnbl HtEnbl EcoEnbl
16 FanDly PofCfg CO2Cfg MdHt2Ins Rt2Ins OnRlys ExRlys12 ExRlys34
24 EcoPos VfdBwPos VfdExPos AlrmSts AlrmGrp1 AlrmGrp2 AlrmGrp3 SaTpAlm
32 OaTpAlm SpcTpAlm MchClAlm MchHtAlm PofAlm DrtFAlm SmokeAlm LoSaAlm
40 HiSaAlm CtrlTpCF CtrlTpHF CtrlTp InRh InRhStM DptStM MdClPos
48 MdHtPos MdHt2Pos Rt2Pos OcpClSt OcpHtSt UnClOst UnHtOst WtblSt
56 SaClSt SaHtSt WmupSt SpcTpOst SaTpOst RaTpOst OaTpOst CoilTpSt
64 DptSt InRhSt DuctPrSt RfPrSt SchdFrc OnRly1 OnRly2 OnRly3
72 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6
80 ExRly7 ExRly8 ExRly9 ExRly10 ExRly11 ExRly12 ExRly13 ExRly14
88 ExRly15 ExRly16 CO2St MinEcoSt CO2Level ByPasDmp RaDmp RfPr
96 OaDwpt CoilTp SaTpStM PreHtSp OaCFM EtCFM SaCFM OACfmSt
104 OACfmRs OACfmStM MdCmp2 HdPr1 HdPr2 CdFan1 CdFan2 –
VCM-X WSHP (Tulsa) Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt OaWtbl TpDmnd SpcTp SaTp RaTp
8OaTp DuctPr OaRh UnitMode CtrlSts ClEnbl HtEnbl EcoEnbl
16 FanDly PofCfg CO2Cfg MdHt2Ins Rt2Ins OnRlys ExRlys12 ExRlys34
24 EcoPos VfdBwPos VfdExPos AlrmSts AlrmGrp1 AlrmGrp2 AlrmGrp3 SaTpAlm
32 OaTpAlm SpcTpAlm MchClAlm MchHtAlm PofAlm DrtFAlm SmokeAlm LoSaAlm
40 HiSaAlm CtrlTpCF CtrlTpHF CtrlTp InRh InRhStM DptStM MdClPos
48 MdHtPos MdHt2Pos Rt2Pos OcpClSt OcpHtSt UnClOst UnHtOst WtblSt
56 SaClSt SaHtSt WmupSt SpcTpOst SaTpOst RaTpOst OaTpOst CoilTpSt
64 DptSt InRhSt DuctPrSt RfPrSt SchdFrc OnRly1 OnRly2 OnRly3
72 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6
80 ExRly7 ExRly8 ExRly9 ExRly10 ExRly11 ExRly12 ExRly13 ExRly14
88 ExRly15 ExRly16 CO2St MinEcoSt CO2Level ByPasDmp RaDmp RfPr
96 OaDwpt CoilTp SaTpStM PreHtSp OaCFM EtCFM SaCFM OACfmSt
104 OACfmRs OACfmStM MdCmp2 HdPr1 HdPr2 CdFan1 CdFan2 WaterTpA
112 WaterTpB A1LSPAlm A1LktAlm A2LSPAlm A2LktAlm B1LSPAlm B1LktAlm B2LSPAlm
120 B2LktAlm LWT1Alm LWT2Alm POWF1Alm POWF2Alm ComMAlm – –

PT-Link-LON®Technical Guide
PT-Link Interface
18
VCM-X WSHP (Coil) & VCM-X Data Arrays
Table 4: VCM-X WSHP (Coil) Data Array For Field Server
VCM-X WSHP (Coil) Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt OaWtbl TpDmnd SpcTp SaTp RaTp
8OaTp DuctPr OaRh UnitMode CtrlSts ClEnbl HtEnbl EcoEnbl
16 FanDly PofCfg CO2Cfg MdHt2Ins Rt2Ins OnRlys ExRlys12 ExRlys34
24 EcoPos VfdBwPos VfdExPos AlrmSts AlrmGrp1 AlrmGrp2 AlrmGrp3 SaTpAlm
32 OaTpAlm SpcTpAlm MchClAlm MchHtAlm PofAlm DrtFAlm SmokeAlm LoSaAlm
40 HiSaAlm CtrlTpCF CtrlTpHF CtrlTp InRh InRhStM DptStM MdClPos
48 MdHtPos MdHt2Pos Rt2Pos OcpClSt OcpHtSt UnClOst UnHtOst WtblSt
56 SaClSt SaHtSt WmupSt SpcTpOst SaTpOst RaTpOst OaTpOst CoilTpSt
64 DptSt InRhSt DuctPrSt RfPrSt SchdFrc OnRly1 OnRly2 OnRly3
72 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6
80 ExRly7 ExRly8 ExRly9 ExRly10 ExRly11 ExRly12 ExRly13 ExRly14
88 ExRly15 ExRly16 CO2St MinEcoSt CO2Level ByPasDmp RaDmp RfPr
96 OaDwpt CoilTp SaTpStM PreHtSp OaCFM EtCFM SaCFM OACfmSt
104 OACfmRs OACfmStM MdCmp2 HdPr1 HdPr2 CdFan1 CdFan2 WaterTpA
112 A1LSPAlm A1LktAlm B1LSPAlm B1LktAlm LWT1Alm POWF1Alm ComMAlm –
Table 5: VCM-X Data Array For Field Server
VCM-X Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt OaWtbl TpDmnd SpcTp SaTp RaTp
8OaTp DuctPr OaRh UnitMode CtrlSts ClEnbl HtEnbl EcoEnbl
16 FanDly PofCfg CO2Cfg MdHt2Ins Rt2Ins OnRlys ExRlys12 ExRlys34
24 EcoPos VfdBwPos VfdExPos AlrmSts AlrmGrp1 AlrmGrp2 AlrmGrp3 SaTpAlm
32 OaTpAlm SpcTpAlm MchClAlm MchHtAlm PofAlm DrtFAlm SmokeAlm LoSaAlm
40 HiSaAlm CtrlTpCF CtrlTpHF CtrlTp InRh InRhStM DptStM MdClPos
48 MdHtPos MdHt2Pos Rt2Pos OcpClSt OcpHtSt UnClOst UnHtOst WtblSt
56 SaClSt SaHtSt WmupSt SpcTpOst SaTpOst RaTpOst OaTpOst CoilTpSt
64 DptSt InRhSt DuctPrSt RfPrSt SchdFrc OnRly1 OnRly2 OnRly3
72 OnRly4 OnRly5 ExRly1 ExRly2 ExRly3 ExRly4 ExRly5 ExRly6
80 ExRly7 ExRly8 ExRly9 ExRly10 ExRly11 ExRly12 ExRly13 ExRly14
88 ExRly15 ExRly16 CO2St MinEcoSt CO2Level ByPasDmp RaDmp RfPr
96 OaDwpt CoilTp SaTpStM PreHtSp OaCFM EtCFM SaCFM OACfmSt
104 OACfmRs OACfmStM ––––––

PT-Link Interface
PT-Link-LON®Technical Guide
19
VCM Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt OaWtbl TpDmnd SpcTp SaTp RaTp
8OaTp DuctPr OaRh UnitMode CtrlSts ClDmnd HtDmnd DehmDmnd
16 ClEnbl HtEnbl EcoEnbl FanDly WmupDmnd PofCfg CO2Cfg MdHt2Ins
24 Rt2Ins OnRlys ExRlys12 ExRlys34 EcoPos VfdBwPos VfdExPos AlrmSts
32 AlrmGrp1 AlrmGrp2 AlrmGrp3 SaTpAlm OaTpAlm SpcTpAlm MchClAlm MchHtAlm
40 PofAlm DrtFlAlm SmokeAlm LoSaAlm HiSaAlm CtrlTpCF CtrlTpHF CtrlTp
48 InRh InRhStM DptStM MdClPos MdHtPos MdHt2Pos Rt2Pos OcpClSt
56 OcpHtSt UnClOst UnHtOst WtblSt SaClSt SaHtSt WmupSt SpcTpOst
64 SaTpOst RaTpOst OaTpOst CoilTpSt DptSt InRhSt DuctPrSt RfPrSt
72 SchdFrc OnRly1 OnRly2 OnRly3 OnRly4 OnRly5 ExRly1 ExRly2
80 ExRly3 ExRly4 ExRly5 ExRly6 ExRly7 ExRly8 ExRly9 ExRly10
88 ExRly11 ExRly12 ExRly13 ExRly14 ExRly15 ExRly16 CO2St MinEcoSt
96 CO2Level ByPasDmp RaDmp RfPr OaDwpt CoilTp SaTpStM PreHtSp
Table 7: VCM Data Array For Field Server
Table 6: SA Controller Data Array For Field Server
SA Controller Data Array For Field Server
Offset 01234567
0AppVer ClSt HtSt TpDmnd SpcTp SaTp DuctPr UnitMode
8CtrlSts ClEnbl HtEnbl EcoEnbl FanDly MdHt2Ins Rt2Ins EcoPos
16 VfdBwPos SaTpAlm SpcTpAlm MchClAlm MchHtAlm PofAlm DrtFAlm LoSaAlm
24 HiSaAlm CtrlTpCF CtrlTpHF CtrlTp InRh InRhStM DptStM MdClPos
32 MdHtPos MdHt2Pos Rt2Pos OcpClSt OcpHtSt UnClOst UnHtOst SaClSt
40 SaHtSt WmupSt SpcTpOst SaTpOst CoilTpSt DptSt InRhSt DuctPrSt
48 SchdFrc OnRly1 OnRly2 OnRly3 OnRly4 OnRly5 ExRly1 ExRly2
56 ExRly3 ExRly4 ExRly5 ExRly6 ExRly7 ExRly8 ExRly9 ExRly10
64 ExRly11 ExRly12 ExRly13 ExRly14 ExRly15 ExRly16 CoilTp SaTpStM
72 PreHtSp EaTp EwTp EaRH HdPr1 HdPr2 CoilTp2 EaDpt
80 WSEByp WSEByp2 MdCmp2 CoilTpSt CdPos1 CdPos2 EaTpAlm EmerAlm
88 PoWFAlm DrnAlm EaTpOst EwTpOst ––––
SA & VCM Data Arrays

PT-Link-LON®Technical Guide
PT-Link Interface
20
Appendix A
Use the standard EIA/TIA color code for "CROSS OVER CABLE" as shown.
It is the same as a standard Cat 5 patch cabling. The outer cable jacket should
Be "Orange" in color. This is a straight thru pin 1 to pin 1 cable.
not
not
1
2
3
4
5
6
RJ-45 Connector as viewed
from the bottom side
8
7
6
5
4
3
RJ-45 Connector as viewed
from the bottom side
Brown/White
White/Brown
Orange/White
White/Blue
Blue/White
White/Orange
White/Orange
Orange/White
White/Green
Blue/White
White/Blue
Green/White
Figure 25: RJ-45 8P8C Cable for WattMaster Cross Over Networking - WattMaster Part #HZ000136