Network Guide

Document Revision History:

1.
2.
3.
4.

Version 0.1 - Beta Release - March 2010

Version 1.0 Release to Market June 2010
Version 1.1 October 2010
Version 1.2 Added LONWORKS Network information June 2011

Network Guide
05DI-UGBACNG-12
Copyright Distech Controls Inc.
First printing June 2010. Printed in Canada.
While all efforts have been made to verify the accuracy of information in this manual, Distech
Controls is not responsible for damages or claims arising from the use of this manual.
Persons using this manual are assumed to be trained HVAC professionals and are
responsible for using the correct wiring procedures, correct override methods for equipment
control and maintaining safe working conditions in fail-safe environments. Distech Controls
reserves the right to change, delete or add to the information in this manual at any time
without notice.
Distech Controls and the Distech Controls logo are trademarks of Distech Controls Inc.
LONWORKS is a registered trademark of Echelon Corporation. BACnet is a registered
trademark of ASHRAE. Windows, Windows XP, Windows Vista, and Visual Basic.Net are
registered trademarks of Microsoft Corporation. NiagaraAX is a registered trademark of
Tridium, Inc.

TABLE OF CONTENTS
CHAPTER 1 ........................................................................................................................................... 5
Introduction ........................................................................................................................................ 5
Introduction .................................................................................................................................... 6
About BACnet .............................................................................................................................. 6
About LonWorks .......................................................................................................................... 6
About Subnetworks ..................................................................................................................... 6
About This User Guide .................................................................................................................. 7
Purpose of the User Guide .......................................................................................................... 7
Intended Audience....................................................................................................................... 7
Conventions Used in this Document ........................................................................................... 8
Notes ........................................................................................................................................... 8
Cautions and Warnings ............................................................................................................... 8
Related Documentation ............................................................................................................... 8
Acronyms and Abbreviations Used in this Document ................................................................... 9
CHAPTER 2 ......................................................................................................................................... 10
BACnet MS/TP Communication Bus Fundamentals .................................................................... 10
BACnet MS/TP Data Transmission Essentials............................................................................ 11
Data Bus Devices and Baud Rate ............................................................................................... 13
Data Bus Physical Specifications and Cable Requirements ....................................................... 15
Bus Topology and EOL Terminations.......................................................................................... 16
Data Bus Shield Grounding Requirements ................................................................................. 19
Using Repeaters to Extend the Data Bus .................................................................................... 20
Device Addressing ....................................................................................................................... 23
Inter-Building BACnet Connection ............................................................................................... 30
Power Supply Requirements ....................................................................................................... 31
Typical Device BACnet MS/TP LAN and Power Wiring Diagram ............................................... 35
CHAPTER 3 ......................................................................................................................................... 36
LonWorks Communication Bus Fundamentals ............................................................................ 36
Network Architecture ................................................................................................................... 37
EC-NetAX Network Architecture ................................................................................................. 37
TP/FT-10 Network Topologies..................................................................................................... 38
Bus Topology............................................................................................................................. 38
Free Topology ........................................................................................................................... 38
Network Cables ......................................................................................................................... 40
TP/FT-10 Cable specifications .................................................................................................. 40
Extending the Network ................................................................................................................ 42
Grounding a Network ................................................................................................................... 43
Grounding Shielded Twisted Pair Cable ................................................................................... 43
Building Entrance Protection ..................................................................................................... 43
Power Supply Requirements ....................................................................................................... 44
CHAPTER 4 ......................................................................................................................................... 46
Subnetwork Installation Guidelines ............................................................................................... 46
About the Subnetwork Bus .......................................................................................................... 47
ECx-4XX Subnetwork Bus........................................................................................................... 48
ECx-4XX Subnetwork Bus Physical Specifications and Cable Requirements ......................... 48
ECx-4XX Subnetwork Bus Topology and End-of-Line Terminations ........................................ 48
ECx-4XX Subnetwork Bus Shield Grounding Requirements .................................................... 50
ECx-4XX I/O Extension Module Addressing ............................................................................. 50
Power Supply Requirements ..................................................................................................... 51
EC-Smart-Vue Subnetwork Bus .................................................................................................. 52

Network Guide

EC-Smart-Vue Subnetwork Bus Cable Requirements.............................................................. 52

EC-Smart-Vue Subnetwork Bus Topology and End-of-Line Terminations ............................... 54
Commissioning with an EC-Smart-Vue ..................................................................................... 55
Connecting to the LAN through an EC-Smart-Vue ................................................................... 57
CHAPTER 5 ......................................................................................................................................... 60
BACnet Troubleshooting ................................................................................................................ 60
CHAPTER 6 ......................................................................................................................................... 66
LonWorks Troubleshooting ............................................................................................................ 66
CHAPTER 7 ......................................................................................................................................... 70
ECx-400 Series I/O Extension Module Specific Troubleshooting ............................................... 70
CHAPTER 8 ......................................................................................................................................... 71
EC-Smart-Vue Troubleshooting ..................................................................................................... 71
APPENDIX A ....................................................................................................................................... 73
Typical BACnet EIA-485 Data Bus Transmission Example ......................................................... 73
APPENDIX B ....................................................................................................................................... 75
How to Set a DIP Switch .................................................................................................................. 75
APPENDIX C ....................................................................................................................................... 76
Metric Conversions for Wire Gauge ............................................................................................... 76
APPENDIX D ....................................................................................................................................... 77
Documentation Improvement Form ............................................................................................... 77

Network Guide

CHAPTER 1
INTRODUCTION
This section provides an overview of the user guide.
In This Chapter
Topic

Page

Introduction

About This User Guide

Acronyms and Abbreviations Used in this Document

Network Guide

Introduction

Introduction
This document describes best practices, specifications, wiring rules, device termination, and
application information to implement robust and reliable communications networks.

About BACnet
The BACnet ANSI/ASHRAE Standard 135-2008 specifies a number of Local Area
Network (LAN) transport types. Distech Controls controllers use both BACnet IP and
BACnet Master-Slave/Token-Passing (MS/TP) communications bus (based on EIA-485) as
a local network for internetworking of supervisory controllers and field controllers.

About LonWorks
The LONWORKS standard ANSI/CEA-709.1-B specifies a number of Local Area Network
(LAN) transport types. Distech Controls controllers use a twisted pair "free topology"
communications bus operating at 78 kbit/s as a local network for internetworking of
supervisory controllers and field controllers.
LONWORKS is one of several network types of the BACnet ANSI/ASHRAE Standard;
however, no Distech Controls controllers are compatible with this network type except for an
EC-NetAX.

About Subnetworks
Distech Controls controllers also support the following types of subnetworks:

ECx-4XX subnetwork bus that is used to connect ECx-4XX Series I/O Extension
Modules to an ECB-600 or ECL-600 controller.

EC-Smart-Vue Subnetwork bus is used to connect EC-Smart-Vue sensors to any

Distech Controls ECB series controller or ECL series controller.

Network Guide

Introduction

About This User Guide

Purpose of the User Guide
This user guide does not provide and does not intend to provide instructions for
safe wiring practices. It is the users responsibility to adhere to the safety codes,
safe wiring guidelines, and safe working practices to conform to the rules and
regulations in effect in the job site jurisdiction. This user guide does not intend to
provide all the information and knowledge of an experienced HVAC technician or
engineer.

For BACnet
This User Guide describes the best practices for installing a BACnet MS/TP LAN
and reviews the specifications, device limits, BACNET MS/TP LAN cable
requirements, best wiring practices, the importance of rigorous grounding practices,
24 volt power supply wiring requirements, BACnet MS/TP bus termination, setting
the MAC address and Device Instance for devices on a BACnet MS/TP LAN, and
finally LAN troubleshooting.
This user guide is intended to provide BACnet LAN information to instruct a user to
install and configure a BACnet MS/TP LAN. However, this guide is not intended to
instruct the user on how configure the devices connected to the LAN, to use network
management tool software, to program a device to share points on the network, or
the procedure to install a given device. For this information, refer to the devices
hardware installation guide and its related programming user guide.

For LONWORKS
This User Guide describes the best practices for installing a LONWORKS LAN and
reviews the specifications, device limits, LAN cable requirements, best wiring
practices, grounding practices, 24 volt power supply wiring requirements,
LONWORKS network termination, and finally LAN troubleshooting.
This user guide is intended to provide LONWORKS LAN information to instruct a user
to install and configure a LONWORKS LAN. However, this guide is not intended to
instruct the user on how configure the devices connected to the LAN, to use network
management tool software, to program a device to share points on the network, or
the procedure to install a given device. For this information, refer to the devices
hardware installation guide and its related programming user guide.

For Subnetworks
This user guide also describes the best practices for installing the subnetwork used
for Distech Controls I/O Extension Modules and EC-Smart-Vue; cable requirements,
best wiring practices, bus termination, and device addressing.

Intended Audience
This user guide is intended for system designers, integrators, electricians, and field
technicians who have experience with control systems, and who want to learn about how to
make a successful BACnet MS/TP LAN installation. It is recommended that anyone installing
and configuring the devices specified in this user guide have prior training in the usage of
these devices.

Network Guide

Introduction

Conventions Used in this Document

Notes
This is an example of Note text. Wherever the note-paper icon appears, it means
the associated text is giving a time-saving tip or a reference to associated
information of interest.

Cautions and Warnings

This is an example of Caution or Warning text. Wherever the exclamation icon
appears, it means that there may be an important safety concern or that an action
taken may have a drastic effect on the device, equipment, and/or network if it is
improperly carried out.

Related Documentation
Refer to the Hardware Installation Guide for the devices you are installing.

Network Guide

Introduction

Acronyms and Abbreviations Used in this

Document
Table 1-1: Acronyms and Abbreviations
Acronym

Definition

ANSI

American National Standards Institute

ASHRAE

American Society of Heating, Refrigeration, and Air-Conditioning

Engineers

BACnet

Building Automation and Control Networking Protocol

B-AAC

BACnet Advanced Application Controller

B-ASC

BACnet Application Specific Controller

B-BC

BACnet Building Controller

BBMD

BACnet/IP Broadcast Management Device

DI

Device Instance Number

EIA

Electronic Industries Alliance

EOL

End Of Line

ID

Identifier

LAN

Local Area Network

MAC

Media Access Control

MS/TP

Master-Slave/Token-Passing

Network Guide

CHAPTER 2
BACNET MS/TP COMMUNICATION BUS
FUNDAMENTALS
This chapter describes the BACnet MS/TP Communications Bus operating principals.
In This Chapter
Topic

Page

BACnet MS/TP Data Transmission Essentials

11

Bus Topology and EOL Terminations

16

Using Repeaters to Extend the Data Bus

20

Data Bus Devices and Baud Rate

13

Data Bus Physical Specifications and Cable Requirements

15

Data Bus Shield Grounding Requirements

19

Device Addressing

23

Inter-Building BACnet Connection

30

Power Supply Requirements

31

Typical Device BACnet MS/TP LAN and Power Wiring

Diagram

35

Network Guide

10

BACnet MS/TP Communication Bus Fundamentals

BACnet MS/TP Data Transmission Essentials

Introduction
The BACnet MS/TP bus protocol is part of the BACnet ANSI/ASHRAE Standard 1352008 that uses the EIA-485 (RS-485) physical layer standard for data transmission (herein
called the data bus). Multiple data buses can be logically tied together as each BACnet
MS/TP bus is assigned a unique Network Instance that distinguishes it from other data
buses in the BACnet MS/TP Local Area Network (LAN). An example of an interconnected
BACnet MS/TP bus is shown in Figure 2-16.
EIA-485 is a standard that defines the electrical characteristics of the receivers and drivers
to be used to transmit data in a differential (balanced) multipoint data bus that provides high
noise immunity with relatively long cable lengths which makes it ideal for use in industrial
environments. The transmission medium is inexpensive and readily-available twisted pair
shielded cable.
While there are many possible LAN topologies for an EIA-485 data bus, only devices that
are daisy-chained together are allowed with BACnet MS/TP (see Figure 2-4). A spur is only
permitted when it is connected to the bus through a repeater (see Using Repeaters to
Extend the Data Bus on page 20).
End-of-line (EOL) terminations are critical to error-free EIA-485 data bus operation. The
impedance of the cable used for the data bus should be equal in value to the EOL
termination resistors (typically 120 ohms). Cable impedance is usually specified by the cable
manufacturer.
BACnet MS/TP Data Bus is Polarity Sensitive
The polarity of all devices that are connected to the two-wire BACnet MS/TP data bus must
be respected. The markings to identify the polarity can vary by manufacturer. The following
table summarizes the most common identification labels for BACnet MS/TP data bus
polarity.

Network Guide

11

BACnet MS/TP Communication Bus Fundamentals

Table 2-1: Common Identification Labels for BACnet MS/TP Data Bus Polarity
Device Manufacturer

Data Bus Connections

Inverting

Non-inverting

Reference

Controllers

NET

NET +

24V COM

EC-BOS

Thermostat

Ref

Repeater

Data
Data1

Data+
Data1+

(B)GND

BACnet/IP
to MS/TP
Adapter

RT

RT+

COM

BACnet/IP
to MS/TP
Router

SC

Common identification labels for

BACnet MS/TP data bus polarity
by other Manufacturers

SC

TxD/RxD

TxD+/RxD+

GND

U+

COM

RT

RT+

REF

Sig

Sig+

Data

Data+

Distech Controls

Except for an EC-BOS, never connect the shield of the BACnet MS/TP data bus to
the Reference terminal. See Data Bus Shield Grounding Requirements on page 19
for more information.
When interfacing with BACnet MS/TP devices from other manufacturers, refer to the
documentation for the device to correctly wire the device.

12

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Data Bus Devices and Baud Rate

Maximum Number of BACnet MS/TP Devices on a Data Bus Segment
The BACnet MS/TP data bus supports up 255 devices:

Up to 128 (0 to 127) devices that are Masters (that can initiate communication).

Up to 128 (128 to 255) devices that are Slaves (cannot initiate communication).

However, it is recommended that any given data bus segment have no more than 50
devices. A repeater counts as a device on each data bus segment to which it is connected.
At 9600 Baud, the maximum number of devices is reduced to 25 due to increased
token loop times.
All Distech Controls devices are categorized as BACnet MS/TP Masters and are rated as
follows.
Table 2-2: Device Loading
Manufacturer

Device load on the attached BACnet MS/TP Data Bus

Distech Controls ECB

controllers

load devices

Distech Controls BACnet

MS/TP Thermostats

load devices

Other manufacturers

Refer to their documentation

However, if a data bus segment with Distech Controls Devices are interoperating with one or
more devices from another manufacturer that support fewer devices on a data bus segment,
then the device that supports the fewest devices on the same data bus is the one that sets
the limit for the maximum number of devices for that data bus segment. For example, you
plan to put on one data bus the following devices:
Table 2-3: Device Loading Example
Manufacturer

Quantity of
devices
(example)

Equivalent
full-load
devices

Maximum devices
supported by the
manufacturer

Distech Controls devices

( load devices)

1281 (50
recommended)

Distech Controls BACnet

MS/TP Thermostats (
load devices)

14

64 (50
recommended)

Manufacturer Y (full load

devices)

26

26

32

34

There are too many

devices on the data
bus. It is limited to a
maximum of 32
devices by
Manufacturer Y.

Total Full-Load Devices

This is limited by the maximum number of master devices allowed on a BACnet

MS/TP Data Bus.

The solution for the above example is to create two data bus segments connected together
by a repeater and then split up the devices between the data bus segments, ensuring again

Network Guide

13

BACnet MS/TP Communication Bus Fundamentals

that the maximum number of devices on each separate data bus is not exceeded. See Using
Repeaters to Extend the Data Bus on page 20.
Baud Rate
Most devices will have a range of baud rate settings and possibly an AUTO setting that
detects the baud rate of other devices transmitting on the data bus and adjusts the baud rate
of the device accordingly. Typical baud rates are 9600, 19 200, 38 400, and 76 800. The
baud rate setting determines the rate at which data is sent on the data bus. All devices on
the data bus must be set to the same baud rate. Therefore, the chosen baud rate must be
supported by all devices connected to the data bus.
Distech Controls devices must be power cycled after changing a baud rate setting for it to
take effect.
The recommended baud rate for Distech Controls devices is 38 400.
To set the baud rate, see Setting the BAUD Rate for ECB-Series Controllers (optional) on
page 56.

14

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Data Bus Physical Specifications and Cable

Requirements
Cables composed of stranded conductors are preferred over solid conductors as stranded
conductor cable better resist breakage during pulling operations. Distech Controls highly
recommends the following data bus segment cable specifications be respected.
Table 2-4: BACnet MS/TP Data Bus Segment Physical Specifications and Cable
Requirements
Parameter

Details

Media

Twisted pair, 24 AWG

Shielding

Foil or braided shield

Shield grounding

The shield on each segment is connected to

electrical system ground at one point only; see Data
Bus Shield Grounding Requirements on page 19.

Characteristic impedance

100-130 Ohms. The ideal is 100-120 Ohms.

Distributed capacitance
between conductors

Less than 100 pF per meter (30 pF per foot) The

ideal is less than 60 pF per meter (18pF per foot).

Distributed capacitance
between conductors and shield

Less than 200 pF per meter (60 pF per foot).

Maximum length per segment

1220 meters (4000 feet)

Data Rate

9600, 19 200, 38 400, and 76 800 Baud

Polarity

Polarity sensitive

Multi-drop

Daisy-chain (no T-connections)

EOL terminations

120 ohms at each end of each segment

Data bus bias resistors

510 ohms per wire (max. of two sets per segment)

Shielded cable offers better overall electrical noise immunity than non-shielded cable.
Unshielded cable or cable of a different gauge may provide acceptable performance for
shorter data bus segments in environments with low ambient noise.
Table 2-5: Distech Controls Recommended Cable Types for BACnet MS/TP Data
Buses
Bus and Cable Type

Part Number

O.D. ()

300 meters (1000 feet), 24 AWG Stranded, Twisted

Pair Shielded Cable FT6, Rated for Plenum
Applications

07CBL-BACNET

3.75mm
(0.148 in.)

1. Distech Controls BACnet cable offers the best performance over the full range of baud
rates, cable lengths, and number of connected devices. This is primarily due to lower
conductor-to-conductor capacitance of this cable.

Network Guide

15

BACnet MS/TP Communication Bus Fundamentals

Bus Topology and EOL Terminations

Function of EOL Terminations
The first and last device on the data bus must have End-of-Line (EOL) termination resistors
connected across the two data lines/wires of the twisted pair. These resistors serve the
following purposes:

EOL terminations dampen reflections on the bus that result from fast-switching (highspeed rising and falling data edges) that otherwise would cause multiple data edges to
be seen on the bus with the ensuing data corruption that may result. The higher the
baud rate a data bus is operating at, the more important that EOL terminations be
properly implemented. Electrically, EOL terminations dampen these reflections by
matching the impedance to that of a typical twisted pair cable.

EIA-485 data bus transmitters are tri-state devices. That is they can electrically transmit
1, 0, and an idle state. When the transmitter is in the idle state, it is effectively offline or
disconnected from the data bus. EOL terminations serve to bias (pull-down and pull-up)
each data line/wire when the lines are not being driven by any device. When an undriven data bus is properly biased by the EOL terminations to known voltages, this
provides increased noise immunity on the data bus by reducing the likelihood that
induced electrical noise on the data bus is interpreted as actual data.

When to use EOL Terminations

EOL terminations should only be enabled / installed on the two devices located at either end
of the data bus. All other devices must not have the EOL terminations enabled/installed.
Typical BACnet Device

EOL OFF

EOL OFF

Typical EC-BOS Device

NET+

EOL ENABLED: For the

EC-BOS as a first or last
daisy-chained device:

NET-

NET+

Typical BACnet Device

EOL OFF

NET-

Typical BACnet Device

NET+

NET+

NET-

EOL ON

NET-

Typical BACnet Device

- OPTIONALLY set the

EOL jumper internally

- AND add a 120 Ohm

resistor as shown here

12

Data Bus: Shielded Twisted Pair Cable

First and last daisy-chained device:
- EOL Jumpers are ENABLED
OR EOL resistor is installed
All other Devices:
- EOL Jumpers are DISABLED

Electrical
System
Ground

Figure 2-1: EOL Terminations Must be Enabled at Both the First and Last Device on
the Data Bus
Devices are factory-set with the EOL termination disabled by default.
The BACnet/IP to MS/TP Adapter does not have EOL Termination (and BACnet
MS/TP Data Bus biasing) capabilities to be used at the end of a BACnet MS/TP
data bus. Instead, use the BACnet/IP to MS/TP Router for this application.
When to use EOL Terminations with BACnet MS/TP Thermostats
BACnet MS/TP thermostats support external EOL termination resistors only. When a
BACnet MS/TP thermostat is the first or last daisy-chained device, add a 120 Ohm resistor
across the and + BACnet MS/TP data bus connections.
The BACnet MS/TP data bus must be biased. This bias can only be provided by built-in EOL
termination resistors (ones set with a jumper). If a BACnet MS/TP data bus has a BACnet
MS/TP thermostat at one end of the BACnet MS/TP data bus and an EC-BOS at the other
end, you must set the internal EOL jumper in the EC-BOS so that proper biasing is provided
to the BACnet MS/TP data bus.

16

Network Guide

BACnet MS/TP Communication Bus Fundamentals

No Built-in EOL
Jumper

No Built-in EOL
Jumper

No Built-in EOL
Jumper

12

NET-

NET-

NET-

EOL ENABLED: Use the

EC-BOS as a first or last
daisy-chained device:
The internal EOL jumper
MUST be set to ON to
provide bias to BACnet
MS/TP Data Bus AND
add a 120 Ohm resistor
as shown here

NET+

No Built-in EOL
Jumper

NET+

Typical
BACnet
Device

NET+

Typical
BACnet
Device

NET+

Typical
BACnet
Device

NET-

Typical
BACnet
Device

Typical EC-BOS Device

EOL ON

12

Electrical
System
Ground

Data Bus: Shielded Twisted Pair Cable

EOL: Add a 120
Ohm resistor as
shown here

First and last daisy-chained device:

- EOL Jumpers are ENABLED
at one end, and EOL resistor is
installed at other end.
All other Devices:
- EOL Jumpers are DISABLED.

Figure 2-2: Typical EOL Terminations with BACnet MS/TP Thermostats with Biasing
Provided by the EC-BOS Internal EOL Jumper set to ON
When a BACnet MS/TP data bus has a BACnet MS/TP thermostat at one end of the BACnet
MS/TP data bus and an EC-BOS at the other end without its internal EOL jumper enabled,
fish-tail the BACnet MS/TP data bus back to a controller in which the built-in EOL termination
can be set. This will provide the necessary biasing to the BACnet MS/TP data bus.

No Built-in EOL
Jumper

No Built-in EOL
Jumper

NET+

Typical
BACnet
Device

NET-

NET+

NET-

NET+

NET-

No Built-in EOL
Jumper

Typical
BACnet
Device

NET+

With Built-in EOL Jumper

EOL ON

NET-

Typical BACnet Device

Typical
BACnet
Device

Typical EC-BOS Device

EOL ENABLED: For the
EC-BOS as a first or last
daisy-chained device:
- OPTIONALLY set the
EOL jumper internally

- AND add a 120 Ohm

resistor as shown here

12

Data Bus: Shielded Twisted Pair Cable

Fish-tail the Data Bus back to a controller

that has a built-in EOL Jumper making it
the last device on the Data Bus

Electrical
System
Ground

First and last daisy-chained device:

- EOL Jumpers are ENABLED
OR EOL resistor is installed
All other Devices:
- EOL Jumpers are DISABLED

Figure 2-3: Fish-tailing the BACnet MS/TP Data Bus to use a Controller with Built-in
EOL Termination that will Provide Biasing to the BACnet MS/TP Data Bus
Only a Daisy-Chained Data Bus Topology is Acceptable
Use a daisy-chained BACnet MS/TP data bus topology only. No other data bus topology is
allowed.

Network Guide

17

BACnet MS/TP Communication Bus Fundamentals

- Data Bus Management
- Data Bus Integration
- Device Configuration and
programming
- Graphical Interface
Configuration

- Alarm
- Trend Log
- Schedule
EC-NetAX Supervisor

- User Interface
- Remote Access
- Embedded EC-NetAX Pro
EC-NetAX Pro

Web Browser

Ethernet, TCP/IP, BACnet/IP, LONWORKS IP, XML, HTTP, oBIX

EC-BOSAX
EOL Terminator
MS/TP

Data Bus Segment

Maximum of 32 nodes and 1200 meters.

Maximum is 50 nodes when using
Distech Controls devices exclusively

Segment 1

EOL
ON

EOL Internally Set

Central Plant

Air Handling Controllers

Figure 2-4: Typical BACnet MS/TP LAN Topology Showing How Devices are DaisyChained Together with One Data Bus Segment
Only linear, daisy-chained devices provide predictable data bus impedances
required for reliable data bus operation.
Only a daisy-chained data bus topology should be specified during the planning
stages of a project and implemented in the installation phase of the project.
A spur is only permitted when it is connected to the bus through a repeater (refer
to Using Repeaters to Extend the Data Bus on page 20).
Star and ring topologies are not supported because signal reflections on the data bus may
not be sufficiently dampened by the standard EOL termination resistors supplied by device
manufacturers, as these resistors may present excessively high or low termination
impedance. These topologies have more complex electrical characteristics that require
advanced analysis to determine the appropriate termination resistances to ensure error-free
data transmission on the data bus.

EC-BOSAX

EC-BOSAX

Spur / Backbone
Topologies are
Unsupported

Star Topologies are

Unsupported

Figure 2-5: Unsupported BACnet MS/TP LAN Topologies

18

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Data Bus Shield Grounding Requirements

The EIA-485 data bus standard requires that the data bus must be shielded against
interference. A BACnet MS/TP data bus must be properly grounded. For this, the devices on
each data bus segment must be daisy-chained together with the cable shield twisted
together and isolated with electrical tape at each device. The shield on each segment must
be connected to electrical system ground at one point only, at the Bus Master (Building
Controller) if there is one, as shown below. On data bus segments without a Bus Master
(Building Controller), the ideal point to ground the shield is in the middle of the data bus
segment.
Grounding the shield of a data bus segment in more than one place will more than likely
reduce shielding effectiveness.

Bus Master (Building Controller)

Typical BACnet Device

Typical BACnet Device

Typical BACnet Device

Typical BACnet Device

Data Bus Shields: Twist

together and Isolate
with electrical tape

Electrical
System
Ground

Data Bus Shields: Twist

together and Isolate
with electrical tape

NET-

NET+

NET-

NET+

NET-

NET+

NET-

The shield of the data bus

must be connected to the
electrical system ground at
one point only usually at
the Building Controller,
when present

NET+

Typical EC-BOS Device

Data Bus Shields: Twist

together and Isolate
with electrical tape

Data Bus Shield:

Isolate with
electrical tape

Data Bus: Shielded Twisted Pair Cable

Data Bus Shield:
Connect to the S
terminal

Figure 2-6: Typical Cable-Shield Grounding Requirements for a BACnet MS/TP Data
Bus Segment with a Building Controller located in the End of the Data Bus

Data Bus Shield:

Isolate with
electrical tape

Bus Master (Building Controller)

The shield of the data bus

must be connected to the
electrical system ground
at one point only usually
at the Building Controller,
when present
Data Bus Shields: Twist
together and Isolate
with electrical tape

Typical BACnet Device

Typical BACnet Device

Data Bus Shields: Twist

together and Isolate
with electrical tape

Electrical
System
Ground

NET-

NET+

Typical EC-BOS Device

NET-

NET-

NET+

Typical BACnet Device

NET-

NET+

Typical BACnet Device

NET+

Data Bus Shield:

Connect to the S
terminal

Data Bus Shield:

Isolate with
electrical tape

Data Bus: Shielded Twisted Pair Cable

Figure 2-7: Typical Cable-Shield Grounding Requirements for a BACnet MS/TP Data
Bus Segment with a Building Controller located in the Middle of the Data Bus

Data Bus Shield:

Isolate with
electrical tape

Data Bus Shields: Twist

together and Isolate
with electrical tape

Data Bus: Shielded Twisted Pair Cable

Electrical
System
Ground

Data Bus Shields: Twist

together and Isolate
with electrical tape

Data Bus Shields: Twist

together and Isolate
with electrical tape

NET-

NET+

Typical BACnet Device

NET-

NET+

Typical BACnet Device

NET-

NET+

Typical BACnet Device

NET-

NET+

Typical BACnet Device

NET-

NET+

Typical BACnet Device

Data Bus Shield:

Isolate with
electrical tape

The shield of the data bus must be

connected to the electrical system
ground at one point only, ideally in
the middle of the data bus as shown

Figure 2-8: Typical Cable-Shield Grounding Requirements for a BACnet MS/TP Data
Bus Segment without Building Controller

Network Guide

19

BACnet MS/TP Communication Bus Fundamentals

Using Repeaters to Extend the Data Bus

A BACnet MS/TP data bus segment can be up to 1220 meters (4000 feet) long with up to 50
devices maximum. When a greater length is required, a solution is to use a repeater. A
repeater increases the maximum length of the data bus.
Using an EC-BOS to Increase the Number of Connected Devices
If your BACnet MS/TP network has an EC-BOS, it may be more cost effective to add one or
two MS/TP network cards to the EC-BOS in place of an MS/TP Repeater. A standard
EC-BOS can support up to four MS/TP networks when equipped with two optional MS/TP
network cards. Furthermore, network performance is increased as each MS/TP network will
have lower communication latency due to each MS/TP network having its own token to pass
between devices. See BACnet MS/TP Data Bus Token-Passing Overview on page 24.
With up to 50 devices per MS/TP network, this allows up to a total of 200 devices to be
connected to an EC-BOS. See Figure 2-16.
Using a Repeater to Extend the Length of the BACnet MS/TP Data Bus
Repeaters can be used to extend a BACnet MS/TP data bus up to 3660 meters maximum
total length. Do not use more than two repeaters on a BACnet MS/TP LAN.
A BACnet MS/TP repeater is a bi-directional device that regenerates and strengthens the
electrical signals that pass through it. It creates two electrically-isolated BACnet MS/TP data
bus segments that transparently enable devices on one side of the repeater to communicate
with any device on the other side. The two BACnet MS/TP data bus segments have the
same requirements of an ordinary BACnet MS/TP data bus segment; that is each BACnet
MS/TP data bus segment:

Can be up to 1220 meters (4000 feet) long.

Will have the same network number as they remain part of the same network or LAN.
Do not use more than two repeaters on a BACnet MS/TP data bus.
A repeater can only connect two BACnet MS/TP data bus segments even if it has
ports to support more than two BACnet MS/TP data bus segments.

A repeater can be added anywhere to a data bus segment including the end of the segment
as shown below.
MS/TP Data Bus:
- 3660 m (12 000 ft) Maximum Total
- 50 Connected Devices Maximum Total

MS/TP Data Bus Segment:

- 1220 m (4 000 ft) Maximum

MS/TP Data Bus Segment:

- 1220 m (4 000 ft) Maximum

MS/TP Data Bus Segment:

- 1220 m (4 000 ft) Maximum
EOL Terminators

EOL Terminator

MS/TP
Repeater

EOL
ON

EC-BOSAX

MS/TP
Repeater

EOL
ON

EOL Internally Set

EOL Internally Set

< 7.6 m
< 25 ft

EOL
ON

EOL Internally Set

< 7.6 m
< 25 ft

Figure 2-9: Using a Repeater to Extend the Range of the LAN

A repeater can be used to create a spur as shown below.

20

Network Guide

BACnet MS/TP Communication Bus Fundamentals

MS/TP Data Bus Segment:
- 1220 m (4 000 ft) Maximum
- 50 Connected Devices Maximum Total
EOL Terminator

EOL
ON

EC-BOSAX

MS/TP
Repeater

EOL Terminator

EOL Internally Set

MS/TP Data Bus Segment:

- 1220 m (4 000 ft) Maximum
- 50 Connected Devices Maximum Total
EOL
ON

EOL Internally Set

Figure 2-10: Adding a Spur by Using a Repeater

A repeater is counted as a device on each data bus to which it is connected.
When third party devices are connected to a data bus segment, the number of devices that
can be connected to that data bus segment may be reduced. Refer to Maximum Number of
BACnet MS/TP Devices on a Data Bus Segment on page 13.

Data Bus Shields: Twist

together and Isolate with
electrical tape

Data Bus: Shielded

Twisted Pair Cable

Data + (1)

Data + (20)

Data (2)

Data (19)

2
12

< 7.6 m
< 25 ft

EOL ON

Data Bus Shields: Twist

together and Isolate
with electrical tape

Repeater

Typical BACnet Device

NET-

No Built-in EOL
Jumper

BACnet MS/TP data bus

Bias and EOL termination is
provided by this controllers
internal EOL Jumper being
set to ON

NET+

Typical
BACnet
Device

NET+
NET-

NET-

NET+

EOL ON

BACnet MS/TP data bus

Bias and EOL termination is
provided by this controllers
internal EOL Jumper being
set to ON

NET+
NET-

Typical BACnet Device

The data bus shield must be connected to the electrical system ground at
one point only usually at the Building Controller, when present

Figure 2-11: Repeater Connections when it is the First or Last Device on its
Respective Data Bus Segment
The BACnet MS/TP Data Bus must be biased. This bias can only be provided by built-in
EOL termination resistors (ones set with a jumper). When a repeater is the first or last device
on its respective data bus segment, use the following methods to provide MS/TP Data Bus
biasing and EOL termination as applicable to your situation:

1. On the BACnet MS/TP data bus segment shown in Figure 2-11, bias and EOL
termination is provided by a controllers internal EOL jumper being set to ON. In this
case the connection to the repeater cannot be more than 7.6 meters (25 feet) from this
controller.

2. On the BACnet MS/TP data bus segment shown in Figure 2-11, a 120 EOL
Termination resistor is added to the repeaters terminals. Biasing for this BACnet MS/TP

Network Guide

21

BACnet MS/TP Communication Bus Fundamentals

data bus segment is provided by the internal EOL Jumper being set to ON at the last
controller at the other end of this data bus.
See When to use EOL Terminations on page 16 for more information. Follow shielding and
grounding recommendations: See Data Bus Shield Grounding Requirements on page 19.

22

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Device Addressing
Device addressing allows the coordinated transfer of messages between the intended
devices on the BACnet MS/TP data bus and with devices connected to the internetwork. For
this, each device connected to the BACnet MS/TP data bus is identified by a MAC address,
a Device Instance number, and a Network Number:

The MAC Address uniquely identifies a device on a Network (identified by a Network

Number). Devices on another Network can have the same MAC Address as messages
are not passed at the internetwork level using the MAC Address. The MAC Address also
defines the devices on the data bus that are Masters and Slaves, among other
categories (see Table 2-6). The MAC Address is also used to share data bus bandwidth
between devices through token passing between Master devices.

The Device Instance uniquely identifies a device across the BACnet internetwork. The
Device Instance is any number between 0 and 4 194 303. It is with the Device Instance
that messages are exchanged between BACnet devices. The Device Instance is also
used by routers to forward messages to devices located elsewhere in the internetwork.
Unlike a MAC Address, a Device Instance cannot be reused elsewhere in the BACnet
internetwork (it must be unique).

The Network Number is any number between 1 and 65 534. A network number identifies
a LAN for routing purposes.

Both the MAC Address and the Device Instance must be set for each device and are
essential for proper BACnet LAN operation.
For an example of how MAC address, Device Instance number, and Network Number apply
to a typical BACnet network, see Figure 2-16.
About the MAC Address
The MAC Address is a number from 0 to 255; however we recommend reserving some MAC
Addresses for common commissioning and maintenance tasks. For example, when a
portable adaptor is set to use one of these reserved MAC Addresses, it can be temporarily
connected with certainty to any data bus of any site without conflicting with other devices
already connected to the data bus.
MAC Addresses should be used as shown in the following table.

Network Guide

23

BACnet MS/TP Communication Bus Fundamentals

Table 2-6: Recommended BACnet MS/TP Bus MAC Address Values / Ranges for
BACnet MS/TP Bus Devices
MAC Address
Value / Range

Usage

Devices

Bus Master
(Building Controller)

EC-BOS
This address is invalid for Distech Controls
ECB devices

Temporary
commissioning
connection

Portable adaptor MAC Address for a

temporary commissioning and maintenance
connection

Reserved

Other

3-127

Master Range

Master devices: All Distech Controls

devices are master devices and should be in
this MAC Address range

128-254

Slave Range

Slave devices and network sensors

255

Broadcast

Do not apply address 255 to any device.

BACnet MS/TP Data Bus Token-Passing Overview

The BACnet MS/TP data bus protocol is a peer-to-peer, multiple-master protocol that shares
data bus bandwidth by passing a token between Master devices on the data bus that
authorizes the device that is holding the token to initiate communications on the data bus.
Once the device has completed its request(s), it closes the communications channel, passes
the token to the next Master device (making it the current Master), and liberates the data
bus.
The token is passed through a short message from device to device on the BACnet MS/TP
data bus in consecutive order starting from the lowest MAC address (MAC Address = 0) to
the next MAC Address.
Gaps or pockets of unassigned device MAC Addresses should be avoided as this reduces
bus performance. Every 50 requests, each master must poll for the next master that may
exist on the Data Bus. It is the timeout for each unassigned MAC Address that slows down
the data bus.
The way MAC Addresses are assigned is not a physical requirement: Devices can be daisychained on the data bus in any physical order regardless of their MAC Address sequence.
The goal is to avoid gaps in the device MAC Address range.
Slave devices cannot accept the token, and therefore can never initiate communications. A
Slave can only communicate on the data bus to respond to a data request addressed to it
from a Master device. Gaps in slave device MAC Addressing have no impact on BACnet
MS/TP data bus performance.

24

Network Guide

BACnet MS/TP Communication Bus Fundamentals

No MAC Address Gaps
EOL Terminator

MS/TP
Network # 10

EOL Internally Set

EOL
ON

EC-BOSAX

MAC: 0
DI: 10 000

MAC Address Gaps

MAC: 3
DI: 10 003

MAC: 4
MAC: 5
MAC: 6
DI: 10 004 DI: 10 005 DI: 10 006

MAC Address 1 & 2 are Reserved

for Maintenance Purposes

EOL Terminator

MS/TP
Network # 10

MS/TP
Network # 10

EOL Internally Set

EOL
ON

EC-BOSAX

MAC: 0
DI: 10 000

MAC: 3
DI: 10 003

MAC: 4
MAC: 25
MAC: 26
DI: 10 004 DI: 10 025 DI: 10 026

Avoid MAC Address Gap

EOL Internally Set

EOL
ON

EC-BOSAX

MAC: 0
DI: 10 000

EOL Terminator

MAC: 6
DI: 10 006

MAC Address 1 & 2

are Reserved for
Maintenance Purposes

MAC: 5
MAC: 3
MAC: 4
DI: 10 005 DI: 10 003 DI: 10 004

The Physical Order

of MAC Addresses
is Unimportant

Figure 2-12: Setting the Max Master on the Bus Master (Building Controller) to the
Highest MAC Address Used on the BACnet MS/TP Data Bus
About Tuning the Max Info Frames Parameter
Once a device has the token, it can make a number of information requests to other devices
on the BACnet intranetwork. The maximum number of requests is limited by the
Max Info Frames parameter. Ordinary BACnet MS/TP devices should have the
Max Info Frames parameter set to between 2 and 4. The Bus Master (Building Controller)
should have the Max Info Frames parameter set to 20.
About Tuning the Max Master Parameter
To prevent the passing of the token to unused MAC Addresses situated after the final Master
device, the Max Master must be set. By default, the Max Master for the Bus Master (Building
Controller) is set to 127 which allows for the theoretical maximum of 127 devices besides the
Bus Master to be connected to the data bus.
In practice, the actual number of devices connected to a data bus is far less, resulting in a
gap between the highest MAC Address of any device connected to the data bus and the
value set for Max Master. This gap unnecessarily slows-down the data bus with Poll for
Master requests.
When commissioning a BACnet MS/TP Data Bus, it is useful to start with the Max Master set
to 127 so as to be able to discover all devices connected to the data bus. Then, once all
devices have been discovered and the MAC Addressing is finalized by eliminating any gaps
in the address range, set the Max Master (maximum MAC Address) in the EC-BOS
(Building Controller) to the highest Master devices MAC Address number to optimize the
efficiency of the data bus.

Network Guide

25

BACnet MS/TP Communication Bus Fundamentals

Setting the Max Master and Max Info Frames
The Max Master and Max Info Frames are parameters used to optimize a BACnet MS/TP
Data Bus. This is set in the Bus Master (EC-BOS Building Controller) for the MS/TP port of
the Bus Master and for each BACnet MS/TP device connected on that port.
A Configure MS/TP Devices tool is available to automate this task. This tool:

Can only be used with a live database during commissioning. If you add more devices to
the data bus, you must run this tool again.

Automatically calculates the value for the Max Master by finding the highest Master
device MAC Address on the connected BACnet MS/TP data bus plus 1.

Sets the Max Master for all master devices including the Bus Master (EC-BOS).

Sets the Max Info Frames for all master devices excluding the Bus Master (EC-BOS).

For the Bus Master (EC-BOS), set the Max Info Frames to 20 in the screen shown in Figure
2-15 as this is a device that will make more requests for service from other devices on the
network. In general, according to the way a device is programmed, the Max Info Frames
may have to be set to a higher value than for other devices. For example, when Roof Top
Unit Controllers are used with VAV controllers that use gfxApplications code, they should
also have their Max Info Frames set to a higher value such as 5, as Roof Top Unit
Controllers poll VAV controllers for information.
Set the Max Master and Max Info Frames as follows.

1. Right-click the Link node in the Nav tree and select Ms/Tp Configuration.

Figure 2-13: Launching the Configure MS/TP Devices tool

2. The network must be live; the Status shown in Configure Ms/Tp devices window must
be {ok}.

26

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Figure 2-14: Setting the Max Master on the Bus Master (EC-BOS) to the Highest MAC
Address Used on the BACnet MS/TP Data Bus

3. A confirmation message is shown.

4. Set the Max Info Frames to 20 for the Bus Master (EC-BOS) as shown in the screen
below.

Figure 2-15: Setting the Max Info Frames on the Bus Master (EC-BOS)
Default Device Instance Number Numbering System for Distech Controls controllers
By default, controllers from Distech Controls automatically self assign a Device Instance
number generated from the unique MAC Address assigned to the controller during
installation. The Device Instance number is calculated as follows:
Device Instance number = 364 X 1000 + MAC Address
Where 364 is Distech Controls unique BACnet Manufacturer ID.
This Numbering system is sufficient for a BACnet network that has only one Building
Controller. For larger BACnet networks that have more than one Building Controller (to form
a BACnet intranetwork), set the MAC Addresses, Device Instance Numbers and Network
Numbers according to the numbering scheme below.
Adopting a Numbering System for MAC Addresses, Device Instance Numbers, and
Network Numbers
Good network planning requires a well thought-out numbering scheme for device MAC
Addresses, Device Instance Numbers (DI), and Network Numbers. We recommend the

Network Guide

27

BACnet MS/TP Communication Bus Fundamentals

following scheme, as it reuses the MAC Address and Network Number in the Device
Instance number to make it easier for a network administrator to know where a device is
located in the network. This is shown below.
Table 2-7: Recommended Numbering Scheme for MAC Addresses, Instance Numbers,
and Network Numbers
Description

Range

Example

BACnet/IP Network Number

0 to 65 534

Building Controller BACnet/IP Device Instance

Numbers: Multiples of 10 000

10 000 to
4 190 000

10 000
20 000

BACnet MS/TP Network Number: Building Controller

BACnet/IP Device Instance Number/1000 + 0,1,2,3,4
(for each LAN)

10 to 4190

10
11
20

BACnet MS/TP Device Instance Number =

EC-BOS BACnet MS/TP Network Number * 1000 +
MAC Address

10 000 to
4 190 256

10 007 where
MAC = 7

An example of this numbering system is shown below.

- Data Bus Management
- Data Bus Integration
- Device Configuration and
programming
- Graphical Interface
Configuration

- Alarm
- Trend Log
- Schedule
EC-NetAX Supervisor
IP Network # 1

- User Interface
- Remote Access
- Embedded EC-NetAX Pro
EC-NetAX Pro

Web Browser

Ethernet, TCP/IP, BACnet/IP, LONWORKS IP, XML, HTTP, oBIX

IP Network # 1
EC-BOSAX

EC-BOS MAC on Network # 10 = 0

EOL Terminator

IP Network # 1
DI: 10 000
EC-BOS MAC on Network # 11 = 0
EOL Terminator

BACnet
Router

DI: 20 000
EC-BOS MAC on Network # 20 = 0

EOL Terminator

MAC: 3
DI: 10 003
MS/TP
Network # 10

MAC: 4
DI: 10 004

MAC: 3
DI: 11 003
MS/TP
Network # 11

MAC: 4
DI: 11 004

MAC: 5
DI: 10 005

EOL Internally Set

MS/TP
Network # 20

MAC: 4
DI: 20 004

MAC: 5
DI: 11 005

MAC: 6
DI: 10 006

EOL
ON

MAC: 3
DI: 20 003

EOL
ON

EOL Internally Set

MAC: 5
DI: 20 005

MAC: 6
DI: 11 006

EOL
ON

MAC: 6
DI: 20 006

EOL Internally Set

KEY:
DI: Device Instance
EOL: End of Line
MAC: Media Access Control

Figure 2-16: BACnet MS/TP Numbering System for MAC Addresses, Device Instance
Numbers, and Network Numbers
When discovering devices with an EC-BOS which has the routing option
configured, it will discover all BACnet devices connected to all EC-BOSes. Make
sure to add only the devices connected to the MS/TP port of the specific EC-BOS
being configured. Using this numbering system will greatly help to identify those
devices that should be added to a given EC-BOS.
Setting the MAC Address
The MAC Address on most devices can be set through a DIP switch located on its faceplate,
or though the software interface of a handheld device for example.
An example of how to set the devices MAC Address DIP switch is shown below for a
Distech Controls ECB-203 (and higher) controllers.

28

Network Guide

BACnet MS/TP Communication Bus Fundamentals

ON

Must be set to the

OFF (0) position

Figure 2-17: Typical Device MAC Address DIP Switch Set to 82

The address is the sum of the numbers set to ON. For example, if the second (2), fifth (16),
and seventh (64) DIP switches are set to ON, the device MAC address is 82 (2 + 16 + 64).
Addresses from 3 to 127 are recommended to be used (see Table 2-6). See also How to Set
a DIP Switch on page 75.
Once the MAC Address has been changed, the power to the device must be power cycled
for it to take effect.
For Distech Controls ECB-VAVS and ECB-VAV Series or ECB-103, the MAC Address is set
with an EC-Smart-Vue. See Commissioning with an EC-Smart-Vue on page 55.
For more information about how to set the devices MAC Address, refer to the devices
hardware installation guide.

Network Guide

29

BACnet MS/TP Communication Bus Fundamentals

Inter-Building BACnet Connection

BACnet network connections between buildings must be made using BACnet/IP or FOX as
shown below.
- Data Bus Management
- Data Bus Integration
- Device Configuration and
programming
- Graphical Interface
Configuration

- Alarm
- Trend Log
- Schedule
EC-NetAX Supervisor
IP Network # 2

IP
Router

IP Network # 3

- User Interface
- Remote Access
- Embedded EC-NetAX Pro
EC-NetAX Pro

Web Browser

BACnet/IP, Fox
IP Network # 3

IP Network # 1
BBMD
EC-BOSAX

EC-BOS MAC on Network # 10 = 0

EOL Terminator

DI: 10 000
EC-BOS MAC on Network # 11 = 0
EOL Terminator

BBMD
EC-BOSAX

DI: 20 000
EC-BOS MAC on Network # 20 = 0

EOL Terminator

MAC: 3
DI: 10 003
MS/TP
Network # 10

MAC: 4
DI: 10 004

MAC: 3
DI: 11 003
MS/TP
Network # 11

MAC: 4
DI: 11 004

MAC: 5
DI: 10 005

EOL
ON

EOL Internally Set

MAC: 3
DI: 20 003
MS/TP
Network # 20

MAC: 4
DI: 20 004

MAC: 5
DI: 11 005

MAC: 6
DI: 10 006

EOL
ON

MAC: 6
DI: 11 006

EOL Internally Set

Building #1

MAC: 5
DI: 20 005

EOL
ON

MAC: 6
DI: 20 006

EOL Internally Set

Building #2

KEY:
DI: Device Instance
EOL: End of Line
MAC: Media Access Control

Figure 2-18: Typical Inter-Building Connection Using BACnet/IP or FOX

BACnet/IP Broadcast Management Device Service
Though BACnet/IP or FOX uses IP protocol to communicate, a standard IP router does not
forward broadcast messages which are important in BACnet to identify services that are
available within the BACnet internetwork.
When two Building Controllers communicate to each other over a standard IP connection
that is separated by an IP router, both Building Controllers need the BACnet/IP Broadcast
Management Device (BBMD) service to be configured and operational.
The BBMD service identifies BACnet messages on the BACnet MS/TP network that are
intended for a device located on another BACnet network. The BBMD service encapsulates
these messages into an IP message to the appropriate BBMD service of the other BACnet
MS/TP network(s). The BBMD service on these networks strips out the encapsulation and
sends the BACnet message on to the appropriate devices.
When sending BACnet messages across a standard IP connection that has an IP router,
there must be one BBMD service running on each BACnet MS/TP network.

30

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Power Supply Requirements

BACnet MS/TP is a Three Wire Bus
Even though data is transmitted over a 2-wire twisted pair, all EIA-485 transceivers interpret
the voltage levels of the differential signals with respect to a third voltage reference common
to all devices connected to the data bus (signal reference). In practice, this common signal
reference is provided by the buildings electrical system grounding wires that are required by
electrical safety codes worldwide. Without this signal reference, transceivers may interpret
the voltage levels of the differential data signals incorrectly, and this may result in data
transmission errors.
All Distech Controls devices use the 24V COM terminal as the signal reference point for the
data bus (see Table 2-1 for common device terminal labels). As a consequence, you must
wire the power supply (for any given number of devices) as shown in Figure 2-19, such that
the power bus that is connected to the 24V COM / C terminals are also connected at the
power supply to the buildings ground. This ensures that the 24V COM terminals of all
devices connected to any BACnet MS/TP bus in the building are at the same potential.
As specified by electrical safety codes worldwide, the buildings protective ground
network must not be used to conduct electrical current under normal conditions.
Such current can lift the reference voltage sensed at a controllers 24V COM
terminal, thus resulting in data transmission errors.
A mechanical ground is unacceptable: Do not use a pipe, conduit, or duct work for
a ground. The power supply must have a dedicated ground wire that comes from
the main electrical supply panel.
Any connection between buildings cannot be made with BACnet MS/TP. For
inter-building connections, it is recommended to use a BACnet/IP or FOX network
connection. Refer to Inter-Building BACnet Connection on page 30.
Power Supply
AC Power
Source
24 / 120 / 208 /
240 / 277 / 347 /
480 VAC, 1

BACnet Device

Fuse: 4A Max.
Fast Acting

24V AC/DC
24 VAC
24V COM

Electrical
System
Ground at
transformer
only

Maintain consistent
polarity when
connecting controllers
and devices to the
transformer.
The 24V COM / C
terminals of all devices
must be connected to
the power supply bus
that is grounded.

BACnet Thermostat
RC
C

Figure 2-19: The 24V COM / C Terminal of all Devices must be Connected to the
Grounded Power Supply Bus
The table below lists Distech Controls recommended power cable.

Network Guide

31

BACnet MS/TP Communication Bus Fundamentals

Table 2-8: Distech Controls Recommended Power Cable
Cable Type
AWG
Number of
Conductors

Non-Plenum Applications
(FT4)

Plenum Applications
(FT6)

Part Number

O.D. ()

Part Number

O.D. ()

18-2

07CBL-W181P-1002

5.0mm
0.20in.

07CBL-W181P-2051

5.0mm
0.20in.

16-2

07CBL-W161P-1031

4.8mm /
0.19in.

07CBL-W161P-2062

4.8mm /
0.19in.

14-2

07CBL-W141P-1081

7.2mm /
0.29in.

07CBL-W141P-2013

7.2mm /
0.29in.

Avoid Ground Lift

Power wiring runs should not be too long, nor have too many devices connected to it. Wiring
used to supply power to devices has a resistance that is proportional to the length of the
wiring run (see Table 2-9).
Table 2-9: Resistance of Common Copper Wire Sizes
AWG

Diameter ()

Area

Copper wire resistance

(inch)

(mm)

(kcmil)

(mm)

(/km)

(/1000 ft)

14

0.0641

1.628

4.11

2.08

8.286

2.525

16

0.0508

1.291

2.58

1.31

13.17

4.016

18

0.0403

1.024

1.62

0.823

20.95

6.385

If the power run from the power supply is relatively long and it supplies power to many
devices, a voltage will develop over the length of wire. For example, a 1000 ft of 18 AWG
copper wire has a resistance of 6.4 Ohms. If this wire is supplying 1 Ampere of current to
connected devices (as shown in Figure 2-20), the voltage developed across it will be 6.4
volts. This effect is called ground lift.
Electrical Power Run Length

Power Supply
AC Power
Source
24 / 120 / 208 /
240 / 277 / 347 /
480 VAC, 1

BACnet Device

Fuse: 4A Max.
Fast Acting

24V AC/DC
24 VAC
Reqv

Electrical
System
Ground

I=1A

24V COM

The equivalent resistance of a run of wire. For

example, a 1000 ft of 18 AWG copper wire
has a resistance of 6.4 Ohms. With 1 Ampere
of current, the voltage developed along the
length of the electrical power run for one
conductor will be 6.4 volts.

Figure 2-20: Ground Lift from a Long Power Run

Because the 24V COM terminal is the signal reference point for the data bus, ground lift
offsets the data bus voltage reference that is used to interpret valid data levels sent on the
data bus. If the ground lift is more than 7 volts peak, there is a risk of data corruption and
offline events due to the device being incapable of correctly reading data signals from the
data bus.
Techniques to Reduce Ground Lift
Reduce the impact of ground lift as follows:

32

Network Guide

BACnet MS/TP Communication Bus Fundamentals

Use a heavier gauge wire.

Add more wire runs. Connect these wire runs to the power supply in a star pattern.

For controllers that accept DC power (without triac outputs): Specify a 24 DC power
supply. The continuous and even voltage of a DC power supply makes more efficient
use of the power handling capabilities of a power run. A 24 DC power supply eliminates
the 2.5 multiplication factor associated with the peak AC current being 2.5 times the
average RMS AC current. See below.

Peak Current
Particular attention should be paid to the peak current absorbed by devices that are powered
by an AC circuit. All Distech Controls devices use half-wave rectifiers to supply their onboard
electronics (this is common with most controls manufacturers). With this configuration, the
peak AC current is approximately 2.5 times the average RMS AC current.
Transformer Selection and Determining the Maximum Power Run Length
Distech Controls devices are Class 2 Products. To conform to Class 2 installation
requirements, only use transformers of 100VA or less to power the device(s).
For VAV devices, determine the maximum number of VAVs that can be supplied by a single
power run cable supplied by a 100 VA transformer, according to the cables wire gauge and
the total cable length from the following table.
Table 2-10: Maximum Number of VAV Devices on a Power Run
AWG

Power Run Total

Cable Length

Maximum
Number of
Devices @ 7
VA per device1

Maximum
Number of
Devices @ 10
VA per device2

Maximum
Number of
Devices@ 15
VA per device3

144

75M (250 feet)

14

60M (200 feet)

14

45M (150 feet)

14

30M (100 feet)

16

60M (200 feet)

16

45M (150 feet)

16

30M (100 feet)

18

45M (150 feet)

18

30M (100 feet)

1.
2.
3.
4.

Typical VAV with 1 EC-Smart-Vue and actuator activated. No external loads.

Typical VAV with 1 EC-Smart-Vue, 2 triac loads (1.6 VA each), 1 analog output (20 mA), and actuator
activated.
Typical VAV with 1 EC-Smart-Vue, 4 triac loads (1.6 VA each), 2 analog outputs (20 mA each), and
actuator activated.
Device terminals are not capable of accepting two 14 AWG wires (when daisy-chaining devices). Use a
wire nut with a pig tail to make such a connection.

Any installation condition that is outside of the parameters of Table 2-10 should be avoided.
For non-VAV devices, determine the appropriate size transformer for the job as follows:

1. Add up the power requirements of all devices plus all connected output loads. Multiply
the total power needed by a multiplier of 1.3, as a security margin. For example, to
power five devices (15 VA each), the total load is 75 VA multiplied by 1.3 is 98 VA.
Choose a size of transformer just over this amount: For example, a 100 VA model.

2. When the total load of a number of devices requires a transformer with a rating greater
than 100 VA, use two or more transformers. Ensure that the load to be connected to
each transformer follows the guideline of Step 1 above.

Network Guide

33

BACnet MS/TP Communication Bus Fundamentals

Always use a separate transformer for each ECB-600 series controller and its
associated I/O Extension Modules.
Use an external fuse on the 24VAC side (secondary side) of the transformer, as shown in
Figure 2-19, to protect all controllers against power line spikes.
Maintain consistent polarity when connecting controllers and devices to the transformer, as
shown in Typical Device BACnet MS/TP LAN and Power Wiring Diagram on page 35. That
is, the 24V COM terminal of each controller and each peripheral must be connected to the
same terminal on the secondary side of the transformer. This transformer terminal must be
connected to the buildings ground. This ensures that the 24V COM terminals of all devices
connected to any BACnet MS/TP bus in the building are at the same potential.

34

Network Guide

Network Guide

24 VAC

Fuse: 4A Max.
Fast Acting

24V AC/DC

24V COM

Data Bus Shield:

Isolate with
electrical tape

24V COM

Electrical
System
Ground

24V AC/DC

Data Bus Shields: Twist

together and Isolate
with electrical tape

EOL OFF

EOL OFF

EOL OFF

Typical BACnet Device

NET+

NET-

First and last daisy-chained device:

- EOL Jumpers are ENABLED
All other Devices:
- EOL Jumpers are DISABLED

Data Bus: Shielded Twisted Pair Cable

Data Bus Shields: Twist

together and Isolate
with electrical tape

Typical BACnet Device

Data Bus Shields: Twist

together and Isolate
with electrical tape

Typical BACnet Device

24V COM

EOL ON

24V AC/DC

Typical BACnet Device

24V COM

Beware of Ground Lift. Too much current

over long wire runs can raise the ground
reference at the 24V COM terminals,
causing data bus transmission errors.

24V AC/DC

DC Power
Source

Equivalent
Fuse: 4A Max.
Fast Acting
24 VDC

AC Power
Source
(Mains)

When two or more devices share a single

power source, maintain polarity between
devices. For example, the 24V AC/DC
terminal of all devices must be connected
to the same power supply bus.

24VAC

OR

The shield of the data bus

must also be connected to
the electrical system
ground at only one point
usually at one end of the
bus as shown

Dedicated 24VAC Transformer

Neither side of secondary
connected to Electrical System
Ground

AC Power
Source
(Mains)

Data Bus Shield: Connect

to the S terminal

Electrical
System Ground

RS-485

Typical EC-BOS Device

12

24VDC

24VDC Power Supply, Polarity

is Not Critical No side should be connected
to Electrical System Ground

OPTIONALLY set the

EOL jumper internally
AND add a 120 Ohm
resistor as shown here

EOL ENABLED: For the

EC-BOS as a first or last
daisy-chained device:

Power
Input

EC-NPB-PWR
EC-NPB-PWRUN

Power
Module

BACnet MS/TP Communication Bus Fundamentals

Typical Device BACnet MS/TP LAN and Power

Wiring Diagram
An overview of the BACnet MS/TP LAN and power wiring is shown below.

NET+

NET-

NET+

NET-

NET+

NET-

35

LonWorks Communication Bus Fundamentals

CHAPTER 3
LONWORKS COMMUNICATION BUS
FUNDAMENTALS
This chapter describes the LONWORKS Communications Bus operating principals.
In This Chapter
Topic

36

Page

Network Architecture

37

TP/FT-10 Network Topologies

38

Network Cables

40

Extending the Network

42

Grounding a Network

43

Power Supply Requirements

44

Network Guide

LonWorks Communication Bus Fundamentals

Network Architecture
EC-NetAX Network Architecture
Single-Segment EC-NetAX Network
A single-segment EC-NetAX Network shown with EC-NetAX Supervisor and EC-NetAX Pro.
- Data Bus Management
- Data Bus Integration
- Device Configuration and
programming
- Graphical Interface
Configuration

- Alarm
- Trend Log
- Schedule
EC-NetAX Supervisor

- User Interface
- Remote Access
- Embedded EC-NetAX Pro
EC-NetAX Pro

Web Browser

Ethernet, TCP/IP, BACnet/IP, LONWORKS IP, XML, HTTP, oBIX

EC-BOSAX

LONWORKS Data Bus Segment

Segment 1

Central Plant

Air Handling Controllers

Figure 3-1: Single-Segment EC-NetAX Network

Inter-Building LONWORKS Connection
LONWORKS network connections between buildings must be made using TCP/IP with FOX
as shown below.
- Data Bus Management
- Data Bus Integration
- Device Configuration and
programming
- Graphical Interface
Configuration

- Alarm
- Trend Log
- Schedule
EC-NetAX Supervisor
IP Network # 2

IP
Router

IP Network # 3

- User Interface
- Remote Access
- Embedded EC-NetAX Pro
EC-NetAX Pro

Web Browser

TCP/IP with FOX

IP Network # 3

IP Network # 1
EC-BOS

AX

EC-BOSAX

Building #1

Building #2

Figure 3-2: Typical Inter-Building Connection Using IP/FOX

Network Guide

37

LonWorks Communication Bus Fundamentals

TP/FT-10 Network Topologies

The physical routing of the communication channel defines the network topology. The
channel and transceiver types define the requirements and limitations of each wiring
topology.
TP/FT-10 network segments require termination for proper data transmission performance.
Free topology and bus network topology differ in their termination requirements. The
following sections describe the various network topologies, their terminator types and
termination procedures.

Bus Topology
A bus topology is a physical routing of the communication channel that includes a distinct
beginning and end. It is also known as a daisy-chain topology.

...
Figure 3-3: Bus Topology
TP/FT-10 Bus Topology Network Termination
For bus topology type networks, use the following terminators at each end of the bus
topology channel (2 terminators per channel in total):
+
C1
R1
C2

R1 = 105, 1%, W
C1 = 100F, 50V
C2 = 100F, 50V

Distech Controls Part Number:

PDIDI-BT-TP10XX

It is recommended to use a bus topology when designing a network. Bus

topologies are the easiest to troubleshoot and the maximum wiring length in a
bus topology is greater than that for a free topology. See the section for
detailed information about wiring lengths and network cable considerations.

Free Topology
Free topology is a flexible wiring structure for communication channels that include ring, star,
loop and/or combination wiring structures. A free topology does not have restrictions such as
branching restrictions, stub length limits, device separation requirements or strict termination
guidelines. The free topology transmission specification only has two requirements that must
be met for proper system operation. The distance from each transceiver to all other
transceivers and to the termination must not exceed the maximum node-to node distance. If
multiple paths exist (i.e. a loop topology) then the longest path should be used for
calculations. The maximum total wire length is the total length of wire within a segment. See
the section for detailed information about wiring lengths and network cable considerations.

38

Network Guide

LonWorks Communication Bus Fundamentals

Figure 3-4: Free Topology

TP/FT-10 Free Topology Network Termination
For free topology type networks (TP/FT-10 only), use the terminator shown below for each
free topology channel. It is recommended to always place the terminator near the router for
consistency.
+
C1
R1
C2

Network Guide

R1 = 52.3, 1%, W
C1 = 100F, 50V
C2 = 100F, 50V

Distech Controls Part Number:

PDIDI-FT-TP10XX

39

LonWorks Communication Bus Fundamentals

Network Cables
The following section identifies the type of cabling that may be used in a TP/FT-10 twisted
pair LONWORKS network. The recommendations presented herein are intended to assist
network integrators and OEMs and are provided for informational purpose only.
For more information and detailed explanations on network topology and wire length
restrictions refer to the Junction Box and Wiring Guideline for Twisted Pair LonWorks
Networks. These guides can be downloaded from Echelons web site at www.echelon.com.

As a general rule, the TP/FT-10 channel communication cables should not

be run close to high voltage power cables.
All wiring must comply with applicable national, state and local wiring
electrical codes, ordinances, and regulations.

Parameter

Details

Nickname

Free Topology

Raw Bit rate

78kbps

Packets per second

144/168

Peak traffic

180/210

Topology

Free, Bus

Termination

Maximum number of
devices per segment

64

One per segment in free topology

Two per segment in bus topology
A maximum of 128 devices per channel can be
installed on a TP/FT-10 when a router or
repeater is used. See Extending the Network on
page 42 for more information.

Table 3-1 TP/FT-10 Channel Attributes

TP/FT-10 Cable specifications

Two types of cable are recommended for TP/FT-10 channel installations.
Type 1:
22 AWG (0.65mm), 1 twisted pair (1P), stranded conductor (STR), tinned copper (TNC),
PVC insulation, PVC jacket, unshielded, plenum FT6, CSA 600V, UL 300V.
Parameter

Details

Conductor Gauge (AWG)

22 AWG

Conductor Count

2 Conductors (twisted pair)

Conductor Type

Stranded conductor

Material

Tinned copper

Plenu:

Plenum rated

NEC Rating

UL listed art 800 plenum

CSA
Flame rated
Table 3-2 TP/FT-10 Type 1 Cable Attributes

40

Network Guide

LonWorks Communication Bus Fundamentals

Untwisted wires or cables containing flat or parallel untwisted conductors must not
be used on an LONWORKS twisted pair channel. The use of theses wires/cables may
result in improper network operation and could, in certain circumstances, result in
damage to nodes connected to such a channel.
In a bus topology, the maximum wire length is 1400 meters (4593 feet). The maximum stub
length on a TP/FT-10 channel is 3 meters (10 feet). A stub is a section of unterminated
transmission line that branches off the main transmission line of interest. The branch line is
terminated as an open circuit.
In a free topology, the maximum length is 400 meters (1312 feet) node-to-node and 500
meters (1640 feet) total wire length.
In the event that the limits on the number of transceivers or total wire distance are
exceeded, then one FTT physical layer repeater can be added to interconnect two
segments and double the overall system capability.
Type 2:
16 AWG (1.3mm), 1 twisted pair (1P), stranded conductor (STR), tinned copper (TNC),
PVC insulation, PVC jacket, unshielded, plenum FT6, CSA 600V or UL 300V.
Parameter

Details

Conductor Gauge (AWG)

16 AWG

Conductor Count

2 Conductors (twisted pair)

Conductor Type

Stranded conductor

Material

Tinned copper

Plenu:

Plenum rated

NEC Rating

UL listed art 800 plenum

CSA
Flame rated
Table 3-3: TP/FT-10 Type 2 Cable Attributes
In bus topology, the maximum wire length is 2700 meters (8858 feet). The maximum stub
length on a TP/FT-10 channel is 3 meters (10 feet).
In free topology, the maximum length is 500 meters (1640 feet) node-to-node and 500
meters (1640 feet) total wire length.
For more information about extending the network to a sensor, see Connecting to
the LAN through an EC-Smart-Vue on page 57.

Network Guide

41

LonWorks Communication Bus Fundamentals

Extending the Network

In the event that the limits on the number of transceivers or total wire distance are exceeded,
then one repeater or a router can be added to interconnect two segments and double the
overall system capability.
A maximum of 128 devices per channel can be installed on a TP/FT-10. However, after 64
devices you must add a repeater in order to add more devices up to the 128 device limit.
Alternately, once you have 64 devices on an FT-10 channel you can add a router instead of
a repeater. However the router will create a new channel for your new devices. A router
recommended for optimal performance.

Bus Toplogy

Repeater
or
Router

...
T
T

Bus Toplogy

...
Figure 3-5: Repeater or Router

42

Network Guide

LonWorks Communication Bus Fundamentals

Grounding a Network
Grounding Shielded Twisted Pair Cable
When using Shielded Twisted Pair, terminate the twisted pair and ground the cable shield,
as shown in Figure 3-6.

Figure 3-6: Grounding Shielded Twisted Pair Cable

It is recommended to use shielded cable only when the network cable is outside of
the building since it will be subjected to electromagnetic interference (EMI).
The twisted pair is terminated according to the guidelines listed in the previous sections. The
cable shield should be grounded using a capacitor to tie the shield to earth ground and a
large value resistor should be used to bleed off any static charge on the shield.
Tie the shield to earth ground through a capacitor, instead of with a direct connection. This
prevents DC and 50/60 Hz ground paths from forming through the shield. Typical values for
Cc and Rb are as follows:
Cc = 0.1 F, 10%, Metalized Polyester, 100V
Rb = 470k, 1/4W, 5%
The cable shield should be grounded at least once per segment, and preferably at each
node. Grounding the shield at every node (using the shield grounding circuit shown in Figure
3-6) will assist in suppressing 50/60Hz standing waves.

Building Entrance Protection

Use shielded twisted pair wire for networks, or portions of networks, that are run outside of
buildings. The shield should be connected to earth at each building entry point via a data-line
lightning/surge arrester, to conduct lightning strike energy or power surges directly to ground
and prevent their entry into the building via the control systems network. Data-line
lightning/surge arresters should also be used at each building entrance and should be
connected to the network data lines. Refer to the LonWorks FTT-10A Free Topology
Transceiver Users Guide available from Echelon, for more information about building
entrance protection.

Network Guide

43

LonWorks Communication Bus Fundamentals

Power Supply Requirements

For any given number of devices, wire the power supply as shown in Figure 3-7 and Figure
3-8, such that the power bus that is connected to the 24V COM terminals are also connected
at the power supply to the buildings ground.
As specified by electrical safety codes worldwide, the buildings protective ground
network must not be used to conduct electrical current under normal conditions.
A mechanical ground is unacceptable: Do not use a pipe, conduit, or duct work for
a ground. The power supply must have a dedicated ground wire that comes from
the main electrical supply panel.
Controller 1
24V AC
24V COM
Controller 2
24V AC
24V COM

Fuse: 4 A Max.
Fast Acting
24 VAC

AC

Transformer
Electrical System Ground
- At Transformer Only

Figure 3-7:
Power wiring AC: The 24V COM Terminal of all Devices must be
Connected to the Grounded Power Supply Bus
Controller 1
24V AC/DC
24V COM
Controller 2
24V AC/DC
24V COM

Fuse: 4 A Max.
Fast Acting

24 VDC

Electrical System Ground

- At Power Supply Only

Figure 3-8:
Power wiring DC: The 24V COM Terminal of all Devices must be
Connected to the Grounded Power Supply Bus
The table below lists Distech Controls recommended power cable.
Table 3-4: Distech Controls Recommended Power Cable
Cable Type
AWG
Number of
Conductors

Non-Plenum Applications
(FT4)

Plenum Applications
(FT6)

Part Number

O.D. ()

Part Number

O.D. ()

18-2

07CBL-W181P-1002

5.0mm
0.20in.

07CBL-W181P-2051

5.0mm
0.20in.

16-2

07CBL-W161P-1031

4.8mm /
0.19in.

07CBL-W161P-2062

4.8mm /
0.19in.

14-2

07CBL-W141P-1081

7.2mm /
0.29in.

07CBL-W141P-2013

7.2mm /
0.29in.

Transformer Selection and Determining the Maximum Power Run Length

Distech Controls devices are Class 2 Products. To conform to Class 2 installation
requirements, only use transformers of 100VA or less to power the device(s).
For VAV devices, determine the maximum number of VAVs that can be supplied by a single
power run cable supplied by a 100 VA transformer, according to the cables wire gauge and
the total cable length from the following table.

44

Network Guide

LonWorks Communication Bus Fundamentals

Table 3-5: Maximum Number of VAV Devices on a Power Run
AWG

Power Run Total

Cable Length

Maximum
Number of
Devices @ 7
VA per device1

Maximum
Number of
Devices @ 10
VA per device2

Maximum
Number of
Devices@ 15
VA per device3

144

75M (250 feet)

14

60M (200 feet)

14

45M (150 feet)

14

30M (100 feet)

16

60M (200 feet)

16

45M (150 feet)

16

30M (100 feet)

18

45M (150 feet)

18

30M (100 feet)

1.
2.
3.
4.

Typical VAV with 1 EC-Smart-Vue and actuator activated. No external loads.

Typical VAV with 1 EC-Smart-Vue, 2 triac loads (1.6 VA each), 1 analog output (20 mA), and actuator
activated.
Typical VAV with 1 EC-Smart-Vue, 4 triac loads (1.6 VA each), 2 analog outputs (20 mA each), and
actuator activated.
Device terminals are not capable of accepting two 14 AWG wires (when daisy-chaining devices). Use a
wire nut with a pig tail to make such a connection.

Any installation condition that is outside of the parameters of Table 3-5 should be avoided.
For non-VAV devices, determine the appropriate size transformer for the job as follows:

1. Add up the power requirements of all devices plus all connected output loads. Multiply
the total power needed by a multiplier of 1.3, as a security margin. For example, to
power five devices (15 VA each), the total load is 75 VA multiplied by 1.3 is 98 VA.
Choose a size of transformer just over this amount: For example, a 100 VA model.

2. When the total load of a number of devices requires a transformer with a rating greater
than 100 VA, use two or more transformers. Ensure that the load to be connected to
each transformer follows the guideline of Step 1 above.
Always use a separate transformer for each ECL-600 series controller and its
associated I/O Extension Modules.
Use an external fuse on the 24VAC side (secondary side) of the transformer, as shown in
Figure 3-7 and Figure 3-8, to protect all controllers against power line spikes.
Maintain consistent polarity when connecting controllers and devices to the transformer.
That is, the 24V COM terminal of each controller and each peripheral must be connected to
the same terminal on the secondary side of the transformer. This transformer terminal must
be connected to the buildings ground.

Network Guide

45

Subnetwork Installation Guidelines

CHAPTER 4
SUBNETWORK INSTALLATION GUIDELINES
This chapter describes the Extension and Room Sensor Bus Installation Guidelines.
In This Chapter
Topic

46

Page

About the Subnetwork Bus

47

ECx-4XX Subnetwork Bus

48

EC-Smart-Vue Subnetwork Bus

52

Network Guide

Subnetwork Installation Guidelines

About the Subnetwork Bus

Introduction
The subnetwork bus uses the EIA-485 standard for data transmission. The ECB-600 and
ECL-600 controllers use this bus to support the ECx-4XX Series I/O Extension Modules
through a 2-wire shielded cable.
All Distech Controls ECB-600 and ECL-600 series controllers also use the subnetwork bus
to support one or more EC-Smart-Vue(s) using standard structural cabling. For the
EC-Smart-Vue, the subnetwork bus also extends the LAN to the EC-Smart-Vue room sensor
to provide convenient network access for maintenance and troubleshooting purposes (see
Connecting to the LAN through an EC-Smart-Vue on page 57).
Sub-Network Bus Total Length: 300 m (1 000 ft) Maximum
EC-Smart-Vue Sub-Network Bus: 200 m (650 ft)
Maximum

ECx-4XX Sub-Network Bus: 300 m (1 000 ft)

Maximum

Typical ECx-4XX Series Extension I/O Modules For use

with an ECB-600 / ECL-600 Series Controller Only

Typical ECB-600 /
ECL-600 Controller

EC-Smart-Vue Sub-Network Bus Cat 5e Cable with RJ-45 Connectors

ECx-4XX Sub-Network Bus

LAN Access
Connector

2-Wire Shielded

Typical Adaptor /
Network Interface

- Temporary
Commissioning and
Maintenance
Connection
- No EOL Resistors are
Necessary

EC-Net Pro

Figure 4-1: Subnetwork Bus Overview Showing the EC-Smart-Vue Subnetwork Bus
and the ECx-4XX Subnetwork Bus
Subnetwork Bus Total Length
The total maximum length of all subnetwork buses, including both the length of the
EC-Smart-Vue subnetwork bus and the ECx-4XX subnetwork bus is 300 m (1 000 ft). The
maximum length of the EC-Smart-Vue subnetwork bus is 200 m (650 ft). The maximum
length of the ECx-4XX subnetwork bus is 300 m (1 000 ft).

Network Guide

47

Subnetwork Installation Guidelines

ECx-4XX Subnetwork Bus

Introduction
The ECx-4XX subnetwork bus is used to connect ECx-4XX Series I/O Extension Modules to
an ECB-600 or ECL-600 controller.
ECx-4XX Subnetwork Bus is Polarity Sensitive
The polarity of the ECx-4XX subnetwork bus must be respected as shown in Figure 4-4. All
terminals identified as SUBNET+ must be connected to the same conductor. Likewise, all
terminals identified as SUBNET- must be connected to the same conductor.

ECx-4XX Subnetwork Bus Physical Specifications and Cable

Requirements
Cables composed of stranded conductors are preferred over solid conductors as stranded
conductor cable better resist breakage during pulling operations. Distech Controls highly
recommends the following ECx-4XX subnetwork bus cable specifications be respected.
Table 4-1: ECx-4XX Subnetwork Bus Physical Specifications and Cable Requirements
Parameter

Details

Maximum number of ECx-4XX Series I/O

Extension Modules

Media

Shielded, twisted pair

Characteristic impedance

100-130 Ohms

Distributed capacitance

Less than 100 pF per meter (30 pF per

foot)

Maximum length of the EC-Smart-Vue

subnetwork bus and the ECx-4XX
subnetwork bus (total length)

300 m (1 000 ft) Maximum

Polarity

Polarity sensitive

Multi-drop

Daisy-chain (no T-connections, no

routers)

EOL terminations

Built-in. Must be set / enabled on the last

I/O Extension Module only.

Shield grounding

See ECx-4XX Subnetwork Bus Shield

Grounding Requirements on page 50

Distech Controls recommended cable is shown below.

Table 4-2: Distech Controls Recommended Cable Types for the ECx-4XX Subnetwork
Bus
Bus Cable Type

Part Number

O.D. ()

300 meters (1000 feet), 24 AWG Stranded, Twisted

Pair Shielded Cable FT6, Rated for Plenum
Applications

07CBL-BACNET

3.75mm
(0.148 in.)

ECx-4XX Subnetwork Bus Topology and End-of-Line

Terminations
Only a daisy-chain topology is acceptable for the ECx-4XX subnetwork bus. T-connections
and routers are not allowed.

48

Network Guide

Subnetwork Installation Guidelines

When ECx-4XX I/O Extension Modules are installed with an ECB-600 / ECL-600, only the
EOL terminations of the ECB-600 / ECL-600 and the last ECx-4XX are set to ON. All other
ECx-4XX I/O Extension Modules must have their EOL terminations set to OFF. This is
shown below.
Typical ECx-4XX Series Extension I/O Modules For use
with an ECB-600 / ECL-600 Series Controller Only

Typical ECB-600 /
ECL-600 Controller

ECx-4XX Sub-Network Bus

2-Wire Shielded

Inside
ECx-4XX

Inside
ECx-4XX

EOL OFF

EOL OFF

EOL ON

EOL ON

For ECx-4XX:
For ECB-600 / ECL-600, the
Sub-Network EOL is set to ON

Last daisy-chained ECx-4XX:

EOL Jumper is ON
All other ECx-4XX:
EOL Jumpers are OFF

Figure 4-2: Setting the EOL Terminations on the ECx-4XX Subnetwork Bus
When ECx-4XX I/O Extension Modules are installed with an ECB-600 / ECL-600 and with
EC-Smart-Vue sensor(s), only the EOL terminations the last ECx-4XX and the last EC Smart
Vue are set to ON. All other ECx-4XX I/O Extension Modules and EC-Smart-Vues must
have their EOL terminations set to OFF. This is shown below.
Typical ECB-600 /
ECL-600 Controller

EC-Smart-Vue Sub-Network Bus Cat 5e

Cable with RJ-45 Connectors

Typical ECx-4XX Series Extension I/O Modules For use

with an ECB-600 / ECL-600 Series Controller Only

ECx-4XX Sub-Network Bus

2-Wire Shielded

Inside
ECx-4XX

Back of
EC-Smart-Vue

OFF

EOL

ON

EOL OFF

For EC-Smart-Vue:
- Last daisy-chained EC-Smart-Vue:
EOL Jumper is ON
- All other EC-Smart-Vue:
EOL Jumpers are OFF

EOL ON

For ECx-4XX:
-

Last daisy-chained ECx-4XX:

EOL Jumper is ON
All other ECx-4XX:
EOL Jumpers are OFF

Figure 4-3: Setting the EOL Terminations on the ECx-4XX Subnetwork Bus when
EC-Smart-Vue Sensors are used
ECx-4XX devices and EC-Smart-Vue sensors are factory-set with the EOL set to OFF by
default.

Network Guide

49

Subnetwork Installation Guidelines

ECx-4XX Subnetwork Bus Shield Grounding Requirements

The best protection against interference is to use properly grounded shielded cable for the
ECx-4XX subnetwork bus. For this, the I/O Extension Modules on the ECx-4XX subnetwork
bus must be daisy-chained together with the cable shield twisted together and isolated with
electrical at each I/O Extension Module.
When using an ECB-600 / ECL-600, the shielding of the ECx-4XX subnetwork bus cable
must be connected to the electrical system ground at one point only.

ECx-4XX SubNetwork Bus

SUBNET -

Data Bus: Shielded

Twisted Pair Cable

ECx-4XX Sub-Network Bus

Shields: Twist together and
Isolate with electrical tape

Electrical
System
Ground

SUBNET +

ECx-4XX

SUBNET +

SUBNET -

ECx-4XX

SUBNET+

SUBNET -

ECB-600
ECL-600

ECx-4XX SubNetwork Bus

Shield: Isolate
with electrical
tape

Figure 4-4: ECB-600 / ECL-600: ECx-4XX Subnetwork Bus Shielding

ECx-4XX I/O Extension Module Addressing

Each I/O Extension Module on an ECx-4XX subnetwork bus needs to be set to a unique
address. The range of valid addresses is 1 to 7.
Table 4-3: I/O Extension Module Address DIP Switch Settings
Switch Position

Value

OFF

OFF

OFF

Invalid

ON

OFF

OFF

OFF

ON

OFF

ON

ON

OFF

OFF

OFF

ON

ON

OFF

ON

OFF

ON

ON

ON

ON

ON

An example of how to set an I/O Extension Module address DIP switch is shown below.

50

Network Guide

Subnetwork Installation Guidelines

ON

Must be set to the

OFF (0) position

Figure 4-5: Typical I/O Extension Module Address DIP Switch Set to 2

Power Supply Requirements

The ECB-600 / ECL-600 and the associated I/O Extension Modules must have their own
dedicated power supply. To size the power supply transformer, see Transformer Selection
and Determining the Maximum Power Run Length on page 33.
The ECx-4XX subnetwork bus is a three-wire bus that has specific installation requirements:
Follow all requirements described in Power Supply Requirements on page 31 for the ECB600 / ECL-600 and the associated I/O Extension Modules.

Network Guide

51

Subnetwork Installation Guidelines

EC-Smart-Vue Subnetwork Bus

Introduction
The EC-Smart-Vue subnetwork bus is used to connect EC-Smart-Vue sensors to any
Distech Controls ECB controller or ECL-600 controller.
Never connect an IP network to the SUBNET PORT connector of a controller or to
an EC-Smart-Vue. Equipment damage may result.

EC-Smart-Vue Subnetwork Bus Cable Requirements

The EC-Smart-Vue subnetwork bus uses common Cat5e structural cabling fitted with RJ-45
connectors. If you make your own patch cable, use Category 5e cable and crimp the RJ-45
connectors at both ends of the cable either as T568A or T568B.
Table 4-4: EC-Smart-Vue Subnetwork Bus Physical Specifications and Cable
Requirements
Parameter

Details

Maximum number of EC-Smart-Vue

Room Sensors

See Controller Data Sheet

Media

Cat 5e Patch Cable with RJ-45

Connectors

RJ-45 Pin Configuration

Four (4) pairs required. Straight-through

wiring. Crimp connectors as per T568A or
T568B (both cable ends must be crimped
the same way).
See Table 4-5 and Figure 4-6.

Characteristic impedance

100-130 Ohms

Distributed capacitance

Less than 100 pF per meter (30 pF per

foot)

Maximum length of the EC-Smart-Vue

subnetwork bus and the ECx-4XX
subnetwork bus

300 m (1 000 ft) Maximum

Maximum EC-Smart-Vue subnetwork bus

Length

200 m (650 ft) Maximum

Polarity

Polarity sensitive

Multi-drop

Daisy-chain (no T-connections)

EC-Smart-Vue room sensors have two
RJ-45 female pass-through connectors to
facilitate daisy-chain connections

EOL terminations

Must be set / enabled on the last room

sensor only

Shield grounding

Not applicable

Crimp both ends of the cable either as T568A or T568B as shown below.

52

Network Guide

Subnetwork Installation Guidelines

Table 4-5: T568A and T568B Terminations for an RJ-45 Connector
Pin
1

T568A (at both cable ends)

T568B (at both cable ends)

Pair

Pair

Color

2
white/green stripe

white/orange stripe

2
green solid

orange solid

3
white/orange stripe

white/green stripe
1

blue solid
5

blue solid

1
white/blue stripe

white/blue stripe

3
orange solid

green solid

4
white/brown stripe

Color

white/brown stripe
4

brown solid

brown solid

The final result of a crimped RJ-45 connector is shown graphically below.

T568A

T568B

1 2 3 4 5 6 7 8

Key:

1 2 3 4 5 6 7 8

Stripe Solid

Pair 3 Pair 1 Pair 2 Pair 4

Pair 2 Pair 1 Pair 3 Pair 4

Figure 4-6: Pins on RJ-45 Jack Face

Distech Controls recommends the cables shown below. Cables fitted with connectors are
wired as T568B.
Table 4-6: Distech Controls Recommended Cable Types for the EC-Smart-Vue
Subnetwork Bus
Bus and Cable
Type

Non-Plenum Applications (Use in

Conduit - FT4)
Part Number

9m (30 ft), Cat 5e Cable 07CBL-PATCHCORD30-FT4

fitted with RJ-45
Connectors
15m (50 ft), Cat 5e Cable 07CBL-PATCHCORD50-FT4
fitted with RJ-45
Connectors
22m (75 ft), Cat 5e Cable 07CBL-PATCHCORD75-FT4
fitted with RJ-45
Connectors
30m (100 ft), Cat 5e
07CBL-PATCHCORD100-FT4
Cable fitted with RJ-45
Connectors

Network Guide

O.D. ()1

Plenum Applications (FT6)

Part Number

O.D. ()1

4.6mm (0.18in.)

07CBL-PATCHCORD30-FT6

4.6mm (0.18in.)

4.6mm (0.18in.)

07CBL-PATCHCORD50-FT6

4.6mm (0.18in.)

4.6mm (0.18in.)

07CBL-PATCHCORD75-FT6

4.6mm (0.18in.)

4.6mm (0.18in.) 07CBL-PATCHCORD100-FT6 4.6mm (0.18in.)

53

Subnetwork Installation Guidelines

Bus and Cable
Type

Non-Plenum Applications (Use in

Conduit - FT4)
O.D. ()1

Part Number
300 meters (1000 feet),
Cat 5e Cable Without
Connectors
100 Crimp RJ-45
Connectors

Plenum Applications (FT6)

O.D. ()1

Part Number

07CBL-W244P-1446WHTB

4.6mm (0.18in.)

07CBL-W224P-2176WHTB

4.6mm (0.18in.)

07CBL-PATCHCONNECTOR

N/A

07CBL-PATCHCONNECTOR

N/A

Outer Cable diameter This does not factor the RJ-45 connector.

EC-Smart-Vue Subnetwork Bus Topology and End-of-Line

Terminations
Only a daisy-chain topology is acceptable for the EC-Smart-Vue subnetwork bus. Tconnections are not allowed. EC-Smart-Vue sensors are factory-set with the EOL
termination set to OFF by default.
When one or more EC-Smart-Vues are installed with an ECB-VAVS / ECB-VAV, ECB-103,
ECB-203, ECB-400 Controller Series, only the EOL terminations of the last EC-Smart-Vue
are set to ON. All other EC-Smart-Vues must have their EOL terminations set to OFF. The
ECB-VAVS / ECB-VAV, ECB-103, ECB-203, ECB-400 Controller Series must be the first
devices on the bus as the EOL termination in these devices are permanently enabled. This
is shown below.
EC-Smart-Vue Sub-Network Bus Cat 5e Cable with RJ-45 Connectors

Back of
EC-Smart-Vue

EOL set to ON
at the last
sensor at the
end of the Bus

ON
OFF

EOL

Controller Series:
ECL-VAVS / ECL-VAV
ECL-103
ECL-203
ECL-300
ECL-400
ECB-VAVS / ECB-VAV
ECB-103
ECB-203
ECB-300
ECB-400

Figure 4-7: Setting the EOL Terminations on the EC-Smart-Vue Subnetwork Bus for
the ECB-VAVS / ECB-VAV, ECB-103, ECB-203, ECB-400 Controller Series
When one or more EC-Smart-Vues are installed with an ECB-600 / ECL-600, only the EOL
terminations the ECB-600 / ECL-600 and the last EC Smart Vue are set to ON. All other
EC-Smart-Vues must have their EOL terminations set to OFF. This is shown below.

54

Network Guide

Subnetwork Installation Guidelines

EC-Smart-Vue Sub-Network Bus Cat 5e Cable with RJ-45 Connectors

Controller Series:
ECB-600
ECL-600

Inside
ECB/ECL-600

Back of
EC-Smart-Vue

EOL OFF
EOL ON

ON
OFF

EOL

For ECB-600 / ECL-600, set the

Sub-Network EOL to ON

EOL set to ON
at the last
sensor at the
end of the Bus

Figure 4-8: Setting the EOL Terminations on the EC-Smart-Vue Subnetwork Bus

Commissioning with an EC-Smart-Vue

Setting the EC-Smart-Vue Subnet ID
ECB and ECL Series controllers can be commissioned with an EC-Smart-Vue. The default
Subnet ID for an EC-Smart-Vue is 1. To commission an ECB / ECL Series controller, the
EC-Smart-Vues Subnet ID must be set to 1. If the EC-Smart-Vues Subnet ID has been set
to another value (for example, the display flashes error code 1 with the Bell icon when the
EC-Smart-Vue is connected to a controller for commissioning), change the Subnet ID to 1 as
follows:

1. Connect an EC-Smart-Vue to the controller with a Cat 5e patch cable. Wait for the Bell
icon and the number 1 to flash on the display.

2. Press and hold the Menu button

for 5 seconds to enter the password menu. 10000 is

shown on the display.

3. Use the down button

4. Use the Menu button

to set the number to 9995 (this is the default password).

to select SUBNET ID. The current controllers Subnet ID is

shown.
to set the controllers Subnet ID. Tip: Hold down
either the up or down button to fast-advance the display value.

5. Use the up and down buttons

6. Press the Menu button once to apply the value.

7. Press and hold the Menu button for 5 seconds to exit the configuration menu.
The EC-Smart-Vue can now be used to go from one ECB / ECL Series controller to the next
for commissioning purposes.
Commissioning ECB-Series Controllers
To commission a controller with a DIP switch located on the faceplate, first set the DIP
switch to 0 (all off). When using an EC-Smart-Vue for commissioning ECB Series controllers
(before code is downloaded to the controller from EC-gfxProgram), connect an
EC-Smart-Vue to the controller with its Subnet ID set to 1. During commissioning, the
EC-Smart-Vue is used to set the controllers BACnet MAC Address and Baud rate. For
ECB-VAV controllers, commissioning can be used to perform application selection if needed.
Applications are pre-loaded programs that enable the ECB-VAV to control a typical VAV box.
Set the EC-Smart-Vues Subnet ID and the connected controllers MAC Address as follows:

1. Connect an EC-Smart-Vue to the controller with a Cat 5e patch cable. Wait for the
display to show the room temperature.

Network Guide

55

Subnetwork Installation Guidelines

2. Press and hold the Menu button

for 5 seconds to enter the password menu. 10000 is

shown on the display.

3. Use the down button

to set the number to 9995 (this is the default password).
4. Use the Menu button to select GEN CFG.
5. Press the down button
once to enter the GEN CFG submenu. The MAC ADDRESS
menu is shown with the current controllers BACnet MAC Address.
to set the controllers MAC Address. Only
addresses from 1 to 127 are recommended to be used.

6. Use the up and down buttons

7. Press the Menu button once to apply the value.

8. Press and hold the Menu button for 5 seconds to exit the configuration menu.
Once the BACnet MS/TP network is operational, the controller can be programmed with
EC-gfxProgram. For each EC-Smart-Vue, set its Subnet ID number to the block number of
its associated CommSensor block in EC-gfxProgram. This is done in the EC-Smart-Vues
GEN CFG menu under SUBNET ID.
Setting the BAUD Rate for ECB-Series Controllers (optional)
For information about what the BACnet MS/TP network baud rate should be set to, see Data
Bus Devices and Baud Rate on page 13.
By default, the BAUD rate for the controller is set to automatically detect the current
communication BAUD rate of the connected BACnet MS/TP network (AUTO). This is the
preferred setting for a controller. However, at least one controller on the BACnet MS/TP
network data bus must have its BAUD rate set. The preference is to set the building
controllers BAUD rate (if present). Otherwise, set the BAUD rate on one controller that will
set the BAUD rate for all other controllers (to act as the master for setting the BAUD rate).
When the Baud rate is set to AUTO, the controller cannot initiate any
communication until it has detected the baud rate of the BACnet MS/TP network.
If all controllers on the BACnet MS/TP network are set to AUTO, then all
controllers will not communicate.
Set the connected controllers BAUD rate as follows:

1. Connect an EC-Smart-Vue to the controller with a Cat 5e patch cable. Wait for the
display to show the room temperature.

2. Press and hold the Menu button

for 5 seconds to enter the password menu. 10000 is

shown on the display.

3. Use the down button

4. Use the Menu button
5. Press the down button

to set the number to 9995 (this is the default password).

to select GEN CFG.
once to enter the GEN CFG submenu. The MAC ADDRESS

menu is shown.

6. Use the Menu button

to select BAUD RATE. The current controllers BAUD rate is

shown.
to set the controllers Baud rate. AUTO detects and
uses the Baud rate currently being used by the BACnet MS/TP network.

7. Use the up and down buttons

8. Press the Menu button once to apply the value.

9. Press and hold the Menu button for 5 seconds to exit the configuration menu.

56

Network Guide

Subnetwork Installation Guidelines

Connecting to the LAN through an EC-Smart-Vue

For a LONWORKS Network
Set the two Net to Subnet Port Settings jumpers inside the ECL series controller to
Enable to connect the main LONWORKS network to the EC-Smart-Vue subnetwork
Cat5e cable.

Net to Subnet
Port Settings
Enable
Disable
Enable
Disable

Figure 4-9: ECL-Series controllers: Set Net to Subnet Port Settings

Jumpers to Enable
This will create a free-topology LONWORKS network Comply with the maximum
cable lengths for a free-topology LONWORKS shown in Network Cables on page 40.
This must include the cable length between the controller and the EC-Smart-Vue.
The length of the EC-Smart-Vue subnetwork bus must also comply with the
restrictions shown in Subnetwork Bus Total Length on page 47.
22AWG (0.65mm) Unshielded Twisted Pair Network Cable
Controller

EC-Smart-Vue

Free-Topology
Network

Cat5e network cable:

EC-Smart-Vue Sub-Network
Bus and LONWORKS Network

Figure 4-10: LonWorks Network Free Topology

To temporarily access the LAN for commissioning and maintenance purposes,
connect a LON USB Network Interface to the stereo audio plug located on the lower
edge of the EC-Smart-Vue.
Wire a standard three-conductor 3.5 mm () stereo jack as shown below.

Network Guide

57

Subnetwork Installation Guidelines

LAN Access
Connector
LON1
LON2
Shield

To Portable Router

EC-Net Pro

- Temporary
Commissioning and
Maintenance
Connection

LON USB Network

Interface

Figure 4-11: 3.5mm Stereo Jack Connection for a LONWORKS Network

Interface
Ensure the BAC/LON jumper in the EC-Smart-Vue is set to the LON position.

BAC
LON

3.5 mm (1/8) Network

Access Jack

Network Type
Jumper

Figure 4-12: BAC/LON Jumper Set to the LON (LONWORKS) Position

For a BACnet Network

To temporarily access the LAN for commissioning and maintenance purposes,
connect a portable adaptor to the stereo audio plug located on the lower edge of the
EC-Smart-Vue.
The BACnet MS/TP adaptor must have an electrically-isolated RS-485 port.
Otherwise a ground path from the BACnet network will be made through the
computer that will disrupt BACnet network communications.
Wire a standard three-conductor 3.5 mm () stereo jack as shown below.
LAN Access
Connector

BACnet MS/TP Adaptor

with Isolated RS-485 Port

NET+
NETShield

To Portable Router

- Temporary
Commissioning and
Maintenance
Connection
- No EOL Resistors are
Necessary

EC-Net Pro

Figure 4-13: 3.5mm Stereo Jack Connection for a Portable Adaptor

58

Network Guide

Subnetwork Installation Guidelines

Ensure the BAC/LON jumper in the EC-Smart-Vue is set to the BAC position (this is
the factory-set default jumper position).

BAC
LON

Network Type
Jumper

3.5 mm (1/8) Network

Access Jack

Figure 4-14: BAC/LON Jumper Set to the BAC (BACnet) Position

Network Guide

59

BACnet Troubleshooting

CHAPTER 5
BACNET TROUBLESHOOTING
Table 5-1: Troubleshooting ECB Device Symptoms
Symptom

Possible Cause

Solution

Device does not

communicate on
the BACnet
MS/TP network

The device does not have

power / poor-quality power.

See Power Supply Requirements on page 31.

BACnet data bus polarity

reversed.

Ensure the polarity of the BACnet data bus is

always the same on all devices. See BACnet
MS/TP Data Bus is Polarity Sensitive on page
11.

Cut or broken wire.

Isolate the location of the break and pull a

new cable.

The BACnet data bus has

one or more devices with
the same MAC Address.

See Adopting a Numbering System for MAC

Addresses, Device Instance Numbers, and
Network Numbers on page 27.

The BAUD rate for all

devices are set to AUTO

At least one device must be set to a baud

rate, usually the bus master.

The device is set to a MAC

Address in the range of 128
to 255.

See if the STATUS led on the device is

showing a fault condition. See Table 5-2 for a
list of fault codes.
This range is for slave devices that cannot
initiate communication. All Distech Controls
devices are master devices and must their
MAC Address set accordingly. See Device
Addressing on page 23.

The maximum number of

devices on a data bus
segment has been
exceeded.

Use a repeater to extend the BACnet data

bus. See Data Bus Devices and Baud Rate on
page 13.

Max Master parameter

Configure the Max Master to the highest MAC

Address of any device on the MS/TP data
bus. See Setting the Max Master and Max
Info Frames on page 26.

Absent or incorrect supply

voltage

1. Check if the device is showing the PoorQuality Power status code. See Table 5-4 for
a list of fault codes.
2. Check power supply voltage between
24VAC 15% and COM pins and ensure that
it is within acceptable limits.
3. Check for tripped fuse or circuit breaker.

Overloaded power
transformer

1. Check if the device is showing the PoorQuality Power status code. See Table 5-4 for
a list of fault codes.
2. Verify that the transformer used is powerful
enough to supply all controllers. See
Transformer Selection and Determining the
Maximum Power Run Length on page 33.

60

Network Guide

BACnet Troubleshooting
Symptom

Possible Cause

Solution

Network not wired properly

Double check that the wire connections are

correct.

Absent or incorrect network

termination

Check the network termination(s).

There is another controller

with the same MAC
Address on the BACnet
MS/TP data bus

Each controller on a BACnet MS/TP data bus

must have a unique MAC Address. Use an
EC-Smart-Vue to check the MAC Address of
each controller. See Adopting a Numbering
System for MAC Addresses, Device Instance
Numbers, and Network Numbers on page 27.

There is another controller

with the same Device ID on
the BACnet intranetwork

Each controller on a BACnet intranetwork (the

entire BACnet BAS network) must have a
unique Device ID. Use an EC-Smart-Vue to
check the Device ID of each controller. See
Adopting a Numbering System for MAC
Addresses, Device Instance Numbers, and
Network Numbers on page 27.

The STATUS
led is blinking

The device has autodiagnosed a fault condition

See Table 5-2 for a list of fault codes.

Controller is
powered but
does not turn on

Fuse has blown

Disconnect the power. Check the fuse

integrity. Reconnect the power.

Power supply polarity

Verify that consistent polarity is maintained

between all controllers and the transformer.
Ensure that the COM terminal of each
controller is connected to the same terminal
on the secondary side of the transformer. See
Figure 6-1.

Controller
communicates
well over a short
network, but
does not
communicate on
large network

Network length

Check that the total wire length does not

exceed the specifications of the Network
Guide: Data Bus Physical Specifications and
Cable Requirements on page 15.

Wire type

Check that the wire type agrees with the

specification of the Network Guide: Data Bus
Physical Specifications and Cable
Requirements on page 15.

Network wiring problem

Double check that the wire connections are

correct.

Absent or incorrect network

termination

Check the network termination(s). Incorrect or

broken termination(s) will make the
communication integrity dependent upon a
controllers position on the network.

Number of controllers on
network segment exceeded

The number of controllers on a channel

should never exceed 50. Use a router or a
repeater: See Maximum Number of BACnet
MS/TP Devices on a Data Bus Segment on
page 13.

Max Master parameter

Configure the maximum number of master

device on the MS/TP network in all devices to
the controllers highest MAC address used on
the MS/TP trunk. See BACnet MS/TP Data
Bus Token-Passing Overview on page 24.

Network Guide

61

BACnet Troubleshooting
Symptom

Possible Cause

Solution

Hardware input
is not reading
the correct
value

Input wiring problem

Check that the wiring is correct according to

this manual and according to the peripheral
devices manufacturer.

Open circuit or short circuit

Using a voltmeter, check the voltage on the

input terminal. For example, for a digital input,
a short circuit shows approximately 0V and an
open circuit shows approximately 5V. Correct
wiring if at fault.

Configuration problem

Using the controller configuration wizard,

check the configuration of the input. Refer to
the controllers user guide for more
information.

Over-voltage or overcurrent at an input

An over-voltage or over-current at one input

can affect the reading of other inputs. Respect
the allowed voltage / current range limits of all
inputs. Consult the appropriate datasheet for
controller input range limits.

Fuse has blown (Auto reset

fuse)

Disconnect the power and outputs terminals.

Then wait a few seconds to allow the autoreset fuse to cool down. Check the power
supply and the output wiring. Reconnect the
power.

Output wiring problem

Check that the wiring is correct according to

this manual and according to the peripheral
devices manufacturer.

Configuration problem

Using the controller configuration wizard,

check the configuration of the output. Refer to
the controllers user guide for more
information.

0-10V output, 24VAC

powered actuator is not
moving.

Check the polarity of the 24VAC power supply

connected to the actuator while connected to
the controller. Reverse the 24VAC wire if
necessary.

Device not associated to

controller

Using the device configuration wizard, check

the configuration of the input. Refer to the
devices user guide for more information.

Power discharge

1. Recharge device with light (if solarpowered) or replace battery (if batterypowered).
2. Ensure sufficient light intensity (200lx for 4
hours/day).

Device too far from the

Wireless Receiver

Reposition the device to be within the range of

the Wireless Receiver. For information on
typical transmission ranges, refer to the Opento-Wireless Solution Guide.

Configuration problem

Using the device configuration plug-in or

wizard, check the configuration of the input.
Refer to the Wireless Battery-less Sensors
and Switches Solutions Guide for more
information.

Hardware
output is not
operating
correctly

Wireless
devices not
working
correctly

62

Network Guide

BACnet Troubleshooting
Table 5-2: Led Fault Condition Interpretation for ECB Devices
ECB Device Led
Interpretation

Description

Solution

RX LED not blinking

Data is not being received from the BACnet

MS/TP data bus.

TX LED not blinking

Data is not being transmitted onto the

BACnet MS/TP data bus.

If there is no
communication, see
Table 5-1.

POWER constant on

Power is available at the device. However

this does not mean that the quality of
supplied power is good. Verify the STATUS
led. See also Power Supply Requirements
on page 31.

If not lit, see Power

Supply Requirements
on page 31 for the
power requirements.

STATUS blinking

See below.

Table 5-3: STATUS Led Interpretation for Normal Operation with ECB Devices
Device STATUS Led blink
patterns

Status

Description

Fast blink continuous:

Initialization

The device is starting up.

Solid ON

Firmware upgrade
in progress

Controller operation is temporarily

unavailable. The new firmware is being
loaded into memory. This takes a few
seconds. Do not interrupt power to the
device during this time.

STATUS led is always OFF

No anomaly

Normal operation.

(150ms On, 150ms Off, continuous)

Network Guide

63

BACnet Troubleshooting
Table 5-4: STATUS Led Fault Condition Interpretation for ECB Devices
Device STATUS Led blink
patterns every 2 seconds
(highest priority shown first)

Possible Cause

Corrective action

Long Long Long blink

Offline

The device has not received a BACnet

token, and therefore cannot
communicate on the network.

Poor-quality
power.
The device has
browned-out.

The voltage at the 24VAC and 24VCOM

terminals was not at an acceptable level
during power up.

Invalid MAC
address

The devices MAC address is set to zero

(0) or is set to an address higher than
the Max Master. See BACnet MS/TP
Data Bus Token-Passing Overview on
page 24.

Backup and
Restore.

The controller is being backed-up or

restored.

(800ms On, 300ms Off, 800ms On,

300ms Off, 800ms On)

Short Short Long blink

(150ms On, 300ms Off, 150ms On,
300ms Off, 800 ms On)

Short Long blink

(150ms On, 300ms Off)

Long Short Short Short Short

Long Short:
(800ms On, 300ms Off, 150ms On,
300ms Off, 150ms On, 300ms Off,
150ms On, 300ms Off, 150ms On,
300ms Off, 800ms On, 300ms Off,
150ms On)

64

Network Guide

BACnet Troubleshooting
Table 5-5: Verify that the Following Recommendations have been Carried Out Before
Calling Technical Support
Recommendation

Description

Properly terminate the BACnet MS/TP

data bus

EOL terminations must be enabled / installed at either

end of the data bus only. See Figure 2-1.

Avoid duplicate MAC Addresses

Verify that no device has a duplicate MAC Address by

checking the MAC Address DIP switch settings on all
devices on the data bus, including segments
connected by a repeater.
If necessary, isolate devices from the data bus to
narrow-down the number of devices that may be at
fault.

All devices must be set to the same

baud rate

When all devices are set to AUTO BAUD rate, at least

one device must be set to a baud rate, usually the bus
master.

The bus is polarity sensitive

Ensure that the polarity of all data bus wiring is

consistent throughout the network. See BACnet MS/TP
Data Bus is Polarity Sensitive on page 11.

Do not overload the data bus with

Change of Value (COV) reporting

COV reports create the most traffic on the BACnet

MS/TP data bus. Set the COV report rate to the largest
value that provides acceptable performance. Only map
COV reports for values that are necessary. For
mapped analog points that are continuously changing,
try increasing the COV increment on these points or
set the COV minimum send time flag to true to send
the value at a regular frequency.

Do not leave address holes in the

devices MAC Address range

Assign MAC Address to device starting at 3, up to 127.

Do not skip addresses. Set the maximum MAC
Address in the Bus Master (Building Controller) to the
final MAC Address number actually installed.
NOTE: The physical sequence of the MAC Address of
the devices on the data bus is unimportant: For
example, the MAC Address of devices on the data bus
can be 5, 7, 3, 4, 6, and 8.

Only daisy-chained devices are

acceptable

Eliminate T-taps and star configurations. Use a router

to connect a data bus spur.

Connect no more than five devices to a

power supply transformer

BACnet MS/TP devices require good power quality.

See Power Supply Requirements on page 31.

Network Guide

65

LonWorks Troubleshooting

CHAPTER 6
LONWORKS TROUBLESHOOTING
Table 6-1: Troubleshooting ECL Device Symptoms
Symptom

Possible Cause

Solution

Device does not

communicate on
the LONWORKS
network

The device does not have

power / poor-quality power.

See Power Supply Requirements on page 44.

Cut or broken wire.

Isolate the location of the break and pull a

new cable.

The maximum number of

devices on a segment has
been exceeded.

Use a repeater to extend the LONWORKS data

bus. See Network Cables on page 40 and
also Extending the Network on page 42.

Absent or incorrect supply

voltage

1. Check if the device is showing the Poor

Power Quality status code. See Table 6-4 for
a list of fault codes.
2. Check power supply voltage between
24VAC 15% and COM pins and ensure that
it is within acceptable limits.
3. Check for tripped fuse or circuit breaker.

Overloaded power
transformer

1. Check if the device is showing the Poor

Power Quality status code. See Table 6-4 for
a list of fault codes.
2. Verify that the transformer used is powerful
enough to supply all controllers. See
Transformer Selection and Determining the
Maximum Power Run Length on page 44.

Network not wired properly

Double check that the wire connections are

correct.

Absent or incorrect network

termination

Check the network termination(s). See TP/FT10 Free Topology Network Termination on
page 39.

The STATUS
led is blinking

The device has autodiagnosed a fault condition

See Table 6-2 for a list of fault codes.

Controller is
powered but
does not turn on

Fuse has blown

Disconnect the power. Check the fuse

integrity. Reconnect the power.

Power supply polarity

Verify that consistent polarity is maintained

between all controllers and the transformer.
Ensure that the COM terminal of each
controller is connected to the same terminal
on the secondary side of the transformer. See
Power Supply Requirements on page 44.

Controller
communicates
well over a short
network, but
does not
communicate on
large network

Network length

Check that the total wire length does not

exceed the specifications of the Network
Guide. See Network Cables on page 40.

Wire type

Check that the wire type - see Network Cables

on page 40.

Network wiring problem

Double check that the wire connections are

correct.

66

Network Guide

LonWorks Troubleshooting
Symptom

Hardware input
is not reading
the correct
value

Hardware
output is not
operating
correctly

Network Guide

Possible Cause

Solution

Absent or incorrect network

termination

Check the network termination(s). Incorrect or

broken termination(s) will make the
communication integrity dependent upon a
controllers position on the network. See
TP/FT-10 Network Topologies on page 38.

Extra capacitance

Make sure that no extra capacitance is being

connected to the network other than the
standard FTT circuit, and a maximum of a 3
meter stub (in bus topology).

Number of controllers on
network segment exceeded

Too many controllers on a channel. See

Network Cables on page 40. Use a repeater
in accordance to the Network Guide. See
Extending the Network on page 42.

Network traffic

Query node statistic to check errors.

Use a LON protocol analyzer to check
network traffic.

Input wiring problem

Check that the wiring is correct according to

this manual and according to the peripheral
devices manufacturer.

Open circuit or short circuit

Using a voltmeter, check the voltage on the

input terminal. For example, for a digital input,
a short circuit shows approximately 0V and an
open circuit shows approximately 5V. Correct
wiring if at fault.

Configuration problem

Using the controller configuration wizard,

check the configuration of the input. Refer to
the controllers user guide for more
information.

Over-voltage or overcurrent at an input

An over-voltage or over-current at one input

can affect the reading of other inputs. Respect
the allowed voltage / current range limits of all
inputs. Consult the appropriate datasheet for
controller input range limits.

Fuse has blown (Auto reset

fuse)

Disconnect the power and outputs terminals.

Then wait a few seconds to allow the autoreset fuse to cool down. Check the power
supply and the output wiring. Reconnect the
power.

Output wiring problem

Check that the wiring is correct according to

this manual and according to the peripheral
devices manufacturer.

Configuration problem

Using the controller configuration wizard,

check the configuration of the output. Refer to
the controllers user guide for more
information.

0-10V output, 24VAC

powered actuator is not
moving.

Check the polarity of the 24VAC power supply

connected to the actuator while connected to
the controller. Reverse the 24VAC wire if
necessary.

67

LonWorks Troubleshooting
Symptom

Possible Cause

Solution

Wireless
devices not
working
correctly

Device not associated to

controller

Using the device configuration wizard, check

the configuration of the input. Refer to the
devices user guide for more information.

Power discharge

1. Recharge device with light (if solarpowered) or replace battery (if batterypowered),
2. Ensure sufficient light intensity (200lx for 4
hours/day).

Device too far from the

Wireless Receiver

Reposition the device to be within the range of

the Wireless Receiver. For information on
typical transmission ranges, refer to the Opento-Wireless Solution Guide.

Configuration problem

Using the device configuration plug-in or

wizard, check the configuration of the input.
Refer to the Wireless Battery-less Sensors
and Switches Solutions Guide for more
information.

Table 6-2: Led Fault Condition Interpretation for ECL Devices

ECL Device Led
Interpretation

Description

Solution

RX LED not blinking

Data is not being received from the

LONWORKS MS/TP data bus.

TX LED not blinking

Data is not being transmitted onto the

LONWORKS MS/TP data bus.

If there is no
communication, see
Table 5-1.

POWER constant on

Power is available at the device. However

this does not mean that the quality of
supplied power is good. Verify the STATUS
led. See also Power Supply Requirements
on page 44.

If not lit, see Power

Supply Requirements
on page 44 for the
power requirements.

STATUS blinking

See below.

Table 6-3: STATUS Led Interpretation for Normal Operation with ECL Devices
Device STATUS Led blink
patterns

Status

Description

Fast blink continuous:

Initialization

- Initialization: The device is starting up.

- Firmware upgrade in progress. Controller
operation is temporarily unavailable. The
new firmware is being loaded into memory.
This takes a few seconds. Do not interrupt
power to the device during this time.

No anomaly

Normal operation.

(150ms On, 150ms Off, continuous)

STATUS led is always OFF

68

Network Guide

LonWorks Troubleshooting
Table 6-4: STATUS Led Fault Condition Interpretation for ECL Devices
Device STATUS Led blink
patterns every 2 seconds
(highest priority shown first)

Possible Cause

Corrective action

Long blink continuous:

The controller is
unconfigured

Commission the controller

The controller is
offline

Set the controller Online

The controller is in
bypass mode

Set the controller Online

(150ms On, 300ms Off, 150ms On, 300ms Off, 800 ms On)

Poor-quality
power; The device
has browned-out

The voltage at the 24VAC and 24VCOM

terminals has gone below the devices
acceptable limit during power up.

Fast blink 12x:

Wink

The wink function is used to identify a

device.

(1s On, 1s Off, continuous)

Long Long Long blink

(800ms On, 300ms Off, 800ms On, 300ms Off,
800ms On)

Long Short Short Short blink

(800ms On, 300ms Off, 150ms On, 300ms Off, 150ms On,
300ms Off, 150ms On)

Short Short Long blink

(80ms On, 80ms Off, 12x)

Table 6-5: Verify that the Following Recommendations have been Carried Out Before
Calling Technical Support
Recommendation

Description

Properly terminate the LONWORKS data

bus

EOL terminations must be enabled / installed at either

end of the data bus only. See TP/FT-10 Free Topology
Network Termination on page 39.

Connect no more than five devices to a

power supply transformer

LONWORKS devices require good power quality. See

TP/FT-10 Free Topology Network Termination on page
39.

Network Guide

69

ECx-400 Series I/O Extension Module Specific Troubleshooting

CHAPTER 7
ECX-400 SERIES I/O EXTENSION MODULE
SPECIFIC TROUBLESHOOTING
For general troubleshooting of an ECx-400 Series I/O Extension Module, first follow the
troubleshooting for a controller see BACnet Troubleshooting on page 60 and LonWorks
Troubleshooting on page 66. Then follow the troubleshooting tips shown below.
Table 7-1: Troubleshooting ECx-400 Series I/O Extension Module Device Specific
Symptoms
Symptom

Possible Cause

Solution

Device does not

communicate on
the subnetwork

Cut or broken wire.

Isolate the location of the break and pull a

new cable.

Network not wired properly

Double check that the wire connections are

correct.

Absent or incorrect network

termination

Check the network termination(s). See

ECx-4XX Subnetwork Bus Topology and Endof-Line Terminations on page 48.

There is another controller

with the same Subnet ID on
the subnetwork

Each I/O Extension Module on the

subnetwork must have a unique Subnet ID.
Look at the Subnet ID DIP switch on the
faceplate of each I/O Extension Module. See
ECx-4XX I/O Extension Module Addressing
on page 50.

Network length

Check that the total wire length does not

exceed specification shown in About the
Subnetwork Bus on page 47.

Wire type

Check that the wire type agrees with the

specification shown in ECx-4XX Subnetwork
Bus Physical Specifications and Cable
Requirements on page 48.

70

Network Guide

EC-Smart-Vue Troubleshooting

CHAPTER 8
EC-SMART-VUE TROUBLESHOOTING
Table 8-1: EC-Smart-Vue Normal Operation
Symptom

Status

Description

When the
EC-Smart-Vue is
connected to a
Controller, the LCD
display on the
EC-Smart-Vue is
blank with the
backlight ON for
about 30 to 45
seconds

Firmware upgrade in
progress

Wait for the upgrade to complete. Do not

disconnect the EC-Smart-Vue from the controller
as the upgrade will only restart once it is
reconnected.

Table 8-2: Troubleshooting EC-Smart-Vue Symptoms

Symptom

Possible Cause

Solution

EC-Smart-Vue
screen is blank &
back light is off

Is the EC-Smart-Vue
connected to the
controller?

Verify that the EC-Smart-Vue is connected to the

controller and that the patch cables are pluggedin to the connectors. Refer to EC-Smart-Vue
Subnetwork Bus on page 52 for more information.

Is power being
supplied to the
controller?

There may be no power being supplied from the

controller. Check if the controller has power or if
the controllers internal fuses have blown or
tripped.

Is the cable
connected to the
controller and
EC-Smart-Vue?

Verify wiring.

Is the address
correctly set to a
unique address?

Each EC-Smart-Vue must be set to a unique

address for each controller. See Commissioning
with an EC-Smart-Vue on page 55.

Was the patch cable

was made onsite?

Verify that the RJ-45 crimp connectors were

installed on the cable correctly. See
EC-Smart-Vue Subnetwork Bus Cable
Requirements on page 52.

Is the device too far

from controller?

Verify the distance between the device and the

controller. See Subnetwork Bus Total Length on
page 47.

Is there a
configuration
problem?

With EC-gfxProgram, check the configuration of

the sensor, for example, is it enabled? Refer to
the EC-gfxProgram User Guide for more
information.

Device is not
communicating
with controller

Network Guide

71

EC-Smart-Vue Troubleshooting
Table 8-3: Error code Interpretation for EC-Smart-Vue Symptoms
Symptom

Possible Cause

Corrective action

Clock icon flashing for 15

seconds

Cannot
communicate with
controller.

Verify power at controller

Verify wiring to controller

Error code 2 with Bell icon

Invalid
configuration.

In EC-gfxProgram, resynchronize the

code with the controller.
Contact Distech Controls Customer
Support.

Error code 3 with Bell icon

EC-Smart-Vue is
not configured in
the controller

With EC-gfxProgram, check the

configuration of the sensor, for example,
is it enabled? Refer to the
EC-gfxProgram User Guide for more
information.

After 15 seconds: Error code 1

with Bell icon

72

Network Guide

Typical BACnet EIA-485 Data Bus Transmission Example

Appendix A
TYPICAL BACNET EIA-485 DATA BUS
TRANSMISSION EXAMPLE
The graph below shows electrical signals for the transmission of one byte of data
(hexadecimal D3, least significant bit first). Note that when idle, the BACnet MS/TP bus is
biased such that the Net + connection is positive with respect to the Net connection.

Net -

Idle

Space

Mark

Mark

Mark

Space

Space

Net +

Mark
Mark
Idle

Stop

Start

Figure 8-1: Example of a Typical EIA-485 Data Bus Transmission

The permitted voltage levels of an EIA-485 transmitter and receiver are shown below.
EIA-485 Receiver Differential Input

EIA-485 Transmitter Signal Voltage

+12 Volts

+12 Volts
Permissible
Range
+2 Volts

+0.2 Volts
Voltage VNet-,Net+
-0.2 Volts

Voltage VNet-,Net+
-2 Volts

Transition
Region

Maximum
Operating
Range

Permissible
Range
-7 Volts

-7 Volts

Figure 8-2: Typical EIA-485 Data Bus Operating Signal Levels

Table 8-1: EIA-485 Signal Specifications
Parameter

Conditions

Min

Max

Units

1.5

-1.5

-5

Differential Driver Output Voltage Open Circuit

Driver Output Voltage - Loaded

RLOAD = 27

Driver Common Mode (CM) Voltage

RLOAD = 54

-1

Receiver Sensitivity

-7 Vcm +12

0.2

Receiver Common-Mode Voltage

Range

-7

Receiver Input Resistance

96K

V
+12

The receiver is also protected against the temporary application of 24VAC and against
transients. However, such events will interrupt data reception.

Network Guide

73

Typical BACnet EIA-485 Data Bus Transmission Example

Common Mode Noise Rejection
Noise induced onto the conductors of the data bus cable will be common to both Net + and
Net - data bus wires that is to say, the noise will be of the same amplitude and polarity as
the conductors in the cable are so close together. For this reason the EIA-485 data bus is
differential bus. The receiver nulls out common mode induced noise picked up on the data
bus wire by subtracting the negative input from the positive input. This greatly reduces the
impact that induced noise has on the bus.
Induced common-mode noise transient
Noise transient
attenuation

Typical EIA-485 line

receiver with inverting
input shown

Figure 8-3: Common-Mode Noise is Significantly Attenuated by a Differential EIA-485

Line Receiver

74

Network Guide

How to Set a DIP Switch

Appendix B
HOW TO SET A DIP SWITCH
DIP switches are used to set the address of a device. In the following table, A & B represent
the binary ON / OFF setting for the DIP switch required for a given decimal value shown in
the table.
B

000

001

010

011

100

101

110

111

0000

0001

10

11

12

13

14

15

0010

16

17

18

19

20

21

22

23

0011

24

25

26

27

28

29

30

31

0100

32

33

34

35

36

37

38

39

0101

40

41

42

43

44

45

46

47

0110

48

49

50

51

52

53

54

55

0111

56

57

58

59

60

61

62

63

1000

64

65

66

67

68

69

70

71

1001

72

73

74

75

76

77

78

79

1010

80

81

82

83

84

85

86

87

1011

88

89

90

91

92

93

94

95

1100

96

97

98

99

100

101

102

103

1101

104

105

106

107

108

109

110

111

1110

112

113

114

115

116

117

118

119

1111

120

121

122

123

124

125

126

127

ON

For example
82 = A: 1010 & B: 010

Figure 8-1: Example of How to Set a DIP Switch to 82

Network Guide

75

Metric Conversions for Wire Gauge

Appendix C
METRIC CONVERSIONS FOR WIRE GAUGE
The following table provides information about metric wire equivalents for wire gauge.
AWG

76

Approximate stranded
metric equivalents

Diameter ()

Area

(inch)

(mm)

(kcmil)

(mm)

10

0.1019

2.588

10.4

5.26

12

0.0808

2.053

6.53

3.31

14

0.0641

1.628

4.11

2.08

16

0.0508

1.291

2.58

1.31

18

0.0403

1.024

1.62

0.823

24/0.2

20

0.0320

0.812

1.02

0.518

16/0.2

22

0.0253

0.644

0.642

0.326

7/0.25

24

0.0201

0.511

0.404

0.205

1/0.5, 7/0.2, 30/0.1

Network Guide

Documentation Improvement Form

Appendix D
DOCUMENTATION IMPROVEMENT FORM
Is any part of this document not clear enough? Are there any comments about the content of
this document? Do not hesitate to use this form to send us comments and
recommendations, as there is always a drive to improve documentation to further satisfy
clients.

Please mail or fax this form to:

Distech Controls Inc.
4005-B Boul. Matte
Brossard, QC
J4Y 2P4
Fax: 1-450-444-0770
Email: [email protected]

Distech Controls Documentation Improvement Form

Document Title and Version: Network Guide Network Guide

Page #

Network Guide

Suggestions or Comments

77

Distech Controls Inc

4005-B Boul. Matte
Brossard, QC J4Y 2P4
Tel.: 1-800-404-0043
Tel.: 1-450-444-9898
www.distech-controls.com

*05DI-UGBACNG-12*
05DI-UGBACNG-12