BACnet Network Set Up and Troubleshooting

BACnet
Network Setup and

Troubleshooting Manual
Siemens Industry, Inc.
125-5103
2013-11-14
Restricted
Table of contents
About this Manual .............................................................................................................. 5
Chapter 1 - BACnet Basics ............................................................................................... 6
BACnet Internetwork ............................................................................................................ 6
BACnet Network Numbers................................................................................................... 6
BACnet Device Instance ...................................................................................................... 7
BACnet Data Link Layer ...................................................................................................... 7
BBMD - BACnet/IP Broadcast Management Device ........................................................... 8
Foreign Devices ................................................................................................................... 8
BACnet Objects and Properties ........................................................................................... 8
Chapter 2 - BACnet Firmware/Hardware ....................................................................... 10
Firmware Compatibility Chart ............................................................................................ 10
Hardware Overview ........................................................................................................... 11
Maximum Number of MS/TP Devices per network ........................................................... 12
Chapter 3 - BACnet IP ALN ............................................................................................. 13
Overview ............................................................................................................................ 13
Standard BACnet/IP Networks .......................................................................................... 13
BBMDs ............................................................................................................................ 13
Foreign Device ................................................................................................................... 16
Setting or Modifying the Field Panel IP Configuration ....................................................... 17
Chapter 4 - BACnet MS/TP ALN ..................................................................................... 21
Overview ............................................................................................................................ 21
Rules for BACnet MS/TP ALN ........................................................................................... 22
Adding a BACnet Field Panel as a MS/TP ALN Node ...................................................... 22
Configuring BACnet MS/TP Network Type ........................................................ 22
Modifying BACnet Device Settings .................................................................... 22
Modifying MS/TP ALN Settings .......................................................................... 24
Chapter 5 - BACnet MS/TP FLN ...................................................................................... 26
Overview ............................................................................................................................ 26
MS/TP FLN versus MS/TP ALN ........................................................................................ 27
Adding a BACnet MS/TP PXC Compact 16/24 or UEC to a MS/TP FLN Network ........... 28
Configuring BACnet MS/TP Network Type ........................................................ 28
Configuring a Field Panel as a MS/TP Device ................................................... 28
Adding a BACnet TEC or a Third-party MS/TP Device to a BACnet Field Panel30
Cimetrics MS/TP Router Set Up for Communication with BACnet TECs .......... 36
Chapter 6 - Troubleshooting BACnet Network Using WireShark ............................... 45
Overview ............................................................................................................................ 45
Setting Up Wireshark Capture Software ............................................................................ 45
Starting Wireshark ............................................................................................................. 47
3
Network Setup and Troubleshooting Manual

Restricted
125-5103
2013-11-14
Saving Wireshark Capture ................................................................................................. 51

Wireshark Display Filters ................................................................................................... 52
Building Wireshark Display Filters ..................................................................................... 54
Displaying Wireshark Statistics .......................................................................................... 57
Wireshark Examples .......................................................................................................... 72
Chapter 7 - Wiring Guideline for MS/TP Network ......................................................... 74
Overview ............................................................................................................................ 74
MS/TP 3-Wire Specification* ............................................................................................. 74
3-Wire Network Terminator (550-975P100, Pkg. of 100) .................................................. 75
3-Wire Network RS-485 Reference Terminator (550-974P10 Pkg. of 10) ........................ 76
Network Repeater for 3-Wire Networks ............................................................................. 76
MS/TP 2-Wire Specification ............................................................................................... 78
4

Restricted
125-5103
2013-11-14
About this Manual
About this Manual

This manual is intended to help you understand, commission, and troubleshoot the
Building Automation and Control networks (BACnet) standard data communication
protocol in the APOGEE Building Automation System. The networks that are not
configured properly may results in a variety of BACnet communication issues.
Here is a list of useful documents to help with understanding/configuring BACnet at the
beginning of the manual.
BACnet Application Guide (125-1984)

APOGEE Wiring Guidelines for Field Panels and Equipment Controllers (125-3002)
PXC Modular Series for BACnet Networks Technical Specification Sheet (149-487)
PXC Compact Series for BACnet Networks Technical Specification Sheet (149
206)
PXC-24 Unitary Equipment Controller Technical Specification Sheet (149-837)

Siemens MS/TP Point Pick-up Module Technical Specification Sheet (149-220)
PXM10T and PXM10S Operator Display for Siemens Compact and Modular
Controllers Technical Specification Sheet (149-210)
5

Restricted
125-5103
2013-11-14
Chapter 1 - BACnet Basics

BACnet Internetwork

BACnet Internetwork
A BACnet internetwork is two or more BACnet networks setup to communicate to each
other. The BACnet networks are connected to each other by BACnet routers. There
must only be one path between the two BACnet devices on a BACnet internetwork.
BACnet Network Numbers

Each BACnet network number in a BACnet internetwork must be unique. The range for
BACnet network numbers is 1 through 65534.
If the jobsite does not have a predefined scheme, use the following BACnet network
numbering scheme which is based on Building Field Panel.
NOTE:
Use BACnet Network #1 for the BACnet/IP backbone.
For MSTP FLNs, break the BACnet network range (1 through 65534) into two sections
BBBFF where
BBB is the building number (001 through 418)
FF is the Field Panel number (01 through 99)
Example
Building 65, Field Panel 43 with a MSTP FLN.
The BACnet/IP network number for Building 65 Panel 43 is 1.
The MS/TP network number for Building 65 Panel 43 is 6543.
Example BACnet Network.

6

Restricted
125-5103
2013-11-14

BACnet Device Instance
BACnet Device Instance

Each BACnet device must have a unique Device Instance in a BACnet internetwork.
The range for Device Instance numbers is 0 4194302.
If the jobsite does not have a predefined scheme, use the following Device Instance
numbering scheme which is based on Building Field Panel MSTP Device.
Break the BACnet Device Instance range (0 through 4194302) into three sections
BBBFFMM where
BBB is the building number (001 through 418)
FF is the Field Panel number (01 through 99)
MM is the MSTP/FLN Device number (01 through 99)
Example
Building 65, Field Panel 43 with a MSTP TEC 21.
The Field Panel would be Device Instance 654300.
MSTP TEC 21 would be Device Instance 654321.
BACnet Data Link Layer

BACnet can communicate over various datalinks. The datalinks that BACnet supports
are BACnet/IP, Ethernet, ARCNET, PTP, MS/TP, ZigBee, and LonTalk.
Some of the common protocols are:
IP
Uses the IP protocol
Controller to controller
Controller to HMI
Some field devices
Ethernet 802.3
Raw Ethernet Packets
MS/TP
Field Devices
NOTE:
Native BACnet means that a device supports that functionality/protocol without the
addition of a gateway or other module.
7

Restricted
125-5103
2013-11-14

BBMD - BACnet/IP Broadcast Management Device
BBMD - BACnet/IP Broadcast Management Device

A BBMD is a network application that resides inside of a BACnet/IP device. Its purpose
is to distribute BACnet broadcasts between IP subnets that would typically be blocked
by IP routers. The IP address of the BBMD device must be static.
There are two methods a BBMD may use to distribute messages, which are called 1Hop distribution and 2-Hop distribution.
A BBMD configured for 1-Hop distribution sends a packet with a destination

address that causes the IP Router to broadcast the message on another subnet.
The IP router needs to be configured for direct-broadcast which is not typical.
A BBMD configured for 2-Hop distribution sends a packet to another BBMD that
rebroadcasts the packet on its subnet.
NOTE:
Siemens Industry, Inc. recommends to always use 2-Hop forwarding.
Foreign Devices
A foreign device is a BACnet/IP device that registers with a BBMD device to receive
BACnet broadcast messages for a set period of time. It resides on a subnet that does
not have a BBMD in it. It is typically used for BACnet/IP devices that are not permanent
on the network, like a laptop.
BACnet Objects and Properties

Data inside a BACnet device is organized as a series of objects. Each object has a
type and a set of properties. There is always at least one object in a device it is used
to represent the device itself. The other objects represent the devices data.
Commonly used properties - Almost all objects you encounter will have these (and
more) properties.
Object Type:
Popular Object Types: Analog Input, Analog Output, Binary Input, Binary Output.
Instance Number:
A number that must be not be repeated for any other object of the same type. The
instance number and the object type must be unique for every object in a device.
Name:
Name of device.
Present Value:
The current value of the object. BACnet has ways of telling you if the present value is
valid it uses a property called Reliability.
8

Restricted
125-5103
2013-11-14

BACnet Objects and Properties
BACnet Services
Services are like messages and allow devices to do something.
AddListElement Service. Rarely supported
RemoveListElement Service. Rarely supported
CreateObject Service. Rarely supported
DeleteObject Service. Rarely supported
ReadProperty Service. Always Supported
ReadPropertyConditional Service. Rarely supported - Returns a list of

objects/properties that meet the specified selection criteria. For example, all Analog
Inputs.
ReadPropertyMultiple Service. Often supported
ReadRange Service. Rarely supported
WriteProperty Service. Almost always supported
WritePropertyMultiple Service. Less often supported than ReadPropertyMultiple
9

Restricted
125-5103
2013-11-14
Chapter 2 - BACnet Firmware/Hardware

Firmware Compatibility Chart

Firmware Compatibility Chart
The following table provides a quick reference to the compatible features offered for
each revision. The left column represents the various features of the firmware, and the
top row represents the different firmware revisions. For example, Firmware Revision
3.1 supports MS/TP Routing, Remote Trending, P1BIM, DB Restore from Flash, USB,
Adapt and Wireless FLN.
Compatible Functionalities Each Firmware Revision Supports.
Firmware Rev.
3.2.5
3.2.4
3.2.3
UEC 16
Desigo CC support
Remote Notification
SNMP
Facility To Go
Web Server
PXM 10T/S
File System/AutoSave
Event Enrollment
Hand-Off-Auto
(HOA) b)
MS/TP Routing
Remote Trending
P1BIM
DB Restore from
Flash
USB Support
Adapt
Wireless FLN
a)
3.2.2 a)
3.2
3.1
3.0.1
3.0
a)
Firmware is designed for PXC Series controllers, the features attached to this firmware are for these
specific controllers only.
b)
For PXC Compact Series controllers only.
10

Restricted
125-5103
2013-11-14

Hardware Overview
Hardware Overview
The following table provides a quick reference for hardware supported by BACnet
Firmware and the ALN and FLN options supported by each type of hardware.
Field Panel
PXC Compact 24
PXC Compact 16
ALN
BACnet/IP
FLN
Optional depending on model requires FLN
license
P1 or BACnet MS/TP (Configurable FLN:
controller supports either one P1 FLN or one
BACnet MS/TP FLN).
Supports up to 32 BACnet or P1 TECs on single
FLN network.
BACnet MS/TP
BACnet MS/TP FLN or P1 FLN not supported in

combination with BACnet MS/TP ALN on PXC
Compact.
UEC 16/24
BACnet MS/TP

controller supports either one P1 FLN or one
BACnet MS/TP FLN).
PXC Compact 36
BACnet/IP
Optional FLN requires license for PXC 36

BASE, or included with PXC 36 with FLN and
TX I/O support.
controller supports either two P1 FLNs or one
BACnet MS/TP FLN).
Supports up to 96 BACnet TECs on single FLN
network, or up to 96 P1 TECs among two FLN
networks (that is, up to 48 on each of two FLN
networks). Always match electrical and
performance requirements to number of devices
on FLN.
When FLN is configured for BACnet MS/TP,
then it also supports BACnet MS/TP ALN.
BACnet MS/TP
Optional FLN requires license for PXC 36

BASE, or included with PXC 36 with FLN and
TX I/O support.
controller supports one P1 FLN or one BACnet
MS/TP FLN).
PXC Modular
BACnet/IP and/or
BACnet MS/TP
Three P1 FLNs or one BACnet MS/TP FLN

(Configurable).
Power Open Processor
BACnet/IP
Three P1 FLNs or one BACnet MS/TP FLN

(Configurable)
Power MEC
BACnet/IP
Optional depending on model: Three P1 FLNs

or one BACnet MS/TP FLN (Configurable)
BACnet/IP
Lon-Talk
11

Restricted
125-5103
2013-11-14

Maximum Number of MS/TP Devices per network
The PXC Compact 36 includes (2) RS-485 connections which are marked B and A.
HMI prompt?
ALN
Connection
BACnet/IP
MSTP ALN
MSTP FLN
BACnet/IP
P1 FLN
(FLN2)
P1 FLN
(FLN1)
BACnet
MS/TP
ALN
FLN
S, H, F, C, A, M, M (System, Hardware,
Fieldpanels, Config, Aln, Mstp, Modify)
Some of the BACnet controllers can reside on BACnet IP ALN, BACnet MS/TP ALN or
BACnet MS/TP FLN.
PXC-24 Unitary Equipment Controller
PXC-16 Unitary Equipment Controller
PXC Compact 16
PXC Compact 24
Maximum Number of MS/TP Devices per network

Field Panel
Number of
MSTP FLN
Ports
Max Number of
MS/TP device
per FLN
Number of
MSTP ALN
ports
Max Number of
MS/TP ALN
Devices per
ALN
PXC Modular
96
10
PXC Compact 36
96
10
PXC Compact 16/24
32
Power MBC/Power
MEC
96
12

Restricted
125-5103
2013-11-14
Chapter 3 - BACnet IP ALN

Overview

Overview
BACnet/IP networks are a collection of one or more IP sub networks (IP domains) to
which a single, unique BACnet network number is assigned. You can set up the
software to function as one of the following:
A Standard BACnet/IP or MS/TP device
A BACnet Broadcast Management Device (BBMD)
A Foreign Device
Use the following guidelines to determine the appropriate setup for your installation.
UDP/IP on port 47808 (0xBAC0)
MAC address is IP Address, Port Number
Unicast, Broadcast
BACnet/IP and BACnet Ethernet Share Wire
Standard BACnet/IP Networks

Set up a workstation to function as a Standard BACnet/IP device if the BACnet/IP
network does not span IP routers. A Standard BACnet/IP network consists of BACnet
devices on a single IP subnet.
BBMDs
Many IP routers prevent broadcast messages from being transmitted across a Wide
Area Network (WAN). The BACnet protocol uses broadcast messages called Who-Is
and I-Am to interrogate the network and determine what other BACnet devices exist on
the BACnet Internetwork. For these broadcast messages to be transmitted across IP
routers that block such messages, one device on each IP subnet must be set up as a
BBMD.
Each BBMD has a table called a Broadcast Distribution Table (BDT) which is the same
in every BBMD in a given BACnet/IP network. If the BBMD has also been designated
to register foreign devices as described below, it will also have a Foreign Device Table
(FDT).
13

Restricted
125-5103
2013-11-14

BBMDs
Guidelines/Recommendations
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 workstation to work with.
The Broadcast Distribution Tables must match the list of BACnet devices. If this is
already an operational BACnet network, BBMDs may have been set up by the Network
Administrator/Coordinator. Always consult with your Network Administrator/Coordinator
when setting up BBMDs. There must be only one BBMD per IP subnet. This BBMD
may be a workstation, Siemens field panel or a third-party panel.
BBMDs can only be configured on BACnet/IP networks.
Each workstation that acts as a BBMD for a subnet requires a fixed IP address.
All Broadcast Distribution Tables on all BBMDs on a particular BACnet/IP network

must be identical.
There are two ways that a BBMD may distribute broadcast messages to remote IP
subnets.
Sending directed broadcasts to an IP subnet (also called "one-hop" distribution).

This involves sending the message using a BACnet/IP address in which the
network portion of the address contains the subnet of the destination IP subnet and
the host portion of the address contains all 1's. While this method of distribution is
efficient, it requires that the IP router serving the destination subnet be configured
to support the passage of such directed broadcasts.
Sending directed unicasts to another BBMD (also called "two-hop" distribution).

It transmits the message using the BACnet/IP broadcast address. Since the use of
one-hop distribution requires an IP router configured to pass directed broadcasts
and the two-hop method is always available. Two-hop distribution is strongly
recommended.
14

Restricted
125-5103
2013-11-14

BBMDs
Example
1. A field panel in IP Subnet 1 (10.0.0.x) initiates a broadcast message (such as

WHO-IS) that is received by the other BACnet device and the BBMD on the same
subnet.
2. The BBMD on IP Subnet 1 sees the broadcast and sends a directed unicast
message through the IP routers to the BBMD on IP Subnet 2 (20.0.0.x) and IP
Subnet 3 (30.0.0.x)
3. The BBMDs of IP Subnet 2 and 3 then re-broadcast the message on its respective
network.
If a new BBMD joins the network, the Insight workstation must be rebooted if its
defined as BBMD.
15

Restricted
125-5103
2013-11-14

Foreign Device
BBMD Configurations
BBMD on Computer
No Embedded Panels on Subnet (that is, DataCenter)
Pro:
A computer is more powerful and can handle more communications.
Cons:
Broadcast communications goes down temporarily upon reboot of a computer
Broadcast communications goes down temporarily upon modification of the

BACstac.
BBMD on Field Panel

No computer on Subnet
Pro:
No restart required for BBMD changes.
Con:
Not as powerful as a computer; might slow down control on field panel.
Foreign Device
BACnet devices can be configured as a foreign device if you do not allow the Siemens
field panel to be a BBMD on their network or if a third party device is on a different
subnet and does not support the BBMD function.
May or may not support the BBMD service.
Every foreign device must be subscribed to a single BBMD on another subnet.
Communicate broadcasted message ONLY with the BBMD to which they are
individually subscribed.
Do not re-broadcast message received from their subscribed BBMD to their local
network.
16

Restricted
125-5103
2013-11-14

Setting or Modifying the Field Panel IP Configuration

NOTE:
The field panel coldstarts during this procedure.
HMI
S, H, E, S, M (System, Hardware, Ethernet, ipSettings, Modify)
Prompt / Field
Option/Entry
Description
Node name
Alphanumeric field
Object name of the panel - must be
unique on the entire system.
Site name
Alpha-numeric field
BACnet panels and Insight software
on same IP subnet should have the
same site name. The site name
affects which discovery and
replication times are used.
BLN name
Alpha-numeric field
This must be identical to the System
Name of the BACnet ALN in System
Profile.
DNS suffix
ENTER = continue without entering

data
BACnet field panels do not use
naming resolution.
DHCP
DHCP is enabled
DHCP server is to assign the field
panels IP addresses.
DHCP is disabled
If using fixed IP addresses.
IP address
Numeric field
If DHCP = N, you are prompted for
an IP setting. Enter the IP setting.
If DHCP = Y, you are not prompted
for the IP setting.
Netmask
Numeric field
Gateway address
IP address for the assigned

gateway
If there is no IP gateway, enter
0.0.0.0.
DNS 1
Enter the address of the DNS

server.
This can be obtained from the sites
IT department. If you do not need to
specify DNS addresses, enter
0.0.0.0 for each of these.
DNS 2
DNS 3
DNS 4
17

Restricted
125-5103
2013-11-14

Telnet Enabled
Configure BACnet
Configure BACnet device
Enable BACnet IP ALN
Act as a Foreign Device
Telnet is enabled
To allow remote HMI sessions via
Telnet and to enable FTP
Telnet is disabled
Remote HMI and FTP are blocked.
BACnet configuration options are

displayed.
Exit configuration and save or

discard changes.
Configure BACnet Device.
Device Instance Number
Numeric field.
Valid values are 0 through 4,194,
302 - must be unique on the entire
BACnet site.
Recommended values: 7000 though
7999 for Siemens panels.
Device Location
Alpha-numeric field
Specify a descriptive location so the
customer or other Siemens
employee can locate the device.
Device Description
ENTER = accept existing value

Enter a device description.
Device Reserved Instance Base
ENTER = accept the default of

10,000
Enter the instance number where
the field panel starts creating
BACnet points for FLN devices; this
must be at least 10000.
COV Resubscribe Period (min)
ENTER = accepts default of 30

Enter a number that identifies how
often the field panel and the system
will re-register for COVs.
COV Poll Rate (sec)

Enter a number, in seconds (10 to
3600) that identifies how often the
field panel and the system will poll
devices that do not support the
Subscribe COV BACnet service.
ENTER = default value (10000)
Configure the IP ALN
BACnet IP Network Number
Specify a network, valid values are

1 through 65534.
This network must be unique for the
entire BACnet site.
No other BACnet MS/TP ALN or
BACnet MS/TP FLN or third-party
network number may be the same.
UDP Port
Accept the default BACnet UDP

port, 47808. Other port may be used
if required.
No IP ALN.
A foreign device is a BACnet device

(workstation or field panel) that has
18

Restricted
125-5103
2013-11-14

an IP connection but does not have
a BBMD or multicast router on its
subnet to allow it access to BACnet
broadcast messages. A foreign
device enables itself to send and
receive both directed and broadcast
messages.
Foreign devices are only used when
a BACnet device is joining a
network that spans multiple IP
subnets and it is only going to be on
that network for a short time.
Enable MSTP ALN
P1, Mstp
If the BACnet network does not

span multiple Networks, enter N.
If MS/TP ALN is used, enter Y and

configure the next 3 parameters.
MSTP ALN Baud Rate
Enter the desired baud rate. 38400

is recommended.
MSTP ALN Network Number
Specify a network. Valid values are

1 through 65534.
entire BACnet site. No other
BACnet/IP ALN, BACnet MS/TP
ALN or BACnet MS/TP FLN or thirdparty network number may be the
same.
MSTP ALN Node Address
Enter a MAC address. Valid values

are 0 through 127. Address 0 is
recommended .
This address is the MAC address of
the BACnet/IP to BACnet MS/TP
ALN router. No other device on the
BACnet MS/TP ALN may have the
same MAC address. Other MS/TP
FLNs or MS/TP ALNs may use this
address.
Enter N unless MS/TP ALN is being

used.
Select P for p1.
FLN1 Baud Rate
A typical baud rate is 4800 for TECs

and VFDs. If you are using P1 BIM,
PXC on P1, PXMs, you can specify
another baud rate.
On a PXC Modular, you will be
prompted for the baud rates of all
three FLNs.
FLN2 Baud Rate

FLN3 Baud Rate
Wireless Enabled (Y/N)
If the FLN will be Wireless, specify

Y. Otherwise, specify N.
Select M for MS/TP FLN.
Enable MSTP FLN (Y/N)
Select Y to enable the MS/TP FLN.
MSTP FLN Baud Rate
Enter the desired baud rate. 38.4k is

recommended
19

Restricted
125-5103
2013-11-14

OK to coldstart (Y/N)
MSTP FLN Network Number
Specify a network. Valid values are

1 through 65534. This network must
be unique for the entire BACnet site.
No other BACnet/IP ALN, BACnet
MS/TP ALN or BACnet MS/TP FLN
or third party network number may
be the same.
MSTP FLN Node Address
Enter a BACnet Media Access

Control (MAC) address. Valid
values are 0 through 127. Address 0
is recommended. This address with
be the MAC address of the
BACnet/IP to BACnet MS/TP FLN
router.
No other device on the BACnet
MS/TP FLN may have the same
MAC address. Other MS/TP FLNs
or MS/TP ALNs may use this
address.
MSTP Keep Alive Poll Rate
Enter desired time between live

node scans (10 to 300 seconds) if
different than the default setting.
Accept the default of 60.
MSTP FLN Discovery Poll Rate
Enter the desired time between

dead node scans (10 to 300
seconds) if different than default
setting.
Accept the default of 60.
Coldstart the field panel and save

the configuration.
Do not coldstart - discard any

changes.
20

Restricted
125-5103
2013-11-14
Chapter 4 - BACnet MS/TP ALN

Overview

Overview
Firmware Revision 3.1 and later supports BACnet MS/TP ALN. The BACnet MS/TP
ALN configuration is supported exclusively through the PXC Modular and select PXC
Compact hardware (see PXC Modular Configuration & Sizing Guidelines (145-045)
and PXC Compact Configuration & Sizing Guidelines (145-171)). The PXC Modular
and PXC Compact 36 are the only APOGEE field panels that have simultaneous
support for BACnet/IP ALN and BACnet MS/TP ALN. Therefore, they act as a router
between BACnet/IP and BACnet MS/TP devices, objects, and properties, as specified
by the BACnet standard.
The BACnet MS/TP ALN has the following performance considerations:
In general, faster baud rates will increase performance on the network, so that 76.8
Kbps will perform faster than 19.2 Kbps, for example. However faster baud rates
do increase sensitivity to outside interference on RS-485 wiring. Every device on
the network must support and be configured for the same baud rate.
Since Siemens devices that reside on a BACnet MS/TP ALN are treated as field
panels to be backed up and monitored by the Insight workstation, network traffic
between these devices and the Insight workstation is extensive. This limits the
number of devices that may productively reside on a single BACnet MS/TP ALN
network to approximately 10 devices, depending on point counts and network
activity. Network performance may drop significantly if more than 10 Siemens field
panels are added to the MS/TP ALN.
Additional BACnet MS/TP ALN networks, with different ALN Name, may be added
without compromising network performance through an additional PXC
Modular/PXC Compact 36.
Third-party BACnet MS/TP devices may be added to a BACnet MS/TP ALN without
the consequence of excess traffic.
Each additional device on a BACnet MS/TP network that is set up as a master

(ALN devices must be MS/TP masters) creates another device to pass the token,
which takes time and decreases overall response times. Consider every additional
node on the MS/TP network as adding 1 second to the token pass response time.
Token pass times may exceed 1 second per node depending on the support of
COV and the number of points monitored.
21

Restricted
125-5103
2013-11-14

Rules for BACnet MS/TP ALN
Rules for BACnet MS/TP ALN
Only PXC Modular with Firmware Revision 3.1 and later and the PXC Compact 36
BACnet field panel support the BACnet/IP ALN to BACnet MS/TP ALN router
functions.
Integration drivers are not supported as BACnet ALN routers.
Only one BACnet/IP to BACnet MS/TP router is allowed per ALN.
All BACnet MS/TP ALN devices on an ALN must be on the same physical MS/TP
segment.
A maximum of 10 Siemens field panels, including the Router, can be wired on a

single BACnet MS/TP ALN.
For example, you have two PXC Modular and two PXC Compact 36 field panels on a
BACnet IP network. Each of those supervisory controllers has nine PXC Compact
16/24 connected to the MS/TP ALN port . In this case, you must define four separate
ALNs in System Profile.
Adding a BACnet Field Panel as a MS/TP ALN Node

Configuring BACnet MS/TP Network Type
HMI
S, H, F, C, E, M (System, Hardware, Fieldpanels, Config, nEttype, Modify)
Prompt / Field
Option / Entry
Description
Alnnode, Flnnode
Type A for Alnnode and then press

ENTER
Type F for Flnnode and then press

ENTER
Type Y to coldstart the device and save

the configuration changes
Type N to cancel, all configuration

changes will be lost.
Ok to coldstart (Y/N)
Modifying BACnet Device Settings

CAUTION
If the Device Instance Number or Device Reserved Instance Base are changed, the
field panel coldstarts at the end of this procedure.
NOTE:
To accept the existing value and advance to the next entry field at any step of BACnet
configuration, press ENTER.
22

Restricted
125-5103
2013-11-14

To modify BACnet device settings, type the following letters in sequence and proceed
with the steps:
HMI
S, H, F, C, V, M (System, Hardware, Fieldpanels, Config, deVice, Modify)
Prompt / Field
Option / Entry
Description
Enter the device instance number
(0 through 4,194,302)
Recommended values are 7000 through
7999; must be unique throughout the
BACnet network.
Device Location
Enter the device location
Device Description
Enter the device description
Enter the starting reserved instance

number
Enter the COV resubscribe period in

minutes
COV Poll Rate (sec)
enter the COV poll rate in seconds
For more information on this parameter, see

Device Reserved Instance Base in this
section
This prompt only displays if you change the

Instance Number or Device Reserved
Instance Base.
Y
Coldstart the device and save your

configuration changes
Cancel the configuration
Example
>Point, Application, Time, Message, Cancel, System, passWord,
Bye? s
>Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text,
Quit? h
>Fieldpanels, Ethernet, nodeNametable, Disks, Reportprinter,
Licensemanager, Quit? f
>Log, Display, Add, dElete, Modify, Config, Quit? c
>Hmi, Aln, deVice, db_fiLe, Fln, Names, Defaultlanguage, Quit? v
>Display, Modify, Quit? m
>Device Instance Number
13933--
>Device Location
BIERMAN SUB BASEMENT---------
>Device Description
ABSORPTION CHILLER-----------
>Device Reserved Instance Base :
10000--
>COV Resubscribe Period (min)
30--
>COV Poll Rate (sec)
60--
Command successful
>Display, Modify, Quit? -
23

Restricted
125-5103
2013-11-14

Modifying MS/TP ALN Settings

NOTE:
The field panel coldstarts during this procedure.
For more information on ALN port configuration, see PXC Modular Port Configuration
and PXC Compact Port Configuration.
To modify MS/TP ALN settings, complete the following steps:
HMI
S, H, F, C, A, M, M (System, Hardware, Field Panel, Config, Aln, Mstp, Modify)
NOTE:
If the MS/TP ALN is already enabled, and the BACnet/IP ALN port is either disabled
or not present on this device, the following prompt is not displayed. Under these
conditions, continue this procedure with the following step (MS/TP ALN Baud Rate
prompt).
Prompt / Field
Option / Entry
Description
Enable MSTP ALN (Y/N)
Enables the MS/TP ALN port
Disables the MS/TP ALN port
MSTP ALN Baud Rate
Enter the Baud rate for this port
Enter the network number for this

port, or press ENTER to accept the
current value, if other than 65535
Enter the node address for this port
If you made any changes from

existing values during this
procedure, OK to coldstart (Y/N) is
displayed. Do one of the following:
Coldstarts the device and saves

your configuration changes
Cancels the configuration
The network number must be

changed from the system default of
65535
Example
>MSTP ALN Network Number : 55-->MSTP ALN Node Address : 127
>MSTP ALN Baud Rate : 9600--->OK to coldstart (Y/N) : y
24

Restricted
125-5103
2013-11-14

Devices Instance #7001 is BACnet/IP device and #7002 is BACnet MS/TP ALN device.
Both appear on same level of ALN in System Profile.
25

Restricted
125-5103
2013-11-14
Chapter 5 - BACnet MS/TP FLN

Overview

Overview
Firmware Revision 3.1 or later supports BACnet MS/TP FLN configuration (not
including the BACnet MS/TP Intennjjhg vgration Driver discussed above). The BACnet
MS/TP FLN configuration is supported through the PXC Modular with the FLN
expansion module, PXC Compact with FLN port and FLN license, Power MEC with
FLN, and Power Open Processor. With Firmware Revision 3.1 or later, the FLN may
be configured in the field panel as either a BACnet MS/TP FLN or P1 FLN. When
configured for BACnet MS/TP FLN, physical FLN 1 port is used for communication and
all other FLN ports are deactivated.
The BACnet MS/TP FLN has the following performance considerations:
In general, faster baud rates will increase performance on the BACnet MS/TP
network, so that 76.8 Kbps will perform faster than 19.2 Kbps, for example.
However faster baud rates do increase sensitivity to RS-485 wiring guidelines. Also
a number of microprocessor UARTS of MS/TP device cannot accurately produce
76800 baud signals. Devices using these microprocessors might list 76800 as
supported but you may have network issue. 38.4K Kbps is strongly recommended
for MS/TP network communication.
BACnet MS/TP devices resident on a BACnet MS/TP FLN are treated as FLN
devices with point teams automatically created in the field panel. Point teams are
intended to optimize communication with application specific devices, such as
Siemens BACnet TECs.
Siemens BACnet TECs are supported by the field panel and Insight workstation
with initial values support, and drag and drop reports.
NOTE:
All Programmable TEC and BACnet TEC (Rev Bx20 series) are 1/8 load.
Each additional device on a BACnet MS/TP network that is set up as a master

creates another device to pass the token, which takes time and decreases overall
network response times. Consider every additional node on the MS/TP network as
adding 1 second to the token pass response time. Token pass times may exceed 1
second per node depending on the support of COV and the number of points
monitored. Loading a FLN with the maximum of 96 devices, response times due to
token pass may be approximately 90 seconds.
Each additional device on a BACnet MS/TP network that is set up as a slave

creates another device to poll, which takes time and decreases overall network
response times. Consider every additional node on the MS/TP network as adding 1
second to the poll time which impacts overall response time. Response times may
exceed 1 second per node depending on the number of points monitored. Loading
a FLN with the maximum of 96 devices, response times due to polling may be
approximately 90 seconds. Generally, with Siemens-only devices and low
monitoring requirements, all devices configured as slaves on the MS/TP network
perform faster than all devices configured as masters.
26

Restricted
125-5103
2013-11-14

MS/TP FLN versus MS/TP ALN
In general, expect that BACnet MS/TP FLNs will perform slower than P1 FLNs due
to the following: increased communication requirements for BACnet MS/TP
compared to P1, lack of COV support in many BACnet MS/TP devices (including
BACnet TECs), token passing when MS/TP devices configured as masters require
additional communication time, and high volume of devices on single physical
network which adds to communication time. So despite the significant increased
speed of the BACnet MS/TP baud rate over the P1 baud rate, the actual
communication response is slower due to the factors cited above.
Based on field experience with MS/TP devices connected to a BACnet router, data
transfer speed is decreased as the number of MS/TP devices is increased. When
the number of devices exceeds 50, the data transfer speed becomes unacceptably
slow for most customers. The system may experience slow updates of points
(COVs, Alarms, etc.), and/or frequent device failures and return from failures.
Therefore, it is recommended not to connect more than 50 BACnet MS/TP devices
on a single BACnet network.
MS/TP FLN versus MS/TP ALN

Advantages
You can have more than 10 Siemens field panels reside on a MS/TP FLN whereas
you are limited to only10 Siemens field panels on a MS/TP ALN.
You want to replace a third-party controller that is on the FLN with a Siemens
BACnet field panel and use the same wiring.
With a MS/TP Driver you can add a Siemens BACnet field panel on that FLN.
Disadvantages
You cannot edit the field panels database from the Insight workstation.
The field panel cannot be restored from the workstation if it coldstarts. However, it
can restore its own database using the flash memory Autorestore feature.
If the System Name for points in the child field panel is longer than 12 characters,
then the parent panel will use the ObjectName_InstanceNumber as the name.
27

Restricted
125-5103
2013-11-14

Adding a BACnet MS/TP PXC Compact 16/24 or UEC to a MS/TP FLN Network
Adding a BACnet MS/TP PXC Compact 16/24 or UEC

to a MS/TP FLN Network
NOTE:
BACnet MS/TP PXC-16/24 controller is configured as an ALN node out of factory,
opposed to UEC is configured as a FLN node out of factory.
Configuring BACnet MS/TP Network Type

HMI
S, H, F, C, E, M (System, Hardware, Fieldpanels, Config, nEttype, Modify)
Prompt / Field
Option / Entry
Description
Alnnode, Flnnode
Type A for Alnnode and then press

ENTER
Type F for Flnnode and then press

ENTER
Type Y to coldstart the device and save

the configuration changes
Type N to cancel, all configuration

changes will be lost.
Ok to coldstart (Y/N)
Configuring a Field Panel as a MS/TP Device

NOTE:
Although the UEC has a functional Ethernet port, it does not support BACnet IP ALN.
The IP connection can be used for Telnet, FTP, etc. but must be configured only if
these options are used. (See Steps 3 through 6.)
HMI
S, H, E, S, M (System, Hardware, Ethernet, ipSettings, Modify)
Prompt / Field
Option / Entry
Description
Node name
Alpha-numeric field
Object name of the panel, must be
unique on the entire system.
Site name
Alpha-numeric field
BACnet panels and Insight software on
same IP subnet should have the same
site name. The site name affects which
discovery and replication times are
used.
BLN name
Alpha-numeric field
This must be identical to the System
Name of the BACnet ALN in System
Profile.
28

Restricted
125-5103
2013-11-14

DNS suffix
DHCP
Telnet Enabled
Configure BACnet
Configure BACnet device
ENTER = continue without entering

data
BACnet field panels do not use naming
resolution.
Y
DHCP is enabled
DHCP server is to assign the field
panels IP addresses.
DHCP is disabled
If using fixed IP addresses.
IP address
Numeric field
If DHCP = N, you are prompted for an
IP setting. Enter the IP setting.
If DHCP = Y, you are not prompted for
the IP setting.
Telnet is enabled
To allow remote HMI sessions via
Telnet and to enable FTP
Telnet is disabled
Remote HMI and FTP are blocked.
BACnet configuration options are

displayed.
Exit configuration and save or discard

changes.
Configure BACnet Device.
Numeric field
Valid values are 0 through 4,194, 302 must be unique on the entire BACnet
site.
Recommended values: 7000 through
7999 for Siemens panels.
Device Location
Alpha-numeric field
Specify a descriptive location so the
customer or other Siemens employee
can locate the device.
Device Description
ENTER = accept existing value

Enter a device description.
ENTER = accept the default of 10,000

Enter the instance number where the
field panel starts creating BACnet
points for FLN devices; this must be at
least 10000.

Enter a number that identifies how often
the field panel and the system will reregister for COVs.
COV Poll Rate (sec)
ENTER = accepts the default of 60

Enter a number, in seconds (10 to
3600) that identifies how often the field
panel and the system will poll devices
that do not support the Subscribe COV
BACnet service.
ENTER = default value (10000)
29

Restricted
125-5103
2013-11-14

Enable MSTP ALN
If MS/TP ALN is used, enter Y and

configure the next 3 parameters.
MSTP ALN Baud Rate
Enter the desired baud rate. 38400 is

recommended.
Specify a network. Valid values are 1

through 65534.
entire BACnet site. No other BACnet/IP
ALN, BACnet MS/TP ALN or BACnet
MS/TP FLN or third-party network
number may be the same.
Enter a MAC address. Valid values are

0 through 127. Address 0 is
recommended.
This address with be the MAC address
of the BACnet/IP to BACnet MS/TP
ALN router. No other device on the
BACnet MS/TP ALN may have the
same MAC address. Other MS/TP
FLNs or MS/TP ALNs may use this
address.
Enter N unless MS/TP ALN is being

used.
Coldstarts the field panel and saves the

configuration.
Do not coldstart - discard any changes.
It is strongly recommended that you enable the Auto-Save and Auto-Restore features
since the field panel is now configured as a MS/TP FLN device and can no longer
perform a database transfer with the Insight workstation.
Adding a BACnet TEC or a Third-party MS/TP Device to a

BACnet Field Panel
The following procedure explains how to add a BACnet MS/TP device on the FLN of a
BACnet/IP field panel with Firmware Revision 3.1 and later. It can be performed from
the Insight workstation or from the field panels HMI prompt.
Gathering Information from the BACnet MS/TP Device

The following information is required from each BACnet MS/TP device:
MAC Address
For BACnet TECs (BTECs), the MAC address is also the value of CTLR
ADDRESS (Point 1).
MS/TP Device Instance Number

See the ID field in the BACnet Properties dialog box in WCIS.
Baud Rate
See the Baud Rate drop-down list in the BACnet Properties dialog box in WCIS.
MS/TP Node Type (slave or master)

See the MSTP Slave check box in the BACnet Properties dialog box in WCIS.
30

Restricted
125-5103
2013-11-14

The following Figure is an example of the BTEC information displayed in the WCIS
BACnet Properties dialog box:
MAC Address = 50 (from the value of CTLR ADDRESS (Point 1))
MSTP Device Instance Number = 250205 (from the ID field)
Baud Rate = 38400 bps
MS/TP Node Type = Slave (MSTP Slave option is checked)
BACnet Properties Dialog Box
31

Restricted
125-5103
2013-11-14

Configuring the FLN for MS/TP

From the Insight Workstation
1. In System Profile, double-click BACnet/IP field panel.
2. Go to the FLN Configuration section. From the Type menu, select MS/TP.
3. Click the FLN Settings button.
The MS/TP FLN Settings dialog box displays.
4. Check Enable MS/TP FLN Port.
5. In the Baud Rate drop-down list, select the rate that matches the baud rate of the
BACnet MS/TP device. For more information, see the section Gathering
Information from the BACnet MS/TP Device.
6. In the Network Number field, specify a unique number.
Valid values are 0 through 65534.
This number should not be the same as the BACnet/IP Network Number or any
other network number on the site, including third-party network numbers.
The Virtual BACnet network in the Cimetrics properties has a default network
number of 2. The network number cannot match any network number used for
the MS/TP FLN.
7. Leave the rest of the fields as default in the MS/TP FLN Settings dialog box and
click OK.
8. When the BACnet Field Panel Definition dialog box displays, click OK.
9. Click Yes when prompted with the following message:
The changes made to the panel definition will cause the field
panel to coldstart. Do you wish to proceed?
32

Restricted
125-5103
2013-11-14

FLN Settings Dialog Box
From the Field Panels HMI Port

Point, Application, Time, Message, Cancel, System, passWord, Bye? s
Diagnostics, Users, dSt, Bacnet, Error_msgs, Hardware, Text, Quit? h
Fieldpanels, Ethernet, nodeNametable, Disks, Reportprinter, Licensemanager, Quit? f
Log, Display, Add, dElete, Modify, Config, Quit? c
Hmi, Aln, deVice, db_fiLe, Fln, mBus, Names, Defaultlanguage, Quit? f
fln1, fln2, fln3, Wireless, Mstp, flnType, Quit? m
Enable MSTP FLN (Y/N) : Y
Enter baud rate : 38400---
NOTE: Must be identical to the MS/TP device baud rate. See the Baud Rate
drop-down list in the BACnet Properties dialog box in WCIS.
Network Number : 21---
NOTE: Must be a unique number. Valid values are 1 through 65534. This
number cannot be the same as the BACnet/IP Network Number or any other
Network Number on the site, including third-party network numbers.
MSTP Device Mac Address : 127
NOTE: Field panel's MAC address. Leave it as 127, unless another device on
the network has a MAC address of 127.
Keep Alive Poll Rate : 60---
NOTE: Leave it as the default.
Discovery Poll Rate : 60---
NOTE: Leave it as the default.
Command successful
33

Restricted
125-5103
2013-11-14

Adding the MS/TP Device

From the Insight Workstation:
1. In System Profile, drag and drop a BACnet TEC icon to FLN 1 of the BACnet/IP
field panel.
2. Enter the parameters for the following:
-
System Name and Name: Enter a descriptive name without any special
characters. It does not have to match the Name defined in Device Properties in
WCIS.
Descriptor: (Optional) Enter a description without any special characters.
Graphic Name: (Optional)
Application: Select 65535 for a BTEC; otherwise, enter a number from 10000
through 11999.
Device Instance: MS/TP Device Instance Number. For BTECs this is the value
from the ID field in WCIS.
Network Number: Enter the MSTP Device Network Number. This number must
be identical to the Network Number defined in the MS/TP FLN Settings dialog
box in the procedure Configuring the FLN for MS/TP. Valid values are 1
through 65534. This number must not be same as the BACnet/IP Network
Number.
BACnet MAC Address: Enter the value for the Controller Address point
obtained from WCIS in the procedure Gathering Information from the BACnet
MS/TP Device. Enter the value as a decimal value.
MS/TP Node Type: Select the same MS/TP node type as you obtained from
WCIS in the procedure Gathering Information from the BACnet MS/TP Device.
Initial Value Priority: Select 16 Available 16.
Save Relinquish Defaults: Select this check box for a BTEC. Clear this check
box for third-party devices.
Password: Enter HIGH
34

Restricted
125-5103
2013-11-14

FLN Device Definition Dialog Box
From the Field Panels HMI Port

Point, Application, Time, Message, Cancel, System, passWord, Bye? a
Ppcl, flNdevice, Quit? n
Mstp, Tec, Uc, Quit? m
Log, Display, Edit, Initvalues, Quit? e
Add, Modify, Copy, Delete, Look, Quit? a
Field
Value
--------------------------------------------------------------------------MSTP Device system name
: ASB54A
MSTP Device name
: ASB54A
MSTP Device Instance Number
: 70011
NOTE: This is the number from the ID field in the BACnet Properties
dialog box in WCIS.
Application number : XXXXX
NOTE: Leave this field blank for BACnet TECs (BTECs). For thirdparty devices, valid values are 10000 through 11999
Descriptor
NOTE: You can enter any type of descriptor.
Access group(s)
: <all>
Field panel name
: 70011
NOTE: Device Instance Number of the field panel.
Master, Slave : Slave
NOTE: Can be either Slave or Master.
MSTP Device Network Number : 11
NOTE: Enter a unique number. Valid values are 1 through 65534. It

cannot be the same as the BACnet/IP Network Number or any other
Network Number on the site, including third-party network numbers.
35

Restricted
125-5103
2013-11-14

MSTP Device Mac Address
: 1
NOTE: For BTECs, the MAC address is also the value of CTLR
ADDRESS (Point 1).
Initial Value Priority
: 16
NOTE: For third-party devices, leave this field at 16.
Save Relinquish Defaults
: YES
NOTE: For BTECs, set this field to YES. For third-party devices, set
this field to NO.
Device Init Password
: HIGH
NOTE:
The field panel must be made ready for communications to occur.
Cimetrics MS/TP Router Set Up for Communication with

BACnet TECs
The Cimetrics B6000 Router allows the BACnet MS/TP TEC and third-party MS/TP
devices to communicate with an Insight BACnet Client by converting BACnet/IP to
BACnet MS/TP. This following procedure covers the entire setup procedure for the
Cimetrics B6000 Router, the BACnet TEC configuration, and the Insight workstation
configuration. The MS/TP Router specifically refers to the Cimetrics B6000 BACnet
MS/TP router, whereas router refers to generic BACnet routers.
The following procedures are for configuring the MS/TP Router:
Gathering Necessary Information
Wiring and Network Electrical Considerations
Setting the MS/TP Router Terminations
Connecting to the MS/TP Router with a Computer for Configuring
Configuring the MS/TP Router BACnet/IP Settings
Configuring the MS/TP Router MS/TP Settings
Confirming the MS/TP Router Settings
Configuring the BACnet TECs
Establishing Communication with the Insight workstation
The Configuring the BACnet TECs procedure may be performed before Setting the
MS/TP Router Terminations through Configuring the MS/TP Router Settings (in the
case that the BACnet TECs are available before the MS/TP Router).
Gathering Necessary Information

Physical Network (DNET) Setting Numbers, UDP Port Number, BTEC Object Names
and Object IDs.
Before going to the job site, be sure to obtain the BACnet TEC startup document(s) for
your application(s). Those documents are available at:
http://iknow.us.abatos.com/customsolutions/HVAC_main.asp
Beacon: https://inet.sbt.siemens.com/customsolutions/HVAC_main.asp
36

Restricted
125-5103
2013-11-14

To configure the MS/TP Router, it is necessary to assign it two physical network

numbers, one for each of the following:
The BACnet/IP network
The MS/TP network
Cimetrics refers to the physical network numbers as DNET numbers. These DNET
numbers must be configured properly or communication cannot be established.
In addition, it is also necessary to know the UDP port number that is being used, since
this must be configured at both the router and at the Insight BACnet workstation. This
process assumes the Cimetrics router will be used in conjunction with an Insight
workstation. If it is used with another third-party system, you must find the physical
network number(s) the third-party system uses.
Physical Network (DNET) Setting Numbers and UDP Port Number

To determine which network numbers and which UDP port number to use, if there are
no third-party BACnet vendors present, do the following at the Insight workstation: This
procedure assumes you have already followed the Setting Up BACnet in the Insight
Online Documentation under Getting Started.
1. Click Start, Settings, Control Panel, and then double-click Network Connections.
2. Right-click the connection that represents the Network Interface Card that is bound
to the BACstac Protocol, and then click Properties.
3. Select Cimetrics BACstac(TM) Routing Edition v4.2 Protocol, and then click
Properties.
4. Make a note of the following:
Physical Network number for the BACnet/IP network to which you intend to
connect the router. This is located in the Network Num column. This number will be
used as the Routers BACnet/IP DNET number.
The UPD Port number. This number will be used in the BACnet/IP configuration of
the B6000 Router. It is usually set to 47808.
The network numbers of any other networks in the Cimetrics BACstac(TM) Routing
Edition v4.2 Protocol. When you configure the MS/TP Routers MS/TP settings,
make sure neither the BACnet/IP DNET number nor the MS/TP DNET number is
the same value as any of the physical network or virtual numbers defined for the
Insight workstation.
To determine which physical network numbers and which UDP port number to use, if
the third-party BACnet vendors are present, then ask the following questions:
Which physical network numbers are being used for the BACnet/IP network?
Use this network number for both of the following:
The Routers BACnet/IP DNET number.
The Insight BACnet workstations BACnet/IP network number.
Which physical network and virtual numbers they are using for other networks?
Do not use these network numbers in the routers configuration or for the Insight
BACnet workstations Cimetrics Setting.
Which UDP port they are using? The UPD port 47808 is the default, but
sometimes, other ports may be used.
37

Restricted
125-5103
2013-11-14

BTEC Object Names and Object IDs

Be sure to consult with the customer or third-party vendor to determine the best
naming convention for the BTEC Object Names and Object IDs on the MS/TP network.
The names are determined in the same way as standard APOGEE Automation System
names. The Object IDs are usually in a range reserved for this type of device. If the job
is small, the Object IDs can be in any range. However, if there are several BACnet
devices on the network, an organizational spreadsheet should be used to keep an ID
from being accidentally reused.
Wiring and Network Electrical Considerations
All BACnet TECs must be daisy chained. No T-Taps are allowed.
The end of every segment must be terminated. The end of a segment is any FLN
connector with only one set of wires connected to it. The following are different
ways to terminate segment ends:
The MS/TP Router is terminated by placing the termination jumpers (see

Setting the Router Termination).
The recommended wiring is our standard ALN/FLN wiring, 24 gauge, Cat 5,

twisted, shielded pair, low capacitance (12.5 pF/ft.), available from Anixter. See
the Field Purchasing Guide for more information.
Terminate the last TEC with an ALN Trunk Terminator (Part Number 538-664).
Terminate all FLN connectors that connect to an HSTIE by setting the Trunk
Termination Switch (inside the HSTIE enclosure) for that FLN connector to an
End of Line (EOL). Do not add an ALN Trunk Terminator. If there are two sets
of wires in one FLN connector, the Trunk Termination Switch should be set to
Normal (NRML).
HSTIEs are required if more than 31 of the older BACnet TECs are used. For
BACnet TECs sold after November 2005, a maximum of 50 TECs can be placed
on a single router without any HSTIE. Additional TECs can actually be used, but
over 50 is not recommended because change of values (COVs) will update slowly.
To determine if the BACnet TECs are the type that allows more than 31 on a segment,
locate the chip labeled U16 on the board, which is about 1-inch above terminations 7
and 8. If the TEC is the newer type, the marking MAX3085 is printed on the chip. The
older types of TECs have a series of numbers printed on them, but not "MAX3085".
The E terminal of the power connector for all BACnet TECs must be connected to
earth ground. If the E terminal is not connected to earth ground, the BACnet TECs
could potentially lock up and stop communicating.
Connect the shield wire to every BACnet TEC and to the MS/TP Router.
38

Restricted
125-5103
2013-11-14

Setting the Router Termination

Only perform this procedure if the router is at the end of a segment (which means, the
routers MS/TP connector has only one set of FLN wires connected to it).
1. Unplug all connections to the router, including power.
2. With a small Phillips screwdriver, remove the four screws on the sides of the router.
3. Remove the top cover.
4. Move the three jumpers near the green MS/TP connector on J5 from Spare to
Terminated.
Termination Jumper Placement inside the Cimetrics B6000 Router.

5. Place the cover back and tighten the four screws.
6. Reconnect the power supply. Leave the Ethernet and MS/TP connectors
disconnected.
39

Restricted
125-5103
2013-11-14

Connecting to the Router with a Computer for Configuring

1. Obtain an Ethernet Crossover cable or an Ethernet hub and two Ethernet patch
cables.
2. Configure your laptop computer or another computer to have a fixed IP address of
192.168.88.90 with a subnet mask of 255.255.255.0. To do so, perform the
following steps (these steps assume you have Windows XP):
-
Click Start, Settings, Control Panel, and then double-click Network

Connections.
Right-click on the Connection that represents your Network Interface Card, and
then click Properties.
Select Internet Protocol (TCP/IP), and then click the Properties button.
Select Use the Following IP Address.
- Type the following:

IP address 192.168.88.90
Subnet Mask 255.255.255.0
-
Click OK to the Internet Protocol (TCI/IP) Properties dialog box.
Click OK to the Local Area Connection Properties dialog box.
Close the Network Connections window.
3. Disable the ISA Firewall Client by right-clicking on the ISA Firewall Client icon in
the system tray in the lower right corner of the screen and selecting Disable.
ISA Firewall Client Icon.

4. Open Internet Explorer. Type http:// 192.168.88.89 in the Address box and press
ENTER.
5. The MS/TP Router prompts you for a User Name and Password. Type admin for
both the username and password.
Configuring the Router BACnet/IP Settings [Not released]

1. Log on to the B600 Web interface, click on BACnet/IP settings.
2. Enter the desired IP address for the router.
3. Set Network Mask, type the desired subnet mask for the router.
Make a note of the MS/TP Routers IP address and Subnet Mask for your records.
4. Set UDP Port, use 47808, unless you are not using the default BACnet port.
5. Set DNET, type the Physical Network number you obtained from Procedure 1; this
should match the physical network number of the Insight workstations BACstac
properties.
6. Click Save.
40

Restricted
125-5103
2013-11-14

Configuring the Router MS/TP Settings

1. Click MS/TP Settings.
2. Configure the baud rate. The recommended baud rate is 38400 bps.
A baud rate of 76800 bps does not work with HSTIEs.
-
Set the value of This Station (MAC), to a value from 1 through 127, that is not
equal to any of the ADDRESS (1) subpoints of any BACnet TECs. The MS/TP
Router is actually a node on the MS/TP network, similar to TECs. If the MAC
address of the MS/TP Router were the same as one of the BACnet TECs, the
network would not communicate properly and the BACnet TECs would fail.
Set Max Info Frames to a value of 1.
Set Max Master to 127. This sets the highest MAC address the MS/TP Router
can poll. As a general rule, this should be at least the value of the highest TEC
address on the network if it is not, the TECs cannot communicate.
Set Reply Timeout to 255 mS.
Set Usage Timeout to 20 mS.
Set DNET to a unique value. This value must be different from the following:
The DNET parameter on the BACnet/IP settings.
The Insight workstation's Cimetrics Network numbers (physical and virtual).
The networks for any other router or Insight workstation.
Click Save.
Confirming the Router Settings

1. Click Activate Configuration.
2. Click Confirm.
The following message displays: Confirmation saved. Now rebooting the
device.
3. Close Internet Explorer.
4. Disconnect the Ethernet cable that was used for configuring and connect the cable
that will be used to connect the MS/TP Router to the Insight workstation.
5.
From the Insight workstation, click Start, Run, type CMD and then press ENTER.
6. Verify that the Insight workstation has Ethernet connectivity to the MS/TP Router.
Type PING [IP address of MS/TP Router] and then press ENTER.
7. If you need to verify settings from the Insight workstation, open Internet Explorer
and type http://[IP address of MS/TP router]in the address box and then press
ENTER.
The MS/TP Router configuration Web page can still be contacted from a computer
whose IP address is 192.168.88.90 by typing http://192.168.88.89 in the address box
of Internet Explorer. This method works even if the MS/TP router has been configured
with a different IP address. This is useful if the IP address of the MS/TP Router is
unknown.
41

Restricted
125-5103
2013-11-14

Configuring BACnet TECs

Perform the following procedure at all BACnet TECs.
1. Connect to the BACnet TEC with WCIS 2.1.4 or later through the TECs HMI port.
-
WCIS 2.1.4 is available on the Field Support Web site:

http://iknow.us009.siemens.net/fieldsupport/WindowsCIS.asp
From Beacon: https://inet.sbt.siemens.com/fieldsupport/WindowsCIS.asp
2. Set the communications baud rate to 1200 bps.

3. Click Device, and then Connect.
4. Set the MAC address of the BACnet TEC by overriding the point ADDRESS (1), to
the desired value.
NOTE: Do not leave more than one BACnet TEC that has not been addressed
connected to the network. The default address of 99 is a valid BACnet address.
Therefore, if you leave more than one BACnet TEC connected with an address of
99, you will have duplicate addresses, and you will be unable to establish
communication.
5. Set APPLICATION (2) to the desired application.
6. Follow the remaining procedures in the Startup Documents with the exception of
Configuring BACnet Parameters section:
-
http://iknow.us.abatos.com/customsolutions/HVAC_main.asp
From Beacon: https://inet.sbt.siemens.com/customsolutions/HVAC_main.asp
7. Save TEC initial values using the backup feature in WCIS 2.1.4. Neither the MS/TP
Router nor the BACnet MS/TP Driver has the ability to back up or restore initial
values.
8. Click the Device drop-down menu. The WCIS software pauses and the mouse
pointer may change to an hour glass.
9. Click on Device Properties. Again, there may be a pause.
10. Set Object Name to a unique name (12-character limit).
11. Set the Object ID to a unique value from 0 to 4194303.
NOTE: Object ID is not the MAC address; it is a higher-level address within the
BACnet MS/TP protocol (device instance number).NOTICE!
12. Type a Description for the controller (60-character limit). (Optional)
13. Type a Location describing the physical location of controller (60-character limit).
(Optional)
14. Set CIS/MMI Command Property to a value 8.
15. If the TEC is connected to an MS/TP Router and metric units are desired, select
the Metric Units check box.
16. Set the baud rate to match Baud Rate of the MS/TP Router. The options for baud
rate are; 9600, 19200, 38400 or 76800. The default is 19200.
NOTE: HSTIEs cannot be configured for 76800 bps. It is recommended to
configure the BACnet TECs to a baud rate of 38400 bps.
42

Restricted
125-5103
2013-11-14

17. Configure the controller for MSTP Master or Slave. To determine which to use,
consider the following:
-
Use Master if you will be referencing several of the BACnet TEC points in
PPCL. If you select Master, you can use the BACnet TEC point names in
PPCL, such as [ObjectName]Room Temp.
Use Slave if you are concerned with performance, specifically the rate at which
the BACnet TECs update. To use the BACnet TEC point names, such as
[ObjectName]Room Temp in PPCL, you must manually type the name in the
BACnet address table from System Profile or the field panel HMI, or use a fully
qualified BACnet object name, such as 70001_AI_4.
If the customer requests Metric Units, select the Metric Units check box.
Click the Write button.
Initialize the TEC, or cycle power to it.
18. Follow the procedures in the BACnet TEC startup document(s) for your application.
Those documents are available at.
http://iknow.us.abatos.com/customsolutions/HVAC_main.asp.
Establishing Communication with an Insight Workstation

1. If the BACnet TECs are configured for MS/TP Slave, change the value of the
registry key PingByReadPropertyFrequency to a value of 4. To do this:
-
Click Start, Run, and type regedt32 and press ENTER.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\LANDIS &

GYR\Insight\CurrentVersion\BACnet\Client\.
Double-click PingByReadPropertyFrequency, and change the value from 0

(default) to 4. Click OK.
Exit Regedt32.
2. Once all the BACnet TECs have been configured, connect the MS/TP connector to
the MS/TP Router.
3. Open System Profile at the Insight workstation.
4. If there is not already one present, create a BACnet ALN.
5. Do one of the following:
-
If the TECs are configured for MS/TP master, click Enable BACnet Discovery in
System Profile, and then click Send Who Is.
If the TECs are configured for MS/TP Slave or you want to specify the System
Name of the TECs, manually add the BACnet TEC. To do this, drag-and-drop a
field panel on the ALN for each TEC.
6. Set the Device Instance Number equal to the TEC device instance number (Object
ID) in Configuring BACnet TEC, Step 11.
7. Assign a unique System Name and Name.
43

Restricted
125-5103
2013-11-14

8. If you are not using BACnet Discovery, manually add a TEC. To do this, drag-anddrop a field panel on the ALN for each TEC.
-
Set the Device Instance Number equal to the TEC device instance number
(Object ID) in Configuring BACnet TEC, Step 11.
Assign a unique System Name and Name.
9. Using Database Transfer, upload each BACnet TEC.

10. Run a Point Log report to verify that all of the BACnet TECs are communicating.
44

Restricted
125-5103
2013-11-14
Chapter 6 - Troubleshooting BACnet Network Using WireShark

Overview
Chapter 6 - Troubleshooting BACnet Network

Using WireShark
Overview
Wireshark is an open source network analyzer. This is a software application that can
be used to capture, view, and save network traffic for the purpose of troubleshooting
network communication problems including BACnet (BACnet/IP, BACnet Ethernet, and
BACnet MS/TP).
Installation
Wireshark can be installed on most Microsoft operating systems running Windows XP,
Windows Server 2003, Windows Vista, Windows 2008, Windows 7, and Windows 2008
R2.
You can download a copy of the latest Wireshark application from
http://www.wireshark.org/.
During the Wireshark installation, two components are installed:
Wireshark Application for configuring the capture filters, setting capture

parameters, displaying frames, decoding frames, producing graphs, tables, and
statistics.
Winpcap Drivers used to capture packets off the NDIS interface.
Setting Up Wireshark Capture Software

Install Wireshark on a computer running BACnet software, for example an Insight
workstation.
1. Capture all IP network packets on an Insight workstation.
2. Capture all IP network packets on a specific field panel using an Ethernet hub.
Install Wireshark on laptop computer and connect to the Ethernet network using a true
hub so that the laptop computer will get all packets received and delivered from the
perspective of the field panel. See Figure Switched Media (with Hub).
NOTE: Unlike switches, when routing data, hubs broadcast the data to all of their ports
knowing that the correct recipient will receive it.
45

Restricted
125-5103
2013-11-14

Setting Up Wireshark Capture Software
True hub models that are known to work:
Netgear DS104
Netgear DS108
Netgear GS108NA
Netgear GS105?
Advantage - Cheap and easy to install.

Disadvantage - Reduces link to half duplex and is not practical on servers or switch
uplink.
Capture all IP network packets on a specific field panel using a switch with port
mirror.
Install Wireshark on laptop computer and connect to the Ethernet network using a
switch with port mirroring capabilities. Using the switch management, you can select
both the monitoring port and assign a specific port you wish to monitor. Actual
procedures vary between switch models and you may need to use a terminal emulator,
specialized SNMP client software or (more recently) a Web browser.
46

Restricted
125-5103
2013-11-14

Starting Wireshark
Switch model that is known to work:
Netgear GS108E
Advantage - Does not require link to be dropped and great for one-time link monitoring.
Disadvantage - Requires switch access and configuration.
Capture all MS/TP network packets using a Serial to RS-485 adaptor.
Install Wireshark on laptop computer and connect to the RS-485 network using a Serial
to RS-485 adapter.
Starting Wireshark
1. Click Start, Programs, Wireshark.
The main window displays.
2. The two main menus you will use are:

-
File. The File menu allows you to open, save, and export capture files.
Capture. The Capture menu allows you to start and stop a capture, as well as
select a network interface where you want capture data to reside on.
47

Restricted
125-5103
2013-11-14

Starting Wireshark
Starting and Stopping Wireshark Capture for an IP Network

1. To start a capture, select Interfaces from the Capture drop-down menu.
The Capture Interfaces dialog box displays.
2. Select the network card you want to capture data from by using the radio buttons
on the left side and then click the Start button.
3. The data packets will display in the main window.
4. Select Stop from the Capture menu, to stop the capture.

48

Restricted
125-5103
2013-11-14

Starting Wireshark
Starting and Stopping Wireshark Capture for MSTP network using

MSTPCAP
1. From Command Prompt, type the following:
MSTPCAP <COM> <BAUD> <WindowsPipe>
where <COM> syntax is COMx where x is port, for example COM2 or COM12.
where <BAUD> syntax number equal to baud (19200, 38400, etc)
where <WindowsPipe> is \\.\pipe\wireshark
MSTPCAP creates capture files in the following format:
Mstp_YYYYMMDDHHMMSS.cap (YearMonthDayHourMinuteSeconds)
NOTE: There is a packet counter that increments every 100 packets. If counter
stays at 0, check ComPort and Baud settings.
-
2. After running MSTPCAP with a WindowsPipe, start Wireshark.

3. Select Options from the Capture menu.
4. In the Interface field, enter WindowPipe (use from MSTPCAP command line).
5. Click the Start button.

The data packets will display in the main window.
6. Select Stop from the Capture menu to stop capture.
NOTE: After stopping Wireshark capture, you must also stop MSTPCAP by using
CTRL-C in Command Prompt.
7. The data packets will display in the main window.
49

Restricted
125-5103
2013-11-14

Starting Wireshark
8.
Select Stop from the Capture menu, to stop the capture.
50

Restricted
125-5103
2013-11-14

Saving Wireshark Capture
Saving Wireshark Capture

NOTE:
You can only save a capture that is not actively running.
1. To save the data packets, select Save-As from the File menu.
The Wireshark Save file as dialog box displays.
2. To save all the packets, select the All packets and Captured radio buttons in the
Packet Range section.
3. Navigate to the folder location where you want to save the captures, type in a
filename, and then click Save.
51

Restricted
125-5103
2013-11-14

Wireshark Display Filters

Display Filters are used to view only the packets that you want to see and hide the
packets you dont want to see. You do this by building a filter expression in the filter
toolbar.
To build a filter expression, you will use a combination of Comparison operators,

Logical operators, common keywords, and values. The following tables are the most
commonly used operators, keywords, and values used to build expressions.
Comparison Operators
Description
Wireshark syntax
English syntax
Equal
==
eq
Not equal
!=
ne
Greater than
>
gt
Less than
<
lt
Greater than or equal to
>=
ge
Less than or equal to
<=
le
Wireshark syntax
English syntax
&&
and
Or
or
Not
not
Logical Operators
Description
And
Common keywords MAC address

Description
IP Address
Wireshark syntax
ip.addr
Source IP Address
ip.src
Destination IP Address
ip.dst
MSTP Source MAC
mstp.src
MSTP Destination MAC
mstp.dst
52

Restricted
125-5103
2013-11-14

Common keywords BACnet

Description
Wireshark syntax
Only BACnet Packets
bacnet
BACnet Object Type
bacapp.objectType
BACnet Object Instance
bacapp.instance_number
BACnet Confirmed Service
bacapp.confirmed_service
BACnet Unconfirmed Service
bacapp.unconfirmed_service
BACnet Object Type Values

Object Type
Value
Analog Input
Analog Output
Analog Value
Binary Input
Binary Output
Binary Value
Calendar
Command
Device
EventEnrollment
MultiState Input
13
MultiState Output
14
MultiState Value
19
BACnet Confirmed Service Values (that is, bacapp.confirmed_service == xx)

Object Type
Value
confirmedCOVNotification
confirmedEventEnrollment
SubscribeCOV
ReadProperty
12
ReadPropertyMultiple
14
WriteProperty
15
WritePropertyMultiple
16
ConfirmedPrivateTransfer
18
53

Restricted
125-5103
2013-11-14

Building Wireshark Display Filters
BACnet Unconfirmed Service Values (that is, bacapp.unconfirmed_service == xx)

Object Type
Value
I-Am
I-Have
unconfirmedCOVNotification
unconfirmedEventNotification
Who-Has
Who-Is

Building Display Filter Expression
You build a Display Filter by using the Filter Expression dialog box.
1. Select the Expression on the toolbar.

The Filter Expression Profile:Default dialog box displays.
2. Select Field name, Relation, and Value to build the expression.

For BACnet, the following Field name sections are useful:
BACapp - Building Automation and Control Networks APDU
BACnet - Building Automation and Control Networks NPDU
BACnet MS/TP BACnet MS/TP
54

Restricted
125-5103
2013-11-14

Building Display Filter Packet Details Pane

1. Right-click the Packet Detail pane.
2. Select a packet you want to filter on in the Packet List pane.
3. Right-click the part of the packet you want to filter on in the Packet Details pane.
4. Select Apply as Filter.
5. Select the appropriate Logical Operator syntax.
The result is a Display Filter of bacapp.confirmed_service == 15, which results
in only displaying WriteProperty packets.
Exmple
Packet 167 was selected from the Packet List.
The Service Choice: WriteProperty (15) was highlighted in the Packet Detail pane.
The Logical Operator syntax Selected was selected..
55

Restricted
125-5103
2013-11-14

The result is a Display Filter of bacapp.confirmed_service == 15 which only displays

WriteProperty packets.
56

Restricted
125-5103
2013-11-14

Displaying Wireshark Statistics

This procedure allows you to display the statistics on all the packets you have captured
and statistics for any packets that meet the Display Filter criteria you have defined.
To display the summary, select Summary from the Statistics menu.

The Summary dialog box displays.
57

Restricted
125-5103
2013-11-14

Using Filter Expressions to Display COV Traffic
To define a filter that displays all COV traffic:

-
Filter expression: bacapp.confirmed_service == 1 && !(bacapp.type == 2)
58

Restricted
125-5103
2013-11-14

The Summary dialog box displays a total of 4.978 COVs per second being sent.
59

Restricted
125-5103
2013-11-14

To define a filter that only displays packets from a source IP address of

192.168.1.125:
-
Filter expression: bacapp.confirmed_service == 1 && !(bacapp.type == 2) &&

(ip.src == 192.168.1.125)
60

Restricted
125-5103
2013-11-14

61

Restricted
125-5103
2013-11-14

The Summary dialog box displays statistics of 4.444 COVs per second from IP address
192.168.125.
62

Restricted
125-5103
2013-11-14

To define a filter that only show packets from Binary Value, 123:
-

(ip.src == 192.168.1.125)&& (bacapp.objectType == 5) &&
(bacapp.instance_number == 123)
63

Restricted
125-5103
2013-11-14

The Summary dialog box displays statistics of 4.089 COVs per second from Binary
Value 123.
64

Restricted
125-5103
2013-11-14

Using Filter Expressions to Display Alarms
To define a filter that displays all the alarms:

Filter expression: bacapp.confirmed_service == 2 && !(bacapp.type == 2)
65

Restricted
125-5103
2013-11-14

The Summary dialog box displays statistics of a total of 2.703 alarms per second being
sent.
66

Restricted
125-5103
2013-11-14

To define a filter that only displays alarms from a source IP address of

192.168.1.125:
(ip.src == 192.168.1.125)
67

Restricted
125-5103
2013-11-14

The Summary dialog box displays statistics of a total of 2.339 alarms per second from
IP address 192.168.1.125.
68

Restricted
125-5103
2013-11-14

To define a filter that only displays alarms from a Binary Value, 444:
(ip.src == 192.168.1.125)&& (bacapp.objectType == 5) &&
(bacapp.instance_number == 444)
69

Restricted
125-5103
2013-11-14

The Summary dialog box displays statistics of 1.967 alarms per second from Binary
Value 444.
70

Restricted
125-5103
2013-11-14

Using Filter Expressions to Find Duplicate BBMD/Broadcast Storms
To define a filter that only displays broadcasts generated by BBMDs:

Filter expression: bvlc.function == 0x04 && ip.dst == 10.0.0.255
Both 10.0.0.19 and 10.0.0.54 are configured as BBMDs on the same subnet.
71

Restricted
125-5103
2013-11-14

Wireshark Examples
The Summary dialog box displays statistics of 191.567 broadcasts per second
occurring on this subnet.
Wireshark Examples
It is important to ensure that each segment on the network has only one BBMD
defined. Having multiple BBMDs on the same segment will cause excessive traffic and
system response to be sluggish.
Network analyzer Wireshark can be used to troubleshoot issues with multiple BBMDs
in a segment. The screenshots below are an example on how to accomplish this.
The two packets in Figure 1 below look suspicious since both 158.132.217.98 and
158.132.217.70 are broadcasting a Who-IS message to the same network segment
(158.132.217.255). Typically only a BBMD will broadcast to a network segment.
Figure 1
Figure 2 below is packet 2569 expanded. The source of this packet is 158.132.217.98.
You can see by looking at the section Device Instance Range Low Limit that this is a
broadcast to find an object with an instance number of 30109.
Under the section BACnet Virtual Link Control, the Function shows Forwarded-NPDU
and the IP shows 158.132.217.61. This indicates that 158.132.217.98 forwarded this
packet to all devices on the 158.132.217.255 network on behalf of 158.132.217.61 who
is the originator of this packet.
72

Restricted
125-5103
2013-11-14

Wireshark Examples
The fact that 158.132.217.61 forwarded this packet indicates that it is a BBMD device.
Figure 2
Figure 3 below shows packet 2570 expanded. It shows the source of this packet is
158.132.217.70. You can see by looking at the section Device Instance Range Low
Limit that this is a broadcast to find an object with an instance number of 30109.
Under the section BACnet Virtual Link Control, the Function shows Forwarded-NPDU
and the IP shows 158.132.217.61. This indicates that 158.132.217.70 forwarded this
packet to all devices on the 158.132.217.255 network on behalf of 158.132.217.61 who
is the originator of this packet. The fact that 158.132.217.70 forwarded this packet
indicates that it is a BBMD device.
Figure 3
This indicates that both 158.132.217.70 and 158.132.217.98 are BBMD devices on the
same segment.
73

Restricted
125-5103
2013-11-14
Chapter 7 - Wiring Guideline for MS/TP Network

Overview

Overview
1.5-Pair Network Cable. The network cable recommended for use with the 3-wire
(isolated RS-485 common) is a single pair cable with third wire (1.5-pair) that is used to
tie the RS-485 reference (communication common) of all the nodes on the network
together.
By providing the RS-485 ground signal of the interface to the network termination
plug, all node communication ports can be referenced together providing a high
degree of noise immunity.
The RS-485 common reference wire is terminated at one point (and only one point)
to earth ground.
An overall foil shield and drain wire provide additional noise protection.
MS/TP 3-Wire Specification*

Cable configuration
1.5-Pair (1 TP & 1 Conductor) w/overall Shield and

drain wire
Gauge
24 AWG (stranded)
Capacitance
11 pf/foot (conductor to conductor)

24 pf/foot (conductor to shield)
Twists per foot
4 minimum
Shields
100% foil with drain wire
NEC class
UL listed, CM, CMP (75C or higher)
CEC class
FT4, FT6 (75C or higher)
Required for BACnet MS/TP network that use the 3-wire interface.
74

Restricted
125-5103
2013-11-14

3-Wire Network Terminator (550-975P100, Pkg. of 100)
3-Wire (1.5-pair) Network Wiring Detail.
3-Wire Network Terminator (550-975P100, Pkg. of

100)
The 3-wire network requires a new network terminator. The new terminator is a 120
ohm 1/2W carbon composition resistor. One terminator must be placed at each end of
the 3-wire network section.
75

Restricted
125-5103
2013-11-14

3-Wire Network RS-485 Reference Terminator (550-974P10 Pkg. of 10)
3-Wire Network RS-485 Reference Terminator (550974P10 Pkg. of 10)

The nodes that use a 3-wire network interface must have the RS-485 reference wire
(yellow) of the network cable terminated to EARTH GROUND at ONE END ONLY
through an RS-485 reference terminator (shown below). The RS-485 reference
terminator consists of a PTC thermistor (polyfuse device) and wire to allow connection
to earth ground. A PTC was chosen in case the third wire of the network cable, (the
common reference between all 3-wire nodes), is accidentally grounded to earth ground
at a second location that could cause high ground currents to flow, due to a difference
in earth ground potential. The PTC would open during the short condition if large
currents start to flow in the reference wire. Without the PTC or 100 ohm resistor,
sufficient current could flow to damage the cable. The PTC will return to normal
resistance (less than 1 ohm) when the fault condition is removed.
Before the RS-485 reference terminator is installed, the third wire (yellow) must be
tested with a DMM to insure it is not already connected to earth ground. If the wire is
connected to earth ground the fault condition must be remedied before terminating the
wire using the RS-485 reference terminator.
Network RS-485 Reference Terminator.
Network Repeater for 3-Wire Networks

When placing nodes on a network repeater, (capable of supporting 3-wire networks),
use the following sample connection methods. An RS-485 repeater that supports 3wire interface cabling methods can be purchased from Black Box, (Model ICD107A
along with 12Vdc power source (PSD100). This repeater is fully optically isolated. This
repeater is recommended whenever cable is run between two buildings or sections of
building supplied from separate power sources. Black Box can be found in the Field
Purchasing Guide section 16-05 (http://iknow.us009.siemens.net/fpg/sec1605/default.asp).
Network traffic is only allowed to go though two repeaters in series.
Baud rate and mode switches must be setup to conform to network speed and half
duplex 2-wire (vs. 4-wire) operation
The following figures depict several scenarios for network repeater usage.
76

Restricted
125-5103
2013-11-14

Network Repeater for 3-Wire Networks
Intra-Building Repeater.
77

Restricted
125-5103
2013-11-14

MS/TP 2-Wire Specification
Intra-Building Repeater or Mixed 1pr & 1.5Pr Cable.

Cable configuration
Twisted shielded pair (TSP)
Gauge
24 AWG (stranded)
Capacitance
12.5 pf/foot or less
Twists per foot
4 minimum
Shields
100% foil with drain wire
NEC class
UL listed, CM, CMP (75C or higher)
CEC class
FT4, FT6 (75C or higher)
78

Restricted
125-5103
2013-11-14

3-Wire Nodes wired using 1 Pair Cable.
79

Restricted
125-5103
2013-11-14
Issued by
Building Technologies Division
1000 Deerfield Pkwy
Buffalo Grove IL 60089
Tel. +1 847-215-1000
Document ID
125-5103
Edition
2013-11-14
2013 Copyright Siemens Industry, Inc.

Technical specifications and availability subject to change without notice.
125-5103(BA)
Restricted

BACnet Network Set Up and Troubleshooting

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BACnet Network Set Up and Troubleshooting

Hochgeladen von

Copyright:

Verfügbare Formate

BACnet

Network Setup and

Siemens Industry, Inc.

Network Setup and Troubleshooting Manual

Saving Wireshark Capture ................................................................................................. 51

Network Setup and Troubleshooting Manual

About this Manual

About this Manual

BACnet Application Guide (125-1984)

PXC-24 Unitary Equipment Controller Technical Specification Sheet (149-837)

Network Setup and Troubleshooting Manual

Chapter 1 - BACnet Basics

Chapter 1 - BACnet Basics

BACnet Network Numbers

BBB is the building number (001 through 418)

FF is the Field Panel number (01 through 99)

Example BACnet Network.

Network Setup and Troubleshooting Manual

Chapter 1 - BACnet Basics

BACnet Device Instance

BBB is the building number (001 through 418)

FF is the Field Panel number (01 through 99)

MM is the MSTP/FLN Device number (01 through 99)

BACnet Data Link Layer

Some of the common protocols are:

Uses the IP protocol

Some field devices

Raw Ethernet Packets

Network Setup and Troubleshooting Manual

Chapter 1 - BACnet Basics

BBMD - BACnet/IP Broadcast Management Device

A BBMD configured for 1-Hop distribution sends a packet with a destination

BACnet Objects and Properties

Network Setup and Troubleshooting Manual

Chapter 1 - BACnet Basics

AddListElement Service. Rarely supported

RemoveListElement Service. Rarely supported

CreateObject Service. Rarely supported

DeleteObject Service. Rarely supported

ReadProperty Service. Always Supported

ReadPropertyConditional Service. Rarely supported - Returns a list of

ReadPropertyMultiple Service. Often supported

ReadRange Service. Rarely supported

WriteProperty Service. Almost always supported

WritePropertyMultiple Service. Less often supported than ReadPropertyMultiple

Network Setup and Troubleshooting Manual

Chapter 2 - BACnet Firmware/Hardware

Chapter 2 - BACnet Firmware/Hardware

For PXC Compact Series controllers only.

Network Setup and Troubleshooting Manual

Chapter 2 - BACnet Firmware/Hardware

BACnet MS/TP FLN or P1 FLN not supported in

P1 or BACnet MS/TP (Configurable FLN:

Optional FLN requires license for PXC 36

Optional FLN requires license for PXC 36

Three P1 FLNs or one BACnet MS/TP FLN

Power Open Processor

Three P1 FLNs or one BACnet MS/TP FLN

Optional depending on model: Three P1 FLNs

Network Setup and Troubleshooting Manual

Chapter 2 - BACnet Firmware/Hardware

PXC-24 Unitary Equipment Controller

PXC-16 Unitary Equipment Controller

Maximum Number of MS/TP Devices per network