How To: Discover and Install Comm3-4 Bridge with Tracer SC

Hi, my name is Jeff Heilman
Today I'm going to show you

How to install a Comm3/4 to Tracer SC
Bridge in the Tracer SC Interface

What you see here is the Bridge side
that I've created in Tracer Summit

You see I have a PCM.
This is treated as an Air Handler

And then I have 4 VAV II/III/IV

One thing you notice is the
last two here, 70 and 71

Are actually non communicating
devices that don't exist

I'm going to show you
you'll see in Tracer SC interface

Why I'm showing you this

So the first step in the installation
is obviously to ensure

That all our devices are communicating

So coming in to Tracer Summit
verifying communication

Is an important first step
We've also added some reports

To make this process easier
A unit configuration Report

Site Configuration Report that
will show you the devices

You have in your site

So once I've verified that everything
looks good in my Bridge side

And everything is communicating

I want to switch over to
my Tracer SC Interface

So you see here I'm just
logging into my Tracer SC

Using any browser I want, with this new
Tracer SC interface you can use

Any of the main web browsers

Chrome, Firefox, Internet Explorer

All right, so you are going to see here
I have no devices installed in this SC

I have an empty device count here

I want to go and discover the devices
that I have in my Bridge

So this process is very similar
to the BACnet and LON discovery

This product in particular you are
going to select BACnet/IP discovery

This is on Ethernet Port 1. So now
in the lower right hand corner

I'm going to start my discovery

And at this point Tracer SC
is going to go and look for the devices

On the Bridge and the Bridge itself

As you can see Tracer SC finished
its discovery of the BACnet IP network

And found 6 devices, so I'm going
to select install devices

You see it has three that are ready
to be defined for installation

And if you look at this first tab,
there were three devices

Found that are not ready.
The first is the BMTB

Which will never be installed and
it says is not supported

The other two, the VAVs that were
comm down show up as devices offline

We cannot install offline devices

Because the SC creates a data packet
dynamically based on

The configuration of the UCMs

And therefore we are not able
to install devices

That we can't communicate with

All right, back to the define for installation

You see the VAV II/III/IV are ready
to auto install

And we also get assigned
a standard graphic

No template is necessary or
even possible for these VAVs

PCM on the other hand, in addition to
the UPCM and TCM Slave

You can create templates for it
So for the PCM, I'm going to click

I'm going to select to assign a
template that I've already created

For the PCM

One thing to note, if you are
creating a template from scratch

You'll get default point and variable
names displayed in the SC interface

We'll actually read those off from
the device to make

The template process
easier for you

The one piece of information
that is important to remember is

If you are going to create
your own keys for those

Make sure you assign
a dimensionality

So that they have a set of units
associated with each custom key

All right, I've setup my devices up
So they are ready for installation

I'm going to select
to install the devices

All right, SC has now finished installing
the three devices

So I'm going to click in done

Now you see the three devices here

So I'm just going to quick click on
a VAV II/III/IV so you can see

The similarities to a VV550 or a
UC210 or a UC400 VAV box

You notice that almost all of the
data is going to be the same

And we automatically assigned a
standard graphic

Just like we would for any
other VAV box

And better yet, when you
go to the Spaces Page

Your customers are not going to
be able to tell the difference

Between which protocol and which
controller we are talking to

All VAV boxes, all the data has been
normalized to the same

Set of standard SC information

Likewise with the PCM which
I installed as an Air Handler

I can open that

And look at the graphic I assign in the template

I selected a standard graphic

Or the assign graphic rather

You see we have the Rooftop Air Handler Graphic

And if I go back to status, you are
going to see a combination of keys

That I just used the default
PCM variable names

As well as some that I assigned
standard keys for or custom keys for

And some familiar system keys
that we've pre-engineered

Into the product such as occupancy
and heat/cool mode

All right, now that all of your devices
have been installed

You have the ability to
create your Air Systems

Your Schedules, your Areas, and when
we support chillers your chiller plants

With these Comm3 and 4 devices
so they'll be allowed to be added

As members to VAS and Area
just like any other device

And you see here I can
make my PCM a member

For my Air Handlers

And my spaces

I can assign my VAV boxes

Just like I could any device in SC

And better yet they are not
separated by protocol

Similar if I open TGP2 or TGE
(Tracer Graphics Editor)

I'll see these controllers
in each of those

For system custom programming
or custom graphics

That is how you install a Comm3/4 to
Tracer SC Bridge in the SC interface