Documente Academic
Documente Profesional
Documente Cultură
Systems
Table of Contents
Introduction .......................................................................................................................1
Controller Basics...............................................................................................................2
NETWORK 8000.................................................................................................................4
DMS ..................................................................................................................................10
DMS Controllers..............................................................................................................10
Programming Software for DMS .....................................................................................11
Graphical User Interfaces ...............................................................................................11
Introduction
In 1987, Barber-Colman® Company of Rockford, Illinois introduced a family of DDC
controls called NETWORK 8000®. At nearly the same time, Robertshaw Company of
Richmond, Virginia developed a DDC system called DMS™ (Digital Management System).
By 1990 both Barber Colman Company and Robertshaw Company had been purchased by
Siebe, PLC of the United Kingdom. Robertshaw and Barber Colman merged to form Siebe
Environmental Controls® (SEC). In the mid-1990’s, Siebe Environmental Controls
developed a new family of DDC controls called the I/A (Intelligent Automation) Series™.
These controllers are called I/A Series® MicroNet™ controllers, and they were among the
first controllers to use LON® (Local Operating Network) technology. In 2005 BACnet
controllers were added to the I/A Series® MicroNet™ family. Invensys Building Systems
was purchased by Schneider Electric in 2006, and is now part of TAC.
This document explains the features and functions of the controllers in these DDC families,
along with descriptions of the Graphical User Interfaces (GUIs) used by each system. Not
every controller in each family is discussed.
Page 1
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Controller Basics
The basic control system is made up of a sensor, a controller and a controlled device.
A sensor sends a signal to the controller. The signal can be analog or digital. A sensor sends an
analog signal (input) if it modulates or varies, such as a temperature sensor. If a sensor produces
an on or an off signal it is a digital input, such as an airflow switch.
The controller is a microprocessor that reads signals from attached sensors, processes the signal
data and sends an output signal to an attached controlled device. A software control program
that runs in the controller accomplishes this process.
A controlled device receives a control signal from the controller. The signal can be analog or
digital. If the controlled device uses the signal to allow more or less flow of the controlling
medium, such as hot water or air, it is receiving an analog signal from the controller. If the
controlled device is a piece of equipment such as a pump or fan, it requires a digital signal from
the controller.
Temperature Supply
Air Flow Fan
(Static Pressure) Outside Air
Low Limit
Controller Dampers
(Freeze stat)
Chilled Water
Supply Pump
Smoke
Humidity Humidifier
Electric Heat
Page 2
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
There are essentially four types of I/O points – analog inputs (AIs), digital inputs (DIs), analog
outputs (AOs) and digital outputs (DOs). A common example of a physical device connected to
a controller as an AI is a temperature sensor. The sensor may vary its electrical resistance based
on the surrounding (ambient) temperature. A flow switch, sometimes called a “sail” switch, that
closes when airflow pushes against a sail, is an example of a DI. Switches are digital because
they are open or closed (two-position) and the sensor is an input because the signal comes into
the controller. Two common examples of AO type points would be a proportional valve or
damper. A voltage or current signal is sent from the controller to move the valve or damper to a
specific position. The point is analog because the position of the valve or damper could vary
anywhere from full-closed to full-open. A fan or pump that is turned ON or OFF by the
controller would be a DO.
Be careful when thinking about I/O point types. While turning a pump or fan ON or OFF is
done by a DO point, variable speed pumps and fans are controlled by AO points. While
proportional valves and dampers are controlled by AO points, two-position valves or dampers,
which are fully-open or fully-closed only, are controlled by DO points. DDC controllers are
typically described by the number of I/O points that they have available.
Another type of I/O point is called a Universal Point. Universal Points can be configured in
software to be an AI, an AO, a DI or DO. Universal Points make a controller very flexible
because they can provide a variety of configurations for different applications. However,
Universal Points are costly because each point must have the hardware for four different types.
Some controllers have Universal Inputs, which must be used for hardware inputs, but can be
either Analog Inputs or Digital Inputs.
Page 3
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
NETWORK 8000
The ASD Bus can have up to 7 MicroNet 2000™ Integrators, and connected to each integrator
can be up to 31 MicroNet 2000 controllers. MicroNet 2000 controllers come in two models: MN
FLO, which is used to control VAV boxes and MN HPFC, which is used to control heat pumps
or fan coil units. Although it is confusing, these MicroNet 2000 devices are in no way related to
the I/A Series MicroNet controllers that use LON technology, which are discussed later.
Page 4
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
There are three different types of communications between the GCMs in a NETWORK 8000
network – BC LAN™, Echelon® and Ethernet. BC LAN (Barber Colman Local Area Network)
is the oldest and slowest network communications. Ethernet is the newest and fastest. The
Echelon and Ethernet connections between GCMs are made with NIMs (Network Interface
Modules) that mount on the side of a GCM. Considering that a NETWORK 8000 network can
have up to 31 GCMs, and each GCM can have 31 LCMs and 128 ASD controllers connected to
it, the network can be very large, with thousands of controllers connected to tens-of-thousands of
I/O points
Ethernet or Echelon
GCM GCM
MZ I I NIM
NIM
PEM
Integrator
LCM
MicroNet 2000
VAV
Heat pump/
Fan coil
LCM Bus
MF I I
ASD Bus
Page 5
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
PSI™ (Personal System Interface) was the first software tool for programming devices found on
the ASD Bus, including the MICROZONE II, PEM, MICROFLO II, and the LIM.
Illustration of PSI
Page 6
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Another programming tool for NETWORK 8000 controllers was developed in the late1990’s
and is called Tree Tech™. Tree Tech, a Windows-based software package, was developed for
use with the InVue graphical user interface software. Tree Tech can be used as an alternative to
Terminal Mode and PSI.
Stonet Systems, a wholly owned subsidiary of the IFO Base Controls, has developed the
Eclypse™ software, also known as ProBlock™, in the late 1990’s. ProBlock is a windows-
based programming tool designed to update the look of Terminal Mode, as well as to add more
functions to increase the efficiency of creating and maintaining a controller database. ProBlock
can be used in place of Terminal Mode and PSI.
Page 7
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
HOST-8000™
The Host-8000 is a GUI that runs on the QNX® operating system and DOS® 3.1. Host-8000
uses icons to navigate the system. Due to the non-availability of QNX operating system, Host-
8000 is no longer available.
SIGNAL®
SIGNAL is a Windows based interface that can run in a Windows® 3.1, Windows 95, Windows
98 or Windows XP operating system. SIGNAL uses icons to navigate the system.
Illustration of Signal
ULTIVIST™
UltiVist uses a tree structure, and is the most powerful, flexible, and complex of the GUIs.
Because it is based on the OS/2® operating system, UltiVist is no longer available.
Page 8
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
INVUE™
The InVue graphical user interface is an application based on the Wonderware InTouch™
software. InVue was developed as part of the overall I/A Series® MicroNet system to
accompany the I/A controllers. InVue runs on a Windows NT or Windows 2000 operating
system.
Page 9
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
DMS
DMS Controllers
The area controller for the DMS system is a DMS 3500™. The local controllers in a DMS
system are called MicroSmart™ Controllers. There are different MicroSmart Controllers with
different arrangements of I/O points. The MicroSmart Controllers connect to the DMS 3500 via
two RS-485 buses, called MicroSmart Trunks. Up to 31 MicroSmart controllers can be
connected together on a single MicroSmart Trunk. The DMS 3500 area controllers are
connected via NIMs, (Network Interface Modules), using Ethernet or Echelon, very much like
GCMs in NETWORK 8000. Older versions of DMS area controllers include DMS 350A™ and
DMS 35™. The DMS 350A requires another device called the Distributed Control Module
(DCM) to communicate with the MicroSmart Controllers.
DMS ARCHITECTURE
Ethernet or Echelon
DMS-3500 NIM
DMS-3500 NIM
Page 10
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Illustration of OPRIF
Page 11
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
LonWorks is the name of the collective technology developed by the Echelon Corporation. It
refers to a networking communications system using LonWorks hardware and software
components that allows the direct sharing of data between devices. Echelon designed LonWorks
as a modular, “open architecture” system, providing a method for manufacturers to build devices
that can operate on an interoperable control network.
MicroNet Controllers
The I/A Series MicroNet LON and MicroNet BACnet controllers each have a defined I/O point
configuration. Refer to the table below:
Page 12
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
BACnet
Controllers
MNB-300 Detachable Subbase
(Unitary) 0 6 3 0 6
Universal Inputs include 0 to 5 Vdc, 0 to 20 mA, Balco, Platinum, 10K Thermistor with 11K shunt
(TS-87xx-850 series) or Digital Inputs.
In addition, an MNL-800 UI accepts Copper sensors and temperature sensors equipped with a
pushbutton switch (TS-90xxx series).
The MNL 50, MNL 100, MNL 150, MNL 200 and MNL VAV controllers are LonMark
compliant. This means they contain a fixed LonMark HVAC profile that facilitates the
communication between controllers. A profile contains a certain list of Standard Network
Variable Types (SNVTs). Using network management software, SNVTs are “bound” between
controllers to allow data sharing. Network variables in I/A Series MicroNet Controllers fall into
three general classes:
• NCIs (Network Configuration Inputs)
nciSetPnts
nvoSpaceTemp
Page 13
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
LONMARK®PROFILE
All I/A Series MicroNet LON controllers, except the MNL 800 Controller, have a specific
LonMark HVAC functional profile (Fan Coil, Roof Top, VAV), determined by its model. A
LonMark profile describes the general application purpose and the network image of a device. A
profile is made from a standardized set of SNVTs available to other LON devices. A controller
profile is set at the factory and held in read-only memory (ROM), and therefore a profile cannot
be erased or changed. There is no external difference among controller models containing the
same profile. For example, all of the MNL 200 model controllers look the same. However,
MNL 200 controller models can differ by LonMark profile.
The I/A MNL 800 Series Controller is a LonWorks controller with eight universal inputs, four
analog outputs, eight digital outputs, which is the exact same I/O configuration as a NETWORK
8000 MICROZONE II. The MNL 800 provides the same basic network variable functionality as
with the LonMark compliant MicroNet controllers; however, it does not contain a LonMark
profile. A programmer can choose which SNVTs he or she wishes to use with each MicroNet
800.
Page 14
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
The LNC provides an interface between a NETWORK 8000 or DMS system and LonWorks
network devices. Devices on the LonWorks network include the I/A Series MicroNet controllers
and third-party devices. The LNC is very similar to the NETWORK 8000 GCM area controller.
The main difference is the LNC has a connection for a LonWorks network (instead of the LCM
bus) and an ASD (Application Specific Device) bus. Like the GCM, the LNC is programmed
using Terminal Mode, Tree Tech or ProBlock. An LNC does not contain a LonMark profile.
Page 15
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Page 16
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
I/A Series Enterprise Server (software) is a network server for connected UNCs. The I/A
Enterprise Server software runs on a PC with the Windows 2000 or NT operating system. I/A
Enterprise Server functions include processing alarms and logs, plus making graphics available
to Internet browsers.
Page 17
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
WorkPlace Pro (software) is a graphical engineering tool. It is used to create the database that
includes control logic and graphics for UNC controllers and the I/A Enterprise Server.
Page 18
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Internet
Remote Browser
User Interface
BACnet Devices
Enterprise
BACnet Systems
Server
Ethernet
UNC-500
or UNC-600 UNC-600
UNC-510
WorkPlace Local Browser
Pro Interface
RS-232
MZ2
ASD Bus
MZ2
ASD Bus
MS Trunk
DMS
MF2
LON
MF2
LON
Micro
Smart
PEM
Micro
Smart
A B R I E F H I S T O R Y O F O U R D D C S Y S T E M S
Page 20
A BRIEF HISTORY OF OUR DDC SYSTEMS
Review Questions
1. Define the following abbreviations:
IBS ___________________________________________________________________
DDC __________________________________________________________________
DMS __________________________________________________________________
MS ____________________________________________________________________
GUI ___________________________________________________________________
GCM __________________________________________________________________
LCM __________________________________________________________________
PEM __________________________________________________________________
ASD __________________________________________________________________
AI ____________________________________________________________________
DI ____________________________________________________________________
AO ____________________________________________________________________
DO ____________________________________________________________________
UNC __________________________________________________________________
2. a.) What company initially developed the NETWORK 8000 DDC family?
________________________________________________________________________
b.) What company initially developed the DMS family of controllers?
________________________________________________________________________
c.) What company developed the LonWorks technology?
________________________________________________________________________
Page 21
A BRIEF HISTORY OF OUR DDC SYSTEMS
Page 22
A BRIEF HISTORY OF OUR DDC SYSTEMS
8. Tell which operating system each graphical user interface uses, and then specify the
controller families that the GUI can talk to.
GUI or Controller
Programming Tool O/S Families
a. PSI _______________ ____________________
b. OPRIF _______________ ____________________
c. Host _______________ ____________________
d. Signal _______________ ____________________
e. UltiVist _______________ ____________________
f. InVue _______________ ____________________
g. WorkPlace Tech _______________ ____________________
h. Niagara _______________ ____________________
____________________
10. What are the two unique advantages of the I/A Series Niagara Framework user
interface? _______________________________________________________________
________________________________________________________________________
Page 23
A BRIEF HISTORY OF OUR DDC SYSTEMS
DDC Abbreviations
NETWORK 8000
GCM Global Control Module (an area controller)
LCM Local Control Module (16 universal points)
MF II MicroFlo II (VAV controller)
ASD Application Specific Device (a family of controllers)
MZ II MicroZone II (8 UIs, 4 AOs, 4 DOs)
PEM Packaged Equipment Module (12 points)
LIM Lighting Interface Module (GE Lighting Panel)
User Interfaces
PSI Personal System Interface (DOS based)
Host QNX based (NW 8000)
OPRIF Operator’s Interface – DOS based (DMS)
Signal Windows 95 or XP based (NW 8000 or DMS)
UltiVist OS/2 based (NETWORK 8000 or DMS)
InVue Windows NT based (NW 8000 or DMS)
Niagara Windows NT or Windows 2000 based – generates web pages
(NW8000, DMS, LON, BACnet)
Page 24