tac xenta 555 - community.exchange.se.com

TAC Xenta 555Supplement Manual

Copyright © 2006 TAC AB. All rights reserved.

This document, as well as the product it refers to, is only intended for licensed users. TAC AB owns the copyright of this document and reserves the right to make changes, additions or deletions. TAC AB 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 AB, 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 Xenta 555, Supplement Manual Contents

Contents

INTRODUCTION

1 About this Manual 91.1 Product Context.......................................................................................................... 101.1.1 Product Capabilities ................................................................................................... 111.1.2 Scope for the Manuals................................................................................................ 121.2 Structure ..................................................................................................................... 151.3 Typographic Conventions .......................................................................................... 161.4 Prerequisites ............................................................................................................... 161.5 Related Documents .................................................................................................... 17

2 About TAC Xenta 555 192.1 TAC Xenta 555 .......................................................................................................... 192.2 Communications Ports ............................................................................................... 20

GETTING STARTED

3 Commissioning the TAC Xenta 555 23

4 Connecting the TAC Xenta 555 to Your Network 254.1 Alternative Port Settings ............................................................................................ 274.1.1 HTTP and HTTPS...................................................................................................... 274.1.2 MicroNet Access (VisiSat Port)................................................................................. 274.2 Choosing a Location for the TAC Xenta 555 ............................................................ 284.3 Connecting the TAC Xenta 555 to a MicroNet Controller LAN............................... 294.3.1 Connecting to a MicroNet NCP network (MN MI not used)..................................... 304.3.2 Connecting to a MicroNet ARCNET network (MN MI used) .................................. 314.3.3 Connecting to a Satchnet network (MIU not used).................................................... 31

5 Creating a MicroNet Network in TAC XBuilder 335.1 Using TAC XBuilder ................................................................................................. 335.2 Creating a MicroNet Project ...................................................................................... 345.3 Creating a MicroNet Network from an XML File ..................................................... 365.4 Updating Your Project with a New MicroNet XML File .......................................... 38

6 Setting Up MicroNet Communications Parameters 396.1 About MicroNet Communications Parameters .......................................................... 396.2 Defining MicroNet Communications Parameters ...................................................... 40

7 Creating Web Pages with TAC XBuilder 417.1 Mapping MicroNet Point Signals to Web Pages........................................................ 417.1.1 Using Signals Folders ................................................................................................ 417.1.2 Mapping MicroNet Point Signals to Values Pages .................................................... 41

TAC AB, Oct 2006 5 (82)04-00054-01-en

Contents TAC Xenta 555, Supplement Manual

7.1.3 Mapping MicroNet Point Signals to Graphic Pages................................................... 447.1.4 Using Connection Objects .......................................................................................... 507.2 Mapping MicroNet Time and Holiday Schedules...................................................... 527.2.1 Creating Schedule Link Pages.................................................................................... 537.2.2 Linking a Schedule to a Graphic Page ....................................................................... 54

8 Engineering the TAC Xenta 555 in Vista 578.1 Adding a TAC Xenta Server 555 Object to TAC Vista�s Database........................... 578.2 Editing a TAC Xenta Server 555................................................................................ 578.3 Verifying a TAC Xenta 555 in TAC Vista Workstation............................................ 588.4 Displaying TAC Xenta Server 555 Web Pages.......................................................... 59

REFERENCE

9 MicroNet Objects in XBuilder 639.1 MicroNet Device Addressing ..................................................................................... 639.1.1 NCP and ARCNET Networks .................................................................................... 639.1.2 Satchnet Networks...................................................................................................... 649.2 Network Objects ......................................................................................................... 649.3 Point Signals ............................................................................................................... 659.3.1 MicroNet Point Signal Attributes ............................................................................... 659.3.2 Time and Holiday Schedules...................................................................................... 66

10 VisiSat to XML Conversion 6910.1 Generation of the XML file for XBuilder .................................................................. 70

11 VisiSat IP Tunnel Configuration 7111.1 VisiSat Port Number................................................................................................... 7111.2 IP Tunnel and Satchnet networks ............................................................................... 75

12 Performance Considerations 7712.1 Network Architecture ................................................................................................. 7712.2 Bandwidth and Performance ...................................................................................... 7712.3 Web Page Updates...................................................................................................... 78

Index 79

6 (82) TAC AB, Oct 200604-00054-01-en

INTRODUCTION

1 About this Manual

2 About TAC Xenta 555

TAC Xenta 555, Supplement Manual 1 About this Manual

1 About this ManualThis manual describes a particular process. For information on certain products, we refer you to the manual for the product in question.

For information on how to install software, we refer you to the instruc-tions delivered with the software.

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.

Notes

� 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.

TAC AB, Oct 2006 9 (82)04-00054-01-en

1 About this Manual TAC Xenta 555, Supplement Manual

1.1 Product ContextThe Xenta Server family consists of different products: TAC Xenta 511, TAC Xenta 555, TAC Xenta 527, and TAC Xenta 913. Xenta Servers are equipped with several features; these are defined in the following tables:

Table 1.1: Terms and definitions.

Term Definition

Proxy (Fieldbus/Protocol) Different communication proto-cols, such as I/NET, MicroNet, Modbus, and BACnet, can be connected to the Xenta Servers used with TAC Vista.

LTA LonTalk Adapter; a LonWorks network can be connected to the Xenta Servers used with TAC Vista.

Gateway A flow of signals can be config-ured between the connected net-works in Xenta Servers.

Table 1.2: Product functions and limitations

Product Functions Limitations

TAC Xenta 511 Xenta Server

Presentation web

Only gateway for LonWorks, Modbus, and SNVTs


Presentation web

Only gateway for I/NET, Lon-Works, and SNVTs


Presentation web

Only gateway for MicroNet, LonWorks, and SNVTs

TAC Xenta 913 Xenta Server Does not handle trend logs and alarms (LON, I/NET and inter-nal)

10 (82) TAC AB, Oct 200604-00054-01-en


1.1.1 Product Capabilities

TAC Xenta 511

The TAC Xenta 511 can serve as a Xenta Server for a LonWorks net-work, and/or a Modbus network in a Vista system serving Vista with all the information available on those networks.

The Xenta 511 also provides a web application for displaying values and graphics, trend logging and displaying alarms and events from con-nected networks in a web browser.

The Xenta 511 also provides gateway functionality for interconnecting signals between the LonWorks and the Modbus networks.

The Xenta 511 can also serve as a stand-alone web server for a Lon-Works network and/or a Modbus network and thereby provide a web interface for operating devices on the connected networks.

TAC Xenta 527/527-NPR

The TAC Xenta 527 can serve as a Xenta Server for an I/NET network, and/or a LonWorks network in a Vista system serving Vista with all the information available on those networks. Configuring the I/NET net-work from Vista is enabled by the use of the I/NET Host Tool.

The Xenta 527 also provides a web application for displaying values and graphics, trend logging and displaying alarms and events from the connected networks in a web browser.

The Xenta 527 also provides gateway functionality for interconnecting signals between the I/NET and the LonWorks networks.

The Xenta 527 can also serve as a stand-alone web server for an I/NET network, and/or a LonWorks network to provide a web interface for operating devices on the connected networks.

The Xenta 527-NPR, is a feature-enhanced version of the I/NET Net Plus Router.

TAC Xenta 555

The TAC Xenta 555 can serve as a Xenta Server for a MicroNet net-work, and/or a LonWorks network in a Vista system serving Vista with all the information available on those networks.

The Xenta 555 also provides a web application for displaying values and graphics, trend logging and displaying alarms and events from the connected networks in a web browser.

The Xenta 555 also provides gateway functionality for interconnecting signals between the MicroNet and the LonWorks networks.

The Xenta 555 can also serve as a stand-alone web server for a Micro-Net network, and/or a LonWorks network to provide a web interface for operating devices on the connected networks.

TAC AB, Oct 2006 11 (82)04-00054-01-en


TAC Xenta 913

The TAC Xenta 913 can serve as a communication port for a LonWorks network in a Vista system. At the same time it can serve as a Xenta Server for an I/NET network, and/or third party communication proto-cols in a Vista system serving Vista with all the information available on those networks.

The Xenta 913 also provides gateway functionality for interconnecting signals between the connected networks.

1.1.2 Scope for the Manuals

TAC Xenta Server, Technical Manual

This manual describes how to engineer different functions such as dis-playing values and graphics, trend logging and displaying alarms and events and so on for the Xenta 511, Xenta 527 and the Xenta 555.

This manual also describes how to present the information available in the Xenta Server for an operator of a Vista system.

Although all the examples in this manual are based on a LonWorks net-work and a Xenta 511 in Vista, they also apply to the Xenta 527 and an I/NET network, and to the Xenta 555 and a MicroNet network.

Functions that are unique to the Xenta 527 in combination with an I/NET network are described in TAC Xenta 527/527-NPR, Supplement Manual. Similarly, functions that are unique to the Xenta 555 in combi-nation with a MicroNet network are described in TAC Xenta 555, Sup-plement Manual.

TAC Xenta 527/527-NPR, Supplement Manual

This manual describes how to engineer functions that are unique to the Xenta 527 in combination with an I/NET network, such as connecting an I/NET network and displaying I/NET point signals and I/NET Link pages.

Configuring the I/NET network from Vista using the I/NET Host Tool is also described in this manual.

Configuring the Xenta 527-NPR for communication with an I/NET Host is also described in this manual.

TAC Xenta 555, Supplement Manual

This manual describes how to engineer functions that are unique to the Xenta 555 in combination with a MicroNet network, such as connecting

Important

� As a Xenta 913 can be added as a Xenta Server in a Vista system, the parts about creating the Xenta Server and editing it using XBuilder are also valid for the Xenta 913.

12 (82) TAC AB, Oct 200604-00054-01-en


a MicroNet network and displaying MicroNet point signals and Micro-Net schedules.

Note

In most instances within the Xenta 555 Supplement, the term �Micro-Net network� refers to either a MicroNet network or a Satchnet net-work. A MicroNet network may comprise MN50 Series controllers (for example, MN550, MN650) or slightly older MicroNet devices (for example, MN500, MN620) using the ARCNET or NCP protocol. A Satchnet network will comprise legacy products (for example, IAC420, IAC600, MMC3601 using the SNP protocol).

TAC AB, Oct 2006 13 (82)04-00054-01-en


Engineering TAC Xenta Gateway – TAC Xenta 511/527/555/913

This manual describes how to configure a third party protocol using TAC Device Editor, based on an example for a Modbus network. The Xenta 913 is added as a LonWorks Device in Vista. The examples show how to interconnect signals in a Modbus device and signals in a Xenta device on the LonWorks network using the gateway application in the Xenta 913. Another example shows how to add SNVTs in the Xenta 913 and propagate them on the LonWorks network.

Important

� As the Xenta 511 can communicate using Modbus, the informa-tion about configuring the Modbus communication in this man-ual is also valid for the Xenta 511.

� As the Xenta 511/527/555/913 can propagate SNVTs on a Lon-Works network, the information in this manual about adding SNVTs is also valid for the Xenta 511/527/555.

� Connecting signals between the connected networks is described in detail in this manual; this information also applies to the Xenta 511/527/555/913.

14 (82) TAC AB, Oct 200604-00054-01-en


1.2 StructureThe manual is divided into the following parts:

� Introduction The Introduction section contains information on how this manual is structured and how it should be used to find information in the most efficient way.

� Getting Started The Getting Started section contains a step-by-step description of how to engineer or carry out different tasks. It also gives you guided instructions on how to complete a sample project. If you want more information, see the corresponding chapter in the Ref-erence section of the manual.

� Reference The Reference section contains more comprehensive information about various parts of the Getting Started section. It also provides you with information on alternative solutions not covered by the Getting Started section.

TAC AB, Oct 2006 15 (82)04-00054-01-en


1.3 Typographic ConventionsThroughout the manual the following specially marked texts may occur.

1.4 PrerequisitesTo be able to profit from the contents in this manual, you are recom-mended to read the following manuals:

� Classic Networks, Technical Manual, and/or

� LNS Networks, Technical Manual.

� VisiSat Engineering Guide (Version 2.0 or earlier for Satchnet net-works, Version 2.1 or later for MicroNet networks).

! Warning

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

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.

16 (82) TAC AB, Oct 200604-00054-01-en


1.5 Related Documents� TAC Software, Installation Manual

Part No.: 03-00001

� TAC Xenta Server, Technical Manual

Part No.: 03-00051

� TAC Xenta 527/527-NPR, Supplement Manual

Part No.: 03-00052

� Classic Networks, Technical Manual

Part No.: 03-00015

� LNS Networks, Technical Manual

Part No.: 03-00016

� TAC Xenta 555, Supplement Manual

Part No.: 03-00054

� TAC Xenta 511/527/555/911/913, Product Manual

Part No.: 03-00071

TAC AB, Oct 2006 17 (82)04-00054-01-en


18 (82) TAC AB, Oct 200604-00054-01-en

TAC Vista, TAC Xenta 555 2 About TAC Xenta 555

2 About TAC Xenta 555

2.1 TAC Xenta 555The Xenta 555 is a web-based presentation system for MicroNet net-works. Using a standard web browser, the operator can easily view and control the devices in the MicroNet network via the Internet or a local intranet.

Using the Xenta 555, you can create a hardware bridge that integrates MicroNet devices into your LonWorks network. The Xenta 555 pro-vides a web based presentation of a MicroNet system. TAC�s XBuilder is the programming tool you can use to design, generate, and maintain web pages in the Xenta 555.

The Xenta 555 also supports the tunnelling of VisiSat over IP. This means that with the VisiSat PC connected to the same IP network as the Xenta 555, you can make program changes to MicroNet controllers over the ethernet network.

TAC AB, Oct 2006 19 (82)04-00054-01-en

2 About TAC Xenta 555 TAC Vista, TAC Xenta 555

2.2 Communications PortsThe following communication ports are commonly used to configure the Xenta 555 and/or use it with MicroNet or Satchnet.

1 MicroNet Direct Connection (RS232 A)

Use this port to directly connect a MicroNet Manager Interface (MN MI) to the Xenta 555. Refer to Section 4.3.2, �Connecting to a MicroNet ARCNET network (MN MI used)�, on page 31 for more information about this type of connection.

2 Console Connection (RS232 B)

This port allows you to directly connect a PC to the Xenta 555. You can then use a program such as Windows HyperTerminal to config-ure and monitor the Xenta 555 through a console window. Refer to TAC Xenta 511/527/555/911/913, Product Manual for more infor-mation.

3 Ethernet LAN Connection (TCP/IP)

Use this port to connect the Xenta 555 to an Ethernet network. Refer to Chapter 4, �Connecting the TAC Xenta 555 to Your Net-work�, on page 25 for more information.

4 MicroNet or Satchnet Controller LAN Connection (RS485)

Use this port to connect the Xenta 555 to a MicroNet controller LAN. Refer to Section 4.3, �Connecting the TAC Xenta 555 to a MicroNet Controller LAN�, on page 29 for more information.

Fig. 2.1: Xenta 555 communications ports

Rx Tx Rx Tx

A RS 232 B

TAC Xenta 555

RS485 CRX/TX+

RX/TX–

10Base-T

MMC

Rx / TxRun

11 12 13 14 15 16 17 18 19 20

IP address.................-................-...............-................

MicroNet or SatchnetController LAN Connection(RS485)

Ethernet LANConnection(TCP/IP)

Console Connection(RS232 B)

Direct Connection toMicroNet Manager Interface

(RS232 A)

1

23

LON24 VAC

5 VAG G0 C1 C2 G0

Fail-safe

RX-LON

1 2 3 4 5 6 7 8 9 10

RS485 A

RX/TX+

RX/TX-

RX+

4

20 (82) TAC AB, Oct 200604-00054-01-en

GETTING STARTED

3 Commissioning the TAC Xenta 555

4 Connecting the TAC Xenta 555 to Your Network

5 Creating a MicroNet Network in TAC XBuilder

6 Setting Up MicroNet Communica-tions Parameters

7 Creating Web Pages with TAC XBuilder

8 Engineering the TAC Xenta 555 in Vista

TAC Xenta 555, Supplement Manual 3 Commissioning the TAC Xenta 555

3 Commissioning the TAC Xenta 555There are six basic steps to commissioning the Xenta 555. These steps are described below.

To commission the TAC Xenta 555

1 Connect the Xenta 555 to 24 VAC power.

Refer to TAC Xenta 555 Installation Instructions (0FL-3956-005) for instructions.

2 Connect a PC to the Xenta 555�s serial port.

Attach a serial cable from the computer�s COM port to the RS232 B port on the front of the Xenta 555. Refer to TAC Xenta 511/527/555/911/913, Product Manual for complete instructions.

3 Set the Xenta 555�s communication parameters.

Before the Xenta 555 can successfully communicate on the Ether-net, you must first set its IP address and other basic parameters. Refer to TAC Xenta 511/527/555/911/913, Product Manual for complete instructions.

4 Connect the Xenta 555 to the Ethernet network.

Attach the Xenta 555 to the network at the necessary location. Refer to Chapter 4, �Connecting the TAC Xenta 555 to Your Net-work�, on page 25 for more information.

5 If necessary, load the Xenta 555�s software.

The Xenta 555 is delivered from the factory with pre-loaded soft-ware. If you need to reload this software, you can download it from TAC�s website (http://delphi.tac-global.com). Before installing downloaded software, review its release information to verify com-patibility with your hardware. Refer to TAC Xenta 511/527/555/911/913, Product Manual for complete instructions.

6 Configure the Xenta 555 to communicate with MicroNet/Satchnet controllers.

In order for the Xenta 555 to communicate with MicroNet devices from across an Ethernet network, you may need to define some basic communication parameters. Refer to Chapter 6, �Setting Up

Caution

Ensure correct polarity at all 24 VAC devices.

TAC AB, Oct 2006 23 (82)04-00054-01-en

3 Commissioning the TAC Xenta 555 TAC Xenta 555, Supplement Manual

MicroNet Communications Parameters�, on page 39 for more information.

24 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 4 Connecting the TAC Xenta 555 to Your Network

4 Connecting the TAC Xenta 555 to Your Network

The Xenta 555 integrates with your building control system by commu-nicating across the Ethernet using TCP/IP transport protocols.

The Xenta 555 can connect directly to a MicroNet controller LAN (or a Satchnet controller LAN) and also to the Ethernet. Using the Xenta 555, you can access your MicroNet system from a web browser on any PC connected to the Ethernet.

Note

Before you connect the Xenta 555 to your network, assign it an IP address and load its software. Refer to TAC Xenta Server, Technical Manual for the necessary instructions.

TAC AB, Oct 2006 25 (82)04-00054-01-en

4 Connecting the TAC Xenta 555 to Your Network TAC Xenta 555, Supplement Manual

The following figure shows an example network configuration.

In order for the Xenta 555 to successfully establish communications with your building control system, certain network criteria must be met. More specifically, the ports required for proper communication with these systems must be open and available to the Xenta 555. The Xenta 555 uses the following communication ports:

� Port 80 (HTTP access, configurable)

� Port 443 (HTTPS access, configurable)

� Port 20/21 (FTP access)

� Port 25 (SMTP access)

� Port 80 (Status Viewer, Alarm Viewer and Graphics Viewer)

� Port 1068 (LTA for Vista)

� Port 161 (SNMP access)

� Port 7001 (VisiSat access, configurable)

Fig. 4.1: Connecting the Xenta 555 to a network

Firewall 2

Xenta 555

Firewall 1

Internet

DMZ

Intranet

Vista Network

Router

Node

Node

Node

Option A

Xenta 555

Option B

MicroNetController LAN

Node

Node

Node

Xenta 555

Option C

Install the Xenta 555at any of these locations

26 (82) TAC AB, Oct 200604-00054-01-en


4.1 Alternative Port Settings

4.1.1 HTTP and HTTPS

Perhaps you are unable to make the necessary configuration changes to your proxies/firewalls because of restrictions imposed by your com-pany�s network security policies. In this case, you have the option of choosing different numbers for the HTTP and HTTPS communication ports shown above.

The following steps describe how to select other communication ports:

1 From the web browser, expand the navigation tree as shown in the following figure and select HTTP Server.

2 Set the HTTP and HTTPS communication port assignments to the appropriate values.

3 Accept your settings by selecting Save & Restart.

4 Configure your network to allow communication on the ports you assigned to the Xenta 555.

5 Verify that the Xenta 555 can now successfully communicate across the Internet and with your building control systems.

4.1.2 MicroNet Access (VisiSat Port)

The VisiSat port number is 7001 by default, but if this number has already been allocated elsewhere, you have the option of changing it. This port number must be changed in two places and the port number must be the same in each case:

� in the properties page for the MicroNet object in XBuilder. Refer to Section 6.2, �Defining MicroNet Communications Parameters�, on page 40.

� in the Host Port Number field of the IP Tunnel Configuration dialog box of the VisiSat Configuration Tool. Refer to Chapter 11, �VisiSat IP Tunnel Configuration�, on page 71.

TAC AB, Oct 2006 27 (82)04-00054-01-en


4.2 Choosing a Location for the TAC Xenta 555Connect the Xenta 555 to your network at the desired location. Depend-ing on your network�s design, you may have to configure proxies/fire-walls to allow for proper communication (refer to TAC Xenta Server, Technical Manual for information about proxy servers and firewalls). An example network and the location options for the Xenta 555 are shown on Page 26. Each location is described below.

Explanation of Option A:

The first location (see Option A in the example 26) shows the Xenta 555 installed in the DMZ between two firewalls (be aware that this may be logically two firewalls but physically only one piece of hardware). This location requires the following configuration:

� Firewall 1: For security reasons, you may only want to open ports 80 and 443 from the internet. This is all that is necessary for inter-net access to the Xenta 555�s web interface.

� Firewall 2: Open ports 20, 21, 25, 80, 161, and 443 from the intra-net side. Also open port 1068 and VisiSat port 7001 from the DMZ side to allow the Xenta 555 to communicate with Vista and Micro-Net networks.

Explanation of Option B:

The second location (see option B in the example 26) shows the Xenta 555 installed on the network with no firewall between it and the building control systems. This location requires that both firewalls allow traffic through ports 80 and 443. The other ports are not required to be open on either firewall since the Xenta 555 is installed at a network location that allows it to communicate directly with MicroNet and Vista networks.

Explanation of Option C:

The third location (see option C in the example 26) shows the Xenta 555 installed on the MicroNet controller LAN. Like Option B above, this location requires that both firewalls allow traffic through ports 80 and 443. The other ports are not required to be open on either firewall since the Xenta 555 is installed at a network location that allows it to commu-nicate directly with MicroNet and Vista networks.

28 (82) TAC AB, Oct 200604-00054-01-en


4.3 Connecting the TAC Xenta 555 to a MicroNet Controller LAN

The method of connecting the Xenta 555 to a MicroNet controller LAN depends on the MicroNet LAN type. These networks are:

� MicroNet NCP network, that is, MicroNet controllers using the Native Communications Protocol. A MicroNet Manager Interface (MN MI) must not be used.

� MicroNet ARCNET network, that is, MicroNet controllers using the Attached Resource Computer Network protocol. An MN MI must be used.

� Satchnet network, that is, older products using the Satchwell Net-working Protocol (SNP). A Modem Interface Unit (MIU) must not be used.

! Note

Auto dial remote sites are not supported by the Xenta 555.

Tip

The MN MI and the MIU are not required for NCP and SNP networks and can be removed when installing the Xenta 555.

TAC AB, Oct 2006 29 (82)04-00054-01-en


4.3.1 Connecting to a MicroNet NCP network (MN MI not used)

The Xenta 555 connects to the MicroNet controller network through ter-minals 5 and 6 of its upper terminal block connector.

To connect the TAC Xenta 555 to a MicroNet controller LAN

1 Connect the positive (+) line to position 5.

2 Connect the negative (�) line to position 6.

Join the shield wires together at each device on the controller LAN, and connect to a good earth ground at one location only. Ensure that shield wire continuity is maintained across the controller LAN.

If Belden 9502 dual-twisted pair is being used (recommended), join together both wires of the second twisted pair and connect them to the LAN REF terminal at each MicroNet device (refer to the relevant MicroNet data sheets for details). For the Xenta 555, connect the second twisted pair to Pin 2 (G0).

Fig. 4.2: RS485 LAN connections (MicroNet NCP network)

Rx Tx Rx Tx Rx / TxRun

LON24 VAC

5 VAG G0 C1 C2 G0

Fail-safe

RX-LON

MicroNet ControllerLAN Connection(RS485)

1 2 3 4 5 6 7 8 9 10

RS485 A

RX/TX+

RX/TX-

RX+

! Caution

Belden 9502 dual-twisted pair cable contains one black wire in each twisted pair. It is essential to good communications that these black wires are not crossed over between pairs.

Note

It is important to ensure that the polarity of the network connections is consistent throughout the system, that is, (�) is connected to (�) and (+) is connected to (+).

30 (82) TAC AB, Oct 200604-00054-01-en


4.3.2 Connecting to a MicroNet ARCNET network (MN MI used)

To connect to a MicroNet ARCNET network (MN MI used)

1 Connect adapter 3-621-3056-0 to the MN MI�s serial COM port

2 Connect cable 3-781-0118-0 to the above adaptor and then to the Xenta 555�s RS232 A port

3 If connecting an ARCNET network, connect the LAN twisted pair cable to the MN MI (MN50-MI-ARC) terminals as detailed in MicroNet data sheet DS 10.217A.

4 If connecting an NCP network, connect the LAN twisted pair cable to the MN MI (MN50-MI-NCP) terminals as detailed in MicroNet data sheet DS 10.217A.

4.3.3 Connecting to a Satchnet network (MIU not used)

This method applies to Satchnet networks. The Xenta 555 connects to the MicroNet controller network through terminals 5 and 6 of its upper terminal block connector.

To connect the TAC Xenta 555 to a MicroNet controller LAN

1 Connect the positive (+) line to position 5.

2 Connect the negative (�) line to position 6.

Join the shield wires together at each device on the controller LAN, and connect to a good earth ground at one location only. Ensure that shield wire continuity is maintained across the controller LAN.

Fig. 4.3: RS485 LAN connections (Satchnet network)

Rx Tx Rx Tx Rx / TxRun

LON24 VAC

5 VAG G0 C1 C2 G0

Fail-safe

RX-LON

Satchnet ControllerLAN Connection(RS485)

1 2 3 4 5 6 7 8 9 10

RS485 A

RX/TX+

RX/TX-

RX+

Note

It is important to ensure that the polarity of the network connections is consistent throughout the system, that is, (�) is connected to (�) and (+) is connected to (+).

TAC AB, Oct 2006 31 (82)04-00054-01-en


32 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 5 Creating a MicroNet Network in TAC XBuilder

5 Creating a MicroNet Network in TAC XBuilder

5.1 Using TAC XBuilderWhen you create an XBuilder project that uses the Xenta 555 template, a �Micronet 1� object becomes available. This object provides functions that allow you to add MicroNet related items to your project.

XBuilder uses an imported XML file to create a representation of the MicroNet network. Any portions of the MicroNet network that are defined in the MicroNet XML file (.xmlm) will be included in the asso-ciated XBuilder representation.

The MicroNet XML file is generated by the VisiSat Configuration Tool. Refer to Visisat 2.1 Engineering guide for full details. For convenience, an outline is included in Chapter 10, �VisiSat to XML Conversion�, on page 69.

Fig. 5.1:

TAC AB, Oct 2006 33 (82)04-00054-01-en

5 Creating a MicroNet Network in TAC XBuilder TAC Xenta 555, Supplement Manual

The MicroNet network in XBuilder

The following figure shows a portion of a MicroNet network that has been created from an XML file. The figure is annotated to describe how an object in the network view represents a portion of the network.

5.2 Creating a MicroNet Project To create a MicroNet project:

1 Within XBuilder, on the File menu, click New Project to start a new project.

2 In the New Project dialog box, perform the following tasks:

a Define a name for the new project.

b Choose the appropriate storage location for the project files.

c Select the X555 Project template.

d Click OK to save these settings.

Fig. 5.2:

Note

A Satchnet network is set up using the same procedures as a MicroNet network.

34 (82) TAC AB, Oct 200604-00054-01-en


3 In the project Settings dialog box, enter a description of the project and set the other parameters as necessary.

4 Click OK.

5 In the network pane of XBuilder, expand the IP Backbone item.

6 Right-click the RS232-485 A item, point to Add, then click Micronet.

7 A Micronet 1 object will appear beneath the RS232-485 A item. If required, rename the Micronet 1 object to a name more suitable for the network for example, �Main Building�.

TAC AB, Oct 2006 35 (82)04-00054-01-en


5.3 Creating a MicroNet Network from an XML FileTo create a MicroNet network from an XML file

1 Right-click the Micronet 1 object and then click Insert MicroNet Network.

2 Select the appropriate XML file and click Open.

Tip

Before importing an XML file from VisiSat it is a good idea to ensure that points for the VisiSat Points Gallery are carefully selected, and if necessary renamed, so that they accurately reflect the requirements of the Xenta 555 project; it is the data from these points and their names which will eventually be represented in the Xenta Server�s web pages.

Caution

Where the Xenta 555 is being added to an existing site that has been upgraded from a VisiSat 1.0 project to a 2.1 project, it will be neces-sary to re-create the points gallery in VisiSat.

36 (82) TAC AB, Oct 200604-00054-01-en


3 Expand the Micronet 1 object (or the renamed object) and verify that your project now contains imported MicroNet network objects (subnets, controllers and so on) and point signals.

4 Note the parameters of the highlighted Micronet 1 object. You may need to set its parameters as described in Chapter 6, �Setting Up MicroNet Communications Parameters�, on page 39.

Note

The Online Status point signal will always be added to your selected signals. The Null Outputs point signal will be present for MN, MN50 Series and IAC controllers, but not Unifact Pro, Bonsai or MMC controllers (see Section 9.3.1, �MicroNet Point Signal Attributes�, on page 65 for a description of these point signals).

TAC AB, Oct 2006 37 (82)04-00054-01-en


5.4 Updating Your Project with a New MicroNet XML File

Modifications within your MicroNet system such as adding or deleting points and point extensions will cause XML files to change. If changes occur in any of the MicroNet XML files that you have already imported into your project, you must update your project so that it accurately rep-resents the modified MicroNet network. You can insert the new one directly, in which case you will be prompted to delete the old one first, or you can delete the old network first and then insert the new one.

To update the network in your project

1 Follow the steps detailed in Section 5.3, �Creating a MicroNet Network from an XML File�, on page 36.

If you did not delete the old MicroNet network first, you will be prompted to do so in the following dialog box.

2 Click Yes to replace the old network with another network.

3 Expand the Micronet 1 object and verify that your project now contains updated MicroNet network objects.

To delete the network in your project

1 Right-click the Micronet 1 object and then click Delete.

2 Click Yes in the resulting confirmation dialog box.

The whole MicroNet network will be deleted from the project.

38 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 6 Setting Up MicroNet Communications Parameters

6 Setting Up MicroNet Communications Parameters

6.1 About MicroNet Communications ParametersAll services required to send and receive data to connected MicroNet networks are provided by a Serial Communications Interface (SCI), which defines the communications properties for a MicroNet network.

These properties are configured during initialisation, when you initially add a MicroNet network in XBuilder (see Chapter 5.2, �Creating a MicroNet Project�, on page 34); these properties are read from the con-figuration file Micronet.xml.

The properties page in XBuilder for the Micronet 1 object therefore has the following default properties:

However, it may be necessary to change some of these parameters to match the MicroNet network you import (see Chapter 5.3, �Creating a MicroNet Network from an XML File�, on page 36).

Fig. 6.1:

Note

� In practice, it is usual to accept the defaults for NCP and ARC-NET networks.

� If you are engineering a Satchnet network using IP Tunnel, please refer to Section 11.2, �IP Tunnel and Satchnet networks�, on page 75.

TAC AB, Oct 2006 39 (82)04-00054-01-en

6 Setting Up MicroNet Communications Parameters TAC Xenta 555, Supplement Manual

6.2 Defining MicroNet Communications Parameters

1 Select a network from the Network Type drop-down menu. The options are Micronet NCP, Satchnet NCP or Micronet Arcnet.

2 Set the baud rate of the connected network from the Baud Rate drop-down menu. The options are 1200, 4800, 9600, 19200 and 38400.

3 Enter the Subnet Address of the Xenta 555 (any number from 1 to 127 inclusive, default is 1).

4 Enter the Node Address of the Xenta 555 (any number from 1 to 255 inclusive, default is 254).

5 Select either Y or N from the Update Subnet drop-down menu. This defines whether Subnet address broadcasts are made to the connected network. Set this to Y if an MN MI is not present.

6 Enter the Time Update Interval. This is the interval in minutes between time broadcasts to the connected network (any number from 0 to 1440 inclusive, default is 10).

7 Enter the VisiSat Port number. This defines the TCP/IP port that VisiSat will connect to using the VisiSat IP Tunnel (any number from 0 to 65535 inclusive, default is 7001). Refer to Section 4.1.2, �MicroNet Access (VisiSat Port)�, on page 27 for further informa-tion.

Note

In practice, it is usual to accept the defaults for NCP and ARCNET networks.

Note

An Arcnet network must connect via an MN MI, whilst an NCP net-work must connect directly to the RS485 network. A Satchnet net-work must not connect via an MN MI or an MIU.

Note

If an MN MI is detected the communications interface will automat-ically set the MN MI to run at 38400 and then switch to the faster speed. Other connections will run at the programmed baud rate.

Note

Broadcasts are made every five minutes if enabled. Subnet broad-casts are automatically disabled at the driver if an MN MI is detected.

40 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 7 Creating Web Pages with TAC XBuilder

7 Creating Web Pages with TAC XBuilder

7.1 Mapping MicroNet Point Signals to Web PagesWithin XBuilder, each imported MicroNet point has an associated sig-nal, termed a �point signal�, which represents the current value of the point. For a description of MicroNet points, refer to Chapter 9, �Micro-Net Objects in XBuilder�, on page 63. You can use MicroNet point sig-nals within web pages in your project.

Mapping a MicroNet point to a web page can be as easy as dragging a signal from XBuilder�s network view and dropping it onto the appropri-ate web page in the system view. The way the point information on a page is displayed to the user, and the way it can be used, depends on the type of web page on which it resides.The procedures for mapping point signals are described below.

7.1.1 Using Signals Folders

If the value of a point signal is to be used in several places, it is a good idea to create a signal object in a Signals folder and link to it using short-cuts.

To create and use a signals folder

1 In the system view, select and right-click a folder, point to New and click Folder.

2 Rename the folder to �Signals�.

3 Drag the signals as required from the MicroNet network to the Signals folder.

4 Drag any of these signals to a values page, graphics page and so on, to create the required shortcuts.

7.1.2 Mapping MicroNet Point Signals to Values Pages

In the following example, we will map MicroNet point information to a values page.

Tip

It is strongly recommended that Signals folders are created along with a point signal for each MicroNet point, and that each signal is dragged from the Signals folder to wherever it is needed. In this way, if a spe-cific signal needs to be changed, it need only be changed once (in the Signals folder).

TAC AB, Oct 2006 41 (82)04-00054-01-en

7 Creating Web Pages with TAC XBuilder TAC Xenta 555, Supplement Manual

To map MicroNet point information to a values page

1 In the system view, select and right-click a folder, point to New, point to Page, and then click Values Page to add a values page to the project.

2 Type a name for the new values page.

3 Add signals to the values page by dragging signals from the net-work view and dropping them onto the values page

The signals will appear as shortcuts on the values page. If the name of any signal needs to be changed, enter a Description. This text will appear on the resulting web page, and should therefore be meaningful to the end user. See later notes on changing signal names.

42 (82) TAC AB, Oct 200604-00054-01-en


4 Generate the project and send it to the Xenta 555. Using a Web browser, verify that the values page displays properly.

The following illustration shows a sample Points Gallery in Visi-Sat, with the original names for the points in the ContAB(550560) points list. This is how they will be named on import to XBuilder (and in the subsequent Xenta 555 web pages), unless you rename them in each Point Properties dialog box. Observe that the address values (1/2, 2/5 and 2/8) indicate that the sample points list contains points for more than one controller.

Observe also that the selected �Text Group� (in the drop-down box of the RL2 State signal�s properties dialog box) provides enumer-ations of On and Off to the Value field of the same signal when dis-played in a web page. However, if the text provided from VisiSat is not applicable to the a particular signal, you can use XBuilder�s

Notes

� Changing the name of the point signal in the Name field will not change the name of the point signal in the resulting web page. You must use the Description field to do this.

� You can also change the names of point signals in VisiSat�s Points Gallery, before importing to XBuilder (see following example). If this is done it will not be necessary to change point signal names in XBuilder�s Description field. Refer to VisiSat 2.1 Engineering Guide.

� You can also select the �Text Group� in VisiSat (see following example) before importing to XBuilder. This will provide enu-merations to the Value field of the signal. Refer to VisiSat 2.1 Engineering Guide.

� When viewing a point�s value, be aware that the Xenta 555 uses an Ansi-C 32-bit standard for floating points. Point values that exceed this limit of floating points are subject to inconsistent dis-plays.

TAC AB, Oct 2006 43 (82)04-00054-01-en


Tools � Enumerations menu to provide new enumerations. For further information refer to TAC Xenta Server, Technical Manual.

7.1.3 Mapping MicroNet Point Signals to Graphic Pages

In the following example, we will map MicroNet point information to a graphic page.

To map MicroNet point information to a graphic page

1 In the system view, select and right-click a folder, point to New, point to Object, and then click Graphic to add a graphic object to the project.

2 In the New graphic dialog box, specify a name and location for the new graphic.

Fig. 7.1:

44 (82) TAC AB, Oct 200604-00054-01-en


3 Type a name for the new graphic object. In this example, we will name the object �graphic_Finance�.

4 Right-click the object and click Edit Graphic to open the new graphic in the graphics editor.

5 Add a graphics symbol by dragging a component from a template to the graphic. In this example, we will drag a Temperature Sensor graphic symbol to the graphic and assign a MicroNet point value adjacent to it.

TAC AB, Oct 2006 45 (82)04-00054-01-en


6 In the Properties pane, rename the object and change any other properties as required.

7 On the toolbar, click the Text button, then select and click a posi-tion adjacent to the sensor object and add some text that describes the object. Click OK.

8 In the Objects pane, right-click the word Text and create a new binding for the selected text.

46 (82) TAC AB, Oct 200604-00054-01-en


9 Click the word Bind and type a suitable name in the Properties � General box, then select Content from the Target � Attribute drop-down list.

10 Add further text to the graphic if required, using the Text button as previously described. In this example the �° C� text has been added and the �Temp Input� text has been right aligned for a neater presentation in the web browser.

11 Save the graphic. Check that the name of the binding is now asso-ciated with the graphic object in XBuilder. Observe that the bind-

TAC AB, Oct 2006 47 (82)04-00054-01-en


ing in XBuilder has a question mark icon to show that it is not yet connected to a point signal:

12 Now drag a point signal to the binding.

13 Check that the question mark icon is replaced by the standard �point signal� icon:

14 In the system view, right-click the folder, point to New, point to Page, then click Graphics Page to add a graphic page to the project.

15 Type a name for the new graphic page. In this example, we will name the page �page_Finance�.

48 (82) TAC AB, Oct 200604-00054-01-en


16 Link the graphic object to the graphic page by dragging the object onto the page.

17 Verify that the graphic page in the system view now has a child item representing the graphic that you just linked to the page.

18 Generate the project and send it to the Xenta 555. Using a Web browser, verify that the graphic page displays properly.

TAC AB, Oct 2006 49 (82)04-00054-01-en


7.1.4 Using Connection Objects

Connection objects are useful for replicating the properties of a point signal, for instance, you may want to use an outside air temperature input for two buildings using only one sensor.

In the following example, we will connect MicroNet point information from a point signal in one controller (address 2/5, in the �Finance� area) to another controller (address 2/8, in the �Production� area).

To connect signal point values from one device to another

1 In the system view, select and right-click a folder, point to New, point to Object, and then click Connection Object to add a con-nection object to the project.

2 If required, type a new name for the new connection object (right-click the object, Rename).

3 Double click the object to display the From and To connectors.

50 (82) TAC AB, Oct 200604-00054-01-en


4 Drag a signal from the source device to the From connector.

5 Drag a signal from the destination device to the To connector.

The two signals �Temp Input� and �Analogue Ref� are now con-nected.

Caution

Connect signals with similar data ranges; the system will check the ranges of both the source and destination signals and generate a com-pile warning if the ranges are significantly different.

TAC AB, Oct 2006 51 (82)04-00054-01-en


6 At the web browser, verify that the connected point signals have the same value.

Refer to TAC Xenta Server, Technical Manual for more information about connection objects.

7.2 Mapping MicroNet Time and Holiday SchedulesIn addition to the point signals that are associated with a MicroNet net-work in XBuilder, signals derived from some MicroNet objects are available, that is, time and holiday schedules. The following MicroNet schedules can be used within your project and are further described in Section 9.3.2, �Time and Holiday Schedules�, on page 66:

� Time Schedule

� Optimiser Time Schedule

� Holiday Schedule

There are two variants of holiday schedule, one for a MicroNet network and the other for an Satchnet (SNP) network.

All MicroNet schedules must be connected to a standard link page in XBuilder. The link page can optionally be connected to a graphic page, allowing a user to click on a defined area in the graphic and jump directly to the appropriate MicroNet schedule.

Only the system administrator, or a user with �operator� privileges, can modify MicroNet time or holiday schedules.

The procedures for creating link pages for MicroNet time (and holiday) schedules, and for linking the schedules to a graphic page are described next. These procedures apply for all types of schedule.

52 (82) TAC AB, Oct 200604-00054-01-en


7.2.1 Creating Schedule Link Pages

To create a link page for a schedule

In the following example, we will create a link page that connects to a MicroNet time schedule.

1 In the system view, right-click the folder, point to New, point to Page, then click Link Page to add a link page to the project.

2 Type a name for the new link page. In this example, we will name the page �link_Time Schedule�.

3 Associate the link with a MicroNet time schedule by dragging a Time Schedule object onto the link object.

Now that you have created a link page that jumps to a MicroNet time schedule, you can associate the link page with an image on a graphic page.

TAC AB, Oct 2006 53 (82)04-00054-01-en


7.2.2 Linking a Schedule to a Graphic Page

To associate a link page with an image on a graphic page

In this example, we will import an image to the graphic page and create a link to it so that a time schedule will be displayed when the link is acti-vated in the web browser. The image we will use for the time schedule is a previously prepared calendar icon called calendar.bmp (you can choose another suitable image if required).

1 Perform one of the following tasks:

� Open an existing graphic object by right-clicking the graphic object and selecting Edit Graphic from the resulting pop-up menu.

� Add a new graphic object to the project by performing the first 4 steps in �Mapping MicroNet Point Signals to Graphic Pages� on page 44.

2 In the graphics editor�s toolbar, click the Insert Picture button, then click anywhere in the graphics area and browse for the required image.

3 Click Open to drop the graphic, and if required, add suitable text adjacent to the imported graphic using the Text button on the tool-bar.

54 (82) TAC AB, Oct 200604-00054-01-en


4 In the Objects pane, click the word Image, and in the Properties pane, rename the image and change any other properties as required.

5 In the Objects pane, right-click the name of the image and add a new link.

6 Click the word Link and rename the link as required.

7 Save the graphic. In XBuilder, check that the link is now associ-ated with the graphic object. Observe that the link icon has a red cross to show that there is not yet a link to a time schedule:

8 Now drag the Link page of the required time schedule to the graphic link:

TAC AB, Oct 2006 55 (82)04-00054-01-en


9 Check that the question mark icon is replaced by the standard �link� icon:

10 Generate the project and send it to the Xenta 555.

11 Using a Web browser, verify that the graphic page now links to the specified schedule.

Notes

� At the browser, a schedule with grey bars instead of green bars indicates historical data, that is, schedule data is no longer avail-able from the MicroNet controller due to a controller fault or a communications failure.

� If an existing schedule has never been available to the Xenta 555, an error message will be displayed at the browser for example, �Holiday Schedule read error code 42279�. This is due to a com-munications failure.

56 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 8 Engineering the TAC Xenta 555 in Vista

8 Engineering the TAC Xenta 555 in Vista

Vista Workstation can interface with the Xenta Server 555 and the MicroNet building control system. By adding Xenta Server 555 objects and their associated XBuilder projects to Vista�s database, you can use Vista Workstation to monitor and control MicroNet equipment.

8.1 Adding a TAC Xenta Server 555 Object to TAC Vista’s Database

To add a TAC Xenta Server 555

1 In Vista Workstation, right-click the Vista Server object, point to New, point to Device, and then click Xenta Server 555.

2 Type a name for the new device. In the example, type �South East Unit X555�.

When you add a Xenta Server 555 object to the Vista database, the object will initially have no XBuilder project associated with it in the Vista database. This is true even if the actual Xenta Server 555 hard-ware is already loaded with an XBuilder project. Until you save the Xenta Server 555 project to the Vista database, you will not be able to monitor or control equipment on the Xenta Server 555�s associated net-work from Vista Workstation.

Use the following section to save an XBuilder project to the Xenta Server 555 object in the Vista database.

8.2 Editing a TAC Xenta Server 555In order to associate an XBuilder project with a Xenta Server 555 object in the Vista database, you have to save the XBuilder project to the Vista database.

When you save the project in the Vista database, the web site for the Xenta Server 555 is generated. You then send the XBuilder project to the Xenta Server 555 and once that is done the Xenta Server 555 is able to communicate to Vista.

To edit a TAC Xenta Server 555

1 In the folders pane, right-click the newly added Xenta Server 555 object and click Edit.

2 Log into Vista Server from XBuilder.

3 By default, XBuilder starts a new project the first time you edit a newly-created Xenta Server 555 object in the Vista database.

TAC AB, Oct 2006 57 (82)04-00054-01-en

8 Engineering the TAC Xenta 555 in Vista TAC Xenta 555, Supplement Manual

In this case, you can edit the project as necessary. When you finish editing this project and send it to the Xenta Server 555, Vista Server automatically links the XBuilder project to the Xenta Server 555 object in the Vista database. If you have an existing XBuilder project that you would rather use, you can discard the new project (that is, close it without saving) and open the existing XBuilder project. In this case, you will have to manually save the XBuilder project to the Vista database.

4 If you opened an existing project rather than creating a new project; on the Vista Database menu, click Save As.

5 In the Select dialog box, locate and select the Xenta Server 555 you created in Vista Workstation.

6 Click Select.

7 If the project contains references to objects outside of the project folders, you will receive a message. In this case, click Yes to copy objects to the project�s folders.

8 Send the project to the Xenta Server 555.

9 Quit XBuilder.

8.3 Verifying a TAC Xenta 555 in TAC Vista Workstation

After sending the project to the Xenta Server 555 you can see the result of the operation in the folders pane in Vista Workstation.

58 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 8 Engineering the TAC Xenta 555 in Vista

To verify a TAC Xenta 555 in TAC Vista Workstation

1 In Vista Workstation, in the folders pane, click TAC Vista and then click Refresh.

2 Expand the Vista Server object.

3 In the folders pane, verify that the Xenta Server 555 no longer has an asterisk.

4 Expand the Xenta Server 555 object and verify that the project you built in XBuilder is now reflected in Vista Workstation. Also ver-ify that the MicroNet network is present.

8.4 Displaying TAC Xenta Server 555 Web PagesAny web pages you�ve added to the Xenta Server 555�s project can be displayed in Vista Workstation.

To display TAC Xenta Server 555 web pages

1 In the folders pane, locate the desired web page in the Xenta Server 555�s project.

The following example shows the location of a web page named page_Finance.

2 Click on the web page to display the web page embedded in Vista Workstation.

TAC AB, Oct 2006 59 (82)04-00054-01-en

8 Engineering the TAC Xenta 555 in Vista TAC Xenta 555, Supplement Manual

60 (82) TAC AB, Oct 200604-00054-01-en

REFERENCE

9 MicroNet Objects in XBuilder

10 VisiSat to XML Conversion

11 VisiSat IP Tunnel Configuration

12 Performance Considerations

TAC Xenta 555, Supplement Manual 9 MicroNet Objects in XBuilder

9 MicroNet Objects in XBuilderThe following figure shows a portion of a MicroNet network (NCP or ARCNET) in XBuilder. The figure is annotated to describe how an object represents a portion of the MicroNet network. The objects are further described below.

9.1 MicroNet Device Addressing

9.1.1 NCP and ARCNET Networks

Each device (controller) in MicroNet (NCP and ARCNET) has a unique address that identifies it in the system. An address in the MicroNet sys-tem comprises two numbers, in the following format:

2/5

where:

2 = a subnet number

5 = a node number

The subnet number specifies the device's subnet (sub-LAN) address. In an NCP network, a LAN can exist under a touchscreen, and in an ARC-NET network, a LAN can exist under an ARCNET router; these LANs are then known as sub-LANs. A MicroNet controller or touchscreen connected to the top-level LAN has a subnet address of 1. Each sub-LAN has a different (subnet) address.

TAC AB, Oct 2006 63 (82)04-00054-01-en

9 MicroNet Objects in XBuilder TAC Xenta 555, Supplement Manual

The node number specifies the address of a device (node) on a subnet (sub-LAN) and is specified using bit switches in the device or Mainte-nance screen at the touchscreen.

9.1.2 Satchnet Networks

The following figure shows a portion of a MicroNet network (Satchnet) in XBuilder.

Each device in a Satchnet network has a single number as its address, rather than the subnet/node arrangement for NCP and ARCNET net-works as described above. However, the representation of a Satchnet network in XBuilder is similar to that of an NCP or ARCNET network, but observe the following:

� All IAC Touchscreens used on a main LAN will have an address within the limits of 65 and 95.

� Any controllers on an IAC Touchscreen�s sub-LAN will be repre-sented in XBuilder by its bit switch address and not by its sub-LAN controller address as used in VisiSat. Refer to VisiSat 2 Engi-neering Guide for further Satchnet addressing details.

9.2 Network ObjectsThe following objects in XBuilder�s network pane represent physical devices in the MicroNet network:

� MicroNet Interface � This object represents the top level of the MicroNet network.

� Subnet � This object represents a MicroNet subnet (for NCP or ARCNET). In Satchnet networks, it represents a Main LAN or an IAC TouchScreen sub-LAN.

� Touchscreen � This object represents a MicroNet/IAC touch-screen.

64 (82) TAC AB, Oct 200604-00054-01-en


� MN3x0 � This object represents any of the following:

� MN300 series controller or an MN350 series controller.

� Unifact 1201 or Unifact 2201.

� MN4x0 � This object represents any of the following:


� IAC400 or IAC420.

� Any Unifact Pro or Bonsai controller.

� MN5x0, MN6x0 � This object represents any of the follow-ing:



� IAC600 controller.

� MMC � This object represents an MMC3601 or MMC4601 controller.

9.3 Point SignalsAll signals imported from MicroNet (except for the three described below) are represented by the standard Xenta point signal icon:

The following three signal icons represent MicroNet VisiSat objects:

� Time Schedule � This object represents a MicroNet time schedule object (general).

� Optimiser Time Schedule � This object represents a time schedule for use with the MicroNet optimiser object only.

� Holiday Schedule � This object represents a MicroNet holi-day schedule object.

9.3.1 MicroNet Point Signal Attributes

All point signals imported from MicroNet (with the exception of time and holiday schedules) are of one of three data types, as shown in the DataType field of the XBuilder properties pane:

� Integer � a number that is an integer.� Real � a real number (for example, 31.4). Default = one deci-

mal place.� String � a string may contain any ASCII characters. Only two point signals, Online Status and Null Outputs, are of the bool-ean data type:

TAC AB, Oct 2006 65 (82)04-00054-01-en


� Null Outputs (present for MicroNet and IAC Controllers only (not Unifact Pro)) � this signal is used to determine if a control-ler�s outputs have been switched off (that is, set to zero) and con-trol logic processing suspended in VisiSat, or if there is a controller problem. Values are Yes (switched off) and No.

� Online Status � reports the status of the associated controller (Online or Offline).

Although some MicroNet point signals can be changed (writable) from the Xenta 555 web page, none can be overridden (forcible).

9.3.2 Time and Holiday Schedules

Along with the signals described above, signals are also available for MicroNet time and holiday schedules. You can add these signals to Link Pages within an XBuilder project (see Section 7.2, �Mapping MicroNet Time and Holiday Schedules�, on page 52).

� Time Schedule � The following is an example of an ordinary MicroNet time schedule screen as seen in a web browser.

� Optimiser Time Schedule � The following is an example of an optimiser time schedule screen as seen in a web browser.

66 (82) TAC AB, Oct 200604-00054-01-en


� Holiday Schedule � The following is an example of a holiday schedule screen as seen in a web browser.

TAC AB, Oct 2006 67 (82)04-00054-01-en


68 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 10 VisiSat to XML Conversion

10 VisiSat to XML ConversionIn order to create and use MicroNet system objects and points within XBuilder, you must first obtain an XML file (based on your chosen MicroNet network) using the VisiSat Configuration Tool. This XML file is generated from a prepared VisiSat points list and will have a suf-fix to represent MicroNet (.xmlm).

Please refer to the VisiSat Engineering Guide (Version 2.1 or later) for details of how to create a points list and generate an XML file for use in a Xenta 555 project.

However, for information purposes the method is outlined in this chap-ter.

Caution

Where the Xenta 555 is being added to an existing site that has been upgraded from a VisiSat 1.0 project to a 2.1 project, it will be neces-sary to re-create the points gallery in VisiSat.

TAC AB, Oct 2006 69 (82)04-00054-01-en

10 VisiSat to XML Conversion TAC Xenta 555, Supplement Manual

10.1 Generation of the XML file for XBuilderAssuming that the required points list has been created in VisiSat, the XML file can be created in VisiSat using the following method:

1 In the VisiSat Project Definition window, selecting the Tools � Export to TAC XBuilder menu option displays the XBuilder XML Export Wizard.

2 The required points list is selected from the Pointfile drop-down list. Clicking the Generate XML button produces the .xmlm file which can be saved in a convenient location for import to XBuilder. The default location is in the VisiSat folder in the cur-rently selected project.

Note

If points are required from more than one controller, they can (and must) be merged into a single points list using the Points Gallery dia-log box.

Tip

Before importing an XML file from VisiSat it is a good idea to ensure that points for the VisiSat points gallery are carefully selected, and if necessary renamed, so that they accurately reflect the requirements of the Xenta 555 project; it is the data from these points and their names which will eventually be represented in the Xenta Server�s web pages.

70 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 11 VisiSat IP Tunnel Configuration

11 VisiSat IP Tunnel ConfigurationVisiSat IP Tunnel configuration enables you to communicate with MicroNet via Internet/Intranet, using the Xenta 555 as a web server. With XBuilder and the VisiSat Configuration Tool installed on a single PC, you can configure VisiSat objects at a remote site.

11.1 VisiSat Port NumberIt is important to ensure that the correct port numbers are set up in XBuilder and in the VisiSat server for successful communication to take place. The port number is 7001 by default but there may be some sites where this number has already been allocated and it will then be neces-sary to use another number.

If you need to change the VisiSat port number in the MicroNet object�s properties in XBuilder, in you will also need to change the port number in VisiSat.

Refer to Chapter 4.1.2, �MicroNet Access (VisiSat Port)�, on page 27 to change the VisiSat port number in XBuilder.

Refer to VisiSat Engineering Guide (version 2.1 or later) to change the VisiSat port number in VisiSat. However, for information purposes, the method of changing the VisiSat port number is outlined here.

TAC AB, Oct 2006 71 (82)04-00054-01-en

11 VisiSat IP Tunnel Configuration TAC Xenta 555, Supplement Manual

Changing the VisiSat port number

1 Opening the VisiSat Configuration Tool and then double clicking the VisiSat server icon in the system tray produces the VisiSat � Server dialog box.

2 Selecting Settings from the Network menu produces the Config-ure Network Settings dialog box.

3 Selecting an unused network and then selecting IPTunnel from the drop-down menu and clicking Configure produces the IP Tunnel Configuration dialog box.

72 (82) TAC AB, Oct 200604-00054-01-en


4 The IP address of the Xenta 555 must be typed in the Host Name/IP Address (localhost) field.

5 The number of the VisiSat port must be typed in the Host Port Number field. It must match the number entered in XBuilder�s properties for the MicroNet object.

! Notes

� When connecting via an MN MI, the Connect via MI option should be selected.

� When connecting VisiSat to the Xenta 555, ensure that the Xenta 555 is configured with the correct communications parameters. Refer especially to the next section.

TAC AB, Oct 2006 73 (82)04-00054-01-en


Tip

If communications become erratic when using VisiSat via the IP Tun-nel, restart the VisiSat server (open the VisiSat � Server dialog box and select Restart from the Network menu option). In the majority of cases communications will be re-established; this situation can occur if the Ethernet connection is poor or is lost completely, that is, hub/switch powered down or unplugged from the controller.

74 (82) TAC AB, Oct 200604-00054-01-en


11.2 IP Tunnel and Satchnet networksBy default the the Xenta 555 is configured to expect an NCP network in the communications parameters for the imported network (refer to Chapter 6, �Setting Up MicroNet Communications Parameters�, on page 39):

However, before you can engineer a Satchnet network, you must first set up a Satchnet project in XBuilder in order to ensure successful IP Tunnel communications with the Xenta 555 (refer to Chapter 5, �Creat-ing a MicroNet Network in TAC XBuilder�, on page 33).

A completed XBuilder project is not required at this stage, only the establishment of a Satchnet network. This is achieved by the selection of a Satchnet SNP network in the drop-down box of the Network Type parameter:

You must also set the Baud Rate parameter to match the speed of your Satchnet network (either 1200 or 4800 bauds).

TAC AB, Oct 2006 75 (82)04-00054-01-en


76 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual 12 Performance Considerations

12 Performance Considerations

12.1 Network ArchitectureThe size of a MicroNet/Satchnet network within XBuilder is not lim-ited. It is quite possible to have 80 Unifact Pro controllers directly con-nected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555.

Note that Satchnet networks run four times slower than MicroNet NCP networks.

12.2 Bandwidth and PerformanceBecause both MicroNet and Satchnet networks are polled, there is a lim-ited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than oth-ers. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency.

Priority is given to signals with the fastest poll rate, therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate.

In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate).

Typically, the order of engineering priority should be:

1 Alarms

2 Web pages

3 Logs.

TAC AB, Oct 2006 77 (82)04-00054-01-en

12 Performance Considerations TAC Xenta 555, Supplement Manual

As a performance example, consider a Xenta 555 ARCNET or NCP net-work with three web clients showing three web pages (two alarm pages and one values page with 50 signals).

The Xenta 555 configuration comprises a total of 480 signals:

� 100 alarm signals set with a scan time of four seconds.

� 300 logs at a logging interval of one hour.

� 30 connection objects at a period of 10 seconds.

� 50 point signals on a values page with a fixed refresh time of 10 seconds.

In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds.

The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance.

Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time.

12.3 Web Page UpdatesIn addition to MicroNet network updates, web pages are updated at reg-ularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update.

However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web cli-ents is restricted to three for a typical Xenta 555 network as described in the example given earlier.

! Tip

Connection objects should be kept to a minimum because each con-nection comprises a read signal and a write signal (that is, two opera-tions).

78 (82) TAC AB, Oct 200604-00054-01-en

TAC Xenta 555, Supplement Manual Index

IndexAaddressing, MicroNet devices 63ARCNET 29, 40

Ggraphic page 44, 52, 54

Hholiday schedule 65, 67

IIP address 23, 25IP tunnel 27, 71

Llink page 52�53, 66

MMicroNet

device addressing 63mapping points 44objects in XBuilder 63point signal attributes 65

MicroNet interface 64MMC 65MN MI 20, 30�31, 40MNx30 65MNx40 65MNx50 65

NNCP 40network objects 64null outputs 66

Oonline status 66optimiser time schedule 65�66

Ppoint object 64�65point signals 13, 37, 41, 52, 65

attributes 65points, mapping 44

SSatchnet 13, 16, 20, 25, 29, 31, 34, 64signals, point 65subnet 64

Ttime schedule 54, 65�66touchscreen 64

VVisiSat 19, 26, 33VisiSat port 27, 40, 71

XXML file 33, 36, 38, 69

TAC AB, Oct 2006 79 (82)04-00054-01-en

Index TAC Xenta 555, Supplement Manual

80 (82) TAC AB, Oct 200604-00054-01-en

Copyright © 2006, TAC ABAll brand names, trademarks and registered trademarks are the property of their respective owners. Information con-tained within this document is subject to changewithout no-tice. All rights reserved.

04-00054-01-en

Europe / Headquarters Malmö, Sweden +46 40 38 68 50

Americas Dallas, TX +1 972-323-1111

Asia-Pacific Sydney, Australia +61 2 9700 1555

www.tac.comLast Manual Page