Академический Документы
Профессиональный Документы
Культура Документы
Product Names are trademarks of Schneider Electric. All other trademarks are the prop-
erty of their respective owners.
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 Elec-
tric. 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 soft-
ware. 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, trade-
marks, 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 ............................................. 17
Continuum/BACnet Controller Overview ......................... 18
Mixing Continuum and BACnet Networks................. 20
BACnet and web.Client ............................................... 21
BACnet Communications over Multiple IP Subnets ................. 22
BACnet Communications with “Foreign Devices” ..................... 24
Chapter 3 ............................................................................... 27
Starting BACnet .......................................................................... 27
Continuum/BACnet Concepts ..................................................... 27
CyberStation Viewing Options .......................................... 28
Configuring BACnet Devices ............................................. 28
Third-Party Devices - What Can I Do with Them?........... 29
Manually Controlling Continuum BACnet Points............ 29
Command Priority .............................................................. 30
Continuum/BACnet Configuration Basics ................................. 34
Set Up the Network or Load Your Existing Database...... 34
Configure Your bCX1 (40x0) or b4920 Devices ................. 34
Chapter 4 .............................................................................. 45
BACnet Program Editor.............................................................. 45
Status Differences Between Infinity and BACnet Programs ... 47
BACnet Properties and Plain English ....................................... 47
Proprietary BACnet Schedule Properties for Programs .. 48
BACnet versus Plain English Property Names................ 50
Note regarding BACnet Numerics.............................. 54
Plain English Keywords for BACnet .......................................... 64
ReadProperty...................................................................... 65
Relinquish........................................................................... 66
WriteProperty..................................................................... 68
6 Schneider Electric
Chapter 1: Introduction
Chapter 1
Introduction
Related Documentation
Please consult the following Andover Continuum documentation as
needed:
10 Schneider Electric
Chapter 1: Introduction
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.
12 Schneider Electric
Chapter 1: Introduction
BACnet PICS
14 Schneider Electric
Chapter 1: Introduction
16 Schneider Electric
Chapter 2: Continuum/BACnet Hardware
Chapter 2
Continuum/BACnet
Hardware
18 Schneider Electric
Chapter 2: Continuum/BACnet Hardware
20 Schneider Electric
Chapter 2: Continuum/BACnet Hardware
22 Schneider Electric
Chapter 2: Continuum/BACnet Hardware
24 Schneider Electric
Chapter 2: Continuum/BACnet Hardware
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.
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-3001-
890) or the b3 and b4920 Controller Technical Reference Guide (30-
3001-862) for the b4920.
26 Schneider Electric
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:
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:
28 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
z EventEnrollments
z EventNotifications (NotificationClass in the BACnet standard)
z Schedules
z Calendars
z TrendLogs
z 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.
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.
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
30 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
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.
1 Null
2 Null
3 Null
4 28
5 Null
7 Null
8 Null
9 Null
10 6
11 Null
12 Null
13 22
14 Null
15 Null
16 Null
Priority
Value
Level
1 Null
2 Null
3 Null
4 Null
5 Null
6 Null
7 Null
32 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
8 Null
9 Null
10 6
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.
Step 7: Run your web browser and enter the following url: http://
169.254.1.1
34 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
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.
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.
The following table lists the Infinity class and its BACnet equivalent.
Table 4
Infinity Class BACnet Object Type
36 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
Table 4
InfinityOutput (ElecType: Tristate) Multi-State Output
Program Program
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.
38 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
Step 1: Right click Root in the Explorer’s navigation pane and the
object drop-down menu appears.
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.
40 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
Step 1: Right click the BACnet device and select Send to Database
option from the popup menu.
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.
Step 1: Right click on the Continuum icon in the lower right hand
corder of the window task bar.
42 Schneider Electric
Chapter 3: Continuum/BACnet Concepts and Configuration
Step 3: The first item on the list is Enable BACnet; change the value
of item 1 to False.
44 Schneider Electric
Chapter 4: Plain English for BACnet
Chapter 4
Plain English for BACnet
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.
46 Schneider Electric
Chapter 4: Plain English for BACnet
Inactive Idle
The tables on the following pages map each BACnet object’s properties
to the equivalent Plain English name. You would use the Plain English
name in a Plain English program.
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.
Note: Also refer to the Transition Time fields on the Current State tab
of the Schedule editor.
48 Schneider Electric
Chapter 4: Plain English for BACnet
z ScheduleName: PreviousTransitionTime
z ScheduleName: NextTransitionTime
z ScheduleName: FollowingTransitionTime
ScheduleName represents the name of the Schedule object, whose
transition times are being computed.
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.
Object_Name Name R
Present_Value Value W
Units Units W
50 Schneider Electric
Chapter 4: Plain English for BACnet
Object_Name Name R
Object_Type Type R
Present_Value Value W
Number_Of_States NumberOfStates R 3
Object_Name Name R
Object_Type Type R
Present_Value Value W
Object_Name Name R
Object_Type Type R
Present_Value Value W
Relinquish_Default RelinquishDefault W
Units Units W
Object_Name Name R
Object_Type Type R
52 Schneider Electric
Chapter 4: Plain English for BACnet
Present_Value Value W
Relinquish_Default RelinquishDefault W
Number_Of_States NumberOfStates R 3
Object_Name Name R
Object_Type Type R
Present_Value Value W
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.
Object_Name Name W
Object_Type Type R
Out_Of_Service OutOfService W
Present_Value Value W
Relinquish_Default RelinquishDefault W
Units Units W
Object_Name Name W
Object_Type Type R
Out_Of_Service OutOfService W
Present_Value Value W
Relinquish_Default RelinquishDefault W
54 Schneider Electric
Chapter 4: Plain English for BACnet
Example 1
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 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.
Object_Name Name W
56 Schneider Electric
Chapter 4: Plain English for BACnet
Out_Of_Service OutOfService W
Present_Value Value W
Table 16 Program
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Object_Name Name R
Object_Type Type R
Out_Of_Service OutOfService W
Program_Change StatusChange W
Program_State Status R
Table 17 Schedule
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Object_Name Name W
Object_Type Type R
Present_Value Value W
Priority_For_ Priority W
Writing
PreviousTransitionTime
NextTransitionTime
FollowingTransitionTime
These properties are all writable. Please see the section, Proprietary
BACnet Schedule Properties for Programs for further information.
Table 18 Calendar
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Object_Name Name W
Object_Type Type R
Date_List DateList W
Present_Value Value R
Table 19 Device
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
APDU_Segment_ APDUSegTimeout W
Timeout
APDU_Timeout APDUTimeout W
Application_ ApplSoftwareVers R
Software_version ion
Backup_Failure_ BackupFailureTi W
Timeout meout
Configuration_Files ConfigurationFile R
List
58 Schneider Electric
Chapter 4: Plain English for BACnet
Table 19 Device
Daylight_Savings_ DaylightSavingsS W
Status tatus
Firmware_Revision FirmwareRevision R
Last_Restore_Time LastRestoreTime R
Local_Date LocalDate R
Local_Time LocalTime R
Max_APDU_Lengt MaxAPDUAccept R
h_Accepted ed
Model_Name ModelName R
Object_Name Name W
Object_Type Type R
Protocol_Conforma ProtocolConfClass R
nce_Class
Protocol_Version ProtocolVersion R
Segmentation_Sup SegmentationSup R
ported port
System_Status System_Status R
UTC_Offset UTCOffset W
Vendor_Identifier VendorIdentifier R
Vendor_Name VendorName R
Event_State EventState R
Notify_Type NotifyType W
Object_Name Name W
Object_Type Type R
Object_Name Name W
Object_Type Type R
Table 22 File
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Archive Archive W
Description Description W
File_Access_Method AccessMethod R
60 Schneider Electric
Chapter 4: Plain English for BACnet
Table 22 File
File_Size Size W Writing is enabled in
Restore mode, but
the value is limted to
0 or the current file
size.
File_type FileType R
Modification_Date ModificationDate R
Object_Name Name R
Object_Type Type R
Read_Only ReadOnly R
Table 23 Loop
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Action Action W
Bias Bias W
Controlled_Variabl ControlledVariabl W
e_Units eUnits
Controlled_Variabl ControlledVariabl R
e_Value eValue
Derivative_ DerivativeConsta W
Constant nt
Derivative_Constan DerivativeConsta W
t_Units ntUnits
Description Description W
Event_State EventState R
Integral_Constant IntegralConstant W
Table 23 Loop
Integral_Constant_ IntegralConstant W
Units Units
Maximum_Output MaximumOutput W
Minimum_Output MinimumOutput W
Object_Name Name W
Out_Of_Service OutOfService W
Output_Units OutputUnits W
Present_Value Value W
Priority_For_ Priority W
Writing
Proportional_Const ProportionalConst W
ant ant
Proportional_Const ProportionalConst W
ant_Units antUnits
Reliability Reliability R
Setpoint Setpoint W
Update_Interval UpdateInterval W
Table 24 TrendLog
Plain English READ/WRITE
BACnet Property Restrictions
Name R/W
Buffer_Size BufferSize W
COV_Resubscriptio COVResubscriptio R
n_Interval nInterval
Description Description W
Event_State EventState R
62 Schneider Electric
Chapter 4: Plain English for BACnet
Table 24 TrendLog
Log_Enable LogEnable W
Log_Interval LogInterval W
Object_Name Name W
Object_Type Type R
Stop_When_Full StopWhenFull W
Total_Record_ TotalRecordCount R
Count
z ReadProperty
z Relinquish
z WriteProperty
64 Schneider Electric
Chapter 4: Plain English for BACnet
ReadProperty
Format ReadProperty (Object_Property, Index)
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.
Example 2 Use ReadProperty to get the description of an analog point and place it
into a string Point.
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)
Relinquish
Format Relinquish (Object_Property, Priority)
Example Use Relinquish to relinquish the last command issued with priority 5.
Relinquish (NET1\B4\AV, 5)
66 Schneider Electric
Chapter 4: Plain English for BACnet
WriteProperty
Format WriteProperty (Object_Property, Value, Priority, Index)
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 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).
Or
Example 3 Use WriteProperty to set a point log entry to 100, using index 2.
68 Schneider Electric
Chapter 4: Plain English for BACnet
70 Schneider Electric
Introducing BACnet - A Guide for Continuum Users
Document Number 30-3001-863
Revision H