micronetmicronet.com.ua/data/data-support/system/micronet... · micronet components include...

MicroNet

System Overview

Copyright © 2007 TAC Satchwell. All rights reserved.

This document, as well as the product it refers to, is only intended for licensed users. TAC Satchwell owns the copyright of this document and reserves the right to make changes, additions or deletions. TAC Satchwell assumes no responsibility for possible mistakes or errors that might appear in this document.

Do not use the product for other purposes than those indicated in this document.

Only licensed users of the product and the document are permitted to use the document or any information therein. Distribution, disclosure, copying, storing or use of the product, the information or the illustrations in the document on the part of non-licensed users, in electronic or mechanical form, as a recording or by other means, including photo copying or information storage and retrieval systems, without the express written permission of TAC Satchwell, will be regarded as a violation of copyright laws and is strictly prohibited.

Trademarks and registered trademarks are the property of their respective owners.

TAC Vista® and TAC Xenta® are registered trademarks of TAC AB.

MicroNet System Overview Contents

Contents

1 About this Manual 31.1 Purpose of this Manual............................................................................................... 31.2 Structure ..................................................................................................................... 31.3 Acrobat (PDF) Conventions....................................................................................... 41.4 Typographic Conventions .......................................................................................... 41.5 Terminology............................................................................................................... 51.6 Applicable Documentation......................................................................................... 7

2 Introduction to MicroNet 112.1 About MicroNet Systems........................................................................................... 112.2 MicroNet Hardware Components .............................................................................. 132.2.1 Controllers............................................................................................................... 132.2.2 MicroNet Manager Interface................................................................................... 142.2.3 ARCNET Routers ................................................................................................... 162.2.4 MicroNet Touch Screen .......................................................................................... 182.2.5 MicroNet MN LCD................................................................................................. 202.2.6 MicroNet Sensors.................................................................................................... 212.2.7 TAC Xenta 555 Web Server ................................................................................... 222.3 MicroNet Software Components................................................................................ 232.3.1 MicroNet View........................................................................................................ 232.3.2 VisiSat ..................................................................................................................... 232.3.3 XBuilder (for the Xenta 555 web server)................................................................ 232.3.4 WorkPlace Tech Tool ............................................................................................. 242.3.5 Remote Alarm Manager .......................................................................................... 242.4 Networked Systems.................................................................................................... 242.4.1 NCP Networks ........................................................................................................ 252.4.2 ARCNET Networks ................................................................................................ 272.4.3 LONWORKS Networks ............................................................................................ 29

3 MicroNet 'MN 50 Series' Controllers 333.1 Introduction ................................................................................................................ 333.1.1 Programming........................................................................................................... 333.1.2 I/O Point Comparison ............................................................................................. 333.1.3 Universal Inputs ...................................................................................................... 343.1.4 Programming Capacities ......................................................................................... 343.1.5 Networking Objects ................................................................................................ 353.2 MicroNet 350 Series Controllers ............................................................................... 353.3 MicroNet 450 Series Controllers ............................................................................... 363.4 MicroNet 550 Series Controllers ............................................................................... 373.5 MicroNet 650 Series Controllers ............................................................................... 39

TAC Satchwell, Feb 2007 1 (76)3/06387400_A3

Contents MicroNet System Overview

4 MicroNet LONMARK Controllers 414.1 Introduction ................................................................................................................ 414.1.1 Model Numbers ....................................................................................................... 414.2 MicroNet LONMARK MNL 50 Series Controllers...................................................... 424.3 MicroNet LONMARK MNL 100, 150 and 200 Series Controllers.............................. 434.4 MicroNet LONMARK MNL 110 and 130 Controllers................................................. 464.5 MicroNet LONMARK VAV Series Controllers........................................................... 48

5 MicroNet Interface Devices 515.1 MicroNet Manager Interface ...................................................................................... 515.2 MicroNet Touch Screen ............................................................................................. 525.3 MicroNet LCD............................................................................................................ 55

6 Software Interfaces 576.1 MicroNet View........................................................................................................... 576.2 MicroNet View Functions .......................................................................................... 596.2.1 MicroNet View........................................................................................................ 596.2.2 MicroNet View Pro ................................................................................................. 606.3 VisiSat Configuration Tool ........................................................................................ 616.3.1 Connecting VisiSat to a Network ............................................................................ 626.4 XBuilder ..................................................................................................................... 646.5 WorkPlace Tech Tool................................................................................................. 656.5.1 Application Creation and Modification................................................................... 666.6 MicroNet VAV Flow Balance Software .................................................................... 666.7 LON Network Management Tools ............................................................................. 676.8 MicroNet Remote Alarm Manager............................................................................. 676.9 TAC Vista Workstation.............................................................................................. 68

7 Glossary 69

2 (76) TAC Satchwell, Feb 20073/06387400_A3

MicroNet System Overview 1 About this Manual

1 About this Manual

1.1 Purpose of this ManualThis manual introduces the MicroNet system. If you are new to Micro-Net and wish to gain an understanding of the components and network types that form a MicroNet system, you should read at least Chapter 1.

MicroNet components include controllers, and software tools. Chapters 2 to 6 describe these components in further detail.

For information on third party products, we refer you to the instructions delivered with the third party product.

If you discover errors and/or unclear descriptions in this manual, please contact your TAC representative.

After reading this manual, you should understand:

• The purposes of the various MicroNet controller and interface devices.

• How the various devices are used in NCP, ARCNET and LON-WORKS networks

• The functions of the various software tools and interfaces.

1.2 StructureThis manual contains the following:

Chapter 1 - About this Manual

This chapter - describes the structure and scope of this manual.

Chapter 2 - Introduction to MicroNet

This chapter introduces MicroNet systems, including the hardware and software components and network types that form a MicroNet system.

Note

• We are continuously improving and correcting our documenta-tion. This manual may have been updated.

Please check our Docnet site at www.tac.com for the latest ver-sion.


1 About this Manual MicroNet System Overview

Chapter 3 - MicroNet 'MN 50 Series' Controllers

This chapter provides descriptions of the programmable 'MN 50 Series' controllers (MN350, 450, 550 and 650), which are suitable for NCP, ARCNET or LONWORKS networks.

Chapter 4 - MicroNet LonMark Controllers

This chapter provides descriptions of the LONMARK® controllers (MNL 50, 100, 110, 130, 150, 200 and VAV), which are suitable for LON-WORKS® networks only.

Chapter 5 - MicroNet Interface Devices

This chapter provides descriptions of the MicroNet Manager Interface (MN MI), Touch Screen and LCD device.

Chapter 6 - Software Interfaces

This chapter provides descriptions of the various software systems, such as VisiSatTM, WorkPlace Tech Tool, MicroNet View and XBuilder.

Glossary

The Glossary defines terms used in this manual as well as terms used in the HVAC industry.

1.3 Acrobat (PDF) Conventions If reading this manual online in Adobe® Acrobat® (.PDF file format), numerous hypertext links exist for all entries in the Contents list, and other standard cross references. These links are indicated when the cur-sor changes to a hand with a pointing finger.

1.4 Typographic ConventionsThe following conventions are used in this manual:

• Bold is used for option names.

• Italics are used for references to external manuals.

In addition, the following specially marked texts may occur throughout the manual:

! Warning

• Alerts you that failure to take, or avoid, a specific action might result in physical harm to you or to the hardware.



1.5 TerminologyTable 1.1 explains the terminology used in this manual.

Table 1.1: Terminology

Caution

• Alerts you to possible data loss, breaches of security, or other more serious problems.

Important

• Alerts you to supplementary information that is essential to the completion of a task.

Note

• Alerts you to supplementary information.

Tip

• Alerts you to supplementary information that is not essential to the completion of the task at hand.

Advanced

• Alerts you that the following information applies to complex tasks or tasks restricted by access.

Term Description

AI Analogue Input

AO Analogue Output

ARCNET® Attached Resource Computer Network

CAD Computer-Aided Design

DDE Dynamic Data Exchange

DI Digital Input



DO Digital Output

EEPROM Electrically Erasable Programmable Read Only Memory

FTT Free Topology Transceiver

HVAC Heating, Ventilating and Air-Conditioning

I/O Input / Output

LAN Local Area Network

LCD Liquid Crystal Display

LED Light Emitting Diode

mA milliAmperes

MN MicroNet

MN-Sx MicroNet Sensor

MN View MicroNet View

NCP Native Communications Protocol

PC Personal Computer

PSTN Public Switched Telephone Network

RAM Random Access Memory

RAM Remote Alarm Manager

RTC Real Time Clock

S-LK Sensor Link

S-Link Sensor Link

SNVT Standard Network Variable Type

SPI Satchwell Pager Interface

UI Universal Input

Vac Volts (Alternating Current)

VAV Variable Air Volume

WP Tech WorkPlace Tech Tool

AI Analogue Input

Term Description

AI Analogue Input



1.6 Applicable DocumentationTable 1.2 details the available MicroNet documentation.

Table 1.2: MicroNet Documentation

Document Description Audience Purpose

Quote name MicroNet System Engineering Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides engineering information for install-ing MicroNet Systems.

Quote name MicroNet View Engineering Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides information for using all aspects of MicroNet View, excluding the I/O-Servers.

Quote name MicroNet NCP/ARCNET I/O-Server Engineering Guide

• Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides information for setting up and using the NCP/ARCNET I/O-Servers.

Quote name VisiSat Engineering Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides information for applying and using all aspects of the VisiSat Configuration Tool.

Quote name WorkPlace Tech Tool User's Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides step-by-step instructions for using the WorkPlace Tech Tool interface.

Quote name WorkPlace Tech Tool Engineering Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides engineering and technical informa-tion for applying and using all aspects of WorkPlace Tech Tool.

Quote name EN-215 Air Balancing Terminal Boxes Controlled by MicroNet Controllers Using Third-Party Network Management Tools

• Application Engineers• Qualified Air Balancers

Provides instructions for manually balancing terminal boxes controlled by MNL-V1RVx and MNL-V2RVx VAV Controllers using a third-party network management tool.

Quote name MicroNet Touch Screen User's Guide • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides step-by-step instructions for using the Touch Screen Display.

Quote name MicroNet Remote Alarm Manager Instal-lation and User Guide


Provides information for installing and using the Remote Alarm Manager.

DS 10.000 MicroNet Sensor Specification Data Sheet • Application Engineers• Sales Personnel

Describes features and specifications of the MicroNet Sensors.

DS 10.050 MicroNet Touch Screen Display Specifica-tion Data Sheet

• Application Engineers• Sales Personnel

Describes features and specifications of the MicroNet Touch Screen Display.

DS 10.060 MicroNet MN LCD Display Specification Data Sheet


Describes features and specifications of the MicroNet MN LCD Display.



DS 10.070 MicroNet LONMARK ® MNL 50 Series Controllers Specification Data Sheet


Describes features and specifications of the MicroNet LONMARK MNL 50 Controller.

DS 10.100 MicroNet LONMARK MNL 100, 150 and 200 Series Controllers Specification Data Sheet


Describes features and specifications of the MicroNet LONMARK MNL 100, 150 and 200 Series Controllers.

F-26886 MicroNet LONMARK 110 Controller Spec-ification Data Sheet


Describes features and specifications of the MicroNet LONMARK 110 Controller.

F-27040 MicroNet LONMARK 130 Controller Spec-ification Data Sheet


Describes features and specifications of the MicroNet LONMARK 130 Controller.

F-26887 MicroNet LONMARK 110 and 130 Control-lers Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet LONMARK 110 and 130 Controllers. Also includes check-out and LED indication sections.

DS 10.120 MicroNet LONMARK VAV Series (MNL-V1RVx and MNL-V2RVx) Controllers Specification Data Sheet


Describes features and specifications of the MicroNet MNL-V1RVx and MNL-V2RVx VAV Controllers.

DS 10.121 MicroNet LONMARK VAV Series (MNL-V3RVx) Controller Specification Data Sheet


Describes features and specifications of the MicroNet MNL-V3RVx VAV Controller.

DS 10.151 MicroNet 350 Series Controllers Specifi-cation Data Sheet


Describes features and specifications of the MicroNet 350 Controllers.










DS 10.201 MicroNet View Specification Data Sheet • Application Engineers• Sales Personnel

Describes features and specifications of the MicroNet View software.

DS 10.202 MicroNet VisiSat Configuration Tool Specification Data Sheet


Describes features and specifications of the VisiSat Configuration Tool software.

DS 10.203 Commissioning, Service and Maintenance Tool Specification Data Sheet


Describes features and specifications of the Commissioning, Service and Maintenance Tool software.

DS 10.217 MicroNet Manager Interface & ARCNET Router Specification Data Sheet


Describes features and specifications of the MicroNet Manager Interface.

DS 10.250 EN-206 Guidelines for Powering Multiple Full-Wave and Half-Wave Rectifier Devices from a Common Transformer

• Application Engineers• Installers• Service Personnel

Offers guidelines for avoiding equipment damage associated with improperly wiring devices of varying rectifier types. Contains instructions for identifying device rectifier type, guidelines for correctly powering devices of varying rectifier types, and exam-ples illustrating proper power wiring tech-niques.

DS 10.050A MicroNet Touch Screen Display Installa-tion Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet Touch Screen Display. Also includes checkout sec-tion.




DS 10.060A MicroNet MN LCD Display Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet MN LCD Display. Also includes checkout section.

DS 10.070A MicroNet LONMARK ® MNL 50 Series Controllers Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet MNL 50 Controller. Also includes checkout section.

DS 10.100A MicroNet LONMARK MNL 100, 150 and 200 Series Controllers Installation Instruc-tions


Provides step-by-step mounting and installa-tion instructions for the MicroNet LONMARK MNL 100, 150 and 200 Series Controllers. Also includes checkout and LED indication sections.

DS 10.151A MicroNet MN350 Series Controllers Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet 350 Con-troller. Also includes checkout section.










DS 10.120A MicroNet LONMARK VAV Series (MNL-V1RVx and MNL-V2RVx) Controllers Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet LONMARK MNL-V1RVx and MNL-V2RVx VAV Con-trollers. Also includes checkout and LED indi-cation sections.

DS 10.121A MicroNet LONMARK VAV Series (MNL-V3RVx) Controllers Installation Instruc-tions


Provides step-by-step mounting and installa-tion instructions for the MicroNet LONMARK MNL-V3RVx VAV Controller. Also includes checkout and LED indication sections.

DS 10.217A MicroNet Manager Interface & ARCNET Router Installation Instructions


Provides step-by-step mounting and installa-tion instructions for the MicroNet Manager Interface & ARCNET Router. Also includes checkout section.

DS 1.003 DDT Duct Sensor (100 to 330mm Stem Length) General Instructions


Provides step-by-step installation and check-out procedures for DDT Duct Sensor.




DS 1.020 DUSF Fan Speed Control Sensor General Instructions


Provides step-by-step installation and check-out procedures for DUSF Fan Speed Control Sensor.

DS 1.030 DDU Duct Sensor General Instructions • Application Engineers• Installers• Service Personnel• Start-up Technicians

Provides step-by-step installation and check-out procedures for DDU Duct Sensor

DS 1.203 DST Strap-On Pipe Surface Temperature Sensor General Instructions


Provides step-by-step installation and check-out procedures for DST Strap-On Pipe Surface Temperature Sensor.

DS 1.203 DWT Immersion Sensor (100 to 330mm Stem Length) General Instructions


Provides step-by-step installation and check-out procedures for DWT Immersion Sensor.

DS 1.204 DWT Fast Response Immersion Sensor (120 Stem Length) General Instructions


Provides step-by-step installation and check-out procedures for DWT Fast Response Immersion Sensor.

DS 1.402 DOS Solar Gain Effect Sensor General Instructions


Provides step-by-step installation and check-out procedures for DOS Solar Gain Effect Sensor.

DS 1.402 DOT Outside Air Temperature Sensor General Instructions


Provides step-by-step installation and check-out procedures for DOT Outside Air Tempera-ture Sensor.

DS 1.502 DRTH Room Humidity Sensor General Instructions


Provides step-by-step installation and check-out procedures for DRTH Room Humidity Sensor.



MicroNet System Overview 2 Introduction to MicroNet

2 Introduction to MicroNetThis chapter gives an introduction to MicroNet systems. If new to MicroNet, you should read all of this chapter first. Further details are given in later chapters.

2.1 About MicroNet SystemsThe MicroNet System is an HVAC control system incorporating con-figurable 'MN 50 Series' controllers, LONMARK controllers, interfacing devices, temperature sensors, Touch Screens, LCD display devices and the necessary software tools for system configuration and monitoring. Software tools include VisiSat and WorkPlace Tech Tool, which are PC-based programs for configuring and downloading controller appli-cations, XBuilder for web based monitoring and control (within the Xenta 555) and a Remote Alarm Manager for alarms configuration and monitoring.

Also available is the powerful MicroNet View, which provides a set of sophisticated graphical PC-based applications for monitoring and acknowledging alarms, logging data and viewing or changing the oper-ation of the equipment being controlled.

In its simplest form, a MicroNet system may consist of a single standa-lone controller and sensor, as shown in Fig. 2.1. For more comprehen-sive control schemes, MicroNet controllers can be networked in an NCP, ARCNET or LONWORKS network. Fig. 2.2 shows an example of an NCP network.

In ARCNET and LONWORKS networks, data can be transferred between controllers. This is achieved using network variable objects in the con-troller application, which define the information to transfer between controllers (known as Standard Network Variable Types, or SNVTs, in LONWORKS networks).

MicroNet includes a wide variety of different hardware and software options, which enable you to select the correct hardware and software to match the requirements of the control scheme. This chapter gives an introduction to the MicroNet components and to the three different net-work types. The remaining chapters of this manual give further details about the MicroNet hardware and software components.


2 Introduction to MicroNet MicroNet System Overview

.

Fig. 2.1: Standalone MicroNet Controller

Fig. 2.2: Example Networked MicroNet System (NCP)

Controller (MN450 shown)

Sensor (DUSF shown)

DUSF sensor

DRTH sensor

MN550 controller

MN450 controller

Touch Screen MN450 controller

MN MI

MicroNet View or VisiSat Configuration Tool. (VisiSat is normally used on a laptop PC.)

Alarm printer

RS 232

Additional MicroNet controllers

Additional MicroNet controllers and Touch Screens MN450 controller

A Touch Screen can display and change information from one or more of its connected controllers.

Xenta 555 web server

Optional connection to TAC Vista

Ethernet



2.2 MicroNet Hardware ComponentsMicroNet systems can include the following hardware components:

• 'MN 50 Series' Controllers MN350, 450, 550 and 650

• LONMARK Controllers (MNL 50, 100, 110, 130, 150 and 200 and MNL VAV)

• MicroNet Manager Interfaces (MN MIs) and ARCNET Routers

• Touch Screen Displays (MN Touch (NCP and ARCNET) and MN LON Touch)

• LCD Displays (MN LCDs)

• MicroNet compatible sensors (MN-Sx, DOT, DOS, DST, DWT, DDT, DUSF and DRTH).

It is also possible to connect a TAC Xenta 555 web server to a MicroNet network and monitor and control the network from a PC connected to the internet.

2.2.1 Controllers

The following controller types are available (see Fig. 2.3):

• 'MN 50 Series' MN350, 450, 550 and 650 fully programmable controllers. These allow customisation of the control scheme. NCP, ARCNET and LONWORKS communications options are available, e.g. MN350-NCP, MN450-ARC and MN450-LON.

• LONMARK-compliant MNL 50, 100, 110, 130, 150 and 200 con-trollers. These LONWORKS controllers are suitable for heat pump, fan coil and similar applications. The controllers feature a fixed LONMARK (SNVT) profile. Although fully programmable, appli-cations can be selected from a library.

• MNL VAV (Variable Air Volume) LONMARK-compliant control-lers. These LONWORKS controllers provide a wide range of control strategies for pressure-independent terminal boxes, with or with-out reheat capabilities. Like the MNL 50, 100, 110, 130, 150 and 200, these controllers feature a fixed LONMARK (SNVT) profile, and applications can be selected from a library.



Fig. 2.3: Examples of MicroNet Controllers

2.2.2 MicroNet Manager Interface

A MicroNet Manager Interface (MN MI) can be placed at the head of an NCP or ARCNET network. An MN MI has several purposes:

• It can be used to synchronize time across all controllers in the net-work.

• It allows VisiSat and MicroNet View to connect to the network via a serial connection to the MN MI (see Fig. 2.4).

• It can connect to a modem to enable remote access to the network from VisiSat or MicroNet View (see Fig. 2.5). The MN MI fea-tures password protection to stop unauthorized computers from interrogating remote sites

• It enables local alarm checking and data logging as part of a MicroNet View monitored system.

DO

124VA

CD

O2

DO

324VA

CD

O4

?

DO

5C

5

DO

6C

6

DO

7C

7

GN

D0V

24VAC

UI3

CO

M 0V

UI2

CO

M 0V

UI1

S-LK

S-LK

LON

LON

SRVC

RECV

XMIT

J1

SR

VC

MN550 and MN650MN450

MNL VAV

MNL 100, MNL 150 and MNL 200

MNL 50

MN350

DO

124VA

CD

O2

DO

324VA

CD

O4

DO

5C

5

GN

D0V

24VAC

UI3

CO

M 0V

UI2

CO

M 0V

UI1

S-LK

S-LK

LON

LON

SRVC

RECV

XMIT

J1

SR

VC

MNL 110 MNL 130



Fig. 2.4: Example NCP/ARCNET Network with MN MI

MN MI

DUSF sensor

DRTH sensor

DUSF sensor

MN550

MN450

MN450

Additional NCP/ARCNET Touch Screens and controllers

MicroNet View or VisiSat PC (VisiSat is normally used on a laptop PC)

RS 232



Fig. 2.5: Example NCP/ARCNET Network with MN MI used for Remote Access

2.2.3 ARCNET Routers

An ARCNET router is used to increase both the wiring length of an ARCNET network and the number of controllers that can be used.

Connecting an ARCNET router creates a new branch of the LAN, known as a sub-LAN, to which other ARCNET controllers and routers can be connected, as shown in Fig. 2.6. The main LAN may contain up to 95 devices (plus the MN MI). Up to 31 sub-LANs can be used, each allowing a further 95 devices to be connected. For performance reasons when transferring network variables between controllers, the main LAN should have only ARCNET routers connected to it (unless there are no


RS 232

RS 232

Modem

Modem

Public Switched Telephone Network (PSTN)

MN MI

DUSF sensor

MN450

MN650

DUSF sensor

Additional MicroNet Touch Screens and controllers



sub-LANs). The maximum wiring path between the two most distant devices on the main LAN must not exceed 800m. However, a maximum of 5 routers can be cascaded to increase the maximum routing length to 4.8km.

Fig. 2.6: Using ARCNET Routers

Alarm printer

MN450

Additional ARCNET routers and controllers


RS 232

MN450

MN450 MN450

Additional ARCNET routers and controllers

ARCNET router

ARCNET router

Additional ARCNET routers

MN MI

ARCNET router

ARCNET touchscreen

DUSF sensor



2.2.4 MicroNet Touch Screen

MicroNet Touch Screens are available for NCP, ARCNET and LON-WORKS controllers. The Touch Screen provides a liquid-crystal display that gives a graphical interface for viewing or changing the current state of the control system. It does this by accessing selected points within controllers, such as the inputs and outputs to each controller, or other points within the controller applications. The points that each Touch Screen accesses is set up within the VisiSat Configuration Tool.

A Touch Screen can be used in a single-controller system (see Fig. 2.7), on the top-level LAN of an NCP network, on an ARCNET sub-LAN (or on the main LAN if no ARCNET sub-LAN exists), or anywhere on a LONWORKS network.

A real-time clock (RTC) module with backup battery is built into the Touch Screen, which can be used to synchronize time amongst control-lers on its sub-LAN (NCP) or across all controllers on the network (ARCNET and LONWORKS).

Touch Screen Functions

An NCP or ARCNET Touch Screen can read/write up to 256 controller parameters. LONWORKS Touch Screens can read/write up to 128 con-troller parameters. These parameters appear as individual icons and can be organized on menu-accessible screens. Depending on the selected parameters, various Touch Screen actions are possible including over-ride initiations, setpoint adjustment, time schedule adjustment and graphical viewing of historical data. Up to 32 of the parameters can be configured in the Touch Screen for local alarm polling and annunciation to the display.

The Touch Screen is available as a panel-mount device, or can be wall mounted using the MN-DK kit. The Touch Screen can also be mounted in an NCP networked MN550 or MN650 controller (MN550-NCP or MN650-NCP).

NCP Touch Screens

In an NCP network, the Touch Screen creates a new branch of the LAN (a sub-LAN) to which other NCP controllers can be connected (see Fig. 2.2). This increases the maximum number of controllers that can be used, since the main LAN can have up to 63 devices, and each sub-LAN a further 63 controllers (with a system maximum of 20 sub-LANs).

Note

To maintain network performance, the network must be organized to ensure that data (network variables) transferred between controllers does not have to pass through a router.



An NCP Touch Screen can be used to monitor or control one or more of the controllers on its sub-LAN.

Another useful feature of a Touch Screen in an NCP network is that it enables the total network length to be increased, since the main LAN and each sub-LAN has its own maximum wiring length of 1000m.

Fig. 2.2 shows an example of a panel-mount Touch Screen used in an NCP network. Fig. 2.7 shows an example of a Touch Screen mounted in a standalone MN550 controller.

Fig. 2.7: Stand-Alone NCP Controller with Touch Screen

ARCNET Touch Screens

In an ARCNET network, a Touch Screen is able to monitor or control one or more controllers located anywhere on the network, even if they are on different sub-LANs. The Touch Screen does not create a sub-LAN in an ARCNET network; a router is used for that purpose.

MicroNet Touch Screen fitted in an MN550-NCP controller

DUSF sensor



Fig. 2.8: ARCNET Network with Touch Screens

LONWORKS Touch Screens

In a LONWORKS network, a Touch Screen (known as the LON Touch Screen) is able to monitor or control one or more controllers located anywhere on the network.

2.2.5 MicroNet MN LCD

A MicroNet MN LCD can connect to a single MN550 or MN650 con-troller on an NCP, ARCNET or LONWORKS network. It can also con-nect to an NCP MN350, 450, 550 or 650 controller, providing the controller is not networked. The device contains a liquid-crystal display

ARCNET router

Additional ARCNET routers

MN450 controller

MN550 controller

MN650 controller

Alarm printer

Touch Screen

MicroNet Manager Interface (MN MI)

Sub-LAN

MicroNet View or VisiSat Configuration Tool. (VisiSat is normally used on a laptop PC.)

ARCNET router

Sub-LAN

Touch Screen

MN450 controller

LCD Device



that gives a text, menu-driven interface for viewing or changing the cur-rent behaviour of the controller to which it is connected.

The LCD display can, for example, be used to interrogate and alter tem-perature inputs, equipment status and time and holiday schedules.

MN LCD configuration is achieved in a similar way to a Touch Screen by using VisiSat to specify which points in the controller to access. The points accessed could be inputs and outputs to the controller, or other points within the controller application.

The MN LCD is often used as a low-cost solution for providing a user interface to a standalone controller, as shown in Fig. 2.9.

The MN LCD model features a built-in real-time clock (RTC) to pro-vide controller or network time synchronization.

The MN LCD is available as a panel-mount device, or can be wall mounted using the MN-DK kit. The MN LCD can also be mounted in a standalone NCP networked MN550 or MN650 controller (MN550-NCP or MN650-NCP).

Fig. 2.9: Stand-Alone Controller with MN LCD

2.2.6 MicroNet Sensors

A wide range of different sensor types are suitable for use with Micro-Net (Fig. 2.10). For example:

• MN-Sx Series Digital Wall Sensors

• DDT, DST and DWT Temperature Sensors

• DUSF Fan Speed Control Sensor

• DRTH Room Humidity Sensor

• DOT Outside Air Temperature Sensor.

Fig. 2.10: Examples of MicroNet Sensors

MN LCD fitted in an MN550-NCP controller

DUSF sensor

MN-S2 MN-S5 DRTH DOTDUSF



The MN-Sx digital wall sensors can connect to any of the 'MN 50 Series' controllers (MN350, 450, 550, 650) on an NCP, ARCNET or LONWORKS network, or to any of the LONWORKS MNL 50, 100, 110, 130, 150, 200 or VAV controllers. Depending on model, MN-Sx sen-sors give control over functions such as the current temperature, fan speed and controller mode. The MN-S3, MN-S4 and MN-S5 sensors provide an LCD interface.

The MN-Sx Sensor Link communication protocol allows a simple two-wire interface for power and communications information. Optionally, an MN-Sx sensor can also be wired to the LONWORKS network using a LONWORKS cable pair. This enables WorkPlace Tech Tool, VisiSat, the MicroNet VAV Flow Balance software and third-party network man-agement tools to connect to the LONWORKS network using the MN-Sx's built-in 'LON Jack'.

2.2.7 TAC Xenta 555 Web Server

The TAC Xenta 555 Web Server can connect to MicroNet networks and provides secure web browser access to MicroNet controllers. It can also act as a server for LONWORKS networks, providing a gateway to TAC Vista.

The Xenta 555 is programmed using XBuilder (refer to Page 64).

The Xenta 555 can be used with NCP, ARCNET and LONWORKS net-works.

Fig. 2.11: TAC Xenta 555 Web Server

For further details of the TAC Xenta 555 web server, refer to the follow-ing documents:

• TAC Xenta 555 Data Sheet - 03-00044-01-en

• TAC Xenta Product Manual - 04-00071-01-en

• TAC Xenta Server Technical Manual - 04-00051-01-en

• TAC Xenta 555 Supplement Manual - 04-00054-01-en

• TAC Xenta 555 Operating Manual - 04-00044-01-en.



2.3 MicroNet Software ComponentsThe following software components can be used in a MicroNet system:

• MicroNet View

• VisiSat Configuration Tool

• XBuilder (for the Xenta 555 MicroNet web server)

• WorkPlace Tech Tool

• Flow Balance Software

• Third-Party Network Management Tools

• Remote Alarm Manager

In addition, the MicroNet system can interface to TAC Vista via a Xenta 555 used as a gateway.

2.3.1 MicroNet View

MicroNet View provides a comprehensive and intuitive PC-based graphical environment, enabling people to monitor, manage and control the building equipment.

Included within MicroNet View is the ability to set up and manage alarm conditions, and to record and view logged data. For improved performance, MicroNet View is able to distribute the tasks of alarm checking and data logging to an MN MI at the head of an NCP or ARC-NET network.

MicroNet View is compatible with NCP, ARCNET and LONWORKS networks, and has the advantage of being able to control multiple sites, including remote sites accessed via modem.

For further details of MicroNet View, refer to Page 57.

2.3.2 VisiSat

VisiSat is a PC-based engineering program for configuring and down-loading applications to MicroNet MN350, 450, 550 and 650 controllers on an NCP, ARCNET or LONWORKS network. It is also able to config-ure MicroNet Touch Screens, MN LCDs and MN MIs.

VisiSat is normally used on a laptop PC, since it is necessary for VisiSat to connect to controllers only during system setup and commissioning.

For further details of VisiSat, refer to Page 61.

2.3.3 XBuilder (for the Xenta 555 web server)

The TAC Xenta 555 enables the monitoring and control of a MicroNet system over the Internet or through an intranet, using Internet Explorer. XBuilder is the software design tool which enables the creation of a cus-tomized set of web pages which can be used to represent selected items



of building equipment in the MicroNet controlled system. When viewed over the internet in a browser, this set of web pages will visibly respond in real time to the changes occurring in the MicroNet system (tempera-tures, pressures etc.). The operator can then interact with this scheme, monitoring and if necessary changing point values as required.

For further details of XBuilder, refer to Page 64.

2.3.4 WorkPlace Tech Tool

WorkPlace Tech Tool is a PC-based engineering program required to configure and program individual MNL 50, 100, 110, 130, 150, 200 and VAV controller applications on a LONWORKS network.

Controller configuration is similar to VisiSat; a library of objects is pro-vided, which can be placed and connected to form the control scheme.

A library of pre-engineered control schemes is also available.

For further details of WorkPlace Tech Tool, refer to Page 65.

2.3.5 Remote Alarm Manager

The Remote Alarm Manager collects alarms from MicroNet View, then distributes them as messages to the relevant personnel. Alarm messages can be distributed in a variety of different forms, including as fax mes-sages, printed output, in web pages over the Internet, or in WAP or text messages at mobile phones. Once delivered, alarms can be acknowl-edged and alarm messages accepted/refused remotely (depending on configuration).

For further details of the Remote Alarm Manager, refer to Page 67.

2.4 Networked SystemsIn larger control schemes, increased capacity is achieved by installing additional controllers. Although it is possible to install these as indepen-dent controllers, a networked solution provides several advantages:

• Networking enables centralized monitoring and control from a MicroNet Touch Screen. This allows all the controllers used to be monitored and controlled from a single point in the building, thereby giving possible reductions in the amount of interface hard-ware required.

• ARCNET and LONWORKS networks are peer-to-peer. This means that controllers on ARCNET and LONWORKS networks can share data, such as temperature values from a sensor connected to just one controller. LONWORKS controllers can also exchange data with other third-party devices through standardized network vari-ables (SNVTs).



• MicroNet View can connect to a networked system to provide an enhanced graphical interface to the control scheme.

• Controller configuration is easier when the devices are networked, since the VisiSat Configuration Tool and WorkPlace Tech Tool can communicate with all controllers using a single connection to the network. This eliminates the need to visit each controller in turn, which may be difficult when equipment is installed in areas that are not easy to access. VisiSat can also configure networked con-trollers remotely.

• The current time at each controller in the network can be synchro-nised. This is achieved by assigning one device (a Touch Screen, MN MI, MN LCD or a third-party LONWORKS device) to be a net-work time master.

A real-time clock (RTC) is built into the MN MI, Touch Screen and MN LCD devices to maintain time during a power failure. An RTC is also able to be fitted to standalone MicroNet NCP MN350, 450, 550 and 650 controllers.

The following sections describe the features of each of the three net-work types (NCP, ARCNET and LONWORKS).

2.4.1 NCP Networks

An NCP network (Fig. 2.12) represents a cost-effective solution when neither open protocol (LONWORKS) nor peer-to-peer (ARCNET) com-munications are required. An NCP network has a communications speed of 9.6k baud using screened RS 485 twisted-pair cabling in a daisy-chain bus topology. No terminators are required.

MicroNet MN MI, 350, 450, 550 and 650 controllers can be used on an NCP network. MicroNet Touch Screens can also be used.

RS 485 communication drivers are built into NCP devices; no plug-in card needs to be fitted to controllers or Touch Screens to enable NCP communications.

An LCD device can be connected to an MN550 or 650 controller. An LCD device can also be connected to an MN350, 450, 550 or 650 con-troller that is not networked.

If an LCD device is connected to a networked MN550-XCOM or MN650-XCOM controller, it is not necessary to fit a communications card to the controller.

Since the network uses master-slave communications and the control-lers do not communicate in peer-to-peer fashion, direct data exchange between controllers cannot take place. However, data can be exchanged through MicroNet View.

The main LAN in an NCP network can support up to 63 devices. If required, the system can be expanded by adding sub-LANs to the net-work. A sub-LAN connects to a Touch Screen, which serves as the poll-



ing device for the devices on its sub-LAN. A maximum of 20 sub-LANs can be used, each with a maximum of 63 devices. An NCP Touch Screen can display or modify data belonging to only those controllers on its sub-LAN.

The maximum cable distance of the main LAN is 1000m; each sub-LAN extends this range by a further 1000m.

The PC-based VisiSat Configuration Tool is used to configure the MN MIs, controllers, LCD devices and Touch Screens on the network.

MicroNet View provides alarm checking, plus dynamic and historical logging of data from the network. MicroNet View requires each local and remote NCP network to be headed by an MN MI.

Networks not using MicroNet View do not require an MN MI, but using an MN MI enables remote configuration via a serial port from VisiSat (as well as automatic network-level time synchronization). NCP net-works without an MN MI can be configured from VisiSat by using an RS232-to-RS485 converter, which allows direct connection from the VisiSat PC to the NCP network.

Note

Touch Screens cannot be cascaded. A Touch Screen must connect only to the main LAN.



Fig. 2.12: Example NCP Network

2.4.2 ARCNET Networks

If peer-to-peer communications and high performance are desired, but the open LONWORKS protocol is not required, the ARCNET network option may be the best choice. Fig. 2.13 shows an example of an ARC-NET network.

Peer-to-peer communications enables controllers on an ARCNET net-work to send data to other controllers. That is, a parameter value can be sent from one controller to another over the network. This is achieved

MN450 Controller (MN450-NCP)

MN550 Controller (MN550-NCP) DRTH Sensor

DUSF SensorDUSF Sensor

Printer

MicroNet View PC

Typically, a laptop PC running VisiSat is temporarily connected to the MNMI during system installation and configuration.


MN450 Controller (MN450-NCP)MN450 Controller

(MN450-NCP)


For Remote Connection

Modem


RS 232

Connection via RS 232 Port

MicroNet Manager Interface (MN50-MI-NCP)

Touch Screen (MN50-TS-NCP with MN-DK)

Sub-LANSub-LAN

Sub-LAN

MicroNet Manager Interface (MNMI-NCP)

Remotely Located MicroNet System (NCP Network)

Touch Screen MN50-TS-NCP with MN-DK)

Touch Screen (MN50-TS-NCP with MN-DK)

Additional NCP MicroNet Controllers



NCP Network Communicates at 9.6k baud

Modem



by using the Network Variable (NVTx and NVRx) control objects in VisiSat. Typical data shared includes overrides, non-critical sensor data and monitor points to other controllers. (It is not advisable to split a con-trol system between different controllers, as no guarantee can be given over control performance.)

Network binding (i.e. specifying which controllers receive data from a controller) is also achieved within VisiSat.

The network protocol is token passing, i.e. only the node that has the token can send a message, after which the token must be given up. This token-passing method means that the network performance and speed can be calculated i.e. performance is deterministic.

An ARCNET network has a communications speed of 156k baud using screened RS 485 twisted-pair cabling.

The main LAN in the network can support up to 95 devices (plus the MN MI). Up to 31 sub-LANs may be added using ARCNET routers attached to the main LAN, and each sub-LAN may contain up to 95 devices (plus the router). No more than 31 sub-LANs should be used.

MicroNet MN MI, 350, 450, 550 and 650 controllers can be used on an ARCNET network. ARCNET routers and Touch Screens can also be used, and LCD devices connected to MN550 or 650 controllers.

The maximum cable distance of the main LAN is 800m; each sub-LAN extends this range by a further 800m. A maximum of 5 routers can be 'cascaded' to give a total maximum routing length of 4.8km.

The PC-based VisiSat Configuration Tool is used to configure the MN MI, controllers, LCD displays and Touch Screens on the network.

MicroNet View provides alarm checking, plus dynamic and historical logging of data from the network. MicroNet View requires each local and remote ARCNET network to be headed by an MN MI.

Networks not using MicroNet View do not require an MN MI, but using an MN MI enables remote configuration via a serial port from VisiSat (as well as automatic network-level time synchronization). ARCNET networks without an MN MI can be configured from VisiSat by using an ARCNET card in the PC, which allows direct connection from the VisiSat PC to the ARCNET network.

Note

It is important to ensure that the polarity of the network connections is consistent throughout the system, i.e. -ve is connected to -ve and +ve is connected to +ve.



Fig. 2.13: Example ARCNET Network with Local and Remote Sites

2.4.3 LONWORKS Networks

A LONWORKS network (Fig. 2.14) offers the most flexibility of the three network types because its network communications uses a stan-dard protocol called LonTalk®. This allows the integration of other ven-dors' LONWORKS devices as nodes on the MicroNet network, provided they are LONMARK certified or utilize compatible Standard Network Variable Types (SNVTs). Nodes can be simple sensors and actuators to controllers, Touch Screens, network management tools and protocol analyzers.

ARCNET Router (MN50-MI-RTR)

MN450 Controller (MN450-ARC)

MN550 Controller (MN550-ARC) DRTH Sensor

DUSF SensorDRTH Sensor

Alarm PrinterMicroNet View PC

VisiSat Configuration Tool




MN450 Controller (MN450-ARC)MN450 Controller

(MN450-ARC)


Modem

Modem


RS 232

RS 232



Sub-LAN Sub-LANSub-LAN



Nodes on a LONWORKS network can communicate with each other in a peer-to-peer fashion, meaning that they can freely share data using SNVTs. Typical data shared includes overrides, non-critical sensor data and monitor points to other LONWORKS nodes. (It is not advisable to split a control system between different controllers, as no guarantee can be given over control performance.)

A LONWORKS network allows the largest selection of MicroNet con-trollers. MNL 50, 100, 110, 130, 150, 200 and VAV, 350, 450, 550 and 650 controllers can all be used on a LONWORKS network. MicroNet LON Touch Screens can also be used.

All MicroNet controllers use the popular FTT-10A transceiver. The FTT-10A transceiver operates at 78kbps over twisted pair cable, and connections are not polarity sensitive.

A LONWORKS network uses a free-topology or bus (daisy-chain) con-figuration and can host up to 64 LONWORKS nodes per wiring segment. Using repeaters and routers allows a network to be expanded to contain up to 32,385 nodes.

VisiSat can be used to configure MN350, 450, 550 and 650 Lon control-lers and the Lon Touch Screen on a LONWORKS network using a Lon-Talk card fitted to the PC. VisiSat is also able to configure LCD devices connected to an MN550 or 650.

WorkPlace Tech Tool is used to configure and program the MNL 50, 100, 110, 130, 150, 200 and VAV controller applications.

MicroNet View uses Echelon® Corporation's LNS DDE server and pro-vides alarm checking, dynamic logging and historical logging for the network.

Note

MN MIs are not currently supported on LONWORKS networks.



Fig. 2.14: Example LONWORKS Network

LONWORKS Network Communicates at 78.1k baud

Connection using LonTalk adaptor

MNL 100

MNL VAV

MNL 200

Sensor Link (S-link)

MN-S5 Sensor

MN-S5 Sensor

Sensor Link (S-link)

Alarm PrinterMicroNet View PC

MN450-LON

DRTH Sensor

DUSF Sensor

MN550-LON

VisiSat is used on a notebook PC, which is temporarily connected to the network for the configuration of MN350, 450, 550 and 650 controllers. WorkPlace Tech Tool is used for the configuration of MNL 50, 100, 110, 130, 150, 200 and MNL VAV controllers.


MicroNet System Overview 3 MicroNet 'MN 50 Series' Controllers

3 MicroNet 'MN 50 Series' ControllersThis chapter describes the VisiSat-programmable 'MN 50 Series' MicroNet controllers:

• MicroNet 350 Series controllers




3.1 IntroductionMicroNet 350, 450, 550 and 650 series controllers are fully-program-mable, using a set of control objects in controller memory.

These controllers feature a variety of built-in inputs and outputs. The MN650 has the most (33) I/O points, followed by the MN550 with 29 I/O points. The MN350 and 450 controllers are smaller in size, with 19 and 16 I/O points respectively.

MicroNet 350, 450, 550 and 650 controllers are 24Vac/24Vdc powered devices (the MN350 controller can also operate from a 230Vac supply). Controllers can be DIN rail-mounted or panel-mounted. Each type of controller can be used standalone or in an NCP, ARCNET and LON-WORKS communications network (depending on variant).

A real-time clock (RTC) module can be fitted to a standalone MN350, 450, 550 or 650 controller to maintain the controller's time during a power failure.

3.1.1 Programming

These controllers are fully programmable with VisiSat Configuration Tool, meaning that a custom application must be designed in VisiSat and downloaded into the device before it can be used.

3.1.2 I/O Point Comparison

Selection of a controller usually depends on the I/O points offered and its programming capacity. The higher the model number, the more I/O points and logical programming capacity it will have. For example, an


3 MicroNet 'MN 50 Series' Controllers MicroNet System Overview

MN650 controller has more I/O points than an MN450. Table 3.1 pro-vides a comparison of the models and I/O points.

3.1.3 Universal Inputs

By setting the controller's jumper pins, any of the universal inputs may be configured as a voltage, resistive or dry contact input. This must match the configuration of each universal input, as set up in the VisiSat Configuration Tool.

3.1.4 Programming Capacities

Logical programming capacity for each MicroNet controller is mea-sured by the number of objects and connections each controller can sup-port. The MN650 has the greatest available number of control objects and connections, and the MN350 the fewest. The VisiSat 2.1 Engineer-ing Guide documents the available number and types of objects in each controller.

Table 3.1: Comparisons of Input/Output Points.

Types of Inputs and Output (I/O) PointsController Type

MN350 MN450 MN550 MN650

Universal Inputs (UIs) - Each separately jumper-config-urable for either resistive/temperature (0-10KΩ), 0 to 10Vdc or digital use.

8 6 10 12

Digital Inputs (DIs) - Dry Contact, equipment status only, capable of responding to one change per controller cycle.

0 0 0 8

Pulse-Counting Digital Inputs (DIs) - Dry Contact, capable of counting up to 10 pulses per second. Note: The actual speed depends on the application cycle time, i.e. how often the pulse input signal is passed to a counter module. Typically this is 2Hz or less.

0 0 2 0

Analogue Outputs (AOs) - 0 to 10Vdc for analogue actu-ator or transducer control (10KΩ minimum input load). 0 3 4 4

Digital (Triac) Outputs (DOs) - Triac outputs for 24Vac. 7 6 6 8Relay Outputs - Relay outputs for switching 230Vac (see warning below). 3 0 6 0

Sensor Link for MN-Sx Sensor. 1 1 1 1

! Warning

Electrical Shock Hazard. Refer to DS 10.151A (MN350) or DS 10.153A (MN550) before wiring the relay outputs.



3.1.5 Networking Objects

In addition to the common control objects, these MicroNet controllers also contain ARCNET transceiver and receiver objects, which can be used wherever needed to transfer data between controllers over the net-work.

3.2 MicroNet 350 Series Controllers

Fig. 3.1: MicroNet 350 Series Controllers.

The MicroNet MN350 controller is available in three models: NCP, ARCNET or LONWORKS (refer to Table 3.2). They are both fully pro-grammable and are designed for roof top, unit ventilator and terminal unit applications.

MN350 controllers have the inputs and outputs shown in Table 3.3.

Table 3.2: MicroNet 350 Series Controllers.

Model Description CommunicationsRTC Card Available

MN350-ARC MicroNet 350 ARCNET Controller ARCNET YesMN350-NCP MicroNet 350 NCP Controller NCP YesMN350-LON MicroNet 350 LON Controller LonWorks Yes

Table 3.3: I/O Points on MicroNet 350 Series Controllers.

Description I/O Points

Universal Inputs (UIs): Each separately jumper-config-urable for analogue (0 to 10Vdc), resistive/temperature (0-10KΩ), or dry contact use

8

Digital (Relay) Outputs (DOs): Relay outputs for switching 230Vac (see warning below).

3

Digital (Triac) Outputs (DOs): Triac Outputs for switch-ing 24Vac (triacs rated at 18VA at 24Vac)

7

Sensor Link for MN-Sx Sensor 1



Electrical and Physical Features

The MicroNet 350 Series Controllers have these features:

• 35mm DIN-rail or wall mounting.

• Compact IP 20 case allows mounting in confined spaces.

• Power can be supplied from 24Vac/24Vdc or 230Vac 50/60Hz power supply.

• Operating temperature range, 0 to 50°C.

• 15Vdc (25mA) supply output for humidity and pressure sensors, DUSF, etc.

• Fixed screw terminal blocks.

• Power failure protection, whereby the controller EEPROM pre-serves memory.


Fig. 3.2: MicroNet 450 Series Controllers.

The MicroNet MN450 controller is available in three models: NCP, ARCNET or LONWORKS (Table 3.4). They are both fully programma-ble and are designed for roof top, unit ventilator, air handling unit (AHU) and central heating and cooling applications.

! Warning

Electrical Shock Hazard. Refer to DS 10.151A (MN350) before wir-ing the relay outputs.

Table 3.4: MicroNet 450 Series Controllers.

Model Description Communications RTC Card Available

MN450-ARC MicroNet 450 ARCNET Controller ARCNET YesMN450-NCP MicroNet 450 NCP Controller NCP YesMN450-LON MicroNet 450 LON Controller LonWorks Yes





The MicroNet 450 Series Controllers have these features:


• Compact IP 20 case allows mounting in confined spaces.

• 24Vac, 50/60Hz power supplied from a transformer, or 24Vdc



• Pluggable screw terminal blocks.



Fig. 3.3: MicroNet MN550 Series Controllers.

The MicroNet MN550 controller is available in four models: NCP, Dual NCP, ARCNET or LONWORKS (Table 3.6). They are both fully pro-grammable and are designed for roof top, unit ventilator, air handling unit (AHU), boiler control, and central heating and cooling applications.

Table 3.5: I/O Points on MicroNet 450 Series Controllers.


Universal Inputs (UIs): Each separately jumper-config-urable for analogue (0 to 10Vdc), resistive/temperature (0 to 10KΩ), or dry contact use

6

Digital Triac Outputs (DOs): Triac outputs for switch-ing 24Vac (triacs rated at 18VA at 24Vac)

6

Analogue Outputs (AOs): 0 to 10Vdc at 1mA 3Sensor Link for MN-Sx Sensor 1





The MicroNet MN550 Series Controllers have these features:


• IP 40 Protection Rating.




• Built-in 5A, 230Vac relays.



Table 3.6: MicroNet MN550 Series Controllers.


MN550-ARC MicroNet 550 ARCNET Controller ARCNET YesMN550-NCP MicroNet 550 NCP Controller NCP YesMN550-XCOM MicroNet 550 Dual-NCP Controller NCP YesMN550-LON MicroNet 550 LON Controller LonWorks Yes

Table 3.7: I/O Points on MicroNet MN550 Series Controllers.


Universal Inputs (UIs): Each separately jumper-config-urable for analogue (0 to 10Vdc), resistive/temperature (0 to 10KΩ), or dry contact use

10

Pulse Count Digital Inputs (Max 10 pulses per control-ler cycle; typically 2)

2

Digital Relay Outputs (DOs): 5A resistive, at 230Vac (see warning below).

6


! Warning

Electrical Shock Hazard. Refer to DS 10.153A (MN550) before wir-ing the relay outputs.




Fig. 3.4: MicroNet MN650 Series Controllers.

The MicroNet MN650 controller is available in four models: NCP, Dual NCP, ARCNET or LONWORKS Table 3.8. They are both fully program-mable and are designed for roof top, unit ventilator, air handling unit (AHU), boiler control, and central heating and cooling applications.



The MicroNet MN650 Series Controllers have these features:


• IP 40 Protection Rating.



Table 3.8: MicroNet MN650 Series Controllers.


MN650-ARC MicroNet 650 ARCNET Controller ARCNET YesMN650-NCP MicroNet 650 NCP Controller NCP YesMN650-XCOM MicroNet 650 Dual-NCP Controller NCP YesMN650-LON MicroNet 650 LON Controller LonWorks Yes

Table 3.9: I/O Points on MicroNet MN650 Series Controllers.


Universal Inputs (UIs): Each separately jumper-config-urable for analogue (0 to 10Vdc), resistive/temperature (0 to 10KΩ) or dry contact use

12

Digital Inputs (DIs) 8Digital Triac Outputs (DOs): Triac outputs for switch-ing 24Vac (18VA at 24Vac)

8



MicroNet System Overview 4 MicroNet LONMARK Controllers

4 MicroNet LONMARK ControllersThis chapter describes the MicroNet LONMARK controllers:

• MicroNet LONMARK 50 Series controllers


• MicroNet LONMARK 110 controller

• MicroNet LONMARK 130 controller



• MicroNet LONMARK VAV Series controllers

4.1 IntroductionThe MicroNet LONMARK controllers are programmable, LONMARK-compliant controllers and feature Sensor Link support for an optional digital wall temperature sensor.

MicroNet LONMARK controllers each have a LONMARK HVAC Func-tional Profile. This profile defines a general application purpose and the controller's LONWORKS 'network image'. The following LONMARK pro-files are used in these controllers:

• Fan Coil Unit (8020)

• Heat Pump (8051)

• Roof Top Unit (8030)

• Satellite (8030)

• Variable Air Volume (8010).

4.1.1 Model Numbers

The two characters at the end of a controller's model number consist of its profile (F = Fan Coil Unit, H = Heat Pump, R = Roof Unit, S = Sat-ellite and V = Variable Air Volume) and profile version number. For example, an MNL-V2RVx model controller has a Variable Air Volume profile (V) and its profile version is 2.


4 MicroNet LONMARK Controllers MicroNet System Overview

4.2 MicroNet LONMARK MNL 50 Series ControllersThe MNL 50 Series LONMARK controllers are programmable, LON-MARK-compliant controllers and have a fixed LONMARK Functional HVAC profile. When loaded with a pre-engineered application from the application library, or programmed using WorkPlace Tech Tool, these controllers provide control for packaged rooftops, heat pumps, fan coils, unit ventilators and similar applications.

MicroNet LONMARK MNL 50 controllers are available in several mod-els (see Table 4.1).

All LONMARK MNL 50 controllers feature Sensor Link (S-LK) support, Light Emitting Diode (LED) indication, screw terminal blocks, one dig-ital input, one universal input and three digital outputs. These control-lers can function in either standalone mode or as part of a LONWORKS FTT-10 Free Topology communications network.

Fig. 4.1: MicroNet LONMARK 50 Series Controller

Note

x denotes the version of the profile. The latest version will be shipped. For further details of these profiles, refer to the Workplace Tech Tool User’s Guide or Workplace Tech Tool Engineering Guide.

AO

SW24H3SW24H2SW24H124H24GGND

UIDI

S-LK/COMS-LK

LON

LON

LONMARK MNL 50 Series Controller

Table 4.1: MicroNet LONMARK 50 Series Controllers.

Model DescriptionLONMARK

Profile Number

MNL-5RFx MicroNet LONMARK MNL 50 Controller with LONMARK Fan Coil Profile

8020

MNL-5RHx MicroNet LONMARK MNL 50 Controller with LONMARK Heat Pump Profile

8051

MNL-5RRx MicroNet LONMARK MNL 50 Controller with LONMARK Roof-top Profile

8030

MNL-5RSx MicroNet LONMARK MNL 50 Controller with LONMARK Satel-lite Profile

8030



The MicroNet LONMARK 50 series controllers are 24Vac powered LONMARK controllers and have the on-board I/O points shown in Table 4.2.


The MNL 50 Series controllers have these features:

• Neuron ® based with FTT-10A Free Topology Transceiver.

• Low voltage, Class 2, 24Vac nominal power supply requirement.

• Onboard LED indication without cover removal.

• Extended operating temperature range, -40 to +60°C.

• Compact size allows mounting in confined spaces.

• Accessible field wiring terminals.

4.3 MicroNet LONMARK MNL 100, 150 and 200 Series Controllers

The MicroNet LONMARK MNL 100, MNL 150 and MNL 200 series controllers are interoperable, LONMARK-compliant controllers and have a fixed LONMARK Functional HVAC profile. When loaded with an application from the application library, or programmed using Work-Place Tech Tool, these controllers provide control for packaged roof-tops, heat pumps, fan coils, unit ventilators and similar applications.

All three feature Sensor Link (S-Link) support, LED indication and screw terminal blocks in addition to DIN rail or wall mounting ability. These controllers can function in either standalone mode or as part of a LONWORKS FTT-10 Free Topology communications network.

Note

x denotes the version of the profile. The latest version will be shipped.

Table 4.2: I/O Points on MicroNet LONMARK 50 Series Controllers.

I/O Points 50 Series

Digital Inputs (DI), Dry Contact Type 1Configurable Universal Inputs (UI):

RTD (1KΩ Balco Input, 1KΩ Platinum Input, 10KΩ Thermistor w/11KΩ Shunt Resistor, 10K Resistance 0 to 10.5KΩ),

0 to 5Vdc, 0 to 20mA and Dry Contact Digital Input

1

Digital Relay Outputs (DO), 24VA at 24Vac, Pilot Duty 3Sensor Link for MN-Sx Sensor 1



MicroNet LONMARK MNL 100, 150 and 200 series controllers are available in several models (Table 4.3 to Table 4.5).

The MNL 100, MNL 150 and MNL 200 series controllers use the same physical packaging but differ in the onboard I/O points they provide (see Table 4.6).

Fig. 4.2: MicroNet LONMARK MNL 100, MNL 150 and MNL 200 Series Controllers.

MNL 100 Controller MNL 200 ControllerMNL 150 Controller



Profile Number

MNL-10RFx MicroNet LONMARK MNL 100 Controller with LONMARK Fan Coil Profile.

8020

MNL-10RHx MicroNet LONMARK MNL 100 Controller with LONMARK Heat Pump Profile.

8051

MNL-10RRx MicroNet LONMARK MNL 100 Controller with LONMARK Rooftop Profile.

8030

MNL-10RSx MicroNet LONMARK MNL 100 Controller with LONMARK Satellite Profile.

8030



Profile Number


8020


8051


8030


8030



.


The MNL 100, MNL 150 and MNL 200 Series controllers have these features:

• Neuron ® based with FTT-10A Free Topology Transceiver.


• Wiring sub-base with screw terminal blocks and plug-in electron-ics.



Profile Number


8020


8051


8030


8030

Note


Table 4.6: I/O Points on MicroNet LONMARK MNL 100, 150 and 200 Series Controllers.

I/O Points100

Series150

Series200

Series

Digital Inputs (DI), Dry Contact Type 1 0 2Configurable Universal Inputs (UI): RTD (1KΩ Balco Input, 1KΩ Platinum Input, 10KΩ Thermistor w/11KΩ Shunt Resistor, 1KΩ Resistance 0 to 1.5KΩ, 10K Resistance 0 to 10.5KΩ),

0 to 5Vdc, 0 to 20mA and Dry Contact Digi-tal Input

2 3 3

Digital Relay Outputs (DO), 24VA at 24Vac, Pilot Duty 4 2 6

Analogue Outputs (AO), 0 to 20mA 0 2 2Sensor Link for MN-Sx Sensor 1 1 1





• 35mm DIN rail or wall mounting.


4.4 MicroNet LONMARK MNL 110 and 130 Controllers

The MicroNet MNL 110 and MNL 130 controllers are interoperable, LONMARK-compliant controllers. When programmed using WorkPlace Tech Tool, these controllers provide control for fan coil and unit venti-lator applications.

Both controllers feature screw terminal blocks in addition to DIN rail or wall mounting ability (within a suitable earthed metal enclosure). They also have three universal inputs, software configured to respond to one of five input types (one (MNL 110) or three (MNL 130) high-voltage relay output(s) and four 24Vac Triacs (digital outputs) and an S-Link interface for connection to an optional S-Link sensor. These controllers can function in either standalone mode or as part of a LONWORKS FTT-10 Free Topology communications network.

MicroNet MN 110 and MNL 130 controllers are shown in Table 4.7. The MN 110 and MN 130 controllers use the same physical packaging but differ in the onboard I/O points they provide (Table 4.8).

Fig. 4.3: MicroNet LONMARK MNL 110 and MNL 130 Controllers

MNL 110 Controller MNL 130 Controller

DO

124VA

CD

O2

DO

324VA

CD

O4

?

DO

5C

5

DO

6C

6

DO

7C

7

GN

D0V

24VAC

UI3

CO

M 0V

UI2

CO

M 0V

UI1

S-LK

S-LK

LON

LON

SRVC

RECV

XMIT

J1

SR

VC

DO

124VA

CD

O2

DO

324VA

CD

O4

DO

5C

5

GN

D0V

24VAC

UI3

CO

M 0V

UI2

CO

M 0V

UI1

S-LK

S-LK

LON

LON

SRVC

RECV

XMIT

J1

SR

VC

Table 4.7: MicroNet LONMARK 110 and 130 Controllers.


Profile Number

MNL-11RFx MicroNet LONMARK MNL 110 Controller with LONMARK Fan Coil Profile and One High Voltage Relay

8020

MNL-13RFx MicroNet LONMARK MNL 130 Controller with LONMARK Fan Coil Profile and Three High Voltage Relays

8020




The MNL 110 and MNL 130 controllers have these features:

• FTT-10A Free Topology communications network.

• Capability to function in standalone mode or as part of a LON-WORKS network.

• LONMARK compliant, using the LONMARK Fan Coil Profile 8020 for interoperability.

• Four 24Vac Triac outputs.

• Built-in LON jack, for connection to a LON network.




• 35mm DIN rail or panel mounting.


Note


Table 4.8: I/O Points on MicroNet LONMARK 110 and 130 Controllers.

I/O Points MNL 110 MNL 130

Configurable Universal Inputs (UI): RTD (1KΩ Resistance 0 to 1.5KΩ, 1KΩ Balco Input, 1KΩ Platinum Input, 10KΩ Thermistor with 11KΩ shunt resistor, 10K Resistance 0 to 10.5KΩ),

0 to 5Vdc, 4 to 20mA and Dry Contact Digital Input

3 3

Digital Triac Outputs (DO), 12VA at 24Vac (Max. 12VA Total, DO1 - DO4) 4 4

High Voltage Relay Outputs, 230Vac at 3A 1 3

Sensor Link for MN-Sx Sensor 1 1

! Warning

The MNL 110 and MNL 130 controllers are not suitable for exposed mounting on a wall or panel, or in any other easily accessible place due to the possibility of personal contact with the high voltage terminals. They must be mounted in a suitable earthed metal enclosure.



4.5 MicroNet LONMARK VAV Series ControllersThe three MicroNet LONMARK VAV (Variable Air Volume) Series Controllers are interoperable, LONMARK-compliant controllers. The model types are given in Table 4.9.

When programmed using WorkPlace Tech Tool, they provide a wide range of control strategies for cooling and reheat applications. All three models feature an integral patented differential pressure transducer, Sensor Link (S-Link) support and LED indication.

In addition, the MNL-V1RVx and MNL-V2RVx models provide an integral actuator with manual override and over-the-shaft damper mounting. The MNL-V3RVx model has two triac outputs for interface with an external actuator. All three models feature different combina-tions of inputs and outputs to suit a variety of applications Table 4.10 and a variety of control strategies are available Table 4.11. These con-trollers can function either in a standalone mode or as part of a LON-WORKS FTT-10 Free Topology communications network.

Fig. 4.4: MicroNet LONMARK VAV Series Controllers

AO

SW24H3SW24H2SW24H124H24GGND

UI

COM

DIS-LK/COM

S-LK

LON

LON

OPEN24G

CLOSE24G

AO

MNL-V1RVx MNL-V2RVx MNL-V3RVx

Table 4.9: MicroNet LONMARK VAV Series Controllers.


Profile Number

MNL-V1RVx VAV terminal box control. Controller has integral actuator and pressure transducer.

8020

MNL-V2RVx VAV terminal box control and various forms of reheat, series fan pow-ered, and parallel fan. Controller has integral actuator and pressure transducer.

8051

MNL-V3RVx VAV terminal box control. Controller has triac outputs for use with an external actuator.

8030

Note





The MicroNet LONMARK VAV Series Controllers have these features:

• 3150 Neuron based with FTT-10A Free Topology Transceiver.

• Low voltage, Class 2; 24Vac, 50 to 60Hz nominal power supply requirement.

• MNL-V1RVx and MNL-V2RVx models feature integral actuator with over-the-shaft damper mounting.

• IP 20 rated enclosure conforms to NEMA-1 requirements.


• Integral pressure transducer.

Table 4.10: I/O Points on MicroNet LONMARK VAV Series Controllers.

I/O PointsModels

MNL-V1RVx

MNL-V2RVx

MNL-V3RVx

Digital Inputs (DI), Dry Contact Type 1 1 1Universal Inputs (UI): RTD (1KΩ Balco Input, 1KΩ Platinum Input, 10KΩ Thermistor, 1KΩ Resistance 0 to 1.5KΩ, 10KΩ Resistance 0 to 10.5KΩ), 0 to 5Vdc, 0 to 20mA, and Dry Contact Digital Input

1 1 1

Digital Outputs (DO), 24VA at 24Vac, Pilot Duty 0 3 3Analogue Outputs (AO), 0 to 20mA 0 1 1Triac Outputs, 18VA (0.75A) each Output at 24Vac. Total of 18VA for both outputs. 0 0 2

Table 4.11: Control Strategies for MicroNet LONMARK VAV Series Controllers.

Model Box Configuration Reheat Type Other

MNL-V1RVx • Cooling

• None

• None • None


• Series Fan

• Induction

• Parallel Fan

• Staged Electric Reheat

• Floating/Proportional Hydronic Reheat

• Time Proportioned

• None

• Occupancy

• Satellitea


• Series Fan

• Induction

• Parallel Fana. Available control strategies depend on controller I/O.


MicroNet System Overview 5 MicroNet Interface Devices

5 MicroNet Interface DevicesThis chapter describes the following MicroNet interface devices:

• MicroNet Manager Interface (MN MI)

• MicroNet Touch Screen and LON Touch Screen

• MicroNet LCD device

5.1 MicroNet Manager Interface

Fig. 5.1: MicroNet Manager Interface (MN MI)

The MN MI provides the network-level management functions for a network of ARCNET or NCP MicroNet controllers and Touch Screens.

An RS 232 port on the MN MI provides a connection to a PC running the VisiSat Configuration Tool or MicroNet View software, or to a modem for remote access. A second RS 232 port can be used for an additional connection to the VisiSat Configuration Tool when the pri-mary port is occupied by the modem.

The MN MI is also capable of programmable alarm polling and data logging via the MicroNet View software. MN MI polling is able to track 'points' among controllers on the network, both for local log storage and alarm detection. Refer to the MicroNet View Engineering Guide for fur-ther information.

The MN MI features password protection to stop unauthorized comput-ers from interrogating remote sites.

The MN MI features a built-in RTC that can be used for network time synchronization. A Lithium battery provides backup power for the RTC for up to 350 days if external power is lost.

Refer to Page 14 for further information and examples of use.


5 MicroNet Interface Devices MicroNet System Overview


The MN MI has these features:


• 24Vac, 50/60Hz power supplied from transformer.


• Two 9-pin RS 232 port for connection to a modem or a PC, sup-porting communications speed 38.4k baud.

• Built-in RTC with battery backup. Maintains system time for up to 350 days.


Modems

When an MN MI communicates via modem, US Robotics brand auto-matic-switching modems (such as the 56K Fax Modem Model #5630) are recommended. This brand of modem has been tested and found to work satisfactorily with the MicroNet system. Other modem brands that are capable of transferring data at 9600 baud and higher may also func-tion properly. If you wish to use another brand of modem, please contact your local sales office for the latest information on approved models.

5.2 MicroNet Touch Screen

Fig. 5.2: MicroNet Touch Screen Display

The MicroNet Touch Screen contains a graphical LCD that allows a user to view and configure parameter values for multiple controllers on a network.

The standard Touch Screen is available for use on NCP networks but can easily be converted to work on ARCNET communications net-works with the use of an optional plug-in card. A separate LON Touch Screen is available for LONWORKS networks.

Table 5.1: MN MI

Model Description Communications On-board RTC

MN50-MI-ARC MicroNet ARCNET Interface ARCNET YesMN50-MI-NCP MicroNet NCP Interface NCP Yes

Touch Screen (Panel-Mount Version)

Touch Screen (Wall-Mount Version)



The Touch Screen is available as a panel-mount device, or can be wall mounted using the MN-DK kit. The Touch Screen (MN50-TS-NCP only) can also be mounted in an NCP networked MN550 or MN650 controller (MN550-NCP or MN650-NCP respectively).

The touch-sensitive keypad works easily with the screen's intuitive graphical representation of common control parameters. The display, whose characteristics are configured from the VisiSat Configuration Tool, shows a series of 16 subscreens, each of which gives access to controller parameters (16 parameters per subscreen for NCP and ARC-NET Touch Screens, or 8 parameters per subscreen for LONWORKS Touch Screens). LONWORKS Touch Screens also have built-in holiday and time schedules.

Controller data can also be configured to cause alarm indications on the Touch Screen.

Fig. 5.3 shows the basic features of the Touch Screen, together with a default screen. Fig. 5.4 shows how a trend may be displayed.

Refer to Page 18 for further details of the Touch Screen and examples of use.

Table 5.2: MicroNet Touch Screen Display.

Model Description CommunicationsOn-

board RTC

MN50-TS-NCP MicroNet NCP Touch Screen Display (Wall or Controller Mounting)

NCP Yes

MN50-TSP-NCP MicroNet NCP Touch Screen Display (Panel Mounting)

NCP Yes

MN50-TS-ARC MicroNet ARCNET Touch Screen Display (Wall Mounting)

ARCNET Yes

MN50-TSP-ARC MicroNet ARCNET Touch Screen Display (Panel Mounting)

ARCNET Yes

MNL-TS-100 MicroNet LONWORKS Touch Screen Display (Wall Mounting)

LONWORKS Yes

MNL-TSP-100 MicroNet LONWORKS Touch Screen Display (Panel Mounting)

LONWORKS Yes



-

s.

or

ESC

0 1 2 3 4 5 6 7 8 9

FAN

70TMP

72RMT BLR

38OAT

75RAT

EXH

PMP

Fig. 5.3: Touch Screen Display Features

Sample Display (Default Screen)

Numeric KeysUsed to enter numeric value

Escape Key - Moves the display back one level.

Backspace Key - Deletes unwanted entries.

Minus Key - Used with numeric keys to enter negative values.

Next Screen or Move Key - Moves display up one level.

Enter Key - Enters and confirms settings.

ESC

0 1 2 3 4 5 6 7 8 9Water Temp

10

LOG

50

9.4

16:14:2303/16

Fig. 5.4: Sample Touch Screen Display Showing a Log Data Graph

Short Text

MaximumCursor

Time Sample Display (Log Data Graph)

Day/MonthMonth/Day

Value Indicator

State Indicator

Minimum Long Text




The MicroNet Touch Screen has these features:

• Both panel-mount and wall-mount (35mm DIN-rail) models are available.

• The MN50-TS-NCP model can be mounted on an MN550-NCP or MN650-NCP controller.

• Back-lighted graphic LCD with an intuitive, graphics-based menu system.


• Built-in RTC with battery backup, to preserve the system time for up to 350 days if external power is lost.

• Screen configuration is saved on EEPROM, providing protection from power failure.



5.3 MicroNet LCD

Fig. 5.5: MicroNet LCD

The MicroNet LCD can connect to a single MN550 or MN650 control-ler on an NCP, ARCNET or LONWORKS network. It can also connect to any NCP controller (MN350, 450, 550 or 650) controller, providing the controller is not networked. If the LCD is attached to a networked NCP controller, it must be the MN550-XCOM or MN650-XCOM variant, and if attached to a networked ARCNET controller, it must be the MN550-ARC or MN650-ARC variant. The LCD contains a liquid-crys-tal display that gives a text, menu-driven interface for viewing or chang-ing the current behaviour of the controller to which it is connected.

The MN LCD model has a built-in real-time clock (RTC) to provide time setting and synchronization for a stand-alone controller. It can also be used for network time synchronization across a LONWORKS network.

The display parameters are configured using the VisiSat Configuration Tool. The display configuration is downloaded to the MN550 or MN650 controller, from where it can be uploaded to the MN LCD.

MN50-LCDP (Panel-Mount Version)

MN50-LCD (Wall-Mount Version)



The MN LCD is available as a panel-mount device, or can be wall mounted using the MN-DK kit. The MN LCD can also be mounted in a stand-alone NCP MN550 or MN650 controller.

Refer to Page 20 for further details of the LCD and examples of use.


The MN LCD has these features:

• Both panel-mount and wall-mount (35mm DIN-rail) models are available.

• Can be mounted on MN550 or MN650 controllers using the sup-plied ribbon cable.

• Clear, high contrast LCD with a text-based menu system.


• Built-in RTC with battery backup, to preserve the system time for up to 350 days if external power is lost.

• Screen configuration is saved on EEPROM, providing protection from power failure.



Table 5.3: MicroNet LCD.

Model Description CommunicationsOn-

board RTC

MN50-LCD MicroNet LCD (Controller or Wall Mounting) Point-to-Point NCP YesMN50-LCDP MicroNet LCD (Panel Mounting) Point-to-Point NCP Yes


MicroNet System Overview 6 Software Interfaces

6 Software InterfacesMicroNet Systems can use the following software programs:

• MicroNet View - A graphical user interface

• VisiSat Configuration Tool - An engineering tool

• XBuilder - A configuration tool for TAC Xenta 555

• WorkPlace Tech Tool - An engineering tool

• Flow Balance Software - An engineering tool for VAV controllers

• Third-Party Network Management Tools - Engineering tools for LONWORKS networks.

• MicroNet Remote Alarm Manager - An alarm management tool

It is also possible to monitor and control MicroNet equipment using TAC Vista Workstation via the TAC Xenta 555.

6.1 MicroNet ViewMicroNet View (MN View) comprises a suite of software programs that provide an intuitive, graphical interface for network-level supervisory and control functions. MicroNet View can be used with any of the MicroNet network options (LONWORKS, NCP and ARCNET) and is able to control multiple sites, including remote sites accessed via modem.

At the heart of the MicroNet View system are the WindowMaker and WindowViewer applications. WindowMaker is used for the design of dynamic views of network operations. The WindowViewer application (see Fig. 6.1) enables the real-time data gathered from controllers to be displayed in the windows designed in WindowMaker.

MicroNet View includes ActiveX® controls, such as the Alarm Man-ager (see Fig. 6.2), which gives the ability to set up, manage and acknowledge alarm conditions, including the viewing of alarm instruc-tions and history. The MicroNet View Logging ActiveX control con-troller data to be logged and viewed.

Communication with controllers is achieved using I/O-Servers. The NCP/ARCNET I/O-Server is available for communication with NCP/ARCNET controllers, and the LNS DDE I/O-Server is a third-party product for communication with LONWORKS networks.


6 Software Interfaces MicroNet System Overview

For improved performance, MicroNet View is able to distribute the tasks of alarm checking and data logging to an MN MI at the head of an NCP or ARCNET network. MicroNet View can also be connected to SatchNet networking products (IAC 420, 600 and Touch Screen) via the SatchNet I/O server.

Fig. 6.1: MicroNet View - Monitoring and Controlling a Control Scheme in WindowViewer

Fig. 6.2: MicroNet View Alarm Manager

Alarm conditions are shown in this area



Fig. 6.3: MicroNet View Connectivity

6.2 MicroNet View Functions

6.2.1 MicroNet View

Time Scheduling

User can easily change the controller's time schedule entries using a graphical ActiveX component.

Holiday Scheduling

Holiday Schedule ActiveX enables modification of the holiday sched-ule objects in the controller.

Compensation Curve Adjustment

Look-up-table ActiveX modification of the look-up-table objects in the controller.

PSTN

MicroNet View MicroNet View

Ethernet 10 Mbps/100 Mbps

MicroNet View

Central Alarm Database I/O-servers

Connection to

DMS Network 8000 LON Chillers Lifts Boilers Access Control Fire

Controller network e.g. NCP, ARCNET, Satchnet

Controller network e.g. NCP, ARCNET, Satchnet



Alarm Handler

User may define two types of alarms, analogue and digital point alarms sent from the MN MI and MicroNet controllers. Alarm points can be allocated to different alarm groups, and different priorities can be assigned to them.

Logging Management

Direct, individual real time data sampling and gathering of data resident in the MN MI is supported. Logging viewing is available through a log-ging viewing module. Automatic retrieval and storage of analogue val-ues and digital states from MicroNet programmable controllers from local and remote sites are supported.

Control Performance Optimization

ActiveX components allow easy optimization of the control perfor-mance.

Monitor Tool

Designed for each configuration of alarms and data logs on both local and remote sites. The Monitor Tool provides very extensive options for alarm management and data logging and integrates seamlessly with SPI (GSM/Pager Interface) for alarm remote transmission to pagers, mobile phones, remote faxes and for e-mailing the alarms.

6.2.2 MicroNet View Pro

MicroNet View Pro includes all the features described above, plus the additional features offered by MicroNet View WindowMaker:

Screen Design

Monitoring screens may be designed for maximum effectiveness using a variety of embedded third-party graphics and drawings. Screens can be tested before use with live data.

Object-Oriented Graphics

Objects and groups of objects can be moved, sized, and animated more quickly and simply than bit-mapped graphics. The object-oriented design tools enable the user to draw, arrange, align, layer, space, rotate, invert, duplicate, cut, copy, paste, erase and more.

Script Editor

MicroNet View provides extensive scripting capability for rapid proto-typing, background calculations and simulation.

Script Functions

Script functions support logical and mathematical expressions. Users can display single-precision floating-point numbers, while internal cal-culations use double-precision floating-point numbers.



Wizards and ActiveX Controls

MicroNet View Pro includes a library of Wizards and ActiveX compo-nents, which are pre-configured complex objects that users can modify and duplicate freely. Frequently used Wizards and ActiveX controls can be added to the Toolbox for even easier access during the application development. The ActiveX component library includes support for the MicroNet controller Look-up-table, Time Schedule, Holiday Schedule, Optimiser and Cascade objects.

Animation Links

Animation links may be combined to provide complex size, colour, movement, and/or position changes.

6.3 VisiSat Configuration ToolVisiSat is a PC-based engineering program for configuring and down-loading applications to MicroNet MN350, 450, 550 and 650 controllers on an NCP, ARCNET or LONWORKS network. It is also able to config-ure MicroNet Touch Screen, MN LCD and MN MI devices.

It uses a Visio® 32-bit drawing interface for graphic representation of control applications and control objects. As a Visio-based engineering interface, VisiSat ensures that control logic engineering is always doc-umented.

VisiSat enables an engineer to place down and connect graphical sym-bols representing the control objects in a graphical Computer-Aided Design (CAD) environment known as 'Bubbleland', as shown in Fig. 6.4. Designing the control scheme for a controller in Bubbleland is similar to designing a conventional circuit diagram - the engineer places objects from a standard library into the drawing, then connects them together.

VisiSat contains a comprehensive library of objects, including objects to access the controller inputs and outputs, logic objects, maths objects and other objects designed specifically for use in HVAC systems.

Controller engineering in VisiSat is typically created in the offline mode (i.e. not necessarily when the VisiSat PC is connected to the network). Once the engineering work in VisiSat is complete, an engineer can visit the site and connect the VisiSat PC to the network to download the engi-

Note

For further information about MicroNet View, refer to the MicroNet View Engineering Guide.

Note

Visisat 2.1 or later is required to configure MN 50 Series devices.



neered applications to each controller. Configuration can also be carried out via modem for NCP and ARCNET networks.

VisiSat is normally used on a laptop PC, since it is normally necessary for VisiSat to connect to controllers only during system setup and com-missioning.

Fig. 6.4: VisiSat Bubbleland Drawing

6.3.1 Connecting VisiSat to a Network

There are several alternative methods of connecting a VisiSat PC to the controller network, depending on network type:

• NCP and ARCNET networks — By using an MN MI, as shown in Fig. 6.5.

• NCP networks — By using an RS232-to-RS485 converter, as shown in Fig. 6.6.

• ARCNET networks — By using an ARCNET card in the PC to make a direct connection to the ARCNET network.

• LONWORKS networks — By using a LonTalk ® card in the PC to make a direct connection to the LONWORKS network.

Object library



Fig. 6.5: VisiSat Configuration Tool Connectivity to NCP/ARCNET Network

Fig. 6.6: VisiSat Connection Via RS 232 to RS 484 Converter

Fig. 6.7: VisiSat Configuration Tool Connectivity to LONWORKS Network

Network

VisiSat PC

Connection via RS 232 Port. (Not used to connect to LONWORKS networks).

MN650 Controller

MN350 Controller

MN450 Controller

MN-Sx Sensor


Other MicroNet Controllers (MN350, 450, 550, 650)

MN LCD

Controller (MN450-NCP shown)

RS 232

DUSF MicroNet Sensor

VisiSat PC

An RS 232 to RS 485 converter can be used to connect the PC temporarily to an NCP controller or network.

Converter (LIB-4-485 or MA-44)

Controller (MN450-LON shown)

DUSF MicroNet Sensor

VisiSat PC

Direct connection using LONTALK PC card



6.4 XBuilderXBuilder is the programming tool for the TAC Xenta 555. It enables the monitoring and control of a MicroNet building management system over the Internet or through a company's intranet, using Internet Explorer.

XBuilder is used to create projects, each project comprising a number of web pages containing graphics, signal object values, MicroNet time and holiday schedules and optimiser time schedules. The web pages can be configured to represent different parts of the building management scheme.

Fig. 6.8: The XBuilder interface

The XBuilder interface (Fig. 6.8) comprises:

• A System pane in which the hierarchical structure of the web-based scheme is built. This is usually mapped to the building(s) controlled by MicroNet.

• A Network pane which contains a representation of the monitored MicroNet network, containing controllers, management devices and point signals. This representation is derived from an imported XML file which is generated in the VisiSat Points Gallery by the configuration engineer. Once the XML file has been imported, the network is fixed in XBuilder and any further network changes required must be changed in VisiSat and a new XML file must be imported.

• A Properties pane which displays the parameters of items selected in the System or Network panes.



When the basic web page structure of the Xenta 555 web server has been built in the System pane, point signals can be dragged and dropped from the Network pane to the web pages on the System pane. This pro-vides the web pages with dynamic values, e.g. a Temp Input object in a MicroNet controller which has been dropped into a ‘values’ web page will be seen to be varying in temperature when the Xenta 555 is accessed via a web browser.

For further details of the XBuilder software, refer to the following doc-umentation:

• TAC XBuilder Data Sheet - 03-00040-01-en

• TAC Xenta Server Technical Manual - 04-00051-01-en

• TAC Xenta 555 Supplement Manual - 04-00054-01-en

• TAC Xenta 555 Operating Manual - 04-00044-01-en.

6.5 WorkPlace Tech ToolThe WorkPlace Tech Tool (WP Tech, part number WP-TECH-CD-E-32) is a PC-based software tool used to program, compile and download a control application to an MNL 50, 100, 110, 130, 150, 200 or VAV controller.

In a similar manner to VisiSat, WP Tech uses a Visio 32-bit drawing interface to represent each application as a control logic drawing. WP Tech uses unique shapes for control objects and 'connection wires' to define the logic and flow of data in an application.



Fig. 6.9: A WP Tech Application

6.5.1 Application Creation and Modification

Application creation and modification can be carried out offline, with each application based on a special WP Tech (Visio) template. As each controller is fully programmable, fully-custom control applications are possible.

• A library of pre-engineered applications is also available on an Applications CD, currently part number MNCD-APPS-100. Application CDs are obtained on request by contacting your local sales office. Note these same pre-engineered applications are also available for download in a 'zipped' format. Download access is password-protected.

6.6 MicroNet VAV Flow Balance SoftwareThe MicroNet Flow Balance software is used to air balance terminal boxes controlled by MicroNet LONMARK VAV controllers.

The MicroNet LONMARK VAV controllers are interoperable, LON-MARK-compliant devices that provide a wide range of control strategies for pressure independent terminal boxes with, or without, reheat capa-bilities.



6.7 LON Network Management ToolsOnce the VisiSat or WorkPlace Tech Tool scheme is complete, a net-work management tool is required to make bindings between the SNVTs in the different nodes (controllers and other devices) on the net-work. This ensures that the data transmitted by one node is received at the correct nodes on the network. Network management tools can also be used to modify external configuration parameters of a node.

One of the most widely used network management tools is Echelon's program called 'LonMakerTM for Windows' that provides a graphical representation of a LONWORKS network. It provides functions for node installation, network variable binding and network variable browsing in a client/server architecture.

6.8 MicroNet Remote Alarm ManagerThe Remote Alarm Manager collects and displays alarms from Micro-Net View, distributes those alarms as messages to the relevant person or device and allows remote message acceptance (Fig. 6.10).

Fig. 6.10: Remote Alarm Manager (simplified)

Alarm messages can be distributed in a variety of different forms, such as fax messages, printed output, emails or WAP or text messages to mobile phones. The content of messages can be customized, and can be different for different recipients.

Web browser

Accept/Refuse

MicroNet Controller Network

Remote Alarm Manager

MicroNet View

Alarms

Alarm Messages: contents can be customized by recipient type

Simultaneous or sequential routing depending on alarm priority/type

Fax machinePrinter Mobile phone

Remote Alarm Manager can be on same PC as MN View



Once delivered, alarms can be acknowledged and alarm messages accepted/refused remotely (depending on configuration).

Alarm messages can be routed to different recipients or devices depend-ing on factors such as alarm priority and type of alarm. Alarm messages can be routed simultaneously to everyone in a call list, or in rotation until one person in the list accepts the alarm. In addition, duty rosters can be set up to specify the recipients or devices that are to receive alarm messages during specified periods of the week.

To guarantee successful transmission, alarm messages can be set up to require acceptance from a recipient. Acceptance can be carried out from the Remote Alarm Manager Console (the main user interface), from a GSM or WAP-enabled mobile phone, by email, or from a Web browser over the Internet. Accepting an alarm message can automatically cause the alarm to be acknowledged in the Active Alarms area of the Remote Alarm Manager and can also cause that acknowledgement to be passed through to MicroNet View.

Typically, the Remote Alarm Manager is installed on the same PC as MicroNet View, although the system supports full client/server net-works, where different components of the system can be installed on different computers.

6.9 TAC Vista WorkstationVista Workstation can communicate with MicroNet via the Xenta Server 555. The TAC Vista Server includes Xenta communications for transferring signals and information between the TAC Vista building management system and Xenta devices on the ethernet.

After adding Xenta Server 555 objects and their associated XBuilder projects to Vista’s database, the Vista Workstation can be used to mon-itor and control MicroNet equipment. Any signals, alarms, time sched-ules, web pages, trend logs, graphics and event logs configured in XBuilder projects are then available in Vista.

For further information about TAC Vista, please refer to TAC ExchangeOnline at http://extranet.tac.com/.


MicroNet System Overview 7 Glossary

7 Glossary

Term Definition

AO Analogue Output, a controller output used to proportionally control (modulate) a damper or valve actuator, or some other device.

Application Essentially, an application is the re-usable control logic contained in a controller. A con-troller stores control logic as algorithms acted on by its program (the executable code in the controller). In VisiSat and WorkPlace Tech Tool, we know an application as a Visio draw-ing file, which contains pages showing the application's modifiable properties, a graphi-cal representation of the control logic, and other drawing pages that define its implemen-tation. Each MicroNet controller uses the con-trol logic in a single application for control of a particular type of HVAC equipment, for example, a heat pump or fan coil unit.

Application Library

An application library is a collection of appli-cations. In VisiSat and WorkPlace Tech Tool, application libraries consist of Visio template files, each having a collection of drawing pages and information that can be copied, modified as required, and stored as an applica-tion.

ARCNET A high-performance, peer-to-peer communi-cations protocol that may be used when an open communications standard is not neces-sary.

Bindings Data connections that allow network data sharing.

Connectivity The ability of a device to use a standardized method of communications, both physically (media connection) and logically (protocol implementation). LONWORKS provides both.


7 Glossary MicroNet System Overview

Control Logic The control algorithms performed by a con-troller. For each application, control logic is graphically represented in VisiSat and Work-Place Tech Tool as interconnected elemental control objects on Visio drawing pages.

Control Object An elemental object used with other control objects to provide a control application in an MicroNet controller. Each control object typi-cally has configuration properties, input prop-erties, and output properties.

DI Digital Input. A physical input point on an MicroNet controller compatible with a two-state field contact (open/close contact).

Digital I/O Controller inputs and outputs that have only two states, such as Open/Closed.

DIN Rail Also 'DIN track', is an extruded metal rail that allows a standardized 'snap-on' method for mounting of relays and other control modules. An MicroNet controller can be mounted on a standard 35mm DIN rail.

Drawing The method of application storage in Micro-Net Tech Tool, with each application saved as a Visio drawing file (.VSD) having multiple drawing pages.

Echelon The corporation that developed and supports LONWORKS technology, and continues to pro-mote interoperability through the LONMARK Program.

Folders Synonymous with directories and subdirecto-ries in Windows. WorkPlace Tech Tool stores each project in its own folder, which may con-tain one or more applications (files).

Free Topology Describes the FTT LONWORKS network topol-ogy that allows any combination of multiple wiring trees, stars, loops, or bus to intercon-nect nodes on the same wiring segment. Free Topology provides great flexibility when installing or modifying LONWORKS wiring.

Term Definition



FTT-10 Free Topology Transceiver. MicroNet control-lers have an FTT-10A transceiver module for connection to a twisted-pair, polarity-insensi-tive LONWORKS network. The '10' in this term indicates a 10MHz input clock rate for the Neuron. An FTT LONWORKS network can use either a Free Topology or a Doubly Termi-nated Bus Topology.

Interoperability The ability of multiple vendors' products to be integrated into one flexible system without using custom integration products. There are varying degrees of interoperability.

LONMARK Is a logo signifying that a product has met LONMARK guidelines that allow it to interop-erate with other LONMARK-compliant prod-ucts on a LONWORKS network.

LONMARK Pro-file

A special class of LONMARK Object that defines both a functional purpose and a stan-dardized 'network image' to allow a device to share data and control on a LONWORKS net-work. A profile has a defined collection of input and output 'data slots' and configuration properties. Some example HVAC profiles are for a roof top unit, heat pump, or fan coil unit. Profiles provide the highest class of interoper-ability.

LonTalk Echelon's open-architecture communications protocol used by all LONWORKS-based devices.

LONWORKS The collective hardware and software technol-ogy developed by Echelon to provide an open communications network for control devices.

LONWORKS Network

A peer-to-peer network of LONWORKS-based control devices. MicroNet controllers can be connected to a LONWORKS network with other nodes having FTT-10A (or LPT-10) transceiv-ers, using low-cost, unscreened, twisted-pair cabling. In this context, also called an FTT LONWORKS network.

NCP Native Communications Protocol. A commu-nications protocol that may be used when nei-ther an open communications standard nor a peer-to-peer network is necessary.

Term Definition



Neuron (Neuron Chip). The Echelon-developed core component of any LONWORKS node, contain-ing internal processors and the LonTalk com-munications protocol.

Neuron Identifi-cation Number

The 48-bit identification number factory-assigned to the Neuron used in every LON-WORKS-based node. Neuron IDs are used in the MicroNet Tech Tool and VisiSat as a means of identifying a target controller to receive an application download.

Node Device, meaning any LONWORKS-based device containing a Neuron and transceiver that is connected to a LONWORKS network. Each MicroNet LONMARK or LONWORKS controller can be a node, along with any LON-WORKS-based sensor, actuator, or other device (such as a PC with an Echelon LonTalk adapter).

Object When creating or modifying a project drawing in the VisiSat or WorkPlace Tech Tool, objects are shapes, representing entities, that are taken from a stencil then connected to each other. Examples include primitive control objects and controller objects.

Open Protocol An open-architecture communications proto-col, such as LonTalk, that allows conforming devices from different manufacturers to com-municate with each other.

Peer-to-Peer A method of direct communications among networked devices without a central host device or system. Nodes on a LONWORKS or ARCNET network communicate in a peer-to-peer fashion.

Profile See LONMARK Profile.Project One or more applications in WorkPlace Tech

Tool, typically associated with a particular job. Each project is a folder (subdirectory) used to store the applications.

S-Link Sensor Link. The twisted-pair, polarity-insen-sitive connection between an MicroNet con-troller and an MicroNet S-Link sensor. The S-Link powers and enables the MicroNet sensor.

Stencil An associated collection of Visio master shapes that can be individually copied onto a Visio drawing.

Term Definition



Sub-LAN A sub-network within an NCP or ARCNET network.

TAC Vista TAC Vista is an advanced building manage-ment system. TAC Vista monitors, controls and supervises systems for lighting, heating, ventilation, climate control and access/se-curity in all types of premises and buildings.

UI Universal Input. Used to describe the ana-logue inputs on MicroNet controllers, which can be used with temperature sensors (1KΩ Balco, 1KΩ Platinum, or 10KΩ thermistor), 0 to 5Vdc and 0 to 20mA analogue devices, or digital sensing of dry contacts.

VAV Variable air volume. A system that controls space temperature by varying the quantity of supply air rather than by varying the tempera-ture of the supply air.

Visio The product name of the popular drawing application from the Microsoft Corporation. TAC Satchwell uses Visio as the user interface to VisiSat, allowing graphical representations of applications.

XBuilder The software tool used to create projects in the Xenta 555 server.

Xenta A range of TAC LON controllers.XIF File A file within a LONMARK device that

describes the device's network-accessible inputs, outputs, and configuration data.

XML File In this context, a file which represents a MicroNet network (when imported into an XBuilder project).

Term Definition


Copyright © 2007, TACAll brand names, trademarks and registered trademarksare the property of their respective owners. Informationcontained within this document is subject to changewithout notice. All rights reserved.

306387400_A3

TAC HeadquartersMalmö, Sweden+46 40 38 68 50

Satchwell Helpline+44 (0) 1753 [email protected]

www.tac.com

micronetmicronet.com.ua/data/data-support/system/micronet... · micronet components include...

Documents