KBA: Application Bulletin 09-0021-01-00

Setting Up "Annex J" BACnet/IP in BACtalk

____________________________________________________________________________________

PRODUCTS AFFECTED
• All

Version 3.10 of BACtalk for Windows introduces Internet Protocol (IP) support at the BACtalk operator
terminal. IP support is implemented using "Annex J" BACnet/IP. This article series on the Alerton Support
Network seeks to thoroughly inform you about Annex J, from the history of its inception to a preview of
the specifics for setting up devices. Alerton believes that IP capability is a door opener, but only if you
understand its implications, capabilities, and limitations. It's our hope that this series helps you prepare.

Setting Up "Annex J" BACnet/IP in BACtalk

BACtalk for Windows v3.10 supports "Annex J" BACnet/IP, which enables BACnet messages to run over
Internet Protocol (IP) Wide Area Networks (WAN). If your BACnet internetwork runs on an enterprise
network connected by IP routers, you can set up BACtalk for Windows to have an "always on" connection
over the IP/WAN. You can also choose to use the IP/WAN to temporarily connect a BACtalk operator
terminal, which is useful if you have a PPP connection, or some other type of roaming access to your
IP/WAN.

This article first introduces you to the critical component of BACnet/IP with BACtalk products-the BACnet
Broadcast Management Device (BBMD). It then discusses how to set up a BACtalk operator terminal to
participate on a BACnet/IP WAN permanently, and then how to set the operator terminal up to use the IP
WAN for temporary connections.

Caution! Setting up a BACnet system on an IP internetwork requires close coordination with IT and
networking professionals who maintain the network. Seek out contacts in this profession as early as
possible in the project to help you determine IP networking parameters that will work. Their expertise and
insight during the planning phase will save countless hours later in the project. If no such professional is
available, you will need to set IP network parameters on your own. If this is the case, research on IP
internetworks and the BACnet/IP Annex J implementation is recommended, but you can use "cookbook"
settings if there is no chance of conflicting with other enterprise applications.

Sample Network Architecture Diagram

A sample network architecture diagram is available in 11 X 17 PDF format. Click here to view or save.

Setting Up BACnet Broadcast Management Devices (BBMD)

BACnet Broadcast Management Devices (BBMDs) are the key devices in a BACnet/IP setup within
BACtalk. BACtalk LSis (v3.10 EPROM and later) and BTIs are BBMDs. The BBMD sits on a BACnet
subnet. It's responsible for re-broadcasting messages that it receives over IP to other BACnet devices on
its subnet. Each BBMD keeps a table of the IP addresses of other BBMDs so they can share data over
the IP WAN.

1
KBA: Application Bulletin 09-0021-01-00

Essentially, BBMDs make the IP WAN look like a single BACnet internetwork to BACnet devices. Setting
IP Networking parameters in all internetworked BBMDs correctly is critical to system success. Table 1
provides an explanation of IP settings in BACnet/IP-enabled devices.

Table 1 Annex J BACnet/IP settings for the LSi (version 3.10 EPROM and later) and the BTI.

Field Values Remarks

BACnet/Eth YES | NO YES = Enables BACnet message transmission on the local Ethernet network
segment.

NO = Disables BACnet message transmission--the controller sends no messages

on the network.

Some network administrators may disallow BACnet packets on shared networks.

In this case, set this value to NO and ensure that IP Enabled is YES and that each
controller to communicate locally has IP parameters set up correctly.
IP Enabled YES | NO YES = Enables IP support.

NO = Disables IP support.

If the controller is on an Ethernet LAN but does not use IP, ensure that IP Enabled
= NO (or that Addr = 000.000.000.000). This prevents the controller from sending
any IP messages over the LAN. Default is ON, but addr defaults to
000.000.000.000. IP won't run until addr is set.
B/IP Clause J Fixed to Annex J BACnet/IP support.
IP Comm* DIX | 802.2 The Ethernet frame type used for incoming and outbound IP transmissions. The
primary difference between frame types is the LLC header.

DIX = The controller generates and routes DIX (Ethernet II) frames.

802.2 = The controller generates and routes 802.2 (also known as 802.3/802.2-not
RAW Ethernet) frames.
Virtual Net Range is 0- The BACnet Network Number that is assigned to the "virtual network" created by
65534 the IP WAN. All BBMDs participating on the IP WAN (in other words, all BBMDs in
the routing table) must have this Virtual Net set to the same number. This Network
Number must also be unique with respect to internetworked BACnet LANs. It
cannot match other BACnet Network Numbers (Ethernet LANs, MS/TP LANs,
ARCNET LANs, etc.) Default is 00001.
Assy 001-300 The fragment reassembly time-out, in seconds. Default is 120.
Timeout*
Max MTU* 90-1500 The Maximum Transmission Unit in bytes. Default is 1500 (typical for Ethernet
networks).
Time to Live* 001-255 Sets the initial TTL value for IP packets sent from this controller. TTL enumerates
the number of hops (the number of forwarding routers) the packet is allowed to
pass between source and destination. This prevents looping packets from crashing
routers and saturating entire links or networks. Default is 64.

2
KBA: Application Bulletin 09-0021-01-00

Type of 0, 1, 2, 4, 8, 15 Sets the 4-bit type of service (TOS) value in the IP packet header. Some
SVC* applications may use TOS to provide precedence levels and determine optimum
routing methods for packets. Default is 0.

Setting TOS Bits Meaning

0 0000 Default
1 0001 Minimize monetary cost
2 0010 Maximize reliability
4 0100 Maximize throughput
8 1000 Minimize delay
15 1111 Maximize security

Addr* nnn.nnn.nnn.nnn The IP address assigned to this controller in dotted-decimal format. nnn is a
number from 0-255. Follow IP addressing conventions and rules for your network.
Default is 000.000.000.000, which prevents IP operation even when IP Enabled =
yes.
Port* 47808-47823 The UDP port of this controller, which is used to establish connectionless
recommended transmission over IP with other BACnet/IP-enabled controllers. This UDP port must
be the same as other BACnet/IP-enabled controllers on the same subnet,
especially if the controllers exchange messages only using BACnet/IP (BACnet/Eth
= NO).

There are notable exceptions to this rule:

• When another BBMD is on the same subnet, the UDP ports of the
BBMDs must be different.
• Any device on the same subnet that registers with the BBMD as a foreign
device (such as a BACtalk operator workstation) must have a different
local UDP port from the BBMD.

Only those controllers with same UDP port on a subnet will exchange BACnet/IP
messages. For best results, always ensure that controllers on an internetwork use
the same UDP ports.
MASK* nnn.nnn.nnn.nnn The netmask value for transmission on this network in dotted-decimal. Follow IP
netmasking conventions and rules. Default is 255.255.255.000, which is typical.
Gt01* nnn.nnn.nnn.nnn The IP address, in dotted-decimal, of the primary IP router the controller uses to
connect to the IP internetwork. nnn is a number from 0-255. Default is 0.0.0.0,
indicating no device.
Gt02* nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the secondary IP router the
controller uses to connect to the IP internetwork. nnn is a number from 0-255.
Default is 0.0.0.0, indicating no device.
Srvr nnn.nnn.nnn.nnn Optional. The IP address, in dotted-decimal, of the device that functions as the
broadcast distribution table (BDT) server to this controller. This controller retrieves
its routing table from the Srvr device if the table is lost for any reason. If left to
000.000.000.000, the routing table must be reset manually at the controller. For
this reason, the IP address of the Srvr should appear in its own routing table.
Broadcast Distribution Table (BDT)

3
KBA: Application Bulletin 09-0021-01-00

The broadcast distribution table (BDT) contains three associated entries for each BBMD on the IP Virtual Net being
defined. These three entries must be assigned for each BBMD on the Virtual Network. The first entry identifies the IP
address of BBMDs in the group, the second the UDP port associated with the BBMD, and the third the netmask used
on the BBMD's subnet. Usually, BBMDs have identical BDTs because one is set up as the BDT server (see Srvr
herein).

Important! Although options appear for up to 32 devices, the IP Virtual Network implementation in the LSi
supports a maximum of 4 BBMDs. A greater number of BBMDs requires that you set up aggregate IP Virtual
Networks.
d01 ... d04 nnn.nnn.nnn.nnn Each entry is the IP address of a BBMD on the IP Virtual Network.
01p ... 04p 47808-47823 Each entry is the UDP port of the BBMD of interest. This is the same value set up
recommended with the Port entry in the BBMD of interest.
01m ... 04m nnn.nnn.nnn.nnn Each entry is used as a mask for the target BBMDs network. Typically set to
255.255.255.255, specifying that messages go only to the target BBMD.
*These settings should be chosen and coordinated with the IT professional on site.

Setting Up a BACtalk Operator Workstation for BACnet/IP

Important! Windows IP networking and connection parameters for the site IP network must be
configured correctly. Coordinate with IT professionals to ensure proper Windows internetworking setup.

Use Online Help in Setup Dialogs

When you set up an IP connection in BACtalk v3.10, it's easy to forget what settings do and what the
basic rules are. For a quick reminder, click the question mark in the dialog box and then click the control
or setting you need information about. For more detailed information, click the Help button in the dialog
box. This article is available as a help topic from within BACtalk operator workstation software.

Know the Operator Workstation Setup Essentials

When a BACtalk operator workstation connects to a BACnet/IP internetwork, it "registers" with a BBMD.
Your setup in BACtalk ensures that the BACtalk operator workstation has the following information:

• The IP address of the BBMD it registers with, this can be a BBMD on the same subnet (0 router
hops), or anywhere on the internetwork.
• The UDP port of the BBMD
• A UDP port for the operator workstation, which should be different than the UDP port of the
BBMD, and must be different if the operator workstation and BBMD are on the same subnet (0
router hops).
• The BACnet/IP Virtual Network Number that the operator terminal joins.
• A re-registration interval, in seconds, after which the operator terminal and BBMD re-confirm
communications.

The "Always On" Option: Set Up Annex J in the Network Tab of General System
Setup
For the always on option, BACnet messages pass over the IP network in the same way as any other
application data: data displays, schedules, trendlogs, and alarms can reference Device Instances and
properties that originate on a BACnet/IP internetwork. They appear to the BACtalk operator workstation

4
KBA: Application Bulletin 09-0021-01-00

as though they were locally connected. BACtalk operator workstation software initiates the connection on
startup. Set up this type of IP connection on the Network tab of General System Setup.

The "Temporary Connection" Option: Set Up Annex J in Connection Manager for

a Remote Site
In addition to the always on Annex J option, BACtalk enables you to set up temporary connections over
IP through the Connection Manager. You can set up the connection type in a remote site profile to use
Annex J, just as you would normally use a modem or a serial cable. In this way, you can temporarily
connect to a remote site over the BACnet/IP network. Once you establish your connection to the network-
plugging into an available Ethernet jack, dialing in through PPP or RAS, etc.-you can open BACtalk and
then use Connection Manager to initiate a BACtalk session by registering with the BBMD. You select
Annex J under Connection Type and then click Settings to set connection details. Note that the Virtual
Network # is used differently during an Annex J connection; it is the BACnet/IP Virtual Network Number.

____________________________________________________________________________________

Doc ID: 09-0021-01-00

Release date: 10/01/03
Expires: 10/01/04
Products: All