BACnet

BACnet Interface Reference
July 2021
Issue 17
DISCLAIMER
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part
of this document or its contents shall be reproduced, published, or
disclosed to a third party without the express permission of Honeywell
International Sàrl.
While this information is presented in good faith and believed to be
accurate, Honeywell disclaims the implied warranties of merchantability
and fitness for a purpose and makes no express warranties except as may
be stated in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or
consequential damages. The information and specifications in this
document are subject to change without notice.
Copyright 2021 - Honeywell International Sàrl
2
Contents
CONTENTS
Contents 3
Getting started 7
Understanding BACnet 7
Standard object types 7
Alarms and events 10
Command, Group, and Schedule objects 11
Other documentation for BACnet 11
Choosing the BACnet interface to use 12
BACnet Direct Client interface 12
BACnet Server 12
Setting up BACstac software 13
Setting up BACnet IP 13
Setting up BACnet Ethernet 13
Protocol Implementation Conformance Statement (PICS) for BACnet
interfaces 14
BACnet-specific terms 14
BACnet Direct Client Interface Setup 17
BACnet Direct architecture 17
Defining a BACnet Point Server in Station 18
BACnet Point Server Configuration tab properties 19
Defining the BACnet point server using the configuration tool 20
Discovering Points 21
Discovering Points Using Quick Builder 22
Discovering Points Using Station 25
Manually Building Points Using Quick Builder 26
Downloading and Uploading Points Using Quick Builder 27
Deleting and Renaming Points 27
3
Contents
Point Naming Conventions 28

Building Schematics 31
History collection for BACnet points 32
EBI history collection 33
Backfill-only history collection 33
EBI history collection with backfill 35
Gapfill history collection 36
Configuring BACnet schedules 38
Overriding default state text for binary object schedules 38
Overriding default state text for multistate object schedules 38
Maintaining BACnet controllers 39
Point detail display (Advanced tab) for BACnet points 39
Backing up BACnet controller configuration 39
Restoring BACnet controller configuration 40
Copying BACnet configuration file for restore 41
Support for alternative BACnet specifications 41
KBOB BACnet 2017 requirements 41
BACnet Secure Connect 45
Using the BACnet Server 47

Discovering Points with the BACnet Server 47
Using the whohas Method 47
Using the bacnetbld Utility 48
Removing discovered points in the BACnet Server 49
Flexible Points 49
Configuring derived points 50
Rules that Determine the BACnet Object Type for Standard Points 50
When a Parameter Value is Entered 51
When a Parameter Value is Omitted 52
Determining the Parameters for Read/Write Requests 53
4
Contents
Rules that Determine the BACnet Object Type for Flexible Points 53
Example 54
EBI Server Point Mapping to BACnet Objects 55
Device Object 55
Analog Input Object 59
Analog Output and Analog Value Objects 64
Binary Output and Binary Value (Pseudo Binary Points) 68
Multi-state Input 70
Multi-state Output 72
Engineering units supported by BACnet Server 74
EXCEL 5000 Direct to BACnet Property Mapping 80
AI - Analog Input Mapping (EXCEL 5000 Direct to BACnet) 81
AO - Analog Output Mapping (EXCEL 5000 Direct to BACnet) 83
AV - Analog Value Mapping (EXCEL 5000 Direct to BACnet) 84
BI - Binary Input Mapping (EXCEL 5000 Direct to BACnet) 86
BO - Binary Output Mapping (EXCEL Classic to BACnet) 87
BV - Binary Value Mapping (EXCEL 5000 Direct to BACnet) 88
MI4 MI8 MI16 - Multi-State Input Mapping (EXCEL 5000 Direct to BACnet) 90
MO4 MO8 MO16 - Multi-State Output Mapping (EXCEL 5000 Direct to
BACnet) 91
EXCEL Classic to BACnet Property Mapping 92
AI AP AZ- Analog Input Mapping (Excel Classic to BACnet) 93
AO - Analog Output Mapping (EXCEL Classic to BACnet) 95
AV - Analog Value Mapping (EXCEL Classic to BACnet) 96
BI - Binary Input Mapping (EXCEL Classic to BACnet) 98
BO - Binary Output Mapping (EXCEL Classic to BACnet) 99
BV - Binary Value Mapping (EXCEL Classic to BACnet) 100
MI - Multi-State Input Mapping (EXCEL Classic to BACnet) 102
MO - Multi-State Output Mapping (EXCEL Classic to BACnet) 103
R7044 to BACnet Property Mapping 104
5
Contents
AI AP- Analog Input Mapping (R7044 to BACnet) 106

AO - Analog Output Mapping (R7044 to BACnet) 107
AV - Analog Value Mapping (R7044 to BACnet) 108
BI - Binary Input Mapping (R7044 to BACnet) 110
BO - Binary Output Mapping (R7044 to BACnet) 111
BV - Binary Value Mapping (R7044 to BACnet) 113
MI DP- Multi-State Input Mapping (R7044 to BACnet) 114
MO - Multi-State Output Mapping (R7044 to BACnet) 115
XML Parameter Tag and Default Values 116
BACnet Server settings 118
Testing communications with a BACnet device 121
Notices 122
6
CHAPTER
1 GETTING STARTED
This reference describes how to set up, configure and test the various
BACnet interfaces.
Understanding BACnet
BACnet is an ANSI-standard network protocol that is applicable to many
distributed control and monitoring applications. Unlike network protocols
such as Ethernet and TCP/IP, BACnet focuses on defining a method for
abstracting the functionality commonly found in control and monitoring
devices. In BACnet, network-accessible functionality in a device is
represented as a collection of objects that other devices may access using
BACnet services.
BACnet has a broad set of standard object types and services, but
proprietary object types and services may also be defined. BACnet
messages can be transmitted on networks employing a wide range of
technologies, including Ethernet and LonTalk.
Standard object types

A BACnet device can contain a range of different BACnet objects from an
Analog Input to a Loop object. A BACnet device can be a master
timekeeper, which sends time sync messages to other BACnet devices. A
BACnet device may also keep bindings to other BACnet devices for
communications purposes.
7
Getting started
BACnet object types and supported interfaces

The table below shows BACnet object types and the interfaces that support
each object type.
BACnet object Supports intrinsic Supported in BACnet Supported in

type alarming? Direct Client Interface? BACnet Server?
Alert enrollment Y
Analog input Y Y Y
Analog output Y Y Y
Analog value Y Y Y
Binary input Y Y Y
Binary output Y Y Y
Binary value Y Y Y
Calendar Y
Channel Y
Command Y
Device Y Y
Event enrollment Y
File Y
Group Y
Lighting output Y
Loop Y Y
Multi state input Y Y Y
Multi state Y Y Y
output
Notification class Y Y
Notification Y
forwarder
8
Getting started

Program Y Y
Schedule Y Y
Averaging Y
Multi state value Y Y
Trend log Y Y
Life safety point Y Y
Life safety zone Y Y
Accumulator Y Y
Pulse converter Y Y
Event log Y Y
Global group Y Y
Trend log Y Y
multiple
Load control Y Y
Structured view Y
Bitstring value Y Y
Characterstring Y Y
value
Date pattern Y
value
Date value Y
Datetime pattern Y
value
Datetime value Y
9
Getting started

Integer value Y Y
Large analog Y Y
value
Octetstring value Y
Positive integer Y Y
value
Time pattern Y
value
Time value Y
Alarms and events

BACnet provides two different types of notification generation, Intrinsic
alarming and Algorithmic alarming.
Intrinsic alarming
Several types of BACnet objects can have intrinsic alarm conditions (for
example, Present Value High and Low). These objects can be
associated with Notification Class, which can help with prioritizing
and routing the alarms to a list of recipients.
Algorithmic alarming
BACnet Event Enrollment can monitor algorithmic alarm conditions on the
referenced BACnet device object properties. These Event Enrollment
objects can be associated with Notification Class, which can help
with prioritizing and routing the alarms to a list of recipients. Algorithmic
alarm conditions are applicable to all BACnet object property types. These
referenced object properties can be either internal or external to the device
containing the Event Enrollment object.
For details about notification generation, refer to the BACnet Standard.
10
Getting started
Command, Group, and Schedule objects

A Command object contains a list of references to other
device/object/properties. By controlling the command object a set of values
can be sent to each of the referenced properties. The command object also
allows the operator to monitor the status of the set of controls performed
and if any errors occurred.
A Group object contains a list of references to other object properties within
the device. The Group object allows for the value of each of these
properties to be viewed in a quick manner.
A Schedule object contains a list of time/value pairs for each day of the
week. It also contains a list of exception dates and their corresponding
time/value pairs. The exception dates may be a reference to a calendar of
dates, a specific date, a range of dates, or a recurring day. At the given time
the value shall be sent to a list of object/property references contained
within the device.
Other documentation for BACnet

The following documents are relevant to the BACnet system and should be
read before using or installing the BACnet Client Interface:
n BACnet - A Data Communication Protocol for Building Automation and

Control Networks, ANSI/ASHRAE Standard 135-2012
11
Getting started
n Current versions of BACnet Protocol Implementation Conformance

Statements (PICS)
Choosing the BACnet interface to use

EBI supports two BACnet interfaces:
n BACnet Direct Client Interface, a point server interface

n BACnet Server
TIP: The BACnet Client Interface is no longer supported in EBI

R600.
BACnet Direct Client interface
ATTENTION: If BACnet Server is licensed, BACnet Direct Client

can only be used on a remote computer.
Select the BACnet Direct Client Interface if you want the EBI server to act
as the master system integrator for other Honeywell or third-party BACnet
devices, controllers or specialty equipment that have high levels of
compliance to the BACnet standard.
This interface uses point server technology. It supports all the BACnet
object types except Access Control objects. All standard and optional
properties are natively supported; mapping into fixed point types is not
required. It also uses a dynamic scanning strategy based on what has
recently been shown on operator stations, reducing bandwidth
requirements.
Because the BACnet objects are modeled natively, this interface requires
the BACnet device to perform its own intrinsic alarming. The interface can
support devices that do not have intrinsic alarming, but you will need to set
up server scripts or derived points to generate any alarms in place of the
BACnet device that is generating the alarms, and this strategy removes the
advantage of a dynamic scanning strategy.
BACnet Server
Select this interface if you want the EBI server to act as a peer amongst
other BACnet subsystems in a facility (for example, where Security, Life
Safety and HVAC are independently tendered). In this case the EBI server
acts as a BACnet gateway. The EBI server communicates with various
controllers using proprietary protocols and serves this information up to
12
Getting started
other BACnet clients.
Setting up BACstac software

Whichever interface you decide to use you need to ensure that the
Cimetrics BACstac Gateway Protocol has been set up on the EBI server
and the BACnet point server.
Setting up BACnet IP
To use BACnet on an IP network you need to add a BACnet/IP port. This
port can be set up in one of three ways.
n A regular BACnet/IP port. This is used to communicate to a single

BACnet/IP subnet.
n A BACnet/IP port and a BBMD device. This is used to set up the server
to act as a BACnet Broadcast Management Device (BBMD). A BBMD is
used to propagate broadcast messages to another IP subnet, allowing a
BACnet network to span multiple IP subnets.
n An FD port and FD device. This is used to request that the specified
remote BBMD include this port in the broadcasts for the BACnet/IP
network.
To add a BACnet/IP port
1. Right-click the BACnet Direct icon in the Windows system tray and
choose Configure BACstac.
2. Click Add and choose BACnet/IP.
3. Set the port number and network number leaving the IP Address and
UDP Port unless they need changing.
4. Set the properties on the BBMD property tab if you want the server to
act as a BBMD.
5. Set the properties on the Foreign Device property tab if you want to
request a remote BBDM to include this port on broadcasts.
6. Click OK.
Setting up BACnet Ethernet

The following default ports are set up when BACstac software is installed:
attached physical Ethernet port #1 to the network #1 with default NIC;
attached virtual port #2 to the network #2.
13
Getting started
For most installations, the only fields in this table that need to be modified
are the network numbers. Each network segment in a BACnet internetwork
must be assigned a single unique network number. Each of the routers
directly attached to a network segment contains this network number in
their routing tables.
Prerequisites
n You have installed the NDIS driver for the computer's Ethernet adapter.
n You have installed WinPCap.
To set the network number of a BACnet/Ethernet port:
1. Right-click the BACnet Direct icon in the Windows system tray and
choose Configure BACstac.
2. Click the Ethernet port and then click Edit.
3. Type the new the network number.
4. If there is more than one physical Ethernet network adapter on the
server, select the Network Interface Card you want to use.
5. Click OK.
Protocol Implementation Conformance

Statement (PICS) for BACnet interfaces
The Protocol Implementation Conformance Statement (PICS) summarizes
the capabilities of a BACnet system in a standard way. The current version
of this document is the Enterprise Buildings Integrator R610 Protocol
Implementation Conformance Statement (PICS).
For a copy of the latest version of the PICS for EBI BACnet solutions,
contact your local technical assistance center.
BACnet-specific terms
Term Description
ASHRAE American Society of Heating, Refrigeration, and Air-Conditioning

Engineers.
BACnet Building Automation and Control Network. A protocol standard

developed by ASHRAE to allow open communications.
14
Getting started
Term Description
BACnet A system on the BACnet network that can support BACnet Services
Device and BACnet Objects.
BACnet Network of computers that obey the BACnet protocol standard

Network
BACnet An abstract data structure used to represent information on the

Objects network. All BACnet objects are referenced by its object identifier
which is unique within the BACnet device. When combined with the
system-wide unique object identifier of the BACnet Device, a BACnet
object can be accessed from anywhere in the control system
network.
BACnet Application Layer services used to manage communication over the

Services BACnet network.
BACstac Software by Cimetrics that the server uses to communicate over the
standard Ethernet LAN to comply to the BACnet standard.
COV Change of Value.
Device On a BACnet network, every device (including the server) must have
Instance a unique 22-bit number to identify itself.
Hardware One scan per controller every diagnostic period for automatic
Diagnostic recovery from communications failure with the controller.
Scan
Object All BACnet objects are identified by a 10-bit object type and a 22-bit
Identifier object instance. An object identifier is unique within the BACnet
device.
Object Type A 10-bit number identifying the type of object. For example, Analog
Input = 0, Analog Output = 1, Multi-state Input = 13, Device = 8 and
so on. This forms part of the object identifier.
Object A 22-bit number identifying the instance of an object within a

Instance BACnet device. This forms part of the object identifier.
Periodic A defined regular interval in which the server database acquires

Data information from the data tables in the PLC and processes the
Acquisition values as point parameters. For the source address, the scan period
15
Getting started
Term Description
Scan assigned should reflect both the rate at which the value held in
memory changes and its importance to the process (critical or non-
critical). There is one periodic data acquisition scan per scan packet.
Property All BACnet objects have attributes that describe the object. These
Identifier attributes are known as properties and are identified by a number. As
part of the configuration of BACnet points, you must know the
identifier number that refers to the server parameter such as a PV,
OP or SP. See the BACnetStandard for details.
PICS Protocol Implementation Conformance Statement. A document that

is part of the BACnet Standard, which gives an overview of the
services and objects that are supported in the device.
16
CHAPTER
2 BACNET DIRECT CLIENT
INTERFACE SETUP
This section describes how to set up the BACnet Direct Client Interface and
perform related operational tasks. It assumes that you have already
installed the BACstac software and connected the server to the BACnet
network.
BACnet Direct architecture

Following are some key differences regarding the behavior of local and
remote BACnet Direct point servers within a redundant setup.
Remote point server within a redundant system

When installing a remote BACnet Direct point server within a redundant
system consider the following:
n Each remote BACnet Direct Point Server communicates to the current

primary EBI server. If there is a EBI server failover, the remote point
server will automatically switch communicating from the old primary EBI
server to the new EBI server.
Local point server on a redundant system

When installing a local BACnet Direct point server on a redundant system
consider the following:
n Each local BACnet Direct point server will monitor whether it is running
on the primary or backup server. If a failover occurs, the BACnet point
server running on the new primary server is aware that it is running as
primary.
n Each EBI server will only communicate to its local BACnet Direct point
server.
n The failure of a local point server will not initiate a EBI server failover.
17
BACnet Direct Client Interface Setup
n Each local point server, regardless of whether it is running on the

primary or backup server is communicating on the BACnet network in
some capacity. For this reason each point server must be configured
with a unique PointServerDeviceID registry setting.
Defining a BACnet Point Server in Station

You use Station to define the BACnet Point Server, so that the EBI server
can communicate with BACnet devices.
Prerequisites
n You must be logged on to Station with MNGR security level (if you are
using Station-based security).
n The BACnet Point Server service is running.
To define the point server:

1. In Station, choose Configure > System Hardware > Controller Interfaces >
Point Servers.
2. Click an empty record to call up the Point Server detail display.
3. From the Point Server Type list, select BACnet as the point server type
and click Configure.
4. On the Configuration tab, configure the point server properties as
appropriate.
ATTENTION: It is not recommended that you select Allow online

discovery of new points on the Configuration tab of the point server
detail display. If you do, those discovered points will prevent
other points from being downloaded from Quick Builder.
5. On the Location Mapping tab, click to call up the Location Browser

display.
6. Select the physical location of the point server within the tree.
7. Click Apply and then click Close.
8. On the Status tab, verify that the point server is communicating with the
EBI server.
18
TIP: It may take up to 30 seconds before it is apparent that

communication has been established.
BACnet Point Server Configuration tab properties

Following are the properties associated with the Configuration tab of a
BACnet Point Server.
Property Description
Point Server
Network Name The TCP/IP name of the computer on which the BACnet point
server resides.
When defining a local BACnet point server on a redundant

system, the network name must be localhost.
Alias The user defined name of the point server. The alias defaults to
the point server type (for example, BACnet). The alias must be
unique and is case sensitive.
Architecture
Point server Select the Point Server connected via dual network check box if the
connected via point server communicates through a dual network setup.
dual network
Options
Allow remote Select the Allow remote servers to query new points check box if you
servers to query want to enable the ability of DSA servers to access your BACnet
new points point server for point information.
Point Discovery
Allow online Select the Allow online discovery of new points check box if you
discovery of new want to enable the ability to search and discover points from
points other DSA servers.
TIP: The use of this option is not recommended, as online

discovery is not the recommended method for discovering
points.
19
Alarm Processing
Raise all alarms Select the Raise all alarms received check box if you want to see all
received the alarms generated by controllers that are managed by this
BACnet point server.
Ignore alarms Select the Ignore alarms from points not configured on this server
from points not unless they are fire alarms check box if you only want to see alarms
configured on for points engineered on the BACnet point server. Alarms from
this server Life Safety Point and Life Safety Zone objects are still processed.
unless they are
fire alarms ATTENTION: The Allow online discovery of new points option
must be disabled in order for this option to function
properly.
Ignore all alarms Select the Ignore all alarms from points not configured on this server
from points not check box if you only want to see alarms for points engineered
configured on on the BACnet point server. Alarms from Life Safety Point and
this server Life Safety Zone objects are processed only if the object is
engineered on the BACnet point server.
ATTENTION:
l The Allow online discovery of new points
option must be disabled in order for this
option to function properly.
l This option is not available for selection if
the system has the Underwriters
Laboratories "Full UL" or "UL Ancillary"
license option enabled.
Defining the BACnet point server using the

configuration tool
In addition to defining the BACnet point server in Station, you need to define
the BACnet point server using the BACnet configuration tool to ensure
communications from the BACnet point server to the EBI server.
20
To define settings for the BACnet point server

1. On the point server computer double-click the BACnet Direct
configuration tool icon in the notification area.
2. In the Server name box, type the computer name of the EBI point server
as follows:
l If the BACnet point server is installed on redundant servers, type
localhost .
l If the BACnet point server is installed on a remote computer and you
have redundant servers, the server name should be the base
computer name of the redundant server pair. For example, if the
computer names for the redundant servers is HoneywellServerA
and HoneywellServerB, the base computer name is
HoneywellServer.
l If the BACnet point server is installed on a remote computer, this
should be set to the computer name where the EBI server is
installed.
3. In the Alias box type the same point server alias that was created when
you defined the BACnet point server in Station.
4. In the Device instance box, type device ID of the BACnet point server on
the BACnet network.
This must be a unique number that is not used by any other BACnet
device or BACnet point server connected to the same BACnet network.
Discovering Points
Use one of the following techniques to discover points, which include
BACnet devices and BACnet objects.
n Use one of Quick Builder's wizards. This is the recommended technique

when configuring a new system, or making significant changes to an
existing system.
n Discover points in Station (not recommended).
n Manually define points in Quick Builder. Only use this technique if you do
not have a connection to the BACnet network from your Quick Builder
computer.
21
Discovering Points Using Quick Builder

Quick Builder includes wizards you can use to discover points and add
them to a project. After discovering the points (and, if necessary, editing
their properties), you download them to the EBI server.
The ComfortPoint Import wizard can discover points for ComfortPoint AP
controllers by:
n Extracting information from a ComfortPoint Studio project

The BACnet Discovery wizard can discover points for BACnet controllers
by:
n Searching the BACnet network using either the WhoIs or WhoHas

services.
The QB EDE Import wizard can download controller and point information
from BACnet controllers by:
n Extracting information from an EDE template (an Excel spreadsheet or

.csv file).
Prerequisites
n If you want the wizard to search the BACnet network, the computer on
which you are using Quick Builder must have the BACnet protocol stack
installed and must have access to the BACnet network
n The Quick Builder project to which the wizard adds points must have
the BACnet device type and BACnet point components enabled.
n If the Allow online discovery of new points option has been selected on
the configuration tab of the Point Server Detail display, you must stop
the BACnet Point Server service and delete any discovered points from
the server database before downloading from Quick Builder. See
"Deleting and Renaming Points" on page 27.
n Learn how the Quick Builder wizards name discovered points, in the
topic 'Point Naming Conventions'.
To import points using the CARE/XL Toolkit Import

Wizard and download them to the EBI server:
1. Create a new (or open and existing) Quick Builder project, making sure
you enable the following components: BACnet Direct device and
BACnet Direct point.
22
2. Choose Tools > QB CARE/XL Toolkit Import Wizard.
TIP: If the wizard is not available, make it available by selecting

Tools > Add-In Manager and then select the wizard.
The wizard's operation is self-explanatory, and takes you step-by-step

through the import options.
The wizard adds the BACnet devices it has imported to the project as
controllers, and BACnet objects as points.
3. If appropriate, change the names of the controllers and points to
something more meaningful than their default BACnet object names.
You can also configure their EBI-specific properties, such as Location.
4. When you have finished making changes, download the points to the
EBI server.
To import points using the ComfortPoint Import Wizard

and download them to the EBI server:
2. Choose Tools > QB ComfortPoint Import Wizard.


The wizard adds the BACnet devices it has imported to the project as
EBI server.
23
To discover points using the BACnet Discovery Wizard

and download them to the EBI server:
2. Choose Tools > QB BACnet Discovery Wizard.

3. Do one of the following:

l Click WhoIs if you want to discover all BACnet devices on the
network, or all BACnet devices with a specific device range.
l Click WhoHas if you want to discover BACnet devices with objects
that have a specific object identifier or object name.
4. Follow the steps in the discovery wizard.
The wizard adds the BACnet devices it discovers to the project as
EBI server.
TIP: The BACnet Discovery wizard only returns devices among

the first 2000 to broadcast a response during the timeout delay,
and each discovery can return a maximum of 5000 objects. To
build a large system, specify a WhoIs Device Range during
object discovery.
To discover points using the QB EDE Import Wizard and

download them to the EBI server
24
2. Choose Tools > QB EDE Import Wizard.

3. Follow the steps in the import wizard.

The wizard adds the BACnet objects it imports to the project as points.
4. If appropriate, change the names of the points to something more
meaningful than their default BACnet object names. You can also
configure their EBI-specific properties, such as Location.
Discovering Points Using Station
ATTENTION: Due to certain constraints within the process, using

Station is not the recommended technique when discovering points.
You can discover BACnet devices and objects (points) using Station. This
is an online technique, which means that the point's details are immediately
loaded into the system's database.
When you use this technique, the system instructs the BACnet point server
to request a 'Who-Has service' on the BACnet network. If any BACnet
devices respond, then the point is discovered and its Point Detail display is
called up.
Before discovering points, consider the following:
n You can only use Station to discover points if you know the point's
name, and the name is 40 characters or less. If you do not know the
name, the name exceeds 40 characters, or you need to discover many
points, see the topic 'Discovering Points Using Quick Builder'.
n You can also force the system to discover points the first time you call
up a display that references them (for example, custom displays, trends
and the History Assignment display).
n If you use this method to discover points, you cannot download these
same points in Quick Builder. Using both methods will cause duplicate
points to be built within the server, which will cause confusion and
inconsistency when trying to access these points.
n You must first define and download a BACnet device to the EBI server
with Quick Builder before BACnet points can be discovered in Station.
25
To discover points using Station:

1. Log on to Station.
2. Call up the point server's configuration display and select Allow online
discovery of new points.
3. Type the point's name in the Command Zone and press F12.
Manually Building Points Using Quick Builder

If your Quick Builder computer does not have a network connection to the
BACnet network, you can manually create BACnet points.
TIP: You should only use this technique if you need to define a few
points. Ideally, you should discover them using the BACnet
Discovery wizard, or import them using the Care/XL Toolkit Import
Wizard.
To manually create a controller using Quick Builder
1. Click to open the Add Items dialog box.

2. Select Controller from Add Items.
3. Select BACnet Interface from Type.
4. Complete the Technical Address of the controller by entering the
Instance Number.
5. Specify the same location code as the BACnet point server.
To manually create a point using Quick Builder
1. Click to open the Add Items dialog box.

2. Select Point from Add Items.
3. Select BACnet Point from Type.
4. Complete the Technical Address of the point by selecting the Controller,
Item Type and Instance Number.
5. Assign the same location code as the BACnet point server.
6. When you have finished defining points, download them to the EBI
server.
26
Downloading and Uploading Points Using Quick Builder

Points that have been discovered or manually built in Quick Builder must be
downloaded to the EBI server.
If you want to manage points that have been created online (discovered in
Station), you must upload them from the EBI server database into the Quick
Builder project.
To download points:
1. Select Tools > Download.
2. Select the scope of points to download.
3. If you are only downloading BACnet points, clear the Rebuild Scan
Tables check box, to reduce the download time.
4. Click OK.
To upload points:
1. Select Tools > Upload.
2. Select the scope of points to upload.
3. Click OK.
Deleting and Renaming Points

You use the normal Quick Builder techniques to delete or rename points—
for details, see Quick Builder's help.
If you want to delete or rename points that have been discovered online
(discovered using Station), you must first upload them into Quick Builder.
To rename a point that has been discovered online:

1. Upload the point into Quick Builder.
2. Delete it and then download the deletion.
3. Either re-discover or manually re-create the point, giving it a new name.
4. Download the renamed point.
27
Point Naming Conventions

BACnet objects are uniquely identified within a particular BACnet device by
a 32-bit numeric 'object identifier.' Although these names expedite access
over the network, their use by human operators is impractical. Therefore,
BACnet also allows each object to be referenced by an 'object name'.
The standard, however, only specifies a minimum length of one printable
character for the object name and does not even require that it be writable
(modifiable), when a device is commissioned. This was done to
accommodate very simple devices, for example in unitary or application-
specific controllers.
To cater for these constraints on BACnet object names, the EBI server
provides two approaches to naming the points which reference BACnet
objects:
n Explicit Point Name

n Arbitrary Point Name
Explicit Point Name

An explicit point name is used where the point name clearly implies the
BACnet object it is referencing. This can be used where the BACnet object
name or BACnet object identifier is meaningful enough to describe the
object.
The format of the explicit point name is as follows:
n ObjectRef@DeviceRef to reference a BACnet object

n DeviceRef to reference a BACnet device
Where:
n DeviceRef = DeviceName or DEVDeviceIdentifier

n DeviceIdentifier = 22-bit numeric instance number of the BACnet
device
n ObjectRef = ObjectName or ObjectTypeIDObjectIdentifier
n ObjectName = Name of the BACnet object
n ObjectIdentifier = 22-bit numeric instance number of the BACnet
object
n ObjectTypeID = See the following table
28
Table 2-1: BACnet Object Types and ObjectTypeIDs
BACnet Object Type ObjectTypeID BACnet Object Type ObjectTypeID
ACCUMULATOR ACC INTEGER_VALUE IV
ALERT_ENROLLMENT AE LARGE_ANALOG_ LAV

VALUE
ANALOG_INPUT AI LIFE_SAFETY_POINT LSP
ANALOG_OUTPUT AO LIFE_SAFETY_ZONE LSZ
ANALOG_VALUE AV LIGHTING_OUTPUT LGTO
AVERAGING AVG LOAD_CONTROL LC
BINARY_INPUT BI LOOP LP
BINARY_OUTPUT BO MULTISTATE_INPUT MSI
BINARY_VALUE BV MULTISTATE_OUTPUT MSO
BIT_STRING_VALUE BSV MULTISTATE_VALUE MSV
CALENDAR CAL NOTIFICATION_CLASS NC
CHANNEL CHN NOTIFICATION_ NFWD

FORWARDER
CHARACTER_STRING_ CSV OCTETSTRING_VALUE OSV

VALUE
COMMAND CMD POSITIVE_INTEGER_ PIV

VALUE
DATE_PATTERN_VALUE DPV PROGRAM PRG
DATE_TIME_PATTERN_ DTPV PULSE CONVERTER PLC

VALUE
DATE_TIME_VALUE DTV SCHEDULE SCH
DATE_VALUE DV STRUCTURED_VIEW SV
DEVICE DEV TIME_PATTERN_ TPV

VALUE
29
BACnet Object Type ObjectTypeID BACnet Object Type ObjectTypeID
EVENT_ENROLLMENT EE TIME_VALUE TV
EVENT_LOG ELOG TRENDLOG TL
FILE FL TREND_LOG_ TLOGM

MULTIPLE
GLOBAL_GROUP GGRP
GROUP GRP
Example
A BACnet device (with identifier 102100 and name
'AirCon1') may have a BACnet Analog Input object
(with identifier 23 and name 'RoomTemp').
Each of the following point names would explicitly

reference this object:
l RoomTemp@AirCon1
l RoomTemp@DEV102100
l AI23@AirCon1
l AI23@DEV102100
ATTENTION: Once a BACnet object has been referenced

via a particular point naming scheme it must always
be referenced by the same scheme. To use a different
scheme you need to delete the old point name first
and then rediscover the point using the new scheme.
Arbitrary Point Name

Sometimes the BACnet object name or object identifier is not very
meaningful to an operator. This may arise where the site has a standard
naming convention for all points to follow. An example of this is the
FACILITY/SYSTEM/POINT (FSP) naming scheme. A point named
'BLDG226/AHU1/MA_TEMP' would mean the facility is Building 226, the
system is Air Handler Unit 1, and the point is the mixed air temperature.
30
To cater for arbitrary point naming schemes, it is possible to 'rename' a

BACnet object to have any valid point name using Quick Builder. This
makes it easy to manage a consistent naming scheme within Quick Builder.
ATTENTION: A point can only be renamed after it has been

discovered in Quick Builder and before it has been downloaded to
the EBI server. To rename a point you need to delete the old point
name first, re-discover the object using Quick Builder and then
rename it.
The way Quick Builder keeps track of the BACnet object being referenced
by the arbitrarily named point is through a technical address. The format of
the technical address in Quick Builder is as follows:
ControllerName ItemType InstanceNumber
Where:
n ControllerName = Point name of the BACnet device point

n ItemType = Type of the BACnet object
n InstanceNumber = 22-bit numeric instance number of the BACnet
object
For example, a BACnet device (with identifier 102100 and name 'AirCon1')
may have a BACnet Analog Input object (with identifier 23 and name
'RoomTemp').
The device could be represented by the following point:
n Rooftop/AirCon1
The object could be represented by the following point:
n Floor1/ConfRoom1A/Temperature
With a technical address of:
n Rooftop/AirCon1 AnalogInput 23
Building Schematics
When you use the BACnet Direct Client, all of the BACnet objects are
represented natively in the EBI server. This means that any of the standard
or optional properties of the BACnet object can be referenced as a
parameter of the point in the EBI server.
For example a BACnet Analog Input Point will have the following
parameters:
31
BACnet Analog Input Point Properties
ObjectIdentifier OutOfService NotificationClass
ObjectName UpdateInterval HighLimit
ObjectType Units LowLimit
PresentValue MinPresValue Deadband
Description MaxPresValue LimitEnable
DeviceType Resolution EventEnable
StatusFlags CovIncrement AckedTransitions
EventState TimeDelay EventTimeStamp
Reliability NotifyType
In most cases when you are building schematics you will be referring to the
PresentValue property of a BACnet Point. For a list of parameter names for
each of the BACnet object types, see the BACnet Standard.
To determine how to reference these parameters on a schematic, you can
refer to the system displays provided with the EBI server. The BACnet point
detail displays refer to nearly all of the BACnet properties and have a
filename like sysDtlBACnetXXXXXX.htm where XXXXX is the type of
BACnet ObjectTypeID, for example, sysDtlBACnetAI.htm. For a list of
ObjectTypeIDs, see the topic "Point Naming Conventions" on page 28.
History collection for BACnet points

In EBI point parameters can be configured for history collection so that their
values are stored by the system at pre-determined intervals. These values
can be called up on a Station Trend display later.
As an alternative to using the values from the BACnet object in question,
different history collection schemes can use data from BACnet Trend Log
(TL) or Trend Log Multiple (TLOGM) objects that reference the point
parameter of interest. Depending on the situation, these alternative
schemes of history collection can offer advantages over the traditional EBI
history collection mechanism.
The BACnet Direct Client supports the following different types of history
collection:
32
n EBI history collection

n Backfill-only history collection
n EBI history collection with backfill
n Gapfill history collection
TIP: A history record for the sample needs to exist in EBI before data
from a TL or TLOGM object can be inserted.
To enable samples to be filled during the times when the EBI server is not
running, the "History initialize percent" value needs to be set to 100 using
the "fileio" tool (the HIPCNT value is at file 8, record 1, offset 26).
In the examples provided in the topics that follow, history is to be stored in
EBI for the point parameter "APoint.AParameter". Where appropriate, a
TL/TLOGM object "ALogCollector" is assumed to be configured with
"APoint.AParameter" in its Log_DeviceObjectProperty property.
EBI history collection

With EBI history collection, the BACnet Direct Client will obtain data from
"APoint" via BACnet change-of-value (COV) notifications or polling using
ReadProperty (RP) or ReadPropertyMultiple (RPM) services. The replies
from the controller do not include time stamps, therefore the samples are
time-stamped by EBI.
Advantage
History samples are stored and available soon after its time of occurrence.
Disadvantages
n If history is not collected by EBI (for example, if the EBI Server is not
running, or the BACnet Direct Client loses connection to the controller),
the history quality will be BAD for the sample.
n The value stored could have occurred at any time in the preceding time
period, depending on when it is processed by EBI.
Backfill-only history collection

If a point parameter to be stored to EBI history is referenced by a BACnet
TL or TLOGM object, data from the TL or TLOGM object can be used
instead for storage to EBI history.
33
In this configuration, history data is not collected via the COV or RP/RPM
mechanisms from "APoint". Instead, the BACnet Direct Client would issue
ReadRange requests to "ALogCollector" to obtain data from the controller
under any of these conditions:
n The BACnet Direct Client starts.

n The BACnet Direct Client (re)connects to the controller.
n A Buffer_Ready event notification is received for "ALogCollector".
When a ReadRange request is to be generated, the BACnet Direct Client
does the following:
1. Retrieves the time stamp of the last log record for "ALogCollector" that
was previously collected, and issues a ReadRange by time request with
this as the reference time.
2. Processes the log records returned and sends the history data for
"APoint.AParameter" to EBI in blocks. If there are multiple records for
the history time interval, the most recent record before the time interval
boundary is stored to EBI history.
3. Using the last record time as the reference time, the BACnet Direct
Client issues another ReadRange by time request to "ALogCollector",
and processes the data returned. This continues until all the log records
from "ALogCollector" have been retrieved.
4. Waits for the next collection (usually on receiving a Buffer_Ready event
notification from "ALogCollector").
Advantage
Backfill-only history collection has the following advantages:
n There will be minimum gaps in EBI history, as any data for gaps that
would otherwise be present in EBI history collection would also be
"backfilled" into EBI history.
n Since the log records are time-stamped at the controller and the most
recent sample before the time interval is used, potentially the stored
history value better reflects the true value at the time interval (compared
with EBI history collection).
Disadvantage
With backfill-only history collection, history data may not be available in EBI
until much later after its occurrence (after the next Buffer_Ready notification
is received and the data is retrieved and processed from the controller).
34
Configuration
To configure backfill-only history collection:
n Leave the BACnet Point Server "TrendProcessingMode" registry value

at the default value of 0.
n Configure "APoint.AParameter" in EBI history assignment, with the
Backfill only option selected.
n Download the "ALogCollector" point to EBI.

n Configure "ALogCollector" correctly for data to be collected and for
Buffer_Ready notifications to be sent in a timely manner to EBI
(appropriate Notification_Threshold in relation to buffer size, Notify_
Type should be "Alarm", and the "To-Normal" bit in Event_Enable
needs to be set).
EBI history collection with backfill

To get around the delay with backfill-only history collection, EBI history
collection can be run together with backfill by not selecting the Backfill only
option in the history assignment for "APoint.AParameter".
With this configuration, the BACnet Direct Client obtains history data using
two mechanisms in parallel:
n Accesses "real-time data" from "APoint" using COV/RP/RPM services

("normal" history).
n Retrieves data from "ALogCollector" using the ReadRange service
under the same conditions as backfill-only history collection
("backfilled" history).
This configuration is not recommended for the following reasons:
n Inefficient use of controller bandwidth (information is read twice from

the controller: once from the actual object, and once from the
corresponding TL/TLOGM object).
n The "backfilled" data always overwrites "normal" history. For example, if
a TL object is configured to collect data once a minute, the
corresponding Fast history sample in EBI will eventually be overwritten
by the minute samples.
n The data from the two different sources may not match (potentially
different collection mechanisms, time slew, data time-stamped at
different locations). This means that data originally stored via "normal"
history can change once backfill has occurred.
35
Gapfill history collection

Gapfill history collection was added in EBI R500 CU5. In this history
collection mode:
n The BACnet Direct Client accesses "real-time data" from "APoint" using
COV/RP/RPM services ("normal" history).
n The BACnet Direct Client also tracks potential history gaps (for
example, due to disconnection to a controller). When it can, the BACnet
Direct Client issues ReadRange requests to the TL/TLOGM object for
data where the history gap is potentially present, processes the data,
and tries to reconcile the new information with the history already
collected in EBI ("gapfilled" history).
Gapfill history collection uses the following mechanism:
1. The BACnet Direct Client accesses "real-time data" from "APoint" using
COV/RP/RPM services, and the changes are stored to EBI history.
2. The BACnet Direct Client also keeps track of potential gaps in history.
The following conditions are tracked:
l When the EBI server is not collecting history.
l When the BACnet Direct Client is not running.
l When the BACnet Direct Client has lost its connection with the
controller.
3. When the BACnet Direct Client can get data from the controller (for
example, on re-connection), for a gap that occurred from time T1 to T2:
l The BACnet Direct Client issues a ReadRange by time request for
"ALogCollector" to the controller, with T1 as the reference time and a
count of –1. The controller is expected to return the most recent log
record before T1.
l The BACnet Direct Client issues ReadRange by time requests for
"ALogCollector" to the controller to retrieve log records, until the last
record from before T2 is received.
l These samples are processed and sent to EBI in blocks to fill the gap
in history.
36
TIP: The gapfill mechanism relies on the controller correctly

returning the most recent sample before the reference time when the
retrieval count is –1. Some controller firmware can erroneously return
an older sample, in which case a "flatline" can occur in EBI history
(as the logic would conclude that there was no change between the
erroneous sample and the first sample after the reference time).
Advantage
Gapfill history collection has the following advantages:
n “Normal" history is available from EBI soon after the sample's

occurrence, with minimal delay.
n BAD samples during potential gaps in "normal" history are overwritten
with data from a TL/TLOGM object.
n Efficient use of bandwidth. The BACnet Direct Client requests the data
at a particular time from the controller only once, not twice.
Disadvantage
EBI history contains data reconciled from two different sources (with
potential discontinuities due to the different logging criteria and time-
stamping mechanisms), but there is no ability in EBI to distinguish between
the two.
Configuration
To configure gapfill history collection:
n The BACnet Point Server "TrendProcessingMode" registry value

should be set to 1.
n "APoint.AParameter" must be configured in EBI history assignment.
The Backfill only option should not be selected.
n The "ALogCollector" point must be downloaded to EBI.
n "ALogCollector" must be configured correctly for data to be collected.
n It is not necessary to configure "ALogCollector" to send Buffer_Ready
event notifications to EBI.
37
Configuring BACnet schedules

This section discusses how to override default settings within the BACnet
Schedules configuration.
Overriding default state text for binary object schedules

The BACnet Schedule point-detail display shows binary values as active or
inactive by default. The default text can be changed for each schedule
object using Quick Builder.
1. In Quick Builder, discover the binary object schedule.

2. Select the discovered schedule object and click the User Defined tab.
3. Click Insert.
4. Set custom parameters for active text:
a. In the Parameter name text box, type active_text .
b. From the Link type drop-down combo box, select Constant.
c. From the Value type drop-down combo box, select String.
d. In the Link type value text box, type in the required text string (for
example, ON).
5. Click Insert.
6. Set custom parameters for inactive text:
a. In the Parameter name text box, type inactive_text .
d. In the Link type value text box, type in the required text string (for
example, OFF).
7. Download the schedule object to the EBI server.
Overriding default state text for multistate object

schedules
The BACnet Schedule point-detail display shows multistate values as
enumeration values (for example, 1, 2, 3) by default. The default text can be
changed for each schedule object using Quick Builder.
1. In Quick Builder, discover the multistate object schedule.

2. Select the discovered schedule object and click the User Defined tab.
3. Click Insert.
4. Set custom parameters for each state text:
a. In the Parameter name text box, type state_text0 .
38

d. In the Link type value text box, type 0 .
5. For each state to be defined, repeat steps 3 and 4 with the Parameter
name defined as state_text# and the Link type defined as # (where #
represents the number of the state to be configured).
6. Download the schedule object to the EBI server.
Maintaining BACnet controllers

This section discusses backup and restore information applicable to
BACnet Controllers.
Point detail display (Advanced tab) for BACnet points

The Point detail display for BACnet points now contains an Advanced tab.
This tab uses different technology and augments the existing tabs, enabling
a user to see and potentially modify any property available on an object that
is built into EBI.
TIP: The Advanced tab is not available on systems that are licensed
with the Electronic Signature option.
Backing up BACnet controller configuration

It is recommended to back up BACnet controller information after initial
(and any subsequent revision to) configuration of the device. If needed,
backed up files can be used to restore a BACnet controller to its configured
state.
To back up a controller's configuration files

1. Log on to Station with supv security level or higher.
2. Choose View > System Status > Controllers.
3. Call up the point detail display for the controller.
4. Click the Maintenance tab.
5. Click Backup.
6. At the operator prompt, type in the controller's password and click OK.
The controller backup process will start automatically.
39
TIP: At the bottom of the Maintenance tab, you can track the
progress of the backup process by watching the Status and
Details information boxes.
TIP: At the bottom of the Maintenance tab, within the Files will be
located in directory field, you can view the folder where the
backed up files are located.
Restoring BACnet controller configuration
Prerequisites
A set of configuration files and a configuration XML file are required to
restore BACnet controller configuration information. These files can be
generated from either:
n A previous BACnet controller backup. This will automatically create the

files and store them in a defined repository.
n Generated by configuration tools. These tools can export the
configuration setup to files for restore.
In order to restore these files, they need to be stored within a specific
repository on the EBI server.
To restore the controller's configuration files:

1. Log on to Station with supv security level or higher.
2. Choose View > System Status > Controllers.
3. Call up the point detail display for the controller.
4. Click the Maintenance tab.
5. Click Restore.
6. At the operator prompt, type in the controller's password and click OK.
The controller restore process will start automatically.
TIP: At the bottom of the Maintenance tab, you can track the
progress of the restore process by watching the Status and
Details information boxes.
40
Copying BACnet configuration file for restore

For a BACnet controller restore, all configuration files required need to be
stored in the controller specific repository. The files generated from
previous controller backups will be automatically saved in the required
repository already. However, additional configuration files, which are
generated by third party configuration tools, will need to be manually copied
to the required repository.
To copy all configuration files to the restore

1. Log into the system with an Administrator account.
2. Choose Start > Programs > Accessories > Windows Explorer.
3. Navigate to the
C:\ProgramData\Honeywell\EBI\server\download\applica
tion folder.
4. Right-click the application folder window pane and choose New Folder.
5. Type in the controller's object name as the new folder name.
6. Copy all configuration files to the restored to the new controller object
folder.
7. Copy the configuration XML file to the new controller folder.
8. Rename the XML file to <Name>.xml , where Name is the controller's
object name.
Support for alternative BACnet specifications

This section describes support for alternative BACnet specfications.
KBOB BACnet 2017 requirements

This topic describes EBI support for KBOB BACnet 2017 requirements:
n AMEV support
n Support for extended point names in Quick Builder
n Quick Builder EDE Import Wizard
n Report configuration
n BACnet point name searches
n Unaffected EBI subsystems
The KBOB BACnet 2017 requirements allow the use of special characters
and extended BACnet point names.
41
NOTE: To use the KBOB BACnet 2017 enhancement, the EBI license
must be updated.
AMEV support
A new option, Enable read/write of Description property from controller at
runtime, has been added to the Quick Builder Tools > Options > BACnet
Options dialog box.
When this option is selected, during runtime the Description property of

the BACnet object is read from the controller. If this option is not selected,
during runtime the Description property of the object is read from the
EBI database.
NOTE: This change only affects BACnet points that have been
downloaded to EBI after this option is enabled; existing points must be
deleted from EBI and downloaded again.
Support for extended point names in Quick Builder

In Quick Builder a new option, Enable extended name for BACnet points, has
been added to the BACnet Options dialog box (Tools > Options > BACnet
options). When this option is selected, a new text box named Extended
Name appears in Quick Builder for the BACnet points fields list, which has
fewer restrictions than point name (TagName). The Extended Name text box
supports:
n Point names up to 64 characters in length.

n All special characters (except control characters such as Tab, CR, and
LF).
NOTE: The dollar sign ($) and ampersand character (@) are not
allowed as the first character.
NOTE: This change only affects BACnet points that have been
downloaded to EBI after this option has been selected; existing points
must be deleted from EBI and downloaded again.
42
Quick Builder EDE Import Wizard

The QB EDE Import Wizard assumes that the .csv file is UTF-8, but the
Wizard also supports UTF-16LE, which is the default EDE export format of
CARE/BACshark.
ANSI (Windows 1252) or another code page may not work for non-ASCII
characters; for example:
°C -?ß@%μ/:€;$,£+O=§ öä$éà£ç€
will load as:
If this is a problem, the operator should save the EDE file as UTF-8 by using
the Save As command in Notepad.
Report configuration
When specifying a list of point parameters in the definition for the History
report, because the comma character (,) is used as the delimiter, you must
escape the comma in point parameter names by using the backslash (\)
character, like this: \,
BACnet point name searches

When searching for point names by using the F12 key, a user must employ
the backslash (\) character to escape the following characters:
n Asterisk (*)
n Question mark (?)
n Colon (:)
n Backslash (\)
The <data
folder>\Honeywell\EBI\Client\Station\Station.ini file
(where <data folder> is the location where EBI data is stored) contains
an entry named BlackListedSearchTokens, which defines the
characters that are prohibited in Station search functions (for example, an
F12 search).
43
In order to include any characters listed in this entry in search strings, the
characters must be removed from the BlackListedSearchTokens
entry.
Unaffected EBI subsystems

The following EBI subsystems are not affected by the KBOB BACnet 2017
enhancements:
n OPC Data Transfer. Retains the 40-character length for point names and
uses existing character restrictions.
n Cloud Connector. Uses existing event Source field and 40-character long
point names with existing character restrictions.
NOTE: Honeywell Forge and Honeywell Forge Connect have

not been updated and still work with 40-character point names
and event Source field.
n Automation Rules. You can search for points using their extended name,
but when the rule is configured, the 40-character point name is
displayed and used in the rule.
n Global Schedules. Control items of type Honeywell Server Schedules
use the extended name, but BACnet control items use the 40-character
point name.
44
BACnet Secure Connect

BACnet Secure Connect (BACnet/SC), BACnet Standard addendum 135-
2016bj approved in November 2019, is a datalink layer option in the
BACnet protocol. The layer uses secure WebSocket connections over
Transport Layer Security (TLS 1.3), and has the following distinguishing
characteristics from BACnet/IP:
n Uses Transmission Control Protocol (TCP) instead of UDP

n Works with DNS, DHCP, firewalls, and NAT
n BBMD no longer required
n UDP broadcasts not used
BACnet/SC has a "hub and spoke" logical topology where BACnet/SC
nodes communicate via a BACnet/SC hub. A BACnet/SC network can co-
exist and communicate with a BACnet/IP network via a BACnet/SC-to-
BACnet/IP router.
The BACnet Point Server currently supports the BACnet/IP datalink layer,
and is fully interoperable with a BACnet/SC network via a suitable router.
45
46
CHAPTER
3 USING THE BACNET SERVER

This section describes how points on the EBI server are mapped to BACnet
objects.
If BACnetServer is licensed, BACnet Direct Client can only be used on a
remote computer.
You can use the BACnet Server on its own, or in conjunction with the
BACnet Direct Client. However, the Cimetrics BACstac software must be
installed first, and the computer restarted before the BACnet Server can
function.
The BACnet Server maps EBI server points into BACnet objects. Not all
BACnet object properties are mapped one-to-one, in which case the best
interpretation of the property is matched to the EBI server point attribute.
The BACnet Server operates over Ethernet and IP and supports the objects
listed in the Protocol Implementation Conformance Statement for BACnet
Interfaces.
Discovering Points with the BACnet Server

There are potentially 65000 points on the EBI server. Typically only a few
hundred or even less are required to be mapped as BACnet objects.
There are two methods by which the BACnet Server makes a EBI server
point a BACnet object.
n Using the whohas Method

n Using the bacnetbld Utility
Using the whohas Method

If the BACnet client (on another EBI system or a third-party system)
performs a
whohas <EBI server pointname>.<EBI server parameter>
or a
whohas <EBI server pointname>
request, the BACnet Server instantiates a BACnet object that maps to this
EBI server point and parameter.
47
Using the BACnet Server
Once a whohas request is performed, the BACnet Server retains this

mapping indefinitely. Next time the computer is restarted, there is no need
to repeat the whohas discovery process.
whohas AnalogPoint1.SP shall create an AO instance 1

BACnet object that the Present Value property always
looks at the SP parameter only. The result of this
request is the 'I-Have AO 1' response.
whohas AnalogPoint1 shall create an AO instance 1

BACnet object that the Present Value property maps
to the PV parameter on a read property and maps to
the SP or OP parameter on a write property request.
Using the bacnetbld Utility

The second discovery process is used if the BACnet client does not support
whohas and/or there are many EBI server points to map.
To use the banetbld utility, you need to create a text file that contains a list
of all the points that are required to be mapped as BACnet objects. The
point names must be in one of the following formats, depending on the type
of point:
n pointname.parametername, for a scan task point

n pointname, for a flexible point
The following figure shows an example text file, created using Notepad.
48
To run the bacnetbld utility

1. Open a Command Prompt window.
2. Type bacnetbld filename, where filename is the name of the text
file that contains the list of points you want to map.
There is a <filename>.errlog file that is printed and viewable to
show the result of this utility.
3. Restart the BACnet server.
Removing discovered points in the BACnet

Server
The BACnet Server stores device/object references for each discovered
point. If you need to remove these references, use the following procedure.
To remove stored references:

1. Open the Start-Stop EBI Server utility.
2. Select Database Only.
3. If prompted, click Yes to confirm the action.
5. Type the following command to remove the stored references:
bac_d freeheap
6. Restart the EBI server by selecting System Running in the EBI Server
dialog box.
Flexible Points
A flexible point must be configured on the EBI server to allow BACnet
server support before it can be mapped to a BACnet object.
Before using whohas and bacnetbld, check that the flexible point:
n Is sourced from a point server that supports BACnet object mapping.

n Has been built on the EBI server with BACnet server support
nominated. The way that BACnet server support is configured depends
on the type of point server interface the flexible point is served from, for
example, EXCEL 5000 Direct uses Quick Builder. See the relevant
controller reference for more information.
49
When using whohas and bacnetbld, flexible points can only be discovered
as <EBI server pointname> not <EBI server pointname>.<EBI
server parameter>. Some BACnet clients might timeout on a whohas
request for flexible points. In this case use bacnetbld to first discover these
points.
If the point server does not support BACnet object mapping, you need to
build a derived point so that the flexible point information can be mapped
indirectly to a BACnet object. See the Configuration Guide for information
about building derived points.
Configuring derived points

BACnet Server only supports limited intrinsic reporting for point server
points. Derived points are an effective way of generating BACnet intrinsic
notifications for point server points.
To configure derived points:

1. Create a user scan task channel and controller.
2. For each point server point parameter you wish to trigger intrinsic
notifications on, configure a user scan task point with a compatible
present value.
For example, to trigger notifications on the PointValue of an EXCEL
5000 Direct Analog Input point, create an analog user scan task point
with PV referencing PointValue of the EXCEL 5000 Direct Point.
3. Configure alarm limits or alarm values for each derived user scan task
point.
4. Use bacnetbld or whohas to map these user scan task points
through the BACnet Server.
5. Subscribe to notifications from the BACnet Server from your BACnet
client.
Rules that Determine the BACnet Object Type for

Standard Points
The BACnet Server uses the following rules to determine what type of
BACnet object (that is AI, AO, AV, BI, MI and so on) to map the EBI server
standard point to:
n When a parameter value is entered

n When a parameter value is omitted
50
n Determining the parameters for read/write requests

This mapping is also applicable for derived points.
When a Parameter Value is Entered

The following table shows how the BACnet Object type is derived from the
scan type, range, point parameter and the tag type.
Tag Type/ Point

PV MD OP SP A1 A2 A3 A4
Parameter
0 Status Points BI(1) BO BO(1) N/A N/A N/A N/A N/A

or BV or BV
(2) or (2) or
MI(3) MO(3)
1 Analog Points AI or MO AO or AO or AO or AO or AO or AO or
AV(2) AV(2) AV(2) AV(2) AV(2) AV(2) AV(2)
2 Accumulators AI or N/A N/A N/A N/A N/A N/A N/A

AV(2)
3 Access Points MI N/A N/A N/A N/A N/A N/A N/A
Notes from table
n (1) - If the range of the point is from 0 - 1 (i.e. two states) then the object
is of type Binary.
n (2) - If the scan type is < 2 (i.e. has no hardware address), then the
object is of type Binary Value or Analog Value.
n (3) - If the range of the point is greater than 2 then the object is of type
Multi-state.
The following abbreviations were used in the previous table:
Abbreviation Meaning
BI, BO, BV Binary Input, Binary Output, Binary Value
AI, AO, AV Analog Input, Analog Output, Analog Value
MI, MO Multi-state input, Multi-state output
N/A Not applicable
51
When a Parameter Value is Omitted

BACnet Object
PV SP OP Ax
Type
Status Point Y N/A N N/A MI or BI or BV
N N/A Y N/A MO or BO
Analog Y N N N AI or AV
Point
N Y Y Y AO or AV
Accum. Y N/A N/A N/A AI or AV

Point
Access Point Y N/A N/A N/A MI
Y – an address (either field or database) has been defined for this parameter
N/A – not applicable for this type of point
N – no address defined for this parameter
Example
For a EBI server status point, if:
l the PV is defined as a field address and the number of states is 2,

then it will be a BI object
l the PV is a database address, then it will be a BV object
l the number of states is greater than 2, then it will become a MI object.
For a EBI server analog point, if:
l any one of the SP, OP, Ax (i.e. A1-A4) parameters are defined and it
has a field address then it will be a AO object
l the point has a database address, then it will be a AV object.
52
Determining the Parameters for Read/Write Requests

Read Property Write Property
Analog Input PV PV
Analog Output PV, SP, or OP SP or OP
Analog Value PV, SP, or OP SP or OP
Binary Input PV PV
Binary Output PV, OP OP
Binary Value PV, OP OP
Multi-state Input PV PV
Multi-state Output PV OP
For example, on a Read Property of Present Value request of an Analog

Output object, if the corresponding EBI server point has a field address
defined for the PV, the PV will be returned. However, if the PV has no field
address and the SP has a field address, the SP will be returned. Likewise, if
the PV and the SP has no field address and the OP does have a field
address, the OP will be returned.
A similar strategy is employed for the Write Property to a Present Value. In
the case of an Analog Output object, a Write Property will write to the SP by
default, and to the OP if no SP field address is defined.
Rules that Determine the BACnet Object Type for

Flexible Points
When a flexible point is configured to map to a BACnet object, the rules
used to define the mapping are unique for each point server and flexible
point type. A flexible point that supports BACnet object mapping must have
a parameter definition called BACnetType, the value of which indicates
which XML definition describes this object mapping. These XML definitions
are contained in XML files located in the
\server\data\templates\bacnet folder that must reside on the EBI
server.
53
Example
The room temperature read from an EXCEL 5000 Direct
Analog Input point called 'RoomTemp' is required to
be served from the EBI server to a third-party
BACnet client. In Quick Builder the RoomTemp point
is configured as a BACnet object of type Analog
Input, which is then downloaded to the EBI server.
(See the Honeywell EXCEL 5000 Interface Reference
for more information.)
From the XML definition, the BACnet server

translates RoomTemp.PointValue to the PresentValue
property of the particular AI object instance
created to represent the point RoomTemp.
Translation of flexible point parameters to BACnet object properties is

defined uniquely by an XML definition for each point server interface and
flexible point type. Do not attempt to modify the XML definition files.
A subset of BACnet object properties are determined directly by the
BACnet server regardless of the point server type. The determination of
these properties is fixed. The following table lists these properties, which
are common to all flexible points.
Table 3-1: Common Properties for BACnet Objects Mapped from Flexible Points
Property Identifier Property Datatype Code
Object_Identifier BACnetObjectIdentifier R
Object_Name CharacterString R
Object_Type BACnetObjectType R
Description CharacterString OR
Event_State BACnetEventState R
Time_Delay Unsigned OR
Notification Class Unsigned OR
Acked_Transitions BACnetEventTransitionBits OR
Notify_Type BACnetNotifyType OR
54
EBI Server Point Mapping to BACnet Objects

The description for each BACnet Object includes a table summary that lists
the property identifier, the datatype of the property, some comments or
example data, and one of the following:
n OR – indicates that the property is optional and is readable using

BACnet services.
n OW – indicates that the property is optional and is readable and writable
using BACnet services.
n R – indicates that the property is mandatory and readable using BACnet
services.
n W – indicates that the property is mandatory, readable, and writable
using BACnet services.
Each property in the supported BACnet standard objects is designated one
of the above codes. When a property is designated an OR or an OW,
ASHRAE has indicated that the property is optional to the BACnet object
and it is up to the user to include these properties in their development.
Therefore, any OR or OW means that the property has been included in this
development.
The value of R or OR properties may be examined through the use of the
ReadProperty service. When a property is designated as W or OW, the
value of the property can be changed through the use of the WriteProperty
service. The value of W or OW properties may also be examined through
the use the ReadProperty service. Any R or OR properties may be changed
to be writable if required in future.
Each object has a set of attributes defined as properties. These properties
have an associated enumerated value; for more information, see the
BACnet Standard.
Device Object
The Device Object type defines a standardized object whose properties
represent the externally visible characteristics of a BACnet Device. The EBI
server is therefore called a BACnet Device. There is one Device Object in
each BACnet Device.
A Device Object is referenced by its Object_Identifier property, which is not
only unique to the BACnet Device that maintains this object but is also
unique throughout the BACnet internetwork.
The object and its supported properties in this development are
summarized in the following table.
55
Table 3-2: Supported Properties of the Device Object
System_Status BACnetDeviceStatus R
Honeywell_Name CharacterString R
Honeywell_Identifier Unsigned16 R
Model_Name CharacterString R
Firmware_Revision CharacterString R
Application_Software_Version CharacterString R
Location CharacterString OW
Protocol_Version Unsigned R
Protocol_Conformance_Class Unsigned(1..6) R
Protocol_Services_Supported BACnetServicesSupported R
Protocol_Object_Types_Supported BACnetObjectTypesSupported R
Object_List BACnetARRAY[N] of ObjectIdentifier R
Max_APDU_Length_Accepted Unsigned R
Segmentation_Supported BACnetSegmentation R
Local_Time Time OR
Local_Date Date OR
UTC_Offset INTEGER OR
Daylight_Savings_Status BOOLEAN OR
APDU_Segment_Timeout Unsigned R
56
APDU_Timeout Unsigned R
Number_of_APDU_Retries Unsigned R
Device_Address_Binding List of BACnetAddressBinding R
Table 3-3: Property Descriptions of the Device Object
Property
Description
Identifier
Object_Identifier BACnetObjectIdentifier is a numeric code that is used to identify

the object. For a Device Object, this identifier is unique
internetwork-wide. For other objects, it is only unique to the
BACnet-device. The instance number defaults to the system
number identity that comes with the Honeywell Software License
Certificate. This may be changed by the user if required.
Object_Name Name of the object of type CharacterString that is unique

internetwork-wide for Device Object. For other objects, it is only
unique to the BACnet-device. This defaults to the network host-
name of the EBI server.
Object_Type Indicates membership in a particular object type class. For

example, DEVICE or ANALOG_INPUT.
System_Status Reflects the current physical and logical status of the BACnet
Device. Possibilities are: {OPERATIONAL, OPERATIONAL_READ_
ONLY, DOWNLOAD_REQUIRED, DOWNLOAD_IN_PROGRESS,
NON_OPERATIONAL}. For EBI server, only OPERATIONAL or
NON_OPERATIONAL is relevant.
Honeywell_ Identifies the manufacturer. This is defaulted to Honeywell.

Name
Honeywell_ This is a unique vendor identifier assigned by ASHRAE.

Identifier Honeywell is number 17.
Model_Name This is the name of the system, such as 'Enterprise Buildings

Integrator'.
Firmware_ This is the release version of the EBI server system.

Revision
57
Property
Description
Identifier
Applicaton_ This is the version of the BACstac® software used in this

Software_ development.
Version
Location Indicates the physical location of the device. This is blank by

default and can be set during commissioning.
Description This is the release date of the Server.
Protocol_Version Represents the version of the BACnet protocol supported.
Protocol_ This development conforms to class 4.

Conformance_
Class
Protocol_ Indicates which standard services are supported.

Services_
Supported
Protocol_Object_ Indicates which objects are supported in this development.

Types_
Supported
Object_List Lists the object and its identifiers that are accessible within the
device. The Device Object and Notification Class is always shown
here. This list will change continuously since Point objects are
created dynamically.
Max_APDU_ Maximum number of octets that may be contained in a single,

Length_ indivisible application layer protocol data unit. This value is >=
Accepted 50. The value is also constrained by the underlying data link
technology. This is defaulted by the BACstac® software.
Segmentation_ Indicates support of segmentation of messages. Possibilities are:

Supported {SEGMENTED_BOTH, SEGMENTED_TRANSMIT, SEGMENTED_
RECEIVE, NO_SEGMENTATION}.
Local_Time Indicates the local time of the Server.
Local_Date Indicates the date of the Server.
UTC_Offset Indicates the number of minutes (-720+720) offset between local

standard time and Universal Time Coordinated time.
58
Property
Description
Identifier
Daylight_ Indicates whether Daylight Saving is supported (TRUE or FALSE).

Savings_Status
APDU_Segment_ Amount of time in ms between retransmission of APDU segment.

Timeout This value is non-zero if the property Number_Of_APDU_Retries
is non-zero. For reliable communications, all BACnet-devices on
the network should have this value the same. This is defaulted by
the BACstac software.
APDU_Timeout Amount of time in ms between retransmissions of an APDU

requiring acknowledgment for which no acknowledgment has
been received. Default is 3000ms and can be changed
dynamically via the Write Property Services. This value is non-
zero if the property Number_Of_APDU_Retries is non-zero. For
reliable communications, all BACnet-devices on the network
should have this value the same. This is defaulted by the
BACstac® software.
Number_Of_ Indicates the maximum number of times that an APDU is

APDU_Retries retransmitted. Default is 0. A value of 0 means that the device
does not perform retries.
Device_Address_ This is a list of BACnetAddressBinding, each of which consists of

Bindings an ObjectIdentifier of the Device Object and a BACnet device
address in the form of BACnetAddress. Entries in this list identify
the actual device addresses that are used when the remote
device must be accessed via a BACnet service request. The list
may be empty if no device identifier-device address bindings are
currently known to the device. For EBI server, this list is empty.
The optional components of the Device Object Properties are

chosen to verify times between the EBI server and the third-party
server (for example, XFi). It is up to the third-party system to
determine what is to be done with the time information.
Analog Input Object

The Analog Input Object type defines a standardized object whose
properties represent the externally visible characteristics of a analog input.
The object and its supported properties in this development are
summarized in the following table.
59
Table 3-4: Supported Properties of the Analog Input Object
Property
Property Datatype Code
Identifier
Object_ BACnetObjectIdentifier R
Identifier
Present_ REAL R1
Value
Device_Type CharacterString OR
Status_Flags BACnetStatusFlags R
Reliability BACnetReliability OR
Out_of_ BOOLEAN R
Service
Update_ Unsigned OR
Interval
Units BACnetEngineeringUnits R
Min_Present_ REAL OR
Value
Max_Present_ REAL OR
Value
Resolution REAL OR
COV_ REAL OR2

Increment
1This property is required to be Writable if Out_of_Service is TRUE.
2This property is required if COV Reporting is supported.
60
Property
Identifier
Time_Delay Unsigned OR1
Notification Unsigned OR
Class
High_Limit REAL OR
Low_Limit REAL OR
Deadband REAL OR
Limit_Enable BACnetLimitEnable OR
Event_Enable BACnetEventTransitionBits OR
Acked_ BACnetEventTransitionBits OR
Transitions
Table 3-5: Property Descriptions of the Analog Input Object With Standard Point Types
Property
Description
Identifier
Object_ Unique numeric number used to identify the object. For all points,
Identifier the instance number is incremented as objects are created.
Object_Name Unique name for the object. For all points, the name is the same as
the EBI server wide point name and the parameter.
Object_Type Indicates the object class. For analog input this is ANALOG_INPUT.
Present_Value Indicates the current value in engineering units for analog points.
Description This is point description of the associated EBI server point.
Device_Type This is the type of the controller the associated EBI server point is
connected to.
Status_Flags Represents four boolean flags that indicate the general health of a
point. Three of the flags are associated with the values of other
1These properties are required if Intrinsic Reporting is supported.
61
Property
Description
Identifier
properties of this object. The four flags are:
l IN_ALARM, the values being:

FALSE(0) if Event_State = NORMAL, else TRUE(1).
l FAULT, the values being:

TRUE if Reliability not equal to NO_FAULT_DETECTED, else FALSE.
l OVERRIDDEN. This is set to TRUE when the point is put in Out
of Scan by the EBI server.
l OUT_OF_SERVICE. This is the same value as Out_Of_Service
property.
Event_State The event state of the object: {Normal, Fault, OffNormal, High
Limit, Low Limit}. This is always NORMAL if intrinsic reporting is
not supported.
Reliability Provides an indication of whether the Present_Value is reliable as

far as the BACnet-device can determine, and if not, why.
l No_Fault_Detected. Point on scan and not BAD value.

l No_Sensor, Open_Loop, Shorted_Loop. Not applicable to EBI
server.
l Over_Range, Under_Range. If PV is over the low/high limit.
l Unreliable_Other. Point is on scan and BAD value.
Out_Of_ If the point MD (mode) parameter is 'Manual' this property is set. If

Service MD is 'auto' or in other states, it is cleared.
This property is writable to allow BACnet clients to send control to a

point on the EBI system.
Update_ Indicates the maximum period of time between updates to the PV

Interval in hundredths of a second. This is set to be the 'PVPERIOD' of the
point. If no PVPERIOD is specified, the value is 0.
Units Indicates the measurement units of this object, and is mapped to

the equivalent EBI server engineering units of the associated point.
Min_Pres_ Indicates the lowest/highest number in engineering units that can

Value, Max_ be reliably obtained for the Present_Value of this object. For the
62
Property
Description
Identifier
Pres_Value EBI server, this is set to the Range.
Resolution Indicates the smallest recognizable change in Present_Value. This

is the EBI analog point drift deadband.
COV_ Minimum change in PV that causes a COVNotification issued to

Increment subscribers. This defaults to be the same as the resolution but the
value can be changed by the user.
Time_Delay Specifies the minimum time in seconds that the PV must remain
outside the band of High_Limit and Low_Limit before a TO_
OFFNORMAL event is generated, or within the same band (taking
in consideration the DeadBand) before a TO_NORMAL event is
generated. Since the Server has no concept of this property, the
value can be set by the user. The default is 0 seconds.
Notification_ Specifies the notification class to be used when handling and

Class generating event notifications for this object. This property
implicitly refers to a Notification Class Object that has a
Notification_Class property with the same value. The default is 0
(no notification class), and can be changed by the user.
High_Limit Specifies a limit that the PV must exceed before an event is

generated. This is to the PV high limit defined for the point on the
Server. If no PV high limit is defined, this value defaults to the high
value of the range.
Low_Limit Specifies a limit that the PV must fall below before an event is
generated. This is set to the PV low limit defined for the point on
the Server. If no PV low limit is defined, this value defaults to the
low value of the range.
DeadBand Specifies a range between High_Limit and Low_Limit which the PV

must remain for a TO_NORMAL event to be generated. This is set
to the analog alarm deadband of the Server point.
Limit_Enable Conveys two flags that separately enable and disable reporting of
High and Low Limit off-normal and return to normal events. If the
Server point has its alarm disabled, then the value is {FALSE,
FALSE}. If alarm is enabled, then the value is determined by the
priority of the alarm selection. If the priority is 'Journal', then the
flag for the corresponding limit is turned off. If the priority is not
63
Property
Description
Identifier
equal to 'Journal', then the flag is turned on for the corresponding

limit.
Event_Enable Conveys three flags that separately enable and disable reporting of
TO_OFFNORMAL, TO-FAULT, and TO_NORMAL events. The default
is {TRUE, TRUE, TRUE}, and can be changed by the user.
Acked_ Conveys three flags that separately indicate the receipt of

Transitions acknowledgments for TO_OFFNORMAL, TO_FAULT, and TO_
NORMAL events. The default is {FALSE, FALSE, FALSE}, and can be
changed by the user.
Notify_Type Conveys whether notifications generated are to be ALARMS or

EVENTS. The default is EVENTS, and can be changed by the user.
In the BACnet standard, the Present_Value is required to be

writable when the object is Out of Service for the purposes of
simulating a fixed condition or for testing purposes. The standard
also states that other functions that depend on the state of the
Present_Value properties shall respond to changes made to this
property as if the changes had occurred in the physical input.
Analog Output and Analog Value Objects

The Analog Output and the Analog Value Object type defines a
standardized object whose properties represent the externally visible
characteristics of an analog output and an analog value respectively. An
'analog value' is a software point residing in the memory of the BACnet
device.
Both objects have the same supported properties in this development and
are summarized in the following table. Any property identifiers not
described below follows the same philosophy as described in the Analog
Input Object.
Table 3-6: Property Identifier for Analog Output and Analog Value Objects
Property
Identifier
Object_ BACnetObjectIdentifier R
Identifier
64
Property
Identifier
Present_Value REAL W
Out_of_ BOOLEAN R
Service
Units BACnetEngineeringUnits R
Min_Present_ REAL OR1

Value
Max_Present_ REAL OR
Value
Resolution REAL OR
Priority_Array BACnetPriorityArray R
Relinquish_ REAL R
Default
COV_ REAL OR2

Increment
Notification_ Unsigned OR
1These properties are present if the object is Analog Output.
2This property is required if COV Reporting is supported.
65
Property
Identifier
Class
High_Limit REAL OR
Low_Limit REAL OR
Deadband REAL OR
Limit_Enable BACnetLimitEnable OR
Acked_ BACnetEventTransitionBits OR
Transitions
Table 3-7: Property Descriptions for the Analog Output and Analog Value Objects
Property
Description
Identifier
Priority_Array Array of prioritized values. Follows the standard BACnet priority

mechanism; for more information, see the BACnet Standard.
Relinquish_ Default value to be used for the PV when all command priority
Default values in the Priority_Array property have NULL value. See Section
19 of the standard. For the EBI server, when all elements in the
Priority_Array are NULL, the Relinquish_Default will be the same as
the Present_Value.
Binary Input The Binary Input object type defines a standardized object whose
properties represent the externally visible characteristics of a binary
input. A binary input object is a physical device or hardware input
that can be in only one of two states. A Polarity property in this
object determines the application-level logical states of the object.
Digital points with only two possible states in the EBI server are
represented with these Binary Objects.
The Binary Input Object properties supported in this development

are summarized in Binary Input Object Properties table. Any
property identifiers not described below follow the same philosophy
as described in the Analog Input Object.
66
Table 3-8: Binary Input Object Properties
Present_Value BACnetBinaryPV R1
Out_of_Service BOOLEAN R
Polarity BACnetPolarity R
Active_Text CharacterString OR
InActive_Text CharacterString OR
Notification_Class Unsigned OR
Alarm_Value BACnetBinaryPV OR
67
Table 3-9: Property Descriptions for the Binary Input Objects With Standard Point Types
Property
Description
Identifier
Present_ Logical state of the binary point, either ACTIVE or INACTIVE.

Value
Polarity Indicates the relationship between the physical state and the logical
state of the point. Polarity can be NORMAL or REVERSE. Since the EBI
server already has a polarity mechanism, this is set to NORMAL to
avoid the confusion of reversing the polarity twice.
Inactive_ Represents a human-readable description of the INACTIVE state of the

Text PV. This is equivalent to the Server text for the '0' state.
Active_ Represents a human-readable description of the ACTIVE state of the

Text PV. This is equivalent to the Server text for the '1' state.
Time_ Specifies the minimum time in seconds during which the PV must
Delay remain equal to the Alarm_Value before a TO_OFFNORMAL event is
generated, or remain not equal to Alarm_Value before a TO_NORMAL
event is generated. Since the EBI server has no concept of this
property, the value can be set by the user.
Alarm_ Specifies the value that the PV must have before an event is generated.
Value For the EBI server, this value is the alarm state of the digital point. If
both states are being alarmed by the EBI server, then the state with the
most highest priority is chosen. If both have the same priority, then the
first state (state 0) is chosen.
Binary Output and Binary Value (Pseudo Binary Points)

The Binary Output or Binary Value object type defines a standardized
object whose properties represent the externally visible characteristics of a
binary output/binary value. A binary object is a physical device or hardware
output that can be in only one of two states.
The object's Polarity property determines the application-level logical states
of the object. A binary value is a control system parameter residing in the
memory of the BACnet Device. Digital points with only two states in the EBI
server are represented with these Binary Objects.
The Binary Output and Binary Value Objects properties supported in this
development are summarized in the following table. Any property identifiers
not described here follows the same philosophy as described in the Analog
Input Object.
68
Table 3-10: Binary Output and Binary Value Object Properties
Present_Value BACnetBinaryPV W1R2
Polarity BACnetPolarity R
Active_Text CharacterString OR
InActive_Text CharacterString OR
Relinquish_Default BACnetBinaryPV R
Notification_Class Unsigned OR "OR" above
Alarm_Value BACnetBinaryPV OR "OR" above
1This property is be Writable if object is of type Binary Output.
2This property is Writable if Out_of_Service is TRUE and object is

Binary Value.
3
These properties are required if Intrinsic Reporting is supported.
69
Event_Enable BACnetEventTransitionBits OR "OR" on the previous page
Acked_Transitions BACnetEventTransitionBits OR "OR" on the previous page
Notify_Type BACnetNotifyType OR "OR" on the previous page
Multi-state Input
The Multi-state Input Output object type defines a standardized object
whose Present_Value represents the result of an algorithmic process within
the BACnet Device in which the object resides. Since the algorithmic
process itself is a local matter and is not defined by the protocol, multi-state
inputs are used to represent the EBI server digital input points that have
more than two states (there are a maximum of eight states). The Multi-state
Input object type and its properties are summarized in the following table.
ATTENTION: Do not confuse the Present_Value state with the

Event_State property, which reflects the offnormal state of the Multi-
State Input. Any property identifiers not described here follows the
same philosophy as described in other BACnet Objects.
Table 3-11: Multi-State Input Properties
Present_Value Unsigned R1
70
Number_of_States Unsigned R
State_Text BACnetARRAY[N] of CharacterString OR
Alarm_Values List of Unsigned OR
Fault_Values List of Unsigned OR
Table 3-12: Property Description for Multi-State Input Objects with Standard Point Types
Property
Description
Identifier
Present_ Reflects the logical state of the input which can be one of 'n' states,
Value where 'n' is defined in Number_Of_States. PV is always greater than 0.
Object The object name of a Multi-state input is represented differently if it

Name maps to a EBI server access point. Since there are no parameters for
card and cardholder information in the BACnet standard types, a
strategy has been devised to notify clients whether a card has been
granted access or denied access. This information is relayed when
requested by the read property, or can also be subscribed as a COV.
Card Number: 12 characters,
Technology Type: 4 characters, (SE, uLPM, or FS90)
Access State: 7 characters, (Access or Denied)
71
Property
Description
Identifier
Reason Access or Denied: 20 characters,
Cardholder Name: 32 characters,
Access Point Descriptor: 40 characters
For example, an object name field may look like:
123456789012, SE, Access, Granted, John Smith, Door Level 1
The Object Name field is not writable for an access point.
Number_ Defines the number of states that the PV may have. This is determined
Of_States from the Server digital point.
State_Text Array of CharacterString representing descriptions of all possible

states of the PV. This is determined from the Server digital point.
Alarm_ Specifies any states that PV must equal before a TO_OFFNORMAL

Values event is generated. This is made equivalent to the states that have
their alarms enabled (priority must not be 'Journal') in the Server point.
Fault_ Specifies any states that PV must equal before a TO_FAULT event is
Values generated. Since the Server has no concept of this property, this is
defaulted to no states.
Multi-state Output
The Multi-state Output object type defines a standardized object whose
properties represent the desired state of one or more physical outputs or
processes within the BACnet Device in which the object resides. For
example, a particular state may represent the active/inactive condition of
several physical outputs or perhaps the value of an analog output. The
Present_Value property is an unsigned integer number representing the
state. The State_Text property associates a description with each state.
Since the algorithmic process is a local matter and is not defined by the
protocol, multi-state outputs are used to represent the EBI server digital
output points that have more than 2 states (there are a maximum of 8
states). The Multi-state Output object type and its properties are
summarized in the following table. Any property identifiers not described
here follow the same philosophy as described in other BACnet Objects.
72
Table 3-13: Multi-State Output Object Properties
Present_Value Unsigned W
Number_of_States Unsigned R
State_Text BACnetARRAY[N] of CharacterString OR
Relinquish_Default Unsigned R
Feedback_Value Unsigned OR
73
Table 3-14: Property Description for Multi-State Output Object With Standard Point Types
Property
Description
Identifier
Feedback_ Indicates the status of a feedback value from which the PV must
Value differ before a TO_OFFNORMAL event is generated.
Engineering units supported by BACnet Server

When defining the PV of a point, you need to specify the type of engineering
unit used in representing the PV value. BACnet compares the engineering
unit specified for an EBI point against a fixed list and returns an
enumeration to BACnet clients. The proper syntax must be used in order for
BACnet to interpret the engineering unit correctly.
Following is a list of supported units:
BACnet Engineering Unit

EBI Unit BACnet Unit
Number
% UNIT_PERCENT 98
%/s UNIT_PERCENT_PER_SECOND 99
%ob/ft UNIT_PERCENT_OBSCUR_PER_FOOT 143
%ob/m UNIT_PERCENT_OBSCUR_PER_ 144

METER
/h UNIT_PER_HOUR 131
/m UNIT_PER_MINUTE 100
/s UNIT_PER_SECOND 101
A UNIT_AMPERES 3
bar UNIT_BARS 55
Btu UNIT_BTUS 20
Btu/h UNIT_BTUS_PER_HOUR 50
Btu/lb UNIT_BTUS_PER_POUND 117
Btu/lba UNIT_BTUS_PER_LB_DRY_AIR 24
74

Number
C UNIT_DEGREES_C 62
C/H UNIT_DEGREES_C_PER_HOUR 91
C/m UNIT_DEGREES_C_PER_MINUTE 92
cm UNIT_CENTIMETERS 118
cm2 UNIT_SQ_CENTIMETERS 116
cmH2O UNIT_CENTIMETERS_OF_WATER 57
cmHg UNIT_CENTIMETERS_OF_MERCURY 60
cur1 UNIT_CURRENCY1 105
cyc/h UNIT_CYCLES_PER_HOUR 25
cyc/m UNIT_CYCLES_PER_MINUTE 26
day UNIT_DAYS 70
deg UNIT_DEGREES_ANGULAR 90
degdaC UNIT_DEGREE_DAYS_C 65
degdaF UNIT_DEGREE_DAYS_F 66
degPh UNIT_DEGREES_PHASE 14
delF UNIT_DELTA_DEGREES_ 120

FAHRENHEIT
delK UNIT_DELTA_DEGREES_KELVIN 121
F UNIT_DEGREES_F 64
F/H UNIT_DEGREES_F_PER_HOUR 93
F/m UNIT_DEGREES_F_PER_MINUTE 94
ft UNIT_FEET 33
ft/m UNIT_FEET_PER_MINUTE 77
ft/s UNIT_FEET_PER_SECOND 76
75

Number
ft2 UNIT_SQ_FEET 1
ft3 UNIT_CUBIC_FEET 79
ft3/m UNIT_CUBIC_FEET_PER_MINUTE 84
ft3/s UNIT_CUBIC_FEET_PER_SECOND 142
ftc UNIT_FOOT_CANDLES 38
Gal UNIT_US_GALLONS 83
Gal/m UNIT_US_GALLONS_PER_MINUTE 89
h UNIT_HOURS 71
hp UNIT_HORSEPOWER 51
HPa UNIT_HECTOPASCALS 133
Hz UNIT_HERTZ 27
IGal UNIT_IMPERIAL_GALLONS 81
IGal/m UNIT_IMP_GALLONS_PER_MINUTE 86
in UNIT_INCHES 32
in2 UNIT_SQ_INCHES 115
inH2O UNIT_INCHES_OF_WATER 58
inHg UNIT_INCHES_OF_MERCURY 61
J UNIT_JOULES 16
J/K UNIT_JOULES_PER_DEGREE_K 127
J/kga UNIT_JOULES_PER_KG_DRY_AIR 23
J/kgK UNIT_JOULES_PER_KG_DEGREE_K 128
K UNIT_DEGREES_K 63
kg UNIT_KILOGRAMS 39
76

Number
kg/h UNIT_KGS_PER_HOUR 44
kg/m UNIT_KGS_PER_MINUTE 43
kg/s UNIT_KGS_PER_SECOND 42
kHz UNIT_KILOHERTZ 129
kJ UNIT_KILOJOULES 17
kJ/kG UNIT_KILOJOULES_PER_KG 125
kmh UNIT_KILOMETERS_PER_HOUR 149
Kohms UNIT_KILOHMS 122
kPa UNIT_KILOPASCALS 54
kV UNIT_KILOVOLTS 6
kVA UNIT_KILOVOLT_AMPERES 9
kVAR UNIT_KILOVOLT_AMPERES_ 12
REACTIVE
kW UNIT_KILOWATTS 48
kWh UNIT_KILOWATT_HOURS 19
kwh/ft2 UNIT_KWATT_HOURS_PER_SQ_FOOT 138
kwh/m2 UNIT_KWATT_HOURS_PER_SQ_ 137

METER
L UNIT_LITERS 82
L/h UNIT_LITERS_PER_HOUR 136
L/m UNIT_LITERS_PER_MINUTE 88
L/s UNIT_LITERS_PER_SECOND 87
lbf/in2 UNIT_LBS_FORCE_PER_SQ_INCH 56
lbm UNIT_POUNDS_MASS 40
77

Number
lbm/h UNIT_LBS_MASS_PER_HOUR 46
lbm/m UNIT_LBS_MASS_PER_MINUTE 45
lbm/s UNIT_LBS_MASS_PER_SECOND 119
lm UNIT_LUMENS 36
lx UNIT_LUXES 37
m UNIT_METERS 31
m/h UNIT_MILES_PER_HOUR 78
m/s UNIT_METERS_PER_SECOND 74
m2 UNIT_SQ_METERS 0
m3 UNIT_CUBIC_METERS 80
m3/h UNIT_CUBIC_METERS_PER_HOUR 135
m3/s UNIT_CUBIC_METERS_PER_SECOND 85
mA UNIT_MILLIAMPERES 2
mb UNIT_MILLIBARS 134
MHz UNIT_MEGAHERTZ 130
min UNIT_MINUTES 72
MJ UNIT_MEGAJOULES 126
mj/ft2 UNIT_MEGAJOULES_PER_SQ_FOOT 140
mj/m2 UNIT_MEGAJOULES_PER_SQ_ 139

METER
mm UNIT_MILLIMETERS 30
mmHg UNIT_MILLIMETERS_OF_MERCURY 59
Mohms UNIT_MEGOHMS 123
month UNIT_MONTHS 68
78

Number
MV UNIT_MEGAVOLTS 7
mV UNIT_MILLIVOLTS 124
MVA UNIT_MEGAVOLT_AMPERES 10
MVAR UNIT_MEGAVOLT_AMPERES_ 13
REACTIVE
MW UNIT_MEGAWATTS 49
mW UNIT_MILLIWATTS 132
ohms UNIT_OHMS 4
Pa UNIT_PASCALS 53
PF UNIT_POWER_FACTOR 15
ppb UNIT_PARTS_PER_BILLION 97
ppm UNIT_PARTS_PER_MILLION 96
psi/F UNIT_PSI_PER_DEGREE_F 102
rad UNIT_RADIANS 103
rpm UNIT_REVOLUTIONS_PER_MIN 104
RT UNIT_TONS_REFRIGERATION 52
s UNIT_SECONDS 73
T UNIT_TONS 41
Th UNIT_TON_HOURS 22
thm UNIT_THERMS 21
V UNIT_VOLTS 5
VA UNIT_VOLT_AMPERES 8
VAR UNIT_VOLT_AMPERES_REACTIVE 11
W UNIT_WATTS 47
79

Number
W/ft2 UNIT_WATTS_PER_SQ_FOOT 34
W/m2 UNIT_WATTS_PER_SQ_METER 35
W/m2K UNIT_WATTS_PER_SQ_M_DEGREE_K 141
week UNIT_WEEKS 69
WH UNIT_WATT_HOURS 18
year UNIT_YEARS 67
EXCEL 5000 Direct to BACnet Property Mapping

The mapping tables show the supported BACnet object properties for each
EXCEL 5000 Direct point type.
The table columns are described below.
Column
Description
Name
Property All supported properties for the given BACnet object.
Readability Shows whether the EXCEL 5000 point type supports the read
operation of the given BACnet property. Note that not all property
types are supported in the BACnet server, In addition, some
properties can be read directly from the BACnet server, whereas
others need to be mapped via an XML file.
Each property is flagged R , NS , XM , or XC:
l R - property is mapped and can be read directly from the BACnet server.
l NS - property is currently not supported with EXCEL 5000 Direct point
types.
l XM - property is readable via mapping to a tag within the XML file.
l XC - property can be read from XML, but is not mapped to any tags by
default.
l When the value XC or XM, an additional parameter is included to show
whether a default built-in value is used of the XML property mapping is
not found. This additional value can be D or N.
l D - indicates that a default value will be used if the property is not
mapped in the XML.
80
Column
Description
Name
l N - indicates that there are no default values for this property if there is
no XML mapping.
See the topic, “XML Parameter Tag and Default Values”, to see the
corresponding XML tags and any default values.
Writability Shows whether the EXCEL 5000 point type supports the mapping of
a write operation of the given BACnet property. Note that all property
types are not supported in the BACnet server.
l Each property is flagged W , RO , NS , XM , or XC :

l W - property is supported and can be written directly.
l RO - property is supported, but its value is read only.
l NS - property is currently not supported with EXCEL 5000 Direct point
types.
default.
AI - Analog Input Mapping (EXCEL 5000 Direct to

BACnet)
Property Readability Writability
Object_ R RO
Identifier
Object_Name R RO
Object_Type R RO
Present_Value XM, N XM1
Description R RO
1The Present_Value property is only writable when Out_Of_Service is TRUE.
81
Device_Type XM, N RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_ XM, D XM
Service
NOTE: The Out_Of_Service property is
represented as <MODE> tag in XML files.
Update_ XC, N RO
Interval
Units XC, D RO
Min_Pres_ XC, N RO
Value
Max_Pres_ XC, N RO
Value
Resolution XC, N RO
COV_ XC, D RO
Increment
Time_Delay R W
Notification_ R W
Class
High_Limit XM, D RO
Low_Limit XM, D RO
Deadband XM, D RO
Limit_Enable XC, D RO
Event_Enable XC, D XC
Acked_ R RO
82
Transitions
Notif_Type R W
Event_Time_ NS NS
Stamps
Profile_Name NS NS
AO - Analog Output Mapping (EXCEL 5000 Direct to

BACnet)
Object_Identifier R RO
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_Service XM2, D XM
Units XC, D RO
Min_Pres_Value XC, N RO
Max_Pres_Value XC, N RO
2The Out_Of_Service property is represented as <MODE> tag in XML files.
83
Resolution XC, N RO
Priority_Array R RO
Relinquish_Default R RO
COV_Increment XC, D RO
Time_Delay R W
Notification_Class R W
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
Acked_Transitions R RO
Notif_Type R W
Event_Time_Stamps NS NS
Profile_Name NS NS
AV - Analog Value Mapping (EXCEL 5000 Direct to

BACnet)
Object_Name R RO
Object_Type R RO
84
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Units XC, D RO
Priority_Array R RO
Time_Delay R W
High_Limit XM, D RO
Low_Limit XM, D RO
Deadband XM, D RO
Notif_Type R W
Profile_Name NS NS
85
BI - Binary Input Mapping (EXCEL 5000 Direct to

BACnet)
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Polarity XC, D RO
Inactive_Text XC, N RO
Active_Text XC, N RO
Change_Of_State_Time NS NS
Change_Of_State_Count NS NS
Time_Of_State_Count_Reset NS NS
Elapsed_Active_Time NS NS
Time_Of_Active_Time_Reset NS NS
Time_Delay R W
86
Alarm_Value XC, D RO
Notif_Type R W
Profile_Name NS NS
BO - Binary Output Mapping (EXCEL Classic to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Polarity XC, D RO
87
Minimum_Off_Time NS NS
Minimum_On_Time NS NS
Priority_Array R RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
BV - Binary Value Mapping (EXCEL 5000 Direct to

BACnet)
Object_Name R RO
88
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_Service XM2, D X
Priority_Array R RO
Time_Delay R W
89
Notif_Type R W
Profile_Name NS NS
MI4 MI8 MI16 - Multi-State Input Mapping (EXCEL 5000

Direct to BACnet)
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Number_Of_States XM, N RO
State_Text XC, D RO
Time_Delay R W
90
Alarm_Values XC, D RO
Fault_Values XC, D RO
Notif_Type R W
Profile_Name NS NS
MO4 MO8 MO16 - Multi-State Output Mapping (EXCEL

5000 Direct to BACnet)
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_Service XM2, D X, M
91
State_Text XC, D RO
Priority_Array R RO
Time_Delay R W
Feedback_Value XC, D RO
Notif_Type R W
Profile_Name NS NS
EXCEL Classic to BACnet Property Mapping

The following tables show the supported BACnet object properties for each
EXCEL Classic point type. The table columns are described below.
Column
Description
Name
Readability Shows whether the EXCEL Classic point type supports the read
operation of the given BACnet property. Note that not all property
types are supported in the BACnet server, In addition, some
properties can be read directly from the BACnet server, whereas
others need to be mapped via an XML file.
Each property is flagged R , NS , XM , or XC :
l NS - property is currently not supported with EXCEL Classic point types.
92
Column
Description
Name
default.
l When the value is XC or XM, an additional parameter is included to
show whether a default built-in value is used if the XML property
mapping is not found. This additional value can be D or N .
mapped in the XML.
l N - indicated that there are no default values for this property if there is
no XML mapping.
Writability Shows whether the EXCEL Classic point type supports the mapping
of a write operation of the given BACnet property. Note that all
property types are not supported in the BACnet server.
Each property is flagged W , RO , NS , XM , or XC :

l NS - property is currently not supported with EXCEL Classic point types.
default.
AI AP AZ- Analog Input Mapping (Excel Classic to

BACnet)
Object_Name R RO
Object_Type R RO
93
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Update_Interval XC, N RO
Units XC, D RO
Resolution XC, N RO
Time_Delay R W
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
94
Notif_Type R W
Profile_Name NS NS
AO - Analog Output Mapping (EXCEL Classic to

BACnet)
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Units XC, D RO
Min_Pres_Value XM, N RO
Max_Pres_Value XM, N RO
Resolution XC, N RO
95
Priority_Array R RO
Time_Delay R W
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
Notif_Type R W
Profile_Name NS NS
AV - Analog Value Mapping (EXCEL Classic to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
96
Status_Flags R RO
Event_State R RO
Reliability R RO
Units XC, D RO
Priority_Array R RO
Time_Delay R W
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
Notif_Type R W
Profile_Name NS NS
97
BI - Binary Input Mapping (EXCEL Classic to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Polarity XC, D RO
Time_Delay R W
98
Notif_Type R RO
Profile_Name NS NS
BO - Binary Output Mapping (EXCEL Classic to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Polarity XC, D RO
99
Priority_Array R RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
BV - Binary Value Mapping (EXCEL Classic to BACnet)

Object_Name R RO
Object_Type R RO
100
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Priority_Array R RO
Time_Delay R W
101
Notif_Type R W
Profile_Name NS NS
MI - Multi-State Input Mapping (EXCEL Classic to

BACnet)
Object_ R RO
Identifier
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_ XM2, D X "MI - Multi-State Input Mapping (EXCEL Classic

Service to BACnet)" above, M
Number_Of_ XM, N RO
States
State_Text XC, D RO
102
Time_Delay R W
Notification_ R W
Class
Acked_ R RO
Transitions
Notif_Type R W
Event_Time_ NS NS
Stamps
Profile_Name NS NS
MO - Multi-State Output Mapping (EXCEL Classic to

BACnet)
Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
103
Event_State R RO
Reliability R RO
State_Text XC, D RO
Priority_Array R RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
R7044 to BACnet Property Mapping

The following tables show the supported BACnet object properties for each
R7044 point type. The table columns are described below.
Column
Description
Name
Readability Shows whether the R7044 point type supports the read operation of
the given BACnet property. Note that not all property types are
supported in the BACnet server, In addition, some properties can be
104
Column
Description
Name
read directly from the BACnet server, whereas others need to be

mapped via an XML file.
Each property is flagged R , NS , XM , or XC :
l NS - property is currently not supported with R7044 point types.
default.
l When the value is XC or XM, an additional parameter is included to
show whether a default built-in value is used if the XML property
mapping is not found. This additional value can be D or N .
mapped in the XML.
l N - indicated that there are no default values for this property if there is
no XML mapping.
Writability Shows whether the R7044 point type supports the mapping of a
write operation of the given BACnet property. Note that all property
types are not supported in the BACnet server.
Each property is flagged W , RO , NS , XM , or XC :

l NS - property is currently not supported with R7044 point types.
default.
105
AI AP- Analog Input Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Update_Interval XC, N RO
Units XC, D RO
Resolution XC, N RO
Time_Delay R W
High_Limit XC, D RO
Low_Limit XC, D RO
106
Deadband XC, D RO
Notif_Type R W
Profile_Name NS NS
AO - Analog Output Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Units XC, D RO
107
Min_Pres_Value XM, N RO
Max_Pres_Value XM, N RO
Resolution XC, N RO
Priority_Array R RO
Time_Delay R W
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
Notif_Type R W
Profile_Name NS NS
AV - Analog Value Mapping (R7044 to BACnet)

Object_ R RO
Identifier
Object_Name R RO
Object_Type R RO
108
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Out_Of_ XM2, D XM
Service
Units XC, D RO
Priority_Array R RO
Relinquish_ R RO
Default
COV_ XC, D RO
Increment
Time_Delay R W
Notification_ R W
Class
High_Limit XC, D RO
Low_Limit XC, D RO
Deadband XC, D RO
Acked_ R RO
Transitions
109
Notif_Type R W
Event_Time_ NS NS
Stamps
Profile_Name NS NS
BI - Binary Input Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Polarity XC, D RO
110
Time_Delay R W
Notif_Type R RO
Profile_Name NS NS
BO - Binary Output Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
111
Reliability R RO
Polarity XC, D RO
Priority_Array R RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
112
BV - Binary Value Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
Priority_Array R RO
113
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
MI DP- Multi-State Input Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
Reliability R RO
114
State_Text XC, D RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
MO - Multi-State Output Mapping (R7044 to BACnet)

Object_Name R RO
Object_Type R RO
Description R RO
Status_Flags R RO
Event_State R RO
115
Reliability R RO
State_Text XC, D RO
Priority_Array R RO
Time_Delay R W
Notif_Type R W
Profile_Name NS NS
XML Parameter Tag and Default Values

Property XML Tag Default Value
Device_Type <DeviceType> -
Reliability <Reliability> -
Out_Of_Service <Mode> Automatic

mode
Event_Enable <EventEnable> 0
Present_Value <PresentValue> -
116
Update_Interval <UpdateInterval> -
Units <Units> UNIT_NO_

UNITS
Min_Pres_Value <MinPresValue> -
Max_Pres_Value <MaxPresValue> -
Resolution <Resolution> -
COV_Increment <CovIncrement> 0
High_Limit <HighLimit> 0
Low_Limit <LowLimit> 0
Deadband <Deadband> 0
Limit_Enable <LimitEnable> 0
Polarity <Polarity> POLARITY_

NORMAL
State_Text <StateText> NULL
Change_Of_State_Time(1) <ChangeOfStateTime> -
Change_Of_State_Count(1) <ChangeOfStateCount> -
Time_Of_State_Count_Reset(1) <TimeOfStateCountReset> -
Elapsed_Active_Time(1) <ElapsedActiveTime> -
Time_Of_Active_Time_Reset(1) <TimeOfActiveTimeReset> -
Minimum_Off_Time(1) <MinimumOffTime> -
Minimum_On_Time(1) <MinimumOnTime> -
Alarm_Values <AlarmValue> NULL
Feedback_Value <FeedbackValue> 0
Number_Of_States <NumberOfStates> -
117
Fault_Values <FaultValues> NULL
Notes from table
n (1) - This property can be mapped to XML tags but is currently not
supported in BACnet server.
BACnet Server settings

Following are the properties associated with a BACnet Server:
ATTENTION: Point Object Defaults are used when creating new

objects. Changing these settings will have no influence on existing
objects. If you want the changes to apply to all objects, existing
objects will have to be deleted and reloaded after Point Object
Default settings have been changed.
Device Object Defaults
Object instance Device Object Instance number. This may be changed if there is
a duplicate device object instance in the system or you need to
have a specific device object instance. Default is the system
number, which can be identified on your license.
Object name Placeholder for additional text to expand or clarify the BACnet
device. Default is an empty text string.
Location Name of the computer where the BACnet Server resides. Default
is the computer name.
Point Object Defaults
Event enable Three flags that separately enable and disable reporting of TO-
OFFNORMAL, TO-FAULT, and TO-NORMAL events. Default is
for all checkboxes to be selected.
Time delay Minimum period of time (in seconds) that Present_Value

remains in alarm before a TO-OFFNORMAL event is generated
or remains not in alarm before a TO-NORMAL event is
generated. Default is 5 seconds.
118
Notification class The notification class used when handling and generating event
notifications for this object. Default is 1.
Notify type Indicates whether the notifications generated by the object

should be Events or Alarms. Default is Alarms.
System Parameters
Time Checkbox enabling BACnet Server to accept Time

synchronization synchronization messages from devices on the network.
enabled
Time The difference (in seconds) that must occur between local time
synchronization and Time synchronization before local time is updated. Default
deadband is 0.
Maximum Maximum number of notifications which are allowed to queue

number of in the BACnet Server. Default is 0.
notifications
allowed to queue
Time from Maximum time (in seconds) which a change of value (COV) is
current time of allowed in the queue. Default is 5216.
oldest
notification to
remain in queue
Default ProcessID Default process identifier which is used for broadcasting

for broadcast notifications. Default is 0.
notifications
BACnet client Not used.

write property
priority (1 high,
16 low)
119
120
CHAPTER
4 TESTING COMMUNICATIONS WITH
A BACNET DEVICE
The BACnet test utility, bactst, can be used to test communications between
EBI and a BACnet controller. Only the Cimetrics BACstac software needs
to be installed to run bactst.
Before testing ensure that:
n BACnet controllers (or a BACnet gateway such as the BACnet Server)

is running and have BACnet objects defined.
n The network connection of interest is active, and that the BACstac
software is configured to run on the network.
To run the utility:

2. Type bactst and press ENTER.
Follow the directions as prompted.
Example: To initialize bactst for

communications:
1. Type whois to determine the BACnet Server devices available on the
network.
2. If more than one device is visible, select a device to test. Type
choose n , where n is the “Device Index” number of the device that
was printed as a result of the 'whois' request.
3. Do a read property request of an object.
For example, to read the Present Value property (property
identifier=85) of an analog input object (object type=0) with instance
number 1000, type readp 0 1000 85.
121
Notices
NOTICES
Honeywell Trademarks
IdentiPoint® is a U.S. registered trademark of Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries.
BACnet® is a registered trademark of the American Society of Heating,
Refrigerating and Air-Conditioning Engineers.
Other brands or trademarks are trademarks of their respective owners.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a
software defect or weakness that can be exploited to reduce the operational
or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting
Honeywell products and services.
To report a potential security vulnerability against any Honeywell product,
please follow the instructions at:
https://www.honeywell.com/en-us/product-security.
Support
For technical assistance, contact your nearest Honeywell office.
Training classes
Honeywell holds technical training classes on Enterprise Buildings
Integrator. These classes are taught by experts in the field of building
control systems. For more information about these classes, contact your
Honeywell representative.
122

BACnet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BACnet

Uploaded by

Copyright:

Available Formats

BACnet Interface Reference

Point Naming Conventions 28

Using the BACnet Server 47

AI AP- Analog Input Mapping (R7044 to BACnet) 106

Standard object types

BACnet object types and supported interfaces

BACnet object Supports intrinsic Supported in BACnet Supported in

Multi state input Y Y Y

BACnet object Supports intrinsic Supported in BACnet Supported in

Multi state value Y Y

Life safety point Y Y

Life safety zone Y Y

BACnet object Supports intrinsic Supported in BACnet Supported in

Alarms and events

Command, Group, and Schedule objects

Other documentation for BACnet

n BACnet - A Data Communication Protocol for Building Automation and

n Current versions of BACnet Protocol Implementation Conformance

Choosing the BACnet interface to use

n BACnet Direct Client Interface, a point server interface

TIP: The BACnet Client Interface is no longer supported in EBI

BACnet Direct Client interface

ATTENTION: If BACnet Server is licensed, BACnet Direct Client

other BACnet clients.

Setting up BACstac software

n A regular BACnet/IP port. This is used to communicate to a single

To add a BACnet/IP port

Setting up BACnet Ethernet

To set the network number of a BACnet/Ethernet port:

Protocol Implementation Conformance

ASHRAE American Society of Heating, Refrigeration, and Air-Conditioning

BACnet Building Automation and Control Network. A protocol standard

BACnet Network of computers that obey the BACnet protocol standard

BACnet An abstract data structure used to represent information on the

BACnet Application Layer services used to manage communication over the

COV Change of Value.

Object A 22-bit number identifying the instance of an object within a

Periodic A defined regular interval in which the server database acquires

PICS Protocol Implementation Conformance Statement. A document that

2 BACNET DIRECT CLIENT

BACnet Direct architecture

Remote point server within a redundant system

n Each remote BACnet Direct Point Server communicates to the current

Local point server on a redundant system

n Each local point server, regardless of whether it is running on the

Defining a BACnet Point Server in Station

n The BACnet Point Server service is running.

To define the point server:

ATTENTION: It is not recommended that you select Allow online

5. On the Location Mapping tab, click to call up the Location Browser

TIP: It may take up to 30 seconds before it is apparent that

BACnet Point Server Configuration tab properties

When defining a local BACnet point server on a redundant

TIP: The use of this option is not recommended, as online

Defining the BACnet point server using the

To define settings for the BACnet point server

n Use one of Quick Builder's wizards. This is the recommended technique

Discovering Points Using Quick Builder

n Extracting information from a ComfortPoint Studio project

n Searching the BACnet network using either the WhoIs or WhoHas

n Extracting information from an EDE template (an Excel spreadsheet or

To import points using the CARE/XL Toolkit Import

2. Choose Tools > QB CARE/XL Toolkit Import Wizard.

TIP: If the wizard is not available, make it available by selecting