BACnet Protocol

Advanced Training
Systems Integration Services Europe Training Program
Agenda

 Introduction
 History
 Interoperability
 Objects
 Functions
 Profiles
 Communication
 Devices
 Network Topology

2
Introduction or What is BACnet ?

Building Automation and Control network

BACnet is a registered Trademark of ASHRAE

BACnet is a data transmission protocol for data exchange of devices in the

building management system.

BACnet describes standardized Objects of the Building Automation System

BACnet describes Services for the access of these Objects and their Attributes

3
Introduction or What is BACnet ?

Building Automation and Control network

BACnet is manufacturer independent

BACnet is a “book“, not a Software or Hardware

BACnet is license free i.e. no charges

BACnet supports a lot of network standards and topologies incl. the Internet
protocol (BACnet/IP)

4
BACnet Organisations

ASHRAE (American Society of Heating, Refrigeration

and Air-Conditioning Engineers)

BACnet Interest Group Europe e.V. BIG-EU

BACnet Interest Group North America BIG-NA

BACnet Interest Group Australia-Asia BIG-AA

BACnet Interest Group Middle East BIG-ME

BACnet Manufacturers Association BMA

5
History

Developed by ASHRAE
Development Time: ca. 8-9 Years (1987-1995)
Original standard published in 1995 by
ASHRAE/ANSI as 135-1995
Approved as ISO 16484-5 in 2003
Current standard is 135-2016
No approved Addendums, yet

Affiliated of CEN/TC 247 for Automation- and

Management Level

6
BACnet Levels

• BACnet in the CEN – Level Scheme

Protocol Norm
Management
BACnet EN V 1805-1 Level
EN ISO 16484-5

Automation
BACnet EN ISO 16484-5 Level
Profibus EN V 13321-1, EN 50170
WorldFIP EN V 13321-1, EN 50170
KNXnet EN 50090, CEN EN 13321-1 ISO 14543-3

LON EN V 13154-2 Field

KNX EN 50090, CEN EN 13321-1 ISO 14543-3 Level
Batibus EN V 13154-2
EHS EN V 13154-2
BACnet EN ISO 16484-5

AS-i EN 50295 Actuator

BACnet EN ISO 16484-5 Level

7
BACnet Levels

• BACnet in the JCI Scheme

Management
BACnet M5i, M3i Level
OPC
BACnet IP

Automation
BACnet NxE Level

BACnet FX16 Series, TUC, Modules Field

LON TEC Series Level
N2 System 91
BACnet MSTP

BACnet Romutec Actuator

Level

8
Protocol Levels and their Meaning

• Transport of Data • Interpretation of Data

– Network Layer – Application Layer
– Security Layer • Services
– Physical Layer • Object

BACnet Application Layer Application

BACnet Network Layer Network

IP Data-Link
ISO 8802-2 MS / TP Dial-up PTP
Media access
LonTalk
ETHERNET ARCNET RS 485 RS 232 Physical

BACnet IP BACnet MS/TP

= CEN-Norm

10
Transport Media

Ethernet IP BACnet IP, (Annex J)

Ethernet ISO 8802-3, Ethernet (Clause 7)
ARCNET ASTM 878.1, 2.5 Mb ARCNET (Clause 8)
ARCNET ASTM 878.1, RS-485 ARCNET (Clause 8)
RS485 MS/TP master (Clause 9)
RS485 MS/TP slave (Clause 9)
RS232 Point-To-Point, EIA 232 (Clause 10)
RS232 Point-To-Point, modem, (Clause 10)
LON LonTalk, (Clause 11)

11
BACnet Systems

BACnet Implementations

Company A Company B

Company C

13
BACnet Description Diagram

PICS Protocol Implementation Conformance Statement

Profile defines a set of BACnet services and objects

BIBBs BACnet Interoperability Building Blocks

Services Functions to provide interoperability

Objects Data with a set of properties

Required properties
Optional properties
Proprietary properties

14
Objects

 Every BACnet device holds objects

 Objects are composed of properties

 Properties can be readable or readable and writable

 Certain properties are defined to be required (R)

 Some are required to be writable (W)

 Other properties can be optionally supported (O)

 For particular functions e.g. COV reporting (notification of a change of value)

or intrinsic reporting (notification of alarms or events), certain properties are
respectively required.

15
Objects

All BACnet objects (including the device object or vendor specific objects) support
the following properties:

Object_Identifier 10 Bit Type, 22 Bit Instance 210= 1,024

Number 222= 4,194,304
Object_Name Unique Name
Object_Type 10 Bit Type (List)

 Objects can represent physical inputs or outputs

 BI, BO, AI, AO, Mi, MO
• Objects can represent pseudo / organizational data points
 BV, AV, MV, ….
• Objects can represent a function
 Scheduling, Calendar, Trend, ….
• Device Objects represent the device attributes
 Device

16
Objects

Object Types listed Added after 1995:

• 18 Averaging
• 19 Multistate Value
• 0 Analog Input • 20 Trend-Log
• 1 Analog Output
• 2 Analog Value • 21 Life Safety Point
• 3 Binary Input • 22 Life Safety Zone
• 4 Binary Output Added after 2001:
• 5 Binary Value • 23 Accumulator
• 6 Calendar • 24 Pulse Converter
• 7 Command Added after 2004:
• 8 Device • 25 Event-Log
• 9 Event Enrollment • 26 Global-Group
• 10 File • 27 Trend-Log-Multiple
• 11 Group
• 12 Loop • 28 Load-Control
• 13 Multistate Input • 29 Structured View
• 14 Multistate Output • 30 Access Door
• 15 Notification Class Added after 2008:
• 16 Program • 32 Access Credential
• 17 Schedule • 33 Access Point
• 34 Access Rights
• 35 Access User
• 36 Access Zone
• 37 Credential Data Input

17
Objects

Object Types listed

Added after 2010

• 38 Network Security
• 39 BitString Value
• 40 CharacterString Value
• 41 Date Pattern Value
• 42 Date Value
• 43 DateTime Pattern Value
• 44 DataTime Value
• 45 Integer Value
• 46 Large Analog Value
• 47 OctetString Value
• 48 Positive Integer Value
• 49 Time Pattern Value
• 50 Time Value
• 51 Notification Forwarder
• 52 Alert Enrollment
• 53 Channel
• 54 Lighting Output

18
Objects e.g. Analog Input

Required

Object Identifier
Object Name Optional
Object Type
Present Value Description TimeDelay
Status Flags Device Type Notification Class
Event State Reliability High Limit
Out of Service Update Interval Low Limit
Units Min Value Deadband
Max Value Limit enable
Resolution Event Enable Company-
specific
COV Increment Acked Transitions
Notification Class
Property 1
Property 2
Property N

19
Objects e.g. Analog Output

PROPERTIES CONFORMANCE
CODE
Object_Identifier R
Object_Name R
Object_Type R
Present_Value R
Description O
DeviceType O
Status_Flags R
Event_State R
Reliability O
Out_Of_Service R
Units R
Min_Pres_Value O
Max_Pres_Value O
Resolution O
Priority_Array R
Relinquish_Default R
COV_Increment O
Time_Delay O
Notification_Class O
High_Limit O
Low_Limit O
Deadband O
Limit_Enable O
Event_Enable O
Acked_Transitions O
Notify_Type O

20
Objects e.g. Analog Input

Example: Temperature Sensor

Object_Identifier 0, 4
Object_Name T_ROOM1
required
Object_Type Analog Input
(mandatory)
Present Value 26,5
Units C
... ...

Description 1st Floor East Wing optional

... ...

Serial_Number 334-24-V1-2
company-
... ... specific

21
BIBBs

BIBBs is short for:

BACnet
Interoperability
Building
Blocks

BIBBs allow a significantly more accurate specification of the functions

supported by a device.

BIBBs are part of the current 135-2004 ISO 16484-5:2003 standard

BIBBs are specified for five interoperability areas IOB

22
BIBBs

The five interoperability areas are:

DS: Data Sharing

AE: Alarm / Event Management
SCHED: Scheduling
T: Trending
DM: Device and Network Management

A class “A” device defines a “requestor” of data and functions (client)

A class “B” device defines a “provider” of data and functions (server)

23
BIBBs

BACnet Interoperability Building Blocks

 DS-RP Data Sharing – Read Property
 DS-RPM Data Sharing – Read Property Multiple
 DS-RPC Data Sharing – Read Property Conditional
 DS-WP Data Sharing – Write Property
 DS-WPM Data Sharing – Write Property Multiple
 DS-COV Data Sharing – Change Of Value
 DS-COVP Data Sharing – Change Of Value Property
 DS-COVU Data Sharing – Change Of Value Unsubscribed
 AE-N-I (E) Alarm & Event Notification Internal (External)
 AE-ACK Alarm & Event Acknowledge
 AE-ASUM Alarm & Event Alarm Summary
 AE-ESUM Alarm & Event EventEnrollment Summary
 AE-INFO Alarm & Event Information

24
BIBBs

BACnet Interoperability Building Blocks

 AE-LS Alarm & Event LifeSafety
 SCHED Scheduling
 DM-DDB Device Management – Dynamic Device Binding
 DM-DOB Device Management – Dynamic Object Binding
 DM-TS Device Management – Time Sync
 DM-UTC Device Management – UTC Time Sync
 DM-DCC Device Management – Device Communication Control
 DM-RD Device Management – Reinitialize Device
 DM-BR Device Management – Backup and Restore
 DM-R Device Management – Restart
 DM-LM Device Management – List Manipulation
 DM-OCD Device Management – Object Creation and Deletion
 T-VMT Trending - Viewing and Modifying Trends
 T-ATR Trending – Automated Trend Retrieval

25
BIBBs

BACnet Interoperability Building Blocks

 NM-CE Network Management – Connection Establishment
 NM-RC Network Management – Router Configuration
 DM-BR Device Management – Backup and Restore
 DM-R Device Management – Restart
 DM-LM Device Management – List Manipulation
 DM-OCD Device Management – Object Creation and Deletion
 T-VMT Trending - Viewing and Modifying Trends
 T-ATR Trending – Automated Trend Retrieval

26
BIBBs

NEW BIBBs since 135-2008 Addendum L

 DS-(A)V Data Sharing - (Advanced) View
 DS-(A)M Data Sharing - (Advanced) Modify
 AE-AS Alarm & Event - Alarm Summary View
 AE-(A)VM Alarm & Event - (Advanced) View and Modify
 AE-(A)VN Alarm & Event - (Advanced) View Notifications
 AE-ELV Alarm & Event - Event Log View
 AE-ELVM Alarm & Event - Event Log View and Modify
 AE-EL-I Alarm & Event - Event Log Internal
 AE-NF Alarm & Event – Notification Forwarder
 SCHED-(A)VM Scheduling - (Advanced) View and Modify
 SCHED-WS Scheduling – Weekly Schedule

27
BIBBs

 T-AVM Trending - (Advanced) View and Modify

 T-V Trending - View
 T-A Trending – Archival
 DM-TM Device Management – Text Message
 DM-ADM Device Management – Automatic Device Mapping
 DM-ATS Device Management – Automatic Time Sync
 DM-MTS Device Management – Manual Time Sync
 NS-SD Network Security – Secure Device
 NS-ED Network Security – Encryption Device
 NS-… Network Security – … 5 more (Addendum 2008g)

NEW BIBBs since 135-2010 Addendum AA

 DS-WG Data Sharing - WriteGroup
 DS-WG-I Data Sharing – WriteGroup Internal
 DS-WG-E Data Sharing – WriteGroup External
28
BIBBs

Example ReadProperty (DS-RP-A)

 Service Initiate ReadProperty
Example ReadProperty (DS-RP-B)
 Service Execute ReadProperty

Example COV (DS-COV-A)

 Services Initiate Subscribe COV
 Execute ConfirmedCOV Notification
 Execute UnconfirmedCOV Notification
Example COV (DS-COV-B)
 Services Execute Subscribe COV
 Initiate ConfirmedCOV Notification
 Initiate UnconfirmedCOV Notification

29
Services

Services are for reading, writing, subscribing and monitoring values

The BACnet services cover 5 areas:

1) Data Sharing Services

e.g. ReadProperty, WriteProperty, ReadPropertyMultiple, WritePropertyMultiple,
AtomicReadFile, AtomicWriteFile, SubscribeCOV, UnsubscribeCOV, COVNotification …

2) Alarm and Event Services

e.g. EventNotification, AcknowledgeAlarm, GetAlarmSumary

3) Schedule Services
e.g. ReadProperty, WriteProperty

4) Trending Sevices
e.g. ReadRange, EventNotification

5) Device Management Services

e.g. TimeSynchronization, Who-Is, I-Am, Who-Has, I-Have, ReinitialDevice
VT-Open, VT-Data, VT-Close

30
Profiles

Device profiles are defined in Annex L of the DIN EN ISO 16484−5

 Device profiles define specific BACnet services and objects (BIBBs) that a
device type has to fulfill for a defined interoperability area.

 Enables the classification of devices into functional groups: from simple I/O
devices to work/management stations.

 The Norm Specifies 6 Device Profiles prior to 135-2008 Addendum L

 The Norm Specifies 8 Device Profiles since 135-2008 Addendum L

31
Profiles

Device profiles defined in Annex L prior 2008 Addendum L

 B-OWS: BACnet Operator Workstation

 BACnet OPC Server

 B-BC: BACnet Building Controller - ”high-end” automation station

 NAE, NIE, NCE Rel. 3

 B-AAC: BACnet Advanced Application Controller - “middle range”

automation device with default program
 FX Series

 B-ASC: BACnet Application Specific Controller - ”small controller”,

specified functions (e.g. single room controller)
 FX Series, TEC Series, FEC Series

32
Profiles

Device profiles defined in Annex L prior 2008 Addendum L

 B-SA: BACnet Smart Actuator - network compatible switching/

positioning device (actuator)
 Romutec Module

 B-SS: BACnet Smart Sensor - network compatible sensor

 Net Sensor

 (B-GW: BACnet Gateway only in the guidelines)

33
Profiles

Device profiles changed in Addendum L for Annex L in 2008

 B-AWS: BACnet Advanced Operator Workstation

 Similar like the “old” B-OWS

 B-OWS: BACnet Operator Workstation

 Like B-AWS, but with less functionality (No Configuration, No troubleshooting Functions)
 i.e. for the daily use

 B-OD: BACnet Operator Display

 Basic Operator Interface

The BACnet servers are the same

34
Profiles

35
PICS

Protocol Implementation Conformance Statement

 A PICS is a written document, created by the manufacturer of a device, that identifies

the particular options specified by BACnet that are implemented in the device. A
BACnet PICS is considered a public document that is available for use by any
interested party.

36
PICS

It describes the BACnet functionality of a BACnet Device

 Device Identification
 NCE, NAE5500
 Supported Profile
 B-BC,
 BIBBs
 B-OWS, B-BC, B-ASC, B-AAC
 Object Types
 BI, BO, AI, AO, Scheduler, Calendar …..
 Network options
 IP, MS/TP, PTP, Segmentation, BBMD (BACnet Broadcast management device)
 Character Sets
 ISO 10646 (UTF-8) [formerly: ANSI X4.3 (ASCII)], ISO 10646 (UCS-2), ISO 8859-1 ….

37
PICS

ANNEX A - PROTOCOL IMPLEMENTATION CONFORMANCE

STATEMENT (NORMATIVE)
BACnet Protocol Implementation Conformance Statement

Date: __________________________
Vendor Name: ___________________
Product Name: __________________
Product Model Number: ____________
Applications Software Version: ______
Firmware Revision: _______________
BACnet Protocol Revision: __________

Product Description: _______________

Example PICS of the NAE V5.0

38
Network Topologies

Network example

Management Station (BACnet Client)

Network 1 (e.g. 100 BASE-T) BACnet / IP

BACnet BACnet
Router Gateway
Server

BACnet BACnet 1
12 34 56 78

2 3 4 5 6

C ON
7 8 7 8

E
IN

ND
UT

O F
R E
LO
A D

ON

LI N
FI

Server
G.

E
- AT T EN T I O N -
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
F ER
12 34 56 78 IN

Server

2N
-
O R E

2 N
UT LO

+
1 2 3 4 5 6 7 8 7 8
A D
C ON E
ND
O F

ON

LI N
FI
G.

E
- AT T EN T I O N -
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
F ER
12 34 56 78 IN

a NE XT S ERVI CE DA T E:

2N
-
B
AT
T O R E

2 N
ER UT LO

+
Y 1 2 3 4 5 6 7 8 7 8
A D
C ON E
ND

I SA
O F

ON

LI N
FI

SL
G.

E
O
- AT T EN T I O N -

TS
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
b
D I SC O N N E C T P
O
W
P O W E R BE F O R E S
U
E
R
P
S ER V I C IN G P

F ER
LY

a NE XT S ERVI CE DA T E:

2N
-
B
AT
T

2 N
ER

+
Y

I SA
SL
O
TS
b
D I SC O N N E C T P
O
W
P O W E R BE F O R E S
U
E
R
II S ER V I C IN G
P
P
LY

a NE XT S ERVI CE DA T E:
B
AT
T
ER
Y

C
OM R TS
PO
I

M-

I SA
SL
O
TS
I II

b
D I SC O N N E C T P
O
W
P O W E R BE F O R E S
U
E
R
II D A N G ER
S ER V I C IN G
P
P
LY

L I NE V OL T A G E
I N SI D E
IV

C
OM R TS
PO
I

M-
I II

II D A N G ER

L I NE V OL T A G E
I N SI D E
IV

C
OM R TS
PO

M-
I II

D A N G ER

L I NE V OL T A G E
I N SI D E
IV

Network 2 Network 3
(e.g. MSTP) Manufacturer specific protocol

39
Network Topologies

Data Link Layer Options:

 BACnet IP, (Annex J)

 BACnet IP, (Annex J), Foreign Device
 ISO 8802-3, Ethernet (Clause 7)
 ASTM 878.1, 2.5 Mb. ARCNET (Clause 8)
 ASTM 878.1, RS-485 ARCNET (Clause 8) baud rate(s) ______
 MS/TP master (Clause 9), baud rate(s):
 MS/TP slave (Clause 9), baud rate(s):
 Point-To-Point, EIA 232 (Clause 10), baud rate(s):
 Point-To-Point, modem, (Clause 10), baud rate(s):
 LonTalk, (Clause 11), medium: __________
 Other:

40
Network Topologies

BACnet Network versa Ethernet Network

An Ethernet Network can consist of several LANs

It can contain a single BACnet Network

BACnet IP

A single LAN can contain a single BACnet Network Router

BACnet MSTP BACnet MSTP

41
Network Topologies

BACnet Network versa Ethernet Network

Several BACnet Networks can share a single Ethernet Network
Standard BACnet/IP Port is 47808 (Hexadecimal: BAC0)

BACnet Client BACnet Client

Port 47808 Port 47809

BACnet / IP

BACnet Server BACnet Server

Port 47808 Port 47809

42
Network Topologies

BACnet / IP Routing
Devices can communicate directly with other devices in an IP network

In large networks, individual smaller

networks are mostly connected through
IP routers.

BACnet often uses broadcast

messages. But since these are mostly
blocked by IP routers, a direct
connection is not possible (Firewall
effect).

This problem can be solved by using a

BBMD (BACnet Broadcast
Management Device).

The BBMD does not have to be a

separate device, since it can be
integrated into BACnet/IP devices as an
additional function.

43
Network Topologies

BACnet MS/TP
Devices can communicate directly with other devices in a RS485 network

MS/TP Master Slave Token Passing

Automation engines and controllers are

using mostly BACnet / IP

Smaller field devices are using BACnet IP

BACnet MS/TP
Communication medium is RS485 Router
using twisted pair.
Devices on BACnet MS/TP can be
Master, Master/Slave or Slave.
Peer to peer communication is possible
if it is supported by the device.
Using an BACnet /IP to BACnet MS/TP
Router the devices can be connected to
an BACnet / IP network
BACnet MSTP BACnet MSTP

44
JCI BACnet Devices

• BMS
B-OWS
Metasys UI Metasys UI
– M5i, M3i (Browser) Standard (Browser)
– Based on BACnet OPC server Network

12 34 56 78 IN

O R E
1 2 3 4 5 6 7 8 7 8 UT LO
A D
C ON E
ND
O F

ON

LI N
FI
G.

E
- AT T EN T I O N -
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
F ER

2N
-

2 N
+
12 34 56 78 IN

O R E
1 2 3 4 5 6 7 8 7 8 UT LO
A D
C ON E
ND

a O F

ON

LI N
NE XT S ERVI CE DA T E: FI
G.

E
B
AT
T
ER - AT T EN T I O N -
Y
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

NIE85

ER
I SAS
L
O
TS

F ER
b

2N
-
D I SC O N N E C T P

2 N
O

+
P O W E R BE F O R E S
U
W
E
R
P
S ER V I C IN G P
LY

I
12 34 56 78 IN

O R E
1 2 3 4 5 6 7 8 7 8 UT LO
A D
C ON E
ND
O F a NE XT S ERVI CE DA T E:

ON

LI N
FI
G.

E
B
AT
- AT T EN T I O N - T
ER
Y
P LE A S E DI S CO N N E DT B A T E R Y
II

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER

I SAS
L
O
TS
C
OM R TS
PO

M-

F ER
b

2N
I II

-
D I SC O N N E C T P

2 N
O

+
P O W E R BE F O R E S
U
W
E
R
P
S ER V I C IN G P
LY

12 34 56 78

Network Integration Server

IN

O R E
1 2 3 4 5 6 7 8 7 8 UT LO
D A N G ER A D
I C ON E
ND
L I NE V OL T A G E O F

ON

LI N
FI
I N SI D E
IV G.

E
- AT T EN T I O N -
P LE A S E DI S CO N N E DT B A T E R Y

P
a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
a NE XT S ERVI CE DA T E:
B
AT
T
ER
Y

II

F ER
I SAS
L

2N
O

-
TS

2 N
+
C
OM R TS
PO

M-
b
D I SC O N N E C T
P O W E R BE F O R E S
P
O
W
E
I II
U R
P

NCM
S ER V I C IN G P
LY

D A N G ER
I
12 34 56 78 IN
L I NE V OL T A G E
I N SI D E
a NE XT S ERVI CE DA T E:

O R E
IV B
AT
T
ER
Y
1 2 3 4 5 6 7 8 7 8 UT LO
A D
C ON E
ND

I SAS
O F

ON

LI N
FI

L
G.

O
E

TS
- AT T EN T I O N -
P LE A S E DI S CO N N E DT B A T E R Y

P
II a b

OW
B E F O R E I N S T A L L IN G M E M O R Y D -R
AM

ER
b
D I SC O N N E C T P
O
P O W E R BE F O R E W

C
S E
U R

OM R TS
P

PO
S ER V I C IN G P
LY

M-

F ER

2N
-
I II

2 N
+
NCM
I

12 34 56 78 IN
D A N G ER

L I NE V OL T A G E O R E
I N SI D E UT LO
IV 1 2 3 4 5 6 7 8 7 8
A D
E
II C ON ND
O F

ON

LI N
N2 or LON
FI
G.

E
- AT T EN T I O N -
a NE XT S ERVI CE DA T E:
P LE A S E DI S CO N N E DT B A T E R Y

P
B
AT
a b

OW
T
ER B E F O R E I N S T A L L IN G M E M O R Y D -R
Y

C
AM

ER
OM R TS
PO

M-
I SAS
L
O
TS
I II

F ER

2N
b

2 N
+
D I SC O N N E C T P
O
P O W E R BE F O R E S
W
E

NCM
U R
P
S ER V I C IN G P
LY D A N G ER

L I NE V OL T A G E
I N SI D E
IV

a NE XT S ERVI CE DA T E:

N2 or LON
B
AT
T
ER
Y

II

I SAS
L
O
TS
C
OM R TS
NCM

PO
b

M-
D I SC O N N E C T P
O
P O W E R BE F O R E S
U
W
E
R
I II S ER V I C IN G
P
P
LY

I
D A N G ER

L I NE V OL T A G E
I N SI D E
IV

N2 or LON
II

C
OM R TS
PO

M-
I II

NCM N2 or LON
IV
D A N G ER

L I NE V OL T A G E
I N SI D E

NCM
N2 or LON
N2 or LON

Over IP Over IP
MSTP

Fan Split
Systems
BACnet IP
Fire
panels
Fan Coils, HVAC
Variable Speed Drivers Access
Control
Other 3-party
controllers HVAC

45
JCI BACnet Devices

• Automation Engines
B-BC profile BACnet IP
– NAE55, NAE45, NAE35, NCE
Standard components with BACnet IP, BACnet

MSTP
MSTP, LON, N2

– NIE55
to integrate N1 networks
Access CCTV
Intrusion HVAC
Control

BACnet IP

NCE NAE

46
BACnet Summary

 BACnet is manufacturer independent. This enables the exchange of data

between different systems.

 Enables the realization of cross-manufacturer functions.

 Through the use of usual network media, BACnet is extremely flexible.

 BACnet already covers a large range of the functions required by today's

building automation technology.

 BACnet is “International” (USA, Europe, Asia and Australia)

50
BACnet Summary

 It is necessary to invest some time and money into the planning of BACnet
systems.

 There needs to be communication: “Technical” as well as “Human”.

 The BACnet Standard is constantly being updated.

 New objects and services are being defined in order to make BACnet
available for use in other application areas of building automation, e.g.
Counter objects, Security, Integration of Video, Web services.

51
Next Sessions

Questions you have asked

What is needed connecting a BACnet device ?
What could be the problems using BACnet/IP , BACnet MS/TP ?
What software (for troubleshooting) we can use ?
Basic overview ?
Comparison with over protocols
Critical condition ?
Addressing issues ?
How to estimate Support ?
What are PICS describing ?
What does a NAE expose ?

52
Next Sessions

Reviewing a BACnet / IP recording

Reviewing a BACnet MS/TP recording
NAE / NCE FC Bus and SA Bus
BBMD Functionality
COV Functionality (What is COVU ?)
Alarm Functionality (General and NAE specific)
Behavior of JCI BACnet OPC server and other BACnet Clients
Out of Service Functionality
EDE BACnet Functionality
BACnet Routers
Tools

53
 THANKS FOR YOUR ATTENTION

FEEL FREE TO CONTACT US!

54
BACnet Protocol
Advanced Training Part 2

Systems Integration Services Europe Training Program

55 Johnson Controls
BACnet Protocol
Advanced Training Part 2

Systems Integration Services Europe Training Program

BACnet Project Topics

What is needed connecting a BACnet device ?

What could be problems using BACnet/IP , BACnet MS/TP ?
Critical condition ?
Addressing issues ?
How to estimate Support ?
What are PICS describing ?
What does a NAE expose ?
What software (for troubleshooting) we can use ?
Tools ?

57
Advanced BACnet Knowledge

Reviewing a BACnet / IP recording

Reviewing a BACnet MS/TP recording
NAE / NCE FC Bus and SA Bus
JCI BACnet OPC capabilities V7.0 / V7.1
BBMD Functionality
COV Functionality (What is COVU ?)
Alarm Functionality (General and NAE specific)
Behavior of JCI BACnet OPC server and other BACnet Clients
Out of Service Functionality
EDE BACnet Functionality
BACnet Routers

58
What is needed connecting a BACnet device ?

• Request a PICS document of the other BACnet device

(JCI PICS are on the Intranet)
• Compare BIBBs of the devices
• Compare character sets of the devices
• Compare customer requests with the consolidated result of both devices
• Request network layout on big sites (BBMD ?)
• Request Device ID(s) (They must be unique)
• Request alarm priorities for different alarm categories
• Request / Check the use of command priorities (Manual, Override, etc.)

59
Addressing issues

• Device ID
• Each Device ID must be unique
• This includes BACnet MS/TP trunks connected via a router to BACnet / IP
• The MAC address on a MS/TP trunk is independent of the Device ID
• MAC Address
• BACnet MS/TP Master devices 0 – 127 (is changeable)
• BACnet MS/TP Slave devices 128 - 254 (is changeable)

61
Addressing on a NAE/NCE BACnet MS/TP Trunk
MAC Addresses

62
Using BACnet MS/TP on a NAE/NCE

 NCE25 models support:

 32 devices total on the FC Bus (maximum)
 NAE35 models support
 50 devices total in the FC Bus (maximum)
 NAE45/55 models support when all of the devices connected on the FC Bus are
Metasys FX’s, FECs, VMAs, and/or IOMs:
 100 devices total per FC Bus (maximum)
 NAE45/55 models support when one or more TEC-26xx Series thermostat or third-
party MS/TP device is connected on the FC Bus:
 64 devices total per FC Bus (maximum)

63
Using BACnet MS/TP on a NAE/NCE

Example with NAE-35

• NAE-35
– MS/TP Trunk
• Only JCI devices
(FXs)
• Max 50 devices per
trunk
• Max 32 devices per
segment
– Max 2500 objects per
NAE (Includes all
points, extensions,
graphics, trend study,
and other objects)

64
What could be a problem using BACnet/IP , BACnet MS/TP ?

JCI BACnet OPC Server (V7.0 and earlier) connecting to BACnet devices
which does not support ReadPropertyMultiple
Using character sets not supported by Client AND Server
Former ANSI X3.4 and UTF8 character sets are slightly different
FC-Bus supports MS/TP Master devices, only
Same Baudrate for all devices on a MS/TP bus
BACnet MS/TP uses RS485 Hardware ie. max 32 devices on a segment
For more devices repeaters must be used
SA-Bus supports MS/TP Slave devices known in CCT, only

65
NAE / NCE FC Bus and SA Bus

SA Bus supports known MS/TP Slave devices, only

Like IOM, Romutec modules
SA Bus devices are configured in CCT
FC Bus supports MS/TP Master devices, only
Like IOM, FEC, Network Sensor, 3rd party devices

66
BBMD Functionality

BBMD

Router Router blocks broadcast

Router Router blocks broadcast

BBMD

67
BBMD Functionality

BBMD

Router

Router

Foreign Device

68
COV Functionality (What is COVU ?)

Client subscribes COV with a Life Time (indefinite shall not be used; it would
stay forever)
COV Event is send when value changes exceeding COV Increment
COV Increment should be writable to adjust sending of values
1000 COV Table Entries in a NAE/NCE

COVU-A uses broadcast to distribute the value. Should be used with care.
No Subscription is needed; COVU-B must supported to receive the value.
It is seldom used.

69
Alarm Functionality

Intrinsic Alarming in AI, BI, etc.

sends alarm to NC Alarm Viewer
Alarm Enrollment creates alarms from BACnet
several conditions and sends alarm Client
to NC
Notification Class defines priority and Acknowledge Alarm
sends alarm to Recipient(s)
(NAE checks Status of Recipient
before sending alarm) NC 1
Alarm Acknowledge is send to BACnet
Notification Class Server
Alarm Acknowledge Event is send to AI 23 MO 77
Recipient(s)

70
Out of Service Functionality

Present Value and Reliability are writable when set

Useful when eg. the outdoor temperature sensor is broken
the Present Value of this AI is set manually to a nearly correct value

71
BACnet Routers

 Device Names must be unique

in the complete BACnet network
 Device ID must be unique in the BACnet IP Network 1001
complete BACnet network
Router Router
 Network Number must be
unique in the complete BACnet
network
 BACnet MS/TP Slave devices
need “Slave Proxy” functionality
in the router (I-Am will be send BACnet MSTP BACnet MSTP
Network 1002 Network 1003
by the router for a slave device).

72
Software for Troubleshooting

• Wireshark for BACnet / IP

• For Ethernet networks a Hub or a switch with monitoring port is needed.
NOT A SIMPLE SWITCH !!

• Wireshark for BACnet MS/TP (using a BACnet router)

• mstpcap for BACnet MS/TP (from BACnet tools on Source Forge)
• MAX Tool scans BACnet /IP
MultiProtocol Application eXplorer
• MAX Tool scans BACnet MS/TP Bus (using a BACnet router)
• BTF for testing (expensive)
• VTS Visual Test Shell (from Source Forge)

73
Reviewing BACnet Records

Examples:
• NAE Startup
• Alarming
• COV
• BACnet Router
• BBMD
• MS/TP

74
BACnet Network Sniffing

NAEs

Switch
BACnet Client
BACnet / IP

I-Am is send by
Router for BACnet
Slave devices Router

BACnet MS/TP

Master and / or MS/TP MS/TP MS/TP

Slave devices Device Device Device

75
BACnet Network Sniffing

Influence on Network Traffic by Network Components

 Ethernet Routers
Transmits Unicast messages, only; No Broadcasts
 Switch (non manageable)
Filters Unicast messages (only 2 ports are involved)
Transmits Broadcasts messages to all ports
 Hub (obsolete)
Transmits all messages to all ports
 BACnet Router (IP to MS/TP)
Transmits Unicast and Broadcast BACnet messages
Tokens are not transmitted

76
BACnet Network Sniffing

NAEs

Switch
BACnet Client BACnet / IP

Hub
NAE
BACnet
Router
BACnet MS/TP
Wireshark
MS/TP MS/TP MS/TP
Device Device Device

77
BACnet Network Sniffing

BBMD NAE

BACnet Client Router

Switch BBMD NAE

Hub
NAE

Wireshark

78
 THANKS FOR YOUR ATTENTION

FEEL FREE TO CONTACT US!

79