TAC Xenta Server â Controller - IAS Automatika

TAC Xenta Server – Controller 

Technical Manual

TAC Xenta Server – Controller 

Technical Manual

Copyright © 2007 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 Server – Controller, Technical Manual 

Contents 

Contents 

INTRODUCTION 

1 About this Manual 13 

1.1 Product Features......................................................................................................... 13 

1.2 Structure ..................................................................................................................... 15 

1.3 Typographic Conventions .......................................................................................... 16 

1.4 Prerequisites ............................................................................................................... 17 

1.5 New in This Edition ................................................................................................... 17 

1.6 Related Documents .................................................................................................... 17 

GETTING STARTED 

2 Planning the Project 21 

2.1 ACME Inc. ................................................................................................................. 21 

2.2 The Example .............................................................................................................. 22 

2.2.1 The LonWorks Network Structure.......................................................................... 24 

2.2.2 The Project Folder and Folder Structure on the Hard Disk .................................... 25 

2.3 Developing the Project............................................................................................... 26 

3 Preparatory Work in TAC Vista 27 

3.1 Removing an Existing TAC Xenta Device from the LonWorks Network ................ 27 

3.2 Udating the Network Information.............................................................................. 28 

4 Using TAC Xenta I/O Modules in the Project 29 

4.1 Deleting Unused Signal Objects ................................................................................ 30 

4.2 Adding a TAC Xenta I/O Module.............................................................................. 30 

4.3 Assigning a Neuron ID for a TAC Xenta I/O Module in TAC XBuilder.................. 33 

5 Configuring I/O Points in The Project 35 

5.1 Configuring Physical Inputs....................................................................................... 35 

5.1.1 Configuring a Universal Input U as a Digital Input................................................ 36 

5.1.2 Configuring a Universal Input U as a Linear Analog Input.................................... 36 

5.1.3 Configuring a Universal Input U as a Non-Linear (Thermistor) Input................... 37 

5.1.4 Configuring a Universal Input U as a Pulse Counting Input .................................. 38 

5.2 Configuring Physical Outputs .................................................................................... 39 

5.2.1 Configuring a Digital Output K .............................................................................. 39 

5.2.2 Configuring a Digital Output K as Pulsed Output .................................................. 40 

5.2.3 Configuring an Analog Output Y............................................................................ 41 

6 Verifying the TAC Xenta I/O Modules in the Project 45 

6.1 Saving a TAC Xenta Server Project in a TAC Vista Database.................................. 45 

6.2 Sending a TAC XBuilder Project to a TAC Xenta Server......................................... 47 

TAC AB, Sep 2007 5 (226) 

04-00123-01-en

Contents 


6.3 Viewing the TAC Xenta I/O Modules Using a Browser............................................ 48 

6.3.1 Verifying a Connected Signal in the I/O Module.................................................... 49 

7 Adding TAC Menta Objects to the Control Application 51 

7.1 Adding an Applications Folder .................................................................................. 51 

7.2 Adding a TAC Menta Object ..................................................................................... 52 

7.3 Adding a TAC Menta Application File ...................................................................... 53 

7.3.1 Importing a TAC Menta Application File to a TAC Menta Object ........................ 53 

8 Assigning a Control Task to TAC Menta Objects in The Control Application 59 

8.1 Assigning a Control Task for a TAC Menta Object................................................... 59 

8.2 Execution Order in a Control Task............................................................................. 61 

9 Modifying and Refining Objects in the Project 63 

9.1 Time Objects in the Control Application ................................................................... 63 

9.2 Alarm Objects in the Control Application.................................................................. 64 

9.3 Trend Log Objects in the Control Application........................................................... 64 

9.4 I/O Signals as SNVTs in the Control Application...................................................... 64 

9.4.1 I/O Signals as SNVTs from an Imported TAC Menta Application ........................ 64 

9.4.2 Changing Connection Block Type .......................................................................... 65 

9.5 ERR Blocks in the Control Application ..................................................................... 72 

9.5.1 ERROR Blocks in an Imported TAC Menta application ........................................ 72 

9.5.2 Adapting a TAC Menta Application for the ERROR Block Design ...................... 72 

10 Adding SNVT Objects to the Project 77 

10.1 SNVT Objects in the Control Application ................................................................. 77 

10.1.1 SNVTs from an Imported TAC Menta application................................................. 78 

10.1.2 Adding a Controller Object ..................................................................................... 79 

10.1.3 Adding a SNVT....................................................................................................... 80 

10.2 Creating a New .xif File ............................................................................................. 92 

11 Connecting Signals in the Project 93 

11.1 Connecting a Signal Between TAC Menta Objects ................................................... 94 

11.2 Connecting a Signal to a SNVT ................................................................................. 97 

11.3 Locking the Filter View.............................................................................................. 99 

11.4 Connecting a Signal to a TAC Xenta I/O Point ......................................................... 102 

11.5 Connecting a Pulse Output Signal to a TAC Xenta I/O Point.................................... 105 

11.6 Connecting a TAC Xenta I/O Online Signal.............................................................. 107 

11.7 Connecting a System Variable ................................................................................... 108 

12 Monitoring the Application Using the Service Web 109 

12.1 Viewing the Execution Time for a Control Application ............................................ 109 

12.1.1 Viewing the Control Task Execution Values .......................................................... 110 

12.1.2 Viewing the Execution Time Values for the Application in a Menta Object ......... 111 

12.2 Clearing Task Dynamic Data ..................................................................................... 112 

12.2.1 Clearing Dynamic Data for All Tasks..................................................................... 113 

12.3 Viewing the Function Block Diagram for a TAC Menta Object ............................... 113 

12.4 Daily Operations via the Web .................................................................................... 115 

13 Exporting an I/O Point List from TAC XBuilder 117 

14 Preparing Logical Signals for the Web 119 

14.1 Arranging Signals to be used in the Project ............................................................... 119 

14.1.1 Adding Signals ........................................................................................................ 119 

6 (226) TAC AB, Sep 2007 

04-00123-01-en


Contents 

REFERENCE 

15 Using TAC Xenta I/O Modules in TAC XBuilder 125 

15.1 TAC Xenta I/O Module Properties in TAC XBuilder ............................................... 125 

15.2 Adding a TAC Xenta I/O Module.............................................................................. 126 

15.3 Defining the Network Address................................................................................... 126 

15.4 Configuring the TAC Xenta I/O Points ..................................................................... 126 

16 Configuring the Device Address for a TAC Xenta I/O Module 127 

16.1 Assigning a Neuron ID for a TAC Xenta I/O Module Using TAC XBuilder ........... 127 

16.2 Configuring a Device Address for a TAC Xenta I/O Module Using TAC Vista Workstation.............................................................................................................................. 

128 

16.2.1 Configuring the Device Address for a TAC Xenta I/O Module Using the Service Pin 

Message...................................................................................................................... 128 

16.2.2 Configuring the Device Address for a TAC Xenta I/O Module Manually............. 131 

16.3 Assigning a Neuron ID for a TAC Xenta I/O Module on the TAC Xenta Server Web Site 

132 

16.3.1 Configuring the Device Address for a Replaced TAC Xenta I/O Module Using the Service 

Web..................................................................................................................... 133 

17 Using I/O Points in TAC XBuilder 135 

17.1 The Digital Input X .................................................................................................... 135 

17.1.1 Configuring a Digital Input Type X........................................................................ 136 

17.1.2 Signals in the Digital Input Type X ........................................................................ 136 

17.2 The Universal Input U................................................................................................ 137 

17.2.1 Configuring a Universal input U as Current input.................................................. 137 

17.2.2 Signals in the Universal Input U as Current Input .................................................. 138 

17.2.3 Configuring a Universal Input U as User Defined Current Input ........................... 139 

17.2.4 Signals in the Universal Input U as User Defined Current Input............................ 141 

17.2.5 Configuring a Universal Input U as Voltage Input ................................................. 141 

17.2.6 Signals in the Universal Input U as Voltage Input.................................................. 143 

17.2.7 Configuring a Universal Input U as User Defined Voltage Input........................... 143 

17.2.8 Signals in the Universal Input U as User Defined Voltage Input ........................... 145 

17.2.9 Configuring a Universal Input U as Non-linear (Thermistor) Input....................... 146 

17.2.10 Signals in the Universal Input U as Non-linear (Thermistor) Input ....................... 147 

17.2.11 Configuring a Universal Input U as SP Adjust Input.............................................. 147 

17.2.12 Signals in the Universal Input U used as SP Adjust Input...................................... 148 

17.2.13 Configuring a Universal Input U as Digital Input, On/Off Type............................ 149 

17.2.14 Signals in the Universal Input U Used as Digital Input, On/Off Type ................... 150 

17.2.15 Configuring a Universal Input U as Digital Input, Counter Type .......................... 150 

17.2.16 Signals in the Universal Input U Used as Digital Input, Counter ........................... 151 

17.3 The Non-linear Analog Input B ................................................................................. 152 

17.3.1 Configuring a Non-linear Analog Input B .............................................................. 153 

17.3.2 Signals in the B Type Analog Input........................................................................ 153 

17.4 The Digital Output K ................................................................................................. 154 

17.4.1 Configuring a Digital Output K .............................................................................. 155 

17.4.2 Signals in the K Type Digital Output...................................................................... 155 

17.5 The Analog Output Y................................................................................................. 156 

17.5.1 Configuring an Analog Output Y............................................................................ 158 

17.5.2 Signals in the Analog Output Type Y..................................................................... 159 


04-00123-01-en

Contents 


18 Using LON Wall Modules in TAC XBuilder 161 

18.1 Adding a LON Wall Module...................................................................................... 161 

18.2 Configuring the Device Address for a LON Wall Module ........................................ 162 

18.3 Configuring a LON Wall Module .............................................................................. 162 

19 TAC Menta Objects in TAC XBuilder 163 

19.1 TAC Menta Object Properties .................................................................................... 163 

19.2 The Control Task Property ......................................................................................... 164 

19.2.1 Selecting the Control Task for a TAC Menta Object.............................................. 164 

19.2.2 Changing the Control Task Assignment for a TAC Menta Object ......................... 164 

19.2.3 Removing a Control Task Assignment for a TAC Menta Object ........................... 164 

19.3 The Cycle Time Property ........................................................................................... 164 

19.4 The Execution Order Property.................................................................................... 165 

19.5 Signal Structure in TAC Menta Objects..................................................................... 165 

20 Using TAC Menta Application Files in TAC XBuilder 167 

20.1 The Specialized TAC Menta Programming Tool....................................................... 167 

20.2 Importing a TAC Menta Application File to the TAC Menta Object Using TAC XBuilder 

169 

20.3 Importing a TAC Menta Application File to the TAC Menta Programming Tool .... 169 

20.4 Loading an Application Part as a Macro .................................................................... 171 

20.5 Creating a New TAC Menta Application File............................................................ 172 

21 Using the TAC Menta Library in TAC XBuilder 177 

21.1 Adding an Existing TAC Menta Object to the TAC Menta Library.......................... 178 

21.2 Adding a New TAC Menta Object to the TAC Menta Library.................................. 180 

21.3 Editing a TAC Menta Object in the TAC Menta Library .......................................... 180 

21.4 Importing a TAC Menta Application File to a TAC Menta Library Object .............. 181 

21.5 Using a TAC Menta Object from the Library ............................................................ 182 

21.6 Making a Local Copy of a TAC Menta Object from the TAC Menta Library .......... 183 

21.7 Exporting a TAC Menta Library ................................................................................ 184 

21.8 Importing a TAC Menta Library ................................................................................ 185 

21.9 Deleting a TAC Menta Library Object....................................................................... 185 

22 Control Tasks in TAC XBuilder 187 

22.1 Control Task Properties.............................................................................................. 187 

22.1.1 The Control Task Cycle Time ................................................................................. 187 

22.2 Viewing the Control Task Assignments..................................................................... 189 

22.2.1 Viewing a Control Task Reference ......................................................................... 189 

22.2.2 Viewing the Control Task Assignment for a TAC Menta Object........................... 189 

22.3 Defining Execution Order .......................................................................................... 190 

22.3.1 Changing the Execution Order Within a Control Task ........................................... 190 

22.4 Accessing Execution Time Values for the Control Tasks.......................................... 191 

22.4.1 Control Task System Variables............................................................................... 191 

22.4.2 Creating an Alarm for the Control Task Overruns System Variable ...................... 192 

22.4.3 Viewing the Control Task Execution Times Values Via the Service Web............. 192 

22.5 Clearing Task Dynamic Data ..................................................................................... 193 

22.5.1 Clearing Task Dynamic Data via the Service Web................................................. 193 

22.5.2 Clearing Dynamic Data for all Tasks ...................................................................... 193 

22.5.3 Clearing Task Dynamic Data Using System Variables........................................... 193 

22.6 Viewing the Execution Time Values for the Application in a TAC Menta Object ... 194 


04-00123-01-en


Contents 

23 Variables in a TAC Xenta Server 700 195 

23.1 Automatically Added Variables................................................................................. 195 

23.2 Adding a Variable ...................................................................................................... 196 

23.3 Defining the Source for a Variable ............................................................................ 197 

23.4 Using the Value/State of a Variable........................................................................... 197 

23.5 Finding Signals Connected to a Variable................................................................... 197 

23.6 Disconnecting a Signal from a Variable .................................................................... 198 

24 Alarm Objects in the Control Application 199 

24.1 The TAC Xenta Server Alarm Object in a TAC Menta Object................................. 199 

24.2 Alarm Objects from an Imported TAC Menta Application ....................................... 200 

24.3 Adapting an Alarm Object ......................................................................................... 201 

24.4 Alarm Objects in a New TAC Menta Application..................................................... 201 

24.5 Creating an Alarm Page ............................................................................................. 201 

25 Time Objects in the Control Application 203 

25.1 Time Objects Imported from a TAC Menta Application........................................... 203 

25.2 Connecting a Time Object to a TAC Menta Object................................................... 204 

25.3 Time Objects in a New TAC Menta Application....................................................... 204 

25.4 Creating a Time Object Page ..................................................................................... 205 

26 Trend Logs in the Control Application 207 

26.1 Trend Log Objects Imported from a TAC Menta Application .................................. 207 

26.2 Adapting a Trend Log ................................................................................................ 207 

26.3 Trend Log Objects in a New TAC Menta Application .............................................. 208 

26.4 Creating a Trend Log Page ........................................................................................ 208 

27 I/O Signals as SNVTs in the Control Application 209 

27.1 I/O Signals as SNVTs from an Imported TAC Menta application ............................ 209 

27.2 Changing Connection Block Type ............................................................................. 209 

27.3 SNVTs as I/O Signals in a New TAC Menta Application......................................... 209 

28 ERR Function Blocks in the Control Application 211 

28.1 ERROR Blocks in an imported TAC Menta Application.......................................... 211 

28.2 Adapting an ERR Block Design ................................................................................ 211 

28.3 ERROR Blocks in a New TAC Menta Application................................................... 211 

29 Changing the Receive Timer Value 213 

29.1 Changing the Receive Timer Value in TAC Vista Workstation................................ 213 

29.2 Changing the Receive Timer Value in the TAC XBuilder Project............................ 214 

30 Connecting Rules in TAC XBuilder 215 

Index 219 


04-00123-01-en

Contents 



04-00123-01-en

1 About this Manual 

INTRODUCTION




1.1 Product Features 

This 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 instructions 

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

This manual may have been updated. 

• Please check our Docnet site at www.tac.com for the latest version. 

The Xenta Server family consists of different products: 

• TAC Xenta 511, 


• TAC Xenta 527-NPR, 





• TAC Xenta 731, and 

• TAC Xenta 913. 

Xenta Servers are equipped with several features; the major features are 

defined in the following table: 


04-00123-01-en

1 About this Manual TAC Xenta Server – Controller, Technical Manual 

Table 1.1: Major features 

Product LON I/NET MicroNet ModBus Web a I/O 

Modules 

Xenta 

Supp. b 

Xenta 511 x C x 

Xenta 511-B x x C x 

Xenta 527 x x C x 

Xenta 527-NPR x S 

Xenta 555 x x C x 

Xenta 701 x S 10 

Xenta 711 x C 10 x 

Xenta 721 x S 20 x 

Xenta 731 x x x x C 20 x 

Xenta 913 c x x x S 

a. S – Service. Means that the web interface is automatically generated in XBuilder and only contains values 

in value pages and is aimed for commissioning and service. It is not possible to have any end-user web 

content, such as graphics, trend viewers, alarm viewers or value pages. 

C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features 

for creating a full end-user web are available. 

b. Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the Lon- 

Works network beneath a Xenta 700 and are fully supported by both the Xenta 700 and TAC Vista on top 

of Xenta 700. 

c. The Xenta 913 also supports BacNet, M-Bus, and C-Bus. 


04-00123-01-en



1.2 Structure 

The 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 Reference 

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. 


04-00123-01-en


1.3 Typographic Conventions 

Throughout the manual the following specially marked texts may occur. 

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

Advanced 

Alerts you that the following information applies to complex tasks or 

tasks restricted by access. 


04-00123-01-en



1.4 Prerequisites 

1.5 New in This Edition 

To be able to profit from the contents in this manual, you are recommended 

to read the following manuals: 

• Classic Networks, Technical Manual, and/or 

• LNS Networks, Technical Manual, and 

• TAC Xenta Server – TAC Networks, Technical Manual. 

• New manual. 

1.6 Related Documents 

• Classic Networks, Technical Manual 

Part No.: 04-00015 

• LNS Networks, Technical Manual 

Part No.: 04-00016 

• TAC Graphics Editor – TGML, Technical Manual 

Part No.: 04-00026 

• TAC Vista, Technical Manual 

Part No.: 04-00021 

• TAC Menta, Technical Manual 

Part No.: 04-00030 

• TAC Xenta 500/700/911/913, Product Manual 

Part No.: 04-00071 

• TAC Xenta Server – TAC Networks, Technical Manual 

Part No.: 04-00121 

• TAC Xenta Server – Web Server, Technical Manual 

Part No.: 04-00122 

• TAC Xenta Server – Gateway, Technical Manual 

Part No.: 04-00124 


04-00123-01-en



04-00123-01-en

GETTING STARTED 

2 Planning the Project 

3 Preparatory Work in TAC Vista 

4 Using TAC Xenta I/O Modules in the 

Project 

5 Configuring I/O Points in The Project 

6 Verifying the TAC Xenta I/O Modules 

in the Project 

7 Adding TAC Menta Objects to the 

Control Application 

8 Assigning a Control Task to TAC 

Menta Objects in The Control Application 

9 Modifying and Refining Objects in 

the Project 

10 Adding SNVT Objects to the Project 

11 Connecting Signals in the Project 

12 Monitoring the Application Using the 

Service Web 

13 Exporting an I/O Point List from TAC 

XBuilder 

14 Preparing Logical Signals for the Web




2.1 ACME Inc. 

We are going to create a Xenta Server control application for the fictional 

company called ACME Inc. 

The facility is a small, two-story office building, served by roof-top 

units. The first floor houses the Lobby, Accounts, Conference Room, 

and Marketing/Management. The second floor area houses Customer 

Support and Engineering. 

The system is managed using TAC Vista. 

Lobby 

Accounts 

Conference Room 

Support 

Engineering 

Marketing and Management 

Fig. 2.1: The ACME Building. 


04-00123-01-en

2 Planning the Project TAC Xenta Server – Controller, Technical Manual 

2.2 The Example 

The Xenta Server, in the example, a Xenta 731 includes a controller. 

The existing Xenta 401 device for the roof top unit RTU4 is replaced 

and a control application to execute the same control functions is created 

to be executed in the Xenta Server together with Xenta I/O modules. 

Note 

• Although the Xenta Server described in this manual is a 

Xenta 731, a Xenta 711 could also be used for this purpose. 

The other LonWorks devices in the building are connected to the Lon- 

Works network beneath the Xenta 731. 

The Xenta 731 (called Xenta_Server_A) also includes a presentation 

system that can be accessed using a web browser anywhere on the network. 

For more information on how to create the presentation web, see the 

TAC Xenta Server – Web Server, Technical Manual. 

Important 

• The functionality to design a customized presentation web is not 

available in two types of Xenta Servers: 

• Xenta 701 and 

• Xenta 721 

In our example, we have simplified the ACME Inc. building as follows: 

VistaSRV1 

I/O Modules 

Lobby 

Xenta_Server_A 

Conf_Room 

Energy meter 

Fig. 2.2: Simplified ACME building 


04-00123-01-en



In the example in the manual, the devices are connected to the Lon- 

Works network. 

First Floor 

Lobby 

Xenta 104 

Conf_Room 


Energy meter 

Xenta Server A 


I/O-Modules 



Fig. 2.3: The devices. 

• The roof-top unit Lobby is illustrated by a Xenta 104. A secondary 

air handling unit in the conference room, Conf_Room, is illustrated 

by a Xenta 281. 

• The energy meter measures the total energy usage in the ACME 

building. 

• The roof-top unit application will be handled by the Xenta 731 and 

I/O modules. 


04-00123-01-en


2.2.1 The LonWorks Network Structure 

The LonWorks network structure is created in TAC Vista and is called 

ACME_Inc after the company. Since the building has two floors, the 

network is originally designed with its devices divided into two Xenta 

groups named 1st_Floor and 2nd_Floor. Devices located on the first 

floor belong to the Xenta group 1st_Floor. The Xenta 104 and the 

energy meter are members of the LonWorks group 1st_Floor_LW. 

With the control application running in the Xenta 731, there is no longer 

a Xenta 401 for the RTU4. Therefore, the Xenta group 2nd_Floor is no 

longer required. 

The Xenta 731 is connected to Vista via a Local Area Network or alternatively 

a Wide Area Network using the TCP/IP protocol. 

TAC Vista 

Xenta_Server_A 

LAN/WAN 

LonWorks network (ACME_Inc) 

Conf_Room Lobby Energy meter 

M1 M3 

1st_Floor 

1st_Floor_LW 

Fig. 2.4: The revised LonWorks network. 

All the devices on the LonWorks network are connected to the Lon- 

Works port on the Xenta 731. All signal values, trend logs, alarms and 

so on are handled by the Xenta 731 and the data is sent to and from Vista 

across the IP network. 

The Xenta 731 also includes a presentation of the ACME building that 

allows users to operate the system. 

The design for web access is detailed in the TAC Xenta Server – Web 

Server, Technical Manual. 


04-00123-01-en



2.2.2 The Project Folder and Folder Structure on the Hard Disk 

A project for a complete system is best placed in a directory containing 

the folders and subfolders similar to the figure below. 

Fig. 2.5: The folder structure on the hard disk. 

This structure should be prepared when the device structure of the 

project is created, as described in Classic Networks, Technical Manual 

or LNS Networks, Technical Manual. The whole structure, or parts of it, 

should be in place at this point. 

In the text that follows, we use C:\ProjectACME as the project folder. 

The Vista database (containing the network structure) requires a folder 

of its own. The folder is a subfolder to ProjectACME, and it is called 

VistaDb. 

A short description follows of the intended use for the folders and their 

contents: 

• DeviceDescr – .mta files and .xif files for the LonWorks devices. 

• Documentation – general information, for example, manuals, data 

sheets, functional descriptions, I/O lists and so on. 

• VistaDb – the Vista database. 

• Graphics – .tgml files (graphics) for the Xenta Server created 

using TAC Graphics Editor, which can be made already before the 

XBuilder project is made. 

• BackupLM – backup files of the LonMaker database, in case an 

LNS network is in use (not included in Fig. 2.5). 


04-00123-01-en


2.3 Developing the Project 

TAC XBuilder 

XBuilder is the programming tool used to program the control application 

for the Xenta server. 

References to signals are prepared in a structure for future use on web 

pages. 

TAC Menta 

The Menta programming tool is used when new Menta block diagrams 

are needed. 

The Xenta 731 will replace the Xenta Server, previously used in the 

original ACME Inc. network 

The LonWorks network is already configured in Vista and is made 

available in Vista through the Xenta Server. 

The Xenta device for RTU4 is removed and the control application is 

executed in the Xenta 731. 


04-00123-01-en




Creating the Xenta Server and connecting the LonWorks network is 

performed in Vista Workstation. 

For detailed instructions see the TAC Xenta Server – TAC Networks, 

Technical Manual. 

As the control application will be executed in the Xenta Server, this 

example describes how to remove the existing Xenta 401 from the Lon- 

Works network. 

3.1 Removing an Existing TAC Xenta Device from the 

LonWorks Network 

The application for RTU4 in the ACME installation will be executed in 

the Xenta Server instead of the Xenta 401. 

As the LonWorks network and the device structure are created in 

TAC Vista, you use Vista Workstation to make necessary changes. 

In our example, the device you want to remove the Xenta 400 for the 

RTU4. 

Tip 

• If, as in our example, you are reusing existing Xenta I/O modules, 

you can make a note of the Neuron ID for each I/O module 

before deleting them. You will find the Neuron IDs as properties 

of the I/O modules in Vista Workstation. 


04-00123-01-en

3 Preparatory Work in TAC Vista TAC Xenta Server – Controller, Technical Manual 

To remove an existing TAC Xenta device from the LonWorks 

network 

1 In Vista Workstation, in the folders pane, right-click the object you 

want to remove. In our example, 

VistaSRV1-Xenta_Server_A-ACME_Inc-2nd_Floor-RTU4. 

2 Click Delete. 

3 Click Yes to confirm. 

. 

Note 

• As the Xenta 400 in the example is the only device in the Xenta 

group called 2nd_Floor you could remove the complete Xenta 

group. 

3.2 Udating the Network Information 

The LonWorks network was changed when you deleted the Xenta group 

and the Xenta 401 device. TAC Vista alerts the user of this by showing 

the LonWorks network object with an asterix. To update the network 

information you have to make a new commission and download of the 

network. 

For more information on how to commission and download the Lon- 

Works network, see the TAC Xenta Server – TAC Networks, Technical 

Manual. 

Once you have deleted the appropriate object and updated the network 

information you will complete any additional work in XBuilder. 


04-00123-01-en


4 Using TAC Xenta I/O Modules in the Project 

4 Using TAC Xenta I/O Modules in the 

Project 

The Xenta Server object and the XBuilder project have already been 

created in Vista and stored in the Vista database. For more information, 

see the TAC Xenta Server – TAC Networks, Technical Manual. 

The LonWorks Network object that is connected to the Xenta Server is 

imported by XBuilder; it can be viewed in the network pane in 

XBuilder. The Xenta 401 device and the original I/O modules are no 

longer part of the LON network. 

The Xenta 700 devices have no onboard I/O. Xenta I/O modules are 

used when physical I/O points are needed in the control application. 

If you require I/O points you, you can add the required types and number 

of Xenta I/O modules and configure them. 

The workflow in XBuilder for adding Xenta I/O modules to the Xenta 

Server is as follows: 

• Adding Xenta I/O modules for physical in- and outputs. 

• Defining the network address for the I/O modules (Neuron ID). 

This work is performed by editing the Xenta Server project in XBuilder. 


04-00123-01-en

4 Using TAC Xenta I/O Modules in the Project TAC Xenta Server – Controller, Technical Manual 

4.1 Deleting Unused Signal Objects 

In our example, signals that were created beforehand in XBuilder are 

referring to RTU4 have lost their references, as the RTU4 Xenta 401 

device was removed from the network. These signals need to be deleted 

but will be recreated at a later stage in the project. 

For more information about the signals that have been created beforehand, 

see the TAC Xenta Server – TAC Networks, Technical Manual. 

To delete unused signal objects 

1 In Vista Workstation, in the folders pane, right-click the Xenta 

Server and click Edit. In our example, Xenta_Server_A. 

2 Log in to Vista Server. 

3 In XBuilder, in the system pane, expand 

ACME_Building_A-Air_Handling-RTU4. 

4 Right-click the Signals folder and click Delete. 

5 Click Yes. 

4.2 Adding a TAC Xenta I/O Module 

To obtain physical I/O points for a control application you must add 

Xenta I/O modules of the types and numbers that satisfy your need of 

I/O points. The Xenta I/O modules are added to the LON network, in 

the network pane. 

In our example you will add five Xenta I/O modules for the RTU4 application. 

To add a TAC Xenta I/O module 

1 In XBuilder, in the network pane, right-click the LON network 

where you want to add the I/O module. In our example, 

IP Backbone-TAC_Xenta_731-LON. 

2 Point to Add I/O Module and then click the required type of I/O 

module. In our example, click Xenta 422A. 

3 Right-click the I/O module you have added and then click 

Rename. 


04-00123-01-en



4 Enter the required name for the new I/O module. In our example, 

“M1”. 

5 Double-click the I/O module M1 to view the available I/O points. 


04-00123-01-en


Adding I/O modules one by one 

To meet the demand for I/O point allocation in your project, you will 

will frequently need more than one Xenta I/O module. Repeat the 'To 

add a Xenta I/O module' procedure as described above to add additional 

I/O modules as required. 

In our example, add the following I/O modules: 

• Add one more Xenta 422A I/O module and name it “M2”. 

• Add also two Xenta 452A I/O modules and name them “M3” and 

“M4” respectively. 

• Add one Xenta 451A I/O module and name it “M5”. 


04-00123-01-en



4.3 Assigning a Neuron ID for a TAC Xenta I/O 

Module in TAC XBuilder 

There are a number of different ways to configure the address for Xenta 

I/O modules used with the Xenta Server. The method depends on the 

availability of the network and also whether a Vista system is available. 

• Using XBuilder. 

• Using Vista Workstation, where you can, 

• use the Service Pin switch or 

• enter the Neuron ID manually. 

• Via the Xenta Server Service web pages. 

The method you choose depends on the situation, whether a Vista system 

is available and the availability of an operating network. 

For more information on other ways to configure the address for Xenta 

I/O modules see Section 16, “Configuring the Device Address for a 

TAC Xenta I/O Module”, on page 127. 

When working with XBuilder, the Xenta I/O modules are not online and 

the address is defined by entering it manually. 

In our example, you will use XBuilder to enter the Neuron ID to address 

the Xenta I/O module. 

Important 

• The Subnet and Node part of the address for I/O modules used by 

TAC Vista is configured automatically when the XBuilder 

project is saved to the Vista database. The XBuilder project is 

supplemented with the subnet and node address. 


04-00123-01-en


To assign a Neuron ID to a TAC Xenta I/O module in TAC 

XBuilder 

1 In XBuilder, in the network pane, click the I/O module that 

requires the Neuron ID. In our example, M1. 

2 In the properties pane, in the Neuron ID box, enter the Neuron ID 

for the I/O module. In our example, “04C83A1C0200”. 

3 Press Enter. 

Tip 

• You can avoid reading and typing errors when entering Neuron 

IDs by using a bar-code scanner connected to the PC and scanning 

the bar-code on the Xenta I/O module label for input. 

Assigning Neuron ID I/O module by I/O module 

Repeat the procedure above to assign the Neuron ID for all I/O modules 

used by the control application in the Xenta server. 

In our example, enter the Neuron IDs for the remaining four I/O modules: 

• Enter “123456789012” as Neuron ID for the Xenta 422A I/O 

module M2 

• Enter “04ED2F0C0200” as Neuron ID for the Xenta 452A I/O 

module M3. 


module M4. 


module M5. 


04-00123-01-en




Xenta I/O modules are added and the device address are defined. 

A suitable next step is to configure the physical I/O points in the Xenta 

Server. 

All physical I/O points in a I/O module are configured in XBuilder, by 

selecting properties, similar to using the BIND dialog in the Menta programming 

tool. The properties to define to define vary and are dependent 

upon the type of point and its usage. 

Xenta I/O points are configured by editing the Xenta Server project in 

XBuilder. 

When you edit the Xenta Server in XBuilder you must be logged on to 

the Vista server. 

For more information on how to log on to Vista server, see the TAC 

Xenta Server – TAC Networks, Technical Manual. 

In our example, a few variations of physical inputs and outputs are configured. 

For more information on how to configure other variations of physical 

inputs and outputs, see Section 17, “Using I/O Points in TAC 

XBuilder”, on page 135. 

5.1 Configuring Physical Inputs 

Physical inputs in the I/O modules are either digital or analog. The following 

input types are available in XBuilder: 

• Digital input X(n) 

• Universal input U(n) 

• Analog input, thermistor B(n) 


04-00123-01-en

5 Configuring I/O Points in The Project TAC Xenta Server – Controller, Technical Manual 

5.1.1 Configuring a Universal Input U as a Digital Input 

In our example you configure a universal input for a digital input signal. 

To configure a universal input U as a digital input 

1 In the network pane, double-click the required I/O module to view 

the signals. In our example, M1. 

2 In the network pane, click the required input. In our example, U1. 

3 In the properties view, in the Description box, enter a suitable 

description for the point. In our example, enter “SFan_Status”. 

4 In the Sensor Type list, click the required type. In our example, 

On/Off (Digital). 

5 In the Normal polarity list, click the required polarity. In our 

example, Open. 

6 In the LED behavior list, click the required behavior. In our example, 

Green. 

5.1.2 Configuring a Universal Input U as a Linear Analog Input 

In a control application you often use different types of inputs. 

The next physical input you configure in our example is a universal 

input for an analog voltage signal. 

To configure a universal input U as a linear analog input 





description for the point. In our example, enter 

“Static_Press_Sensor”. 

4 In the Sensor Type list, click the required type. In our example, 2 

-10V (Voltage). 

5 In the Minimum Value box, enter the required value. In our 

example, “0” (Zero). 

6 In the Maximum Value box, enter the required value. In our 

example, “5”. 


04-00123-01-en



7 In the Category list, click the required category. In our example, 

click pressure. 

8 In the Unit list, click the required unit. In our example, click mHg. 

9 In the Unit Prefix list, click the required unit prefix. In our example, 

click m. 

Important 

• You cannot filter the reading of the analog input. When filtering 

is required, you have to use the TimeConst parameter in the connected 

Menta block (RI). 

5.1.3 Configuring a Universal Input U as a Non-Linear (Thermistor) 

Input 

In this example you will configure a universal input for a thermistor 

temperature sensor. 

To configure a universal input U as a non-linear (thermistor) 

input 





description for the point. In our example, enter “DAT_Sensor”. 


Thermistor 1.8k (TAC). 

Important 





04-00123-01-en


5.1.4 Configuring a Universal Input U as a Pulse Counting Input 

In your projects you may want to count pulses on a digital input. 

In our example you configure a universal input for counting pulses. 

To configure a universal input U as a pulse counting input 





description for the point. In our example, enter “Pulse”. 


Counter (Digital). 

• In the Normal Polarity list, click the required polarity. In our 

example, Open. 

• In the Counter Enable Default list, click the required list item. In 

our example, click 1. 


04-00123-01-en



5.2 Configuring Physical Outputs 

5.2.1 Configuring a Digital Output K 

Physical outputs in the I/O modules are either digital or analog. The following 

are available for configuring in XBuilder: 

• Digital output K(n) 

• Analog output Y(n) 

In our example you configure a physical output for a digital on/off output 

signal. 

To configure a digital output K 



2 In the network pane, click the required output. In our example, K1. 


description. In our example, enter “SFan_StartStop”. 


click On/Off. 

5 In the Initial Value list, click the required value. In our example, 

Off. 


04-00123-01-en


5.2.2 Configuring a Digital Output K as Pulsed Output 

In our example you configure a physical output for a pulsed digital output 

signal. 

To configure a digital output K as pulsed output 



2 In the network pane, click the required output. In our example, K3. 


description. In our example, enter “Relief_Air_Dmprs_Do”. 


click Pulse. 

Important 

• When necessary, you define the value for a minimum pulse duration 

with the MinPulse parameter in the Menta PO connection 

block. 


04-00123-01-en



5.2.3 Configuring an Analog Output Y 

In a control application you may want to use more than one type of output. 

In our example you configure a physical output for an analog output signal 

with an output of 0 to 10 volt. 

To configure an analog output Y 



2 In the network pane, select the required output. In our example, 

Y1. 


description. In our example “VSD”. 

4 In the Initial Value box, enter the required value. In our example, 

“0” (Zero). 

5 In the Category list, click the required category. In our example, 

click percentage. 

6 In the Voltage at 0% box, enter the required value. In our example, 

“0” (Zero). 

7 In the Voltage at 100% box, enter the required value. In our 

example, “10”. 

Configuring I/O point by point 

Repeat the procedure above to configure all I/O points you require for 

your project. 

In our example, configure the following I/O points in each I/O module. 

In the Xenta module M1 

Configure the digital output K2. 

• Description = “Relief_Fan” 

• Sensor Type = On/Off 

• Initial value = Off 


04-00123-01-en



Configure the universal input U1. 

• Description = “C1_Status” 

• Sensor Type = On/Off (Digital) 

• Normal polarity = Open 

• LED behavior = Green 






Configure the digital input U3. 





Configure the digital input U4. 






• Description = “C1_Start_Stop” 










• Initial value = Off. 


04-00123-01-en









• Description = “RAHumiditySen”. 

• Sensor Type = 2–10 V (Voltage). 

• Minimum Value = 0 

• Maximum Value = 100 


• Description = “CO2”. 


• Category = percentage 

• Unit = ppm 


• Maximum Value = 2000. 

Important 

• The category and unit must be defined as ppm before the value of 

the Max.Value property can be entered. 

Note 

• ppm is a unit property of the percentage category. 


• Description = “Bldg_Static”. 


• Category = pressure 

• Unit = mHg 

• Unit Prefix = m 

• Minimum Value= – 0.25. 

• Maximum Value= 0.25. 


04-00123-01-en


Configure the analog input U6. 

• Description = “RAT_Sensor”. 

• Sensor type = Thermistor1.8k (TAC). 


• Description = “MAT_Sensor”. 



• Description = “OA_Temp_sens”. 


Configure the analog output Y2. 

• Description = “Mixed_Air_Dampers”. 

• Sensor type = 0–10 V 

• Initial value = 0 

• Voltage at 0% = 0 

• Voltage at 100% = 10 

• Category = percentage. 



• Description = “Fan_Speed” 

• Sensor type = 0–10 V (Voltage). 


• Maximum Value = 100 



• Description = “OAHumiditySen”. 

• Sensor type = 0–10 V (Voltage) 

• Minimum Value = 0. 

• Maximum Value = 100. 


04-00123-01-en


6 Verifying the TAC Xenta I/O Modules in the Project 

6 Verifying the TAC Xenta I/O Modules 

in the Project 

To verify the functionality of the I/O modules and view connected signals 

in the Xenta device, you can generate and send the additions you 

made to the Xenta Server project and view the result on the Xenta 

Server web site. 

The procedure for doing this is: 

• Save the project in the Vista database. 

• Send the project to the Xenta Server. 

• View the Xenta I/O modules using a web browser. 

• View signals in the Xenta I/O modules. 

6.1 Saving a TAC Xenta Server Project in a TAC Vista 

Database 

When you save the Xenta Server project in the Vista database, the 

project is automatically generated and can be sent to the device when 

the save is finished. You can do this at any stage of the project, to 

inspect the results. 

XBuilder automatically builds a web site for the Xenta Server when the 

project is generated. The pages in the web site we are currently interested 

in are Configuration and Utilities. 

Tips 

• When the Xenta Server project is generated, XBuilder verifies 

that the project does not contain errors that can cause the transfer 

to fail. If you generate the project regularly, it is easier for you to 

establish the causes of the errors. 

• If you want to generate the Xenta Server project without saving 

it, click Generate on the Project menu. 


04-00123-01-en

6 Verifying the TAC Xenta I/O Modules in the Project TAC Xenta Server – Controller, Technical Manual 

Note 

• Xbuilder automatically generates the project on the command 

Save to Vista Database. A project can only be saved if it is generated 

without errors. If there are errors, or if the project is 

incomplete, it is possible to save the project in the Xbuilder 

Project folder (File/Save or File/Save As). 

In this case as we have only added and configured Xenta I/O modules 

so the XBuilder project can be saved to the Vista database. 

To save a TAC Xenta Server project in a TAC Vista database 

• In XBuilder, on the Vista Database menu, click Save. 

The XBuilder project is now generated without errors and saved in 

Vista database. 

The project can now be sent to the Xenta Server. 


04-00123-01-en



6.2 Sending a TAC XBuilder Project to a TAC Xenta 

Server 

If the Xenta I/O modules are installed and connected to the LonWorks 

network you can test the functionality of the I/O points. When you send 

the project, the Xenta Server is referred to as the target system, that is 

the target to which the project is sent. 

For more information about sending the Xenta Server project to the 

Xenta Server, see the TAC Xenta Server – TAC Networks, Technical 

Manual. 

In our example you send the project with the configured I/O modules to 

the device. 

To send a TAC XBuilder project to a Xenta Server 

1 On the Project menu, click Send to Target. 

You have added the I/O modules to the project and you send only 

modifications of the project. 

2 Click OK. 

The Output pane monitors the progress of the transfer. 

Once the Xenta Server project has been sent to the Xenta device, you 

can view the added I/O modules and the inputs and outputs on the Xenta 

Server web site. 


04-00123-01-en


6.3 Viewing the TAC Xenta I/O Modules Using a 

Browser 

A pre-configured service web is automatically created in the Xenta 

Server when a XBuilder project is generated. The service web is used to 

commission a Xenta Server via the web, using a web browser. 

As the project progresses, more pages containing information will 

become available. 

At this stage of the project, the only addition to the Configuration and 

Utilities web pages are those that display the I/O modules and their signals. 

For information on how to log in to the Xenta Server, see the TAC Xenta 

Server, TAC Networks, Technical Manual. 

To view the TAC Xenta I/O modules 

1 In the navigator, expand Utilities-Control Applications and click 

I/O modules. 

2 In the main page, view the I/O modules, their type, subnet and 

node part of address, and Neuron IDs. 


04-00123-01-en



6.3.1 Verifying a Connected Signal in the I/O Module 

When you view the I/O modules via the web site you can also view the 

I/O points. If the I/O points are configured and signals are connected to 

the inputs, you can view dynamic values for the points. Otherwise, only 

their default values are shown. 

To verify a connected signal in the I/O module 

1 In the navigator, expand Utilities-Control Applications and click 

I/O modules. 

2 In the main page, in the Name column, click the name of the I/O 

module. In our example, click M3. 

3 In the main page, check that all values appear as expected. 


04-00123-01-en



04-00123-01-en


7 Adding TAC Menta Objects to the Control Application 

7 Adding TAC Menta Objects to the 

Control Application 

The control algorithms and logical designs of the control application are 

created from Menta objects in the Xenta Server. 

The workflow in our example in XBuilder for creating the control application 

in the Xenta Server is as follows: 

• Create Menta objects. 

• Define the Menta objects. 

• Add applications to the Menta objects. 

This work is performed by editing the Xenta Server project in XBuilder. 

7.1 Adding an Applications Folder 

You can maintain a good structure in the XBuilder project by putting all 

the control applications in a separate folder. 

In our example you use an XBuilder folder for the Menta objects. 

To add an applications folder 

1 In XBuilder, in the system pane, right-click the root folder. In our 

example, ACME_Building_A. 

2 Point to New, and then click Folder. 

3 Type the name. In our example, “Control_Applications”. 


04-00123-01-en

7 Adding TAC Menta Objects to the Control Application TAC Xenta Server – Controller, Technical Manual 

7.2 Adding a TAC Menta Object 

The major part of the control application in the Xenta Server comprises 

one or more Menta objects. Each Menta object contains a Menta application. 

Menta objects are added using the system pane in XBuilder. 

For more information on how to create new Menta applications, see 

TAC Menta, Technical Manual. 

In our example, existing Menta application files are used for the control 

application. 

To add a TAC Menta object 

1 In XBuilder, in the system pane, right-click the application folder 

where you want the control application to be located. In our example, 

the Control_Application folder. 

2 Point to New, point to Object and then click Menta Object. 

3 Type the name. In our example, “RTU4_Zones”. 

Adding Menta objects one at a time 

In order to take full advantage of the characteristic that allows the Xenta 

Server to use an application comprising a number of smaller parts, the 

control application should be constructed using several Menta objects. 

Repeat the procedure above to create all required number of Menta 

objects. 

In our example, the remaining parts of the control application is divided 

in two Menta objects. One Menta object for air handling parts and one 

for executing the logic for the chillers. 

• RTU4_AHU 

• RTU4_CoolingLogic 

Repeat the procedure above to add these to the Control_Applications 

folder. 

Note 

• The order of Menta object creation in the system pane is not 

important. However, when making connections, it can be useful 

to have the Menta objects in a given order as this facilitates an 

overview. To achieve the desired order, you can use the Move up 

and Move down buttons in the toolbar. 


04-00123-01-en



7.3 Adding a TAC Menta Application File 

The Menta objects can acquire an application code by using an existing 

Menta application file or by creating a new one. 

There are two methods of locating an existing Menta application. It can 

be imported directly to XBuilder or via an opened Menta programming 

tool. 

For more information on other ways to add the Menta applications, see 

Section 20, “Using TAC Menta Application Files in TAC XBuilder”, 

on page 167. 

In our example, existing Menta applications are imported to the Menta 

objects using XBuilder. 

7.3.1 Importing a TAC Menta Application File to a TAC Menta Object 

One of the ways to import a Menta application file is to browse and 

import the application file directly to XBuilder. 

In our example, you will use existing Menta applications for the air handling 

unit RTU4. The applications are located in the folder 

ProjectACME\DeviceDescr\Menta_Files_to_X700. 

To import a TAC Menta application file to a TAC Menta 

object 

1 In XBuilder, in the system pane, right-click the required Menta 

object. In our example, the RTU4_Zones. 

2 Click Import. 

Important 

• When you import a Menta application file and view errors and 

messages, make sure the output pane in XBuilder is visible and 

that filtering is switched off. 

• Unallowed characters in block names, inputs, outputs, alarms, 

time schedules, public signals and public constants used in the 

existing .mta file are converted to underscore characters. 

3 In the Open dialog box, browse to the required Menta application 

file. In our example, the RTU4_Zones.mta. 

Notes 

• Browsing a Menta application from XBuilder will only show 

Menta project files (files with the extension .mta). 

• To use a Menta function block diagram with the extension .aut 

you must open Menta from within XBuilder and then import the 

file. 


04-00123-01-en


4 Click Open. 

Important 

• Unallowed characters in block names, inputs, outputs, alarms, 

time schedules, public signals and public constants used in the 

existing .mta file are converted to underscore characters. 

When the import is finished, the Menta object is expanded to show the 

first sub-level of the pre-defined substructure of the object. 

A signal is located in an additional subfolder if the signal is a part of a 

Menta module. 

Physical I/Os in the imported Menta application are automatically 

replaced with new blocks, connection blocks, when a Menta application 

file is imported. 

Important 

• If the imported Menta application contains physical I/Os defined 

as SNVTs, a connection block of a type corresponding to the 

SNVT is created. The SNVT definition is thereby discarded and 

a text file for each Menta object listing all the definitions is created 

automatically. 

• The definition as SNVT is discarded, but an automatically created 

text file for each Menta object, listing all the definitions is 

created. 

• The event and location of the text file is listed in the output window, 

under the Generate tab. If you double-click the line in the 

list, the text file is opened in a text editor and you can save the 

file in a suitable location. 


04-00123-01-en



A Xenta Server alarm object is automatically created in the Alarms 

folder for each ALARM block in the imported .mta application file. 

When you import a Menta application file containing a trend log, the 

defined trend log in the .mta (source) file is automatically converted to 

a corresponding Xenta Server trend log. 

After the import to the Menta object, the trend log objects are collected 

on the same level in the system pane hierarcy as the Menta object it was 

imported to. 

You can move a Trend Log object to another suitable location by selecting 

the object and click Move up or Move down. 

The trend log object retains the signal to log and the other log settings 

when it is imported by XBuilder. 

Trend logs are numbered when they are imported. The numbering is visible 

as the last numeral in the trend log object name. If you reimport a 

trend log it will be given a new and higher trend log number. 

Important 

• Deleting a Menta object that has contained trend log objects, will 

not remove the trend log objects created by XBuilder. 

• If you import the same application or another Menta application 

a new set of Trend log objects will be added XBuilder. 

When you import a Menta application file, any existing ERR function 

block in the .mta source file will be replaced with a ERROR function 

block. 

Important 

• The ERROR function block detects fewer system errors than the 

ERR function block. 

If the original ERR block uses bits, not adjusted by the replacement 

ERROR block, some changes of the Menta application might be 

needed. 

For more information on the ERROR function block functionality, see 

the TAC Menta, Technical Manual. 


04-00123-01-en


In our example, you will work in detail with some of these objects later 

as the exercise proceeds. 

Tip 

• If an import that fails, you can edit the Menta object, and troubleshoot 

the application in the Menta programming tool. 

Adding Applications One at a Time 

When the control application uses several Menta objects, each Menta 

object contains a Menta application. 

Repeat the procedure above to import all required Menta application 

files. 

In our example, import the following Menta applications to each Menta 

object: 

• Import the RTU4_AHU.mta application to the RTU4_AHU Menta 

object. 

In this application there is one time schedule in the imported application. 

For more information on Xenta Server time objects from an 

imported Menta application, see Section 25.1, “Time Objects 

Imported from a TAC Menta Application”, on page 203. 

This Menta application contains 


04-00123-01-en



• Import the RTU4_Cool_Logic.mta application to the 

RTU4_CoolingLogic Menta object. 


04-00123-01-en



04-00123-01-en


8 Assigning a Control Task to TAC Menta Objects in The Control 

8 Assigning a Control Task to TAC 

Menta Objects in The Control 

Application 

The control application in each Menta object is executed in a control 

task. Xenta Servers have a set of control tasks, each with a preset cycle 

time. You must assign a control task to each Menta object application 

you want to be run. 

If neccesary, you can control the order of execution of the Menta object 

codes. 

To complete this work you must edit the Xenta Server project in 

XBuilder. 

For more information about control tasks in a Xenta Server 700, see 

Section 22, “Control Tasks in TAC XBuilder”, on page 187. 

8.1 Assigning a Control Task for a TAC Menta Object 

When you assign a control task to the Menta object the application in 

the Menta object will be executed within the assigned control task cycle 

time. 

In our example you assign the application code to be executed in the 

medium fast control task. 

To assign a control task to a TAC Menta object 

1 In the system pane, right-click the required Menta object. In our 

example, RTU4_Zones. 

2 Click Select Task. 


04-00123-01-en

8 Assigning a Control Task to TAC Menta Objects in The Control Application TAC Xenta Server – Controller, Techni- 

3 In the Select Control Task dialog box, click the required control 

time. In our example, click Medium Fast. 

4 Click OK. 

5 In the network pane, view the control task assignment. In our 

example, view the Control Tasks-Medium Fast-RTU4_Zones 

assignment link. 

Tip 

• You can also select the control task for a Menta object by dragging 

the required Menta object in the system pane to the required 

control task in the network pane. 


04-00123-01-en


8 Assigning a Control Task to TAC Menta Objects in The Control 

Notes 

• You can view the result of the assignment by clicking the Menta 

object and in the properties pane, in the Control task box, view 

the control task that has been assigned. 

• To view the path of the control task link you can click the Menta 

object task link and in the properties pane, in the Reference box, 

view the path of the link (reference) 

Assigning Control Tasks to Menta Objects One by One 

All Menta objects in an application must be assigned to a control task. 

Repeat the procedure above to assign control tasks for all Menta objects. 

In our example, assign the following Menta objects to the control task 

Medium: 

• RTU4_AHU 

• RTU4_Cooling_Logic 

8.2 Execution Order in a Control Task 

The execution order for the Menta objects in an application is determined 

by the position of the control task assignment link in the control 

task, as shown in the XBuilder network pane. The execution takes place 

from the top and downwards. 

For more information on control tasks in XBuilder, see Section 22.3, 

“Defining Execution Order”, on page 190. 


04-00123-01-en

8 Assigning a Control Task to TAC Menta Objects in The Control Application TAC Xenta Server – Controller, Techni- 


04-00123-01-en


9 Modifying and Refining Objects in the Project 

9 Modifying and Refining Objects in 

the Project 

When you imported the Menta applications, some objects were automatically 

created by XBuilder and you may find it necessary to modify 

them. 

A recommended workflow in XBuilder when creating the control application 

in the Xenta Server is as follows: 

• When necessary, create and connect Time objects. 

• When necessary, create, modify and connect Alarm objects. 

• When necessary, create, modify and connect Trend Log objects. 

• When necessary, modify the Menta application when using the 

ERR function block. 

9.1 Time Objects in the Control Application 

The control application in the Xenta Server uses Xenta Server Time 

objects. Time objects are automatically created by XBuilder when a 

Menta application containing time schedule blocks is imported to the 

Menta object. The original TSCH function block in the Menta application 

is replaced with a TSCHI function block. 

For more information on Xenta Server time objects, see the TAC Xenta 

Server – Web Server, Technical Manual. 

In our example, the application contains an automatically created time 

object in one of the Menta objects. The scheduling is used within the 

Menta object and you do not need to make any changes. 

Note 

• The contents of a time object can be edited in XBuilder or on a 

time object page on the Xenta Server web site. 


04-00123-01-en

9 Modifying and Refining Objects in the Project TAC Xenta Server – Controller, Technical Manual 

9.2 Alarm Objects in the Control Application 

The control application in the Xenta Server uses Xenta Server alarm 

objects. Alarm objects are automatically created by XBuilder when a 

Menta application containing an alarm is imported to the Menta object. 

Alarm objects can also be manually created. 

For more information on Xenta Server alarm objects, see the TAC Xenta 

Server – Web Server, Technical Manual. 

In our example, the application contains several automatically created 

alarm objects in the Menta objects. The logical state of each alarm are 

used within each Menta object and you do not need to make any 

changes. 

9.3 Trend Log Objects in the Control Application 

To log signals in the Xenta Server, you use Xenta Server trend log 

objects in XBuilder. Trend logs are automatically created by XBuilder 

when a Menta application containing trend logs is imported to the 

Menta object. 

Trend Log can also be manually created. 

For more information on how to create a trend log in XBuilder, see the 


In our example, the imported Menta applications contain several automatically 

created trend logs and you do not need to make any changes 

to them. 

9.4 I/O Signals as SNVTs in the Control Application 

The control application in XBuilder can use SNVTs. The Menta object 

uses the required type of connection block and separately created and 

defined SNVTs are connected. 

9.4.1 I/O Signals as SNVTs from an Imported TAC Menta Application 

Physical I/Os, defined as SNVTs, in a Menta application you import can 

be either digital (DI/DO) or analog (AI/AO) type. The I/Os are automatically 

replaced with connection blocks, when the Menta application file 

is imported. In the ordinary version of Menta the AI and AO function 

blocks are used for SNVTs of both real and integer type. In the XBuilder 

version of Menta, different connection blocks must be used. 


04-00123-01-en



9.4.2 Changing Connection Block Type 

A typical way to adapt the result of an imported Menta application using 

SNVTs, is to make sure that the automatically created connection 

blocks are the required type and if necessary replace them. 

In existing Menta applications, inputs and outputs defined as SNVTs 

are often integers. In the XBuilder version of Menta the connection 

blocks II or IO must be used. 

In our example, XBuilder automatically replaced a few AI function 

blocks with RI connection blocks when the RTU4_Zones.mta application 

file was imported. 

As these SNVTs are integers, the “crystal ball” will tell you that this will 

cause problems when connecting to the appropriate SNVTs later in the 

project.To avoid these problems, you will need to edit the imported 

Menta application and replace the RI function blocks with II function 

blocks. To make the changed II connection blocks to function properly 

in the application you will also add conversion operators. 

A suggested working method is: 

• Create one new II function block. 

• Add a Conversion operator. 

• Connect the two new elements. 

• Make a copy of the two elements. 

• Copy the Names and Descriptions from the existing (RI) function 

blocks to the new function block. 

• Disconnect and delete the existing (RI) function block. 

• Move the new two elements in position. 

• Connect the two elements. 

• Repeat the procedure for all required function blocks. 


04-00123-01-en


To change connection block type 


object. In our example, the Control_Applications-RTU4_Zones. 

2 Click Edit to open the application in Menta. 

3 In the Menta editor, right-click and then click Simple Block. 

4 In the Select Simple Block dialog, in the Simple Block box, enter 

“II” to add an integer input connection block. 

5 Click OK. 

6 While the new II block is selected, place it in a free area in the editor 

window. 

7 Click outside the selected block. 

8 In the Menta editor, right-click and then click Operator. 

9 In the Select Operator dialog, in the Operator list, click ConversionAA. 

10 Click OK. 

11 While the new ConversionAA block is selected, put it on the right 

of the added II function block. 

12 Click outside the selected block. 

13 Connect the two blocks by dragging the output of the II block to 

the input (the arrow) of the Conversion AA operator. 

The two blocks can now be used as a “master” for the replacements 

of the RI connection blocks. 


04-00123-01-en



Identifiers and descriptions are easily copied from the original RI 

blocks. 

14 Double-click the first RI block to be replaced. In our example, the 

VAV_4_1_Occ_Status block. 

15 In the Edit block RI dialog box, in the Identifier box, copy the 

complete text string. 

16 Click OK. 

17 Double-click the new II block. 

18 In the Edit block II dialog box, in the Identifier box, Paste the 

complete text string. 

19 Click OK. 

20 Copy the text string in the Description box of the first RI block to 

the new II function block. 

Now you have a correct replacement for the first RI block. 

21 Right-click the connection line from the first RI block to be 

replaced. In our example, In our example, the 

VAV_4_1_Occ_Status block. 

22 Click Detach to break the connection. 

23 Select the original RI block and then click Delete. 

24 Select the replacement II block and operator and click CTRL+C to 

make a duplicate set. 

25 Click CTRL+V to paste the copy. 

26 While the duplicate is selected, drag it to the position of the original 

block. 


04-00123-01-en


27 Connect the output of the replacement combination (the conversionAA 

operator) to the broken connection. 

28 In the File menu, click Return to XBuilder. 

29 In the TAC Menta confirmation dialog box, click Yes. 

The connection blocks are now of the correct type and you will create 

SNVTs and connect them later. 

In our example, repeat the procedure above to replace the following RI 

function blocks with II function blocks: 

• Connection block VAV_4_2_Occ_Status. 






04-00123-01-en



Changing connection block type in the RTU4_AHU Menta 

object 

In the RTU4_AHU application, XBuilder has replaced two analog output 

blocks used for SNVTs with RO connection blocks. 

• The SFAN-Term_Unit_OccCmd RO connection block. 

• The Econ-CO2_SNVT RO connection block. 

It will not be possible to connect the required SNVT type to these blocks 

Replace both connection blocks with IO (integer type) connection 

blocks the same way as described aboveand according to figures below: 

Fig. 9.1: The SFAN-Term_Unit_OccCmd RO connection block to replace. 


04-00123-01-en


Fig. 9.2: The replaced SFAN-Term_Unit_OccCmd RO connection block. 

Fig. 9.3: The Econ-CO2_SNVT connection block to replace. 


04-00123-01-en



Fig. 9.4: The replaced Econ-CO2_SNVT connection block. 

All connection blocks in our example are now of the correct type and 

you will connect them later. 


04-00123-01-en


9.5 ERR Blocks in the Control Application 

In the control application for the Xenta Server you cannot use the Menta 

ERR system block. The control application in a Xenta Server can use 

the Menta ERROR function block and also many system variables and 

signals in XBuilder. 

9.5.1 ERROR Blocks in an Imported TAC Menta application 

When you import a Menta application file, any existing ERR function 

locks in the .mta source file will be replaced with a ERROR function 

block. 

In our example, XBuilder automatically replaced a some existing ERR 

function blocks with ERROR function blocks when the 

RTU4_AHU.mta application file was imported.. 

Important 

• The Menta function blocks ERR and ERROR differ in functionality. 

For more information on these function blocks, see the TAC 

Menta, Technical Manual. 

9.5.2 Adapting a TAC Menta Application for the ERROR Block Design 

Existing Menta application sometimes need to be modified when used 

in a Xenta Server. 

A typical example is when a Menta application uses any bit value which 

the ERROR function block does not adjust. Changing the Menta function 

block diagram to use a system variable in XBuilder can often solve 

the problem. 

In our example the ERR block is used for detecting when an I/O module 

is oflline and also if any I/O point is in a forced state. An I/O module 

offline is detected by the state of bit 11 (value of the block 2048). 

Adjusting the bit 11 is handled by the new ERROR block. If an I/O point 


04-00123-01-en



is in a forced state is detected by bit 12 (value of the block 4096). 

Adjusting the bit 12 is not handled by the new ERROR block. 

To Adapt a TAC Menta Application for the ERROR Block 

Design 


object. In our example, the Control_Applications-RTU4_AHU. 

2 Click Edit to open the application in Menta. 

3 In the Menta editor window, find the I/O Alarm part of the design. 

4 Right-click the connection line to the function block to disconnect. 

In our example, the input to the lower XPB function block. 

5 Click Detach to break the connection. 

The system variable you will use is a boolean signal, ready to connect 

to an ALARM block, so you do not need to decode the value of an 

ERROR block. You can delete the XPB block. 

6 Select the lower expression block and then click Delete to remove 

the block. 

7 In the Menta editor, right-click and then click Simple Block. 


04-00123-01-en


8 In the Select Simple Block dialog box, in the Simple Block box, 

enter “BI” to add an boolean input connection block. 

9 Click OK. 

10 Locate the block in a suitable place. In our example, below the 

remaining XPB block. 

11 Double-click the new BI block. 

12 In the Edit block BI dialog box, in the Identifier box, type the 

name. In our example, “IO_Forced”. 

13 Click OK. 

14 Connect the new BI block with the FO_Alarm ALARM block by 

dragging the output of the BI block to the input (the arrow) of the 

ALARM block. 


16 In the TAC Menta confirmation dialog box, click Yes. 

17 In the system pane, view the Control Applications-RTU4_AHU-Inputs-IO_Forced 

signal 


04-00123-01-en



The new signal is prepared and you will later connect it to the IO Any 

HW Forced system variable. 

Notes 

• The above described modification is not the same as detecting 

the state of bit 12 in the original ERR function block. The modified 

design detects only I/O that are overridden by switches in 

the I/O modules. 

• Detecting this override state can also be done by changing the 

expression block to detect the value 32. 

Tip 

• You could remove ERROR block and the other XPB block and 

create a new connection block for the IO Any Offline system 

variable for the other alarm. 

Note 

• You could remove ERROR block and the other XPB block and 

create a new connection block for the IO Any Offline system 

variable for the other alarm. 


04-00123-01-en



04-00123-01-en




When you imported the Menta applications, signals that included 

SNVTs were not complete. SNVTs must be created and defined manually. 

The workflow for creating the control application in the Xenta Server is 

as follows in XBuilder: 

• Add controller objects for the SNVTs. 

• Create the required SNVTs. 

This work is carried out in XBuilder. 

Tip 

• Use the list containing the definitions of the omitted SNVT definitions 

generated when the Menta application was imported to 

help you. 

10.1 SNVT Objects in the Control Application 

The control application in Xenta Server can use SNVTs and make them 

available on the LonWorks network. The SNVTs can also be made 

available in Vista, for example, when the Xenta Server is installed as a 

LonWorks device in a classic network. 

For more information about SNVTs, see the TAC Xenta Server – Gateway, 


Important 

• Many SNVTs are 32 bit integer variables. Depending how you 

use these SNVTs in a Menta object, the Menta application will 

have to be designed to handle the variable values. For more 

information on this, see the TAC Menta, Technical Manual. 

In our example the control application uses a number of signals defined 

as SNVTs. 


04-00123-01-en

10 Adding SNVT Objects to the Project TAC Xenta Server – Controller, Technical Manual 

10.1.1 SNVTs from an Imported TAC Menta application 

A connection block of the corresponding type will be created for any 

existing I/O block in the .mta source file when you import a Menta 

application file. The signal object is located within the structure of the 

Menta object. 

Important 


as SNVTs, a connection block of a type corresponding to each 

SNVT is created. The definition as SNVT is discarded, but an 

automatically created text file for each Menta object, listing all 

the definitions is created. 


under the Generate tab. 

• If you double-click the line in the list, the text file is opened in a 

text editor and you can save the file in a suitable location. 

In our example, the control application uses a number of signals defined 

as SNVTs. You will have to create the SNVTs manually and also make 

the connection to the signal object. 


04-00123-01-en



10.1.2 Adding a Controller Object 

Controller objects are used in the Xenta Server to collect SNVTs. 

One controller object, the Node object 0, is pre-configured and cannot 

be changed. It contains the SNVTs for the Xenta Server as a device. 

If other SNVTs are used, they must be created in a controller object. 

You can create several SNVTs in one controller object. You can use 

several controller objects to structure the SNVTs to meet your requirements. 

In our example, you add four controller objects to structure the SNVTs 

to be used in the application. 

To add a controller object 

1 In the network pane, right-click IP Backbone-TAC_Xenta_731-SNVTs-LonMarkObjects 

and then click 

New Controller Object. 

2 Name the new controller object. In our example, enter 

“TERM_UNITS”. 

Adding Controller Objects One at a Time 

It is often convenient to use several control objects in order to improve 

the overview of the SNVTs. Repeat the procedure described above and 

create all required control objects. 

In our example, also add the following control objects: 

• SFAN 

• ECON 


04-00123-01-en


• COOLING 

10.1.3 Adding a SNVT 

SNVTs in the Xenta Server are added to Network Variables, a subfolder 

to a controller object. 

In our example, you add SNVTs from the zone controllers in the dedicated 

control object TERM_UNITS. 

To add a SNVT 

1 Right-click the required network variables icon. In our example, 

the TERM_UNITS-NetworkVariables. 

2 Click New SNVT. 

3 In the New SNVT dialog box, in the Name box, enter the name of 

the SNVT. In our example, enter “VAV4_1_OccStatus”. 

4 In the Type list click the required type. In our example, click occupancy. 

5 In the Direction list click the required direction. In our example, 

click Input. 

6 In the Period (s) box, enter the required value. In our example 

“60”. 


04-00123-01-en



7 Click the Backup check box for storing the momentary value of 

the signal in memory for using it until the value is updated after a 

restart of the Xenta Server. 

8 In the Initial value box, enter the required value. In our example 

“0” (zero). 

9 Click OK. 

The controller object and the SNVT are now created and the SNVT 

can be used in the XBuilder project. 

Adding SNVTs One at a Time 

In a project there are often several signals that are SNVTs. Repeat the 

procedure and create all required SNVTs. 

In our example, add SNVTs to the controller objects TERM_UNITS, 

SFAN, ECON, and COOLING. 

Add the following SNVTs to the controller object TERM_UNITS: 

Table 10.1: 

Name 

Type 

Direction 

VAV4_2_OccStatus 

occupancy 

Input 

Period 60 


04-00123-01-en


Table 10.1: 

Poll 

Backup 

Checked 

Initial value 0 

Delta 

Used only for output SNVTs 

Table 10.2: 

Name 

Type 

Direction 


occupancy 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.3: 

Name 

Type 

Direction 


occupancy 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.4: 

Name 

Type 

Direction 


occupancy 

Input 


04-00123-01-en



Table 10.4: 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.5: 

Name 

Type 

Direction 


occupancy 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.6: 

Name 

Type 

Direction 

VAV4_1_SpaceTemp 

temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.7: 

Name 

Type 


temp_p 


04-00123-01-en


Table 10.7: 

Direction 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.8: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.9: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.10: 

Name 



04-00123-01-en



Table 10.10: 

Type 

Direction 

temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.11: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.12: 

Name 

Type 

VAV4_1_SetPoint 

temp_p 


04-00123-01-en


Table 10.12: 

Direction 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 

Used only for output SNVTs. 

Table 10.13: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.14: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.15: 

Name 



04-00123-01-en



Table 10.15: 

Type 

Direction 

temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.16: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.17: 

Name 

Type 

Direction 


temp_p 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 



04-00123-01-en


Add the following SNVT to the controller object SFAN: 

Table 10.18: 

Name 

Type 

Direction 

Term_Unit_OccCmd 

occupancy 

Output 

Period 60 

Send 

Backup 

Checked 

Checked 


Delta 0.5 


04-00123-01-en



Add the following SNVT to the controller object ECON: 

Table 10.19: 

Name 

Type 

Direction 

CO2_SNVT 

ppm 

Output 

Period 60 

Send 

Backup 

Checked 

Checked 


Delta 0.5 


04-00123-01-en


Add the following SNVTs to the controller object COOLING: 

Table 10.20: 

Name 

Type 

Direction 

VAV4_1_Term_Load 

lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.21: 

Name 

Type 

Direction 


lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.22: 

Name 

Type 

Direction 


lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 



04-00123-01-en



Table 10.23: 

Name 

Type 

Direction 


lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.24: 

Name 

Type 

Direction 


lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 


Table 10.25: 

Name 

Type 

Direction 


lev_percent 

Input 

Period 60 

Poll 

Backup 

Checked 


Delta 

Used only for output SNVTs. 


04-00123-01-en


10.2 Creating a New .xif File 

The SNVTs are now created and ready to be connected to the different 

inputs and outputs in the control application. You will do this later. 

A new .xif file for the Xenta Server is automatically created when the 

project with the added SNVTs is generated. The .xif file is used by the 

LNS database to make the new SNVTs in the Xenta Server available for 

binding; this is done using LonMaker. 


04-00123-01-en




The Menta objects are now created and they have been allocated a 

Menta application code. Each Menta object is associated to a control 

task with a suitable cycle time, and the execution order for the parts of 

the application is determined. 

Signals in the application are created automatically by XBuilder or 

manually, however they are not connected. 

The continued workflow in XBuilder for creating the control application 

in our example is the following: 

• Connect signals between Menta objects. 

• Connect signals between Menta objects and SNVTs. 

• Connect signals between Menta objects and physical in- and outputs 

in the I/O modules. 

• Connect system signals to Menta objects. 

In XBuilder you can connect signals using different methods. You can 

drag and drop signals within the system pane or between the network 

pane and the system pane. You can also connect signals using the very 

useful filter view in XBuilder. 

The Filter view is normally synchronized to show all signals that can be 

connected to the selected signal in the system pane. 

The Filter view shows the combination of items from both the system 

pane and the network pane. The filter view is a tabbed version of the network 

pane. 

Using the filter view is particularly useful when you want to connect 

signals in XBuilder projects with an extensive structure. Finding an 

already connected signal is also very easy using the filter view. 

Fore more information on allowed connections of signals, see 

Chapter 30, “Connecting Rules in TAC XBuilder”, on page 215. 


04-00123-01-en

11 Connecting Signals in the Project TAC Xenta Server – Controller, Technical Manual 

11.1 Connecting a Signal Between TAC Menta Objects 

When you can connect signals between Menta objects, both signals are 

located in the system pane in XBuilder. Using the filter view pane you 

can easily view the required signals even if they are far from each other 

in the structure. 

In our example you connect a boolean type signal from the Menta object 

RTU4_Zones to the RTU4_AHU Menta object. 

To connect signals between TAC Menta objects 

1 In the system pane, expand the Menta object to view the input signal 

you want to connect. In our example, 

RTU4_AHU-Term_Units-Inputs-VAV_Bypass. 

2 In the network pane, click the Filter View tab to view the signals 

you can connect. 

3 In the filter view pane, expand the Menta object containing the 

output signal you want to connect. In our example, click 


04-00123-01-en



ACME_Building_A-Control_Applications-RTU4_Zones-Term_U 

nits-Public Signals. 

4 In the filter view pane, click the signal you want to connect. In our 

example, click RTU4_Zones-Term_Units-PublicSignals-VAV_Bypass. 


04-00123-01-en


5 In the filter view pane, on the toolbar, click Connect ( ). 

Tips 

• You can see whether an input signal is connected or not by looking 

at the signal icon in the system pane tree structure. 

• If the signal is not connected you will see a red cross at the 

bottom right part of the icon. 

• The red cross disappears when the signal is connected. 

Table 11.1: 

• You can find all the objects a signal is connected to by 

right-clicking the required signal, clicking Show Connections 

and then viewing the result in the output pane. 

• You can verify the signal and path for a connection by clicking 

the required signal and then view the path in the Connection-Reference 

box in the properties pane. 

Connecting Signals One at a Time 

In a control application there are several signals that generally need to 

be connected between various Menta objects. Repeat the procedure 

above to connect all required signals. 

In our example, also connect the following signals between Menta 

objects: 

Input Signal 

RTU4_CoolingLogic-Cooling-Inputs-C1_Fan 

Speed. 

RTU4_CoolingLogic-Cooling-Inputs- 

Cooling_FanSpeed. 

Output Signal 

RTU4_AHU-Cooling-Outputs-C1_FanSpeed. 

RTU4_AHU-Cooling-Outputs- 

Cooling_FanSpeed. 


04-00123-01-en



11.2 Connecting a Signal to a SNVT 

Sometimes in a control application, signals communicate with such 

devices as SNVTs. The SNVTs, located in the network pane, are connected 

to signals in Menta objects, located in the system pane 

Important 

• Many SNVTs are 32 bit integer variables. Depending how you 

use these SNVTs in a Menta object, you might need to connect 

the SNVT to two signals in the Menta object. For more information 

on this, see the TAC Menta, Technical Manual. 

Sometimes in your control application, SNVTs communicate with 

devices outside the XBuilder project. To achieve this communication, 

the SNVTs must be bound using a binding tool, such as LonMaker, after 

finishing your XBuilder project. 

In our example, signals are received as SNVTs from the terminal units. 

The SNVTs are located in the network pane and you use the filter view 

pane to find the required signals. 

To connect a signal to a SNVT 



RTU4_Zones-Term_Units-Inputs-VAV_4_1_Occ_Status. 



3 In the filter view pane, expand the LonMarkObject containing the 

SNVT you want to connect. In our example, click 


04-00123-01-en


IP_Backbone-TAC_Xenta_731-SNVTs-LonMarkObjects-TERM_UNITS-NetworkVariables. 

4 In the filter view pane, click the SNVT you want to connect. In our 

example, click IP_Backbone-TAC_Xenta_731-SNVTs-Lon- 

MarkObjects-TERM_UNITS-NetworkVariables-VAV4_1_OccStatus. 


Tip 

• You can view the path to the connection by clicking the signal in 

the system pane and looking in Connection-Reference box in 

the properties pane. 


04-00123-01-en



11.3 Locking the Filter View 

Table 11.2: 

Often in the control application the filter view shows a collection of signals 

you want to collect. To prevent the need to repeatedly expand the 

structure you can stop the automatic refresh of the view (lock the filter 

view). 

In our example, you use this when connecting the remaining inputs for 

occupancy. 

To lock the filter view 

1 In the filter view pane, on the toolbar, click Update ( ). 

The icon changes to show the locked view ( ). 



RTU4_Zones-Inputs-VAV_4_2_Occ_Status. 

3 In the filter view pane, click the SNVT you want to connect. In our 

example, click IP_Backbone-TAC_Xenta_731-SNVTs-Lon- 

MarkObjects-Term_Units-NetworkVariables-VAV4_2_OccStatus. 


5 In the filter view pane, on the toolbar, click Update ( ) when 

finished. 

Connecting SNVTs One at a Time 

There are generally several SNVTs to connect in a control application. 

Repeat the procedures above to connect all required SNVTs. 

In our example, connect the following SNVTs: 

Input Signal In Menta Object 

SNVT Variable 

Module Term_Units 

RTU4_Zones-Term_Units-Inputs- 

VAV_4_3_Occ_Status. 

TAC_Xenta_731-SNVTs-LonMarkObjects-TERM_UNITS-NetworkVariables-VAV_4_3_OccStatus. 



TERM_UNITS-NetworkVariables-VAV_4_4_OccStatus. 








VAV_4_1_SpaceTemp. 

TERM_UNITS-NetworkVariables-VAV_4_1_SpaceTemp. 


04-00123-01-en


Table 11.2: 


















VAV_4_1_SetPoint. 

TERM_UNITS-NetworkVariables-VAV_4_1_SetPoint. 















SNVT Variable 

Module SFAN 

SFAN-NetworkVariables-Term_Unit_OccCmd. 

Module ECON 

RTU4_AHU-Econ_Outputs-CO2_SNVT. 

ECON-NetworkVariables-CO2_SNVT. 

Module COOLING 


RTU4_AHU-SFan-Outputs-Term_Unit_OccCmd. 

RTU4_AHU-Cooling-Inputs- 

VAV4_1_Term_Load. 





COOLING-NetworkVariables- 

VAV4_1_TermLoad. 






04-00123-01-en



Table 11.2: 








SNVT Variable 








04-00123-01-en


11.4 Connecting a Signal to a TAC Xenta I/O Point 

You connect signals in the Menta objects to the required physical I/O 

points located in the network pane in XBuilder. The signals in Menta 

objects are located in the system pane and you use the filter view pane 

to find the required signals. The signal that is normally used in an I/O 

point is the Value signal. Other signals can be used for special purposes. 

For more information on I/O points in XBuilder, see the Chapter 17, 

“Using I/O Points in TAC XBuilder”, on page 135. 

In our example, you connect the status indication for the supply fan to 

the I/O point for the indicating signal. 

To connect a signal to a TAC Xenta I/O point 

1 In the system pane, expand the required Menta object to view the 

signals. In our example, 

Xenta_Server_A-Control_Applications-RTU4_AHU-SFan-Inputs 

2 Click the required input signal. In our example, click 

Xenta_Server_A-Control_Applications-RTU4_AHU-SFan-Inputs 

-SFan_Status signal. 



4 In the filter view pane, expand the LON object to view the Xenta 

I/O modules. 


04-00123-01-en



5 Expand the required I/O module to view the I/O points. In our 

example, expand M1. 

6 Expand the required I/O point to view the available signals. In our 

example, expand U1. 

7 In the filter view pane, click the I/O point signal you want to connect. 

In our example, click 

IP_Backbone-Xenta_Server_A-LON-M1-U1-Value signal. 


04-00123-01-en



Tip 

• To view the connection to an I/O point you can click the required 

signal and then view the path to the connected I/O point in the 

Connection-Reference box in the properties pane. 


04-00123-01-en



11.5 Connecting a Pulse Output Signal to a TAC Xenta 

I/O Point 

In the control application you sometimes use control algorithms where 

the output signal is a pulse with varying duration. The Menta function 

block PIDI is a typical example. 

The output from the controller PIDI is a floating point value, defining 

the duration of the requested pulse. The digital output in the I/O module 

is normally a Boolean value and the connection would not be possible 

if the two signals had be the same type. This problem is overcome 

by XBuilder automatically adapting the type of the I/O point signal to 

be a floating point (REAL) type when the digital output I/O point is 

configured as pulse. 

Important 

• The data type for the Value signal in a digital physical output, is 

normally declared as BOOL. 

• When the physical output is configured as pulse output, the data 

type for the Value signal is automatically declared as REAL, and 

allows you to connect the output signal of the PO block to the 

physical output in XBuilder. 

When you need to define a minimum duration of the output pulse, you 

assign a value in the MinPulse parameter of the Menta PO connection 

block 

In our example you connect the pulse output signal from the Menta 

block to a digital I/O point where the output type gives a pulsed output. 

To connect a pulse output signal to a Xenta I/O point 


signals. In our example, click 

Xenta_Server_A-Control_Applications-RTU4-AHU-Relief-Outputs. 

2 Click the required signal. In our example, click the 

Xenta_Server_A-Control_Applications-RTU4-AHU-Relief-Outputs-Relief_Air_Dmprs_Do 

signal. 




I/O modules. 

5 Expand the required I/O module to view the I/O points. In our 


6 Expand the required I/O point to view the available signals. In our 

example, expand K3. 


04-00123-01-en


7 In the filter view pane, click the I/O point signal you want to connect. 


IP_Backbone-Xenta_Server_A-LON-M1-K3-Value signal. 


Connecting signals one at a time 

In order to continue with the control application, you must connect all 

required signals to the appropriate I/O points. 

In our example, connect the following signals: 

Menta Signal 

Xenta I/O Point Signal 

M1 (Xenta 422A) 

RTU4-AHU-Cooling-Inputs-Pulse 

RTU4-AHU-SFan-Outputs-SFan_StartStop 

RTU4-AHU-Relief-Outputs-Relief_Fan 

IP_Backbone-Xenta_Server-LON-M1-U2-Value 

Xenta_Server-LON-M1-K1-Value 



RTU4-CoolingLogic-Cooling-Inputs-C1_Status 




RTU4-CoolingLogic-Cooling-Outputs-C1_StartStop 




Xenta_Server-LON-M2-U1-Value 









RTU4_AHU-VSD-Inputs-Static_Press_Sensor 

RTU4-AHU-ECON-Inputs-RAHumiditySen 

RTU4-AHU-ECON-Inputs-CO2_Sens 

RTU4-AHU-Relief-Inputs-Bldg_Static_Sens 

RTU4-AHU-Cooling-Inputs-DAT_Sensor 

RTU4-AHU-ECON-Inputs-RAT_Sensor 








04-00123-01-en



Menta Signal 

RTU4-AHU-ECON-Inputs-MAT_Sensor 

RTU4-AHU-Inputs-OA_Temp_sens 

RTU4-AHU-VSD-Outputs-VSD 

RTU4-AHU-ECON-Outputs-Mixed_Air_Dampers 

Xenta I/O Point Signal 



Xenta_Server-LON-M3-Y1-Value 

Xenta_Server-LON-M3-Y2-Value 

M4 (Xenta 452) 

RTU4-AHU-COOLING-Inputs-FanSpeed 


M5 (Xenta 451) 

RTU4-AHU-ECON-Inputs-OAHumiditySen 


11.6 Connecting a TAC Xenta I/O Online Signal 

In the control application in a Xenta 700 you can make system solutions 

using a variety of signals in XBuilder. 

In our example the reaction of the control application is dependent upon 

whether the Xenta I/O module M3 is online or offline. The system signal 

online for the I/O module is connected to an input in the Menta 

object. 

To connect a TAC Xenta I/O online signal 



Xenta_Server_A-Control_Applications-RTU4-AHU-VSD-Inputs. 


Xenta_Server_A-Control_Applications-RTU4-AHU-VSD-Inputs- 

Mod3 signal. 




I/O modules. 

5 Expand the required I/O module to view the online signal. In our 


6 In the filter view pane, click the online signal you want to connect. 


IP_Backbone-Xenta_Server_A-LON-M1-M3-Online signal. 



04-00123-01-en


11.7 Connecting a System Variable 

In our example you modified the Menta application for the functionality 

of the ERROR block and added an input for a system variable. 

To connect a system variable 



Xenta_Server_A-Control_Applications-RTU4-AHU-Inputs. 


Xenta_Server_A-Control_Applications-RTU4-AHU-Inputs-IO_F 

orced signal. 



4 In the filter view pane, expand the required System Variables to 

view the signals. In our example, expand IO. 

5 In the filter view pane, click the signal you want to connect. In our 

example, click IP_Backbone-Xenta_731-System Variables-IO-IO 

Any HWforced signal. 


All signals are now connected in our example project and you can continue 

and view the application on the Xenta Server web site. 


04-00123-01-en


12 Monitoring the Application Using the Service Web 

12 Monitoring the Application Using the 

Service Web 

Most of the control application is now completed and the XBuilder 

project can be sent to the Xenta Server for verification purposes. When 

you send the project, contents are automatically added to the Utilities 

pages in the Xenta Server. Using a web browser you can view essential 

information when you open the control application. 

• Save the project in the Vista database and send it to the Xenta 

Server. For more information about this procedure, see Chapter 6, 

“Verifying the TAC Xenta I/O Modules in the Project”, on 

page 45. 

12.1 Viewing the Execution Time for a Control 

Application 

The Utilities-Control Applications-Status page on the Xenta Server web 

site contains information about the execution of the five control tasks 

and the applications for commissioning and trouble shooting purposes, 

the values are shown for each task. 


04-00123-01-en

12 Monitoring the Application Using the Service Web TAC Xenta Server – Controller, Technical Manual 

12.1.1 Viewing the Control Task Execution Values 

For each control task the you can view the following values: 

• Cycle time. 

• Latest exec time. 

• Max exec time. 

• Min exec time. 

• Overruns. 

• Overruns quota. 

For more information on the execution time values in a 

Xenta Server 700, see Section 22.1.1, “The Control Task Cycle Time”, 

on page 187. 

To view the control task execution values 

1 In a web browser, log on to the Xenta Server web site. 

2 In the navigator, click Utilities-Control Applications-Status. 

3 In the main frame, click the Show detailed view link to see values 

for the different tasks. 


04-00123-01-en



12.1.2 Viewing the Execution Time Values for the Application in a 

Menta Object 

Both the information about the execution of the control task and time 

values for the application in each Menta object can be viewed using the 

service web pages. 

The values are shown for each Menta object in the control task table. 

The available values for each Menta object are: 

• Description 

• Latest exec time (ms) 

• Max exec time (ms) 

• Min exec time (ms) 

All values are cleared when the Clear task dynamic data for the control 

task is used. 

To view the execution time values for the application in a 

Menta object 



3 In the main frame, click the Show detailed view link to see the 

values for the different tasks. 


04-00123-01-en


4 In the main frame, scroll to the required control task listing. In our 

example, the Medium Control Task. 

12.2 Clearing Task Dynamic Data 

The status for the Medium Control Task and the Menta objects 

RTU4_AHU and RTU4_CoolingLogic are displayed. 

Sometimes, particularly when debugging a project, you need to clear all 

the statistics for a task. 

To clear task dynamic data 



3 In the main frame, scroll to the required control task listing. In our 

example, the Medium Control Task 

4 In the main frame, click the Clear Task Dynamic Data. 

5 Click Refresh. 

The new statistics for the task are now displayed. 


04-00123-01-en



12.2.1 Clearing Dynamic Data for All Tasks 

You can also clear dynamic data for all tasks. 

To clear dynamic data for all tasks 



3 In the main frame, in the Control Applications Status list, click 

Clear all dynamic data. 

12.3 Viewing the Function Block Diagram for a TAC 

Menta Object 

You can use the automatically created web page to to view the graphic 

representation of the application code in a Menta object. This is similar 

to the Menta programming tool. In the page you can view block and signals 

with dynamic indication of state or value as the implementation 

proceeds. Static parts, like texts are also shown in the view. 

Note 

• I/O points in Xenta I/O modules are not shown in the diagram. 

To view the function block diagram for a TAC Menta object 




04-00123-01-en


3 In the main frame, scroll the Control tasks listing to view the listing 

of the required control task. In our example, scroll to the 

Medium Control task. 

4 In the control tasks listing, scroll to view the required Menta 

object. In our example, scroll to view RTU4_AHU. 

5 In the listing, click the required Menta object link. In our example, 

the RTU4_AHU link. 

You can use the scroll bars to view the complete diagram. 

Notes 

• A Screen tip shows the signal name if you hold the pointer over 

the block. 

• The values or status of the signals are shown and are dynamically 

updated. 

• The values or status of the signals in the view cannot be altered 

by the user. 

• The appearance of connection lines show the logical state of the 

signal: 

• A thin line indicates a boolean signal being false (Zero). 

• A bold line indicates a boolean signal being true (One). 


04-00123-01-en



12.4 Daily Operations via the Web 

Depending on the type of Xenta Server, web pages for daily operations 

can be available. 

For more information on how to create the web pages, see the TAC 

Xenta Server – Web Server, Technical Manual. 


04-00123-01-en



04-00123-01-en


13 Exporting an I/O Point List from TAC XBuilder 

13 Exporting an I/O Point List from TAC 

XBuilder 

A useful utility is the facility that allows you to create a document containing 

the information about the connections made in a project. 

One list is created for the entire project; divided into two separate 

groups, one for the signals to Xenta I/O modules and the other for the 

signals to Menta objects. 

The created list can be saved in any location for further processing. The 

list can be saved as a text file or in XML format. 

To export an I/O list 

1 In XBuilder, on the Tools menu, click Export I/O list. 

2 Under File, click the browse button and browse to the folder 

where you want to save the list file. In our example, browse to the 

ProjectACME\Documentation folder. 

3 In the File Name box, enter the required name for the list file. In 

our example, enter “RTU4_IO”. 


04-00123-01-en

13 Exporting an I/O Point List from TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

4 In the Save as type list, click the required file type. In our example, 

“Text files (*.txt)”. 

5 Click Save. 

6 In the Export I/O List dialog box, in the Select type(s) area, 

select the required range of types to export. 

7 Click Create File. 

The exported I/O list file is saved and automatically opened in 

Note Pad. 

8 In the Export I/O List dialog box, click Close. 


04-00123-01-en


14 Preparing Logical Signals for the Web 


This chapter describes a way to arrange signals so they are identical to 

the collection prepared in the TAC Xenta Server – TAC Networks, Technical 

Manual. 

14.1 Arranging Signals to be used in the Project 

14.1.1 Adding Signals 

Physical signals in the network connected to the Xenta Server are used 

in the graphic presentation, for alarms, trend logging and other usage. 

To simplify the engineering, the signals are connected to signal objects 

in XBuilder. 

In the following example, signals from the control application for 

RTU4, required by an example graphic in the TAC Xenta Server – Web 

Server, Technical Manual. 

In order for a graphic to display values from a signal or for a trend log 

to log a value you will reference the signal from the graphic or the trend 

log. These signals need to be added in XBuilder before they can be referenced. 

To simplify the engineering the signals are best placed in a separate 

folder for each device. For large applications it may be useful also to 

imitate the Menta module structure in the folder. 

To add signals 

1 In the system pane, right-click the folder where you want to add a 

folder for your signals. In our example, ACME_Building_A-Control 

Applications. 

2 Point to New and click Folder. 


04-00123-01-en

14 Preparing Logical Signals for the Web TAC Xenta Server – Controller, Technical Manual 

3 Enter the name of the new folder. In our example, 

“RTU4_Signals”. 

4 Use the Up Arrow or Down Arrow to move the new folder to a 

location where it is suitable. In our example, locate the folder as a 

sub-folder to Control Applications. 

5 In the properties pane, under Page, in the Visible box, click the 

visibility option. In our example, False 

6 Add subfolders according to the following figure. 

7 In the system pane, drag the required signal to the destination 

folder. In the example, drag ACME_Building_A-Control Applications-RTU4_AHU-Cooling-Public 

Signals-DAT to 


04-00123-01-en



ACME_Building_A-Control Applications-RTU4_Signals-Cooling 

in the system pane. 

Adding Signal by Signal 

Table 14.1: Signals required in the RTU4 graphic. 

Complete the RTU4_Signals folder with all required signals using the 

procedure described above. In our example add the following signals: 

Signals in the Menta objects 

RTU4_AHU-Cooling-Public Signals-DAT 

RTU4_CoolingLogic-Inputs-C1_Status 




RTU4_CoolingLogic-Inputs-Cooling_FanSpeed 

RTU4_AHU-Econ-Public Signals-CO2 

RTU4_AHU-Econ-Public Signals-MAT 

RTU4_AHU-Econ-Outputs-Mixed_Air_Dampers 

RTU4_AHU-Econ-Public Signals-OAHumidity 

RTU4_AHU-Econ-Public Signals-OAT 

RTU4_AHU-Econ-Public Signals-RAHumidity 

RTU4_AHU-Econ-Public Signals-RAT 

RTU4_AHU-Relief-Outputs-Relief_Air_Dmprs_Do 

RTU4_AHU-Relief-Outputs-Relief_Fan 

RTU4_AHU-SFan-Public Signals-SFan_MC 

Signals in the 

RTU4_Signals folder 

-Cooling-DAT 

-Cooling-C1_Status 




-Cooling-Cooling_FanSpeed 

-Econ-CO2 

-Econ-MAT 

-Econ-Mixed_Air_Dampers 

-Econ-OAHumidity 

-Econ-OAT 

-Econ-RAHumidity 

-Econ-RAT 

-Relief-Relief_Air_Dmprs_Do 

-Relief-Relief_Fan 

-SFan-SFan_MC 


04-00123-01-en

14 Preparing Logical Signals for the Web TAC Xenta Server – Controller, Technical Manual 

Table 14.1: Signals required in the RTU4 graphic. 

Signals in the Menta objects 

RTU4_AHU-SFan-Outputs-SFan_Start_Stop 

RTU4_AHU-SFan-Inputs-SFan_Status 

RTU4_Zones-Term_Units-Public Signals-VAV__Bypass 

RTU4_AHU-VSD-Public Signals-DAP_SP 

RTU4_AHU-VSD-Public Signals-Static_Pressure 

Signals in the 

RTU4_Signals folder 

-SFan-SFan_Start_Stop 

-SFan-SFan_Status 

-Term_Units-VAV__Bypass 

-VSD-DAP_SP 

-VSD-Static_Pressure 

When you have finished the result should look like this: 

Tip 

• Verify that the Xenta Server project appears as expected, by saving 

the Xenta Server project in the Vista database and sending it 

to the Xenta Server. 

You can now use the signals in the RTU4_Signals folder for any purpose 

in the project: graphic presentation, trend logging and so on. For 

more information about creating a presentation of the project, see the 



04-00123-01-en

REFERENCE 

15 Using TAC Xenta I/O Modules in 


16 Configuring the Device Address for a 

TAC Xenta I/O Module 

17 Using I/O Points in TAC XBuilder 

18 Using LON Wall Modules in TAC 

XBuilder 

19 TAC Menta Objects in TAC XBuilder 

20 Using TAC Menta Application Files in 


21 Using the TAC Menta Library in TAC 

XBuilder 

22 Control Tasks in TAC XBuilder 

23 Variables in a TAC Xenta Server 700 

24 Alarm Objects in the Control 

Application 

25 Time Objects in the Control 

Application 

26 Trend Logs in the Control Application 

27 I/O Signals as SNVTs in the Control 

Application 

28 ERR Function Blocks in the Control 

Application 

29 Changing the Receive Timer Value

30 Connecting Rules in TAC XBuilder


15 Using TAC Xenta I/O Modules in TAC XBuilder 

15 Using TAC Xenta I/O Modules in 


The Xenta 700 devices have no onboard I/O. Xenta I/O modules are 

used when physical I/O points are needed in the Xenta Server control 

application. If yopu need I/O (points), you can add the required types 

and number of I/O modules and configure them. 

The suggested workflow in XBuilder for adding Xenta I/O modules to 

the Xenta Server is as follows: 

• Add Xenta I/O modules (for physical in- and outputs) 

• Define the network address (Neuron ID) 

• Configure the Xenta I/O points 

15.1 TAC Xenta I/O Module Properties in TAC 

XBuilder 

Xenta I/O modules are added to the LON network, in the network pane. 

A Xenta I/O module has the following properties in XBuilder: 

Table 15.1: 

General. 

Property 

Name. 

Description. 

Subnet. 

Node. 

Neuron ID. 

User’s designation of the I/O module. 

I/O module type. 

The subnet part of the device address, used 

by TAC Vista to address the device in a 

LonWorks network. 

The node part of the device address, used 

by TAC Vista to address the device in a 

LonWorks network. 

The Neuron ID, used to address the device 

in a LonWorks network. 

Settings. 


04-00123-01-en

15 Using TAC Xenta I/O Modules in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

Table 15.1: 

Property 

Min Send Time. 

Max Send Time. 

Reconnect Timeout. 

Fast CNT Reporting. 

Used when an input in the I/O module is 

configured as pulse counting. 

False (0). 

Pulse counting is fast. To reduce the 

load on the LON network the values 

are sent every 10 seconds. 

True (1). 

Pulse counting is normal. Each new 

value is directly sent on the LON network. 

Default value is 0 (False). 

15.2 Adding a TAC Xenta I/O Module 

A detailed description of how to to add a Xenta I/O modules is described 

in Section 4.2, “Adding a TAC Xenta I/O Module”, on page 30 

15.3 Defining the Network Address 

Different methods to configure the device address for an I/O module is 

described in Section 16, “Configuring the Device Address for a TAC 

Xenta I/O Module”, on page 127 

15.4 Configuring the TAC Xenta I/O Points 

How to configure Xenta I/O Points is described in Section 17, “Using 

I/O Points in TAC XBuilder”, on page 135. 


04-00123-01-en


16 Configuring the Device Address for a TAC Xenta I/O Module 

16 Configuring the Device Address for a 

TAC Xenta I/O Module 

There are a number of ways to configure the device address for Xenta 

I/O modules used with the Xenta Server. The way of working depends 

on the availability of network and also whether a Vista system is available. 

The methods are: 

• Using XBuilder. 

• Using Vista Workstation. 

• Using the Service Pin message. 

• Entering the Neuron ID manually. 

• Via the Service web pages. 

Important 

• The subnet and node part of the address for I/O modules, used by 

TAC Vista, is configured automatically when the XBuilder 

project is saved to the Vista database. The subnet and node 

address is also supplemented to the XBuilder project. 


Module Using TAC XBuilder 

The way to define the The Neuron ID, used to communicate with the I/O 

module after downloading the XBuilder project to the Xenta Server, is 

described in Section 4.3, “Assigning a Neuron ID for a TAC Xenta I/O 

Module in TAC XBuilder”, on page 33. 


04-00123-01-en

16 Configuring the Device Address for a TAC Xenta I/O Module TAC Xenta Server – Controller, Technical Manual 

16.2 Configuring a Device Address for a TAC Xenta 

I/O Module Using TAC Vista Workstation 

The address can be configured using Vista Workstation if the Xenta 

Server is a device in a Vista system (a subsystem to Vista) and the Lon- 

Works network is operating. 

Using TAC Vista Workstation, there are two ways to configure the 

address: 

• Using the Service Pin message. 

• Entering the Neuron ID manually. 

TAC Vista assigns a subnet and a node address for the I/O-module and 

updates the XBuilder project with the Neuron ID, the subnet and the 

node address when an XBuilder project is saved in the TAC Vista database. 

Important 

• The subnet and node part of the address for I/O modules, used by 

TAC Vista, is configured automatically when the XBuilder 

project is saved to the Vista database. The XBuilder project is 

supplemented with the subnet and node address. 

16.2.1 Configuring the Device Address for a TAC Xenta I/O Module 

Using the Service Pin Message 

Using the service pin message to configure the device address in Vista 

Workstatition is usable when the identity of which device transmitting 

the message is known. 

There is a condition for using the service pin message to configure the 

device address. 

Important 

• To make it possible for Vista Workstation to receive the service 

pin message from Xenta I/O modules, Vista needs a LonWorks 

Network device in the Xenta Server. 

• You add a LonWorks Network device in Vista Workstation by 

right-clicking the Xenta Server, pointing to New, pointing to 

Device, and then clicking LonWorks Network. 


04-00123-01-en



To configure device address for a TAC Xenta I/O module 

using the Service Pin Message 

1 In Vista Workstation, in the folders pane, click the device with the 

required I/O module.l 

2 In the main window, in the object view, double-click $IO to view 


3 Double-click the required I/O module to se the properties. In our 

example, double-click the M1 (the Xenta 422 I/O module). 

4 Click the Neuron ID box to access the SP button. 


04-00123-01-en


5 In the Neuron ID box, click the SP button to start the searching 

for a Service Pin message. 

6 On the Xenta I/O module, press the Service Pin switch. 

7 When the Neuron ID message has been received, click OK to 

close the dialog. 

The device address for the I/O module is now configured. 

Important 

• When a LonWorks Network device is added in Vista Workstation, 

TAC Vista changes the value for the receive timer in the 

XBuilder project. The changed value (24576 ms) is often too 

long for maintaining good communication when many Xenta I/O 

modules are connected to the Xenta Server. In such cases the 

value must be decreased until the required communication is 

achieved. 

• You decrease the value for the receive timer in XBuilder, by 

clicking LON in the Network pane and selecting an appropriate 

value in the properties pane, under File Transfer Timers, in the 

Receive Timer property list. 

When the Xenta Server is a subsystem to TAC Vista Workstation, 

the value for the timer shall be changed in TAC Vista Workstation. 

For more information about changing the value, see 

Chapter 29.1, “Changing the Receive Timer Value in TAC Vista 

Workstation”, on page 213. 


04-00123-01-en



16.2.2 Configuring the Device Address for a TAC Xenta I/O Module 

Manually 

It can be advantageous to enter the Neuron ID manually in Vista Workstation 

at an early stage in the project as you have more control over the 

final location of each device at this stage. 

To configure the device address for a TAC Xenta I/O 

module manually 

1 In Vista Workstation, in the folders pane, click the device with the 

required I/O module. 

1 In the main window, in the object view, double-click $IO to view 


2 Double-click the required I/O module to view the properties. 

3 In the Neuron ID box, enter the required Neuron ID. 

4 Click Enter. 

The device address for the I/O module is now configured. 

Tip 

• You can avoid reading and typing errors when entering Neuron 

IDs by using abar-code scanner connected to the PC and scanning 

the bar-code on the Xenta I/O module label for input. 


04-00123-01-en



Module on the TAC Xenta Server Web Site 

Configuring the device address for a Xenta I/O module can also be done 

by entering the Neuron ID via the service menu, accessible via the web. 

To assign a Neuron ID for a TAC Xenta I/O module on the 

TAC Xenta Server web site 

For information about how to browse and log on to the Xenta Server, 

see, TAC Xenta Server – TAC Networks, Technical Manual. 

1 Start Internet Explorer and log on to the Xenta Server. 

2 In the Navigator, click Utilities-Control Applications-I/O modules. 

3 In the main frame, in the Neuron ID box for the required I/O module, 

enter the required Neuron ID string. 

4 Click Save. 

The device address for the I/O module is now configured and the 

Xenta 731 can now communicate with the I/O module. 

Important 

• During any subsequent download to the Xenta 731, the following 

will occur. If the XBuilder project contains another Neuron ID 

for the I/O module, the user will be asked which Neuron ID 

should be used, the one in the project or in the one in the device. 


04-00123-01-en



16.3.1 Configuring the Device Address for a Replaced TAC Xenta I/O 

Module Using the Service Web 

Configuring the device address via the service menu is particularly useful 

when replacing an existing I/O module used by the Xenta Server. 

To configure the device address for a replaced TAC Xenta 

I/O module using the service web 

1 Physically remove the I/O module that needs to be replaced. 

2 Insert the replacement I/O module. 

The LED on the I/O module starts to blink rapidly. This is because 

it has not been assigned an address. 

3 Start Internet Explorer and log on to the Xenta Server. 

4 In the Navigator, click Utilities-Control Applications-I/O modules. 

5 In the Control Applications page, in the Neuron ID box for the 

required I/O module, enter the required Neuron ID string. 

6 Click Save. 

The new Neuron ID is saved and after a short while, the LED on the 

I/O module blinks normally. The I/O module has now been 

assigned a address. 

Note 

• All configured signals in the I/O module retain their properties in 

the replaced module. 

Important 

• During any subsequent downloads to the Xenta 731, the following 

will occur. If the XBuilder project contains another Neuron 

ID for the I/O module, the user will be asked which Neuron ID 

should be used, the one in the project or the one in the device. 


04-00123-01-en



04-00123-01-en




17.1 The Digital Input X 

When you work with a control application in a Xenta Server, each physical 

I/O point in a Xenta I/O module you use is configured in XBuilder. 

Physical I/Os in the Xenta I/O modules are either digital or analog. You 

configure the following I/O points in XBuilder: 

• Digital inputs (X). 

• Universal inputs (U). 

• Analog inputs, thermistor type (B). 

• Digital output (K). 

• Analog output (Y). 

Configuring an I/O point includes selecting properties, similar to using 

the BIND dialog in the Menta programming tool. The properties to 

define variy and depend on the type of point and the actual usage. 

All properties for signals in an I/O point are defined by the configuration 

of the I/O point. 

For more information on signals in a Xenta Server, see the TAC Xenta 

Server – TAC Networks, Technical Manual. 

The digital input X in a Xenta I/O module can be used for the following 

applications: 

• On/off digital input. 

• Pulse counting digital input. 

The digital input X, has the properties: 

Table 17.1: 

General 

Property 

Name 

Description 

I/O Point Type 

Point designation X(n), in the I/O module. 

User’s description of the I/O point. 

Digital Input. 


04-00123-01-en

17 Using I/O Points in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

Table 17.1: 

Property 

Sensor Type 

Normal Polarity 

User selected input type. 

• On/Off. 

• Counter. 

User selected normal state for the contact. 

• Open. 

• Closed. 

Measurement System 

Category 

The category is used to automatically assign a 

measurement unit to a signal. 

A boolean signal has the property: 

• No category. 

Unit 

Unit Prefix 

A boolean signal has no unit. 

A boolean signal has no unit prefix. 

17.1.1 Configuring a Digital Input Type X 

The digital input X in a Xenta I/O module can be used for on/off or pulse 

counting detection. 

The Sensor Type property determines the application. 

To configure a digital input type X 

17.1.2 Signals in the Digital Input Type X 

1 In the network pane, select the required input. 

2 In the properties view, in the Description box, enter an optional 

description. 

3 In the Type list, click the required type. 

4 In the Normal polarity list, click the required polarity. 

A digital input X has the following signals: 

• The Value signal. 

• The CounterEnable signal. 

The Value signal 

The Value signal in a digital input X represents the logical state of connected 

equipment. 


04-00123-01-en



The CounterEnable signal 

17.2 The Universal Input U 

The CounterEnable signal in a digital input X is Applicable only when 

the Sensor Type property is Counter. 

The signal starts and stops counting changes on the input. 

• When the signal is true (1), the counting is enabled. 

• When the signal is false (0), the counting is disabled. 

The universal input U in a Xenta I/O module can be used for the following 

range of applications: 

• Linear Analog input. 

• Non-Linear Analog input. 

• SP adjustment input. 

• Digital input. 

You define the field of application using the Sensor Type property. The 

various types have different sets of properties. 

Percentage is the default category for a universal input, when it is configured 

as a linear analog input. When this percentage is used, the input 

signal level is calculated to be a value ranging from the value of the 

Minimum Value property (0) to the value of the Maximum Value property 

(100). 

17.2.1 Configuring a Universal input U as Current input 

The universal input U defined as Current input, is a linear analog input 

used for the following applications: 

• 0–20 mA. 

• 4–20 mA. 

• User Defined. 

The universal input U, configured as current input, has the properties: 

Table 17.2: 

Property 

General 

Name 

Description 

IO Point Type 

Point designation U(n), in the I/O module. 


Universal Input. 


04-00123-01-en


Table 17.2: 

Property 

Sensor Type. 

Minimum Value 

Maximum Value 

User selected input range 

• 0-20 mA 

• 4-20 mA. 

User defined minimum value for the converted 

reading of the input. 

Default value is 0. 

User defined maximum value for the converted 




Category 



Default category for the input: 

• percentage. 

Unit 

Unit Prefix 

The unit for an input is automatically selected 

by the category property. 

Can be changed by the user from the Unit list. 

Optionally selected by the user from the Unit 

Prefix list. 

To configure a universal input U as current input 



description. 

3 In the Sensor Type list, click the required input range. 

4 In the Minimum Value box, enter the required value. 

5 In the Maximum Value box, enter the required value. 

17.2.2 Signals in the Universal Input U as Current Input 

A universal input U used as current input has the following signals: 


The Value signal is the analog value from connected equipment. 

• The CounterEnable signal does not apply to the analog input. 


04-00123-01-en



17.2.3 Configuring a Universal Input U as User Defined Current Input 

You can also configure the Universal input U to read any input current 

within the range from 0 (zero) to 20 mA. 

Changing the input range is done using two properties for the input, the 

Multiplier and the Offset properties. 

Selecting the range for the signal values is done, using the Minimum 

Value and Maximum value properties. 

The universal input U, configured as user defined current input, has the 

properties: 

Table 17.3: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Multiplier 

Offset 

Minimum Value 

Maximum Value 


Users description of the I/O point. 


User selected type. 

• User defined (Current). 

The ratio of maximum input range and actual 

input range. 

The value added to the lowest actual input signal 

level to result in 0 (zero). 








Category 





Unit 

The unit for an input is automatically selected by 

the category property. 



04-00123-01-en


Table 17.3: 

Property 

Unit Prefix 


Prefix list. 

When you configure a universal input for a user defined input current 

range you change the input range by using the Multiplier and Offset 

properties. 

The Multiplier property is a value for the ratio of maximum input range 

and actual input range. 

The Offset property is a value added to the lowest actual input signal 


Example 

Assume an application where a signal input level of 4 mA is the lowest 

level and 20 mA is the highest input level. 4 mA shall result in 0 percent, 

20 mA shall result in 100 percent. 

Multiplier = Maximum input range / (Highest actual input signal 

level – Lowest actual input signal level). 

The maximum input range for the current input is 0 mA – 20 mA = –20 

mA. 

The required input span is 20 mA – 4 mA = 16 mA. 

The ratio between maximum and actual range is 20/16 = 1.25. 

The above calculations gives us a Multiplier = 1.25. 

The Offset value is always calculated for a signal value converted to a 

range from 0 to 100. 

The actual input level that shall give 0 (zero) is 4 mA. 

Offset = Input level for zero * Multiplier * (Signal value range/Maximum 

input range) *(-1) 

Offset = 4 * 1.25 * (100/20) * (-1) 

The above calculations gives us an Offset = –25. 


04-00123-01-en



Adapting the converted values to other ranges can be done, using the 

Minimum Value and Maximum value properties. 

Important 

• Using the Minimum Value and Maximum value properties to 

adapt the converted value has no influence on the calculation of 

Multiplier and Offset. 

• It can be necessary to change the Category property to a property 

that allows entering the required values for the Minimum 

and Maximum properties. 

To configure a universal input U as user defined current 

input 



description. 

3 In the Sensor Type list, click User Defined (Current). 

4 In the Multiplier box, enter the required value. 

5 In the Offset box, enter the required value. 



17.2.4 Signals in the Universal Input U as User Defined Current Input 

A universal input U configured as user defined current input has the following 

signals: 




17.2.5 Configuring a Universal Input U as Voltage Input 

The universal input U defined as Voltage input, is a linear analog input 

used for the following applications: 

• 0–1 volt. 

• 0–5 volt. 

• 0–10 volt. 

• 2–10 volt. 

• User defined. 


04-00123-01-en


The universal input U, configured as voltage input, has the properties: 

Table 17.4: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Minimum Value 

Maximum Value 




User selected input range. 

• 0-1 volt. 

• 0-5 volts. 

• 0-10 volts. 

• 2-10 volts. 








Category 

The Category is used to automatically assign a 




Unit 

Unit Prefix 





Prefix list. 


04-00123-01-en



To configure a universal input U as voltage input 



description. 

3 In the Sensor Type list, click the required input range. 



17.2.6 Signals in the Universal Input U as Voltage Input 

A universal input U, configured as voltage input, has the following signals: 




17.2.7 Configuring a Universal Input U as User Defined Voltage Input 

You can also configure the Universal input U to read any input voltage 

within the range from 0 (zero) to 10 volt. 

The universal input U, configured as user defined voltage input, has the 

properties: 

Table 17.5: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Multiplier 

Offset 

Minimum Value. 




User selected type 

• User defined (Voltage). 

The ratio of maximum input range and actual 

input range. 

The value added to the lowest actual input signal 






04-00123-01-en


Table 17.5: 

Property 

Maximum Value. 





Category 





Unit 

Unit Prefix 





Prefix list. 

When you configure a universal input for a user defined input voltage 

range you change the input range by using the Multiplier and Offset 

properties. 

The Multiplier property is a value for the ratio of maximum input range 

and actual input range. 

The Offset property is a value added to the lowest actual input signal 


Example 

Assume an application where a signal input level of 2 volts is the lowest 

level and 8 volts is the highest input level. 2 Volts shall result in 0 percent, 

10 volts shall result in 100 percent. 

Multiplier = Maximum input range / (Highest actual input signal 

level – Lowest actual input signal level). 

The maximum input range for the voltage input is 10 volts – 0 Volts = 

10 Volts. 

The required input span is 10 volt – 2 Volt = 8 volts. 

The ratio between maximum and actual span is 10/8 = 1.25. 

The above calculations gives us a Multiplier = 1.25. 

The Offset value is always calculated for a signal value converted to a 

range from 0 to 100. 

The actual input level that shall giving 0 (zero) is 2 Volts. 


04-00123-01-en



Offset = Input level for zero * Multiplier * (Signal value range/Maximum 

input range) *(–1) 

Offset = 2 * 1.25 * (100/10) * (–1) 

The above calculations gives us an Offset = –25. 

Adapting the converted values to other ranges can be done, using the 

Minimum Value and Maximum value properties. 

Important 

• Using the Minimum Value and Maximum value properties to 

adapt the converted value has no influence on the calculation of 

Multiplier and Offset. 

• It can be necessary to change the category property to a property 

that allows entering the required values for the Minimum and 

Maximum properties. 

To configure a universal input U as user defined voltage 

input 



description. 

3 In the Sensor Type list, click User Defined (Voltage). 

4 In the Multiplier box, enter the required value. 

5 In the Offset box, enter the required value. 



17.2.8 Signals in the Universal Input U as User Defined Voltage Input 

A universal input U, configured as user defined voltage input, has the 

following signals: 





04-00123-01-en


17.2.9 Configuring a Universal Input U as Non-linear (Thermistor) 

Input 

The universal input U configured as Non-linear (Thermistor) input is a 

Non-Linear Analog input. You can define the non-linear input for the 

applications: 

• Thermistor 1.8 k (TAC). 

• Thermistor 10 k (CSI). 

The universal input U, configured as Non-linear (Thermistor) input, has 

the properties: 

Table 17.6: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 





• Thermistor 1.8k (TAC) 

• Thermistor 10k (CSI) 


Category 




• temperature. 

Unit 

Unit Prefix 





Prefix list. 


04-00123-01-en



To configure a universal input U as non-linear (thermistor) 

input 



description. 

3 In the Sensor Type list, click the required thermistor type. 



17.2.10 Signals in the Universal Input U as Non-linear (Thermistor) 

Input 

A universal input U configured as non-linear (thermistor) input has the 

following signals: 




17.2.11 Configuring a Universal Input U as SP Adjust Input 

The universal input U configured as SP Adjust input is a analog input 

used for setpoint adjustments. You can configure the adjustment range 

from ±1 degree to ±9 degrees in steps of 1 degree. 

The measurement system unit for the adjustment range, depends on the 

Unit property of the input. 

The universal input U as SP Adjust input has the properties: 

Table 17.7: 

Property 

General 

Name 

Description 

IO Point Type 





04-00123-01-en


Table 17.7: 

Property 

Sensor Type 

User selected adjustment range. 

• SP adjust ±1. 










Category 



category for the input: 


Unit 

Unit Prefix 

The unit for an input is automatically selected by 




Prefix list. 

To configure a universal input U as SP adjust input 



description. 

3 In the Sensor Type list, click the required SP adjust range. 

17.2.12 Signals in the Universal Input U used as SP Adjust Input 

A universal input U used as SP adjust input has the following signals: 





04-00123-01-en



17.2.13 Configuring a Universal Input U as Digital Input, On/Off Type 

The universal input U configured as Digital input can be configured for 

the applications: 

• On/Off input. 

• Pulse Counter input. 

The universal input U, configured as On/Off Digital input, has the properties: 

Table 17.8: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 


LED behavior. 





• On/Off (Digital). 

User’s selection of Normal state for the contact. 

• Open. 

• Closed. 

User’s selection for the indication LEDs behaviour. 

• Green. 

• Red. 

• Green Inverted. 

• Red Inverted. 


Category 

Unit 

Unit Prefix 








04-00123-01-en


To configure a universal input U as digital input, on/off 

type 



description. 

3 In the Sensor Type list, click On/Off (Digital). 

4 In the Normal Polarity list, click the required state. 

5 In the LED behavior list, click the required behavior. 

17.2.14 Signals in the Universal Input U Used as Digital Input, On/Off 

Type 

A universal input U used as digital input, on/off type has the signals: 


The Value signal is the logical state of connected equipment. 

• The CounterEnable signal does not apply to the on/off input. 

17.2.15 Configuring a Universal Input U as Digital Input, Counter Type 

The universal input U, configured as counter type Digital input, has the 

properties: 

Table 17.9: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type. 






• Counter (Digital). 

User’s selection of normal state for the contact. 

• Open. 

• Closed. 


04-00123-01-en



Table 17.9: 

Property 

Counter Enable 

Default 

User’s selection for controlling the counter. 

• 1. Counting is enabled 

• 0. Counting is disabled. 

Using the CounterEnable signal overrides the 

Counter Enable Default property selection. 


Category 

Unit 

Unit Prefix 







To configure a universal input U as digital input, counter 

type 



description. 

3 In the Sensor Type list, click Counter (Digital). 

4 In the Normal Polarity list, click the required state. 

5 In the Counter Enable Default list, click the required state. 

17.2.16 Signals in the Universal Input U Used as Digital Input, Counter 

A universal input U used as digital input, counter type has the signals: 


The Value signal is the logical state of connected equipment. 

• The CounterEnable signal. 

The signal starts and stops counting changes on the input. 

• When the signal is true (1), the counting is enabled. 

• When the signal is false (0), the counting is disabled. 


04-00123-01-en


17.3 The Non-linear Analog Input B 

The non-linear analog input B in a Xenta I/O module is used for sensors 

of thermistor type and setpoint adjustments. You can configure the following 

types in XBuilder: 

• Thermistor sensors. 

• SP adjust in ranges. 

The non-linear analog input B has the following properties: 

Table 17.10: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Point designation B(n), in the I/O module. 


Analog Input. 


• Thermistor 1.8k (TAC) 

• Thermistor 10k (CSI) 

• SP adjustment. Ranging from ±1 to ±9. 


Category 



The category for the input is: 


Unit 

Unit Prefix 

The unit for a signal is automatically selected by 



Not applicable for the input. 


04-00123-01-en



17.3.1 Configuring a Non-linear Analog Input B 

The non-linear analog input B is used for the following applications: 

• Thermistor 1.8 k (TAC). 

• Thermistor 10 k (CSI). 

• SP adjustment in ranges from ±1 to ±9. 

The measurement system unit for the SP adjustment range, depends 

on the category and Unit property of the input. 

You determine which application using the Sensor Type property. 

To configure a non-linear analog input B 

17.3.2 Signals in the B Type Analog Input 



description. 

3 In the Sensor Type list, click the required Thermistor type or SP 

adjustment range. 

Important 




The analog input B has one signal: 


The Value signal is the analog value from the connected thermistor 

sensor. 


04-00123-01-en


17.4 The Digital Output K 

The digital output K in a Xenta I/O module can be used for the following 

applications: 

• On/Off digital output. 

• Pulse width modulated digital output. 

The digital output K has the properties: 

Table 17.11: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Initial Value 

Point designation K(n), in the I/O module. 


Digital output 


• On/Off. 

• Pulse. 

User selected initial output state at first execution. 

(initial output value). 

• On. 

• Off. 


Category 

The category is used to automatically assign a measurement 

unit to a signal. 



Unit 

Unit Prefix 




04-00123-01-en



17.4.1 Configuring a Digital Output K 

The digital output K in a Xenta I/O module can be used for either on/off 

or pulsed output applications. 

You determine which application using the Sensor Type property. 

You can define an initial value for the output using the Initial Value 

property. 

To configure a digital output K 

1 In the network pane, select the required output. 


description. 

3 In the Sensor Type list, click the required type. 

4 In the properties view, in the Initial Value list, click the required 

value. 

17.4.2 Signals in the K Type Digital Output 

A digital output K has the following signals: 


The Value signal represents the logical state for equipment connected 

to the digital output 

• The HWForced signal. 

The HWForced signal in a digital output K indicates whether the 

manual override switch for the output is activated or not. 

• False (0), the switch is in the position AUTO. 

• True (1), the switch is in either the position ON or OFF. 

• The HWForcedValue signal. 

The HWForcedValue signal in a digital output K represents the 

logical state of the manual override switch for the output 

• When the signal is false (0), it indicates that the switch is in 

manual OFF position. 

• When the signal is true (1), it indicates that the switch is in 

manual ON position. 


04-00123-01-en


17.5 The Analog Output Y 

The analog output Y in a Xenta I/O module is used for a voltage signal 

output. The IO Point Type property cannot be changed. 

The analog output Y can be configured to limit either the physical output 

signal range within 0–10 volts or the input signal span to give the 

fixed output signal range 0 to 10 volts. 

Normally the analog output Y is used for giving a physical output voltage 

signal from connected signal values ranging from 0 (zero) to 100. 

When the default category for the analog output Y percentage is used, 

the utilization of the physical output voltage range is defined by the two 

properties Voltage at 0% and the Voltage at 100%. 

When other categories are defined, the fixed output signal range 0 to 10 

volts is calculated from the connected signal value where the value of 

the Minimum Value property results in 0 (zero) volts output level and 

the value of Maximum Value property results in the output level of 10 

volts. 

The analog output Y has the properties: 

Table 17.12: 

Property 

General 

Name 

Description 

IO Point Type 

Sensor Type 

Initial Value. 

Voltage at 0%. 

Voltage at 100%. 

Point designation Y(n), in the I/O module. 


Analog Output. 

0–10 volts. 

User selected output signal value, used when 

the I/O module goes offline or immediately 

after a restart. 

The Voltage level on the physical output when 

the connected signal value to the I/O is 0 (zero) 

Valid when the category is percentage. 

The Voltage level on the physical output when 

the connected signal value to the I/O is 100. 

Valid when the category is percentage. 


04-00123-01-en



Table 17.12: 

Property 

Minimum Value. 

Maximum Value. 

The value of the connected signal to the I/O 

which results in 0 (zero) volts on the physical 

output. 

Valid when other Categories than percentage 

is used. 

The value of the connected signal to the I/O 

which results in 10 volts on the physical output. 

Valid when other Categories than percentage 

is used. 

Measurements System 

Category. 

The category property for the analog output is 

used to define the range for either the input or 

output. 

• When the category is percentage, the values 

of Voltage at 0% and Voltage at 100% 

are used to define the output signal range. 

The Minimum Value and Maximum Value 

properties are not used. 

• When any other category is used the values 

of Minimum Value and Maximum 

Value are used to define the input range for 

the fixed output signal range. 

The Voltage at 0% and Voltage at 100% 

properties are not used. 

Unit. 

Unit Prefix. 

The unit for a signal, signal is automatically 

selected by the Category property but can be 

changed by the user from the Unit list. 

The presentation of the selected unit is governed 

by the Measurement System setting for 

the project. 


Prefix list. 


04-00123-01-en


17.5.1 Configuring an Analog Output Y 

The category property is used for the analog output Y to define either 

the signal input range or the signal output range. 

You use the category percentage to make the output compatible with 

existing physical analog outputs. 

When the category percentage is used, the two properties Voltage at 

0% and Voltage at 100% can be used to limit the output signal level 

within the range 0 to 10 volts. The two properties Minimum Value and 

Maximum Value are not used. 

When any other category is used, the two properties Minimum Value 

and Maximum Value define the input range for the fixed output signal 

range 0 to 10 volts. The two properties Voltage at 0% and Voltage at 

100% are not used. 

To configure an analog output Y 

1 In the network pane, select the required output. 

2 In the properties view, in the Description box, type a suitable 

description. 

3 In the Initial Value box, enter the required value. 

4 In the Category list, click the required category. 

Important 

• If the category percentage is used, you can specify the output 

range using the two properties Voltage at 0% and Voltage at 

100%: 

• In the Voltage at 0% box, enter the required value for the 

output level when the input is 0%. 

• In the Voltage at 100% box, enter the required value for the 

output level when the input is 100%. 

5 In the Voltage at 0% box, enter the required value. 

6 In the Voltage at 100% box, enter the required value. 

Note 

• If another category is used, you can specify the input range for 

the fixed output signal range 0 to 10 volts. 

• In the Minimum Value box, enter the required value for the 

input giving 0 volts output level. 

• In the Maximum Value box, enter the required value the 

input giving 10 volts output level. 


04-00123-01-en



17.5.2 Signals in the Analog Output Type Y 

An analog Output Y has the following signals: 

• Value. 

The Value signal represents the analog value of the output. 

• HWForced. 

The HWForced signal indicates whether the manual override 

switch for the output is activated or not. 

• False (0), the switch is in the position AUTO. 

• True (1), the switch is in the position MANUAL. 


04-00123-01-en



04-00123-01-en


18 Using LON Wall Modules in TAC XBuilder 

18 Using LON Wall Modules in TAC 

XBuilder 

You can use LON wall modules to display and control room temperatures 

and fan speed. The wall modules communicate using LonWorks 

and can be connected without the need for a separate binding tool. 

The workflow in XBuilder for adding wall modules to the Xenta Server 

is as follows: 

• Add the wall module. 

• Define the network address. 

• Configure the wall module. 

18.1 Adding a LON Wall Module 

STR 350/351 wall modules are added to the LON network, in the network 

pane, in the same way as you add Xenta I/O modules. 

To add a LON wall module 

1 In XBuilder, in the network pane, right-click the LON network. 

2 Point to Add I/O Module and then click STR35X. 

3 Right-click the added wall module and then click Rename to 

name the new wall module. 


04-00123-01-en

18 Using LON Wall Modules in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

4 Double-click the wall module to view the available signals. 

The wall module is now added to the network in the XBuilder project. 

18.2 Configuring the Device Address for a LON Wall 

Module 

The device address for the RTU wall module is configured in the same 

way as for the Xenta I/O modules. The way of working depends on the 

availability of network and also whether a Vista system is available. 

The choises are: 

• Use XBuilder 

• Use Vista Workstation 

• using the Service Pin switch 

• entering the Neuron ID manually 

• Via the Service web pages 

For more information on how to configure the device address, see 

Chapter 16, “Configuring the Device Address for a TAC Xenta I/O 

Module”, on page 127. 

18.3 Configuring a LON Wall Module 

To configure the the STR 350/351 wall module, please refer to the 

0FL-4125-001, Configuration Instruction, delivered together with the 

product. 


04-00123-01-en




Menta objects in XBuilder contain the application code, which is 

designed and programmed in the Menta programming tool. A complete 

application in the Xenta 700 controller can consist of several Menta 

objects. 

A Menta application created in the XBuilders version of Menta cannot 

be used in the generic version of Menta. 

Menta applications created for Xenta 200/300/400 can be re-used by 

importing them to the Menta objects in XBuilder. 

When the Menta programming tool is started from XBuilder it always 

saves the Menta application as an Menta application file (.mta) file. 

Browsing Menta application files from XBuilder will only find .mta 

files. 

It is possible to re-use an application file of .aut type, however, these 

files must be imported to Menta, when Menta is opened from XBuilder. 

Copy and pasting a design between two instances of Menta will only 

work between diagrams for Xenta 700 devices. Reusing designs from 

other type of device should be done using the import function. 

19.1 TAC Menta Object Properties 

The Menta object have the properties: 

Table 19.1: 

Property 

Name 

Description 

Control Task 

Cycle time 

Execution order 

Description 

Name of the Menta object. 

Description of the Menta object. 

Name of the control task in which the Menta 

object code is executed. 

Cycle time of the control task in which the 

Menta object code is executed. 

Execution order of the Menta object within 

the referenced control task. 


04-00123-01-en

19 TAC Menta Objects in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

19.2 The Control Task Property 

The control application code in each Menta object is executed in a control 

task. 

For more information on control tasks in a Xenta Server 700, see 

Section 22, “Control Tasks in TAC XBuilder”, on page 187. 

19.2.1 Selecting the Control Task for a TAC Menta Object 

The control application code in each Menta object is executed in a control 

task and with the cycle time for the assigned control task. 

For more information on how to assign a control task to a TAC Menta 

object, see Section 8.1, “Assigning a Control Task for a TAC Menta 

Object”, on page 59. 

19.2.2 Changing the Control Task Assignment for a TAC Menta Object 

Sometimes you need to change the task assignment for the application 

in a Menta object. You can change the control task assignment manually 

using drag and drop. 

To change the control task assignment for a TAC Menta 

object 

1 In the network pane, click the Menta object task link you wish to 

change. 

2 Drag the Menta object task link to the required control task. 

19.2.3 Removing a Control Task Assignment for a TAC Menta Object 

19.3 The Cycle Time Property 

In exeptional cases you may want to remove a control task assignment. 

To remove a control task assignment for a TAC Menta 

object 

• In the Network pane, right-click the Menta object control task 

assignment link you want to remove, and then click Delete. 

The control application code in each Menta object is executed with the 

cycle time for the assigned control task. 

For more information about cycle times in a Xenta Server 700 control 

task, see Section 22.1.1, “The Control Task Cycle Time”, on page 187. 


04-00123-01-en



19.4 The Execution Order Property 

The control application codes are executed in the order in which the 

Menta object control task links appear in the control task, starting with 

the uppermost. 

For more information about the execution order in a Xenta Server 700 

control task, see Section 22.3, “Defining Execution Order”, on 

page 190. 

19.5 Signal Structure in TAC Menta Objects 

Menta objects and the signals in the control application are located in 

the system pane in XBuilder. 

Public signals in a Menta object are organized in a predetermined structure. 

When Menta modules are used, each module collects the signals in the 

module in the predetermined structure. 

Public signals in a Menta object are organized in a predetermined structure 

and when Menta modules are used, each module collect the signals 

in the predetermined structure. 

Signals are organized with folders in the following structure within each 

Menta object or module: 

• Public Signals. 

• Inputs. 

• Outputs. 

• Alarms. 

• Time objects. 

If a signal is a part of a Menta module, the signal is located in an additional 

subfolder with the name of the Menta module. 

Important 

• Structural folders without signal objects will not be auto-maticcally 

created. 


04-00123-01-en

19 TAC Menta Objects in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en


20 Using TAC Menta Application Files in TAC XBuilder 

20 Using TAC Menta Application Files in 


Control algorithms and logical design in the control application is made 

up of one or more Menta objects in the Xenta Server. The Menta objects 

contain the application code and are added in the System pane in 

XBuilder. 

The Menta objects can obtain the application code either by using an 

existing Menta application file or by creating a completely new one. 

There are different ways to re-use an existing Menta application. You 

can import it either directly to XBuilder or via the opened Menta programming 

tool. 

• Importing a Menta Application File to the Menta object Using 

XBuilder. 

• Importing a Menta Application File to the Menta Programming 

Tool. 

• Loading parts of an application as Macro 

• Creating a New Menta Application File 

20.1 The Specialized TAC Menta Programming Tool 

When Menta is opened from XBuilder, the functionality of the programming 

tool is specialized for creating applications to run in the 

Xenta 700 device. A major difference from the original Menta programming 

tool is that the use of some function blocks differs. These are: 

• Function blocks for physical I/O points. 

There are no physical I/O blocks in the Menta application for the 

Xenta Server. Function blocks representing physical I/Os are 

replaced with connection blocks. These connection blocks are connected 

to signals in physical I/Os in XBuilder. 

However, if the I/O point is defined as a SNVT, no SNVT is created, 

but a LIST specifying the SNVT for each point is generated. 

You must create the SNVTs manually and make the connection to 

the signal object. 

• CNT function blocks. 


04-00123-01-en

20 Using TAC Menta Application Files in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

The special pulse counter input block CNT in a Menta application 

is replaced with a PI block. This blocks is later connected 

to a signal in a physical I/Os in XBuilder. 

• DOPU function blocks. 

The special pulse output block DOPU in a Menta application 

is replaced with a PO block. This blocks is later connected to 

a signal in a physical I/Os in XBuilder. 

• ALARM function block. 

An Xenta Server Alarm object is automatically created by 

XBuilder for each ALARM block in a Menta diagram which is 

introduced to a Menta object in a XBuilder project. 

The Xenta Server Alarm object is created in a sub-folder to the 

Menta object and named Alarms. The Xenta Server Alarm 

object is also located in an additional folder if the ALARM 

block is a part of a Menta module. 

• TSCH function block. 

A Time Schedule Reference object is automatically created by 

XBuilder for each TSCH block in a Menta diagram which is 

introduced to a Menta object in a XBuilder project. XBuilder 

creates the Time Schedule Reference object in a sub-folder to 

the Menta object and names the folder Time objects. The Time 

Schedule Reference object is also located in an additional 

folder if the TSCH block is a part of a Menta module. 

The original TSCH function block is replaced with a TSCHI 

function block in the application code for the Menta object in 

XBuilder. 

• ERR function block. 

The functionality of the ERR function block, available in 

XBuilder, is modified for the Xenta 700 device. The original 

ERR function block is replaced with a ERROR function block 

in the application code for the Menta object in XBuilder. 

• Trend logs. 

If the application .mta (source) file contains a Trend log, the 

log is automatically converted to a corresponding XBuilder 

Trend Log object. 

Important 

• All not permitted characters in block names, inputs, outputs, 

alarms, time schedules, public signals and public constants are 

converted to underscore when a Menta application file is 

imported. 


04-00123-01-en



20.2 Importing a TAC Menta Application File to the 

TAC Menta Object Using TAC XBuilder 

One useful way to import a Menta application file to the Menta object 

is to locate and import it directly using XBuilder. 

For more information on how to browse and import the application file 

directly to the Menta object using XBuilder, see Section 7.3, “Adding a 

TAC Menta Application File”, on page 53. 

20.3 Importing a TAC Menta Application File to the 

TAC Menta Programming Tool 

In addition to importing Menta application files directly to XBuilder, it 

is also possible to import an existing Menta application file from the 

Menta programming tool. 

Important: 

• The only application files you can import directly to Menta 

objects in XBuilder are .mta files. 

• To import Menta application files via the Menta programming 

tool is particularly useful as you also can import Menta .aut type 

of files. 

• When Menta is started from XBuilder it always saves an application 

as an .mta file. 

To import a TAC Menta file to the TAC Menta Programming 

Tool 

1 In XBuilder, in the system window, right-click the required Menta 

object. 

2 Click Edit. 

3 In Menta, in the File menu, click Import. 

4 In the Import dialog, browse to the required Menta application. 

5 Click Open. 

Menta opens with the application loaded. 

Important 

• Make sure the Output window is visible in XBuilder so you can 

view possible errors and messages when importing a Menta 

application file. 


04-00123-01-en


6 In the Menta editor, in the File menu click Return to XBuilder 

when finished. 

7 In the TAC Menta dialog, click Yes to save the changes to 

XBuilder. 

When the import is finished, the Menta object is expanded to show 

the first sub-level of the pre-defined substructure of the object and 

you can view the folders for public signals, constants, alarms and 

time objects. If modules are used in the imported application, the 

signals are collected in a separate folder for each Menta module. 

8 In XBuilder, in the system pane, view the structure of the Menta 

object. 

Important 


as SNVT, a connection block of a type corresponding to the 

SNVT is created. The definition as SNVT is discarded when the 

application is imported into XBuilder, but an automatically created 

text file for each Menta object, listing all the definitions is 

created. 


under the Generate tab. 

• If you double-click the line in the list, the text file is opened in a 

text editor and you can save the file at a suitable location. 

XBuilder Trend log objects are automatically created if the imported 

Menta application file contained a defined trend log. The created Trend 

log objects are located in the structure, on the same level as the Menta 

object. 

Important 

• Removing a Menta object that has contained trend log objects 

will not remove the trend log objects. 

• Importing the same application or another Menta application will 

add a new set of Trend log objects. 


04-00123-01-en



20.4 Loading an Application Part as a Macro 

Previously saved macro blocks can be added to the function block diagram 

by loading them to the diagram window. 

Important 

• Only macro blocks prepared for a Xenta 700 can be loaded as 

macro blocks for this type of device. 

Tip 

• Use the Zoom out command to get an satisfactory overview of 

the blocks in the diagram window. 

To load a macro block 

1 Click in the diagram window to clear any selection. 

2 Place the cursor on an empty area in the diagram window. 

3 Right-click and then click Load Macro. 

4 In the Open dialog box, select the macro block to load. 

5 Click Open. 

6 Move the blocks to a suitable position in the diagram window. 

7 Click outside the macro block to de-select the items. 


04-00123-01-en


20.5 Creating a New TAC Menta Application File 

When you make control designs you often can re-use existing designs, 

although you might need to modify them. Sometimes you must create 

completely new control functions in Menta; this can be achieved by 

using connection blocks in the Menta application and XBuilder objects 

for Time objects, Alarm objects and Trend logs. 

The following is an example of how to create a new Menta function 

block diagram. The example is a much simplified Menta solution to 

obtain an alarm in the system and generate a response on a physical 

device when a button is pressed. 

For more information on how to create a Menta application, see the TAC 

Menta, Technical Manual. 

Creating a new TAC Menta application file 


object. In our example, the AlarmButtonResponse. 

2 Click Edit. 

Menta starts in the editor mode, with an empty application program 

window. 

3 In the application program window, right-click in the left part of 

the window. 

4 In the New dialog, point to the class of block you want to select a 

new block from. In our example, click Simple Block. 

5 In the Select Simple Block dialog, in the Block Class list box 

select Connection Blocks. 

6 In the Block list, double-click the required block. In our example, 

click BI. 


04-00123-01-en



A new BI block will appear in the left part of the window, that is 

where the cursor was when you started. 

7 Double-click the BI block. 

8 In the Edit block BI dialog, in the Identifier box, enter the 

required name of the block. In our “Boolean_input”. 

9 Click OK. 

10 In the application program window, right-click in the middle part 

of the window. 


select Time schedule and alarm. 


click ALARM. 

A new ALARM block will appear in the window. 

13 Double-click the ALARM block. 


04-00123-01-en


14 In the Edit block ALARM dialog, in the Identifier box, enter the 

required name of the block. In our example “Alarm” 

15 In the application program window, right-click in the right part of 

the window. 

16 In the New dialog, point to the class of block you want to select a 

new block from. In our example, click Simple Block. 


select Connection Blocks. 


click BO. 

A new BO block will appear. 

19 Double-click the BO block. 


04-00123-01-en



20 In the Edit block BO dialog, in the Identifier box, enter the 

required name of the block. In our example, enter 

“Boolean_output”. 

21 Click OK. 

22 In the application program window, click the stub on the right 

edge of the BI block to get a cursor like a cross. 

The connection point is now extended to form a flexible line, following 

the pointer. 

23 While keeping the left mouse button pressed, drag the line to the 

left edge of the ALARM block until the cursor looks like a cross 

within a square. 

24 Release the mouse button to anchor the connection. 

25 In the application program window, click the stub on the right 

edge of the ALARM block and connect to the BO block. 


27 In the TAC Menta dialog, click Yes to save. 


04-00123-01-en


28 In XBuilder, in the system pane, view the AlarmButtonResponse 

object, it’s structure and the signals. 

In the structure you can identify the two signals in the Menta object: 

• AlarmButtonResponse-Inputs-Boolean_input signal. 

• AlarmButtonResponse-Outputs-Boolean_Output signal. 

These are the signals you connect to input and output signals in Xenta 

I/O modules. 

You can also identify the automatically created XBuilder alarm object 

named Alarm. 


04-00123-01-en


21 Using the TAC Menta Library in TAC XBuilder 

21 Using the TAC Menta Library in TAC 

XBuilder 

Sometimes the control application can be designed so that the code in a 

Menta object can be used several times. A solution for this is to work 

with Menta objects in the XBuilder Menta Library. A Menta object 

located in the library is used as a source object and references to the 

library object are used in the control application. 

Parameters and settings in the referenced Menta objects can be customized. 

One of the advantages of working with the Menta Library is that you can 

change the Menta code in the library object and the change will be effective 

in all referenced objects. 

Another advantage is that the Menta objects in a Menta Library can be 

exported for use in other XBuilder projects. 

A Menta object can be created in the XBuilder Menta Library in two 

ways: 

• Create a new Menta object in the library. 

• Promote an existing Menta object to the library 


04-00123-01-en

21 Using the TAC Menta Library in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

21.1 Adding an Existing TAC Menta Object to the TAC 

Menta Library 

It can be useful to add an existing Menta object to the library as you can 

then re-use it in the project when appropriate. 

The Menta Library in XBuilder is a tabbed alternative of the Network 

pane. 

To add an existing TAC Menta object to the TAC Menta 

Library 

1 In the Network pane, click the Menta Library tab to display the 

library. 

2 In the system pane, right-click the Menta object you want to send 

to the Menta Library and then click Add to Library. 

3 In the Select Folder where the library object will be created 

dialog box, select the required location. 


04-00123-01-en



4 Click OK. 

Note 

• When you add an existing Menta object to the Menta Library in 

XBuilder the original Menta object icon , is changed to a referenced 

object icon . 

Tip 

You can also promote an existing Menta object to the Menta library by 

dragging the required Menta to the Menta library pane and dropping it. 

Note 

• You can view the path to the library object by clicking the Menta 

object in the system pane and then viewing the path in the 

Library Reference box, in the properties pane. 

Important 

• On completion, you cannot edit the Menta application in the 

Menta object located in the system pane. You have to change the 

application by editing the object located in the Menta Library. 


04-00123-01-en


21.2 Adding a New TAC Menta Object to the TAC 

Menta Library 

It can be useful to create a new Menta object in the Menta Library when 

you foresee that the required Menta object will be used several times in 

the project. 

To add a new TAC Menta object to the TAC Menta Library 

1 In the Network/Menta library pane, click the Menta Library tab. 

2 Right-click the Menta Library root object and then click New 

Menta Library Object. 

3 Name the new Menta library object. 

4 In the properties pane, in the Description box, enter a description 

if required. 

A new Menta library object is created. 

21.3 Editing a TAC Menta Object in the TAC Menta 

Library 

Menta objects in the library are edited in the same way as menta objects 

in the system pane. 

After editing a Menta object in the Menta Library, all Menta objects that 

are referencing the library object are changed. 

Editing a Menta Library object does not change the Menta object connections; 

these are automatically updated. 

To edit a TAC Menta object in the TAC Menta library 

1 In the Menta library pane, click the Menta Library tab. 

2 Right-click the Menta object you want to edit and then click Edit. 

The application is opened in the Menta programming tool. 

3 In Menta, click Return to XBuilder when finished. 

The Menta object in the library and all Menta objects referencing the 

library object are automatically updated when the editing is saved. 


04-00123-01-en



21.4 Importing a TAC Menta Application File to a TAC 

Menta Library Object 

Importing an Menta application file (.mta) is useful when a Menta 

library object is created in XBuilder and you want to use an externally 

available .mta file. 

A Menta application file is imported to a Menta library object in the 

same way as application files are imported to Menta objects in the system 

pane. 

T 

Important 

• The application in all Menta objects referencing the library 

object are changed when you import a menta application file to 

the Menta library object. 

Important 

• Make sure that the Output pane is open so you can see possible 

error messages. 

To import a TAC Menta application file to a TAC Menta 

library object 


2 Right-click the Menta library object to which you want to import 

the .mta file and then click Import mta file. 

3 In the Open dialog box, browse to the .mta file you want to use. 

4 Click Open. 

The Menta application file is now imported to the Menta object in the 

library. 


04-00123-01-en


21.5 Using a TAC Menta Object from the Library 

It can be convenient to use an existing Menta object in the Menta 

Library as you can use it as many times as you like in the same project: 

• Create a Menta object in the system pane. 

• Select a suitable Menta object from the library. 

The Menta object in the system pane, the referenced object, can be individualized 

by changing parameters and setpoints when necessary. 

To use a TAC Menta object from the library 

1 In XBuilder, in the system pane, right-click the application folder 

where you want the Menta object to be located. 

2 Point to New, point to Object and then click Menta object. 

3 Name the new Menta object. 

4 Right-click the new Menta object, and then click Select from 

Library. 

5 In the Select Library Object dialog box, browse to the required 

Menta library object. 

6 Click OK. 

Note 

• The icon for the Menta object changes to an icon for a library 

object. 


04-00123-01-en



21.6 Making a Local Copy of a TAC Menta Object from 

the TAC Menta Library 

Changing a Menta object from the library object to a local copy is useful 

when the Menta object in an application shall not be affected by changes 

in the Menta Library object. 

Important 

• When you make a local copy of a Menta object, it will retain all 

its properties, however the object will not change when the 

library object is changed. 

To make a local copy of an TAC Menta object from the TAC 

Menta library 

1 In XBuilder, in the system pane, right-click the Menta object you 

want to disconnect. 

2 Click Disconnect from Library. 

Note 

• The Menta object icon changes to a normal icon. 


04-00123-01-en


21.7 Exporting a TAC Menta Library 

Exporting a Menta objects library is useful when you want to use the 

same library in another XBuilder project. 

Exporting a library can be done for a complete library or selected 

objects. 

The exported library is saved in a compressed (.zip) format in a user 

selected location. 

To export a TAC Menta library 


2 Right-click the Menta Library root object and then click Export. 

3 In the Export Library dialog box, browse to the folder where you 

want to locate the exported library file. 

4 In the File name box, enter the name you want to use for the 

exported file. 

5 Click Save. 

The Menta library is now exported to the required location. 


04-00123-01-en



21.8 Importing a TAC Menta Library 

Importing a Menta objects library is useful when you want to re-use the 

library from another XBuilder project. 

Importing a library can be done for a complete library or selected 

objects. 

To import a TAC Menta library 


2 Right-click the Menta Library root object and then click Import. 

3 In the Import Library dialog box, browse to the Menta library 

export file you want to import to the library. 

4 Click Open. 

Note 

If you import a library again, you will get duplicates of the Menta 

objects. 

21.9 Deleting a TAC Menta Library Object 

Deleting a Menta Library object will result in changes if a Menta object 

is referencing the library object. If no Menta object is referencing the 

library object there are no consequences. If there are Menta objects referencing 

the library object you delete, the referenced objects are 

changed to local Menta objects. 

Important 

• When you delete a Menta Library object all Menta objects referencing 

the library object are changed to local Menta objects. 

To delete a TAC Menta library object 


2 Right-click the Menta library object you want to delete and then 

click Delete. 

3 In the TAC XBuilder confirmation dialog, click Yes. 

The library object is deleted from library. 


04-00123-01-en



04-00123-01-en




22.1 Control Task Properties 

The entire control application in the Xenta Server is executed in one or 

more control tasks. There are five control tasks with different cycle 

times. Which task to use for the application, or parts of it, depends on 

how quick a response is required. 

The code for several Menta objects can be run in the same control task. 

The execution of each control task is supervised by the system and 

important information is available as system variables in XBuilder. 

There are five control tasks in a Xenta Server 700. 

• Fast 

• Medium Fast 

• Medium 

• Medium Slow 

• Slow 

Each control task has the following properties: 

Table 22.1: 

Property 

Description 

Name 

Description 

Cycle time 

Name of the control task 

Description of the control task 

Cycle time for the control task (ms) 

22.1.1 The Control Task Cycle Time 

Each control task in the Xenta Server 700 has a predefined cycle time. 

The cycle times cannot be changed. 


04-00123-01-en

22 Control Tasks in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 

The execution of a control task is restarted with the periodicity approximately 

equal to the cycle time. 

Table 22.2: 

Task 

Cycle Time 

Fast 

Medium Fast 

Medium 

Medium Slow 

Slow 

100 ms 

500 ms 

1000 ms (1s) 

5000 ms (5s) 

10000 ms (10s) 

You select to run your Menta object application code in a control task 

with the cycle time required for the application. 

Control tasks with shorter cycle times are normally used when fast 

response is required. An example of such applications is light control. 

The code in a Menta object that requires an execution time of 600 ms is 

not suitable to be executed in a Fast or Medium Fast task. The application 

will generate overruns. Such an application can be executed in 

either the Medium, Medium Slow or Slow task. 

Which of the slower tasks to use depends on the allowed length of the 

cycle time. If, for example, a cycle time of 5000 ms is accepted, the 

Medium Slow control task can be used; otherwise the Medium control 

task is suitable. 

The total execution time for the code in all Menta objects in the same 

control task should not exceed the cycle time of the task. If the cycle 

time is exceeded, a control task with a longer cycle time should be used. 

Alternatively the total application might be revised by executing the 

some of the Menta objects in a control task with a longer cycle time. 

If the execution time is longer than the cycle time for the task it will 

mean that the application will never be executed with the designed cycle 

time. All application code in the task will be executed with the necessary 

execution time, but the next execution of the task will start when 

the task is scheduled to start. The resulting cycle time will then be as 

much as twice than intended. 


04-00123-01-en



22.2 Viewing the Control Task Assignments 

22.2.1 Viewing a Control Task Reference 

A Menta object control task link is created in the control task when a 

Menta object is assigned to the control task. The control tasks and the 

task links are shown in the network pane. 

You can view the Menta objects assigned to each task in the control 

tasks structure in the network pane. They can be identified by their 

names. You can also find the assigned Menta object by viewing the 

property of the task reference. 

To view a control task reference 

1 In the network pane, click the Menta object task link. 

2 In the properties pane, in the Reference box, view the path of the 

reference. 

22.2.2 Viewing the Control Task Assignment for a TAC Menta Object 

Occasionally you may want to view which control task a Menta object 

is assigned to. 

To view the control task assignment for a TAC Menta object 

1 In the system pane, click the required Menta object. 

2 In the properties pane, in the Control task box, view the assigned 

control task. 


04-00123-01-en


22.3 Defining Execution Order 

The execution order for the code in Menta objects is determined by the 

order of the Menta object control task assignment links in the task, as 

shown in the XBuilder network pane. The codes are executed consecutively 

from the top of the structure and down. 

Xbuilder automatically assigns the execution order and sequences the 

execution order in line with the defined control task assignment links. 

The order can be rearranged manually when needed. 

22.3.1 Changing the Execution Order Within a Control Task 

XBuilder automatically assigns the execution order and sequences the 

execution order in line with the defined control task assignment links. 

The assigned execution order can be changed by moving the control 

task assignment links up or down in the structure. 

To change the execution order within a control task 

1 In the network pane, double-click Control Tasks to view the 

tasks. 

2 Click the control task link for which you want to change the execution 

order. 

3 In the toolbar, click Move up or Move down to move the task link 

to the required position. In our example, to the top of the structure. 


04-00123-01-en



22.4 Accessing Execution Time Values for the Control 

Tasks 

22.4.1 Control Task System Variables 

The execution of each control task is supervised by the system in the 

Xenta 731 and important values are available in two ways: 

• As system variables in XBuilder. 

• As values accessed via the service web. 

The control task system variables in the Xenta Server 700 can be made 

visible in TAC Vista graphics or on web pages. You can also use them 

in a design where an alarm is generated at a required level. 

For more information on how to use Xenta Server signals in a TAC 

graphic, see the TAC Xenta Server – Web Server, Technical Manual. 

For more information on how to create an XBuilder alarm object, see 

the TAC Xenta Server – Web Server, Technical Manual. 

The available system variables for each control task are listed in the 

table below: 

Table 22.3: 

Name Description Type 

Cycle time Cycle time for the task [ms] Real 

Latest exec time Latest achieved execution time [ms] Real 

Max exec time Maximum execution time [ms] Real 

Min exec time Minimum execution time [ms] Real 

Overruns Total number of overruns Integer 

Overruns quota Percentage of overruns last hour Real 

Clear all Clears all data for the task, if true Boolean 

The variables are located in the network pane, in the System Variables 

folder. 

The execution time of a control task is particularly interesting during the 

design and commissioning phase. 

If, for example, the Min execution time is longer than the cycle time for 

the task it will mean that the application will never be executed with the 

intended cycle time. All application code in the task will be executed 

with the necessary execution time, but the next execution of the task 

will start when the task is scheduled to start. The resulting cycle time 

can in such case be almost twice the intended. 


04-00123-01-en


Another variable of special interest is the value of Overruns in a task. 

The value for Overruns shows how many times the task has not executed 

within the cycle time for the task. 

If there are an increasing number of Overruns, it indicates the need to 

use a control task with a longer cycle time, or that the control application 

should be re-designed. 

The value for Overruns quota shows the percentage of overruns in the 

last hour. 

If the value for Overruns quota is low, it indicates a possibly temporary 

overload on the task but the progress on overruns should be monitored. 

Tip 

• One way to use the value of the Overruns quota is to connect it to 

an XBuilder alarm object for generating an alarm. 

22.4.2 Creating an Alarm for the Control Task Overruns System 

Variable 

One way to use the value of the Overruns quota is to connect it to an 

XBuilder alarm object for generating an alarm. Choose a suitable alarm 

level and delay for the application. 

To create an alarm for the control task overrun signal 

• Create a new alarm object. 

• Configure the alarm object to take an analog value and that the 

alarm shall be tripped if the value is greater than some decimal 

value between 0 and 100 reflecting the percentage value of overruns 

desired. 

• Connect the overrun signal from a task to the alarm input. 

22.4.3 Viewing the Control Task Execution Times Values Via the Service 

Web 

A page in the sevice web contains values for several of the system variables 

with information about the execution of the five control tasks and 

the applications. 

How to use the the Xenta Server web site for monitoring is described in 

the Section 12.1, “Viewing the Execution Time for a Control Application”, 

on page 109. 


04-00123-01-en



22.5 Clearing Task Dynamic Data 

Sometimes, particularly during debugging a project, you need to clear 

all the statistics for the execution of a task. 

Clearing all values can be done in two ways: 

• Via the service web. 

• Using the system variables. 

22.5.1 Clearing Task Dynamic Data via the Service Web 

Sometimes, particularly during debugging a project, you need to clear 

all the statistics for the execution of a task. 

For more information on how to clear task dynamic data, see 

Section 12.2, “Clearing Task Dynamic Data”, on page 112. 

22.5.2 Clearing Dynamic Data for all Tasks 

For debugging purposes you can also clear dynamic data for all tasks. 

For more information on how to clear task dynamic data, see 

Section 12.2.1, “Clearing Dynamic Data for All Tasks”, on page 113. 

22.5.3 Clearing Task Dynamic Data Using System Variables. 

Clearing task dynamic data can also be done for each control task, using 

the system variable Clear all. This requires that you create a design 

where the variable is used in a TAC graphic or make a web page with 

the variable available for the user. 

For more information on how to use an XBuilder signal in a TAC 

graphic, see TAC Xenta Server – Web Server, Technical Manual. 

For more information on how to create an XBuilder alarm object, see 

TAC Xenta Server – TAC Networks, Technical Manual. 


04-00123-01-en


22.6 Viewing the Execution Time Values for the 

Application in a TAC Menta Object 

Both the information about the execution of the control task and time 

values for the application in each Menta object can be viewed using the 

service web pages. 

The values are shown in a list for each Menta object in the control task. 

The available values for each Menta object are: 

• Description 

• Latest exec time (ms) 

• Max exec time (ms) 

• Min exec time (ms) 

For more information on how to view execution time values for an 

application, see Section 12.1.2, “Viewing the Execution Time Values 

for the Application in a Menta Object”, on page 111. 


04-00123-01-en

TAC Xenta Server – Controller, Technical Manual 23 Variables in a TAC Xenta Server 700 

23 Variables in a TAC Xenta Server 700 

Variables in XBuilder are special signals and available only in Xenta 

Server 700 devices. They are useful for sharing signal information 

between parts in the network. 

23.1 Automatically Added Variables 

Three variables are automatically created by XBuilder, and are located 

in a separate folder called Constants: 

• Binary Zero. 

• Integer Zero. 

• Real Zero. 

You can rename or configure some of their properties like Data Type, 

Initial Value. You can also choose to delete the variables. 

A typical use of these three is to temporarily connect input signals in 

Menta objects during the development of a project until the final connections 

are made. 

Connecting input signals to these variables will satisfy XBuilders 

demand that all inputs are connected and allow the project to be generated 

and saved to Vista database as well as downloaded to Xenta 700 

devices. 


04-00123-01-en

23 Variables in a TAC Xenta Server 700 TAC Xenta Server – Controller, Technical Manual 

23.2 Adding a Variable 

Yo can create all variables and structural folders you need for an 

XBuilder project. You create Variables in the network pane in 

XBuilder. 

Note 

• You can structure your variables by using folders. 

• You create a folder by right-clicking the required location and 

then click New Folder. 

To add a variable 

1 In the network pane, right-click the Xenta_700 device-Variables 

and then click New Variable. 

2 Name the new variable. 

3 In the properties pane, in the DataType list, click the required data 

type. 

4 In the properties pane, in the InitValue box, enter the required 

value. 

5 In the properties pane, in the Backup box, click the required alternative. 

6 In the properties pane, in the Writable box, click the required 

alternative. 


04-00123-01-en

TAC Xenta Server – Controller, Technical Manual 23 Variables in a TAC Xenta Server 700 

23.3 Defining the Source for a Variable 

Variables represent the value/state of output signals in the XBuilder 

project. The value/state of a variable is updated every time the source of 

the variable is changed. An initial value can be assigned to each variable. 

The source of a variable is conveniently defined using drag and drop of 

the variable to the source signal. 

To define the source for a variable 

• In the network pane, click the required variable and then drag and 

drop the variable on the output signal. 

23.4 Using the Value/State of a Variable 

When you use a variable, you drag and drop the variable to the required 

input signal. 

To use the value/state of a variable 

• In the network pane, click the required variable and then drag and 

drop it on the input source signal. 

23.5 Finding Signals Connected to a Variable 

You can find the signals connected to a variable with the aid of the output 

pane. 

To find signals connected to a variable 

1 In the network pane, right-click the required variable and then 

click Show Connections. 

2 In the output pane, view the paths of signals connected to the variable. 


04-00123-01-en

23 Variables in a TAC Xenta Server 700 TAC Xenta Server – Controller, Technical Manual 

23.6 Disconnecting a Signal from a Variable 

When you no longer want to have a signal connected to the variable, you 

disconnect the signal. 

To disconnect a signal from a variable 

• In the system pane, right-click the required signal and then click 

Disconnect. 


04-00123-01-en


24 Alarm Objects in the Control Application 

24 Alarm Objects in the Control 

Application 

The control application in the Xenta Server uses Xenta Server alarm 

objects. 

Alarm objects are automatically created by XBuilder when a Menta 

application containing an alarm is imported to the Menta object. 

Alarm objects can also be created manually. 

For more information about Xenta Server alarm object, see the TAC 

Xenta Server – TAC Networks, Technical Manual. 

24.1 The TAC Xenta Server Alarm Object in a TAC 

Menta Object 

The Xenta Server alarm object created from an ALARM function block 

in a Menta object differs from the generic Xenta Server alarm object in 

that there is no signal called “Input”. The input is defined in the Menta 

application file (the Menta function block diagram). Otherwise, the 

alarm objects in the Xenta Server are the same. 

The scan time for an alarm is specified by the Scan time property for 

the alarm object. The scan time is the interval to scan the input to determine 

the alarm condition. 

The Menta application code, determining the condition for the alarm 

(the input), is executed with the assigned control task cycle time. 

The scan time is independent of the control task cycle time. 


04-00123-01-en

24 Alarm Objects in the Control Application TAC Xenta Server – Controller, Technical Manual 

The Alarm object in a Menta object has the signals: 

Table 24.1: 

Signal 

Acknowledge. 

Output. 

State. 

Description 

Signal to acknowledge the 

alarm. When the signal is true, 

the alarm is acknowledged. 

The alarm digital output. 

The output is true as long as the 

alarm condition is either: 

• ACTIVE or 

• PASSIVE and not 

ACKNOWLEDGED. 

If the alarm is blocked, the output 

is false. 

The alarm state output can be 

used to describe the alarm status 

in clear text, for example on values 

pages or in dialog boxes of a 

dynamic object in graphics: 

• normal 

• active . unacked 

• active . acked 

• passive . unacked 

• blocked. 

Values for the Delay On and Delay Off properties of the alarm, are 

effective on the two signals Output and State. 

24.2 Alarm Objects from an Imported TAC Menta 

Application 

A Xenta Server Alarm object is automatically created by XBuilder for 

each ALARM block in a Menta diagram which is introduced to a Menta 

object in an XBuilder project. 

For more information on alarm objects imported from a Menta application, 

see Section 7.3.1, “Importing a TAC Menta Application File to a 

TAC Menta Object”, on page 53. 


04-00123-01-en


24 Alarm Objects in the Control Application 

24.3 Adapting an Alarm Object 

The functionality of the Alarm object created by XBuilder and the 

Menta function block diagram is retained within the Menta object when 

a Menta application file is imported. 

If the state of the function block ALARM shall be used as input in other 

Menta objects you need to make sure the application includes the necessary 

signal. 

To provide for this there must be a public function block connected to 

the output of the ALARM function block, to create the required signal 

in the XBuilder Menta object. A BO connection block or a public XPB 

function block are two alternatives. 

! Important 

24.4 Alarm Objects in a New TAC Menta Application 

24.5 Creating an Alarm Page 

• The state of the ALARM function block is not directly accessible 

as a signal in the XBuilder Menta alarm object. There must be a 

public function block, of boolean type, connected to the output of 

the ALARM function block, to create the required signal. 

When you create a new Menta application you can use two types of 

alarm. You can use the Menta ALARM block in the function block diagram 

or you can use XBuilder Alarm objects and connect them to an 

input in the Menta object. 

To make alarms visible to the operator on a Xenta Server web site, a 

alarm page is added to the XBuilder project. 

For more information on how to create an alarm page in XBuilder, see 



04-00123-01-en

24 Alarm Objects in the Control Application TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en


25 Time Objects in the Control Application 

25 Time Objects in the Control 

Application 

The control application in the Xenta Server uses Xenta Server time 

objects. 

Time objects are automatically created by XBuilder when a Menta 

application containing time schedule function blocks is imported to the 

Menta object. Time objects can also be manually created in XBuilder 

and connected to the Menta objects. 

Note 

• The contents of a time object can be edited in XBuilder or on a 

time object page on the Xenta Server web site. 

For more information on XBuilder Time objects, see the TAC Xenta 

Server – TAC Networks, Technical Manual. 

25.1 Time Objects Imported from a TAC Menta 

Application 

A Xenta Server time object is automatically created by XBuilder for 

each TSCH block (time schedule) in a Menta diagram which is introduced 

to a Menta object. 

For more information on Xenta Server time objects imported from a 

Menta application, see Section 7.3.1, “Importing a TAC Menta Application 

File to a TAC Menta Object”, on page 53. 


04-00123-01-en

25 Time Objects in the Control Application TAC Xenta Server – Controller, Technical Manual 

25.2 Connecting a Time Object to a TAC Menta Object 

The functionality of the time object created by XBuilder and the Menta 

function block diagram is retained within the Menta object when a 

Menta application file is imported. 

If you need to use the same time schedule in other Menta objects, the 

appropriate output signal must be connected to all these Menta objects. 

If you need to use the logical state of the time schedule in another Menta 

object, you connect the signal called Output to an input in all these 

Menta objects. 

Note 

• The output signal in an XBuilder time object is, by default, of 

real type. 

If you need to use the value for time time before the time schedule is 

active, you connect the signal called TimeLeft to an input in tall these 


In our example, the time object is used only internally in the Menta 

object called AHU. There is no need to connect the signal to other 


To connect a time object to a TAC Menta object 

1 In the system pane, expand the Menta object where you want to 

use (connect) the time scheduling. 

2 Click the input where you want to connect the time scheduling. 



4 In the filter view pane, expand the time object you want to connect. 

5 In the filter view pane, click the signal you want to connect, either 

the Output or the TimeLeft. 


25.3 Time Objects in a New TAC Menta Application 

When you create a new Menta application you can choose one of two 

ways to organize time scheduling. You can use the Menta TSCHI block 

in the function block diagram and let XBuilder automatically create the 

time object or you can make a design where you use XBuilder time 

objects, prepare inputs in the Menta application and connect them to the 

XBuilder time objects. 

For information on how to create time objects in XBuilder see the TAC 



04-00123-01-en


25 Time Objects in the Control Application 

25.4 Creating a Time Object Page 

To make XBuilder time objects visible to the operator on a Xenta Server 

web site, each chart must be on a separate time object page. 

For information on how to create time object pages in XBuilder see the 



04-00123-01-en

25 Time Objects in the Control Application TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en




For logging signals in the Xenta Server, you use Trend log objects in 

XBuilder. 

Trend log objects are automatically created by XBuilder when a Menta 

application containing trend logs is imported to the Menta object. 

Trend log objects can also be created manually. 

For more information on how to create a trend log in XBuilder, see TAC 


26.1 Trend Log Objects Imported from a TAC Menta 

Application 

26.2 Adapting a Trend Log 

When you import a Menta application file containing a trend log, the 

defined trend log in the .mta (source) file is automatically converted to 

a corresponding XBuilder trend log object. 

For more information on trend log objects imported from a Menta application, 

see Section 7.3.1, “Importing a TAC Menta Application File to 

a TAC Menta Object”, on page 53. 

XBuilder will create a trend log object for a real point when the default 

value (0.5) for hysteres is used by the ordinary Menta programming tool 

when logging a boolean (digital) point. 

The hysteresis for a boolean log point must be 0 (zero) when you import 

the application. Othervise there will be an error when the XBuilder 

project is generated. 

Important 

• The hysteresis for a Trend log of a boolean log point in an existing 

Menta application file must be 0 (zero) when you import the 

application. The default value (0.5) used by the ordinary Menta 

programming tool will cause XBuilder to create a trend log for a 

real value point and will cause an error when the XBuilder 

project is generated. 


04-00123-01-en

26 Trend Logs in the Control Application TAC Xenta Server – Controller, Technical Manual 

26.3 Trend Log Objects in a New TAC Menta 

Application 

26.4 Creating a Trend Log Page 

When you create a new Menta application, you can use XBuilder trend 

log objects and specify the log in XBuilder. 

For more information on how to create a trend log in XBuilder, see the 


To make trend logs visible to the operator on the web site in a Xenta 

server, each trend log must be on a separate trend log page. 

For more information on how to create a trend log page in XBuilder, see 



04-00123-01-en


27 I/O Signals as SNVTs in the Control Application 

27 I/O Signals as SNVTs in the Control 

Application 

The control application in XBuilder can use SNVTs. The Menta object 

uses the required type of connection block and connected to separately 

created and defined SNVTs. 

The required SNVTs are additionally created in the network pane in 

XBuilder. 

For more information on how to create the SNVTs, see Section 10, 

“Adding SNVT Objects to the Project”, on page 77. 

27.1 I/O Signals as SNVTs from an Imported TAC 

Menta application 

Physical I/Os, defined as SNVTs, in a Menta application you import can 

be either digital (DI/DO) or analog (AI/AO) type. The I/Os are automatically 

replaced with connection blocks, when the Menta application file 

is imported. In the ordinary version of Menta the AI and AO function 

blocks are used for SNVTs of both real and integer type. In the XBuilder 

version of Menta, different connection blocks must be used. 

27.2 Changing Connection Block Type 

A typical need to adapt the result of an imported Menta application 

using SNVTs, is to make sure that the automatically created connection 

blocks are the required type and if necessary replace them. 

For more information on how change the type of automatically created 

connection blocks, see Section 9.4, “I/O Signals as SNVTs in the Control 

Application”, on page 64. 

27.3 SNVTs as I/O Signals in a New TAC Menta 

Application 

When you create a new Menta application, you can make a Menta 

design where the correct type of connection block is used. 


04-00123-01-en

27 I/O Signals as SNVTs in the Control Application TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en


28 ERR Function Blocks in the Control Application 

28 ERR Function Blocks in the Control 

Application 

In the control application for Xenta Server controller you can not use the 

Menta ERR system block. The control application in a Xenta 700 type 

of device can use the Menta ERROR function block and also many system 

variables and signals in XBuilder. 

28.1 ERROR Blocks in an imported TAC Menta 

Application 

When you import a Menta application file, any existant ERR function 

block in the .mta source file will be replaced with a ERROR function. 

Important 

The Menta function blocks ERR and ERROR differ in functionality. 

For more information on these function blocks, see the TAC Menta, 


28.2 Adapting an ERR Block Design 

Existing Menta applications sometimes needs to be changed when used 

in a Xenta 700 controller. 

A typical example is when a Menta application needs to be changed is 

when the application uses a bit value which the ERROR function block 

does not adjust. Changing the Menta function block diagram to use a 

system variable in XBuilder can often solve the problem. 

28.3 ERROR Blocks in a New TAC Menta Application 

When you create a new Menta application, you have the option of using 

the ERROR function block and suitable XBuilder signals and variables. 


04-00123-01-en

28 ERR Function Blocks in the Control Application TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en


29 Changing the Receive Timer Value 

29 Changing the Receive Timer Value 

TAC Vista Workstation has a default value for the receive timer for the 

communication in a LonWorks network. This value is also in force for 

the Xenta Server. 

29.1 Changing the Receive Timer Value in TAC Vista 

Workstation 

When the Xenta Server is a subsystem to TAC Vista Workstation, the 

default value for the receive timer (24576 ms) is often too long for maintaining 

good communication when many Xenta I/O modules are connected 


In such cases, the value has to be decreased until satisfying communication 

is achieved. 

To change the receive timer value in TAC Vista Workstation 

1 In TAC Vista Workstation, right-click the required LonWorks Network 

in the Xenta Server. 

2 Click Properties. 

3 In the LonWorks Networks dialog, click the Timers tab. 


04-00123-01-en

29 Changing the Receive Timer Value TAC Xenta Server – Controller, Technical Manual 

4 In the Network timers area, in the Receive timer list, click the 

required value. 

5 Click OK. 

The new value will automatically be in force in the XBuilder project or 

in a Xenta Server online in the system. 

29.2 Changing the Receive Timer Value in the TAC 

XBuilder Project 

When the Xenta Server is used as a stand-alone system, that is not connected 

to a TAC Vista Workstation, you are recommended to make sure 

that the receive timer value in the XBuilder project has a necessary low 

value. 

To change the receive timer value in the TAC XBuilder 

project 

1 In the Network pane, click the LON network. 

2 In the properties pane, under File Transfer Timers, in the 

Receive Timer property list, click the required value. 

The new value will be in force when the project has been down-loaded 



04-00123-01-en


30 Connecting Rules in TAC XBuilder 


Table 30.1: Allowed connections of signals in XBuilder. 

Signals in XBuilder can be connected according to the following table: 

From\To 

TimeObject-Output. 

TimeObject-TimeLeft. 

Trendlog-input. 

Trendlog-start. 

Trendlog-send data. 

Alarm-input. 

Alarm-acknowledge. 

Alarm-output. 

Alarm-state. 

Connectio Object-from. 

Connectio Object-to. 

Menta-input. 

Menta-output. 

Graphic page. 

Value page. 

HTML varaible page. 

X X X X X X X X X 

X X X X X X X 

TimeObject- 

Output. 

TimeObject- 

TimeLeft. 

Trendloginput. 

Trendlogstart. 

Trendlogsend 

data. 

Alarminput. 

Alarmacknowledge. 

Alarmoutput. 

Alarmstate. 

X X X X X X X X X X 

X X X X X X X 


04-00123-01-en

30 Connecting Rules in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 


From\To 






Alarm-input. 


Alarm-output. 

Alarm-state. 



Menta-input. 

Menta-output. 

Graphic page. 

Value page. 


I/O K(n)- 

Value. 

I/O K(n)- 

HWForced. 

I/O K(n)- 

HWForcedValue. 

I/O U(n)- 

Value. 

I/O U(n)- 

CounterEnable. 

I/O X(n)- 

Value. 

I/O X(n)- 

CounterEnable. 

I/O Y(n)- 

Value. 

I/O Y(n)- 

HWForced. 

I/O B(n)- 

Value. 

System 

Variables. 

X X X X X X X X X X X X X X 










X X X X X X X X X X X X X X X X 

SNVTs. X X X X X X X X X X X X X X X X 

Mentapublic 

signals. 

X X X X X X X X X X X X X X X X 


04-00123-01-en




From\To 






Alarm-input. 


Alarm-output. 

Alarm-state. 



Menta-input. 

Menta-output. 

Graphic page. 

Value page. 


Menta- 

X 

Inputs. 

Menta- 

Outputs. 


Memory Signals. X X X X X X X X X X X X X X X X 

Legend: X indicates a permitted connection. 


04-00123-01-en

30 Connecting Rules in TAC XBuilder TAC Xenta Server – Controller, Technical Manual 


04-00123-01-en


Index 

Index 

A 

alarm object 

adapt 201 

imported from a TAC Menta application 200 

in a new TAC Menta application 201 

in control application 64 

alarm page 

create 201 

analog output Y 156 

applications folder 

add 51 

B 

BackupLM (folder) 25 

C 

connecting rules, in TAC XBuilder 215 

connection block type 

change 209 

control application 

add TAC Menta object to 51 

alarm object in 64, 199 

ERR block in 72 

I/O signal as SNVT in 64, 209 

SNVT object in 77 

time object in 63, 203 

trend log in 207 

trend log object in 64 

view the execution time 109 

control task 

accessing execution time value 191 

execution order 61 

in TAC XBuilder 187 

properties 187 

property 164 

control task assignment 

view 189 

control trask 

assign for a TAC Menta object 59 

D 

device address 

configure for a LON wall module 162 

configure for a TAC Xenta I/O module 127 

configure for a TAC Xenta I/O module using TAC 

Vista Workstation 128 

DeviceDescr (folder) 25 

digital input X 135 

digital output K 154 

Documentation (folder) 25 

dynamic data 

clear 193 

E 

ERR block 


ERR block design 

adapt 211 

ERROR block 


in an imported TAC Menta application 211 

execution order 

define 190 

property 165 

execution time 

accessing value for the control task 191 

view for a control application 109 

view value for the application in a TAC Menta 

object 194 

F 

filter view 

lock 99 

folder 

add applications folder 51 

folder structure, see project folder structure 

function block diagram 

view for a TAC Menta object 113 

G 

Graphics (folder) 25 

I 

I/O point 

use in TAC XBuilder 135 

I/O point list 

export from TAC XBuilder 117 

I/O signal 

as SNVT from from an imported TAC Menta 

application 209 


04-00123-01-en

Index 

as SNVT in the control application 64, 209 

input 

configure physical input 35 

L 

LON wall module 

add 161 

configure 162 

configure the device address for 162 


LonWorks network 

remove an existing TAC Xenta device from 27 

update 28 

N 

network address 

define in TAC XBuilder 126 

neuron ID 

assign for a TAC Xenta I/O module on the TAC Xenta 

Server web site 132 

assign for a TAC Xenta I/O module using TAC 

XBuilder 127 

O 

output 

configure physical output 39 

P 

physical inputs 

configure 35 

physical outputs 

configure 39 

project folder 

BackupLM 25 

create on hard disk 25 

DeviceDescr 25 

Documentation 25 

Graphics 25 

VistaDb 25 

project folder structure 

create on hard disk 25 

pulse output signal 

connect to a TAC Xenta I/O point 105 

R 

receiver timer value 

change in TAC Vista Workstation 213 

change in the TAC XBuilder project 214 

S 

signal 

connect a signal to a SNVT 97 


connect a signal to a TAC Xenta I/O point 102 

signal structure in TAC Menta object 165 

signal object 

delete unused 30 

SNVT 

as I/O signal in a new TAC Menta application 209 

connect a signal to a SNVT 97 

SNVT object 


system variable 

connect 108 

T 

TAC Menta application 

alarm object from 200 

alarm objects in a new … 201 

ERROR block in a new … 211 

ERROR block in an imported … 211 

I/O signal as SNVT from an imported … 209 

load part as macro 171 

SNVT as I/O signal in a new … 209 

time object from 203 

time object in a new … 204 

trend log object imported from 207 

trend log object in a new … 208 

view the execution time in a TAC Menta object 194 

TAC Menta application file 

add 53 

create 172 

import to a TAC Menta library object 181 

import to the TAC Menta object using TAC 

XBuilder 169 

import to the TAC Menta programming tool 169 


TAC Menta library 

add an existing TAC Menta object 178 

add TAC Menta object 180 

delete 185 

edit TAC Menta object 180 

export 184 

import 185 

make a local copy of an TAC Menta object 183 

use a TAC Menta object 182 


TAC Menta library object 

import a TAC Menta application file 181 

TAC Menta object 

add 52 

add to control application 51 

add to the TAC Menta library 178, 180 

assign a control task to 59 

connect a signal between objects 94 

connect a time object 204 


04-00123-01-en


edit in TAC Menta Library 180 

import a TAC Menta Application file using TAC 

XBuilder 169 

in TAC XBuilder 163 

make a local copy of an … from the TAC Menta 

Library 183 

properties 163 

signal structure 165 

TAC Xenta Server alarm object 199 

use a … from the TAC Menta Library 182 

view function block diagram 113 

view the execution time for the application 194 

TAC Menta programming tool 167 

import a TAC Menta application file 169 

TAC Vista Workstation 

configure a device address for a TAC Xenta I/O 

module 128 

TAC Workstation 

change receiver timer value 213 


add a TAC Xenta I/O module 126 

assign a neuron ID for a TAC Xenta I/O 

module 33, 127 

configure the TAC Xenta I/O points 126 

connecting rules 215 

control task 187 

define network address for TAC Xenta I/O 

module 126 

export an I/O point list 117 

import a TAC Menta application file to the TAC 

Menta object 169 

TAC Menta object in 163 

TAC Xenta I/O module properties 125 

use I/O point 135 

use LON wall module 161 

use TAC Menta application file 167 

use TAC Xenta I/O module 125 

use the TAC Menta library 177 

TAC XBuilder project 

change receiver timer value 214 

send to a TAC Xenta Server 47 

TAC Xenta device 

remove from LonWorks network 27 

TAC Xenta I/O module 

add 30, 126 

assign a neuron ID in TAC XBuilder 33 

assign a neuron ID on the TAC Xenta Server web 

site 132 

assign a neuron ID using TAC XBuilder 127 

configure a device address using TAC Vista 

Workstation 128 

configure device address 127 

configure TAC Xenta I/O points 126 

define network address 126 

Index 

properties in TAC XBuilder 125 


TAC Xenta I/O modules 

verify in the project 45 

view using a browser 48 

TAC Xenta I/O online signal 

connect 107 

TAC Xenta I/O point 

configure in TAC XBuilder 126 

connect a pulse output signal to 105 

connect signal to 102 

TAC Xenta Server 

send a TAC XBuilder project to 47 

TAC Xenta Server 700 variable 195 

add 196 

automatically added 195 

define source 197 

disconnect a signal from 198 

find signals connected to 197 

use the state 197 

use the value 197 

TAC Xenta Server alarm object 

in a TAC Menta object 199 

TAC Xenta Server project 

save in TAC Vista 45 

TAC Xenta Server web 

assign a neuron ID for a TAC Xenta I/O module on 

the site 132 

task dynamic data 

clear 112 

time object 

connect to a TAC Menta object 204 


in a control application 63, 203 


time object page 

create 205 

trend log 

adapt 207 

in a control application 207 

trend log object 


in a control application 64 


trend log page 

create 208 

U 

universal input U 137 

V 

VistaDb (folder) 25 


04-00123-01-en

Index 


X 

.xif file 

create 92 


04-00123-01-en


Index 


04-00123-01-en

Index 



04-00123-01-en

Copyright © 2007, TAC AB 

All brand names, trademarks and registered trademarks are 

the property of their respective owners. Information contained 

within this document is subject to changewithout notice. 

All rights reserved. 

04-00123-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.com 

Last Manual Page

TAC Xenta Server â Controller - IAS Automatika

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

TAC Xenta Server â Controller - IAS Automatika