Siemens Bacnet

BACnet Client & Server
for Insight
Getting Started Manual

571-225
Rev. 1, 11/99
Copyright Notice for Documentation

Information in this document is subject to change without notice. Companies, names, and
data used in examples herein are fictitious unless otherwise noted. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for
any purpose, without the express written permission of Siemens Building Technologies, Inc.
All software described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.
Copyright 1999 by Siemens Building Technologies, Inc.
Credits
Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated.
APOGEE is a trademark and Insight is a registered trademark of Siemens Building
Technologies, Inc.
BACnet is a trademark of the American Society of Heating, Refrigerating and AirConditioning Engineers, Inc.
BACstac is a trademark of Cimetrics, Inc.
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox.
LonTalk is a trademark of Echelon Corporation.
Windows NT is a registered trademark of Microsoft Corporation.
For additional information, contact your nearest Siemens representative.
Printed in U.S.A.
Table of Contents
Table of Contents
How to Use This Manual ......................................................................................... 5
Organization of the Manual ................................................................................................ 5
Conventions Used in This Manual ..................................................................................... 6
Symbols Used in This Manual............................................................................................ 6
Getting Help ....................................................................................................................... 7
ANSI/ASHRAE Standard 135-1995............................................................................ 7
Insight Help System ..................................................................................................... 7
Insight Release Notes ................................................................................................... 7
Where To Send Comments ................................................................................................. 7
Chapter 1 Welcome to the BACnet Client & Server Option for Insight ............ 9
What Is BACnet and the BACnet Option? ......................................................................... 9
BACnet Client Features ............................................................................................... 9
BACnet Server Features............................................................................................. 10
Network Configurations............................................................................................. 11
How BACnet Works .................................................................................................. 14
Before You Begin ............................................................................................................. 23
System Requirements ....................................................................................................... 24
Installation Options........................................................................................................... 24
Chapter 2 Installing and Setting Up the BACnet Option ................................. 25
Installing Insight ............................................................................................................... 25
Installing and Setting Up the Cimetrics BACstac Protocol .............................................. 25
Removing Unwanted Bindings .................................................................................. 27
Setting Up the Network Type..................................................................................... 28
Running the LocalNet Configuration Utility .................................................................... 40
Whats Next?..................................................................................................................... 41
Chapter 3 BACnet Server in Insight.................................................................. 43
Siemens Building Technologies, Inc.
iii
Table of Contents
Creating User Accounts for BACnet.................................................................................43

Windows NT...............................................................................................................43
Insight .........................................................................................................................45
Adding an Access Group...................................................................................................46
Changing Access Levels ...................................................................................................46
Exporting Points................................................................................................................48
Sending Alarms to BACnet Devices.................................................................................50
Commanding APOGEE Points .........................................................................................54
Chapter 4 BACnet Client in Insight....................................................................55
Defining BACnet Building Level Networks .....................................................................55
Defining BACnet Field Panels..........................................................................................58
Uploading Points ...............................................................................................................62
Registering Insight to Receive Alarms..............................................................................63
Commanding BACnet Points ............................................................................................65
Editing BACnet Points ......................................................................................................68
Chapter 5 Troubleshooting ................................................................................69
Glossary .................................................................................................................71
Index .......................................................................................................................79
iv
How to Use This Manual

The BACnet Client & Server for Insight Getting Started Manual contains detailed
information about using the BACnet Client & Server option software. This section
covers manual organization, documentation conventions and symbols, and
instructions for finding additional help.
Organization of the Manual

The BACnet Client & Server for Insight Getting Started Manual consists of the
following five chapters:
Chapter 1 Introduction
Contains a brief explanation of BACnet and its features, installation prerequisites,
system requirements, installation options, and directions for finding additional
information.
Chapter 2 Installing and Setting Up the BACnet Option
Provides step-by-step instructions for installing the BACnet option and configuring
network types.
Chapter 3 BACnet Server in Insight
Walks you through creating BACnet user accounts, exporting points from Insight to a
BACnet network, and sending alarms from Insight to BACnet devices.
Chapter 4 BACnet Client in Insight
Guides you through defining BACnet BLNs and field panels, uploading BACnet
points, registering for BACnet alarms in Insight, and commanding BACnet points.
Chapter 5 Troubleshooting
Provides solutions to the BACnet problems you are most likely to face.
Conventions Used in This Manual

The following table lists additional conventions designed to help you use Insight
Getting Started.
Convention
Example
Numbered Lists (1,2,3) indicate

a procedure with sequential steps.
From the Trend menu, click Copy Definition.

Select the Trend Definition window where you want
to place the copied information.
Actions that you should perform

are specified in boldface type.
Type F for Field panels.

Click OK to save changes and close the dialog box.
Error and system messages are

displayed in Courier New
font.
The message Report Definition

successfully renamed appears in the status
bar.
Angle brackets <placeholder>

indicate text that can vary based
on your selection.
If you select Hours, Days, Weeks or Months from the

Time Period list, specify a parameter in the # of
<units> box.
Names of menus, menu

commands, dialog boxes, buttons,
tabs, and fields are all initial
capped.
View menu
Critical Alarm Selection dialog box
Alarm History button
Symbols Used in This Manual

The following symbol is used to draw your attention to important information.
Symbol
Meaning
CAUTION:
Indicates that equipment damage or loss of data may occur if the user
does not follow a procedure as specified.
Getting Help
You can find additional information about BACnet in the following documents:
ANSI/ASHRAE Standard 135-1995

Standard 135-1995 is available through the ASHRAE bookstore at www.ashrae.org.
For general information about BACnet, visit www.bacnet.org.
Insight Help System

Information about the BACnet option has been incorporated into the online help
system that is automatically installed with Insight. You can access main (crossapplication) or application-specific online help by using the following methods:
Main Help
From the Insight Main Menu, click the Help icon

to activate the Online
Documentation Screen. From there, you can access Insights Main Help system.
Application-Specific Help
From the Help menu within an Insight application, click Help Topics to view the
help contents for the application.
From windows or menu commands, press F1 or click the Help button.
Insight Release Notes

The Release Notes describe system features, last-minute enhancements, and issues
related to BACnet and other Insight options and applications. The Notes are available
as a PDF file in the root directory of the Insight installation CD. To view the PDF
file, you will need a copy of Adobe Acrobat Reader.
Where To Send Comments

Your feedback is important to us, so if you have comments about this manual, please
submit them to apogee.swtechcomm@sbt.siemens.com.
Chapter 1 Welcome to the BACnet Client & Server Option for Insight
Chapter 1 Welcome to the BACnet Client

& Server Option for Insight
Welcome to the BACnet Client & Server for Insight Getting Started Manual (571225). Please read this manual before you install the BACnet option.
This manual contains installation and setup information for the BACnet for Insight
option only. For complete Insight installation instructions, see the Insight Getting
Started Manual (571-041).
What Is BACnet and the BACnet Option?

BACnet is a data communication protocol for building automation and control
networks (ANSI/ASHRAE Standard 135-1995) that allows building automation
equipment from multiple manufacturers to work together as a coherent system.
The BACnet option is a software add-on to Insight designed to provide
communication with BACnet networks. The option allows you to monitor and
command points from either an Insight workstation or a third-party BACnet
workstation.
The BACnet software consists of two parts, the client and the server, which can exist
on a separate or the same workstation. Together, the software components are called
the BACnet Client and Server Option for Insight. A BACnet Client is any Insight that
has a BACnet network assigned to it. A BACnet Server is any Insight connected to a
P2 BLN that has points exported to a BACnet network.
BACnet Client Features

The BACnet Client software is implemented as a new protocol stack and includes the
ability to:
Import existing physical BACnet networks, devices, and points into the Insight
database.
Support an unlimited number of BACnet networks.
Make BACnet networks look like BLNs and BACnet devices look like field
panels in Insight.
Function as a router so that APOGEE and pre-APOGEE1 field panels can access
points residing in BACnet devices.
Monitor and report the status and present value of points residing in BACnet
devices.
Register for COVs and receive COVs from BACnet devices.
Plot dynamic point values.
Command the present value and the out of service status of BACnet points.
Receive and acknowledge alarms originating from BACnet devices.
BACnet Server Features

The BACnet Server software is implemented as an NT service and includes the
ability to:
Let you select the points that are exported to a BACnet network.
Represent APOGEE and pre-APOGEE field panels as BACnet devices on

BACnet networks.
Represent points residing in APOGEE and pre-APOGEE field panels as BACnet

points accessible on BACnet networks.
Allow BACnet devices to read the present value, the status, and other attributes
of points residing in APOGEE and pre-APOGEE field panels.
Let BACnet devices register for COVs with and receive COVs from APOGEE
and pre-APOGEE field panels.
Allow BACnet devices to command the present value and priority of

commandable points in APOGEE and pre-APOGEE field panels.
Allow Insight to send standard alarms to and receive alarm acknowledgements

from BACnet devices.
Let BACnet devices register themselves to receive alarms from an Insight

workstation.
APOGEE field panels refer to panels operating Firmware Revision 2.0 and higher. Pre-APOGEE field
panels refer to panels operating Firmware Revision 1.5 and lower, and 12.x and lower.
10
Network Configurations
The BACnet Option for Insight supports communication with BACnet devices over
Ethernet or TCP/IP. The following three network configurations (Figures 1 through
3) are supported.
Figure 1 shows a dedicated BLN, an MLN, and a BACnet BLN on separate networks
connected to Insight. The Insight workstation contains two network interface cards
one for connection with the BACnet BLN, the other for connection with the MLN.
INSIGHT
WORKSTATION
INSIGHT
WITH
TM
BACnet OPTION
ETHERNET
ETHERNET or BACnet TM / IP
Trunk Interface II
Power
DTR
TX
PMD
RX
TI-II
FLN
LED 8
7
FLN
MBC
DI1 12
DI2 34
DI4 78
AO9
C
DO25 NO
NC
C
DO26 NO
NC
C
DO27 NO
NC
C
DO28 NO
NC
C
DO29 NO
NC
C
DO30 NO
NC
C
DO31 NO
NC
C
DO32 NO
NC
9
10 DI5
11
12 DI5
13
14 DI5
15
16 DI5
17 +
18 -
25 +
AO13 26
-
27 +
19 + AO14 28 AO10 20
29 +
21 + AO15 30 AO11 22
31 +
23 + AO16 32 AO12 24
-
49
50
51
52
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
LED 9
LED 6
3
10 11 12 13 14 15 16
BACnet TM BLN
TX
TEC
DI3 56
APIN0024R1
RX
LED 7
LED 2 LED 3
TX
LED 4
MBC
LED 5
DEDICATED P2 BLN (RS-485)
THIRD PARTY
TM
BACnet
WORKSTATION
BACnet
TM
BACnet
TM
BACnet TM
DEVICE
BACnet TM
DEVICE
UC
53
54
55 + 24 V
56
SHIELD
AI17
AI18
AI19
AI20
33 +
34 35 +
36 37 +
38 39 +
40 -
AI21
AI22
AI23
AI24
41 +
42 43 +
44 45 +
46 47 +
48 STATUS
MODEM
BLN
TX
BATT
EXP
TX
BLN
RX
EXP
RX
MEC
Figure 1. Insight with a Dedicated BLN, an MLN, and a BACnet BLN

on Separate Networks.
11
Figure 2 shows a dedicated building-level network (BLN) connected to Insight. The

BACnet BLN is assigned to the same Insight because it is the Insight with the
BACnet option. The MLN and BACnet BLN share the Ethernet.
INSIGHT
WORKSTATION
INSIGHT
WITH
TM
BACnet OPTION
ETHERNET
Trunk Interface II
Power
DTR
TX
PMD
RX
TI-II
FLN
LED 8
7
FLN
MBC
C
DO25 NO
NC
C
DO26 NO
NC
C
DO27 NO
NC
C
DO28 NO
NC
C
DO29 NO
NC
C
DO30 NO
NC
C
DO31 NO
NC
C
DO32 NO
NC
9
10 DI5
11
12 DI5
13
14 DI5
15
16 DI5
DI1 12
DI2 34
DI3 56
DI4 78
17 +
18 -
25 +
AO13 26
-
27 +
19 + AO14 28 AO10 20
29 +
21 + AO15 30 AO11 22
31 +
23 + AO16 32 AO12 24
-
49
50
51
52
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
LED 9
LED 7
5
10 11 12 13 14 15 16
BACnet TM BLN
TX
TEC
AO9
APIN0023R1
RX
LED 6
LED 2 LED 3
TX
LED 4
MBC
LED 5
DEDICATED P2 BLN (RS-485)
THIRD PARTY
TM
BACnet
WORKSTATION
BACnet
TM
BACnet
TM
BACnet TM
DEVICE
BACnet TM
DEVICE
UC
53
54
55 + 24 V
56
SHIELD
AI17
AI18
AI19
AI20
33 +
34 35 +
36 37 +
38 39 +
40 -
AI21
AI22
AI23
AI24
41 +
42 43 +
44 45 +
46 47 +
48 STATUS
MODEM
BLN
TX
BATT
EXP
TX
BLN
RX
EXP
RX
MEC
Figure 2. Insight with a Dedicated BLN and a BACnet BLN.
12
Figure 3 shows an APOGEE Ethernet Microserver (AEM) connecting a remote P2

BLN to the Ethernet. The AEM can be assigned to either Insight. The BACnet BLN
is assigned to the Insight with the BACnet option. The MLN and BACnet BLN share
the Ethernet.
INSIGHT
WORKSTATION
INSIGHT
WITH
TM
BACnet OPTION
ETHERNET
ETHERNET
APOGEE
ETHERNET
MICROSERVER
THIRD PARTY
TM
BACnet
WORKSTATION
REMOTE P2 BLN (RS-485)
FLN
LED 8
7
FLN
MBC
DI4 78
AO9
C
DO25 NO
NC
C
DO26 NO
NC
C
DO27 NO
NC
C
DO28 NO
NC
C
DO29 NO
NC
C
DO30 NO
NC
C
DO31 NO
NC
C
DO32 NO
NC
9
10 DI5
11
12 DI5
13
14 DI5
15
16 DI5
DI1 12
DI2 34
17 +
18 -
25 +
AO13 26
-
27 +
AO14 28
19 +
AO10 20
29 +
AO15 30
21 +
AO11 22
31 +
23 + AO16 32 AO12 24
-
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
LED 9
LED 7
LED 6
3
10 11 12 13 14 15 16
BACnet TM BLN
TX
TEC
DI3 56
APIN0033R1
RX
LED 5
LED 2 LED 3
TX
LED 4
MBC
BACnet
TM
BACnet
TM
BACnet TM
DEVICE
BACnet TM
DEVICE
UC
53
54
55 + 24 V
56
49
50
51
52
SHIELD
AI17
AI18
AI19
AI20
33 +
34 35 +
36 37 +
38 39 +
40 -
AI21
AI22
AI23
AI24
41 +
42 43 +
44 45 +
46 47 +
48 STATUS
MODEM
BLN
TX
BATT
EXP
TX
BLN
RX
EXP
RX
MEC
Figure 3. Insight with a Remote AEM BLN and a BACnet BLN.
13
How BACnet Works

Like most building control systems, BACnet groups devices into networks. Within
BACnet, these networks can be the same or different physical wire. BACnet uses
hardware devices called routers to connect these different networks into a larger
network, called a BACnet internetwork.
Insight with the BACnet option acts as a router and connects to a BACnet
internetwork using Cimetrics' BACstac software.
Figure 4 shows two Insights with the BACnet option participating in a BACnet
internetwork. The routers in this scenario allow connection between two Insight P2
networks (30 and 40), an Ethernet network (1), and BACnet network 20.
The sample internetwork in Figure 4 is comprised of both physical and virtual
networks. A virtual network is a logical grouping of devices that is assigned a unique
network number. In Figure 4, networks 20, 30, and 40 are considered virtual
networks. Assigning a virtual network number on an Insight workstation with
BACnet option allows you to identify APOGEE and/or pre-APOGEE field panels on
the BACnet internetwork.
The physical network, network 1 in Figure 4, connects the routers together to form
the internetwork. Insight workstations with BACnet option must use the same
physical network number as other routers connected to the same network segment.
Otherwise, the workstation will not be able to communicate across the internetwork.
14
BACnet NETWORK 40
(VIRTUAL)
FP
Insight
w/ BACnet
P2 BLN
FP
FP
BACnet NETWORK 30
(VIRTUAL)
FP
FP
P2 BLN
FP
PHYSICAL NETWORK NUMBERS

AT THE ROUTERS MUST
option
Insight
w/ BACnet
option
MATCH ACROSS THE NETWORK

CIMETRICS
SOFTWARE
40
30
CIMETRICS
SOFTWARE
ETHERNET
BACnet NETWORK 1
(PHYSICAL)
1
ROUTER
APIN0034R2
20
BACnet
BACnet
Device
Device
BACnet
BACnet NETWORK 20
Device
(VIRTUAL)
Figure 4. A Sample BACnet Internetwork Using Ethernet.
15
BACnet BLNs
When viewed in Insights System Profile application, BACnet physical and virtual
networks appear as yellow BLNs. BACnet Devices appear as yellow field panels on
those BLNs. If a BACnet network contains more than 100 devices, multiple Insight
BLNs map to one BACnet network.
This means that when you import a BACnet network containing more than 100
devices, you need to create an additional BLN for each additional 100 devices and
then assign the additional BLN the same BACnet network number you used for the
first BLN.
Among other things, Figure 5 shows an example of how 105 BACnet devices display
in System Profile (using system names) across two BLNs. BACnet_20 represents the
first 100 devices on network 20, while BACnet_20_Two represents the remaining
five devices on network 20.
Insight workstations with the BACnet option, and third-party BACnet workstations
residing on the physical network (see BACnet_1), are considered BACnet devices,
so they also appear as yellow field panels in Insight. This allows you to see
workstations connected to the network, as well as their device names and instance
numbers. The local Insight workstation with the BACnet Client appears as a standard
Insight icon only.
16
Local Insight workstation with

the BACnet Client installed.
Insight Workstations (with the

BACnet Client software) and
third-party BACnet devices on
network 1.
BLN name with network no.

(100 nodes).
BLN name with network no. and
descriptor showing continuation
of network 20 (BACnet_20).
BACnet devices with node

number and device name.
Dedicated BLN.
Figure 5. Example of BACnet Networks in System Profile.
17
BACnet Objects
In BACnet, objects represent physical things such as inputs and outputs, and nonphysical things such as software and software processes.
BACnet defines 18 standard object types, shown in the following table.
Standard BACnet Object Types
Binary Input
Multi-State Input
File
Binary Output
Multi-State Output
Program
Binary Value
Loop
Schedule
Analog Input
Calendar
Group
Analog Output
Notification Class
Event Enrollment
Analog Value
Command
Device
Only Binary Input, Binary Output, Binary Value, Analog Input, Analog Output,
Analog Value, Multi-State Output, Notification Class, and Device objects are used by
the Insight BACnet Option.
Object Identifiers
In BACnet, each object has an Object ID that distinguishes it from other objects in a
device. The Object ID includes the objects typesuch as a Device, an Analog Input,
or a Notification Classand its instance number. The instance number distinguishes
an object from other objects of the same type within a device.
For Device objects, the Object ID is unique within the BACnet system. For all other
objects (such as an Analog Output), the Object ID is unique within its device only.
The Object ID is used as part of the System Name when BACnet objects are
imported into APOGEE.
BACnet Devices Viewed in Insight

When BACnet device objects are imported into Insight, Insight assigns a System
Name to them. The System Name includes the prefix BACDev, which stands for
BACnet Device, and the devices BACnet Instance Number.
For example, Insight will assign a System Name of BACDev_2084 to a BACnet
device object with Instance Number 2084.
18
BACnet Points
Even though the BACnet standard never uses the term BACnet points, in this manual
the term is used to refer to BACnet objects that map to APOGEE points.
Points Imported from BACnet

Points imported from BACnet to Insight are mapped to the following equivalent
APOGEE point types.
BACnet Point Type
APOGEE Point Type
AI (Analog Input)
LAI (physical)
AO (Analog Output)
LAO (virtual)
AV (Analog Value)
LAO (virtual)
BI (Binary Input)
LDI (physical)
BO (Binary Output)
LDO (virtual)
BV (Binary Value)
LDO (virtual)
MI (Multi-State Input)
LENUM
MO (Multi-State Output)
LENUM
EE (Event Enrollment)
LENUM
When BACnet points are imported into Insight, Insight creates both a System Name
and a Name.
APOGEE System Names
The APOGEE System Name for a BACnet point is comprised of the prefix BAC,
followed by the Instance Number of the device that the point resides in, and finally
the points Object ID.
The following example shows the APOGEE System Name for three imported
BACnet Analog Outputs associated with BACnet device 2084:
BAC_2084_AO_3
BAC_2084_AO_18
BAC_2084_AO_5
19
APOGEE Names
If you use APOGEE Names, instead of APOGEE System Names, Insight attempts to
use the Name properties of the BACnet device and the point. If the point mapping
leads to names longer than thirty characters, Insight truncates the name as follows:
For this example, the
BACnet Name property of the BACnet device is Building7Floor2
BACnet Name property of the BACnet point is SetpointRoomTemperature
Instance Number of the BACnet device is 2084
Object ID of the BACnet point is AO 16
When creating the APOGEE Name, Insight first attempts to use the BACnet Name of
both the device and point:
Building7Floor2_SetpointRoomTemperature (39 characters)
If the created name is longer than 30 characters, Insight attempts to use the prefix
BAC and the devices Instance Number in place of the devices BACnet name:
BAC_2084_SetpointRoomTemperature (32 characters)
If the created name is still longer than 30 characters, Insight will use the prefix BAC,
plus the devices Instance Number and the points Object ID as the APOGEE Name:
BAC_2084_AO_16
Points Exported from Insight

The main difference between imported and exported points is that when you export
similar point types from the same field panel, Insight assigns unique Object IDs
starting at one for each object type. So, if you export three physical LAIs and three
physical LDIs, Insight maps them as BACnet Analog Inputs one through three and
BACnet Binary Inputs one through three, as shown in the following example:
Analog Input 1
Analog Input 2
Analog Input 3
Binary Input 1
Binary Input 2
Binary Input 3
20
Points exported from Insight to BACnet are mapped to the following equivalent
BACnet point types.
Insight Point Type
BACnet Point Type
LAI (virtual)
AV (Analog Value)
LAI (physical)
AI (Analog Input)
LAO (virtual)
AV (Analog Value)
LAO (physical)
AO (Analog Output)
LDI (virtual)
BV (Binary Value)
LDI (physical)
BI (Binary Input)
LDO (virtual)
BV (Binary Value)
LDO (physical)
BO (Binary Output)
L2SL (virtual)
BV (Binary Value)
L2SL (physical)
BO (Binary Output)
L2SP (virtual)
BV (Binary Value)
L2SP (physical)
BO (Binary Output)
LFSSL
LFSSP
LOOAL
LOOAP
LPACI (virtual)
AV (Analog Value)
LPACI (physical)
AO (Analog Output)
LENUM
21
Mapping of BACnet Properties

The following table shows the mapping between BACnet Properties and APOGEE
Point Attributes.
BACnet Object
Property
APOGEE Point
Attribute
Used by BACnet
Objects
Example
Object_Identifier
System Name
(encoded)
All
BAC_2000_AO_7
Object_Name
Name
All
Bldg 5_SetPoint5
Object_Type
All
AO
Present_Value
Current Value
All except EE
68
Description (optional)
Descriptor
All
Setpoint for Building 5
Status_Flags
Status
All except EE
Normal
Out_Of_Service
Out_Of_Service
All except EE
FALSE
Polarity
Inverted
BI, BO, BV
TRUE
Units
Engineering Units
AI, AO, AV
Deg F
Inactive_Text (optional)
StateTextTable
BI, BO, BV
ON
Active_Text (optional)
StateTextTable
BI, BO, BV
OFF
State_Text
StateTextTable
MI, MO
Mode 1
Priority_Array
Command Priority
AO, AV, BO, BV, MO
Operator
COV_Increment3
COV Limit
AO, AI, AV
High_Limit
High Limit
AO, AI, AV
Low_Limit
Low Limit
AO, AI, AV
Reliability
Fail or
Out_Of_Service
No Fault Detected
22
The Object_Type is reflected in the System Name.
Used only if an object supports COV reporting.
Before You Begin

Make sure that you have met the following prerequisites before you install the
BACnet option:
For Ethernet and BACnet/IP Networks
Have a copy of the Insight Getting Started Manual (571-041) available.
Review the Installation Options section in this chapter.
Select an appropriate starting number (First Device Instance No.) for the field
panels you plan to export. You will need to know the device instance numbers of
all other devices already on the BACnet network. See the How BACnet Works
section in this chapter and the Exporting Points section in Chapter 3 for
additional information.
If you plan to add networks and devices to an existing (already online) BACnet
internetwork, make sure that you use unique Network Numbers and Device
Instance Numbers. See the How BACnet Works section in this chapter for
additional information.
For Insights with the BACnet Client software, assign the same physical network
number as other routers connected to the same network segment. See the How
BACnet Works section in this chapter for additional information.
If you plan to send alarms from APOGEE and/or pre-APOGEE field panels to
BACnet devices, you will need the Process ID and either the Device Instance
Number or the MAC address and network number of those devices. Typically,
the Process ID is 0. However, to ensure that you have the correct value, you
should obtain the Process ID from the vendor you are integrating with.
Additional Prerequisites for BACnet/IP Networks Only

Work with the Network Administrator to obtain a list of IP addresses that you
can use to identify Insight workstations as BACnet Broadcast Management
Devices on BACnet/IP networks. See the Setting Up the Network Type section in
Chapter 2 for additional information.
Work with the Network Administrator to obtain an IP address that you can use to
identify Insight as a Foreign Device on a BACnet/IP network. See the Setting Up
the Network Type section in Chapter 2 for additional information.
23
System Requirements
An Insight workstation with the BACnet option has the same system requirements as
an Insight workstation without the BACnet option. See the Insight Getting Started
Manual (571-041) for specific hardware requirements.
Installation Options
The BACnet Client & Server option for Insight can be installed only with Insight
Revision 3.2 or higher.
NOTE:
24
To communicate with each other, all Insight workstations on a

Management Level Network (MLN) must be at the same revision level.
Chapter 2 Installing and Setting Up the

BACnet Option
Before using the BACnet option with Insight, you need to complete several tasks,
including:
Installing Insight and the BACnet Client & Server Option
Installing and setting up the Cimetrics BACstac protocol stack
Running the LocalNet Configuration Utility
Installing Insight
To install Insight and the BACnet Client and Server Option, see the Insight Getting
Started Manual (571-041).
NOTE:
After you install Insight, you do not need to immediately restart the
computer. You can first install the BACstac protocol, set up the BACnet
network type, and then restart the computer.
Installing and Setting Up the Cimetrics BACstac

Protocol
The BACstac protocol is available for installation only if you selected the BACnet
Client & Server option when you installed Insight. If you purchased the BACnet
option and did not select the BACnet Client & Server option, you must return to the
Insight setup program and select the BACnet option before you can continue with the
steps in this section.
You must install the BACstac protocol on every Insight workstation that will serve as
either a BACnet Client or a BACnet Server.
To install the BACstac protocol, complete the following steps:
1. Log on to Windows NT using an account with Administrator privileges.
2. From the Windows NT Taskbar, click Start, select Settings, then click Control
Panel.
3. Double-click the Network applet.
4. Click the Protocols tab.
25
5. Click Add, and then Have Disk.

6. Type the path to the Bacstac.exe file, typically C:\Insight\BACstac, where C:
represents the letter of the local hard drive.
7. Select BACstac Protocol, and then click OK to install the stack.
The Cimetrics BACstac Gateway v3.0 Properties dialog box displays with
default values.
NOTE:
If you uninstall Insight, you must manually remove the BACstac protocol
from the workstation before you reinstall Insight.
To remove the BACstac protocol, complete the following steps:

2. From the Windows NT Taskbar, click Start, select Settings, then click Control
Panel.
5. Select BACstac Protocol, and then click Remove.
6. Click Yes in the Warning message box.
7. Click Close, and then restart the computer.
26
Removing Unwanted Bindings

NOTE:
If your workstation has only one network interface card, skip this section.
The BACstac protocol automatically binds to all network interface cards (adapters)
installed in the Insight workstation, but will use only one adapter for BACnet
communication. Therefore, you need to remove the bindings from all adapters,
except for the adapter that will communicate with the BACnet network.
To remove bindings, complete the following steps:
1. From the Windows NT Taskbar, click Start, select Settings, and then click
Control Panel.
3. Click the Bindings tab.
4. From the Show Bindings for list, select all protocols.
5. Expand the BACstac Protocol to show adapters currently bound to it.
6. Disable any adapter that should not be used for BACnet communication by
selecting an adapter, and then clicking Disable.
27
Setting Up the Network Type

An Insight with the BACnet option supports both physical and virtual networks.
Physical networks include Ethernet and BACnet/IP. A virtual network is a logical
grouping of devices associated with a router that you assign a unique network
number to. Where Insight functions as a router, the virtual network number identifies
APOGEE and/or pre-APOGEE field panels on the BACnet network.
Setting up virtual networks and joining Ethernet networks involves assigning port
and network numbers to Insight so that it functions properly as a router on a specific
network. Setting up a BACnet/IP network also involves assigning port and network
numbers, plus an IP address.
Use the following guidelines to help you determine the appropriate setup for your
installation.
Physical Networks
Choose either Ethernet or BACnet/IP
Set up Insight on an Ethernet network when Insight will communicate with

other devices that support the Ethernet protocol. For steps on setting up Insight
on a BACnet Ethernet network, see the Setting Up Insight on a BACnet Ethernet
Network section in this chapter.
Set up Insight on a BACnet/IP network when Insight will communicate with

devices that support only the BACnet/IP protocolfor instance, on a wide area
network (WAN). A BACnet/IP network is a collection of one or more IP
subnetworks (IP domains) that you assign a single, unique BACnet network
number to. For steps on setting up Insight on a BACnet/IP network, see the
Setting Up Insight on a BACnet/IP Network section in this chapter.
Virtual Networks
In addition to setting up Insight on a physical network, set up Insight on a Virtual
network if Insight will function as a BACnet Server. For steps on setting up Insight
on a virtual network, see the Setting Up Insight on a Virtual Network section in this
chapter.
28
Setting Up Insight on a BACnet Ethernet Network

Setting up Insight on a BACnet Ethernet network is fairly straightforward.
To set up Insight on a BACnet Ethernet network, complete the following steps:
1. Log into Windows NT using an account with Administrator privileges.
Control Panel.
5. Select BACstac Protocol, and then click Properties.
The Cimetrics BACstac Gateway v3.0 Properties dialog box displays with
default values.
6. Highlight the first entry in the dialog box, and then click Edit.
The Ethernet Port Properties dialog box displays.
29
7. Complete the fields in the Ethernet Port Properties dialog box.
Port ID. Enter an identification number between 1 and 255. You can use any
number not used in the Cimetrics BACstac Gateway v3.0 Properties dialog
box.
Network Number. Accept the default, or if another number is assigned to

the physical network, enter it instead. This is the same physical network
number used by other BACnet routers on the same network segment (see
Figure 6).
BACnet NETWORK 40
(VIRTUAL)
FP
Insight
w/ BACnet
P2 BLN
FP
FP
BACnet NETWORK 30
(VIRTUAL)
FP
FP
P2 BLN
FP
PHYSICAL NETWORK NUMBERS

AT THE ROUTERS MUST
option
Insight
w/ BACnet
option
MATCH ACROSS THE NETWORK

CIMETRICS
SOFTWARE
40
30
CIMETRICS
SOFTWARE
ETHERNET
BACnet NETWORK 1
(PHYSICAL)
1
ROUTER
APIN0034R2
20
BACnet
BACnet
Device
Device
BACnet
BACnet NETWORK 20
Device
(VIRTUAL)
Figure 6. Using the Same Physical Network Numbers at the Routers.
Network Interface Card. Leave Default selected.
Attached. Leave this box checked. It specifies that the router port is
accessible to other devices on the BACnet network.
8. Click OK twice, and then click Close. Do not restart the computer until you have
set up your virtual BACnet networks.
30
Setting Up Insight on a BACnet/IP Network

You can set up Insight to function on a Standard BACnet/IP network, or to function
as a BACnet Broadcast Management Device (BBMD) or as a Foreign Device.
Use the following guidelines to help you determine the appropriate setup for your
installation:
Standard BACnet/IP Networks
Set up Insight to function on a Standard BACnet/IP network if Insight will not span
IP routers and will not support connections from BACnet/IP Foreign Devices. A
Standard BACnet/IP network consists of BACnet devices on a single IP subnet. See
Figure 7.
IP SUBNET
LAN
BACnet / IP
NETWORK 70
(PHYSICAL)
Insight
w/ BACnet
Option
BACnet
Device
BACnet
Device
P2 BLN
(VIRTUAL BACnet NETWORK)
APIN0040R1
FP
FP
FP
Figure 7. Insight on a Standard BACnet/IP Network.
31
BBMDs
Many IP routers prevent broadcast messages from being transmitted across a WAN.
The BACnet protocol uses broadcast messages called Who-Is and I-Am to interrogate
the network and determine what other BACnet devices exist. For these broadcast
messages to be transmitted across IP routers that block such messages, one device on
each subnet must be set up as a BBMD (an auxiliary router).
Set up only one BBMD for each IP subnet, and set up the Broadcast Distribution
Table with the IP addresses of all other BBMDs that you want the Insight to connect
to. Each Insight that acts as a BBMD for a subnet requires a fixed IP address.
A BBMD can send broadcasts to another subnet or directly to another BBMD.
Sending broadcasts to a subnet is called One-Hop Forwarding. Sending broadcasts to
another BBMD is called Two-Hop Forwarding. If you want to use the Two-HopForwarding feature of BACnet/IP networks, you need to set up at least two BACnet
devices as BBMDs, each on different IP subnets. Two-hop forwarding allows
messages blocked by IP routers to be sent to another BBMD, which will then
transmit the message to the network. See Figure 8.
IP SUBNET 1
BACnet / IP
NETWORK 70
IP ROUTER
WAN
LAN
BACnet
Device
Insight as BBMD
BACnet
Device
IP SUBNET 2
LAN
BACnet / IP
NETWORK 70
IP ROUTER
BACnet
Device
Insight as BBMD
APIN0041R1
FP
BACnet
Device
FP
FP
Figure 8. Insight Functioning as BBMDs.
32
Foreign Devices
Set up Insight to function as a Foreign Device if Insight needs to communicate with
BACnet devices on a different subnet, but not route messages between them, or if the
Insight does not have a fixed IP address.
A Foreign Device is an Insight that has a different IP subnet address from the IP
subnet addresses comprising the BACnet/IP network that the Insight wants to
communicate with. Foreign Devices can communicate directly with any other device
on the network, but must register with a BBMD to receive broadcasts from devices
on other IP subnets. See Figure 9.
IP SUBNET 1
LAN
BACnet / IP
NETWORK 70
IP ROUTER
BACnet
Device
Insight as BBMD
BACnet
Device
IP SUBNET 2
LAN
BACnet / IP
NETWORK 70
IP ROUTER
BACnet
Device
WAN
Insight as BBMD
FP
BACnet
Device
FP
FP
APIN0042R1
IP SUBNET 3
LAN
BACnet / IP
NETWORK 70
IP ROUTER
Insight as
FOREIGN DEVICE
Figure 9. Insight Functioning as a Foreign Device.
33
To set up Insight to function on a Standard BACnet/IP network, complete the

following steps:
Control Panel.
The Cimetrics BACstac Gateway v3.0 Properties dialog box displays.
6. Click Add, and then select BACnet/IP.

The BACnet/IP Port Properties dialog box displays.
34
7. Complete the fields in the Port tab.
Port ID. Enter an identification number between 1 and 255. You can use any
number not used in the Cimetrics BACstac Gateway v3.0 Properties dialog
box.
Network Number. Enter the physical network number where this Insight
will reside. For example, in Figure 10, the network number is 70.
IP Address. Either accept the default or enter another IP address.
UDP Port. Accept the default number of 47808.
Subnet Mask. Enter the value used in the TCP/IP Properties dialog box.
(The following path leads to the dialog box: Start\Settings\Control
Panel\Network\Protocols\TCP/IP\Properties)
Attached. Leave this box checked. It specifies that the port is accessible.
35
Complete the following steps only if you are setting up Insight to function as a
BBMD:
1. Complete steps 1 through 7 (except for the IP Address, UDP Port, and Subnet
Mask fields in step 7) for the Standard BACnet/IP network.
2. Click the BBMD tab.
3. Complete the fields in the BBMD tab.
36
BACnet Broadcast Management Device. Check this box.
Two-Hop Forwarding. Check this box to enable two-hop forwarding of

network messages.
IP Address. Enter the IP addresses for all other BBMDs on the network.
(The following path leads to the IP addresses: Start\Settings\Control
UDP Port. Enter the standard BACnet UDP port number: 47808.
Subnet Mask. For each BBMD this Insight connects to, enter the value used
in the TCP/IP Properties dialog box. (The following path leads to the subnet
mask: Start\Settings\Control
Add Button. Click this button to add the IP address, the UDP port, and the
subnet mask to the Broadcast Distribution Table.
Remove Button. Click this button to remove a selected entry from the
Broadcast Distribution Table.
Enable. Check this box to enable the BBMD to handle foreign device
registration.
Max FDT Entries. Enter the maximum number of entries you want in the
Foreign Device Table.
Complete the following steps only if you are setting up Insight to function as a
Foreign Device:
1. Complete steps 1 throught 7 (except for the IP Address, UDP Port, and Subnet
Mask fields in step 7) for the Standard BACnet/IP network.
2. Click the Foreign Device tab.
Complete the fields in the Foreign Device tab.
Foreign Device. Check this box.
37
Permanent. This box is checked by default. Because the Foreign Device is

set up as a permanent connection, it will try to re-register with the BBMD if
the value you enter in the Time To Live field expires.
Remote BBMD Section

IP Address. Enter the IP address of the remote BBMD that the Foreign
Device will register with.
UDP Port. Accept the default value of 47808.
Time To Live. Enter the number of seconds you want the Foreign Device to
wait before it tries to re-register with the BBMD. For a permanent
connection, leave 0 as the default.
Setting Up Insight on a Virtual BACnet Network

You need to set up a virtual network on every Insight workstation that will be a
BACnet Server.
To set up a virtual network, complete the following steps:
Control Panel.
The Cimetrics BACstac Gateway v3.0 Properties dialog box displays.
38
6. Select the Virtual network type, and then click Edit.

The Virtual Port Properties dialog box displays.
7. Complete the fields in the Virtual Port Properties dialog box.
Port ID. Displays 2 by default. Do not modify this number.
Network Number. Enter the number assigned to this network. The number
must be a network number not already used by the BACnet internetwork.
Attached. Leave this box checked to specify that the port is accessible.
8. Click OK twice, click Close, and then restart the computer.
39
Running the LocalNet Configuration Utility

You must run the LocalNet Configuration Utility to make sure the BACnet Client
and BACnet Server option are properly set up.
To run the LocalNet Configuration Utility, complete the following steps:
1. From the Windows NT Taskbar, click Start, select Programs, Insight Version
3, and then click LocalNet Configuration Utility.
The LocalNet Configuration Utility dialog box displays.
2. Click Configure for BACnet Client or Configure for BACnet Server, or both.
3. Click Close.
40
Whats Next?
Once you have finished installing and setting up the BACnet option, your next step is
to set up your workstation with the BACnet Client or Server functionality, or both, by
completing the tasks in the BACnet Server in Insight and BACnet Client in Insight
chapters of this manual.
41
42

The primary purpose of the BACnet Server is to allow BACnet devices and thirdparty BACnet workstations on a BACnet network to access points residing in
APOGEE and pre-APOGEE field panels. However, before you can take full
advantage of the BACnet Server functionality, you need to complete the following
tasks:
Create BACnet user accounts in Windows NT and in Insight
Add access groups
Change access levels for an access group
Export Points
Set up APOGEE and pre-APOGEE field panels to send alarms to BACnet

devices
Creating User Accounts for BACnet

You need to create an NT and an Insight account for BACnet. The NT account will
allow users to log on to the workstation, while the Insight account will allow you to
export Insight points to a BACnet system.
Windows NT
Keep in mind the following considerations for NT accounts:
Before you can create any new NT accounts on a stand-alone Insight

workstation, you must be logged on to NT using an account that has
Administrator privileges.
Before you can create any new NT accounts on an MLN setup, you must be
logged on to NT using an account that has Domain Administrator privileges.
Furthermore, you must add these accounts from the NT Server on the Domain. If
you do not have Domain Administrator privileges on an MLN setup on a
corporate network, you will need to work with the Network Administrator.
43
To create a Windows NT user account for BACnet, complete the following steps:
1. Do one of the following:
For a stand-alone Insight workstation: From the Windows NT Taskbar, click

Start, select Programs, Administrative Tools, and then click User
Manager.
For an MLN setup: From the Windows NT Taskbar, click Start, select
Programs, Administrative Tools, and then click User Manager for
Domains.
2. From the User menu, click New User.

The New User dialog box displays.
3. In the Username field, type BACnet.

4. Complete the remaining fields. Click Help if you need information about the
fields.
5. Click OK or Add to create the user account.
6. Close the User Manager or User Manager for Domains window.
44
Insight
To create an Insight account for BACnet, complete the following steps:
1. From the Insight Main menu, click User Accounts
The User Accounts window displays with the Insight Account tab active by
default.
2. From the Account menu, select New, and then click Insight Account.
The Add Insight Account dialog box displays.
3. Complete the fields in the Add Insight Account dialog box.
Domain. Click the drop-down arrow and select the domain you want to add
the account to.
User Name. Click the drop-down arrow and select BACnet.
Full Name. Insight automatically adds BACnet as the default in this field if
you selected BACnet in the User Name field.
Initials. Enter one to three character to identify the userfor example, BAC.
Default Graphic. To associate a graphic name to the BACnet account for

use in the Graphics application, click the Object Selector , and then select
a graphic name.
Display. If you want the user to see the System Name of objects, click
System Name. If you want the user to see the Name of objects, click Name.
45
Language. Displays a users default log on language.
Security. Click According to Access Level defined for Access Groups.
4. Click OK.
Insight adds the new user account, and the account information displays in the
Insight Account tab.
Adding an Access Group

After you create an Insight account for BACnet, you can also add an access group for
BACnet, although it is not required. The BACnet group is where you will add Insight
points so that you can export them to the BACnet network.
To add an access group for BACnet, complete the following steps:
1. In the User Accounts application, click the Access Groups tab.
2. In the Access Groups section, click Add.
The Add Access Group dialog box displays.
3. Type the name of the new access groupfor example, BACnet Export.
4. Click OK.
Insight adds the new access group, and the information displays in the Access
Groups tab.
Changing Access Levels

You can change access levels for the BACnet access group you just created, as well
as for the various Insight applications. For the BACnet Export access group, you
need to assign users a privilege of Read Only or higher.
46
To change the access level for the BACnet access group, complete the following
steps:
1. In the User Accounts application, click the Insight Account tab.
2. From the list of accounts, select BACnet.
3. From the list of access groups, select the BACnet group you created in Step 3 of
the Adding an Access Group section.
4. From the Edit menu, click Access Level.
The Access Level dialog box displays.
5. Click the Privilege drop-down arrow, and then select an access level of Read
Only or higher.
6. Click OK.
The new access level displays next to the access group.
47
Exporting Points
Before you export points from Insight, make sure that you have selected an
appropriate starting device instance number. This ensures that the device instance
numbers generated for exported field panels will not conflict with existing device
instance numbers on the BACnet network. To select an appropriate starting device
instance number, you will need to know the instance numbers of all other devices
already on the BACnet network.
Each APOGEE and/or pre-APOGEE field panel on a BACnet network is
automatically assigned a unique device instance number determined by the following
formula:
First Device Instance No. + (200 x Trunk Sequence No.) + Node No.
The First Device Instance No. is the starting point for points exported from Insight.
The Trunk Sequence Number is the number of a BLN in a series of BLNs containing
exported devices. Trunk Sequence Numbers begin with 0. So, the first of five BLNs
would have a Trunk Sequence Number of 0, while the fifth of five BLNs would have
a Trunk Sequence Number of 4.
Example 1
First Device Instance No. = 2000
Trunk Sequence Number = 0
Node Number = 5
Device Instance Number = 2000 + (200 x 0) + 5 = 2005
Example 2
Node Number = 18
Example 3
Node number = 47
48
When you export points from an APOGEE and/or pre-APOGEE field panel, two
things happen:
Insight automatically creates a Notification Class object for the field panel so that
the panel can send alarms and alarm acknowledgements to a user-defined list of
devices on the BACnet network. For additional information, see the Sending
Alarms to BACnet Devices section in this chapter.
Insight exports the points as BACnet points (objects) to make them available to a
BACnet system for commanding and monitoring. (For additional information
about BACnet points, see the How BACnet Works section in Chapter 1, and the
Commanding BACnet Points section in Chapter 4.)
NOTE:
You need to run BACnet Export whenever you add, delete, or change the
point type for any exported point.
To export points to the BACnet network, complete the following steps:

1. In the User Accounts application, click the Access Groups tab.
2. From the list of access groups, select BACnet Export.
3. In the Group Members section, click Add to open the Object Selector.
4. Select the objects you want added to the access group.
5. Click OK.
Insight adds the objects to the access group, and displays the information in the
Object Name field.
6. Click the Insight Account tab.
7. Click the Account menu, and then click BACnet Export.
The BACnet Export dialog box displays.
49
8. In the First Device Instance No. field, enter the First Device Instance Number.
9. Click Export, and then OK. Restart the computer.
10. To save information about exported points to a comma-separated value file that
can be imported into Excel, reopen the BACnet Export dialog box, then click
CSV File.
Sending Alarms to BACnet Devices

When you exported points from an APOGEE and/or pre-APOGEE field panel,
Insight automatically created a notification class object for the panel so that it could,
with some minor additional set up, send alarms to a user-defined list of recipients
(devices) on the BACnet network.
NOTE:
You can export only standard alarms to BACnet. You cannot use enhanced
alarms.
To set up an APOGEE or pre-APOGEE field panel to send alarms to BACnet

devices, complete the following steps:
1. From the Insight Main menu, click System Profile
In the system tree, click the APOGEE or pre-APOGEE field panel that will
send alarms to BACnet devices. From the Tools menu, click Notification
Class.
Right-click the APOGEE or pre-APOGEE field panel that will send alarms
to BACnet devices, and then click Notification Class.
NOTE:
The Notification Class command applies only to APOGEE and/or

APOGEE field panels that have points exported to the BACnet system.
The Notification Class dialog box displays.
50
3. Complete the fields in the Notification Class dialog box.
Instance. Displays 1 as the default.
Name. Leave NC object as the default.
Description. Enter text that provides additional information about this field
panel. For example, MBC_1.
Acknowledge Required for Section. Allows the panel sending the alarms to
require acknowledgement from devices on the recipient list for various alarm
states: TO-OFFNORMAL (signifies an alarm condition), TO-FAULT
(signifies a device malfunction), and TO-NORMAL (signifies normal
operation).
Priority Section. Allows you to set the priority of the alarm states. Alarm
priorities rank from the highest, 0, to the lowest, 255. To set the priority, type
a number or use the up-down arrows to set the number.
Recipient List Section. Allows you to add, edit, or delete BACnet devices
that the field panel sends alarms to. To add a device to the list, click Add.
The BACnet Destination dialog box displays.
51
4. Complete the fields in the BACnet Destination dialog box.
52
Recipient Section. Allows you to enter either the Instance number or the
MAC address and network number of the BACnet device you want to send
alarms to.
To enter an Instance number, click Instance, and then type the device
instance number.
To enter a MAC address, click MAC, and then click either

Hexadecimal or Decimal. Type the address and network number.
Recipient Process Section. Identifies an application inside a BACnet device.

In the Process ID field, enter the Process ID of the application in the BACnet
device you are sending alarms to. Typically, the value is 0. However, to
ensure that you have the correct value, you should obtain the Process ID
from the vendor you are integrating with.
Notifications Section. Allows a device to issue confirmed alarm

notifications, which means that the device sending the alarm requires a
response from the device receiving the alarm. To issue confirmed
notifications, leave the Issue Confirmed Notifications box checked.
Transitions Section. Allows you to select alarm transitions (TOOFFNORMAL, TO-FAULT, or TO-NORMAL) for a device.
Valid Days Section. Allows you to define the days of the week that a device
will receive alarms.
Period Section. Defines a window of time that a device will receive alarms.
Check the From or To boxes, or both, to set the duration, then enter the time
or use the up-down arrows to set the time. If you do not define a period of
time, the device will receive alarms 24 hours a day, as indicated in the
Duration field.
5. Click OK.
Insight adds the device to the Recipient List in the Notification Class dialog box.
53
Commanding APOGEE Points

If you command APOGEE points from a BACnet workstation, you can expect
standard BACnet behavior from those points. However, if you command APOGEE
points from an Insight workstation, the priority array is cleared, and all pending
commands are removed. As a result, the priority array will contain 0 entries if the
APOGEE Priority is NONE, and only 1 entry in all other cases. The mapping in the
following table applies.
NOTE:
Insight priority PDL is executed at BACnet priority 16, EMERGENCY at

7, SMOKE at 4, and OPERATOR at 1.
BACnet Priority Level
BACnet Priority
Insight Priority
Manual Life Safety
OPERATOR
Automatic Life Safety
SMOKE
Available
SMOKE
Available
SMOKE
Critical Equipment Control
EMERGENCY
Minimum On/Off
EMERGENCY
Available
EMERGENCY
Manual Operator
PDL
Available
PDL
10
Available
PDL
11
Available
PDL
12
Available
PDL
13
Available
PDL
14
Available
PDL
15
Available
PDL
Available
PDL
NULL
NONE
16
1
NULL
1. NULL means that there is no command associated with the points Present Value
property. In this case, the Present Value equals the Relinquish Default.
54

The primary purpose of BACnet Client software is to allow Insight to access points
residing in BACnet devices on BACnet networks. However, before you can take full
advantage of BACnet Client functionality and start monitoring and commanding
points, you need to complete the following tasks:
Define BACnet BLNs
Define BACnet field panels
Upload points
Register Insight to receive alarms from BACnet devices
Defining BACnet Building Level Networks

You need to define one or more BACnet BLNs if you want to view online BACnet
devices on the BACnet internetwork.
To define a BACnet building level network, complete the following steps:
to the Insight you want to

From the Devices toolbar, drag the BLN icon
add the BACnet BLN to, and then release the mouse button.
In the system tree, click the Insight you want to add the BACnet BLN to.
From the Device menu, select Insert, and then click Building Level
Network (BLN).
Right-click the Insight icon you want to add the BACnet BLN to, select
Insert, and then click Building Level Network (BLN).
The Building-Level Network Definition dialog box displays.
55
3. Complete the fields in the Building-Level Network Definition dialog box.
System Name. Enter the system name using a maximum of 30 characters,

upper and lowercase letters, numbers, periods, and spaces.
NOTE: You cannot change the system name after you have added the BLN
to the system tree.
Name. Use the system name or enter a name using a maximum of 30

characters, upper and lowercase letters, numbers, periods, and spaces. You
can change the name after you have added the BLN to the system tree.
Descriptor. Enter text that provides additional information about the BLN
using a maximum of 30 characters, upper and lowercase letters, numbers,
periods, and spaces.
Type. Click the drop-down arrow, and then select BACnet.
Settings Button. Click the Settings button.
The BACnet Connection Settings dialog box displays.
56
4. In the Network No. field, enter the BACnet network number that this BLN will
reside on.
5. The BACnet Client represents this Insight as a BACnet device on the BACnet
network. In the Insight Instance No. field, enter an instance number for this
Insight that will uniquely identify it on the BACnet network.
6. Click OK.
The BACnet Network Number displays in the Current Settings field.
7. Click OK to close the Building-Level Network Definition dialog box.
Insight adds the BACnet BLN to your workstation, and a BLN icon displays in
the system tree.
NOTE:
If you are importing a BACnet network containing more than 100

devices, you need to create an additional BLN for each additional 100
devices, then assign the additional BLN the same network number
used for the first BLN. For additional information, see the How
BACnet Works section in Chapter 1.
8. If this is the first time the BLN has been defined, you must restart Insight on
all other Insight workstations on the network to get the BACnet devices to
appear in the system tree at this workstation.
57
Defining BACnet Field Panels

NOTE:
Manually defining BACnet field panels is optional. The standard method

of defining BACnet field panels is to create one or more BACnet BLNs in
System Profile, then let Insight detect and add online devices.
To manually define a BACnet field panel on a BACnet BLN, complete the

following steps:
From the Devices toolbar, drag the field panel icon

to the BLN icon
you want to add the field panel to, and then release the mouse button.
In the system tree, click the BLN you want to add the field panel to. From the
Device menu, select Insert, and then click Field Panel.
Right-click the BLN icon you want to add the field panel to, select Insert,
and then click Field Panel.
The BACnet Field Panel Definition dialog box displays.
58
3. Complete the fields in the BACnet Field Panel Definition dialog box.
Device Instance. Enter the instance number for the BACnet device. As you
enter the number, Insight automatically adds the device instance number to
the system name and simultaneously adds the system name and device
instance number to the name field. The Device Instance number will also
become part of the field panel name that displays in the system tree. For
example, if you enter 2032 as the Device Instance number, BACDev_2032,
along with the panels node number, will display in the system tree.
NOTE: You cannot change the device instance number after you have
added the field panel to the system tree. If you want the field panel
to reflect a different device instance number, you must first delete
the panel, and then add a new one.
System Name. Displays the default system name, BACDev_. Insight

modifies this field to reflect the number you enter in the Device Instance
field.
59
NOTE: You cannot change the system name after you have added the field
panel to the system tree. If you want the field panel to have a
different system name, you must first delete the panel, then add a
new one.
Name. Leave this field blank. As you enter a number in the Device Instance
field, Insight automatically enters the following in the Name field:
BACDev_xxx, where xxx is the Device Instance number.
NOTE: You can change the name after you complete the Device Instance
field or after you have added the field panel to the system tree.
Descriptor. Leave this field blank. Once Insight and the BACnet field panel
start communicating, Insight automatically detects and adds the descriptor to
this field.
Panel Type. Displays BACnet as the default.
Vendor Name. Leave this field blank. Once Insight and the BACnet field
panel start communicating, Insight automatically detects and adds the vendor
name to this field.
Model Name. Leave this field blank. Once Insight and the BACnet field
panel start communicating, Insight automatically detects and adds the model
name to this field.
Application SW Rev. Leave this field blank. Once Insight and the BACnet
field panel start communicating, Insight automatically detects and adds the
application software revision string to this field.
Firmware Rev. Leave this field blank. Once Insight and the BACnet field
panel start communicating, Insight automatically detects and adds the
firmware revision string to this field.
Node Number. Enter a node number from 1 through 100 to establish the
field panels identification address on the BACnet BLN.
MAC Address Section. Allows you to enter the Media Access Control
address of the device on the network.
If the device is capable of sending I-Am broadcasts, leave the fields in this
section blank. (An I-Am broadcast tells other devices on a BACnet network
that the sending device exists. The PICS of the vendor you are integrating
with will state the devices capability for sending I-Am broadcasts.) Once
Insight and the BACnet device start communicating, Insight automatically
60
detects and adds the MAC address to this section.

If the device is not capable of sending I-Am broadcasts, you must specify a
MAC address.
To enter the MAC address in decimal format, click the Decimal button,
then enter the address. The address in decimal form must use the
numbers 0 through 255, separated by points, in aaa.bbb.ccc.ddd format.
For example, 125.97.0.0 is a valid address using the decimal form, as is
199.
To enter the MAC address in hexadecimal format, click the

Hexadecimal button, then enter the address. The address in
hexadecimal form must use an even number of 2 to 12 alphanumeric
characters, including 0 through 9, and A through F as either upper or
lower case letters. For example, a50307567d4E is a valid address using
the hexadecimal form, as is 88.
Status Section. Fields in this section are blank and inactive. However, once
Insight and the BACnet device start communicating, Insight detects the status
and displays a check in the On-line box, and Ready and OK in the status
fields.
4. Click OK.
Insight adds the BACnet field panel to your system, and a BACnet field panel icon
displays in the system tree.
61
Uploading Points
Once you have imported (defined) BACnet networks and devices, you need to upload
BACnet points so that you can monitor and command them in Insight.
To upload points from a BACnet device into the Insight database, complete the
following steps:
1. From the Insight Main menu, click Database Transfer
2. In the System Overview section of the Database Transfer window, highlight the
BACnet network or device whose points you want to upload, and then click Add.
BACnet
Devices
Selected
BACnet
Device
3. Click Upload All
, and then OK.
Insight begins the upload and displays the results of the transfer in the Transfer
Operations and Transfer Diagnostics sections.
62
Registering Insight to Receive Alarms

Before Insight can receive alarms from BACnet devices, it must first add itself as an
alarm recipient to the devices notification classes. A notification class is a group of
devices that receive alarms and alarm acknowledgements.
An Insight workstation with the BACnet option supports registering and
unregistering alarms for an individual BACnet device or for all BACnet devices on a
BACnet BLN.
Registering for alarms on a device will add the Insight to all notification classes on
the device. Unregistering for alarms on a device will remove the Insight from all
notification classes on the device.
Registering for alarms on a BACnet BLN will add the Insight to all notification
classes on all devices on the BLN. Unregistering for alarms on a BACnet BLN will
remove the Insight from all notification classes on all devices on the BLN.
NOTE: 1. All alarms in BACnet appear as Priority 3 in Insight.
2. BACnet supports standard alarming only.
To register Insight to receive alarms, complete the following steps:
In the system tree, click the BACnet device or BACnet BLN that will register
Insight. From the Tools menu, click Register Alarms.
Right-click the BACnet device or BACnet BLN that will register Insight, and
then click Register Alarms.
If you clicked Register Alarms for a device, Insight displays a message box
similar to the following:
63
If you clicked Register Alarms for a BLN, Insight displays a message box similar
to the following:
3. Click OK.
64
Commanding BACnet Points

Commanding BACnet points is similar in most aspects to commanding Insight
points. You can command BACnet points using the Point Commander, Global
Commander, and Graphics applications. For a list of equivalent Insight and BACnet
point types, see the How BACnet Works section of this manual.
Present Value and Out of Service Properties
If a BACnet device allows you to modify the Present Value (Current Value in
Insight) and Out of Service properties, you can command those properties from an
Insight workstation with the BACnet Client.
Out of Service Points
An Insight workstation will not allow you to command the Current Value property of
APOGEE points that are Out of Service. However, on a BACnet network, a physical
point that is Out of Service is treated as if it were merely disconnected from the
physical input, but still fully functional otherwise. Therefore, you can command Out
of Service BACnet points from an Insight workstation with the BACnet Client. This
principle applies even to physical input points (Binary Input, Analog Input).
Command Priorities
The BACnet protocol specifies 16 priorities, whereas APOGEE specifies 5 priorities.
When you command BACnet points, you will see the standard Insight Command
PrioritiesOPERATOR, SMOKE, EMERGENCY, PDL, and NONE. Insight maps
these priorities internally into BACnet priorities, so you will not be able to view all
16 of the BACnet priorities shown in the following table:
65
BACnet Priority Level
BACnet Priority
Insight Priority
Manual Life Safety
OPERATOR
Automatic Life Safety
SMOKE
Available
SMOKE
Available
SMOKE
Critical Equipment Control
EMERGENCY
Minimum On/Off
EMERGENCY
Available
EMERGENCY
Manual Operator
PDL
Available
PDL
10
Available
PDL
11
Available
PDL
12
Available
PDL
13
Available
PDL
14
Available
PDL
15
Available
PDL
Available
PDL
NULL
NONE
16
1
NULL
1. NULL means that there is no command associated with the points Present Value
property. In this case, the Present Value equals the Relinquish Default.
BACnet Priorities That Do Not Map Directly to Insight

The Point Commander application shows the actual Current Value and the highest
priority with an associated value in the Command Priority Array. If Insight cannot
map the current BACnet priority directly to an Insight priority that is, the BACnet
priority has no direct Insight equivalentInsight displays the next highest, equivalent
Insight priority. For example, if you command a BACnet point that is currently at
priority 12 to PDL, Insight executes the command at priority 8.
Priorities Higher Than or Equal to Current Priorities
When you command a BACnet point to a priority higher than or equal to the point's
current priority, Insight executes the command at the lowest corresponding BACnet
priority. For example, if you command a BACnet point that is currently at priority 10
to EMERGENCY, Insight executes the command at priority 7.
66
Priorities Lower Than Current Priorities

When you command a BACnet point to a priority lower than the points current
priority, Insight performs two tasks. First, it relinquishes (releases) all commands
stored in the Command Priority Array at higher prioritiesbut only for commands
executed from Insight, and not from a third party BACnet workstation or control
program. Second, Insight executes the command at the new priority. For example, if
you command a BACnet point that is currently at priority 5 to NONE, Insight
executes the command to NULL.
Commanding Priority NONE
If you command a point to Insight priority NONE, Insight relinquishes all commands
stored in the Command Priority Array at higher prioritiesbut only for commands
executed from Insight, and not from a third party BACnet workstation or control
program. If no more commands are available in the Command Priority Array, the
point's Present Value will equal the Relinquish Default (NULL).
A Final Note about Commanding
After you command a point, Insight reads the Present Value, Priority Array, and
Status Flags properties so that Insight can display the actual value.
67
Editing BACnet Points

If you change the attributes of BACnet points in Insights Point Editor application,
Insight saves the changes to its database. However, the changes will have no effect in
the BACnet device where the point resides, and could be overridden on an upload.
Editable fieldsfields that an upload will not overrideinclude Graphic Name,
Informational Text, and Access Groups.
Editable Fields
68
This section provides solutions to the problems you are most likely to encounter with
BACnet devices and networks. Find the problem in boldface type that best describes
your problem, then complete the steps that follow.
Which of the following best describes the problem?
You Have Defined a BACnet BLN in System Profile, and No BACnet Devices
Appear in the System Tree
1. Make sure that the Insight GlobalTablesService is running. To open the Services
applet, click Windows NT Taskbar\Start\Settings\Control Panel\Services.
2. In System Profile, disable then enable the BLN.
Exported Points Are Not Showing Up on the BACnet Network
1. Make sure that you have run the LocalNet Configuration Utility and checked the
Configure for BACnet Server checkbox. For instructions on running the utility,
see the Running the LocalNet Configuration Utility section in Chapter 2 of this
manual.
2. Make sure that the Insight BACnetServerSvc is running. To open the Services
3. Make sure that you changed the access level to Read Only or higher for the
BACnet access group in the User Accounts application. See the Changing Access
Levels section in Chapter 3 of this manual.
4. Make sure that exported devices are physically connected to the BLN.
You Are Unable to Import BACnet Devices and Networks
1. Make sure that you have run the LocalNet Configuration Utility and checked the
Configure for BACnet Client checkbox. For instructions on running the utility,
see the Running the LocalNet Configuration Utility section in Chapter 2 of this
manual.
2. Make sure that the Insight BACnetClientSvc is running. To open the Services
69
APOGEE Point Changes from Analog Input to Virtual, but the BACnet Point Still
Shows it as an Analog Input
1. Re-export the point to change its point type.You may have to wait up to two
minutes for Insight to update information.
After editing the notification class using the NC editor, the BACnet device does not
see the changes.
1. Wait up to two minutes for Insight to update information.
2. Make sure that points are exported for the field panel in question.
3. Make sure that the Insight BACnetServerSvc is running. To open the Services
BACnet Device will not connect.
1. Make sure the the MAC address is correct.
2. Make sure the network number is correct.
BACnet Device displays as ostracized.
1. The device is on the wrong network. Move the device to the correct network
Insight is Not receiving alarms from BACnet devices.
1. Make sure that the Insight BACnetClientSvc is running. To open the Services
2. Make sure that Insight is registered to receive alarms.
3. Make sure that the Insight ID has not changes since it was registered to receive
alarms.
70
Glossary
Glossary
A
Adapter
See Network Adapter Card.
APOGEE Field Panel
Refers to panels operating Firmware Revision 2.0 and higher. See also Pre-APOGEE
Field Panel.
ARCNET
Attached Resource Computer Network. A type of LAN that works like a token-ring
network, except that the connections between computers do not need to be in the
shape of a ring. ARCNET networks usually use Ethernet hardware.
B
BACnet
Data communication protocol for Building Automation and Control networks,
ANSI/ASHRAE Standard 135-1995. BACnet allows devices from multiple
manufacturers to work together.
BACnet Broadcast Management Device (BBMD)
Logical device used to propagate broadcasts. Used when a BACnet/IP network will
span IP routers or when you need to support connections from BACnet/IP Foreign
Devices.
BACnet Device
Any physical or virtual device that supports digital communication using the BACnet
protocol.
BACnet Internetwork
Two or more BACnet networks interconnected by routers.
71
Glossary
BACnet/IP
BACnet protocol over the Internet Protocol (IP).
BACnet/IP Network
Collection of one or more IP subnetworks (IP domains) that are assigned a single
BACnet network number.
BACnet Network Number
Unique number assigned to a network segment in a BACnet internetwork.
BACnet Notification Class
BACnet object type. A Notification Class object consists of a list of BACnet device
objects that send or receive alarms and alarm acknowledgements.
BACnet Object ID
32-bit numeric code consisting of a 10-bit Object Typesuch as a Device, an Analog
Input, or a Notification Classand a 22-bit Instance Number. The Object ID
distinguishes an object from other objects within a device.
BACstac
Protocol stack developed by Cimetrics that allows applications to communicate with
systems from multiple vendors across BACnet networks. BACstac implements the
BACnet application, network, and data link layers of the OSI reference model.
BBMD
See BACnet Broadcast Management Device (BBMD).
Bindings
Connections between network cards, protocols, and services on a computer.
BLN
See Building Level Network (BLN).
Building Level Network (BLN)
Communication trunk connecting Insight workstations and field panels in the
building control system. Also known as Protocol 2, P2, or peer-to-peer network.
72
Glossary
D
Data Link Layer
Second layer of the OSI model. Provides data transport service between two directly
connected computers.
Device Instance Number
Instance Number in the Device Object ID. See also BACnet Object ID.
Device Name
Name of a BACnet device in Insight. If you use System Names, BACnet devices
imported into an Insight workstation display with the prefix BACDev_, followed by
the Device Instance Number. Otherwise, Insight displays the Name property of the
device. The Device Name, along with the BACnet Object ID, is a system-wide
device identifier.
DHCP
See Dynamic Host Configuration Protocol (DHCP).
Dynamic Host Configuration Protocol (DHCP)
Protocol for automatic TCP/IP configuration that provides static and dynamic address
allocation and management.
E
Emergency Repair Disk
Floppy disk that contains system settings you can use to repair Windows NT if it
becomes damaged.
Ethernet
Type of protocol developed by the IEEE (802.3) that maps to the Physical layer in
local area networks.
F
FLN
See Floor Level Network (FLN).
73
Glossary
Floor Level Network (FLN)

Communication trunk connecting field panels and FLN devices such as TECs and
UCs.
Foreign Device
BACnet device, typically a workstation, that participates in a network as an end node.
Foreign Devices can communicate with more than one network, but not route
messages between them. Used in wide area networks.
H
Hardware Compatibility List
Microsofts list of supported computers and hardware for Windows operating
systems. Current versions of the list are available at the following internet address:
http://www.microsoft.com/isapi/hwtest/hcl.idc
I
Insight
Software program created by Siemens Building Technologies that provides a
graphical user interface for managing and controlling a building environment.
Insight Instance Number
Number that identifies an Insight workstation on a BACnet network.
M
MAC Address
Media Access Control address, also known as Ethernet address or E-MAC address.
The unique, 12-digit, hexadecimal, physical Ethernet node address contained in a
devices on-board, read-only memory. The address is also located on a small label on
the device. The device can be an adapter card, a router, a serial server, or any other
piece of hardware that connects to the Ethernet.
MBC
See Modular Building Controller (MBC).
74
Glossary
Modular Building Controller (MBC)

Field panel with replaceable Open Processors, and Power, Controller, and Point
Termination Modules.
MEC
See Modular Equipment Controller (MEC).
Modular Equipment Controller (MEC)
Microprocessor-based field panel that supports digital and analog input and output on
the Building Level Network.
MS/TP
Master-Slave/Token-Passing. A type of LAN that uses a bus layout and a tokenpassing scheme. Every computer receives all of the data, but only those addressed
respond. A token that travels the wire determines which computer is able to
broadcast.
N
National Institute of Standards and Technology (NIST)
Operates a lab where manufacturers can test their products for BACnet conformance.
Network Device Interface Specification (NDIS)
Standard that defines an interface for communication between the Media Access
Control sublayer and protocol drivers.
NDIS
See Network Device Interface Specification (NDIS).
Network Adapter Card
An expansion card used to connect a computer to a local area network.
Network Interface Card
Another term for Network Adapter Card.
75
Glossary
Network Layer
Third layer of the OSI model. Allows computers and devices residing on different
networks to communicate.
NIST
See National Institute of Standards and Technology (NIST).
NT service
Executable program that runs in the background on a Windows NT computer.
O
Object ID
System-wide device identifier consisting of a BACnet Object Type and an Instance
Number.
Open Systems Interconnection (OSI) Reference Model
Set of specifications that describe a seven-layered network architecture for
connecting dissimilar devices. Each layer of the model covers different network
activities, equipment, or protocols.
OSI
See Open Systems Interconnection (OSI) reference model.
P
PICS
Protocol Implementation Conformance Statement. Available from building
automation control vendors, a PICS documents such things as supported
conformance class, functional groups, standard application services, standard object
types, data link layer options, character sets, and any special functionality built into
the protocol.
Port ID
Number assigned to a BACnet router for a specific BACnet network.
76
Glossary
Pre-APOGEE Field Panel

Refers to panels operating Firmware Revision 1.5 and lower, and 12.x and lower. See
also APOGEE Field Panel.
Process ID
Numeric value that represents an application inside a BACnet device. Along with
either a Device Instance Number or a MAC address and network number, a Process
ID allows a BACnet device to send alarms to another BACnet device.
Protocol
Standard way of regulating data transmission between computers. Software that
enables computers to exchange information.
Protocol Stack
Combination of protocols. For example, BACstac is a protocol stack, as is TCP/IP.
R
Router
Device used to connect networks using different architectures and protocols. Routers
determine the best path for sending data, and filter broadcast traffic to the local
segment.
S
Site Offset
First number of a range of instance numbers for devices at this site. For example, in
the range of instance numbers 20003000, the Site Offset is 2000.
T
TCP/IP
See Transport Control Protocol/Internet Protocol (TCP/IP).
TEC
See Terminal Equipment Controller (TEC).
77
Glossary
Terminal Equipment Controller (TEC)

Application-specific equipment controller used in pressure-independent Variable Air
Volume (VAV) applications.
Transport Control Protocol/Internet Protocol (TCP/IP)
Wide area network protocol that provides communication across diverse,
interconnected networks.
U
UDP
User Datagram Protocol. Used for internetworking, UDP is a connectionless
transport protocol that facilitates transport of the IP.
Unitary Controller
Programmable, microprocessor-based equipment controller used to coordinate the
activity of mechanical equipment that controls the building control system.
W
Wide Area Network (WAN)
Computer network that uses telecommunications links to connect the networked
computers over long distances.
78
Index
Index
A
adding an access group for BACnet .......46
AEM (APOGEE Ethernet Microserver) 13
alarms
registering Insight to receive ..............63
sending to BACnet devices.................50
unregistering Insight to receive ..........63
application-specific online help ...............7
ARCNET (Attached Resource Computer
Network).............................................71
ASHRAE Standard 135-1995 ..................7
B
BACnet
about .....................................................9
adding an access group for .................46
Broadcast Management Device ..........31
changing access levels for ..................46
client tasks ............................................9
commanding points.............................65
configuring..........................................25
creating user accounts.........................43
defining BLNs ....................................55
defining field panels ...........................58
Device Instance Number ..............23, 48
exporting points to ..............................49
Foreign Device .............................31, 33
how it works .......................................14
installation options..............................24
installation prerequisites .....................23
installing .............................................25
internetwork........................................14
IP network...........................................28
Object Identifier..................................18
option....................................................9
point mapping .....................................19
points.................................................. 19
Process ID .............................. 23, 52, 77
server tasks......................................... 10
setting up ............................................ 25
Trunk Sequence Number.................... 48
uploading points................................. 62
virtual network ................................... 14
what is .................................................. 9
BACnet/IP network ............................... 28
BACstac
installing and configuring .................. 25
Bindings................................................. 27
C
changing access levels ........................... 46
client tasks ............................................... 9
commanding BACnet points.................. 65
configuring the BACnet option ............. 25
configuring the network type................. 28
creating user accounts for BACnet ........ 43
D
defining BACnet BLNs ......................... 55
defining BACnet field panels ................ 58
Device Instance Number.................. 23, 48
DHCP (Dynamic Host Configuration
Protocol)............................................. 73
E
Ethernet network.................................... 28
exporting points ..................................... 49
F
FD (Foreign Device)........................ 31, 33
79
Index
H
Hardware Compatibility List ........... 24, 74
help
application-specific .............................. 7
main...................................................... 7
online.................................................... 7
How BACnet works............................... 14
I
Insight
Getting Started Manual ............ 9, 23, 25
installing............................................. 25
online help system................................ 7
Release Notes ....................................... 7
Insight Getting Started Manual.... 9, 23, 25
Insight Release Notes .............................. 7
installation options for BACnet ............. 24
installation prerequisites ........................ 23
installing and configuring BACstac....... 25
installing Insight .................................... 25
installing the BACnet option ................. 25
internetwork........................................... 14
IP address............................................... 23
IP subnet .................................... 28, 31, 33
L
LocalNet Configuration Utility.............. 40
M
MAC address ....................... 23, 52, 60, 74
main online help ...................................... 7
mapping BACnet points ........................ 19
MS/TP.................................................... 75
N
network configurations .......................... 11
network interface card ........................... 11
80
O
Object Identifier .....................................18
online help system....................................7
P
PICS (Protocol Implementation
Conformance Statement ...............60, 76
points
exporting.............................................49
uploading ............................................62
Process ID ..................................23, 52, 77
R
registering Insight to receive alarms ......63
router ................................................14, 77
Insight .................................................14
running the LocalNet Configuration
Utility..................................................40
S
sending alarms to BACnet devices.........50
server tasks .............................................10
setting up the BACnet option .................25
Site Offset...............................................48
system requirements...............................24
T
Trunk Sequence Number........................48
two-hop forwarding................................36
U
UDP (User Datagram Protocol) .......35, 78
unregistering Insight to receive alarms ..63
uploading points .....................................62
V
virtual network .................................14, 28

Siemens 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

Siemens Bacnet

Uploaded by

Copyright:

Available Formats

BACnet Client & Server

Getting Started Manual

Copyright Notice for Documentation

Creating User Accounts for BACnet.................................................................................43

Siemens Building Technologies, Inc.

How to Use This Manual

How to Use This Manual

Organization of the Manual

Siemens Building Technologies, Inc.

How to Use This Manual

Conventions Used in This Manual

Numbered Lists (1,2,3) indicate

From the Trend menu, click Copy Definition.

Actions that you should perform

Type F for Field panels.

Error and system messages are

The message Report Definition

Angle brackets <placeholder>

If you select Hours, Days, Weeks or Months from the

Names of menus, menu

Symbols Used in This Manual

Siemens Building Technologies, Inc.

How to Use This Manual

ANSI/ASHRAE Standard 135-1995

Insight Help System

From the Insight Main Menu, click the Help icon

From windows or menu commands, press F1 or click the Help button.

Insight Release Notes

Where To Send Comments

Siemens Building Technologies, Inc.

How to Use This Manual

Siemens Building Technologies, Inc.

Chapter 1 Welcome to the BACnet Client

What Is BACnet and the BACnet Option?

BACnet Client Features

Support an unlimited number of BACnet networks.

Siemens Building Technologies, Inc.

Register for COVs and receive COVs from BACnet devices.

Plot dynamic point values.

Receive and acknowledge alarms originating from BACnet devices.

BACnet Server Features

Represent APOGEE and pre-APOGEE field panels as BACnet devices on

Represent points residing in APOGEE and pre-APOGEE field panels as BACnet

Allow BACnet devices to command the present value and priority of

Allow Insight to send standard alarms to and receive alarm acknowledgements

Let BACnet devices register themselves to receive alarms from an Insight

Siemens Building Technologies, Inc.

DEDICATED P2 BLN (RS-485)

Figure 1. Insight with a Dedicated BLN, an MLN, and a BACnet BLN

Siemens Building Technologies, Inc.

Figure 2 shows a dedicated building-level network (BLN) connected to Insight. The

DEDICATED P2 BLN (RS-485)

Figure 2. Insight with a Dedicated BLN and a BACnet BLN.

Siemens Building Technologies, Inc.

Figure 3 shows an APOGEE Ethernet Microserver (AEM) connecting a remote P2

REMOTE P2 BLN (RS-485)

Figure 3. Insight with a Remote AEM BLN and a BACnet BLN.

Siemens Building Technologies, Inc.

How BACnet Works

Siemens Building Technologies, Inc.

PHYSICAL NETWORK NUMBERS

MATCH ACROSS THE NETWORK

Figure 4. A Sample BACnet Internetwork Using Ethernet.

Siemens Building Technologies, Inc.