Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
Introduction
1
1.1
1.2
1.3
2
2.1
2.2
Tutorial
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.3
3.3.1
3.3.2
3.3.3
4
4.1
4.2
4.3
4.4
4.5
4.6
5
5.1
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
7
7.1
7.2
7.3
7.4
7.5
8
8.1
8.2
8.3
8.4
8.5
8.6
9.1
9.2
10
10.1
10.2
10.3
11
11.1
11.2
11.3
11.4
11.5
12
12.1
13
13.1
13.2
13.3
13.4
13.5
14
14.1
14.2
14.3
14.4
14.5
14.6
14.7
14.8
14.9
14.10
Introduction
Topics
Purpose of This Guide
How This Guide is Organized
Typographical Conventions
1.1
1.2
Introduction
The Introduction part contains information on the purpose of this guide, how this
guide is organized, where to find more information, and information on regulatory
notices.
Tutorial
The Tutorial part contains a step-by-step description of how to carry out different
tasks. If you want more information, see WebHelp or the corresponding Building
Operation Guide.
The Tutorial part includes a case study for a fictional customer called University X.
You can decide if you want to follow the example or use the described procedures
as reference information. The case study in this tutorial is an example of a typical
way of configuring Building Operation for a customer. When reading through this
tutorial, you might not have access to the devices, programs, and other files that
are needed for the fictional customer University X. However, the purpose of having
a case study is to see the procedures put in context, so you see how the
procedures could be used when configuring Building Operation, devices, or
programs for your customer.
Note
The programs and files that are used for the fictional customer University X are
intended for training purposes only.
1.3
Typographical Conventions
Building Operation Guides use the following specially marked texts:
Tip
Helps you understand the benefits and capabilities of the product.
Note
Provides you with supplementary information.
Important
Alerts you to supplementary information that is essential to the completion of a
task.
Caution
Alerts you to a condition that can cause loss of data.
Warning
Alerts you to a condition that can cause product damage or physical harm.
Bold texts:
User interface items, such as property names and buttons, are written in bold, for
example "On the File menu, select New."
Example texts:
All the example related information is indicated by blue lines and bullets.
Additional Information
Topics
Where to Find Additional Information
Regulatory Notices
2 Additional Information
2.1 Where to Find Additional Information
2.1
Some StruxureWare Building Operation software products give you contextsensitive help by opening a WebHelp page that explains the view or dialog box you
have in focus. Some programs open up an overview page. From these pages, you
can follow the links to get more detailed information.
WebHelp contains all the technical information that is in the guides, specification
sheets, and installation instructions.
Finding information
The easiest way to find information on WebHelp is to search for it.
All technical information is gathered in one place, so you do not need to know
which guide, specification sheet, or installation instruction the information is in.
2 Additional Information
2.1 Where to Find Additional Information
2 Additional Information
2.2 Regulatory Notices
2.2
Regulatory Notices
UL 916 Listed products for the Unites States and Canada, Open
Class Energy Management Equipment.
Industry Canada
ICES-003
This is a Class B digital device that meets all requirements of the Canadian
Interference Causing Equipment Regulations.
Tutorial
Topics
University X
Requirements and Specifications
Focus of This Tutorial
3.1
University X
We are going to install Building Operation as the building management system for
University X. The university is a campus of buildings for which heating and cooling
are supplied from a Central Plant with an underground distribution system. The
case study focuses on the renovation of the Central Plant and the expansion of the
School of Business.
The heating plant consists of two boilers in parallel, each with their own inline
pumps. Much of the time only one boiler is required to meet the load but under
greater load, both boilers will operate at the same time. The flow from the two
boilers comes together in a common supply header. There is a line from the supply
header to the mechanical systems that require a source of hot water. This line has
two constant volume distribution pumps in parallel. Only one is required to meet
the load. The second is back-up and lead-lag is used to alternate which pump
runs. The water returning from the mechanical systems flows into the return header
where it can be pumped by the inline pumps through the boilers. There is a
common line between the supply header and the return header. When the inline
pumps are flowing at a rate that exceeds the distribution pump flow rate, the water
flow in the common line is from the supply header to the return header. When the
distribution pump is flowing at a rate that exceeds the combined inline pump flow
rates, flow in the common line is from the return header to the supply header. Each
boiler has its own self contained control system that interfaces with Building
Operation through a combination of binary electrical control and network variables.
The inline pumps are locally controlled by the self contained control system.
Note
The programs and files that are used for the fictional customer University X are
intended for training purposes only.
3.2
3.2.1
3.2.2
3.2.3
Specifications
You find specifications in the Building Operation specification sheets for Enterprise
Server, WorkStation, Project Configuration Server, PS-24V Power Supply,
Automation Server, BACnet b3867 Terminal Controllers, and BACnet
b3865/866/885-V VAV Controllers with Built-in Actuator.
3.3
3.3.1
The Automation Server called CPlant AS controls the Cooling Plant and Heating
Plant.
CPlant AS has the following folder structure:
In this tutorial, no programs need to be present in the project database on the offsite computer.
3.3.2
3.3.3
Topics
Logging on to WorkStation for Projects
Opening a Project
Creating a BACnet Interface
Creating a BACnet MS/TP Network
Configuring the MS/TP Network for b3 Communication
Creating a Folder
Our Example
In this chapter, you prepare the Automation Server to function as the BACnet
interface and create the MS/TP network so that b3 BACnet devices can be added
for controlling the East Wing of the School of Business.
You first log on to WorkStation for Projects on the off-site computer and open the
University X Project. You then create the BACnet interface and the MS/TP network.
Additionally, you create a folder structure in the System Tree pane to ensure that
the network is organized to maximize operating and engineering efficiency, such as
cloning multiple Air Handling Unit controllers and Variable Air Volume controllers.
4.1
Note
The first time you log on to WorkStation for Projects you need to use
the administrator user account to create a project user account. For
more information, see the Creating a Project Configuration Server
User Account topic on WebHelp.
3. In the Server box, select the hypertext transfer protocol you want to use and
then enter a server name or an IP address. In this example, click HTTPS
and then enter localhost.
4. Select Remember me to have WorkStation for Projects remember your
settings.
5. Click Log on.
4.2
Opening a Project
You open a project to configure a project or to deploy a project to a server.
For more information, see the Projects topic on WebHelp.
In this example, you open the University X Project on the off-site computer.
To open a project
1. In WorkStation for Projects, in the WorkStation for Projects - Projects
view, select the project that you want to open. In this example, select
University X Project.
2. On the toolbar, click the Open Project button
4.3
In this example,
5. Click Next.
Continued on next page
Note
If you enter an Instance ID manually, you must ensure that it is
globally unique among all the BACnet devices on the
internetwork (that is, among all the devices that it can
communicate with).
7. In the Network ID box, enter 1, which is the universal standard for all BACnet
IP communications.
8. Click Create.
4.4
In this example,
4. Click Next.
Continued on next page
In
6. In the MAC address box, enter the number that represents the Automation
Server's address on the MS/TP network. In this example, enter 0.
7. In the RS-485 port box, enter the location of the serial port RS485-COMA
or RS485-COMB. In this example, enter ...University X
ES1/Servers/CPlant AS/System/Ports/Serial/RS485-COMA.
8. Click Create.
4.5
In
4. In the Maximum master box, enter the highest node ID that will be used on
the MS/TP network and allow for adding future devices. In this example,
enter 10.
5. Click OK.
4.6
Creating a Folder
You create folders to organize your Building Operation database.
In this example, you create a folder named AHU_01 in the Automation Server. This
folder will contain the programs, schedules, and values for the b3 BACnet device
that will serve as AHU controller.
To create a folder
1. In WorkStation, in the System Tree pane, select the folder, server, or
network where you want to create the folder. In this example,
select ...University X ES1/Servers/CPlant AS.
2. On the File menu, point to New and then click Folder.
3. In the Name box, type a name for the folder.
AHU_01.
4. Click Create.
For this example, repeat the procedure to create the following folder structure in
the Automation Server:
Table: CPlant AS Folders
Name
Location
Programs
...University X ES1/Servers/CPlant
AS/AHU_01
Schedules
...University X ES1/Servers/CPlant
AS/AHU_01
Continued
Name
Location
Values
...University X ES1/Servers/CPlant
AS/AHU_01
VAV_01
...University X ES1/Servers/CPlant
AS/AHU_01
Programs
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01
Values
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01
Topics
Creating a b3 BACnet Device
Our Example
In this chapter, you create the b3 BACnet devices on the MS/TP Network for
operation of the Air Handling Unit AHU_01 and control of the Variable Air Volume
unit VAV_01_01. The physical devices are connected to the network at the time
you deploy the Automation Server.
5.1
Note
The b3 object display Name is limited to 16 characters
consisting solely of letters, digits, and underscores.
4. Click Next.
Continued on next page
6. In the BACnet name box, type a BACnet name. Do not type a name if you
want it assigned for you. In this example, type AHU_01.
Note
The BACnet name is limited to 16 characters consisting solely
of letters, digits, and underscores.
7. In the Model name box, select the model name.
b3867.
8. In the Infinet ID box, enter the Infinet ID for the b3 BACnet device.
example, enter 1.
In this
Note
The Infinet ID is required for communication between different
devices. Each device is identified by its unique ID number.
9. Click Create.
Now that the device is created, you need to commission the device. For more
information, see section 14.7 Commissioning a b3 BACnet Device on page 204.
For this example, repeat the procedure to create a VAV controller named
VAV_01_01. Use the following settings:
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP Network
Name
VAV_01_01
Instance ID
4011
BACnet name
VAV_01_01
Model name
b3866
Infinet ID
Serial number
Null
Topics
Creating a b3 BACnet Device Analog Input Point
Configuring the COV Increment and the Unit for a b3
BACnet Device Analog Input Point
Creating a b3 BACnet Device Analog Output Point
Configuring the COV Increment and the Unit for a b3
BACnet Device Analog Output Point
Configuring the Electrical Scale and the Engineering Scale
for a b3 BACnet Device Analog Output Point
Creating a b3 BACnet Device Analog Value
Configuring the COV Increment and the Unit for a b3
BACnet Device Analog Value
Creating a b3 BACnet Device Digital Input Point
Creating a b3 BACnet Device Digital Output Point
Creating a b3 BACnet Device Digital Value
Creating a b3 BACnet Device Multistate Pulsed Output Point
Our Example
In this chapter, you create all the b3 BACnet input points, output points, and values
that will reside within the Air Handling Unit controller and also the Variable Air
Volume controller. The data from these points and values will be mirrored up to
values that reside within the Automation Server. The Automation Server will analyze
this data and perform logical decisions before passing the data back to the b3
BACnet devices that are controlling the system.
6.1
5. In the Name box, type a name for the analog input point.
type Dat.
In this example,
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Next.
9. In the Channel box, enter the input channel you want the point to read from.
In this example, enter channel 1.
10. In the Electrical type box, select the electrical type on the input point.
this example, select Temp(DEGC) or Temp(DEGF).
In
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
VAVTemp
Channel
Electrical type
Temp(DEGC) or Temp(DEGF)
6.2
In this
.
Continued on next page
8. Click OK.
9. In the COV increment box, enter the minimum change in the Value property
that causes a COV notification to be sent. In this example, enter 1.
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
VAVTemp
Unit
C (F)
COV increment
6.3
5. In the Name box, type a name for the analog output point.
type VlvPosn.
In this example,
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Next.
Continued on next page
9. In the Channel box, enter the output channel you want the point to write to.
In this example, enter channel 6.
10. In the Electrical type box, select the electrical type on the output point.
this example, select Voltage.
In
6.4
In this
.
Continued on next page
8. Click OK.
Continued on next page
9. In the COV increment box, enter the minimum change in the Value property
that causes a COV notification to be sent. In this example, enter 2.
6.5
In this
5. Under Conversion Settings, in the Electrical scale top box, enter the
highest electrical value for the analog output point. In this example, enter 10
(Volt).
6. In the Electrical scale bottom box, enter the lowest electrical value for the
analog output point. In this example, enter 0 (Volt).
7. In the Engineering scale top box, enter the highest engineering value for
the analog output point. In this example, enter 100.
Continued on next page
8. In the Engineering scale bottom box, enter the lowest engineering value
for the analog output point. In this example, enter 0.
9. Click OK.
6.6
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Create.
For this example, repeat the procedure to create the other analog values for the
AHU_01 and VAV_01_01 b3 BACnet devices. Use the following settings:
Table: AHU_01 b3 BACnet Device Analog Value
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application
Name
StPrSP
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Continued
Component
Name
Setting
DmprPosn
TermLoad
6.7
In this
.
Continued on next page
8. Click OK.
9. In the COV increment box, enter the minimum change in the Value property
that causes a COV notification to be sent. In this example, enter 1.
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application
Name
StPrSP
Unit
Pa (inH2O)
COV increment
0.05
Component
Setting
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
DmprPosn
Unit
COV increment
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
TermLoad
Unit
COV increment
6.8
5. In the Name box, type a name for the digital input point.
type FanStatus.
In this example,
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Next.
Continued on next page
9. In the Channel box, enter the input channel you want the point to read from.
In this example, enter channel 2.
6.9
5. In the Name box, type a name for the digital output point.
type FanCmd.
In this example,
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Next.
9. In the Channel box, enter the output channel you want the point to write to.
In this example, enter channel 1.
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
Light
Channel
6.10
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
6. Click Next.
Continued on next page
8. Click Create.
For this example, repeat the procedure to create the other digital values in the
AHU_01 and VAV_01_01 b3 BACnet devices. Use the following settings:
Table: AHU_01 b3 BACnet Device Digital Values
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application
Name
OccCmd
FanAlarm
Component
Setting
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
OccStatus
OccCmd
Ovrd
6.11
5. In the Name box, type a name for the multistate pulsed output point.
example, type DmprCmd.
In this
You can type more than 16 characters for b3 object display names and are
not restricted to using only letters, digits, and underscores.
Continued on next page
6. Click Next.
7. Under Instance ID, generate or enter a BACnet Instance ID:
Click Automatically generated to have the server generate a BACnet
Instance ID for you (Recommended).
Click Manually entered to manually enter a BACnet Instance ID, and
then type an appropriate Instance ID for the BACnet object.
In this example, click Automatically generated.
If you enter an Instance ID manually, you must ensure it is unique within the
application for this type.
8. Click Next.
Continued on next page
9. In the Channel box, enter the channel where you want to put the multistate
pulsed output. In this example, enter channel 1.
Topics
Creating a Server Analog Value
Configuring the Value and the Unit for a Server Analog
Value
Creating a Server Digital Value
Creating a BACnet Value
Configuring a BACnet Analog Value
Our Example
In this chapter, you create all the server values and BACnet values that reside in the
Automation Server within the BACnet Interface. The server values are mirrored from
the values in the b3 BACnet devices. Programs in the Automation Server perform
logical decisions to these values and then pass that data down to the BACnet
values that reside in the Automation Server within the BACnet Interface. Those
values are then passed down to the b3 BACnet devices.
7.1
5. Click Create.
For this example, repeat the procedure to create the required analog values in the
Automation Server AHU_01/VAV_01 folder. Use the following settings:
Setting
Location
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01/Values
Name
DmprPosn_AS
TermLoad_AS
7.2
To configure the value and the unit for a server analog value
1. In WorkStation, in the System Tree pane, select the server analog value you
want to configure. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/Values/VlvPosn_AS.
2. On the File menu, click Properties.
3. Under Status Information, click the Configure button
6. Click OK.
7. Click OK.
For this example, repeat the procedure to configure the analog values in the
Automation Server AHU_01/VAV_01 folder. Use the following settings:
Table: Analog Value in the Automation Server AHU_01/VAV_01 Folder
DmprPosn_AS
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01/Values
Name
DmprPosn_AS
Unit
Setting
Location
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01/Values
Continued
Component
Setting
Name
TermLoad_AS
Unit
7.3
5. Click Create.
7.4
5. Click Next.
Continued on next page
7. In the Command priority retain level box, select one of the following
options to configure the warm start and cold start settings for a command
priority array:
Warm start: The variable retains the last value set by a user or
application. However, the variable reverts to the default value for a cold
start.
Cold start: The variable retains the last value set by a user or application
for a warm start or cold start.
No: The variable reverts to the default value upon a restart.
In this example, select Cold start.
8. Click Create.
For this example, repeat the procedure to create the remaining BACnet analog and
digital values in the same folder. Use the following settings:
Table: BACnet Analog Values
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
Type
Continued
Component
Setting
Name
AHU_01_StPrSP
Cold start
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
Type
Name
AHU_01_VAVOccCmd
AHU_01_VentReq
AHU_01_OccCmd
Cold start
7.5
In this
.
Continued on next page
7. In the Unit box, enter the unit that matches the unit of the input and output
points on the Automation Server IO module. In this example, enter C (F).
8. Click OK to return to the Basic tab.
9. Click OK.
For this example, repeat the procedure to configure the other BACnet analog value
in the same folder. Use the following settings:
Table: BACnet Analog Value
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
Name
AHU_01_StPrSP
Unit
Pa (inH2O)
Creating Programs in
Automation Server and b3
BACnet Devices
Topics
Creating a Function Block Program
Importing Function Block Program Code
Creating a Script Program
Importing Script Program Code
Creating a b3 Script Program
Importing Script Program Code
Our Example
In this chapter, you create all the Script and Function Block programs. Program
code is then imported to all the application programs that are needed to control the
system for the East Wing. Some programs are mirror programs that pass data from
the b3 BACnet devices up to the Automation Server and then back down to the b3
BACnet devices. The other programs are logical programs that apply logical
decisions depending on the data it receives.
8.1
4. In the Name box, type a name for the function block program.
example, type Occupancy.
In this
5. Click Create.
8.2
Tip
When a Menta file is imported, TSCH blocks and ALARM blocks
are removed, AI/DI blocks are converted to RI/BI blocks, and
AO/DO blocks are converted to RO/BO blocks. As a result of
these conversions, you may need to make adjustments to the
imported Menta code.
04-16030-01-en, December 2014
8.3
5. Click Create.
In this example, repeat the procedure to create the following script programs:
Setting
Location
...University X ES1/Servers/CPlant
AS/AHU_01/Programs
Name
StPrSP
Mirror_AHU
Setting
Location
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01/Programs
Name
Mirror_VAV
8.4
Tip
When a Plain English .txt file is imported, you have to load the file
and complete a conversion process. As a result of these
conversions, you may need to make adjustments to the
imported Script program code.
In this example, repeat the procedure to import script .txt files to the following
Script programs:
Table: Script Programs in the Automation Server AHU_01 Folder
Component
Setting
Program location
...University X ES1/Servers/CPlant
AS/AHU_01/Programs
Program name
StPrSP
Mirror_AHU
Continued
Component
Setting
File location
File name
StPrSP.txt
Mirror_AHU.txt
Setting
Program location
...University X ES1/Servers/CPlant
AS/AHU_01/VAV_01/Programs
Program name
Mirror_VAV
File location
File name
Mirror_VAV.txt
8.5
In this example,
5. Click Next.
Continued on next page
7. Click Create.
For this example, repeat the procedure to create the following b3 script programs:
Table: b3 Script Programs in the AHU_01 b3 BACnet Device
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application
Name
CoolingCoil
FanControl
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Continued
Component
Name
Setting
Mirror
Occupancy
CalcDmprPosn
CalcTermLoad
8.6
Tip
When a Plain English .txt file is imported, you have to load the file
and complete a conversion process. As a result of these
conversions, you may need to make adjustments to the
imported Script program code.
In this example, repeat the procedure to import program code to the following
Script programs:
Table: Script Programs in the AHU_01 b3 BACnet Device
Component
Setting
Program location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application
Program name
CoolingCoil
FanControl
Continued
Component
Setting
File location
File name
CoolingCoil.txt
FanControl.txt
Setting
Program location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Program name
Mirror
Occupancy
CalcDmprPosn
CalcTermLoad
File location
File name
Topics
Creating a Digital Schedule
Configuring a Schedule as a Shadow
Our Example
In this chapter, you create a digital schedule named Schedule and configure it as a
shadow schedule of the Cooling Plant Enable Schedule to control the Cooling
Application for AHU_01. The Occupancy program for AHU_01 in the Automation
Server will use the value of the Schedule to control the Air Handling Unit.
9.1
5. Click Create.
Now you can add events to the digital schedule and bind it to a digital value.
9.2
4. Click OK.
10
Topics
Binding Values Using a Binding Template
Importing a Solution
Binding Values Using a Binding Template
Our Example
In this chapter, you first create all the bindings necessary to establish data flow in
and out of programs in the b3 BACnet devices. For engineering efficiency, you use
the Default name matching template to establish the data flow. You then import five
custom binding templates. You use the following four templates to create all the
bindings necessary to establish data flow between the Automation Server and the
b3 BACnet devices:
Data from AS to AHU: Data flow from the Automation Server to the Air
Handling Unit controller mirror program
Data from AS to VAV: Data flow from the Automation Server to the Variable Air
Volume controller mirror program
Data from AHU to AS: Data flow from the Air Handling Unit controller to the
Automation Server
Data from VAV to AS: Data flow from the Variable Air Volume controller to the
Automation Server
10.1
Tip
When creating bindings, follow the recommended general guidelines: create
bindings between Inputs and Outputs only and do not create bindings to
Public Signals.
For more information, see the Binding Templates topic on WebHelp.
In this example, you create the bindings between the CalcDmprPosn program in the
VAV_01_01 b3 BACnet device and b3 BACnet values in the same device. You use
the Default name matching template to create the required bindings. The bindings
you create are internal to the device.
3. In the binding point browser, drag the object or folder to the binding template
that you want to apply. In this example, drag ...University X
ES1/Servers/CPlant AS/BACnet Interface/MSTP
Network/VAV_01_01/Application to the Default name matching
template.
5. Click OK.
Continued on next page
Tip
To ensure data flow is occurring as intended, use the Watch pane to view
values and monitor changes.
CalcDmprPosn Program in the VAV_01_01 Device
Table: Results Verification CalcDmprPosn Program Bindings
Binding Point
Binding
Input - OccStatus
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccStatus
/Value
Output - DmprPosn
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/DmprPosn
/Value
Binding Point
Binding
For this example, repeat the procedure to create the other required internal
bindings for the following programs in the VAV_01_01 and AHU_01 b3 BACnet
devices:
CalcTermLoad Program in the VAV_01_01 Device
Create the bindings for the ...University X ES1/Servers/CPlant AS/BACnet
Interface/MSTP Network/VAV_01_01/Application/CalcTermLoad
program:
Drag ...University X ES1/Servers/CPlant AS/BACnet Interface/MSTP
Network/VAV_01_01/Application to the Default name matching
template.
Table: Results Verification CalcTermLoad Program Bindings
Binding Point
Binding
Input - OccStatus
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccStatus
/Value
Output - TermLoad
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/TermLoad
/Value
Binding
Input - VAVOccCmd_AS
Output - OccCmd
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccCmd/
Value
Binding
Input - OccCmd
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccCmd/
Value
Input - Ovrd
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/Ovrd/Valu
e
Output - Light
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/Light/Valu
e
Output - OccStatus
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccStatus
/Value
Binding
Input - DatSp_AS
Input - OccCmd_AS
Input - StPrSp_AS
Input - VentReq_AS
Output - DatSp
.../BACnet Interface/MSTP
Network/AHU_01/Application/DatSP/Value
Output - OccCmd
.../BACnet Interface/MSTP
Network/AHU_01/Application/OccCmd/Val
ue
Output - StPrSp
.../BACnet Interface/MSTP
Network/AHU_01/Application/StPrSP/Value
Output - VentReq
.../BACnet Interface/MSTP
Network/AHU_01/Application/VentReq/Valu
e
Binding Point
Binding
Binding
Input - Dat
.../BACnet Interface/MSTP
Network/AHU_01/Application/Dat/Value
Input - DatSP
.../BACnet Interface/MSTP
Network/AHU_01/Application/DatSP/Value
Input - FanStatus
.../BACnet Interface/MSTP
Network/AHU_01/Application/FanStatus/Val
ue
Input - OccCmd
.../BACnet Interface/MSTP
Network/AHU_01/Application/OccCmd/Val
ue
Output - VlvPosn
.../BACnet Interface/MSTP
Network/AHU_01/Application/VlvPosn/Valu
e
Binding
Input - FanStatus
.../BACnet Interface/MSTP
Network/AHU_01/Application/FanStatus/Val
ue
Input - OccCmd
.../BACnet Interface/MSTP
Network/AHU_01/Application/OccCmd/Val
ue
Output - FanAlarm
.../BACnet Interface/MSTP
Network/AHU_01/Application/FanAlarm/Val
ue
Continued
Binding Point
Binding
Output - FanCmd
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP
Network/AHU_01/Application/FanCmd/Valu
e
10.2
Importing a Solution
You import a solution that was created or modified on another Building Operation
server. You can also use the standard copy and paste method to copy solutions to
other file locations on the same server.
For more information, see the Import and Export Overview topic on WebHelp.
In this example, you import a file that contains five custom binding templates to be
used to create bindings for data flow between the Automation Server and the b3
BACnet devices.
To import a solution
1. In WorkStation, in the System Tree pane or List View, select a location
where you want to import a solution. In this example, select ...University
X ES1/System/Binding Templates.
2. On the File menu, click Import.
3. In the Open dialog box, select the file and click Open. In this example,
select ...\Desktop\student desktop files\Project 4\Template
Imports\Binding Templates Project 4.xml.
Continued on next page
4. Click Import.
10.3
Tip
When creating bindings, follow the recommended general guidelines: create
bindings between Inputs and Outputs only and do not create bindings to
Public Signals.
For more information, see the Binding Templates topic on WebHelp.
In this example, you create the bindings for data flow between the Automation
Server and the Mirror program in the AHU_01 b3 BACnet device. You use the
custom binding template named Data from AS to AHU to create the required
bindings.
3. In the binding point browser, drag the object or folder to the binding template
that you want to apply. In this example, drag ...University X
ES1/Servers/CPlant AS to the Data from AS to AHU custom binding
template.
5. Click OK.
Continued on next page
Tip
To ensure data flow is occurring as intended, use the Watch pane to view
values and monitor changes.
Mirror Program in the AHU_01 Device
Table: Results Verification Mirror Program Bindings
Binding Point
Binding
Input - DatSp_AS
.../BACnet
Interface/Application/AHU_01_DatSP/Value
Input - OccCmd_AS
.../BACnet
Interface/Application/AHU_01_OccCmd/Val
ue
Input - StPrSp_AS
.../BACnet
Interface/Application/AHU_01_StPrSp/Value
Continued
Binding Point
Binding
Input - VentReq_AS
.../BACnet
Interface/Application/AHU_01_VentReq/Val
ue
For this example, repeat the procedure to create the other required bindings for
data flow between the Automation Server and the VAV_01_01 and AHU_01 b3
BACnet devices.
Mirror Program in the VAV_01_01 Device
Create the bindings for data flow between the Automation Server and
the ...University X ES1/Servers/CPlant AS/BACnet Interface/MSTP
Network/VAV_01_01/Application/Mirror program:
Drag ...University X ES1/Servers/CPlant AS to the Data from AS to
VAV custom binding template.
Table: Results Verification Mirror Program Bindings
Binding Point
Binding
Input - VAVOccCmd_AS
.../BACnet
Interface/Application/AHU_01_VAVOccCmd
/Value
Binding
Input - VlvPosn
.../BACnet Interface/MSTP
Network/AHU_01/Application/VlvPosn/Valu
e
Output - VlvPosn_AS
.../AHU_01/Values/VlvPosn_AS/Value
Binding
Input - DmprPosn
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/DmprPosn
/Value
Input - OccStatus
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/OccStatus
/Value
Input - TermLoad
.../BACnet Interface/MSTP
Network/VAV_01_01/Application/TermLoad
/Value
Output - DmprPosn_AS
.../AHU_01/VAV_01/Values/DmprPosn_AS/
Value
Output - OccStatus_AS
.../AHU_01/VAV_01/Values/OccStatus_AS/
Value
Output - TermLoad_AS
.../AHU_01/VAV_01/Values/TermLoad_AS/
Value
11
Duplicating a b3 BACnet
Device
Topics
Creating a b3 BACnet Device
Merging Copied Device Content in a b3 BACnet Device
Copying a Folder or Object
Renaming a Folder or Object
Binding Values Using a Binding Template
Our Example
In this chapter, you create an additional b3 BACnet device using the Merge Copied
Device Content feature. The device will serve as a second VAV controller for
AHU_01. In the Automation Server, within the AHU_01 folder, you create a new
folder (VAV_02) using a copy and paste operation. By using the imported custom
binding templates, you create all the necessary bindings needed to establish data
flow between the Automation Server and the second VAV controller.
11.1
Note
The b3 object display Name is limited to 16 characters
consisting solely of letters, digits, and underscores.
4. Click Next.
Continued on next page
6. In the BACnet name box, type a BACnet name. Do not type a name if you
want it assigned for you. In this example, type VAV_01_02.
Note
The BACnet name is limited to 16 characters consisting solely
of letters, digits, and underscores.
7. In the Model name box, select the model name.
b3866.
8. In the Infinet ID box, enter the Infinet ID for the b3 BACnet device.
example, enter 3.
In this
Note
The Infinet ID is required for communication between different
devices. Each device is identified by its unique ID number.
9. Click Create.
Now that the device is created, you need to commission the device. For more
information, see section 14.7 Commissioning a b3 BACnet Device on page 204.
11.2
11.3
11.4
Note
When changing the name of a folder or server, you also have to reconfigure users
and user groups path permissions to this server or folder. For more information,
see the Path Permissions topic on WebHelp.
Note
You cannot change the name of a domain that is shared between servers.
For more information, see the Move, Copy, Paste, Rename, and Delete topic on
WebHelp.
In this example, you change the name of the copied folder from VAV_01_copy to
VAV_02.
In this example,
4. Click OK.
11.5
Tip
When creating bindings, follow the recommended general guidelines: create
bindings between Inputs and Outputs only and do not create bindings to
Public Signals.
For more information, see the Binding Templates topic on WebHelp.
In this example, you create the output bindings and correct the input bindings for
the Mirror_VAV program in the Automation Server AHU_01/VAV_02 folder. You use
the custom binding template named Data from VAV to AS to create and correct
the bindings. The bindings are required for data flow between the program and the
VAV_01_02 b3 BACnet device. The bindings for the Mirror program in the
VAV_01_02 device do not need to be corrected.
3. In the binding point browser, drag the object or folder to the binding template
that you want to apply. In this example, drag ...University X
ES1/Servers/CPlant AS to the Data from VAV to AS custom binding
template.
5. Click OK.
Continued on next page
Tip
To ensure data flow is occurring as intended, use the Watch pane to view
values and monitor changes.
Mirror_VAV Program in the Automation Server AHU_01/VAV_02 Folder
Table: Results Verification Mirror_VAV Program Bindings
Binding Point
Binding
Input DmprPosn
.../BACnet Interface/MSTP
Network/VAV_01_02/Application/DmprPosn
/Value
Input OccStatus
.../BACnet Interface/MSTP
Network/VAV_01_02/Application/OccStatus
/Value
Input TermLoad
.../BACnet Interface/MSTP
Network/VAV_01_02/Application/TermLoad
/Value
Continued
Binding Point
Binding
Output DmprPosn_AS
.../AHU_01/VAV_02/Values/DmprPosn_AS/
Value
Output OccStatus_AS
.../AHU_01/VAV_02/Values/OccStatus_AS/
Value
Output TermLoad_AS
.../AHU_01/VAV_02/Values/TermLoad_AS/
Value
12
Topics
Binding Values Using a Binding Template
Our Example
In this chapter, you create all the bindings necessary to establish data flow internally
in the Automation Server. For engineering efficiency, you use the following custom
binding template to establish the data flow:
AS Programs: Data flow into and out of AS programs
12.1
Tip
When creating bindings, follow the recommended general guidelines: create
bindings between Inputs and Outputs only and do not create bindings to
Public Signals.
For more information, see the Binding Templates topic on WebHelp.
In this example, you create the bindings for the Occupancy program in the
Automation Server AHU_01 folder. You use the custom binding template named
AS Programs to create the required bindings. The created bindings are internal to
the Automation Server.
3. In the binding point browser, drag the object or folder to the binding template
that you want to apply. In this example, drag ...University X
ES1/Servers/CPlant AS to the AS Programs custom binding template.
5. Click OK.
Continued on next page
Tip
To ensure data flow is occurring as intended, use the Watch pane to view
values and monitor changes.
Occupancy Program in the Automation Server AHU_01 Folder
Table: Results Verification Occupancy Program Bindings
Binding Point
Binding
Input - Schedule
.../AHU_01/Schedules/Schedule/Value
Input - VAV_01_OccStatus
.../AHU_01/VAV_01/Programs/Mirror_VAV/
OccStatus_AS
Input VAV_02_OccStatus
.../AHU_01/VAV_02/Programs/Mirror_VAV/
OccStatus_AS
Output OccCmd
.../BACnet
Interface/Application/AHU_01_OccCmd/Val
ue
Continued
Binding Point
Binding
Output VAVOccCmd
.../BACnet
Interface/Application/AHU_01_VAVOccCmd
/Value
Output VentReq
.../BACnet
Interface/Application/AHU_01_VentReq/Val
ue
For this example, repeat the procedure to create the required bindings for the other
supervisory programs in the Automation Server. Use the following settings:
DatSP Program in the Automation Server AHU_01 Folder
Create the bindings for the ...University X ES1/Servers/CPlant
AS/AHU_01/Programs/DatSP program:
Drag ...University X ES1/Servers/CPlant AS to the AS Programs
custom binding template.
Table: Results Verification DatSP Program Bindings
Binding Point
Binding
Input - VAV_01_TermLoad
.../AHU_01/VAV_01/Programs/Mirror_VAV/
TermLoad_AS
Input - VAV_02_TermLoad
.../AHU_01/VAV_02/Programs/Mirror_VAV/
TermLoad_AS
Output - DatSp
.../BACnet
Interface/Application/AHU_01_DatSP/Value
Binding
Input - VAV_01_DmprPosn
.../AHU_01/VAV_01/Programs/Mirror_VAV/
DmprPosn_AS
Input - VAV_02_DmprPosn
.../AHU_01/VAV_02/Programs/Mirror_VAV/
DmprPosn_AS
Output - StPrSp
.../BACnet
Interface/Application/AHU_01_StPrSP/Valu
e
13
Topics
Creating a b3 BACnet Device
Merging Copied Device Content in a b3 BACnet Device
Copying a Folder or Object
Renaming a Folder or Object
Binding Values Using a Binding Template
Our Example
In this chapter, you use all the procedures from the previous chapters. The primary
focus of this chapter is engineering efficiency on how to create multiple Air Handling
Unit controllers and Variable Air Volume controllers within a timely fashion. At the
conclusion of this chapter, you will have two Air Handling Unit controllers that will
each be associated with two Variable Air Volume controllers.
13.1
Note
The b3 object display Name is limited to 16 characters
consisting solely of letters, digits, and underscores.
4. Click Next.
Continued on next page
6. In the BACnet name box, type a BACnet name. Do not type a name if you
want it assigned for you. In this example, type AHU_02.
Note
The BACnet name is limited to 16 characters consisting solely
of letters, digits, and underscores.
7. In the Model name box, select the model name.
b3867.
8. In the Infinet ID box, enter the Infinet ID for the b3 BACnet device.
example, enter 4.
In this
Note
The Infinet ID is required for communication between different
devices. Each device is identified by its unique ID number.
9. Click Create.
Now that the device is created, you need to commission the device. For more
information, see section 14.7 Commissioning a b3 BACnet Device on page 204.
For this example, create two additional VAV controllers, named VAV_02_01 and
VAV_02_02. Use the following settings:
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP Network
Name
VAV_02_01
Instance ID
4014
BACnet name
VAV_02_01
Model name
b3866
Infinet ID
Serial number
Null
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP Network
Name
VAV_02_02
Instance ID
4015
BACnet name
VAV_02_02
Model name
b3866
Infinet ID
Serial number
Null
13.2
For this example, repeat the procedure to copy the contents of the VAV_01_01 b3
BACnet device and merge the copied content with the VAV_02_01 device and also
with the VAV_02_02 device. Use the following settings:
Table: Copying the VAV_01_01 Device and Merging the Copied Device Content
with the VAV_02_01 and VAV_02_02 Devices
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/MSTP Network
Source device
VAV_01_01
Target devices
VAV_02_01
VAV_02_02
13.3
Settings
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
Source values
AHU_01_DatSP
AHU_01_OccCmd
AHU_01_StPrSP
AHU_01_VAVOccCmd
AHU_01_VentReq
Target folder
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
13.4
Note
When changing the name of a folder or server, you also have to reconfigure users
and user groups path permissions to this server or folder. For more information,
see the Path Permissions topic on WebHelp.
Note
You cannot change the name of a domain that is shared between servers.
For more information, see the Move, Copy, Paste, Rename, and Delete topic on
WebHelp.
In this example, you change the name of the copied folder from AHU_01_copy to
AHU_02.
In this example,
4. Click OK.
For this example, repeat the procedure to rename the copied BACnet values. Use
the following settings:
Table: Renaming Copied BACnet Values
Component
Setting
Location
...University X ES1/Servers/CPlant
AS/BACnet Interface/Application
Old names
AHU_01_DatSP_copy
AHU_01_OccCmd_copy
AHU_01_StPrSP_copy
AHU_01_VAVOccCmd_copy
AHU_01_VentReq_copy
Continued
Component
New names
Setting
AHU_02_DatSP
AHU_02_OccCmd
AHU_02_StPrSP
AHU_02_VAVOccCmd
AHU_02_VentReq
13.5
Tip
When creating bindings, follow the recommended general guidelines: create
bindings between Inputs and Outputs only and do not create bindings to
Public Signals.
For more information, see the Binding Templates topic on WebHelp.
In this example, you correct the input bindings for the Mirror program in the AHU_02
b3 BACnet device. You use the custom binding template named Data from AS to
AHU to correct the bindings. The output bindings do not need to be corrected.
3. In the binding point browser, drag the object or folder to the binding template
that you want to apply. In this example, drag ...University X
ES1/Servers/CPlant AS to the Data from AS to AHU custom binding
template.
5. Click OK.
Continued on next page
Tip
To ensure data flow is occurring as intended, use the Watch pane to view
values and monitor changes.
Mirror Program in the AHU_02 Device
Table: Results Verification Mirror Program Bindings
Binding Point
Binding
Input DatSp_AS
.../BACnet
Interface/Application/AHU_02_DatSP/Value
Input OccCmd_AS
.../BACnet
Interface/Application/AHU_02_OccCmd/Val
ue
Input StPrSp_AS
.../BACnet
Interface/Application/AHU_02_StPrSp/Value
Input VentReq_AS
.../BACnet Interface/Application/AHU_02
_VentReq/Value
Binding Point
Binding
For this example, repeat the procedure to create the other required bindings for
data flow between the Automation Server and the VAV_02_01, VAV_02_02, and
AHU_02 devices.
Mirror Program in the VAV_02_01 Device
Create the bindings for data flow between the Automation Server and
the ...University X ES1/Servers/CPlant AS/BACnet Interface/MSTP
Network/VAV_02_01/Application/Mirror program:
Drag ...University X ES1/Servers/CPlant AS to the Data from AS to
VAV custom binding template.
Table: Results Verification Mirror Program Bindings
Binding Point
Binding
Input - VAVOccCmd_AS
.../BACnet
Interface/Application/AHU_02_VAVOccCmd
/Value
Binding
Input - VAVOccCmd_AS
.../BACnet
Interface/Application/AHU_02_VAVOccCmd
/Value
Binding
Input - DmprPosn
.../BACnet Interface/MSTP
Network/VAV_02_01/Application/DmprPosn
/Value
Continued
Binding Point
Binding
Input - OccStatus
.../BACnet Interface/MSTP
Network/VAV_02_01/Application/OccStatus
/Value
Input - TermLoad
.../BACnet Interface/MSTP
Network/VAV_02_01/Application/TermLoad
/Value
Output - DmprPosn_AS
.../AHU_02/VAV_01/Values/DmprPosn_AS/
Value
Output - OccStatus_AS
.../AHU_02/VAV_01/Values/OccStatus_AS/
Value
Output - TermLoad_AS
.../AHU_02/VAV_01/Values/TermLoad_AS/
Value
Binding
Input - DmprPosn
.../BACnet Interface/MSTP
Network/VAV_02_02/Application/DmprPosn
/Value
Input - OccStatus
.../BACnet Interface/MSTP
Network/VAV_02_02/Application/OccStatus
/Value
Input - TermLoad
.../BACnet Interface/MSTP
Network/VAV_02_02/Application/TermLoad
/Value
Output - DmprPosn_AS
.../AHU_02/VAV_02/Values/DmprPosn_AS/
Value
Output - OccStatus_AS
.../AHU_02/VAV_02/Values/OccStatus_AS/
Value
Output - TermLoad_AS
.../AHU_02/VAV_02/Values/TermLoad_AS/
Value
Create the bindings for data flow between the AHU_02 b3 BACnet device and
the ...University X ES1/Servers/CPlant
AS/AHU_02/Programs/Mirror_AHU program:
Drag ...University X ES1/Servers/CPlant AS to the Data from AHU to
AS custom binding template.
In the Confirm Bindings dialog box, clear Bind for the Enabled binding
point.
Table: Results Verification Mirror_AHU Program Bindings
Binding Point
Binding
Input - VlvPosn
.../BACnet Interface/MSTP
Network/AHU_02/Application/VlvPosn/Valu
e
Output - VlvPosn_AS
.../AHU_02/Values/VlvPosn_AS/Value
Binding
Input - Schedule
.../AHU_02/Schedules/Schedule/Value
Input - VAV_01_OccStatus
.../AHU_02/VAV_01/Programs/Mirror_VAV/
OccStatus_AS
Input - VAV_02_OccStatus
.../AHU_02/VAV_02/Programs/Mirror_VAV/
OccStatus_AS
Output - OccCmd
.../BACnet
Interface/Application/AHU_02_OccCmd/Val
ue
Output - VAVOccCmd
.../BACnet
Interface/Application/AHU_02_VAVOccCmd
/Value
Output - VentReq
.../BACnet
Interface/Application/AHU_02_VentReq/Val
ue
Binding
Input - VAV_01_TermLoad
.../AHU_02/VAV_01/Programs/Mirror_VAV/
TermLoad_AS
Input - VAV_02_TermLoad
.../AHU_02/VAV_02/Programs/Mirror_VAV/
TermLoad_AS
Output - DatSp
.../BACnet
Interface/Application/AHU_02_DatSP/Value
Binding
Input - VAV_01_DmprPosn
.../AHU_02/VAV_01/Programs/Mirror_VAV/
DmprPosn_AS
Input - VAV_02_DmprPosn
.../AHU_02/VAV_02/Programs/Mirror_VAV/
DmprPosn_AS
Output - StPrSp
.../BACnet
Interface/Application/AHU_02_StPrSP/Valu
e
14
Deploying Servers
Topics
Moving a Project Database
Logging on to WorkStation for Projects
Opening a Project
Deploying a Server
Logging on to WorkStation as a Building Operation User
Configuring a Factory-Set b3 BACnet Device after a Deploy
Commissioning a b3 BACnet Device
Downloading to a b3 BACnet Device
Moving a Project Database
Summary
14 Deploying Servers
Our Example
In this chapter, you deploy the CPlant AS server configuration to the Automation
Server and the University X ES1 server configuration to the Enterprise Server.
Because you can deploy a server only once, you are required to have completed
the University X Project before you deploy the servers.
You first move the University X Project database from the off-site computer (at the
Schneider Electric office) to the on-site computer (at the university). The on-site
computer is connected to the same network as the Automation Server and
Enterprise Server. In our example, you use a USB drive to move the project
database from one computer to another.
You log on to WorkStation for Projects on the on-site computer and open the
project. You then deploy the server configurations to the servers to add the
configurations that you have created off site. You first deploy the Automation Server
and then deploy the Enterprise Server.
After the deployment, you log on to WorkStation to configure the serial numbers of
the b3 BACnet devices, commission the b3 BACnet devices, and download the
objects that remain in the database to the b3 BACnet devices. You also check that
the servers function as intended and modify the configuration, if needed.
Finally, you move the project database back to the off-site computer.
14 Deploying Servers
14.1 Moving a Project Database
14.1
Note
A project closes 5 minutes after the last user has logged off or when
the Project Configuration Server Windows service is stopped in
Software Administrator.
Note
When multiple users are working with the Project Configuration
Server, make sure a stop of the Project Configuration Server
Windows service does not negatively affect your projects before
closing.
Continued on next page
14 Deploying Servers
14.1 Moving a Project Database
5. In Windows Explorer, in the Address box, paste the path of the Projects
folder. In this example, paste the path of the Projects folder for the off-site
computer.
14 Deploying Servers
14.1 Moving a Project Database
8. In Windows Explorer, in the Address box, paste the path of the Projects
folder. In this example, paste the path of the Projects folder for the on-site
computer.
9. Move the individual project folder from the USB drive to the Projects folder.
In this example, move the University X Project folder from the USB drive to
the Projects folder on the on-site computer.
The project can now be opened in WorkStation for Projects on the target computer.
14 Deploying Servers
14.1 Moving a Project Database
Important
To see the recently moved project in WorkStation for Projects - Projects view on
the target computer, refresh the view or restart the Project Configuration Server.
For more information, see the Project Not Visible topic on WebHelp.
14 Deploying Servers
14.2 Logging on to WorkStation for Projects
14.2
Note
The first time you log on to WorkStation for Projects you need to use
the administrator user account to create a project user account. For
more information, see the Creating a Project Configuration Server
User Account topic on WebHelp.
14 Deploying Servers
14.2 Logging on to WorkStation for Projects
3. In the Server box, select the hypertext transfer protocol you want to use and
then enter a server name or an IP address. In this example, click HTTPS
and then enter localhost.
4. Select Remember me to have WorkStation for Projects remember your
settings.
5. Click Log on.
14 Deploying Servers
14.3 Opening a Project
14.3
Opening a Project
You open a project to configure a project or to deploy a project to a server.
For more information, see the Projects topic on WebHelp.
In this example, you open the University X Project on the on-site computer.
To open a project
1. In WorkStation for Projects, in the WorkStation for Projects - Projects
view, select the project that you want to open. In this example, select
University X Project.
2. On the toolbar, click the Open Project button
14 Deploying Servers
14.4 Deploying a Server
14.4
Deploying a Server
You deploy a server configuration to an Enterprise Server or Automation Server to
add the configuration that you have created off site.
For more information, see the Deploy topic on WebHelp.
Important
It is recommended that you update the Enterprise Server communication
parameters before the deploy of the of the first Automation server, and all
Automation Server communication parameters before the deploy of the
Enterprise Server.
Caution
Ensure that you have created all domain devices and objects before the deploy of
an Automation Server. If you add devices and objects to the Automation Server
and deploy the server again, you first have to clear the database of the physical
Automation Server.
Ensure that you have created all objects and servers, with devices and objects, in
the project and deployed all Automation Servers before the deploy of the
Enterprise Server. Any additional servers, devices, and objects have to be created
on the on-site server.
For more information, see the Deploy topic on WebHelp.
In this example, you deploy the CPlant AS server configuration to the Automation
Server to add the configuration that you have created off site in the University X
Project.
To deploy a server
1. In WorkStation for Projects, in the System Tree pane, select the server that
you want to deploy. In this example, select ...University X
Project/Servers/University X ES1/Servers/CPlant AS.
2. On the Actions menu, click Deploy.
3. Click Yes.
4. Click Close.
For this example, repeat the procedure to deploy the University X ES1 server
configuration to the Enterprise Server. Use the following settings:
14 Deploying Servers
14.4 Deploying a Server
Setting
Location
...University X Project/Servers/University X
ES1
You can now commission or associate the devices to bring them online with the
Enterprise Server or Automation Server.
14 Deploying Servers
14.5 Logging on to WorkStation as a Building Operation User
14.5
Important
Ensure that you have a working and available WorkStation license. A working
license is required to log on to WorkStation. For more information, see the
Licenses topic on WebHelp.
For more information, see the Log on to WorkStation or WebStation topic on
WebHelp.
In this example, you log on to WorkStation in order to commission the field bus
devices, to check that the Enterprise Server and Automation Server function as
intended, and to make configurations changes, if needed. You use the local
administrator (admin) account to log on to the Enterprise Server.
In this
14 Deploying Servers
14.5 Logging on to WorkStation as a Building Operation User
3. Select the Server hypertext transfer protocol option for communication with
the server. In this example, select HTTPS.
4. In the Server box, enter a server name or an IP address. In this example,
enter the host name (DNS name) for the Enterprise Server.
5. Select Remember me to have WorkStation remember your settings.
6. Click Log on.
7. You can register the system now or later:
Click Register now to register your system. For more information, see
the System Registration Overview topic on WebHelp.
Click Register later to skip registration and register at a later time.
In this example, click Register later.
14 Deploying Servers
14.5 Logging on to WorkStation as a Building Operation User
14 Deploying Servers
14.6 Configuring a Factory-Set b3 BACnet Device after a Deploy
14.6
Note
You can obtain the serial number from the label on the device. The
serial number is used to locate the b3 BACnet device on the MS/TP
network. When a message goes out on the network, the b3 BACnet
device responds and identifies itself as the designated device.
Continued on next page
14 Deploying Servers
14.6 Configuring a Factory-Set b3 BACnet Device after a Deploy
5. Click OK.
You now need to commission the b3 BACnet device and download the objects that
remain in the Building Operation database to the b3 BACnet device.
For this example, repeat the procedure to configure serial numbers for the AHU
controller (b3867) named AHU_02 and the four VAV controllers (b3866) named
VAV_01_01, VAV_01_02, VAV_02_01, and VAV_02_02 respectively.
14 Deploying Servers
14.7 Commissioning a b3 BACnet Device
14.7
Tip
You can commission multiple devices at the same time.
3. On the Actions menu, point to Device and then click Commission.
4. Click Close when the operation is completed.
14 Deploying Servers
14.8 Downloading to a b3 BACnet Device
14.8
Tip
You can download objects to multiple devices at the same time.
3. On the Actions menu, click Download.
A decision box displays indicating that the download operation will attempt to
delete any non-Building Operation object in the device.
4. Click Yes to proceed.
5. Use the Progress view to monitor the Download command.
Note
Download performs three steps: commission, reset, and
download objects. A status bar shows the commissioning and
download operations as they occur and lists the objects as they
are commissioned and downloaded.
14 Deploying Servers
14.9 Moving a Project Database
14.9
Note
A project closes 5 minutes after the last user has logged off or when
the Project Configuration Server Windows service is stopped in
Software Administrator.
Note
When multiple users are working with the Project Configuration
Server, make sure a stop of the Project Configuration Server
Windows service does not negatively affect your projects before
closing.
Continued on next page
14 Deploying Servers
14.9 Moving a Project Database
5. In Windows Explorer, in the Address box, paste the path of the Projects
folder. In this example, paste the path of the Projects folder for the on-site
computer.
14 Deploying Servers
14.9 Moving a Project Database
8. In Windows Explorer, in the Address box, paste the path of the Projects
folder. In this example, paste the path of the Projects folder for the off-site
computer.
9. Move the individual project folder from the USB drive to the Projects folder.
In this example, move the University X Project folder from the USB drive to
the Projects folder on the off-site computer.
The project can now be opened in WorkStation for Projects on the target computer.
14 Deploying Servers
14.9 Moving a Project Database
Important
To see the recently moved project in WorkStation for Projects - Projects view on
the target computer, refresh the view or restart the Project Configuration Server.
For more information, see the Project Not Visible topic on WebHelp.
14 Deploying Servers
14.10 Summary
14.10
Summary
The network of b3 BACnet devices are programmed and configured and are online
and communicating. The CPlant AS was already functioning as an IP controller for
the Central Plant as a result of previous work in the system. The East Wing of the
School of Business is now being controlled by a BACnet network comprised of two
b3867 devices for the Air Handling Units and four b3866-V devices for VAV damper
control.
The final result is, if the building is unoccupied, the valve position remains closed
whether the fan status is active or inactive. If the building is occupied, the valve
position will only open when the fan status is active and the damper position will
calculate a value. OccStatus is controlled with the AHU_01_VAVOccCmd
(AHU_02_VAVOccCmd) and also can be overridden with the Ovrd value.
You used WorkStation for Projects to create and configure the BACnet network and
the b3 BACnet devices off site (at the Schneider Electric office).