ABB CBXi Series User manual

—
USER GUIDE
MAN0141 rev 23
CBXi IP Controller

©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
2
MAN0141 rev 23
Style conventions used in this document:
UI Text: Text that represents elements of the UI such as button names, menu
options etc. is presented with a grey background and border, in Tahoma
font which is traditionally used in Windows UIs. For example:
Ok
Standard Terms (Jargon): Text that is not English Language but instead refers to
industry standard concepts such as Strategy, BACnet, or Analog Input is
represents in slightly condensed font. For example:
BACnet
Code: Text that represents File paths, Code snippets or text file configuration
settings is presented in fixed-width font, with a grey background and
border. For example:
$config_file = c:\CYLON\settings\config.txt
Parameter values: Text that represents values to be entered into UI fields or
displayed in dialogs is represented in fixed-width font with a shaded
background. For example
10°C
Product Names: Text that represents a product name is represented in bold
colored text. For example
INTEGRA™
Company Brand names: Brands that are not product names are represented by
bold slightly compressed text:
ABB Active Energy
PC Keyboard keys: Text representing an instruction to press a particular key on
the keyboard is enclosed in square brackets and in bold font. For
example:
[Ctrl]+[1]

table of contents
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
3
MAN0141 rev 23
1THE CBXI SERIES
Introduction ............................................................................................................ 5
Application .............................................................................................................. 5
2IP NETWORKING
What is IP? ............................................................................................................... 6
Physical Layer (Layer 1) ..................................................................................................................................... 6
DataLink Layer (Layer 2)................................................................................................................................... 6
Network Layer (Layer 3) ................................................................................................................................... 6
Transport Layer (Layer 4)................................................................................................................................. 6
Session Layer (Layer 5)..................................................................................................................................... 6
Presentation Layer (Layer 6)........................................................................................................................... 6
Applications Layer (Layer 7) ............................................................................................................................ 6
IP Addressing...........................................................................................................7
DHCP (Dynamic Host Configuration Protocol) ..........................................................................................7
Subnetwork (Subnet).........................................................................................................................................7
Default gateway ................................................................................................................................................. 8
Port Numbers...................................................................................................................................................... 9
Uplink/WAN and Segmentation........................................................................ 10
Network Address Translation (NAT)............................................................................................................10
Domain Name System (DNS).............................................................................. 11
3BACNET NETWORKING
What is BACnet?....................................................................................................12
BACnet object types.............................................................................................13
BACnet services.....................................................................................................13
BACnet's Client / Server nature ........................................................................ 14
Network Types...................................................................................................... 14
PIC Statement........................................................................................................15
BACnet Topology ..................................................................................................15
BACnet IP Broadcast Management Device (BBMD) .......................................16
BACnet MS/TP Device Loading ..........................................................................17
Read Property Multiple ........................................................................................17
4CBXI WEB UI
Summary Dashboard........................................................................................... 18
BACnet Menu ........................................................................................................ 18
Device ...................................................................................................................................................................18
Router Networks ...............................................................................................................................................19
Time Sync ............................................................................................................................................................19
BBMD / NAT....................................................................................................................................................... 20
IP Network..............................................................................................................21
Configuration.....................................................................................................................................................21
TCP/UDP Ports ................................................................................................................................................. 22
Edit SSL Cert / Sign SSL Cert ....................................................................................................................... 23
RS-485 Port ........................................................................................................... 24

table of contents
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
4
MAN0141 rev 23
Platform................................................................................................................. 25
Status report ..................................................................................................................................................... 25
Firmware Upgrade utility............................................................................................................................... 25
Backup/Restore utility.................................................................................................................................... 26
Set Time and Date ............................................................................................................................................27
Restart utility ......................................................................................................................................................27
Diagnostics ........................................................................................................... 28
Processes ........................................................................................................................................................... 28
Debug Level ....................................................................................................................................................... 28
System logs ....................................................................................................................................................... 28
Open-source acknowledgment notices .................................................................................................... 29
5INSTALLATION
Apply power to the CBXi-8R8(-H) ..................................................................... 30
Connect the CBXi to an IP network .................................................................. 30
The CBXi Integrated Ethernet Switch .........................................................................................................31
Configuring the IP connection ......................................................................................................................31
Configure the CBXi-8R8(-H) for BACnet® communications ........................ 38
Connect the CBXi to BACnet MS/TP ................................................................ 41
Terminate the MS/TP network .....................................................................................................................41
Attach RS-485 communication wires to the MS/TP Subnet port.......................................................41
Connect the CBXi-8R8(-H) to FLX units........................................................... 42
Set the FLX address ........................................................................................................................................ 42
Join or terminate the FLX bus ...................................................................................................................... 43
(If required) Set up FLX bus extension ...................................................................................................... 43
Add the Controller to the CXproᴴᴰ Site............................................................46
Set Controller Date and Time ....................................................................................................................... 46
Set up the CBXi and connected FLX modules in a Site in CXproᴴᴰ.................................................... 47
(if required) Configure a Modbus Connection .........................................................................................51
Set I/O to a known Safe Mode ..................................................................................................................... 59
Set up the Controller Strategy ..................................................................................................................... 59
Accessing Modbus points in the Strategy.................................................................................................61
6CBXI OPERATION
Physical Layout..................................................................................................... 63
Dimensions ........................................................................................................................................................ 63
Wiring................................................................................................................................................................... 63
Terminals............................................................................................................................................................64
CBXi Indicator LED Signals............................................................................................................................ 65
Inputs and Outputs ............................................................................................. 66
Input modes ...................................................................................................................................................... 66
Output modes...................................................................................................................................................69
Auxiliary Power outputs...................................................................................... 70
Using a Keypad with the CBXi ........................................................................... 70
Output Override ....................................................................................................71
Restarting and Resetting the CBXi....................................................................72
Resetting the WebUI login..............................................................................................................................72
Full factory reset................................................................................................................................................72
Restarting the controller without power cycling .....................................................................................72

CBXi IP Controller | The CBXi Series
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
5
MAN0141 rev 23
1 The CBXi Series
INTRODUCTION
The CBXi-8R8 and CBXi-8R8-H are fully programmable IP-based BTL-listed BACnet® Building Controllers
(B-BC) that supports simultaneous multi-protocol communications including BACnet/IP, BACnet MS/TP,
Modbus TCP, and Modbus RTU.
Part of Cylon’s CB Line of BACnet field controllers, the CBXi Series of controllers are built on an extendible
platform that features 8 UniPuts™ with Relay and 8 Universal Inputs,and feature support for up to five
FLX (Field Level e X pansion) Series extension modules providing a scalable solution from 16 up to 96
points of control. FLX expansion modules are available in a variety of options to allow maximum
flexibility in achieving the required point configuration. The CBXi-8R8-H provides local Hand-Off-Auto
override functionality.
The fully programmable CBXi-8R8(-H) can be tailored to meet a variety of applications by creating and
modifying strategies using Cylon's CXproᴴᴰ programming interface.
APPLICATION
The CBXi-8R8(-H) is designed for a wide range of energy management applications for intelligent control
of:
•HVAC equipment such as Central Plant, Boilers, Chillers, Cooling Towers, Pump Systems, Air Handling
Units (Constant Volume, Variable Air Volume, and Multi-zone), and Rooftop Units,
•Electrical systems such as lighting control, variable frequency drives and metering.
The CBXi-8R8(-H) can be used as an integration platform and natively supports the routing of either
BACnet MS/TP to BACnet/IP or Modbus RTU to Modbus TCP without the need for gateways or additional
hardware.

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
6
MAN0141 rev 23
2 IP Networking
WHAT IS IP?
IP (Internet Protocol) is an agreed standard that defines how devices communicate over the Internet or
other Internet-like Ethernet network.
IP is part of a 7-layer architecture consisting of
•Physical Layer (Layer 1)
•DataLink Layer (Layer 2)
•Network Layer (Layer 3)
•Transport Layer (Layer 4)
•Session Layer (Layer 5)
•Presentation Layer (Layer 6)
•Applications Layer (Layer 7)
PHYSICAL LAYER (LAYER 1)
This refers to the electrical impulses (or light signal or radio signals) carried on the cable (or fiber, air or
other physical medium). For IP, the physical layer is usually Ethernet.
DATALINK LAYER (LAYER 2)
This is where data packets are translated to and from bits, which can be transferred on the Physical Layer
NETWORK LAYER (LAYER 3)
Layer 3 provides switching and routing to create paths for data to be transmitted from node to node
within the network. This is the layer that gives IP its name.
TRANSPORT LAYER (LAYER 4)
This layer is responsible for end-to-end error recovery and flow control, enabling transparent transfer of
data between hosts.
SESSION LAYER (LAYER 5)
The Session layer manages exchanges (conversations) between the “applications” on each host.
PRESENTATION LAYER (LAYER 6)
This layer translates between application and network formats, so that communication independent of
data representation such as ASCII, GIF, JPEG etc.
APPLICATIONS LAYER (LAYER 7)
Everything at layer 7 is application-specific, such as Telnet, FTP, WWW browsers, HTTP etc.

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
7
MAN0141 rev 23
IP ADDRESSING
Each device has at least one IP address, which uniquely identifies it from all other devices on the network.
There are several forms of IP addresses, but the most commonly used is IPv4, which consists of 4
numbers (between 0 and 255 ) separated by dots e.g. 192 . 168 . 222 . 51
DHCP (DYNAMIC HOST CONFIGURATION PROTOCOL)
The address can be set manually on the device itself, or else the device can be assigned one by a master
controller on the network. This master controller is known as the Dynamic Host Configuration Protocol
(DHCP) server.
To use an IP address, a device must know several pieces of data, including the IPv4 address that the
device will use, the IP address of the Domain Name Server (DNS) where the device can find IP addresses
of other devices, and the IP address of the Default Gateway device through which communications are
routed.
Using DHCP means that all these pieces of information are set automatically avoiding the need for
specialist knowledge of IP networking. If DHCP is available on your network is the most convenient way
to configure your devices.
DHCP reservation
A DHCP server can be configured to always assign a particular IP address to a specific device. This is
called a DHCP reservation and enables a user to access a device by IP address even if the device power-
cycles and makes a new DHCP request.
SUBNETWORK (SUBNET)
A subnet is a logical division of a network –that is while it might be physically connected to other
subnets, communications traffic from one subnet can be kept separate from comms origination on
other subnets.
A group of the most significant bits of the IPv4 address (the numbers at the start of the address)
specifies the address of a network or subnetwork. This is called the Network Prefix. The remainder
specifies the host –the address unique to the specific device.
For example:
•on the 192.168 subnet, an IP address of 192.168.2.54 refers to device 2.54.
•On the 55.231.77 subnet, IP address 55.231.77.3 refers to device 3
The specific parts of the address that are in each portion is defined by the device’s ‘Subnet Mask’. This
can be expressed as a “bitmask” that is applied by a bitwise AND operation – e.g. 255.255.0.0 means that
only the last 2 segments of the address apply to the local subnet.
For example,
•if the address 192.168.2.54 has a subnet mask “255.255.0.0”, that means that 192.168 is the subnet
address, and 2.54 is the device address.
•if the address 55.231.77.3 has a subnet mask “255.255.255.0”, that means that 55.231.77 is the subnet
address, and 3 is the device address.
The network can also be identified by a decimal number following the first IP address on the network –
e.g. 55 . 231 . 77 . 0 / 24 . This is called Classless Inter-Domain Routing (CIDR) notation. The decimal number
represents the number of bits allocated for the Network Prefix.
Each segment of an IP address represents 8 bits,
i.e. 192 . 168 . 2 . 54 could also be written 11000000 . 10101000 . 00000010 . 00110110

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
8
MAN0141 rev 23
In CIDR notation, /16 means that 16 of these bits represents the subnet, and the remainder specifies the
host:
CIDR
192 . 168 . 2 . 54 / 16
IP
Address
decimal
192
.
168
.
2
.
54
IP
Address
Binary
1
1
0
0
0
0
0
0
.
1
0
1
0
1
0
0
0
.
0
0
0
0
0
0
1
0
.
0
0
1
1
0
1
1
0
16 bits representing the subnet
host
Equivalen
t subnet
mask
255
.
255
.
0
.
0
CIDR
55 . 231 . 77 . 3 / 24
IP
Address
decimal
55
.
231
.
77
.
3
IP
Address
Binary
0
0
1
1
0
1
1
1
.
1
1
1
0
0
1
1
1
.
0
1
0
0
1
1
0
1
.
0
0
0
0
0
0
1
1
24 bits representing the subnet
host
Equivalent
subnet
mask
255
.
255
.
255
.
0
DEFAULT GATEWAY
Devices on the same subnet can address IP packets to each other without using a router device.
To communicate with devices on another subnetwork, the traffic must be routed through a router
device’s WAN port. When a device needs to communicate with an IP address that is not on the same
network, it sends the packet to the Default Gateway, which is usually the subnet’s Router.
Note: Some BACnet services use “broadcasts” (e.g. “Who-Is”). On a LAN with standard routers, these
broadcasts are “blocked”. As a result, BACnet broadcasts are limited to the IP Subnet of the BACnet
device. With a BACnet/IP network of 2 or more IP subnets, a device that can act as a BACnet/IP
Broadcast Management Device (BBMD) must be used.

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
9
MAN0141 rev 23
PORT NUMBERS
A “Port” on an IP device is a concept that allows traffic to be mapped within a device’s address to a
specific process running in that device. A Port number forms part of a data packet’s IP address, but is
often set by convention, depending on the protocol that the packet uses. For example, HTTP traffic by
convention uses port 80 . If no port is specified in the IP address for HTTP traffic, port 80 will be assumed.
If a port is specified (e.g. port 8080 as in the address 192 . 168 . 100 . 33 : 8080 ), the specified port will be used
instead. This allows the device to communicate on multiple protocols at the same time.
Some of the services associated with port numbers include:
Service
Protocol
Default Port
Number
SMTP
TCP
25
DNS
TCP, UDP
53
DHCP
UDP
67
HTTP
TCP
80
HTTPS
TCP
443
BACnet/IP
UDP
47808
Some of the port numbers recognized by CBXi are shown below. These can be changed in the controllers
Web UI at Communications > Serial Ports > IP Ports

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
10
MAN0141 rev 23
UPLINK/WAN AND SEGMENTATION
Physically splitting a network into different function groups is known as “Network segmentation”. This is
done to improve performance (by reducing the amount of traffic on each segment) and to improve
security. It is achieved by connecting Routers together by their “WAN” or “UPLINK” ports.
If routers are connected without using their “WAN” or “UPLINK” ports, the result is a single segment:
NETWORK ADDRESS TRANSLATION (NAT)
Network Address Translation is a function of a router or firewall, which maps multiple local IP addresses to
a single public IP address. This is necessary because the number of IPv4 addresses is finite.

CBXi IP Controller | IP Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
11
MAN0141 rev 23
DOMAIN NAME SYSTEM (DNS)
When communicating on the wider Internet, it can be difficult to remember the numeric IP address for
each device with which you want to communicate. The Domain Name System (DNS) was created to allow
internet users to use a text-based Uniform Resource Locator (URL) with meaningful values such as
“www.cylon.com” to connect to a site or device without having to know the server’s IP address. The DNS
finds the URL in its distributed database and passes the corresponding numeric IP address to the
requesting device. If a device’s IP address changes, the DNS server can be updated with its new IP
address, ensuring that other networked devices can still find this device from its URL.
When setting a devices IP parameter manually, between one and three DNS IP address are usually
provided. The second and third addresses are used if the first DNS becomes unavailable.
If you do not know the address of your DNS server(s), you can use publicly available DNS server addresses
for example primary = 8.8.8.8 and secondary = 4.4.4.4

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
12
MAN0141 rev 23
3 BACnet Networking
WHAT IS BACNET?
BACnet is "a data communication protocol for building automation and control networks." This means it
is a set of rules for exchanging BMS information between systems from different manufacturers.
The rules take the form of a written specification that spells out what is required to conform to the
protocol
The key feature of BACnet is that the rules relate specifically to the needs of building automation and
control equipment - for example, how to ask for the value of a temperature, define a fan operating
schedule, or send a pump status alarm.
BACnet provides a standard way of representing the functions of any device - for example analog or
binary inputs or outputs, schedules, control loops and alarms.
The standardized model of a device represents these common functions as collections of related
information called objects
Each object has a set of properties that further describe it. Each analog input, for instance, is
represented by a BACnet "Analog Input object", which has a set of standard properties such as 'Present
Value', 'Sensor Type', 'Location', 'Alarm Limits' etc. Some of these properties are required, while others are
optional.
The only required object in each BACnet controller is the Device object. This object contains the
properties that define the controller’s behavior on the network. Each controller’s Device object has an
associated number called the Device Instance. It is this unique number that allows all other BACnet
devices to unambiguously access the controller.
Here is an illustration of BACnet objects:

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
13
MAN0141 rev 23
BACNET OBJECT TYPES
The BACnet standard defines a number of standard object types, and this number is increasing over time.
Cylon uses the following standard types (* indicates that the object is proprietary):
•Device
•Analog Input
•Analog Value
•Analog Output
•Binary Input
•Binary Value
•Binary Output
•Schedule
•Calendar
•Unitron Schedule *
•Notification Class
•File
•Trend Log
•Manufacturing Object *
BACNET SERVICES
The BACnet standard defines numerous services for interaction between BACnet devices. The following
are supported by Cylon BACnet products:
•ReadProperty
•WriteProperty
•ReadPropertyMultiple
•WritePropertyMultiple
•Read Range
•WhoIs
•IAm
•WhoHas
•IHave
•UnconfirmedPrivateTransfer
•TimeSynchronization
•UTCTimeSynchronization
•DeviceCommunicationControl
•ReinitializeDevice
•AtomicWriteFile
•AtomicReadFile
•AcknowledgeAlarm
•GetAlarmSummary
•GetEventInformation
•ConfirmedEventNotification
•UnconfirmedEventNotification
•SubscriveCOV
•ConfirmedCOVNotification
•UnconfirmedOVNotification

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
14
MAN0141 rev 23
BACNET'S CLIENT / SERVER NATURE
BACnet uses a “Client/Server" architecture. BACnet messages are called service requests. A Client machine
sends a service request to a Server machine that then performs the service and reports the result to the
Client.
Example:
A simple device such as a fixed function VAV controller would typically act as Server.
Front-end software running on a PC would act as a BACnet Client reading status values from the VAV and
changing set-points.
Notes:
Server devices cannot initiate communication. Higher end embedded controllers generally include both
server and client functionality. This allows them to share information such as outside temperature with
each other or send alarms to a PC.
BACnet currently defines 35 message types that are divided into 5 groups or classes. For example, one
class contains messages for accessing and manipulating the properties of the objects described above.
A common message type is the "ReadProperty" service request. This message causes the server
machine to locate the requested property of the requested object and send its value back to the client.
Other classes of services deal with: alarms and events, file uploading and downloading, managing the
operation of remote devices and virtual terminal functions.
NETWORK TYPES
BACnet messages can be carried over the following types of network:
•Ethernet
•ARCnet
•Master-Slave/Token-Passing (MS/TP)
•Point-to-Point (PTP)
•LON
•BACnet/IP

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
15
MAN0141 rev 23
PIC STATEMENT
Every BACnet device is required to have a "protocol implementation conformance statement“ (PICS). A
PICS is a BACnet specification sheet, containing a list of a device's BACnet capabilities.
It contains:
•a general product description
•details of a product's BACnet capabilities
•which LAN options are available
•a few other items relating to character sets and special functionality
The PICS is the place to start to see what a device's capabilities are.
BACNET TOPOLOGY
A typical BACnet Network consists of devices connected to physical networks. Each device is a separate
piece of hardware and has a physical connection to the network. Devices are given a unique Device
Instance Number which can be a number between 0 and 4194302. BACnet MS/TP devices have additional
addressing designations called MAC addresses. For most users it is the Device Instance Number which is
used as a reference, but the combination of the Network Number and MAC address of an MS/TP device
may be configured by a System Integrator to avoid any MAC address conflicts on the EIA-485 network.

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
16
MAN0141 rev 23
BACNET IP BROADCAST MANAGEMENT DEVICE (BBMD)
Some BACnet services use “broadcasts” (e.g. “Who-Is”). On a LAN with standard routers, these
broadcasts are “blocked”. Thus, BACnet broadcasts are limited to the IP Subnet of the BACnet device.
With a BACnet/IP network of 2 or more IP subnets, a device with BBMD can be used.
A BBMD located on an IP subnet monitors the origin of a broadcast message on that subnet and, in turn,
constructs a “peer to peer” message in order to pass through an IP router. This “peer to peer” message is
received by other BBMDs on other IP subnets and transmitted as a broadcast on their attached subnets.
Since the BBMD messages are directed messages, individual messages must be sent to each BBMD. Each
BBMD device maintains a Broadcast Distribution Table (BDT) , the content of which is usually the same for
all BBMDs within the network. BBMDs must know the IP address of all other BBMDs in the network.
It is possible to communicate to a device on a subnet that does not have a BBMD as in the BACnet
Workstation example above. This type of device is called a foreign device since it resides on a different IP
subnet from devices attempting to communicate with it.
Usually, in BACnet/IP, a foreign device is on a different subnet.
The foreign device (e.g. BOWS) registers with each BBMD, after which it can communicate with all other
devices on the network. The BBMD then maintain a Foreign Device Table (FDT) which keeps track of
foreign devices.

CBXi IP Controller | BACnet Networking
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
17
MAN0141 rev 23
BACNET MS/TP DEVICE LOADING
MS/TP (Master-Slave Token Passing) is a protocol where each device is wired in series and they take
turns communicating, depending on which device currently holds a “token”. It is a robust design, and
simpler/cheaper than IP though less flexible in terms of interoperability.
BACnet MS/TP is widely used in building automation, and usually uses RS-485 networking. As a result, the
number of devices that can be connected together (on a “trunk” or “Fieldbus”) is limited by the electrical
load the device puts on the network.
Unit Load is a concept created by the RS-485 specification to help determine how many devices can be
connected to each fieldbus. The number of devices that can be connected depends on how much each
device loads the fieldbus so the more a device loads the fieldbus, the fewer additional devices can be
used. The total Unit Loads on a fieldbus must be 32 or less.
BACnet MS/TP allows 127 master device addresses, but the Unit Loading usually prevents that number of
devices being active on a fieldbus.
READ PROPERTY MULTIPLE
A single BACnet request can contain a sequence of BACnet property references, each representing a
single BACnet property. This allows multiple properties to be read with a single BACnet request.
By default, CBXi will read 5 properties at once.

CBXi IP Controller | CBXi Web UI
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
18
MAN0141 rev 23
4 CBXi Web UI
SUMMARY DASHBOARD
The Summary Dashboard displays the controller status including important information such as firmware
versions and I/O status.
BACNET MENU
DEVICE
The BACnet Device Name and Device ID are set from this page.

CBXi IP Controller | CBXi Web UI
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
19
MAN0141 rev 23
ROUTER NETWORKS
BACnet Network numbers are used to identify the “wire” to which the device is attached.
•For IP, all devices on the local LAN must have the same BACnet Network number.
•For MS/TP devices, each serial bus line must have a unique BACnet Network number.
TIME SYNC
BACnet Time Synchronization messages can be sent from this device to any BACnet device in order to
ensure that those devices have the correct times.
•The Transmit Options control how often and when to send.
•The Destinations list the targets to which the Time Sync messages will be sent.
Time Sync messages can be broadcast to an entire network if desired.

CBXi IP Controller | CBXi Web UI
©ABB 2022 All Rights Reserved.
Subject to change without notice
WWW.CYLON.COM
20
MAN0141 rev 23
BBMD / NAT
BBMD connects BACnet IP networks that are not on the same local network (see BACnet IP Broadcast
Management Device (BBMD) on page 16 for details).
NAT connects sites where there is a NAT gateway between them.