Creating and Configuring A BACnet Network With b3 BACnet Devices Tutorial Guide

StruxureWare Building Operation
Creating and Configuring a BACnet Network with b3

BACnet Devices
Tutorial Guide
04-16030-01-en
December 2014
StruxureWare Building Operation

Creating and Configuring a BACnet Network with b3
BACnet Devices
Tutorial Guide
04-16030-01-en
December 2014
Copyright 2014 Schneider Electric. All rights reserved.

The Schneider Electric brand and any registered trademarks of Schneider Electric Industries SAS referred to in this guide are the sole property of Schneider
Electric SA and its subsidiaries. They may not be used for any purpose without the owner's permission, given in writing. This guide and its content are
protected, within the meaning of the French intellectual property code (Code de la proprit intellectuelle franais, referred to hereafter as "the Code"), under
the laws of copyright covering texts, drawings and models, as well as by trademark law. You agree not to reproduce, other than for your own personal, noncommercial use as defined in the Code, all or part of this guide on any medium whatsoever without Schneider Electric's permission, given in writing. You also
agree not to establish any hypertext links to this guide or its content. Schneider Electric does not grant any right or license for the personal and noncommercial use of the guide or its content, except for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved.
Trademarks and registered trademarks are the property of their respective owners.
Contents
Introduction
1
1.1
1.2
1.3
2
2.1
2.2
About This Guide ......................................................... 11

Purpose of This Guide ................................................................. 13
How This Guide is Organized ...................................................... 14
Typographical Conventions ......................................................... 15
Additional Information .................................................. 17

Where to Find Additional Information ........................................... 19
Regulatory Notices ...................................................................... 21
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
04-16030-01-en, December 2014
Our Case Study ........................................................... 25

University X ................................................................................. 27
Requirements and Specifications ................................................ 30
Devices Used for This Case Study ............................................. 30
Software Used in This Tutorial ................................................... 30
Specifications ........................................................................... 30
Focus of This Tutorial .................................................................. 31
Pre-existing Project Database Folders and Programs ................ 31
Pre-existing Project Database Objects ...................................... 32
Pre-existing WorkStation for Projects User Accounts ................. 33
Creating the BACnet MS/TP Network .......................... 35

Logging on to WorkStation for Projects ....................................... 38
Opening a Project ....................................................................... 40
Creating a BACnet Interface ........................................................ 41
Creating a BACnet MS/TP Network ............................................. 43
Configuring the MS/TP Network for b3 Communication ............... 45
Creating a Folder ........................................................................ 46
Creating and Configuring b3 BACnet Devices .............. 49

Creating a b3 BACnet Device ...................................................... 52
Creating I/O Points and Variables in the b3 BACnet

Devices ........................................................................ 55
Creating and Configuring a BACnet Network with b3 BACnet Devices
5
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
Creating a b3 BACnet Device Analog Input Point ......................... 58

Configuring the COV Increment and the Unit for a b3 BACnet Device
Analog Input Point ....................................................................... 61
Creating a b3 BACnet Device Analog Output Point ...................... 65
Analog Output Point .................................................................... 68
Configuring the Electrical Scale and the Engineering Scale for a b3
BACnet Device Analog Output Point ........................................... 72
Creating a b3 BACnet Device Analog Value ................................. 75
Analog Value ............................................................................... 78
Creating a b3 BACnet Device Digital Input Point .......................... 83
Creating a b3 BACnet Device Digital Output Point ....................... 86
Creating a b3 BACnet Device Digital Value .................................. 89
Creating a b3 BACnet Device Multistate Pulsed Output Point ...... 92
Creating Variables in the Automation Server ................. 95

Creating a Server Analog Value ................................................... 98
Configuring the Value and the Unit for a Server Analog Value ..... 100
Creating a Server Digital Value ................................................... 103
Creating a BACnet Value ........................................................... 104
Configuring a BACnet Analog Value .......................................... 107
Creating Programs in Automation Server and b3 BACnet

Devices ...................................................................... 109
Creating a Function Block Program ........................................... 112
Importing Function Block Program Code ................................... 113
Creating a Script Program ......................................................... 114
Importing Script Program Code ................................................. 116
Creating a b3 Script Program .................................................... 118
Importing Script Program Code ................................................. 121
Creating and Configuring Schedules in Automation

Server ........................................................................ 123
9.1
9.2
Creating a Digital Schedule ....................................................... 126

Configuring a Schedule as a Shadow ....................................... 127
10
Creating Bindings for the b3 BACnet Devices ............. 129
10.1
10.2
10.3
11
11.1
11.2
11.3
11.4
11.5
12
Binding Values Using a Binding Template .................................. 132

Importing a Solution .................................................................. 139
Duplicating a b3 BACnet Device ................................. 147

Creating a b3 BACnet Device .................................................... 150
Merging Copied Device Content in a b3 BACnet Device ............ 152
Copying a Folder or Object ........................................................ 154
Renaming a Folder or Object ..................................................... 155
Creating Bindings Internal to the Automation Server ... 161

6
04-16030-01-en, December 2014
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
04-16030-01-en, December 2014
Duplicating b3 BACnet Devices .................................. 169

Creating a b3 BACnet Device .................................................... 172
Merging Copied Device Content in a b3 BACnet Device ............ 175
Copying a Folder or Object ........................................................ 177
Renaming a Folder or Object ..................................................... 178
Deploying Servers ...................................................... 187

Moving a Project Database ....................................................... 190
Logging on to WorkStation for Projects ..................................... 194
Opening a Project ..................................................................... 196
Deploying a Server .................................................................... 197
Logging on to WorkStation as a Building Operation User ........... 199
Configuring a Factory-Set b3 BACnet Device after a Deploy ...... 202
Commissioning a b3 BACnet Device ......................................... 204
Downloading to a b3 BACnet Device ......................................... 205
Moving a Project Database ....................................................... 206
Summary .................................................................................. 210

7
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.
About This Guide
Topics
Purpose of This Guide
How This Guide is Organized
Typographical Conventions
1 About This Guide

1.1 Purpose of This Guide
1.1
Purpose of This Guide

This tutorial provides step-by-step instructions for creating a BACnet network
configured with an Automation Server and b3 BACnet devices.
This tutorial focuses on the following Building Operation Engineering Certification
objectives:
Create a new Building Operation system using an Automation Server and b3
BACnet devices
Integrate b3 BACnet devices in a new Building Operation system
Organize folders and objects in the System Tree pane
Identify engineering process and communication flow between devices and
servers
Import applications
Use standards and templates for efficient engineering
04-16030-01-en, December 2014

13
1 About This Guide

1.2 How This Guide is Organized
1.2
How This Guide is Organized

This Building Operation Guide is divided into the following parts:
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.

14
04-16030-01-en, December 2014
1 About This Guide

1.3 Typographical Conventions
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.
04-16030-01-en, December 2014

15
Additional Information
Topics
Where to Find Additional Information
Regulatory Notices
2 Additional Information
2.1 Where to Find Additional Information
2.1
Where to Find Additional Information

All the technical Building Operation information is available online, on WebHelp.
WebHelp is a web-based help system for StruxureWare Building Operation and
Automation Server Family products, the software and hardware that powers
SmartStruxure solution.
By pressing F1 or clicking a Help button in the StruxureWare Building Operation
software your web browser opens WebHelp with the latest, up-to-date, technical
documentation.
Figure: Help in StruxureWare Building Operation
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.
The WebHelp site

One of the advantages with WebHelp is that you can reach Help without having the
StruxureWare Building Operation software installed on your computer. By entering
the URL address help.sbo.schneider-electric.com you can access WebHelp from
any computer, smartphone, or tablet connected to the internet.
Finding information
The easiest way to find information on WebHelp is to search for it.
Figure: Home page search
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.
Filtering the information

To narrow down the search results, you can use these filters:
Product
Functionality
Information type
04-16030-01-en, December 2014

19
2.1 Where to Find Additional Information
Figure: Search filters

20
04-16030-01-en, December 2014
2.2 Regulatory Notices
2.2
Regulatory Notices
UL 916 Listed products for the Unites States and Canada, Open
Class Energy Management Equipment.
WEEE - Directive of the European Union (EU)

This equipment and its packaging carry the waste of electrical and electronic
equipment (WEEE) label, in compliance with European Union (EU) Directive
2002/96/EC, governing the disposal and recycling of electrical and electronic
equipment in the European community.
CE - Compliance to European Union (EU)

2004/108/EC Electromagnetic Compatibility Directive
This equipment complies with the rules, of the Official Journal of the European
Union, for governing the Self Declaration of the CE Marking for the European Union
as specified in the above directive(s) per the provisions of the following standards:
IEC/EN 61326-1 Product Standard, IEC/EN 61010-1 Safety Standard.
Industry Canada
ICES-003
This is a Class B digital device that meets all requirements of the Canadian
Interference Causing Equipment Regulations.
C-Tick (Australian Communications Authority (ACA))

AS/NZS 3548
This equipment carries the C-Tick label and complies with EMC and radio
communications regulations of the Australian Communications Authority (ACA),
governing the Australian and New Zealand (AS/NZS) communities.
Federal Communications Commission

FCC Rules and Regulations CFR 47, Part 15, Class B
This device complies with part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) This device may not cause harmful interference. (2) This
device must accept any interference received, including interference that may cause
undesired operation.
04-16030-01-en, December 2014

21
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.
Our Case Study
Topics
University X
Requirements and Specifications
Focus of This Tutorial
3 Our Case Study

3.1 University X
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.
Figure: The School of Business and the Central Plant
The Cooling Plant consists of a single chiller with a primary-secondary pumping

system. The secondary water loop serves four VAV air handling units with chilled
water coils located in the School of Business. The secondary loop has two water
pumps. Only one pump is required for 100 % of the load. The second pump
provides 100 % backup. The secondary pumps are variable speed. The primary
chilled water loop has a single constant volume chilled water pump. The condenser
loop rejects heat by means of a cooling tower. The condenser loop has a single
constant volume condenser water pump. The tower has two constant speed, drawthrough fans to increase the capacity of the tower above the natural draft capacity.
A diverting valve can be used to protect the chiller from condenser water thermal
shock. The water leaving the condenser can be diverted back to the inlet of the
condenser without any cooling effect.
04-16030-01-en, December 2014

27
3 Our Case Study

3.1 University X
Figure: Cooling Plant diagram
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.

28
04-16030-01-en, December 2014
3 Our Case Study

3.1 University X
Figure: Heating Plant diagram
Note
The programs and files that are used for the fictional customer University X are
intended for training purposes only.
04-16030-01-en, December 2014

29
3 Our Case Study

3.2 Requirements and Specifications
3.2
Requirements and Specifications

To be able to configure Building Operation for University X, the following devices
and software are used in this tutorial.
3.2.1
Devices Used for This Case Study

The following devices are used for this case study:
Power Supply, PS-24V
Automation Server
BACnet Terminal Controller:
2 x b3867 (factory-set)
BACnet VAV Controller:
4 x b3866-V (factory-set)
This tutorial describes an example with b3 BACnet devices that still have their
factory settings.
3.2.2
Software Used in This Tutorial

The following software is used in this tutorial:
License Administrator, and a valid license file
Enterprise Server
WorkStation
Project Configuration Server
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.

30
04-16030-01-en, December 2014
3 Our Case Study

3.3 Focus of This Tutorial
3.3
Focus of This Tutorial

The university requires the new East Wing of the School of Business to be
controlled using b3 BACnet devices. The equipment consists of two VAV-Air
Handling Unit controllers and four VAV controllers.
In this tutorial, you create and configure the BACnet network and the b3 BACnet
devices required. This includes organizing the BACnet network folder structure and
establishing communication between the network devices.
You create and configure the BACnet network and the b3 BACnet devices off site
(at the Schneider Electric office) using WorkStation for Projects.
3.3.1
Pre-existing Project Database Folders and

Programs
For University X, a project called University X Project has been created in the Project
Configuration Server on the off-site computer. The University X Project includes an
Enterprise Server and an Automation Server.
The Enterprise Server called University X ES1 has the following folder structure:
Figure: University X ES1 and its folder structure
The Automation Server called CPlant AS controls the Cooling Plant and Heating
Plant.
CPlant AS has the following folder structure:
04-16030-01-en, December 2014

31
3 Our Case Study

Figure: CPlant AS and its folder structure
In this tutorial, no programs need to be present in the project database on the offsite computer.
3.3.2
Pre-existing Project Database Objects

For University X, the following objects are available in the project database on the
off-site computer prior to the creation and configuration of BACnet network with b3
BACnet devices:
...University X ES1/Servers/CPlant AS/Cooling Application/Schedules/Cooling
Plant Enable Schedule

32
04-16030-01-en, December 2014
3 Our Case Study

3.3.3
Pre-existing WorkStation for Projects User

Accounts
For University X, the following WorkStation for Projects user account is available on
the off-site computer as well as the on-site computer:
Pete
04-16030-01-en, December 2014

33
Creating the BACnet MS/TP

Network
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
4 Creating the BACnet MS/TP Network
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.
04-16030-01-en, December 2014

37

4.1 Logging on to WorkStation for Projects
4.1

You use WorkStation for Projects to access the Project Configuration Server.
For more information, see the Log on to WorkStation for Projects topic on
WebHelp.
In this example, you log on to the Project Configuration Server on the off-site
computer, using the project user account Pete.
To log on to WorkStation for Projects

1. In the Building Operation WorkStation for Projects window, in the User
name box, type the user name. In this example, type Pete.
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.
2. In the Password box, type the password.
In this example, type Pete.

Continued on next page

38
04-16030-01-en, December 2014

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.
04-16030-01-en, December 2014

39

4.2 Opening a Project
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
The project opens in WorkStation for Projects.

40
04-16030-01-en, December 2014

4.3 Creating a BACnet Interface
4.3
Creating a BACnet Interface

You create the BACnet Interface to enable the BACnet communications port on an
Enterprise Server or Automation Server.
For more information, see the BACnet Interface topic on WebHelp.
In this example, you create the BACnet Interface in the CPlant AS.
To create a BACnet Interface

1. In WorkStation, in the System Tree, select the location where you want to
create the BACnet Interface. In this example, select ...University X
ES1/Servers/CPlant AS.
2. On the File menu, point to New and then click Interface.
3. In the object type list, select BACnet Interface.
4. In the Name box, type a name for the BACnet Interface.

keep the default name of BACnet Interface.
In this example,
5. Click Next.
04-16030-01-en, December 2014

41

4.3 Creating a BACnet Interface
6. 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 interface.
In this example, click Automatically generated.
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.

42
04-16030-01-en, December 2014

4.4 Creating a BACnet MS/TP Network
4.4
Creating a BACnet MS/TP Network

You create an MS/TP network in order to connect a b3 BACnet device or other
BACnet device to an Automation Server.
For more information, see the BACnet Networks topic on WebHelp.
In this example, you create the MS/TP Network (RS-485), which is used to control
the new East Wing of the School of Business building. This building will be
controlled by a field bus comprised of b3 BACnet devices.
To create a BACnet MS/TP network

1. In WorkStation, in the System Tree, select the BACnet Interface. In this
example, select ...University X ES1/Servers/CPlant AS/BACnet
Interface.
2. On the File menu, point to New and then click MSTP Network.
3. In the Name box, type a name for the MS/TP network.
keep the default name MSTP Network.
In this example,
4. Click Next.
04-16030-01-en, December 2014

43

4.4 Creating a BACnet MS/TP Network
5. In the Network ID box, enter a unique number between 1 and 65534.

this example, enter 5555 for the Network ID.
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.

44
04-16030-01-en, December 2014

4.5 Configuring the MS/TP Network for b3 Communication
4.5
Configuring the MS/TP Network for b3

Communication
You configure the MS/TP network to optimize its performance.
For more information, see the Communication Between the AS and b3 BACnet
Device topic on WebHelp.
In this example, you configure the MS/TP network to optimize b3 communications.
To configure the MS/TP Network for b3 communication

1. In WorkStation, in the System Tree pane, select the MSTP Network. In
this example, select ...University X ES1/Servers/CPlant AS/BACnet
Interface/MSTP Network.
2. On the File menu, click Properties.
3. On the Basic tab, in the MSTP baud rate box, select the baud rate.
this example, select 76800.
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.
04-16030-01-en, December 2014

45

4.6 Creating a Folder
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.
In this example, type
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
AS/AHU_01

46
04-16030-01-en, December 2014

4.6 Creating a Folder
Continued
Name
Location
Values
AS/AHU_01
VAV_01
AS/AHU_01
Programs
AS/AHU_01/VAV_01
Values
AS/AHU_01/VAV_01
04-16030-01-en, December 2014

47
Creating and Configuring b3

BACnet Devices
Topics
Creating a b3 BACnet Device
5 Creating and Configuring b3 BACnet Devices
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.
04-16030-01-en, December 2014

51

5.1 Creating a b3 BACnet Device
5.1

You can create an offline b3 BACnet device, enter identifying information, and then
commission the device to make it available for network communications.
For more information, see the b3 BACnet Device Controllers topic on WebHelp.
In this example, you create an AHU controller named AHU_01. You select a model
name (b3867) that corresponds to the physical device. You enter valid numbers for
the Instance ID and Infinet ID. You also enter a BACnet name for the device. You
leave the serial number unspecified. You will enter the serial number later, after you
deploy the servers.
To create a b3 BACnet device

1. In WorkStation, in the System Tree pane, select the MSTP Network where
you want to create the b3 BACnet device. In this example,
select ...University X ES1/Servers/CPlant AS/BACnet
2. On the File menu, point to New and then click b3 Device.
3. In the Name box, type a name for the BACnet device.
AHU_01.
Note
The b3 object display Name is limited to 16 characters
consisting solely of letters, digits, and underscores.
4. Click Next.

52
04-16030-01-en, December 2014

5. Under Download to BACnet device, in the Instance ID box, type a

unique instance ID for BACnet configuration and communication. In this
example, type 4010.
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.
In this example, select
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:
04-16030-01-en, December 2014

53

Table: b3 BACnet Device VAV_01_01

Component
Setting
Location
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

54
04-16030-01-en, December 2014
Creating I/O Points and

Variables in the b3 BACnet
Devices
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
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
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
6 Creating I/O Points and Variables in the b3 BACnet Devices
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.
04-16030-01-en, December 2014

57

6.1 Creating a b3 BACnet Device Analog Input Point
6.1
Creating a b3 BACnet Device Analog

Input Point
You create analog input points in the Application folder of the b3 BACnet device.
For more information, see the b3 BACnet Device Point and Value Configuration
topic on WebHelp.
In this example, you create an analog input point named Dat in the AHU_01 b3
BACnet device.
To create a b3 BACnet device analog input point

1. In WorkStation, in the System Tree pane, expand the b3 BACnet device
where you want to create the analog input point. In this example,
expand ...University X ES1/Servers/CPlant AS/BACnet
Interface/MSTP Network/AHU_01.
2. Select Application.
3. On the File menu, point to New and then click Point.
4. In the object type list, select BACnet Analog Input (Continuum).
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.

58
04-16030-01-en, December 2014


Click Manually entered to manually enter a BACnet instance ID, and
then type an appropriate Instance ID for the BACnet object.
If you enter an Instance ID manually, you must ensure it is unique within the
application for this type.
8. Click Next.
04-16030-01-en, December 2014

59

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
11. Click Create.

For this example, repeat the procedure to create an analog input point named
VAVTemp in the VAV_01_01 b3 BACnet device. Use the following settings:
Table: VAV_01_01 b3 BACnet Device Analog Input Point VAVTemp
Component
Setting
Location
AS/BACnet Interface/MSTP
Network/VAV_01_01/Application
Name
VAVTemp
Channel
Electrical type
Temp(DEGC) or Temp(DEGF)

60
04-16030-01-en, December 2014

6.2 Configuring the COV Increment and the Unit for a b3 BACnet Device Analog Input Point
6.2
Configuring the COV Increment and the

Unit for a b3 BACnet Device Analog
Input Point
You configure the COV increment and the unit for a b3 BACnet device analog input
point to ensure that the analog input point holds the COV increment and the unit as
required by the project.
topic on WebHelp.
In this example, you configure the COV increment and the unit for the analog input
point named Dat in the AHU_01 b3 BACnet device.
To configure the COV increment and the unit for a b3 BACnet

device analog input point
and then select Application. In this example, expand ...University X
ES1/Servers/CPlant AS/BACnet Interface/MSTP Network/AHU_01
and then select Application.
2. In the List View, select the b3 BACnet device analog input point.
example, select Dat.
In this

04-16030-01-en, December 2014

61

4. Click the Basic tab.
5. For Value, click the Configure Settings icon
.

62
04-16030-01-en, December 2014

6. Select the Configured box that is in front of the Unit box.
7. In the Unit box, enter the unit.
In this example, enter C (F).
8. Click OK.
04-16030-01-en, December 2014

63

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.
10. Click OK.

For this example, repeat the procedure to configure the COV increment and the
unit for the analog input point named VAVTemp in the VAV_01_01 b3 BACnet
device. Use the following settings:
Table: VAV_01_01 b3 BACnet Device Analog Input Point VAVTemp
Component
Setting
Location
Name
VAVTemp
Unit
C (F)
COV increment

64
04-16030-01-en, December 2014

6.3 Creating a b3 BACnet Device Analog Output Point
6.3

Output Point
You create analog output points in the Application folder of the b3 BACnet device.
topic on WebHelp.
In this example, you create an analog output point named VlvPosn in the AHU_01
b3 BACnet device.
To create a b3 BACnet device analog output point

where you want to create the analog output point. In this example,
4. In the object type list, select BACnet Analog Output (Continuum).
5. In the Name box, type a name for the analog output point.
type VlvPosn.
In this example,
6. Click Next.
04-16030-01-en, December 2014

65


8. Click Next.

66
04-16030-01-en, December 2014

9. In the Channel box, enter the output channel you want the point to write to.
10. In the Electrical type box, select the electrical type on the output point.
this example, select Voltage.
In
11. Click Create.
04-16030-01-en, December 2014

67

6.4 Configuring the COV Increment and the Unit for a b3 BACnet Device Analog Output Point
6.4

Output Point
You configure the COV increment and the unit for a b3 BACnet device analog
output point to ensure that the analog output point holds the COV increment and
the unit as required by the project.
topic on WebHelp.
In this example, you configure the COV increment and the unit for the analog output
point named VlvPosn in the AHU_01 b3 BACnet device.

device analog output point
1. In WorkStation, in the System Tree pane, expand the b3 BACnet device and
then select Application. In this example, expand ...University X
2. In the List View, select the b3 BACnet device analog output point.
example, select VlvPosn.
In this


68
04-16030-01-en, December 2014

.
04-16030-01-en, December 2014

69

In this example, enter %.
8. Click OK.

70
04-16030-01-en, December 2014

10. Click OK.
04-16030-01-en, December 2014

71

6.5 Configuring the Electrical Scale and the Engineering Scale for a b3 BACnet Device Analog Output Point
6.5
Configuring the Electrical Scale and the

Engineering Scale for a b3 BACnet
Device Analog Output Point
You configure the electrical scale and the engineering scale for a b3 BACnet device
analog output point to ensure that the analog output point holds the conversion
settings as required by the project.
topic on WebHelp.
In this example, you configure the electrical scale and the engineering scale for the
analog output point named VlvPosn in the AHU_01 b3 BACnet device.
To configure the electrical scale and the engineering scale for

a b3 BACnet device analog output point
2. In the List View, select the b3 BACnet device analog output point.
example, select VlvPosn.
In this


72
04-16030-01-en, December 2014

4. Click the Advanced tab.
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.
04-16030-01-en, December 2014

73

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.

74
04-16030-01-en, December 2014

6.6 Creating a b3 BACnet Device Analog Value
6.6

Value
You create analog values in the Application folder of the b3 BACnet device.
topic on WebHelp.
In this example, you create an analog value named DatSP in the AHU_01 b3
BACnet device.
To create a b3 BACnet device analog value

where you want to create the analog value. In this example,
3. On the File menu, point to New and then click Value.
4. In the object type list, select BACnet Analog Value (Continuum).
5. In the Name box, type a name for the analog value.

DatSP.
6. Click Next.
04-16030-01-en, December 2014

75


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
Network/AHU_01/Application
Name
StPrSP
Table: VAV_01_01 b3 BACnet Device Analog Values

Component
Setting
Location

76
04-16030-01-en, December 2014

Continued
Component
Name
Setting
DmprPosn
TermLoad
04-16030-01-en, December 2014

77

6.7 Configuring the COV Increment and the Unit for a b3 BACnet Device Analog Value
6.7

Value
You configure the COV increment and the unit for a b3 BACnet device analog value
to ensure that the analog value holds the COV increment and the unit as required by
the project.
topic on WebHelp.
In this example, you configure the COV increment and the unit for the analog value
named DatSP in the AHU_01 b3 BACnet device.

device analog value
2. In the List View, select the b3 BACnet device analog value.
example, select DatSP.
In this


78
04-16030-01-en, December 2014

.
04-16030-01-en, December 2014

79

In this example, enter C (F).
8. Click OK.

80
04-16030-01-en, December 2014

10. Click OK.

For this example, repeat the procedure to configure the COV increment and the
unit for the other analog values in the AHU_01 and VAV_01_01 b3 BACnet devices.
Use the following settings:
Table: AHU_01 b3 BACnet Device Analog Value StPrSP
Component
Setting
Location
Name
StPrSP
Unit
Pa (inH2O)
COV increment
0.05
04-16030-01-en, December 2014

81

Component
Setting
Table: VAV_01_01 b3 BACnet Device Analog Value DmprPosn

Component
Setting
Location
Name
DmprPosn
Unit
COV increment
Table: VAV_01_01 b3 BACnet Device Analog Value TermLoad

Component
Setting
Location
Name
TermLoad
Unit
COV increment

82
04-16030-01-en, December 2014

6.8 Creating a b3 BACnet Device Digital Input Point
6.8
Creating a b3 BACnet Device Digital

Input Point
You create digital input points in the Application folder of the b3 BACnet device.
topic on WebHelp.
In this example, you create a digital input point named FanStatus in the AHU_01 b3
BACnet device.
To create a b3 BACnet device digital input point

where you want to create the digital input point. In this example,
4. In the object type list, select BACnet Digital Input (Continuum).
5. In the Name box, type a name for the digital input point.
type FanStatus.
In this example,
6. Click Next.
04-16030-01-en, December 2014

83


8. Click Next.

84
04-16030-01-en, December 2014

9. In the Channel box, enter the input channel you want the point to read from.
10. Click Create.
04-16030-01-en, December 2014

85

6.9 Creating a b3 BACnet Device Digital Output Point
6.9

Output Point
You create digital output points in the Application folder of the b3 BACnet device.
topic on WebHelp.
In this example, you create a digital output point named FanCmd in the AHU_01 b3
BACnet device.
To create a b3 BACnet device digital output point

where you want to create the digital output point. In this example,
4. In the object name list, select BACnet Digital Output (Continuum).
5. In the Name box, type a name for the digital output point.
type FanCmd.
In this example,
6. Click Next.

86
04-16030-01-en, December 2014


8. Click Next.
04-16030-01-en, December 2014

87

9. In the Channel box, enter the output channel you want the point to write to.
10. Click Create.

For this example, repeat the procedure to create a digital output point named Light
in the VAV_01_01 b3 BACnet device. Use the following settings:
Table: VAV_01_01 b3 BACnet Device Digital Output Point Light
Component
Setting
Location
Name
Light
Channel

88
04-16030-01-en, December 2014

6.10 Creating a b3 BACnet Device Digital Value
6.10

Value
You create digital values in the Application folder of the b3 BACnet device.
topic on WebHelp.
In this example, you create a digital value named VentReq in the AHU_01 b3
BACnet device.
To create a b3 BACnet device digital value

where you want to create the digital value. In this example,
4. In the object type list, select BACnet Digital Value (Continuum).
5. In the Name box, type a name for the digital value.

VentReq.
6. Click Next.
04-16030-01-en, December 2014

89


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
Name
OccCmd
FanAlarm

90
04-16030-01-en, December 2014

Component
Setting
Table: VAV_01_01 b3 BACnet Device Digital Values

Component
Setting
Location
Name
OccStatus
OccCmd
Ovrd
04-16030-01-en, December 2014

91

6.11 Creating a b3 BACnet Device Multistate Pulsed Output Point
6.11
Creating a b3 BACnet Device Multistate

Pulsed Output Point
You create multistate pulsed output points in the Application folder of the b3
BACnet device.
Digital and Multistate Pulsed output points, DateTime and String values, and
program and function objects are non-BACnet proprietary object types. For more
information, see the BACnet Objects in StruxureWare topic on WebHelp.
topic on WebHelp.
In this example, you create a multistate pulsed output point named DmprCmd in the
VAV_01_01 b3 BACnet device.
To create a b3 BACnet device multistate pulsed output point

where you want to create the multistate pulsed output point. In this
example, expand ...University X ES1/Servers/CPlant AS/BACnet
Interface/MSTP Network/VAV_01_01.
4. In the object type list, select Multistate Pulsed Output.
5. In the Name box, type a name for the multistate pulsed output point.
example, type DmprCmd.
In this

92
04-16030-01-en, December 2014

6. Click Next.
8. Click Next.
04-16030-01-en, December 2014

93

9. In the Channel box, enter the channel where you want to put the multistate
pulsed output. In this example, enter channel 1.
10. Click Create.

94
04-16030-01-en, December 2014
Creating Variables in the

Automation Server
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
7 Creating Variables in the Automation Server
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.
04-16030-01-en, December 2014

97

7.1 Creating a Server Analog Value
7.1
Creating a Server Analog Value

You create analog values in the Automation Server or Enterprise Server for the
following reasons:
A variable needs to be bound to multiple programs.
A calibrated analog input variable needs to be forced.
For more information, see the Bindings Overview topic on WebHelp.
In this example, you create an analog value named VlvPosn_AS in the Automation
Server AHU_01 folder.
To create a server analog value

1. In WorkStation, in the System Tree pane, select the server or folder where
you want to add an analog value. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/Values.
3. In the object type list, select Analog Value.
4. In the Name box, type a name for the analog value.

VlvPosn_AS.
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:

98
04-16030-01-en, December 2014

7.1 Creating a Server Analog Value
Table: Analog Values in the Automation Server AHU_01/VAV_01 folder

Component
Setting
Location
AS/AHU_01/VAV_01/Values
Name
DmprPosn_AS
TermLoad_AS
04-16030-01-en, December 2014

99

7.2 Configuring the Value and the Unit for a Server Analog Value
7.2
Configuring the Value and the Unit for a

Server Analog Value
You configure the value and the unit for a server analog value to ensure that the
server analog value holds the value and the unit as required by the project.
In this example, you configure the analog value named VlvPosn_AS in the
Automation Server AHU_01 folder. You set the unit to percent (%), but leave the
value as is.
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.
3. Under Status Information, click the Configure button

100
04-16030-01-en, December 2014

In this example, enter %.
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
Name
DmprPosn_AS
Unit
Table: Analog Value in the Automation Server AHU_01/VAV_01 Folder

TermLoad_AS
Component
Setting
Location
04-16030-01-en, December 2014

101

Continued
Component
Setting
Name
TermLoad_AS
Unit

102
04-16030-01-en, December 2014

7.3 Creating a Server Digital Value
7.3
Creating a Server Digital Value

You create digital values in the Automation Server or Enterprise Server for the
following reasons:
A variable needs to be bound to multiple programs.
A digital schedule or an alarm needs to send information to a program.
In this example, you create a digital value named OccStatus_AS in the Automation
Server VAV_01 folder.
To create a server digital value

you want to add a digital value. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/VAV_01/Values.
3. In the object type list, select Digital Value.
4. In the Name box, type a name for the digital value.

OccStatus_AS.
5. Click Create.
04-16030-01-en, December 2014

103

7.4 Creating a BACnet Value
7.4
Creating a BACnet Value

You create a BACnet analog, digital, or multistate value in a local server so you can
then configure a control system parameter for the server. The server can be an
Automation Server or an Enterprise Server. The BACnet values that you create are
visible to other workstations and devices in the BACnet internetwork. You create
BACnet values for a server in the Application folder of the server's BACnet Interface.
For more information, see the BACnet Objects and Properties topic on WebHelp.
In this example, you create a BACnet analog value named AHU_01_DatSP in the
Application folder of the Automation Server's BACnet Interface.
To create a BACnet value

1. In WorkStation, in the System Tree, expand the BACnet Interface and then
select Application. In this example, expand ...University X
ES1/Servers/CPlant AS/BACnet Interface and then select
Application.
3. In the object type list, select the type of BACnet value that you want to create.
Do not select String Value or Time Stamp Value, which are not BACnet
object types. In this example, select BACnet Analog Value.
4. In the Name box, type a name for the value.

AHU_01_DatSP.
5. Click Next.

104
04-16030-01-en, December 2014


Instance ID for you.
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
AS/BACnet Interface/Application
Type
BACnet Analog Value
04-16030-01-en, December 2014

105

Continued
Component
Setting
Name
AHU_01_StPrSP
Command priority retain level
Cold start
Table: BACnet Digital Values

Component
Setting
Location
Type
BACnet Digital Value
Name
AHU_01_VAVOccCmd
AHU_01_VentReq
AHU_01_OccCmd
Command priority retain level

106
Cold start
04-16030-01-en, December 2014

7.5 Configuring a BACnet Analog Value
7.5
Configuring a BACnet Analog Value

You configure a BACnet analog value to define a control system parameter for an
Automation Server or Enterprise Server. You can also create an intrinsic alarm for
the analog value and enter a value for the Relinquish default property.
In this example, you configure the unit for the BACnet analog value named
AHU_01_DatSP, which is located in the Application folder of the Automation
Server's BACnet Interface.
To configure a BACnet analog value

1. In WorkStation, in the System Tree, expand the BACnet Interface and then
select Application. In this example, expand ...University X
ES1/Servers/CPlant AS/BACnet Interface and then select
Application.
2. In the List View, select the analog value that you want to configure.
example, select AHU_01_DatSP.
In this

5. For Value, click the Configure button
.
04-16030-01-en, December 2014

107

7.5 Configuring a BACnet Analog Value
6. Select the Unit check box.
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
Name
AHU_01_StPrSP
Unit
Pa (inH2O)

108
04-16030-01-en, December 2014
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
8 Creating Programs in Automation Server and b3 BACnet Devices
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.
04-16030-01-en, December 2014

111

8.1 Creating a Function Block Program
8.1
Creating a Function Block Program

You create a Function Block program to import existing program code or to
program new logic for the Automation Server using Function Block Editor.
For more information, see the Graphical Programming topic on WebHelp.
In this example, you create a function block program named Occupancy in the
Automation Server.
You can use Function Block programs or Script programs in the Automation Server.
You use a Function Block program in this example, but you can also use a Script
program for the same control logic in the Automation Server. When you decide to
use Function Block programming or Script programming, consider the engineer's
familiarity with programming tools and whether the programs require standard
programming features or customized details.
To create a function block program

you want to create the function block program. In this example,
select ...University X ES1/Servers/CPlant AS/AHU_01/Programs.
2. On the File menu, point to New and then click Program.
3. In the object type list, select Function Block Program.
4. In the Name box, type a name for the function block program.
example, type Occupancy.
In this
5. Click Create.

112
04-16030-01-en, December 2014

8.2 Importing Function Block Program Code
8.2
Importing Function Block Program Code

You import function block program code to reuse all or parts of existing code.
Function Block Editor supports import of .aut and .mta files created for Xenta
280/300/400 LonWorks devices in Menta Editor, as well as .aut file previously
created in Function Block Editor.
For more information, see the Graphical Programming topic on WebHelp.
In this example, you import program code to the Occupancy function block
program for use in the Automation Server.
To import function block program code

1. In WorkStation, in the System Tree pane, select the function block program
you want to import program code to. In this example, select ...University
X ES1/Servers/CPlant AS/AHU_01/Programs/Occupancy.
2. On the Actions menu, click Edit.
3. In Function Block Editor, on the File menu, click Import.
4. Select the file you want to import. In this example,
select ...\Desktop\student desktop files\Project 4\AS
Programs\Occupancy.AUT.
5. Click Open.
6. On the File menu, click Save.
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

113

8.3 Creating a Script Program
8.3
Creating a Script Program

You create a Script program to import existing program code or to program new
logic for an Automation Server using Script Editor.
For more information, see the Script Programs topic on WebHelp.
In this example, you create a script program named DatSP in the Automation
Server.
You can use Function Block programs or Script programs in the Automation Server.
You use a Script program in this example, but you can use a Function Block
program for the same control logic in the Automation Server. When you decide to
use Function Block programming or Script programming, consider the engineer's
familiarity with programming tools and whether the programs require standard
programming features or customized details.
To create a script program

you want to create the script program. In this example, select ...University
X ES1/Servers/CPlant AS/AHU_01/Programs.
3. In the object type list, select Script Program.
4. In the Name box, type a name for the script program.

DatSP.
5. Click Create.
In this example, repeat the procedure to create the following script programs:

114
04-16030-01-en, December 2014

8.3 Creating a Script Program
Table: Script Programs in the Automation Server AHU_01 Folder

Component
Setting
Location
AS/AHU_01/Programs
Name
StPrSP
Mirror_AHU
Table: Script Program in the Automation Server AHU_01/VAV_01 Folder

Component
Setting
Location
AS/AHU_01/VAV_01/Programs
Name
Mirror_VAV
04-16030-01-en, December 2014

115

8.4 Importing Script Program Code
8.4

You import Script program code to reuse all or parts of existing code. Script Editor
supports import of .txt files created using the Plain English tool, as well as previously
created Script program files.
For more information, see the Script Program Instructions topic on WebHelp.
In this example, you import program code to the DatSP Script program in the
Automation Server AHU_01 folder.
To import Script program code

1. In WorkStation, in the System Tree pane, select the Script program or
function you want to import program code to. In this example,
select ...University X ES1/Servers/CPlant
AS/AHU_01/Programs/DatSP.
3. In Script Editor, position the insertion point in the program or function where
you want to import program code.
4. Click the Script menu button
5. Point to Import and click Text or Plain English.

Text.
In this example, click

select ...\Desktop\student desktop files\Project 4\AS
Programs\DatSP.txt.
7. Click Open.
8. Click Save.
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
AS/AHU_01/Programs
Program name
StPrSP
Mirror_AHU

116
04-16030-01-en, December 2014

Continued
Component
Setting
File location
...\Desktop\student desktop files\Project

4\AS Programs
File name
StPrSP.txt
Mirror_AHU.txt
Table: Script Programs in the Automation Server AHU_01/VAV_01 Folder

Component
Setting
Program location
AS/AHU_01/VAV_01/Programs
Program name
Mirror_VAV
File location

4\AS Programs
File name
Mirror_VAV.txt
04-16030-01-en, December 2014

117

8.5 Creating a b3 Script Program
8.5
Creating a b3 Script Program

You create a Script program to import existing program code or to program new
logic for a b3 BACnet device using Script Editor.
In this example, you create a b3 script program named Mirror in the AHU_01 b3
BACnet device.
To create a b3 script program

1. In WorkStation, in the System Tree pane, select the folder where you want
to create the b3 script program. In this example, select ...University X
ES1/Servers/CPlant AS/BACnet Interface/MSTP
Network/AHU_01/Application.
3. In the object type list, select b3 Script Program.
4. In the Name box, type a name for the b3 script program.

type Mirror.
In this example,
5. Click Next.

118
04-16030-01-en, December 2014


Instance ID for you.
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
Name
CoolingCoil
FanControl
Table: b3 Script Programs in the VAV_01_01 b3 BACnet Device

Component
Setting
Location
04-16030-01-en, December 2014

119

Continued
Component
Name
Setting
Mirror
Occupancy
CalcDmprPosn
CalcTermLoad

120
04-16030-01-en, December 2014

8.6

You import Script program code to reuse all or parts of existing code. Script Editor
supports import of .txt files created using the Plain English tool, as well as previously
created Script program files.
In this example, you import program code to the Mirror Script program in the
AHU_01 b3 BACnet device.
To import Script program code

1. In WorkStation, in the System Tree pane, select the Script program or
function you want to import program code to. In this example,
Interface/MSTP Network/AHU_01/Application/Mirror.
3. In Script Editor, position the insertion point in the program or function where
you want to import program code.
4. Click the Script menu button
5. Point to Import and click Text or Plain English.

Text.
In this example, click

select ...\Desktop\student desktop files\Project 4\AHU_01
Programs\Mirror.txt.
7. Click Open.
8. Click Save.
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
Program name
CoolingCoil
FanControl
04-16030-01-en, December 2014

121

Continued
Component
Setting
File location

4\AHU_01 Programs
File name
CoolingCoil.txt
FanControl.txt
Table: Script Programs in the VAV_01_01 b3 BACnet Device

Component
Setting
Program location
Program name
Mirror
Occupancy
CalcDmprPosn
CalcTermLoad
File location
File name

4\VAV_01_01 Programs
Mirror.txt
Occupancy.txt
CalcDmprPosn.txt
CalcTermLoad.txt

122
04-16030-01-en, December 2014
Creating and Configuring

Schedules in Automation
Server
Topics
Creating a Digital Schedule
Configuring a Schedule as a Shadow
9 Creating and Configuring Schedules in Automation Server
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.
04-16030-01-en, December 2014

125

9.1 Creating a Digital Schedule
9.1
Creating a Digital Schedule

You create a digital schedule to control the state of a digital value.
For more information, see the Digital Schedules topic on WebHelp.
In this example, you create a digital schedule that will be used as a shadow
schedule to the Cooling Plant Enable Schedule.
To create a digital schedule

1. In WorkStation, in the System Tree pane, select the server or the folder
where you want to create the schedule. In this example,
select ...University X ES1/Servers/CPlant AS/AHU_01/Schedules.
2. On the File menu, point to New and then click Schedule.
3. In the object type list, select Digital Schedule.
4. In the Name box, type a name for the schedule.

Schedule.
5. Click Create.
Now you can add events to the digital schedule and bind it to a digital value.

126
04-16030-01-en, December 2014

9.2 Configuring a Schedule as a Shadow
9.2
Configuring a Schedule as a Shadow

You configure a schedule as a shadow to synchronize it with a schedule that
already contains all weekly events and exception events.
For more information, see the Schedule and Calendar Synchronization topic on
WebHelp.
In this example, you configure the digital schedule named Schedule as a shadow
schedule of the Cooling Plant Enable Schedule.
To configure a schedule as a shadow

1. In WorkStation, in the System Tree pane, select the schedule you want to
configure as a shadow. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/Schedules/Schedule.
3. In the Lead object box, enter the schedule that you want to synchronize the
shadow schedule with. In this example, enter ...University X
ES1/Servers/CPlant AS/Cooling Application/Schedules/Cooling
Plant Enable Schedule.
4. Click OK.
04-16030-01-en, December 2014

127
10
Creating Bindings for the b3

BACnet Devices
Topics
Binding Values Using a Binding Template
Importing a Solution
10 Creating Bindings for the b3 BACnet Devices
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
04-16030-01-en, December 2014

131

10.1 Binding Values Using a Binding Template
10.1
Binding Values Using a Binding

Template
You use binding templates to reduce engineering time when creating bindings.
Binding templates are defined and created for binding patterns that are frequently
reused.
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.
To bind values using a binding template

1. In WorkStation, in the System Tree pane, select the object that you want to
bind values to. In this example, select ...University X
Network/VAV_01_01/Application/CalcDmprPosn.
2. On the Actions menu, click Edit bindings.

132
04-16030-01-en, December 2014

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
Network/VAV_01_01/Application to the Default name matching
template.
4. Select the bindings that you want to create.

bindings selected.
In this example, keep all
5. Click OK.
04-16030-01-en, December 2014

133

6. Verify that all bindings are correctly bound.

bindings against the table below.
In this example, verify the
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
Network/VAV_01_01/Application/DmprPosn
/Value

134
04-16030-01-en, December 2014

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
template.
Table: Results Verification CalcTermLoad Program Bindings
Binding Point
Binding
Input - OccStatus
/Value
Output - TermLoad
Network/VAV_01_01/Application/TermLoad
/Value
Mirror Program in the VAV_01_01 Device

Interface/MSTP Network/VAV_01_01/Application/Mirror program:
template.
Table: Results Verification Mirror Program Bindings
Binding Point
Binding
Input - VAVOccCmd_AS
The binding to the VAVOccCmd_AS input

point is for data from the Automation Server
and will be created later.
Output - OccCmd
Network/VAV_01_01/Application/OccCmd/
Value
Occupancy Program in the VAV_01_01 Device

Interface/MSTP Network/VAV_01_01/Application/Occupancy program:
template.
04-16030-01-en, December 2014

135

Table: Results Verification Occupancy Program Bindings

Binding Point
Binding
Input - OccCmd
Network/VAV_01_01/Application/OccCmd/
Value
Input - Ovrd
Network/VAV_01_01/Application/Ovrd/Valu
e
Output - Light
Network/VAV_01_01/Application/Light/Valu
e
Output - OccStatus
/Value
Mirror Program in the AHU_01 Device

Interface/MSTP Network/AHU_01/Application/Mirror program:
Network/AHU_01/Application to the Default name matching template.
Binding Point
Binding
Input - DatSp_AS
The binding to the DatSp_AS input point is

for data from the Automation Server and will
be created later.
Input - OccCmd_AS
The binding to the OccCmd_AS input point

is for data from the Automation Server and
will be created later.
Input - StPrSp_AS
The binding to the StPrSp_AS input point is

for data from the Automation Server and will
be created later.
Input - VentReq_AS
The binding to the VentReq_AS input point

is for data from the Automation Server and
will be created later.
Output - DatSp
Network/AHU_01/Application/DatSP/Value
Output - OccCmd
Network/AHU_01/Application/OccCmd/Val
ue
Output - StPrSp
Network/AHU_01/Application/StPrSP/Value
Output - VentReq
Network/AHU_01/Application/VentReq/Valu
e

136
04-16030-01-en, December 2014

Binding Point
Binding
CoolingCoil Program in the AHU_01 Device

Interface/MSTP Network/AHU_01/Application/CoolingCoil program:
Table: Results Verification CoolingCoil Program Bindings
Binding Point
Binding
Input - Dat
Network/AHU_01/Application/Dat/Value
Input - DatSP
Network/AHU_01/Application/DatSP/Value
Input - FanStatus
Network/AHU_01/Application/FanStatus/Val
ue
Input - OccCmd
ue
Output - VlvPosn
Network/AHU_01/Application/VlvPosn/Valu
e
FanControl Program in the AHU_01 Device

Interface/MSTP Network/AHU_01/Application/FanControl program:
Table: Results Verification FanControl Program Bindings
Binding Point
Binding
Input - FanStatus
Network/AHU_01/Application/FanStatus/Val
ue
Input - OccCmd
ue
Output - FanAlarm
Network/AHU_01/Application/FanAlarm/Val
ue
04-16030-01-en, December 2014

137

Continued
Binding Point
Binding
Output - FanCmd
Network/AHU_01/Application/FanCmd/Valu
e

138
04-16030-01-en, December 2014

10.2 Importing a Solution
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.
04-16030-01-en, December 2014

139

10.2 Importing a Solution
4. Click Import.

140
04-16030-01-en, December 2014

10.3

Template
reused.
Tip
Public Signals.
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.

Network/AHU_01/Application/Mirror.
04-16030-01-en, December 2014

141

ES1/Servers/CPlant AS to the Data from AS to AHU custom binding
template.

bindings selected.
5. Click OK.

142
04-16030-01-en, December 2014


Tip
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
04-16030-01-en, December 2014

143

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.
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.
Binding Point
Binding
.../BACnet
Interface/Application/AHU_01_VAVOccCmd
/Value
Mirror_AHU Program in the Automation Server AHU_01 Folder

Create the bindings for data flow between the AHU_01 b3 BACnet device and
the ...University X ES1/Servers/CPlant
AS/AHU_01/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
e
Output - VlvPosn_AS
.../AHU_01/Values/VlvPosn_AS/Value
Mirror_VAV Program in the Automation Server AHU_01/VAV_01 Folder

Create the bindings for data flow between the VAV_01_01 b3 BACnet device and
AS/AHU_01/VAV_01/Programs/Mirror_VAV program:
Drag ...University X ES1/Servers/CPlant AS to the Data from VAV to

144
04-16030-01-en, December 2014

Table: Results Verification Mirror_VAV Program Bindings

Binding Point
Binding
Input - DmprPosn
/Value
Input - OccStatus
/Value
Input - 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
04-16030-01-en, December 2014

145
11
Duplicating a b3 BACnet
Device
Topics
Merging Copied Device Content in a b3 BACnet Device
Copying a Folder or Object
Renaming a Folder or Object
11 Duplicating a b3 BACnet Device
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.
04-16030-01-en, December 2014

149

11.1

In this example, you create a second VAV controller, which you name VAV_01_02.
You select a model name (b3866) that corresponds to the physical device. You
enter valid numbers for the Instance ID and Infinet ID. You also enter a BACnet
name for the device. You leave the serial number unspecified. You will enter the
serial number later, after you deploy the servers.

VAV_01_02.
Note
4. Click Next.

150
04-16030-01-en, December 2014


example, type 4012.
want it assigned for you. In this example, type VAV_01_02.
Note
b3866.
example, enter 3.
In this
Note
9. Click Create.
04-16030-01-en, December 2014

151

11.2 Merging Copied Device Content in a b3 BACnet Device
11.2
Merging Copied Device Content in a b3

BACnet Device
You can directly copy a b3 BACnet device in one step and then merge that device's
content with another b3 device or group of b3 BACnet devices.
For more information, see the b3 BACnet Device Merge Copied Device Content
topic on WebHelp.
In this example, you copy the contents (programs, values, and I/O points) of the
VAV_01_01 b3 BACnet device and merge the copied device content with the
VAV_01_02 device.
To merge copied device content in a b3 BACnet device

2. In the List View, select the source b3 BACnet device that you want to copy
from. In this example, select VAV_01_01.
3. On the Edit menu, click Copy.

4. Select the target b3 BACnet device(s).
In this example, select VAV_01_02.
5. On the Actions menu, click Merge copied device content.


152
04-16030-01-en, December 2014

6. When the operation is complete, click Close.
04-16030-01-en, December 2014

153

11.3 Copying a Folder or Object
11.3

You copy a folder or object when you quickly want to create a new folder or object.
In this example, you copy the VAV_01 folder under the AHU_01 folder and paste the
copied folder (VAV_01_copy) in the same AHU_01 folder.
To copy a folder or object

1. In WorkStation, in the System Tree pane, select the folder or object you
want to copy. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/VAV_01.
3. In the System Tree pane, select the folder where you want to paste the
copied folder or object. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01.
4. On the Edit menu, click Paste.

154
04-16030-01-en, December 2014

11.4 Renaming a Folder or Object
11.4

You rename a folder or object to make the name more suitable to your needs.
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.
To rename a folder or object

want to rename. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01/VAV_01_copy.
2. On the Edit menu, click Rename.
3. In the Rename object dialog box, type the new name.
type VAV_02.
In this example,
4. Click OK.
04-16030-01-en, December 2014

155

11.5

Template
reused.
Tip
Public Signals.
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.

ES1/Servers/CPlant AS/AHU_01/VAV_02/Programs/Mirror_VAV.

156
04-16030-01-en, December 2014

ES1/Servers/CPlant AS to the Data from VAV to AS custom binding
template.

bindings selected.
5. Click OK.
04-16030-01-en, December 2014

157


Tip
Binding Point
Binding
Input DmprPosn
/Value
Input OccStatus
/Value
Input TermLoad
/Value

158
04-16030-01-en, December 2014

Continued
Binding Point
Binding
Output DmprPosn_AS
Value
Output OccStatus_AS
Value
Output TermLoad_AS
Value
04-16030-01-en, December 2014

159
12
Creating Bindings Internal to

the Automation Server
Topics
12 Creating Bindings Internal to the Automation Server
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
04-16030-01-en, December 2014

163

12.1

Template
reused.
Tip
Public Signals.
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.

ES1/Servers/CPlant AS/AHU_01/Programs/Occupancy.

164
04-16030-01-en, December 2014

ES1/Servers/CPlant AS to the AS Programs custom binding template.

bindings selected.
5. Click OK.
04-16030-01-en, December 2014

165


Tip
Occupancy Program in the Automation Server AHU_01 Folder
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
OccStatus_AS
Output OccCmd
.../BACnet
ue

166
04-16030-01-en, December 2014

Continued
Binding Point
Binding
Output VAVOccCmd
.../BACnet
/Value
Output VentReq
.../BACnet
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
TermLoad_AS
TermLoad_AS
Output - DatSp
.../BACnet
StPrSP Program in the Automation Server AHU_01 Folder

AS/AHU_01/Programs/StPrSP program:
Table: Results Verification StPrSP Program Bindings
Binding Point
Binding
Input - VAV_01_DmprPosn
DmprPosn_AS
DmprPosn_AS
Output - StPrSp
.../BACnet
Interface/Application/AHU_01_StPrSP/Valu
e
04-16030-01-en, December 2014

167
13
Duplicating b3 BACnet Devices
Topics
Merging Copied Device Content in a b3 BACnet Device
13 Duplicating b3 BACnet Devices
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.
04-16030-01-en, December 2014

171

13.1

In this example, you create a second AHU controller, which is named AHU_02. You
select a model name (b3867) that corresponds to the physical device. You enter
valid numbers for the Instance ID and Infinet ID. You also enter a BACnet name for
the device. You leave the serial number unspecified. You will enter the serial number
later, after you deploy the servers.

AHU_02.
Note
4. Click Next.

172
04-16030-01-en, December 2014


example, type 4013.
want it assigned for you. In this example, type AHU_02.
Note
b3867.
example, enter 4.
In this
Note
9. Click Create.
For this example, create two additional VAV controllers, named VAV_02_01 and
VAV_02_02. Use the following settings:
04-16030-01-en, December 2014

173


Component
Setting
Location
Name
VAV_02_01
Instance ID
4014
BACnet name
VAV_02_01
Model name
b3866
Infinet ID
Serial number
Null

Component
Setting
Location
Name
VAV_02_02
Instance ID
4015
BACnet name
VAV_02_02
Model name
b3866
Infinet ID
Serial number
Null

174
04-16030-01-en, December 2014

13.2
Merging Copied Device Content in a b3

BACnet Device
You can directly copy a b3 BACnet device in one step and then merge that device's
content with another b3 device or group of b3 BACnet devices.
For more information, see the b3 BACnet Device Merge Copied Device Content
topic on WebHelp.
In this example, you copy the contents (programs, values, and I/O points) of the
AHU_01 b3 BACnet device and merge the copied device content with the AHU_02
device.
To merge copied device content in a b3 BACnet device

2. In the List View, select the source b3 BACnet device that you want to copy
from. In this example, select AHU_01.

4. Select the target b3 BACnet device(s).
In this example, select AHU_02.
5. On the Actions menu, click Merge copied device content.

04-16030-01-en, December 2014

175

6. When the operation is complete, click Close.
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
Source device
VAV_01_01
Target devices
VAV_02_01
VAV_02_02

176
04-16030-01-en, December 2014

13.3 Copying a Folder or Object
13.3

You copy a folder or object when you quickly want to create a new folder or object.
In this example, you copy the AHU_01 folder in the Automation Server and paste
the copied folder (AHU_01_copy) in the same location as the source.
To copy a folder or object

want to copy. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01.
3. In the System Tree pane, select the folder where you want to paste the
copied folder or object. In this example, select ...University X
ES1/Servers/CPlant AS.
4. On the Edit menu, click Paste.
For this example, repeat the procedure to copy the BACnet values in the
Application folder of the Automation Server's BACnet Interface and paste the
copied BACnet values in the same Application folder. Use the following settings:
Table: Copying BACnet Values
Component
Settings
Location
Source values
AHU_01_DatSP
AHU_01_OccCmd
AHU_01_StPrSP
AHU_01_VAVOccCmd
AHU_01_VentReq
Target folder
04-16030-01-en, December 2014

177

13.4

You rename a folder or object to make the name more suitable to your needs.
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.
To rename a folder or object

want to rename. In this example, select ...University X
ES1/Servers/CPlant AS/AHU_01_copy.
2. On the Edit menu, click Rename.
3. In the Rename object dialog box, type the new name.
type 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
Old names
AHU_01_DatSP_copy
AHU_01_OccCmd_copy
AHU_01_StPrSP_copy
AHU_01_VAVOccCmd_copy
AHU_01_VentReq_copy

178
04-16030-01-en, December 2014

Continued
Component
New names
Setting
AHU_02_DatSP
AHU_02_OccCmd
AHU_02_StPrSP
AHU_02_VAVOccCmd
AHU_02_VentReq
04-16030-01-en, December 2014

179

13.5

Template
reused.
Tip
Public Signals.
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.

Network/AHU_02/Application/Mirror.

180
04-16030-01-en, December 2014

ES1/Servers/CPlant AS to the Data from AS to AHU custom binding
template.

bindings selected.
5. Click OK.
04-16030-01-en, December 2014

181


Tip
Binding Point
Binding
Input DatSp_AS
.../BACnet
Input OccCmd_AS
.../BACnet
ue
Input StPrSp_AS
.../BACnet
Interface/Application/AHU_02_StPrSp/Value
Input VentReq_AS
.../BACnet Interface/Application/AHU_02
_VentReq/Value

182
04-16030-01-en, December 2014

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.
Binding Point
Binding
.../BACnet
/Value

Binding Point
Binding
.../BACnet
/Value

Binding Point
Binding
Input - DmprPosn
/Value
04-16030-01-en, December 2014

183

Continued
Binding Point
Binding
Input - OccStatus
/Value
Input - TermLoad
/Value
Value
Value
Value

Binding Point
Binding
Input - DmprPosn
/Value
Input - OccStatus
/Value
Input - TermLoad
/Value
Value
Value
Value
Mirror_AHU Program in the Automation Server AHU_02 Folder

184
04-16030-01-en, December 2014

Create the bindings for data flow between the AHU_02 b3 BACnet device and
AS/AHU_02/Programs/Mirror_AHU program:
Drag ...University X ES1/Servers/CPlant AS to the Data from AHU to
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
e
Output - VlvPosn_AS
.../AHU_02/Values/VlvPosn_AS/Value
Occupancy Program in the Automation Server AHU_02 Folder

AS/AHU_02/Programs/Occupancy program:
Binding Point
Binding
Input - Schedule
.../AHU_02/Schedules/Schedule/Value
OccStatus_AS
OccStatus_AS
Output - OccCmd
.../BACnet
ue
Output - VAVOccCmd
.../BACnet
/Value
Output - VentReq
.../BACnet
ue
DatSP Program in the Automation Server AHU_02 Folder

AS/AHU_02/Programs/DatSP program:
04-16030-01-en, December 2014

185

Table: Results Verification DatSP Program Bindings

Binding Point
Binding
TermLoad_AS
TermLoad_AS
Output - DatSp
.../BACnet
StPrSP Program in the Automation Server AHU_02 Folder

AS/AHU_02/Programs/StPrSP program:
Table: Results Verification StPrSP Program Bindings
Binding Point
Binding
DmprPosn_AS
DmprPosn_AS
Output - StPrSp
.../BACnet
Interface/Application/AHU_02_StPrSP/Valu
e

186
04-16030-01-en, December 2014
14
Deploying Servers
Topics
Moving a Project Database
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
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.
04-16030-01-en, December 2014

189
14.1 Moving a Project Database
14.1

You move a project database from an off-site computer to a customer site
computer, when a project cannot be deployed from an off-site computer.
For more information, see the Deploy topic on WebHelp.
In this example, you 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. You use a USB drive to move the project database from one
computer to another.
To move a project database

1. On the source computer, in WorkStation for Projects, ensure that the project is
backed up. For more information, see the Checking the Backup Status of a
Server topic on WebHelp. In this example, ensure that the University X
Project is backed up on the off-site computer.
2. Close WorkStation for Projects. In this example, close for WorkStation for
Projects on the off-site computer.
3. Wait 5 minutes to ensure that the project is closed.
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.

190
04-16030-01-en, December 2014
4. In Software Administrator, in the Project Configuration Server tab, copy

the path of the Projects folder. In this example, copy the path of the
Projects folder for the off-site computer.
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.
6. Move the individual project folder to a USB drive or to another appropriate

media. In this example, move the University X Project folder from the offsite computer to a USB drive.
04-16030-01-en, December 2014

191
7. On the target computer, in Software Administrator, in the Project

Configuration Server tab, copy the path of the Projects folder. In this
example, copy the path of the Projects folder for the on-site computer.
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.

192
04-16030-01-en, December 2014
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.
04-16030-01-en, December 2014

193
14.2

You use WorkStation for Projects to access the Project Configuration Server.
For more information, see the Log on to WorkStation for Projects topic on
WebHelp.
In this example, you log on to the Project Configuration Server on the on-site
computer, using the project user account Pete.
To log on to WorkStation for Projects

1. In the Building Operation WorkStation for Projects window, in the User
name box, type the user name. In this example, type Pete.
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.
In this example, type Pete.


194
04-16030-01-en, December 2014
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.
04-16030-01-en, December 2014

195
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.
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
The project opens in WorkStation for Projects.

196
04-16030-01-en, December 2014
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.
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.
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:
04-16030-01-en, December 2014

197
14.4 Deploying a Server
Table: University X ES1 Server Configuration

Component
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.

198
04-16030-01-en, December 2014
14.5 Logging on to WorkStation as a Building Operation User
14.5
Logging on to WorkStation as a Building

Operation User
You log on to WorkStation to securely access the functions in Building Operation.
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.
To log on to WorkStation as a Building Operation user

1. In the User name box, type the Building Operation user name.
example, type admin.
In this

04-16030-01-en, December 2014

199
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.

200
04-16030-01-en, December 2014
8. If the Select Default Workspace window is displayed, click the workspace

you want to have as the default. In this example, click Engineering.
04-16030-01-en, December 2014

201
14.6 Configuring a Factory-Set b3 BACnet Device after a Deploy
14.6
Configuring a Factory-Set b3 BACnet

Device after a Deploy
After a server deployment, you configure the serial numbers for the b3 BACnet
devices in the System Tree pane to associate the logical devices with the physical
devices. The factory-set b3 BACnet devices must be physically connected to the
Automation Server field bus.
In this example, you configure the serial number for the b3 BACnet device named
AHU_01.
To configure a factory-set b3 BACnet device after a deploy

1. In WorkStation, in the System Tree pane, select the b3 BACnet device that
you want to configure. In this example, select ...University X
ES1/Servers/CPlant AS/BACnet Interface/MSTP Network/AHU_01.
3. Click the Advanced tab.
4. In the Serial number box, type the serial number for the b3 BACnet device.
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.

202
04-16030-01-en, December 2014
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.
04-16030-01-en, December 2014

203
14.7 Commissioning a b3 BACnet Device
14.7
Commissioning a b3 BACnet Device

You synchronize the MAC address with the value in the database by commissioning
the b3 BACnet device. This is particularly useful in those situations where the
devices MAC address may not match the database (for example, a factory-set b3).
topic on WebHelp.
In this example, you commission the b3 BACnet devices named AHU_01, AHU_02,
VAV_01_01, VAV_01_02, VAV_02_01, and VAV_02_02. The devices are physically
connected to the network.
To commission a b3 BACnet device

2. In the List View, select the b3 BACnet devices that you want to commission.
In this example, select AHU_01, AHU_02, VAV_01_01, VAV_01_02,
VAV_02_01, and VAV_02_02.
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.

204
04-16030-01-en, December 2014
14.8 Downloading to a b3 BACnet Device
14.8
Downloading to a b3 BACnet Device

After a reset, you download the objects that remain in the database to the b3
BACnet device.
For more information, see the b3 BACnet Device Overview topic on WebHelp.
In this example, you download the objects that remain in the database to the b3
BACnet devices named AHU_01, AHU_02, VAV_01_01, VAV_01_02, VAV_02_01,
and VAV_02_02.
To download to a b3 BACnet device

2. In the List View, select the b3 BACnet devices for which you want to
download objects. In this example, select AHU_01, AHU_02,
VAV_01_01, VAV_01_02, VAV_02_01, and VAV_02_02.
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.
6. Click Close to close the Progress view.

04-16030-01-en, December 2014

205
14.9

You move a project database from an off-site computer to a customer site
computer, when a project cannot be deployed from an off-site computer.
In this example, you move the University X Project database from the on-site
computer (at the university) back to the off-site computer (at the Schneider Electric
office). You use a USB drive to move the project database from one computer to
another.
To move a project database

1. On the source computer, in WorkStation for Projects, ensure that the project is
backed up. For more information, see the Checking the Backup Status of a
Server topic on WebHelp. In this example, ensure that the University X
Project is backed up on the on-site computer.
2. Close WorkStation for Projects. In this example, close for WorkStation for
Projects on the on-site computer.
3. Wait 5 minutes to ensure that the project is closed.
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.

206
04-16030-01-en, December 2014
4. In Software Administrator, in the Project Configuration Server tab, copy

the path of the Projects folder. In this example, copy the path of the
Projects folder for the on-site computer.
folder. In this example, paste the path of the Projects folder for the on-site
computer.
6. Move the individual project folder to a USB drive or to another appropriate

media. In this example, move the University X Project folder from the onsite computer to a USB drive.
04-16030-01-en, December 2014

207
7. On the target computer, in Software Administrator, in the Project

Configuration Server tab, copy the path of the Projects folder. In this
example, copy the path of the Projects folder for the off-site computer.
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.

208
04-16030-01-en, December 2014
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.
04-16030-01-en, December 2014

209
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).

210
04-16030-01-en, December 2014
Schneider Electric | Buildings Division

www.schneider-electric.com/buildings
2014 Schneider Electric. All rights reserved.
04-16030-01-en
December 2014

Creating and Configuring A BACnet Network With b3 BACnet Devices Tutorial Guide

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Creating and Configuring A BACnet Network With b3 BACnet Devices Tutorial Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

StruxureWare Building Operation

Creating and Configuring a BACnet Network with b3

StruxureWare Building Operation

Copyright 2014 Schneider Electric. All rights reserved.

About This Guide ......................................................... 11

Additional Information .................................................. 17

04-16030-01-en, December 2014

Our Case Study ........................................................... 25

Creating the BACnet MS/TP Network .......................... 35

Creating and Configuring b3 BACnet Devices .............. 49

Creating I/O Points and Variables in the b3 BACnet

Creating a b3 BACnet Device Analog Input Point ......................... 58

Creating Variables in the Automation Server ................. 95

Creating Programs in Automation Server and b3 BACnet

Creating and Configuring Schedules in Automation

Creating a Digital Schedule ....................................................... 126

Creating Bindings for the b3 BACnet Devices ............. 129

Binding Values Using a Binding Template .................................. 132

Duplicating a b3 BACnet Device ................................. 147

Creating Bindings Internal to the Automation Server ... 161

Creating and Configuring a BACnet Network with b3 BACnet Devices

04-16030-01-en, December 2014

04-16030-01-en, December 2014

Binding Values Using a Binding Template .................................. 164

Duplicating b3 BACnet Devices .................................. 169

Deploying Servers ...................................................... 187

Creating and Configuring a BACnet Network with b3 BACnet Devices

The Introduction part contains information on the purpose

About This Guide

1 About This Guide

Purpose of This Guide

04-16030-01-en, December 2014

Creating and Configuring a BACnet Network with b3 BACnet Devices

1 About This Guide

How This Guide is Organized

Creating and Configuring a BACnet Network with b3 BACnet Devices

04-16030-01-en, December 2014

1 About This Guide

04-16030-01-en, December 2014

Creating and Configuring a BACnet Network with b3 BACnet Devices

Where to Find Additional Information

Figure: Help in StruxureWare Building Operation

The WebHelp site

Figure: Home page search

Filtering the information

04-16030-01-en, December 2014

Creating and Configuring a BACnet Network with b3 BACnet Devices

Figure: Search filters

Creating and Configuring a BACnet Network with b3 BACnet Devices

04-16030-01-en, December 2014

WEEE - Directive of the European Union (EU)

CE - Compliance to European Union (EU)

C-Tick (Australian Communications Authority (ACA))

Federal Communications Commission

04-16030-01-en, December 2014

Creating and Configuring a BACnet Network with b3 BACnet Devices

The Tutorial part contains a step-by-step description of

Our Case Study

3 Our Case Study

Figure: The School of Business and the Central Plant

The Cooling Plant consists of a single chiller with a primary-secondary pumping

04-16030-01-en, December 2014

Creating and Configuring a BACnet Network with b3 BACnet Devices