27360

TAC I/A Series MicroNet BACnet Wiring and Networking Practices Guide
TAC I/A Series MicroNet BACnet Wiring and Networking Practices Guide
Printed in U.S.A.
7-07
F-27360-3
Copyright Notice
The confidential information contained in this document is provided solely for use by TAC employees, licensees, and system owners, and is not to be released to, or reproduced for, anyone else. Neither is it to be used for reproduction of this control system or any of its components. All specifications are nominal and may change as design improvements occur. TAC shall not be liable for damages resulting from misapplication or misuse of its products. TAC 1354 Clifford Avenue P.O. Box 2940 Loves Park, Illinois 61132-2940 United States of America www.tac.com
Copyright 2007, TAC.

All brand names, trademarks, and registered trademarks are the property of their respective owners. Information contained within this document is subject to change without notice. Distributed, manufactured, and sold by TAC. I/A Series trademarks are owned by Invensys Systems, Inc. and are used on this product under license from Invensys. Invensys does not manufacture this product or provide any product warranty or support. For service, support, and warranty information, contact TAC at 1-888-444-1311.
t.a.c, TAC, and MicroNet are trademarks of TAC. BACnet is a trademark of the American Society of Heating, Ventilating, Refrigeration, and Air-conditioning Engineers (ASHRAE). Adobe and Acrobat are trademarks of Adobe Systems, Inc. Windows is a trademark of Microsoft Corp. All other trademarks are the property of their respective owners.
Preface
Purpose of this Manual
This MicroNet BACnet Wiring and Networking Practices Guide is a reference for creating a network of MicroNet BACnet controllers. This guide provides the following discussions and instructions for the MicroNet BACnet series:
MicroNet BACnet Controllers and their features Controller wiring terminals and wiring recommendations Controller input and output specifications MicroNet Digital Wall Sensors and their features Diagnostic functions of the MicroNet Digital Wall Sensors BACnet overview MicroNet BACnet system architecture overview Network configuration, including physical and logical restrictions How to network into an IP over an Ethernet backbone
Other literature related to the implementation of a MicroNet BACnet system are referenced throughout this guide and are listed in "Applicable Documentation, on page iv. It is assumed that readers of this manual already understand basic HVAC concepts. An understanding of BACnet networking and communications, as well as a general understanding of Ethernet networks, is also helpful. This manual is written for:
Application engineers. Users who change hardware or control logic. TAC technicians and field engineers.
F-27360-3
MicroNet BACnet Wiring and Networking Practices Guide
iii
Applicable Documentation
F-Number Description WorkPlace Tech Tool 4.0 Engineering Guide. Audience Application Engineers Service Personnel Application Engineers Installers Start-up Technicians Service Personnel Purpose Provides a programming reference for MicroNet controllers. Gives detailed descriptions for each of the Control Objects used with MicroNet controllers. Provides step-by-step instructions for using the WorkPlace Tech Tool, version 4.0. Provides supplemental information for programming MicroNet BACnet controllers. Gives detailed descriptions for each of the unique BACnet Control Objects used with these controllers. Provides step-by-step instructions for using the WorkPlace Commissioning Tool and Flow Balance Tool. Provides best practices information related to the implementation of I/A Series MicroNet BACnet devices in BACnet applications, acquired from factory testing and actual jobsite installations. Provides BACnet compliance information on MicroNet BACnet MNB-300, MNB-V1, and MNB-V2 controllers. Provides step-by-step mounting and installation instructions for the MicroNet MNB-70 Controller. Provides step-by-step mounting and installation instructions for the MicroNet MNB-300 Controller. Provides step-by-step mounting and installation instructions for the MicroNet MNB-V1 and MNB-V2 Controllers. Provides step-by-step mounting and installation instructions for the MicroNet MNB-1000 Controller. Provides step-by-step installation and checkout procedures for TAC I/A Series MicroNet MN-SX Series Sensors. Also contains instructions for sensor operation.
F-27254
F-27255
I/A Series WorkPlace Tech Tool 4.0 Users Guide
F-27356
WorkPlace Tech Tool 5.x Engineering Guide Supplement
Application engineers Service personnel
F-27358
I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool Users Guide
Application Engineers Installers Start-up Technicians Service Personnel Application Engineers Installers Start-up Technicians Service Personnel
F-27457
I/A Series BACnet Best Practices
F-27365
BACnet PIC Statement
Application engineers Application Engineers Installers Service Personnel Start-up Technicians Application Engineers Installers Service Personnel Start-up Technicians Application Engineers Installers Service Personnel Start-up Technicians Application Engineers Installers Service Personnel Start-up Technicians Application Engineers Installers Service Personnel Start-up Technicians
F-27456
MicroNet BACnet MNB-70 Zone Controller Installation Instructions MicroNet BACnet MNB-300 Unitary Controller Installation Instructions MicroNet BACnet MNB-V1, MNB-V2 VAV Controllers Installation Instructions MicroNet BACnet MNB-1000 Plant Controller Installation Instructions
F-27345
F-27346
F-27347
F-26277
I/A Series MicroNet MN-SX Series Sensors General Instructions
iv MicroNet BACnet Wiring and Networking Practices Guide
F-27360-3
Preface
Related Documentation
Applies To
For more information, consult the following documentation:
Description Niagara Release 2.3.4 Installation and Upgrade Instructions
Source
UNC Controllers
Niagara System and Power Monitoring, Engineering TAC I/A Series Enterprise Server Notes CD Niagara Networking & Connectivity Guide Tech Zone at The Source Niagara Standard Programming Reference Manual, Release 2.3.4 BACnet Integration Reference
(http://source.tac.com/)
BACnet Networks
ANSI/ASHRAE Standard 135-2001 BACnetA Data Communication Protocol for Building Automation and Control Networks.
ANSI/ASHRAE
Conventions Used in this Manual
The following conventions apply to this printed manual:
Menu commands appear in bold.

Example On the Special menu, point to Security, then click Log On.
Italics is used for emphasis in a statement, such as:

If maximum closed switch voltage is not more than 1.0 V and minimum open switch voltage is at least 4.5 V, then solid state switches may be used for a UI or a DI. It is also used when referring to a document, such as: Refer to the WorkPlace Tech Tool 5.x Engineering Guide Supplement, F-27356.
Acrobat (PDF) Conventions
If you are reading this manual online in Adobe Acrobat (.PDF file format), numerous hypertext links exist, both in normal black text and in blue text.
Hypertext links in this document include all entries in the Table of

Contents, as well as cross-references within the body text. For ease of recognition, cross-reference links within the body text appear in blue type, for example Manual Summary. A link is indicated whenever the mouse pointer changes to a hand with a pointing finger.
When viewing this guide with Adobe Acrobat, you can display various
bookmark links on the left side of your screen by choosing Bookmarks and Page from the View menu. As with the links described above, these bookmark links will also cause the mouse pointer to change to a hand with a pointing finger.
F-27360-3
Abbreviations Used in this Manual
ASHRAE
ANSI AWG BACnet BAS B-ASD C DI DIP DO EEPROM
EMI EOL F FRAM ft. GND HVAC Hz I/A I.D. I/O IP Kb KB kHz LCD LED m mA MAC MB mm MS/TP n/a O.D.
American Society of Heating, Ventilating, Refrigeration, and Air-conditioning Engineers American National Standards Institute American Wire Gage Building Automation and Controls Network Building Automation System BACnet Application Specific Device Degrees Celsius Digital Input Dual In-line Package (switch) Digital Output Electrically Erasable Programmable Read-Only Memory Electromagnetic Interference End-Of-Line Degrees Fahrenheit Ferroelectric RAM foot Ground (electrical) Heating, Ventilating, and Air Conditioning hertz Intelligent Automation Inside Diameter Input / Output Internet Protocol Kilobit Kilobyte kiloHertz Liquid Crystal Display Light Emitting Diode meter milliAmperes Media Access Control Megabyte millimeter Master Slave Token Passing Not Applicable Outside Diameter
PC PDF pF RAM RFI RH SDRAM SPST SRAM TO UI UO V VA Vac, Vdc VAV W.C. WP Tech
Personal Computer Portable Document Format picofarad Random Access Memory Radio Frequency Interference Relative Humidity Synchronous Dynamic RAM Single Pole Single Throw Static RAM Triac Output Universal Input Universal Output Volts Volt-Amp Volts Alternating Current, Volts Direct Current) Variable Air Volume Water Column WorkPlace Tech Tool
vi MicroNet BACnet Wiring and Networking Practices Guide
F-27360-3
Preface
Manual Summary
The MicroNet BACnet Wiring and Networking Practices Guide contains three chapters. Chapter 1, I/A Series BACnet Hardware, provides a brief overview of the various I/A Series MicroNet BACnet controllers and sensors. Chapter 2, Networking Practices, provides an overview of the BACnet protocol and, more specifically, its implementation in the MicroNet BACnet system. This chapter then explains how MicroNet BACnet controllers and sensors are configured for an MS/TP network. Chapter 3, Checkout and Troubleshooting, provides steps for determining the proper operation of the MicroNet BACnet system and suggests corrective actions for any discovered faults.
F-27360-3
vii
viii MicroNet BACnet Wiring and Networking Practices Guide
F-27360-3
Table of Contents Preface

Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Applicable Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Acrobat (PDF) Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Abbreviations Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . vi Manual Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Chapter 1
I/A Series BACnet Hardware

MicroNet BACnet Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Common Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 BACnet Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 MNB-300 Unitary Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 MNB-V1, MNB-V2 VAV Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 5 MNB-70 Zone Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 MNB-1000 Plant Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Input and Output Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Universal Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Universal Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Digital Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Digital Outputs, Triac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 20 Vdc Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Inputs from MN-Sx MicroNet Sensor . . . . . . . . . . . . . . . . . . . . . . 16 Velocity Pressure Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 MicroNet Digital Wall Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Common Sensor Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Keypad Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 LCD Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Communications Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Sensor Link (S-Link) Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 MicroNet MS/TP Network Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Wiring Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Approved Cable Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 I/O Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Power Supply Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 2
Networking Practices
Introduction to BACnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Connected Devices . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 32 32 34 34 34 34
F-27360-3
ix
Table of Contents
Addressing Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Limits to Number of Polled Points . . . . . . . . . . . . . . . . . . . . . . . . 35 Limits to Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Connection to an MS/TP Network . . . . . . . . . . . . . . . . . . . . . . . . . . 35 MS/TP Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Master and Slave Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Physical Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Required Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 MAC Address for BACnet Tools . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Other Network Setup Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Port Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Single Path to Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Routers and Network Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Network Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Physical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Set the DIP Switches on the Controllers . . . . . . . . . . . . . . . . . . . . . . 42 Power on the Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Commission UNCs and ENCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Commission the Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 3
Checkout and Troubleshooting

Mechanical Hardware Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Communications Hardware Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
x MicroNet BACnet Wiring and Networking Practices Guide
F-27360-3
Chapter 1 I/A Series BACnet Hardware

This chapter provides a brief overview of the various I/A Series MicroNet BACnet controllers and sensors, including:
Common Controller Features BACnet Compliance MNB-300 Unitary Controller MNB-V1, MNB-V2 VAV Controllers MNB-70 Zone Controllers MNB-1000 Plant Controller MicroNet Digital Wall Sensors (MN-Sx Series)
MicroNet BACnet hardware products include controllers and compatible sensors.
MicroNet BACnet controllers provide direct-digital control for packaged

rooftop, heat pump, fan coil, unit ventilator, and VAV, as well as complex mechanical equipment such as central station air handlers, VAV air handlers, and cooling towers. Five basic controller platforms are available, each with a number of I/O points and support for a digital room temperature or humidity sensor (MicroNet sensor).
MicroNet sensors are digital wall temperature and humidity sensors

designed specifically for use with MicroNet controllers. 12 different models offer varying levels of sensor push-buttons and LCD screens.
F-27360-3
Chapter 1
MicroNet BACnet Controllers

There are five hardware platforms for MicroNet BACnet controllers: the MNB-70, the MNB-300, the MNB-V1, the MNB-V2, and the MNB-1000. Each is described in the following sections.
Common Controller Features
While all controller platforms differ by their physical characteristics and numbers and types of I/O points, all controller platforms provide the following common features:
24 Vac powered. Capability to function in standalone mode or as part of an I/A Series

building automation network.
Support for a digital MicroNet sensor via a Sensor Link (S-Link) bus. Sequence of operation and BACnet image are fully programmable using
WorkPlace Tech Tool 5.0 or greater.
Extensive BACnet object and services support. DIP switch for setting the physical (MAC) address. LED indication of MS/TP communication link and activity, and controller
status.
Isolated EIA-485 (formerly RS-485) transceiver for MS/TP

communications.
Firmware upgradeable over the network or directly to the controller.
BACnet Compliance
Each MicroNet BACnet controller conforms to the requirements of a BACnet Application Specific Device (B-ASD). For a list of objects supported by these controllers, and the services provided, refer to the BACnet PIC Statements, available on the Tech Zone, at The Source (http://source.tac.com/).
2 MicroNet BACnet Wiring and Networking Practices Guide
F-27360-3
MNB-300 Unitary Controller
The I/A Series MicroNet BACnet Unitary Controller, MNB-300, is an interoperable controller with native BACnet MS/TP communications support. The controller features Sensor Link (S-Link) support, LED status and output indication, screw terminal blocks, as well as a panel-mount sub-base with removable electronics module. The MNB-300 also includes one end-of-line (EOL) termination and two bias resistors, both of which are jumper-selectable. When programmed using WorkPlace Tech Tool, the MNB-300 provides a wide range of control strategies for packaged rooftop, heat pump, fan coil, unit ventilator, and similar applications. Unique Features In addition to common MicroNet BACnet controller features (Common Controller Features section in this chapter), the MNB-300 offers the following:
Removable electronics module that mates with panel-mounted subbase. Optional NEMA 1 enclosure. IAM button for BACnet I am message broadcast. Integral MS/TP jack for direct connection of a PC with the WorkPlace Tech Tool. commissioning.
Removable terminals for power and communications, to facilitate LED indication of UO and TO state.
Memory Available
Table1.1 MNB-300 Available Memory. Model Number MNB-300 Flash 256 KB SRAM 8 KB SDRAM n/a EEPROM 4 KB FRAM 8 KB
Physical I/O Points

Table1.2 MNB-300 Inputs and Outputs. Model Number MNB-300 UI 6 Inputs and Outputs UO DO (Triac) 3 6
Refer to "Input and Output Specifications" on page 12 for a detailed discussion of each input or output type. Time Clock The MNB-300 controller uses a software clock. This software clock defaults to a predefined Date/Time following a reset.
F-27360-3
Chapter 1
Wiring Terminals
Refer to Figure-1.1 for the power and network communications wiring connections available on the MNB-300 controller.
Universal Inputs 0 to 5 Vdc 3 0 to 20 mA 10K Thermistor 4 1K Balco 1K Platinum 1K Resistive 10K Resistive Digital (dry switched contact) 5 6 Standard Pulse 8 Fast Pulse (UI1) 9
UI1 COM UI2
MNB-300 Unitary Controller
1
24H 24G COM GND
AC Power 20.4 to 30 Vac 50/60 Hz Class 2 (EN 60742) 16 VA per controller
TO1 (DO1) UI3 COM
1
UI4
Internal Triac Switches (Isolated)
C1 TO2 (DO2) C2
UI5 TO3 (DO3) COM C3 UI6 TO4 (DO4)
Digital Outputs (Triac) 12 VA at 24 Vac, 50/60 Hz. Each Triac output individually isolated from AC input and other I/O. Class 2
Universal Outputs 0 to 20 mA into an 80 to 550 load
UO1 C4 COM UO2
Connectors (2) UO LEDs (3) 7

XMT
Disable
TO5 (DO5) C5 STATUS RCV

LSB
S-LK Supports one I/A Series MN-Sxxx Sensor 10 MS/TP Jack BACnet Network MS/TP Communications 1
UO3 COM IAM S-LK MS+ MSSLD

Enable
TO6 (DO6) C6
EOL
Physical Address
EN DIS
1 TO (DO) LEDs (6)
1 2
MSB
MS BIAS
All wiring terminals accept a single AWG #14 (2.08 mm2) or up to two AWG #18 (0.823 mm2) or smaller wires. Power and MS/TP connectors have removable screw terminals. Input signals of 1 to 11 Vdc must be converted to 0.45 to 5 Vdc with a voltage divider, part number AD-8961-220. In applications requiring universal inputs with ranges of 0 to 20 mA, a 250 shunt resistor kit, part number AD-8969-202, is needed.
An 11 k shunt resistor kit, part number AD-8969-206, is required for a 10 k Thermistor Sensor (non-850 series) universal inputs. To detect a closed switch, resistance must be less than 300 . To detect an open switch, resistance must be greater than 2.5 k. External load is not required to illuminate UO LEDs. Minimum rate of 1 pulse per 4 minutes. Maximum rate of 1 pulse per second.
Minimum rate of 1 pulse per 4 minutes. Maximum rate of 10 pulses per second.
2 3
5 6 7 8
10 When making an MS/TP cable, use a 1.3 x 3.5 mm Vdc power plug with strain relief (Vimex part number SCP-2009A-T, TAC part number E24-1442, or equivalent). The cable should be no longer than 6 ft. Connect MS+ to the center contact and MS to the outside contact: _ Note: The MS/TP cable described above is available from TAC as MNB-CT-CBL. Contact TAC for more information.
Figure1.1 MNB-300 Terminal Connections.
F-27360-3
MNB-V1, MNB-V2 VAV Controllers
The I/A Series MicroNet BACnet VAV (Variable Air Volume) Controllers, MNB-V1 and MNB-V2, are interoperable controllers with native BACnet MS/TP communications support. Both models incorporate: an integral actuator with manual override; an integral, patented, pressure transducer; three universal inputs; Sensor Link (S-Link) support; LED status indication; and over-the-shaft damper mounting. The MNB-V1 controller is designed specifically for cooling applications, while the MNB-V2 controller adds digital and universal outputs that make it suitable for additional VAV applications. When programmed using WorkPlace Tech Tool, these controllers provide a wide range of control strategies for pressure-dependent and pressure-independent terminal boxes, with or without reheat capabilities.
SW 24 SW H1 24 SW H2 24 24H H3 24G (C GN OM) D ST MSATUS MSTP R TP CV XM T
UO 1 CO M UI 1 CO M UI 2 S-L UI K/C 3 MS OM T MS P + TP SH LD
Unique Features In addition to common MicroNet BACnet controller features (Common Controller Features section in this chapter), the MNB-V1 and MNB-V2 offer the following:
Air balancing performed using WorkPlace Flow Balance Tool. Integrated packaging with actuator, pressure transducer, and controller. Integral actuator features manual override and travel limit stops for easy
set up and adjustment.
Enclosure approved for use in air plenums. Damper position feedback to the BACnet Building Automation System
(BAS) via integral hall effect sensor.
Stable flow control down to 0.004 in. W.C. (0.996 Pa) differential
pressure. Memory Available
Table1.3 MNB-Vx Available Memory. Model Number MNB-V1 MNB-V2 Flash 256 KB SRAM 8 KB SDRAM n/a EEPROM 4 KB FRAM n/a
Physical I/O Points

Table1.4 MNB-Vx Inputs and Outputs. Model Number MNB-V1 MNB-V2 UI 3 3 Inputs and Outputs UO DO (Triac) 0 0 1 3
Refer to the "Input and Output Specifications" on page 12 for a detailed discussion of each input or output type. Time Clock The MNB-V1 and MNB-V2 controllers use a software clock. This software clock defaults to a predefined Date/Time following a reset.
F-27360-3
Chapter 1
Wiring Terminals
Refer to Figure-1.2 for the power and network communications wiring connections available on the MNB-V1 and MNB-V2 controllers.
MNB-V1 / -V2 Controllers
Internal Triac Switches (3) Digital Outputs Total 24 VA (DO1+DO2), 12 VA (DO3) at 24 Vac, 50/60 Hz, Class 2. Pilot Duty SW24H1* (DO1)
1 UO1* COM*
Universal Output 0 to 20mA into an 80 to 550 load Universal Inputs 0 to 5 Vdc 2 3 0 to 20 mA 10K Thermistor 4 1K Balco 1K Platinum 1K Resistive 10K Resistive Digital (dry switched contact) 5 6 Standard Pulse 7
UI1 COM
SW24H2* (DO2) UI2 SW24H3* (DO3) UI3 24H S-LK/COM 24G (COM) AC Power 20.4 to 30 Vac, 50/60 Hz Class 2 (EN 60742) 15 VA per controller plus DO load S-LK GND
LSB
STATUS MSTP RCV MSTP XMT

MSB
MSTP + Physical
MS/TP Jack
S-LK Supports one I/A Series MN-Sxxx Sensor
MSTP SHLD BACnet Network Communications
8 Address
Note: Asterisks (*) indicate terminals that apply to the MNB-V2 controller but not to the MNB-V1. 1
Fixed screw terminals that accept a single AWG #14 (2.08 mm2) wire or up to two AWG #18 (0.823 mm2) or smaller wires. Input signals of 1 to 11 Vdc must be converted to 0.45 to 5 Vdc with a voltage divider, part number AD-8961-220. In applications requiring universal inputs with ranges of 0 to 20 mA, a 250 shunt resistor kit, AD-8969-202, is needed. An 11 k shunt resistor kit, AD-8969-206, is required for a 10 k Thermistor Sensor (non-850 series) universal inputs.
5 6 7 8
To detect a closed switch, maximum resistance must be less than 300 . To detect an open switch, minimum resistance must be greater than 2.5 k. Minimum rate of 1 pulse per 4 minutes. Maximum rate of 1 pulse per second. When making an MS/TP cable, use a 1.3 x 3.5 mm Vdc power plug with strain relief (Vimex part number SCP-2009A-T, TAC part number E24-1442, or equivalent). The cable should be no longer than 6 ft. Connect MS+ to the center contact and MS to the _ outside contact: Note: The MS/TP cable described above is available from TAC as MNB-CT-CBL. Contact TAC for more information.
2 3
Figure1.2 MNB-Vx Terminal Connections.
F-27360-3
MNB-70 Zone Controllers
The I/A Series MicroNet BACnet Zone Controller, MNB-70, is an interoperable controller with native BACnet MS/TP communications support. The controller features: three universal inputs; one universal output; three digital (Triac) outputs; Sensor Link (S-Link) support; LED status indication; and screw terminal blocks. When programmed using WorkPlace Tech Tool, the MNB-70 provides a wide range of control strategies for heat pump, fan coil, unit ventilator, mixing boxes, and similar applications. Unique Features
SW 24 SW H1 24 SW H2 24 24H H3 24G (C GN OM) D ST MSATUS TP MS R TP CV XM T
UO A1 CO O M UI 1 CO M UI 2 S-L UI K/C 3 OM MS T MS P + TP SH LD
In addition to common MicroNet BACnet controller features (Common Controller Features section in this chapter), the MNB-70 offers the following:
I-Am button for BACnet I-am message broadcast. Integral MS/TP jack for direct connection of a PC with the WorkPlace
Tech Tool.
Small footprint. Enclosure approved for use in air plenums.

Memory Available
Table1.5 MNB-70 Available Memory. Model Number MNB-70 Flash 256 KB SRAM 8 KB SDRAM n/a EEPROM 4 KB FRAM n/a
Physical I/O Points

Table1.6 MNB-70 Inputs and Outputs. Model Number MNB-70 UI 3 Inputs and Outputs UO DO (Triac) 1 3
Refer to the "Input and Output Specifications" on page 12 for a detailed discussion of each input or output type. Time Clock The MNB-70 controller uses a software clock. This software clock defaults to a predefined Date/Time following a reset.
F-27360-3
Chapter 1
Wiring Terminals
Refer to Figure-1.3 for the power and network communications wiring connections available on the MNB-70 controller.
MNB-70 Controller Internal Triac Switches (3) Digital Outputs Total 24 VA (DO1+DO2), 12 VA (DO3) at 24 Vac, 50/60 Hz, Class 2. Pilot Duty SW24H1 (DO1) COM SW24H2 (DO2) UI2 SW24H3 (DO3) UI3 24H S-LK/COM 24G (COM) AC Power 20.4 to 30 Vac, 50/60 Hz Class 2 (EN 60742) 15 VA per controller plus DO load S-LK GND
LSB
1 UO1 COM
Universal Output 0 to 20mA into an 80 to 550 load Universal Inputs 0 to 5 Vdc 2 3 0 to 20 mA 10K Thermistor 4 1K Balco 1K Platinum 1K Resistive 10K Resistive Digital (dry switched contact) 5 6 Standard Pulse 7
UI1

MSB
MSTP + Physical Address MSTP

MS/TP Jack
S-LK Supports one I/A Series MN-Sxxx Sensor
SHLD
IAM
BACnet Network Communications
Fixed screw terminals that accept a single AWG #14 (2.08 mm2) wire or up to two AWG #18 (0.823 mm2) or smaller wires. Input signals of 1 to 11 Vdc must be converted to 0.45 to 5 Vdc with a voltage divider, part number AD-8961-220. In applications requiring universal inputs with ranges of 0 to 20 mA, a 250 shunt resistor kit, AD-8969-202, is needed. An 11 k shunt resistor kit, AD-8969-206, is required for a 10 k Thermistor Sensor (non-850 series) universal inputs.
5 6 7 8
To detect a closed switch, maximum resistance must be less than 300 . To detect an open switch, minimum resistance must be greater than 2.5 k. Minimum rate of 1 pulse per 4 minutes. Maximum rate of 1 pulse per second. When making an MS/TP cable, use a 1.3 x 3.5 mm Vdc power plug with strain relief (Vimex part number SCP-2009A-T, TAC part number E24-1442, or equivalent). The cable should be no longer than 6 ft. Connect MS+ to the center contact and MS to the _ outside contact: Note: The MS/TP cable described above is available from TAC as MNB-CT-CBL. Contact TAC for more information.
2 3
F-27360-3
MNB-1000 Plant Controller
The I/A Series MicroNet BACnet Plant Controller, MNB-1000, is an interoperable controller with native BACnet MS/TP communications support. The controller features Sensor Link (S-Link) support, LED status and output indication, two Ethernet ports, and screw terminal blocks. The MNB-1000s sequence of operation and BACnet image are fully programmable using WorkPlace Tech Tool, and can be applied to a wide range of mechanical equipment. Typical applications include central station air handlers, VAV air handlers, and cooling towers. Unique Features In addition to common MicroNet BACnet controller features ("Common Controller Features" on page 2), the MNB-1000 offers the following:
Optional NEMA 1 enclosure. IAM button for BACnet I am message broadcast. Integral MS/TP jack for direct connection of a PC with the WorkPlace
Tech Tool.
LED indication of Ethernet communication link and activity, DO state,

and UO state.
Application-programmable LED provides on/off indication of a

user-defined application parameter.
BACnet router functionality. Ethernet port bridging. 72 hour, battery-backed real time clock.
Memory Available
Table1.7 MNB-1000 Available Memory. Component C Motherboard Engine (Core) Engine (Boot) Flash 128 KB n/a 32 or 16 MBa 2 MB SRAM 4 KB 256 KB n/a n/a SDRAM n/a n/a 64 MB n/a EEPROM 4 KB 128 KB 1 Kb n/a FRAM n/a n/a n/a n/a
a.MNB-1000s with a date code prior to 0726 have 32 MB of core memory. Beginning with date code 0726, core memory was changed to 16 MB. However, because the MNB-1000 has always used only the first 16 MB of memory, this change has no impact on the controllers operation, the size of the application allowed, or the controllers application compatibility.
Physical I/O Points

Table1.8 MNB-1000 Inputs and Outputs. Model MNB-1000 UI 12 Inputs and Outputs DI UO 4 8 DO (Triac) 8
Refer to the "Input and Output Specifications" on page 12 for a detailed discussion of each input or output type. Time Clock The MNB-1000 features an onboard, real-time clock. A lithium battery provides backup power for up to 72 hours in the event of a primary power interruption. The real-time clock acts as a Date/Time server using native
F-27360-3
Chapter 1
BACnet services. In the absence of another Date/Time server on the network, the MNB-1000 can provide this functionality to other nodes on the BACnet internetwork. Battery Replacement If the real-time clocks battery becomes depleted, replace it with lithium battery, part number E17-137, according to the instructions in Figure-1.4. For additional disassembly and reassembly instructions, refer to MicroNet BACnet MNB-1000 Plant Controller Installation Instructions, F-27347 Caution: Follow static discharge precautions when handling the MNB-1000 and its component parts. Note: Whenever the battery is removed from the MNB-1000, the clock setting and volatile data will be lost. Reprogram the MNB-1000 as needed after installing the replacement battery.
1 2 3
If the controller is mounted inside an enclosure, open the enclosure cover. Remove power from the controller. Referring to MicroNet BACnet MNB-1000 Controller Installation Instructions, F-27347, remove the controllers main assembly from the base plate. Remove two screws, and then separate the printed circuit board from the cover. Locate the battery on the printed circuit board. Remove the depleted battery, and then install a new lithium battery, part number E17-137. Make sure that the positive (+) side faces upward. Reassemble the printed circuit board to the cover, and secure with the two screws removed in step 4. Referring to F-27347, reassemble the controllers main assembly to the base plate.
Restore power to the controller.
Printed Circuit Board
10 If applicable, close the enclosure cover. Cover
5 6
Screw (1 of 2) Base Plate
Lithium Battery E17-137
Printed Circuit Board

Figure1.4 MNB-1000 Real-time Clock Battery Replacement.
F-27360-3

Wiring Terminals
Refer to Figure-1.5 for the wiring connections available on the MNB-1000 controller.
20 Vdc Output 20 Vdc 10% at 100 mA
20V UI1 COM UI2 UI3 COM UI4 UI5 COM U6 U7 COM U8 U9 COM U10 11 COM UI12
24H 24G COM GND TO1 (DO1) C1 TO2 (DO2) C2 TO3 (DO3) C3 TO4 (DO4) C4 TO5 (DO5) C5
1 Internal Triac Switches (8) (Isolated) TO (DO) LEDs (8)
Universal Inputs 0 to 5 Vdc 3 0 to 20 mA 4 5 10K Thermistor 1K Balco 1K Platinum 1K Resistive 10K Resistive Digital (dry switched contact) 6 7 Standard Pulse 10 Digital Inputs Dry Switched 6 Contact Fast Pulse 11
AC Power 20.4 to 30 Vac 50/60 Hz Class 2 (EN 60742) 50 VA per controller Isolated from I/O
TO6 (DO6) C6 TO7 (DO7) C7 TO8 (DO8) C8

ACT
Digital Outputs 12 VA at 24 Vac, 50/60 Hz Each Triac output individually isolated from AC input and other I/O.
DI1 COM DI2 DI3 COM DI4 LD COM S-LK IO+ IO-
1 UO LEDs (8) 9
UO1 COM UO2 UO3 COM UO4
0 PORT
1 PORT
Local Display Supports connection to Local Display unit S-LK Supports one I/A Series MN-Sxxx Sensor 2 BACnet Network Communications
Universal Outputs 0 to 20 mA into an 80 to 550 load
LNK
RCV IO MSTP
XMT
UO5 COM UO6 UO7 COM UO8
1
DIS EN Disable Enable
SLD MS+ MSSLD
STATUS
AUX
IO EOL MS BIAS MS EOL MS BIAS ETHERNET
To detect an open switch, minimum resistance must be greater than 2.5 k. To detect an open switch, minimum resistance must be equal to or greater than 100 k.
All wiring terminals accept a single AWG #14 (2.08 mm2) or up to two AWG #18 (0.823 mm2) or smaller wires. Power and MS/TP connectors have removable screw terminals.
IAM
12
Physical Address
LSB
External load is required to illuminate UO LEDs.
MS/TP Jack
MSB
10 Minimum rate of 1 pulse per 4 minutes. Maximum rate of 1 pulse per second. 11 Minimum rate of 1 pulse per 4 minutes. Maximum rate of 10 pulses per second. 12 When making an MS/TP cable, use a 1.3 x 3.5 mm Vdc power plug with strain relief (Vimex part number SCP-2009A-T, TAC part number E24-1442, or equivalent). The cable should be no longer than 6 ft. Connect MS+ to the center contact and MS to the _ outside contact: Note: The MS/TP cable described above is available from TAC as MNB-CT-CBL. Contact TAC for more information.
3 4 5 6
Input signals of 1 to 11 Vdc must be converted to 0.45 to 5 Vdc with a voltage divider, part number AD-8961-220. In applications requiring universal inputs with ranges of 0 to 20 mA, a 250 shunt resistor kit, AD-8969-202, is needed. An 11 k shunt resistor kit, AD-8969-206, is required for a 10 k Thermistor Sensor (non-850 series) universal inputs. To detect a closed switch, maximum resistance must be less than 300 .
F-27360-3
11
Chapter 1
Input and Output Specifications

Universal Inputs
All MicroNet BACnet controllers use input and output types as described in this section. The universal input characteristics are software-configured to respond to one of the eight input types listed in Table1.9.
Table1.9 Universal Inputs. Input 10 k: Thermistor with 11 k: Shunt Resistor 1 k: Balco 1 k: Platinum 1 k: Resistive 10 k: Resistive Analog Voltage Analog Current Digital Characteristics Sensor operating range -40 to 250 F (-40 to 121 C), requires TAC model TSMN-57011-850 series, TS-5700-850 series, or equivalent. -40 to 250 F (-40 to 121 C), TAC model TSMN-81011, TS-8000 series, or equivalent. -40 to 240 F (-40 to 116 C), TAC model TSMN-58011, TS-5800 series, or equivalent. 0 to 1500 :. 0 to 10.5 k:. Range 0 to 5 Vdc 0 to 20 mA, requires external 250 : shunt resistor kit, AD-8969-202. Dry switched contact; detection of closed switch requires less than 300 : resistance; detection of open switch requires more than 2.5 k:.
See Figure-1.6 for examples of connections to universal inputs.
10 Thermistor (with an 11 k shunt resistor)
Controller UI1 COM UI2
4 to 20 mA Transmitter
Controller Inputs 250 UI1 COM 1 UI2
+ _
Sensor Power Source
0 to 5 Vdc Transmitter
Controller Inputs UI1 COM UI2 1 Resistor kit, AD-8969-202.
+ _
Sensor Power Source
Figure1.6 Universal Input Connections.
F-27360-3
I/A Series BACnet Hardware Universal Outputs

0 to 20 mA (output load from 80 to 550 :). See Figure-1.7 for examples of connections to universal outputs.
Controller Outputs UO1 COM UO2
4 to 20 mA Actuator
Controller Outputs UO1 COM UO2 2
0 to 10 Vdc Actuator
+ _
500
+ _
Controller Output Configured as 0 to 20 mA UO1 COM
Functional Devices RIBU1C Relay 3 N/C Wht/Blu 10-30 Vdc Wht/Yel COM COM N/O
1 2 3
Output accuracy degrades as input impedance decreases. Resistor kit, AM-708. Can be purchased through PS3, part number FUN-RIBU1-C.
Figure1.7 Universal Output Connections.
Digital Inputs
Dry switched contact. Detection of a closed switch requires less than 300 : resistance. When connected to a controllers digital inputs, detection of an open switch requires more than 100 k:. When connected to a controllers universal inputs (used as digital inputs), detection of an open switch requires more than 2.5 k:. See Figure-1.8 for examples of a connection to digital inputs.
Connection to Digital Inputs

DI Input On-Off Type Device NC COM NO Controller Inputs DI1 COM DI2
Connection to Universal Inputs

DI Input On-Off Type Device NC COM NO Controller Inputs UI1 COM UI2
Figure1.8 Fixed Digital Input Connections.
F-27360-3
13
Chapter 1 Digital Outputs, Triac

MNB-V2 and MNB-70 Table1.10 lists specifications for the Triac outputs featured on the MNB-V2 and MNB-70 controllers. Caution: The Triac (digital) outputs on MicroNet BACnet controllers are not protected against short circuits. Take necessary precautions to protect these outputs against short circuits.
Table1.10 Digital Outputs, Triac, on MNB-V2 and MNB-70. Input Common Terminal Rating (DO1+DO2)b Rating (DO3)b Default Output State Characteristicsa High side switching. TO outputs share a common supply (24H) that is independently switched to each output terminal (DO1, DO2, DO3). 24 VA total at 24 Vac, 50/60 Hz. 12 VA at 24 Vac, 50/60 Hz. OFF (inactive).
a.As with all Triac devices, a high-impedance meter on the output without a load will show 24 Vac, due to low level leakage through the device. b.As labeled on the controller, SW24H1=DO1, SW24H2=DO2, and SW24H3=DO3 (see Figure-1.2).
See Figure-1.9 for an example of a connection to an MNB-V2 or MNB-70 controllers Triac outputs.
Load1
Load2
Load3
SW24H1 (DO1) MNB-V2 Controller
SW24H2 (DO2)
SW24H3 (DO3)
GND
24G
24H
24 Vac
Primary
Class 2 Transformer
Figure1.9 MNB-V2 and MNB-70 Controller Triac Output Circuit Configuration.
Note: With the MNB-V2 and MNB-70, AC voltage to Triacs is sourced from the controller. This is different from the MNB-300 and MNB-1000 controllers, where AC voltage is sourced externally.
F-27360-3

MNB-300 and MNB-1000 Table1.11 lists specifications for the Triac outputs featured on MNB-300 and MNB-1000 controllers. Caution: The Triac (digital) outputs on MicroNet BACnet controllers are not protected against short circuits. Take necessary precautions to protect these outputs against short circuits.
Table1.11 Digital Outputs, Triac, on MNB-300 and MNB-1000. Input Isolation Common Terminal Rating Default Output State Characteristics Each output individually isolated from circuit common. Each TO has its own common terminal. This is the voltage switched to each TO output. 12 VA at 24 Vac, 50/60 Hz. OFF (inactive).
See Figure-1.10 for an example of a connection to an MNB-300 or MNB-1000 controllers Triac outputs.
24 Vac
24 Vac
24 Vac
Load1
Load2
Loadx
TO1
C1
TO2
C2
TOx
Cx
GND
24G
24H
Class 2 Transformer Primary
24 Vac
Figure1.10 MNB-300 and MNB-1000 Controllers Triac Output Circuit Configuration.
20 Vdc Output
20 Vdc 10% at 100 mA for supplying power to an external device. See Figure-1.11 for an example of a connection to a 20 Vdc output.
Auxiliary Device + Humidity 4 to 20 mA (example) 250 1
Controller 20V UI1 COM 1 Resistor kit, AD-8969-202, 4 to 20 mA only. Not required for Vdc.
Figure1.11 20 Vdc Output Connection.
F-27360-3
15
Chapter 1 Inputs from MN-Sx MicroNet Sensor

Table1.12 lists specifications for the inputs from MicroNet Sensors. For an example showing how a MicroNet Sensor may be wired to a MicroNet BACnet controller, see Figure-1.12.
Table1.12 Inputs from MN-Sx MicroNet Sensor. Input Space Temperature Space Humidity Local Setpoint Override Pushbutton Fan Operation and Speed Mode System Mode Emergency Heat Characteristics 32 to 122 F (0 to 50 C). 5 to 95% RH, non-condensing. Adjustable within limits set by application programming tool. For standalone occupancy control. On/off, speed (low/medium/high), or auto. Heat, cool, off, or auto. Enable or disable.
To Rest of the BACnet Network Controller COM SLK S-Link 3
Wire S-Link to terminals 1 and 2 on baseplate S-Link Jack MN-Sx Sensor
5 SLD (SHLD) MS+ (MSTP+) MS- (MSTP-)
MS/TP 1 Shield 2 4
_ +
MS/TP Jack 2
MS/TP wiring of controller to sensor screw terminals is optional. Note: To preserve the integrity of the network, the MS/TP network wiring connecting a MicroNet BACnet controller to an MN-Sx sensor must be run to the sensor and back, in daisychain fashion. A wire spur must not be used to connect the sensor to the controller. Observe consistent polarity when wiring. S-Link wiring is not polarity-sensitive. Tie the MS/TP shields together at the sensor. MS/TP shields must be connected to the SLD (or SHLD) terminal of all MicroNet BACnet controllers.
To Rest of the BACnet Network Wire MS/TP to terminals 3 and 4 on baseplate
2 3 4 5
Figure1.12 Sensor Link (S-Link) Connection.
F-27360-3
I/A Series BACnet Hardware Velocity Pressure Input

MNB-V1 and MNB-V2 Table1.13 lists specifications for the velocity pressure inputs on MNB-Vx controllers.
Table1.13 Velocity Pressure Input, on MNB-V1 and MNB-V2. Input Control Range Over Pressure Withstand Accuracy Sensor Type Tubing Connections Tubing Length Characteristics 0.004 to 1.5 in. of W.C. (0.996 to 373.5 Pa) 20 in. of W.C. (4.980 kPa) 5% at 1.00 in. of W.C. (249.00 Pa) with laminar flow at 77 F (25 C) and suitable flow station. Self-calibrating flow sensor (differential pressure). Barb fittings for 0.170 in. I.D. (4.3 mm I.D.) FRPE polyethylene tubing or 0.25 in. O.D./0.125 in. I.D. (6.4 mm O.D./3.2 mm I.D.) Tygon tubing (high and low pressure taps). 5 ft (1.52 m) maximum, each tube.
F-27360-3
17
Chapter 1
MicroNet Digital Wall Sensors

Each MicroNet BACnet controller supports a single MN-Sx digital wall sensor. 12 sensor models are presently available, six sensing zone temperature and six sensing both zone temperature and humidity. These range from a sensor-only model to one with seven pushbuttons and an LCD screen. Table1.14 provides a feature summary of the MN-Sx sensors.
Table1.14 MicroNet Sensors. Sensor Model MN-S1 MN-S1HT Features Sensor Model MN-S2 MN-S2HT Features
No buttons Sensor only. Its primary function is to provide room temperature or humidity sensing values to the controller via the Sensor Link.
One button Sensor (as in MN-S1). Override key with LED indicator, to allow the timed override of unoccupied to occupied modes of operation.
MN-S3 MN-S3HT Three buttons MN-S2 featuresSensor; Override key with LED indicator. 3-digit LCD for showing (typically) the current temperature. Up and Down keys to allow adjustment of the current setpoint.
MN-S4 MN-S4HT
Six buttons MN-S3 featuresSensor; Override key with LED indicator; LCD temperature, humidity, and function display (larger than in MN-S3, capable of showing up to four possible displays); Up and Down keys for setpoint adjustment. These sub-base functions: Mode key allowing two Heat/Cool/Auto/Off modes. Fan key to control fan operation or speed. Setpoint key to select up to four Heat/Cool setpoints. Seven buttons MN-S4 featuresSensor; Override key with LED indicator; larger LCD capable of showing up to four possible temperature, humidity, and function displays; Up and Down keys for setpoint adjustment; Mode key, Fan key, and Setpoint key sub-base functions. Emergency Heat key with LED indicator for emergency heat activation or indication (Heat Pump applications).
MN-S4-FCS MN-S4HT-FCS Six buttons Larger LCD capable of showing up to four possible temperature, humidity, and function displays Up and Down keys for setpoint adjustment. Three fan speed selection keys: High Fan Speed Medium Fan Speed Low Fan Speed Fan On / Off / Auto key.
MN-S5 MN-S5HT
F-27360-3
Common Sensor Features
An MN-Sx sensor communicates with (and is powered by) two Sensor Link (S-Link) terminals on a MicroNet controller it does not consume a typical I/O point. The S-Link connection between the sensor and the controller can use low-cost, twisted-pair wire up to 200 ft (61 m), and is not polarity sensitive. All MN-Sx sensor models also include an MS/TP jack for a convenient means of connecting a network tool, such as a Work Place Tech Tool PC, to the BACnet network. Under each MN-Sx sensors detachable cover is a pre-wirable baseplate and a removable electronic assembly (Figure1.13). The same baseplate is used in all MN-Sx sensor models.
Pre-wirable Sensor Baseplate
S-Link Screw Terminals (1 and 2)
Removable Electronic Assembly (contains temperature sensor)
MS/TP Jack
Figure1.13 MN-Sx Sensor Pre-Wirable Baseplate and Electronic Assembly.
Note: MN-Sx sensors have no independent intelligence. This means any MN-Sx sensors behavior is defined by how the application control logic has been engineered, compiled, and downloaded into the MicroNet controller. This allows replacement of a sensor without need of additional programming.
Keypad Icons
Depending on the sensor model used and the control application, various keypad buttons allow the sensor user to select or perform different functions.
Table1.15 TAC I/A Series MicroNet Sensor Keypad Icon Definitions.
+
+
Setpoint Up Down
Override
Emergency Heat Fan On/Off or Speed Fan Speed (MN-S4-FCS) Hi, Med, Low Fan On/Off Auto (MN-S4-FCS)
Mode
F-27360-3
19
Chapter 1
LCD Icons
Sensor models featuring an LCD typically show the current zone temperature as a default display. The MN-S4, MN-S4HT, MN-S5, and MN-S5HT models can also display selected icons, as shown in (Table1.16). These icons represent status items, depending on keypad input and the current control application.
Table1.16 TAC I/A Series MicroNet Sensor LCD Icon Definitions.
F C
Degrees F
Fan
Cool
Degrees C
Fan Speed Hi
On
Relative Humidity
Fan Speed Med
AUTO Auto
Off
Outdoor Air
Fan Speed Lo
Fan
Heat
Unoccupied
Diagnostic Functions
MN-S3, S3HT, S4, S4HT, S4-FCS, S4HT-FCS, S5, and S5HT sensors provide access to additional diagnostic data through the sensor keypad. This Diagnostic Mode data is displayed on the LCD screens of these sensors. See Figure1.14 (MN-S5 and MN-S5HT) and Figure1.15 (MN-S4-FCS and MN-S4HT-FCS) for descriptions of the various elements of the keypad and LCD display.
LCD. The top area displays analog values, such as temperature and setpoints. 1
F C %
The MN-S4, S4HT, S5, and S5HT can show additional icons in this area. 1
AUTO
Setpoint, Mode, and Fan buttons on the MN-S4, S4HT, S5, and S5HT.
!
+ +
Up/Down buttons on MN-S3, S3HT, S4, S4HT, S4-FCS, S4HT-FCS, S5, and S5HT are used to adjust setpoints and cycle through LCD icon displays. Override button and Override LED. MN-S2, S2HT, S3, S3HT, S4, S4HT, S4-FCS, S4HT-FCS, S5, and S5HT have this feature.
Emergency Heat button and LED (MN-S5 and MN-S5HT only).
1 The icons displayed in the LCD are dependent upon the sensor model used, the mode the controller is in, and the sensor's configuration in WP Tech. Not all icons are shown in this illustration.
Figure1.14 MN-S5 and MN-S5HT Keypad and LCD (Most LCD Icons Shown Illuminated).
F-27360-3
LCD. The top area displays analog values such as temperature, humidity, and setpoints. 1
F C
%
The MN-S4-FCS and S4HT-FCS can show additional icons in this area. 1
AUTO
+
Up/Down buttons are used to adjust setpoints and cycle through LCD icon displays.
Fan speed buttons, used to set High, Medium and Low speed.
Fan - On/Off Auto (optional) and Fan indication LED.
1 The icons displayed in the LCD are dependent upon the mode the controller is in and the sensor's configuration in WP Tech. Not all icons are shown in the illustration.
Figure1.15 MN-S4-FCS and MN-S4HT-FCS Keypad and LCD (Most LCD Icons Shown Illuminated).
The LCD screen includes separate displays (frames) for the MicroNet controllers:
Subnet and Node Address

Note: Subnet will always display (null), and the node address will reflect the address DIP switch setting.
ErrorsNot Supported AlarmsNot Supported Temperature and Relative Humidity Offsets

With the exception of the Temperature or Relative Humidity Offset, Diagnostic Mode data is view only. The Temperature or Relative Humidity Offset is adjustable and applies only to the integral temperature or humidity sensor in the MN-Sx sensor. See the I/A Series MicroNet Sensors General Instructions, F-26277, for detailed information on the features and operation of MN-Sx sensors, including the Diagnostic Mode.
F-27360-3
21
Chapter 1
Communications Wiring
Caution:
Be sure to observe proper polarity when wiring the controllers MS/TP

terminals to the MN-Sx Sensors wall plate. See Figure1.12.
To preserve the integrity of the network, the MS/TP network wiring

connecting a MicroNet BACnet controller to an MN-Sx sensor must be run to the sensor, then to the next controller, in daisy-chain fashion. A wire spur or tee must not be used to connect the sensor to the controller.
Communication wire pairs must be dedicated to MN-Sx (S-Link) and

MicroNet BACnet network communications. They cannot be part of an active, bundled telephone trunk.
When wiring the MNB-300 and MNB-1000 controllers, provide enough

strain relief (slack) in the wires to allow full range of movement for the input and output boards.
Shielded cable is required for MS/TP network wiring. Shielded cable is not required for S-Link wiring. If the cable is installed in areas of high RFI/EMI, the cable must be in
conduit.
The cables shield must be connected to earth ground at one end only.
Shield must be continuous from one end of the trunk to the other. Communications wiring includes a connection between the controller and a MicroNet MN-Sx Sensor via the S-Link, and a connection between the controller and the MicroNet BACnet Network. Optionally, an MS/TP jack on the MN-Sx sensor allows a PC with a network tool, such as WorkPlace Tech Tool, to be connected to the BACnet network.
Sensor Link (S-Link) Wiring
S-Link wiring powers and enables the MN-Sx sensor. The S-Link needs 24 gauge (0.51 mm) or larger, twisted pair, voice-grade telephone wire. The capacitance between conductors cannot be more than 32 pF per foot (0.3 m). If shielded cable is used, the capacitance between any one conductor and the others, connected to the shield, cannot be more than 60 pF per foot (0.3 m). Maximum wire length is 200 ft. (61 m). Note:
Each MicroNet BACnet controller supports one MicroNet Sensor

(MN-Sx).
S-Link wiring between the sensor and the controller is not polarity
sensitive.
If conduit is used between an MN-Sx sensor and a controller, the

MicroNet BACnet MS/TP network and S-Link wiring can be in the same conduit, so long as they are separate cables.
S-Link wiring can be in the same conduit with UI, UO, and DI Wiring, but
not DO wiring.
S-Link and AC power should not be run in the same conduit.
F-27360-3
MicroNet MS/TP Network Wiring
Caution:
Before terminating the communications (MS/TP) wiring at the controller,

test the wiring for the presence of a 24 Vac or 120 Vac voltage signal. If present, do not terminate the wiring at the controllers MS/TP terminals. Doing so will damage the transceiver chip, rendering the controller unable to communicate. Instead, take corrective action before terminating the controller.
Polarity must be observed for all MS/TP wiring within the MicroNet
BACnet network.
The MS/TP cables shield must be connected to earth ground (GND) at

one end only, to prevent ground currents. Shield must be continuous from one end of the trunk to the other.
To preserve the integrity of the network, the MS/TP network wiring

connecting a MicroNet BACnet controller to an MN-Sx sensor must be run to the sensor, then to the next controller, in daisy-chain fashion. A wire spur or tee must not be used to connect the sensor to the controller.
Do not mix MS/TP wiring with UI, UO, or DI types of wiring. If conduit is
used between an MN-Sx sensor and a controller, the MicroNet BACnet MS/TP network and S-Link wiring can be in the same conduit, so long as they are separate cables.
BACnet MS/TP network and Class 2 AC Power wiring can be in the

same conduit provided they are separate cables and the MS/TP wire meets the stated BACnet requirements and is properly shielded. See Chapter 2, Networking Practices, to design a MicroNet BACnet network, including recommended topologies.
Wiring Specifications
Wiring for an MS/TP EIA-485 (formerly RS-485) network shall meet the following specifications:
Use shielded, twisted-pair cable with characteristic impedance between

100 and 130 :.
Distributed capacitance between conductors shall be less than 15 pF/ft

(49 pF/m).
Distributed capacitance between the conductors and the shield shall be

less than 30 pF/ft (98 pF/m).
Foil or braided shields are acceptable. The maximum recommended length of an MS/TP segment is 4000 ft
(1200 m), using the cables listed in Table 1.17, on page 24.
F-27360-3
23
Chapter 1 Approved Cable Types

The stranded, twisted-pair cables listed in Table1.17 are recommended for wiring a MicroNet BACnet MS/TP network.
Table1.17 Recommended BACnet MS/TP Cable Types. No. of Devicesa AWG Plenum(mm2) Ratedb Electrical Specifications Capacitance @1 kHz Cond. DC Oper. Resis. per Temp. Cond-Cond Cond-Shield 1000 ft 22.0 pF/ft 42.0 pF/ft -4 to +176 F 25 : (73 pF/m) (140 pF/m) (-20 to +80 C) 31.0 pF/ft 59.0 pF/ft +32 to +140 F 24 : (103 pF/m) (197 pF/m) (-0 to +60 C) 25.0 pF/ft (83 pF/m) 11.4 pF/ft (38 pF/m) 12.0 pF/ft (40 pF/m) 45.0 pF/ft (150 pF/m) 24 : +32 to +140 F (-0 to +60 C) +302 F max. (+150 C max.) -94 to +392 F (-70 to +200 C)
Baud Rate
Cable
19,200 or Less
32 Devices or Less
24 (0.205) 24 Belden 82641 (0.205) 24 Belden 82502 (0.205) Belden 8641
No Yes Yes
76,800 or Less
Connect-Air W241P-2000F 24 128 Devices Connect-Air (0.205) or Less W241P-2000S 24 Belden 89841 (0.205)
Yes
n/a
27 :
Yes
22.0 pF/ft (73 pF/m)
24 :
a.The length of a wiring segment must be 4000 ft or less. b.Use plenum-rated cable for operating temperatures less than -4 F (-20 C).
F-27360-3
I/O Wiring
I/O connections include universal inputs, analog outputs, digital inputs, and digital outputs. See Figure-1.1, Figure-1.2, and Figure-1.5 for wire terminal information. Caution: If shielded cable is used, connect only one end of the shield to the common terminal at the controller. Universal Inputs (UI), Universal Outputs (UO), and Digital Inputs (DI) Caution:
Input and output devices cannot share common wiring. Each connected
device requires a separate signal and return conductor.
Power wiring cannot share conduit with UI, UO, S-Link, BACnet, or DI
wiring.
BACnet MS/TP network and Class 2 AC power wiring can be in the

same conduit provided they are separate cables and the MS/TP wire meets the stated BACnet requirements and is properly shielded. Note:
If maximum closed switch voltage is not more than 1.0 V and minimum
open switch voltage is at least 4.5 V, then solid state switches may be used for a UI or a DI.
UI, UO, DI, and S-Link wiring can share a single conduit.
UI, UO, and DI wiring needs at least AWG #24 (0.205 mm2), twisted pair, voice grade telephone wire. The capacitance between conductors cannot be more than 32 pF per foot (0.3 m). If shielded cable is used, the capacitance between any one conductor and the others, connected to the shield, cannot be more than 60 pF per foot (0.3 m). Table1.18 provides wiring specifications.
Table1.18 UI, UO, and DI Wiring Specifications. Connection Gauge AWG (mm2) 18 (0.823) 20 (0.518) 22 (0.326) 24 (0.205) Maximum Distance ft (m) 300 (91) 200 (61) 125 (38) 75 (23)
UI, UO, and DI
Refer to Figure1.6, Figure1.7, and Figure1.8, respectively, for examples of UI, UO, and DI connections.
F-27360-3
25
Chapter 1
Digital Outputs (DO) Caution:
The Triac (digital) outputs on MicroNet BACnet controllers are not

protected against short circuits. Take necessary precautions to protect these outputs against short circuits.
DO terminals accept up to one AWG #14 (2.08 mm2) or two AWG #18
(0.823 mm2) or smaller wires. The selected wire gauge must be consistent with the load current rating.
DO wiring cannot be intermixed with DI,UI,S-Link, and UO wiring. The

MicroNet BACnet MS/TP wiring can be in the same conduit, so long as they are separate cables.
MicroNet BACnet controllers are Class 2 devices. Each digital (Triac)

output on an MNB-300 or MNB-1000 controller can support up to 12 VA at 24 Vac, 50/60 Hz, pilot duty. On MNB-V2 and MNB-70 controllers, digital (Triac) outputs DO1 plus DO2 can support a combined total of 24 VA at 24 Vac, 50/60 Hz, pilot duty, while DO3 can support up to 12 VA. Note: Digital Output wiring can be intermixed with Class 2 power wiring. If the transformer is sized correctly, the 24 Vac Class 2 power source may be used for load power. See Figure1.16 for a diagram showing this with an MNB-300 or MNB-1000. Note: With the MNB-V2 and MNB-70, AC voltage to Triacs is sourced from the controller. This is different from the MNB-300 and MNB-1000 controllers, where AC voltage is sourced externally. Refer to Figure1.9 and Figure1.10 for examples of Triac (DO) connections.
F-27360-3
24 H 24 G GND
Primary
24 Vac
Class 2 Transformer
TO1 Load1 C1 TO2 Load2 C2 TOx Loadx Cx
Figure1.16 MNB-300 and MNB-1000Sharing Common Transformer Between DO Loads and Controller Power.
Power Supply Wiring
Caution:
Very important! When powering multiple Class 2 devices from the

same Class 2 power transformer, polarity must be observed (24H connected to 24H, and 24G connected to 24G).
MicroNet BACnet controllers are Class 2-only devices and must be

connected to a Class 2 source. Class 2 circuits must not intermix with Class 1 circuits.
The MNB-70, MNB-300, and MNB-Vx controllers contain a non-isolated

half-wave rectifier power supply and must not be powered by transformers used to power other devices containing non-isolated full-wave rectifier power supplies. Note that this precaution does not apply to the MNB-1000, whose IO are fully isolated from its power supply input. Therefore, an MNB-1000 can be powered with the same transformer used to power MNB-70, MNB-300, and MNB-Vx controllers. Refer to EN-206, Guidelines for Powering Multiple Devices from a Common Transformer, F-26363, for detailed information.
Power wiring cannot be intermixed with S-Link, UI, UO, or DI wiring. Do not mix MS/TP wiring with UI, UO, DI types of wiring. If conduit is
used between an MN-Sx sensor and a controller, the MicroNet BACnet MS/TP network and S-Link wiring can be in the same conduit, so long as they are separate cables.
Use a Class 2 power transformer supplying a nominal 24 Vac, sized

appropriately for the controller (16 VA for MNB-300, 15 VA for MNB-70 and MNB-Vx, and 50 VA for MNB-1000) plus the anticipated DO loads. The supply to the transformer must be provided with a breaker or disconnect. In European Community, transformer must conform to EN 60742.
F-27360-3
27
Chapter 1 The Class 2 power transformer may be used to power multiple Class 2
powered devices, provided that the transformer is properly sized to power all equipment simultaneously and all devices contain the same type of rectifier power supplies or internal isolation.
The transformer frame must be grounded.

Ensure that MNB-70, MNB-300, and MNB-Vx controllers have appropriate 24 Vac power. Where power is derived from a central transformer, ensure that that transformer is appropriately sized for the required VA with adequate margin and that the power wiring length is minimized and the appropriate wire size utilized to minimize line drops. Adequate transformer power margin should be allowed so that fluctuations of the primary transformer voltage or fluctuations in the secondary loads do not cause low voltage power conditions as seen at the 24 Vac input to the controllers. The MNB controllers contain circuitry which is designed to protect the integrity of the embedded flash memory under low-voltage or questionable input voltage conditions. In the event of a controller-perceived low-voltage condition, the controller will set a read-only flag and lock out all writes to memory as well as turn off controller outputs. The read-only flag can be easily viewed from the WPT commissioning tool under the Device Properties and will indicate the controller status as Operational, Read-Only. The Read-Only status can help serve as an indicator that the input voltage to the controller may be questionable. Attention should also be paid to the wire distance between the central transformer and the secondary loads, especially in the case of half-wave input devices like the MNB-70, MNB-V series and MNB-300 controllers. With half-wave type input devices, significant AC input current spikes can occur during the positive half-cycle of the AC input. Large resistances due to the wire lengths can cause significant voltage drops as seen from the controller AC input. In extreme cases, the controller may enter the read-only mode at apparent AC voltages exceeding 20 Vac due to the asymmetrical nature of the AC input voltage waveforms. In these cases, reducing the load on the transformer, reducing the wire length between the controller and the transformer, and using higher current rated wire will correct the problem. Note:
Power wiring terminals accept one AWG #14 (2.08 mm2) or up to two
AWG #18 (0.823 mm2) wires.
Power wiring can be intermixed with DO wiring. Twisted or untwisted cable can be used for power wiring. To preserve the integrity of the network, the MS/TP network wiring
connecting a MicroNet BACnet controller to an MN-Sx sensor must be run to the sensor and back, in daisychain fashion. A wire spur must not be used to connect the sensor to the controller. Figure-1.17 and Figure-1.18 are acceptable wiring configurations.
F-27360-3
To Rest of the BACnet Network
Primary
24 Vac Secondary Class 2
MNB-70 MNB-300 MNB-1000 MNB-V1 MNB-V2 24H 24G GND 2
1 MS/TP S-Link MN-Sx Sensor
Black White Green (Ground)
MS/TP From Rest of the BACnet Network
1 2
Optional connection provides local access to the BACnet network. Ground the frame of the transformer to a known ground.
Figure1.17 Single Controller Powered from a Separate Class 2 Power Source.
F-27360-3
29
Chapter 1
To Other MNB-70, MNB-300, MNB-1000, and MNB-Vx Controllers Primary MNB-70 MNB-300 MNB-1000 MNB-V1 MNB-V2 3
9 To Rest of the BACnet Network
Or to End-Of-Line Resistor E O L
5 6
7 SLD (SHLD) MS- (MSTP-) MS+ (MSTP+) Shield MS/TP S-Link 24H 24G GND MN-Sx Sensor 4 1
24 Vac Secondary Class 2 Black White Green (Ground)
2 1 2 3 Optional connection provides local access to the BACnet network. Ground the frame of the transformer to a known ground. MS/TP shield must be tied to ground (GND) at a single point only. Tie the MS/TP shields together at the sensor baseplate (there is no GND terminal at the sensor). In MS/TP networks, a 120 5% EOL resistor (part number 40-1758) must be used at each end of line. In the case of an MNB-300 or MNB-1000, EOL jumpers are provided. Do not use EOL resistors in standalone applications that do not include MS/TP communications. MS/TP shields must be connected to the SLD (or SHLD) terminal of all MicroNet BACnet controllers. Do not make an MS/TP connection to the sensor at the end of chain unless an EOL resistor is used. At least one set, and no more than two sets, of network bias resistors must be present on each network segment, preferably at an end (or ends) of the segment. This requires an MNB-300 or MNB-1000 with the appropriate jumper settings. Note: Bias resistors are built into UNC-520s. 2 MNB-70 MNB-300 MNB-1000 MNB-V1 MNB-V2 7 5 6 E O L Shield MS/TP 8 2 MNB-70 MNB-300 MNB-1000 MNB-V1 MNB-V2 7 SLD (SHLD) MS- (MSTP-) MS+ (MSTP+) Shield MS/TP S-Link 24H 24G GND E O MN-Sx Sensor 4 1 MNB-70 MNB-300 MNB-1000 MNB-V1 MNB-V2 7 SLD (SHLD) MS- (MSTP-) MS+ (MSTP+) Shield MS/TP 4 1
24H 24G GND
MN-Sx Sensor
S-Link 24H 24G GND 2 To Rest of the BACnet Network MN-Sx Sensor
Figure1.18 Multiple Controllers Powered from a Single Class 2 Power Source and Sharing Communications in a BACnet MS/TP Segment.
F-27360-3
Chapter 2 Networking Practices

This chapter provides an overview of the BACnet protocol and, more specifically, its implementation in the MicroNet BACnet system. This chapter then explains how MicroNet BACnet controllers and sensors are configured for an MS/TP network. The topics covered include:
Introduction to BACnet Architecture Overview Network Configuration MS/TP Network Considerations Other Network Setup Considerations Network Setup Procedures
Introduction to BACnet
In BACnet systems, BACnet devices use BACnet objects to share data. To allow this sharing of data, a BACnet network must be properly configured. On a properly configured network, the BACnet protocol carries data and uses Ethernet, Internet Protocol (IP), and Master Slave Token Passing (MS/TP) for network communication. At the device level, MS/TP network trunks connect individual BACnet compliant controllers.
F-27360-3
31
Chapter 2
Architecture Overview
Introduction
As implemented in a TAC I/A Series MicroNet BACnet network, the BACnet architecture uses one or more networking protocols to allow communication among controllers and engineering tools. At the device level, Master Slave Token Passing (MS/TP) networks can be used to connect up to 127 MNB-70, MNB-300, or MNB-Vx controllers and MS/TP tools to an MNB-1000 controller (see Table 2.1, on page 34). With 127 devices connected to an MNB-1000, all 128 MS/TP addresses on the MS/TP network are used. Similarly, up to 127 devices (MNB-70, MNB-300, MNB-Vx, MNB-1000, or MS/TP tools) can be connected to each network trunk of a UNC (Universal Network Controller) or ENC (Enterprise Network Controller), provided sufficient resources are available within the UNC or ENC (Table2.1). Multiple BACnet MS/TP networks can be connected by networking the MNB-1000s and UNC/ENCs, using BACnet over IP or BACnet over Ethernet. This is referred to as a BACnet internetwork. In such a configuration, the MNB-1000s and/or UNC/ENCs manage communication throughout the internetwork and serve as routers. Engineering tools can be used to manage controllers throughout an internetwork by connecting them to an MS/TP network trunk or by connecting to the IP network. Figure-2.1 shows a BACnet internetwork comprising four or five individual networks. There are thee individual MS/TP network trunks, each managed by a UNC/ENC or MNB-1000 and running individual BACnet devices. Ethernet or IP can be used as the networking technology for the backbone, adding a fourth network. If appropriate for the installation, both Ethernet and IP can be used on the network backbone. This would add a fifth network to the internetwork as shown in Figure2.1.
F-27360-3
PC Workstation with WorkPlace Tech Tool Suite and: Enterprise Server (used with UNC) or Enterprise Network Server (used with ENC)
Ethernet and/or IP Backbone
BACnet Internetwork
MSTP NetworkTrunk
UNC-520 Universal Network Controller or ENC-520 Enterprise Network Controller MicroNet BACnet MNB-1000 Plant Controller
Optional Port Bridging to Additional MNB-1000 Controllers
MicroNet BACnet MNB-300 Unitary Controller BACnet MS/TP Communications Bus MicroNet BACnet MNB-1000 Plant Controller BACnet MS/TP Communications Bus MicroNet BACnet MNB-70 Zone Controller
AO
BACnet MS/TP Communications Bus
MicroNet BACnet MNB-V1 or V2 VAV Controller
S-Link Sensor
S-Link Sensor
S-Link Sensor
AO
MicroNet BACnet MNB-70 Zone Controller
MicroNet BACnet MNB-300 Unitary Controller
MicroNet BACnet MNB-70 Zone Controller

AO
S-Link Sensor
S-Link Sensor
MicroNet BACnet MNB-300 Unitary Controller
BACnet MS/TP Comm Bus S-Link Sensor
S-Link Sensor
S-Link Sensor
Notebook PC with WorkPlace Tech Tool Software
S-Link Sensor
PC Workstation with WorkPlace Tech Tool Software Suite
Figure2.1 BACnet Internetwork
F-27360-3
33
Chapter 2
Network Configuration
The basic TAC I/A Series BACnet configuration is shown in Figure2.1. Observe the following networking guidelines, for best operation on your BACnet MS/TP network trunks.
Physical Limits
Number of Connected Devices
EIA-485 Specification 128 devices (including the UNC/ENC-520 or MNB-1000) is the physical limit of a MicroNet BACnet MS/TP network trunk. This limitation comes from the EIA-485 (formerly RS-485) specification on which a BACnet MS/TP network is based. According to this specification, the electrical limit of EIA-485 networks is 32 unit loads per segment (between repeaters), based upon the loading characteristics of the devices on that segment. However, because the UNC/ENC-520 and MicroNet BACnet controllers all use 1/4-load transceivers, four of these devices would together equal one unit load. Therefore, the actual electrical limit of an MS/TP network trunk comprised of a UNC/ENC-520 or MNB-1000, plus the MicroNet BACnet controllers connected to it, is 4 times 32, or 128 total devices. Note: In terms of the EIA-485 standard, a unit load is based upon a device that has a EIA-485 transceiver whose load effect is 12 k:. The design of the EIA-485 transceiver on MicroNet BACnet controllers results in a load effect of 48 k:, thus making these controllers 1/4-load devices. Maximum Number of Devices Table2.1 lists the physical limit on the number of devices that can be connected to an MNB-1000, a UNC-520, or an ENC-520.
Table2.1 Maximum Number of Connected Devices on MS/TP Trunk. MicroNet BACnet Router MNB-1000 UNC-520 ENC-520 Maximum Number of MS/TP Connections 1 4 4 Physical Limit of Connected Devices (not including router) 127 508 508
Note: The physical limit on the number of connected devices shown in Table2.1 does not mean that a UNC-520, an ENC-520, or an MNB-1000 can effectively support that number of devices. There are many logical factors that can further limit that number. Refer to Logical Limits, below.
Logical Limits
Addressing Limit
The addressing of an MS/TP network trunk is limited to 256 Media Access Control (MAC) addresses, numbered 0 to 255. Master devices are restricted to the first 128 addresses (0 to 127), slave devices may use any address
F-27360-3
from 0 to 255. Because all UNC/ENC-520s and MicroNet BACnet controllers on an MS/TP network trunk are master devices, they must be addressed with the first 128 addresses. As such, the address limit is the same as the physical limit of an MS/TP network trunk.
Limits to Number of Polled Points
Methods for Limiting Polled Points There are three means for limiting the number of polled points, as described below. Note: For additional information related to limiting the number of polled points, refer to the latest BACnet Best Practices document. This document can be found in the Tech Zone, at The Source (http://source.tac.com/) PollOnDemand Containers: The first method uses PollOnDemand containers, which limit the polling to those points that are being queried by an active GxPage. This means the points are polled if the graphic is being viewed in a browser, otherwise they do not. Points that must be polled all of the time (such as schedules), and points that are being logged, do not qualify for use in PollOnDemand containers. Number of Devices: The second method is to limit the number of connected devices, as fewer devices equals fewer polled points. COV Subscription: The third method is to use COV subscription to create subscriptions that send notifications to the subscribing device, thereby limiting the overall number of polled points. COV subscription can be used for most points that support the Subscribe COV service. However, it should be avoided for points that change value quickly, because every change of value greater than the COV increment will result in a notification. Note: The relationship between polled points and COV subscribed points is not always easy to define. In general, COV subscribed points would not be considered polled points. However, a UNC/ENC-520 station will poll any BACnet output or AV priority point, therefore these point types still count as polled points, even when they are configured as COV subscribed points.
Limits to Resources
Communications through UNC/ENC-520s is further limited by the availability of Java resources (resource count) and other resources, such as processor and memory. A shortage of these resources will limit the devices on an MS/TP network to a number less than the physical limit. There are two methods for connecting a PC or notebook computer running WorkPlace Commissioning Tool (or WorkPlace Tech 5.x) to an MS/TP network. BACnet Ethernet or BACnet/IP The preferred method is to connect the PC or notebook computer to a LAN connection, and use BACnet/IP to connect to the BACnet internetwork. The BACnet internetwork connection routes the BACnet messages to the BACnet MS/TP network, as needed, through BACnet routers
Connection to an MS/TP Network
F-27360-3
35
Chapter 2
(UNC/ENC-520s or MNB-1000s). BACnet Ethernet can also be used to connect to the BACnet internetwork, but communication speed will be slower. Controller MS/TP Jack or Sensor S-Link Jack The second method connects the PC or notebook computer directly to the MS/TP network, either at the MS/TP jack on a MicroNet BACnet controller, or at the MS/TP jack of an S-Link sensor, provided it is connected to the MS/TP trunk. This type of connection requires a USB-to-MS/TP converter or EIA-232-to-MS/TP converter, depending on the port used on the computer. Caution: A notebook computer connected to the MS/TP jack on an S-Link Sensor creates a Tee connection into the daisy-chained MS/TP network trunk. To minimize disruption of MS/TP trunk communications, the cable connecting the notebook to the MS/TP trunk should be as short as possible.
MS/TP Network Considerations

Master and Slave Devices Physical Addressing
On a BACnet MS/TP network, TAC I/A Series MicroNet BACnet controllers operate as master devices only. Valid DIP switch settings for these master controllers are 0-127. Each controller on an MS/TP network trunk is initially identified by a unique MAC address. The physical address is defined by the network number of the MS/TP network trunk into which the controller is connected and the addressing DIP switch on the controller. Procedures for assigning an MS/TP network number to an MS/TP network trunk under the control of a UNC-520 or ENC-520 are provided in the BACnet Integration Reference. Procedures for assigning an MS/TP network number to an MNB-1000 are found in the Commissioning Tool and Flow Balance Tool Users Guide, F-27358.
F-27360-3
Networking Practices Required Configuration

The DIP switch must be set on every controller that is added to an MS/TP network trunk. This number must be unique on that particular MS/TP network trunk but can be used on another internetworked MS/TP network trunk. For example, referring to Figure2.1, each of the three MS/TP network trunks shown could use the DIP switch setting 5. Refer to (Figure2.2).
Least Significant Bit (LSB)
O N
1 2 3 4 5 6 7 8
Most Significant Bit (MSB)
Figure2.2 DIP Switch Set to MAC Address 5
However, the same MAC address can not be used on two controllers that are on the same MS/TP network trunk. Note that the least significant bit on the DIP switch is switch 1, the left-most switch. Use Table2.2 to calculate the DIP switch value for MAC addressing.
Table2.2 DIP Switch Value Switch Number 1 (LSB) 2 3 4 5 6 7 8 (MSB) Amount to add if switch is on 1 2 4 8 16 32 64 Always OFF
Caution: A unique MAC address must be assigned to each controller on an MS/TP network trunk for communication to occur.
Duplicate MAC addresses on an MS/TP network trunk will result in

erratic behavior, lost tokens, and disrupted communication.
There is no software tool that will identify duplicate MAC addresses on

an MS/TP network trunk.
Be sure a network wiring diagram is used to assign and record MAC

addresses assigned to the controllers.
F-27360-3
37
Chapter 2 Optimization
MS/TP relies on a communication token that is passed among all devices on an MS/TP network. Starting at MAC address 0 the token is passed, sequentially, to each device on the MS/TP network trunk until it reaches the device with the greatest MAC address (i.e. Max Master, explained later in this paragraph). The token then starts again at address 0 and repeats the cycle. A controller will attempt to pass the token to the MAC address one greater than its own. If no device occupies that MAC address, the sending controller tries the next address. It continues searching sequential addresses until it finds a device to accept the token. For each failed pass there is a slight delay. Multiple gaps in the sequential MAC addressing can result in increased communication overhead and decreased network efficiency. Therefore, MAC addresses should be a contiguous set. Later, using the Commissioning Tool, a value will be set to indicate the greatest valid MAC address on the MS/TP network trunk. This value is called Max Master. It prevents devices from searching for valid MAC addresses beyond the greatest valid MAC address. Additional optimization can be performed later by using the Commissioning Tool. Refer to: the WorkPlace Tech Tool 5.x Engineering Guide Supplement, F-27356; the BACnet Best Practices document, found in the Tech Zone, at The Source (http://source.tac.com/); and the WorkPlace Tech Tool Release Notes, which is provided with WorkPlace Tech and is also available in Tech Zone at The Source (http://source.tac.com/). A BACnet tool, connected to an MS/TP network, requires a MAC address for token passing. Leave one MAC address unused and available for use by a BACnet tool.
MAC Address for BACnet Tools
F-27360-3
Other Network Setup Considerations

Figure2.3 shows an IP network backbone and an Ethernet network backbone plus thee MS/TP network trunks forming one BACnet internetwork. The network backbone can be Ethernet only, IP only, or both.
Optional Port Bridging to One or Two Additional MNB-1000 Controllers
2 3 1 4 5
AO
7
AO
8
AO
Up to 127 controllers can be attached to each trunk of a UNC-520 or ENC-520 network controller, provided there are sufficient resources available within the device. Only one UNC-520, ENC-520, or MNB-1000 may be configured to route between any two BACnet networks. MNB-1000 configured for routing to MS/TP network trunks and optionally, between Ethernet and IP. A high degree of communications performance may not be possible if more than one, or possibly two, MNB-1000 controllers are placed downstream of a bridge. Therefore, no more than three MNB-1000 controllers should be bridged together.
5 6 7 8
Up to 127 conttrollers can be attached to an MNB-1000. MNB-1000 not configured for routing. MS/TP trunks are daisy-chained. A notebook connection to a controller or the MS/TP jack of an S-Link Sensor is a Tee. It must be as short as possible to preserve network integrity, and have its own unique MAC address.
2 3 4
Figure2.3 BACnet Networking Restrictions
F-27360-3
39
Chapter 2
Port Bridging
Beginning with Release 1.2, port bridging is enabled on the second Ethernet port of the MNB-1000 controller. With port bridging, the MNB-1000 acts as a switch, where messages to and from the LAN are passed from the first Ethernet port to the second port (Figure2.4). As such, port bridging is a convenient method for connecting additional MNB-1000 controllers.

3 Ethernet Port 0 1 4 2 Ethernet Port 1 1 4 MicroNet BACnet MNB-1000 Plant Controller 3
5 3 6 MicroNet BACnet MNB-1000 Plant Controller
5 3 6
MicroNet BACnet MNB-1000 Plant Controller
1 2
The MNB-1000 contains two Ethernet ports: Port 0 (labeled "0 Port) and Port 1 (labeled "1 Port"). The Ethernet port that is connected to the IP network will operate at the rate implemented in that network (10 or 100 mbps). When using port bridging, observe the following limitations: The maximum distance between MNB-1000 controllers is 300 ft. The throughput through the bridge is limited to 2.5 megabits. The throughput of the bridge is limited by the activity level of the MNB-1000 controller at any given time and the resources available to process the bridged data.
When port bridging, data is simply passed through an MNB-1000 from one Ethernet port to the other. Neither port is designated as the "uplink" or "downlink" port. Therefore, either of the two Ethernet ports of an MNB-1000 may be connected to the IP network, and the other to an adjoining MNB-1000. As a general rule, do not place any customer IT devices such as computers or routers downstream of an MNB-1000 used as a bridge. Doing so may adversely affect the performance of such devices. All devices being port-bridged to an MNB-1000 will operate at the reduced rate of 2.5 mbps (see note 3). As a result, a high degree of communications performance may not be possible if one, or possibly two, MNB-1000 controllers are placed downstream of a bridge. Therefore, no more than three MNB-1000 controllers should be bridged together.
Figure2.4 MNB-1000 Port Bridging.
F-27360-3
Single Path to Device
BACnet requires that there be no more than one communication path between two devices anywhere on the BACnet internetwork. More than one communication path between two devices results in a circular path. Normally this does not occur because the nature of a properly configured network does not allow multiple paths between devices. On a BACnet internetwork that uses both BACnet/IP and BACnet Ethernet, only one UNC/ENC or MNB-1000 in the internetwork may be configured to route between Ethernet and IP. If two or more devices are configured to route between BACnet Ethernet and BACnet/IP, multiple paths between controllers result. In Figure2.5 a UNC/ENC routes between BACnet/IP and BACnet Ethernet. It also routes MS/TP traffic for the BACnet trunk that is attached to it. The MNB-1000 routes BACnet Ethernet or BACnet/IP for the BACnet trunk that is attached to it. In this example, the MNB-1000 would be the second device configured to route between BACnet/IP and BACnet Ethernet, and this is not permitted. Allowing both the UNC/ENC and the MNB-1000 to serve as routers violates BACnet internetwork design requirements. This may cause intermittent communication failures, bandwidth problems, or the interruption of routing to MS/TP network trunks, as well as the shutdown of BACnet routing on the UNC/ENC (a self-protective feature).
Ethernet and IP Backbone

IP Ethernet IP Ethernet
One Universal Network Controller (UNC) or Enterprise Network Controller (ENC) can route between Ethernet and IP.
A second device must not be configured for both Ethernet and IP in a BACnet internetwork.
AO
AO
Figure2.5 Incorrect Router Configuration
Routers and Network Numbers
In a BACnet internetwork every network is assigned a unique network number. BACnet routers use the network numbers to route communication across the internetwork to individual controllers. The network numbers of all networks connected to a router must be entered into that router using the setup tool appropriate for the router. The Commissioning tool is used to enter network numbers in an MNB-1000. In a UNC, WorkPlace Pro is used to enter network numbers, and WorkBench is the tool used for this purpose with the ENC.
F-27360-3
41
Chapter 2
Network Setup Procedures

The general procedures for setting up a BACnet network are described below. Follow these procedures to prepare a BACnet network trunk for logical addressing. After you complete these setup procedures, the Commissioning Tool can be used to configure logical addressing. For logical address configuration, refer to the Commissioning Tool and Flow Balance Tool Users Guide, F-27358.
Overview
The general steps are listed below and detailed in the following sections. 1. Perform the physical installation of controllers and cabling. 2. Set the DIP switches on the controllers. 3. Power on the controllers. 4. Use WorkPlace Pro or WorkBench to set BACnet service properties. Caution: Do not learn controllers until Step 6 has been completed. This allows traffic to be routed to the MS/TP network trunk(s) attached to the UNC/ENC and assigns logical addressing to the unit. 5. Use the Commissioning Tool to commission the MNB-1000(s) connected directly to the backbone and used for routing, if applicable. This allows traffic to be routed to the MS/TP network trunk attached to the MNB-1000 and assigns instance numbers to the MNB-1000. 6. Use the Commissioning Tool to assign instance numbers to MNB-1000 that are not directly connected to the backbone, MNB-70 controllers, MNB-300 controllers, and MNB-Vx controllers.
Physical Installation
Install the cabling and controllers following the installation procedures in the Wiring Guidelines portion of this manual and the following guides:
MicroNet BACnet MNB-70 Zone Controller Installation Instructions,

F-27456
MicroNet BACnet MNB-300 Unitary Controller Installation Instructions,

F-27345
MicroNet BACnet MNB-V1, MNB-V2 VAV Controllers Installation

Instructions, F-27346
MicroNet BACnet MNB-1000 Plant Controller Installation Instructions,

F-27347
I/A Series UNC-520 Installation Instructions, F-27391 I/A Series ENC-520 Installation Instructions, F-27416
Set the DIP Switches on the Controllers
A DIP switch must be set on each MNB-70, MNB-300, MNB-1000, MNB-V1, and MNB-V2. The number must be unique on the MS/TP network trunk in which the controller is installed but can be repeated elsewhere on the BACnet internetwork. Refer to "Physical Addressing" on page 36. Follow the wiring diagram to set the DIP switch on each controller.
F-27360-3
Power on the Controllers Commission UNCs and ENCs Commission the Controllers
Apply power to the controllers. A transmit LED and a receive LED will blink on each controller to show communication.
For UNC or ENC commissioning instructions, refer to the BACnet Integration Reference.
For Commissioning Tool details, refer to the Commissioning Tool and Flow Balance Tool Users Guide, F-27358. Controllers must be commissioned to interoperate with other BACnet devices.
F-27360-3
43
Chapter 2
F-27360-3
Chapter 3 Checkout and Troubleshooting

This chapter provides guidance for troubleshooting MicroNet BACnet controllers and sensors, including:
Mechanical Hardware Checkout Communications Hardware Checkout
Mechanical Hardware Checkout

Check out the mechanical hardware as follows: MNB-Vx Controllers Only 1. Verify both set screws are tightened to damper shaft. 2. Press and hold manual override button and rotate damper by turning damper shaft. Verify damper moves freely between full open and full closed positions. All MNB Controllers 1. Verify that the wiring between the controller and the MicroNet Sensor is installed according to the job wiring diagram, and with national and local wiring codes. Caution:
Before terminating the communications (MS/TP) wiring at the controller,

test the wiring for the presence of a 24 Vac or 120 Vac voltage signal. If present, do not terminate the wiring at the controllers MS/TP terminals. Doing so will damage the transceiver chip, rendering the controller unable to communicate. Instead, take corrective action before terminating the controller.
Polarity must be observed for all MS/TP wiring within the MicroNet
BACnet network.
S-Link wiring between the sensor and the controller is not polarity
sensitive. 2. If the controller is part of a MicroNet BACnet network, verify that the MS/TP wiring between the controller and other devices is installed in accordance with the job wiring diagram, following national and local electrical codes.
F-27360-3
45
Chapter 3
3. Connect controllers in a MicroNet BACnet network in daisy-chain fashion. Be sure that MS/TP polarity, biasing, and termination are correctly implemented for each network segment. 4. Check for voltage at the COMM wires before setting termination at the controllers. Be sure voltage is not 24 to 120 Vac. 5. Verify that 24 Vac power is provided from a Class 2 power transformer, and that power wiring is installed in accordance with the job wiring diagram, following national and local electrical codes. 6. If multiple devices are powered from a common transformer, verify that all issues associated with powering multiple devices from a common transformer have been addressed. In particular, verify that wiring polarity has been maintained between all connected devices (i.e. 24H connected to 24H and 24G connected to 24G). Note: For more information, refer to EN-206, Guidelines for Powering Multiple Full-Wave and Half-Wave Rectifier Devices from a Common Transformer, F-26363. 7. Verify that digital outputs are wired according to the job wiring diagram, and with national and local electrical codes. 8. Make certain that electrical current requirements of the controlled device do not exceed the rating of the controllers digital outputs. Caution: The digital outputs are not internally protected from over-current or over-voltage conditions.
F-27360-3
Communications Hardware Checkout

See Figure3.1 for the locations of controller LEDs and jumpers. Table3.1 provides a guide for interpreting the LED indications.
MNB-300 Unitary Controller 5

TO (DO) LEDs (8)
UO LEDs (3)
TO (DO) LEDs (6)
2 2
XMT STATUS RCV
6 1
STATUS
IO MSTP AUX
UO LEDs (8)
RCV
XMT
5 MNB-V1 / -V2 Controller 1 1 5 MNB-70 Controller 2 3 4 1 3

Bi-color status LED: green=good; red=fault; flashing red=bootloader mode. Green data transmission LED. Amber data reception LED. Red/Green bi-color AppLED: Can be defined in the device's application program. Off=0, Green=1, and Red=2. Internal Triac switches. EOL and bias jumpers.
5 6
2 1 3
Figure3.1 Location of Controller LEDs and Jumpers.
F-27360-3
47
Chapter 3
Table3.1 LED Indications. Controller MNB-1000 MNB-300 MNB-V1 MNB-V2 MNB-70 Indicator Context Status Corrective Action
Status
X X X X Status LED Red/green Power-up Blinks red briefly then becomes solid green. No action Indicates: A normal, healthy state. required. Blinks red during power-up, which takes 70 to 90 seconds to complete. When the No action power-up process successfully completes, required. the Status LED becomes solid green. Indicates: Normal operation. Blinks red for a period of 2 minutes, then switches to solid red ON. Indicates: Power-up process has failed. Controller fault. Solid green. Indicates: A normal, healthy state. Solid red. Indicates: A controller fault. Wink Mode. Blinks red ON for 3 seconds, then OFF for 1 second, repeatedly for a period of 20 seconds (default). The MN-Sx sensors Override LED also blinks (all sensors except MN-S1 and MN-S1HT). Indicates: Normal operation. Wink Mode. Blinks red ON for 1 second, then OFF for 1 second, repeatedly for a period of 20 seconds (default). The MN-Sx sensors Override LED also blinks (all sensors except MN-S1 and MN-S1HT). Indicates: Normal operation. Contact TAC Technical Services. No action required. Contact TAC Technical Services.
Status LED Red/green
Power-up
Status LED X Red/green Status LED Red/green Status LED Red/green
Power-up
Normal Operation Normal Operation
Normal Operation
No action required.
Normal Operation
No action required.
After Flash Upgrade
Bootloader Mode. Solid red ON at power-up. Indicates: That the bootloader code is executing and the CRC test is either pending or has failed. No action Blinks red ON for 1 second, then OFF for required. 1 second. Indicates: The bootloader has passed the CRC test. Continues to repeat this pattern while the bootloader waits for a firmware upgrade or prepares for the jump to existing firmware.
F-27360-3

Table3.1 LED Indications. (Continued) Controller MNB-1000 MNB-300 MNB-V1 MNB-V2 MNB-70 Indicator Context Status Corrective Action
Power-up
Bootloader Mode. Continues to blink red beyond the initial 2 minute period during power-up. Indicates: The motherboard is in the bootloader mode of operation, and is awaiting a firmware upgrade. Cold Reset without Power Loss (commanded from the network management tool). MN-Sx sensor is shut OFF for 2 seconds, and then communication between the controller and the sensor is re-established. Indicates: Normal operation. This allows the sensor to mimic the reset without power loss scenario.
No action required.
MN-Sx Sensor
Cold Reset
No action required.
Application Download
Normal controller function until download is completed. LED flashes red briefly following application No action download. required. Controller resets. Indicates: Normal operation. Flashes ON red for 1 second, then OFF for 1 second, repeatedly for a period of 4 to No action 6 minutes following the file transfer from the required. PC to the controller. Indicates: Normal operation. Red or green ON, or OFF, as programmed for the application. Indicates: Normal operation. Solid ON when the respective input is turned ON. Indicates: Normal operation. Take action as appropriate for the application.
Firmware Upgrade
Auxiliary LED Red/green
Normal Operation
Outputs
X Triac Output X LEDs Red Universal Output LEDs Red Input is Turned ON No action required.
Normal Operation
Illuminates in proportion to the output command signal, whether a load is attached No action or not. required. Indicates: Normal operation. Illuminates in proportion to the output command signal, provided a proper load is attached to the output. Indicates: Normal operation. Note: Output LEDs on open circuit outputs will not illuminate.
Universal X Output LEDs Red
Normal Operation
No action required.
F-27360-3
49
Chapter 3
Table3.1 LED Indications. (Continued) Controller MNB-1000 MNB-300 MNB-V1 MNB-V2 MNB-70 Indicator Context Status Corrective Action
Communications
Flashes as messages are sent from the controller. Indicates: Normal operation. The controller is healthy and is sending out a No action Poll-for-Master message. required. Note: This LED should flash even if the controller is not connected to any other controllers (except for V1.0 of the MNB-1000). Flashes as messages are received from the network. Indicates: Normal operation. No action Note: This LED should remain OFF after required. disconnecting the MS/TP segment from the controller. 1. Check for shorted MS/TP+ to SLD or GND and make corrections as needed. 2. Verify network wiring integrity, polarity, and biasing, and make corrections as needed. Ensure that network bias resistors are installed, and that EOL resistors are properly placed on the network segment daisy chain.
MS/TP Transmit Normal X Data LED Operation Green
MS/TP Receive X Data LED Amber
Normal Operation
MS/TP Receive X Data LED Amber
Normal Operation
Solid ON. Indicates: 1. MS/TP+ shorted to SLD or GND on MS/TP network wiring. 2. Excessively heavy MS/TP traffic.
MS/TP Transmit and Receive Normal X Data LEDs Operation Green and Amber
LEDs behave erratically. Indicates: Improperly biased MS/TP network segment.
Ethernet 10/100 Link Integrity Normal X LED Operation Green Ethernet 10/100 Normal X Activity LED Operation Amber
Solid ON. Indicates: Normal operation. The link to the No action Ethernet PHY (physical layer transceiver) is required. good. Flashes ON for approximately 80 milliseconds each time there is receive or transmit activity. Indicates: Normal operation. No action required.
F-27360-3
Service
Components within MNB-70, MNB-300, MNB-V1, MNB-V2, and MNB-1000 controllers cannot be field repaired. If there is a problem with a controller, follow the steps below before contacting TAC Technical Support. 1. Make sure all controllers are connected and communicating to the desired devices. 2. Check that all sensors and controlled devices are properly connected and responding correctly. 3. If a controller is operating, make sure the correct application is loaded, using Work Place Tech Tool. For more information, see the WorkPlace Tech Tool 4.0 Engineering Guide, F-27254, and the WorkPlace Tech Tool 5.x Engineering Guide Supplement, F-27356. 4. Record the precise hardware setup, indicating the following:
Version numbers of applications software. Controller firmware version number. Information regarding the WorkPlace Tech Tool. A complete description of the difficulties encountered.
F-27360-3
51
Chapter 3
F-27360-3
TAC 1354 Clifford Avenue P.O. Box 2940 Loves Park, IL 61132-2940
F-27360-3
2007 TAC. All rights reserved
Printed in U.S.A.

27360

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

27360

Загружено:

Авторское право:

Доступные форматы

TAC I/A Series MicroNet BACnet Wiring and Networking Practices Guide

Copyright 2007, TAC.

MicroNet BACnet Wiring and Networking Practices Guide

I/A Series WorkPlace Tech Tool 4.0 Users Guide

WorkPlace Tech Tool 5.x Engineering Guide Supplement

Application engineers Service personnel

I/A Series BACnet Best Practices

BACnet PIC Statement

I/A Series MicroNet MN-SX Series Sensors General Instructions

iv MicroNet BACnet Wiring and Networking Practices Guide

For more information, consult the following documentation:

Description Niagara Release 2.3.4 Installation and Upgrade Instructions

Conventions Used in this Manual

The following conventions apply to this printed manual:

Menu commands appear in bold.

Italics is used for emphasis in a statement, such as:

Acrobat (PDF) Conventions

Hypertext links in this document include all entries in the Table of

MicroNet BACnet Wiring and Networking Practices Guide

Abbreviations Used in this Manual

ANSI AWG BACnet BAS B-ASD C DI DIP DO EEPROM

vi MicroNet BACnet Wiring and Networking Practices Guide

MicroNet BACnet Wiring and Networking Practices Guide

viii MicroNet BACnet Wiring and Networking Practices Guide

Table of Contents Preface

I/A Series BACnet Hardware

MicroNet BACnet Wiring and Networking Practices Guide

Checkout and Troubleshooting

x MicroNet BACnet Wiring and Networking Practices Guide

Chapter 1 I/A Series BACnet Hardware

MicroNet BACnet hardware products include controllers and compatible sensors.

MicroNet BACnet controllers provide direct-digital control for packaged

MicroNet sensors are digital wall temperature and humidity sensors

MicroNet BACnet Wiring and Networking Practices Guide

MicroNet BACnet Controllers

Common Controller Features

24 Vac powered. Capability to function in standalone mode or as part of an I/A Series

Isolated EIA-485 (formerly RS-485) transceiver for MS/TP

Firmware upgradeable over the network or directly to the controller.

2 MicroNet BACnet Wiring and Networking Practices Guide

I/A Series BACnet Hardware

MNB-300 Unitary Controller

Physical I/O Points

MicroNet BACnet Wiring and Networking Practices Guide

UI1 COM UI2

MNB-300 Unitary Controller

AC Power 20.4 to 30 Vac 50/60 Hz Class 2 (EN 60742) 16 VA per controller

TO1 (DO1) UI3 COM

Internal Triac Switches (Isolated)

UI5 TO3 (DO3) COM C3 UI6 TO4 (DO4)

Universal Outputs 0 to 20 mA into an 80 to 550 load

UO1 C4 COM UO2

Connectors (2) UO LEDs (3) 7

TO5 (DO5) C5 STATUS RCV

UO3 COM IAM S-LK MS+ MSSLD

1 TO (DO) LEDs (6)

Figure1.1 MNB-300 Terminal Connections.

4 MicroNet BACnet Wiring and Networking Practices Guide

I/A Series BACnet Hardware

MNB-V1, MNB-V2 VAV Controllers

SW 24 SW H1 24 SW H2 24 24H H3 24G (C GN OM) D ST MSATUS MSTP R TP CV XM T

Physical I/O Points

MicroNet BACnet Wiring and Networking Practices Guide