Introducing BACnet

Introducing BACnet
A Guide for Continuum Users
2010, Schneider Electric

All Rights Reserved
No part of this publication may be reproduced, read or stored in a retrieval system, or
transmitted, in any form or by any means, electronic, mechanical, photocopying, recording,
or otherwise, without prior written permission of Schneider Electric.
This document is produced in the United States of America.
Product Names are trademarks of Schneider Electric. All other trademarks are the property of their respective owners.
Title: Introducing BACnet: A Guide for Continuum Users
Revision: H
Date: October, 2010
Part number: 30-3001-863
Andover Plain EnglishTM is a trademark of Schneider Electric.
Andover InfinetTM is a trademark of Schneider Electric.
Andover InfinityTM is a trademark of Schneider Electric.
CyberStation Version 1.9
The information in this document is furnished for informational purposes only, is subject
to change without notice, and should not be construed as a commitment by Schneider Electric. Schneider Electric assumes no liability for any errors or inaccuracies that may appear
in this document.
On October 1st, 2009, TAC became the Buildings Business of its parent company Schneider
Electric. This document reflects the visual identity of Schneider Electric. However, there
remain references to TAC as a corporate brand throughout the Andover Continuum software. In those instances, the documentation text still refers to TAC - only to portray the
user interface accurately. As the software is updated, these documentation references will
be changed to reflect appropriate brand and software changes. All brand names, trademarks, and registered marks are the property of their respective owners.
Schneider Electric
One High Street
North Andover, MA 01845
(978) 975-9600
Fax: (978) 975-9782
http://www.schneider-electric.com/buildings
Introducing BACnet
A Guide for Continuum Users
30-3001-863
Revision H
October, 2010
Contents
Chapter 1 ............................................................................... 9
Integrated Native BACnet .......................................................... 9
Name References in this Document................................... 10
Related Documentation ...................................................... 10
Continuum/BACnet CyberStation - What Has Changed .......... 11
What is BACnet?................................................................. 11
How is BACnet Integrated with Continuum? ................... 11
BACnet Objects versus Continuum Objects ............... 12
BACnet PICS ................................................................ 13
Native BACnet and Continuum/BACnet Device Profiles 13
When Are the BACnet XDrivers Used?............................. 14
Device Restriction Differences Between Infinity and BACnet 14
Chapter 2 ............................................................................... 17
Overview of Hardware Differences .............................................
Continuum/BACnet Controller Overview .........................
Mixing Continuum and BACnet Networks.................
BACnet and web.Client ...............................................
BACnet Communications over Multiple IP Subnets .................
BACnet Communications with Foreign Devices .....................
17
18
20
21
22
24
Chapter 3 ............................................................................... 27
Starting BACnet ..........................................................................
Continuum/BACnet Concepts .....................................................
CyberStation Viewing Options ..........................................
Configuring BACnet Devices .............................................
Third-Party Devices - What Can I Do with Them?...........
Manually Controlling Continuum BACnet Points............
Command Priority ..............................................................
Continuum/BACnet Configuration Basics .................................
Set Up the Network or Load Your Existing Database......
Configure Your bCX1 (40x0) or b4920 Devices .................
27
27
28
28
29
29
30
34
34
34
Introducing BACnet for Continuum Users
Infinity Capabilities..................................................... 35
Configure b3xxx Devices.................................................... 35
Create Objects .................................................................... 36
Editor Differences ........................................................ 37
Set up Alarms..................................................................... 38
Using Templates for EventEnrollments and EventNotifications 39
Locate Existing BACnet devices........................................ 39
Save to Database ................................................................ 40
Disabling BACnet........................................................................ 42
Chapter 4 .............................................................................. 45
BACnet Program Editor..............................................................
Status Differences Between Infinity and BACnet Programs ...
BACnet Properties and Plain English .......................................
Proprietary BACnet Schedule Properties for Programs ..
BACnet versus Plain English Property Names................
Note regarding BACnet Numerics..............................
Plain English Keywords for BACnet ..........................................
ReadProperty......................................................................
Relinquish...........................................................................
WriteProperty.....................................................................
6 Schneider Electric
45
47
47
48
50
54
64
65
66
68
Chapter 1: Introduction
Chapter 1
Introduction
Integrated Native BACnet
Schneider Electric, formerly TAC and Andover Controls, has been
providing innovative building automation solutions for more than 25
years. Infinity and Andover Continuum systems are in use today in
over 40,000 applications. Throughout all these years, Schneider
Electric has been consistently successful with regards to connectivity.
Special interfaces, called XDrivers, allow Infinity and Continuum
systems to interoperate with dissimilar systems from Carrier, McQuay,
Grinnell, and others using their proprietary protocols.Through these
interfaces, our systems provide both environmental control and secured
access for hundreds of building sites throughout the world.
A building automation standard has emerged that provides for the
automatic interoperability of many manufacturers systems. BACnet,
the Building Automation and Control network standard developed by
ASHRAE allows products made by different manufacturers to be
integrated into a single building automated control system.
More and more construction projects are beginning to specify control
equipment that operates on the BACnet standard.
In the early 1990s, during BACnets infancy, representatives from
Schneider Electric were among the first to participate in its conception.
Our engineering expertise with control-related networking was called
upon in producing the first BACnet standard. In fact, much of the

internal communication layers designed into Continuums
CyberStation have been BACnet compliant since the products
introduction in 1998. BACnet XDrivers have been available as well.
In Andover Continuum CyberStation version 1.6 and higher and
BACnet controllers version 4.0 and higher, integrated Native BACnet
is included in our line of building automation solutions.
Name References in this Document

Throughout this document there are references to object classes and
object properties (attributes). The final section contains several charts
that map the names used for those properties by source (BACnet
specification, CyberStation, Command Terminal, and so on). This
document makes exclusive use of the names used by CyberStation.
Related Documentation
Please consult the following Andover Continuum documentation as
needed:
Table 1 Related Documentation
Document Name
Part Number
CyberStation online help

CyberStation Access Control Essentials 30-3001-405
Guide
CyberStation HVAC Essentials Guide
30-3001-1000
Andover Plain English Language

Reference Guide
30-3001-872
bCX1 Series Controller Technical

Reference Guide
30-3001-890
b3 and b4920 Controller Technical

Reference Guide
30-3001-862
Continuum/BACnet CyberStation - What Has Changed

If youve used Continuums Infinet (non-BACnet) versions of
CyberStation, you should have no problem using the BACnet versions.
Support for BACnet was added to Continuum on Version 1.6 and
greatly enhanced in subsequent versions. another difference when
using BACnet devices is that in BACnet, alarms are actually events
and the Import/Export (IE) method of reporting has been replaced with
change of value (COV). Many of these under-the-hood modifications
largely do not affect the user interface except where controls are added
to support the new functionality.
What is BACnet?
BACnet is a communication protocol started by ASHRAE that allows
products made by different manufacturers to be integrated into a single
building automated control system. This means that as long as they
meet the ANSI/ASHRAE Standard 135-2004 version (BACnet) or older,
different manufacturers products can communicate data to each other
over a network. The level of interoperability depends on how much of
the standard each vendor has implemented. Although the standard
specifies communications between devices, it does not address
programming or user interface issues.
Note: If you intend to incorporate a BACnet network into your site we
strongly advise that you obtain the BACnet standard and
learn the terminology to properly assess the level of
interoperability in the system. The specification can be obtained
from the ASHRAE bookstore as Standard 135-2004 at
www.ashrae.org.
How is BACnet Integrated with Continuum?

To make the product line more effective for existing Continuum users,
BACnet support has been simply added into the product. CyberStation
still supports Infinity, Infinet, and Infinet II devices. Alarms, listviews,
11
programs, CFR-11 features, and graphics are unchanged. In fact, if

you are not interested in using a BACnet network on your site,
you can simply turn the feature off.
For those interested in setting up a Continuum/BACnet system, you
will find it a very familiar experience. Configuration of the new
Continuum BACnet controllers is accomplished in a very similar
manner to that done with Infinity and Continuum controllers. All the
point, program, and graphic editors work the same. In addition, there
is a BACnet view complete with new editors that allow you to view the
status of and change the point values of other third-party BACnet
hardware.
There is a new way of setting up alarms in a BACnet system that
differs from the method you previously used to configure Infinity
alarms.
There is a new schedule editor that incorporates calendars and BACnet
date and time that is different than the old editor.
Version 1.73 introduced Continuum implementation of BACnet Loops,
TrendLogs, BACnet Backup and Restore enhancements, BACnet
Schedule enhancements, extended log enhancements, and other
enhancements based on BACnet Protocol Revision 4 (the 2004 version
of the BACnet Standard). For complete information, please see the
Continuum CyberStation online help.
Plain English is used to program Andover Continuum BACnet devices.
Some new features have been added to allow you to query and change
points on other BACnet third-party hardware. Through programming,
Continuum/BACnet allows a user to manipulate an Infinity point that
subsequently operates a BACnet device and vice versa.
BACnet Objects versus Continuum Objects

Like Continuum, all information in a BACnet system is represented in
terms of objects. Objects may represent a single physical point or
logical groupings of points that perform a specific function. The
information contained within a BACnet object is presented as a set of
properties. In Continuum, BACnet object properties are similar to an
objects attributes.
BACnet PICS
PICS (Protocol Implementation Conformance Statements) are detailed
descriptions of a devices inherent BACnet capabilities. PICS tell a
potential user what objects and BACnet services a device supports. It
also details the type of communications network, the baud rate, the
range of values each object property expects and whether a property is
writable or just read-only. PIC statements are available from each
BACnet manufacturer. These are used to assess the level of
interoperability between devices. Andover Continuums hardware and
software PICS can be found on our web site. The PIC statements can be
found in the Continuum section of the Technical Support node within
the Schneider Electric Global Extranet.
Native BACnet and Continuum/BACnet Device Profiles

Continuum/BACnet devices are considered native BACnet because
they inherently communicate utilizing BACnet messaging. Continuum/
BACnet devices can be connected to a BACnet system without
requiring a gateway device or software driver to translate to and from
any proprietary protocols.
There are six standard BACnet device profiles. Full descriptions of
these profiles can be found in the BACnet specification already
referenced. Any device that implements all the required BACnet
capabilities for a particular device type and interoperability area may
claim to be a device of that particular type. Devices may also provide
additional capabilities not specified in the standard.
z
BACnet Operator Workstation (B-OWS)
BACnet Building Controller (B-BC)
BACnet Advanced Application Controller (B-AAC)
BACnet Application Specific Controller (B-ASC)
BACnet Smart Actuator (B-SA)
BACnet Smart Sensor (B-SS)
The following are examples of Andover Continuum hardware that

fulfill the BACnet categories listed above:
z
The CyberStation/BACnet Workstation feature set is closest to the

feature set of the B-OWS profile.
13
The bCX1 (4040) is a BACnet B-BC device.
The b4920 System Controller/BACnet Router (revision 4.2) is a BAAC device.
The entire line of the b3xxx equipment controllers operate on the

MS/TP network. All b3 (revision 4.2 or higher) devices are BACnet
B-AAC devices.
When Are the BACnet XDrivers Used?

BACnet XDrivers are special interfaces that are required when you
want Infinity and Continuum systems to interoperate with third party
devices. Continuum version 1.6 and higher reduces the need for
XDrivers when communicating to BACnet devices. If the BACnet
devices are BACnet/IP, or are accessible via a BACnet/IP router, you
may only require CyberStation to discover the device, view/edit BACnet
objects, receive alarms, edit schedules, and create graphics.
To exchange data between Infinity controllers (for example,
NetController, NetController II, and i2 controllers) and a BACnet
system (including those with third party BACnet controllers - BACnet/
IP, BACnet over Ethernet), a bCX1 or b4920 provides the easiest
solution to interoperate. If control of a third-party device is required,
then XDrivers are still required. CyberStation can access and control
any BACnet Ethernet or IP controller. An XDriver would be required to
access a BACnet PTP device.
Schneider Electric offers XDrivers for BACnet Ethernet, BACnet/IP,
and BACnet PTP devices.
Device Restriction Differences Between Infinity and BACnet

Infinity devices have always had a restriction on the number of entries
in the Import/Export table. (Infinet devices can only reference 255
foreign points.) BACnet devices have a similar restriction, but it is not
a limitation in the number of points, it is a limitation in the number of
foreign devices.
Andover Continuums implementation of standard BACnet devices

(such as b3 controllers) assigns a restriction to the amount of
communications initiated by the device. This means that Andover
Continuum limits the number of devices that each device can initiate
communication with. In particular, the limitation applies to these types
of communications: Point-to-Point (read and write), COV subscription
requests, and event notifications.
The b3 controllers are restricted to 32 devices, which means they can
simultaneously deliver alarms, write and/or read values in up to 32
different devices (Andover Continuum or third-party). The bCX1 and
the b4920 permit COV relationships with up to 255 devices.
15
Chapter 2: Continuum/BACnet Hardware
Chapter 2
Continuum/BACnet
Hardware
Overview of Hardware Differences

In non-BACnet Continuum systems, the main focal point is the CX
(NetController or NetController II). These controllers are connected by
Ethernet to the WorkStation and then through Infinet to other
equipment controllers such as TCX850s, i2865s, TCX845s and all other
Infinet devices.
With Continuum/BACnet, new controllers (bCX1 40x0, b4920) become
the interface or router to the system. Like the CX or NetController, the
bCX1 40x0 and b4920 controllers connect directly to the Ethernet. The
new controllers communicate with the Continuum Workstation;
however, the equipment controllers connected to the bCX1 40x0 and
the b4920 do not use Infinet to communicate. Instead, the controllers
use another RS-485 protocol called the BACnet MS/TP. Infinet (or i2)
controllers cannot connect to MS/TP; therefore, we have introduced the
b3 series, a complete line of BACnet compatible equipment controllers.
The b3 series is functionally equivalent to the entire i2 product line.
17
Figure 1 Unlike Infinet networks, MS/TP networks require terminators be placed

at each end as shown in the diagram above.
Continuum/BACnet Controller Overview

The following information lists the basic features included in the
BACnet controllers. Specific information on each controller may be
found in the b3 and b4920 Controller Technical Reference, 30-3001-862.
Table 2 Continuum/BACnet Controller Overview

Model
Inputs
Outputs
b3608
8 Universal
None
b3624
24 Universal
None
b3800
8 Universal Smart
Sensor
8 Form C
b3804
8 Universal Smart
Sensor
4 Form C
4 Analog
8 Universal Smart
Sensor
8 Form C
8 Universal Smart
Sensor
z
z
4 Universal Smart
Sensor
b3810
b3814
b3850
b3851
b3853
b3865
b3866
b3867
b3885
Other Features
Output Override Control
Expansion Interface
4 Form C
Output Override control
4 Analog
Expansion Interface
3 Form A
1 Airflow Sensor
1 Form K Tri-state
Expansion Interface
4 Universal Smart
Sensor
3 Form A
Expansion Interface
1 Form K Tri-state
4 Universal Smart
Sensor
3 Form A
2 Airflow Sensors
1 Form K Tri-state
Expansion Interface
4 Universal Smart
Sensor
3 Form A Triac
1 Airflow Sensor
1 Tri-state Actuator
Control
Built-in Actuator
4 Universal Smart
Sensor
3 Form A Triac
1 Airflow Sensor
control
Built-in Actuator
2 Analog
4 Universal Smart
Sensor
5 Form A Triac
2 Analog
2 Universal
2 Form A Triac
1 Airflow Sensor
control
Built-in Actuator
19
Table 2 Continuum/BACnet Controller Overview

b3887
b3887-L
b3920
b4920
bCX1 4000
bCX1 4040
3 Universal Smart
Sensor
4 Form A Triac
1 Form A Relay
3 Universal Smart
Sensor
4 Form A Triac
120/230VAC powered
1 Form A Relay
24VAC power output
16 Universal Smart
Sensor
8 Form C
8 Analog
Expansion Interface
16 Universal Smart
Sensor
8 Form C
8 Analog
Expansion Interface
Ethernet Router
Registered Foreign Device
Ethernet Router
BBMD
Optional SNMP Alarming
Ethernet Router
Controller
Optional Expansion
Interface
BBMD
Optional SNMP Alarming
Custom Web Pages

through Plain English
None
None
None
None
Mixing Continuum and BACnet Networks

The specific design of the Continuum/BACnet product allows seamless
integration of Infinity CX, Continuum NetController, NetController II,
BACnet bCX1, and b4920 system controllers. CyberStation interacts
effortlessly with each controller type.
BACnet and web.Client

BACnet objects can also be viewed using the web.Client product.
21
BACnet Communications over Multiple IP Subnets

BACnet devices use two types of messages for communication:
UNICAST and BROADCAST.
UNICAST messages are communications from one BACnet device to
another:
BROADCAST messages are from one device to every device on the

subnet:
When traversing an Intranet or the Internet, subnets are connected

together through IP routers. IP routers block all broadcast messages,
including BACnet broadcasts:
A special device can be used to allow BACnet broadcast messages to

traverse IP routers by packaging them into unicasted IP packets. That
device is called a BACnet Broadcast Management Device (BBMD). The
BBMD is installed on the subnet(s) where you require access:
23
The bCX1 can be configured to act as a BBMD. Also, CyberStation,

version 1.62 and higher, allows you to designate it to act as a BBMD
device as well. Refer to the CyberStation online help system for specific
information about setting up your CyberStation to act as a BBMD.
Note: Only one BBMD can exist on a particular subnet.
BACnet Communications with Foreign Devices

It is not economical to install, configure, and maintain a BBMD on a
subnet with a small number of BACnet IP devices. Although it is costefficient to operate a subnet without a BBMD, BACnet/IP devices
require a mechanism to allow them to communicate with devices on
other IP subnets, and to associate them with a BACnet network. In
BACnet, this type of required device is called a foreign device. In the
diagram below, the b4920 on Subnet 3 would be a foreign device
because its Subnet include no other BACnet devices:
There is no restriction on where these foreign devices are or how they

gain access to the Internet. Such a foreign device could just as easily be
a workstation on a full-time Internet subnet or a laptop accessing the
Internet through an Internet Service Provider at home.
You must register the IP address of the foreign device with a BBMD
that exists on the network. Not all BACnet devices can be registered as
foreign devices; refer to the PICS of each device to see if it supports
foreign device registration.
Each BBMD maintains its individual Foreign Device Registration
information and does not share this information with other devices.
When a BBMD receives a broadcast message from its local network, it
forwards one copy of the message to the devices in its Foreign Device
Registration list. Therefore, information is exchanged, but not shared.
CyberStation version 1.62 and higher allows you to register a
CyberStation as a foreign device to a BBMD. Refer to the CyberStation
online help system for specific information.
The bCX1 and the b4920 controller may be registered as foreign devices
as well. This is done through the commissioning process that is
described in the bCX1 Controller Series Technical Reference (30-3001890) or the b3 and b4920 Controller Technical Reference Guide (303001-862) for the b4920.
25
Chapter 3: Continuum/BACnet Concepts and Configuration
Chapter 3
Continuum/BACnet
Concepts and Configuration
Starting BACnet
After installation, the system is automatically set up to allow BACnet
messaging and viewing. You begin setting up your site as you did with
other versions of CyberStation.
Continuum/BACnet Concepts
There are a few BACnet features that you will come across in menus
and windows that will be reviewed in the following sections. These
features are:
z
CyberStation Viewing Options
Configuring BACnet Devices
Third-Party Devices - What Can I Do with Them?
Manually Controlling Continuum BACnet Points
Command Priority
27
CyberStation Viewing Options

This version of CyberStation includes new Explorer viewing options
added to address the presence of the BACnet devices in the object tree.
A new folder (BACnet Devices) appears in the tree.
All devices that you create and any configured third-party devices show
up as a sub-tree inside this folder. The folder introduces a new icon for
the tree, the BACnet icon:
Continuum/BACnet offers you three ways to view Andover Continuum
BACnet devices in the Explorer. The viewing options are:
z
As an Infinity Controller and BACnet device
As a BACnet device only
As an Infinity device only
A full explanation of these new viewing options may be found in the

BACnet topics of the CyberStation online help.
Configuring BACnet Devices

Andover Continuum BACnet devices are configured using the
CyberStation workstation and must be configured in order to create
objects. While some aspects of Andover Continuum BACnet controllers
can be configured by a third-party workstation, the proprietary aspects
of our devices must be configured using CyberStation.
Similar to Andover Continuum BACnet devices, CyberStation cannot

configure inherently proprietary aspects of a third-party device, such as
programming. The BACnet standard does not specifically address
programming; therefore, if applicable, each BACnet vendor uses its
own programming language from its own programming tool.
Third-Party Devices - What Can I Do with Them?

Once a third-party BACnet device is configured, you can detect its
presence and view it in the object tree of the CyberStation. You can
create the following object classes in a third-party device:
z
EventEnrollments
EventNotifications (NotificationClass in the BACnet standard)
Schedules
Calendars
TrendLogs
Loops
Whether or not an object type can be created is determined by the

individual device, and is documented in its PICS. When supported by
the device, CyberStation can create any supported object type, even on
third-party controllers. You can view the current state of the device and
change any BACnet property that the device makes writable.
Manually Controlling Continuum BACnet Points

Sometimes, during the testing of an installation, it is helpful to be able
to enable/disable and/or change the value of various points in the
system. Continuum BACnet device appears as both an Infinity and a
BACnet controller in the object tree. Once a point is configured, you
have the option of reading or changing its value through either its
Infinity point editor or its BACnet editor. There are obvious advantages
to using the already familiar Infinity editor. Some BACnet-specific
features are only available through the BACnet editor.
29
Command Priority
When the actions of two or more application programs or operators
conflict with regard to the value of a property, there is a need to
arbitrate between them. The objective of the arbitration process is to
ensure the desired behavior of an object that is manipulated by several
program (or non-program) entities.
In Continuum, the Plain English Firing Order insures that critical
programs have a higher priority than the other less-critical ones. You
can determine which program has priority. If two or more operators
attempt to control the same output object, the last command received
becomes the output value.
In BACnet there is a more specific mechanism than the Plain English
Firing Order, it is called Command Priority. Command Priority applies
to programs and manual actions. Setting the command priority is done
through either the Plain English or BACnet editors.
There are sixteen priority levels, where sixteen is the lowest priority
level and 1 is the highest priority level. The priority levels were
implemented to give priority to controls where conflicting control
situations may occur. For example, consider a fireman who wishes to
control a blower mechanism that is normally controlled by a program.
Obviously, the fireman does not want a program or another operator to
defeat his control. In this case, the fireman sets the blower to OFF with
a priority of Life Safety, which has a value of 1. A program may have a
default command priority of 10, and controls in graphic panels may

have a priority of 8. As long as the fireman uses the Life Safety priority,
he is assured the blower will be under his control.
Value has been set by

operator at priority level 4.
Value does not change at this stage
because earlier setting had a higher
priority. The value at priority level 10
does change and will take effect if all
priority levels above are relinquished.
Value from priority level 4 is
relinquished. Output changes
value to the next higher priority
request (level 10 from program).
Note: In Continuum, you refer to the BACnet Present_Value

property as Value.
The value property of outputs and value objects (analog value, binary
value, multi-state value) has a 16-entry table where the desired value
is stored. Each table entry corresponds to a given priority level. The
example below shows a typical output where three value requests have
been made. The value in the highest priority table location will be the
current value. In this case the output will be 28.
Table 3 Command Priority Value
Priority
Level
Value
Null
Null
Null
28
Null
31
Table 3 Command Priority Value

6
Null
Null
Null
Null
10
11
Null
12
Null
13
22
14
Null
15
Null
16
Null
When an action on longer commands the output it relinquishes its

value request and the output assumes the value stored in the next
highest priority table entry. In the following example, the former value
of 28 in priority 4 has been relinquished (set to Null) and the request at
priority level 10 sets the value at 6.
Priority
Level
Value
Null
Null
Null
Null
Null
Null
Null
Null
Null
10
11
Null
12
Null
13
22
14
Null
15
Null
16
Null
If all table entries are Null, the default value for the output is
determined by the value of the BACnet property called
relinquish_default. In Continuum, the value is set in the Relinquish
Default field of the Command Priority tab of the AnalogOutput,
AnalogValue, BinaryOutput, BinaryValue, MultistateOutput, and
MultistateValue editors.
The Command Priority of each value change is assigned in the BACnet
Preferences dialog. A full description of setting priorities can be found
in the BACnet topics of the CyberStation online help.
33
Continuum/BACnet Configuration Basics

The following discussion is an outline of the steps necessary to get your
BACnet devices, both Continuum and third-party, online. For full
details on the steps, refer to the CyberStation online help.
Set Up the Network or Load Your Existing Database

Step 1: The first step is to create the network object. If you have an
existing database with your setup all configured, everything
should appear in the Explorer as it did with earlier versions of
the software with the exception of a new set of folders for the
BACnet devices and networks.
Configure Your bCX1 (40x0) or b4920 Devices

Step 2: The bCX1 (40x0) and the b4920 devices connect directly to the
Ethernet. Before they can communicate, you must set up
various network address just as you had to for the
NetController.
Note: Commissioning the bCX1 (40x0) and the b4920 devices is
different than the NetController. You need at CAT5 cable
connected between a PC and the controllers Ethernet port.
Step 3: If your system uses a proxy server, disable it before
proceeding.
Step 4: Disable DHCP Services on your PC.
Step 5: Set your IP address to 196.254.1.2
Step 6: Using the crossover cable, connect your PC to the controllers
Ethernet port
Step 7: Run your web browser and enter the following url: http://
169.254.1.1
Step 8: At the logon screen, enter the default Andover Continuum

username and password.
Step 9: Edit the network parameters on the web screen.
After commissioning, the controller is ready to be set up like any other
controller.
Infinity Capabilities
All Andover Continuum BACnet devices are both BACnet and Infinity
controllers; therefore, it is possible to access Infinity objects through a
BACnet controller. Select New > InfinityController and the familiar
device editor appears. The configuration process is similar to the
NetController configuration process.
Although the b4920 and the bCX1 40x0 act somewhat like a
NetController, you cannot load XDrivers into a b4920 or a bCX1.
Once the controller is completely configured it shows up as both an
Infinity controller and a BACnet controller in the Explorer.
Configure b3xxx Devices

Connect any third party MS/TP devices to the network before
performing this step. It is necessary that they be present during the
learn operation. The bCX1 and b4920 detect any used MS/TP
addresses and assign b3xxx controllers unused addresses. Third party
devices that are added later must be assigned an address that has not
been assigned to any other device.
The bCX1 and b4920 connect to equipment controllers via MS/TP.
These devices are configured and treated just like Infinet devices. Open
the COMM Port of the bCX1 or b4920 where they are connected and
perform a Learn operation.
35
Create Objects
Configuration of objects is done the same way as the Infinity side of the
device. However, BACnet objects are not the same as Infinity points.
The system will display Infinity points as their BACnet object
equivalents, after the corresponding BACnet device is saved to the
database. Once the object is configured it appears as both an Infinity
and BACnet object. Editing the value of these objects can be done
through either the Infinity or BACnet object editors.
Note: If you change the ElecType of a previously assigned
InfinityInput or InfinityOutput, you may have to manually
resave the object from the BACnet view and correct any
references to the object in programs or graphics. This is required
only if the ElecType change causes the BACnet object type to
change, according to the table below. For example, changing
DegC to DegF retains the same object type, but changing DegF
to Digital changes the object type, thus requiring a resave of the
BACnet objects.
The following table lists the Infinity class and its BACnet equivalent.
Table 4
Infinity Class
BACnet Object Type
InfinityInput (ElecType: ACCTemp(DegC))
Analog Input
InfinityInput (ElecType: ACCTemp(DegF))
Analog Input
InfinityInput (ElecType: InputCurrent)
Analog Input
InfinityInput (ElecType: Voltage)
Analog Input
InfinityInput (ElecType: Counter)
Analog Input
InfinityInput (ElecType: Digital)
Binary Input
InfinityInput (ElecType: Supervised)
Multi-State Input
InfinityOutput (ElecType: Current)
Analog Output
InfinityOutput (ElecType: Voltage)
Analog Output
InfinityOutput (ElecType: Digital)
Binary Output
Table 4
InfinityOutput (ElecType: Tristate)
Multi-State Output
InfinityNumeric
Binary Value
InfinityNumeric
Analog Value
InfinityNumeric
Multi-State Value
Program
Program
Continuums implementation of several other BACnet object types is
somewhat different, as follows:
z
Calendar, Device, EventEnrollment, Loop, and TrendLog are

strictly BACnet object types. There are no Infinity equivalents.
However, these BACnet object types are integrated into
Continuums implementation of BACnet, including integration into
the BACnet section of Continuum Explorer.
Schedule and File, though they have the same name, are both
Infinity class and BACnet object type. However, they mean
different things to Infinity and BACnet, respectively.
Though Notification Class is a BACnet standard object type name,

Continuum uses another name - EventNotification. Therefore,
BACnet object types named EventNotification are Notification
Class object types. On third-party devices (in non-Continuum
systems) they appear as Notification Class objects.
Editor Differences
Each device manufacturer may support different properties. If you
encounter a tab on any class object editor with some, or all, areas
unavailable (grayed-out), it is because that property is not supported on
the particular object you are editing. This may vary from class to class.
In order to accommodate some differences (versus Infinity objects) of
the BACnet standard, the Units field is no longer a free-entry editable
text field. It has been changed to a drop-down selection menu.
37
Set up Alarms
Configuring alarms for BACnet devices differs somewhat from the
standard Continuum alarm configuring procedure. A newer object
class, called EventEnrollment, is used instead of the AlarmEnrollment
object. The complete procedure for doing this task is covered in the
CyberStation online help system.
In Infinity you could have one point with up to eight alarms attached.
In BACnet there is one EventEnrollment for each alarm. However, a
point can have any number of EventEnrollments.
In BACnet, you attach EventNotifications, which correspond with the
BACnet Notification Class object type, and objects to
EventEnrollments. The EventEnrollment object represents and
contains the information required for managing events within BACnet
systems. The EventEnrollment object contains the event-type
description, the parameters needed to determine if the event has
occurred, and a link to an EventNotification object and the object to
which the event applies. Use the EventEnrollment editor to access and
edit EventEnrollment objects.
Each EventEnrollment contains two properties that are references to
other objects:
z
EventNotification: Refers to the previously mentioned

EventNotification object.
Object Property Reference: References the alarmed property of a

specific object.
The purpose of an EventEnrollment is to define criteria that will

generate an event when applied to the attached object and will
transmit to the event recipients as defined by the attached
EventNotification.
BACnet requires that EventNotifications must exist in the device
where the EventEnrollment lies an Andover Continuum devices
specifically require EventEnrollments to exist in the device where the
alarmed point lies. Make sure the EventEnrollment and the
EventNotification exist within the same controller.
Note: You cannot attach a BACnet alarm to an Infinity System

Variable. To alarm a system variable, you must use Plain
English. First, set up an alarmed InfinityNumeric. Then, set the
numeric equal to the System Variable.
Using Templates for EventEnrollments and EventNotifications

As you will be creating a large number of EventEnrollments and
EventNotifications, a comprehensive template system has been created
to streamline the process. Full documentation on templates for these
objects is included in the CyberStation online help system.
Locate Existing BACnet devices

If you are using Continuum/BACnet on a mixed (Andover Continuum
and third-party system) BACnet site, the first thing you should do is
learn any existing BACnet pre-configured connected devices:
Step 1:
Right click Root in the Explorers navigation pane and the

object drop-down menu appears.
39
Step 2: A new BACnet network device icon

appears in the
navigation pane. Click the + sign next to that icon to view any
found BACnet devices.
Depending on the size of your network and the quantity of BACnet

devices, it may take some time for all the devices to appear. During the
operation, a progress bar cannot be displayed because the number of
third-party devices on your site is an unknown quantity.
Save to Database
Although the BACnet devices have been found, the objects contained in
those devices have not been saved to the database. Therefore, once a
device is located, you must save the objects to the database. You can
have objects automatically saved when you create them by selecting the
Automatically Save New BACnet Devices to Database option in
the BACnet Preferences dialog.
To manually save a BACnet device, perform the following steps:

Step 1:
Right click the BACnet device and select Send to Database

option from the popup menu.
The contents of the device will upload to the SQL database.

There is no explicit indication of the save operation, which could take
up to several minutes. Whenever the distribution server is active, the
icon animates to indicate the activity. Connecting lines appear between
the document and the controller, and a red dot animates along the
connecting lines:
Step 2: Once the process is completed, select Refresh from the

Explorers View menu. The exclamation flag disappears from
the devices icon in the Explorer.
Note: There is a significant difference between the Save to Database
feature on the BACnet view versus the Save to Database
feature on the Infinity view for the same controller. The Infinity
view saves the complete object information to the database,
including proprietary Andover Continuum properties, such as
ElectType and Channel number. The BACnet view saves only
the BACnet objects and properties to the database.
41
Disabling BACnet
To make it easy for existing BACnet installers, CyberStation is shipped
with BACnet support enabled. However, if your site does not contain
any BACnet devices, including bCX1 or b4920, it is simple to disable
BACnet messaging and to hid any BACnet devices that are created by
the system.
Use the following steps to disable BACnet:
Step 1:
Right click on the Continuum icon in the lower right hand

corder of the window task bar.
Step 2: Select BACnet Preferences from the popup menu.
Step 3: The first item on the list is Enable BACnet; change the value
of item 1 to False.
Selecting False disables any BACnet messages from being transmitted

or received. A BACnet Devices folder will still appear in the object
tree, but there will be no devices inside.
43
Chapter 4: Plain English for BACnet
Chapter 4
Plain English for BACnet
BACnet Program Editor

Plain English programs still run on our BACnet controllers. In fact, you
can view some statistics about programs running on third-party devices
with the new BACnet Program editor.
45
The Program editor allows you to run, restart, halt, and check the
status of BACnet programs running on Andover Continuum BACnet
devices (bCX, b4, and b3 controllers) and third-party BACnet devices.
Note: On third-party BACnet devices, you might also be able to load

and unload BACnet programs through the Program editor,
depending on whether the third-party device supports these
capabilities. As programs are always loaded, you cannot load
and unload programs on Andover Continuum BACnet devices.
Status Differences Between Infinity and BACnet

Programs
The following table lists differences in states, the Infinity state and its
BACnet equivalent, under which a program can be operating.
Table 5 System Differences between Infinity and BACnet
Programs
Infinity
BACnet
Inactive
Idle
Active and Enabled
Running
Active and Disabled
Halted
Active and Enabled (waiting

on an asynchronous process
- serial I/O)
Waiting
Note: Two BACnet Program states, Loading and Unloading, do not

correspond with any Infinity Program state and are therefore
not implemented.
BACnet Properties and Plain English

When you create an Infinity object in a BACnet controller, it is also a
certain type of BACnet object. The table earlier in this document listed
Infinity object classes and their BACnet equivalents.
The tables on the following pages map each BACnet objects properties
to the equivalent Plain English name. You would use the Plain English
name in a Plain English program.
47
Any properties not listed in the BACnet object properties tables are
properties that are not supported in Plain English. The READ/
WRITE column indicates whether these properties can be changed (W)
or just read (R) by third-party devices, CyberStation, or a Plain English
Program.
The Restrictions column indicates any Andover Continuum specific
restriction on the property. Our restrictions are documented in each
devices PICS. The specific restrictions do not necessarily coincide with
those of a third-party device.
Proprietary BACnet Schedule Properties for Programs

Andover Continuum has three proprietary BACnet Schedule-object
properties that are used in Plain English programs to optimize the
start and stop times for scheduled events in HVAC systems. These
proprietary properties replaced the traditional occupancy functions;
however, they are more general because they simply provide
information about scheduled events. For example, they might supply
information when rooms need to be prepared with heating before
occupancy or when lights need to be shut off after occupancy.
Note: Also refer to the Transition Time fields on the Current State tab
of the Schedule editor.
The Schedule-object properties are as follows:
Table 6 Schedule-object properties
Proprietary Property
Meaning
PreviousTransitionTime
The time when the Schedules

Present_Value most recently
changed.
NextTransitionTime

Present_Value is next scheduled to
change.
Table 6 Schedule-object properties

FollowingTransitionTime

Present_Value is next scheduled to
change the value following the time
indicated by Next_Transition.
The Schedule properties are unsigned integer values, each giving a

date and time expressed as the number of seconds. Although Schedule
properties are defined in this way, Plain English identifies them as
DateTime values.
Plain English, which specifies the behavior of Program objects, can
compare these items with the present time and compute time intervals.
In a Plain English program, the value of each property would be
specified as follows:
z
ScheduleName: PreviousTransitionTime
ScheduleName: NextTransitionTime
ScheduleName: FollowingTransitionTime
ScheduleName represents the name of the Schedule object, whose

transition times are being computed.
Each transition indicates a scheduled change in the value of the
Schedules Present_Value property. These values are stored as, and can
be read or written as, InfinityDateTime values.
Note: In a Plain English program, the ReadProperty function can be
used to retrieve the values of these properties, which are read
only. Refer to Plain English Keywords for BACnet for further
information.
When determining a transition, time-value paris that specify the same
value as the Schedules PresentValue (that do not change the value) are
not considered transitions. Similarly, if two or more time-value paris
have the same time, only the last pair with that time is used for
determining a transition.
For additional information about the proprietary Schedule properties
for programs, see the Andover Plain English Language Reference, 303001-863, or the Continuum online help system.
49
BACnet versus Plain English Property Names

For each BACnet object type, the following tables compare the BACnet
objects property names with the equivalent Plain English names. You
would use the Plain English names in a Plain English program.
Any properties not listed in the following tables are properties that are
not supported in Plain English. The READ/WRITE column indicates
whether these properties can be changed (W) or just read (R) by Plain
English.
The Restrictions column indicates any Andover Continuum specific
restriction on the property. Our restrictions do not necessarily coincide
with those of a third-party device.
Table 7 Analog Input
BACnet Property
Plain English
Name
READ/WRITE
R/W
COV Increment
COVIncrement
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Constant based upon

the class
Out_Of_Service
OutOfService
Cannot be set false if

channel not
configured
Present_Value
Value
Units
Units
Restrictions
Table 8 Binary Input

BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Number_Of_States
NumberOfStates
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Restrictions

channel not
configured
Table 9 Multistate Input

Restrictions

channel not
configured
51
Table 10 Analog Output

BACnet Property
Plain English
Name
READ/WRITE
R/W
COV Increment
COVIncrement
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Relinquish_Default
RelinquishDefault W
Units
Units
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Restrictions

channel not
configured
Table 11 Binary Output
Restrictions

channel not
configured
Table 11 Binary Output

Polarity
Polarity
Present_Value
Value
Relinquish_Default
RelinquishDefault W
Table 12 Multistate Output

BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Number_Of_States
NumberOfStates
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Relinquish_Default
RelinquishDefault W
Restrictions

channel not
configured
1..3
The following tables are for objects that do not have an ElecType. When
you create the InfinityNumeric object you must select a BACnet Object
Type from a drop down list within the InfinityNumeric editor.
Table 13 Analog Value
BACnet Property
Plain English
Name
READ/WRITE
R/W
COV Increment
COVIncrement
Description
Description
Restrictions
Limited to 32
characters
53
Table 13 Analog Value

Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Relinquish_Default
RelinquishDefault W
Units
Units
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Relinquish_Default
RelinquishDefault W
Table 14 Binary Value

Restrictions
Note regarding BACnet Numerics

Due to the internal workings of the Andover Continuum BACnet
controllers, if you create a Numeric (Binary Value) in a b3 or b4
BACnet controller and you import that value into another controller for
use in controlling an output (using the standard Continuum points and
program syntax), the output will pulse once on change-of-state then
shut off (equivalent to output = 1).
Similarly, changing the BinaryValue from inactive to active will cause

the output to pulse as well.
55
Example 1
The program below in the importing controller is a one-line looping
program as follows:
output1= B4/B3/BinaryValue
A possible use for this would be a global occupancy point being used to
turn the lights on.
Example 2
Step 1:
Write a Plain English program to copy a BinaryValue (BV) to a

BinaryOutput (BO).
Step 2: Set the BV to Inactive. Observe that the BO is Inactive.

Step 3: Set the BV to Active. Observe that the BO pulses for one
second.
The proper way to perform this function would be to use the BACnet
objects, BinaryValue and BinaryOutput, in your program.
Example:
BACnetDevices\B4\Output1=BACnetDevices\Bnet123\B3\Bina
ryValue
Now, when the BinaryValue is true, active, on, or 1, the output will be
set to on.
Table 15 Multistate Value
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Limited to 32
characters
Event_State
EventState
Always Normal
Number_Of_States
NumberOfStates
255*
Object_Name
Name
Restrictions
Table 15 Multistate Value

Object_Type
Type
Out_Of_Service
OutOfService
Present_Value
Value
Relinquish_Default
RelinquishDefault W
1..255
*255 or a variable based on standard Continuum enumerations.

Table 16 Program
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Object_Name
Name
Object_Type
Type
Out_Of_Service
OutOfService
Program_Change
StatusChange
Program_State
Status
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Object_Name
Name
Object_Type
Type
Present_Value
Value
Priority_For_
Writing
Priority
Restrictions
Limited to 32
characters
Table 17 Schedule
Restrictions
Limited to 32
characters
57
For a Schedule object, Andover Continuum provides three additional

proprietary BACnet properties:
PreviousTransitionTime
NextTransitionTime
FollowingTransitionTime
These properties are all writable. Please see the section, Proprietary
BACnet Schedule Properties for Programs for further information.
Table 18 Calendar
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Object_Name
Name
Object_Type
Type
Date_List
DateList
Present_Value
Value
Plain English
Name
READ/WRITE
R/W
Restrictions
Limited to 32
characters
Table 19 Device
BACnet Property
APDU_Segment_
Timeout
APDUSegTimeout W
APDU_Timeout
APDUTimeout
Application_
Software_version
ApplSoftwareVers R
ion
Backup_Failure_
Timeout
BackupFailureTi
meout
Configuration_Files ConfigurationFile
List
W
R
Restrictions
Table 19 Device
Daylight_Savings_
Status
DaylightSavingsS
tatus
Firmware_Revision
FirmwareRevision R
Last_Restore_Time
LastRestoreTime
Local_Date
LocalDate
Local_Time
LocalTime
Max_APDU_Lengt
h_Accepted
MaxAPDUAccept
ed
Model_Name
ModelName
Number_Of_APDU
_Retries
NumberAPDURet W
ries
Object_Name
Name
Object_Type
Type
Protocol_Conforma
nce_Class
ProtocolConfClass R
Protocol_Version
ProtocolVersion
Segmentation_Sup
ported
SegmentationSup
port
System_Status
System_Status
UTC_Offset
UTCOffset
Vendor_Identifier
VendorIdentifier
Vendor_Name
VendorName
0-255
59
Table 20 Event Enrollment

BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Event_State
EventState
Event_Type
EventType
Notify_Type
NotifyType
Object_Name
Name
Object_Type
Type
Restrictions
Limited to 32
characters
*see below
*Limited to Change_Of_State, Change_Of_Value, Floating_Limit,

Out_Of_Range, and Buffer_Ready
Table 21 Notification Class
BACnet Property
Plain English
Name
READ/WRITE
R/W
Description
Description
Object_Name
Name
Object_Type
Type
BACnet Property
Plain English
Name
READ/WRITE
R/W
Archive
Archive
Description
Description
File_Access_Method
AccessMethod
Restrictions
Limited to 32
characters
Table 22 File
Restrictions
Table 22 File
File_Size
Size
Writing is enabled in
Restore mode, but
the value is limted to
0 or the current file
size.
File_type
FileType
Modification_Date
ModificationDate
Object_Name
Name
Object_Type
Type
Read_Only
ReadOnly
BACnet Property
Plain English
Name
READ/WRITE
R/W
Action
Action
Bias
Bias
Controlled_Variabl
e_Units
ControlledVariabl
eUnits
Controlled_Variabl
e_Value
ControlledVariabl
eValue
Derivative_
Constant
DerivativeConsta
nt
Derivative_Constan DerivativeConsta
t_Units
ntUnits
Description
Description
Event_State
EventState
Integral_Constant
IntegralConstant
Table 23 Loop
Restrictions
61
Table 23 Loop
Integral_Constant_
Units
IntegralConstant
Units
Maximum_Output
MaximumOutput
Minimum_Output
MinimumOutput
Object_Name
Name
Out_Of_Service
OutOfService
Output_Units
OutputUnits
Present_Value
Value
Priority_For_
Writing
Priority
Proportional_Const
ant
ProportionalConst W
ant
Proportional_Const
ant_Units
ProportionalConst W
antUnits
Reliability
Reliability
Setpoint
Setpoint
Update_Interval
UpdateInterval
BACnet Property
Plain English
Name
READ/WRITE
R/W
Buffer_Size
BufferSize
COV_Resubscriptio
n_Interval
COVResubscriptio R
nInterval
Description
Description
Event_State
EventState
Table 24 TrendLog
Restrictions
Table 24 TrendLog
Log_Enable
LogEnable
Log_Interval
LogInterval
Object_Name
Name
Object_Type
Type
Record_Count
RecordCount
Stop_When_Full
StopWhenFull
Total_Record_
Count
TotalRecordCount R
Can write 0, only
63
Plain English Keywords for BACnet

In order to accommodate BACnets command priority scheme, Plain
English has been modified to include BACnet compliant keywords. The
following pages describe these additions.
There are three new keywords:
ReadProperty
Relinquish
WriteProperty
ReadProperty
Format
ReadProperty (Object_Property, Index)
Purpose
To get (return) the property of a BACnet object.
Remarks
Replace Object_Property with the object name, including a full path

name, followed by a property name. The object Identifier and Property
Identifier are combined as one argument. Replace Index with an array
index. This is optional. It only applies to an array-type BACnet
property. The index is ignored whenever it is not applicable. The
returned value is the object property value that has been read.
Example 1
Use the ReadProperty to get the value of an Analog Value point.

Print ReadProperty (Net1\B4\AV1 Value)
Example 2
Use ReadProperty to get the description of an analog point and place it

into a string Point.
StringPoint = ReadProperty (Net1\B4\AV1 Description)
Example 3
Use ReadProperty to get the description of an analog point using index

3 and assign it to the numeric Num1.
Num1 = ReadProperty(BACnetDevices\B4\B3\AV1, 3)
Related
Keywords
Products
Supported
Modes
Available
WriteProperty, Relinquish
b3 series, b4920, bCX 4040 controllers and CyberStation.
Command lines and programs.
65
Relinquish
Format
Purpose
Relinquish (Object_Property, Priority)

To relinquish a command issued at an earlier time.
Returns SUCCESS or FAILURE.
Remarks
A relinquish operation is similar to a WriteProperty operation (refer to

WriteProperty for further information), with the exception that it
places a NULL value in the Priority_Array that corresponds to the
appropriate priority. When that occurs, the next lower priority, nonNULL position takes control of the property. If all the priority table
array elements are NULL, the commandable property (refer to
CyberStation online help for further information) assumes the one
defined in the Relinquish_Default property of the object.
Note: For Andover Continuum systems, Present_Value is the
commandable property for the following classes:
Analog Output
Multi-State Output
Binary Output
Binary Value
Analog Value
Multi-State Value
name, followed by a property name. The Object Identifier and Property
Identifier are combined as one argument. Property is expected to be the
Present_Value of the BACnet commandable property (Present_Value is
Value in Plain English). If it is missing, it is assumed to be
Present_Value.
Replace Priority with the priority number, ranging from 1 (highest) to
16 (lowest). Applies only to a BACnet commandable property. If not
present, the property value that matches with priority 10, if applicable,
is used for controllers. For CyberStations, the priority from the BACnet
Preferences is used.
Example
Use Relinquish to relinquish the last command issued with priority 5.

Relinquish (NET1\B4\AV, 5)
This statement places a NULL in the 5th entry.

Related
Keywords
Products
Supported
Modes
Available
WriteProperty, ReadProperty
b3 series, b4920, bCX 4040 controllers, and CyberStation
67
WriteProperty
Format
Purpose
WriteProperty (Object_Property, Value, Priority, Index)

To set a property of a BACnet object.
Returns SUCCESS or FAILURE.
Remarks

name, followed by a property name. The object Identifier and Property
Identifier are combined as one argument.
Replace Value with the actual value to set the property to. This is
option. If it is not present, then the next argument, Priority, must be
present to perform a Relinquish command (see Relinquish key word).
Replace Priority with the priority number, ranging from 1 (highest) to
16 (lowest). This is optional. Applies only to a BACnet commandable
property. (Refer to the CyberStation online help.) If not present, the
property value that matches with priority 10, if applicable, is used for
controllers. For CyberStations, the priority from the BACnet
Preferences is used.
Replace Index with an array index. This is optional. It only applies to
an array-type property. The index is ignored whenever it is not
applicable.
Example 1
Use WriteProperty to set the Value property of an object to 100.

Value property is assumed
WriteProperty (BacnetDevices\B4\B3\BV1, 100)
Or
Value property is explicitly mentioned
WriteProperty (BacnetDevices\B4\B3\BV1 Value, 100)
Example 2
Use WriteProperty to set the Present_Value property of an object to

100, using priority 5.
WriteProperty (BacnetDevices\B4\AV1 Value, 100, 5)
Example 3
Use WriteProperty to set a point log entry to 100, using index 2.
WriteProperty (NET1\CX1\AV1, 100, ,2)

Note that the priority argument is not passed.
Example 4
Use WriteProperty to relinquish a command using priority 5.

Value is not passed; this is equivalent to a Relinquish.
WriteProperty (BACnetDevices\B4\AV1, ,5)
Related
Keywords
Products
Supported
Modes
Available
ReadProperty, Relinquish
b3 series, b4920, bCX 4040 controllers, and CyberStation
69
Introducing BACnet - A Guide for Continuum Users

Document Number 30-3001-863
Revision H

Introducing BACnet

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Introducing BACnet

Caricato da

Copyright:

Formati disponibili

Introducing BACnet

A Guide for Continuum Users

2010, Schneider Electric

Introducing BACnet for Continuum Users

upon in producing the first BACnet standard. In fact, much of the

Name References in this Document

CyberStation online help

CyberStation HVAC Essentials Guide

Andover Plain English Language

bCX1 Series Controller Technical

b3 and b4920 Controller Technical

Continuum/BACnet CyberStation - What Has Changed

How is BACnet Integrated with Continuum?

Introducing BACnet for Continuum Users

programs, CFR-11 features, and graphics are unchanged. In fact, if

BACnet Objects versus Continuum Objects

Native BACnet and Continuum/BACnet Device Profiles

BACnet Operator Workstation (B-OWS)

BACnet Building Controller (B-BC)

BACnet Advanced Application Controller (B-AAC)

BACnet Application Specific Controller (B-ASC)

BACnet Smart Actuator (B-SA)

BACnet Smart Sensor (B-SS)

The following are examples of Andover Continuum hardware that

The CyberStation/BACnet Workstation feature set is closest to the

The bCX1 (4040) is a BACnet B-BC device.

The b4920 System Controller/BACnet Router (revision 4.2) is a BAAC device.

The entire line of the b3xxx equipment controllers operate on the

When Are the BACnet XDrivers Used?

Device Restriction Differences Between Infinity and BACnet

Andover Continuums implementation of standard BACnet devices

Introducing BACnet for Continuum Users

Chapter 2: Continuum/BACnet Hardware

Overview of Hardware Differences

Introducing BACnet for Continuum Users

Chapter 2: Continuum/BACnet Hardware

Figure 1 Unlike Infinet networks, MS/TP networks require terminators be placed

Continuum/BACnet Controller Overview

Chapter 2: Continuum/BACnet Hardware

Table 2 Continuum/BACnet Controller Overview

Output Override Control

Output Override control

Introducing BACnet for Continuum Users

Chapter 2: Continuum/BACnet Hardware

Table 2 Continuum/BACnet Controller Overview

24VAC power output

Output Override control

Output Override control

Registered Foreign Device

Optional SNMP Alarming

Registered Foreign Device

Optional SNMP Alarming

Custom Web Pages

Registered Foreign Device

Mixing Continuum and BACnet Networks

Chapter 2: Continuum/BACnet Hardware

BACnet and web.Client

Introducing BACnet for Continuum Users

Chapter 2: Continuum/BACnet Hardware

BACnet Communications over Multiple IP Subnets

BROADCAST messages are from one device to every device on the

Chapter 2: Continuum/BACnet Hardware

When traversing an Intranet or the Internet, subnets are connected

A special device can be used to allow BACnet broadcast messages to