I - A Series WorkPlace Tech Programming. Pre-Course Material

I/A Series WorkPlace Tech
Programming
Pre-Course Material
Each student should read this document before attending

the WorkPlace Tech Programming Course.
Also complete the review questions at the end of the
document before coming to class.
Note: Students may wish to print out the review questions at the end and fill in
the answers as they read the document.
Copyright 2007 TAC Page 1 1/30/2007

I/A Series WorkPlace Tech Pre-Course Material
I/A Series Architecture
Internet
Remote Browser WorkPlace Pro

User Interface (Field Office)
BACnet Devices
Enterprise
BACnet
BACnet Systems
Systems
Server
Ethernet
UNC 510-2 UNC 610 UNC 610
WorkPlace Local Browser

Pro Interface
RS-232
RS-485
RS-485
MNL 50 MNB 1000

Plant Controller
RS-485
MNL 50
MNL 200 MPC MZ2

MNL 200
LON
GCM
LON
MNB 300
Unitary Controller MPC MF2
MNL VAV
MNL 800
Third Party
Device
MNB VAV
MNL =MicroNet LON MNB =MicroNet BACnet
Copyright 2007 - TAC Page 2 1/30/2007

Table of Contents
I/A Series Architecture ....................................................................................................2
Table of Contents ............................................................................................................3
I/A Series Hardware Products..........................................................................................5
MicroNet LonWorks Standard Controllers...................................................................5
Common Controller Features...................................................................................5
Universal Inputs ......................................................................................................6
MNL 50, 100,150, 200 Hardware Platforms ................................................................6
LONMARK Profiles.....................................................................................................7
MNL 110, 130 Hardware Platforms.............................................................................8
VAV Hardware Platforms ...........................................................................................8
Models With Integral Actuators...............................................................................9
Model Without An Integral Actuator .......................................................................9
Controller Firmware Revisions ..................................................................................10
Profile Version Numbers ....................................................................................... 11
MicroNet LonWorks MNL 800 Controller ................................................................12
MicroNet Digital Wall Sensors..................................................................................13
Common Sensor Features ......................................................................................13
Sensor Models and Functions ................................................................................14
Diagnostic Functions of LCD Screen Models ........................................................15
WorkPlace Communications Adapters.......................................................................15
I/A Series BACnet Controllers...................................................................................16
MicroNet BACnet Plant Controller (MNB 1000) ................................................... 16
MicroNet BACnet Unitary Controller (MNB 300) .................................................17
MicroNet BACnet VAV Controllers (MNB V1 and MNB V2) .............................. 18
I/A Series Universal Network Controllers.................................................................. 19
UNC 410 ............................................................................................................... 19
UNC 510 ............................................................................................................... 20
UNC 610 ............................................................................................................... 21
Enterprise Server ................................................................................................... 21
I/A Series Software Products.........................................................................................22
The WorkPlace Tech Tool.........................................................................................22
Application Creation and Modification .................................................................. 22
Online Diagnostics ................................................................................................ 23
Project Based Folders ............................................................................................24
MicroNet VAV Flow Balance Software..................................................................... 24
Third-Party LONWORKS Products........................................................................... 24
Network Management Tools......................................................................................24
LONWORKS Network Architecture .............................................................................25
WP Tech on an I/A Series LonWorks Network..........................................................25
Data Exchange....................................................................................................... 25
LONWORKS Topology and Wiring Guidelines ........................................................26
Free Topology Guidelines......................................................................................26
FTT Doubly-Terminated Bus Topology Segments .................................................27
FTT-10 Cabling Requirements ..................................................................................28

Guidelines on FTT Repeaters and Routers .............................................................29

Domain and Subnet Addresses...................................................................................29
Service Pin Methods..................................................................................................29
Service Pin vs. Wink Message ...............................................................................29
Communications Wiring............................................................................................30
Sensor Link (S-Link) Wiring ................................................................................. 30
MicroNet LONWORKS Network (LON) Wiring................................................... 30
I/O Wiring .............................................................................................................31
Power Supply Wiring ............................................................................................34
WorkPlace Tech Pre-Course Review .............................................................................36

I/A Series Hardware Products

I/A Series hardware products include controllers, digital sensors, and WorkPlace communication
(PC to LONTALK) adapter cards.
• I/A Series MicroNet LonWorks standard controllers provide direct digital control for fan coil,
heat pump, roof top unit, unit ventilator, and VAV applications. Nine basic controller platforms are
presently available; each has a number of I/O points and support for a digital room temperature or
temperature and humidity sensor (I/A Series MicroNet sensor). Each controller contains a
LONMARK HVAC Functional Profile that defines its “network image”.
• I/A Series MNL 800 controllers feature more I/O points than I/A Series MicroNet Lon standard
controllers, and use a programmable LONWORKS profile. The MNL 800 has an integral real time
clock (RTC) and also supports an I/A Series MicroNet sensor.
• I/A Series MicroNet sensors are digital sensors specifically for use with I/A Series MicroNet
LonWorks controllers. Twelve different models offer temperature only or temperature and
humidity sensing with varying levels of push buttons and LCD screens.
• WorkPlace Communication Adapters are Echelon LONTALK PC adapter cards with integral FTT-
10 transceivers. A PC running WP Tech requires an adapter to communicate with I/A Series
MicroNet Lon controllers.
MicroNet LonWorks Standard Controllers

There are nine hardware platforms for I/A Series MicroNet LonWorks standard controllers. Six
platforms (MNL 50, 100, 110, 130, 150, and 200) are for control of packaged rooftops, heat
pumps, fan coils, and similar unitary applications. Three platforms (V1R, V2R, and V3R) are
variable air volume (VAV) models.
Common Controller Features

All standard LonMark controller platforms differ by physical characteristics and numbers and
types of I/O points, but each controller platform provides these features:
• 24Vac powered.
• Standalone control capability.
• Support for a digital MicroNet sensor via a Sensor Link (S-LK) bus.
• LONMARK compliance, each having a LONMARK HVAC Profile.
• Onboard LONWORKS FTT-10 transceiver.
• Onboard LON Service LED, Receive and Transmit Data LEDs, and Service Pin Button.
• Onboard Neuron chip. The Neuron chip is the core hardware to all LonWorks devices. The
unique Neuron ID for each controller is built into the Neuron chip.
• Analog outputs are 0-20 milliamp and Digital Outputs are relays (except where noted.)

Model Number Code

The model number for any MicroNet LonWorks standard controller is coded with the following
information:
Universal Inputs
The universal input characteristics are software-configured to respond to one of the five input
types listed in Table–1.1.
MNL 50, 100,150, 200 Hardware Platforms

The MNL 50 series is the smallest platform and has the fewest I/O points. An MNL 50 controller
can be panel mounted and has connections for power, communications, and I/O wiring on two
terminal blocks. Refer to Table–1.2 below for the I/O points provided by the MNL 50.

The MNL 100, 150, and 200 hardware platforms feature a detachable subbase with screw
terminals for wiring, and can be DIN rail or panel mounted. The electronics/cover assembly plugs
into the wiring subbase. The controller cover has three status LEDs plus two hinged-flaps for
accessing field wiring. Controllers provide a built-in LON Jack to allow local PC access to the
LON. All three controller platforms have the same physical size and appearance, however, the
MNL 100 platform has the fewest I/O points and the MNL 200 platform the most I/O points. The
analog outputs are 0 to 20 mAmp current outputs, which can be converted to 0 to 10 Vdc with a
500 Ohm resistor. Refer to the table below.
LONMARK Profiles
Each of the four controller platforms is available in models that differ by LONMARK profile, which is
programmed at the time of manufacture. The profile is in read-only-memory and cannot be
erased or changed. A profile is not a pre-programmed application. A profile is actually a pre-
determined list of SNVTs – Standard Network Variable Types.
The following LONMARK profile types (and corresponding model numbers) for MNL 50, 100, 150,
and 200 are available:
Note: “Satellite” profile controller models are similar to those with Roof Top Unit profiles, but
include a more flexible assortment of network variables for use in general-purpose types of
applications.

MNL 110, 130 Hardware Platforms
The MNL 110 and MNL 130 Fan Coil Controllers with High Voltage Relays are provided with the
LONMARK Fan Coil Unit functional profile (8020). They are programmed using the WP Tech to
provide control for fan coil applications.
The MNL 110 and 130 can be either DIN rail or panel mounted, and have terminal blocks for
connections to power, communications, and I/O wiring. The MNL 110 and 130 feature 3 amp
maximum 240 Vac relays making them especially suited for the fan coil application. The two
models differ by the number of relays. Refer to Table–1.5. In addition, a built-in LON jack allows
local PC access to the LON. Status indication is provided by three LEDs that can be viewed with
the cover in place.
VAV Hardware Platforms

There are three different models of I/A Series MicroNet Lon VAV controllers. All models have the
LONMARK VAV Controller functional profile. Each model also has a built-in differential pressure
transducer for measurement of velocity pressure (airflow) at a VAV terminal box, plus some
additional points of I/O on field wiring terminal blocks. Status indication is provided by three LEDs

Models With Integral Actuators

Two VAV controller models have an integral actuator for over-the-shaft mounting on a damper of
a VAV terminal box. The actuator tightens on a damper shaft using set screws, and a manual
override button allows physical repositioning. Both of these controller models use the same
physical package, but vary in numbers of I/O points Table–1.7.
Model Without An Integral Actuator

The MNL-V3RVx series VAV controller has no integral damper actuator and so is physically
smaller. This controller has two triac outputs for use with an external actuator, plus additional I/O
points. The total number of I/O points is shown below Table–1.8.

Controller Firmware Revisions

The MicroNet LonWorks standard controllers come with Revision 4.X (Rev.4.X) firmware. The
MNL 800 controller comes with Revision 1.X (Rev.1.X) firmware (or higher).
Identifying pre-Rev.3 Models

These controllers have pre-Rev.3 firmware:
• MNL-10Rx1 and MNL-20Rx1, where “x” denotes profile type (F, H, R)
• MNL-V1RV1, MNL-V2RV1, MNL-V3RV1
Identifying Rev.3.X Models
The following controller models contain Rev.3 or higher firmware:
• Where xx is F2, R2, H2, S1, or S2:
– MNL-5Rxx
– MNL-10Rxx
– MNL-15Rxx
– MNL-20Rxx
– MNL-11RF2
– MNL-13RF2
– MNL-V1RV2
– MNL-V2RV2
– MNL-V3RV2
Identifying Rev.4.X Models
The following controller models contain Rev.4.1 or higher firmware:
• Where xx is F3, R3, H3, S3 or S4:
– MNL-5Rxx
– MNL-10Rxx
– MNL-15Rxx
– MNL-20Rxx
– MNL-11RF3
– MNL-13RF3
– MNL-V1RV3
– MNL-V2RV3
– MNL-V3RV3
Standard Standard
WorkPlace Controllers MNL-110 MNL-130 MNB
MNL-800 Controllers
Tech with Rev 2.0
Controller
Controller Controller
with Rev. 4.1
BACnet
Version or 3.x s s Controllers
Firmware Firmware
WPT 3.0 Yes No No No No No
WPT 3.1 Yes Yes No No No No
WPT 3.2 Yes Yes Yes No No No
WPT 3.2
Service Yes Yes Yes Yes No No
Pack 1
WPT 4.0 Yes Yes Yes Yes Yes No
WPT 5.x Yes Yes Yes Yes Yes Yes

Profile Version Numbers

MicroNet LonWorks MNL 800 Controller
The MicroNet MNL 800 controller differs from the MicroNet LonWorks standard controller models
by having a “programmable” LONWORKS profile, versus a fixed LONMARK profile, and by offering
more I/O points. This controller features an onboard, capacitor-backed Real Time Clock (RTC)
and provides additional capacities and features for more control functions.
The MNL 800 features the following:

• LONWORKS-compatible applications are completely programmable.
• A backed-up time clock provides true stand-alone direct digital control with optimum start stop,
scheduling functions, and backed-up RAM.
• Programmable point history log (auto trending) with adjustable sample rates, continually
accumulating log data, and a time stamp of the last 48 analog values or digital changes of state.
• One Universal Input (UI1) may be used for high speed pulse counting. Maximum pulse count
rate is 10 per second with 50% duty cycle. All other UIs can be configured as DIs or for pulse
counting with a maximum pulse rate of 1 per second with a 50% duty cycle.
• Functions as part of a LONWORKS FTT-10 Free Topology network.
• Support for one digital MicroNet sensor via the Sensor Link (S-LK) bus.
• LED indication of communications, service pin, LON jack.

• Controller card can be installed in either a wall-mount enclosure or a panel-mount enclosure.

The controller card can also be plugged directly into an existing MicroZone II controller sub-base
for upgrade to a LON.
• Eight universal inputs and eight pilot duty digital outputs
MicroNet Digital Wall Sensors

Any I/A Series LONMARK MicroNet controller supports a single digital wall temperature sensor.
Twelve models are available with features ranging from temperature sensing only with no control
or display to temperature and humidity sensing with a seven button control panel and LCD
display.
Common Sensor Features

An MN-Sxx sensor communicates with (and is powered) by two S-Link (S-LK) terminals on a
MicroNet controller — it does not consume a typical I/O point. This connection between the
sensor and controller can use low-cost twisted-pair wire up to 200 ft. (61 m), and is not polarity
sensitive. All MN-Sxx sensor models include a LON Jack to support an optional (and additional)
twisted-pair connection to the LON. The LON Jack is compatible with the plug-in cable included
with any of the three WorkPlace Communication Adapters (Echelon LONTALK PC adapters); TAC
models WPA-LON-1, WPA-LON-2, and WPA-LON-3. Under the sensor’s detachable cover, each
MN sensor model includes a pre-wirable baseplate and a removable electronic assembly Figure-
1.8. The same baseplate is used for each MN sensor model.

Note: MN Sensors have no independent intelligence. This means any MN sensor’s 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.
Sensor Models and Functions

Table–1.13 shows the features available with each model of I/A Series

Diagnostic Functions of LCD Screen Models

MN-S3xx, S4xx, S4xx-FCS, and S5xx sensors provide access to additional diagnostic data from
a sensor-user keypad request. This Diagnostic Mode data is displayed on the LCD screens of
these sensors, and includes separate displays (frames) for the MicroNet controller’s:
• Subnet and Node Address
• Errors
• Alarms (see following Note)
• Temperature Offset
• Relative Humidity Offset
Note: Alarm frames allow viewing of the last four alarms in the MicroNet Lon controller’s local
alarm buffer. These alarms correspond to Message ID numbers assigned in one or more control
objects in the MicroNet controller. With the exception of the Temperature and Relative Humidity
Offsets, Diagnostic Mode data is view only. The offsets are adjustable and apply only to the
integral temperature and relative humidity sensors in the MN sensor.
WorkPlace Communications Adapters

There are three models of WorkPlace Communications Adapters:
• WPA-LON-1 - An ISA adapter card for use in a desktop style PC.
• WPA-LON-2 - A Type II PC Card (formerly PCMCIA) for use in a notebook or laptop style PC.
• WPA-LON-3 - A PCI adapter card for use in a desktop style PC.
Common Adapter Features

These adapters are Echelon-manufactured LONTALK PC adapter cards that feature:
• An integral FTT-10 transceiver.
• Plug-and-play capability with Microsoft Windows 2000/XP. (No jumpers or switches.)
• A special 6 ft. (1.83 m) cable for plug-in connection to a built-in LON Jack featured on MNL
100, 110, 130, 150, 200, and 800 controllers and all I/A Series MicroNet sensors.
• Compatibility with software drivers included with WP Tech.
WPA-LON-1
The WPA-LON-1 is Echelon’s model PCLTA-10 PC LONTALK Adapter. This is a half-length, half-
height card that requires an available 16-bit ISA slot in a PC for installation. The adapter has a
removable two-position connector plug that can be terminated to the included 6 ft. LON Jack
(TAC) cable, or instead wired to any point on an FTT-10 based LON.
WPA-LON-2
The WPA-LON-2 is Echelon’s model PCC-10 PC Card. This is a Type II PC Card used in a
notebook computer. The card has a special 15-pin Hirose connector for the network port. An
included 6 ft. LON Jack (TAC) cable connects this PCC-10 port to a built-in LON Jack featured on
MNL 100, 110, 130, 150, 200, and 800 controllers and all I/A Series MicroNet sensors.
ECH-74501
The ECH-74501 is designed for installation in an available 32-bit PCI slot in a PC.

I/A Series BACnet Controllers
Presently there are three I/A Series BACnet Controllers: the Plant Controller (MNB 1000), the
Unitary Controller (MNB 300), and the BACnet VAV controllers (MNB V1 and MNB V2). All
MicroNet BACnet Controllers are programmed using WorkPlace Tech 5.0.
MicroNet BACnet Plant Controller (MNB 1000)
The I/A Series MicroNet BACnet Plant Controller is an interoperable controller with native BACnet
and MS/TP (Master Slave / Token Passing) communications support. The controller features
Sensor Link (S-Link) support, two Ethernet ports and 32 physical I/O points. The MicroNet
BACnet Plant Controller can function either in a standalone mode or as part of a BACnet building
automation system (BAS) network.
Features of the I/A Series MicroNet BACnet Plant Controller include:

 Integral MS/TP jack for direct connection to a PC with WorkPlace Tech 5.0.
 DIP switch addressable
 Optional plenum-rated enclosure
 Service pin button for BACnet “I am” message broadcast
 Isolated RS-485 transceiver for MS/TP communications
 LED indication of MS/TP and Ethernet IP communications activity, controller status, DO
state and UO state
 Firmware upgradable over the network
 72 hour battery backed real time clock
The 32 physical I/O points of the MicroNet BACnet Plant Controller consists of:
 12 Universal Inputs
 4 Digital Inputs (Dry Switched Contact)
 8 Universal Outputs
 8 Digital Outputs (Triacs)
Input Types for I/A Series BACnet Controller Universal Inputs include:
 10K Ohm Thermistor with 11KΩ Shunt Resistor
 1K Ohm Balco Sensor
 1K Ohm Platinum Sensor
 1K Ohm Resistive
 10K Ohm Resistive
 Analog Voltage (0 to 5 Vdc.)
 Analog Current (0 to 20 mAmp)
 Digital (dry contact)

Output Types for I/A Series BACnet Controller Universal Outputs include:
 0 to 20 mAmp
 0 to 10 Volts
The MicroNet I/A Series BACnet Plant Controller incorporates and isolated RS-485 transceiver
for BACnet MS/TP communications. Up to 127 devices can be connected to an MS/TP subnet
without repeaters.
MicroNet BACnet Unitary Controller (MNB 300)
The I/A Series MicroNet BACnet Unitary Controller is an interoperable controller with native
BACnet MS/TP (Master Slave / Token Passing) communications support. The controller features
Sensor Link (S-Link) support, a panel mount sub-base with removable electronics module and 15
physical I/O points. The MicroNet BACnet Unitary Controller can function either in a standalone
mode or as part of a BACnet building automation system (BAS) network.
Features of the I/A Series MicroNet BACnet Unitary Controller include:

 Optional plenum-rated enclosure
 Removable terminals for power and communications to facilitate commissioning
 LED indication of MS/TP communications activity, controller status, DO and UO state
The 15 physical I/O points of the MicroNet BACnet Unitary Controller consist of:
 6 Universal Inputs
 3 Universal Outputs
 6 Digital Outputs (Triacs)
The Universal Inputs and Outputs of the Unitary Controller can be configured as the same types
as the Plant Controller.

MicroNet BACnet VAV Controllers (MNB V1 and MNB V2)
The I/A Series MicroNet BACnet VAV Controllers are interoperable controllers with native BACnet
MS/TP (Master Slave / Token Passing) communications support. All models incorporate an
integral actuator with manual override and an integral pressure transducer. The controllers
feature Sensor Link (S-Link) support and over-the-shaft damper mounting. The MicroNet BACnet
VAV Controllers can function either in a standalone mode or as part of a BACnet building
automation system (BAS) network.
Features of the I/A Series MicroNet BACnet VAV Controllers include:

 Plenum-rated enclosure
 LED indication of MS/TP communications activity and controller status
 Damper position feedback to the BAS via an integral hall effect sensor
 Stable flow control down to 0.004 in. W.C. differential pressure
The table below shows the physical I/O for the two different models of I/A Series BACnet VAV
Controllers.
Inputs and Outputs
Model Description UI UO DO (Triac)
MNB-V1 Cooling Only 3
MNB-V2 Deluxe 3 1 3
The Universal Inputs and Outputs of the Unitary Controller can be configured as the same types
as the Plant Controller and Unitary Controllers.

I/A Series Universal Network Controllers

This section discusses the architecture of I/A Series devices – the UNCs (Universal Network
Controllers) and the Enterprise Server plus specifications on each of the hardware types.
UNC 410
The standard features of a UNC 410 include:

 Motorola RISC processor @ 250 MHz.
 Wind River VxWorks operating system
 64 MB RAM
 32 MB flash memory for operating system and database backup
 Battery backup for O/S, database and real-time clock Input voltage 120 Vac
 Metal enclosure
 Web UI (Browser) support
 One RJ-45 10/100 Mb Ethernet port
 One RJ-45 RS-232 port (Can be used for an optional external modem)
 One RS-485 Port
 One FTT-10 Lon Port
Only LON and BACnet are supported in the UNC 410.

Note: There is a limit on the number of Network Connected Devices with a UNC 410. The UNC
410 allows a maximum of 27 connected BACnet or LON devices.
The UNC 410 is the only UNC that has built-in physical I/O:
 6 Universal Inputs that can be Thermistor, 4-20 mAmp, 0-10 Volt, or dry contact digital
inputs.
 4 Digital Outputs - 24 Volt Relays with LED indication.The only option available for a UNC
410 is an internal modem.

UNC 520
The standard features of a UNC 520 include:

 Motorola RISC processor @ 250 MHz.
 Wind River VxWorks operating system
 128 MB RAM
 32 MB Flash for operating system and database backup
 Battery Backup for O/S, database and real-time clock Input voltage is 120 Vac.
Options available for a UNC 520 include Web Browser (Web UI) support, which allows graphics
within the UNC to be served up as web pages and an internal modem.
UNC 520 Ports:

 2 RS-232 Ports
 4 electrically Isolated RS-485 Ports.
 1 LON Port
 1 Ethernet Port
The UNC 520 is the only model of UNC that will communicate with BACnet MS/TP (Master Slave
Token Passing) devices on its RS-485 ports. Note: The obsolete UNC 510-2 can also support
BACnet MS/TP devices on its RS-485 ports.

UNC 610
The UNC 610 is now obsolete. The UNC 610 is an industrial packaged PC controller with a 1.2
Ghz. Celeron processor.
The standard features of the UNC 610 are:

 256 MB RAM
 20 gigabyte hard drive
 Embedded Windows XP
 10/100 Mb Ethernet adapter with RJ-45 connector
 Two RS-232 9-Pin connectors
 Hardware included: rubber feet for desktop mounting or brackets for cabinet mounting.
 Power cord for 120Vac or other line voltagesOptions available for the UNC 610 include:
 Web Browser support for graphics access
 RAM Memory Upgrade from 256 MB to 512 MB
 Database Service for archiving logs and alarms to the UNC 610Full version of Windows
XP
Enterprise Server
The Enterprise Server is the network server for all connected UNCs. The Enterprise Server
provides access to alarms, logs, graphics and schedules via a web browser. The WorkPlace Pro
engineering tool is included with the Enterprise Server. An Enterprise Server is required
whenever a site has two or more UNCs. The license for the Server is based on the number of
UNCs that are connected to it.
The Enterprise Server has the Alarm Console built in. The Alarm Console allows for reporting
and acknowledging alarms and alerts generated within a UNC or the Server. Also built into the
Enterprise Server is the Admin Tool. The Admin Tool allows the programmer to start and stop
stations (databases), import and export databases, and upgrade existing UNCs over the network.
When the Enterprise Server software is first loaded, a sample database called “DemoR2” is
included. After installation, a 14-day temporary license allows the programmer to use WorkPlace
Pro, but not communicate to UNCs. The programmer will complete his server license request
form and send it into the factory to receive his permanent license.

I/A Series Software Products
The WorkPlace Tech Tool

The WorkPlace Tech Tool (WP Tech) is the PC-based software tool used to program, compile,
download, and upload and redraw a control application. WP Tech works with I/A Series MicroNet
Controllers. WP Tech 4.0 is designed for use with Windows® 2000 Professional or Windows XP
and Microsoft Visio® 2002. Note: WP Tech 4.0 is not designed for use on with any other operating
system, including Windows 98 or Windows NT®. An application represents all the control logic in
a controller. WP Tech uses a Visio™ 32-bit drawing interface to represent each application as a
control logic drawing, using unique shapes for control objects and tags. Control objects are
copied from stencils as needed, and have built-in “connection wires” that define the logic and flow
of data in an application.
Application Creation and Modification

Application creation and modification is done offline, with each application based on a WP Tech
(Visio) template. As each controller is fully programmable, fully custom control applications are
possible. Alternately, a “pre-engineered” application can be used.
Pre-engineered Applications
A library of pre-engineered applications is available on the I/A Series Application CD for WP Tech
4.0. This CD may be obtained on request after contacting the Technical Services Group in the
TAC Customer Care Center. Note that these same pre-engineered applications are also available
for download on the http://source.tac.com/ website, in a “zipped” format. Download access is
password-protected.

Custom Application Overview

A “custom” application template provides a “blank” control logic page plus all of the control object
stencils. The target MicroNet controller and sensor must be identified by running the Hardware
Wizard. After the desired control objects are copied onto the drawing and connected as needed,
the application can be compiled and downloaded into a MicroNet controller. In this way, a custom
application can be built “from scratch.”
Application Upload
WorkPlace Tech 4.0 can upload application code from a controller and generate a Visio drawing
from the uploaded information. This is very useful if an original drawing is lost or you must
reverse engineer an application from an installed controller.
Applications that were created using WorkPlace Tech 4.0 include object positioning information
from the original Visio drawings. WorkPlace Tech 4.0 uses this uploaded information to create
drawings that are logically identical and very similar in appearance to the original drawings.
Applications that were created with WorkPlace Tech 3.2 or earlier do not include the original
object positioning information. WorkPlace Tech 4.0 uses this uploaded information to create
drawings that are logically identical to the original drawings. However, the appearance of the
uploaded drawing will likely be very different than that of the original drawing.
Online Diagnostics
In addition to the download function, WP Tech provides an online “Connect” function that allows
viewing of real-time data directly on an application’s control logic drawing. The application must
first be downloaded into a selected I/A Series MicroNet controller.
Realtime data is received by moving “Monitor tag” shapes onto the drawing and attaching them to
outputs of objects and tags. When “Connected” to an I/A Series MicroNet controller, values in the
monitor tags update. Monitor tags are for de-bugging and not intended for extended real time
monitoring.
Note: Connected (active) monitor tag values are polled, causing additional network traffic. Be
sure to disconnect (de-activate) monitor tags to relieve network traffic burden.
Diagnostic Writes
Fixed values to control objects can be temporarily modified when connected to a controller, using
a “Write to RAM” function. This allows quick changes to constant values when diagnosing an
application online. Temporary values are cleared after resetting the controller or after
downloading a database to the controller. A separate but similar function is available to write or
read values in configuration properties of the profile, which are called Network Configuration
Inputs (NCIs). Any change to an NCI is permanently retained until it is changed again.

Project Based Folders

In WP Tech, all work is done in a project. A project is a folder that contains one or more
applications. Usually, a project is assigned the job’s name and the applications are assigned
names to indicate which controllers they represent. Each time WP Tech is started, a Projects
Dialog Box lists all projects saved in the default Projects directory. For best organization, it is
highly recommended that all projects be kept in the default Projects directory.
Note: It is easier to organize and maintain multiple small projects rather than a single large
project.
MicroNet VAV Flow Balance Software

The MicroNet Flow Balance software is used to air balance terminal boxes controlled by I/A
Series MicroNet VAV controllers. The MicroNet Lon VAV controllers are interoperable, LONMARK-
compliant devices that provide a wide range of control strategies for pressure independent
terminal boxes with, or without, reheat capabilities.
Third-Party LONWORKS Products

Manufacturers other than TAC are also producing LONWORKS-based hardware and software.
Typical hardware devices include special-purpose controllers, discrete I/O modules, sensors, and
transducers. For the most part, these devices perform a fixed function and can be configured (but
not programmed). Any required configuration is achieved by accessing configuration properties
and network variables of the LONMARK objects or profile using a network management tool.
Third-party LONWORKS-based software programs are in two major categories:
• Network Management Tools
• User Interface Tools
Of the two, a network management tool is the most essential when installing a job with networked
nodes, as it is needed for the logical configuration of any LONWORKS network (LON).
Network Management Tools

A network management tool is required to assign logical addresses to networked LONWORKS
nodes (including I/A Series MicroNet LonWorks controllers) and to make any subsequent
“bindings” between network variables among the nodes. It can also be used to modify external
configuration parameters of a node. I/A Series WorkPlace Pro™ provides a comprehensive set
of engineering tools combined into one common easy to use graphical-based engineering
environment. WorkPlace Pro includes a network management tool for LONWORKS based
devices including node installation, network variable bindings, and automatic network “learning.”
When MicroNet LonWorks I/A Series controllers are used on an I/A Series Niagara Web-
accessed system, WorkPlace Tech Tool can operate at a remote location by use of the Virtual
LON (VLON) service. A computer operating with WorkPlace Tech Tool and VLON can provide full
access to a MicroNet Lon I/A controller at a different location via an Ethernet connection and an
I/A Series Universal Network Controller at the remote location. Two network management tools
are Echelon’s LONMAKER® for Windows and IEC’s ICELAN 2000™. Both programs present a
graphical representation of a LON network. Functions are included for node installation, network
variable binding, and network variable browsing.

LONWORKS Network Architecture
WP Tech on an I/A Series LonWorks Network

WP Tech communicates with all I/A Series devices, using a LONWORKS FTT-10 Free Topology
communications network. LONWORKS is a peer-to-peer communications architecture that allows
the direct sharing of data between networked I/A Series MicroNet LonWorks controllers, and this
communication is not affected by the use of routers in the network. A LONWORKS network has a
communications speed of 78k baud, using unshielded, twisted-pair cabling, with connections that
are not polarity sensitive.
Data Exchange
Data exchange is performed through the use of network variables (NVs), which are defined by a
set of Standard Network Variable Types (SNVTs). Using network variables, MicroNet LonWorks
controllers can also exchange data directly with other manufacturers’ LONWORKS controllers,
providing a high level of interoperability. This chapter describes the network variables available in
I/A Series MicroNet Lon standard controllers and MNL 800 controllers. Network variables in I/A
Series MicroNet LonWorks controllers fall into three general classes:
• NCIs (Network Configuration Inputs)
• NVIs (Network Variable Inputs)
• NVOs (Network Variable Outputs)
Conceptually, NVs are “data slots,” defining the controller’s “network image.” In any I/A Series
MicroNet Lon controller, the collection of these three types of network variables defines the
controller’s “network profile.” In a MicroNet Lon controller, control objects and other resources
(sensor tags, schedule tags) can be connected to these data slots to allow sharing of data and
control over a LONWORKS network. Data is exchanged between NVIs and NVOs in different
devices using peer-to-peer “bindings.” Note that the actual engineering of bindings requires a
LONWORKS network management tool such as LONMAKER for Windows.

LONWORKS Topology and Wiring Guidelines

Topology defines the physical layout (architecture) used in the design of the network wiring.
Wiring guidelines include details on approved cable types, allowable distances, and termination
details. MicroNet LONWORKS networks are FTT-10 (FTT) based networks; each device has an
Echelon-designed Free Topology Transceiver for connection to a wiring “segment”. Category 4,
twisted-pair cable (two conductors) is required for all FTT segment wiring. The LONWORKS
communication connections are not polarity sensitive. The communication speed is 78.1 Kbps.
Two possible topologies exist for a LONWORKS FTT segment:

• Free Topology (singly-terminated bus, unlimited wiring tees, stars, and even “loops”).
• Doubly-Terminated Bus (device-to-device, daisy-chain bus only).
Free Topology is used in most FTT segments due to its flexibility when wiring and making
changes and additions, although wiring segment lengths are less than when using the Bus
topology.
LONWORKS Terms
Because LONWORKS is not proprietary to IBS, these common terms are often used when
explaining MicroNet LONWORKS networks:
Node - any addressable device on the network, including any MNL controller or third-party
LONWORKS device.
Segment - each MicroNet LONWORKS network has at least one wiring segment, the length of
which is limited by the topology used (Free Topology or Bus). If more wiring is required, a
LONWORKS FTT repeater must be installed, which adds one (or more) new wiring segments.
Wiring segments are sometimes called channels.
Subnet - a logical group of devices on the network; subnet is part of a node’s complete address,
namely: Domain, Subnet, and Node Address. If required, a subnet can span multiple segments
joined by repeater(s). The standard LONWORKS node limit of a subnet is 127 nodes.
FTT Repeater - an active (powered) device that receives LONTALK messages on any attached
FTT segment and rebroadcasts them to all other attached FTT segments. Some FTT repeaters
allow connection of more than two FTT segments (channels).
Free Topology Guidelines

• In addition to the limit of 1641 feet (500m) of total wire in a Free Topology segment, the wiring
path between the two most distant nodes cannot exceed 1312 feet (400m).
• The optional FTT (LON) wiring to the MN-Sx sensor can connect to the most convenient or
closest point on the wiring segment, as shown in Figure–13. MN-Sx sensors do not count as
nodes.

End-of-Line Termination
In Free Topology, multiple “end of lines” exist, and so a single terminator consisting of a special
RC circuit (LON-TERM1) is placed anywhere on the FTT segment (Figure–13). The terminator
can connect to any device or wiring junction on the segment.
FTT Doubly-Terminated Bus Topology Segments

A Doubly-Terminated Bus segment requires daisy-chain connection of each device, with wiring
connections only on the devices themselves (no tee “stubs”). Longer lengths are possible using
this topology—up to a maximum segment length of 4593 feet (1400m) using the recommended
22 AWG (0.62mm) cabling.
Bus Topology Guidelines

• An FTT wiring segment is either Free Topology or Bus topology; a “proportional hybrid” is not
possible. This means that while most of an FTT segment might be daisy-chained from device to
device, the first wiring “tee” makes the entire segment Free Topology, and therefore subject to the
1641 feet (500m) total wiring length limitation (and different end-of-line termination).
• The optional FTT (LON) wiring to (and from) an MN-Sx sensor must be daisy-chained. MN-Sx
sensors do not count as nodes.
End of Line Terminator

Two terminators consisting of a special RC circuit (LON-TERM2) are required, one installed at
each end of the FTT segment as shown in Figure–14. Each terminator connects directly to the
device at the end of the wiring bus.

MN-Sx to LONWORKS Network Wiring

Each MN-Sx digital wall sensor must be wired to a specific MN 100, 200, or VAV Series controller
using an S-Link (S-LK) wire pair. The S-LK connection powers and enables the sensor.
Optionally, an MN-Sx sensor can also be wired to the LONWORKS network using another wire
pair (LON), which permits use of the MN-Sx’s built-in “LON Jack”. An MN-Sx sensor is not a
“node”, however, all LONWORKS network (LON) wiring to the sensor becomes part of the FTT
wiring segment.
FTT-10 Cabling Requirements

Echelon-approved FTT-10 cable models are listed in Table–8. All cables listed are Category 4
types specifically for FTT-10 segment wiring. The recommended cables for most MicroNet
LONWORKS networks are the unshielded, plenum-rated, 22 AWG (0.65mm) models.
• Unshielded cable is easier to install and better suited to this application unless routed in an area
of high electrical noise. If shielded cable is used, the shield wire must run continuously throughout
the segment and be grounded through a 470K ohm, 1/4-watt resistor at one end only (any point if
a Free Topology segment).
• Plenum-rated cable is specified for most jobs and often is easier to obtain due to high demand.
Non-plenum cable is likely to be specified only where conduit is required, and so may be harder
to find.

• In general, 1-pair cables are recommended. An exception would be for extending the LON
connection in a daisy chain, such as when wiring the LON from a controller down to the sensor
and then back up to the controller again.
Guidelines on FTT Repeaters and Routers

LONWORKS FTT repeaters and routers are available from various vendors, which will allow
multiple network segments to be connected to form subnets of up to 127 nodes. A list of these
devices and suppliers can be found at the Echelon web site (http://www.echelon.com).
FTT Repeaters
FTT repeaters re-time and re-transmit all LONTALK packets among all connected wiring segments.
Normally, one repeater is used, but controllers can be tuned to allow the use of additional
repeaters if necessary. The number of repeaters used should be kept to a minimum (no more
than 2 or 3) to prevent message timing problems. FTT repeaters should not be used unless more
wiring is required, as operation is dependent on local power. Each FTT repeater port adds a new
wiring segment, which may be wired either as a Free Topology or as a Doubly Terminated Bus.
Terminating with Repeaters
FTT repeaters often include internal termination resistance, which may preclude the use of
external terminators (LON-TERM1 or LON-TERM2). Consult the FTT repeater product
documentation to determine how segment terminations are accomplished.
FTT Routers and Bridges
FTT routers and bridges provide intelligence that can help manage network traffic between
segments. Some models of LONWORKS routers and bridges allow a LONWORKS network to
use different media (and LONWORKS transceiver types, for example FTT-10 and TP/XF-78).
Domain and Subnet Addresses

In a LONWORKS network, each device has a hierarchical network address that includes a
Domain, Subnet, and Node address. A device must belong to two separate domains (zero-length
domain, and one other). The zero-length domain allows access from any LONWORKS network
management program. The other domain is a non-zero-length domain assigned by that program,
along with a subnet and node address.
Note: LNC-100s (when used) must be manually assigned a unique address that is compatible
with the rest of the network devices.
Service Pin Methods

You can initiate a Service Pin message from a MicroNet LonWorks device as frequently as
needed—it serves only as a method of device identification. It is a broadcast message from a
particular device. Use one of the following manners, depending on the device:
• For any MNL 100, 200, or VAV Series controller that has an MN-S2, S3, S4, or S5 sensor
attached, press and hold the override key of the sensor for a period of 8 seconds.
• Press the dedicated Service Pin pushbutton on the controller.
Service Pin vs. Wink Message

Do not confuse a Wink message with a Service Pin message.
• A Service Pin message is sent from a particular device. All devices on the LONWORKS network
receive it, but only the PC uses it. A Service Pin message identifies the sending device.
• A Wink message is typically sent to a particular device from the PC. Essentially, the Wink
message is asking a specific receiving device to acknowledge itself. A Wink message does not
interfere with the normal application control provided by a MicroNet LonWorks device—Wink
messages can be sent to nodes as frequently as needed

Communications Wiring
Caution:
• Communication wire pairs must be dedicated to MN-Sx (S-Link) and MicroNet LONWORKS
network (LON) communications. They cannot be part of an active, bundled telephone trunk.
• Shielded cable is not required for S-Link or LON wiring.
• If the cable is installed in areas of high RFI/EMI, the cable must be in conduit.
• If shielded wire is used, the shield must be connected to earth ground at one end only by a
470K ohm 1/4 watt resistor. Shield must be continuous from one end of the trunk to the other.
Communications wiring includes a connection between the controller and an I/A Series MicroNet
Sensor via the S-Link and a connection between the controller and the MicroNet LONWORKS
Network (LON). An optional LONWORKS Network connection between the controller and one I/A
Series MicroNet Sensor is also possible.
Sensor Link (S-Link) Wiring

S-Link wiring powers and enables the MN-Sx sensor. The S-Link needs at least 24 gage
(0.51mm), twisted pair, voice grade telephone wire. The capacitance between conductors cannot
be more than 32 pF per foot (0.3m). If shielded cable is used, the capacitance between any one
conductor and the others, connected to the shield, cannot be more than60 pF per foot (0.3m).
Maximum wire length is 200 ft. (61m).
Note:
• Controller supports one I/A Series MicroNet Sensor (MN-Sx).
• S-Link wiring is polarity insensitive.
• If conduit is used between an I/A Series Sensor and a controller, the MicroNet LONWORKS
network and S-Link wiring can be in the same conduit, however, they must be separate cables.
• S-Link wiring can be in the same conduit with UI, AO, and DI Wiring.
• The S-Link does not count as a node on the Lon.
MicroNet LONWORKS Network (LON) Wiring

An approved Category 4 or 5, twisted-pair (two conductors) cable may be used for both
connecting to the MicroNet LONWORKS Network and the optional LONWORKS Network
connection between the controller and MN-Sx sensor. LONWORKS Network wiring is polarity
insensitive.
Caution: Do not mix with UI, AO, DI or DO types of wiring. If conduit is used between an I/A
Series Sensor and a controller, LONWORKS Network wiring and S-Link wiring can be in the
same conduit, however, they must be separate cables.
MNL 100, MNL 150, and MNL 200 controllers use LONWORKS Free Topology Transceiver
(FT3150) and support polarity insensitive bus (daisy-chain) and free (all combinations of star, tee,
and loop) wiring topologies. A maximum of 62 nodes can be connected per segment.
• Use of the LON terminals to connect to the MN-Sx sensor permits use of the sensor’s built-in
LON Jack.
• To preserve the integrity of the network, the LON wiring connecting an I/A Series MicroNet
LonWorks controller to an MN-Sx sensor must be run to the sensor and back, in daisy-chain
fashion. A wire “spur” must not be used to connect the sensor to the controller.
• While the MN-Sx sensor is not counted as a “node” in the LonWorks network (LON), all LON
wiring to the sensor must be counted when determining the length of the FTT wiring segment.

I/O Wiring
I/O connections include universal inputs, analog outputs, digital inputs, and digital outputs.
Caution: If shielded cable is used, connect only one end of the shield to earth ground at the
controller.
Universal Inputs (UI), Analog Outputs (AO), 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, AO, S-Link, LON, or DI wiring.
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, AO, DI, and S-Link wiring can share a single conduit. UI, AO, DI, wiring needs at least 24
gage (0.51mm), twisted pair, voice grade telephone wire.
The capacitance between conductors cannot be more than 32 pF per foot (0.3m). 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.3m). Table-1 provides wiring specifications.


Digital Outputs (DO)

Caution:
• DO terminals accept one 16-gage (1.29mm) wire or two 18 gage (1.02mm) wires. The selected
wire gage must be consistent with the load current rating.
• DO wiring cannot be intermixed with DI, UI, S-Link, LON and AO wiring.
• MNL 100, MNL 150, and MNL 200 controllers are Class 2 devices. Each digital output can
support up to 24 Vac/Vdc at 1.0 amp (24 VA) pilot duty.
Note: Digital Output wiring can be intermixed with class-2 power wiring. Each DO is an isolated
Form A (SPST) relay. If the transformer is sized correctly, the 24 Vac Class 2 Controller power
source (Figure-7) may be used for load power.

Power Supply Wiring

Caution:
• MicroNet LonWorks I/A Series 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.
• This product contains 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. Refer to EN-206, Guidelines for Powering Multiple Devices from a Common
Transformer, F-26363, for detailed information.
• Power wiring cannot be intermixed with LON, S-Link, UI, AO, or DI wiring.
• Use a Class 2 power transformer supplying a nominal 24 Vac (20.4 to 30 Vac) with a minimum
rating of 15 VA at 50/60 Hz plus digital output loads (144VA using 6 DOs or 96VA using 4 DOs if
same transformer is used). The supply to the transformer must be provided with a breaker or
disconnect. In European Community, transformer must conform to EN 60742.
• 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.
• 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).
Note:
• Power wiring terminals accept one 16 gage (1.29mm) or two 18 gage (1.02mm) 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 LON wiring connecting an I/A Series MicroNet
LonWorks controller to an MN-Sx sensor must be run to the sensor and back, in daisy chain
fashion. A wire “spur” must not be used to connect the sensor to the controller.
Figure-8 and Figure-9 are acceptable wiring configurations.


WorkPlace Tech Pre-Course Review

Name __________________________________________ Date ___________
Office __________________________________________
Answer the following questions before coming to class.
1. Complete the following I/O chart.

# of # of # of AOs # of Are the
DOs Relay
Controller DIs UIs or UOs DOs or Triac?
MNL 50
MNL 100
MNL 110
MNL 130
MNL 150
MNL 200
MNL 800
MNL V1
MNL V2
MNL V3
MNB 300
MNB 1000
MNB V1
MNB V2
UNC 410
2. What are the acceptable inputs for a UI for the MicroNet Lon controllers?
______________________________________________________________________
3. What is the range of the AOs for the MicroNet Lon controllers?
______________________________________________________________________
4. What power is required by all MicroNet controllers? _____________________
5. What is the core LonWorks hardware component found in every LonWorks device?
_______________________________

6. What does the abbreviation SNVT stand for?

______________________________________________________________________
7. Which model MNL VAV controller does not have a built-in damper actuator?
__________________________________
8. What LonMark Profiles are available for the MNL 100?
______________________________________________________________________
9. What LonMark Profiles are available for the MNL 800?
______________________________________________________________________
10. Fill in the blanks below based on the following model number: MNL-15RH2
a.) Controller _______________________
b.) Profile _______________________
c.) Profile Version _______________________
11. Which MicroNet controllers have a RTC (Real-Time Clock)?
______________________________________________________________________
12. Which MicroNet controllers contain scheduling capabilities?
______________________________________________________________________
13. Which MicroNet S-Series sensor has no buttons? _____________
14. Which MicroNet S-Series sensor has an emergency heat button? _____________
15. Which WorkPlace Communications Adapter is used on a notebook computer?
__________________________________
16. What tool is used to program all I/A Series MicroNet BACnet controllers?
_______________________________ _______________________________________
17. What is the purpose of the service pin button on the MicroNet BACnet controllers?
_______________________________ _______________________________________
18. How are the addresses of the MicroNet BACnet controllers set?
________________________________________
19. Which model UNC can communicate on its RS-485 ports with BACnet MS/TP
devices? _________________________________________
20. Which is the only model of UNC that has a hard drive? ________________
21. Which UNC models can communicate with LON devices? ____________________
22. What is the name of the network server for all connected UNCs?
______________________________________________________________________
23. WorkPlace Tech uses what drawing interface? ________________________

24. What is the general name for the software tool required for connecting SNVTs?
______________________________________________________
25. The process of connecting SNVTs for peer-to-peer communications on a LonWorks
network is called ______________________________________
26. Give an example of a network management tool.
______________________________________________________________
27. In an FTT-10 LonWorks Network what type of wiring is used and what is the nature
of the polarity? __________________________________________________________
28. In a Free-Topology LonWorks network segment:
a.) What is the part number for the terminator? ___________________________
b.) How many terminators are required? ____________
c.) What is the total wiring limitation? (22 gauge wire) ______________________
29. In a Bus-Topology LonWorks network segment:
a.) What is the part number for the terminator? _________________________
b.) How many terminators are required? ____________
c.) What is the total wiring limitation? (22 gauge wire) ______________________
30. What is the communication speed of the FTT-10 Transceiver? ____________ bps.
31. What is the difference between a wink message and a service pin message?
______________________________________________________________________
______________________________________________________________________
32. In a LonWorks network, each device has a hierarchical network address that
includes what 3 parts? _____________________________
_______________________________ _______________________________________
33. Does an S-Series sensor count as a node on the LON? ___________
34. True or False: DO wiring can be mixed with power wiring, but not with UI, AO, DI,
S-LK, or LON. _________________

I - A Series WorkPlace Tech Programming. Pre-Course Material

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I - A Series WorkPlace Tech Programming. Pre-Course Material

Uploaded by

Copyright:

Available Formats

I/A Series WorkPlace Tech

Each student should read this document before attending

Copyright 2007 TAC Page 1 1/30/2007

I/A Series Architecture

Remote Browser WorkPlace Pro

UNC 510-2 UNC 610 UNC 610

WorkPlace Local Browser

MNL 50 MNB 1000

MNL 200 MPC MZ2

Copyright 2007 - TAC Page 2 1/30/2007

Copyright 2007 - TAC Page 3 1/30/2007

Guidelines on FTT Repeaters and Routers .............................................................29

Copyright 2007 - TAC Page 4 1/30/2007

I/A Series Hardware Products

MicroNet LonWorks Standard Controllers

Common Controller Features

Copyright 2007 - TAC Page 5 1/30/2007

Model Number Code

MNL 50, 100,150, 200 Hardware Platforms

Copyright 2007 - TAC Page 6 1/30/2007

Copyright 2007 - TAC Page 7 1/30/2007

MNL 110, 130 Hardware Platforms

VAV Hardware Platforms

Copyright 2007 - TAC Page 8 1/30/2007

Models With Integral Actuators

Model Without An Integral Actuator

Copyright 2007 - TAC Page 9 1/30/2007

Controller Firmware Revisions

Identifying pre-Rev.3 Models

Copyright 2007 - TAC Page 10 1/30/2007

Profile Version Numbers

Copyright 2007 - TAC Page 11 1/30/2007

MicroNet LonWorks MNL 800 Controller

The MNL 800 features the following:

Copyright 2007 - TAC Page 12 1/30/2007

• Controller card can be installed in either a wall-mount enclosure or a panel-mount enclosure.

MicroNet Digital Wall Sensors

Common Sensor Features

Copyright 2007 - TAC Page 13 1/30/2007

Sensor Models and Functions

Copyright 2007 - TAC Page 14 1/30/2007

Diagnostic Functions of LCD Screen Models

WorkPlace Communications Adapters

Common Adapter Features

Copyright 2007 - TAC Page 15 1/30/2007

I/A Series BACnet Controllers

MicroNet BACnet Plant Controller (MNB 1000)

Features of the I/A Series MicroNet BACnet Plant Controller include:

Copyright 2007 - TAC Page 16 1/30/2007

MicroNet BACnet Unitary Controller (MNB 300)

Features of the I/A Series MicroNet BACnet Unitary Controller include:

Copyright 2007 - TAC Page 17 1/30/2007

MicroNet BACnet VAV Controllers (MNB V1 and MNB V2)

Features of the I/A Series MicroNet BACnet VAV Controllers include:

Copyright 2007 - TAC Page 18 1/30/2007

I/A Series Universal Network Controllers

The standard features of a UNC 410 include:

Only LON and BACnet are supported in the UNC 410.

Copyright 2007 - TAC Page 19 1/30/2007

The standard features of a UNC 520 include:

UNC 520 Ports:

Copyright 2007 - TAC Page 20 1/30/2007

The standard features of the UNC 610 are: