Vista V

TAC Menta
Technical Manual
TAC Menta
Technical Manual
Copyright © 2006 TAC AB. All rights reserved.
This document, as well as the product it refers to, is only intended for licensed users. TAC AB owns the copyright of this document and reserves
the right to make changes, additions or deletions. TAC AB assumes no responsibility for possible mistakes or errors that might appear in this
document.
Do not use the product for other purposes than those indicated in this document.
Only licensed users of the product and the document are permitted to use the document or any information therein. Distribution, disclosure,
copying, storing or use of the product, the information or the illustrations in the document on the part of non-licensed users, in electronic or
mechanical form, as a recording or by other means, including photo copying or information storage and retrieval systems, without the express
written permission of TAC AB, will be regarded as a violation of copyright laws and is strictly prohibited.
Trademarks and registered trademarks are the property of their respective owners.
TAC Menta, Technical Manual Contents
Contents
INTRODUCTION
1 Introduction 15
1.1 Structure ..................................................................................................................... 15
1.2 Prerequisites ............................................................................................................... 16
1.3 Terminology ............................................................................................................... 17
1.4 New in this Edition..................................................................................................... 19
1.5 Typographic Conventions .......................................................................................... 19
GETTING STARTED
2 Menta Programming Fundamentals. 23
2.1 Basic project analysis ................................................................................................. 23
2.2 System configuration ................................................................................................. 23
2.3 Application Programming Phases .............................................................................. 23
2.4 Function Phase of the Application Programming ...................................................... 24
2.5 Design Phase of the Application Programming ......................................................... 24
2.5.1 Point Identification and Allocation ............................................................................ 24
2.5.2 Naming of Points and Alarms. ................................................................................... 24
2.5.3 Structuring the FBD ................................................................................................... 25
2.5.4 Using Modules in the Application ............................................................................. 26
2.5.5 Menus in the OP......................................................................................................... 26
2.6 Test Phase of the Application Programming ............................................................. 28
3 Planning the Project 29
3.1 Folder Structure.......................................................................................................... 29
3.1.1 Creating the Project Folder ........................................................................................ 29
3.2 Case Study.................................................................................................................. 29
3.2.1 Description of the Facility.......................................................................................... 29
3.2.2 Device Description and Naming Convention ............................................................ 30
3.2.3 Devices in Our Example ............................................................................................ 32
4 The RTU4 Application 33
4.1 Functional Description ............................................................................................... 33
4.2 Organizing the FBD ................................................................................................... 36
4.3 Configuring the Device in Menta............................................................................... 38
4.4 The Zone Bypass state ............................................................................................... 40
4.4.1 Designing the FBD..................................................................................................... 40
4.4.2 Simulating the Design ................................................................................................ 43
4.5 Starting and Stopping the VAV AHU Fan................................................................. 45
4.5.1 Designing the FBD..................................................................................................... 45
TAC AB, Nov 2006 5 (450)

04-00030-01-en
Contents TAC Menta, Technical Manual

4.6 The VAV AHU Fan VSD Control ............................................................................. 69
4.6.1 Designing the FBD ..................................................................................................... 69
4.7 The Relief Damper/Fan Control................................................................................. 83
4.8 Economizer Mode Calculations ................................................................................. 103
4.9 The OA/RA Damper Control ..................................................................................... 124
4.10 The DX Cooling Control ............................................................................................ 146
4.11 The DX Cooling Control Logic.................................................................................. 160
4.12 The Values for Graphic Displays ............................................................................... 179
4.13 The I/O Alarms and Energy Consumption ................................................................. 190
4.14 The Trend log ............................................................................................................. 200
4.15 The OP Menu Tree ..................................................................................................... 203
4.16 Downloading to the Xenta Device ............................................................................. 205
4.17 System Configuration and Documentation ................................................................ 207
REFERENCE
5 Introduction to TAC Menta 227
5.1 System of Units .......................................................................................................... 227
5.2 Operation Modes ........................................................................................................ 227
5.3 Program Licenses ....................................................................................................... 228
5.4 Setup ........................................................................................................................... 228
5.5 TAC Menta Start ........................................................................................................ 229
6 General Concepts 231
6.1 Function Block Diagrams........................................................................................... 231
6.2 Signals ........................................................................................................................ 232
6.2.1 Signal Types ............................................................................................................... 232
6.2.2 Signal Names.............................................................................................................. 232
6.2.3 Public Signals ............................................................................................................. 233
6.3 Connections ................................................................................................................ 233
6.4 Function Blocks.......................................................................................................... 233
6.4.1 Simple Blocks............................................................................................................. 234
6.4.2 Expressions................................................................................................................. 234
6.4.3 Operators .................................................................................................................... 235
6 (450) TAC AB, Nov 2006

04-00030-01-en
6.4.4 Test Probes ................................................................................................................. 235

6.4.5 Function Block Groups .............................................................................................. 236
6.5 Constants .................................................................................................................... 236
6.5.1 Constant Names ......................................................................................................... 236
6.5.2 Public Constants......................................................................................................... 236
6.6 External I/O Signals ................................................................................................... 237
6.6.1 I/O Blocks .................................................................................................................. 237
6.6.2 Public Parameters....................................................................................................... 241
6.7 Modules...................................................................................................................... 241
6.8 Hierarchical Function Blocks (HFB) ......................................................................... 242
6.9 Access Rules .............................................................................................................. 243
6.9.1 Signals ........................................................................................................................ 243
6.9.2 Constants .................................................................................................................... 244
6.10 Time Schedules .......................................................................................................... 244
6.11 Alarm Texts................................................................................................................ 244
6.12 Local Trend Logging in the TAC Xenta .................................................................... 244
6.13 Data Files ................................................................................................................... 245
7 The Mouse and Function Keys 247
7.1 The Mouse.................................................................................................................. 247
7.2 The Function Keys ..................................................................................................... 248
8 Edit Mode 251
8.1 Function Blocks ......................................................................................................... 251
8.1.1 Creating a New Block ................................................................................................ 251
8.1.2 Editing a Block........................................................................................................... 252
8.1.3 Moving a Block.......................................................................................................... 254
8.1.4 Deleting a Block......................................................................................................... 254
8.1.5 Disconnecting a Block ............................................................................................... 254
8.2 Connections................................................................................................................ 255
8.2.1 Drawing a Connection................................................................................................ 255
8.2.2 Deleting a Connection................................................................................................ 256
8.2.3 Moving a Node........................................................................................................... 256
8.2.4 Breaking a Connection ............................................................................................... 256
8.2.5 Highlighting a Connection ......................................................................................... 256
8.2.6 Orthogonal Connections............................................................................................. 256
8.3 Operations on Groups ................................................................................................ 257
8.3.1 Selecting a Group ....................................................................................................... 257
8.3.2 Deselecting a Group ................................................................................................... 257
8.3.3 Moving a Group ......................................................................................................... 258
8.3.4 Disconnecting a Group............................................................................................... 258
8.3.5 Deleting a Group ........................................................................................................ 258
8.3.6 Entering or Editing the Module Name ....................................................................... 258
8.3.7 Copying and Pasting a Group .................................................................................... 259
8.3.8 Copying a Selection Rectangle to the Clipboard ....................................................... 259
8.3.9 Centering the Selection Rectangle ............................................................................. 259
8.3.10 Printing the Selection Rectangle ................................................................................ 259
8.3.11 Macro Commands in Comment Blocks ..................................................................... 259
8.3.12 Saving a Macro Block ................................................................................................ 260
8.3.13 Loading a Macro Block.............................................................................................. 261
8.4 Hierarchical Function Blocks (HFB) ......................................................................... 261
TAC AB, Nov 2006 7 (450)

04-00030-01-en
8.4.1 Creating an HFB......................................................................................................... 261

8.4.2 Naming an HFB and Connections .............................................................................. 262
8.4.3 Expanding and Compressing an HFB ........................................................................ 262
8.4.4 Printing out an HFB.................................................................................................... 263
8.5 Constants Table .......................................................................................................... 263
8.5.1 Adding a Constant ...................................................................................................... 263
8.5.2 Editing a Constant ...................................................................................................... 263
8.5.3 Removing a Constant ................................................................................................. 263
8.6 I/O Configuration Table ............................................................................................. 264
8.7 Time Schedule Table .................................................................................................. 264
8.8 Alarm Text Table ....................................................................................................... 265
8.9 Local Trend Logging in TAC Xenta .......................................................................... 265
8.9.1 Selecting a Trend Log ................................................................................................ 266
8.9.2 Defining a Trend Log ................................................................................................. 266
8.10 Setting Date and Time ................................................................................................ 268
8.11 Finding and Replacing a Text String.......................................................................... 268
8.12 Undo ........................................................................................................................... 269
9 Simulation Mode 271
9.1 Compiling the FBD .................................................................................................... 271
9.2 Execution of the Application Program ....................................................................... 272
9.2.1 Starting, Stopping and Initializing Execution ............................................................ 272
9.2.2 Actions affecting the Signals...................................................................................... 273
9.2.3 Highlighting a Connection ......................................................................................... 273
9.2.4 Simulating Executable Files ....................................................................................... 274
9.3 Simulating External Inputs ......................................................................................... 274
9.3.1 Manual Mode of Operation ........................................................................................ 274
9.3.2 Automatic Generation of Input Vectors ..................................................................... 274
9.3.3 Simulation Using Test Probes .................................................................................... 276
9.4 Trend Logging ............................................................................................................ 276
9.4.1 Adding a Signal To the Recorder ............................................................................... 277
9.4.2 Removing a Signal From the Recorder ...................................................................... 277
9.4.3 Clearing the Recorder................................................................................................. 277
9.4.4 Restarting the Recorder .............................................................................................. 277
9.4.5 Resetting the Recorder ............................................................................................... 277
9.4.6 Viewing the Trend Log .............................................................................................. 277
9.4.7 Defining the Sample Time.......................................................................................... 278
9.5 The Logger Tool......................................................................................................... 278
9.5.1 Starting the Logger ..................................................................................................... 278
9.5.2 Diagram Setup ............................................................................................................ 278
9.5.3 Presentation and Analysis of Logged Values ............................................................. 279
9.5.4 Saving and Viewing a Log File .................................................................................. 280
9.5.5 Clearing the Logger .................................................................................................... 280
9.6 Modifying Block Parameters During Simulation....................................................... 280
9.6.1 Function Block Parameters......................................................................................... 280
9.6.2 Time Schedules .......................................................................................................... 280
9.6.3 I/O Binding Data ........................................................................................................ 281
9.6.4 Constants .................................................................................................................... 281
9.6.5 Alarm Texts ................................................................................................................ 281
9.6.6 The ERR Block........................................................................................................... 281
8 (450) TAC AB, Nov 2006

04-00030-01-en
10 OP Configuration Tool 283

10.1 The Menu Structure Display ...................................................................................... 284
10.2 Creating the Menu Structure ...................................................................................... 285
10.2.1 Adding Menu Items.................................................................................................... 285
10.2.2 Sub Menu ................................................................................................................... 286
10.2.3 Status .......................................................................................................................... 286
10.2.4 Alarm.......................................................................................................................... 288
10.2.5 Access Code ............................................................................................................... 288
10.2.6 Date and Time/Daylight Saving................................................................................. 288
10.2.7 Week/Holiday Chart................................................................................................... 289
10.2.8 TAC Service Menu .................................................................................................... 289
10.3 Editing an Existing Menu Structure Tree................................................................... 289
10.3.1 Moving Menu Items ................................................................................................... 290
10.3.2 Changing the Operator Panel Display Layout ........................................................... 290
10.3.3 Copying and Pasting .................................................................................................. 290
10.4 Automatic Generation of an OP Menu Tree .............................................................. 290
10.5 OP Description Files .................................................................................................. 291
10.5.1 Data and Declarations Syntax in OP Description Files (.DOP)................................. 292
10.5.2 OP Description File Example..................................................................................... 294
10.5.3 Importing the OP Description File ............................................................................. 294
10.5.4 Exporting the OP Description File ............................................................................. 295
10.6 Defining a Character Set File ..................................................................................... 295
10.7 Menu Options............................................................................................................. 296
10.7.1 Menu Bar.................................................................................................................... 296
11 Other Functions and Tools 303
11.1 The Program Specification......................................................................................... 303
11.2 Device Configuration ................................................................................................. 304
11.3 Generating Executable Code...................................................................................... 308
11.4 Calculating Memory Usage........................................................................................ 309
11.5 Online Functions ........................................................................................................ 311
11.5.1 Online Mode............................................................................................................... 311
11.6 Downloading the Application Program ..................................................................... 312
11.7 Uploading Application Data ...................................................................................... 313
11.8 Overriding Physical I/O Signals................................................................................. 313
11.9 Modifying Parameter Blocks in Online Mode ........................................................... 314
11.10 Modifying Public Constants in Online Mode ............................................................ 314
11.11 Modifying Binding Parameters in Online Mode........................................................ 315
11.12 Unique Application Program ID ................................................................................ 315
11.13 Marking Standard Applications/Controllers .............................................................. 315
11.14 Printing the Application Program Documentation..................................................... 315
11.15 Associated Text Files ................................................................................................. 317
12 The Download Wizard 319
12.1 How to Use the Download Wizard ............................................................................ 320
12.1.1 The Dialog.................................................................................................................. 320
12.1.2 The General Download Procedure ............................................................................. 321
12.2 TAC Menta v3 Compatibility .................................................................................... 322
12.2.1 .AUT Files.................................................................................................................. 322
12.2.2 .COD Files.................................................................................................................. 322
12.2.3 OP Menu Tree Files ................................................................................................... 323
TAC AB, Nov 2006 9 (450)

04-00030-01-en
12.3 Upgrading a TAC Xenta 300 Device to v3 ................................................................ 323

12.3.1 Updating the .AUT File with Application Data (Optional)........................................ 323
12.3.2 Upgrading System and Application Programs ........................................................... 323
12.3.3 Verifying Correct Operation (Optional But Recommended) ..................................... 324
13 Function Blocks, Summary 325
13.1 I/O Blocks................................................................................................................... 325
13.2 Signal Sources ............................................................................................................ 326
13.3 Logical Functions ....................................................................................................... 326
13.4 Non-linear Functions .................................................................................................. 326
13.5 Delay Blocks .............................................................................................................. 327
13.6 Controllers and Filters ................................................................................................ 327
13.7 Accumulators.............................................................................................................. 328
13.8 System Variables ........................................................................................................ 328
13.9 Time Schedules and Alarms ....................................................................................... 328
13.10 Transformation Functions .......................................................................................... 329
14 Simple Blocks 331
14.1 ACCUM – Accumulator............................................................................................. 332
14.2 AHYST – Analog Hysteresis ..................................................................................... 333
14.3 AI – Analog Input....................................................................................................... 334
14.4 ALARM – Alarm ....................................................................................................... 339
14.5 AND – Logical AND Gate ......................................................................................... 341
14.6 AO – Analog Output .................................................................................................. 342
14.7 CNT – Digital Input – Pulse Counter ......................................................................... 345
14.8 CURVE – Curve Function.......................................................................................... 346
14.9 DATE – Day............................................................................................................... 348
14.10 DELAY – Delayed On/Off......................................................................................... 349
14.11 DELB – Binary Value Delay...................................................................................... 350
14.12 DELI – Integer Value Delay....................................................................................... 350
14.13 DELR – Real Value Delay ......................................................................................... 351
14.14 DI – Digital Input ....................................................................................................... 351
14.15 DO – Digital Output ................................................................................................... 356
14.16 DOPU – Digital Pulse Output .................................................................................... 358
14.17 ENTH – Enthalpy ....................................................................................................... 359
14.18 ERR – System Error ................................................................................................... 362
14.19 Error Codes................................................................................................................. 362
14.20 FILT – First Order Filter ............................................................................................ 363
14.21 HOUR – Hour............................................................................................................. 364
14.22 HYST – Binary Hysteresis ......................................................................................... 365
14.23 INTEG – Integrator .................................................................................................... 366
14.24 LIMIT – High/Low Signal Limit ............................................................................... 367
14.25 MAX – Maximum Signal Selector............................................................................. 367
14.26 MIN – Minimum Signal Selector ............................................................................... 368
14.27 MINUTE – Minute ..................................................................................................... 368
14.28 MONTH – Month....................................................................................................... 369
14.29 NCYC – Program Cycle Counter ............................................................................... 369
14.30 NOT – NOT Gate ....................................................................................................... 370
14.31 OPT – Optimization ................................................................................................... 371
14.32 OR – OR Gate ............................................................................................................ 378
14.33 OSC – Oscillator......................................................................................................... 379
10 (450) TAC AB, Nov 2006

04-00030-01-en
14.34 PIDA – PID Controller – Analog Output................................................................... 380

14.35 PIDI – PID Controller – Incremental Output ............................................................. 383
14.36 PIDP – PID Controller – Analog Output ................................................................... 385
14.37 POLY – Polynomial Function.................................................................................... 389
14.38 PRCNT – Percentage ................................................................................................. 390
14.39 PULSE – Pulse Generator .......................................................................................... 391
14.40 PVB – Binary Value Parameter ................................................................................. 392
14.41 PVI – Integer Value Parameter .................................................................................. 392
14.42 PVR – Real Value Parameter ..................................................................................... 394
14.43 RAMP – Ramp Filter ................................................................................................. 394
14.44 RST – Restart ............................................................................................................. 395
14.45 RT – Run-Time Measurement ................................................................................... 395
14.46 SECOND – Second .................................................................................................... 396
14.47 SEQ – Sequencer........................................................................................................ 397
14.48 SHB – Sample and Hold Binary Value...................................................................... 399
14.49 SHI – Sample and Hold Integer Value....................................................................... 400
14.50 SHR – Sample and Hold Real Value ......................................................................... 401
14.51 SR – Set-Reset Flip-Flop ........................................................................................... 402
14.52 STRIN – STR Input ................................................................................................... 404
14.53 STROUT – STR Output............................................................................................. 405
14.54 TCYC – Cycle Time .................................................................................................. 407
14.55 TRIG – Trigger .......................................................................................................... 407
14.56 TSCH – Time Schedule ............................................................................................. 408
14.57 VECTOR – Vectorial Curve Function ....................................................................... 410
14.58 WDAY – Week Day .................................................................................................. 412
14.59 XOR – Exclusive OR Gate ........................................................................................ 412
15 Expressions 415
15.1 Operands .................................................................................................................... 416
15.2 Operators .................................................................................................................... 416
15.3 Aritmethical Functions............................................................................................... 417
15.4 Output......................................................................................................................... 418
16 Operators 419
16.1 Constants .................................................................................................................... 419
16.2 Logical Operators....................................................................................................... 419
16.3 Math Operators........................................................................................................... 420
16.4 Comparison ................................................................................................................ 420
16.5 Bit Operation .............................................................................................................. 421
16.6 Others ......................................................................................................................... 422
17 Supported SNVTs 425
17.1 List of SNVTs ............................................................................................................ 425
18 Test Probe Blocks 429
18.1 Summary .................................................................................................................... 429
18.2 TPAI – Test Probe for Analog Input.......................................................................... 430
18.3 TPAO – Test Probe for Analog Output...................................................................... 430
18.4 TPDI – Test Probe for Digital Input .......................................................................... 431
18.5 TPDO – Test Probe for Digital Output ...................................................................... 432
19 Error Messages 433
TAC AB, Nov 2006 11 (450)

04-00030-01-en
19.1 System Errors ............................................................................................................. 433

19.2 FBD Compilation ....................................................................................................... 433
19.3 Saving and Loading the Application Program in the Database.................................. 435
19.4 Simulation................................................................................................................... 436
19.5 Code Generation ......................................................................................................... 436
19.6 Download ................................................................................................................... 437
19.6.1 Error Codes................................................................................................................. 437
19.7 TAC Xenta Communication....................................................................................... 438
20 Programming Hints 439
20.1 Program Cycle Time................................................................................................... 439
20.2 Time Counter.............................................................................................................. 439
20.3 Equality....................................................................................................................... 439
20.4 Reset Counter ............................................................................................................. 440
20.5 Bitwise Logical Operators.......................................................................................... 440
20.6 Multiplier Parameter in CNT Block ........................................................................... 440
20.7 Sliding Average Value ............................................................................................... 441
20.8 TSCH Output.............................................................................................................. 441
20.9 PIDI – DOPU ............................................................................................................. 441
20.10 Day Shift..................................................................................................................... 442
20.11 Expression Blocks ...................................................................................................... 442
20.12 Start-Up Delay............................................................................................................ 442
Index 443
12 (450) TAC AB, Nov 2006

04-00030-01-en
INTRODUCTION
1 Introduction
TAC Menta, Technical Manual 1 Introduction
1 Introduction
This manual describes the use of the TAC Menta programming tool.
For information of specific products we refer to the manual of the prod-
uct in question.
For information on how to install software, please refer to the instruc-
tions delivered with the software.
For information on specific products, please refer to the manual for the
product in question.
If you discover errors and/or unclear descriptions in this manual, please
contact your TAC representative.
Note
We are continuously improving and correcting our documentation.
This manual may have been updated.
Please check our Docnet site at www.tac-global.com for the latest ver-
sion.
1.1 Structure
This handbook is divided into the following parts:
• Introduction
The Introduction section contains information on how this handb-
bok is structured and how it should be used to find information in
the most efficient way.
• Getting Started
The Getting Started section covers some fundamentals of Menta
programming. An application from the ACME project is used as
example for step-by-step design description of how to engineer or
operate tasks described in this manual.
• Reference
The Reference section contains more easily comprehensible infor-
mation about various parts of the Menta programming tool. It also
gives you information on alternative solutions not covered in the
Getting Started section.
TAC AB, Nov 2006 15 (450)

04-00030-01-en
1 Introduction TAC Menta, Technical Manual
1.2 Prerequisites
To be able to profit from the contents in this manual, you are recom-
mended to read the following manuals:
• TAC Xenta 280 - 300 - 401 Handbook, and
• TAC Xenta OP Handbook
16 (450) TAC AB, Nov 2006

04-00030-01-en
1.3 Terminology
Term Description
TAC Xenta All programmable TAC Xentas, 280/300/401,
Devices will be called Xenta devices throughout this
manual.
When talking about the Xenta 511/911 and the
Xenta 901, we will use their proper names.
The Xenta 422, 452 etc. will be referred to as I/
O modules.
LonWorks All other devices will be called LonWorks
Devices devices, including the Xenta 100.
Classic Network Classic Network refers to a TAC Vista system
with a LonWorks network, TAC Xenta devices
and/or LonWorks devices, using an LTA port
connection/communication to the network and
no LNS database. A Classic Network does
NOT use any SNVT bindings.
LNS Network LNS Network refers to a TAC Vista system
with a LonWorks network, TAC Xenta devices
and/or LonWorks devices, using an LTA port
with a VNI as the Network Interface (NI) appli-
cation, LonMaker 3 and an LNS database. This
type of LTA port is referred to as an LNS port
in TAC Vista.
TAC Xenta A standard controller or a freely programmable
unit with a modular I/O configuration.
OP Operator Panel on the TAC Xenta device.
LonWorks™ The standardized network, used for communi-
cation between the TAC Xenta devices.
TAC Vista A PC based operator unit for the monitoring
and control of air handling and heating systems.
TAC Menta Application programming tool for TAC Xenta.
OP configuration Programming tool for the TAC Xenta Operator
toolpanel, included in TAC Menta.
ASCII American Standard Code for Information Inter-
change.
BMS Building Management System
HVAC Heating, Ventilation & Air Conditioning
TAC AB, Nov 2006 17 (450)

04-00030-01-en
Term Description
ID Plant specific names/descriptors of points etc.
I/O Input/Output
B Defines a physical terminal in a TAC Xenta
device, used for thermistor type inputs.
Cold Start Restart after a power outage which has lasted
longer than 72h, i.e. when the contents of the
RAM in the TAC Xenta are no longer reliable.
FB Function Block
FBD Function Block Diagram.
OP Configuration Programming tool for the TAC Xenta Operator
Tool panel, included in TAC Menta.
OP Operator Panel for the TAC Xenta controller.
SNVT Standard Network Variable Type, which
enables LonWorks™ network communication
between nodes from different manufacturers.
TAC Menta Application programming tool for TAC Xenta
controllers.
TAC Xenta A series of application specific standard con-
trollers (TAC Xenta 3000) and freely program-
mable controllers (TAC Xenta 300/401) with a
modular I/O configuration, and a slimmed-
down version (TAC Xenta 280) without I/O
configuration.
TAC Vista Tool for display and control.
U Defines a physical terminal in a TAC Xenta
device, used for universal type inputs.
Warm Start Restart after a power outage less than 72 h, that
is when the RAM content of the TAC Xenta is
still reliable.
X Defines a physical terminal in a TAC Xenta
device, used for digital type inputs.
Y Defines a physical terminal in a TAC Xenta
device, used for analog type outputs.
K Defines a physical terminal in a TAC Xenta
device, used for relay type outputs.
18 (450) TAC AB, Nov 2006

04-00030-01-en
1.4 New in this Edition

A Getting Started section is added to the manual.
The Getting Started section covers:
• Menta Programming Fundamentals
• Planning the Project
• The RTU4 Application
1.5 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 com-
pletion 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.
TAC AB, Nov 2006 19 (450)

04-00030-01-en
20 (450) TAC AB, Nov 2006

04-00030-01-en
GETTING STARTED
2 Menta Programming Fundamen-
tals.
3 Planning the Project
4 The RTU4 Application
TAC Menta, Technical Manual 2 Menta Programming Fundamentals.
2 Menta Programming Fundamentals.

Before you actually program a Xenta device in a project, there are some
activities to consider.
2.1 Basic project analysis

The basic project analysis contains planning activities, which greatly
affect the number of engineering hours that will be needed later on in
the project. The more complete this is made, the less need there will be
to supplement the programming.
2.2 System configuration

System configuration deals with the layout of the installed system:
where to locate Operator units, the Xenta devices, and how the network
is composed. Of course, it will be most beneficial to do this at an early
stage of a project.
2.3 Application Programming Phases

Application programming of the TAC Xenta device can be divided into
the following phases;
• Function phase
• Design phase
• Test phase:
Function phase Design phase Test phase
FBD programming
Functional System Delivery to plant,

OP configuration
specification tests commissioning
User documentation
TAC AB, Nov 2006 23 (450)

04-00030-01-en
2 Menta Programming Fundamentals. TAC Menta, Technical Manual
The Function Phase

During the Function phase, the functional specification is read, and your
own analysis added. During this stage, you will find out to what extent
you can reuse applications which are already designed.
The Design Phase
During the Design phase, the application program, the optional menus
for an Operator panel, and the user documentation will partly be created
in parallel.
The Test Phase
The Test phase can consist of two parts:
- Off-line functional tests of the program modules as they are integrated
during the design phase. Normally, this is done using the Menta in sim-
ulation mode.
- A final system test where the complete application, including the OP
menu tree, is downloaded to a TAC Xenta device and tested.
2.4 Function Phase of the Application Programming

During the Function phase, the functional specification is read and
interpreted. Your own analysis is added and an overall solution is
formed. During this stage, you will sometimes also need to acquire
more data regarding parts in the installation, affecting the programming.
An important part of this phase is to find the available applications in
your library, which are ready to use or which may only require small
changes or adaptions.
2.5 Design Phase of the Application Programming

2.5.1 Point Identification and Allocation
The importance of a good point allocation is often underestimated.
There is a very close relationship between a well-prepared point alloca-
tion and the efficiency that can be achieved later on in the project.
With good point allocation, copying techniques can substantially reduce
the engineering hours needed for design/manufacturing of electrical
panels. Installation and commissioning work will also benefit from
point allocation being done efficiently.
2.5.2 Naming of Points and Alarms.

The naming of points and signals is an important part of design work.
I/O and signals are best given names that are descriptive and easy to rec-
ognise. The customer or enduser has often specific demands on the use
24 (450) TAC AB, Nov 2006

04-00030-01-en
of acronyms or designations. The same applies, even in a higher degree,

for alarm texts.
2.5.3 Structuring the FBD

In the FBD, the function blocks process input signal(s) to generate a
single output signal. The output signal is transported to other blocks fol-
lowing the route defined by the connections, which represent the data
flow, from left to right, during program execution.
Data flow Connections
DI DO
The design phase starts with the overall structuring, that is identifying
the main functions and how to graphically locate these function groups
in relation to each other.
The grouping can be doen in several ways. The most important thing is
to make the FBD easy to understand. Function blocks that perform a
function together should preferrably be located together.
The second step is to graphically locate the groups. Create a left-to-right
logical sequence in the FBD, meaning that, if there is a connection
between two groups, placing a group that delivers an output, to the left
of a group that recieves an input. To standardize this, we recommend a
logical order from left-to-right: START CONDITION - STOP CONDI-
TION - GENERAL CONTROL - PID CONTROL SEQUENCES -
ALARM HANDLING.
Program header
STOP GENERAL PID CONTROL ALARM
START
CONDITION CONDITION CONTROL SEQUENCES HANDLING
When you locate blocks and groups, in accordance with the described
structure, use the following rules of thumb:
• Enter a framed comment containing the last edition date of the
FBD in the upper left corner. History notes, describing the revi-
sion, can also be included. Update this information whenever you
make a program revision.
TAC AB, Nov 2006 25 (450)

04-00030-01-en
• Try to structure every page so that the physical input blocks are
arranged in a column to the left, and the physical output blocks are
in a column to the right.
• Adjust the FBD to the page break lines, so that a printout will be
easy to read.
• Make space between the groups so that it will be possible to draw
extra connections and additional functions.
• Add new pages to the right when necessary, but try to use only one
page in a vertical direction.
• Mostly it will be convenient to use/locate connections like a bus
with common left-to-right connections at the top of the diagram.
Try to avoid connections running in the opposite direction. But
whenever necessary, put these connections in a separate bus at the
bottom of the page. Mark the direction of these signals.
1.7-9 1.6-9
1.7-6 1.6-6
1.7-10 1.6-10
Fan control Cooling/heating sequence
1.7-1 1.6-1
<<< <<<
1.7-12 1.6-12
1.7-4 1.6-4
1.7-11 1.6-11
1.7-7 1.6-7 1.7-3 1.6-3
1.7-8 1.6-8
1.7-2 1.6-2
1.7-5 1.6-5
• Reuse tested macro blocks from the Macro Block Library or your
own library as much as possible.
2.5.4 Using Modules in the Application

Using a module part in the full signal name will enable you to divide the
application program into different parts so that the parts can be handled
separately in TAC Vista. Public signals within a Module will be located
in the same logical unit in the Vista database. Signals having a module
part in the name will also form sub menus when automatically generat-
ing an OP menu tree.
Structure the application program so that all public signals that you
want to display together will belong to the same Module (and have the
same module name).
2.5.5 Menus in the OP

The menus in an Operator Panel (OP) will have their contents deter-
mined by two different factors.
The two upper levels are determined when the network is created. The
application levels are determined when the application is created using
TAC Menta.
26 (450) TAC AB, Nov 2006

04-00030-01-en
Upper Levels Menus

The structure of the upper level menus used in a Xenta OP is created
when you create Xenta groups and give the Xenta devices their Network
names. The OP displays a view of the network: on the top level, the
TAC Xenta groups, and on the next level, the TAC Xenta devices within
each group.
These menus contains network information and shall be available in all
Xenta devices in the network. This is the reason why every Xenta
device need to have a new menu tree downloaded whenever a new
Xenta Group is added (or renamed) in a network. Whenever a new
Xenta device is added (or renamed) in a network, new information must
be downloaded to all devices in the group with the new (or renamed)
device.
The preparatory work, determining the need for all Xenta devices
including grouping and naming them, is thus of major importance in
order to avoid unnecessary work.
TAC Xenta OP Display
1ST _FLOOR
1ST_FLOOR_LW
2ND_FLOOR
Group Level
CONF_ROOM
LOBBY
RTU4
Device Level
RTU4 RTU4
Info
Binary
Analog
Application Level
Application Level Menus

You can reach the application menu by selecting, first the Xenta group
and then the Xenta device, from the menu tree.
The following menu level windows will show the Xenta device identi-
fied on the first line as an abbreviation. This abbreviation can be the
device name, shortened to a maximum of four characters if necessary.
TAC AB, Nov 2006 27 (450)

04-00030-01-en
The next string on the same line is the name of the application. The
abbreviation and the application name are entered using the Program
Specification form in TAC Menta.
The contents of the remaining lines in these device specific menu win-
dows are created when you use the OP configuration tool.
These menus only contain device specific information and will only be
available in the specific Xenta devices. The revised meny tree is only
downloaded to the actual Xenta device.
2.6 Test Phase of the Application Programming

Testing an application is done using the Simulation mode in TAC
Menta. Often, this is done in offline mode, that is without having a
Xenta device connected. Occasionally, the online mode, with a Xenta
device directly connected, can be used. The possibility to start/stop pro-
gram execution and to alter values/states can be helpful when trouble-
shooting an application.
28 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 3 Planning the Project
3 Planning the Project

Planning the LonWorks Network in advance will save a lot of time and
effort later on in the process. Issues like network structure (groups) and
device-naming conventions, etc. should be considered before actually
creating the Project.
3.1 Folder Structure

Another consideration is the location(s) on the hard drive where files
will be stored. A well-organized project requires a well-organized file
structure.
3.1.1 Creating the Project Folder

When starting a new project you should prepare a directory containing
folders and subfolders as shown below. In this example we will call our
project ACME.
A brief description of their intended use and content:

DeviceDescr
In this folder, we save the *.mta-files. XXX files, *.xif-files for the
devices in the LonWorks network are also saved in this subfolder.
3.2 Case Study

The following chapters describe how to create the application software
for a Xenta device, using TAC Menta.
3.2.1 Description of the Facility

We will create an application for a fictional company called Acme Inc.
The facility is a typical, small, two-storey office building, served by
packaged rooftop equipment. The first floor area serves Marketing,
TAC AB, Nov 2006 29 (450)

04-00030-01-en
3 Planning the Project TAC Menta, Technical Manual
Accounts, Senior Management and the entrance lobby. The second

floor area serves Engineering and Customer Support.
Within the first floor area, the Accounting area is served by a constant
volume rooftop air handling unit. The air handling unit has central sta-
tion cooling and central station heating. The space is divided into con-
trol zones; the Accounting area and a conference room with secondary
air handling. The Marketing and Senior Management areas are served
by a single rooftop variable air volume (VAV) air handling unit. The
first floor lobby area is served by a rooftop constant-volume single zone
air handling unit.
On the second floor, the Customer Support area is served by a single
zone, rooftop constant-volume air handling unit. The Engineering area
is served by a Rooftop VAV air handling unit. The staff can supervise
the system using a PC-based presentation system.
Lobby
RTU1
RTU3
RTU2
RTU4
Lobby
Conf_Room Engineering
Accounts
Support
Conference Room
Marketing and Management
3.2.2 Device Description and Naming Convention

Within the first floor area, the rooftop unit serving the Accounting area
will be controlled by a Xenta 301 named RTU1.
The secondary air handling unit serving Marketing and Senior Manage-
ment will be controlled by a Xenta 281 named Conf_Room.
30 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 3 Planning the Project
The rooftop unit serving Marketing and Senior Management will be

controlled by a Xenta 401 named RTU2, using four I/O modules.
The air handling unit serving the lobby area will be controlled by a
Xenta 104 named Lobby.
Within the second floor area, the rooftop unit serving the Customer Sup-
port area will be controlled by a Xenta 104 named RTU3.
The rooftop unit serving the Engineering area will be controlled by a
Xenta 401 named RTU4, using five I/O modules.
The PC where the presentation system is installed will be called
VistaSrv_1 and this will be located in the Support area.
First Floor Second Floor
Xenta 301 RTU1 Xenta 104 RTU3
Xenta 401 RTU2 Xenta 401 RTU4
Xenta 281 Conf_Room
Xenta 104 Lobby
TAC AB, Nov 2006 31 (450)

04-00030-01-en
3 Planning the Project TAC Menta, Technical Manual
3.2.3 Devices in Our Example

In our example, we have selected the rooftop unit RTU4 to create the
application for a TAC Xenta 401 with two I/O modules.
VistaSrv_1
Lobby RTU4
Conf_Room
We will be working with the following devices:
Second Floor
RTU4
Xenta 401
I/O-Modules
Xenta 452
Xenta 422
32 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 4 The RTU4 Application
4 The RTU4 Application

In this chapter, we will create the application for RTU4, a Rooftop VAV
air handling unit in the ACME Project. We will also test most parts of
the design using the Simulation mode offline. Finally, the completed
application will be downloaded to the Xenta device using an RS232
connection.
The rooftop unit serves the Engineering area on the Second Floor and is
controlled by a Xenta 401 device named RTU4. The device has five I/
O expansion modules.
The user can supervise the system using a Vista Workstation.
4.1 Functional Description

Fan Start/Stop
The air handling unit is to be started on the basis of the time schedule or
whenever any zone is in bypass mode.
The unit can also be started in Timed Override mode by the operator via
a software timer with an adjustable time. Additional commands before
the timer has expired stops the Timed Override.
The operator can manually override the mode using the HMI or OP. The
operator can select Auto, Off, or Manual running. An alarm will be
issued when the unit is manually overridden.
A proofing function is to be provided with a time to state of 30 seconds.
If the fan state input is in the wrong state for more than 30 seconds, the
request for the fan is to be latched off and an alarm issued. The Alarm
latch is to be reset whenever an off command is issued.
The start is to be delayed for an adjustable time following a power
restore.
If the fan is running without the start relay being energized, there will
be an alarm.
When the fan is started and the system is busy, as determined by the
time schedule, an occupancy command is to be sent to all zone VAV ter-
minals.
Fan Variable Speed Device Control
Supply air static pressure is to be controlled using a VSD (variable
speed device). When the static pressure is above the set point, plus half
TAC AB, Nov 2006 33 (450)

04-00030-01-en
4 The RTU4 Application TAC Menta, Technical Manual
the deadband, the signal to the VSD is to be reduced by the bump

amount each sample. If the static pressure exceeds twice the setpoint,
the signal to the VSD is to be reduced by 3 times the bump amount each
sample. When the static pressure falls below the set point, minus half
the deadband, the signal to the VSD is to be increased by 2% once each
sample. When the static pressure is in the deadband, the signal to the
VSD is not to be changed.
The control signal to the VSD has to be an adjustable startup value dur-
ing a defined startup time period. The signal to the VSD is to be set to
zero when the fan is off.
If communication with the pressure sensor's I/O Module is lost or if the
pressure sensor fails, the VSD is to be run at startup speed.
Relief Fan and Damper Control
When the SFan is running, the Relief Damper modulates to maintain the
static pressure of the building at setpoint. If the damper is 100% open
and the static pressure exceeds 0.06 "wc for more than 10 minutes, the
Relief Fan will start. When the Relief Damper is modulated to less than
40% and the static pressure of the building falls below -0.01 "wc, the
Relief Fan will stop.
If there is a communication failure with I/O extension module 3, the
control signal calculated for the VSD will be used as control value for
the Relief Damper.
When the SFan is running, normal control is used. Otherwise the con-
troller output is zero. If there is a static pressure sensor alarm, the con-
troller output will be100 percent.
Economizer Mode Calculations
The economizer mode can be applied to the outside air and the return air
dampers. Calculations regarding enthalpy are to be made based on tem-
perature and humidity measurements of the outside air and the return
air. Offsets for calibrating the sensors are to be used. Alarms, represent-
ing sensor failures, are to be provided. Alarms for high and low Return
air temperatures are also to be provided..
When the outside air enthalpy is -2 BTU/lb below the return air
enthalpy and the fan is running, the economizer mode is to be be
enabled. The economizer mode is to be disabled if the unit supplying
outside air enthalpy measurement is offline. Economizer mode is to be
disabled when the outside air enthalpy rises above 0.5 BTU/lb below the
return air enthalpy.
OA/RA Damper Control
When the fan is running and the economizer mode is disabled, a mini-
mum position is to be imposed on the mixed air dampers. When the
economizer mode is enabled, the OA/RA dampers are to modulate in
order to maintain the mixed air temperature at setpoint. The opening
position of the damper(s) must be limited using an operator's setting
34 (450) TAC AB, Nov 2006

04-00030-01-en
with a minimum value for the opening degree of the dampers. When the
unit is off, the dampers must close.
DX Cooling Control
Four chillers are to be be started/stopped in sequence and adjusted to the
actual cooling demand, where the cooling demand is a function of the
supply fan (VSD) speed, adjusted with regard to the discharge air tem-
perature and the maximum terminal load.
Each chiller stage is to have a defined minimum on and a minimum off
time to be in service. There must also be a delay between the start of
each chiller stage.
The chiller stages are to be started and stopped on the demand level
using hysteresis.
The first chiller stage is to be started and stopped on the demand level,
and the following three chiller stages may only start when Economizer
mode is off.
Separate alarms are to be provided for each chiller stage.
Zone Values for Presentation and Alarms.
The difference between the Effective Setpoint and the actual Space
Temperature for zones VAV_4:1, VAV_4:2, VAV_4:3, VAV_4:4,
VAV_4:5, and VAV_4:6 is to be calculated for graphic display and
alarms when levels exceed their limits.
I/O Alarms
There must be alarms when any expansion I/O module is offline and
when an I/O is manually forced.
Chiller energy consumption
Data for the chiller compressor’s energy consumption is to be totalled
up and stored on both an hourly and a daily basis.
Trend Log
A Trend Log of the Discharge Air Temperature is to be defined.
OP menu tree
An automatically generated menu tree for the Operators panel is to be
generated.
Downloading to a Xenta device
The finished application is to be downloaded to a Xenta 401 device
using RS232 connection.
System Configuration and Documentation
For our project, the system configuration has been prepared. This means
that the Xenta device and expansion I/O modules have already been
selected. All signals and alarms have also bee determined in respect of
TAC AB, Nov 2006 35 (450)

04-00030-01-en
where they are connected, and their names and alarm texts are given. At
the end of this chapter you find the following documentation for the
Xenta device:
• Devices
• I/O point Allocation, SNVTs (Network Variables)
• Alarms
• Public Signals
• Constants
• Constants Usage
• Time Schedules
• Block Parameters
The documentation is arranged the same way as a Menta-generated
Xenta document.
4.2 Organizing the FBD

Taking into account the recommendations given in the previous chap-
ter(s), we want to allocate blocks, comprising the different functional-
ities, both together and in separate modules in the Function Block
Diagram (FBD). If possible, we also want them to appear on one print-
able page each.
We can identify the major parts of the application:
• Zone Bypass state for Terminal Units
• VAV AHU Fan Start Stop.
• VAV AHU Fan VSD Control.
• Relief Damper/Fan control.
• Economizer Calculations.
• Outside/Return Air Damper Control.
• DX Cooling Control.
• Calculation of Zone Values for Display and Alarm.
• I/O Alarms
In the Function Block Diagram, we will create separate modules for
these. In doing so, we will end up with an FBD of ten horizontal and two
vertical printable pages. The lower five pages will only be used for
showing "a bus like collection" of signals. We will try to place the
inputs to the left and the outputs to the right on each page.
36 (450) TAC AB, Nov 2006

04-00030-01-en
From left to right, the pages will display the following:
Zone Bypass Status VAV AHU Fan Start/Stop VAV AHU Fan VSD Control
Relief Damper/Fan Control Economizer Mode Calculations OA/RA Damper Control
DX Cooling Control DX Cooling Control Logic Zone Conditions for display
TAC AB, Nov 2006 37 (450)

04-00030-01-en
I/O Alarms and

Chiller Energy Consumption
4.3 Configuring the Device in Menta

Starting Menta
1 Start TAC Menta. The empty FBD window where your application
will be created appears on your screen.
You would normally start by selecting the Settings in the Preferences
menu to specify which editor to use for making text files, and where
your library folder with completed groups, macro blocks and modules
will belocated.
Device Configuration
This is how we define the hardware we are making the application for.
It is necessary for Menta to assist us when allocating the I/O points and
when downloading to a Xenta device.
For this device, we will use a TAC Xenta 401 equipped with five expan-
sion I/O modules.
2 Select Device configuration under the Options menu and specify
the Xenta 401 device. Use the Add button and define the I/O mod-
ules:
Unit Name Device type

0 TAC Xenta 401
1 M1 TAC Xenta 422
2 M2 TAC Xenta 422
3 M3 TAC Xenta 452
4 M4 TAC Xenta 452
5 M5 TAC Xenta 451
Program Specification
We will also give the application a name and an abbreviation to be used
in the menus of an Operator Panel (OP).
3 Use Program specification under the Options menu and enter the
name RTU4 in the Name: box. Also use RTU4 also for the abbre-
viation and enter RTU4 in the ABBR: box.
38 (450) TAC AB, Nov 2006

04-00030-01-en
For this application we will use the default cycle time of 1000 ms.
4 Check that the Cycle Time: box contains the value 1000.
For this application, we will use a number of blocks representing
SNVTs so we will make sure two boxes are checked.
5 Make sure that the following two boxes are checked.
• XIF-Header generated according to LonMark standard.
• Add new network variables (SNVT) last in the XIF file.
6 Right-click and select Comment ... to create a comment contain-
ing information on the name of the application, the author, perhaps
the version number and the most recent revision date. Frame the
comment by right-clicking and selecting Rectangle ... Locate the
comment in the upper left corner of the FBD diagram, thus making
it the first thing to appear each time the application is opened.
In the Public Signal Table, we will be able to see all signals made pub-
lic during the programming. These are the signals that can be seen in a
Vista and also signals that can be used in an OP menu tree design.
TAC AB, Nov 2006 39 (450)

04-00030-01-en
4.4 The Zone Bypass state

4.4.1 Designing the FBD
One of the conditions for the AHU to run is that at least one terminal
unit is in occupancy mode. Our solution is to use six function blocks of
the analog input type, representing the terminal units. The signals are
obtained via the LonWorks Network. The combined result, performed
by a expression block, is used as one of the starting conditions for an
AHU.
The value of each input block will also be used as condition when gen-
erating differences between temperatures and setpoints. They will be
used in a later part.
The occupancy sensors used here will have the value 2 when in occu-
pancy mode.
This part of a function block diagram (FBD) will use one printable page
on the screen.
We will make the function blocks on this FBD printable page a set of
signals in a common module called Term_Units.
We will locate, in the left part of the FBD, on top of each other, six func-
tion blocks of the AI type.
Locating the Inputs and Outputs
It is often appropriate to start by locating the blocks that represent phys-
ical I/O for a design, or a part of it, on the printable part of the FBD.
Blocks for calculation and logics will then be located between the I/O
blocks.
Note
Use the Online help or read Chapter 8, “Edit Mode” to learn more
about how to work in the Edit Mode of Menta.
1 Locate in the diagram window, VAV_4:1_Occ_Status, a function

block of the AI type, in the upper left part (corner). Then define
the block.
Identifier VAV_4:1_Occ_Status
Unit
Description From FPB-4:1 Software
Public Yes
R/W (Acc.)
Backup No
Bound to SNVT
Type occupancy
40 (450) TAC AB, Nov 2006

04-00030-01-en
Member
Name occupancy nvi4:1_Occ_Stat
Initial Value = 0
Poll No
Period: 60
Note
Use the Online help or read Section 14.3, “AI – Analog Input”to learn
more about the AI block.
2 Locate in the diagram window five more AI function blocks:

VAV_4:2_Occ_Status, VAV_4:3_Occ_Status,
VAV_4:4_Occ_Status, VAV_4:5_Occ_Status, and
VAV_4:6_Occ_Status.
A convenient way to work is to use Edit/Copy followed by Edit/
Paste and make the five duplicates of the block. The duplicates are
complete copies, that is they have exactly the same names and
parameters. Some of these properties must be redefined. The
tables below only show the parameters that differs from block to
block.
Description From FPB-4:2 Hardware
Type occupancy
Member
Description From FPB-4:3 Rio Grande
Type occupancy
Member
Description From FPB-4:4 R&D Services
Type occupancy
Member
Description From FPB-4:5 Software Dev.
Type occupancy
Member
TAC AB, Nov 2006 41 (450)

04-00030-01-en
Description From FPB-4:6 ASG
Type occupancy
Member
A zone is in occupancy mode when the value of the input (SNVT) is 2.

To detect if one (or more) units is running in occupancy mode, we use
an expression block. An XPB expression block with the expression
A=2|B=2|C=2|D=2|E=2|F=2, will do the combined logic to give the
block the logical value 1 (true) if any of the six inputs contain a value of
2. In the XPB block, this expression will form a block containing six
analog inputs, A, B, C, D, E, and F, where the inputs represent six state
inputs.
3 Locate in the diagram window, VAV_Bypass, an XPB expression
block in the middle of the page. Then define the block and enter
the expression A=2|B=2|C=2|D=2|E=2|F=2.
Identifier VAV_Bypass
Unit Auto/Bypass
Description Any Terminal Unit in Bypass
Public Yes
R/W (Acc.)
Type Binary
Expression A=2|B=2|C=2|D=2|E=2|F=2
Note
Use the Online help or read Chapter 15, “Expressions” to learn more
about the EXPRESSION blocks.
4 Connect the output of VAV_4:1_Occ_Status to input A of the XPB

block.
5 Connect the output of VAV_4:2_Occ_Status to input B of the XPB
block.
6 Connect the output of VAV_4:3_Occ_Status to input C of the XPB
block.
7 Connect the output of VAV_4:4_Occ_Status to input D of the XPB
block.
8 Connect the output of VAV_4:5_Occ_Status to input E of the XPB
block.
9 Connect the output of VAV_4:6_Occ_Status to input F of the XPB
block.
The output of the XPB block will be connected later.
42 (450) TAC AB, Nov 2006

04-00030-01-en
Assigning the Module Name "Term_Units"

These 7 function blocks are a subset of a module we want to call
Term_Units.
10 Mark all blocks on the FBD page, Right-click and click Module.
Enter Term_Units in the Module Name: box and then click OK
to assign the module name Term_Units to the blocks.
This will give the module name, in this case "Term_Units", as the first
part of the signal name (block name) separated by a \ (backslash). The
module part of the name will also be shown in the block symbols.The
block type, for a block in a module, will be underlined and in purple
color.
The first part of our FBD design should now look something like this:
Rearranging the layout

If you are not satisfied with the layout, you can always mark a block or
a group of blocks and move them, keeping the left button depressed.
When the route of a connection line needs to be changed, you can mark
a corner and re-position it in the same manner.
4.4.2 Simulating the Design

To test this part of the design, using the simulation mode in Menta will
mostly be a test of the expression block. In a running installation, there
will be other factors such as errors made when naming the SNVT vari-
ables, etc. The application must be tested in an operational network..
1 Enter the simulation mode of Menta, Options/Simulate (F12)
This will display the FBD in the simulation window and the five analog
inputs will be represented by buttons in the left part. The text shown on
TAC AB, Nov 2006 43 (450)

04-00030-01-en
each button is brief, the full name being shown on the status bar down
to the left.
Clicking any of the buttons to the left will open a dialog where you can
enter a value.
Since there is no point in following the values on the logger area, we
can click and press the separator and move it to the right. Alternatively,
you can double-click the separator to make it horizontal..
2 Click execute and observe the state (the gray field close to the out-
put) of the VAV_Bypass block (the XPB block). It should remain 0
(off) as all inputs are 0 (zero).
3 Click a button and enter a value of 1 followed by return (or click
outside the box). No change of the XPB block state is expected.
4 Repeat the procedure but enter a value of 2. The XPB block should
now show a state of 1 (On).
5 Enter a value of 3 and confirm that the state of the XPB returns to
0 (zero). Enter values for the other inputs, the XPB should remain
at 1 as long as at least one input has a value of 2.
44 (450) TAC AB, Nov 2006

04-00030-01-en
4.5 Starting and Stopping the VAV AHU Fan

In this part, we will design the part of the FBD which handles the Start-
ing/Stopping of the VAV AHU. In addition to this, we will also provide
the logic for a signal indicating the Occupancy Command which is sent
to the terminal units using a SNVT.
From the functional description, we find that the unit is started under the
following conditions:
• Based on a time schedule
• Any terminal unit in bypass mode.
• Timed Override via manual command.
• Manually overridden by operator Auto, Off, or Manual.
• Proofing function, latches the start upon error in fan state.
• Start delayed after a power restore.
We will create the design by forming groups of function blocks for spe-
cific mechanisms. These mechanisms are: TimedOverride, Time
Scheduling, Manual Override, Proofing Function, Delayed Startup, and
Manual Alarm.
This part of the function block diagram (FBD) will use one printable
page on the screen.
signals in a common module called SFan.
It is often appropriate to start by placing the blocks that represent the
physical I/O for a design, or a part of it, on the printable part of the FBD.
Blocks for calculation and logics will then be placed between the I/O
blocks.
1 Locate in the diagram window, SFan_Status, a DI type function
block in the upper left part of the printable page. Then define the
block.
Identifier SFan_Status
Unit
Description Supply Fan Status from VFD
Public Yes
R/W (Acc.)
Backup NO
Bound to Physical input
Mod Number M1
TAC AB, Nov 2006 45 (450)

04-00030-01-en
Term. Ref X1
Initial Value = Off
Normally Open = 1
Note
Use the Online help or read Section 14.14, “DI – Digital Input” to
learn more about the DI block.
2 Locate in the diagram window, Fan_Time_Schedule, a TSCH

type block, to the left, approximately one third of the way up from
the bottom. Then define the block.
Identifier Fan_Time_Sched
Unit
Description Fan Start Stop Time Schedule
Public Yes
R/W (Acc.)
Backup
Max Week Charts 4
Chart 1 Start 07:00
Chart 1 Stop 18:00
Chart 1 Weekdays MTWTF__
Max Holiday Charts 7
Holiday Chart 1 2002/5/27
Start Date
Stop date
Holiday Chart 1 00:00
Start Time
Stop Time
Holiday Chart 1 MTWTFSS
1Weekdays
Start Date
Stop date
Start Time
Stop Time
1Weekdays
Start Date
46 (450) TAC AB, Nov 2006

04-00030-01-en

Stop date
Start Time
Stop Time
1Weekdays
Start Date
Stop date
Start Time
Stop Time
1Weekdays
Start Date
Stop date
Start Time
Stop Time
1Weekdays
Note
Use the Online help or read Section 14.56, “TSCH – Time Schedule”
to learn more about the TSCH block.
3 Locate in the diagram window, SFan_MC to the left, and above

the TSCH block. Here we use a block of the PVI type for the oper-
ator to enter a numerical value representing the manual command.
Then define the block.
Identifier SFan_MC
Unit -1/0/1/2
Description Manual control
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue = -1
TAC AB, Nov 2006 47 (450)

04-00030-01-en
Note
Use the Online help or read Section 14.41, “PVI – Integer Value
Parameter” to learn more about the PVI block.
4 Locate in the diagram window a function block of ERR type to

the left and below the TSCH block.
Note
Use the Online help or read Section 14.18, “ERR – System Error”" to
learn more about the ERR block.
5 Locate in the diagram window, SFan_Start_Stop, a DO type

function block, to the right and approximately vertically in the
middle block. Then define the block.
Identifier SFan_Start_Stop
Unit -1/0/1/2
Description Supply Fan Start Stop Circuit
Public Yes
R/W (Acc.) RO
Backup
Bound to Physical output (Digital output)
Mod Number M1
Term. Ref K1
Initial Value = Off
Normally Open = 1
Note
Use the Online help or read Section 14.15, “DO – Digital Output” to
learn more about the DO block.
6 Locate in the diagram window, Term_Unit_Occ_Cmd, an AO

type function block, to the right and below the Sfan_Start_Stop
block. Then define the block.
Identifier Term_Unit_Occ_Cmd
Unit Occu/Unoc
Description Occupancy Command to Terminal Units
Public Yes
R/W (Acc.)
Backup
Bound to SNVT
48 (450) TAC AB, Nov 2006

04-00030-01-en
Type occupancy
Member
Name occupancy nvoVAV_Occ
Initial Value = 1
Send Yes
Delta: 0.5
Period: 60
Note
Use the Online help or read Section 14.6, “AO – Analog Output” to
learn more about the AO block.
Alarm when Manually Overridden.

he function block SFan_MC is the input variable for the operator's com-
mand. Giving the block a value of -1, 0, or 1 defines the Auto, Off and
Hand modes. When ordered to Off or Hand, there must be an alarm.
These two modes represent a value of the block that is larger (absolute
measurement) than -1. We use an expression block to decode the value
and transform it into a logic state. The expression A >-0.5, used in an
expression block with a boolean output (XPB), will create a block with
one input A.
7 Locate an XPB expression block in the diagram window, to the
right of the SFan_MC block (DI). Then define the block and enter
the expression A>-0.5
Identifier (Name)
Unit
Description
Public
R/W (Acc.)
Type Real/Integer/Binary
Expression A>-0.5
8 Connect the output of the SFan_MC block to the input of the XPB
expression block.
The alarm will be generated by an ALARM function block.
9 Locate SFan_MO, which is an ALARM type block, in the dia-
gram window, to the right of the XPB block. Then define the
block.
Identifier SFan_MO
Unit Normal/Alarm
Description Controlled manually
Public
TAC AB, Nov 2006 49 (450)

04-00030-01-en
R/W (Acc.)
Backup
Delay On 30
Delay Off 5
Priority 3
OP Alarm text Manual operation
Alarm Processing
Vista Alarm tripped Unit controlled manually
Vista Alarm reset Unit controlled manually
Note
Use the Online help or read Section 14.4, “ALARM – Alarm” to learn
more about the ALARM block.
10 Connect the output of the XPB block to the input of the SFan_MO
alarm block.
Time scheduled command
TSCH Fan_Time_Sched has a value which is either positive or nega-
tive, depending on whether or not the actual time lies within the defined
start and stop period(s). A standard way of decoding this is to use the
expression A<0 in an expression block of the XPB type.
11 Locate in the diagram window an XPB expression block, to the
right of the TSCH block Fan_Time_Sched.Then define the block
and enter the expression A<0.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<0
12 Connect the output of the TSCH block to the input of the XPB
block.
Combining the Scheduled Start and Manual Mode
We want the Scheduled start to be logically combined with the opera-
tor's manual command mode. In this case, we use the two signals as
inputs to an expression block with a Boolean (logical) output, XPB type
block. We use the expression A<-0.5?b:A. This expression will create a
block with two inputs, A and b. Input A is an analog input and will be
connected to the PVI block SFan_MC. Input b is a logical input and we
use our decoded time schedule value by connecting the XPB block here.
50 (450) TAC AB, Nov 2006

04-00030-01-en
13 Locate in the diagram window an XPB expression block with the

expression A<-0.5?b:A, to the lower right of the SFan_MO Alarm
block.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<-0.5?b:A
14 Connect the output of the XPB block decoding the time schedule
block to input b of the XPB block.
For input a we use the output of the PVI block SFan_MC.
15 Create a new node from the connection to the subsequent XPR
block and connect the new node to input A.
Delayed Start after Power Restore
It is specified that the unit is to have a start delay following a power
restore, if this occurs. To provide for this, we use a function block called
ERR. This function block has a numerical value that is dependent on the
type(s) of system error(s) within the Xenta device. In our case, we are
interested in the error that occurs after a power restore, i.e. the block will
have a value of 1, or an odd value if there are more alarms. We decode
this using the expression A&1, in an expression block giving a logical
output, i.e. a block of the XPB type.
16 Locate in the diagram window an ERR block, below the TSH
block.
right of the ERR block. Enter the expression A&1.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A&1
The desired delay is done using a function block called DELAY.
TAC AB, Nov 2006 51 (450)

04-00030-01-en
18 Locate in the diagram window a DELAY function block, to the

right of the XPB expression block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Delay On 0
Delay Off 20
Note
Use the Online help or read Section 14.10, “DELAY – Delayed On/
Off” to learn more about the DELAY block.
The design created so far will give an output from the delay block that
is 1 (true) for 20 seconds after a power restore, otherwise 0 (false). For
our function, we require a signal that is normally 1 and 0 only following
a restart. We solve this by inverting the signal from the DELAY block.
19 Locate in the diagram window a NOT function block, to the right
of the DELAY block.
Note
Use the Online help or read Section 14.30, “NOT – NOT Gate” to
learn more about the NOT block.
20 Connect the output of the ERR block to the input of the XPB
block.
21 Connect the output of the XPB block to the input of the DELAY
block.
22 Connect the output of the DELAY block to the input of the NOT
block.
Combining Scheduled/Manual Start and Delayed Start
Now we have the logical signal representing the combined start as well
as the logical signal representing the delayed start. We combine these
using a function block of the AND type.
52 (450) TAC AB, Nov 2006

04-00030-01-en
23 Locate in the diagram window an AND function block, to the right

of the XPB block combining the manual command and time
schedule command.
Note
Use the Online help or read Section 14.5, “AND – Logical AND Gate”
to learn more about the AND block.
24 Connect the output of the XPB block to the upper input of the
AND function block.
25 Connect the output of the NOT block (after the DELAY block) to
the lower input of the AND function block.
Our design should now look like this:
Designing TimedOverride
The command for having a run, controlled by a timer, is executed by set-
ting the variable TimedOverride to 1 (one).
The function block we use for the operator’s input is a DELB, a function
block that delays a logical state of program cycle.
26 Locate the TimedOverride, which is a DELB function block, in
the diagram window in the lower part of the FBD diagram area,
slightly to the left. Then define the block..
Identifier TimedOverride
Unit
Description Override Time Command
Public Yes
TAC AB, Nov 2006 53 (450)

04-00030-01-en
R/W (Acc.) RO
Backup Yes
Init Value 0
Note
Use the Online help or read Section 14.11, “DELB – Binary Value
Delay” to learn more about the DELB block.
When the operator enters state 1 for the block, this will only last for one
second so we will have to detect this operation. We use a function block
called TRIG for this. When this block is defined to operate in mode 0,
it will be true on the transition from zero to one [of the input].
27 Locate in the diagram window a TRIG function block, to the right
of the DELB TimedOverride block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Mode 0
Note
Use the Online help or read Section 14.55, “TRIG – Trigger” to learn
more about the TRIG block.
28 Connect the output of the DELB function block to the input of the
TRIG function block.
The adjustable timer period, the OverrideTime, is determined by a func-
tion block of the PVR type.
54 (450) TAC AB, Nov 2006

04-00030-01-en
29 Locate the OverrideTime, which is a PVR function block, in the

diagram window, below the DELB block. Then define the block.
Identifier OverrideTime
Unit Minutes
Description Override Timer time
Public Yes
R/W (Acc.) RW
Backup
InitValue 120
Note
Use the Online help or read Section 14.42, “PVR – Real Value Param-
eter” to learn more about the PVR block.
Now we need a something to react to the input pulse(s) and also perform
a countdown calculation of the elapsed time.
Here we use an expression block with an analog output, XPR. An
expression like a?(D>0?0:B):D>0?D-(1/60):0 will give an XPR block
with three inputs, a, B, and D. Block a contains a binary input to which
we connect the command pulse. B is an analog input and the input to
which we connect the OverrideTime setting value. D is an analog input
to which we connect a value which is counted down during the timed
override.
30 Locate the Timer, which is an XPR expression block, in the
diagram window, to the right of the TRIG block. Then define
the block and enter the expression a?(D>0?0:B):D>0?D-(1/
60):0
Identifier Timer
Unit Minutes
Description Timer time remaining
Public Yes
R/W (Acc.)
Type Real
Expression a?(D>0?0:B):D>0?D-(1/60):0
31 Connect the output of the TRIG function block to input a of the

Timer (XPR) block.
32 Connect the output of the OverrideTime PVR function block to
input B of the Timer (XPR) block.
To allow the value of the XPR block to be fed back to input D,
we add a function block calld DELR to the feedback loop. The DELR
block also delays the value by one program execution.
TAC AB, Nov 2006 55 (450)

04-00030-01-en
33 Locate in the diagram window a DELR function block, to the left

of Timer (XPR) block. Then define the block.
Identifier
Unit
Description
Public No
R/W (Acc.)
Backup
InitValue 0
Note
Use the Online help or read Section 14.13, “DELR – Real Value
Delay” to learn more about the DELR block.
34 Connect the output of the DELR function block to input D of the

XPR expression block.
35 Connect the output of the Timer (XPR) block to the input of the
DELR function block.
Now we have a timer function which, during the timed period, will have
a value which counts down from the start value to zero. We transform
this value into a logical signal by comparing it with a value of zero. If
this value is greater than zero, we want a logical true result.
36 Locate in the diagram window a Greater than operator on the
FBD area, to the right of the Timer expression block. Then define
the block.
Note
Use the Online help or read Section 16.4, “Comparison” to learn more
about the Greater than block.
37 Locate a Real const operator in the diagram window in order to

provide a comparison value of zero, below the Greater than opera-
tor. Then define the block
Identifier
Unit
Description
Public
Mode 2
Value 0
56 (450) TAC AB, Nov 2006

04-00030-01-en
Note
Use the Online help or read to Section 16.1, “Constants” to learn more
about the Real const block.
38 Create a new node from the output of the XPR block and connect
it to the horizontal input of the Greater than operator.
39 Connect the output of the Real const operator to the vertical input
of the Greater than operator.
Combining TimedOverride, Timeschedule and Manual
Command
We can now combine this timer signal with the previously prepared sig-
nal. We do this using an OR function block.
40 Locate in the diagram window an OR function block, to the right
of the AND block combining error delay and time scheduled start.
Note
Use the Online help or read Section 14.32, “OR – OR Gate”to learn
more about the OR block.
41 Connect the output of the AND block to the upper input of the OR
function block.
42 Connect the output of the Greater than operator to the lower input
of the OR function block.
Our design so far will not handle the situation when the operator has
manually ordered the unit to be Off (the value of Sfan_MC is 0).
We will do this by introducing an expression block that detects a value
zero and transforms it into a logical state. We also require a signal for
the normal situation, i.e. when the manual command is something other
than zero in order to have a true state.
43 Locate in the diagram window an XPB expression block, above
both the AND block and the OR block. Then define the block and
enter the expression A=0.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A=0
TAC AB, Nov 2006 57 (450)

04-00030-01-en

of the XPB block.
45 Connect the output of the XPB block to the input of the NOT func-
tion block.
46 Create a new node from the signal SFan_MC (PVR) block. Con-
nect the signal to the input of the newly created XPR block.
Start, without Latching
We are now ready to make another logical combination of the start con-
ditions (signals) we have done so far. We will do this using an AND
function block.
of the most recently created OR block.
48 Connect the output of the OR function block to the lower input of
the AND function block.
49 Connect the output of the NOT function block to the upper input
of the AND function block.
The design for AHU Start Stop should now look like this:
Combining With the Bypass state

The previously designed logic does not include the starting request from
the terminal units. This is done using an OR function block.
50 Locate on the FBD area an OR function block, approximately one
third of the way from the top and one third of the way from the
left.
58 (450) TAC AB, Nov 2006

04-00030-01-en
51 Create a new node from the last AND function block output sig-
nal. Connect the signal to the lower input of the created OR func-
tion block.
52 Connect the output of the VAV_Bypass block to the upper input of
the OR block. The VAV_Bypass block is located on the FBD page,
to the left.
Designing the Proofing Function (latching).
The proofing function will prevent the unit from running and create an
alarm, if the Fan state indication is not received within 30 seconds.
The delay (and counting) is done using a DELAY function block.
The latching function is obtained using an SR function block together
with two TRIG function blocks, one connected to each input.
The first step is to arrange for the signal that is to be connected to the-
actual fan start/stop block. We combine the start signal with a fault sig-
nal in an AND block. This is done so that a start will only be ordered
when there are no faults.
53 Locate in the diagram window an AND function block on the FBD
area, to the right of our most recent OR block.
54 Locate in the diagram window a NOT function block, above the
AND function block.
55 Connect the output from the OR function block to the lower input
57 Locate again in the diagram window an AND function block, not
too close to, as well as to the right of, our last AND block.
58 Locate in the diagram window another NOT function block,
above the AND function block,
59 Connect the output from the AND function block to the left to the
lower input of the new AND function block.
61 Connect the output from the SFan_Status block (DI block) to the
input of the NOT function block.
62 Create a new node and connect the output from the left AND func-
tion block to the input of the Sfan_Start_Stop block (DO, located
to the right in the diagram).
TAC AB, Nov 2006 59 (450)

04-00030-01-en
63 Locate in the diagram window a DELAY function block, to the

right of the AND function block, of the DELAY type. Then define
the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Delay On 30
Delay Off 0
64 Connect the output from the AND function block to the input of
the DELAY function block.
65 Locate in the diagram window a TRIG function block, to the right
of the DELAY function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Mode 1
66 Connect the output from the DELAY function block to the input of
the TRIG function block.
67 Locate in the diagram window an SR type block, to the right of the
TRIG function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
InitValue 0
Note
Use the Online help or read Section 14.51, “SR – Set-Reset Flip-Flop”
to learn more about the SR block.
68 Connect the output from the TRIG function block to input s of the
SR function block.
60 (450) TAC AB, Nov 2006

04-00030-01-en
69 Locate in the diagram window another TRIG function block,

below the previous TRIG function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Mode 1
70 Connect the output from this TRIG function block to input r of the
SR function block.
71 Locate in the diagram window a NOT function block, to the left of
the lower TRIG function block.
72 Connect the output from the NOT function block to the input of
the lower TRIG function block.
73 Connect the output from the left OR function block to the input of
the NOT function block.
74 Locate SFan_Alarm, an ALARM type function block in the dia-
gram window, to the right of but not too close to the SR function
Identifier SFan_Alarm
Unit Normal/Alarm
Description SFan Status Alarm
Public
R/W (Acc.) RO
Backup
Delay On 2
Delay Off 0
Priority 1
OP Alarm text SFan Alarm
Alarm Processing
Vista Alarm tripped SFan Status Alarm 2nd Floor South
Vista Alarm reset SFan Status Alarm 2nd Floor South Return to
normal
75 Create a new node and connect the output from the SR function
block to the input of the leftmost NOT function block.
TAC AB, Nov 2006 61 (450)

04-00030-01-en
This part of our design should now look like this:
Designing the Hand Alarm

The specification also calls for an alarm, SFAN_Hand_Alarm, if the
SFan is running without the SFan_Start_Stop relay being energized
(true). This is accomplished by logically combining a state indication
which is true with an SFan Start_Stop signal which is false. An AND
function block combines them.
76 Locate SFAN_Hand_Alarm, an ALARM type function block, in
the diagram window, to the right of, but not too close to, the previ-
ous ALARM block. Leave space for additional blocks located to
the left. Then define the block..
Identifier SFAN_Hand_Alarm
Unit Normal/Alarm
Description Hand control supply air fan
Public
R/W (Acc.)
Backup
Delay On 20
Delay Off 0
Priority 3
OP Alarm text SFan Manually-operated
Alarm Processing
Vista Alarm tripped Hand control supply air fan, the unit serves 2nd
Floor South
Vista Alarm reset Hand control supply air fan, the unit serves 2nd
Floor South
77 Locate in the diagram window an AND function block. to the left

of our most recent ALARM block.
62 (450) TAC AB, Nov 2006

04-00030-01-en
78 Connect the output from the AND function block to the input of
the ALARM function block.
79 Create a new node and Connect the output from the SFan_Status
function block (DI, located to the left in the diagram) to the upper
input of the AND function block.
For the other input to the AND block, we want a logical true when the
control signal is false. We have to invert the signal.
80 Locate in the diagram window a NOT function block, below the
AND function block,
81 Connect the output of the NOT function block to the lower input
82 Create a new node on the connection to the SFAn_Start_Stop
function block (DO, located to the right in the diagram), and con-
nect it to the input of the NOT function block.
Designing the Terminal Occupancy Command signal
The occupancy command is the result of two signals, the
SFan_Start_Stop and the complete time schedule result (including
TimedOverride and manual override).
of the Term_Unit_Occ_Cmd block (AO, located on the right of the
page). Leave ample space between the blocks, as we are going to
put more blocks in between them.
84 Create a new node and connect the signal connected to the
SFAn_Start_Stop function block (DO, located to the right of the
diagram) to the upper input of the AND function block.
85 Create a new node and connect the signal from the AND function
block, representing the complete time schedule result, tothe lower
input of the AND function block.
87 Connect the output of the AND function block to the input of the
NOT function block.
The signal (output) from the NOT function block is a Boolean state
(true/false). We want to connect it to our Term_Unit_Occ_Cmd func-
tion block, which is of the analog type. A connection like this is not
allowed in Menta, so we will have to change the type of the output sig-
nal.
88 Locate in the diagram window an D/A converter operator, to the
right of the NOT function block.
TAC AB, Nov 2006 63 (450)

04-00030-01-en
Note
Use the Online help or read Section 16.6, “Others” to learn more about
the D/A converter block.
89 Connect the output of the NOT function block to the input of the
D/A converter function block.
90 Connect the output of the D/A converter operator block to the
input of the Term_Unit_Occ_Cmd (AO function block).
Assigning Module Name "Sfan"
The function blocks on this FBD printable page are a set of signals we
want to treat as signals in a common module called SFan.
91 Mark all blocks on the FBD page and assign them the module
name SFan.
When finished, this page should look like this:

1 Enter the simulation mode of Menta, Options/Simulate (F12). If
necessary, use the Zoom/Zoom out a couple of times to see most
of the printable page.
This will open the FBD in the simulation window and the five analog
inputs, together with the Fan state input as buttons in the left part. The
64 (450) TAC AB, Nov 2006

04-00030-01-en
text shown on each button is brief, the full name is shown on the state
bar down to the left.
To fully open the window to show the FBD, we can click and press the
separator of the logger window and move the separator toward the right.
Start of Testing when a Zone is in Bypass
The unit must start when one Zone or more is in bypass. We arrange this
the same way we did during our first test.
2 Click any Term_Units.... button and enter a value of 2 followed
by return (or click outside the box).
3 Click the Step button and observe the state of the OR function
block in front of the SFan_Alarm line. It should be 1 (on). Also
observe the DO block called SFan_Start_Stop. It should also be 1
(on).
Testing the Sfan_Alarm
Testing that an alarm is generated and latching when the Sfan_Status
signal is not received can be done as follows.
4 Click execute and observe the value/state of the ALARM block. in
the gray field close to the output. It should be 1 (on) and the DO
block SFan_Start_Stop should be 0 (off) after a short period.
Alternatively you can Click the Step button 33 times, givning con-
trol over the delay before the alarm.
5 Click the SFan\SFan_Status button to the left to simulate the
indication and observe the state of the ALARM block. If you pre-
viously used the step button, be sure to step again.
There will still be an alarm condition. The alarm will not be restored
until the order to start is restored to zero.
6 Click the same Term_Units.... button as before and enter a value
of 0 and observe the state of the ALARM block. If you previously
used the step button, be sure to step again. The alarm should now
have been restored.
Testing SFan_Hand_Alarm
Testing SFan_Hand_Alarm can be done as follows.
7 Click RST with all Term_Units...buttons 0 while keeping the
SFan\SFan_Status button depressed. The cycle counter will be
restored to 0.
8 Click the Step button 21 times and observe the value/state of the
ALARM block. It should be 1 (on) after being stepped.
9 Release the SFan\SFan_Status button and Step again. The alarm
should be restored immediately.
TAC AB, Nov 2006 65 (450)

04-00030-01-en
Testing the scheduled start.

To adjust a value from the time schedule, TSCH block will give an order
to run; one convenient way is to adjust the Simulator's Real Time Clock
using the command Options/Set Date and Time... This will only change
the time in the Simulator. The clock function in the PC will not be
affected.
10 Use the command Options/Set Date and Time ... and enter a time
within the defined period 07:00 18:00. Make sure the weekday is
not Saturday or Sunday.
11 Click Step (or Execute) and observe the TSCH block. It should
have a value less than zero (negative) and the subsequent XPB
block will be 1 (on). The DO block SFan_Start_Stop should be 1
(on).
Testing the Timed Override
12 Click RST, the upper right corner with all Term_Units...buttons 0
while keeping the SFan\SFan_Status button depressed. The cycle
counter will be restored to 0 and the simulator Real Time Clock
will be reset to the startup values.
13 Make sure all the Term_Units.... button have a value of 0.
14 Click the SFan\SFan_Status button to eliminate the alarm and
the latching.
15 For testing purposes, we temporarily modify the contents of the
OverrideTime (PVR). Click the block to display the MODIFY
form. Change the value to 5.
16 Click the Sfan_Timed_Override block (DELB) to display the
ORDER form and check the radio button State to initiate the over-
ride.
17 Click execute and observe the DO block SFan_Start_Stop. It
should be 1 (on). Also observe the value/state of the Timer block
(the XPR block). It should be counting down from 5 to 0 (zero).
When the value reaches zero the SFan_Start_Stop should go to 0
(off).
Verifying that a Timed Override can be aborted can be done as follows.
18 Repeat the procedure by clicking the Sfan_Timed_Override
block (DELB) and checking the radio button State. Click
Sfan_Timed_Override again, before the XPR block has counted
down, and check that the SFan_Start_Stop immediately goes to 0
(off).
Testing the Hand mode.
Until now, we have used the SFan_MC block with -1, entailing auto-
matic operation. Testing the manual Hand mode can be done as follows.
66 (450) TAC AB, Nov 2006

04-00030-01-en
19 Click the Sfan_Status button to eliminate the alrm and the latch-
ing.
20 Click the Click the SFan_MC block to display the MODIFY
menu. Enter a value of +1 to order the Hand mode.
21 Click Step (or Execute) and observe the DO SFan_Start_Stop
block. It should be 1 (on) immediately. Also observe the
Sfan_Hand ALARM. It should be 1 (on) after 30 execution inter-
vals.
22 Click the SFan_MC block to display the MODIFY menu. Enter a
value of -1 to order Auto mode again. Observe the DO
SFan_Start_Stop block, it should return to 0 (off) immediately.
The Sfan_Hand ALARM should be restored to 0 (off) after 5 exe-
cution intervals.
Testing the Off mode.
23 Keep the SFan\SFan_Status button depressed to eliminate the
alarm and the latching.
value of 0 to order Off mode.
block. It should be 0 (off). Also observe the Sfan_Hand ALARM.
It should be 1 (on) after 30 execution intervals.
26 Use the command Options/Set Date and Time ... and enter a time
block. It should remain 0 (off).
28 Click any Term_Units.... button and enter a value of 2. Observe
the Testing the Terminal unit Occupancy command.
Testing this via simulation only entails checking the generation and the
value of the signal.
restored to 0 and the simulator Real Time Clock will be reset to the
startup values.
31 Click Step (or Execute) and observe the value of the
Term_Unit_Occ_Cmd block (the AO block). It should be 1 (on).
32 Use the command Options/Set Date and Time... and enter a time
TAC AB, Nov 2006 67 (450)

04-00030-01-en
33 Click Step (or Execute) and observe the Term_Unit_Occ_Cmd

block (the AO block) again. It should now be 0 (off).
Repeate the procedure with Term_Units occupied.
restored to 0 and the simulator Real Time Clock will be reset to the
startup values.
Term_Unit_Occ_Cmd block (the AO block) again. It should now
be 1 (on).
37 Click any Term_Units.... button and enter a value of 2. Observe
the value of the Term_Unit_Occ_Cmd block (the AO block). It
should be 1 (on).
Repeate the procedure in Hand Mode
restored to 0 and the simulator Real Time Clock will be reset to
thestartup values.
Term_Unit_Occ_Cmd block (the AO block). It should be 1 (on).
value of +1 to order Hand mode. Observe the value of the
Term_Unit_Occ_Cmd block (the AO block). It should be 0 (off).
Testing the delayed start after a power restore
In Simulator mode, we cannot simulate the value of the ERROR block.
Testing the delay after a power restore can only be tested when the
application software has been downloaded to a Xenta device. To test the
logic, you can temporarily replace the ERROR block with another
block, that is a PVI block and assign a value of 1 temporarily.
68 (450) TAC AB, Nov 2006

04-00030-01-en
4.6 The VAV AHU Fan VSD Control

In this part, we will design the control of the supply air pressure using a
VSD device. Control is based on the supply air static pressure measure-
ment. We will also arrange for alarms when the sensor is failing or when
communication with an important I/O module has been lost.
We can identify some mechanisms, forming groups of function blocks
like:
• Alarm when Static Pressure is Out of Range
• Alarm when Module is Offline
• Sample Rate Generator for Control
• Control Algorithm
• Interval Timer for startup
We will implement the design by forming groups of function blocks for
the identified mechanisms. These mechanisms are: Alarm on sensor
failure, Alarm when module is offline, Sample rate generator, Control
algorithm, Startup interval timer.
page on the screen.
signals in a common module called VSD.
1 Locate Mod3, a DI type function block, in the diagram window,
in the upper left part of the screen. Then define the block.
Identifier Mod3
Unit Offline/Online
Description I/O Module 3 Communication Status
Public Yes
R/W (Acc.) RO
Backup NO
Bound to Online Device
Device Address 3
Initial Value = Off
2 Locate in the diagram window the Static_Press_Sensor, an AI

type block, to the left, approximately vertically midways. Then
define the block.
Identifier Static_Press_Sensor
TAC AB, Nov 2006 69 (450)

04-00030-01-en
Unit "wc
Description
Public No
R/W (Acc.)
Backup
Bound to Linear Analog Input
Mod Number M3
Terminal ref. U1
Sensor Sensor=2..10V
Time Const: 0
Initial Value: 0
Min Value: 0
Max. Value: 5
3 Locate the VSD, an AO type function block, in the diagram win-

dow, to the right of the FBD page and approximately vertically in
the middle block. Then define the block.
Identifier VSD
Unit
Description VSD AO
Public Yes
R/W (Acc.)
Backup
Bound to Physical output
Type
Mod Number M3
Terminal ref: Y1
Initial Value = 0
Voltage 0% 0
Voltage 100% 10
Alarm when Static Pressure experiences Sensor Failure

We need the possibility to calibrate the static pressure measurement. To
achieve this, we add an adjustable offset value and use the totalled
value.
4 Locate Static_Press_Offset, a PVR type function block, in the
diaram window, below the Static_Press_Sensor block (AI block).
Then define the block..
Identifier Static_Press_Offset
Unit "wc
Description Offset for Calibration of Static Press
70 (450) TAC AB, Nov 2006

04-00030-01-en
Public
R/W (Acc.) RW
Backup
InitValue 0
5 Locate Static_Pressure, an Addition operator, in the diagram

window, to the right and midways between the AI and PVI func-
tion blocks. Then define the block. Select Mode 2 for this opera-
tor, arranging both inputs vertically.
Identifier Static_Pressure
Unit "wc
Description Supply Air Static Pressure
Public Yes
Mode 2 Yes
Note
Use the Online help or read Section 16.3, “Math Operators” to learn
more about the Addition block.
6 Connect the output of the Static_Press_Sensor to the upper input

of the Addition operator.
7 Connect the output of the Static_Press_Offset to the lower input of
the Addition operator.
Now we want to trigger an alarm when the value is out of range. This is
done, using an expression in an expression block of XPB type. The
allowed limits are figures in the expression, adapted to the measuring
range of the input. The advantage of this method is that it is hard to
manipulate the allowed levels. The disadvantage is, of course, that you
will have to reprogram and download the application to use new values.
right and slightly above the Addition operator. Then define the
block and enter the expression A<-0.1|A>5.0.
9 Connect the output of the Static_Pressure block (the Addition
operator) to the input of the XPB block.
10 Locate in the diagram window, Duct_Static_SF, an ALARM
function block, to the right of the XPB block. Then define the
block.
Identifier Duct_Static_SF
Unit Normal/Alarm
Description Sensor failure Duct Static sensor
Public
R/W (Acc.)
TAC AB, Nov 2006 71 (450)

04-00030-01-en
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Sensor failure Duct Static
Alarm Processing
Vista Alarm tripped Sensor failure Duct Static sensor
Vista Alarm reset Sensor failure Duct Static sensor return to nor-
mal
11 Connect the output of the XPB block to the input of the

Duct_Static_SF (ALARM) block.
The output of the ALARM block will be connected later.
Alarm when Module Offline
The Mod3 digital input block is designed to monitor communication
with I/O module 3, and is false when this I/O module is Offline. After
inverting the signal from the block, we want the alarm to trigger when
communication is lost. We connect the signal to an ALARM block.
of the Mod3 digital input block.
13 Connect the signal from the Mod3 digital input block to the input
of the NOT function block.
14 Locate Mod_3_Offline, an ALARM function block, in the dia-
gram window, to the right of the Mod3 digital input block. Then
define the block..
Identifier Mod_3_Offline
Unit Normal/Alarm
Description Module 3 Loss comm alarm
Public
R/W (Acc.)
Backup
Delay On 60
Delay Off 0
Priority 9
OP Alarm text MOD3_ALARM
Alarm Processing
Vista Alarm tripped MOD3 Loss Comm Alarm
Vista Alarm reset MOD3 Comm Return to Normal
15 Connect the signal from the NOT function block to the

Mod_3_Offline (Alarm) block.
72 (450) TAC AB, Nov 2006

04-00030-01-en
Our design of this page should now look like this:
Sample Rate Generator for Control

For control purposes, we will use a sample rate generator and we are
now going to start designing this. We will use a PULSE function block,
together with a PVR function block containing the sampling rate.
Locate in the diagram window, somewhere to the left and below the
midline, the following. If necessary, we can adjust the position of these
blocks later.
16 Locate in the diagram window a PULSE function block. Place the
block slightly below the Duct_Static_SF block.
Note
Use the Online help or read Section 14.39, “PULSE – Pulse Genera-
tor” to learn more about the PULSE block.
17 Locate in the diagram window a DELB type function block, to the

left of the PULSE block .
Identifier
Unit
Description
Public No
R/W (Acc.) RO
TAC AB, Nov 2006 73 (450)

04-00030-01-en
Backup No
Init Value 1
18 Connect the output of the DELB block to input t (the trigger input)
of the PULSE function block.
The sample rate, that is the periods when control is calculated, is deter-
mined by the value of a PVR function block.
19 Locate Sample_Rate, a PVR type function block, in the diagram
window, to the left of the PULSE block and below the DELB
block. Then define the block..
Identifier Sample_Rate
Unit Seconds
Description Sample interval
Public No
R/W (Acc.) R/W
Backup No
InitValue 4
20 Connect the output of the Sample_Rate block to input pl (pulse

length) of the PULSE function block.
22 Connect the output of the PULSE block to the input of the NOT
function block.
DELB function block.
We will create a new node and connect the design later.
Control Algorithm
The conditional calculations of the control value are performed by an
expression block with a real (floating) type of output (XPR).
The expression a?c?(B>2*d?3*-F:B>D+E/2?-F:B<D-E/2?F:0)+G:G:0,
in this XPR block, will form a block containing seven inputs:
• a, a binary input representing the Fan state.
• B, an analog input representing the actual Supply Air static pres-
sure
• c, a binary input representing the sample rate pulse.
• D, an analog input representing the setpoint for the Static Pressure.
• E, an analog input representing the deadBand.
• F, an analog input representing the Change per Scan.
• G, an analog input representing the previous control output value.
74 (450) TAC AB, Nov 2006

04-00030-01-en
Control is conditional upon Sfan Status (input a); if the status is off, the
control output signal will be 0 (zero).
During control, the control output is recalculated at each sample.
Between the samples the output signal is kept at the previous level
(input G).
For a deviation where the pressure is too high by more than twice the
level of the setpoint, the control output level will be decreased by a
value three times the Change per Scan.
This is expressed in the B>2*D?3*-F part of the algorithm.
For a deviation where the pressure is too high by over half the Dead-
band, the control output level will be decreased by a value equal to the
Change per Scan.
This is expressed in the B>D+E/2?-F part of the algorithm.
For a deviation where the pressure is too low by over half the Dead-
Band, the control output level will be increased by a value equal to the
Change per Scan (at present 2 %).
This is expressed in the B<D-E/2?F part of the algorithm.
The expression can be viewed like this:
a? ;Fan Status on?
c? ;if sampled
(B>2*D? ;if pressure more than twice the SP
3*-F: ;subtract three times the bump amount
B>D+E/2? ;if pressure more than half the deadband above the SP
-F: ;subtract the bump amount
B<D-E/2? ;if pressure less than half the deadband below the SP
F: ;add the bump amount
0) ;pressure is within the deadBand, add zero.
+G: ;when sampled add previous value
G: ;not sampled, use previous value
0 ;Fan Status is off, use zero.
Actually, the expression can be written in a block like the above for bet-
ter readability. The result, however, will be a much vertically larger
symbol.
24 Locate in the diagram window an XPR expression block contain-
ing the above expression, horizontally approximately in the mid-
dle and vertically approx. one third from the bottom of the
TAC AB, Nov 2006 75 (450)

04-00030-01-en
printable page. Then define the block and enter the expression
a?c?(B>2*d?3*-F:B>D+E/2?-F:B<D-E/2?F:0)+G:G:0.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Real
Expression a?c?(B>2*d?3*-F:B>D+E/2?-F:B<D-E/
2?F:0)+G:G:0
The setpoint, the dead-band, and the change each scan for the control of
the discharge air pressure are determined by the value of three PVR
function blocks.
25 Locate DAP_SP, a PVR type function block in the diagram win-
dow, to the left of the XPR function block. Then define the block..
Identifier DAP_SP
Unit "wc
Description Setpoint discharge air pressure
Public Yes
R/W (Acc.) R/W
Backup Yes
InitValue 1
26 Connect the output of the DAP_SP function block to input D of

the XPR expression block.
27 Locate Dead_Band, a PVR type of function block, in the diagram
window, below and slightly to the left of the DAP_SP function
Identifier Dead_Band
Unit "wc
Description Dead Band Discharge Air Pressure
Public No
R/W (Acc.) R/W
Backup No
InitValue 0.2
28 Connect the output of the Dead_Band function block to input E of

76 (450) TAC AB, Nov 2006

04-00030-01-en
29 Locate Chg_Per_Scan, a PVR type function block, in the dia-

gram window, below and slightly to the right of the Dead_Band
function block. Then define the block.
Identifier Chg_Per_Scan
Unit %
Description % Speed change per scan
Public No
R/W (Acc.) R/W
Backup No
InitValue 2
30 Connect the output of the Chg_Per_Scan function block to input F

of the XPR expression block.
31 Create a new node and connect the signal from the NOT function
block (the output of the Sample rate generator) to input c of the
XPR function block
32 Create a new node and connect the signal from the Static_Pressure
(the Addition operator) to input B of the XPR function block.
To allow for a future feedback signal, we add a function block that has
Read/Write access. We can select different blocks, but here we have
chosen a DELR function block. The block will delay the signal by one
program cycle but this delay can be ignored in the application.
33 Locate in the diagram window a DELR type function block, to the
right of the XPR function block.
Identifier
Unit
Description
Public No
R/W (Acc.)
Backup Yes
InitValue 0
34 Connect the output of the XPR function block to the input of the
35 Locate in the diagram window a LIMIT type function block, to
the right of the DELR function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
TAC AB, Nov 2006 77 (450)

04-00030-01-en
MinValue = 0
MaxValue = 100
Note
Use the Online help or read Section 14.24, “LIMIT – High/Low Signal
Limit” to learn more about the LIMIT block.
36 Connect the output of the DELR function block to the input of the
LIMIT function block.
37 Create a new node and connect the signal from SFan_Status (the
DI in the AHU Fan Start Stop design, the FBD page to the left) to
input a of the XPR function block.
With the exception of the feedback signal, this concludes our design for
calculating the control signal value. It is either this value or a fixed value
that will be used by the application. Which one is used will depend on
the operating conditions..
We use a PVR function block to provide the fixed value.
38 Locate Startup_Value, a PVR type function block, in the diagram
window, above the LIMIT function block. Then define the block.
Identifier StartUp_Value
Unit
Description Value During Start Up
Public Yes
R/W (Acc.) RW
Backup Yes
InitValue 50
Choosing between the values of these two blocks is initially done using
an analog multiplexer as signal selector controlled by a binary signal.
39 Locate in the diagram window an Analog mux operator, to the
right of the LIMIT block and the Startup_Value block. Locate the
block midways.
Note
Use the Online help or read Section 16.6, “Others” to learn more about
the Analog mux block.
40 Connect the output of the Startup_Value (PVR) function block to

the upper horizontal input (1) of the Analog mux operator.
41 Connect the output of the LIMIT function block to the lower hori-
zontal input (0) of the Analog mux operator.
Now we have the feedback signal to connect to the XPR function block.
78 (450) TAC AB, Nov 2006

04-00030-01-en
42 Connect the output of the Analog mux operator block to input G of

Interval Timer for startup
The binary control signal to the analog mux operator is generated here
by a PULSE function block. The duration of the startup time is defined
in a PVB function block connected the PULSE block. The signal (pulse)
is generated once, every time the Fan state is true (1).
43 Locate in the diagram window a PULSE function block, above
and slightly to the right of the XPR function block.
44 Locate Startup_Time, a PVR type function block, in the diagram
window, to the left of the PULSE function block. Then define the
block.
Identifier StartUp_Time
Unit
Description Start Up Timer Time Period
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 300
45 Connect the output of the Startup_Time function block to input pl

46 Connect the output of the PULSE function block to the control
input of the Analog mux operator block (the vertical one).
47 Create a new node and connect the signal from SFan_Status (the
DI in the AHU Fan Start Stop design, the FBD page to the left) to
input t of the PULSE function block.
Control output upon Alarm condition.
The next decision threshold when determining which value to assign to
the analog output block is to react to whether or not there is a pressure
or a communication alarm. In the event of an alarm, we use the startup
value as the control signal level. We use another Analog mux operator
to do the signal selection.
48 Locate in the diagram window an Analog mux operator block, to
the right of the previous Analog mux block.
49 Create a new node and connect the signal from the Startup_Value
function block (the PVR block) to the upper horizontal input (1) of
the Analog mux operator.
50 Connect the output of the previous Analog mux (the Analog mux
to the left) to the lower horizontal input (0) of the Analog mux
operator.
TAC AB, Nov 2006 79 (450)

04-00030-01-en
51 Locate in the diagram window an OR function block, midways

and to the right of the Mod_3_Offline and the Duct_Static_SF
ALARM blocks.
52 Connect the output of the Mod_3_Offline function block to the
upper input of the OR function block.
53 Connect the output of the Duct_Static_SF function block to the
lower input of the OR function block.
54 Connect the output of the OR function block to the control input of
the Analog mux operator block (the vertical one).
Now we are ready to connect the control signal to the output block.
55 Connect the output of the rightmost Analog mux operator to input
of the VSD function block (AO).
Assigning the Module Name "VSD"

want to treat as signals in a common module called VSD.
name VSD.
Now that this is finished, the page of the function block diagram should
look like this:
80 (450) TAC AB, Nov 2006

04-00030-01-en

necessary, to see most of the printable page, use the Zoom/Zoom
out a couple of times
This will open the FBD in the simulation window as well as the five
analog inputs, together with the Sfan\Fan state input and two new but-
tons; VSD\Static_Press_Sensor and VSD\MOD3 in the left-hand part.
The text shown on each button is brief, the full name being shown on
the status bar down to the left.
separator of the logger window and move the separator toward the right.
Testing The Mod3 Alarm
2 Click Execute and observe the state of the Mod_3_Offline block
(ALARM block). It should change from 0 (off) to 1 (on) after 60
execution intervals.
3 Click the VSD\MOD3 button to the left and observe the Alarm
block again, it should return to 0 (zero) immediately.
4 Click Execute to stop execution.
Testing the Static Pressure Alarm
5 Click RST . The cycle counter will be restored to 0 and the simu-
lator Real Time Clock will be reset to the startup values.
6 Click Execute and observe the state of the Duct_Static_SF block
(ALARM block). It should be 0 (off).
7 Click the VSD\Static_Press_Sensor button to the left to display
an Analog input form for entering a value. Enter a value of 6 and
observe the Alarm block again, it should change to 1 (on) after 120
Note
You can use Commands/Execute n Times... and enter, for example,
a value of 119. Continue by manually pressing the Step button until
you see the change.
8 Click the VSD\Static_Press_Sensor button to the left again and

enter a value of 0 and observe the Alarm block again. It should
change to 0 (off) after another 120 execution intervals.
9 Click the VSD\Static_Press_Sensor button to the left once more
and enter a value of -0.15 and observe the Alarm block again. It
should change to 1 (on) after another 120 execution intervals.
Testing the Sample Rate Generator
10 Click RST. The cycle counter will be restored to 0.
TAC AB, Nov 2006 81 (450)

04-00030-01-en
Click the Step button a number of times, and observe the NOT block
located to the right of the PULSE block. The NOT block should change
state to 1 (on) repeatedly, every five execution intervals.
Testing the First Start Interval Timer
11 Click RST. The cycle counter will be restored to 0. Observe the
state of the PULSE block in the center of the FBD page. It should
be 0 (zero).
12 Click Execute and observe the state of the PULSE block again. It
should remain at zero.
Sfan state and observe the state of the PULSE block again. It
should change to 1 (on) immediately and return to 0 (off) after 300
Testing the Control Signal
15 Click Execute button and observe the value of the VSD block to
the right (the AO block). It should start with a value of 0 for 59
execution intervals and after that, change to 50. This level depends
on the Mod3 alarm situation.
Sfan state and observe the value of the VSD block again. It should
change to 50 and remain for the startup period of 300 execution
intervals.
17 Click the VSD\Static_Press_Sensor button to the left to display
an Analog input form for entering a value. Enter a value within the
alarm range (-1, 5.0). The setpoint is 1.0 so we enter a value of 2
and observe the value of the VSD block. It should be counting
down from the previous 50. At 0, it should stop.
18 Click Execute and click Step a couple of times to see the value of
the XPR block. It will be calculating negative values but they will
not be transferred to the output due to the LIMIT block.
19 Click the VSD\Static_Press_Sensor button and enter a value
below the setpoint. Enter for instance a value of 0.5 and observe
the value of the VSD block. It should now be counting up from the
previous level. At 100, it should stop.
within the deadzone 0.2. Enter, for instance, a value of 0.9 and
observe the value of the VSD block. It should now remain steady
at the previous level.
within the deadzone 0.2. Enter, for instance, a value of 1.1 and
observe the value of the VSD block again. It should still remain at
the previous level.
82 (450) TAC AB, Nov 2006

04-00030-01-en
4.7 The Relief Damper/Fan Control

In this part we will design control of the static pressure in the building
using a Relief Damper and a Relief Fan, based on measurement of the
Building Static Air pressure.
We will also arrange for alarms to trigger when the sensor is failing and
when the measurement value is out of limits.
We can identify some mechanisms, forming groups of function blocks
like:
• Alarm when Static Pressure is Out of Range
• Alarm when the measurement is out of limits.
• Control Algorithm for the Damper in two stages.
• Control logic for Relief Fan
We will create the design by forming groups of function blocks for the
specific mechanisms. These mechanisms are: Alarm on sensor failure,
Alarm when measurement is out of limits, Control algorithm for the
damper, Control algorithm for the Relief fan.
page on the screen.
signals in a common module called Relief.
Locating the Input and Output blocks
1 Locate Bldg_Static, an AI type function block, in the diagram
window, to the left and vertically approximately one third of the
way down from the top. Then define the block..
Identifier Bldg_Static
Unit "wc
Description Bldg static pressure sensor
Public No
R/W (Acc.)
Backup No
Mod Number M3
Terminal ref. U4
Sensor 2-10 V
Time Const: 0
Initial Value: .05
Min Value: -0.25
Max. Value: 0.25
TAC AB, Nov 2006 83 (450)

04-00030-01-en
2 Locate Relief_Air_Dmprs_DO, a DOPU type function block, in

the diagram window, to the right of the FBD page and vertically
approximately midways. Then define the block.
Identifier Relief_Air_Dmprs_Do
Unit %Opn
Description Relief Air Dampers Output
Public No
R/W (Acc.)
Backup
Bound to Digital Pulse output
Mod Number M1
Term. Ref K3
Initial Value = 0
Min. Pulse 0.1
Note
Use the Online help or read Section 14.16, “DOPU – Digital Pulse
Output” to learn more about the DOPU block.
3 Locate Relief_Fan, a DO type function block, in the diagram win-

dow, to the right of the FBD page and vertically approximately
one third from the top. Then define the block.
Identifier Relief_Fan
Unit
Description Relief Fan Start/Stop Circuit
Public Yes
R/W (Acc.)
Backup
Mod Number M1
Term. Ref K2
Initial Value = Off
Calibration of the measured value.

We want a possibility to calibrate the static pressure measurement. To
value.
84 (450) TAC AB, Nov 2006

04-00030-01-en
4 Locate Bldg_Static_Offset, a PVR type function, in the diagram

window, below the Bldg_Static block (AI block). Then define the
block.
Identifier Bldg_Static_Offset
Unit "wc
Description Offset for Calibration of d Bldg Static

Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
5 Locate Bldg_Static, an Addition operator, in the diagram win-

dow, to the right of the AI function block. Then define the block.
Select the Mode 1 for this operator, arranging one input horizon-
tally, and the other vertically.
Identifier Bldg_Static
Unit "wc
Description Calibrated Bldg Static
Public Yes
Mode 2 No
6 Connect the output of the Bldg_Static_Press_Sensor, to the hori-

zontal input of the Addition operator.
7 Connect the output of the Bldg_Static_Offset, to the vertical input
of the Addition operator.
Alarm when the Bldg Static Pressure experiences a Sensor
Failure
Now we want to produce an alarm when the value is out of the expected
sensor range. Here it is done, using an expression in an expression block
of the XPB type. Suitable numerals in the expression defines the
allowed levels.
right of the Bldg_Static_Offset (PVR) function block. Then define
the block and enter the expression A<-0.3|A>0.3.
Identifier
Unit
Description
Public No
R/W (Acc.)
Type Binary
Expression A<-0.3|A>0.3
TAC AB, Nov 2006 85 (450)

04-00030-01-en
9 Connect the output of the Bldg_Static block (the Addition opera-

tor) to the input of the XPB block.
10 Locate Bldg_Static_SF, an ALARM function block, in the dia-
block.
Identifier Bldg_Static_SF
Unit Normal/Alarm
Description Sensor failure Bldg Static sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Sensor failure Bldg Static 2S
Alarm Processing
Vista Alarm tripped Sensor failure Bldg Static sensor 2nd Floor
South
Vista Alarm reset Sensor failure Bldg Static sensor 2nd Floor
South return to normal

Bldg_Static_SF (ALARM) block.
Alarm when the Bldg Static Pressure is below Limit
Now we want to trigger an alarm when the value is below a given limit.
We also want this alarm to be suppressed when the sensor failure alarm
is active. The limit value is defined in an PVR type block.
12 Locate Bldg_Static_Lo_AlmSP, a PVR type function block, in
the diagram window, below the Bldg_Static_Offset_SP block
(PVR block). Then define the block.
Identifier Bldg_Static_Lo_AlmSP
Unit "wc
Description Low Alarm Limit for Bldg Static
Public No
R/W (Acc.) Yes
Backup Yes
InitValue -0.1
The alarm condition is determined using an expression A<B, in an

expression block of the XPB type. To suppress the alarm when the sen-
sor failure alarm is active we add a logical condition to the expression,
86 (450) TAC AB, Nov 2006

04-00030-01-en
resulting in the expression c?0:A<B. The expression will create a func-

tion block with one binary input c, two analog inputs A and B, and a
binary output.
right of the Bldg_Static_Lo_Alm_SP (PVR) function block. Then
define the block and enter the expression c?0:A<B.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression c?0:A<B
14 Locate Bldg_Static_Low, an ALARM function block, in the dia-

block.
Identifier Bldg_Static_Low
Unit Normal/Alarm
Description Low Bldg Static Alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Low Bldg Static 2S
Alarm Processing
Vista Alarm tripped Low Bldg Static 2nd Floor South
Vista Alarm reset Bldg Static 2nd Floor South return to normal

Bldg_Static_Low (ALARM) block.
16 Connect the output of the Bldg_Static_Lo_Alm_SP block (the
PVR block) to input B of the XPB block.
17 Create a new node and connect the signal from the Bldg_Static
(the Addition operator) to input A of the expression block.
18 Create a new node and connect the output of the Bldg_Static_SF
(ALARM) block to input c of the XPB block.
Alarm when the Bldg Static Pressure is above Limit
Now we want to trigger an alarm when the value is below a given limit.
The limit value is defined in an PVR type block.
TAC AB, Nov 2006 87 (450)

04-00030-01-en
19 Locate Bldg_Static_Hi_AlmSP, a PVR type function block, in

the diagram window, below the Bldg_Static_LoAlmSP block
(PVR block). Then define the block.
Identifier Bldg_Static_Hi_AlmSP
Unit "wc
Description High Alarm Limit for Bldg Static
Public No
R/W (Acc.) Yes
Backup Yes
InitValue 0.1
Here the alarm condition is determined using an expression A>B, in an

expression block of the XPB type. The expression will create a function
block with two analog inputs A and B, and a binary output.
right of the Bldg_Static_Hi_Alm_SP (PVR) function block. Then
define the block and enter the expression A>B.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A>B
21 Locate Bldg_Static_High, an ALARM function block, in the dia-

block.
Identifier Bldg_Static_High
Unit Normal/Alarm
Description High Bldg Static Alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text High Bldg Static 2S
Alarm Processing
Vista Alarm tripped High Bldg Static 2nd Floor South
Vista Alarm reset Bldg Static 2nd Floor South return to normal
88 (450) TAC AB, Nov 2006

04-00030-01-en

Bldg_Static_High (ALARM) block.
23 Connect the output of the Bldg_Static_Hi_Alm_SP block (the
PVR block) to input B of the XPB block.
24 Create a new node and connect the output signal from the
Bldg_Static (the Addition operator) to input A of the expression
block.
Filtering the measurement of Building Static pressure
To moderate variations in the measurement value used for control we
use a filter.
25 Locate in the diagram window a FILT function block, to the right
of the Bldg_Static (the Addition operator) block. Then define the
block.
Identifier
Unit
Description
Public
R/W (Acc.) Yes
Backup Yes
Time Constant 10
26 Create a new node and connect the signal from the Bldg_Static
(the Addition operator) to the input of the FILT function block.
Our design, so far, should look something like this:
TAC AB, Nov 2006 89 (450)

04-00030-01-en
Modulating the Damper.

The modulating of the damper position uses two controller blocks, one
PIDA controller block to calculate the degree of opening and one PIDI
controller block for positioning the damper.
The PIDA controller block uses a set of operators inputs defined by
PVR function blocks, setpoint, proportional gain and integration time.
The PIDI controller block uses defined constants for internal parame-
ters.
27 Locate in the diagram window a PIDA function block, horizon-
tally and vertically approximately in the middle of the printable
page. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
ControlInt 30
Umin 0
Umax 100
Stroke Time 0
Note
Use the Online help or read Section 14.34, “PIDA – PID Controller –
Analog Output” to learn more about the PIDA block.
28 Locate Bldg_Static_SetPoint, a PVR type function block, in the

diagram window, to the left of the PIDA function block. Leave
space for approximately an additional block between the PVR
block and the PIDA block. Then define the block.
Identifier Bldg_Static_SetPoint
Unit "wc
Description Bldg Static Pressure Setpoint
Public
R/W (Acc.)
Backup
InitValue .05
29 Locate Bldg_Static_PG, a PVR type function block, in the dia-

gram window, below the Bldg_Static_SetPoint. Then define the
block.
Identifier Bldg_Static_PG
90 (450) TAC AB, Nov 2006

04-00030-01-en
Unit % per "wc

Description Bldg Static Proportional Gain
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 500
30 Locate Bldg_Static_Int_TC, a PVR type function block, in the

diagram window, below the Bldg_Static_PG. Then define the
block.
Identifier Bldg_Static_Int_TC
Unit seconds
Description Bldg Static Integral Time Constant
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 1000
31 Connect the output of the Bldg_Static_SetPoint to input SP of the

PIDA function block.
In the application, the PIDA controller will need a negative sign on the
value for gain. We provide for this by using an Negate operator before
the input.
32 Locate in the diagram window an Negate operator, to the right of
the Bldg_Static_PG (PVR) function block.
Note
more about the Negate block.
33 Connect the output of the Bldg_Static_PG block to the input of the

Negate operator.
34 Connect the output of the Negate operator to input G of the PIDA
function block.
The controller parameters derivative time (Td) and deadzone (DZ) are,
in our design, defined by two Real const operators.
35 Locate in the diagram window a Real const operator to the left of
the PIDA function block. If suitable you can select mode 2 to
make the output connection horizontal. Then define the block.
Identifier
Unit
Description
TAC AB, Nov 2006 91 (450)

04-00030-01-en
Public
Mode 2 Yes
Value 0
36 Connect the output of the Real const to input Td of the PIDA func-
tion block.
37 Locate in the diagram window another Real const operator to the
left of the PIDA function block. Then define the block.
Identifier
Unit
Description
Public
Mode 2 No
Value 0
38 Connect the output of the Real const to input DZ of the PIDA

function block.
The controller function block will be in different modes, depending on
operating conditions.
We use an expression block to determine the mode to run. An expres-
sion b?2:a?1:3 used in an expression block with integer output (XPI)
will create a function block with two binary inputs, a and b. Input a rep-
resents the Fan Status input. Input b represents the alarm state.
39 Locate in the diagram window an XPI expression block, above the
column of PVR parameter blocks. Then define the block and enter
the expression b?2:a?1:3.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Integer
Expression b?2:a?1:3
Sfan_Status block DI block on the Fan Start Stop logic part of the
FBD) to input a of the XPI function block.
41 Connect the output signal from the Bldg_Static_SF block to input
b of the XPI function block.
42 Connect the output signal from the XPI function block to input
Mod of the PIDA function block.
92 (450) TAC AB, Nov 2006

04-00030-01-en
If there is a communication failure with I/O extension module 3, the

control signal calculated for the VSD should be used as control value for
the Relief Damper.
We provide for the alternate control signal (in case of communication
loss with Mod 3) using an Analog mux operator as a signal selector.
43 Locate Relief_Air_Dampers, an Analog mux operator, in the
diagram window, to the right of the PIDA function block.
Identifier Relief_Air_Dampers
Unit % Open
Description Relief Air Dampers
Public Yes
Mode 2
44 Create a new node and connect the signal to the VSD (the DO
block on the VSD Control FBD page) to the upper horizontal input
(1) of the Analog mux operator.
45 Connect the output of the PIDA function block to the lower hori-
zontal input (0) of the Analog mux operator.
Mod_3_Offline (alarm block on the VSD Control FBD page) to
the control input of the Analog mux operator block (the vertical
one).
We can now also connect the tracking signal to input Tsg of the PIDA
controller.
47 Create a new node and connect the output signal from the PIDA
block to input Tsg of the same PIDA function block.
TAC AB, Nov 2006 93 (450)

04-00030-01-en
The added part of our design, so far, should look something like this:
Designing the Relief Damper Positioning

The relief damper is modulated between 0 and 100%. The damper actu-
ator is connected to a single binary output.
The damper in question is a device responding to Pulse With Modula-
tion (PWM) of the control input. Parameters are selected to generate
suitable pulses with a length between 0.1 to 5.2 seconds.
The control is executed by a PIDI controller block using a fixed set of
parameters together with a DOPU function block.
Two delay blocks and an inverting block forms a symmetric pulse train
used to "gate" the calculation of the control input to the PIDI control
block.
48 Locate in the diagram window a PIDI function block to the left of
the Relief_Air_Dmprs_Do function block (the DOPU block).
Then define the PIDI block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
94 (450) TAC AB, Nov 2006

04-00030-01-en
ControlInt 10
Stroke Time 5.2
Note
Use the Online help or read Section 14.35, “PIDI – PID Controller –
Incremental Output” to learn more about the PIDI block.
49 Connect the output of the PIDI function block to the

Relief_Air_Dmprs_Do function block (the DOPU block).
In this design, the parameters for setpoint, mode, gain, integration time,
and deadzone are defined using constants. They are not made public.
50 Locate in the diagram window six Real Const operators on top of
each others and to the left of the PIDI function block. For better
use of space, you can alternately locate them left and right of each
other. To have a compact design, you can use mode 2 to have the
outputs horizontally. Then define the blocks.
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
Identifier
Unit
Description
Public
Mode 2 Yes
Value 1
Identifier
Unit
Description
Public
Mode 2 Yes
Value -1
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
TAC AB, Nov 2006 95 (450)

04-00030-01-en
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
Identifier Relief\MAT_DZ
Unit
Description
Public
Mode 2 Yes
Value 0
From the top downward, connect the input parameter blocks (the Real
constants) to the controller block.
51 Connect the upper Real const operator (Value = 0) to input SP
(Setpoint) of the PIDI function block.
52 Connect the next Real const operator (Value = 1) to input Mod
(Mode) of the PIDI function block.
53 Connect the next Real const operator (Value = -1) to input G
(Gain) of the PIDI function block.
54 Connect the next Real const operator (Value = 0) to input Ti (Inte-
gration time constant) of the PIDI function block.
55 Connect the next operator Real const (Value = 0) to input Td (Der-
ivation time constant) of the PIDI function block.
56 Connect the MAT_DZ const (Value = 0) to input DZ (DeadZone)
of the PIDI function block.
As measurement value, we use either the previous determined value, or
a value of two, or a value of zero. The value is entered into the input for
a period of 11 seconds with a pause lasting the same amount of time.
The value of two is entered during periods when the calculated value is
below 1.0. The value of zero is entered during the pauses.
Selecting which value to input is achieved here using an expression
block with an analog output XPR.
In the block we will use the feature that Menta during evaluation of the
expression converts the a, which is a logical (binary) state i.e. on or off
(1 or logical zero), is converted to real 1 or real zero. Thus we will have
a multiplication with the a resulting in either a value of zero or the con-
ditionally calculated value (B or 2).
96 (450) TAC AB, Nov 2006

04-00030-01-en
57 Locate in the diagram window an XPR function block above the

PIDI function block. Enter the expression a*(B>1?B:2). This
expression will create a function block with two inputs, a binary
input a, and an analog input B.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Real
Expression a*(B>1?B:2)
58 Connect the output of the expression block to input MV (Measure-

ment value) of the PIDI function block.
59 Connect the output of the Relief_Air_Dampers (the Analog mux)
to input B of the XPR function block.
The pulse train signal is generated by two delay blocks, one to allow for
the feedback signal in Menta, and an inverting block.
60 Locate in the diagram window a DELB function block to the left
of the XPR function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Init Value 0
61 Connect the output of the DELB function block to input a of the

XPR function block.
62 Locate in the diagram window a NOT function block to the left of
the DELB function block.
64 Locate in the diagram window a DELAY function block to the left
of the NOT function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
TAC AB, Nov 2006 97 (450)

04-00030-01-en
Backup
Delay On 10
Delay Off 10
65 Connect the output of the DELAY function block to the input of

the NOT function block.
66 Create a new node and connect the output signal from the DELB
function block to the input of the DELAY function block.
The most recently added part should look like this:
Designing the Relief Fan Start

The Relief fan is to start when the relief damper is 100% open and the
building static pressure exceeds 0.06 "wc for more than ten minutes.
The relief fan will stop when the relief damper is modulated to less than
40% and the building static pressure falls below -0.01 "wc.
The main part of this control is executed in an expression block with a
binary output, an XPB function block. Values for the levels where the
fan starts and stops are entered as numerals in the expression. This
means that these levels can be changed only by reprogramming and then
downloading the altered application.
The necessary delay is created in a delay function block.
of the Relief_Fan function block (the DO function block). Then
define the block.
Identifier
Unit
Description
Public
98 (450) TAC AB, Nov 2006

04-00030-01-en
R/W (Acc.)
Backup
Delay On 600
Delay Off 10
68 Connect the output of the DELAY function block to the input of

the Relief_Fan function block.
69 Locate in the diagram window a DELB function block to the left
of the DELAY function block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Init Value 0
70 Connect the output of the DELB function block to the input of the
DELAY function block.
71 Locate in the diagram window an XPB expression block to the left
of the DELB function block. Enter the expression
d?0:c&A>99&B>0.06?1:A<40&B<-0.01?0:z. This expression
will create an expression block with five inputs. Here input A rep-
resents the value calculated by the PIDA controller block. Input B
represents the filtered measurement value of the building static
pressure. Input c represents the fan state indication. Input d repre-
sents the static pressure alarm. Input z represents a previous binary
state of the expression and is used for latching the process.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression d?0:c&A>99&B>0.06?1:A<40&B<-0.01?0:z
72 Connect the output of the XPB expression block to the input of the
controller block to input A of the XPB expression block.
74 Create a new node and connect the output signal from the FILT
function block to input B of the XPB expression block.
TAC AB, Nov 2006 99 (450)

04-00030-01-en
75 Create a new node and connect the Fan Status signal to input c of
the XPB expression block. This signal is also used in the EXP
block to determine the Mod of the PIDA controller block.
Bldg_Static_SF ALARM block to input d of the XPB expression
block.
77 Create a new node and connect the output of the DELAY function
block to input z of the XPB expression block.
When completed, the additional part should look like this:
Assigning the Module Name "Relief"

want to treat as signals in a common module called Relief.
name Relief.
Now, that this is finished, the page of the function block diagram should
look like this:
100 (450) TAC AB, Nov 2006

04-00030-01-en

This will open the FBD in the simulation window and the five analog
inputs, together with the previous buttons and a new button, the
Relief\Bldg_Static, as the uppermost button.
The text shown on each button is brief, the full name is being shown on
the status bar down to the left.
Testing the Pressure Sensor Failure Alarm
The alarm should be generated when the value is outside the range -0.3
to 0.3.
2 Click Execute and observe the value of the BLDG_Static_SF
block (the ALARM block). It should be 0 (off).
3 Click the Relief\Bldg_Static button to the left to display an Ana-
log input form for entering a value. Enter a value of -0.5 and
observe the Alarm block again. It should change to 1 (on) after
120 execution intervals.
4 Click the Relief\Bldg_Static button again and enter the original
value of 0.05. Observe the Alarm block again. It should change to
0 (off) after an additional 120 execution intervals.
5 Click the Relief\Bldg_Static button to the left to display an Ana-
log input form for entering a value. Enter a value of 0.5 and
value of 0.05. Observe the Alarm block again. It should change to
0 (off) after an additional 120 execution intervals.
Testing the Pressure level Low Alarm
7 Click the Relief\Bldg_Static button again and enter a value
below the limit of -0.1. Enter a value of -0.2 and observe the
BLDG_Static_Low block, it should change to 1 (on) after 120
8 Click the Relief\Bldg_Static button to enter the original value of
0.05 and observe the Alarm block again. It should return to 0 (off)
after an additional 120 execution intervals.
9 Click the Relief\Bldg_Static button again and enter a value
below the limitfor sensor failure. Enter a value of -0.5, and
observe the BLDG_Static_Low block, it should remain at 0 (off)
after 120 execution intervals. This is because the Low alarm is
suppressed by the sensor failure..
TAC AB, Nov 2006 101 (450)

04-00030-01-en
Testing the Pressure level HighALarm

10 Click Execute and observe the value of the BLDG_Static_High
11 Click the Relief\Bldg_Static button to enter a value above the
limit of 0.1. Enter a value of 0.5 and observe the Alarm block
again.. It should change to 1 (on) after 120 execution intervals.
12 Click the Relief\Bldg_Static button to enter the original value of
0.05 and observe the Alarm block again. It should return to 0 (off)
after 120 execution intervals.
Testing the Relief Damper Control
14 Click Execute and observe the value of the PIDA block in the
middle of the FBD. It should have a value of 0 (zero).
15 Click the Relief\Bldg_Static button and enter a value below the
setpoint (0.1). Enter a value of 0.06 and observe the PIDA block
again. Nothing should happen because the controller is in mode 3
(forced to minimum output level). The controller mode is deter-
mined by the XPR block above and to the left.
We will have to simulate the Sfan being in operation (as well as having
mo alarm) in order to change the mode of the controller.
Sfan state and observe the value of the XPR block. It should
change to 1 (on). Observe the value of the PIDA block again. It
should start to calculate an increasing value.
17 Click the Relief\Bldg_Static button and enter a value of 0.04.
Observe the PIDA block again. It should change to calculate a
decreasing value.
Now the PIDA controller is calculating a value to be used for position-
ing the Relief Damper. The Analog mux operator will still select
another value, the VSD position value, due to a MOD3 alarm situation.
We can observe this in the XPR block (located above the PIDI block) as
a periodical occurrence, 11 seconds out of 22, showing a value of 50.
18 Click the VSD\MOD3 button to the left to suppress the MOD3
Alarm and observe the observe the value of the XPR block again.
It should now periodically have the value from the PIDA control-
ler.
Note
It might be more easier to see the brief duration of the values using the
Step button instead of the Execute button.
102 (450) TAC AB, Nov 2006

04-00030-01-en
19 Right-click the Relief\Relief_Air_Dmprs_Do block and select

Record to follow the pulses in the Trend Logging pane. You
should be able to see short, periodical pulses.
Observe the PIDA block again, it should begin to calculate an
increasing value with a final value of 100.
21 Observe the pulses in the Trend Logging pane, they should now
have become wider (have longer duration).
Testing the Relief Fan Start
Wait for the PIDA block to reach a level of 100.
Note
You can shorten the waiting time by clicking the PIDA block and
entering a value close to 100.
23 Observe the XPB block below the PIDA block. It should change to
1 (on) when the signal level from the PIDA reaches a level of 100.
24 Observe the DELAY block and the Relief_Fan block; they should
change to state 1 (on) after 600 execution intervals.
Wait for the PIDA block to reach a level of 40.
26 Click the Relief\Bldg_Static button and enter a value of -0.015.
Observe the XPB block and the Delay block. The XPB block
should change to 0 (off) immediately, and the Relief_Fan block
should change to 0 (off) after 10 execution intervals.
4.8 Economizer Mode Calculations

In this part, we will design the part of the FBD that handles the calcula-
tions for Economizer mode. Calculations of the enthalpy of the outside
air and the return air will be made. The calculations will be based on air
temperature and humidity measurements in the outside air, as well in the
return air. Our design will produce a signal representing the command
controlling whether to use economizer mode or not.
We will also provide the logic for alarms, activated on sensors failure
and when measurement values are either low or high.
We can identify some mechanisms, forming groups of function blocks.
These are:
• Calculations of outside air measurements
TAC AB, Nov 2006 103 (450)

04-00030-01-en
• Calculations of return air measurements.

• Logically combining the results.
We will create the design by forming groups of function blocks for iden-
tified mechanisms. These mechanisms are: calculation of outside air
measurements, calculation of return air measurements, logically com-
bining the results.
page on the screen.
We will make most of the function blocks on this FBD printable page a
set of signals in a common module called Econ.
Locating the Input blocks
1 Locate OA_Temp, an AI type function block, in the diagram win-
dowto the left and vertically approximately one third from the top.
Identifier OA_Temp
Unit °F
Description Outside Air Temperature
Public No
R/W (Acc.)
Backup No
Bound to Non-Linear Analog Input
Mod Number M3
Terminal ref. B4
Sensor TAC Termistor (°F)
Time Const: 0
Initial Value: 70
2 Locate OAHumiditySen, an AI type function block, in the dia-

gram window, to the left and below the OA_Temp function block.
Leave vertical space allowing for a future block between them.
Identifier OAHumiditySen
Unit %RH
Description Outside Air Humidity
Public No
R/W (Acc.)
Backup No
Mod Number M5
Terminal ref. U1
Sensor 0..10V
104 (450) TAC AB, Nov 2006

04-00030-01-en
Time Const: 0
Initial Value: 50
Min Value: 0
Max. Value: 100
The design of the Return Air temperature is identical to our design of

the Bldg Static Pressure, so we can Copy and Paste the required func-
tion blocks. This way, we create not only the blocks for I/O, but also the
blocks for calculation and logics.
3 Mark and select the AI block, the PVB, the XPB, and the ALARM
blocks we made during the design of the Relief Damper/Fan Con-
trol.
4 Use Edit/Copy and Edit/Paste to duplicate the blocks on the new

FBD page. Locate an AI type function block to the left and verti-
cally approximately one third from the top of the printable page.
Observe that all copies of blocks with names and parameters must be
checked and replaced when necessary. The XPB blocks for high and
low alarms are identical. Redefine all necessary copied blocks.
5 Redefine RAT_Sensor, an AI type function block. Place the AI
block vertically approximately one third from the top and in the
middle horizontally.
Identifier RAT_Sensor
Unit °F
Description Return Air Temperature Sensor
Public No
R/W (Acc.)
Backup No
TAC AB, Nov 2006 105 (450)

04-00030-01-en

Mod Number M3
Terminal ref. B2
Sensor TAC Thermistor [°F]
Time Const: 0
Initial Value: 75
6 Redefine RAT_Offset, the PVR block below the MAT_Sensor

block.
Identifier RAT_Offset
Unit °F
Description Offset for Calibration of RAT
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
7 Redefine RAT, the Addition operator.
Identifier RAT
Unit °F
Description Calibrated RAT
Public Yes
Mode 2
8 Redefine RAT_SF, the ALARM block to the right of the XPB

block.
Identifier RAT_SF
Unit Normal/Alarm
Description Sensor failure return air sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Sensor failure RAT
Alarm Processing
Vista Alarm tripped Sensor failure return air sensor 2nd Floor South
Vista Alarm reset Sensor failure return air sensor 2nd Floor South
return to normal
106 (450) TAC AB, Nov 2006

04-00030-01-en
9 Redefine RAT_LowAlarm, the PVR type function block below

the RAT_HighAlarm block.
Identifier RAT_LowAlarm
Unit °F
Description Low Alarm Limit for RAT
Public No
R/W (Acc.) Yes
Backup Yes
InitValue 50
10 Redefine RAT_Low, the ALARM function block to the right of

the XPB block.
Identifier RAT_Low
Unit Normal/Alarm
Description Low return air temp alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Low RAT
Alarm Processing
Vista Alarm tripped Low return air temperature 2nd Floor South
Vista Alarm reset Return air temperature 2nd Floor South return
to normal
11 Redefine RAT_HighAlarm, the PVR block below the

MAT_Offset block.
Identifier RAT_HighAlarm
Unit °F
Description High Alarm Limit for RAT
Public
R/W (Acc.) Yes
Backup Yes
InitValue 80
12 Redefine RAT_High, the ALARM function block to the right of

the XPB block.
Identifier RAT_High
Unit Normal/Alarm
Description High return air temp alarm
TAC AB, Nov 2006 107 (450)

04-00030-01-en
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text High RAT
Alarm Processing
Vista Alarm tripped High return air temperature 2nd Floor
Vista Alarm reset Return air temperature 2nd Floor South return
to normal
13 Locate RAHumiditySen, an AI type function block, in the dia-

gram window, vertically approximately one fourth of the way up
from the bottom and in the middle horizontally. Then define the
block.
Identifier RAHumiditySen
Unit %RH
Description Return Air Humidity Sensor
Public No
R/W (Acc.)
Backup No
Mod Number M3
Terminal ref. U2
Sensor 2..10 V
Time Const: 0
Initial Value: 50
Min Value: 0
Max. Value: 100
Alarm when the Outside Air Temperature experiences a

Sensor Failure
We want a possibility to calibrate the outside air temperature measure-
ment. To achieve this, we add an adjustable offset value and use the
totalled value.
14 Locate OAT_Offset, a PVR type function block, in the diagram
window, below the OA_Temp block (AI block). Then define the
block.
Identifier OAT_Offset
Unit °F
Description Offset for calibration of OAT
Public Yes
108 (450) TAC AB, Nov 2006

04-00030-01-en
R/W (Acc.) Yes

Backup Yes
InitValue 0
15 Locate OAT, an Addition operator, in the diagram window, to the

right of the AI function block. Then define the block. Select the
Mode 1 for this operator, arranging one input horizontal, and one
input vertical.
Identifier OAT
Unit °F
Description Calibrated OAT
Public Yes
Mode 2
16 Connect the output of OA_Temp to the horizontal input of the

Addition operator.
17 Connect the output of OAT_Offset to the vertical input of the
Addition operator.
done using an expression in an expression block of the XPB type.
Appropriate numbers in the expression define the allowed levels.
right and slightly above the Addition operator. Then define the
block and enter the expression A<-491|A>266.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<-491|A>266
19 Connect the output of the OAT block (the Addition operator) to

the input of the XPB block.
20 Locate OAT_SF, an ALARM function block, in the diagram win-
dow, to the right of the XPB block. Then define the block.
Identifier OAT_SF
Unit Normal/Alarm
Description Sensor failure return air sensor
Public
R/W (Acc.)
Backup
TAC AB, Nov 2006 109 (450)

04-00030-01-en
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Sensor failure OAT
Alarm Processing
Vista Alarm tripped Sensor failure outside air sensor
Vista Alarm reset Sensor failure Outside air sensor return to nor-
mal
21 Connect the output of the XPB block to the input of the OAT_SF
(ALARM) block.
Alarm when the Outside Air Humidity experiences a Sensor
Failure
We want the possibility to calibrate the outside air humidity measure-
totalled value.
22 Locate OAHumid_Offset, a PVR type function block, in the dia-
gram window, below the OAHumiditySen (AI block). Then define
the block.
Identifier OAHumid_Offset
Unit °F
Description Offset for Calibration of OA Humidity
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
23 Locate OAHumidity, an Addition operator, in the diagram win-

dow, to the right of the AI function block. Then define the block.
Select the Mode 1 for this operator, arranging one input horizontal,
and one input vertical.
Identifier OAHumidity
Unit °F
Description Calibrated OA Humidity
Public Yes
Mode 2
24 Connect the output of OAHumiditySen to the horizontal input of

25 Connect the output of OAHumid_Offset to the vertical input of the
Addition operator.
110 (450) TAC AB, Nov 2006

04-00030-01-en
done using an expression in an expression block of the XPB type.
right and slightly below the Addition operator. Then define the
block and enter the expression A<10.
27 Connect the output of the OAHumid block (the Addition operator)
to the input of the XPB block.
28 Locate OAHumidity_SF, an ALARM function block, in the dia-
block.
Identifier OAHumidity_SF
Unit Normal/Alarm
Description Sensor failure OA Humidity sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Sensor failure OA Humidity
Alarm Processing
Vista Alarm tripped Sensor failure OA Humidity sensor
Vista Alarm reset Sensor failure OA Humidity sensor return to
normal

OAHumidity_SF block.
Calculating the Outside Air Enthalpy
Calculation of the enthalpy, based on the air temperature and humidity,
is done using the ENTH function block.
Note
Use the Online help or read Section 14.17, “ENTH – Enthalpy” to
learn more about the ENTH block.
30 Locate in the diagram window an ENTH function block, below

the OAT_SF block.
31 Create a new node and connect the output signal from the OAT
block (Addition operator) to input T of the ENTH function block.
32 Create a new node and connect the output signal from the OAHu-
midity block (Addition operator) to input H of the ENTH function
block.
TAC AB, Nov 2006 111 (450)

04-00030-01-en
Conditional Outside Air Enthalpy Value

A value will only be calculated for the enthalpy when there is no sensor
failure alarm. In the event of an alarm, the value to use is set to 0 (zero).
We use an expression block for this.
33 Locate OA_Enthalpy, an XPR expression block, in the diagram
window, to the right of the ENTH function block. Then define the
block and enter the expression a?100:B. This expression will cre-
ate a block with two inputs, a and B. Input a is a binary input and
represents the alarm state of OAT_SF. Input B is an analog input
and represents the value of calculated enthalpy.
Identifier OA_Enthalpy
Unit BTU/lb
Description
Public Yes
R/W (Acc.)
Type Real
Expression a?100:B
34 Connect the output of the OAT_SF ALARM block to input a of

the XPR block.
35 Connect the output of the ENTH function block to input B of the
XPR block.
112 (450) TAC AB, Nov 2006

04-00030-01-en
The design concerning the outside air measurements will now look like
this:
Alarm when the Return Air Humidity experiences a Sensor

Failure
We want the possibility to calibrate the return air humidity measure-
totalled value.
36 Locate RAHumid_Offset, a PVR type function block, in the dia-
gram window, below the RAHumiditySen (AI block). Then define
the block.
Identifier RAHumid_Offset
Unit %RH
Description Offset for Calibration of RA Humidity
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
TAC AB, Nov 2006 113 (450)

04-00030-01-en
37 Locate RAHumidity, an Addition operator, in the diagram win-

dow, to the right of the RAHumiditySen function block. Then
define the block. Select the Mode 1 for the operator, arranging one
input horizontally, and the other vertically.
Identifier RAHumidity
Unit °F
Description Calibrated RA Humidity
Public Yes
Mode 2
38 Connect the output of RAHumiditySen to the horizontal input of

39 Connect the output of RAHumid_Offset to the vertical input of the
Addition operator.
done using an expression in an expression block of the XPB type. Suit-
able numerals in the expression defines the allowed levels.
block and enter the expression A<10|A>100.
Identifier (Name)
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<10|A>100
41 Connect the output of the RAHumid block (the Addition operator)

to the input of the XPB block.
42 Locate RAHumidity_SF, an ALARM function block, in the dia-
block.
Identifier RAHumidity_SF
Unit Normal/Alarm
Description Sensor failure RA Humidity sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
114 (450) TAC AB, Nov 2006

04-00030-01-en
OP Alarm text Sensor failure RA Humidity

Alarm Processing
Vista Alarm tripped Sensor failure RA Humidity sensor 2nd Floor
South
Vista Alarm reset Sensor failure RA Humidity sensor 2nd Floor

RAHumidity_SF block.
Calculating the Return Air Enthalpy
Calculation of the enthalpy, based on the air temperature and humidity,
is done using the ENTH function block.
44 Locate in the diagram window an ENTH function block, to the
right of the RAT_High block (the ALARM block).
45 Create a new node and connect the output signal from the RAT
block (Addition operator) to input T of the ENTH block.
46 Create a new node and connect the output of RAHumidity (the
Addition operator) to input H of the ENTH function block.
Conditional Return Air Enthalpy Value
A value will only be calculated for the enthalpy when there is no tem-
perature sensor failure. In case of an alarm, the value to use is set to 0
(zero). We use an expression block for this.
47 Locate RA_Enthalpy, an XPR expression block, in the diagram
window, to the right of the ENTH function block. Then define the
block and enter the expression a?0:B. This expression will create a
block with three inputs, a, B, and c. Input a is a binary input and
represents the alarm state of RAT_SF. Input B is an analog input
and represents the value of calculated enthalpy..
Identifier RA_Enthalpy
Unit BTU/lb
Description Return Air Enthalpy
Public Yes
R/W (Acc.)
Type Real
Expression a?0:B
48 Connect the output of the RAT_SF ALARM block to input a of the

XPR block.
49 Connect the output of the ENTH function block to input B of the
XPR block.
TAC AB, Nov 2006 115 (450)

04-00030-01-en
The design concerning the return air measurements will now look like
this.
Enabling the Economizer Mode

The Economizer Mode is enabled when the Fan is running and the out-
side air enthalpy is more than -2 BTU/lb below the return air enthalpy.
The difference is detected by subtracting the return air enthalpy from
the supply air enthalpy. Hysteresis and delays are applied to the differ-
ence in order to reduce changes of state that are too frequent.
50 Locate in the diagram window a Subtraction operator, near the
upper right corner.
51 Locate in the diagram window a function block HYST, to the right
of the Subtraction operator. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
116 (450) TAC AB, Nov 2006

04-00030-01-en
Activate -2
Deactivate -0.5
Note
Use the Online help or read Section 14.22, “HYST – Binary Hystere-
sis” to learn more about the HYST block.
52 Locate in the diagram window a function block, DELAY, to the

right of the HYST function block. Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Delay On 300
Delay Off 300
53 Locate Economizer, an XPB expression block, in the diagram

window, to the right of the DELAY function block. Then define
the block and enter the expression a&b. This expression will cre-
ate a block with two inputs, a, and b. Input a is a binary input and
represents the Fan state. Input b is also a binary input and repre-
sents the created condition based upon a sufficient difference to
enable economizer mode.
Identifier Economizer
Unit
Description Economizer Enabled
Public Yes
R/W (Acc.)
Type Binary
Expression a&b
54 Connect the output of the DELAY function block to input b of the

XPB expression block.
55 Connect the output of the HYST function block to the input of the
DELAY function block.
56 Connect the output of the Subtraction operator to the input of the
HYST function block.
57 Connect the output of the OA_Enthalpy expression block to the
horizontal input of the Subtraction operator.
TAC AB, Nov 2006 117 (450)

04-00030-01-en
58 Connect the output of the RA_Enthalpy expression block to the

vertical input of the Subtraction operator.
59 Create a new node and connect Sfan_Status (DI block, and used in
previous FBD pages) to input a of the expression block.
Assigning the Module Name "Econ"
Most function blocks on this FBD printable page are a set of signals we
want to treat as signals in a common module called Econ.
One function block, the OA_Temp block, is not to be included in the
Mixed_Air module.
The easiest way to do this is as follows:
name Econ.
61 Then mark only the OA_Temp block and Right-click, click Mod-
ule and then click Clear Module to exclude this block from the
module name Mixed_Air..
Now, when this is finished, this page of the total function block diagram
should look like this:

118 (450) TAC AB, Nov 2006

04-00030-01-en
This will open the FBD in the simulation window and the previous but-
tons for inputs, together with four new buttons in the left part. The text
shown on each button is brief, the full name is shown on the state bar
down to the left.
separator ofthe logger window and move the separator toward the right.
Testing the Outside Air Temperature Sensor Failure Alarm
The alarm should be generated when the value is outside the range -491
to 266.
2 Click Execute and observe the value of the OAT_SF block (the
ALARM block). It should be 0 (off).
3 Click the Mixed_Air\OA_Temp button to the left to display an
Analog input form for entering a value. Enter a value of 267 and
value of 70. Observe the Alarm block again. It should change to 0
(off) after another120 execution intervals.
5 Click the Relief\Bldg_Static button again and enter a value of
-492. Observe the Alarm block again. It should change to 1 (on)
after another 120 execution intervals.
(off) again (after another 120 execution intervals).
Testing the Outside Air Humidity Sensor Failure Alarm
The alarm should be generated when the value is below 10.
7 Click Execute and observe the value of the OAHumidity_SF
8 Click the Econ\OAHumiditySen button to the left to display an
9 Click the Econ\OAHumiditySen button again and enter the orig-
inal value of 50.
Testing the Outside Air Enthalpy Value Calculation
10 Make sure Execution has started.
Analog input form for entering a value. Enter a value of 77. If you
run an application created on a PC using the European measure-
ment system you should enter a value of 25.
TAC AB, Nov 2006 119 (450)

04-00030-01-en
12 Click the Econ\OAHumiditySen button to the left to display an

Analog input form for entering a value. Enter a value of 50, and
observe the value of the OA_Enthalpy block (the ENTH block). It
should calculate approximately 29.3. If you run an application cre-
ated on a PC using the European measurement system, the block
should have a value of 50.1 approximately.
Testing the Outside Air Conditional Enthalpy Value
The value to use should be 100 when there is a SF_Alarm, or else it
should be calculated. We create an Outside Air sensor failure alarm just
like before:
13 Click Execute and observe the value of the ENTH block.
observe the OA_Enthalpy block again. Whatever value before, it
should have changed to 100 when the Alarm block got a state of 1
(on) i.e. after 120 execution intervals.
Testing the Return Air Temperature Sensor Failure Alarm
The alarm should be generated when the value is outside the range of
-491 to 266.
15 Click Execute and observe the value of the RAT_SF block (the
16 Click the Econ\RAT_Sensor button to the left to display an Ana-
log input form for entering a value. Enter a value of 267 and
17 Click the Econ\RAT_Sensor button again and enter the original
value of 75. Observe the Alarm block again. It should return to 0
(off) after another 120 execution intervals.
18 Click the Econ\RAT_Sensor button again and enter a value of
-492. Observe the Alarm block again. It should change to 1 (on)
19 Click the Econ\RAT_Sensor button again and enter the original
(off) again (after another 120 execution intervals).
Testing the Return Air Temperature Low Alarm
20 Click the Econ\RAT_Sensor button again and enter a value
below the limit of 50. Enter a value of 49 and observe the
RAT_Low block (the ALARM block), it should change to 1 (on)
21 Click the Econ\RAT_Sensor button to enter the original value of
75 and observe the Alarm block again. It should return to 0 (off)
120 (450) TAC AB, Nov 2006

04-00030-01-en
22 Click the Econ\RAT_Sensor button again and enter a value

below the level for sensor failure. Enter a value of -492, and
observe the RAT_Low block, it should remain 0 (off) also after
120 execution intervals. This is because the Low alarm is sup-
pressed by the sensor failure.
Testing the Return Air Temperature High Alarm
23 Click Execute and observe the value of the RAT_High block (the
ALARM block). It should be 0 (off)
24 Click the Econ\RAT_Sensor button to enter a value above the
limit of 80. Enter a value of 81 and observe the Alarm block
again. It should change to 1 (on) after 120 execution intervals.
25 Click the Econ\RAT_Sensor button to enter the original value of
Testing the Return Air Humidity Sensor Failure Alarm
The alarm should be generated when the value is outside the range 10
to100.
26 Click Execute and observe the value of the RAHumidity_SF
27 Click the Econ\RAHumiditySen button to the left to display an
28 Click the Econ\RAHumiditySen button again and enter the orig-
inal value of 50. Observe the Alarm block again. It should return
to 0 (off) after another120 execution intervals.
29 Click the Econ\RAHumiditySen button again and enter a value
of 9. Observe the Alarm block again. It should change to 1 (on)
30 Click the Econ\RAHumiditySen button again and enter the orig-
inal value of 50. Observe the Alarm block again. It should change
to 0 (off) again (after another after another 120 intervals120 exe-
cution intervals).
Testing the Return Air Enthalpy Value Calculation
31 Make sure Execution has started.
32 Click the Econ\RAT_Sensor button and enter a value of 77. If
you run an application created on a PC using the European mea-
surement system, you should enter a value of 25.
33 Click the Econ\RAHumiditySen button and enter a value of 50.
Observe the value of the RA_Enthalpy block (the ENTH block). It
should calculate approximately 29.3. If you run an application cre-
TAC AB, Nov 2006 121 (450)

04-00030-01-en
ated on a PC using the European measurement system, the block

should have a value of approximately 50.1.
Testing the Return Air Conditional Enthalpy Value
The value to use should be 0 (zero) when there is a RAT_SF alarm, or
else it should be calculated. We create a Return Air sensor failure alarm
just like before:
34 Click Execute and observe the value of the ENTH block.
35 Click the Econ\RAT_Sensor button to the left to display an Ana-
observe the RA_Enthalpy block again. Whatever the value was
before, it should have changed to 0 (zero) when the Alarm block
adopted state 1 (on), that is after 120 execution intervals.
Testing the Economizer Mode signal
When the Outside Air enthalpy is more than -2 BTU/lb below the
Return Air enthalpy and the Sfan is running, Economizer Mode will be
enabled.
We simulate a situation where the outside air enthalpy is greater than the
return air enthalpy. We will simulate an outside air enthalpy of 25.2
BTU/lb, and a return air enthalpy of 29.3 BTU/lb.
36 Click Execute to stop execution and observe the HYST block in
the upper right corner. It should have state 0 (off).
Analog input form for entering a value. Enter a value of 70. If you
run an application created on a PC using the European measure-
ment system you should enter a value of 21.
38 Click the Econ\OAHumiditySen button and enter a value of 50.
Observe the value of the ENTH block. It should calculate approxi-
mately 25.2. If you run an application created on a PC using the
European measurement system, the block should have an approxi-
mate value of 40.5.
39 Click the Econ\RAT_Sensor button and enter a value of 77. If
you run an application created on a PC using the European mea-
surement system you should enter a value of 25.
40 Click the Econ\RAHumiditySen button and enter a value of 50.
Observe the value of the RA_Enthalpy block. It should calculate
approximately 29.3. If you run an application created on a PC
using the European measurement system, the block should have a
value of 50.1 approximately.
41 Click Execute and observe the HYST block in the upper right cor-
ner. It should change state from 0 (off) to 1 (on) after the changes
have been made. The DELAY block should change from 0 to 1,
but only after 300 execution intervals.
122 (450) TAC AB, Nov 2006

04-00030-01-en
42 Click the Mixed_Air\OA_Temp button and enter a value of 77.

If you run an application created on a PC using the European mea-
surement system you should enter a value of 21. Observe the
HYST block, it should change state from 1 (on) to 0 (off) after the
change has been made. The DELAY block should change from 1
to 0, but only after another 300 execution intervals.
Testing the conditional Economizer Mode On
43 Click the Mixed_Air\OA_Temp button and enter a value of 70.
If you run an application created on a PC using the European mea-
surement system you should enter a value of 21. Wait for the
DELAY block to change to 1 (on).
44 Observe the Economizer block (the XPB block), it should be 0
(off).
We have simulated the necessary difference in enthalpy. Besides the
desired difference, Economizer mode should only be on when the Sfan
is in use. We will have to simulate the Sfan running.
Sfan state and observe the state of the Economizer block (the XPB
block). It should change to 1 (on).
46 Release the SFan\SFan_Status button and observe the state of
the Economizer block. It should return to 0 (off).
TAC AB, Nov 2006 123 (450)

04-00030-01-en
4.9 The OA/RA Damper Control

In this part, we will design the part of the FBD dealing with mixed air
temperature control. Temperature control is achieved using the outside
and return air dampers. Our design will include use of the order to run
in Economizer mode. We will also provide the logic for alarms trig-
gered by sensor failure and when measurement values are either low or
high.
These are:
• Mixed air measurement processing
• Return air CO2 measurement processing.
• Control functions including CO2 limitation.
We will create the design by forming groups of function blocks for iden-
tified mechanisms. These mechanisms are: mixed air measurement pro-
cessing, return air CO2 measurement processing and control functions
including CO2 limitation.
page on the screen.
We will make the function blocks on this FBD printable page another
set of signals in a common module called Econ.
124 (450) TAC AB, Nov 2006

04-00030-01-en

The design for Mixed Air temperature is identical to the design we made
for the Bldg Static Pressure so we can use the method to Copy and Paste
the required function blocks.
1 Mark the AI block, the PVB, the XPB, and the ALARM blocks we
made when designing the Relief Damper/Fan Control.
2 Use Edit/Copy and Edit/Paste to duplicate the blocks on the new

FBD page. Place the AI type function block to the left and verti-
cally approximately one third of the way from the top of the print-
able page.
Note that all copies of blocks containing names and parameters must be
checked and replaced whenever necessary. The XPB blocks for high
and low alarms are identical. Redefine all the necessary copied blocks.
3 Redefine MAT_Sensor, an AI type function block.
Identifier MAT_Sensor
Unit °F
Description
Public
R/W (Acc.)
Backup
Mod Number M3
Terminal ref. B3
Time Const: 0
Initial Value: 55
TAC AB, Nov 2006 125 (450)

04-00030-01-en
4 Redefine MAT_Offset, the PVR block, below the MAT_Sensor

block.
Identifier MAT_Offset
Unit °F
Description Offset for Calibration of MAT
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
5 Redefine MAT, the Addition operator.
Identifier MAT
Unit °F
Description Calibrated MAT
Public Yes
Mode 2
6 Redefine the XPB expression block, to the right and slightly

below the Addition operator. Then define the block and enter the
expression A<-491|A>266.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<-491|A>266
7 Redefine MAT_SF, the ALARM block, to the right of the XPB

block.
Identifier MAT_SF
Unit Normal/Alarm
Description Sensor failure mixed air sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 5
Priority 3
OP Alarm text Sensor failure MAT
Alarm Processing
126 (450) TAC AB, Nov 2006

04-00030-01-en
Vista Alarm tripped Sensor failure mixed air sensor 2nd Floor South
Vista Alarm reset Sensor failure mixed air sensor 2nd Floor South
return to normal
8 Redefine MAT_HighAlarm, the PVR block, below the

MAT_Offset block.
Identifier MAT_HighAlarm
Unit °F
Description High Alarm Limit for MAT
Public
R/W (Acc.) Yes
Backup Yes
InitValue 80
9 Redefine MAT_High, the ALARM function block, to the right of

the XPB block.
Identifier MAT_High
Unit Normal/Alarm
Description High mixed air temp alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text High MAT
Alarm Processing
Vista Alarm tripped High mixed air temperature 2nd Floor South
Vista Alarm reset Mixed air temperature 2nd Floor South return
to normal
10 Redefine MAT_LowAlarm, the PVR type function block, below

the MAT_HighAlarm block.
Identifier MAT_LowAlarm
Unit °F
Description Low Alarm Limit for MAT
Public
R/W (Acc.) Yes
Backup Yes
InitValue 50
TAC AB, Nov 2006 127 (450)

04-00030-01-en
11 Redefine MAT_Low, the ALARM function block, to the right of

the XPB block.
Identifier MAT_Low
Unit Normal/Alarm
Description Low mixed air temp alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Low MAT
Alarm Processing
Vista Alarm tripped Low mixed air temperature 2nd Floor
Vista Alarm reset Mixed air temperature 2nd Floor South return
to normal
12 Locate CO2, an AI function block, in the diagram window, to the

left and vertically approximately one Fourth (quarter) from the
bottom,. Then define the block.
Identifier CO2
Unit "wc
Description
Public
R/W (Acc.)
Backup
Mod Number
Terminal ref.
Sensor 2..10 V
Time Const: 0
Initial Value: 500
Min Value: 0
Max. Value: 2000
13 Locate Mixed_Air_Dampers, an AO type function block, in the

diagram window, to the right of the FBD page and vertically
approximately midways. Then define the block.
Identifier Mixed_Air_Dampers
Unit %
Description Mixed Air Dampers
Public Yes
128 (450) TAC AB, Nov 2006

04-00030-01-en
R/W (Acc.)
Backup
Bound to Physical output
Mod Number M3
Terminal ref: Y2
Initial Value = 0
Voltage 0% 0
Voltage 100% 10
One more output block will be used, the CO2_SNVT block, a function
block of the AO type. We will locate and define it later.
Conditional Mixed Air Temperature Value
If there is a sensor failure alarm, the Mixed Air Temperature to use
should have a value of zero. Here we solve this by using an expression
block of the XPR type.
14 Locate in the diagram window an XPR expression block, to the
right of and slightly above the MAT_SF function block. Define the
block and enter the expression b?0:A. This expression will create a
block with two inputs, b, and A. Input b is a binary input and rep-
resents the alarm state of MAT_SF. Input B is an analog input and
represents the MAT.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Real
Expression b?0:A
15 Create a new node and connect the output of the MAT (the Addi-
tion operator) to input A of the XPR block.
16 Connect the output of the MAT_SF block (the ALARM block) to
input b of the XPR block.
TAC AB, Nov 2006 129 (450)

04-00030-01-en
The design concerning the mixed air temperature measurements will

now look like this:
Alarm when the Return Air CO2 experiences a Sensor

Failure
We want the possibility to calibrate the return air CO2 measurement. To
value.
17 Locate CO2_Offset, a PVR type function block, in the diagram
window, below the CO2 block (AI block). Then define the block.
Identifier CO2_Offset
Unit PPM
Description Offset for calibration of CO2
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
18 Locate CO2, an Addition operator, in the diagram window, to the

right of the AI function block. Then define the block. Select the
130 (450) TAC AB, Nov 2006

04-00030-01-en
Mode 1 for this operator, arranging one input horizontally, and the
other vertically.
Identifier CO2
Unit ppm
Description Calibrated CO2
Public Yes
Mode 2
19 Connect the output of the CO2 to the horizontal input of the Addi-
tion operator.
20 Connect the output of the CO2_Offset to the vertical input of the
Addition operator.
done using an expression in an expression block of the XPB type. Suit-
able numbers in the expression define the allowed levels.
block and enter the expression A<100|A>1200.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<100|A>1200
22 Connect the output of the CO2 block (the Addition operator) to the
input of the XPB block.
23 Locate CO2_Alarm, an ALARM function block, in the diagram
window, to the right of the XPB block. Then define the block.
Identifier CO2_Alarm
Unit Normal/Alarm
Description CO2 Alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 5
Priority 3
OP Alarm text CO2 Alarm
Alarm Processing
TAC AB, Nov 2006 131 (450)

04-00030-01-en
Vista Alarm tripped CO2 2nd Floor South Alarm

Vista Alarm reset CO2 2nd Floor South return to normal

CO2_Alarm (ALARM) block.
Breaking the rule of placing outputs to the right on an FBD page, we
locate an output block representing the calibrated CO2 measurement
value close to the input block.
25 Locate CO2_SNVT, an AO type function block, on the FBD
page, above the XPB expression block. Then define the block.
Identifier CO2_SNVT
Unit Unit=ppm
Description SNVT output of CO2
Public Yes
R/W (Acc.)
Backup
Bound to SNVT
Type ppm
Member
Name nvoCO2
Initial Value = 0
Send Yes
Delta: 0.5
Period: 60
26 Create a new node and connect the output of the CO2 (the Addi-
tion operator) to the input of the CO2_SNVT function block.
Conditional Return Air CO2 Value
If there is a sensor failure alarm, the CO2 measurement to use should
have a value of 500. Here we solve that by using an expression block of
the XPR type.
right of and slightly above the CO2_Alarm ALARM block. Then
define the block and enter the expression b?500:A. This expres-
sion will create a block with two inputs, b, and A. Input b is a
binary input and represents the alarm state of CO2_Alarm. Input B
is an analog input and represents the CO2.
Identifier
Unit
Description
Public
132 (450) TAC AB, Nov 2006

04-00030-01-en
R/W (Acc.)
Type Real
Expression b?500:A
28 Create a new node and connect the output of the CO2 (the Addi-
29 Connect the output of the CO2_Alarm block to input b of the XPR
block.
The design concerning the CO2 measurements shall now look like this:
Modulating the OA/RADamper based on Mixed Air

Temperature
Modulation of the damper position uses two controller blocks, one
block to control the position based on the mixed air temperature and
another block to control (limit) the position based on the CO2 measure-
ment value.
The modulating controller based on the mixed air temperature is a con-
troller with an analog output.
This first PIDA controller block uses operator inputs defined by PVR
function blocks for the setpoint, proportional gain and integration time.
30 Locate in the diagram window a PIDA function block, approxi-
mately three function block to the left of the Mixed_Air_Dampers
block (AO block). Then define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
ControlInt 20
Umin 0
Umax 100
TAC AB, Nov 2006 133 (450)

04-00030-01-en
Stroke Time 0
The measurement value of the PIDA controller is the conditional mixed

air temperature value.
31 Connect the output of the XPR block (the XPR block, to the right
of the MAT Addition operator) to input MV of the PIDA function
block.
The setpoint for the controller will depend on the largest terminal load
from a number of zones. This signal will be designed and connected
later. We will prepare a function block for making the signal a function
of the Max_TermLoad.
32 Locate Mixed_Air_Setpoint, a CURVE type function block, in
the diagram window, to the left of the PIDA function block. Leave
space for approximately two additional block between the CURVE
block and the PIDA block. Then define the block.
Identifier (Name) Mixed_Air_Setpoint

Unit
Description
Public Yes
R/W (Acc.)
Backup
Limit 1
Pair, list x1 0
Pair, list y1 75
Pair, list x2 50
Pair, list y2 55
Note
Use the Online help or read Section 14.8, “CURVE – Curve Function”
to learn more about the CURVE block.
33 Locate Mixed_Air_PG, a PVR type function block, in the dia-

gram window, below the Mixed_Air_SetPoint. Then define the
block.
Identifier Mixed_Air_PG
Unit % per deg F
Description Mixed Air Proportional Gain
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 16.66
134 (450) TAC AB, Nov 2006

04-00030-01-en
34 Locate Mixed_Air_Int_TC, a PVR type function block, in the

diagram window, below the Mixed_Air_PG. Then define the
block.
Identifier Mixed_Air_Int_TC
Unit seconds%
Description Mixed Air Integral Time Constant
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
35 Connect the output of Mixed_Air_SetPoint (the CURVE block) to

input SP of the PIDA function block.
In the application, the PIDA controller will need a negative value for
gain. We provide this using a Negate operator before the input.
36 Locate in the diagram window a Negate operator, to the right of
the Mixed_Air_PG (PVR) function block.
37 Connect the output of the Mixed_Air_PG block to the input of the
Negate operator.
function block.
39 Connect the output of the Mixed_Air_Int_TC block to input Td of
the PIDA function block.
In our design, the controller parameters derivative time (Td) and dead-
zone (DZ) are defined by two operator Real consts.
the PIDA function block. If appropriate, you can use mode 2 to
make the output horizontal. Then define the block.
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
41 Connect the output of the Real const (Value=0) to input Td of the

42 Locate in the diagram window a Real const operator, to the left of
the PIDA function block. Then define the block.
Identifier MAT_DZ
Unit
TAC AB, Nov 2006 135 (450)

04-00030-01-en
Description
Public
Mode 2
Value 0.5
43 Connect the output of the Real const (Value=0.5) to input DZ of

The controller function block will be in different modes, depending on
the economizer request and Mod3 communication.
We use an expression block to determine the mode to run in. The
expression a&b?1:3, used in an expression block with an integer output
(XPI), will create a function block with two binary inputs, a and b. Input
a represents the Economizer mode request. Input b represents the Mod3
communication state.
44 Locate in the diagram window an XPI expression block, in the
upper part and approximately horizontally in the middle. Enter the
expression a&b?1:3.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Integer
Expression a&b?1:3
45 Create a new node and connect the output signal from the Econo-
mizer (the XPB block on the previous FBD page) to input a of the
XPI function block.
Mod_3_Offline block (ALARM block on the VSD page, also used
on the previous FBD page) to input b of the expression block.
47 Connect the output signal from the XPI function block to input
Mod of the PIDA function block.
48 Connect the output signal from the XPR function block in the
Mixed Air temperature part to input MV of the PIDA function
block.
The value to be sent to the OA/RA damper actuator must be either the
value calculated by this PIDA controller or a controller calculating a
value based on CO2 concentration. The value to use should be the larger
of the two. We solve this using a MAX function block to select.
136 (450) TAC AB, Nov 2006

04-00030-01-en
49 Locate in the diagram window a MAX function block to the right

of the PIDA controller block.
Note
Use the Online help or read Section 14.25, “MAX – Maximum Signal
Selector” to learn more about the MAX block.
50 Connect the output of the PIDA function block to the upper input
of the MAX function block. We will connect the other input later.
Modulating the OA/RADamper based on the CO2
Concentration
Modulation of the damper position due to CO2 concentration uses
another controller with an analog output.
This PIDA controller block uses a set of operator inputs defined by the
PVR function blocks, setpoint, proportional gain, and integration time.
52 Locate in the diagram window a PIDA function block, below and
slightly to the left of the previous PIDA controller block. Then
define the block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
ControlInt 20
Umin 0
Umax 100
Stroke Time 0
53 Locate CO2_Setpoint, a PVR type function block, in the diagram

window, to the left of the PIDA function block. Leave space for
approximately two additional block between the PVR block and
the PIDA block. Then define the block.
Identifier CO2_SetPoint
Unit ppm
Description Return Air CO2 Setpoint
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 800
TAC AB, Nov 2006 137 (450)

04-00030-01-en
54 Locate CO2_PG, a PVR type function block, in the diagram win-

dow, below the CO2_Setpoint. Then define the block.
Identifier Econ\CO2_PG
Unit % per PPM
Description CO2 Proportional Gain
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 16.66
55 Locate CO2_Int_TC, a PVR type function block, in the diagram

window, below the CO2_PG., then define the block.
Identifier CO2_Int_TC
Unit seconds
Description CO2 Integral Time Constant
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
56 Connect the output of CO2_SetPoint to input SP of the PIDA

function block.
In the application, the PIDA controller will need a negative value for
gain. We provide this using a Negate operator before the input.
57 Locate in the diagram window a Negate operator, to the right of
the CO2_PG (PVR) function block.
58 Connect the output of the CO2_PG block to the input of the
Negate operator.
function block.
60 Connect the output of the CO2_Int_TC block to input Td of the
In our design, the controller parameters derivative time (Td) and dead-
zone (DZ) are defined by two Real const operators.
the PIDA function block. If approprirate, you can use mode 2 to
have the output horizontal. Then define the block.
Identifier
Unit
Description
Public
138 (450) TAC AB, Nov 2006

04-00030-01-en
Mode 2 Yes
Value 0
62 Connect the output of the Real const (Value=0) to input Td of the

the PIDA function block. Then define the block.
Identifier MAT_DZ
Unit
Description
Public
Mode 2
Value 0.5
64 Connect the output of the Real const (Value=0.5) to input DZ of

The controller function block will also be in different modes, depending
on the economizer request and Mod3 communication.
We use the same condition (the same signal) to determine which mode
to run that we used for the other PIDA controller.
65 Create a new node and connect the output signal from the XPI
function block to input Mod of the PIDA function block.
The minimum value for the degree of opening of the OA/RA Damper
is applied here but will, as the design evolves, propagate throughout the
control chain. The value is entered by the operator using a PVR function
block.
66 Locate Min_Position, a PVR type function block, in the diagram
window, below the PIDA controller block. Then define the block.
Identifier Min_Position
Unit %
Description Minimum Damper position
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 20
67 Locate in the diagram window a MAX function block to the right

of the PIDA controller block.
68 Connect the output of the PIDA function block to the upper input
of the MAX function block.
69 Connect the output of the Min_Position PVR function block to the
lower input of the MAX function block.
TAC AB, Nov 2006 139 (450)

04-00030-01-en
71 Connect the output of this latest MAX function block to the lower
input of the first MAX block on the FBD page.
To close the dampers when the Fan is not running, we add an Analog
mux operator to our design. We put it after the largest signal selected
(after the MAX function block following the temperature based control-
ler).
72 Locate in the diagram window an Analog mux operator, to the
right of the upper MAX function block.
We define the value that closes the OA/RA dampers using a constant.
73 Locate in the diagram window a Real const operator, below and
slightly to the left of the Analog Mux operator block. Then define
the block.
Identifier
Unit
Description
Public
Mode 2
Value 0
74 Create a new node and connect the output of the SFan_Status (the
DI block on the Fan Start Stop FBD page and also used on the last
FBD page) to the vertical input of the Analog mux.
75 Connect the output of the Real const operator to the lower input
(input 0) of the Analog mux block.
76 Connect the output of the Analog mux operator to the
Mixed_Air_Dampers function block (AO block).
Assigning the Module Name "Econ"
The function blocks on this FBD printable page are also a set of signals
we want to treat as signals in the common module called Econ.
name Econ.
140 (450) TAC AB, Nov 2006

04-00030-01-en
Now that this is finished, the page of the function block diagram should
look like this:

of the printable page
This will open the FBD in the simulation window. If the line of buttons
is now longer than you see on the display, use the scroll bar to view
them all.
The text shown on each button is brief, the full name is shown on the
status bar down to the left.
Testing the Mixed Air Temperature sensor Failure Alarm
The alarm should be generated when the value is outside the rangeof
-491 to 266.
2 Click Execute and observe the value of the MAT_SF block (the
3 Click the Econ\MAT_Sensor button to the left to display an Ana-
4 Click the Econ\MAT_Sensor button again and enter the original
TAC AB, Nov 2006 141 (450)

04-00030-01-en
5 Click the Econ\MAT_Sensor button to the left to display an Ana-

log input form for entering a value. Enter a value of -492 and
6 Click the Econ\MAT_Sensor button again and enter the original
Testing the Mixed Air Temperature Low Alarm
7 Click the Econ\MAT_Sensor button again and enter a value
below the limit of 50. Enter a value of 49 and observe the
MAT_Low block, it should change to 1 (on) after 120 execution
intervals.
8 Click the Econ\MAT_Sensor button to enter the original value of
9 Click the Econ\MAT_Sensor button again and enter a value
below the limit triggering sensor failure. Enter a value of -492,
and observe the MAT_Low block, it should remain 0 (off) after
Testing the Mixed Air Temperature High ALarm
10 Click Execute and observe the value of the MAT_High block (the
11 Click the Econ\MAT_Sensor button to enter a value above the
limit of 80. Enter a value of 81 and observe the Alarm block
again. It should change to 1 (on) after 120 execution intervals.
12 Click the Econ\MAT_Sensor button to enter the original value of
Testing the Return Air CO2 Alarm
100 to 1200.
13 Click Execute and observe the value of the CO2_Alarm block (the
ALARM block) again. It should be 0 (off).
14 Click the Econ\CO2 button to the left to display an Analog input
form for entering a value. Enter a value of 1201 and observe the
Alarm block again, it should change to 1 (on) after 120 execution
intervals.
15 Click the Econ\CO2 button again and enter the original value of
500. Observe the Alarm block again. It should change to 0 (off)
142 (450) TAC AB, Nov 2006

04-00030-01-en
16 Click the Econ\CO2 button to the left to display an Analog input

form for entering a value. Enter a value of 99 and observe the
Alarm block again. It should change to 1 (on) after 120 execution
intervals.
17 Click the Econ\CO2 button again and enter the original value of
500. Observe the Alarm block again. It should change to 0 (off)
Testing the Return Air CO2 Signal
18 Click Execute, if execution has not already started.
19 Click the Econ\CO2 button again and enter a value of 800.
Observe the XPR block, to the right of the CO2 Alarm block,
again. It should have the value of the CO2 sensor (plus offset, if
any).
If there is a CO2 alarm, the value used by the application should be 500.
Observe the XPR block to the right of the CO2 Alarm block,
again. After the alarm delay, it will have a value of 500.
Observe the XPR block, to the right of the CO2 Alarm block,
againS. It should, after the short delay, have the value of the CO2
sensor (plus offset, if any).
Testing the control based on Temperature
23 Click the Econ\MAT_Sensor button to enter a value of 75.
24 Click Execute, if execution has not already started, and observe
the upper PIDA controller block. It should have a value of 0 (zero)
due to the mode it is running in. It is running mode 3, i.e. control-
ler output to minimum signal level.
We will have to arrange for it to have run in mode 1. The mode is deter-
mined by the XPI block in the upper part of the FBD page.
A MOD3 offline alarm will prevent the controller from running in mode
1, but When the VSD\MOD3 button has not been depressed, it should
not create the alarm situation.
We will also need the Economizer on signal to be true.
To generate this, we will need measurement values that will provide a
sufficient calculation, plus a Sfan_Status signal. The initial values of the
inputs will provide a calculation of Economizer mode as true. We will
arrange for the SFan_Status signal.
Sfan state and observe once again the value of the XPI block. It
should now change to 1 (on). The PIDA controller should calcu-
late an output other than zero.
TAC AB, Nov 2006 143 (450)

04-00030-01-en

Observe the PIDA block. The output should, within a few execu-
tion intervals, be 100 (maximum signal level).
tion intervals, be 0 (minimum signal level).
28 Click the Econ\MAT_Sensor button to enter a value of 53.6.
tion intervals, calculate a higher signal level.
As the PIDA is defined with the TD parameter zero, so it will not con-
tinue to increase. A new, larger value, e.g. 53.8, will give a slightly
higher output level.
Testing the control based on the CO2 Level
The controller mode is determined by the same signal as the previous
controller, so now it should still be 1 (on).
29 Click the Econ\CO2 button again and enter a value of 500 and
observe the PIDA block in the lower part of the FBD. The output
should be 0 (zero) due to the low measurement value. The setpoint
is 800.
30 Click the Econ\CO2 button again and enter a value of 80, and
observe the PIDA block. The PIDA controller should now calcu-
This PIDA is also defined with the TD parameter zero, so it will not con-
tinue to increase. A new, larger value, e.g. 802, will give a slightly
higher output level.
31 Click the Econ\CO2 button again and enter a value of 800.5 and
late a new value.
observe the PIDA block. The PIDA controller should retain the
previous value. The new value lies within the deadzone.
With the existing parameters, we cannot verify that the controller output
is maximized in the MAX block.
Testing the governing control level.
34 Observe the MAX block located to the right of the temperature
PIDA controller. This block should have the higher of the two con-
trollers. The temperature controller, using the 53.6 as input level,
should calculate a slightly higher output level than the CO2 con-
troller.
144 (450) TAC AB, Nov 2006

04-00030-01-en
observe the MAX block. It should now have taken the value from
the CO2 controller. This is also the value of the AO.
36 Release the SFan\SFan_Status button to the left and check that
both controllers stops (calculates zero outputs) and that the value
of the real constant (0) is used for the AO block.
TAC AB, Nov 2006 145 (450)

04-00030-01-en
4.10 The DX Cooling Control

In this part, we will design the part of the FBD that handles the DX
Cooling Control. Our design will include the calculation of two signals
representing the cooling demand, the C1 Fan Speed, and a Cooling Fan
Speed. Cooling is provided by four chiller stages. We will also provide
the logic for alarms triggered by sensor failures and when measurement
values are low or high.
The complete solution for the cooling will use two printable pages. In
this first part we will design the calculation of the fan speeds. In a sec-
ond page, we will design the logic for activating the four cooling stages.
We can identify some mechanisms forming groups of function blocks.
These are:
• Discharge Air Temperature measurement processing
• Terminal load processing.
• Control functions.
• Demand determination.
• Starting and stopping the Cooling Stages.
We will create the design by forming groups of function blocks for the
identified mechanisms. These mechanisms are: discharge air tempera-
ture measurement processing, terminal load processing, control,
demand determination, starting and stopping the Cooling Stages.
page on the screen.
signals in a common module called Cooling.
The design of the Discharge Air temperature will be identical to the
design we created for the Bldg Static Pressure, so we can use the method
to Copy and Paste the required function blocks.
1 Mark the AI block, the PVB, the XPB, and the ALARM blocks we
created in the design for Relief Damper/Fan Control.
146 (450) TAC AB, Nov 2006

04-00030-01-en
2 Use Edit/Copy and Edit/Paste to duplicate the blocks onto the

new FBD page. Locate the AI type function block, to the left and
vertically approximately one third of the way from the top.
Note that all copies of blocks with names and parameters must be
checked and replaced when necessary. All XPB blocks are identical.
Redefine all the necessary copied blocks.
3 Redefine DAT_Sensor, the AI type function block.
Identifier DAT_Sensor
Unit °F
Description
Public
R/W (Acc.)
Backup
Mod Number M3
Terminal ref. B1
Time Const: o
Initial Value: 55
4 Redefine DAT_Offset, the PVR block, below the DAT_Sensor

block.
Identifier DAT_Offset
Unit °F
Description Offset for calibration of DAT
TAC AB, Nov 2006 147 (450)

04-00030-01-en
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
5 Redefine DAT, the Addition operator.
Identifier DAT
Unit °F
Description Discharge Air Temperature
Public
Mode 2
6 Redefine DAT_SF, the ALARM block, to the right of the XPB

block.
Identifier DAT_SF
Unit Normal/Alarm
Description Sensor failure discharge air sensor
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 5
Priority 3
OP Alarm text Sensor failure DAT
Alarm Processing
Vista Alarm tripped Sensor failure discharge air sensor 2nd Floor
South
Vista Alarm reset Sensor failure discharge air sensor 2nd Floor
7 Redefine DAT_HighAlarm, the PVR block below the

MAT_Offset block.
Identifier DAT_HighAlarm
Unit °F
Description High Alarm Limit for DAT
Public
R/W (Acc.) Yes
Backup Yes
InitValue 80
148 (450) TAC AB, Nov 2006

04-00030-01-en
8 Redefine DAT_High, the ALARM block, to the right of the XPB

block.
Identifier DAT_High
Unit Normal/Alarm
Description High discharge air temp alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text High DAT
Alarm Processing
Vista Alarm tripped High discharge air temperature 2nd Floor South
Vista Alarm reset Discharge air temperature 2nd Floor South
return to normal
9 Redefine DAT_LowAlarm, the PVR block, below the

MAT_HighAlarm block.
Identifier DAT_LowAlarm
Unit °F
Description Low Alarm Limit for DAT
Public
R/W (Acc.) Yes
Backup Yes
InitValue 45
10 Redefine DAT_Low, the ALARM block, to the right of the XPB

block.
Identifier DAT_Low
Unit Normal/Alarm
Description Low discharge air temp alarm
Public
R/W (Acc.)
Backup
Delay On 120
Delay Off 120
Priority 3
OP Alarm text Low DAT
Alarm Processing
Vista Alarm tripped Low discharge air temperature 2nd Floor South
TAC AB, Nov 2006 149 (450)

04-00030-01-en
Vista Alarm reset Discharge air temperature 2nd Floor South

return to normal
11 Locate FanSpeed, an AI type function block, in the diagram win-

dow, to the left and vertically approximately midways. Then
define the block.
Identifier FanSpeed
Unit %
Description Fan Speed Feedback from VFD
Public Yes
R/W (Acc.)
Backup
Mod Number M4
Terminal ref. U3
Sensor 0..10 V
Time Const: 0
Initial Value: 0
Min Value: 0
Max. Value: 100
12 Locate VAV_4:1_Term_Load, an AI type function block, in the

diagram window, below the FanSpeed block. Then define the
block.
Identifier VAV_4:1_Term_Load
Unit %Load
Description Terminal Load FPB-4:1 Software
Public Yes
R/W (Acc.)
Backup
Bound to SNVT
Type lev_percent
Member
Name nvi4:1_TermLoad
Initial Value = 0
Poll Yes
Period: 60
We will use five more blocks like VAV_4:1_Term_Load, representing

other terminal units, but we will make copies of a partial design and
rename the blocks later on.
150 (450) TAC AB, Nov 2006

04-00030-01-en
Conditional DAT Air Temperature Value

If there is a sensor failure alarm, the DAT_Air Temperature to use
should have a value of 50. Here we solve this using an expression block
of the XPR type.
right of and slightly above the DAT_SF function block. Then
define the block and enter the expression b?50:A. This expression
will create a block with two inputs, b, and A. Input b is a binary
input and represents the alarm state of DAT_SF. Input B is an ana-
log input and represents the DAT.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Real
Expression b?50:A
14 Create a new node and connect the output of the DAT (the Addi-
15 Connect the output of the MAT_SF block (the ALARM block) to
input b of the XPR block.
The design concerning the DAT air temperature measurements shall
now look similar to this:
TAC AB, Nov 2006 151 (450)

04-00030-01-en
Determining the Terminal Load.

The maximum load from the six terminal units VAV_4:x, is a part of the
cooling demand. We will determine the highestvalue, using a series of
MAX selection blocks.
16 Locate VAV_4:2_Term_Load, an AI type function block, in the
diagram window, to the right of and below the previous
VAV_4:1_Term_Load,. Then define the block.
Unit %Load
Description Terminal Load FPB-4:2 Hardware
Public Yes
R/W (Acc.)
Backup
Bound to SNVT
Type lev_percent
Member
Initial Value = 0
Poll Yes
Period: 60
17 Locate in the diagram window, to the right of

VAV_4:2_Term_Load, a MAX function block.
18 Connect the output of VAV_4:1_Term_Load to the upper input of
the MAX function block.
19 Connect the output of VAV_4:2_Term_Load to the lower input of
the MAX function block.
20 Copy and paste, twice, the two terminal load blocks including the
MAX function block, and locate them below the previous set.
Redefine the added function blocks. VAV_4:3_Term_Load,
VAV_4:4_Term_Load, VAV_4:5_Term_Load, and
VAV_4:6_Term_Load.
Description Terminal Load FPB-4:3 Hardware
Description Terminal Load FPB-4:4 R&D Services
Description Terminal Load FPB-4:5 Software Dev.
152 (450) TAC AB, Nov 2006

04-00030-01-en
Description Terminal Load FPB-4:6 ASG
21 Locate in the diagram window another MAX function block, to

the right of and vertically between the upper two MAX function
blocks.
22 Connect the output of the upper left MAX block to the upper input
of the new MAX function block.
23 Connect the output of the left MAX block, in the middle, to the
lower input of the new MAX function block.
24 Locate in the diagram window the Max_TermLoad, also a MAX
function block, to the right of and slightly below the most recent
MAX function blocks. Name the block.
Identifier MaxTermLoad
Unit %Load
Description Maximum Terminal Load
Public Yes
R/W (Acc.)
Backup
25 Connect the output of the MAX block, up to the left, to the upper
input of the Max_TermLoad function block.
26 Connect the output of the MAX block, down to the left (the uncon-
nected one), to the lower input of the Max_TermLoad function
block.
TAC AB, Nov 2006 153 (450)

04-00030-01-en
If done successfully, this part of the design will look like this:
Generating a Setpoint value for the OA/RA dampers

27 Connect the output of MaxTermLoad (the lower right MAX block)
to the input of the CURVE block we designed in the previous dia-
gram page.
Determining the C1 Fan Speed Signal
The chiller stages are controlled by a load-dependent C1 Fan Speed sig-
nal. The inputs for determining this signal are the actual fan speed, the
discharge air temperature, and the max. terminal load. The basis for this
is the actual fan speed, the discharge air temperature and the max. ter-
minal load compensating (resetting) the value. The signal is calculated
in an expression block, using the sum of the two terms. The values for
the levels where the signal is compensated are entered as numbers in the
expression. This means that these levels can only be changed by repro-
gramming and downloading the altered application.
The first term (expression C>90? C-90+B:B) adds the amount by which
MaxTerm_Load, exceeds the level 90. If C, the load, is 90 or below, the
term will adopt the value of FanSpeed signal.
The second term (expression A<50? (A-50)*5:0) adds five times the
amount by which the discharge air temperature lies below 50. Because
of the expression, the difference will be a value less than zero (nega-
tive). If A, the temperature, is 50 or higher, then the term adds 0 (zero).
28 Locate Compressor_Staging, an XPR expression block, in the
diagram window, in the middle of the page. Then define the block
and enter the expression (C>90?C-90+B:B)+(A<50?(A-50)*5:0).
Identifier Compressor_Staging
Unit
154 (450) TAC AB, Nov 2006

04-00030-01-en
Description
Public No
R/W (Acc.)
Type Real
Expression (C>90?C-90+B:B)+(A<50?(A-50)*5:0)
This expression will create a block conatining three analog inputs, A, B,

and C. Input A represents the conditional selected discharge air temper-
ature. Input B represents the FanSpeed (AI). Input C represents Max-
TermLoad (the rightmost MAX block).
29 Connect the output of the conditionally selected discharge air tem-
perature signal (the uppermost XPR block) to input A of the XPR
block.
30 Connect the output of the FanSpeed (the AI block) to input B of
the XPR block.
31 Create a new node and connect the output of the DAT (the Addi-
32 Create a new node and connect the output of the MaxTermLoad
(the lower right MAX block) to input C of the XPR block.
The output from this XPR block will be used as is during the next part
(page) of this design. We will also use the signal, or a value of zero, to
determine the Cooling Fan Speed. The value to use is dependent on
whether economizer mode is on or off.
33 Locate in the diagram window an Analog mux operator, approxi-
mately in the center of the page.
Identifier
Unit
Description
Public
Mode 2
34 Locate in the diagram window a Real const operator, to the left

of the Analog mux operator. Then define the block.
Identifier
Unit
Description
Public
Mode 2
Value 0
35 Connect the output of the Real const block (Value=0) to the upper
horizontal input (1) of the Analog mux operator.
TAC AB, Nov 2006 155 (450)

04-00030-01-en
36 Connect the output of Compressor_Staging (the XPR block) to the

lower horizontal input (0) of the Analog mux operator.
37 Create a new node and connect the Economizer On signal (used in
the previous page) to the control input of the Analog mux operator
block (the vertical one).
Assigning the Module Name "Cooling"
we want to treat as signals in the common module called Cooling.
38 Mark all blocks on the FBD page and assign them the module nafe
Cooling.
When finished, this page should look like this:

This will open the FBD in the simulation window with the inputs but-
tons located to the left. The buttons are sorted in alphabetical order, use
the scroll-bar to see them all.
156 (450) TAC AB, Nov 2006

04-00030-01-en
Testing the Pressure Sensor Failure Alarm

-49 to 266.
2 Click Execute and observe the value of the DAT_SF block (the
3 Click the Cooling\DAT_Sensor button to the left to display an
observe the alarm block again. It should change to 1 (on) after 120
4 Click the Cooling\DAT_Sensor button again and enter the origi-
nal value of 55. Observe the alarm block again. It should change
to 0 (off) after another 5 execution intervals.
5 Click the Cooling\DAT_Sensor button to the left to display an
Analog input form for entering a value. Enter a value of -48 and
observe the alarm block again. It should change to 1 (on) after 120
6 Click the Cooling\DAT_Sensor button again and enter the origi-
nal value of 55. Observe the alarm block again. It should change
Testing the Pressure level Low Alarm.
7 Click the Cooling\DAT_Sensor button again and enter a value
below the limit 45. Enter a value of 44 and observe the
BLDG_Static_Low block, it should change to 1 (on) after 120
8 Click the Cooling\DAT_Sensor button to enter the original value
of 55 and observe the alarm block again. It should return to 0 (off)
9 Click the Cooling\DAT_Sensor button again and enter a value
below the level for sensor failure. Enter a value of -49, and
observe the DAT_Low block, it should remain 0 (off) also after
Testing the Pressure level High ALarm.
10 Click Execute and observe the value of the DAT_High block (the
11 Click the Cooling\DAT_Sensor button to enter a value above the
limit 80. Enter a value of 81 and observe the alarm block again. It
should change to 1 (on) after 120 execution intervals.
12 Click the Cooling\DAT_Sensor button to enter the original value
of 55 and observe the alarm block again. It should return to 0 (off)
TAC AB, Nov 2006 157 (450)

04-00030-01-en
Testing the MAX Terminal Load Selection.

Testing this part of the design, using the simulation mode in Menta, will
mostly be about testing the signal selection. On a running installation,
there will be other factors like errors when naming the SNVT variables,
etc. The application must be tested in an operational network.
13 Click Execute, if execution it is not already started, and observe
the rightmost MAX function block. It should have a value of 0
(zero).
14 Click the Cooling\VAV4:1_Term_Load button to the left to dis-
play an Analog input form for entering a value. Enter a value of 1
and observe the MAX block again. It should now have a value of
1.
15 Click some Cooling\VAV4:x_Term_Load buttons and enter dif-
ferent values. Observe the MAX block and verify that, irrespective
of the values you enter, the block adopts the largest of these
entered values.
Testing the C1 Fan Speed Signal Calculation.
16 Make sure that all Cooling\VAV4:x_Term_Load values are 90 or
less.
17 Click the Cooling\DAT_Sensor button and enter a value of 55 to
make sure that the value is over 50.
18 Click Execute, if execution is not already started.
19 Click the Cooling\FanSpeed button to the left to display an Ana-
observe the XPR block again. It should now have a value of 25.
20 Click any Cooling\VAV4:x_Term_Load button and enter a value
of 91. Observe the XPR block. The block should have a value of
26, (91-90 added to the 25).
21 Click the Cooling\DAT_Sensor button and enter a value of 49.
Observe the XPR block. The block should have a value of 21, (5
times (49-50), subtracted from the 26).
Testing the Cooling Fan Speed Signal Selection.
The output from the Analog mux is not directly viewable. We can tem-
porarily add a function block just for simulation purposes.
22 Use the command Options/Edit to activate the editing mode.
23 Locate in the diagram window a DELR block, to the right of the
Analog mux operator.
24 Connect the output of the Analog mux operator to the input of the
25 Return to the simulation mode of Menta, Options/Simulate (F12).
158 (450) TAC AB, Nov 2006

04-00030-01-en
26 Click Execute and observe the DELR block. It should show the
previous value 21.
If Economizer mode is enabled, the signal should be zero. We remem-
ber from previous tests, that simulating economizer mode can be
obtained by adjusting the SFan_Status.
Sfan state and observe the DELR block again. It should now have
a value of 0 (zero).
After finishing the test, we must remember to remove the DELB block.
28 Use the command Options/Edit to obtain editing mode and
remove the DELR block to the right of the Analog mux operator.
TAC AB, Nov 2006 159 (450)

04-00030-01-en
4.11 The DX Cooling Control Logic

In this part, we will continue designing the DX Cooling Control. Our
design will include stepping the four cooling stage outputs. Stepping is
based on the level of the control signal C1 Fan Speed, together with a
derivative of the same signal Cooling Fan Speed. Activation is achieved
using hystereses and the stages are equipped with adjustable minimum
on and off times. There is also a delay between the activation of each
stage.
These are:
• Starting and stopping the separate Cooling Stages.
While working with our design, we will create a combination of func-
tion blocks for a part of the design and then, using copy and paste, reuse
this part for the remainder of the design work.
page on the screen.
We will also make the function blocks on this FBD printable page sig-
nals in the common module called Cooling.
1 Locate C1_Status, a DI type function block, in the diagram win-
dow, to the left and approximately one third from the top. Then
define the block.
Identifier C1_Status
Unit
Description Status of Compressor 1
Public Yes
R/W (Acc.)
Backup NO
Bound to Physical input (Digital input)
Mod Number M1
Term. Ref X1
Initial Value = Off
Normally Open = 1
We will use three more blocks like the C1_Status, representing the indi-
cations of other chillers, but we will make copies of a partial design and
rename the added blocks later on.
160 (450) TAC AB, Nov 2006

04-00030-01-en
2 Locate C1_Start_Stop, a DO type function block, in the diagram

window, in the upper right corner. Then define the block.
Identifier C1_Start/Stop
Unit
Description Compressor 1 Start Stop Circuit
Public Yes
R/W (Acc.) RO
Backup
Mod Number M2
Term. Ref K1
Initial Value = Off
We will also use three more blocks like the C1_Start_Stop, but we will
later make copies of a partial design and rename the added blocks later
on.
The first cooling stage shall be activated when the control signal has
reached 60% and be deactivated when the signal has returned to 55%.
We solve this by using a HYST function block.
3 Locate C1_2P, a HYST function block, in the diagram window,
horizontally slightly to the left of the center and vertically approx-
imately one block from the top. Entering names (text strings) in
the Activate and Deactivate boxes, will create constants for these
parameters. Then define the block and the Constants.
Identifier C1_2P
Unit
Description
Public
R/W (Acc.)
Backup
Activate C1_Start_SP
Deactivate C1_Stop_SP
TAC AB, Nov 2006 161 (450)

04-00030-01-en
Constant Start
Identifier C1_Start_SP
Value 60
Unit %
Description Speed at which C1 starts
Public Yes
Constant Stop
Identifier C1_Stop_SP
Value 55
Unit %
Description Speed at which C1 stops
Public Yes
Note here the use of named constants for the Activate and Deactivate
parameters. This enables the operator to easily access the values if
needed.
Giving the chiller stage necessary minimum and maximum RATINGS?
is prepared using two PULSE blocks, one for each setting. The PULSE
blocks generates a binary signal with the defined time. These signals,
once triggered, are used to latch/lock the stage in the desired state. The
values for the settings are entered via two PVR function blocks.
We start with creating the signal (pulse) defining the minimum on time.
4 Locate C1_Min_On, a PVR function block, in the diagram win-
dow, to the right of and slightly above the HYST function block,.
Identifier C1_Min_On
Unit Seconds
Description Compressor 1 Min. On Time
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 300
5 Locate in the diagram window a PULSE function block, to the

right of the C1_Min_On function block.
6 Connect the output of the C1_Min_On block (the PVR block) to
input pl (pulse length) of the PULSE function block.
The pulse for minimum on time works via a signal selector, a Digital
mux operator to select a steady on state value.
162 (450) TAC AB, Nov 2006

04-00030-01-en
7 Locate in the diagram window an Digital mux operator, to the

right of the PULSE function block and vertically aligned with the
HYST function block.
8 Locate in the diagram window an Binary const operator, to the
left of the Digital mux operator. You can use mode 2 to have the
output from the block horizontally. Then define the block.
Identifier
Unit
Description
Public
Mode 2 Yes
Value 1
Note
Use the Online help or read Section 16.1, “Constants” to learn more
about the Binary const block.
9 Connect the output of the Binary const operator (Value= 1) to the

upper horizontal input (1) of the Digital mux.
10 Connect the output of the C1_2P (the HYST function block) to the
lower horizontal input (0) of the Digital mux operator.
Now we continue with creating the signal (pulse) defining the minimum
off time.
11 Locate C1_Min_Off, a PVR function block, in the diagram win-
dow, to the right of and slightly below the HYST function block.
Identifier C1_Min_Off
Unit Seconds
Description Compressor 1 Min. Off Time
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 300
12 Locate in the diagram window a PULSE function block, to the

right of the C1_Min_Off function block,.
13 Connect the output of the C1_Min_Off block (the PVR block) to
input pl (pulse length) of the PULSE function block.
The pulse for minimum on time works via another signal selector, an
Analog mux operator to select a steady off state value.
14 Locate another Digital mux operator in the diagram window, to
the right of the previous Digital mux operator.
TAC AB, Nov 2006 163 (450)

04-00030-01-en
15 Locate in the diagram window an Binary const operator to the

left of the new Digital mux operator. You can use mode 2 to have
the output from the block horizontally. Then define the block.
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
16 Connect the output of the Binary const operator to the upper hori-
zontal input (1) of the Digital mux.
17 Connect the output of the previous Digital mux operator to the
lower horizontal input (0) of the Digital mux operator.
18 Connect the output of the lower PULSE function block (the one in
the Min_Off line of blocks), to input pl (pulse length) of the
PULSE function block.
19 Connect the output of the Digital mux operator to the
C1_Start_Stop function block (DO block), to the right.
Now we will provide the triggering signals, by generating the two
pulses. The minimum on condition is to apply every time the C1_Status
changes to true (on). The minimum off condition is to apply every time
the C1_Status changes to false (off). We use the C1_Status signal
directly connected to trigger the min. on pulse and using an inverted
state to trigger the min. off pulse.
20 Locate in the diagram window a NOT function block to the left of
the PULSE function block (in the Min_off line).
21 Connect the output of the NOT function block to input t (trigger)
22 Connect the output of C1_Status (DI function block) to the input
of the NOT function block.
23 Create a new node and connect the C1_Status signal to input t of
the upper PULSE function block as well (the PULSE block in the
Min. On chain).
Now, we also want an alarm when the state input does not match the
Start_Stop output.
24 Locate C1_Alarm, an ALARM function block, in the diagram
window, to the left and below the C1_Start_Stop function block.
Identifier C1_Alarm
Unit Normal/Alarm
Description Proofing Alarm Compressor 1
164 (450) TAC AB, Nov 2006

04-00030-01-en
Public
R/W (Acc.)
Backup
Delay On 20
Delay Off 0
Priority 1
OP Alarm text 4A-C1 Alarm
Alarm Processing
Vista Alarm tripped 4A-C1 Alarm Tripped
Vista Alarm reset 4A-C1 Alarm Reset
25 Locate in the diagram window an XOR operator to the left of the

C1_Alarm (the ALARM block). Select the Mode 2 to arrange both
inputs vertically.
Note
Use the Online help or read Section 14.59, “XOR – Exclusive OR
Gate” to learn more about the XOR block.
26 Connect the output of the XOR operator to the C1_Alarm function

block.
27 Create a new node and connect the C1_Start_Stop (DO block) to
the upper vertical input of the XOR operator.
28 Create a new node and connect the C1_Status signal to the lower
vertical input of the XOR operator.
When this is done, the current part of the design should look like this.
You might want to adjust the positions of the blocks. We are going to
re-use the layout by copying and pasting.
To create the diagram part of the C2 cooling stage, we copy all the func-
tion blocks and paste the duplicate below the existing part.
29 Select all blocks and use Edit/Copy followed by an Edit/Paste
command.
As the duplicates are complete copies with same names and parameters,
we must make sure they are redefined.
30 Redefine all necessary names and parameters in the duplicate
blocks, the C2 line of blocks.
TAC AB, Nov 2006 165 (450)

04-00030-01-en
DI:
Unit
Public Yes
R/W (Acc.)
Backup
Bound to Physical input
Mod Number M2
Term. Ref X2
Initial Value = Off
Normally Open = 1
HYST:
Identifier C2_2P
Unit
Description
Public
R/W (Acc.)
Backup
Const Start:
Value 70%
Unit %
Public Yes
Const Stop:
Value 65%
Unit %
Public Yes
PVR Min. Off:
Unit Seconds
166 (450) TAC AB, Nov 2006

04-00030-01-en

Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 300
TAC AB, Nov 2006 167 (450)

04-00030-01-en
PVR Min On:
Unit Seconds
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 300
ALARM:
Identifier C2_Alarm
Unit Normal/Alarm
Public
R/W (Acc.)
Backup
Delay On 20
Delay Off 0
Priority 1
Alarm Processing
DO:
Unit
Public Yes
R/W (Acc.)
Backup
Mod Number M2
Term. Ref K2
Initial Value = Off
The starting condition for stage C2 is the level of the control signal
Cooling Fan Speed and a delayed signal reporting that stage C1 has
been requested to start.
31 Locate in the diagram window an Analog mux operator to the
left of the C2__2P (the HYST block). Select the Mode 1 to have
the vertical control input coming from the top of the block.
168 (450) TAC AB, Nov 2006

04-00030-01-en
32 Connect the output of the Analog mux operator to the input of the
C2_2P function block (the HYST block).
33 Connect the Cooling Fan Speed signal (the output of the Analog
mux operator in the previous FBD page) to the upper horizontal
input (1) of the current Analog mux operator.
34 Locate in the diagram window an Integer const operator to the
left of the Analog mux operator. You can use mode 2 to have the
output from the block horizontally. Then define the block.
Identifier
Unit
Description
Public
Mode 2 Yes
Value 0
Note
Use the Online help or read Section 16.1, “Constants” to learn more
about the Integer const block.
35 Connect the output of the Integer const operator (Value=0) to the

lower horizontal input (0) of the current Analog mux operator.
We use a delay function on the C1 start request signal.
of and vertically above the Analog mux operator. Then define the
block.
Identifier
Unit
Description
Public
R/W (Acc.)
Backup
Delay On 300
Delay Off 0
37 Connect the output of the DELAY function block to the vertical

input (the control input) of the Analog mux operator.
TAC AB, Nov 2006 169 (450)

04-00030-01-en
The finished line of function blocks for C2 should look like this:
We are now well prepared to continue with the chain of blocks for the
C3 stage. Again we use the Copy and Paste function.
38 Select all blocks, including the added Delay, the Analog mux the
constant, for the C2 line of blocks and use Edit/Copy.
39 Using Edit/Paste, locate and make a duplicate, located below the
C2 line of blocks.
As the duplicates are complete copies with the same names and param-
eters, we must make sure they are redefined where it is needed.
170 (450) TAC AB, Nov 2006

04-00030-01-en
DI:
Public Yes
Mod Number M2
Term. Ref X3
HYST:
Identifier C3_2P
Const. Start:
Value 80%
Const. Stop:
Value 75%
PVR Min. Off:
Unit Seconds
InitValue 300
PVR Min On:
Unit Seconds
InitValue 300
ALARM:
Identifier C3_Alarm
TAC AB, Nov 2006 171 (450)

04-00030-01-en
DO:
Mod Number M2
Term. Ref K3
41 Now when you are geared up, make one more duplicate for the C4
line of blocks.
42 Using Edit/Paste again, locate and make another duplicate, located
below the C3 line of blocks.
As the duplicates are complete copies with same names and parameters,
we must make sure they are redefined.
172 (450) TAC AB, Nov 2006

04-00030-01-en
DI:
Public Yes
Mod Number M2
Term. Ref X4
HYST:
Identifier C4_2P
Const. Start:
Value 90%
Const. Stop:
Value 85%
PVR Min. Off:
Unit Seconds
InitValue 300
PVR Min. On:
Unit Seconds
InitValue 300
ALARM:
Identifier C4_Alarm
TAC AB, Nov 2006 173 (450)

04-00030-01-en
DO:
Mod Number M2
Term. Ref K4
Assigning the Module Name "Cooling"

we want to treat as signals in the common module called Cooling.
name Cooling.
When finished, this page should look similar to this:

necessary use the Zoom/Zoom out a couple of times to see most
tons located to the left. The buttons are sorted in Types and Alphabetical
order within the types. Use the scroll-bar to see them all.
174 (450) TAC AB, Nov 2006

04-00030-01-en
Testing the C1 Start, Stop, and Alarm.
2 Click the Cooling\FanSpeed button to the left to display an Ana-
observe the HYST block. It should immediately be 0 (off).
Observe the C1_Start_Stop block (the DO block), which should
also be 0 (zero).
3 Click the Step button and observe the C1_2P block (the HYST
block). It should be 0 (off). Observe the C1_Start_Stop block (the
DO block). It should also be 0 (zero).
The level of the C1_Fan_Speed signal is 55. The level where C1 starts
is 60. It stops at 55.
4 Click the Cooling\FanSpeed button and enter a value of 60.
5 Click the Step button and observe the HYST block again. It
should immediately be 1 (on). The C1_Start_Stop block (the DO
block) should remain at 0 (zero).
Because of our design, we will have to wait for the 300 min.off time
before the first start.
6 Use the Command/Execute n Times... and run 295 execution
intervals.
7 Click the Step button at least 6 times and observe the
C1_Start_Stop block (the DO block). It should have a state of 1
(on) after 300 execution intervals. Observe the C1_Alarm block. It
should have a state of 0.
Testing the Alarm
8 Click the Step button another 20 times and observe the C1_Alarm
block. It should now have a state of 1 (on).
9 Click the Cooling\C1_Status button to simulate the running indi-
cation of C1.
10 Click the Step button again and observe the ALARM block, it
should return to 0 (off) state immediately.
Testing the Stop
11 Keep the Execution button depressed for more than 600 execu-
tion intervals and verify that the C1_Start_Stop block remains on.
Observe the HYST block and the C1_Start_Stop block. They
should both immediately be 0 (off).
TAC AB, Nov 2006 175 (450)

04-00030-01-en
Testing the Restart

A restart of C1 is not allowed until 300 execution intervals have
elapsed.
13 Click RST to release the Execute button and reset the cycle
counter.
Observe the HYST block, it should immediately be 1 (on). The
C1_Start_Stop block should be 0 (off).
15 Use Command/Execute n Times... and run 100 execution inter-
vals. Observe the C1_Start_Stop block, it should be 0 (off)
intervals.Observe the C1_Start_Stop block, it should now be 1
(on).
17 Click the Cooling\C1_Status button to simulate the running indi-
cation of C1.
19 Click Step and observe the HYST block and the C1_Start_Stop
block. The HYST block should immediately be 0 (off) and the
C1_Start_Stop should be 1 (on).
intervals. Observe the C1_Start_Stop block, it should now be 0
(off).
21 Release the Cooling\C1_Status button to end simulating the run-
ning indication of C1.
Testing the C2 Start, Stop, and Alarm, No Economizer Mode
The C2 differ from the C1 i some aspects:
• Another control signal is used, conditional to Economizer mode
usage.
• There are different levels where the compressor starts and stops.
• There is a delay between the start of C1 and the start of C2 (300s)
Otherwise the design is identical. Only the test of the differences is
described here.
To start compressor 2 the compressor 1 must be ordered to start.
The level where the C2 starts is 70. It stops at 65.
22 Click RST to release the Execute button and reset the cycle
counter.
24 Click Step and observe the HYST block in the line for C2. It
should immediately be 1 (on). Observe the DELAY block in the
C2 line. It should be 0 (off).
176 (450) TAC AB, Nov 2006

04-00030-01-en

intervals.
26 Click Step and observe the DELAY block in the C2 line. It should
have changed to 1 (on).
27 Observe the C2_2P (the HYST block) in the C2 line. It should be 0
(off).
29 Click Step and observe C2_2P (the HYST block) in the C2 line. It
should have changed to 1 (on).
should have changed to 0 (off).
Testing the C3 Start, Stop, and Alarm, No Economizer Mode
The level where C3 starts is 80. It stops at 75.
intervals and observe C3_2P (the HYST block) in the C3 line. It
should now have changed to 1 (on).
Testing C4 Start, Stop, and Alarm, No Economizer Mode
The level where C4 starts is 90. It stops at 85.
37 Use Command/Execute n Times... and run 300 execution inter-
vals and observe C4_2P (the HYST block) in the C4 line. It should
now have changed to 1 (on).
Testing the used Economizer Mode.
When Economizer Mode is ordered, the control signal level, common
to compressor 2,3,and 4, is 0 (zero).
If Economizer mode is enabled, the signal will be zero. We remember
from previous tests that simulating economizer mode can be obtained
by adjusting SFan_Status.
Sfan state
TAC AB, Nov 2006 177 (450)

04-00030-01-en
41 Click Step and observe the C2_2P, C3_2P, and C4_2P blocks.
They should all have changed to 0 (off).
42 Click Execute.
43 Release the SFan\SFan_Status button to enable the compressors
to start up again. Verify that they start in succession, using their
relative delays.
178 (450) TAC AB, Nov 2006

04-00030-01-en
4.12 The Values for Graphic Displays

In this part, we will design the creation of values to be shown on the
graphics display . We will also create alarms for when levels are outside
given limits.
These are:
• Calculating values for the six separate zones.
We will create a combination of function blocks for an initial set of val-
ues and then, using copy and paste, reuse that part for the remaining
sets.
We will make the function blocks on this FBD printable page another
set of signals in the common module called Term_Units.
1 Locate VAV_4:1_SpaceTemp, an AI type function block, in the
diagram window, to the left and approximately one fourth from the
top. Then define the block.
Identifier VAV_4:1_SpaceTemp
Unit °C
Description From FPB-4:1
Public No
R/W (Acc.)
Backup
Bound to SNVT
Type temp_p
Member
Name nvi4:1_SpaceTemp
Initial Value = 25
Poll No
Period: 60
2 Locate VAV_4:1_SetPoint, an AI type function block, in the dia-

gram window, below the VAV_4:1_SpaceTemp. Then define the
block.
Identifier VAV_4:1_Setpoint
Unit °C
Public No
R/W (Acc.)
TAC AB, Nov 2006 179 (450)

04-00030-01-en
Backup
Bound to SNVT
Type temp_p
Member
Name nvi4:1_setPt
Initial Value = 25
Poll No
Period: 60
We will use three more blocks like VAV_4:1_SpaceTemp and

VAV_4:1_SetPoint, representing the values from other zones, but we
will make copies of a partial design and rename the added blocks later
on.
Calculating the Difference
For presentation we want presentation the difference between the space
temperature and the corresponding setpoint. Here the calculation is
done using an expression block
3 Locate VAV_4:1_Temp_Error, an XPR expression block, in the
diagram window, to the right of VAV_4:1_SpaceTemp. Then
define the block and enter the expression C=0? (A-B):0.
Identifier VAV_4:1_Temp_Error
Unit °F
Description Space Temp Error
Public Yes
R/W (Acc.)
Type Real
Expression C=0? (A-B):0
This expression will create a block with three analog inputs, A, B, and
C. Input A represents the space temperature in the zone. Input B repre-
sents the setpoint for the zone. Input C represents the occupancy state of
the zone.
4 Connect the output of VAV_4:1_SpaceTemp function block to
input A of the XPR block.
5 Connect the output of VAV_4:1_SetPoint function block to input
B of the XPR block.
We will connect input C later.
Detecting the possible alarm levels of the value is carried out using two
more expression blocks.
180 (450) TAC AB, Nov 2006

04-00030-01-en

upper right of the VAV_4:1_Temp_Error function block. Then
define the block and enter the expression A>4.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A>4
7 Connect the output of the VAV_4:1_Temp_Error function block to

the input of the upper XPB block.
8 Locate VAV_4:1_High, an ALARM function block, in the dia-
block.
Identifier VAV_4:1_High
Unit Normal/Alarm
Description High space temp alarm VAV_4:1
Public
R/W (Acc.)
Backup
Delay On 300
Delay Off 60
Priority 3
OP Alarm text High Space VAV_4:1
Alarm Processing
Vista Alarm tripped High space temperature VAV_4:1
Vista Alarm reset Space temperature VAV_4:1 return to normal

VAV_4:1_High Alarm block.
10 Locate again, on the FBD area, an XPB expression block, to the
lower right of the VAV_4:1_Temp_Error function block. Then
define the block and enter the expression A<-4.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<-4
TAC AB, Nov 2006 181 (450)

04-00030-01-en
11 Create a new node and connect the output of the

VAV_4:1_Temp_Error function block to the input of the lower
XPB block.
12 Locate VAV_4:1_Low, an ALARM function block, in the dia-
block.
Identifier VAV_4:1_Low
Unit Normal/Alarm
Description Low space temp alarm VAV_4:1
Public
R/W (Acc.)
Backup
Delay On 300
Delay Off 60
Priority 3
OP Alarm text Low space VAV_4:1
Alarm Processing
Vista Alarm tripped Low space temperature VAV_4:1

VAV_4:1_Low Alarm block.
This part of the design should now look like this (input C not yet con-
nected):
We can now easily duplicate this design and use it for the remaining five
terminal units. Locate VAV_4:2, VAV_4:3 in a column below
VAV_4:1 and make a new column to the right for VAV_4:4, VAV_4:5,
and VAV_4:6.
182 (450) TAC AB, Nov 2006

04-00030-01-en
14 Select all blocks and use Edit/Copy followed by an Edit/Paste

command to create the lines for VAV_4:2, VAV_4:3, VAV_4:4,
VAV_4:5, and VAV_4:6.
As the duplicates are complete copies containing the same names and
parameters, we must make sure they are all redefined.
15 Redefine all the necessary names and parameters in the duplicate
blocks. The tables below only show the parameters that differ
between the blocks.
VAV_4:2
AI SpaceTemp:
AI Setpoint:
Name nvi4:2_setPt
Temp_Error:
High_ALARM:
Low_ALARM:
TAC AB, Nov 2006 183 (450)

04-00030-01-en
VAV_4:3
SpaceTemp:
Setpoint:
Name nvi4:3_setPT
Temp_Error:
High_ALARM:
Low_ALARM:
VAV_4:4
SpaceTemp:
Setpoint:
Name nvi4:4_setPT
184 (450) TAC AB, Nov 2006

04-00030-01-en
Temp_Error:
High_ALARM:
Low_ALARM:
VAV_4:5
SpaceTemp:
Setpoint:
Name nvi4:5_setPT
Temp_Error:
High_ALARM:
TAC AB, Nov 2006 185 (450)

04-00030-01-en
Low_ALARM:
VAV_4:6
SpaceTemp:
Setpoint:
Name nvi4:6_setPT
Temp_Error:
High_ALARM:
Low_ALARM:
What remains now is to connect signals to input C of all the expression

blocks calculating the difference.
186 (450) TAC AB, Nov 2006

04-00030-01-en
In this case, it will be convenient to locate the connections (lines) below

our current FBD printable pages. Locate them like a bus from left to
right.
16 Create a new node and connect the output of the
VAV_4:1_Occ_Status block (the AI function block on our first
FBD page), to input C of the VAV_4:1_Temp_Error block (the
upper left XPR block).
17 Repeat the procedure to additionally connect VAV_4:2, VAV_4:3,
VAV_4:4, VAV_4:5, and VAV_4:6.
Assigning the Module Name "Term_Units"
These 7 function blocks are the remaining blocks we also want to have
in the module called Term_Units.
name Term_Units.
When completed, the page should look like this:

tons located to the left. The buttons are sorted in Types and Alphabetical
order within the types. Use the scroll-bar to see them all.
TAC AB, Nov 2006 187 (450)

04-00030-01-en
Testing the VAV4:1 Difference High Alarm.
2 Click Execute and observe the two XPB blocks to the left of the
VAV4:1 alarm blocks. They should both be 0 (off).
3 Click the TermUnits\VAV4:1_SpaceTemp button to the left to
display an Analog input form for entering a value. Enter a value of
30, simulating 5 degrees too high space temperature, and observe
the XPB blocks. The upper XPB block should immediately be 1
(on), and the lower should remain at 0 (off). Observe the
VAV4:1_High ALARM block. It should change to 1 (on) after
another 300 execution intervals.
4 Click the TermUnits\VAV4:1_SpaceTemp button and enter a
value of 25 again, simulating a space temperature equal to the set-
point, and observe the XPB blocks. The upper XPB block should
immediately be 0 (off), and the lower should remain at 0 (off).
Observe the VAV4:1_High ALARM block. It should change to 0
Testing the VAV4:1 Difference Low Alarm.
value of 20, simulating 5 degrees too low space temperature, and
observe the XPB blocks. The upper XPB block should remain at 0
(off), and the lower should immediately be 1 (on). Observe the
VAV4:1_Low ALARM block. It should change to 1 (on) after
another 300 execution intervals.
value of 25 again, simulating a space temperature equal to the set-
point, and observe the XPB blocks. The upper XPB block should
remain at 0 (off), and the lower should immediately change to 0
(off). Observe the VAV4:1_Low ALARM block. It should change
Testing the VAV4:1 Conditional Difference Calculation.
The actual difference between setpoint and space temperature is only to
be calculated when a zone is in occupied mode. Being in ocupied mode
or not is determined, for each zone, by the signals TermU-
nits\4:*_Occ_Status. A zone is in occupied mode when the signal has a
value of 2.
value of 20, and observe the XPR block. The block should calcu-
late the difference (multiplied by 1.8).
8 Click the TermUnits\VAV4:1_Occ_Status button and enter a
value of 2, and observe the XPR block. The block should now cal-
culate a value of 0 (zero).
188 (450) TAC AB, Nov 2006

04-00030-01-en
9 Click the TermUnits\VAV4:1_Occ_Status button and enter a

value of 0, and observe the XPR block. The block should calculate
the differenceagain (multiplied by 1.8).
Testing the Remaining Zones.
For the sake of completion, the remaining zones VAV4:2, VAV4:3,
VAV4:4, VAV4:5, and VAV4:6 can be tested in the same manner.
TAC AB, Nov 2006 189 (450)

04-00030-01-en
4.13 The I/O Alarms and Energy Consumption

In this part, we will design two independent functions:
• Logic for I/O alarms
• Totalling the Compressor Energy Usage
The function block diagram (FBD) will use one printable page on the
screen.
The design of the logic for I/O alarms will create alarms when an exten-
sion I/O module is offline, as well as when any I/O is manually forced.
Data for the chiller compressors’ energy consumption is prepared for
being logged in the Xenta device and is totalled and stored on both an
hourly and a daily basis.
Designing the I/O Offline Alarm.
The design of the error functions does not require any connected inputs
or outputs (I/O points). Function blocks of system type will be used for
the inputs.
1 Locate in the diagram window, to the left, a function block of the
ERR type.
This function block is the system error block and has different values,
depending on what errors are pending in the device. To react to the dif-
ferent errors that can occur, we decode the value of the block. This is
normally done in a expression block. First we want to act upon any I/O
module online, that is the value of the ERR block is 2048 (bit 12 is true).
right of and slightly above the ERR function block. Then define
the block and enter the expression A&2048.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A&2048
3 Locate I/O_Alarm, an ALARM function block, in the diagram

window, to the right of the XPB block. Then define the block.
Identifier IO_Alarm
Unit Normal/Alarm
Description I/O-module off-line
190 (450) TAC AB, Nov 2006

04-00030-01-en
Public
R/W (Acc.)
Backup
Delay On 30
Delay Off 0
Priority 2
OP Alarm text I/O Module Offline
Alarm Processing
Vista Alarm tripped I/O-module off-line RTU4
Vista Alarm reset I/O-module off-line RTU4
4 Connect the output of the XPB block to the input of the C1_Alarm
function block.
5 Connect the output of the ERR function block to the input of the
XPB block.
Designing the I/O is being Forced Alarm.
Now we want an alarm when any I/O is in forced mode, that is the value
of the ERR block is 4096, bit 13 is true.
6 Locate in the diagram window one more XPB expression block, to
the right of and slightly below the ERR function block. Then
define the block and enter the expression A&4096.
Identifier
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A&4096
7 Locate FO_Alarm, an ALARM function block, in the diagram

window, to the right of the latest XPB block. Then define the
block.
Identifier FO_Alarm
Unit Normal/Alarm
Description I/O Forced
Public
R/W (Acc.)
Backup
Delay On 30
Delay Off 0
Priority 2
OP Alarm text I/O Forced
TAC AB, Nov 2006 191 (450)

04-00030-01-en
Alarm Processing
Vista Alarm tripped I/O forced in RTU4
Vista Alarm reset I/O forced in RTU4
8 Connect the output of the XPB block to the input of the FO_Alarm
function block.
9 Create a new node and connect the output of the ERR function
block to the input of the XPB block.
Your I/O alarm design should now look like this:
Designing the Totalling of the Chiller Energy Consumption.

Pulses representing the electrical energy used by the chiller compres-
sors are totalled and stored as two values.
The Energy measurement design uses one digital input block. We use a
function block that counts every pulse into the input.
10 Locate Pulse, a function block of CNT type. in the diagram win-
dow, to the lover left. Then define the block.
Identifier (Name) Pulse

Unit
Description Energy pulses from Chillers
Public NO
R/W (Acc.)
Backup NO
Bound to Pulse Counter
Mod Number M1
Term. Ref X2
Multiplier Off
Normally Open = 1
Note
Use the Online help or read Section 14.7, “CNT – Digital Input – Pulse
Counter” to learn more about the CNT block.
192 (450) TAC AB, Nov 2006

04-00030-01-en
One value is prepared at the turn of each hour at minute:second 00:00.

The other value is prepared at the turn of each day (24 hour) at 00:00.
Both values are stored until they are replaced by the next period’s totals.
Sometimes, preparations for logging are requested to be done just a few
seconds before the very end of the period. If so, another period change
design is used.
For this design, we use two signals defining the start of each period, the
hour and the day (24h). We use a block to detect the hour in the Xenta
system clock and two expression blocks to detect the two changes.
11 Locate in the diagram window an HOUR block below the CNT
block.
Note
Use the Online help or read Section 14.21, “HOUR – Hour” to learn
more about the HOUR block.
12 Locate ChangeOfHour, an XPB expression block, in the diagram

window, to the right of the HOUR function block. Then define the
block and enter the expression A!=B.
Identifier ChangeOfHour
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A!=B
13 Locate ChangeOfDay, an XPB expression block, in the diagram

window, below the XPB function block. Then define the block and
enter the expression A<B.
Identifier ChangeOfDay
Unit
Description
Public
R/W (Acc.)
Type Binary
Expression A<B
A block delaying the value by one program execution is used to store

previous hour.
TAC AB, Nov 2006 193 (450)

04-00030-01-en
14 Locate in the diagram window a DELI block, below the HOUR

Identifier (Name)
Unit
Description
Public
R/W (Acc.)
Backup Yes
Init Value 0
Note
Use the Online help or read Section 14.21, “HOUR – Hour” to learn
more about the DELI block.
For the hourly value, we use a block that accumulates pulses from the
input block. We will add signals to reset this accumulator when the val-
ues are transferred to a storage block.
15 Locate in the diagram window an ACCUM block, to the right of
the CNT block and approximately five blocks away from it. Then
define the block.
Identifier (Name)
Unit
Description
Public
R/W (Acc.) Yes
Backup Yes
Initial Value: 0
Note
Use the Online help or read Section 14.1, “ACCUM – Accumulator”
to learn more about the ACCUM block.
To allow for converting the number of pulses to the energy, we add a

function block that performs the arithmetic.
16 Locate in the diagram window a Division operator, to the right of
the ACCUM function block.
Note
more about the Operator Division block.
194 (450) TAC AB, Nov 2006

04-00030-01-en
We want the value accumulated during the last period to remain

unchanged for one period, so we use a function block where we can con-
trol when the contents will be altered. We want the contents to be the
converted accumulator and to be changed at the same moment as the
accumulator value is reset.
17 Locate C_Usage, a SHR block, in the diagram window, to the
right of the division operator. Then define the block.
Identifier (Name) C_Usage

Unit KWh
Description Energy Consumption Previous hour
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
Note
Use the Online help or read Section 14.50, “SHR – Sample and Hold
Real Value” to learn more about the SHR block.
We use a function block as the scaling factor to convert the totalled

number of pulses to the energy consumed. In the division operator we
have used, the scaling factor must reflect the number of pulses for each
KWh.
18 Locate Scale_Factor, a PVR function block, in the diagram win-
dow, below the ACCUM function block. Leave vertical space for
two blocks. Then define the block.
Identifier Scale_Factor
Unit Puls/KWh
Description Number of pulses for each KWh
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 1
19 Connect the output of the CNT block to input i of the ACCUM

block.
20 Create a new node and connect the output of the CNT to input rv
of the ACCUM block as well.
21 Connect the output of the ChangeOfHour block ( XPB block) to
input rs of the ACCUM block.
22 Connect the output of the ACCUM block to the horizontal input of
the division operator.
TAC AB, Nov 2006 195 (450)

04-00030-01-en
23 Connect the output of the division operator to input D of the

C_Usage block (SHR block).
24 Create a new node and connect the output of the ChangeOfHour
(XPB block) to input c of the C_Usage block as well.
25 Connect the output of the Scale_Factor block (PVR block) to the
vertical input of the operator division.
Our design for totalling the hourly values should look like this:
For values updated on a daily (24 hour) basis, we do the following:

26 Select and the ACCUM, DIVISION and the SHR block and use
Copy and paste to make a duplicate of the blocks. Then redefine
the copied SHR block.
Identifier (Name) CDay_Usage

Unit KWh
Description Energy Consumption Previous Day
Public Yes
R/W (Acc.) Yes
Backup Yes
InitValue 0
27 Create a new node and connect the output of the Pulse block (CNT
block) to input i of the lower ACCUM block as well.
28 Create a new node and connect the output of the Pulse block (CNT
block) to input rv of the lower ACCUM block as well.
29 Connect the output of the ChangeOfDay block (XPB block) to
input rs of the lower ACCUM block.
30 Connect the output of the lower ACCUM block to the horizontal
input of the lower division operator.
31 Connect the output of the lower division operator to input D of the
CDay_Usage block (SHR block).
196 (450) TAC AB, Nov 2006

04-00030-01-en
32 Create a new node and connect the output of the ChangeOfDay

(XPB block) to input c of the C_Usage block as well.
33 Create a new node and connect the output of the Scale_Factor
block (PVR block) to the vertical input of the lower operator divi-
sion as well.
Our completed design for totalling the energy consumption should look
like this:

In Simulator mode, we cannot simulate the value of the ERR error
block. Testing the alarms can only be performed when the application
software is downloaded to a Xenta device. For testing the logic, you can
temporarily replace the ERR block with another block, for instance a
PVI block, and assign a requested value briefly.
Testing this part of the design using simulation mode in Menta will
mostly be a test of the expression blocks and the alarms.
To simulate a value from the ERR block, we can temporarily replace,
just for simulation purposes, the ERR block with a PVI function block.
1 Use the Options/Edit command to obtain the editing mode.
2 Mark and delete the ERR block.
3 Locate in the diagram window a PVI block, to the left of the two
XPB blocks.
4 Connect the output of the PVI block to the input of the two XPB
blocks.
5 Enter the simulation mode of Menta, Options/Simulate (F12)
Testing the I/O Error Alarm
6 Click Execute and observe the state of the XPB block. It should be
0 (zero).
7 Click the PVI block to display a form for entering a value. Enter a
value of 2048, to simulate the error code, and observe the state of
the upper XPB block. It should change to 1 (on) immediately. The
TAC AB, Nov 2006 197 (450)

04-00030-01-en
state of the I/O_Alarm should change to 1 (on) after 30 execution

intervals.
8 Click the PVI block and enter a value of 0, to simulate no error
condition, and observe the state of the upper XPB block and the I/
O_Alarm. They should both change to 0 (off) immediately.
Testing the FO Alarm
9 Click the PVI block and enter a value of 4096, to simulate the
other error code, and observe the state of the lower XPB block. It
should change to 1 (on) immediately. The state of the I/O_Alarm
should change to 1 (on) after 30 execution intervals.
10 Click the PVI block and enter a value of 0, to simulate no error
condition, and observe the state of the lower XPB block and the I/
O_Alarm. They should both change to 0 (off) immediately.
When testing is finished, we must remember to replace the temporary
PVI block with the ERR block and restore the connections. An alterna-
tive way of reverting to the original design is to reload the application
without saving the changes.
11 Mark and delete the PVI block.
12 Locate in the diagram window an ERR block, to the left of the two
XPB blocks.
13 Connect the output of the ERR block to the input of the two XPB
blocks.
Simulating Totalling of the Energy consumption
15 Click Execute.
16 Click the Cooling\Pulse button to the left twice to simulate a pulse
from the energy meter. Observe the value of the ACCUM block. It
should show a value of 1.
17 Click the Cooling\Pulse button a number of times and observe the
value of the ACCUM block again. It should show the total number
of simulated pulses.
We will have to wait for 3600 simulation execution intervals before we
can observe the number of pulses during the simulated first hour.
Each time we enter the simulation Mode of Menta, the simulation clock/
calender starts with the time 00:00:00 (hh:mm:ss). To shorten this
period of waiting we can as follows:
18 Use Options\Set Date and Time... to enter, for instance 58 in the
minutes field.
19 Click OK.
198 (450) TAC AB, Nov 2006

04-00030-01-en
20 Observe the contents of the two ACCUM blocks and the C_Usage
block (SHR block) after a number of executions. The value of the
upper ACCUM block should have been transferred to the SHR
block and the lower ACCUNM block should contain the number
of pulses.
21 Click the Cooling\Pulse button a number of times and observe the
value of the two ACCUM blocks again. The upper ACCUM block
should show the number of new, simulated pulses and the lower
one should contain the number of all the pulses.
To observe the number of pulses during a full day, we will have to wait
for 86400 simulated execution intervals. To shorten this period of wait-
ing, we do as follows:
22 Use Options\Set Date and Time... to enter, for instance 23 in the
hour field and 58 in the minutes field.
23 Click OK.
24 Observe the contents of the C_Usage and the CDay_Usage blocks
(SHR blocks). The value of each ACCUM block should have been
transferred to the two SHR blocks after a number of executions.
The added number of pulses replaces the contents of the C_Usage
block. The total number of pulses replaces the contents of the
CDay_Usage block.
TAC AB, Nov 2006 199 (450)

04-00030-01-en
4.14 The Trend log

In order for the Xenta device to be able to do Trend Logs, we must, at
the very minimum, define the requested maximum number of trend logs
for the Xenta device. When one or more trend logs are defined, they can
later be specified further using TAC Vista.
Other parameters can be defined during programming in Menta, or later
on using TAC Vista.
We are going to define a number of logs, as well as partly specify one
trend log to be done by the Xenta device.
1 Click Options and then Trend Logs ... to open the Select Trend
Log menu.
2 Use the arrows to enter, for example 32, in the Max number of
logs: box.
3 Select LOG28 and click Edit ... to open the Trend Log Definition
Menu.
Note
You can also double-click the LOG28 to open the Trend Log Defini-
tion Menu.
4 Enter DAT in the Name: box

5 Enter Discharge Air Temperature in the Description: box.
6 In the Logged signal: box, browse to the Cooling\DAT that will
be the logged signal
200 (450) TAC AB, Nov 2006

04-00030-01-en
7 Enter 0.5 in the Hysteresis: box.

To define how frequent we want the value to be logged, we define the
log interval.
8 Enter 6 in the Log Interval: box
9 Click the down arrow to open the box to the right, and then select
Minute(s).
To define how long we want to keep values stored, we define the log
space we want to use.
10 Enter 2 in the Log Space: box.
11 Click the down arrow to open the box to the right, and then select
Day(s)
We want the log to start at a time we define so we define a manual start
of the log.
12 Click the down arrow to open the Activate: box, and then select
Manual - on
To start the log at an exact hour, we also define the starting time.
13 Enter, for example, 2004-01-19 16:00:00 in the Start Time: box.
TAC AB, Nov 2006 201 (450)

04-00030-01-en
14 Click OK.
Note
Read Section 6.12, “Local Trend Logging in the TAC Xenta” to learn
more about the Trend Log.
Here we do not define the Log Type parameters. These are used by hte
TAC Vista operator station, and we assume they are defined using TAC
Vista.
Note
Read the Manual "Engineering TAC Vista Server" to learn more about
the use of Trend Logs in TAC Vista.
202 (450) TAC AB, Nov 2006

04-00030-01-en
4.15 The OP Menu Tree

Preparing an OP menu tree is the task of designing texts for display on
a connected OP operator panel. These texts are defined for each Xenta
device and form a part of the downloaded application.
Many installations are delivered with a custom made OP Menu tree,
prepared using the OP configuration command in the Tools menu.
An alternative way of producing a menu tree is by having Menta auto-
matically prepare it. A menu tree generated automatically will be stan-
dardized regarding its layout and contents.
Note
Read Chapter 10, “OP Configuration Tool” to learn more about the
OP Configuration tool.
During our continuing work on the application, we will be using this

automatically generated menu tree.
An automatically generated menu tree is prepared either in Simulation
mode or using the OP configuration tool. Here we use the OP Configu-
ration tool to create the OP menu tree, however only using it to create
the standardized layout and contents.
1 Click OP Configuration in the Tools menu to open the OP con-
figuration tool.
2 Click Build in the Tree menu to automatically generate an OP
menu tree.
3 Click Generate in the Tree menu to generate the OP menu tree
file.
TAC AB, Nov 2006 203 (450)

04-00030-01-en
4 Click Save in the File menu.

5 Click Exit in the File menu to leave the OP Configuration Tool.
Caution
Automatically generating a menu tree will destroy a previous custom-
made menu tree.
Service menu
One optional part of a menu tree is the TAC service menu, a fixed menu
allowing the user of an OP to read the Xenta system program version,
the name and network address, configure I/O modules, and restart the
Xenta device. The service menu is accessible via a fixed access code.
To include the service menu, we have to use the OP Configuration tool
and prepare the following.
6 Select OP Configuration in the Tools menu to open the OP Con-
figuration tool.
7 Select Settings ... in the Formats menu.
8 Make sure that the Use Service menu is checked and then click
OK.
9 Select Exit from the File menu to close the OP Configuration
tool.
204 (450) TAC AB, Nov 2006

04-00030-01-en
4.16 Downloading to the Xenta Device

Executable program code for the application is automatically generated
when an application is downloaded to a Xenta device.
Program code can also be generated in Simulation mode, by selecting
the Generate command in the Commands menu.
When the executable code is being generated, files for a new OP files
can also be generated, either automatically or designed using the OP
Configuration tool.
In a completed installation, downloading the application is normally
performed using TAC Vista and the network. When downloading an
application from the TAC Vista database, the network neighbourhood
information, stored in the Xenta device, is retrieved from the TAC Vista
database and downloaded to the Xenta device.
Downloading to a Xenta device from TAC Menta can also be done in
online mode, using a serial interface port (COM Port) on the PC, a pre-
pared cable with suitable connectors, connected to the serial port on the
Xenta device. When downloading from Menta via the serial interface,
information about the network neighbourhood is retrieved from the
Xenta device and downloaded again during the download procedure. If
there is no network neighbourhood information stored in the Xenta,
there will be a message about the missing network configuration and the
download will continue.
COM Port
RS232
Downloading the application to a Xenta device from TAC Menta can

also be done by using the Download Wizard, with a serial interface port
(COM Port) on the PC, and a prepared cable connected to the serial port
on the Xenta device. When the Download Wizard is used, the system
software of the Xenta device as well as any network information can
also be downloaded.
Note
Read Chapter 12, “The Download Wizard” to learn more about the
Download Wizard.
Menta will start off a download procedure by checking the type of

Xenta to download to. During the previous chapters, we have made an
TAC AB, Nov 2006 205 (450)

04-00030-01-en
application for a Xenta 401, so we need this type of device to download

the application.
1 Click Settings in the Preferences menu to open the Settings dia-
log.
2 In the Communication Port for this session: box, select the
COM port in the PC you will be using for the connection and then
click OK.
3 Connect the cable between the PC and the connector marked
RS232 on the Xenta device.
4 Click Simulate in the Options menu to enter simulation mode.
5 Click Online in the Options menu or, alternatively, click the
Online button to open the Connecting to device dialog.
6 Click Download to start downloading the application.
If there is no network neighbourhood information stored in the Xenta,
there will be a message saying "No blueprint in TAC Xenta! Don't for-
get to download the network configuration if the TAC Xenta is to func-
tion in a network!". In this case, a name based on the type of device and
its Neuron ID will be downloaded to the Xenta.
The download process continues and may take a few minutes, depend-
ing on the size of the application. The progress of download is shown in
a dialog.
When the download has finished, you will be connected to the Xenta
and executing the application in realtime, viewing and overriding actual
states and values in the function block diagram. The execution of the
application is done according to the cycle time specified in the program
specification. The buttons to the left, representing inputs and outputs,
have now disappeared.
Note
Read Section 11.5.1, “Online Mode” to learn more about using the
Online Mode.
7 Click Online again to return to offline simulation mode.
206 (450) TAC AB, Nov 2006

04-00030-01-en
4.17 System Configuration and Documentation

The following tables include documentation of the Xenta device, as
printed from the Menta programming tool.
Devices
This is the information you get when you use File/Print and have the
Devices box checked.
Unit Name Device type

0 TAC Xenta 401
1 M1 TAC Xenta 422
2 M2 TAC Xenta 422
3 M3 TAC Xenta 452
4 M4 TAC Xenta 452
5 M5 TAC Xenta 451
I/O point allocation

This is the first part of the information you get when you use File/Print
and have the I/O Lis box checked.
Terminal Ref. Name Bound to Parameter/Value Parameter/Value

M1-X1 SFan\SFan_Status Digital input Initial Value=Off Unit=
Normally Open=1
M1-X2 Cooling\Pulse Pulse Counter Normally Open=1
M1-X3
M1-X4
M1-K1 SFan\SFan_Start_Stop Digital output Initial Value=Off Unit=
M1-K2 Relief\Relief_Fan Digital output Initial Value=Off Unit=
M1-K3 Relief\Relief_Air_Dmprs_ Output pulse Initial Value=Off Unit=

Do Minimum Pulse=0.1
M1-K4
M1-K5
M2-X1 Cooling\C1_Status Digital input Initial Value=Off Unit=
Normally Open=1
Normally Open=1
Normally Open=1
Normally Open=1
M2-K1 Cooling\C1_Start/Stop Digital output Initial Value=Off Unit=
TAC AB, Nov 2006 207 (450)

04-00030-01-en

M2-K5
M3-B1 Cooling\DAT_Sensor Non linear Sensor=TAC Ter- Time Constant=0
input mistor (°F) Unit=°F
Initial Value=55
M3-B2 Econ\RAT_Sensor Non linear Sensor=TAC Ter- Time Constant=0
Initial Value=75
M3-B3 Econ\MAT_Sensor Non linear Sensor=TAC Ter- Time Constant=0
Initial Value=55
M3-B4 OA_Temp Non linear Sensor=TAC Ter- Time Constant=0
Initial Value=70
M3-U1 VSD\Static_Press_Sensor Linear input Sensor=2..10V Time Constant=0
Initial Value=0 Unit="wc
Min Value=0 Max. Value=5
M3-U2 Econ\RAHumiditySen Linear input Sensor=2..10V Time Constant=0
Initial Value=50 Unit=%RH
Min Value=0 Max.Value=100
M3-U3 Econ\CO2 Linear input Sensor=2..10V Time Constant=0
Initial Value=500 Unit="wc
M3-U4 Relief\Bldg_Static Linear input Sensor=2..10V Time Constant=0
Initial Value=.05 Unit="wc
Min Value=-0.25 Max.Value=0.25
M3-Y1 VSD\VSD Analog output Initial Value=0 Unit=
Min. Voltage=0 Max. VOltage=10
M3-Y2 Econ\Mixed_Air_Dampers Analog output Initial Value=0 Unit=
Min. Voltage=0 Max. VOltage=10
M4-B1
M4-B2
M4-B3
M4-B4
M4-U1
M4-U2
M4-U3 Cooling\FanSpeed Linear input Sensor=0..10V Ini- Time Constant=0
tial Value=0 Unit=%
M4-U4
M4-Y1
M4-Y2
M5-B1
M5-B2
M5-B3
M5-B4
208 (450) TAC AB, Nov 2006

04-00030-01-en

M5-U1 Econ\OAHumiditySen Linear input Sensor=0..10V Ini- Time Constant=0
tial Value=50 Unit=%RH
M5-U2
M5-U3
M5-U4
M5-Y1
M5-Y2
SNVTs (Network Variables)

This is the second part of the information you get when you use File/
Print and have the I/O Lis box checked.
Name Block Type Parameter/Value Parameter/

Value
Cooling\VAV_4:1_Term_Load AI lev_percent, hvac_mode Initial Value=0 Unit=%
nvi4:1_TermLoad Period=60 Load
Econ\CO2_SNVT AO ppm, ppm nvoCO2 Initial Value=0 Unit=ppm
Period=60
SFAN\Term_Unit_Occ_Cmd AO occupancy, occupancy Initial Value=1 Unit=Occ
nvoVAV_Occ Period=60 u/Unoc
Term_Units\VAV_4:1_Occ_Status AI occupancy, occupancy Initial Value=0 Unit=
nvi4:1_Occ_Stat Period=60
Term_Units\VAV_4:1_Setpoint AI temp_p, temp_p Initial Value=25 Unit=
nvi4:1_setPt Period=60
Term_Units\VAV_4:1_SpaceTemp AI temp_p, temp_p Initial Value=25 Unit=
nvi4:1_SpaceTemp Period=60
nvi4:2SpaceTemp Period=60
TAC AB, Nov 2006 209 (450)

04-00030-01-en
Name Block Type Parameter/Value Parameter/

Value
Term_Units\VAV_4:5_Occ_Setpoint AI temp_p, temp_p Initial Value=25 Unit=
Alarms
This is the part of the information you get when you use File/Print and
have the Alarms box checked.
Alarm name Parameter name Text

Cooling\C1_Alarm OP Alarm Text 4A-C1 Alarm
TAC Vista Alarm
TAC Vista Tripped 4A-C1 Alarm Tripped
TAC Vista Reset 4A-C1 Alarm Reset
TAC Vista Alarm
TAC Vista Alarm
210 (450) TAC AB, Nov 2006

04-00030-01-en

TAC Vista Alarm
Cooling\DAT_High OP Alarm Text High DAT
TAC Vista Alarm
TAC Vista Tripped High discharge air temperature 2nd Floor South
TAC Vista Reset Discharge air temperature 2nd Floor South return
to normal
Cooling\DAT_Low OP Alarm Text Low DAT
TAC Vista Alarm
TAC Vista Tripped Low discharge air temperature 2nd Floor South
TAC Vista Reset Discharge air temperature 2nd Floor South return
to normal
Cooling\DAT_SF OP Alarm Text Sensor failure DAT
TAC Vista Alarm
TAC Vista Tripped Sensor failure discharge air sensor 2nd Floor
South
TAC Vista Reset Sensor failure discharge air sensor 2nd Floor
Econ\CO2_Alarm OP Alarm Text CO2 Alarm
TAC Vista Alarm
TAC Vista Tripped CO2 2nd Floor South Alarm
TAC Vista Reset CO2 2nd Floor South return to normal
Econ\MAT_High OP Alarm Text High MAT
TAC Vista Alarm
TAC Vista Tripped High mixed air temperature 2nd Floor South
TAC Vista Reset Mixed air temperature 2nd Floor South return to
normal
Econ\MAT_Low OP Alarm Text Low MAT
TAC Vista Alarm
TAC Vista Tripped Low mixed air temperature 2nd Floor
TAC Vista Reset Mixed air temperature 2nd Floor South return to
normal
Econ\MAT_SF OP Alarm Text Sensor failure MAT
TAC Vista Alarm
TAC Vista Tripped Sensor failure mixed air sensor 2nd Floor South
TAC Vista Reset Sensor failure mixed air sensor 2nd Floor South
return to normal
Econ\OAHumidity_SF OP Alarm Text Sensor failure OA Humidity
TAC Vista Alarm
TAC Vista Tripped Sensor failure OA Humidity sensor
TAC AB, Nov 2006 211 (450)

04-00030-01-en

TAC Vista Reset Sensor failure OA Humidity sensor return to nor-
mal
Econ\OAT_SF OP Alarm Text Sensor failure OAT
TAC Vista Alarm
TAC Vista Tripped Sensor failure Outside air sensor
TAC Vista Reset Sensor failure Outside air sensor return to normal
Econ\RAHumidity_SF OP Alarm Text Sensor failure RA Humidity
TAC Vista Alarm
TAC Vista Tripped Sensor failure RA Humidity sensor 2nd Floor
South
TAC Vista Reset Sensor failure RA Humidity sensor 2nd Floor
Econ\RAT_High OP Alarm Text High RAT
TAC Vista Alarm
TAC Vista Tripped High return air temperature 2nd Floor
TAC Vista Reset Return air temperature 2nd Floor South return to
normal
Econ\RAT_Low OP Alarm Text Low RAT
TAC Vista Alarm
TAC Vista Tripped Low return air temperature 2nd Floor South
TAC Vista Reset Return air temperature 2nd Floor South return to
normal
Econ\RAT_SF OP Alarm Text Sensor failure RAT
TAC Vista Alarm
TAC Vista Tripped Sensor failure return air sensor 2nd Floor South
TAC Vista Reset Sensor failure return air sensor 2nd Floor South
return to normal
FO_Alarm OP Alarm Text I/O Forced
TAC Vista Alarm
TAC Vista Tripped I/O forced in RTU4
TAC Vista Reset I/O forced in RTU4
IO_Alarm OP Alarm Text I/O Module Offline
TAC Vista Alarm
TAC Vista Tripped I/O-module off-line RTU4
TAC Vista Reset I/O-module off-line RTU4
Relief\Bldg_Static_High OP Alarm Text High Bldg Static 2S
TAC Vista Alarm
TAC Vista Tripped High Bldg Static 2nd Floor South
TAC Vista Reset Bldg Static 2nd Floor South return to normal
Relief\Bldg_Static_Low OP Alarm Text Low Bldg Static 2S
TAC Vista Alarm
TAC Vista Tripped Low Bldg Static 2nd Floor South
TAC Vista Reset Bldg Static 2nd Floor South return to normal
212 (450) TAC AB, Nov 2006

04-00030-01-en

Relief\Bldg_Static_SF OP Alarm Text Sensor failure Bldg Static 2S
TAC Vista Alarm
TAC Vista Tripped Sensor failure Bldg Static sensor 2nd Floor South
TAC Vista Reset Sensor failure Bldg Static sensor 2nd Floor South
return to normal
SFan\SFan_Alarm OP Alarm Text SFan Alarm
TAC Vista Alarm
TAC Vista Tripped SFan Status Alarm 2nd Floor South
TAC Vista Reset SFan Status Alarm 2nd Floor South Return to
normal
SFan\SFAN_Hand_Alarm OP Alarm Text SFan Manually-operated
TAC Vista Alarm
TAC Vista Tripped Hand control supply air fan, the unit serves 2nd
Floor South
TAC Vista Reset Hand control supply air fan, the unit serves 2nd
Floor South
SFan\SFan_MO OP Alarm Text Manual operation
TAC Vista Alarm
TAC Vista Tripped Unit controlled manually
TAC Vista Reset Unit controlled manually
Term_Units\VAV_4:1_High OP Alarm Text High Space VAV_4:1
TAC Vista Alarm
TAC Vista Tripped High space temperature VAV_4:1
TAC Vista Reset Space temperature VAV_4:1 return to normal
Term_Units\VAV_4:1_Low OP Alarm Text Low space VAV_4:1
TAC Vista Alarm
TAC Vista Tripped Low space temperature VAV_4:1
TAC Vista Alarm
TAC Vista Alarm
TAC Vista Alarm
TAC Vista Alarm
TAC AB, Nov 2006 213 (450)

04-00030-01-en

TAC Vista Alarm
TAC Vista Alarm
TAC Vista Alarm
TAC Vista Alarm
TAC Vista Alarm
Term_Units\VAV_4:6_Low OP Alarm Text Low space temperature VAV_4:6
TAC Vista Alarm
VSD\Duct_Static_SF OP Alarm Text Sensor failure Duct Static
TAC Vista Alarm
TAC Vista Tripped Sensor failure Duct Static sensor
TAC Vista Reset Sensor failure Duct Static sensor return to normal
VSD\Mod_3_Offline OP Alarm Text MOD3_ALARM
TAC Vista Alarm
TAC Vista Tripped MOD3 Loss Comm Alarm
TAC Vista Reset MOD3 Comm Return to Normal
Public Signals
have the Public Signals box checked.
Name Type Acc. Unit Description

Cooling\C1_Alarm DIG RO Normal/Alarm Proofing Alarm Compressor 1
Cooling\C1_Min_Off ANA RW Seconds Compressor 1 Min. Off Time
214 (450) TAC AB, Nov 2006

04-00030-01-en

Cooling\C1_Min_On ANA RW Seconds Compressor 1 Min. On Time
Cooling\C1_Start_SP PAR RW % Speed at which C1 starts
Cooling\C1_Start_Stop DIG RO Compressor 1 Start Stop Circuit
Cooling\C1_Status DIG RO Status of Compressor 1
Cooling\C1_Stop_SP PAR RW % Speed at which C1 stops
Cooling\C_Usage ANA RW KWh Energy Consumption Previous Hour
Cooling\CDay_Usage ANA RW KWh Energy Consumption Previous Day
Cooling\DAT ANA RO °F Discharge Air Temperature
Cooling\DAT_High DIG RO Normal/Alarm High discharge air temp alarm
Cooling\DAT_Low DIG RO Normal/Alarm Low discharge air temp alarm
Cooling\DAT_Offset ANA RW °F Offset for calibration of DAT
Cooling\DAT_SF DIG RO Normal/Alarm Sensor failure discharge air sensor
Cooling\FanSpeed ANA RO % Fan Speed Feedback from VFD
Cooling\MaxTermLoad ANA RO %Load Highest Terminal Load
Cooling\Scale_Factor ANA RW Puls/KWh Number of pulses for each KWh
Cooling\VAV_4:1_Term_Load ANA RO %Load Terminal Load FPB-4:1 Software
Cooling\VAV_4:2_Term_Load ANA RO %Load Terminal Load FPB-4:2 Hardware
Cooling\VAV_4:3_Term_Load ANA RO %Load Terminal Load FPB-4:3 Rio Grande
Cooling\VAV_4:4_Term_Load ANA RO %Load Terminal Load FPB-4:4 R&D Ser-
vices
TAC AB, Nov 2006 215 (450)

04-00030-01-en

Cooling\VAV_4:5_Term_Load ANA RO %Load Terminal Load FPB-4:5 Software
Dev.
Cooling\VAV_4:6_Term_Load ANA RO %Load Terminal Load FPB-4:6 ASG
Econ\CO2 ANA RO PPM Calibrated CO2
Econ\CO2_Alarm DIG RO Normal/Alarm CO2 Alarm
Econ\CO2_Int_TC ANA RW seconds CO2 Integral Time Constant
Econ\CO2_Offset ANA RW PPM Offset for calibration of CO2
Econ\CO2_PG ANA RW % per PPM CO2 Proportional Gain
Econ\CO2_SetPoint ANA RW PPM Return Air CO2 Setpoint
Econ\CO2_SNVT ANA RO ppm SNVT output of CO2
Econ\Economizer DIG RO Mech/Econ Economizer Enabled
Econ\MAT ANA RO °F Calibrated MAT
Econ\MAT_High DIG RO Normal/Alarm High mixed air temp alarm
Econ\MAT_Low DIG RO Normal/Alarm Low mixed air temp alarm
Econ\MAT_Offset ANA RW °F Offset for Calibration of MAT
Econ\MAT_SF DIG RO Normal/Alarm Sensor failure mixed air sensor
Econ\Min_Position ANA RW % Minimum Damper position
Econ\Mixed_Air_Dampers ANA RO % Mixed Air Dampers
Econ\Mixed_Air_Int_TC ANA RW seconds% Mixed Air Integral Time Constant
Econ\Mixed_Air_PG ANA RW % per deg F Mixed Air Proportional Gain
Econ\OA_Enthalpy ANA RO BTU/lb Outside Air Enthalpy
Econ\OAHumid_Offset ANA RW °F Offset for Calibration of OA Humid-
ity
Econ\OAHumidity ANA RO °F Calibrated OA Humidity
Econ\OAHumidity_SF DIG RO Normal/Alarm Sensor failure OA Humidity sensor
Econ\OAT ANA RO °F Calibrated OAT
Econ\OAT_Offset ANA RW °F Offset for calibration of OAT
Econ\OAT_SF DIG RO Normal/Alarm Sensor failure return air sensor
Econ\RA_Enthalpy ANA RO BTU/lb Return Air Enthalpy
Econ\RAHumid_Offset ANA RW %RH Offset for Calibration of RA Humidity
Econ\RAHumidity ANA RO °F Calibrated RA Humidity
Econ\RAHumidity_SF DIG RO Normal/Alarm Sensor failure RA Humidity sensor
Econ\RAT ANA RO °F Calibrated RAT
Econ\RAT_High DIG RO Normal/Alarm High return air temp alarm
Econ\RAT_Low DIG RO Normal/Alarm Low return air temp alarm
Econ\RAT_Offset ANA RW °F Offset for Calibration of RAT
Econ\RAT_SF DIG RO Normal/Alarm Sensor failure return air sensor
FO_Alarm DIG RO Normal/Alarm I/O Forced
I/O Alarm DIG RO Normal/Alarm I/O-module off-line
Relief\Bldg_Static ANA RO "wc Calibrated Bldg Static
Relief\Bldg_Static_High DIG RO Normal/Alarm High Bldg Static Alarm
Relief\Bldg_Static_Int_TC ANA RW seconds Bldg Static Integral Time Constant
216 (450) TAC AB, Nov 2006

04-00030-01-en

Relief\Bldg_Static_Low DIG RO Normal/Alarm Low Bldg Static Alarm
Relief\Bldg_StaticOffset ANA RO "wc Offset for Calibration of d Bldg Static
Relief\Bldg_Static_PG ANA RW % per "wc Bldg Static Proportional Gain
Relief\Bldg_Static_SetPoint ANA RW "wc Bldg Static Pressure Setpoint
Relief\Bldg_Static_SF DIG RO Normal/Alarm Sensor failure Bldg Static sensor
Relief\Relief_Air_Dampers ANA RO % Open Relief Air Dampers
Relief\Relief_Fan DIG RO Relief Fan Start/Stop Circuit
SFan\Fan_Time_Sched ANA RO Fan Start Stop Time Schedule
SFan\OverrideTime ANA RW Minutes Override Timer time
Sfan\SFan_Alarm DIG RO Normal/Alarm SFan Status Alarm
Sfan\SFAN_Hand_Alarm DIG RO Normal/Alarm Hand control supply air fan
SFan\SFan_MC ANA RW -1/0/1/2 Manual control
SFan\SFan_MO DIG RO Normal/Alarm Controlled manually
SFan\SFan_Start_Stop DIG RO Supply Fan Start Stop Circuit
SFan\SFan_Status DIG RO Supply Fan Status from VFD
SFan\Term_Unit_Occ_Cmd ANA RO Occu/Unoc Occupancy Command to Terminal
Units
SFan\TimedOverride DIG RO Override Time Command
SFan\Timer DIG RO Minutes Timer time remaining
Term_Units\VAV_4:1_High DIG RO Normal/Alarm High space temp alarm VAV_4:1
Term_Units\VAV_4:1_Low DIG RO Normal/Alarm Low space temp alarm VAV_4:1
Term_Units\VAV_4:1_Occ_Stat ANA RO From FPB-4:1 Software
us
Term_Units\VAV_4:1_Temp_E ANA RO °F Space Temp Error
rror
Term_Units\VAV_4:2_Occ_Stat ANA RO From FPB-4:2 Hardware
us
rror
Term_Units\VAV_4:3_Occ_Stat ANA RO From FPB-4:3 Rio Grande
us
rror
Term_Units\VAV_4:4_Occ_Stat ANA RO From FPB-4:4 R&D Services
us
rror
TAC AB, Nov 2006 217 (450)

04-00030-01-en

Term_Units\VAV_4:5_Occ_Stat ANA RO From FPB-4:5 Software Dev.
us
rror
Term_Units\VAV_4:6_Occ_Stat ANA RO From FPB-4:6 ASG
us
rror
Term_Units\VAV_Bypass DIG RO Auto/Bypass Any Terminal Unit in Bypass
VSD\DAP_SP ANA RW "wc Setpoint discharge air pressure
VSD\Duct_Static_SF DIG RO Normal/Alarm Sensor failure Duct Static sensor
VSD\Mod3 DIG RO Offline/Online I/O Module 3 Communication Status
VSD\Mod_3_Offline Dig RO Normal/Alarm Module 3 Loss comm alarm
VSD\StartUp_Time ANA RW Start Up Timer Time Period
VSD\StartUp_Value ANA RW Value During Start Up
VSD\Static_Press_Offset ANA RW "wc Offset for Calibration of Static Press
VSD\Static_Pressure ANA RO "wc Supply Air Static Pressure
VSD\VSD ANA RO VSD AO
Constants
have the Constants box checked.
Public Name Value

Yes Cooling\C1_Start_SP 60%
Yes Cooling\C1_Stop_SP 55%
218 (450) TAC AB, Nov 2006

04-00030-01-en
Constants usage
have the Constant Usage box checked.
Constant In block
Cooling\C1_Start_SP Cooling\C1_2P
Cooling\C1_Stop_SP Cooling\C1_2P
Time Schedules
have the Time Schedules box checked.
Name W H Start Date Stop Date Start Stop Weekdays

Time Time
SFan\Fan_Time_Sched 4 7 07:00 18:00 MTWTF__
2002/5/27 2002/5/27 00:00 00:00 MTWTFSS
2002/12/24 2002/12/25 00:00 00:00 MTWTFSS
2002/11/21 2002/11/22 00:00 00:00 MTWTFSS
2002/7/4 2002/7/4 00:00 00:00 MTWTFSS
2002/9/2 2002/9/2 00:00 00:00 MTWTFSS
Block Parameters
have the Block Parameters box checked.
Type Name Parameter/Value Parameter/Value

ACCUM [noname] InitValue: 0
ACCUM [noname] InitValue: 0
ALARM Cooling\C1_Alarm DelayOn: 20 DelayOff: 0
Priority:1
Priority:1
Priority:1
Priority:1
TAC AB, Nov 2006 219 (450)

04-00030-01-en

ALARM Cooling\DAT_High DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Cooling\DAT_Low DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Cooling\DAT_SF DelayOn: 120 DelayOff: 5
Priority: 3
ALARM Econ\CO2_Alarm DelayOn: 120 DelayOff: 5
Priority: 3
ALARM Econ\MAT_High DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\MAT_Low DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\MAT_SF DelayOn: 120 DelayOff: 5
Priority: 3
ALARM Econ\OAHumidity_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\OAT_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\RAHumidity_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\RAT_High DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\RAT_Low DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Econ\RAT_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM FO_Alarm DelayOn: 30 DelayOff: 0
Priority: 2
ALARM IO_Alarm DelayOn: 30 DelayOff: 0
Priority: 2
ALARM Relief\Bldg_Static_High DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Relief\Bldg_Static_Low DelayOn: 120 DelayOff: 120
Priority: 3
ALARM Relief\Bldg_Static_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM SFan\SFan_Alarm DelayOn: 2 DelayOff: 0
Priority: 1
ALARM SFan\SFan_Hand_Alarm DelayOn: 20 DelayOff: 0
Priority: 3
ALARM SFan\SFan_MO DelayOn: 30 DelayOff: 5
Priority: 3
ALARM Term_Units\VAV_4:1_High DelayOn: 300 DelayOff: 60
Priority: 3
ALARM Term_Units\VAV_4:1_Low DelayOn: 300 DelayOff: 60
Priority: 3
220 (450) TAC AB, Nov 2006

04-00030-01-en

Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
Priority: 3
ALARM VSD\Duct_Static_SF DelayOn: 120 DelayOff: 120
Priority: 3
ALARM VSD\Mod_3_Offline DelayOn: 60 DelayOff: 0
Priority: 9
B [noname] a:0
B [noname] a:0
B [noname] a:0
B [noname] a:0
B [noname] a:1
B [noname] a:1
B [noname] a:1
B [noname] a:1
CNT Cooling\Pulse BindTo:3,,,0,1,1,X2,1
,1,0,0,0,0,0,0
DELAY [noname] DelayOn: 0 DelayOff: 20
DELB [noname] InitValue: 0
TAC AB, Nov 2006 221 (450)

04-00030-01-en

DELB SFan\TimedOverride InitValue: 0
DELI InitValue: 0
DELR [noname] InitValue: 0
DELR [noname] InitValue: 0
DOPU Relief\Relief_Air_Dmprs_Do BindTo:
FILT [noname] TimeConst: 10
HYST [noname] Activate: -2 Deactivate: -0.5
HYST Cooling\C1_2P Activate: Cool- Deactivate: Cool-
ing\C1_Start_SP ing\C1_Stop_SP
LIMIT [noname] MinValue: 0 MaxValue: 100
PIDA [noname] ControlInt: 20 UMin: 0
UMax: 100 StrokeTime: 0
PIDI [noname] ControlInt: 10 StrokeTime: 5.2
PVI SFan\SFan_MC InitValue: -1
PVR Cooling\C1_Min_Off InitValue: 300
PVR Cooling\C1_Min_On InitValue: 300
PVR Cooling\DAT_HighAlarm InitValue: 80
PVR Cooling\DAT_LowAlarm InitValue: 45
PVR Cooling\DAT_Offset InitValue: 0
PVR Cooling\Scale_Factor InitValue: 1
PVR Econ\CO2_Int_TC InitValue: 0
PVR Econ\CO2_Offset InitValue: 0
PVR Econ\CO2_PG InitValue: 16.66
PVR Econ\CO2_SetPoint InitValue: 800
PVR Econ\MAT_HighAlarm InitValue: 80
PVR Econ\MAT_LowAlarm InitValue: 50
222 (450) TAC AB, Nov 2006

04-00030-01-en

PVR Econ\MAT_Offset InitValue: 0
PVR Econ\Min_Position InitValue: 5
PVR Econ\Mixed_Air_Int_TC InitValue: 0
PVR Econ\Mixed_Air_PG InitValue: 16.66
PVR Econ\Mixed_Air_SetPoint InitValue: 53
PVR Econ\OAHumid_Offset InitValue: 0
PVR Econ\OAT_Offset InitValue: 0
PVR Econ\RAHumid_Offset InitValue: 0
PVR Econ\RAT_HighAlarm InitValue: 80
PVR Econ\RAT_LowAlarm InitValue: 50
PVR Econ\RAT_Offset InitValue: 0
PVR Relief\Bldg_Static_Hi_AlmSP InitValue: 0.1
PVR Relief\Bldg_Static_Int_TC InitValue: 1000
PVR Relief\Bldg_Static_Lo_AlmSP InitValue: -0.1
PVR Relief\Bldg_Static_Offset InitValue: 0
PVR Relief\Bldg_Static_PG InitValue: 500
PVR Relief\Bldg_Static_SetPoint InitValue: .05
PVR Sfan\OverrideTime InitValue: 120
PVR VSD\Chg_Per_Scan InitValue: 2
PVR VSD\DAP_SP InitValue: 1
PVR VSD\Dead_Band InitValue: 0.2
PVR VSD\Sample_Rate InitValue: 4
PVR VSD\StartUp_Time InitValue: 300
PVR VSD\StartUp_Value InitValue: 50
PVR VSD\Static_Press_Offset InitValue: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 0
R [noname] a: 1
R [noname] a: -1
R Econ\MAT_DZ a: 0.5
R Econ\MAT_DZ a: 0.5
R Relief\MAT_DZ a: 0
SHR Cooling\C_Usage InitValue: 0
SHR Cooling\C_Usage InitValue: 0
TAC AB, Nov 2006 223 (450)

04-00030-01-en

SR [noname] InitValue: 0
TRIG [noname] Mode: 0
W [noname] a: 0
W [noname] a: 0
W [noname] a: 0
224 (450) TAC AB, Nov 2006

04-00030-01-en
Menta, Engineering Manual
REFERENCE
5 Introduction to TAC Menta
6 General Concepts
7 The Mouse and Function Keys
8 Edit Mode
9 Simulation Mode
10 OP Configuration Tool
11 Other Functions and Tools
12 The Download Wizard
13 Function Blocks, Summary
14 Simple Blocks
15 Expressions
16 Operators
18 Test Probe Blocks
17 Supported SNVTs
19 Error Messages
20 Programming Hints
TAC AB, Oct 2006 225 (450)

04-00030-01-en
Menta, Engineering Manual
226 (450) TAC AB, Oct 2006

04-00030-01-en
TAC Menta, Technical Manual 5 Introduction to TAC Menta
5 Introduction to TAC Menta

TAC Menta is a graphical application programming tool designed for
the TAC Xenta series of controllers.
In this document, the use of this tool is described and explained from the
user’s point of view. We assume that the user already has a basic knowl-
edge of the TAC Xenta and its programming language so these concepts
will not be explained here. All types of functions available in the TAC
Menta programming language are described in the Reference Section of
this manual.
5.1 System of Units

In TAC Menta, a number of blocks use either the SI (metric) unit system
or the Inch-Pound unit system.
The national settings of the PC Windows© operating system, in which
the application is created, determines the unit system for some of the
blocks. The definition of the signal defines which unit system that will
be used for some other blocks.
5.2 Operation Modes

TAC Menta has two modes of operation, Edit mode and Simulation
mode:
• In Edit mode, the tool allows us to design an application program
by working in the FBD window.
• In Simulation mode, a correctly designed application program may
be executed step-by-step showing the state of the signals in the
FBD window. It is possible work in offline mode (no TAC Xenta
device connected) and in online mode (The TAC Xenta device is
connected to a PC). Simultaneously, it is possible to graphically
display the trend log of up to six analog and/or binary signals. The
user also has the capability to define the behavior of the physical
input signals.
Both modes also contain entries to the OP configuration tool for the
design of operator panel texts and menus.
TAC AB, Nov 2006 227 (450)

04-00030-01-en
5 Introduction to TAC Menta TAC Menta, Technical Manual
5.3 Program Licenses

Table 5.1:
Licensing TAC Menta is provided with a license by the

Privilege License Server used for TAC Vista.
For information on installing TAC Menta and
the Privilege License Server please see the
installation booklet for TAC Vista.
Demo Mode TAC Menta can be run in demo mode without
a license. Demo mode allows the user to try
out all the functions of the program (e.g.,
save, simulate, edit). However, the applica-
tion can only be saved as a demo application.
This means that it will not be possible to
download the application to a TAC Xenta
controller. A demo application can be opened
in a licensed TAC Menta, but cannot be con-
verted into a downloadable TAC Menta appli-
cation.
Note
Applications saved in TAC Menta 4.0 (or higher) can not be used by
versions of TAC Vista older than 3.2. In order to support older TAC
Vista versions, you can save TAC Menta 3.1 applications in TAC
Menta 4.0.
5.4 Setup
TAC Menta Setup is a program module for setting up communication on
your system:
Table 5.2:
Com Port Communication port on the PC.

BPS Bits per second (baud rate), must always be
9600.
228 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 5 Introduction to TAC Menta
Table 5.2: (Contd.)
Create Com Log Debug communication flag (0=log disabled,

1=log enabled). If ComLog=1, then all com-
munication to/from TAC Menta will be
logged in a file with the name pl_com1.txt (if
communication port 1 is used) in the direc-
tory “C:\Windows\Temp”. (Make sure this
directory exists on your hard disk).
Note
This option is for internal debug purposes
only. The log file may become very large.
Time Out, Packet Communication parameters, which should
Size, Resends, Com normally not be altered.
Pause
5.5 TAC Menta Start

TAC Menta is started via the TAC Tools program group, which con-
tains a number of program icons. Multiple instances of the Menta can
be run simultaneously. Also more than one instance can be on line if
communication ports are available. Start the program by clicking the
TAC Menta icon.
Before starting your current TAC Menta work, you should also set up
your system as follows via Preferences – Settings in the TAC Menta
main program:
Each FBD file may have an associated text file. Specify the text editor/
word processor to be used.
You may use a library of pre-designed macro blocks. Specify the search
path to the library.
TAC Menta can also be started from within TAC Vista Explorer, and
from the TAC Vista Device Plug-In, by right-clicking a device and
choosing Edit.
TAC AB, Nov 2006 229 (450)

04-00030-01-en
5 Introduction to TAC Menta TAC Menta, Technical Manual
230 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 6 General Concepts
6 General Concepts
An application program is defined by its graphic representation, the
function block diagram (FBD). The two fundamental elements of the
FBD are the function blocks (FB), which process data, and the connec-
tions, which transport signals (data).
During simulation of the application program, the values of the signals
in the FBD may be observed during runtime. You may modify the sig-
nals during execution, plot the evolution of signals graphically in the
trend log, and assign values to the physical inputs.
6.1 Function Block Diagrams

In an FBD, the function blocks process input signals to generate a single
output signal. Each function block may have one or more parameters,
used in the processing of the input signals. The parameters can be
defined as numeric values or as identifiers, constants, representing con-
stant values.
The output signal is transported to other blocks following the route
defined by the connections, which represent the data flow during pro-
gram execution. The data flow should always be from left to right,
except when a connection is used to close a feedback loop.
Fig. 6.1: A simple function block diagram (FBD)

In general, the blocks which have no inputs, such as physical inputs,
(secure blocks) are located on the left. The blocks whose outputs are not
connected to any other block (destination blocks), such as physical out-
put blocks, are on the right hand side. The intermediate blocks are situ-
ated between the source and destination blocks, always oriented in the
direction of the data flow.
Execution of the application program consists of a control loop which
is executed at a constant time interval. Each execution of the loop is
called a program cycle. In each program cycle, the changes produced in
the source blocks are propagated to the destination blocks via the inter-
mediate blocks, following the data route determined by the connections
and being processed along the way.
TAC AB, Nov 2006 231 (450)

04-00030-01-en
6 General Concepts TAC Menta, Technical Manual
6.2 Signals
A signal is the primary unit of information managed by an application
program, and represents a physical or calculated magnitude which var-
ies with time. The signals are variables in the application program
which are generated as outputs of function blocks and are propagated
via connections to the inputs of other blocks. All function blocks only
have one output, and each function block generates a unique signal.
6.2.1 Signal Types

In an FBD, only connections between outputs and inputs with congruent
types is permitted. There are three types of data for signals:
Table 6.1:
Integer Signed 16 bit number (range: –32768 to

32767).
Real Signed real 32 bit number in the IEEE format
with a precision of 6 decimals
(range: 3.4x10-38 to 3.4x1038).
Binary 1 bit to represent binary values (0/1 =
FALSE/TRUE). The binary type is also
called Boolean or digital.
In some cases, we use a fourth type of signal, namely the analog type
which means that either real or integer signals, without distinction, can
be connected to the outputs/inputs in question.
6.2.2 Signal Names

Signal names consists of two parts, Module and Signal, divided by the
character “\”, e.g. AHU1\T1. The Module and Signal parts are both
alphanumeric strings. The Module part can hold up to 12 characters but
may also be omitted. The Signal part can hold up to 20 characters, which
is equal to the OP display size and the maximum ID string length in
TAC Vista. The signal part must not consist of digits only. The charac-
ters " , ; ’ – . $ are used as separators or system object identifiers in TAC
Vista, and are thus illegal in signal names. The space character is not
allowed, but the characters “/ : _” are. It is also possible to use national
character sets (including e.g. å, ä, ö, ç) in signal names. A signal name
can be entered in quotes (“Signal_name”), but the quotes will be auto-
matically deleted. Signal names may not differ solely in the use of
upper/lower case characters. If so, they are considered to be identical
and an error message will be shown at compilation.
232 (450) TAC AB, Nov 2006

04-00030-01-en
6.2.3 Public Signals

Only a subset of the variables in an application program is of interest to
other nodes in the network, since many signals represent intermediate
calculations. Those signals which are of interest can be declared as pub-
lic signals, thus allowing other network nodes to read and where appli-
cable, also to modify their values. The set of all public signals forms the
program specification of the application program, which defines the
data exchange interface to other nodes.
The public signals in the program specification are classified as:
Table 6.2:
DIG Binary signal.

ANA Analog signal (real or integer).
Depending on whether other nodes will be allowed to read and/or mod-

ify the signal value, we may also classify the signal as read-only or
read/write, see Section 6.9, “Access Rules”
6.3 Connections
A connection is a link between the output of one block and one or more
inputs of other blocks. The connections are typed: they inherit the type
of output of the connected blocks. In the FBD, binary connections end
with empty arrowheads, while analog (real, integer) connections have a
filled arrowhead.
Connections are formed by various straight line segments. The points of
union between segments are called nodes. When a node joins two or
more segments on the screen, the node is displayed as a black circle to
differentiate it from two connections crossing each other. Normally, a
connection starts at a block output and ends at a block input. It is also
possible to have non-terminated connections. In this case, when only
connected to an output, it is represented by a small black circle, and if
only connected to an input, by a black square. However, unconnected
inputs are not allowed by the TAC Menta compiler, so they must be
connected before entering Simulation mode.
6.4 Function Blocks

The function blocks are described in the Reference section of this man-
ual. They are classified in four classes:
• Simple blocks
• Expressions
• Operators
TAC AB, Nov 2006 233 (450)

04-00030-01-en
• Test probes
6.4.1 Simple Blocks

There are various types, each with a specific functionality. Their com-
mon point is that they all have a fixed number of inputs and parameters.
Each simple block generates a single output signal.
Fig. 6.2: A simple block, ACCUM – Accumulator.

The parameters may be of different types with each type allowing a pre-
determined range of values, but always a numeric value or a list of
numeric values. There are two ways of specifying a number:
Table 6.3:
Number A decimal number in exponential format.

Constant An identifier of 20 significant characters
which must be defined in the Constants table.
(see Section 6.5, “Constants”).
6.4.2 Expressions
The expression block is a special block with a number of inputs, an
arithmetic expression (may be complex) but only one output. An
expression block will have as many inputs as there are variables
declared in the expression. The graphic representation of the expression
blocks may change, dependant on the expression size and the number of
inputs.
Fig. 6.3: An expression block.

The expression may contain:
Table 6.4:
Input Variable Single letters, which if capitalized (“X”) rep-

resent an analog input, but if in lower case
(“x”) the variable is a binary input. The input
variables are sorted in alphabetical order on
the left side of the block.
234 (450) TAC AB, Nov 2006

04-00030-01-en
Table 6.4: (Contd.)
Constants Can be Numeric: “5”, “–13”, “0.03”,

“1.25E12” etc. or Alphanumeric: “PI”,
“ENERGY” etc. The alphanumeric constants
are identifiers of 20 significant characters
which must be defined in the Constants table.
The constants can be entered in quotes. Pub-
lic constants are not allowed in expression
blocks.
Operators Operations such as “-” (change of sign), “*”
(multiplication), “+” (addition), “>>” (right
shift), “<” (less than) and “a ? b : c” (IF-
THEN-ELSE statement: “if a then b else c”).
There are three types of expression block depending on if the generated

output signal is of the type real, integer or binary.
6.4.3 Operators
An expression such as the one written on an expression block may be
graphically developed as various operator blocks interconnected by
connections. The result is completely equivalent.
Fig. 6.4: An operator, addition.

Several operator types exist, equivalent to those used in expression
blocks. Public constants are not allowed in operators.
The analog inputs may be connected to a real or an integer output, while
an analog output may be connected to either real or integer inputs. Spe-
cial operators are used to convert between real and integer signals, and
to convert between analog and binary signals.
The four elementary logical operators, NOT, AND, OR, XOR, are also
available as simple blocks. Since the logical block is a simple block, it
is compiled as that. But, every logical operator is compiled to a single
expression block, so it is better to use simple blocks instead of operators
in terms of memory and CPU efficiency. In any case, the difference is
very small, so using logical simple blocks or logical operators is mainly
a matter of taste.
6.4.4 Test Probes

For the simulation of application programs, a model of the controlled
system can be created using simple function blocks, expressions and
operators. Special blocks are required to sample the state of the physical
outputs and to write the calculated values to the physical inputs. These
TAC AB, Nov 2006 235 (450)

04-00030-01-en
test probes can only be used for simulation, it is not possible to generate
application programs which contain test probes.
Fig. 6.5: A test probe, TPAO – Analog output.

Four different test probes are available, which correspond to the four
types of physical signals: TPAO – Analog output, TPDO – Digital out-
put, TPAI – Analog input and TPDI – Digital input. They all have only
one parameter, which specifies the name of the tested input/output
block.
6.4.5 Function Block Groups

It is possible to move and copy a whole group of blocks and connections
at the same time, just by marking the elements which belong to the
group using a selection rectangle.
A group of blocks can also be saved as a macro block for use in other
application programs.
6.5 Constants
TAC Menta allows the definition of identifiers which represent constant
numeric values for use in parameters of blocks instead of a numeric
value. These identifiers we call constants and they are declared in the
Constants table.
6.5.1 Constant Names

Constant names (see Section 6.2.2, “Signal Names”) are alphanumeric
strings of up to 20 characters (equal to the OP display size and the max-
imum ID string length in TAC Vista). A constant name must not consist
of digits only. The characters " , ; ’ – . $ are used as separators or system
object identifiers in TAC Vista, and are not allowed in constant names.
The space character is not allowed, but the characters “/ : _” are. It is
also possible to use national character sets (including e.g. å, ä, ö, ç) in
constant names. A constant name can be entered within quotes
("Constant_name"), but these quotes will be automatically deleted.
6.5.2 Public Constants

Constants can be declared as either public or internal. By definition, a
constant cannot be modified by the application program in which it is
declared. However by declaring it as public it becomes available to
other nodes in the network and can be modified from, for instance, the
OP. In the FBD window, a public constant is marked with a ring “o” to
the right of the FB parameter field. The Module name of a public con-
236 (450) TAC AB, Nov 2006

04-00030-01-en
stant, which by default is the same as the Module name of the block, will
not be displayed in the FBD (unless it differs from the Module name of
the block).
We recommend that you always names blocks containing public con-
stants, otherwise the constants cannot retrieve/change Module names.
Note
It is important to note that public constants can be modified via the net-
work as well during runtime.
Public constants may only be assigned to one FB parameter, whereas
an internal constant may be assigned to any number of FB parameters.
The reason for this is that internal constant names are substituted with
the corresponding numerical values when the FBD is compiled. This
cannot be done with public constants, since the reference (pointer)
mechanisms in TAC Menta do not allow multiple references to one
public constant from several FB parameters during runtime.
A public constant may not be given the same name as a public signal.
Nor is it possible to define a public constant that is not used in any
block parameter.
Public constants are not allowed inside expression blocks, or in oper-
ators, see Section 6.4, “Function Blocks”.
Public constants are not allowed inside the binding parameters of I/O
blocks, see Section 6.6.1, “I/O Blocks”.
Public constants are also included in the program specification, but only
following compilation of the FBD. The public constant are classified as:
Table 6.5:
PAB Binary constant

PAI Integer constant
PAR Real constant
Depending on whether other nodes will be allowed to read and/or mod-

ify the constant value, we may also classify the constants as read-only
or read/write, see Section 6.9, “Access Rules”.
6.6 External I/O Signals

6.6.1 I/O Blocks
External I/O signals can be read into the FBD via four generic I/O
blocks (AI, DI, AO and DO). For the STR Wall Modules there are two
dedicated blocks (STRIN and STROUT) with the same purpose. The
TAC AB, Nov 2006 237 (450)

04-00030-01-en
generic I/O blocks can be associated with either a physical or a network

address; the STR blocks can only be associated with certain STR vari-
ables. This is called binding.
There are also two special I/O block types, CNT for digital input pulse
counting and DOPU for pulse width modulated digital outputs. CNT or
DOPU blocks cannot be bound to remote network addresses, due to
possible timing and synchronization problems.
The I/O blocks binding are listed in the I/O configuration table.
Public signals and constants in other devices in the network can be
imported through the I/O blocks by binding them to a network address
reference defined in the I/O configuration table. A typical case where
this function can be useful is allowing several controllers to share a sen-
sor signal of common interest, e.g. outdoor temperature, which is phys-
ically connected to one of them. Transfer of data between TAC Xenta
application programs should be programmed with the generic input
blocks (AI and DI) in accordance with the principle that you should
read data from other nodes and not write to them.
Public signals can also be imported/exported to other nodes in the net-
work through the I/O blocks by binding them via the SNVT option. This
function is primarily intended to be used for communicating with equip-
ment from other manufacturers, e.g. lighting or intelligent actuators, via
the network.
When bound to a physical terminal, the module number and terminal
reference are displayed next to the I/O block symbol, e.g. “M1-U3”
(module no. 1, universal input no. 3). When bound to a remote network
signal, “Net” or “SNVT” is shown instead of the terminal reference.
Depending on the I/O block type and binding, different sets of configu-
ration parameters are used, see the Reference Section of this manual.
The basic configuration parameters are:
• Physical terminal
• Network variable
• Online device
• SNVT
238 (450) TAC AB, Nov 2006

04-00030-01-en
Physical Terminal
Table 6.6:
Mod Number Of the base device is displayed by name, e.g.:

Xenta 301. The I/O modules are displayed by
module number and model, for example: M1
(422)
Terminal Ref. Character string indicating the type and num-
ber of the terminal (e.g. B1-B4, U1-U4, X1-
X4, Y1-Y4, K1-K4). When selecting the ter-
minal in the terminal reference selection
menu, a “#” after the terminal address indi-
cates that the terminal is already allocated.
Network Variable
Table 6.7:
Network Address Reference to a public signal e.g.

\RPU1\AHU1\OutdoorTemp (maximum
string length \20\12\20), in another TAC
Xenta device. The Network address in a DI
block must always correspond to a binary sig-
nal in the other device, whereas the Network
address in an AI block can either correspond
to a real or an integer signal.
To find a network address, click the browse
button ([…]). If connected to the TAC Vista
database, browse the database for a network
variable. If not connected to the TAC Vista
database, open an *.MTA file and browse the
file for a network variable.
Note
The output of the AI block is always real.
Delta The smallest change of value in the signal
which will initiate an update via the network.
Default value = 0.5.
Period Maximum time interval in seconds (integer)
between two updates of the imported/
exported value. Default value = 60. Whether
the signal has changed or not, the value will
also be updated when the time interval Period
has elapsed following the last update.
TAC AB, Nov 2006 239 (450)

04-00030-01-en
Note
Delta and Period must always be selected in such a way that a high
network load is avoided. Try to send signals via the network on a 60
or a 30 second basis, rather than every second.
Online Device
A generic DI block can be used to check if a remote device is online, by
using the “online device” binding option and specifying the network
address of the remote device in the I/O configuration table. This can be
used, for example, in applications where signals are imported from
other devices in the network, and where alternative actions must be
taken if communication is broken.
Table 6.8:
Device Address The device name entered as a character

string. The DI block output is true (1) if the
referenced device is online, otherwise false
(0). If Device address is the device’s own
address, the output will be false (0) when no
other node in the network can be found, oth-
erwise true (1).
SNVT
The SNVT option is used to import/export external signals via the net-
work. The signal is first given a SNVT name (which may differ from the
signal name) in the binding dialog, and then the defined SNVT variable
is bound to an external signal of the same SNVT type.
For a list of supported SNVT’s see Section 17.1, “List of SNVTs”.
Note
There will be no network communication between two bound SNVT
variables, unless either the output variable is set to Send a new value
periodically (or on Delta change), or the input variable is set to Poll
the output periodically.
240 (450) TAC AB, Nov 2006

04-00030-01-en
Table 6.9:
Type Variable type, selected from a pre-defined list

of supported types. The list is defined in the
TATYPE.INI file. Please contact TAC if the
requested SNVT type is not contained in the
pre-defined list. If the selected SNVT is of
the Structured type (indicated by a Type name
automatically being displayed in the Mem-
bers field), then the SNVT consists of several
variables, in which case the structure Mem-
bers must be represented (and bound) by a
single block each. For this purpose, there are
complete Macro blocks for all the structured
SNVTs in the TAC Macro block library;
please be sure to always use those!
SNVT Name The signal name as it will be stored in the
.XIF file and displayed in external tools. The
name must not exceed 16 characters.
Initial Value This parameter specifies the initial block out-
put value.
Period After external binding, the connection is
polled/updated when the time interval Period
has elapsed following the last update. If
Period is set to 0 in an AO/DO block, the
external variable will only be updated on
Delta/status changes.
Delta The smallest change of value in the signal
which will initiate an update via the network.
6.6.2 Public Parameters

In order to make an internal function block parameter accessible from
other nodes, its value must be specified using a public constant, see
Section 6.5, “Constants”. Public function block parameters can thus be
modified via the network, e.g. from the OP, during runtime.
Note
A public constant can only be assigned to one block parameter.
6.7 Modules
In a block, the Module name will be a part of the signal name (syntax:
Module name\Signal). The Module name can be entered or edited in all
TAC AB, Nov 2006 241 (450)

04-00030-01-en
blocks in a group at the same time. If a block belongs to a Module this

will be indicated by a purple and underlined block type name.
Fig. 6.6:
The Module concept enables you to divide the application program into
different systems, e.g. several heating groups. This provides two major
advantages:
• All public signals belonging to the same Module will be dealt with
together when being imported into a supervisory system (TAC
Vista).
• The same signal name can be used in different Modules, e.g.
AHU1\T1_SP and AHU2\T1_SP.
If a public signal belonging to a Module is used as a Network address in
a Network variable (TACNV), the Module name will have to be
included (syntax: \Device\Module\Signal), where “Device” is the TAC
Xenta Device name. Signals without Module names are addressed
\Device\Application\Signal, where “Application” is the Application
name as entered in the Name field of the Program specification table.
Alternatively, signals without Module name can be addressed
\Device\\Signal.
6.8 Hierarchical Function Blocks (HFB)

A better FBD overview can be achieved by means of grouping blocks
into a hierarchical function block (HFB). An HFB can contain other
compressed function blocks (other HFBs) and connections. Thus, you
can create HFBs on more than one level. The inputs and outputs are
made by certain blocks, for example, HFAI for an analog signal into an
HFB.
An HFB containing at least one signal which is defined as public, is
shown using a red dot in the upper right corner of the HFB symbol. Also
used when the public signal is located as an embedded HFB.
The HFB is a graphical solution in TAC Menta for grouping function
blocks, and can be printed. The program is downloaded to the TAC
Xenta device, not as hierarchical function blocks, but as an ordinary
242 (450) TAC AB, Nov 2006

04-00030-01-en
FBD. The diagrams below show an HFB on the top level, as well as on
the expanded level..
Fig. 6.7: HFB on top level
Fig. 6.8: HFB on expanded level
6.9 Access Rules

6.9.1 Signals
The right of access to a block output signal is defined by its access class:
Table 6.10:
RO Read-only.The signal may be read from the

OP and/or from other nodes in the network,
but not modified.
RW Read/write. The signal may be read and mod-
ified from the OP and/or from other nodes in
the network.
For some blocks, the only available access class is RO. This applies to
all blocks without internal states, where the computed output value
depends only on the current value(s) of the input signal(s). If the output
of such a block is modified via the network, the modification will not
have any effect on the output value computed by the application pro-
gram during the next program cycle. There are other block types, how-
ever, where it makes sense to allow external write operations on block
outputs. This is true, for example, for integrators and accumulators,
TAC AB, Nov 2006 243 (450)

04-00030-01-en
where the new value is computed by adding/subtracting an increment of

the previous output value. Thus by declaring the output signal as RW, it
can be reset via the network.
6.9.2 Constants
Public constants have the access class RW in the FBD. The desired
access class for OP display (RW or RO) is specified by the user in the
OP configuration tool.
6.10 Time Schedules

The time scheduling function is used for starting and stopping of an
object, e.g. an AHU. The function offers the possibility to define weekly
charts to start and stop the AHU at different hours, depending on the
day of the week. It is also possible to define exception schedules, called
holiday charts, during which the normal weekly charts would be over-
ridden by different operating hours. Time schedules are implemented as
a Time Schedule function block (TSCH) with a signed integer output,
where the sign indicates the time schedule status and the numeric value
indicates the time left (in minutes) to the next status change.
Each time schedule can consist of several weekly and holiday charts.
The number of weekly and holiday charts in each time schedule is
defined by two parameters in the TSCH function block. Holiday charts
can also be defined in TAC Vista via the central time schedule function.
6.11 Alarm Texts

An alarm text is a text string associated with an Alarm block. The alarm
text is included in the network alarm message generated when an alarm
is triggered. The alarm texts are edited using the Edit Alarm Text Table
function.
6.12 Local Trend Logging in the TAC Xenta

“Local Trend logging in the TAC Xenta” is a function for collecting
(logging) values and storing them in the TAC Xenta for transfer to TAC
Vista at a later time. In TAC Vista, the logged values can be stored, pro-
cessed and displayed. The function is often used in combination with a
dial-up connection between TAC Vista and TAC Xenta.
The measuring point can be any public real, integer or binary signal.
You can log rapid processes over a short time; i.e. at intervals of seconds
(minimum log interval 10 seconds), as well as longer processes at inter-
vals of days or weeks, e.g. water and energy consumption. Logged val-
ues are “time stamped” with the date and time. “Local Trend logging in
the TAC Xenta” can be defined from TAC Menta, but here no display
of the logged values is possible, only in TAC Vista.
244 (450) TAC AB, Nov 2006

04-00030-01-en
6.13 Data Files

During creation of the complete application program, the following data
file types are involved. Please note that all files related to a certain appli-
cation must reside in the same directory.
Table 6.11:
.AUT Text file with application program source

code and data including graphical block dia-
gram.
.TLG The trendlog definition.
.MCB Macro block file (Group of blocks).
.COD “Machine code” file in ASCII format for
downloading to the TAC Xenta controller.
.XLG The compiled trendlog definition.
.ESP Specification file with public signals, their
attributes etc. generated by TAC Menta. This
file contains input data to the OP configura-
tion tool.
.OPE A file with an empty tree, i.e. an OP tree
without a specification file. This is the kind of
file that is created when the OP configuration
tool is run from the program manager.
.OPC A mix of an .OPE and an .ESP file. This file
is created by the OP configuration tool when
it has been invoked from TAC Menta.
.BIN Binary file with OP menu tree data for down-
loading to the TAC Xenta controller together
with the .COD file.
.CHR National character set file for downloading to
the TAC Xenta controller together with the
.COD file.
.XIF External interface file containing a standard-
ized description of all network variables/
objects of the application program, which
enables binding and communication with
LonWorks nodes from other manufacturers.
TAC AB, Nov 2006 245 (450)

04-00030-01-en
Table 6.11: (Contd.)
.MTA Menta project file, which can include all files

(all types mentioned above except for .MCB
and .OPE) related to a certain application.
Once a file (e.g. .AUT or .OPC) has been
inserted (saved) in the project file, it can be
extracted (opened) anytime as an .MTA file.
The .MTA file can be stored directly in the
TAC Vista database.
Note
The .MTA file can be stored in the TAC Vista
database even though it is not compilable. An
.MTA file which is not compilable will not, of
course, be possible to download into a TAC
Xenta device. It must be correct and com-
pilable before download is possible.
In addition to the files listed above, the fol-
lowing data files are involved in the creation
of the .BIN file. These files are placed in a
specific directory for temporary files.
OPDOC.GOP An ASCII file created by the OP configura-
tion tool when the Generate command is
executed. This file is converted to an .SPT
file, which in turn is converted to a .BIN file.
OPDOC.SPT Intermediate ASCII file generated from the
.GOP file.
OPDOC.TMP Intermediate ASCII file generated from the
.GOP file.
Upon downloading, the following file is temporarily created as well:
Table 6.12:
BPR The Network Neighborhood file, describing

the TAC Xenta device’s surrounding network
nodes and groups.
246 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 7 The Mouse and Function Keys
7 The Mouse and Function Keys

7.1 The Mouse
The options for using the mouse vary depending on whether you are
working in Edit or in Simulation mode. The options primarily depend
on the action taken with the mouse. The possible actions are:
• Clicking the left button.
• Clicking the left button while pressing the Shift key.
• Clicking the left button while pressing the Ctrl key.
• Double-clicking the left button.
• Clicking the right button.
Secondly, each action has a different effect depending on the area where
the cursor is when the action is taken. The possible areas of action for
the mouse in the application program window are:
Table 7.1:
Block Rectangle composed of the yellow area in the

function blocks.
Output All function blocks have an exit which is rep-
resented by a small segment protruding from
the right hand side of the symbol.
Input Some function blocks have inputs which are
shown as arrowheads.
Connection This is any intermediate point on a direct line
connection segment.
Node The end points of a connection are denomi-
nated nodes.
Background Any area of the application program window
which is not one of the above areas belongs to
the background.
TAC AB, Nov 2006 247 (450)

04-00030-01-en
7 The Mouse and Function Keys TAC Menta, Technical Manual
Finally, the definitive option depends on the editing context. Various

possibilities exist for the context, distinguished by the cursor shape:
Table 7.2:
Normal The cursor is the classical arrow.

Block insert from The cursor is an arrow with a block.
Tool bar
Zoom in The cursor is a magnifying glass.
Group selected The cursor is an open hand.
Draw a connection The cursor is an X. The cursor symbol
changes to an X when it is possible to connect
to an input.
Open a selection The cursor is a cross.
rectangle
Draw a group The cursor is crossing arrows.
7.2 The Function Keys

Table 7.3:
Key Description
Delete Deletes a selected block or group of blocks.
F1 Help.
F2 Starts or stops (Toggle) the continuous execu-
tion of the application program. Same as
clicking on the Execute button in Simulation
mode.
F3 Stepwise execution of the application pro-
gram. Same as clicking on the Step button in
Simulation mode.
F5 Toggles between FBD and tabular simulation
mode.
F7 Searches for a block or a comment which con-
tains a given text string in the block name, the
block type or in a parameter. Same as the Edit
– Find command. The key works in both Edit
and Simulation mode.
248 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 7 The Mouse and Function Keys
Table 7.3: (Contd.)
F8 Searches for a given text string in comments,

block names and block parameters and
replace it with the entered text string. Same as
the Edit – Replace command in Edit mode.
F9 Moves the marked area to the center of the
screen. Same as the Edit – Center selection
command. The key works in both Edit and
Simulation mode.
F10 Resets the program cycle counter to zero and
all function block diagram signals to their ini-
tial state. Same as clicking on the RST button
in Simulation mode.
F11 Toggles between Online and Offline mode.
Same as clicking on the Online button in
Simulation mode.
F12 Toggles between Edit and Simulation mode.
CTRL+I Zooms in.
CTRL+O Zooms out.
CTRL+X Cuts text in dialogs.
CTRL+C Copies the selected group of blocks or copies
text in dialogs (same as Ctrl-Insert).
CTRL+V Pastes the copied group of blocks or pastes
text in dialogs (same as Shift-Insert).
CTRL+Z Undoes a deletion.
CTRL+Insert Copies the selected group of blocks or copies
text in dialogs.
Shift+Insert Pastes the copied group of blocks or pastes
text in dialogs.
Tab Zooms in (same as Ctrl-I).
Esc Cancels the operation (same as Cancel button
in dialogs).
Arrow key Moves the FBD window in the direction of
the arrow key (Left, right, up or down).
Available in both Edit and Simulation mode.
TAC AB, Nov 2006 249 (450)

04-00030-01-en
7 The Mouse and Function Keys TAC Menta, Technical Manual
Table 7.3: (Contd.)
Shift+Arrow key Moves the FBD window one screen page in

the direction of the arrow key (Left, right, up
or down). Available in both Edit and Simula-
tion mode.
CTRL+Arrow key Moves the cursor in the Trend logging win-
dow one sample in the direction of the arrow
key (Left or right).
250 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 8 Edit Mode
8 Edit Mode
When TAC Menta is started by the user, it always starts in Edit mode.
In this mode, the main window consists of a single pane in the client
area with two scroll bars. This window is called the diagram window
since it is here the FBD will be created.
8.1 Function Blocks

8.1.1 Creating a New Block
Using the NEW Pop-Up Menu
To create a new block in the application program window, follow these
steps:
8 Select the class of block which you wish to create in the NEW
pop-up menu.
Note
If the class of new block is the same as the last block created, you will
simply be able to double click on the background.
9 After the first step, the block selection dialog will appear. The dia-
log differs depending on the class selected: For the classes Simple
block, Operator and Test probe, the dialogs are very similar. There
are three ways to make the selection:
a Double click on an element in the list of types.
b Click on an element in the list and accept (OK).
c Manually enter the type of the block and accept (OK).
Exiting by selecting Cancel will abort the creation of the
block.
For the Expression class, the selection dialog is the same as the
editing, which we will cover in the next section.
10 On closing the dialog, a new block will appear at the cursor posi-
tion where you clicked during step 1. If the block does not have
enough room, it will appear as a floating selection on the window
background.
TAC AB, Nov 2006 251 (450)

04-00030-01-en
8 Edit Mode TAC Menta, Technical Manual
Duplicate an Existing Block

A simpler way of creating a block, when an equivalent one already
exists, is to duplicate the existing block. Right-click on the block you
wish to duplicate and select Duplicate in the pop-up menu BLOCK .
An HFB cannot be created this way.
8.1.2 Editing a Block

All the function blocks have a certain amount of configurability which
is specified in the Edit block dialog. This dialog varies slightly depend-
ing on the type of block selected.
There are two methods of obtaining the Edit block dialog:
1 Double click on the block.
2 From the pop-up menu BLOCK, select the input Edit.
A simple Edit Block dialog is shown below.
The Edit Block dialog contains the following fields:
Table 8.1:
Identifier This is the identifier of the block which appears

in the top left hand corner of the block in the dia-
gram. This identifier is also associated with the
name of the output signal. You do not need to
complete this field unless the signal is defined as
public, or if the block is an I/O, ALARM or
TSCH block. A maximum of 20 characters is
permitted. (see Section 6.2.2, “Signal Names”).
Unit A unit from the pre-selection list can be selected.
The unit is transferred into TAC Vista, if this is
being used. It is not obligatory to fill in this field.
252 (450) TAC AB, Nov 2006

04-00030-01-en
Table 8.1:
Description In this field, a description of the block can be

made by typing any combination of up to 40
characters, with the exception of ’. The descrip-
tion is transferred into TAC Vista, if this is being
used. Filling in this field is not obligatory.
Public If Public is selected, the output from the block
will be considered as a public signal and
included in the Program specification.
Read/Write If Read/Write is selected, it will be allowed to
modify the block output signal from other net-
work nodes during execution of the application
program in a TAC Xenta device and manually
during offline simulation. The Read/Write
option cannot be selected in blocks with RO
access only.
Backup If this option is selected, a warm start is done
with the current value of the block output and
internal states in the RAM. If not, before a warm
start the block output and internal states are reset
to their initial values (same as for a cold start). If
a power outage lasts for more than 72 h and the
RAM contents are lost, the restart will always be
a cold one and all blocks will be reset to their ini-
tial states, regardless of whether the Backup
option is selected or not.
Mode 2 This option, only available for operators with
two inputs, determines whether the operator is
graphically displayed with the inputs over/under
the symbol ( – Mode 2 selected)
or left of/under ( ) it.
Description This field indicates the type of access (RO or

RW) and the data type (real, integer or binary) of
the output signal, and the memory which the
block occupies in the RAM of the TAC Xenta
device when compiled.
TAC AB, Nov 2006 253 (450)

04-00030-01-en
Table 8.1:
Parameters A list of the parameters appears, which may con-

tain none or various, depending on the type of
block in question. In the generic I/O blocks, the
Parameters section of the dialog is replaced by a
Bind button, which opens the I/O Binding dia-
log. Please refer to Section 6.6.1, “I/O Blocks”
for further details. Clicking on the Help button
in the lower right corner of the dialog displays a
detailed description of this block type on the
screen.
8.1.3 Moving a Block

To move a block in the application program window, it must previously
have been selected by opening a selection rectangle. This technique is
described in Section 8.3, “Operations on Groups”.
8.1.4 Deleting a Block

To delete a block from the FBD, right-click on the block in the normal
editing context to obtain the pop-up menu BLOCK and select the entry
Delete. Alternatively, mark the block and press the Delete key.
8.1.5 Disconnecting a Block

The following options are provided to eliminate connections which start
and/or end in a block:
If the block and all its connections are to be totally disconnected, right-
click on the block and then select Disconnect from the pop-up menu
BLOCK.
If just the connection is to be eliminated, right-click on the input, output
or connection and then select Disconnect/Delete node from the pop-up
menu.
At times, a disconnection is required without eliminating the connec-
tions lines; for example, to substitute one block for another of a different
type, or to move a connection from one place to another etc.:
1 To disconnect an input, click on the input using the left or right
mouse button and from the pop-up menu INPUT select Detach. In
either case, the connection is grabbed by the mouse cursor and
switching to the context drawing a connection occurs (see
Section 8.2.1, “Drawing a Connection”).
2 To disconnect an output, click on the output using the right button
and from the pop-up menu OUTPUT select Detach. Using this
operation, the group of connections beginning at the output are
254 (450) TAC AB, Nov 2006

04-00030-01-en
grabbed and may be moved to another place on the diagram (see

Section 8.2.3, “Moving a Node”).
8.2 Connections
8.2.1 Drawing a Connection
When you draw a connection, the mouse cursor appears as an X and is
tracked by a green, elastic straight line which is always fixed at one of
its end points. To draw a connection, follow these steps:
1 Initiating the Connection
There are various options:
a The connection starts in a block: click using the left button on
the output of the block.
b The connection starts in a node: click using the left button on
the node or click the right button, and select Create Node
from the pop-up menu CONNECTION.
c The connection starts in another connection: right-click on the
connection, and select Create Node from the pop-up menu
CONNECTION.
d The connection starts in the background area: right-click on
the background, select Node… from the pop-up menu NEW
and select the desired type of connection (real, integer or
binary) in the sub-menu.
In every case, a green, elastic connection will track the cursor.
2 Drawing the Connection
Move the cursor to the point where a break point is to be made and
left-click. The floating connection will be converted into a real con-
nection and a new floating connection will be started from the
break point. This step may be repeated as many times as necessary,
creating a connection made up of various consecutive segments. If
the shift key is pressed while the cursor is being moved (and the
Orthogonal connections function is not activated), the connection
will only adopt angles which are multiples of 45 degrees.
3 Deleting the Last Segment of the Connection
Each time the right button is pressed while drawing a connection,
the last segment of the connection will be deleted.
4 Ending the Connection
To end the connection in the input of a block, left-click the input.
The cursor symbol changes appearance when the it is possible to
connect to the input. To let the connection remain unterminated in
some point, double click the left button on the background.
TAC AB, Nov 2006 255 (450)

04-00030-01-en
8.2.2 Deleting a Connection

To delete a connection, right-click on any point on the connection to
open the pop-up menu CONNECTION and select Delete. This may
also be reached via the pop-up menus INPUT and OUTPUT in Discon-
nect. Alternatively, draw a selection box around the connection and use
the Delete button.
8.2.3 Moving a Node

To move a single node, right-click on any point on the node to open the
pop-up menu CONNECTION and select Move node. Alternatively,
draw a selection box around the node. The node will be changed to elas-
tic connections and will follow the movement of the cursor. To drop the
node on the diagram, left-click.
8.2.4 Breaking a Connection

To break a connection at an intermediate point, right-click on the con-
nection and from the pop-up menu CONNECTION, select the entry
Detach. The connection will break into two pieces and the context
draw a connection will be entered (see Section 8.2.1, “Drawing a Con-
nection”).
There are two ways to separate a connection from an input: left-click on
the input or right-click, open the pop-up menu INPUT and select
Detach. In either case the last connected segment of the connection will
become elastic and the draw a connection context will be entered.
To separate a connection from an output, rigt-click on the output and
from the pop-up menu OUTPUT select Detach. Automatically, all the
joined connections will become elastic and the move group context will
be entered (see Section 8.2.3, “Moving a Node”).
8.2.5 Highlighting a Connection

To highlight a connection (including all its branches), right-click on the
connection and from the CONNECTION pop-up menu select Mark.
The connection will then be displayed in a different color, making it
easier to track it across the FBD. To return to the normal connection dis-
play, click the right button on the connection and from the CONNEC-
TION pop-up menu select Unmark.
8.2.6 Orthogonal Connections

The orthogonal connections mode is active by default, but can be
changed in the Preferences menu. When the orthogonal connections
mode is active, two or three orthogonal segments are created when
drawing a connection. When starting in a node on another connection,
only two segments are created. The triple segment connection is only
activated when tracing a connection from a block output. In this case,
256 (450) TAC AB, Nov 2006

04-00030-01-en
pressing the CTRL key while dragging the connection allows the user
to fix the vertical segment in a certain position.
When drawing a connection, the mode of the current segment can tem-
porarily be changed from orthogonal connections to non-orthogonal
connections and vice versa, by pressing the CTRL and Shift keys simul-
taneously.
8.3 Operations on Groups

To perform operations on a group, the blocks and connections which are
to belong to the group must first be selected and contained in a selection
rectangle, whereas the cursor is shown as an open hand. In this context,
whenever the right button is clicked, the pop-up menu GROUP will
appear.
8.3.1 Selecting a Group

To mark a group, click and hold the left button, where one of the four
corners of the selection rectangle is to be situated. The mouse cursor
will change to a cross, and a green elastic rectangle will follow the cur-
sor movements. Keep the button depressed, and move the cursor to the
opposite corner of the rectangle. On releasing the left button, both nodes
and blocks inside the rectangle will be marked as selected. A connection
may be partially selected if either its start or its end, but not both is
selected, or completely selected if both start and end are selected.
Once a selection rectangle has been opened, individual blocks or nodes
may be selected or deselected by left-clicking on the block or node
while pressing the shift key. This operation acts like a toggle, i.e.: if the
element is selected, it will be deselected and vice versa. On selecting an
element outside of the rectangle, the rectangle will increase in size to
contain the element.
To select a single block of the diagram there are two faster methods
which open a selection rectangle containing the block. The first is to
left-click on the block while keeping a shift key depressed. The second
is to open a small selection rectangle which is completely within the
block.
To select the entire FBD, use the option Select all in the Edit menu on
the menu bar. This option opens the smallest rectangle which contains
the complete FBD.
8.3.2 Deselecting a Group

To eliminate the selection rectangle without performing an operation on
the selected group, just left-click outside of the rectangle. Another alter-
native is to right-click inside the window and select Deselect from the
pop-up menu GROUP.
TAC AB, Nov 2006 257 (450)

04-00030-01-en
8.3.3 Moving a Group

Once a selection rectangle has been opened, move the group of elements
selected by clicking inside the selection rectangle without releasing the
left button. Automatically, the group of selected elements will appear
floating on the screen. This entails that:
1 The selection rectangle will change from green to red.
2 The mouse cursor will change to a cross with arrows, to indicating
that we are in the drag context.
3 The selected blocks and the completely selected connections will
be converted to floating; i.e. blocks or connections made up of
dashed lines will appear.
4 The segments of the partially selected connections will be con-
verted to elastic connections, with the connections drawn in green.
While the left button is kept depressed, the group stays floating and will
follow the cursor movements. The elastic connections stretch and con-
tract one of their end points while the other remains fixed.
If the mouse is moved outside of the diagram window, the display will
be scrolled in the direction in which the mouse has moved. When the
button is released, a calculation is performed to determine whether
overlap exists between the floating elements of the group and those
below. This process may consume an appreciable amount of time, if the
diagram contains many elements. If no overlap exists, the group will
drop again onto the diagram and will be redrawn normally. However, if
an overlap does exist, the selected group will remain floating and will
have to be grabbed once again to drag it to an area where there is no
overlap.
8.3.4 Disconnecting a Group

To eliminate the connections selected in a group, select Disconnect
from the pop-up menu GROUP. If at least one partially selected con-
nection exists in the group, only these types of connections will be elim-
inated. If none of these connections exist in the group, all the completely
selected connections will be eliminated.
8.3.5 Deleting a Group

To delete a group, select Delete from the pop-up menu GROUP, or
mark the group and press the Delete key.
8.3.6 Entering or Editing the Module Name

To open the dialog box in order to enter or edit the module name in all
selected blocks, select Module from the pop-up menu GROUP.
258 (450) TAC AB, Nov 2006

04-00030-01-en
8.3.7 Copying and Pasting a Group

To copy a selected group, select Copy from the pop-up menu GROUP
or Copy from the Edit menu. When a group is copied, all of the selected
blocks (including all the signal and parameter names and settings) as
well as the connections which have segments selected are copied to an
internal buffer. To paste the contents of the buffer, the marked area has
to be unmarked. Select Paste from the NEW pop-up menu or Paste
from the Edit menu.
8.3.8 Copying a Selection Rectangle to the Clipboard

This option is used to copy the selected part of the FBD to the clipboard
in order to to export it to other applications in metafile format. This is
achieved by selecting Copy to clipboard from the Edit menu on the
menu bar. If you prefer to copy the figure in black and white, the corre-
sponding option should be selected from the Preferences menu.
8.3.9 Centering the Selection Rectangle

To move a selected group to the center of the screen, select the option
Center selection from the Edit menu. The function key F9 is a shortcut
for this function.
8.3.10 Printing the Selection Rectangle

If an opened selection rectangle exists and Print is selected from the
menu File, only the portion of the FBD contained in the selection rect-
angle will be printed. However, you must select the Scale output to one
page option under Options in the Print dialog as well, otherwise the
size of the printout will be wrong.
8.3.11 Macro Commands in Comment Blocks

Before saving a group as a macro block, the programmer can add macro
commands to be executed when the macro block is loaded. One typical
use for this is when default text strings in signal names, network
addresses or SNVT names are to be replaced with plant-specific texts.
The macros are created by entering the following commands in a com-
ment block:
Table 8.2:
$MESSAGEBOXEnter text$ A message box containing the mes-

sage “Enter text” will be displayed.
Click OK to continue.
TAC AB, Nov 2006 259 (450)

04-00030-01-en
Table 8.2:
$REPLACEText$ A replace dialog will be displayed.

Enter a text string and click OK to
search for the given text string
“Text” in comments, block names
and block parameters and replace it
with the entered text string.
$REMINDEREnter text$ A message box containing the mes-
sage “Enter text” will be displayed.
Click OK to continue. The
Reminder messagebox will not only
be displayed the first time the
macro block is loaded, but every
time the application program con-
taining the macro is opened.
$PLAYSOUND- The file wav.wav will not only be
WAV.WAV$ played the first time the macro
block is loaded, but every time the
application program containing the
macro is opened.
Note
Macro commands are executed in order from top to bottom. The first
Replace command will replace, in all blocks, the first appearance of
the text string, the second Replace command will replace the second
appearance, and so on.
8.3.12 Saving a Macro Block

To save a group of blocks and connections as a macro block from the
pop-up menu GROUP, select Save. On selecting this option, the stan-
dard save dialog will appear, and the name, extension (.MTA/.AUT),
path and disk of the file where the group is to be saved will appear.
Note
Only completely selected connections are saved in the macro block,
see Section 8.3.1, “Selecting a Group”
When a selected group of blocks is saved as an MTA/AUT file, only the

block definitions and connections are saved. Saving a selected group of
blocks as an AUT file is not the same as saving the same set of blocks
using the File – Save command. In the first case, only the information
stored in the marked blocks and connections is included in the saved
260 (450) TAC AB, Nov 2006

04-00030-01-en
file, whereas in the second case, a lot of other information such as con-
stant values, specification data (author, type etc.) is included in the file.
8.3.13 Loading a Macro Block

Using the NEW Pop-Up Menu
A previously saved macro block is loaded from the disk via the pop-up
menu NEW, and selecting Load group. On selecting this option, the
standard open dialog will appear, permitting the selection of the name
and path to be entered. It is possible to choose between an old macro
block (.MCB) and an application program (.MTA/.AUT). The group
will be loaded at the point where the mouse button was clicked to show
the menu. When loading an .MTA/.AUT file which has been saved as a
complete application program, only the FBD and the constant names are
loaded, and no other specification data. The new constants are added to
the Constants table, but if a constant already exists, the old value will be
kept (This applies to both public and local constants).
The default Load group search path, e.g. to a macro block library, can
be specified in the Settings command in the Preferences menu.
Changes to this information will be saved between subsequent sessions.
Note
Only constant names, not constant values, are stored in macro block
(.MCB) files. Thus, the values of constants used in a macro block will
not be imported when a macro block is loaded into an application pro-
gram. If a macro block containing constants is loaded, the new con-
stants will not be added automatically. Instead, the error message
“Undefined constant” is shown when the FBD is being compiled. This
also applies to .AUT files created using the Save Group command.
Using Windows Explorer

Alternatively, a previously saved macro block can be loaded from the
disk via Microsoft® Windows Explorer. Use the drag and drop tech-
nique to load the macro block from the macro block library into the
FBD.
8.4 Hierarchical Function Blocks (HFB)

8.4.1 Creating an HFB
Depending on the situation, you can create HFBs in two ways:
You can create an HFB and then embed function blocks and connec-
tions into it. In this case, select HFB from the NEW pop-up menu and
name the HFB. Then open the HFB via Expand HFB from the
BLOCK pop-up menu.
TAC AB, Nov 2006 261 (450)

04-00030-01-en
If you already have function blocks and connections that you want to
make into an HFB, drag the cursor around a group of function blocks
and select Create HFB from the GROUP pop-up menu. Please note
that you cannot undo a Create HFB command. For this reason, saving
your application before you create an HFB is strongly recommended.
8.4.2 Naming an HFB and Connections

Naming the HFB and connections is done similarly to naming blocks.
However, the HFB signals cannot be made public.
Assigning a name to the HFB is done in the Edit dialog, which is auto-
matically displayed when you create the hierarchical function block. If
you close the dialog box by clicking the Cancel button, no HFB will be
created. It is possible to create more than one HFB level, which means
that you can embed one or more HFBs within an existing HFB. A field
in the status row at the bottom of the application program window indi-
cates the hierarchical level on which the FBD is shown.
An HFB may have several inputs and outputs which must have unique
names within the relevant HFB level. These input and output block
types are called “HFAI” or “HFAO” (analog) and “HFDI” or “HFDO”
(digital), respectively. The inputs and outputs are only displayed on the
expanded level.
Note
These I/O-blocks are only a graphical solution in TAC Menta. They
are not downloaded to the TAC Xenta, entailing that these signalscan-
not be read from TAC Vista or the TAC Xenta OP.
You create the connections within an HFB diagram by selecting the

HFB I/O command in the NEW pop-up menu. Please note that you
have to expand an HFB level before creating its connections. If you cre-
ate an HFB by dragging the cursor around the existing blocks and then
selecting the Create HFB command, only the connections lying par-
tially within the marked area will be displayed in the HFB with default
names; upper-case letters for the analog types and lower-case for the
digital types.
If you create or rename a module that includes an HFB, the HFB and all
the levels below it will belong to this module.
8.4.3 Expanding and Compressing an HFB

The interior function block structure of an HFB is displayed on the
screen by selecting the Expand HFB command from the BLOCK pop-
up menu after right-clicking the HFB. The expanded HFB diagram is
compressed again by selecting the Compress HFB command from the
NEW pop-up menu.
262 (450) TAC AB, Nov 2006

04-00030-01-en
8.4.4 Printing out an HFB

Selecting the Print command in the File menu bar, gives you a printout
of your HFB diagram. In the printout dialog, the “FBD” field has to be
marked. If you select the “All levels”, you will get a printout of each
HFB level on separate pages with its name and with the page number,
at the bottom of the page. For example, if the HFB name is equal to
“ALARMS”, the page numbers will be “ALARMS1.1” and
“ALARMS1.2”respectively, if the printout range is two pages in total.
If you select “Current level”, you will get a printout of the current level
of the HFB when doing the printout.
8.5 Constants Table

Constants are declared in the Constants table. In this dialog, constants
may be added, modified, eliminated or simply viewed. The constants
table is opened by selecting Constants table in the menu Options on
the menu bar.
8.5.1 Adding a Constant

When editing a function block, an identifier can be specified as a param-
eter, still not yet defined in the Constants table. Then, when you are
attempting to close the dialog using the OK button, the edit constants
dialog appears. In this dialog, the constant will appear in the Identifier
field and the default value is set to 0. The user may alter the default
value and define the physical devices in which the parameter value is
measured. You must also define whether the constant is Public, i.e. if it
is to appear in the Program specification.
The constant units are similar to those of the blocks. In the Description
field, you can enter a description of the constant. Another way to add a
constant to the table, is to select the Add… button in the Constants table
dialog. The edit constant dialog will appear as before, but this time with
the Identifier field blank.
8.5.2 Editing a Constant

To change any of the constants in the Constants table, double-click the
constant. This operation causes the edit dialog of the selected constant
to appear, in which all of the fields, except for Name, may be modified.
The constants can be edited in both Edit mode and Simulation mode.
8.5.3 Removing a Constant

To delete a constant from the table, first select it by left-clicking on it.
The selected row is shown in reverse video. If the Delete button is
clicked, the selected constant will be deleted from the table.
TAC AB, Nov 2006 263 (450)

04-00030-01-en
8.6 I/O Configuration Table

The I/O configuration table is opened by selecting the input I/O config-
uration table in the Options menu on the menu bar. From this dialog,
I/O bindings may be defined, modified or simply viewed. The table con-
tains a list of all the I/O signals in the FBD.
The table has four columns: the signal name, the I/O block type, and the
type and address of the external signal to which the signal is bound
(physical input/output, network reference etc.). There is also an Overide
column.
The signals are sorted by name in alphabetical order. It is possible to
resort the list by clicking on the name of each of the columns. When
clicking on a column name, the list is re-sorted according to that column
in ascending order. By clicking a second time on the same column, the
list is re-sorted in descending order.
To edit the binding of an I/O signal, either left-click once on one of the
rows of the I/O configuration table to select it and then click on the Bind
button, or double-click on one of the rows in the I/O configuration table.
This operation opens the Edit I/O Binding dialog of the selected signal,
where the binding may be modified.
Depending on the type of I/O block and the type of binding, there are
several different Edit I/O Binding dialogs. Each binding type also has
its own specific set of configuration parameters, please refer to the ref-
erence section of this manual.
Note
When you are selecting terminals in the terminal reference selection
menu, “#” after the terminal address indicates that the terminal is
already allocated.
Constant names cannot be assigned to I/O configuration parameters.
8.7 Time Schedule Table

A dialog with a table of all time schedules in the FBD opens when you
select the command Time schedule table in the Options menu on the
menu bar. The entries in the Time schedule table are sorted by name in
alphabetical order. To change any of the time schedules in the table,
double click the left button on the row containing the time schedule to
be edited, or select a time schedule by clicking once with the mouse but-
ton on the row and then clicking on the Edit button. This operation
causes the edit dialog for the selected time schedule to appear, in which
week and holiday charts may be modified, added, deleted or simply
inspected.
Time schedules can also be modified during simulation, but the number
of week and holiday charts can only be modified in Edit mode.
264 (450) TAC AB, Nov 2006

04-00030-01-en
8.8 Alarm Text Table

The Alarm Text Table is entered via the Alarm text table command in
the Options menu on the menu bar. A dialog containing all the alarm
blocks and corresponding alarm texts (also for TAC Vista) in the FBD
will open. The alarm text columns can be sorted in any order. To alter
an alarm text, double click the left button on the row containing the
alarm text to be edited, or select the alarm text by clicking once with the
mouse button on the row and then clicking on the Change button. This
operation causes the Edit Alarm Text dialog for the selected alarm to
appear, in which the alarm text can be edited or simply inspected.
8.9 Local Trend Logging in TAC Xenta

The local trend logs are defined when you create the TAC Xenta appli-
cation program (i.e. the .MTA-file). The number of possible log chan-
nels is specified in the application. The number of log channels is
limited by the general application size.
The dialogs in TAC Menta for defining the function “Local Trend log-
ging in TAC Xenta” are opened by selecting Trend logs in the Options
menu. The addition of trend logs in a current application is done in two
ways:
• From TAC Menta, you can export the .MTA-file from TAC Vista
and add log definitions in TAC Menta. Insert the application again
in TAC Vista via a description file and download this to the current
TAC Xenta-device, or
• Create a trend log object from TAC Vista and allocate this to an
available physical resource for an unallocated log in the .MTA-
file. Define the log object to a public signal and select the log
space and log interval. This new data will update the .MTA-file
upon exporting the application program from TAC Vista.
Note
If you alter the attributes logged signal, log interval, log space, do not
stop if logically activated, empty log upon activation or the type of log-
ging (cyclical/non-cyclical log) of an existing log definition and
download it to the TAC Xenta device, the running loggings will be
stopped and all logged values will be lost. You will recieve a warning
before this change.
TAC AB, Nov 2006 265 (450)

04-00030-01-en
8.9.1 Selecting a Trend Log
Table 8.3:
Max number of Enter the maximum number of trend logs that

logs will be possible to define in the current applica-
tion (0–50). This number cannot be changed in
TAC Vista. Unused trend logs, for example,
trend logs that have not been defined or assigned
a name, will be named “LOG<no.>”, e.g.
LOG04, LOG05 and so on.
Name Presentation of the trend log name (see section
below).
Descriptions Presentation of the trend log description (see
section below). You can remove defined trend
logs by reducing the “Max number of logs”.
8.9.2 Defining a Trend Log

The dialog for defining the selected trend log is reached either by click-
ing the Edit button or by double-clicking the marked log. The dialog
contains the following fields:
Table 8.4:
Name Define the trend log name (maximum 20 charac-

ters), e.g. “TempRoom205”. Upon importing the
description file, created in TAC Vista, a log
object and a physical resource were created with
this name. The name of the physical resource
cannot be changed in TAC Vista.
Description Assign a trend log description (maximum 40
characters), e.g. “Temperature logging room
205”.
266 (450) TAC AB, Nov 2006

04-00030-01-en
Signal
Table 8.5:
Logged Signal Click the Browse button to choose the required

log point, which must be a public signal (binary,
real or integer) in the current application.
Hysteresis The smallest change in the logged value (real or
integer) which will initiate a new logged value.
Example: enter a hysteresis of 0.5 to disregard
temperature changes smaller than ±0.5 °C. If no
hysteresis value is entered, the default value 0.5
will be used. If a hysteresis of 0.0 is entered, all
loggings will be stored even if the value of a log-
ging is the same as the previous logging.
Log Interal Enter the required log interval (10 seconds – 530
weeks), i.e. the time between loggings.
Log Space Enter the required log space (unit: time).
Control
Table 8.6:
Activation Select Manual-Off, Manual-On or Automatic.

Start Time When manually activated (Manual-On), you can
choose the date and time for starting the logging.
Logic Variable When automatically activated (Automatic), you
can choose to control logging with a logical vari-
able (a public binary signal) in the current appli-
cation. Choose the signal via the Browse button.
Do Not Stop if Select the check box to prevent the stopping of a
Logically acti- logging that was activated by a logical variable,
vated even if the logical variable de-activates the log-
ging. Logging will continue until it is stopped
manually, by choosing Manual-Off, or until the
log becomes full.
Empty Log Select this check box to clear the trend log when
Upon Activation it is activated.
Logging Type
Select one of four possible logging types. Cyclical log storage means
that the logging will continue when the log space is full, the oldest val-
ues then being overwritten by the new values.
• Cyclical log in TAC Xenta, cyclic storage in TAC Vista
TAC AB, Nov 2006 267 (450)

04-00030-01-en
• Cyclical log in TAC Xenta, non-cyclic storage in TAC Vista

• Cyclical log in TAC Xenta, no storage in TAC Vista
• Non-cyclical log in TAC Xenta, no storage in TAC Vista
Table 8.7:
Log Space in If an alternative that includes storage in TAC

TAC Vista Vista is chosen above, specify the required log
space in TAC Vista, e.g. 10 weeks.
Fetch (Retrieve) At the specified percentage, (e.g. 80%), the
at % Full logged values are retrieved from the TAC Xenta
device and stored in TAC Vista. When a TAC
Xenta is connected to a TAC Vista, the TAC
Xenta will communicate with TAC Vista when
the specified precentage is reached.
Fetch (Retrieve) At the specified percentage (e.g. 60 %), the
if Connected logged values are retrieved from the TAC Xenta
and % Full device and stored in TAC Vista, if the connection
between TAC Vista and TAC Xenta is made for
another reason. However, during slowpoll, the
logged values are always retrieved.
8.10 Setting Date and Time

The user may set initial date and time values for offline simulation
(enables testing functions, dependant on date & time of day) via the Set
date and time command in the Options menu. If this is done in online-
mode, the time will be changed in the TAC Xenta device.
8.11 Finding and Replacing a Text String

The Find dialog is entered via Find in the Edit menu, or via function
key F7. You can search for a block or a comment which contains a cer-
tain text string in the block name, the block type or in a parameter. The
first block where a match is found is highlighted with a green selection
box. The dialog also contains buttons to search for the next match,
whole words and case sensitive.
The Replace dialog is entered via Replace in the Edit menu, or via
function key F8. You can search for a given text string in comments,
block names and block parameters and replace it with the entered text
string. The first block where a match is found is highlighted with a green
selection box, for confirmation. Then, click the Replace button to
replace the text string, or click Find next to search for the next match
without replacing the text string. When replacing, only the first appear-
ance found in the block will be replaced, if Replace only first appear-
ance is checked, otherwise all appearances in the block will be replaced.
268 (450) TAC AB, Nov 2006

04-00030-01-en
The dialog also contains buttons for case sensitive searches, searches
for whole words and the replacement of matches in all blocks (Replace
all).
Note
The following functions in the Find and Replace dialogs:
Checking the Signal and Constant names box means searching for the
text string used as a Signal name in block identifiers, in constant
names, in network addresses and in SNVT names.
Checking the Module names box means searching for the text string
used as a Module name in block identifiers, in constant names, in net-
work addresses and in SNVT names.
Checking both the Module names and the Signal and Constant names
box means searching for a text string containing both the Module
name and Signal name, e.g. AHU01\TS, in block identifiers, in con-
stant names, in network addresses and in SNVT names. Note, how-
ever, that in this case, changing the Module name is not allowed.
The program will not always do a string length check in a name after
executing a Replace command. So, please check carefully that the
Module name does not exceed 12 characters, and that the Signal and
Constant names do not exceed 20 characters after executing a Find
and Replace command.
When the Search for field is empty, all blocks of the marked block
type(s) will be searched for.
The most recent unique search and replace strings are saved and can
be retrieved via the dialog.
8.12 Undo
The Undo command is executed via Undo in the Edit menu, or via keys
Ctrl-Z. You can undo a deletion of one or more selected function blocks,
including the connected nodes. If the area covered by the deleted func-
tion blocks and connected nodes is too big to fit into the screen, the
upper left corner of this area will be shown.
Using the Undo command, it is possible to make one step backwards. If
another command, except File/Save, is executed, the Undo command
will be disabled. Example: if you delete a function block and then, for
instance, open a hierarcical function block diagram, you will not be able
to undo deletion of the function block.
TAC AB, Nov 2006 269 (450)

04-00030-01-en
270 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 9 Simulation Mode
9 Simulation Mode
Once the FBD has been created and correctly designed, you may go
from Edit mode to Simulation mode, in which the application program
may be executed in order to study the behavior of the signals. In online
mode, signal behavior is simulated in real time. In this mode of opera-
tion, the application window is made up of two panes, the diagram win-
dow and the trend logging window:
Fig. 9.1:
The two panes are separated by a separator which may freely be moved
to change the proportions of the two windows. To move the separator,
click on it with the left button and hold, move the cursor sideways. On
releasing the button, the sizes of the two panes will be recalculated.
Double clicking the left button on the separator will switch between ver-
tical and horizontal separation of the panes. The diagram window dis-
plays either the FBD or a table (Tabular mode) containing all public
signals and parameters, sorted in alphabetical order. There are a number
of buttons exist the two windows. The buttons on the left are used to
manage the physical inputs, The buttons at the top are for controlling the
execution of the application program.
9.1 Compiling the FBD

The step of moving from Edit mode to Simulation mode is achieved by
selecting the Simulate entry from the Options menu or by pressing the
function key F12. Before changing mode, the current FBD is automati-
cally saved to the AUTOSAVE.AUT file, if so selected in the Settings
dialog in the Preferences menu. In this way, the FBD will be saved,
even if the program is interrupted.
TAC AB, Nov 2006 271 (450)

04-00030-01-en
9 Simulation Mode TAC Menta, Technical Manual
When the mode is changed, the application program is automatically

compiled. The compiler first processes those blocks that have no input.
This is important for test probe blocks (seeSection 9.3.3, “Simulation
Using Test Probes”), because these blocks could otherwise be processed
randomly with respect to I/O blocks, so the delay in propagating a
change from the I/O block to the Test probe, and vice versa, would not
be at random. There is always a one step delay for propagation.
If during compilation, which may take a few seconds depending on the
complexity of the application program, errors are detected, a dialog
indicating the cause of the error will appear. At the same time, the block
causing the error will be marked by a green rectangle. The faulty block
will automatically be centred in the middle of the screen.
9.2 Execution of the Application Program

Execution of the application program in the TAC Xenta device consists
of an endless loop, executed at constant time intervals. During each iter-
ation of the loop (the program cycle), all function block output signals
are updated. In the TAC Menta, the user has the opportunity to execute
the application program step-by-step, to simulate actions from other
network nodes and to observe the evolution of all of the signals in order
to ensure that the application program does exactly what it is supposed
to.
9.2.1 Starting, Stopping and Initializing Execution

To start the application program, there are various options:
Table 9.1:
Continuous Pressing the Execute button or function key F2,

Execution starts the continuous execution of the application
program. This will not stop until the operation
has been repeated a second time.
Step by Step Pressing the Step button or the function key F3
Execution will execute a single cycle of the application pro-
gram.
272 (450) TAC AB, Nov 2006

04-00030-01-en
Table 9.1: (Contd.)
Execute n Selecting Execute… from the Command menu

Cycles causes a dialog to appear which asks for the
number of cycles to execute. The dialog is closed
by pressing Return
While the application program is in continuous
execution, it will halt when the Execute, Step or
RST buttons or their corresponding function
keys are pressed.
The display which appears on the upper right
side of the window shows the cycle count of the
application program since the last reset. Pressing
the RST button or function key F10, resets the
counter to zero, and all of the application pro-
gram signals return to their initial state.
9.2.2 Actions affecting the Signals

At any moment during the simulation, the user may modify the value of
a signal, which is equivalent to executing an action from the superior
node. Not all of the application program signals may be modified; only
RW (read/write), may be modified, but not RO (read only).
To modify a signal, click using the left button on the block or connec-
tion which transports the signal. Depending whether the selected signal
is analog or binary, the MODIFY or ORDER dialogs appear, respec-
tively. In MODIFY, the actual value of the signal which appears may be
replaced by the new value simply by typing it from the keyboard and
pressing Return. In ORDER, the signal may have two values: the logical
zero, represented by an empty circle and the logical one, represented by
a filled circle. Clicking the interior of the circle using the mouse
changes its state. In either case, the order will not be executed until the
dialog is closed, via the Return key or by clicking inside the dialog.
However, if the dialog is closed via the Escape key, the action will not
be executed.
9.2.3 Highlighting a Connection

To highlight a connection (including all its branches), click the right
mouse button on the connection and select Mark from the SIGNAL
pop-up menu. The connection will then be displayed in a different color,
making it easier to track across the FBD. To return to the normal con-
nection display, click the right mouse button on the connection and
select Unmark from the SIGNAL pop-up menu.
TAC AB, Nov 2006 273 (450)

04-00030-01-en
9.2.4 Simulating Executable Files

In Simulation mode can executable files be loaded via the File – Open
command, by selecting a .COD file. The file can be simulated offline,
executed online and configured, but only in tabular form. The source
code cannot be modified.
9.3 Simulating External Inputs

The user has various ways of simulating the behavior of the external
inputs of the controller in TAC Menta during execution of the applica-
tion program.
The input signals are accessed through the input buttons on the left side
of the Diagram window. Each input block in the application program is
represented by a button, showing the name of the corresponding input
block. TAC Menta supports an arbitrary number of input blocks in the
diagram. If the number of inputs used exceeds the available space on the
screen, a scroll bar will be added to the physical input button tool bar.
The simulated values generated by the input buttons are independent of
the I/O configuration parameters, e.g. the Normally Open parameter in
the DI block is not taken into account during simulation. The exception
to this rule is the Time Constant parameter in the AI block, which will
simulate the same filter function as in the TAC Xenta device in auto-
matic mode (but not in manual mode).
9.3.1 Manual Mode of Operation

Manual mode is the default operating mode of the physical inputs and
consists of manually defining the value of an input. Every time an input
value is modified, it will remain constant until it is modified again.
The buttons which represent the physical digital inputs act like
switches: they toggle between the open and closed states each time the
left mouse button is clicked.
When clicking on the buttons representing the analog inputs using the
left mouse button, a dialog opens. In this dialog, you define the value
taken by the physical input in engineering units (e.g. ºC). The value
should be entered in the same units as the output of the analog input
block. To accept the new value, the dialog must be closed by pressing
Return or clicking inside the dialog. The input value is not altered.
9.3.2 Automatic Generation of Input Vectors

In this mode of operation, the physical inputs allow the definition of an
arbitrary input function which varies in time during execution of the
application program. To select automatic mode, click the right mouse
button on the physical input button; a different dialog will then open,
depending on whether the input is analog or digital.
274 (450) TAC AB, Nov 2006

04-00030-01-en
Generating Analog Waves

For the analog inputs, there are two options for selecting the operating
mode, manual or automatic. In manual mode, the input behaves as
explained in the previous section. If automatic mode is selected, the rest
of the fields in the dialog must be taken into consideration. The wave
which can be defined is made up of he following parameters:
Table 9.2:
Wave Form Selects continuous, square, sinusoidal, ramp,

saw or impulse.
Amplitude Here, a sequence of amplitudes, separated by
commas, may be defined. During execution of
the application program, the first complete
period of the wave will take the first value, the
second the second value and so on. The ampli-
tudes are defined in the same units as the output
of the analog input block.
Circular If this option is selected, when the number of
complete cycles equals the amplitudes defined in
the previous sequence, the cycle will restart from
the beginning of the sequence. However, if this
option is not selected, when the first cycle of the
sequence has been completed, it will automati-
cally revert to the manual mode of operation.
Average Value Defines an average value for the wave. The aver-
age value is defined in the same units as the out-
put of the analog input block. For example, if the
average value is 50 and the amplitude is 10, a
sinusoidal wave will take values in the range of
40 to 60.
Phase This is a displacement on the time axis of the
wave. It is measured in degrees. A complete
period is 360. For example, a sinusoidal wave
with a phase of 90 is equivalent to a cosine.
Period Defines the duration of a complete wave period
measured in seconds.
Generating Binary Sequences

For the digital inputs, there are also two operating modes, manual or
automatic. In manual mode, the input behaves as explained in
Section 9.3.1, “Manual Mode of Operation”. If automatic mode is
selected, the rest of the fields in the dialog must be taken into consider-
TAC AB, Nov 2006 275 (450)

04-00030-01-en
ation§. The sequence which can be defined is made up of the following

parameters:
Table 9.3:
Sequence This is a series of ones and zeros which define a

square wave. Each sample of the series has a
duration equal to the defined period.
Circular If the option is selected, when execution of the
sequence is completed, this will be repeated
from the beginning of the sequence. However, if
this option is not selected, once execution of the
first cycle has terminated, the digital input will
automatically revert to the manual mode of oper-
ation.
Period Defines the duration of a sample of the sequence
measured in ms.
9.3.3 Simulation Using Test Probes

The test probes for simulation are used to create auxiliary application
programs which simulate the system which we wish to control using
real application programs. If we know the approximate functioning of
the controlled system, we will be capable of designing an application
program which simulates the behavior of that system. The test probe
blocks are used in the following manner:
• The real application program reads the physical inputs blocks and
governs the physical outputs.
• The auxiliary model uses TPAO/TPDO blocks to read the physical
outputs from the application program, and writes the model calcu-
lated values to the physical inputs using TPAI/TPDI blocks.
When TPAI or TPDI blocks exist in a function block diagram, the ter-
minals connected to these blocks may not be managed from the input
buttons, either in manual or automatic mode. However, the buttons can
be used to read the values of the inputs at each moment. Applications
containing test probes cannot be downloaded to the TAC Xenta device.
9.4 Trend Logging

The trend logging of the signals permits the user to record, during sim-
ulation, in a time diagram, the evolution of up to six signals from the
application program simultaneously. Analog and binary signals may be
simultaneously mixed in the signal being recorded.
276 (450) TAC AB, Nov 2006

04-00030-01-en
9.4.1 Adding a Signal To the Recorder

To record a signal, click the right mouse button on the corresponding
block in the flow diagram and select the Record entry in the SIGNAL
pop-up menu. If the signal is analog, the RECORD dialog will open,
where the range of the signal is defined. The requested maximum and
minimum values correspond to the values which the signal takes at the
end and origin, respectively, of the y-axis of the diagram. The default
plot range is 0–100.
9.4.2 Removing a Signal From the Recorder

To stop recording a signal, there are two options. The first is clicking
the right mouse button on the display of the recorder to open the
RECORD pop-up menu and selecting Delete. The second option con-
sists of clicking using the right mouse button on the block which corre-
sponds to the signal to in order obtain the SIGNAL pop-up menu and
selecting Delete.
9.4.3 Clearing the Recorder

Clearing the recorder means just erasing the graphs in the time dia-
gram while maintaining the same signal(s) to be recorded. To achieve
this, click the right mouse button on the time diagram and, from the
TREND pop-up menu, select the Clear entry.
9.4.4 Restarting the Recorder

Restarting the recorder means that the graphs will continue tracing from
the origin of the coordinates, but without deleting the graphs already
drawn. To achieve this, click using the right mouse button on the
RECORD pop-up menu and select the Restart input.
9.4.5 Resetting the Recorder

Resetting the recorder means eliminating all of the signals being
recorded. This may be achieved by removing them one by one using the
procedure explained in the previous section, or all at the same time. The
latter option is achieved by clicking the right mouse button on the time
diagram to obtain the TREND pop-up menu and selecting the Reset
entry. Before Reset is executed, the user is prompted to confirm the
operation.
9.4.6 Viewing the Trend Log

It is possible to scan the graphs using a cursor, and consult the samples
at any point. To achieve this, simply click the left mouse button on a
point on the graph. The cursor will appear at the selected point as a dot-
ted vertical line. At the same time, the registers and the cycle counter
TAC AB, Nov 2006 277 (450)

04-00030-01-en
will be updated with the value corresponding to each sample at this

point.
Clicking and holding the left mouse button while moving the mouse to
the left or right will cause the cursor to follow the mouse movement, but
moving one sample at a time. The trend log cursor can also be moved
using the left and right arrow keys, while pressing the Ctrl key.
To remove the cursor from the time diagram, click the right mouse but-
ton on the diagram.
9.4.7 Defining the Sample Time

By default, the recorder takes one sample of each of the signals to be
recorded during each program cycle. However, it is possible to define
the number of program cycles executed per sample taken on the
recorder. Selecting the Sampling input from the Commands menu on
the menu bar opens a dialog in which this parameter may be defined.
The default number of cycles per sample is one, which is equivalent to
showing every program cycle in the trend log.
In Online mode, the sampling rate for the trend log is expressed in sec-
onds instead of in program cycles, as in Offline mode. However, due to
limitations in the operating system, this sampling rate is not very accu-
rate.
9.5 The Logger Tool

The Logger tool is an addition to the trend logging function, which per-
mits further analysis of the recorded log values, and saving them to a
file. The recorded signals are the same as those in the Trend log func-
tion.
9.5.1 Starting the Logger

Recording is started in simulation mode as follows:
1 Select the Logger via the Logger command in the Tools menu.
2 Select the signals to be recorded, see Section 9.4.1, “Adding a Sig-
nal To the Recorder”.
3 Start program execution.
9.5.2 Diagram Setup

By means of the diagram setup, you can split the Logger window into
several sub windows (diagrams) and set different properties for each
diagram.
Click the main setup button ( ) directly below the Logger menu bar.
278 (450) TAC AB, Nov 2006

04-00030-01-en
To the left of the displayed dialog, there is a list of diagrams. Add or

remove diagrams via the Add diagram and Remove diagram buttons
below the list box.
To the right there is a list of the signals available. Assign signals to the
diagrams using drag-and-drop technique. Double click the diagram icon
to show the signals assigned to the specific diagram. Then a highlighted
signal can be removed from the diagram via the Remove signal button.
Click OK when ready.
Arrange the diagrams using the Tile or Cascade commands in the Win-
dow menu.
9.5.3 Presentation and Analysis of Logged Values

Set the properties for each diagram via the setup button ( )in the dia-
gram sub window:
Table 9.4:
Labels Explanatory descriptions of the X and Y axes.

Grid Turns the grid on or off.
Scale Types Selects Slide scale ( ), Grow scale ( ) or
Fix scale ( ).
Coordinates Sets minimum and maximum values for the X
and Y axes.
Click OK when you are done.

The logged values are displayed as a graph in the diagram in accordance
with the diagram setup. The names of the signals are displayed in the
upper left corner of each diagram. Above the diagram, the most recently
recorded value and program cycle (sample) number for the selected sig-
nal is displayed.
If you want to zoom in and select a part of the diagram for detailed anal-
ysis, this area must be marked by drawing a rectangle with the left
mouse button depressed. The diagram scaling will automatically be
altered so that the selected area will cover the full diagram window. The
arrow buttons to the right of a diagram are used to move the displayed
area along the X axis (number of program cycles).
Use the Default scale button ( ) to the right of the diagram to restore
the diagram scale to the default settings X = 0–1000, Y = 0–100.
Clicking the print button to the right of the diagram, prints the current
diagram on the active printer.
TAC AB, Nov 2006 279 (450)

04-00030-01-en
9.5.4 Saving and Viewing a Log File

All the logged values can be saved to a file via the save button ( ), or
via the File – Save log command in the Logger. The user is then
prompted to enter a file name. The following data is saved in the log file:
Fig. 9.2:
The data is saved in ASCII format, enabling export for further analysis
using other tools. The log file can also be displayed in the Logger via
the File – View log command.
9.5.5 Clearing the Logger

Clearing the Logger means deleting the recorded signal values from all
diagrams, but maintaining the same signal to be recorded. This may be
achieved via the File – Clear log command or by clicking the Clear
button.
The File – Exit command is used to exit the Logger.
9.6 Modifying Block Parameters During Simulation

9.6.1 Function Block Parameters
Internal block parameters cannot be modified in Simulation mode.Val-
ues can be inspected using the View command in the SIGNAL pop-up
menu. In order to modify public block parameters during simulation, the
user must enter the Constants table and change the value of the corre-
sponding public constant.
9.6.2 Time Schedules

Any Simulation mode change of TSCH information will be retained
when returning to Edit mode, regardless of whether the change is made
from the block or via the TSCH table. In Online mode, changes in
TSCH week and holiday chart settings are transferred directly to the
device. Please note that if the numbers of week or holiday charts are
changed, new .COD and .BIN files must be generated and downloaded.
280 (450) TAC AB, Nov 2006

04-00030-01-en
9.6.3 I/O Binding Data

Any Simulation mode change of I/O binding data will be retained when
returning to Edit mode. In Tabular mode, I/O binding information is
only accessible through the I/O Binding table. After changing I/O bind-
ing data, a new .COD file has to be generated and downloaded in order
to transfer the changes to the device.
9.6.4 Constants
Only public constants are accessible in Simulation mode. Values of
non-public constants can be inspected but not modified in the Constant
Table. Public constant values that are modified from the Constants
Table update the source code, but changes from Tabular mode do not.
9.6.5 Alarm Texts

Alarm texts are only accessible through the Alarm Text Table. Changes
always update the source code. After changing alarm texts, a new .COD
file has to be generated and downloaded in order to transfer the changes
to the device.
9.6.6 The ERR Block

In Simulation mode, it is possible to edit the ERR block to simulate dif-
ferent internal signals or errors from the system program. For informa-
tion on the ERR block, see Section 19.1, “System Errors”.
TAC AB, Nov 2006 281 (450)

04-00030-01-en
282 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 10 OP Configuration Tool
10 OP Configuration Tool
The OP configuration tool is accessed through the OP configuration
command in the Tools menu. When this command is selected, the spec-
ification (.ESP) file is automatically generated and the OP configuration
tool is invoked with the .OPC file of the current application. If this file
does not exist, a warning message will appear and the user will be
prompted to select either the default file (DEFAULT.OPE) or an exist-
ing .OPE file to be used as the default tree. Clicking OK without select-
ing an .OPE file, will invoke the tool with a completely empty menu
tree.
Fig. 10.1:
The screen consists of four main areas:
Table 10.1:
Menu Structure Shows the complete menu structure of the cre-

Tree ated dialog. The operator can navigate in this
tree by highlighting the different menu items.
Depending on the selected item type, the three
different parts on the right side of the screen will
show different types of information.
TAC AB, Nov 2006 283 (450)

04-00030-01-en
10 OP Configuration Tool TAC Menta, Technical Manual
Change Menu The menu item name can be edited by using the
Item Name Change Name command button. For the root
menu item (application) both the name and the
abbreviation are shown, but neither of them can
be changed, since they are defined in the Pro-
gram specification in the FBD programming part
of TAC Menta. The abbreviation is shown in all
dialogs so that the operator can always see the
device on the network that he is presently work-
ing with. The abbreviation is also used to indi-
cate a summary alarm in the TAC Xenta, the text
will flash to indicate that there are unacknowl-
edged alarms in the alarm list.
Operator Panel By locating the cursor in the display area, texts
Display can be edited or added. Depending on the menu
item type, different default texts will be copied
to the display. The application abbreviation text
will always be copied to the upper left corner of
all displays. Also, the menu item name will auto-
matically be copied to the top row of the screen
display when a screen item is created.
For some menu items, this area also includes a
number of command buttons for inserting refer-
ences, names etc. There are also command but-
tons for setting the properties of inserted signal
references.
Menu Item List This area will contain the list of menu items (sub
(Signal List) menu) for the selected menu item, if that is a sub
menu or the root item type. This area can also
display a list of signals used when inserting ref-
erences, names etc. into the OP display.
10.1 The Menu Structure Display

The different menu item types are represented by different symbols in
the menu structure tree. The first two item types can be compared with
folders in Microsoft® Windows Explorer:
Table 10.2:
Menu root item, also the name of the application

to be displayed in the TAC Xenta OP display
when the network devices are shown.
284 (450) TAC AB, Nov 2006

04-00030-01-en
Sub menu menu item, this is a menu item type

that can contain a number of other menu items
forming a sub menu. It is used to build the hier-
archical levels of the menu structure.
The other item types, called screen items, can be compared to files in
Microsoft® Windows Explorer, with the “file” contents shown in the OP
display:
Table 10.3:
Status, this type contains a number of pages/

screens displaying traditional signals and param-
eters such as set point values, measured values
etc.
Alarm, below this menu item the alarm list of the
device is displayed.
Access code, this menu item will lead to a screen
where an access code can be entered.
Edit access code, this menu item will lead to a

screen where the access code can be edited.
Date and time, this menu item will lead to a
screen where the date and time can be set.
Daylight saving, this menu item will lead to a
screen where the daylight saving settings can be
entered.
Week chart, this menu item contains a number of
week charts related to one time schedule.
Holiday chart, this menu item contains a number
of holiday charts related to one time schedule.
10.2 Creating the Menu Structure

10.2.1 Adding Menu Items
If no previously saved menu structure is selected, the OP configuration
tool starts displaying only a default menu root item in the menu struc-
ture display. This root item has a name that identifies the TAC Xenta
device (application) used when the OP displays all the devices in the
network. A menu structure is created by adding menu items to the root
menu ( ) and to sub menus ( ). Adding a menu item is done by
selecting the root menu or a sub menu in the menu structure display and
TAC AB, Nov 2006 285 (450)

04-00030-01-en
then selecting the Add button in the menu item list part of the screen.
This will open a dialog where a name can be entered and a menu item
type selected. Depending on the type selected, different default panel
displays will be created. When there are menu items below a created sub
menu item, this is indicated by a “+” sign in the sub menu item icon in
the menu structure display. Double-clicking on this icon will also make
the menu items in the sub menu appear in the menu structure display
(see also Tree – Expand menu option).
Note
The OP menu tree can only contain a maximum of 255 OP screens.
To change the order in which menu items appear, these can be moved
using the drag-and-drop technique in the menu item list window. To
delete a menu item, select (highlight) it in the menu item list and
remove it using the Delete button.
10.2.2 Sub Menu

The simplest menu item type is a sub menu ( ). It has only two prop-
erties; name and access level. A sub menu can have any type of menu
item in its menu list, including a new sub menu. However, a maximum
of 15 sub menu levels is allowed.
A sub menu can contain menu items with different access levels. When
you increase the access level for a sub menu, the underlying sub menus
may also change, resulting in the same or higher access levels for these
sub menus.
When you decrease the access level for a sub menu, you may also
choose to change the access levels for the underlying sub menus, result-
ing in the same or higher access levels for these sub menus.
10.2.3 Status
The menu item type Status ( ) is used to create dialogs in which
parameters and measured values are displayed and edited.
In the Operator Panel display window, the actual editing of the screen
layout is done. Text strings and references to signals (parameters, mea-
sured values) can be inserted into a certain position indicated by the cur-
sor by double clicking in the signal list, or by means of the Insert
Module (including the selected separator), Insert Name, Insert Signal
and Insert Unit command buttons. These insert buttons will only work
if a specification file has been loaded. With the cursor correctly posi-
tioned in the Operator Panel display window a signal is selected in the
list in the bottom right corner of the screen. Used signals in the signal
list are shown in normal characters, while unused ones are shown in
bold characters. If a signal reference is used in more than one place
286 (450) TAC AB, Nov 2006

04-00030-01-en
within the menu tree structure, this signal will be shown in normal char-
acters.
Note
The displayed list only contains signals belonging to the same Module,
so you will first you have to select Module via the box above the sig-
nals list. Using the different “insert” buttons names, unit or signal
value references can be inserted into the dialog.
The Property command button is used to invoke a dialog for the signal
highlighted in the Operator Panel display window. The dialog contains
the following settings:
Table 10.4:
Operator Panel Used to define whether the signal should be read

Attributes only or possible to alter (Read/Write) from the
OP.
Signal Refer- This option only applies to real or integer values.
ence Properties The setting No. of decimals is used to decide the
signal’s display format. This number must be set
between –4 and 4. A negative number means that
the value will be altered in steps of 10 (No. of
decimals = –1), 100, 1000 or 10000 (No. of deci-
mals = –4) when altered by the operator.
If a real value requires more digits than have
been reserved, the following characters on the
display row will be overwritten. If the value
won’t fit in the available space at the end of the
row, it will be shown in scientific format (e.g.
14.1E6).
The settings Minimum and Maximum are used to set the limits, which
must be within the range (–32768, 32767), for changes using the “+” or
“–” key in the OP. These limits are only in use when the operator alters
the value via the OP.
Default values for Minimum, Maximum and No. of decimals, for use in
all new signal reference property dialogs, are set via the Signal Prop-
erties command in the Formats menu.
A highlighted signal reference in the Operator Panel display window
can be deleted using the Delete signal button.
TAC AB, Nov 2006 287 (450)

04-00030-01-en
A Status menu item can consist of several pages. Use the Add page
command button to create the additional pages with parameters/values.
Note
If a Status menu item is deleted, then the corresponding signals will
not be indicated as unused (bold) in the signal list until the list is
updated e.g. via the Tree – Update specification command.
10.2.4 Alarm
When a menu item of the Alarm type ( ) is created, a default screen is
created, with references to the alarm list. Note that even if several
instances of Alarm type can be created, they will all refer to the same
alarm list. No other properties than name and access level should be
edited for this menu item type. The alarm text displayed in the OP is
defined in TAC Menta.
10.2.5 Access Code

When the root menu item is active, in the left part of the screen, it is pos-
sible to edit the access levels for the items in the menu item list. One or
more menu items can be selected and when the Level button is
depressed a dialog to define the access level (low(green), medium(yel-
low) or high(red)) will appear. The access level of each item in the menu
structure display is indicated by a color code and a letter (L, M or H).
Note that a menu item of the type Access Code must always be defined
with the access level low.
The Access Code ( ) and Edit Access Code ( ) menu item types,
are used to create the dialogs for changing the access level and editing
the access code. For these types, the explanatory text in the display
screen may be edited. This is done by placing the cursor (using the
mouse) in the Operator Panel display window and overwriting the text
to be changed.
In each TAC Xenta device, there will be default codes (medium = 1111
and high = 2222) that can be edited via the OP. Note that the TAC Xenta
will revert to the default codes whenever the application program is
downloaded.
10.2.6 Date and Time/Daylight Saving

The Date and Time ( ) and Daylight Saving ( ) menu item types are
used to create the dialogs for date and time settings and daylight saving
settings . The default dialogs may be changed or extended by manually
adding text in the Operator Panel display window.
288 (450) TAC AB, Nov 2006

04-00030-01-en
10.2.7 Week/Holiday Chart

The Week chart ( ) and Holiday chart ( ) menu item types are used
to create the dialogs for viewing and editing time schedules. A time
schedule consists of a number of week charts and holiday charts. The
time schedule has been divided into two dialogs (week and holiday
chart) to simplify the operator interface in the OP. When the reference
is assigned for the Week and Holiday chart, it is set to the same time
schedule. The reference is assigned by selecting a time schedule object
name in the signals list (cf. Insert signal in Status dialogs) and clicking
the Assign time sch. button. Used signals in the signal list are shown in
normal characters, and the unused ones are shown in bold characters. If
a signal only is selected a week or holiday chart, this will be shown in
normal characters. Note that the displayed list only contains signals
belonging to the same Module, so you will first have to select Module
via the box above the signals list.
In order to reduce the TAC Xenta’s memory usage, you can, via Settings
in the Formats menu, choose to use Time schedule templates. I doing
so, the Week and Holiday chart dialogs will have a fixed layout. Other-
wise, the default dialogs may be changed or extended by manually add-
ing text in the Operator Panel display window.
10.2.8 TAC Service Menu

The TAC service menu is a fixed menu, which makes it possible, via
the OP, to read the TAC Xenta system program version, TAC Xenta
name and network address, configure the I/O modules and restart the
TAC Xenta.
The service menu has no menu item, since it is automatically created
when generating the OP tree, if the OPDOCADD.GOP file is present in
the TAC Menta directory (can be set in Formats – Settings).
The service menu, which is always located at the end of the menu tree,
is only accessible via a fixed access code.
10.3 Editing an Existing Menu Structure Tree

When a menu structure is reused, or created as previously described,
there may be a need to translate/change texts or rearrange menu items.
In order to reuse an OP menu tree file (.OPC) or parts thereof in another
application, it should be saved under a new name (the name of the new
application). Next, exit the OP configuration tool, and create a new file
(.AUT/.MTA) with the same name (if it does not already exist). Re-
enter the OP configuration tool from the FBD window, and you will be
able to edit the new menu tree file. All references to signals which still
exist (with the same name) in the new file are left intact, other refer-
ences will be empty and can be pasted in from the signal list of the new
TAC AB, Nov 2006 289 (450)

04-00030-01-en
file. New signals which did not exist in the original signal list are avail-
able in the signal list of the revised file and can also be pasted in.
10.3.1 Moving Menu Items

In the “Menu item list”, the different items can be sorted using drag-
and-drop (select a menu item by pointing at it with the mouse, click the
left mouse button and keep it depressed while you drag the menu item
to the required position).It is also possible to move a menu item in the
menu structure tree display from one sub menu node to another.
10.3.2 Changing the Operator Panel Display Layout

When you are translating or editing the texts in the OP display, it may
be necessary to move references to signals in the OP display. This is
done by selecting the reference with the mouse and moving it using a
drag-and-drop. (select a signal reference by pointing at it with the
mouse, click the left mouse button and keep it depressed while you drag
the reference to the required position.)
10.3.3 Copying and Pasting

The Copy and paste functions can be used on all items in the menu root
item, or under a sub menu node. The items are copied/pasted with all
sub menus and signals. The copied items are stored on the clipboard –
both as text and as graphics – and so can also be used for copying
between two operator dialog description files.
10.4 Automatic Generation of an OP Menu Tree

The OP configuration tool contains a function for automatically gener-
ating a complete OP menu tree. By means of this function, the user can
import all public signals from the FBD for standard format OP presen-
tation, instead of having to manually insert every signal.
The function is invoked using a Generate or Download command in
TAC Menta’s Simulation mode if Auto generation of menu tree has
been set in the Preferences menu. The menu tree will then be built from
the empty standard OP menu tree file as specified (Standard OP tree =
Path\FILENAME.OPE) in Formats – Settings. If no standard OP menu
tree file has been specified, the STD_AUT.OPE file will be used. Auto-
matic generation can also be started from the OP configuration tool by
selecting Build in the Tree menu.
The automatic generation function first erases the old data in the status
menu items. Then it does the following:
• All RO binary signals will be sorted in alphabetical order in the
first available low access level Status menu item, with one signal
per row. The signal name is placed in positions 1–14 (longer
names are truncated), the signal reference is placed in positions
290 (450) TAC AB, Nov 2006

04-00030-01-en
15–17 and the unit is placed in positions 18–20. New pages are
automatically added, if necessary.
• All RO analog signals will be sorted in alphabetical order in the
second low access level Status menu item, with one signal per row.
Consequently, there must be at least two status menu items in the
tree, or else the analog signals won’t be displayed. The signal
name is placed in positions 1–9 (longer names are truncated), the
signal reference (with default properties) is placed in positions 10–
17 and the engineering unit is placed in positions 18–20. New
pages are automatically added, if necessary.
• All binary signals (Both RO and R/W) will be sorted in alphabeti-
cal order in the first medium or high access level Status menu
item. Layout handling as above.
• All analog signals (Both RO and R/W) will be sorted in alphabeti-
cal order in the second medium or high access level Status menu.
Layout handling as above.
• The first available Time schedule will be assigned to the first Week
chart menu item and the first Holiday chart menu item. The sec-
ond Time schedule will be assigned to the second Week chart
menu item and the second Holiday chart menu item, etc. Note that
there will be an error message, and generation will be interrupted
if there are more Week/Holiday charts in the menu tree than Time
schedules in the FBD.
If the FBD contains two or more Modules, the Status menu item will
automatically be replaced by a Sub menu item containing the corre-
sponding number of Status menu items, all with the same names as the
Modules.
The OP menu tree often contains an information menu displaying the
application type, software version etc. This type of menu is created as a
Status menu item only containing text. To prevent the information menu
from being overwritten by automatic generation, it can be defined as an
Information node (Name “Info” menu = MENUNAME) in Formats –
Settings. This menu will then be excluded when the program searches
for status menus.
The generated OP menu tree can, of course, be manually edited in the
OP configuration tool. Please note, however, that all manual alterations
will be deleted if you auto generate the menu tree again. Therefore,
always try to prepare the standard OP menu tree file, from which the
menu tree will be built, in such a way that no manual editing will be
needed. For example, it is possible to change the standard of the signal
features and/or to save them.
10.5 OP Description Files

One alternative way to create an OP menu tree is by using OP descrip-
tion files (.DOP). The user describes the OP tree in a text file, imports
TAC AB, Nov 2006 291 (450)

04-00030-01-en
this file into the OP configuration tool, and the .OPC and the .BIN files
are automatically created and saved to disk. The .DOP file can be edited
by any Windows based text editor or word processor.
10.5.1 Data and Declarations Syntax in OP Description Files (.DOP)

The first position in a row is reserved for one of three key words:
Table 10.5:
OPC Full pathname\filename for the OP menu tree to

be created, normally an .MTA file. The .BIN file
will also be stored in the same place.
ESP Full pathname\filename to the signals list, nor-
mally an .MTA file, that is used as the input file
for the .DOP file.
MENU Information about Menu name, Menu item type,
access level and other attributes describing the
layout of the specific OP display.
Comments can be added by starting a row with the * character.

Each Menu item in the OP menu tree must be defined separately. To
place a Menu item on the “root” level, enter a hyphen (-) character in
front of the Menu name. Menu items (without a hyphen), defined after
a “Sub menu” will be built under the “Sub menu” level in the OP tree.
To define that the Menu item will be placed under another “Sub menu”
than the previous one, enter the full path name e.g. -PARAMETERS-
HEATING_COIL-FROST_PROTECTION.
Key words and attributes are separated by blanks or tabs. Consequently,
all attribute texts that contain blanks must be typed between single
quotes, e.g. “Sub menu”. The following Menu item types may follow
the MENU keyword:
Table 10.6:
Sub Menu MENU ’MENU NAME’ ’Sub menu’ High

A standard layout display will be created.
Week Chart MENU ’MENU NAME’ ’Week chart’ Low
AHU01\TC_SF01
A standard layout display will be created, but
note that a reference to a specific time schedule
(e.g. AHU01\TC_SF01) must be included.
292 (450) TAC AB, Nov 2006

04-00030-01-en
Holiday Chart MENU ’MENU NAME’ ’Holiday chart’

Medium AHU01\TC_SF01
A standard layout display will be created, but
note that a reference to a specific time schedule
(e.g. AHU01\TC_SF01) must be included.
Status MENU ’MENU NAME’ Status High
’Text‘ ’T11 ~##.#°C ’ T11 0 100 1 RO
Row by row, the OP display texts are entered between single quotes,
exactly as they will appear on the screen. The texts are truncated if they
are longer than 20 characters. An empty line can be defined as “ “
(a space; do not use tabs!). New pages are automatically created, when
necessary.
Digital signals are defined with a “~#” in the text, followed by two
attributes: the signal reference (including module) and the read/write
attribute (RO/RW), all written on one line.
Analog signals are defined with a “~#.#” in the text, followed by five
attributes: the signal reference (including module), the Minimum set-
ting, the Maximum setting, the No. of decimals setting and the read/write
attribute (RO/RW), all written on one line. To display more than one
signal in an OP display row, separate the next signal reference with a
tab/space and define the signal and its attributes. Max. 10 signals can be
defined in one row, and all the data for one specific row of the display
has to be on one row in the .DOP file.
Table 10.7:
Access Code MENU ’MENU NAME’ ’Access Code’ Low

Edit Access Code MENU ’MENU NAME’ ’Edit Access Medium
Code’
Alarm MENU ’MENU NAME’ Alarm High
Date and Time MENU ’MENU NAME’ ’Date and Time’ Low
Daylight Saving MENU ’MENU NAME’ ’Daylight Saving’ Medium
A standard layout display will be created for all these menu items.
TAC AB, Nov 2006 293 (450)

04-00030-01-en
10.5.2 OP Description File Example
Fig. 10.2:
10.5.3 Importing the OP Description File

There are two alternative ways to import the .DOP file:
1 Use File – Import in the OP configuration tool. If there is a menu
tree already, the imported tree will automatically be placed after
the existing one. Normally, a “Save?” question will be displayed
when exiting the tool. If this question is not displayed the import
has failed.
2 Use the Run command (or a shortcut) in the Windows start menu.
Syntax: Run pathname\GraphOP.exe /d pathname\filename.dop)
Note that the Run command uses DOS; so the pathname\filename must
be entered between quotes if it contains a space or more than eight char-
acters.
The program will create a new .BIN file, but no .OPC file. If there isal-
ready an .OPC file with the same name, this will not be altered. To avoid
mistakes, you should either move the old .OPC file or start the OP con-
figuration tool and save the correct .OPC file.
294 (450) TAC AB, Nov 2006

04-00030-01-en
10.5.4 Exporting the OP Description File

To export an open menu tree to a .DOP file, use File – Export in the OP
configuration tool. When exporting to a .DOP-file, the attributes
belonging to the keyword will be in English, e.g. MENU Week chart
’Week chart’ Medium. However, if your TAC Menta program is
not in English, the attributes will not have to be edited, since the pro-
gram handles both English and your national language when importing.
10.6 Defining a Character Set File

The OP’s LCD display shows decimal coded characters 32-125 in
accordance with the standard ASCII set. In addition, 8 characters with
codes higher than 127 can be defined in a national character set file.
To define a new character set file, start by saving the existing file
CHARSET under a new name in Windows™ Explorer. Then edit the
new character set file by means of the Notepad editor, for instance. The
following format is used in CHARSET:
Fig. 10.3:
A simple way to find the decimal coded character number, is to start the
Character mapping program (CHARMAP.EXE) in Windows™
Explorer (normally located in the Accessories program group), and look
for the character in the Arial True Type mapping, for instance. Here all
characters are shown in order, starting with the “space” (decimal code
32) in the upper left corner.
Finally, open the Formats – Character set file dialog in the OP config-
uration tool, and select the new character set file. From now on, the new
characters will be used when the Generate command is executed.
TAC AB, Nov 2006 295 (450)

04-00030-01-en
10.7 Menu Options

10.7.1 Menu Bar
On the menu bar, here are a number of pull-down menus, each with var-
ious entries, which are explained below:
296 (450) TAC AB, Nov 2006

04-00030-01-en
FILE
Table 10.8:
New Closes the present OP menu tree file and opens a

new file. If the present file has not been saved,
the user will be asked if he/she wants to save the
existing file.
Open Loads an OP menu tree file from the disk. The
files on the disk must have the extension .OPC
(menu tree + specification list) or OPE. (Only
menu tree). The present OP dialog will close
before the new file opens. If the present file has
not been saved, the user will be asked if he/she
wants to save the existing file.
Save Saves the OP dialog with the same nameas.
Save As Saves the present OP dialog but allows the user
to enter a new file name. It is possible to save it
either as an .OPC file or an .OPE file. To save as
an .OPE file, the loaded signal list must first be
deleted (Tree – Remove Specification).
Print Prints an overview or a detailed (a fully
expanded menu tree) documentation of the OP
dialog on the active printer.
Print Preview Displays a preview of the printout on the screen.
Print Setup Used to select the active printer and change its
settings.
Import Used to import an OP menu tree from an OP
description (.DOP) file.
Export Used to export an OP menu tree to an OP
description (.DOP) file.
Exit Leaves the program and returns to the program
manager, or to TAC Menta if it was started from
there. If the present file has not been saved, the
user will be asked if he/she wants to save before
this.
FORMATS
Table 10.9:
Signal Proper- Sets the default values for Minimum, Maximum

ties and No. of decimals, for use in all new signal
reference properties dialogs.
TAC AB, Nov 2006 297 (450)

04-00030-01-en
Alarms A dialog where the texts indicating the alarm sta-

tus in the alarm list can be edited. Abbreviated
localized texts for “tripped”, “reset” and
“acknowledged” can be defined.
Date and Time A dialog where the date and time display format
can be set. The selected format is used in alarms,
time schedule displays etc. National texts for
weekday names are also edited in this dialog.
National Week In this dialog, the national texts for weekdays are
Days Text defined. These text are used in the date and time
display on the operator panel.
National In this dialog, the national texts for months are
Months Text defined. These text are used for displaying some
of the date formats. Only the first three charac-
ters in each month name are used in the sup-
ported date formats.
Character Set When using national characters outside the stan-
File dard ASCII set (0-127), a character set file
including definitions of the national character set
mapping must be used. The LCD display of the
OP supports eight user defined characters,
defined in the national character set file. The file
is used by the tool when the Generate command
is executed. The tool will then check the defined
texts for ASCII codes higher than 127, and
replace them with characters defined in the char-
acter set file. This will enable the OP to display
the correct national characters.
298 (450) TAC AB, Nov 2006

04-00030-01-en
Settings Used for setup of:

• Temporary directory; defines the directory
for all temporary menu tree files, created
and used during the Generate process.
• Separator; one character, e. g. “- ”or “/”, to
be used to separate module and signal
names.
• Use Time Channel Templates; defines
whether Time Schedule Templates are to be
used.
• Use Service menu; defines whether the TAC
Service menu will automatically be included
when generating the OP menu tree.
• Standard OP tree; path and name of the
empty OP menu tree file, from which the
OP menu tree will be built upon an auto-
matic generation of the menu tree.
• Name “Info” menu; defines the entered Sta-
tus menu name as an Information node,
which means that it will be prevented from
being overwritten upon automatic genera-
tion of the menu tree.
• OP; select Custom if an OP using Russian
character set is to be used, otherwise
Default.
Note
If you want to permanently use other default texts or values for Signal
properties, Alarms, Date and time, National Weekdays and National
Months than those stored in the OP configuration tool, you will be able
to save these altered texts and values via Save as an empty menu tree
file (.OPE), which you will then use as template file whenever you are
creating a new menu tree.
TAC AB, Nov 2006 299 (450)

04-00030-01-en
TREE
Table 10.10:
Expand To display all levels of the menu tree. This is

equivalent to double clicking on all menu tree
icons with a “+” sign.
Test Will perform a form of pre compilation check to
ensure that the defined OP dialog can be suc-
cessfully downloaded. This test will check for
the following errors:
• Menu items not arranged by increasing
access level.
• Specification file including signal list not
loaded.
• National character set not selected.
• Root menu item empty.
• Time schedule reference in week chart dis-
play not defined.
• Time schedule reference in holiday chart
display not defined.
This test will also check for the following warn-
ings:
• All signals in specification file not used in
OP dialogs.
• Time schedule in specification file not used
in OP dialogs.
Generate First, the complete OP dialog is tested (see
above). Then, if no errors are found, pressing OK
will compile the menu structure to a file that can
be downloaded together with the application
from TAC Menta. The result of the compilation
is presented dynamically in a window on the
screen. Close this window before continuing
your work.
Build Starts automatic generation of an OP menu tree.
Load Specifica- Used to load a new signal specification list.
tion
300 (450) TAC AB, Nov 2006

04-00030-01-en
Table 10.10:
Update Specifi- Will update the active signal specification list.

cation Used when working with FBD programming and
the OP configuration tool simultaneously. How-
ever, a new specification file (.ESP) version
must first be created via the Simulation mode
command Generate before the specification list
can be updated.
Remove Speci- Will delete the loaded signal list from memory.
fication
View Specifica- Used to display the signal specification list
tion
Copy to clip- The menu structure tree is copied to the clip-
board board in Microsoft® Windows meta file format
and text format. This may in turn be exported
from the clipboard to other Microsoft® Windows
applications. It can be pasted as text or a picture
in, for instance, Microsoft® Word.
HELP
Table 10.11:
Contents Will invoke a help file containing the basic infor-

mation in this manual.
About Will display information on the current software
revision.
TAC AB, Nov 2006 301 (450)

04-00030-01-en
302 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 11 Other Functions and Tools
11 Other Functions and Tools

11.1 The Program Specification
The Program Specification command is found in the Options menu.
The Program specification consists of all of the information about the
application program which the configuration program requires to install
an application program in the TAC Xenta device.
Table 11.1:
Name A string of up to 20 alphanumeric characters

defined by the user containing the name of the
application program. The characters , ; ’ – .$ are
used as separators or system object identifiers in
TAC Vista, and are thus illegal in application
names. The space character is not allowed, but
the characters “_ : /” are. You are allowed to use
national character sets (including e.g. å, ä, ö, ç)
in the application name.
Abbreviation A string of up to 4 characters. This string is only
used by the OP, thus all characters that can be
handled by the OP are legal.
Type A variable length string defined by the user
which describes the type of application program.
Author A variable length string containing the name of
the author of the application program.
Date A read-only field containing the last edit date of
the application program.
Cycle time The application program execution interval (ms)
when the program is executed in the controller.
This parameter does not affect the execution of
the application program during offline simula-
tion. The default value is 1000 ms. The Max.
program cycle time is 65 536 ms. The Min. pro-
gram cycle time is 500 ms.
Blocks The number of blocks in the program. This infor-
mation is only available following compilation
of the program.
TAC AB, Nov 2006 303 (450)

04-00030-01-en
11 Other Functions and Tools TAC Menta, Technical Manual
I/O signals Gives the number of physical signals, inputs and

outputs, analog and digital, which are used by
the application program. This information is
only available following compilation of the pro-
gram.
Public signal A read-only list of all of the application program
table public signals. The list consists of four columns
showing the signal identifier, type, access class
and unit. The parameters of the table of constants
which are defined as public are also included in
the list, as well as all external I/O signals. The
signals/parameters are sorted in alphabetical
order.
Standard App. A read-only box, which specifies whether the
current application is a Standard application or a
Customer specific application (Checked = Stan-
dard application), see Section 11.13, “Marking
Standard Applications/Controllers”.
11.2 Device Configuration

The Device configuration command of the Options menu declares the
TAC Xenta type and I/O or similar to be used by the application.
Table 11.2:
Type The TAC Xenta type (TAC Xenta 280/301/302/

401 etc) for the current application, selected
from a pre-defined list of supported types. The
list is defined in the TATYPE.INI file.
System version Definition of the TAC Xenta system program
version. If 1.x is selected, a Generate or Down-
load command will create downloadable code
files in TAC Xenta version 1.1 format, instead of
in TAC Xenta version 3 format (default).
Hardware ver- Shows the hardware version of the selected TAC
sion Xenta (281/282/301/302/401 etc), and is nor-
mally not to be altered. If the application in a
TAC Xenta 300 is to contain a Trend log, hard-
ware version 2 must be used.
304 (450) TAC AB, Nov 2006

04-00030-01-en
XIF header gen- TAC Menta can, for TAC Xenta from system
erated accordnig program version 3.3, generate an XIF file in
to LonMark which the device’s LonMark approved program
ID is included in the first row of parameters. Pre-
vious versions did not include this information,
but by checking this box, for example, when
upgrading the TAC Xenta device, the correct
information will be included. NB. If the XIF file
is altered in this way, you must re-make all its
bindings in the Network management software.
Add new net- Defines that all new network variables (SNVT)
work variables will be placed last in the XIF file when an exist-
(SNVT) last in ing application program is edited. This means
the XIF file that only these new variables have to be bound in
the Network management software; no existing
bindings must be re-made. Note, however, that if
a network variable is deleted, or if an existing I/
O block is altered e.g. from “Non linear analog
input” to “SNVT”, you must re-make all bind-
ings. Also the very first time the function (which
is the default from TAC Menta version 3.24) is
used on an existing application program, all
bindings must be re-made.
Use LonMark TAC Xenta 283 can work as a LONMARK 3.3
3.3 approved real time keeper, using UTC time as
input and returning local time as output. How-
ever, this applies only to System Version 3.6 or
higher. If the box is not checked a LONMARK
version 3 XIF file will be generated.
The I/O Expansion and Wall Module Table has the buttons Edit, Add
IO Module, Add STR Module, and Remove. The following parame-
ters can be defined/altered in the Edit IO Expansion Module table:
Table 11.3:
Module Definition of the number (Module1, Module2

etc.) of each of the I/O modules in the current
application. New modules can be added, but
only the last module in the list can be removed
(deleted). Before an I/O expansion module can
be removed from the list, all bindings to its I/O
points must be removed (detached). The same
applies when an I/O expansion module is
changed in type and I/O points are influenced.
TAC AB, Nov 2006 305 (450)

04-00030-01-en
Type The type (TAC Xenta 411, TAC Xenta 412 etc.)
of each of the I/O modules in the current applica-
tion, selected from a pre-defined list of sup-
ported types. The list is defined in the
TATYPE.INI file.
Min send time Defines how often the I/O module is allowed to
communicate with the TAC Xenta. The default
and minimum value is 500 ms, but the value can
be increased to reduce network traffic.
Fast CNT Defines whether fast reporting of the status
reporting changes of pulse inputs (CNT) is to be used. The
function is used when connecting push buttons
for lighting control. Note that the function will
increase network traffic. The box is not checked
by default; reporting a status change will then
take about 30 s, which can be used for energy
pulse metering, for instance.
For the STR Wall module the Edit STR Wall module table holds the fol-
lowing parameters to be defined/altered:
Table 11.4:
Module Definition of the number (S1, S2 etc.) for each of

the STR Wall modules in the current application.
New STR Wall modules can be added, but only
the last I/O or STR Wall module in the list can be
deleted.
Type Type (STR350/STR351 etc.) for each of the STR
Wall modules in the current application, selected
from a pre-defined list of supported types.
Min send time Defines how often the STR Wall module is
allowed to communicate with the TAC Xenta.
Default and minimum value is 500 ms, but the
value can be increased to reduce the network
traffic.
Minimum change Minimum change in the space temperature value
for update to initiate an update message from the STR Wall
(TempMinDelta) module.
Space temperature Offset value to calibrate space temperature sen-
offset sor.
(TempOffset)
306 (450) TAC AB, Nov 2006

04-00030-01-en
Temperature dis- Resolution of the temperature display.

play resolution
(Resolution)
Display timeout Time in seconds before the display reverts to the
(DispTimeout) default display. 0 means that a selected function
will remain on the display indefinitely.
Backlight timeout Time in minutes before the display backlight
(BackLightOn) (not available on STR350) turns off. 0 means
disabled backlight.
Temperature set- Lower limit for the temperature setpoint. Abso-
point low limit lute or Offset value depending on configuration
(SetpointLow) (Options1).
When this is an Offset value a negative value
will be used, irrespective of the sign of the
entered value.
Temperature set- Upper limit for the temperature setpoint. Abso-
point high limit lute or Offset value depending on configuration
(SetpointHigh) (Options1).
HVAC Settings Bits are used to set the STR HVAC configura-
(Options1) tion.
Each bit box is described in the Bit(s) descrip-
tion group box, when the cursor is put in the bit
box.
Auxiliary Options Bits are used to set the STR auxiliaries configu-
(Options2) ration. These may include Sunblind, Lighting,
and sensors for CO2, RH or occupancy.
Each bit box is described in the Bit(s) descrip-
tion group box, when the cursor is put in the bit
box.
Spare Options Spare options for future use.
(Options3)
These configuration settings are realised with a number of PVR -

STROUT pairs, put in a separate module, which can be found with the
HFB Navigation Tree. Normally, there is no reason to tamper with
these.
When the device configuration has been made, all binding tables will
contain the current configuration information. The Mod Number
parameter will show the TAC Xenta and defined I/O or Wall module
numbers.
TAC AB, Nov 2006 307 (450)

04-00030-01-en
11.3 Generating Executable Code

Executable application program code is generated by selecting the com-
mand Generate in the Commands menu in simulation mode. Note that
the downloadable code files are defined by the System version setting
in the Device configuration command of the Options menu. The fol-
lowing files are created, where “*” denotes the file name of the applica-
tion program source code (.MTA/.AUT) file:
Table 11.5:
*.COD TAC Xenta “machine code” file in ASCII for-

mat. Executable file to be downloaded to the
controller.
*.ESP Specification file: table containing public sig-
nals, their attributes etc. This file is used as the
input data file for the OP configuration tool.
*.XIF The external interface file will only be generated
if SNVTs are included in the application pro-
gram. It contains a standardised description of all
the network variables/objects of the application
program, which enables binding and communi-
cation with LonWorks nodes from other manu-
facturers.
The file name and date of the source code (.MTA/.AUT) file is included
in the object and executable files. This data is included in the informa-
tion transferred from the controller to the PC during upload, see
Section 11.7, “Uploading Application Data”.
When the executable code is generated, new OP files can also be gener-
ated, either automatically or user selected via a pop-up dialog. In doing
so, the OP configuration tool is invoked with the .OPC file of the current
application, but with “Name” and “Abbreviation” taken from the cur-
rent program specification, and the following files are automatically
generated:
Table 11.6:
*.OPC An OP menu tree file, which consists of a mix of

the .OPE (empty menu tree) and the .ESP file.
*.BIN A binary file with menu tree data for download-
ing to the TAC Xenta controller together with
the .COD file.
*.CHR A national character set file for downloading to
the TAC Xenta controller together with the
.COD file.
308 (450) TAC AB, Nov 2006

04-00030-01-en
11.4 Calculating Memory Usage

You can display the calculated memory usage for the current applica-
tion by means of the Memory usage command in the Options menu.
This dialog also contains text indicating whether the application will fit
into the TAC Xenta or not.
Note
The application can be downloaded even if it doesn’t fit into the TAC
Xenta. In this case, the network configuration will have to be reloaded.
The displayed values are calculated for a version 3 TAC Xenta device,
and may differ slightly from the true memory usage of the TAC Xenta.
Furthermore, there are additional max. limits in the TAC Xenta device,
which may stop a download attempt and give a “Parser code error” mes-
sage while trying to download. Please contact the TAC Helpdesk if you
are having this type of problem!
The available general storage depends on the TAC Xenta device (280/
300/400) and version used. The TAC Xenta uses the following memory
areas (three in the TAC Xenta 300; four in the TAC Xenta 400) to store
the application program and data. In TAC Xenta 300, the Application
files and Application are joined in one single memory area.
Table 11.7:
Application files The downloaded program files (*.COD, *.BIN,

*.CHR and *.BPR).
Application Data extracted from these files, e. g. tables for
public signals, time schedules and alarm texts.
Parameters The parameters used by the function blocks, e. g.
initial values in PV blocks and co-ordinates in
CURVE blocks.
Work area Data created when executing the application pro-
gram, e. g. output status and time schedules.
TAC AB, Nov 2006 309 (450)

04-00030-01-en
Also displayed are:
Table 11.8:
Number of The function blocks and definitions of TAC

objects Menta in the TAC Xenta are transformed into
objects. For each memory area, the dialog shows
the total memory used, the available memory
and the free memory in the TAC Xenta device.
For the Application memory, the sizes of the dif-
ferent downloadable file types are also shown. If
the free memory fr of one of the three areas tends
to become too small, the application program
size may have to be reduced. Then, please note
the following:
• The Application memory usage can be
reduced by bringing down the size of the
application program files. In particular the
OP menu tree and the expression blocks
(also, operators are compiled as expression
blocks) use a lot of memory.
• The free Work area memory space can be
increased by reducing the number of week
and holiday charts.
The Memory usage dialog also contains an Advanced button. Clicking

this button will display a dialog containing the following memory cal-
culation possibilities:
Table 11.9:
TACN/SNVT Each TAC Xenta device type has a fixed number

in/out of input and output entries reserved for Network
variables (TACNV) and SNVT. For the defined
(in the Device Configuration dialog) TAC Xenta
device type, the dialog displays the number of
defined and free entries in the current applica-
tion.
BPR size calcu- If the size of the network neighborhood file
lator (.BPR) is unknown when creating the FBD, it
can be calculated by entering the estimated num-
ber of TAC groups and average number of TAC
Xenta devices (Nodes) in each group, together
with the average number of characters in the
Group and Node names. Clicking the Calculate
button will then displayt the calculated .BPR
size, which is good to know in advance if there is
a risk of running out of Application memory.
310 (450) TAC AB, Nov 2006

04-00030-01-en
11.5 Online Functions

With TAC Menta, the user may read/write public signals and parame-
ters online, i.e. while the application program is executing in a con-
nected TAC Xenta device. The up to six signals included in the trend
log are updated more often than the other signals. It is only possible to
establish an online connection with the local TAC Xenta device which
is physically connected to the PC.
TAC Xenta network communication can be configured without access
to the FBD source code. I/O binding information can be uploaded from
the controller, manipulated and downloaded back to the controller. It is
also possible to define network variables in network offline in Edit
mode, and to download the information later.
11.5.1 Online Mode

Online operation mode is invoked by pressing the Online button in
Simulation mode, or by selecting the Online command in the Options
menu.
You are not allowed to enter Online mode when there are test probes in
the FBD, as programs like this cannot be executed in the controller. If
the program contains test probe blocks, an error message will be shown
and the operation will be aborted.
After the online connection has been established, one of the following
cases will apply, depending on whether an application program is
loaded in TAC Menta or in the connected TAC Xenta device or not:
1. No application program is loaded in TAC Menta nor in
the connected TAC Xenta device
TAC Menta enters Online mode directly. In this case you are only able
to set the device name of the connected device, since no application pro-
gram is loaded.
2. An application program is loaded in the PC and/or in the
connected device
The user is prompted to select Connect, Upload, Download or Cancel.
Connect
The TAC Xenta device is connected immediately, if the program IDs of
the current FBD and the application in the device match, otherwise a
download operation will be performed.
Download
When the Download command is executed, a check that none of the fol-
lowing is true will first be done, in which case the operation will be
aborted:
• There is no FBD in TAC Menta
TAC AB, Nov 2006 311 (450)

04-00030-01-en
• A standard application is to be loaded into a custom device

• A custom application is to be loaded into a standard device
If no errors are detected, the application in TAC Menta will be reset to
its initial state and a new .COD file generated. If required, the user will
be prompted to select whether or not to generate new OP files as well.
If the answer is yes, the OP configuration tool will be invoked with the
.OPC file of the current application, but with “Name” and “Abbrevia-
tion” taken from the current Program specification, and a new .BIN file
will automatically be generated. Finally the .COD, .CHR and .BIN files
are downloaded to the connected device.
Note
The version format (1 or 3) of the downloadable code files can be
defined by the System program setting in the Device configuration
command of the Options menu, if the files are to be generated before
the TAC Xenta device is online.
Upload
When the Upload command is executed, a check whether the device is
empty (No FBD) will be done, in which case the operation will be
aborted.
If the program IDs of the TAC Menta FBD and the program in the con-
nected device do not match, the FBD in TAC Menta will be discarded.
The user is prompted to enter a name for the uploaded .COD file, and
will, following the upload, only be able to work in tabular mode.
If no FBD is loaded in TAC Menta, the user will be prompted to enter a
file name for the uploaded .COD file.
If no errors are detected, the application in the controller will be
uploaded to the PC. Then the .BIN, .CHR (if they exist), .COD and
.BPR files will be uploaded.
11.6 Downloading the Application Program

Normally, downloading is performed in TAC Vista. The function down-
load to a TAC Xenta device from TAC Menta via its serial port is
accessed via the Download command in the Commands menu. This
command is available in Online mode only.
When loading an application as a file into TAC Menta, to download via
the serial interface, information about the network neighborhood is
retrieved from the TAC Xenta device. When opening an application
from the TAC Vista database instead, network neighborhood informa-
tion is retrieved from the TAC Vista database.
Before sending the .COD file to the device, the .COD file saved on the
hard disk is updated with any changes made in online mode. (Actually
312 (450) TAC AB, Nov 2006

04-00030-01-en
the .COD file is saved once more with the same user-selected name as
the uploaded file. The program then looks for the file with the specified
name on the hard disk, and sends a copy to the connected device.
11.7 Uploading Application Data

The function upload to a TAC Xenta device via its serial port is
accessed via the Upload command in the Commands menu. This com-
mand is available in Online mode only. The .COD, .BIN (if it exists) and
.BPR files are uploaded.
When the Upload command is executed, the user is first prompted to
specify the file name of the uploaded .COD file. The program then
uploads the .COD file from the connected device, and saves it on the
hard disk with the selected name. Finally, TAC Menta opens the .COD
file on the hard disk.
After uploading application data, the user can inspect the application
program file name and date in the program specification, thus enabling
him/her to find the corresponding application source code (if available)
on the hard disk. The correct application source code must be loaded
into TAC Menta from the hard disk in order to be able to use the FBD
in online mode, since the graphical information is not stored in the TAC
Xenta.
11.8 Overriding Physical I/O Signals

For commissioning purposes, there is an override function in all I/O
drivers, except the one for CNT blocks:
Table 11.10:
Override Binary parameter (YES/NO), default = NO.
TAC AB, Nov 2006 313 (450)

04-00030-01-en
Override Value Parameter of the same type as the output signal.

When the override switch is set, the override
value directly affects the output of the I/O-
blocka. The override value is normally given in
the same engineering unit as the block output,
except in the case of analog output, where the
override value is given in %.
The override switch and value are supposed to
be used for commissioning purposes and are thus
possible to set via communication. Override may
be considered as an online equivalent to the
manual setting of physical input values in offline
simulation.
The override function is reached via the Over-
ride button in the I/O configuration table (in
online mode only).
a. This means that override affects the signal immediately, without being
filtered
11.9 Modifying Parameter Blocks in Online Mode

Modification of the parameter (PVB/PVI/PVR) block output states in
Online mode is implemented in the following way:
If the Backup check box is set, then the output state will be modified
when the new value is copied to the InitValue parameter in Flash mem-
ory. The new InitValue will thus also be included in the .COD file when
it is uploaded.
If the Backup check box is not set, the modified PVx output state will
not be copied to the InitValue stored in Flash memory. The block output
will then be reset to InitValue when there is a restart. Modified block
output values are not included in the .COD file.
11.10 Modifying Public Constants in Online Mode

If a public constant is modified from TAC Menta in Online mode, the
new value will be immediately transferred to the TAC Xenta, and will
be visible from the OP.
If a public constant value is modified from the OP, this change will only
be transferred to TAC Menta when the application is uploaded.
The dynamic updating of public constants may slow down the signal
display in Online mode. Thus, it is possible to turn off the online updat-
ing of public constants by using the Skip const button.
314 (450) TAC AB, Nov 2006

04-00030-01-en
11.11 Modifying Binding Parameters in Online Mode

When a binding parameter in a physical (AI/AO/CNT/DI/DO/DOPU)
I/O block is modified from TAC Menta in Online mode, the new value
will not be transferred to the TAC Xenta until the next download oper-
ation (including a new .COD file generation) is performed.
11.12 Unique Application Program ID

In order to clarify service/support responsibilities etc., it is necessary to
be able to verify, on site, whether the application program in an installed
device is identical to the source code from, for instance a TAC standard
application library.
The program ID is a checksum which only applies to the structural and
functional parts of the program, not to parameter values or I/O configu-
ration data. It is thus possible to change parameters and/or configuration
data without affecting the program identity. The program ID is dis-
played in the Program Specification dialog.
11.13 Marking Standard Applications/Controllers

A TAC Xenta controller is marked as either a Standard or a Custom
(user programmable) controller. The marking, which is unique to each
controller, is generated from the neuron ID via a special algorithm. If
the controller is marked as Standard, only standard applications can be
downloaded to that controller. If the controller is marked as Custom,
only custom applications can be downloaded to that controller. Thus, it
is not possible to download standard applications into a custom control-
ler or vice versa.
Standard application source code files are marked with a unique pass-
word generated from the FBD checksum using a special algorithm. The
FBD checksum is also used as the unique program ID.
11.14 Printing the Application Program Documentation

The Page setup command in the Preferences menu is used for setting
up both of the FBD printout and the FBD window on the screen, where
the printout page breaks are marked with blue lines. The printout paper
orientation (landscape or portrait), margins and block sizes can be set.
Block sizes of 100% are the default, but smaller block sizes can be used
to obtain better overview, and larger block sizes can be used to make the
printed pages easier to read. The graphical size of the application, the
FBD window workspace (Pages), is set in the number of horizontal and
vertical pages. The workspace can never be smaller than the displayed
number of pages at maximum zoom out.
TAC AB, Nov 2006 315 (450)

04-00030-01-en
The header to be printed on all pages is created in the Page setup dialog.
Row 1 of the header is always the Application name. Row 2 contains the
information entered in the Page header field, which can contain free
text, text from the fields of the Program specification table (#author,
#abbrev, #type and #date), the printout time and date (#prdate and
#prtime) and a tab character (#tab).
The blue lines on the screen, which mark the printout page breaks, can
be switched on/off in the Page setup dialog. The Add boundary ties
command in the Edit menu adds cross reference boxes on both sides of
the page break markers, for all connections that cross page breaks. The
boundary ties can be moved and/or deleted. After a printout, the bound-
ary tie will indicate the page and the signal number where the connec-
tion continues.
The documentation is printed by selecting the Print command in the
File menu. First, the user selects the information to be printed: Specifi-
cation (devices, public signals, I/O list, alarms, constants, constant
usage, time schedules and block parameters), FBD, associated text file
and/or OP menu tree. The orientation of the FBD is selected in the Page
setup dialog, the other information is always printed in accordance with
the Microsoft® Windows printer setup. Select a printer from the Printer
list.
If the text file option is selected, the associated text file (if available) is
printed after the program specification.
The Scale output to one page option in the Print dialog makes it possi-
ble to print one level of the FBD on a page, or one page per level. The
option Color printout is used for color printers. The option Skip empty
pages means that completely empty FBD window pages will not be
printed.
If a group of blocks is selected when the Print command is executed,
the selected group will be printed instead of the complete FBD.
If the function block diagram contains HFBs, you will either be able to
print the FBD on the current level, or make a printout on all levels.
The OP menu tree can be printed on two levels; as an overview part or
as a detailed part, including a fully expanded menu tree.
As an alternative to printing the specification, the I/O list can be saved
as an ASCII text file (.TXT) by means of the Export I/O list command
in the File menu. The text file can in turn be imported into other pro-
grams, for example CAD programs. The I/O list in the text file contains
the following columns: I/O Module No (0 = TAC Xenta 280/301/302/
401 etc), TAC Xenta or I/O Module type, Terminal Reference and Sig-
nal name.
When the “Block parameters” box in the Printout dialog is selected,
comments that are specific for TAC Vista can be printed.
316 (450) TAC AB, Nov 2006

04-00030-01-en
11.15 Associated Text Files

Each FBD (.AUT or .MTA) file may have an associated text file with
the same file name but with the extension .TXT or .DOC. This file can
be used, for instance, for a textual function description. The text editor
and the associated text file extension are user selectable. The name of
the executable file is specified in the Settings command of the Prefer-
ences menu. A change in this information is saved between subsequent
sessions.
The text file editor is opened by selecting the command Text File in the
TOOLS menu. The selected text file editor is then invoked with a text
file corresponding to the current program file name being edited. If the
text file does not exist in the same directory as the .AUT file, the file
DEFAULT.xxx (where “xxx” is the user selected text file extension)
will be copied to the FBD directory and given the same file name as the
FBD file. The file DEFAULT.xxx must be located in the same path as
TAM32.EXE. The DEFAULT.xxx file can be defined by the user and
must, of course, be a document file compatible with the selected word
processor.
TAC AB, Nov 2006 317 (450)

04-00030-01-en
318 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 12 The Download Wizard
12 The Download Wizard

Note
For TAC Vista, the Download Wizard SHOULD ONLY be used to
replace system programs in TAC Xenta devices.
Use of the Download Wizard for applications and network configura-
tion only applies for TAC Vista 3.x and TAC Menta 3.x.
Open the Start menu in Microsoft® Windows. Select TAC and TAC
Tools and you will find the Download Wizard.
The Download Wizard is a guided download procedure for upgrading
the System program of one or several TAC Xenta devices.
Note
The possibility to reuse/update a program module during a system pro-
gram upgrade depends on the program version compatibility. Also,
different extra preparations or actions may be required. For example,
a TAC Xenta 300 using System program v 1.01 cannot be updated to
version 1.13 (or later), unless both the application source code (.AUT)
and the network configuration (.NWC) are available when the proce-
dure is run. So, always read the enclosed upgrading information before
installing a new program version.
! Warning
NEVER download a system program for a TAC Xenta 300 device into
a TAC Xenta 280 device, as this will render the TAC Xenta 280 device
useless.
TAC AB, Nov 2006 319 (450)

04-00030-01-en
12 The Download Wizard TAC Menta, Technical Manual
12.1 How to Use the Download Wizard

12.1.1 The Dialog
The Download Wizard dialog consists of two pages, displayed via the
Next and Previous buttons. Page two contains the following sections:
Table 12.1:
System First check the TAC Xenta Unit type. Select to

Retain current System program, or to Download
new. If downloading a new program, the name
and path of the System file (.MOT) must be
entered.
Application Selects either Retain current Application pro-
gram, or Download new. Selecting the Clear
memory option results in a second dialog where
two alternatives are offerred. Pressing the Yes
button results in clearing the memory totally and
shall only be selected if there shall be no appli-
cation program at all in the TAC Xenta device.
This clearing causes problem when the device is
used in some types of networks. Pressing the No
button results in restoring the device to its fac-
tory contents. The No alternative is the recom-
mended alternative. If downloading a new
program, name and path to the Application file
must be entered.
Configuration Select to Retain current Network configuration,
or to Download new. Tick Check Neuron ID if
the Download Wizard is to look for missing and
mismatched Neuron IDs in the database. If
downloading a new configuration, the name and
path of the Database file must be entered.
Connected unit The current node name of the connected TAC
Xenta device is displayed. Select the desired new
node name (normally the same as Connected
unit) from the Node to download list, which dis-
plays all the nodes in the selected Database file.
320 (450) TAC AB, Nov 2006

04-00030-01-en
The dialog also contains the following buttons:
Table 12.2:
Information Displays the Device type, Hardware version,

System program version and Boot PROM
version of the connected TAC Xenta device,
and informs you if the selected Database file
is marked as dirty (i. e. the network database
contains data which has not been downloaded
to the TAC Xenta device).
Apply Starts the download procedure. The result of
the download is shown in a download
progress window.
Close Closes the dialog.
12.1.2 The General Download Procedure

If the download includes a new Application program, we recommend
that you open the corresponding .AUT file and then immediately close
it again. In this way, you will give the file a new date and avoid an
optional question about generating a .BIN file from TAC Menta during
the download procedure.
1 From the TAC Menta Group start the “Download Wizard”.
2 Connect the RS232 cable between the communication port you
have specified and the TAC Xenta controller.
3 Follow the “Wizard” and specify the software to download.
4 In the Configuration area, there is a choice for checking the Neu-
ron ID. If the box is checked, the Wizard will compare the ID of
the device with that of the database. If the ID is missing from the
database, it will be added. If the IDs differ, you will be asked
whether the database is to be updated.
5 When the appropriate boxes have been checked, click “Apply”
and wait for the procedure to complete. The result is shown in a
download progress window. If the message “Remote device does
not reconnect!” appears, this can normally be ignored.
! Warning
The TAC Xenta System download phase is critical; no other activity
is to take place at this time! If the procedure is interrupted, it may be
impossible to reload the System software.
6 When the download has been acknowledged, the procedure can be

repeated from step 2.
TAC AB, Nov 2006 321 (450)

04-00030-01-en
7 The accumulated results of all the downloads are listed in the file
“dwiz.log”, normally residing in the TAC Menta program direc-
tory. The log contains information about
• start time and affected node
• performed operations with time stamp
• total time required
• result of operations
• delimiter
• at the end: the Neuron ID, if updated in the database.
8 When the download has completed, close the “Download Wizard”
window.
12.2 TAC Menta v3 Compatibility

TAC Menta v4 is fully compatible with the TAC Xenta 280/300/3000/
400/901 and TAC Vista v3. It is also possible to connect to and generate
code for the TAC Xenta 280/300/400 v1.1 (Cf. the Device configuration
dialog), provided that only functions compatible with TAC Menta v1.2
and TAC Xenta v1.1 are used.
12.2.1 .AUT Files

Earlier versions of TAC Menta application source code files may be
opened and edited. When the old file is opened, it is automatically con-
verted to the latest version. If the file is then saved using a manual Save
command, it will be saved in the new format. It is not possible to save
new files in older format(s).
Due to modifications to the print-out page size and page breaking func-
tions in TAC Menta v3, the upgrade of an application from v1 may
require manual adjustment of the graphical layout of the FBD.
12.2.2 .COD Files

After upgrading the TAC Xenta system program from v1.x to v3, the
.COD file must be regenerated from the .AUT file before download, due
to changes in the downloaded (.COD) file format between TAC Menta
v1.2 and v3. Thus, the application source code must be available when
a controller system program is upgraded.
When connected to a TAC Xenta v1.x device, TAC Menta will by
default generate and download .COD files in v1.x format. Before com-
munication starts, a special message is sent to the TAC Xenta device,
the response to which decides what type of protocol to use.
When connected to a TAC Xenta v1.x device, it is also possible to
upload the application. If, before the upload, you open the correspond-
322 (450) TAC AB, Nov 2006

04-00030-01-en
ing .AUT file, you may then regenerate the .COD file (with the
uploaded parameters) in TAC Menta v3 format. This will not, however,
be possible if you do not have the .AUT file. There is currently no way
of converting the .COD file from v1.x to v3 without having access to the
.AUT file.
12.2.3 OP Menu Tree Files

V1.x OP menu tree (.BIN) files using the old, more space-consuming
time schedule format will be accepted by TAC Xenta v3. However, if
application memory space is a problem (which is often the case), the
user is strongly recommended to regenerate the OP file to v3 format
using the Time Schedule Templates option to save space.
12.3 Upgrading a TAC Xenta 300 Device to v3

When upgrading a TAC Xenta 300 device from system program v1.x to
v3, the procedure below should be followed. All TAC Xenta 280/301/
302/401s in the network must have the same System software version
(v1 or v3).
12.3.1 Updating the .AUT File with Application Data (Optional)

• Start TAC Menta and open the .AUT file for the application in the
TAC Xenta device to be upgraded.
• Upload the .COD file from the TAC Xenta device.
• Save the application program file in Simulation mode (answer
“Yes” to the question ”…Do you want to save?”). It will then auto-
matically be converted to TAC Menta v3 format, and updated with
the uploaded parameters.
These steps may be omitted if the .AUT file saved on disk has up-to-
date parameters. This procedure will, however, be necessary, if you
believe that the parameter settings have been modified from the OP or
from TAC Vista, and these settings must be kept after the upgrade.
12.3.2 Upgrading System and Application Programs

Either Alt. 1 or 2 below will apply, depending on the circumstances.
1 No Change in the Network Configuration
• Start the Download Wizard, and select the following options:
Download new system, Download new application, and
Retain current configuration.
• Select the appropriate system program file and application
program file (select the file created in step 1 if applicable).
• Click the Apply button to complete the upgrade procedure.
After the system program has been downloaded, a new .COD
TAC AB, Nov 2006 323 (450)

04-00030-01-en
file in v3 format will be generated from the selected applica-

tion program file and downloaded together with the .BIN file
(if applicable) and the uploaded .BPR file.
2 Alt. 2 – New Or Modified Network Configuration
• Start the Download Wizard, and select the following options:
Download new system, Download new application, and
Download new configuration.
• Select the appropriate system program, application program
(select the file created in step 1, if applicable), and network
database files.
• Click the Apply button to complete the upgrade procedure.
After the system program has been downloaded, a .BPR file
for the connected device will be generated from the selected
network database file, a .COD file in v3 format will be gener-
ated from the selected application program file and, if applica-
ble, a .BIN file as well. Finally, the .COD file will be
downloaded together with the .BIN file and the .BPR file.
12.3.3 Verifying Correct Operation (Optional But Recommended)

• Start TAC Menta, and open the application program file with the
application source code.
• Connect to the device, and verify that the application program in
the controller is operating correctly.
324 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 13 Function Blocks, Summary
13 Function Blocks, Summary

13.1 I/O Blocks
Table 13.1:
Acronym Short description

AI Analog input.
AO Analog output.
CNT Pulse counting digital input
DI Digital input.
DO Digital output.
DOPU Digital pulse output
STRIN STR Wall Module input.
STROUT STR Wall Module output.
External I/O signals can be connected to the application program via

four generic I/O blocks (AI, DI, AO and DO). For the STR Wall Module
there are two dedicated blocks (STRIN and STROUT) with the same
purpose.
The generic I/O blocks can be associated with either a physical or a net-
work address; the STR blocks can only associated with certain STR
variables. This association is called binding.
There are also two special kinds of I/O blocks, one for digital input
pulse counting (CNT), and one for pulse width modulated digital out-
puts (DOPU). It is not possible to bind the CNT and DOPU blocks to
remote network addresses, because of possible timing and synchronisa-
tion problems.
TAC AB, Nov 2006 325 (450)

04-00030-01-en
13 Function Blocks, Summary TAC Menta, Technical Manual
13.2 Signal Sources

Table 13.2:

NCYC Program cycle counter.
OSC Oscillator, gives a pulse train.
PVB Binary value parameter.
PVI Integer value parameter.
PVR Real value parameter.
13.3 Logical Functions

Table 13.3:

AND AND function on 2 Binary signals.
NOT Inverts a Binary signal.
OR OR function on 2 Binary signals.
PULSE Monostable pulse generator (signal).
SR Set-reset flip-flop
TRIG Trigger, true on input change of state
XOR XOR function on 2 Binary signals.
13.4 Non-linear Functions

Table 13.4:

AHYST Analog hysteresis
HYST Binary hysteresis (relay function)
LIMIT Max/min limit
MAX Maximum value of 2 signals
MIN Minimum value of 2 signals
326 (450) TAC AB, Nov 2006

04-00030-01-en
13.5 Delay Blocks

Table 13.5:

DELAY Delay on or off.
DELB Binary value delay in 1 cycle.
DELI Integer value delay 1 cycle.
DELR Real value delay in 1 cycle.
SHB Sample and hold Binary value.
SHI Sample and hold Integer value.
SHR Sample and hold Real value.
Delays have a single input of the same type as the output.

Sample and hold blocks have an input of the same type as the output and
a Binary control input. While the control signal is activated (true), these
blocks function as delay blocks, but when this signal is deactivated, the
output retains the value which it had when the control signal was deac-
tivated.
13.6 Controllers and Filters

Table 13.6:

FILT First order filter.
OPT Start/stop time optimization
PIDA PID controller (analog output)
PIDI PID controller (increase/decrease output)
RAMP Ramp filter (rate limit)
SEQ Sequencer.
TAC AB, Nov 2006 327 (450)

04-00030-01-en
13.7 Accumulators
Table 13.7:

ACCUM Real accumulator
INTEG Integrator
RT Running time measurement
13.8 System Variables

Table 13.8:

DATE Actual date.
ERR System error.
HOUR Actual hour.
MINUTE Actual minute.
MONTH Actual month.
RST Restart. The output is activated the first execu-
tion
SECOND Actual second.
TCYC Cycle time for the application program module.
WDAY Actual day of week. 1 = Monday.
This group consists of function blocks whose output is updated by an

internal variable of the TAC Xenta. Therefore, all the blocks in this
group belong to the source nodes since they have no inputs.
13.9 Time Schedules and Alarms

Table 13.9:

ALARM Initiates alarm message
TSCH Time schedule
328 (450) TAC AB, Nov 2006

04-00030-01-en
13.10 Transformation Functions

Table 13.10:

CURVE Partially linear curve function.
ENTH Enthalpy calculation.
POLY Polynomial transform function.
PRCNT Percentages transformation
VECTOR Vectorial transform function.
TAC AB, Nov 2006 329 (450)

04-00030-01-en
330 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 14 Simple Blocks
14 Simple Blocks
Description
In the description of a block the following information is provided:
Fig. 14.1:
Table 14.1:
Input Name Type explanation

Parameters Name Type explanation
Output types Type
Access RO
Description...
Table 14.2:
Inputs Defines the input types and briefly explains their

function.
Parameters Defines the FB parameters and briefly explains
their meaning.
Output Types Defines the data type of the block output. When
two blocks are connected, the output type should
coincide with the input type.
Access Defines whether the signal exported by the block
is read only (RO) or read/write (R/W). Only
blocks defined as R/W may be modified by an
action from a superior node.
Description A brief functional description of the block.
TAC AB, Nov 2006 331 (450)

04-00030-01-en
14 Simple Blocks TAC Menta, Technical Manual
14.1 ACCUM – Accumulator
Fig. 14.2:
Table 14.3:
Parameters Increment (i) REAL Amount accumulated in each program

cycle
Reset (rs) BINARY Reset input (1 = reset)
ResetValue REAL Value assigned to the output when the
(rv) reset input is actvated
Parameters InitValue REAL Initial accumulator value
Output types REAL
Access R/W
Description
This block is used to accumulate the total consumption from an incre-
mental input (the consumption during one program cycle). It calculates
the sum of the variable Increment over time. The summation is done
with using numerical precision to avoid underflow when the increment
is small.
Note
The accumulated value is delayed by one program cycle before it
appears on the output.
The accumulator output is set to InitValue at the initial state. When the
Reset input is activated, the accumulator output is reset to a value spec-
ified by the ResetValue input signal. When the Reset input is deacti-
vated, the accumulation resumes from the last value of the ResetValue
input.
The upper and lower output limits are set by the maximum floating-
point number that can be represented in the controller.
332 (450) TAC AB, Nov 2006

04-00030-01-en
14.2 AHYST – Analog Hysteresis
Fig. 14.3:
Table 14.4:
Inputs variable REAL input signal

Parameters Rise REAL value of the input signal for the ascent
in the hysteresis loop
Fall value of the input signal for the descent
in the hysteresis loop
Output types REAL
Access R/W
Description
This implements an Analog hysteresis function. The output follows the
input as long as the input is outside the limits of the hysteresis loop.
When the input variable enters into the hysteresis loop, the output takes
the limiting values of the hysteresis, cf. the figure below:
Fig. 14.4:
If Rise > Fall, the loop will be counter-clockwise as indicated in the fig-
ure, and if Rise < Fall, the hysteresis loop will be clockwise.
If a complex function containing several hysteresis loops is required,
the best method of achieving this is to form the function using other
blocks (POLY, CURVE, VECTOR, etc.) and append in cascade as
TAC AB, Nov 2006 333 (450)

04-00030-01-en
many AHYST blocks as there are hysteresis loops in the desired transfer
function.
14.3 AI – Analog Input
Fig. 14.5:
The AI block has five different sets of parameters depending on the
selected I/O Configuration option:
• Linear Analog input
• Non-linear Analog input
• Network variable
• SNVT
• Constant value
The block output is updated only once during each program cycle,
which entails that changes in the physical inputs with a duration of less
than one program cycle will not be noted by the application program.
Note
If you are using TAC Menta version 4.0 and system version 3.5 of the
TAC Xenta device, it is possible to get the AI block to use the SI or I-
P system of units for specified parameters.
Linear Analog Input
Table 14.5:
Parameters Mod Number INTEGER Number of I/O module(s).

Terminal Ref STRING Terminal reference.
Sensor Type ENUM Sensor type
Min Value REAL Lower input range limit
Max Value REAL Upper input range limit
Time Const REAL Filter time constant (sec).
Initial Value REAL Initial output value (Only I/O module).
Default value = 0.
Output type REAL
Access RO
334 (450) TAC AB, Nov 2006

04-00030-01-en
Description
The Linear Analog Input configuration option reads the value of an
Analog input using a linear sensor. The block output value is the phys-
ical Analog input value converted to engineering units.
The conversion for different system of units (SI or I-P) is defined when
the fields Min Value and Max Value are determined in relation to the
input signal range of the selected type of Sensor:
The Mod Number parameter specifies the I/O module number (0 =
TAC Xenta 280/300/400), and Terminal Ref indicates the type and
number of the input terminal (e.g. B1 – B4, U1 – U4).
Select the Sensor Type from a predefined list for the selected type of
TAC Xenta device or I/O module, e.g. 0–10 V or 4–20 mA. The con-
version to engineering units is done with the Min Value and Max Value
parameters, which represent the lower and upper sensor range limits in
engineering units, e.g. 0–40 °C, corresponding to the minimum and
maximum electrical input signal range limits.
After conversion, the sensor reading can be filtered in a discrete time
first order software filter included in the function block. The filter time
constant is specified in seconds with the Time Const parameter.
The filter algorithm is
1
y ( k ) = y ( k – 1 ) + ------------- ( u ( k ) – y ( k – 1 ) )
T
1 + ---
h
where y(k) and u(k) are the filtered and unfiltered values at time k,
respectively, h is the sampling interval (i.e. the application program
cycle time), and T is the filter time constant. If the time constant is less
than or equal to zero, no filtering is done. To obtain a good filter func-
tion, the time constant should be set significantly greater than the appli-
cation program cycle time.
This filter algorithm is based on a straightforward backward difference
approximation of the continuous time derivative operator. For further
details, please refer to, for instance, Åström and Wittenmark: “Com-
puter Controlled Systems – Theory and design”. Prentice-Hall, Engle-
wood Cliffs (1984).
The initial block output value for an I/O module block (before a signal
value has been received from the I/O module) is specified by the Initial
Value parameter. If the I/O module goes offline, the block output will
keep the last value that was received from the I/O module.
TAC AB, Nov 2006 335 (450)

04-00030-01-en
Non-Linear Analog Input

Table 14.6:
Parameters Mod Number INTEGER Number of I/O module.

Sensor Type ENUM Sensor type
Time Const REAL Filter time constant (sec).
Default value = 0.
Output type REAL
Access RO
Description
The Non-linear Analog Input configuration option reads the value of
an Analog input using a non-linear sensor, for instance a thermistor.
The block output value is the physical Analog input value converted to
engineering units. The conversion is done through a predefined curve
defining the sensor characteristics.
The selection is made when the Sensor: parameter is selected in the
Drop-down Combo box in the Bind Analog Input dialog. Selecting a
sensor in the SI unit system (metric) will generate a block where the
block value is in the SI unit system (degree Celsius). Selecting a unit in
the I-P (inch-pound) unit system will generate a block where the block
value is converted to the IP unit system (degrees Fahrenheit).
For this type of analog input, the national setting of the PC does not
influence the unit system.
The Unit: parameter for this type is only a text, used to describe the
block and does not influence the unit system.
An edited application Function Block Diagram (FBD) will retain the
selected unit system for this type of block whether the FBD is opened
in a PC with an SI or an I-P unit system.
number of the input terminal (e.g. B1 – B4, U1-U4).
The type of sensor characteristic used in the conversion to engineering
units is selected from a predefined set of sensor types with the Sensor
Type parameter. The choice SP adjust is used when connecting the
potentiometer signal from the set point offset dial of a ZS 100 range
wall module.
336 (450) TAC AB, Nov 2006

04-00030-01-en
After conversion, the sensor reading can be filtered in a discrete time

first order software filter included in the function block. The filter time
constant is specified in seconds with the parameter Time Const.
The filter algorithm is the same as in the Linear Analog Input configu-
ration option.
The initial block output value for an I/O module block (before a signal
value has been received from the I/O module) is specified by the
parameter Initial Value. If the I/O module goes offline, the block output
will keep the last value that was received from the I/O module.
Network Variable
Table 14.7:
Parameters Network STRING Reference to external TAC network

Address signal
Initial Value REAL Initial output value. Default value = 0.
Delta REAL The smallest change of value in the
external signal which will initiate an
update of the imported value.
Default value = 0.5
Period INTEGER Maximum time interval (in seconds)
between two updates of the imported
value. Default value = 60
Output type REAL
Access RO
Description
The Network Variable configuration option is used to import signals
from other TAC devices into the application program via the network.
The Network Address is a public Real or Integer signal in the other
TAC device, entered as a character string e.g. \RPU1\AHU1\Outdoor-
Temp (maximum string length \20\12\20). It is not possible to change
the network address reference during runtime.
The initial block output value (before a external signal value has been
received via the network) is specified by the Initial Value parameter. In
case of a communications error, the block output will not be updated
(i.e. it will always keep the last signal value that was received via the
network). After a cold start, when the controller RAM is cleared, the
block output will be reset to Initial Value.
The imported value will be updated each time the external signal value
differs from the last sent value by more than Delta units (A negative
Delta value means that the function is not used). Regardless of whether
the external signal has changed or not, the imported value will also be
TAC AB, Nov 2006 337 (450)

04-00030-01-en
updated when the time interval Period has elapsed since the last update
(Period values less than 1 s will give Period = 1 s).
Note
There is no point in using the same network address in several AI
blocks in the same FBD, because it would impose an unnecessary load
on network communications to have multiple import declarations of
the same external signal. Only one block for each signal should be
used, and connected to all blocks in the FBD that are using the
imported signal.
SNVT
Table 14.8:
Parameters Type STRING Reference to SNVT type

Member STRING Reference to SNVT member (Only
applicable when a structured SNVT
type is selected).
SNVT Name STRING Network identifier for the signal, max.
16 characters.
Poll BINARY Defines whether the bound external
output variable is to be polled or not.
Output type REAL
Access RO
Description
The SNVT option is used to import external signals into the application
program via the network. The input block must also be bound to an
external output variable of the same SNVT type via network manage-
ment software. Note that the signal can be given different names within
the application (the block name, e.g. OutdoorTemp) and on the network
(the SNVT name, e.g. nvioutdoortemp).
A SNVT is, by design, represented in the SI unit system, but you can set
it to be represented in the I-P unit system. The default unit selection is
determined by the national setting of the Windows© operating system
for the PC in which the application program is created.
The default Unit: parameter is determined when the Type and Member
of the SNVT is selected in the Bind Analog Input dialog. Selecting the
338 (450) TAC AB, Nov 2006

04-00030-01-en
SNVT in a PC with a SI (metric) unit system will generate a block

where the unit remains in the SI unit system. Selecting the SNVT in a
PC with an I-P (inch-pound) unit system will generate a block where the
value is converted to the I-P unit system.
The Unit: parameter can be redefined using the Drop-down Combo box
in the Bind dialog.
in a PC with an SI or an I-P unit system setting.
Select Type and Member from predefined lists of supported SNVT
types.
The initial block output value (before an external signal value has been
received via the network) is specified by the Initial Value parameter.
After a cold start, when the controller RAM is cleared, the block output
will be reset to Initial Value.
In case of a communications error, the block output will not be updated,
i.e. it will keep the last signal value that was received via the network.
After external binding, the external output variable will be polled if Poll
is checked and no updates arrive within Period.
Constant Value
Table 14.9:
Parameters Initial Value REAL initial value of the output.

Output type REAL
Access RO
Description
The input block is not connected to an external physical or network
address. Instead the option assigns a constant value specified by the
Initial Value parameter to the block output.
14.4 ALARM – Alarm
Fig. 14.6:
TAC AB, Nov 2006 339 (450)

04-00030-01-en
Table 14.10:
Inputs Input BINARY Input signal

Parameters DelayOn REAL Delay before alarm is set (sec)
DelayOff REAL Delay before alarm is reset (sec)
Priority INTEGER Alarm priority level
AlarmText STRING Optional alarm text.
Output type BINARY
Access RO
Description
The ALARM block monitors the state of the Binary input signal. A ris-
ing edge (transition from 0 to 1) starts a timer which measures how
long the input is true (1). If the measured time exceeds the specified
alarm activation (set) delay time, an alarm record containing informa-
tion about the status, time, signal name, priority and an optional alarm
text will be generated by the system software. When an alarm is set, the
alarm block waits for the input to become false (0). The falling edge of
the input signal triggers a timer in the same manner as the rising edge.
After the alarm reset delay time has expired, the alarm is reset by the
system software.
The ALARM block output signal indicates the current alarm status. 1 =
alarm set, 0 = no alarm (reset).
The alarm set and reset delay times are specified in seconds with the
DelayOn and DelayOff parameters, respectively. Please refer to the
timing diagram below, which shows the setting and resetting of an
alarm. If a power outage occurs during the delay, the elapsed delay
time will be saved, if the Backup check box is set.
The alarm priority is specified with the Priority parameter. There are 10
levels, 1 to 9 and 0, where 1 is the highest. Events with priority 0 (Infor-
mation messages) have the lowest priority. They are not placed in the
alarm database of TAC Vista and do not appear in the alarm overview.
The priority value has no function in the Xenta application program
itself; it is used for presentation in, for example, TAC Vista or the TAC
Operator Panel.
340 (450) TAC AB, Nov 2006

04-00030-01-en
Fig. 14.7: Relation between Input signal and Alarm Output signal.
Note
The input signal must be true for a time interval longer than DelayOn
in order to generate a new alarm. The input must also be false for a
time interval longer than DelayOff in order to reset the alarm.
14.5 AND – Logical AND Gate
Fig. 14.8:
Table 14.11:
Inputs state1 BINARY

state2 BINARY
Output type BINARY
Access RO
TAC AB, Nov 2006 341 (450)

04-00030-01-en
Description
Calculates the boolean AND function of state1 and state2 according to
the following truth table:
Table 14.12:
state 1 state 2 output

0 0 0
0 1 0
1 0 0
1 1 1
14.6 AO – Analog Output
Fig. 14.9:
The AO block has three sets of parameters depending on the selected I/
O Configuration option:
• Physical output
• SNVT
• Not connected
Note
TAC Xenta device, it is possible to get the AO block to use the SI or
I-P system of units for specified parameters.
Physical Output
Table 14.13:
Input Input REAL Input signal, 0-100%
342 (450) TAC AB, Nov 2006

04-00030-01-en
Table 14.13:

Voltage 0% REAL Output signal at 0% input (Volt)
Voltage 100% REAL Output signal at 100% input (Volt)
Default value = 0 (Volt).
Output type Block has no
output
Access RO
Description
The Analog output block converts a 0–100% signal from the application
program to a voltage signal on a physical Analog output.
The Mod Number parameter specifies the I/O module number (0 = TAC
Xenta 280/300/400), and Terminal Ref indicates the type and number of
the output terminal (e.g. Y1–Y4).
The output voltages corresponding to 0% and 100% input signal are
specified (in Volts) with the Voltage 0% and Voltage 100% parameters,
respectively. Note that the voltages may be reversed, e.g. Voltage 0% =
10 V and Voltage 100% = 2 V.
The Initial Value parameter specifies the output signal value (in V) for
an I/O module block when the I/O module goes offline, e.g. following
a restart immediately after a power outage.
TAC AB, Nov 2006 343 (450)

04-00030-01-en
SNVT
Table 14.14:

type is selected).
16 characters.
Send BINARY Defines whether the bound external
input variable is to be automatically
updated or not.
Delta REAL The smallest change of value in the
input signal which will be exported to
the external input variable. Default
value = 0.5
between two updates of the exported

output
Access RO
Description
The SNVT option is used to export signals from the application pro-
gram via the network to an external device. The output block must also
be bound to an external input variable of the same SNVT type via net-
work management software. Note that the signal can be given different
names within the application (the block name, e.g. OutdoorTemp) and
on the network (the SNVT Name, e.g. nvooutdoortemp).
A SNVT is, by design, represented in the SI unit system, but you can set
it to be represented in the I-P unit system. The default unit selection is
determined by the national setting of the Windows© operating system
in the PC, in which the application program is created.
The default Unit: parameter is determined when the Type and Member
of the SNVT is selected in the Bind Analog Input dialog. Selecting the
SNVT in a PC with a SI (metric) unit system will generate a block
where the unit remains in the SI unit system. Selecting the SNVT in a
PC with an I-P (inch-pound) unit system will generate a block where the
value is converted to the I-P unit system.
344 (450) TAC AB, Nov 2006

04-00030-01-en
The Unit: parameter can be redefined using the Drop-down Combo box
in the Bind dialog.
in a PC with an SI or an I-P unit system setting.
Select Type and Member from predefined lists of supported SNVT
types.
The initial output value (before the first program cycle is executed) is
specified by the Initial Value parameter.
If Send is checked, the external variable will be updated each time the
block input signal value deviates from the last sent value by more than
Delta units. Regardless of whether the input signal has changed or not,
the external variable will also be updated when the time interval Period
has elapsed since the last update. If Period is set to 0, the external vari-
able will only be updated on Delta deviation.
If Send is not checked, the external device will have to poll to get
updated signal values. The exported value will only be altered if the
block input signal value deviates from the last exported value by more
than Delta units.
Not Connected
The Not connected binding means that the block is not connected to a
physical or network address. It has no configuration parameters.
14.7 CNT – Digital Input – Pulse Counter
Fig. 14.10:
The CNT block can, via the I/O Configuration option be bound as
either Pulse counter (Physical input) or Not connected.
Table 14.15:

Normally BINARY Check box set = trig on rising edge
Open
i.e. open –> closed (Default).
Check box not set = trig on falling
edge i.e. closed –> open.
Multiplier REAL Scale factor. Default value = 1.0
TAC AB, Nov 2006 345 (450)

04-00030-01-en
Table 14.15:
Output type REAL

Access RO
Description
This block counts the number of pulses on a digital input since the last
execution of the application program. The counter will stop, not reset
to zero, if the number of pulses reaches the maximum Integer value
(32767) before the next program cycle or (if an I/O module is used)
before the value has been sent to the TAC Xenta 280/300/400. The
minimum pulse length depends on the hardware used.
The number of pulses is converted to engineering units by multiplying
the pulse counter value with the scaling factor Multiplier.
The Mod Number parameter specifies the number of I/O module (0 =
number of the input terminal (e.g. U1–U4, X1–X4).
Depending on the value of the Normally Open parameter, counting is
triggered by the rising or falling edge of the digital input signal:
Check box set = trig on rising edge (open –> closed) Check box not set
= trig on falling edge (closed –> open).
Not Connected
14.8 CURVE – Curve Function
Fig. 14.11:
Table 14.16:
Inputs Input REAL

Parameters Limit BINARY Selector for limit function (limit = 1)
or linear extrapolation (limit = 0).
Dimension REAL A list of co-ordinate pairs x,y defining
(Pair list x,y) the breakpoints of the curve function.
346 (450) TAC AB, Nov 2006

04-00030-01-en
Table 14.16:
Output type REAL

Access RO
Description
This block implements an arbitrary partially linear curve defined by a
number of curve breakpoints (xi, yi), i.e. the function values y = f(x)
for a set of input x values. The number of breakpoints must not exceed
127. The number of specified breakpoints (N) is indicated as Dimen-
sion in the graphical function block symbol. The breakpoints are
entered as a list of Real values x,y separated by commas, with one co-
ordinate pair on each row. The x values in the list should be entered in
order, i. e. xi-1 < xi < xi+1.
The Input signal is compared to the x-components of the breakpoints in
order. The first coordinate pair with an x-component greater than the
Input signal is chosen as the end point of a line segment starting in the
previous point. The Output signal is then calculated by linear interpola-
tion on this line segment.
If the limit function selector is set to 1, the output will be set to y1 when
the input is less than x1, and to yN when the input is greater than xN.
When the limit selector is disabled, the output is computed by linear
extrapolation whenever the input signal exceeds the range (x1, xN).
The following is a graphical representation of a “simple” case:
Fig. 14.12:
TAC AB, Nov 2006 347 (450)

04-00030-01-en
If two coordinates are equal, the curve will look like this:
Fig. 14.13:
At the discontinuity, i.e. when the input = x2, the function output will be
y2.
14.9 DATE – Day
Fig. 14.14:
Table 14.17:
Output type INTEGER

Access RO
Description
Provides the day of month (1-31) according to the internal time clock.
348 (450) TAC AB, Nov 2006

04-00030-01-en
14.10 DELAY – Delayed On/Off
Fig. 14.15:
Table 14.18:
Inputs state BINARY input signal

Parameters DelayOn REAL activation delay in seconds
DelayOff REAL deactivation delay in seconds
Output type BINARY
Access RO
Description
This block delays the transitions of an input signal (state) by the time
specified in seconds as defined by the DelayOn (transition 0 to 1) and
DelayOff (transition 1 to 0) parameters. Note that the input signal must
be true for a time interval longer than DelayOn in order to generate a
pulse on the block output, cf. the timing diagram below. The input must
also be false for a time interval longer than DelayOff in order to reset the
output to false.
Fig. 14.16:
TAC AB, Nov 2006 349 (450)

04-00030-01-en
If a power outage occurs during the delay, the elapsed delay time will
be saved, if the Backup check box is set.
14.11 DELB – Binary Value Delay
Fig. 14.17:
Table 14.19:
Inputs state BINARY Binary input signal

Parameters InitValue BINARY initial value for the output signal
Output type BINARY
Access R/W
Description
This block introduces a delay of one program cycle in the propagation
of a Binary signal. Each program cycle, the output value is updated
with the input value from the previous cycle.
14.12 DELI – Integer Value Delay
Fig. 14.18:
Table 14.20:
Inputs variable INTEGER input signal.

Parameters InitValue INTEGER initial value for the output signal.
Output type INTEGER
Access R/W
350 (450) TAC AB, Nov 2006

04-00030-01-en
Description
of an Integer signal. For each program cycle the value of the output is
updated with the input value from the previous cycle.
14.13 DELR – Real Value Delay
Fig. 14.19:
Table 14.21:
Inputs variable REAL Analog input signal.

Parameters InitValue REAL Initial value for the output signal.
Output type REAL
Access R/W
Description
of a Real signal. For each program cycle, the value of the output is
updated with the input value from the previous cycle.
14.14 DI – Digital Input
Fig. 14.20:
The DI block has five different sets of parameters depending on the
• Network Variable
• Physical Input
• Online Device
• SNVT
• Constant Value
TAC AB, Nov 2006 351 (450)

04-00030-01-en
The block output is updated only once during each program cycle, this
means that changes to the physical inputs that have a duration of less
than one program cycle will not be noted by the application program.
Network Variable
Table 14.22:
Parameters Network STRING Reference to external TAC network

Address signal.
Initial Value BINARY Initial block output value; On or Off.
Default value = Off.
value. Default value = 60.
Output type BINARY
Access RO
Description
The Network Variable configuration option is used to import signals
from other TAC devices into the application program via the network.
The Network Address must be a public Binary signal in the other TAC
device, entered as a character string e.g. \RPU1\AHU1\ExtendedOp
(maximum string length \20\12\20). It is not possible to change the net-
work address reference during runtime.
received via the network) is specified by the Initial Value parameter. In
case of a communications error, the block output will not be updated
(i.e. it will always keep the last signal value that was received via the
network). When cold starting, after the controller RAM is cleared, the
network input block output will be reset to Initial Value.
The imported value will be updated each time the state of the external
signal changes. Regardless of whether the external signal has changed
or not, the imported value will also be updated when the time interval
Period has elapsed since the last update (Period values less than 1 s
will give Period = 1 s). There is no point in using the same network
address in several DI blocks in the same FBD, because it would impose
an unneccessary load on network communications to have multiple
import declarations of the same signal. Only one block for each signal
should be used and connected to all blocks in the FBD that are using
the imported signal.
352 (450) TAC AB, Nov 2006

04-00030-01-en
Physical Input
Table 14.23:

Initial Value BINARY Initial block output value (Only I/O
module); On or Off. Default value = Off.
Normal BINARY Open or Closed. Open (NO): open input
Polarity contact interpreted as false (0); default.
Closed (NC): open input contact inter-
preted as true (1).
LED Color BINARY Green or Red. Color of LED when acti-
(422A, 452A) vated.
LED Polarity BINARY Condition for LED activation;
(422A, 452A) Non-Inverted or Inverted.
Non-Inverted: Lighted when Closed
Inverted: Lighted when Open.
Output type BINARY
Access RO
Description
The Physical input configuration option reads the state of a digital
input and translates it into a Binary value.
The parameter, Mod Number, specifies the I/O module number (0 =
number of the input terminal (e.g. U1–U4, X1–X4).
Interpretation of the physical digital input state is defined by the Nor-
mal Polarity parameter. Normal Polarity = Open means that an open
input contact gives a block output value of 0 (false), and Normal
Polarity = Closed entails that an open input contact gives a block out-
put value of 1 (true). The initial block output value for an I/O module
block (before a signal value has been received from the I/O module) is
specified by the Initial Value parameter. If the I/O module goes offline,
the block output will keep the last value that was received from the I/O
module.
The TAC Xenta 422A and 452A have universal inputs that can be used
as digital inputs; their status are displayed using LED indicators. LED
Color determines the color (Green or Red) when the Universal Input
functioning as a Digital Input is activated. (If used for pulse counting,
only Green is possible.)
LED Polarity determines if the LED should be lit at closed contact
(Non-Inverted) or at open contact (Inverted).
TAC AB, Nov 2006 353 (450)

04-00030-01-en
Online Device
Table 14.24:
Parameters Device STRING Reference to supervised device

Address
BINARY Initial block output value; On or Off.
Output type BINARY
Access RO
Description
The Online Device option is used to monitor the communication status
of an I/O module or another device in the network. This can be used, for
instance, in applications where signals are imported from other devices
in the network, and where alternative actions must be taken if commu-
nication breaks down. The device name (or the I/O module number: 1,
2, etc.) is specified in the Device Address parameter, which is entered as
a character string. To monitor the communication status of a supervi-
sory TAC Vista system, use the LonWorks Network name as the device
name. Note that the Online Device check can only be used for I/O mod-
ules which are defined in the TAC Xenta device where the application is run-
ning.
The block output will be true (1) if the device referenced by Device
Address is online. Otherwise, the output will be false (0). If Device
Address is the network address of the device itself, the block output will
be false (0) when no other node in the network can be found. Otherwise,
it will be true (1).
354 (450) TAC AB, Nov 2006

04-00030-01-en
SNVT
Table 14.25:

type is selected).
Name STRING Network identifier for the signal, max.
16 characters.
Initial Value BINARY Initial output value. Default value =
Off.
Poll BINARY Defines whether the bound external
output variable is to be polled or not.
Output type BINARY
Access RO
Description
The SNVT option is used to import external signals into the application
program via the network. The input block must also be bound to an
external output variable of the same SNVT type via network manage-
ment software. Note that the signal can be given different names within
the application (the block name, e.g. StartButton) and on the network
(the SNVT Name, e.g. nvistartbutton).
Select Type and Member from the predefined lists of supported SNVT
types. For a Binary signal, SNVT_switch may be used.
received via the network) is specified by the Initial Value parameter.
In case of a communications error, the block output will not be updated,
i.e. it will keep the last signal value that was received via the network.
After external binding, the external output variable will be polled if Poll
is checked and no updates arrive within Period.
Constant Value
Table 14.26:
Parameters Initial Value BINARY Initial block output value; On or Off.

TAC AB, Nov 2006 355 (450)

04-00030-01-en
Table 14.26:
Output type BINARY

Access RO
Description
This input block is not connected to an external physical or network
address. Instead the option assigns a constant value specified by the
Initial Value parameter to the block output.
14.15 DO – Digital Output
Fig. 14.21:
The DO block has three different sets of parameters depending on the
• Physical output
• SNVT
• Not connected
Physical Digital Output
Tabell 5:
Inputs Input BINARY Block input signal

Initial Value BINARY Initial output value (Only I/O module).
output
Access RO
Description
This block sets the state of a physical digital output.
number of the output terminal (e.g. K1–K4).
356 (450) TAC AB, Nov 2006

04-00030-01-en
The Initial Value parameter specifies the output signal value for an I/O
module block when the I/O module goes offline, e.g. following a
restart immediately after a power outage.
SNVT
Table 14.27:

type is selected).
16 characters.
Initial Value BINARY Initial output value. Default value =
Off
Send BINARY Defines whether the bound external
input variable is to be automatically
updated or not.
between two updates of the exported
output
Access RO
Description
This SNVT option is used to export signals from the application pro-
gram via the network to an external device. The output block must also
be bound to an external input variable of the same SNVT type via net-
work management software. Note that the signal can be given different
names within the application (the block name, e.g. StartButton) and on
the network (the SNVT Name, e.g. nvostartbutton).
Select Type and Member from the predefined lists of supported SNVT
types. For a Binary signal SNVT_switch may be used.
The initial output value (before the first program cycle is executed) is
specified by the Initial Value parameter.
If Send is checked, the external variable will be updated each time the
block input signal changes its state. Regardless of whether the input sig-
nal has changed or not, the external variable will be updated when the
time interval Period has elapsed since the last update. If Period is set to
0, the external variable will only be updated on status changes.
TAC AB, Nov 2006 357 (450)

04-00030-01-en
If Send is not checked, the external device will have to poll to get
updated signal values.
Not Connected
14.16 DOPU – Digital Pulse Output
Fig. 14.22:
The DOPU block can, via the I/O Configuration option be bound as
either Digital pulse output (Physical output) or Not connected.
Digital Pulse Output
Table 14.28:
Inputs Input REAL Pulse length (sec).

Min Pulse REAL Minimum output pulse length (sec).

Default = 0.5 sec.
Default value = 0 sec.
output
Access RO
Description
This block activates a pulse on a physical digital output. The output
pulse length is given by the block input signal value (in seconds). The
DOPU block is designed to be used together with the increase/decrease
PID block (PIDI). Negative block input values are ignored.
number of the output terminal (e.g. K1–K4).
The Min Pulse parameter specifies the minimum output pulse length in
seconds. Input signals less than this value are accumulated for the next
358 (450) TAC AB, Nov 2006

04-00030-01-en
application program cycle. Input pulse lengths longer than the applica-
tion program cycle time are truncated to a length equal to the program
cycle.
The Initial Value parameter specifies the output signal value (in sec)
for an I/O module block when the I/O module goes offline, e.g. follow-
ing a restart immediately after a power failure.
Not Connected
14.17 ENTH – Enthalpy
Fig. 14.23:
Table 14.29:
Inputs Temperature REAL Dry-bulb temperature °C (ºF)

(T)
Humidity (H) REAL Relative humidity (%)
Output type REAL
Access RO
Description
The enthalpy, kJ/kg (BTU/pond) of moist air at normal atmospheric
pressure is calculated as a function of the dry-bulb temperature °C, (ºF)
and the relative humidity (%).
Note
TAC Xenta device, it is possible to get the ENTH block to use the SI
or I-P system of units for specified parameters.
The ENTH block will use the T input (temperature) in SI unit system
(metric) or I-P (inch-pound) unit system, depending on the national set-
ting of the Windows© operating system of the PC in which the applica-
tion is generated. Using the metric setting will produce a block where
TAC AB, Nov 2006 359 (450)

04-00030-01-en
the T input is in degrees Celsius, a US setting will produce a block

where the T input is in degrees Fahrenheit.
The above-mentioned setting will also determine the units for the calcu-
lated enthalpy. An SI (metric) setting will give the result in kJ/kg. An I-
P (inch-pound) setting will give a result in BTU/pound. The calculation
of enthalpy in each unit system differs, and cannot be converted from
one unit system to another.
Algorithm, SI measurement units
The water vapor saturation pressure over liquid water for the tempera-
ture range 0 to 200 °C is approximated by the following function:
pws(T) = exp(c8/T + c9 + c10*T + c11*T² + c12*T³ + c13*ln(T)) (6)
where
T= Absolute temperature (K),
pws = saturation pressure (Pa)
and
c8 = –5.8002206E+03;
c9 = 1.3914993E+00;
c10 = –4.8640239E-02;
c11 = 4.1764768E-05;
c12 = –1.4452093E-08;
c13 = 6.5459673+00;
The enthalpy of moist air at normal atmospheric pressure as a function
of the dry-bulb temperature and the relative humidity is then given by
the following equations:
pwsat = pws(t+273.15)
pw = Φ*pwsat/100)(24)
W= 0.62198*pw/(p-pw)(22)
h= t + W*(2501+1.805*t)(32)
where
pwsat = water vapor saturation pressure (Pa)
t = dry-bulb temperature (°C)
Φ = relative humidity (%)
pw = partial pressure of water vapor in moist air (Pa)
p= ambient pressure (101325 Pa)
W= humidity ratio, mass of water per unit mass of dry air
360 (450) TAC AB, Nov 2006

04-00030-01-en
h= enthalpy (kJ/kg)
Note
Reference: ASHRAE Handbook 2001 – Fundamentals SI System of
units. Chapter 6, Psychrometrics. The equation numbers within paren-
thesis refer to the corrsponding equations in the ASHRAE Handbook.
Algorithm, I-P measurement units

The water vapor saturation pressure over liquid water for the tempera-
ture range –80 to 300 °F is approximated by the following function:
pws(T) = exp(c8/T + c9 + c10*T + c11*T² + c12*T³ + c13*ln(T)) (6)
where
T= Absolute temperature (ºR),
pws = saturation pressure (psia)
and
c8 = –1.0440397E+04;
c9 = –1.1294650E+01;
c10 = –2.7022355E-02;
c11 = 1.2890360E-05;
c12 = –2.4780681E-09;
c13 = 6.5459673E+00;The enthalpy of moist air at normal atmospheric
pressure as a function of the dry-bulb temperature and the relative
humidity is then given by the following equations:
pwsat = pws(t+459.67)
pw = Φ*pwsat/100)(24)
W= 0.62198*pw/(p-pw)(22)
h= 0.240*t + W*(1061+0.444*t)(32)
where
pwsat = water vapor saturation pressure (psi)
t = dry-bulb temperature (°F)
Φ = relative humidity (%)
pw = partial pressure of water vapor in moist air (psi)
p= ambient pressure (101325 psi)
W= humidity ratio, mass of water per unit mass of dry air
TAC AB, Nov 2006 361 (450)

04-00030-01-en
h= enthalpy (kJ/kg)
Note
Reference: ASHRAE Handbook 2001 – Fundamentals I-P System of
units. Chapter 6, Psychrometrics. The equation numbers within paren-
thesis refer to the corrsponding equations in the ASHRAE Handbook.
14.18 ERR – System Error
Fig. 14.24:
Table 14.30:
Output type INTEGER

Access RO
Description
The output of this block is an Integer value where each bit represents
an internal signal or error from the system program (see the following
section). Each output bit will be set as long as the error condition
remains, or, in the case of a restart after a power failure, during the first
program cycle following the restart. The output value is zero when no
error conditions are set.
14.19 Error Codes

Table 14.31:
Bit No. Output Value Description

1 1 Restart after power failure
2 2 Integer underflow/overflow
3 4 CNT block overflow
4 8 RT block overflow
5 16 Mainloop overrun. The application
program cannot execute within the
specified cycle time
362 (450) TAC AB, Nov 2006

04-00030-01-en
Bit No. Output Value Description

6 32 At least one of the switches on one
of the I/O modules associated with
the application is in the position for
manually overriding (ON, OFF,
MAN) the output
7 64 OP logged in on yellow or red
access level (applicable from Xenta
system v3.51)
8 128
9 256 Dial-up modem line to TAC Xenta
device disabled
10 512 Update of a Network variable value
was not received within the set
Period
11 1024 There are tripped, unacknowledged,
priority 1 alarms in the alarm list
12 2048 One or several I/O modules offline
13 4096 I/O in forced mode
14 8192 There are tripped and unacknowl-
edged alarms in the alarm list
15 16384 There are tripped and not reset
alarms in the alarm list
Use only one ERR block in the application, otherwise the load on the
TAC Xenta device can be high.
14.20 FILT – First Order Filter
Fig. 14.25:
Table 14.32:
Inputs variable REAL Input signal
TAC AB, Nov 2006 363 (450)

04-00030-01-en
Table 14.32:
Parameters TimeConst REAL Time constant of the filter measured in

seconds
Output type REAL
Access R/W
Description
The function block is a discrete time first order software filter. The fil-
ter time constant is specified in seconds with the Time Const parameter.
The initial block output value is zero.
The filter algorithm is
1
y ( k ) = y ( k – 1 ) + ------------- ( u ( k ) – y ( k – 1 ) )
1+T ---
h
where y(k) and u(k) are the filtered and unfiltered values at time k,
respectively, h is the sampling interval (i.e. the application program
cycle time), and T is the filter time constant. If the time constant is less
than or equal to zero, no filtering is done. To obtain a good filter func-
tion, the time constant should be set significantly greater than the appli-
cation program cycle time.
This filter algorithm is based on a straightforward backward difference
approximation of the continuous time derivative operator. For further
details, please refer to, for instance, Åström and Wittenmark: “Com-
puter Controlled Systems – Theory and design”. Prentice-Hall, Engle-
wood Cliffs (1984).
14.21 HOUR – Hour
Fig. 14.26:
Table 14.33:
Output type INTEGER

Access RO
Description
Provides the current hour (0–23) according to the internal time clock.
364 (450) TAC AB, Nov 2006

04-00030-01-en
14.22 HYST – Binary Hysteresis
Fig. 14.27:
Table 14.34:

Parameters activate REAL threshold value of the input signal for
activation of the output.
deactivate REAL threshold value of the input signal for
deactivation of the output.
Output type REAL
Access RO
Description
This block implements a relay function with hysteresis.
When activate is greater than deactivate, the block has the following
function: If the output is false (0) and the input signal exceeds the acti-
vation threshold, the output will change to true (1). If the output is true
(1) and the input signal drops below the deactivation threshold, the out-
put will change to false (0). When the input signal is in the zone
between the two thresholds, the output will remain in its previous state.
Fig. 14.28:
When activate is less than deactivate, the block has the following func-
tion: If the output is true (1) and the input signal exceeds the deactiva-
tion threshold, the output will change to false (0). If the output is false
(0) and the input signal drops below the activation threshold, the output
TAC AB, Nov 2006 365 (450)

04-00030-01-en
will change to true (1). When the input signal is in the zone between the
two thresholds, the output will remain in its previous state.
Fig. 14.29:
14.23 INTEG – Integrator
Fig. 14.30:
Table 14.35:
Inputs Rate (r) REAL rate input variable
Reset (rs) BINARY reset input (1 = reset)

ResetValue REAL value assigned to the output when the
(rv) reset input is activated
Parameters InitValue REAL Initial integrator value
Output type REAL
Access R/W
Description
This block allows the integration of a rate or flow over time. The inte-
gral is computed as the sum of the rate multiplied by the time incre-
ment, i.e. by the program cycle time. The summation is done using
extended numerical precision to avoid underflow when the rate is
small.
The integrator output is set to InitValue at the initial state. When the
Reset input is activated, the integrator output is reset to a value speci-
fied by the ResetValue input signal. When the Reset input is deacti-
366 (450) TAC AB, Nov 2006

04-00030-01-en
vated, the integration is resumed starting from the last value of the
ResetValue input.
The upper and lower output limits are set by the maximum floating-
point number that can be represented in the controller.
14.24 LIMIT – High/Low Signal Limit
Fig. 14.31:
Table 14.36:
Inputs Input REAL input signal

Parameters MinValue REAL minimum value limit
MaxValue REAL maximum value limit
Output type REAL
Access RO
Description
The Input signal is limited to the range [MinValue, MaxValue].
14.25 MAX – Maximum Signal Selector
Fig. 14.32:
Table 14.37:
Inputs Input1 REAL first input signal

Input2 REAL second input signal
Output type REAL
TAC AB, Nov 2006 367 (450)

04-00030-01-en
Table 14.37:
Access RO
Description
The output of the MAX block is set to the maximum value of Input1
and Input2.
14.26 MIN – Minimum Signal Selector
Fig. 14.33:
Table 14.38:
Inputs Input1 REAL first input signal

Input2 REAL second input signal
Output type REAL
Access RO
Description
The output of the MIN block is set to the minimum value of Input1 and
Input2.
14.27 MINUTE – Minute
Fig. 14.34:
Table 14.39:
Output type INTEGER

Access RO
368 (450) TAC AB, Nov 2006

04-00030-01-en
Descriptipn
Provides the current minute (0–59), according to the internal time
clock.
14.28 MONTH – Month
Fig. 14.35:
Table 14.40:
Output type INTEGER

Access RO
Descriptipn
Provides the month of the year according to the internal time clock.
Month 1 corresponds to January and month 12 to December.
14.29 NCYC – Program Cycle Counter
Fig. 14.36:
Descriptipn
This block increments the output value by one unit each program cycle
if IniValue is less than Final, and decreases it if the opposite applies.
When the count reaches the final value, the counter restarts the count at
the initial value in the next cycle.
TAC AB, Nov 2006 369 (450)

04-00030-01-en
14.30 NOT – NOT Gate
Fig. 14.37:
Table 14.41:
Inputs State BINARY Input signal

Output type BINARY
Access RO
Description
This block inverts a Binary signal.
370 (450) TAC AB, Nov 2006

04-00030-01-en
14.31 OPT – Optimization
Fig. 14.38:
Inputs RoT REAL Room temperature ºC (ºF).
SP REAL Set point, i.e. the desired room temper-

ature during day time ºC (ºF).
OuT REAL Outdoor temperature ºC (ºF).
OpI BINARY Operation indication, i.e. an external

signal that is used for detecting
whether the controlled equipment is in
operation.
OpI = 0 => not in operation.
OpI = 1 => in operation.
TmL INTEGER Time left (minutes) until the plant goes

into operation. If TmL is negative,
OPT will interpret the size of TmL as
the time until the plant d shuts down.
Mode INTEGER Switch for media mode and disabling

optimisation.
Mode = 0 => heating.
Mode = 1 => cooling.
Mode = –1 => no optimisation.
Default = 0, i.e. heating.
TAC AB, Nov 2006 371 (450)

04-00030-01-en
Table 14.42:
Parameters AutoAdjust INTEGER Automatic adjustment switch.

AutoAdjust = 0 => no adjustment.
AutoAdjust = 1 => adjustment of curve points.
AutoAdjust = 2 => adjustment of curve points
and holiday compensation.
Default = 2.
RoomTempF BINARY Room sensor flag.
RoomTempF = 0 => Sensor not present.
RoomTempF = 1 => Sensor present.
Default = 1, i.e. sensor present.
OperIndicF BINARY Flag for selecting whether external operation
indication is present.
OperIndicF = 0 => Not present.
OperIndicF = 1 => Present.
Default = 0, i.e. not present.
StartTimeLo REAL Start-time (minutes) at low outdoor tempera-
ture-10 °C (14ºF), 10 °C (50 ºF).
Default = 105.
StartTimeHi REAL Start-time (minutes) at high outdoor tempera-
ture 10 °C (50 ºF), 30 °C (86ºF).
Default = 45.
Holiday- REAL Holiday compensation ( %) when the plant has
Comp been shut down > 48 h.
Default = 0.
MaxStartTi REAL Max start-time (hours).
Default = 12.
ETol REAL Temperature error when switching from opti-
misation to normal operation.
Default = 0.5.
StopLoTemp REAL Low outdoor temperature point in stop-time
optimisation °C (ºF).
Default = –10.
StopTimeLo REAL Stop-time (minutes) when outdoor tempera-
ture = StopLoTemp.
Default = 0.
StopHiTemp REAL High outdoor temperature point in stop-time
optimisation °C(ºF).
Default = 10.
StopTimeHi REAL Stop-time (minutes) when outdoor tempera-
ture = StopHiTemp.
Default = 0.
372 (450) TAC AB, Nov 2006

04-00030-01-en
Table 14.42:
Output type INTEGER

Access R/W
Description
General
OPT provides optimum start and stop. OPT may be used in heating as
well as cooling applications. It is executed as often as the other function
blocks in the same application. However, the main part of the algorithm
is only executed once every minute. The purpose of the start-time opti-
misation is to start the heating/cooling system in advance in order to
obtain the correct temperature at the beginning of normal operation. The
purpose of the optimum stop is to shut down the heating/cooling system
before the end of normal operation, without the temperature falling out-
side the given limits during normal operation.
The optimisation function may be blocked by setting the parameter
Mode = –1. The output of OPT will then follow the time schedule status,
i.e. the output = 0 when TmL >0, and output = 1 when TmL < 0. Curve
points and HolidayComp will not be adjusted when Mode = –1.
Note
If you are using TAC Menta version 4.0 and system version 3.5 for
TAC Xenta devices, it will be possible to get the OPT block to use the
SI or I-P system of units for specified parameters.
The block will use the RoT, SP, and OuT inputs in the SI unit system
(metric) or I-P (inch-pound) unit system, depending on the national set-
ting of the Windows© operating system of the PC in which the applica-
tion is generated. Using the metric setting will produce a block where
the inputs are in degrees Celsius, and a US setting will produce a block
where the inputs are in degrees Fahrenheit.
The block parameters StartTimeLo, StartTimeHi, defines parts of coor-
dinates for breakpoints which are using fixed temperatures of –10 ºC
(14 ºF), 10 ºC (50 ºF), and 30 ºC (86 ºF). Entering values for the start
times completes definition of the coordinates.
Start-Time Optimization
The start-time is calculated once every minute on condition that TmL >
0 and optimisation has not already started. If the calculated start-time is
longer than the time left until the plant goes into normal operation, the
output of OPT will be set to 2 (optimisation state).
When the room temperature has reached the set point (SP) minus an
adjustable tolerance, ETol (default = 0.5 °C), the output of the function
block is set to 1 (normal operation) in order to indicate that the start-time
optimisation is completed and that normal operation may begin. If the
TAC AB, Nov 2006 373 (450)

04-00030-01-en
room temperature has not reached the temperature required for normal
operation to be set, before TmL turns negative, the output will be set to
1 at this point. During cooling, the output is instead set to 1 when the
room temperature falls below the set point (SP), plus the same tolerance
(ETol). The principle of start-time optimisation is illustrated in Figure
1. Note that we have assumed in the figure that the correct temperature
is reached at the same time as TmL turns negative.
The start-time is obtained from a curve that defines the relationship
between the outdoor temperature (OuT) and the start-time. If a room
sensor is not used, the start-time will be calculated directly from the
curve with a possible contribution from holiday compensation, see
below. When a room sensor is connected, the curve instead yields the
start-time per °C of deviation between the room temperature (RoT) and
its set point (SP). For example, the start-time will be 120 min if the
curve yields the value 60 min at the outdoor temperature in question and
the room temperature is 2 °C too low.
Fig. 14.39: Principle for start-time optimisation.

To obtain a correct start-time after longer shut-down periods, e.g. after
holidays or weekends, an extra contribution may be added to the start-
time. Holiday compensation will contribute to the start-time when the
building has not been in use for a long period, see Holiday compensa-
tion (Monday effect) on the next page. If the parameter OperIndicF is
set to 1, OPT will use the input OpI to decide whether the plant is in
operation. If OperIndicF is set to 0, OPT will ignore the input OpI and
instead assume that the plant is in operation if the output of OPT is 1
(normal operation) or 2 (optimisation state).
Finally, the start-time is limited to a maximum value (MaxStartTi).
OPT Output Values
374 (450) TAC AB, Nov 2006

04-00030-01-en
As described above and in Figure 1, the OPT block output value is used
to set the plant's operating mode, as described in the table below:
• Output = 0 => Off.
• Output = 1 => Normal operation.
• Output = 2 => Optimisation state.
Curve, Start-Time as a Function of Outdoor Temperature
The curve that describes the relationship between the outdoor tempera-
ture and the start-time, or alternatively the start-time per °C of room
deviation if the room sensor is connected, is defined by two points, see
Fig. 2. The outdoor temperature at these points will be defined by the
selection of the Mode (cooling or heating), while the corresponding
start-times (StartTimeLo and StartTimeHi) are freely selectable. The
outdoor temperatures of the curve points are –10 °C and 10 °C during
heating, respectively 10 °C and 30 °C during cooling. The default val-
ues for the start-times are 105 minutes (StartTimeLo) and 45 minutes
(StartTimeHi). The start-times at the curve points may be adjusted auto-
matically, see below.
Fig. 14.40: Curve describing the relationship between outdoor

temperature and start-time. The figure shows the default-curve during
heating.
Automatic Adjustment of Curve Points
To be able to adjust the curve to the thermal properties of a specific
building, there is a mechanism for automatically adjusting the curve
points. If the desired room temperature has not been reached when the
optimisation time expires (or, if it is reached too early), the adjustment
mechanism will compute an estimate of the optimisation time that
should have been used and will adjust the curve points accordingly.
Automatic adjustment of the curve points may only, of course, be used
in systems with a room sensor.
Adjustment of the curve points is performed when normal operation
begins following an optimisation phase. It is also necessary that adjust-
ment has been selected (AutoAdjust >0). Adjustment of the curve points
TAC AB, Nov 2006 375 (450)

04-00030-01-en
will not be performed when the plant has been shut down for more than
20 hours.
It is possible at any time to alter the start-times in the curve points via
the Operators Interface. If this is done while optimisation is active, no
adjustment of the curve points will be performed when normal opera-
tion begins following this optimisation phase (after the next optimisa-
tion phase, the adjustment mechanism will work as normal again).
Holiday Compensation (Monday Effect)
When the building has been shut down for a long period of time, a
longer heating time is required to reach the desired temperature, due to
the fact that the building has been cooled down more effectively. To
compensate for this, we add an extra percentage of the start-time calcu-
lated above when the plant has been shut down for more than 20 hours,
see Fig. 3. 48 hours after shut down, the extra contribution is at maxi-
mum (HolidayComp), since we then assume that the building has
reached a stationary state, i.e. it will not get any colder even if the shut
down lasts longer. The percentage is increased linearly from 0 % at 20
h of shut down time to HolidayComp % at 48 h of shut down time.
Fig. 14.41: Curve describing the relationship between holiday

compensation and shut down time. HolidayComp is assumed to be 30%
in the figure.
It should be noted that the influence of holiday compensation is more
important in systems without a room sensor. The reason for this is that
systems with a room sensor will automatically start earlier following a
longer shut down, since the temperature in the room will in general have
fallen more than during a normal shut down.
Automatic Adjustment of Holiday Compensation
The adjustment of holiday compensation is performed when normal
operation begins following an optimisation phase, on the condition that
the plant has been shut down for more than 30 h. A necessary precondi-
tion is that adjustment has been selected (AutoAdjust = 2). It should be
noted that the curve points and HolidayComp are never adjusted simul-
taneously following an optimisation phase. The curve points may only
376 (450) TAC AB, Nov 2006

04-00030-01-en
be adjusted if the plant has been shut down for less than 20 hours while
HolidayComp may only be adjusted if the plant has been shut down for
more than 30 hours. This also means that no adjustment at all will be
performed if the shut down time is between 20 h and 30 h.
Stop-Time Optimization
The reason for using stop time optimisation is saving energy by stop-
ping heating/cooling before the end of the occupancy time. It is of
course important that the room temperature does not fall outside an
acceptable temperature range during the occupancy time. Since the stop
time that may be used without the temperature falling outside the
acceptable temperature range depends on the room temperature, opti-
mised stop is normally only used in systems with a room sensor. The
stop time is obtained from a curve that describes the relationship
between outdoor temperature and stop-time. The curve gives the stop-
time per °C of deviation between the room temperature and the lowest
permissible temperature in the room at the end of normal operation,
when a room sensor is used. The lowest permissible temperature is set
to the set point (SP) minus StopTimeErr during heating. StopTimeErr is
by default = 0.5 °C. During cooling, the highest permissible room tem-
perature in the room at the end of normal operation is set to the set point
plus StopTimeErr. If a room sensor is not used, the optimisation func-
tion will assume that the room temperature exceeds the set point by 1 °C
in heating operation and is 1 °C below the set point during cooling, cf.
start-time optimisation. Both x (StopLoTemp and StopHiTemp) and y-
values (StopTimeLo and StopTimeHi) for both curve points are freely
selectable. The default values are (-10 °C, 0 min) and (10 °C, 0 min)
respectively. This implies that stop-time optimisation will not have any
effect before these parameters are changed. The reason for this is that
stop time optimisation is used relatively seldom.
Fig. 14.42: Curve describing the relationship between outdoor

temperature and stop-time. The curve does not illustrate default values
conditions.
TAC AB, Nov 2006 377 (450)

04-00030-01-en
14.32 OR – OR Gate
Fig. 14.43:
Table 14.43:
Inputs state1 BINARY Input signal 1

state2 BINARY Input signal 2
Output type BINARY
Access RO
Descriptipn
Calculates the boolean OR function of state1 and state2, according to
the following truth table:
Table 14.44:
state 1 state 2 output

0 0 0
0 1 1
1 0 1
1 1 1
378 (450) TAC AB, Nov 2006

04-00030-01-en
14.33 OSC – Oscillator
Fig. 14.44:
Table 14.45:
Parameters CycleTime REAL Oscillation period (seconds)

PulseTime REAL Pulse duration (seconds)
Output type BINARY
Access RO
Description
This block generates a train of pulses of duration PulseTime and a
period of CycleTime.
The train of pulses is always a multiple of the program cycle time, e.g.
if CycleTime is 7.4 seconds and PulseTime is 5.2 seconds and the cycle
time is 1 second, a 6 second pulse will fire every eight seconds.
TAC AB, Nov 2006 379 (450)

04-00030-01-en
14.34 PIDA – PID Controller – Analog Output
Fig. 14.45:
Table 14.46:
Inputs MV REAL Measured value.

SP REAL Set point.
Mode INTEGER Controller operating mode.
G REAL Proportional gain.
Ti REAL Integral time (sec).
Td REAL Derivative time (sec).
DZ REAL Dead zone
TSg REAL Tracking signal (actual value of the
previous control signal).
Parameters ControlInt REAL Control interval (sec)
UMin REAL Minimum permissible control signal.
UMax REAL Maximum permissible control signal
StrokeTime REAL Actuator full stroke travel time (sec)

Output type REAL
Access R/W
380 (450) TAC AB, Nov 2006

04-00030-01-en
Description
Control Algorithm
The PIDA block is designed to be used in control loops where the con-
troller output is either connected to an analog physical output or used
as a set point for another control loop (cascade control). The control
algorithm is a discrete tim- incremental PID algorithm, where the
change in control signal du(t) is calculated as
h y ( t ) – 2 • y ( t – h ) + y ( t – 2h )
du ( t ) = G ⋅ ⎛ e ( t ) – e ( t – h ) + ----- ⋅ e ( t ) – Td • ------------------------------------------------------------------------⎞
⎝ Ti h ⎠
where e is the control error, y is the measured value (MV), G is the con-
troller gain, Ti is the integral time, Td is the derivative time and h is the
control interval (ControlInt), i.e. the time between two successive
updates of the controller output signal. If ControlInt is set to 0, the con-
trol interval will automatically be set equal to the program cycle time.
Time index t represents the present value of a variable, t-h represents the
value at the previous evaluation of the control algorithm, and so on.
The PID-module is executed at the interval hx seconds, where hx sec-
onds is the application program execution interval, even if the selected
control interval is longer. The control interval, h, must be a multiple of
hx. If this is not the case, the PID algorithm will automatically select the
closest multiple smaller than h as the control interval. By default the
control interval is set equal to 1.
The control error e is defined as e = SP – MV. Thus, if the measured
value is below the set point and the gain G is positive, the controller out-
put will increase (heating control). With a negative G value, the control-
ler output will decrease instead (cooling control). When the control
error is smaller than the dead zone, i.e. abs(e) < DZ, the change in the
control output, du(t), is set to zero. The dead zone is given in the same
units as the measurement value and the set point.
The controller output signal is calculated as
(2) u ( t ) = u ( t – h ) + du ( t )
where u(t) is the present control signal and u(t–h) is the previous value
of the control signal. The value of u(t–h) is taken from the input TSg,
which represents the actual value of the previous control signal, taking
into account any external limitations and/or override functions in the
application program. Normally, the TSg input would be connected
directly to the controller output.
The proportional band corresponding to a certain proportional gain
value G can be calculated as
U M ax – UMin
(3) Pband = ------------------------------------
G
P and PD Controller
TAC AB, Nov 2006 381 (450)

04-00030-01-en
The algorithm described above is used when the controller has integral
action. If a controller without I- or D-action is desired, Ti or Td respec-
tively will be set to 0. In accordance with this, a PI-controller is obtained
by setting Ti ### 0 and Td = 0. If the gain G is set to 0, the program will
not fail to execute, but the control signal will not change, regardless of
the size of the error.
If the incremental control algorithm in equation (1) is used without inte-
gral action, an arbitrarily large stationary error may be obtained which
will not necessarily decrease if the controller gain is increased. For this
reason, we use a special algorithm for P and PD control, where the con-
trol signal is calculated according to eq. (4):
y ( t ) – y ( t – h ) -) + (------------------------------------------
( 4 ) u ( t ) = G ⋅ e ( t ) – Td ⋅ (-------------------------------------- UMax + UMin )-
h h
where UMax is the biggest permissible control signal and UMin is the
smallest permissible control signal.
Limitation of the Control Signal
The maximum rate of change of the controller output during one control
interval, DuMax, depends on the actuator stroke time and can be calcu-
lated as
( Umax – UMin ) ⋅ h
(5) DuMax = -------------------------------------------------
StrokeTime
The calculated change in the control output, du(t), is limited to the range
±DuMax before the absolute level of the control signal is calculated.
The calculated new control signal u(t) is limited to the interval (UMin,
UMax). If UMin and/or UMax are not defined, the corresponding limi-
tation will not be performed. The parameters UMin and UMax should
be given in engineering units. Default values are 0 and 100 (%), respec-
tively.
The parameter StrokeTime is used to define the actual full stroke travel
time of the actuator. Note that StrokeTime may be used to limit the
change of the control signal even if the output is not connected to an
actuator. The StrokeTime is then the minimum permissible time for the
control signal to change from UMin to UMax. If the controller output is
used as a set point for another controller and there is no special reason
for limiting the change in the control signal, StrokeTime should be set
to 0.
Operating Mode
The controller operating mode depends on the input signal Mode, as
described in the table below:
• Mode = 0 => Off, controller stopped (du = 0)
• Mode = 1 => Normal control.
• Mode = 2 => Controller output forced to UMax.
• Mode = 3 => Controller output forced to UMin.
382 (450) TAC AB, Nov 2006

04-00030-01-en
If Mode = 0, the controller output will track the signal on the tracking
signal (TSg) input. If Mode < 0 or Mode > 3, the controller operating
mode will be Off (same as Mode = 0).
14.35 PIDI – PID Controller – Incremental Output
Fig. 14.46:
Table 14.47:

SP REAL Set point.
DZ REAL Dead zone
Parameters ControlInt REAL Control interval (sec)
Output type REAL
Access R/W
Description
Control Algorithm
The PIDI block is designed to be used together with two digital pulse
output (DOPU) blocks in control loops with increase/decrease actua-
tors. The control algorithm is a discrete time incremental PID algo-
rithm, where the calculated change (increment) in the control signal is
TAC AB, Nov 2006 383 (450)

04-00030-01-en
converted to the corresponding travel time of the actuator. The change

in the control signal du(t) is calculated using the same formula as in the
PIDA block (cf. equation (1) in the PIDA block description).
The calculated change in the control signal, du(t), is converted to the
corresponding actuator travel time dt (in seconds) using the following
equation:
du ( % )
(2) dt = ---------------- ⋅ StrokeTime
100%
where StrokeTime is the full stroke actuator travel time (in seconds).
Note that it is assumed that StrokeTime corresponds to a 100% change
in the actuator position. The PIDI block output is the computed dt value.
If StrokeTime is set to 0, a stroke time of 60 seconds will automatically
be used.
If ControlInt is set to 0, the control interval will automatically be set
equal to the application program cycle time. However, if the ControlInt
is longer than the cycle time (hx), we will have to take into consideration
that the DOPU block cannot be active more than hx seconds before a
new output from the PIDI block is calculated. This means that the out-
put time dt, calculated in equation (2), has to be propagated in pieces
that are not longer than hx.
Example: if ControlInt = 10 s, hx = 1 s and dt = 5.5 s, the output from
the PIDI block will be 1 s for 5 cycles, then 0.5 s during the sixth cycle
and finally 0 s during the following 4 cycles, until it is time to calculate
dt again.
The proportional band corresponding to a certain proportional gain
value can be calculated as
100%
(3) Pband = --------------
G
P- and PD Control
A controller with an incremental output does not work very well with-
out I-action. Arbitrarily large steady state errors may be obtained, which
do not necessarily decrease when the controller gain is increased. For
this reason, a controller with an incremental output without I-action
should not be used. However, if a controller without I or D-action is
desired, Ti or Td respectively will be to 0. In accordance with this, a PI-
controller is obtained by setting Ti ### 0 and Td = 0. If the gain G is set
to 0, the program will not fail to execute, but the control signal will not
change, regardless of the size of the error.
The calculated travel time is limited to the range ±ControlInt (sec),
since that is the maximum amount of actuator travel time that can be
obtained during one control interval.
Operating Mode
384 (450) TAC AB, Nov 2006

04-00030-01-en

• Mode = 0 => Off, controller stopped (dt = 0)
• Mode = 1 => Normal control.
• Mode = 2 => Actuator forced to max (dt = ControlInt sec).
• Mode = 3 => Actuator forced to min, (dt = –ControlInt sec).
Note that when Mode = 2 or 3, the travel time is set to the smallest value
that makes the actuator move constantly in the desired direction. If
Mode < 0 or Mode > 3, the controller operating mode will be Off (same
as Mode = 0).
14.36 PIDP – PID Controller – Analog Output
PIDP
MV
Control Int
SP
Mode UMin
G
UMax
Ti
Td Stroke Time
DZ
TSg
Fig. 14.47:
TAC AB, Nov 2006 385 (450)

04-00030-01-en
Table 14.48:

SP REAL Set point.
DZ REAL Dead zone
TSg REAL Tracking signal (actual value of the
previous control signal).
PARAMETERS ControlInt REAL Control interval (sec)
UMin REAL Minimum permissible control signal.
UMax REAL Maximum permissible control signal
OUTPUT TYPE REAL
ACCESS R/W
Description
Control Algorithm
The PIDP block is designed to be used in control loops where the con-
troller output is either connected to an analog physical output or used as
a set point for another control loop (cascade control).
The control algorithm is a discrete time positional PID algorithm, where
the output signal U(k) is calculated according to the diagram below.
386 (450) TAC AB, Nov 2006

04-00030-01-en
Fig. 14.48: PIDP Block diagram
Here SP is the setpoint value, MV is the measured value, G is the con-

troller gain, Ti is the integral time, Td is the derivative time and h is the
control interval (Control Int), i.e. the time between two successive
updates of the controller output signal. If Control Int is set to 0, the con-
trol interval will automatically be set equal to the program cycle time.
Time index k represents the present value of a variable, k-1 represents
the value at the previous evaluation of the control algorithm, and so on.
The PID-module is executed at the interval hx seconds, where hx sec-
onds is the application program execution interval, even if the selected
control interval is longer. The control interval, h, must be a multiple of
hx. If this is not the case, the PID algorithm will automatically select the
closest multiple smaller than h as the control interval. By default the
control interval is set equal to 1.
When the control error is smaller than the dead zone, i.e. abs(e) < DZ,
the control signal is set to the same value as the previous output, that is,
the output is not changed. The dead zone is given in the same units as
the measurement value and the set point.
Other Controller Types
The algorithm described above can be used for all types of controllers.
At PI or PID control the P-part does not depend on the difference
TAC AB, Nov 2006 387 (450)

04-00030-01-en
between the setpoint and the measured value, but only on the measured
value, MV.
If P or PD control is used, the P-part will automatically be changed to
depend on the error (SP-MV). When these controllers are used, an offset
value is also added to the output signal:
( U max + U min )
Offset = --------------------------------------
-
2
where Umax is the biggest permissible control signal and Umin is the
smallest permissible control signal.
If a controller without I- or D-action is desired, Ti or Td respectively is
set to 0. In accordance with this a PI-controller is obtained by setting
Ti > 0 and Td = 0. If the gain G is set to 0, the program will not fail to
execute, but the control signal will not change regardless of the size of
error.
Please note that when any of the G, Ti and Td parameters have been
changed, an automatic internal update of the controller is performed. No
measures have to be taken in the application to avoid bumps in the con-
trol signal.
The parameter StrokeTime is used to define the actual full stroke travel
time of the actuator. Note that StrokeTime may be used to limit the
change of the control signal even if the output is not connected to an
actuator.
If the controller output is used as a set point for another controller and
there is no special reason for limiting the change in the control signal,
StrokeTime should be set to 0, which is also the default value.
The maximum rate of change of the controller output during one control
interval, DuMax, depends on the actuator stroke time and can be calcu-
lated as
( U max – U min ) × h
DuMax = ------------------------------------------------
StrokeTime
This corresponds to the maximum change in two successive output sig-

nals from the PIDP block.
The calculated new control signal u(t) is limited to the interval (Umin ,
Umax). The parameters UMin and UMax should be given in engineering
units. Default values are 0 and 100 (%), respectively.
Operating Mode
388 (450) TAC AB, Nov 2006

04-00030-01-en
Mode = 0 => Off, controller stopped

Mode = 1 => Normal control.
Mode = 2 => Controller output forced to UMax.
Mode = 3 => Controller output forced to UMin.
If Mode = 0, the controller output will track the signal on the tracking
signal (TSg) input. If Mode < 0 or Mode > 3, the controller operating
mode will be Off (same as Mode = 0).
14.37 POLY – Polynomial Function
Fig. 14.49:
Table 14.49:
Inputs variable REAL

Parameters list of coeffi- REAL List of polynomial coefficients a0, …,
cients an
Output type REAL
Access RO
Description
This block calculates the polynomial function defined by the expres-
sion:
p ( x ) = a n ⋅ x n + a n – 1 ⋅ x n – 1 + .....+a 1 ⋅ x + a 0
The order of the polynomial (n) is equal to the number of coefficients

minus one, and this is indicated in the graphical function block symbol.
The maximum number of coefficients is 255.
The polynomial value p(x) is calculated using an algorithm known as
Horner's scheme [Reference: Fröberg, Carl-Erik: “Numerical Mathe-
matics – Theory and Computer Applications”, Addison-Wesley (1985)]
to improve the numerical accuracy and reduce the number of floating
TAC AB, Nov 2006 389 (450)

04-00030-01-en
point operations. The algorithm can be described using the following

equations, where p(x) = bn:
b0 = an
b1 = b 0 ⋅ x + an – 1
b2 = b 1 ⋅ x + an – 2
....
bn = bn – 1 ⋅ x + a0
14.38 PRCNT – Percentage
Fig. 14.50:
Table 14.50:

Parameters value0% REAL value of the input variable for 0% at
the output
value100% REAL value of the input variable for 100% at
the output
Output type REAL
Access RO
Description
Performs a simple linear transformation of the input signal applying
the conversion:
output = 100 * (variable – value0% ) / (value100%-value0%)
The output value is always limited to be between 0 and 100.
390 (450) TAC AB, Nov 2006

04-00030-01-en
14.39 PULSE – Pulse Generator
Fig. 14.51:
Table 14.51:
Inputs Trig (t) BINARY Trigger signal

PulseLength REAL Duration of output pulse (seconds)
(pl)
Output type BINARY
Access RO
Description
A function block with a mono-stable Binary output of variable pulse
length (pulse generator). The pulse length (in seconds) is given by the
input signal PulseLength. The PULSE block only has one stable output
state (0). When the input signal Trig switches from 0 to 1, the output
switches to the unstable state (1) and remains in this state for Pulse-
Length seconds, after which it returns to 0. The output pulse is trig-
gered by the transition of the input signal, from zero to one, and not on
its state. Thus, the output pulse length is independent of the duration of
the trig input pulse length.
Fig. 14.52:
The output pulse length is always a multiple of the program cycle time
e.g. if the PulseLength input is set to 5.2 seconds and the cycle time is
1 second, the output pulse duration will be 6 seconds.
TAC AB, Nov 2006 391 (450)

04-00030-01-en
14.40 PVB – Binary Value Parameter
Fig. 14.53:
Table 14.52:
Parameters InitValue BINARY Initial output state

Output type BINARY
Access R/W
Description
This block is used to assign a user-selectable Binary parameter value to
the input signal of another block. To be accessible from the OP or via
the network, the parameter block output must be declared as Public.
The initial state of the output is determined by the InitValue parameter.
If the output signal is not public, this block will act as a constant
parameter value for another block input, since it is never modified dur-
ing execution of the application program.
14.41 PVI – Integer Value Parameter
Fig. 14.54:
Table 14.53:
Parameters InitValue INTEGER Initial value of the output signal.

Output type INTEGER
Access R/W
Description
This block is used to assign a user selectable Integer parameter value to
392 (450) TAC AB, Nov 2006

04-00030-01-en

The initial value of the output is determined by the InitValue parameter.
PVI – XENTASYSREG
A special variant of the PVI is available (starting with TAC Xenta sys-
tem program v 3.61), adding three new functions. These are activated
by setting one or several of the three least significant bits in the
InitValue of a public PVI block named XENTASYSREG.
• Menu tree without 30 minute reset – Normally the menu tree in the
OP panel is reset to display the root Menu root after 30 minutes.
By activating this option, the OP panel will not be reset to display
the Menu root after 30 minutes.
• Australian daylight saving time option — This will adjust the day-
light saving time according to Australian conditions, which are the
reverse of European conditions.
• For TAC Xenta 401 the normal propagation speed of two SNVTs
per second can be increased to 15 SNVTs/second.
Note
To be able to activate these functions, version 3.61 (or higher) of the
system program and the OP Panel program is required.
To activate one or more of these functions, the PVI block should be

given the name “XENTASYSREG”. The bits will be set if one or sev-
eral of the following non-zero values are added and assigned to the
InitValue of the “XENTASYSREG” PVI block:
Value = 0.None of the functions are active.
Value = 1.Menu tree without 30 minute reset is activated.
Value = 2.Australian daylight saving time option is activated.
Value = 4.Fast SNVT propagation: up to 15 SNVTs/sec.
Note! This is allowed only in TAC Xenta 401!
Example: InitValue=5 will activate Menu tree without reset and Fast
SNVT propagation.
TAC AB, Nov 2006 393 (450)

04-00030-01-en
14.42 PVR – Real Value Parameter
Fig. 14.55:
Table 14.54:
Parameters InitValue REAL Initial value of the output.

Output type REAL
Access R/W
Description
This block is used to assign a user selectable Real parameter value to
The initial value of the output is determined by the InitValue parameter.
14.43 RAMP – Ramp Filter
Fig. 14.56:
Table 14.55:

Parameters increment REAL maximum increment in the signal per
second.
Output type REAL
Access R/W
394 (450) TAC AB, Nov 2006

04-00030-01-en
Description
This filter acts as a rate limit, i.e. it limits the rate of change of the input
variable. The maximum increment in the output signal per second is
given by the parameter increment. The sign of the increment parameter
is ignored, the absolute value is used as a rate limit.
14.44 RST – Restart
Fig. 14.57:
Table 14.56:
Output type BINARY

Access RO
Description
The output is activated during first program cycle following a warm
start.
14.45 RT – Run-Time Measurement
Fig. 14.58:
Table 14.57:
Inputs RunIndica- BINARY Running indication to be measured

tion (i)
Reset (rs) BINARY Reset input (1 = reset)
Parameters Unit INTEGER Output time unit (0 = hours, 1 = min-
utes, 2 = seconds). Default value = 0
(hours)
Output type INTEGER
Access R/W
TAC AB, Nov 2006 395 (450)

04-00030-01-en
Description
This block is used to accumulate the period of time during which the
Binary signal RunIndication is activated (true). The output time unit
(hours, minutes or seconds) is selected using the Unit parameter. The
output and all internal block states are set to zero at the initial state or
when the Reset input is activated. When the Reset input is deactivated,
accumulation resumes.
When the output reaches the maximum Integer limit (32767), accumu-
lation stops, but the output is not reset to zero.
14.46 SECOND – Second
Fig. 14.59:
Table 14.58:
Output type INTEGER

Access RO
Description
Provides the current second (0-59), according to the internal time
clock.
Note
The output signal does not change its value during execution of the
application program module where it is being used. This is important
if longer cycle times than one second are used.
396 (450) TAC AB, Nov 2006

04-00030-01-en
14.47 SEQ – Sequencer
Fig. 14.60:
Table 14.59:
Inputs Input REAL Input signal (%)

Parameters Stages REAL Number of output stages (1 to 16).
Rotation BINARY Defines whether or not there is rotation
of the stages.
Period INTEGER Delay of simultaneous activation of the
stages in milliseconds.
Hysteresis REAL Width of the hysteresis (%).
Output type INTEGER
Access RO
Description
This block is used to start N of M stages, where M is the total number
of output stages as defined by the Stages parameter(up to a maximum
of 16) and N is the Integer part of the result of the following calcula-
tion:
( M + 1 ) ⋅ Input
N = --------------------------------------
100
where Input is a value between 0% and 100%. The M stages are repre-
sented by the first M bits of the Integer block output value. The first N
of these bits will be true (1) and the rest false (0).
Example: If Stages is 4, and neither Hysteresis nor Rotation is used,
stage one will start (Output = 1; 0001) at 20% Input signal, stage two
(Output = 3; 0011) at 40%, stage three (Output = 7; 0111) at 60% and
stage four (Output = 15; 1111) at 80%. Note that TAC Menta uses a
two-complement representation of signed integers, i.e. the output signal
for starting 16 stages would be –1 (1111111111111111).
TAC AB, Nov 2006 397 (450)

04-00030-01-en
If the Hysteresis parameter is zero, the previous formula will give the
number of activated stages as a function of the input signal. If Hystere-
sis has a non-zero value, a hysteresis loop will exist to the left or to the
right (depending on whether Hysteresis is a negative or a positive num-
ber) of the points calculated in the previous equation. In this case, the
activation values of the stages will be displaced with respect to the deac-
tivation values. For example, if we define a 4 stage sequencer, the stages
started according to the previous formula will be one stage at 20%, two
stages at 40%, three stages at 60% and four stages at 80%. If a positive
hysteresis is defined, e.g. equal to 10, activation of the stages will be dis-
placed to the right by 10%, i.e. activation of the stages will be produced
at 30%, 50%, 70% and 90%, but deactivation will be maintained at the
previous values.
On the other hand, if the hysteresis were negative, for example –15%,
deactivation would be displaced to the left and so, the stages would acti-
vate at 20%, 40%, 60% and 80% and deactivate at 5%, 25%, 45% and
65%.
Fig. 14.61:
The Period parameter is used to prevent two or more stages from being
activated simultaneously. If the value is non-zero, the stages will always
be activated sequentially with an interval equal to Period (millisec-
onds), even if the input were to vary sharply, obliging simultaneous
activation of the stages. However, if this value is zero, the stages may
be activated simultaneously.
The Rotation parameter determines whether the active stages should
rotate or not. The difference between Rotation = 1 (with rotation) and
Rotation = 0 (without rotation) is that, in the first case, the stages will
deactivate in the same order in which they activated, i.e. the stage which
has been active longest will always deactivate first, while in the second
case, the deactivation order is the opposite of the activation order. When
the sequencer is defined with rotation, it may be assumed that the time
during which each stage remains active will, in the long term, be
approximately the same for all stages.
398 (450) TAC AB, Nov 2006

04-00030-01-en
14.48 SHB – Sample and Hold Binary Value
Fig. 14.62:
Table 14.60:
Inputs state (d) BINARY Binary input signal.

control (c) BINARY control signal.
Parameters InitValue BINARY initial value of the input signal.
Output type BINARY
Access R/W
Description
This is a sample and hold function with the following transition table:
Table 14.61:
state (t) control (t) output (t+1)

0 0 output (t)
1 0 output (t)
0 1 0
1 1 1
TAC AB, Nov 2006 399 (450)

04-00030-01-en
The block will copy the input state to the output, if the control signal is
active. Whereas, if the control signal is inactive, the output will remain
in the same state.
Fig. 14.63:
14.49 SHI – Sample and Hold Integer Value
Fig. 14.64:
Table 14.62:
Inputs variable (D) INTEGER Analog input signal.

Parameters InitValue INTEGER initial value of the output.
Output type INTEGER
Access R/W
Description
This block functions in an identical manner to the DELI block while
the control input remains active; i.e. delaying the propagation of the
input signal for one program cycle. However, while the control signal
400 (450) TAC AB, Nov 2006

04-00030-01-en
remains inactive, the output retains the value of the input during the
last cycle when the control signal was active.
Fig. 14.65:
14.50 SHR – Sample and Hold Real Value
Fig. 14.66:
Table 14.63:
Inputs variable (D) NTEGER Analog input signal.

Parameters InitValue INTEGER initial value of the output.
Output type REAL
Access R/W
Description
This block functions in an identical manner to the DELR block while
the control input remains active; i.e. is delaying the propagation of the
input signal for one program cycle. However, while the control signal
TAC AB, Nov 2006 401 (450)

04-00030-01-en
remains inactive, the output retains the value of the input during the
last cycle when the control signal was active.
Fig. 14.67:
14.51 SR – Set-Reset Flip-Flop
Fig. 14.68:
Table 14.64:
Inputs Set (s) (D) BINARY activates the output state

Reset (r) BINARY deactivates the output state
Parameters InitValue BINARY initial value of the output signal
Output type BINARY
Access R/W
Description
The SR flip-flop is a bi-stable block with two inputs: set and reset.
Depending on the value of these inputs at any given moment, the output
402 (450) TAC AB, Nov 2006

04-00030-01-en
of the block will be given a value during the next program cycle in
accordance with the following transition table:
Table 14.65:
state (t reset (t) output (t+1)

0 0 output (t)
0 1 0
1 0 1
1 1 inverse (output(t))
Thus, the output at time t+1 will be equal to the input at time t if the two
inputs are inactive. If the two inputs are active, the output changes state
every program cycle. If only one of them is active, the output will be
activated or deactivated depending on whether the input variable set or
reset is active respectively.
Fig. 14.69:
TAC AB, Nov 2006 403 (450)

04-00030-01-en
14.52 STRIN – STR Input
Fig. 14.70:
Table 14.66:
Parameters Wall Module STRING Select name of the STR Wall module
defined in Device Configuration.
Reference STRING Select the relevant input signal from
the STR.
Application ENUM For temperature input signals: unit (°C
Value or °F) of value delivered to application.
Default value = °C.
Output type REAL Output signal to application.
Access RO
Description
The STRIN block handles an input from the STR wall module. Depend-
ing on how the STR is configured, different types of signals may be of
interest. An application may require several STRIN blocks from one
STR wall module.
The block output is updated only once during each application program
cycle, which implies that changes in the physical inputs, with a dura-
tion less than one program cycle, will not be noted by the application
program.
In the Edit block STRIN window Unit is used to determine which
temperature unit (when applicable) will be used for presentation in
TAC Vista.
The Analog input block transfers a signal from the STR Wall module to
the application.
In the Bind STR Input window the Wall Module parameter you spec-
ify the STR module.
Reference: Available input signals from the STR are:
• SpaceTemp (temperature, °C or °F)
• Setpoint (temperature, °C or °F)
• SetptOffset (temperature °C, °F; or °F, no offset)
404 (450) TAC AB, Nov 2006

04-00030-01-en
• OccManCmd (Manual occupancy command)

• AnalogValue (e.g. from a CO2 or RH sensor, 0-10V=0-100%;
occupancy sensor, <10%=closed, >25%=open)
• FanSpeedCmdValue (Fan speed 0 or 1-3)
• FanSpeedCmdState (Fan on/off)
The temperature unit delivered to the application is defined in the field
Application Value. The input block will produce a numeric value corre-
sponding to the selected unit.
The initial block output value for an STR block (before a signal value
has been received from the STR module) is specified by the parameter
Initial Value. If the STR module goes offline, the block output will keep
the last value that was received from the STR module.
14.53 STROUT – STR Output
Fig. 14.71:
Table 14.67:
Input Input REAL Input signal from application.

Parameters Wall Module STRING Select name of the STR Wall module
defined in Device Configuration.
Reference STRING Select the relevant output signal to the
STR Wall module.
output
Access RO
Description
The STROUT block handles an output to the STR Wall module.
Depending on how the STR is configured, different types of signals may
be of interest. An application may require several STROUT blocks.
In the Edit block STROUT window Unit is used to determine which
temperature unit (when applicable) will be sent from the application to
the Wall module and be used for presentation in TAC Vista.
TAC AB, Nov 2006 405 (450)

04-00030-01-en
The Analog output block transfers a signal from the application pro-
gram to the STR Wall module.
In the Bind STR Output window the Wall Module parameter specifies
the STR.
Reference: Available output signals to the STR are:
• SpaceTemp (temperature, °C or °F)
• UserLockout
• EffectSetpt (temperature, °C or °F)
• EffectOccup
• UnitStatus
• OutdoorTemp (temperature, °C or °F)
• SpaceRH
• SpaceCO2
• FanSpeedValue
• TempMinDelta (temperature, °C or °F)
• TempOffset (temperature, °C or °F)
• Resolution
• DispTimeout
• BackLightOn
• Options1
• Options2
• Options3
• SetpointLow (temperature, °C or °F)
• SetpointHigh (temperature, °C or °F)
The Initial Value parameter specifies the output signal value (in the rel-
evant engineering unit), which is transmitted to the STR by the base unit
at startup, e.g. following a restart immediately after a power outage.
406 (450) TAC AB, Nov 2006

04-00030-01-en
14.54 TCYC – Cycle Time
Fig. 14.72:
Table 14.68:
Output type REAL

Access RO
Description
Gives the duration in seconds of one program cycle as specified in the
Specification Table.
14.55 TRIG – Trigger
Fig. 14.73:
Table 14.69:
Inputs state BINARY trigger signal

Parameters mode INTEGER operation modes 1, 2 or 3
Output type BINARY
Access RO
Description
The trigger is a mono-stable one which fires when it detects a transition
in its input signal and generates a pulse which is equal to the duration
of one program cycle. Depending on the mode of operation selected,
the trigger may fire:
• Mode 0 and 1: on the low to high transitions.
• Mode 2: on the high to low transitions.
• Mode 3: on any transition.
TAC AB, Nov 2006 407 (450)

04-00030-01-en
The mode may be entered as an integer between 0 and 255, but any
mode higher than mode 3 will work as mode 3 e.g. the trigger will fire
on any transition.
14.56 TSCH – Time Schedule
Fig. 14.74:
Table 14.70:
Parameters Week charts, INTEGER Number of week charts

Max.
Holiday INTEGER Number of holiday charts
charts, Max.
Output type INTEGER
Access RO
Note
An application program for TAC Xenta 280 devices may only contain
one TSCH block.
Description
The time scheduling function is used to configure week charts to start
and stop, e.g. an AHU at different hours depending on the day of the
week. It is also possible to define date intervals (holidays) within
which the normal week charts would be overridden by different operat-
ing hours.
The TSCH block has a signed Integer output whose sign indicates the
time schedule status (negative = true, positive = false), and whose
value indicates the time left until the next status change (negative =
time in minutes to false, positive = time in minutes to true).
Note
Please note that the Backup check box only applies to the block output
status, i.e. the time left to the next status change. The week and holiday
chart settings are always saved in the controller's Flash memory
regardless of the Backup setting.
408 (450) TAC AB, Nov 2006

04-00030-01-en
The Week charts Max. parameter, defines the number of week charts in
the time schedule. Not all week charts need to be defined during the
application programming phase. The parameter is used to decide how
many week charts should be available in the TAC Xenta OP. Undefined
week charts may be defined using the OP at runtime.
The parameter Holiday charts, Max. defines the number of holiday
charts. Not all holiday charts need to be defined during the application
programming phase. The parameter is used to decide how many holiday
charts should be available in the TAC Xenta OP. Undefined holiday
charts may be defined using the OP at runtime.
The total number of Week and Holiday charts is only limited by the
available memory space in the TAC Xenta controller. But, as each
Week and Holiday chart uses a relatively large memory space, you
should carefully plan how you will use the Time schedules before
increasing the Max. parameter value.
Holiday charts can also be defined in TAC Vista via the central time
schedule function.
Example
Let’s assume that an AHU is to have the following operating hours:
08:00 – 12:00 and 13:00 – 17:30 Monday through Friday
09:00 – 14:00 Saturday
10:00 – 12:00 Sunday
On Christmas Eve, the AHU will be in operation between 15:00 and
16:00, if Christmas Eve is a Monday, Tuesday, Wednesday, Thursday
or Friday.
It should also be possible to define 2 extra holidays via the TAC Xenta
OP.
The time schedule definition would then be as follows:
Week charts, Max. = 4
Table 14.71:
Start time Stop time Weekdays

08:00 12:00 Mon, Tue, Wed, Thu, Fri
13:00 17:30 Mon, Tue, Wed, Thu, Fri
09:00 14:00 Sat
10:00 12:00 Sun
TAC AB, Nov 2006 409 (450)

04-00030-01-en
Holiday charts, Max. = 3:
Table 14.72:
Start Stop Start Stop

Weekdays
date date time time
*-12-24 *-12-24 15:00 16:00 Mon, Tue, Wed,
Thu, Fri
Note
Note 1: Wild cards in the start date and stop date fields of a holiday
chart makes it possible to define a certain day every year. Wild cards
are only allowed in holiday charts.
Note 2: It is permissible to enter the time 24:00. Operating hours of
00:00-24:00 mean that the controlled equipment will be on for a full
twenty-four hour period.
Note 3: It is permissible to define operating hours of 23:00-04:00
Mon. This means the controlled equipment will run from 23:00 to
24:00 for the defined weekday (Mon), and continue to run from 00:00
to 04:00 on the next weekday (Tue).
Note 4: 00:00-00:00 could be used in holiday definitions to turn the
controlled object off for a full twenty-four hour period. Operating
hours defined as 03:34-03:34 will be handled as 00:00-00:00, i.e. the
controlled equipment will be turned off.
14.57 VECTOR – Vectorial Curve Function
Fig. 14.75:
Table 14.73:
Inputs Input REAL Input signal
410 (450) TAC AB, Nov 2006

04-00030-01-en
Table 14.73:
Parameters Xmin REAL Lower limit of the input range.

Xmax REAL Upper limit of the input range.
Dimension REAL List of function values (minimum of 2
(Y(X)) and maximum of 255). Each value in
the list is entered on a separate line.
Output type REAL
Access RO
Description
The VECTOR block permits the definition of any piece-wise linear
function for an input signal within the limits Xmax and Xmin. The
function is defined by specifying the output function values y = f(x) for
N equally spaced input (x) values between the two limits. For input
values between two points, the function value is calculated by linear
interpolation. If the value of the input signal is less than Xmin, the
value defined at that point will be taken, and likewise if the input is
greater than Xmax.
Note
This block can act as a ranged array of Real values for use as a look-
up table as in the example below:
Table 14.74:
Input Output
5 34.5
6 28.0
7 42.5
8 33.9
To do this, the input must always be an Integer between Xmin and

Xmax (Xmin = 5, Xmax = 8 in the example), and the number of ele-
ments in the list must be equal to Xmax – Xmin + 1 (8 – 5 + 1 = 4 in the
example).
TAC AB, Nov 2006 411 (450)

04-00030-01-en
14.58 WDAY – Week Day
Fig. 14.76:
Table 14.75:
Output type INTEGER

Access RO
Description
Provides the day of the week, according to the internal time clock. The
output value 1 corresponds to Monday and 7 to Sunday.
14.59 XOR – Exclusive OR Gate
Fig. 14.77:
Table 14.76:
Inputs state1 BINARY

state2 BINARY
Output type BINARY
Access RO
Description
Calculates the boolean exclusive OR function of state1 and state2,
according to the following truth table:
Table 14.77:
state1 stat2 output

0 0 0
0 1 1
412 (450) TAC AB, Nov 2006

04-00030-01-en
Table 14.77:
state1 stat2 output

1 0 1
1 1 0
TAC AB, Nov 2006 413 (450)

04-00030-01-en
414 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 15 Expressions
15 Expressions
Fig. 15.1:
Expression blocks are special blocks with one parameter, an arithmetic
expression, which may be simple or complex. Depending on the expres-
sion, the block can have many inputs or just a few. The graphic repre-
sentation of the blocks may vary in size, depending on the expression
size and/or the number of inputs.
There is only one output signal from an expression block. Depending on
the output signal type: Real, Integer or Binary, one of three expression
block types is created. These are:
Table 15.1:
Acronym Short description Comments

XPB Expression block. Binary output.
XPI Expression block. Integer output.
XPR Expression block. Real output.
Expression blocks are always read only and the memory which they
occupy, once compiled, depends on the complexity of the expression.
TAC AB, Nov 2006 415 (450)

04-00030-01-en
15 Expressions TAC Menta, Technical Manual
15.1 Operands
The Operands of the expressions can be:
Table 15.2:
Input Variables These are declared in the expression using a sin-

gle letter, which if in uppercase (A, B, C, …)
represents an Analog input, but if in lower case
(a, b, c, …) represents a Binary input. It is not
permissible to use the same letter in both upper
and lower case, e.g. “A” and “a”, in the same
expression. The input variables are sorted in
alphabetical order on the left side of the expres-
sion block.
Numeric Con- The constant is an Integer portion which may be
stants preceded by a symbol: + or –. The Integer por-
tion may be followed by a decimal point (.) and a
decimal portion. Finally, an exponential portion
may be added: the letters e or E, followed by an
Integer with two digits.
Alpanumeric These are alphanumeric identifiers of 20 signifi-
Constants cant characters which must be defined in the
table of constants. The constant name must be
between two " characters if a / or : character is
included in the name. Public constants are not
permitted in expression blocks.
15.2 Operators
The operands are combined with the operators, which are described
below in order of precedence.
Table 15.3:
Unitary Operators –,! change of sign, logical negation
416 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 15 Expressions
Table 15.3:
Binary Operators *, /, % multiplication, division and modu-

lus
+,– addition, subtraction
<< , >> left shift, right shift
<,> less than, greater than
<= , >= less than or equal to, greater than or
equal to
= , != equal to, not equal to
& logical AND (bit wise)
^ logical Exclusive OR (bit wise)
| logical OR (bit wise)
Ternary Operators ?: IF-THEN-ELSE statement.
“a ? b : c” means “if a then b else
c”.
15.3 Aritmethical Functions

Table 15.4:
x**y x raised to the power of y

LN (x) Natural logarithm of x
LOG (x) Base 10 logarithm of x
EXP (x) Exponential e to the power of x
COS (x) Cosine of x (radians), defined for all x
SIN (x) Sine of x (radians), defined for all x
TAN (x) Tangent of x (radians), defined for all x
ACOS (x) Arc cosine of x, where –1 < x < 1, gives a result
between 0 and /2 radians
ASIN (x) Arc sine of x, where –1 < x < 1, gives a result
between –p/2 and p/2 radians
ATAN (x) Arc tangent of x, defined for all x, gives a result
between –/2 and /2 radians
SQRT (x) Square root of x
TAC AB, Nov 2006 417 (450)

04-00030-01-en
15 Expressions TAC Menta, Technical Manual
Table 15.4:
ABS (x) Absolute value of x

INT (x) Conversion to Integer (truncation)
Parentheses may be used in an expression to force an evaluation order

different to that imposed by the order of precedence of the operators.
The three types of variables may always be combined with an operator
without problem, since the necessary type conversions are automati-
cally performed according to the rules described below:
• For the operations +, –, * and /, all values are converted to Real
values.
• For the operations %, <<, >>, &, ^ and | all values are converted to
Integer values (Real values are truncated).
• For the operation !, a Real or Integer value is converted to Binary
using the following rule: if the value is zero, it will be converted to
zero, and if it is non-zero, it will be converted to one before logical
negation is carried out. A “true” bitwise Not operation on an inte-
ger A can be obtained with the operation A ^ (-1), i.e. A XOR (-1).
• The operations >, <, >=, <=, =, != convert the operands to Real
values, perform the comparison and return a Binary result.
15.4 Output
The output signal from the expression block will be:
Table 15.5:
XPB Block A Binary output. If the result is zero, the output

from the block will be zero and if it is any value
other than zero, the output will be one.
XPI Block The result is converted to a 16 bit signed Integer
number.
XPR Block The output is a Real number which is obtained
from the evaluation of the expression.
418 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 16 Operators
16 Operators
An expression block may be graphically developed as various operator
blocks interconnected by connections. Several operator types exist,
equivalent to those used in expression blocks. The result is completely
equivalent; each single operator is compiled to a single expression
block, exactly as if it had been written in an expression block. Output
signals from operators can always be read by the user.
The operator's Analog inputs may be connected to a Real or an Integer
output. The Analog output may be connected to a Real or an Integer
input without distinction. If the output of an Analog operator is con-
nected to an FB with an Integer input, the operator output will be con-
verted to an Integer. Thus, if other FBs with Real inputs are connected
to the same operator output, they will receive an Integer value. Binary
inputs may only be connected to Binary outputs.
The following operators are available. In graphic mode, standard sym-
bols are used for their representation. In this presentation, the operators
are divided into logical groups similar to the simple blocks.
16.1 Constants
Table 16.1:
Name Comments
Binary const No input → Binary output
Integer const No input → Integer output
Real const No input → Real output
Public constants are not allowed in constant operators.
16.2 Logical Operators

Table 16.2:
Name Comments
NOT Binary input → Binary output
TAC AB, Nov 2006 419 (450)

04-00030-01-en
16 Operators TAC Menta, Technical Manual
Table 16.2:
Name Comments
AND Binary inputs → Binary output
OR Binary inputs → Binary output
XOR Binary inputs → Binary output
16.3 Math Operators

Table 16.3:
Name Comments
Negate Analog input → Analog output
Addition Analog inputs → Analog output
Subtraction Analog inputs → Analog output
Product Analog inputs → Analog output
Division Analog inputs → Analog output
Module Analog inputs → Analog output
16.4 Comparison
Table 16.4:
Name Comments
Less than Analog inputs → Binary output
Greater than Analog inputs → Binary output
Equal Analog inputs → Binary output
Not equal Analog inputs → Binary output
Greater or equal Analog inputs → Binary output
Less or equal Analog inputs → Binary output
420 (450) TAC AB, Nov 2006

04-00030-01-en
16.5 Bit Operation

Table 16.5:
Name Comments
bit AND Analog inputs → Analog output
bit OR Analog inputs → Analog output
bit XOR Analog inputs → Analog output
Shift right Analog inputs → Analog output
Shift left Analog inputs → Analog output
Examples
TAC AB, Nov 2006 421 (450)

04-00030-01-en
Note
All 16 positions are shifted, and 0 is shifted into empty positions. Any
shift count 16 always gives the output value 0.
16.6 Others
Table 16.6:
Name Comments
D/A converter Binary input → Analog output
A/D converter Analog input → Binary output
Analog multiplexer Analog inputs → Analog output
Binary multiplexer Binary inputs → Binary output
Conversion AA Integer signal → Real signal
In the expression block, operands of different types may be combined

using any operator. However, when using operator blocks, conversions
should be performed explicitly. The D/A and A/D operators are simply
operators that convert from Binary to Analog and vice versa. Those
operators are needed because the rest of the operators have typed inputs
so, without them, you would not, for example, be able to sum a Binary
and an Analog signal. In expression blocks, conversions are done
implicitly so you won't need these operators in expressions. The conver-
sion rules are as follows:
• A Real or Integer number is converted to a Binary value giving a
logical 0 if the input is exactly 0, or 1 if it is different.
• A Binary signal is converted to Analog as expected: logical 0
gives the number 0 and logical 1 gives the number 1.
The multiplexer operators are switches which select one of two input
signals, depending on the Binary switch value.
The Conversion AA operator is used when connecting an integer output
to a real input or vice versa. Since operators do not distinguish between
422 (450) TAC AB, Nov 2006

04-00030-01-en
Real and Integer values, the Conversion AA operator does not carry out
an explicit type conversion with rounding or truncation. Instead, this
type conversion is done in the block using the Conversion AA output
signal as the input. We recommended using expression blocks when
explicit type conversions with rounding or truncation are needed.
TAC AB, Nov 2006 423 (450)

04-00030-01-en
424 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 17 Supported SNVTs
17 Supported SNVTs
The list of SNVTs supported by TAC Menta is updated regularily.
For up-to-date information, please contact the TAC helpdesk by email-
ing helpdesk@tac.se.
17.1 List of SNVTs

TAC Menta supports the following SNVTs:
Table 17.1:
SNVT Number
SNVT_alarm 88
SNVT_amp 1
SNVT_amp_f 48
SNVT_amp_mil 2
SNVT_angle 3
SNVT_angle_deg 104
SNVT_angle_vel 4
SNVT_btu_f 67
SNVT_char_ascii 7
SNVT_chlr_status 127
SNVT_config_src 69
SNVT_count 8
SNVT_count_f 51
SNVT_count_inc 9
SNVT_count_inc_f 52
SNVT_date_day 11
SNVT_elapsed_tm 87
TAC AB, Nov 2006 425 (450)

04-00030-01-en
17 Supported SNVTs TAC Menta, Technical Manual
SNVT Number
SNVT_elec_kwh 13
SNVT_elec_whr 68
SNVT_flow 15
SNVT_flow_f 53
SNVT_flow_p 161
SNVT_freq_f 75
SNVT_freq_hz 76
SNVT_freq_kilohz 77
SNVT_hvac_emerg 103
SNVT_hvac_mode 108
SNVT_hvac_overid 111
SNVT_hvac_status 112
SNVT_length_mil 20
SNVT_lev_count 21
SNVT_lev_count_f 55
SNVT_lev_disc 22
SNVT_lev_percent 81
SNVT_lux 79
SNVT_magcard 86
SNVT_mass_f 56
SNVT_muldiv 91
SNVT_multiplier 82
SNVT_obj_request 92
SNVT_obj_status 93
SNVT_occupancy 109
SNVT_power 27
SNVT_power_f 57
SNVT_power_kilo 28
426 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 17 Supported SNVTs
SNVT Number
SNVT_ppm 29
SNVT_ppm_f 58
SNVT_preset 94
SNVT_press 30
SNVT_press_f 59
SNVT_press_p 113
SNVT_pwr_fact 98
SNVT_pwr_fact_f 99
SNVT_regval 136
SNVT_regval_ts 137
SNVT_res_f 60
SNVT_rpm 102
SNVT_scene 115
SNVT_scene_cfg 116
SNVT_setting 117
SNVT_speed 34
SNVT_speed_f 62
SNVT_state 83
SNVT_str_asc 36
SNVT_str_int 37
SNVT_switch 95
SNVT_temp 39
SNVT_temp_f 63
SNVT_temp_p 105
SNVT_temp_setpt 106
SNVT_time_f 64
SNVT_time_hour 124
SNVT_time_min 123
TAC AB, Nov 2006 427 (450)

04-00030-01-en
17 Supported SNVTs TAC Menta, Technical Manual
SNVT Number
SNVT_time_sec 107
SNVT_time_stamp 84
SNVT_tod_event 128
SNVT_vol 41
SNVT_vol_f 65
SNVT_vol_kilo 42
SNVT_volt 44
SNVT_volt_f 66
SNVT_zero_span 85
428 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 18 Test Probe Blocks
18 Test Probe Blocks

18.1 Summary
In some cases, the testing and debugging of application programs can
be simplified when the feedback control loops are closed. An auxiliary
model which simulates the dynamics of the system (plant), e.g. an air
handling unit, can be used for this purpose. This model can be pro-
grammed with function blocks and included in the application FBD. To
make the application program independent of the auxiliary simulation
model, we need special blocks which can read the state of the physical
outputs and write the values calculated by the system model to the phys-
ical inputs. These blocks are called test probe blocks. A test probe block
refers to a specific IO block by giving the test probe the same identifier
as the IO block.
Note
Test probe blocks are for simulation purposes only. A program with
test probe blocks cannot generate code to be downloaded to the con-
troller. Thus, any simulation model included in the application pro-
gram must be deleted before the executable code is generated.
There are four different test probe blocks available, corresponding to

the four types of physical I/O signals:
Table 18.1:

TPAO Test probe for Analog output
TPDO Test probe for Digital output
TPAI Test probe for Analog input
TPDI Test probe for Digital input
TAC AB, Nov 2006 429 (450)

04-00030-01-en
18 Test Probe Blocks TAC Menta, Technical Manual
18.2 TPAI – Test Probe for Analog Input
Fig. 18.1:
Table 18.2:
Inputs Input REAL Input signal

output
Access Block used
only during
simulation.
Description
The TPAI block writes a value to the Analog input block which has the
same name (identifier) as the test probe block. Note that the TPAI block
may be used with all types of Analog input blocks. The value of the
Analog input block will be set to the value of the input to the corre-
sponding TPAI block, i.e. no scaling is carried out.
18.3 TPAO – Test Probe for Analog Output
Fig. 18.2:
Table 18.3:
Inputs Block has no

inputs
Output type REAL
430 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 18 Test Probe Blocks
Table 18.3:
Access Block used

only during
simulation.
Description
The TPAO block reads the value of the Analog output block which has
the same name (identifier) as the test probe block. The output of the
TPAO block is set to the same value as the input value to the Analog
output block.
18.4 TPDI – Test Probe for Digital Input
Fig. 18.3:
Table 18.4:
Inputs Input BINARY input signal

output
Access Block used
only during
simulation.
Description
The TPDI block writes the value of Input to the Digital input block
which has the same name (identifier) as the test probe block.
TPDI can also be linked to a CNT block. In this case, only one pulse per
application program cycle can be counted. The pulses are counted on
high to low transitions.
TAC AB, Nov 2006 431 (450)

04-00030-01-en
18 Test Probe Blocks TAC Menta, Technical Manual
18.5 TPDO – Test Probe for Digital Output
Fig. 18.4:
Table 18.5:
Inputs Block has no inputs

Output type Block has no output
Access Block used only during simulation.
The TPDO block reads the status of the Digital output block which has
the same name (identifier) as the test probe block.
TPDO can also be linked to a DOPU block. In this case, the DOPU
parameter MinPulse must be set to the same value as the application
program cycle time (sec), otherwise simulation may give incorrect val-
ues.
432 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 19 Error Messages
19 Error Messages
When run, TAC Menta displays a number of information, warning and
error messages. In this section, the possible causes of some of these
messages are displayed, together with some hints about how to find and
correct the errors.
19.1 System Errors

System out of memory, Out of memory, Compiler out of
memory, API error, No timer allocated, Printing error
All of these error messages can occur if system resources are too low,
although other errors may cause some of them. Close all other programs
and/or restart Windows.
Type description file TATYPE.INI not found
Program files have been deleted or moved from the TAC Menta direc-
tory. Re-install TAC Menta.
19.2 FBD Compilation

During FBD compilation, i. e. when going from Edit mode to Simula-
tion mode in the TAC Menta main program, there is a syntax error
check. The faulty block will be marked and centered.
Sensor type 0..1V may give poor resolution
Not an error, just a warning that the default setting of the Sensor field in
the AI – Linear analog input parameter hasn’t been altered. In most
cases, 0..10V or 2..10V are better choices.
Unconnected input
The inputs to blocks may not be left unconnected. When this error
appears, find the block in the selection rectangle and connect the
input(s) which are unconnected.
Illegal closed loop has been detected
Feedback loops are permitted in the programming language. However,
at least one RW block, i.e. a block with an internal delay between the
input and the output signal, must exist in the loop. If all of the blocks
which constitute the feedback loop are RO, this error message will
appear. The selection rectangle will be positioned over one of the blocks
TAC AB, Nov 2006 433 (450)

04-00030-01-en
19 Error Messages TAC Menta, Technical Manual
in the feedback loop. The solution to this type of error is to introduce an

RW block, typically a delay block, into the feedback loop.
Output is connected to incompatible inputs
This error only occurs when an operator with an analog output is simul-
taneously connected to a real input and an integer input. To resolve this
error, we recommend duplicating the operator and connecting each of
the operators to a single input.
The physical IO requirements exceed the capabiites of the
chosen device.
This error occurs when the same connection has been used for several
blocks.
Redefined identifier
This error occurs when two blocks whose output have been defined as
a public signal have the same identifier. To correct this error, the name
of one of the blocks must be changed.
Undefined constant
This error occurs when a constant identifier is used in a block or blocks
without having been defined in the Constants table.
Block must have a name
This error occurs when a public block output signal has not been given
a name (identifier).
Public constant not supported in expression blocks
Public constants are not permitted in expression blocks. The solution is
to move the constant to a PVB/PVI/PVR block and connect it to the
expression block via an input (or use a non-public constant).
Public constant used more than once
Public constants may not be used in several block parameters at the
same time. The solution is to define different constant names for each
block parameter (if they have to be public), or use a non-public constant.
Public constant identifier is in use already
A signal identifier must not exist simultaneously as a public constant
and public signal. The constant must either be renamed or made non-
public.
Public constant not used
You are not allowed to define a public constant and then not use it as a
block parameter. It must either be renamed or made non-public.
434 (450) TAC AB, Nov 2006

04-00030-01-en
I/O terminal reused in I/O block

Either two I/O blocks uses the same terminal reference, or one I/O block
has no terminal reference at all.
Node name too long
The name of the node is too long. For information on syntax require-
ments see Section 6.2.2, “Signal Names”.
The number of backslashes must be 2 or 3
The number of backslashes is wrong. Only 2 or 3 backslashes are
acceptable. For information on syntax requirements see Section 6.2.2,
“Signal Names”.
19.3 Saving and Loading the Application Program in

the Database
Could not save .mta file
The mta file could not be saved in the TAC Vista database.
Failed to update the database (reserve after inject)
The application program could not be saved in the TAC Vista database.
Could not load mta file
File could not be opened from the TAC Vista database
The application could not be opened. Check that TAC Vista Server is
working properly.
File object is locked by another application
Another application (or user) is currently working on the file and it is
not available.
Could not read temporary file
When working with an application program, a temporary file is used.
This error indicates that the temporary file is damaged or corrupted.
File object contains no actual MTA file
This error can occur when saving an empty application program in the
TAC Vista database.
Unable to save file. The application contains <no> blocks,
but only <no> are allowed
This error occurs when trying to save an application program which
contains more that 4,000 blocks.
TAC AB, Nov 2006 435 (450)

04-00030-01-en
19.4 Simulation
Division by zero, Numerical overflow
Logical application program error. Reconstruct your FBD.
Execution stopped, the block named: <name> and type:
<type> passed its limit
Error message displayed when the limit Stop at a limit (breakpoint) is
reached during a simulation.
19.5 Code Generation

Symbol table full, Value doesn’t fit in byte
In some cases, an application contains too many signals, disabling gen-
eration of the OP menu tree. Take action by starting the OP Configura-
tion Tool and removing parts of the menu tree.
Note
If selected, remove the “Automatic generation of menu tree” selection
in the Preferences menu, or the new menu tree will be overwritten
during the next OP tree generation.
Software error parsing output file, Software error parsing

generated file
TAC Menta was unable to run through the code generation process
completely, although in most cases there are no FBD errors. Try again!
An FBD with test probe cannot be executed online, Can’t
generate a COD file with test probes
An application program containing test probes has not been allowed to
be generated and downloaded. This error message may also be shown if
an error, which has no specific error message, occurs during code gen-
eration.
Parser code error
The application may be using too much memory. Please contact the
TAC Helpdesk.
The maximum number of Alarm blocks is exceeded in the
application. The problem must be solved before the
application can be generated
The application contains more than 127 Alarm Blocks. The number of
Alarm Blocks must not exceed 127.
436 (450) TAC AB, Nov 2006

04-00030-01-en
The TACSnvtCfg.dll was not instantiated successfully! It

will not be possible to use SNVTs in the applications.
The file TACSnvtCfg.dll has been removed from C:\Program
Files\Common Files\TAC Shared. This is probably due to an uninstal-
lation. Please reinstall TAC Menta, if you wish to have access to SNVTs
in the applications.
This SNVT could not be used because all engineering units
are not available for it.
The SNVT in question is not available in Taxif.ini. Please contact the
TAC helpdesk for information.
19.6 Download
If an error occurs during download to the TAC Xenta device, TAC
Menta will display an error message and open the .COD file with the
suspected error marked. The error code number indicates the section in
the .COD file where the download was interrupted. This information
may be useful when trouble-shooting.
Update of description of network neightbourhood from TAC
Vista Server is not performed
This error occurs when performing a download using the serial interface
(RS-232) on a TAC Xenta device. The error indicates that network
neighborhood is not updated in the same way as when downloading
using TAC Vista.
19.6.1 Error Codes
Table 19.1:
No. Error in section Comment

1 Create object
2 Allocate flash
3 I/O module save
4 Version
5 Application name
6 Abbreviation
7 Type
8 Source file
9 Signals
TAC AB, Nov 2006 437 (450)

04-00030-01-en
No. Error in section Comment

10 Alarm texts
11 Time schedule
12 I/O module
13 I/O The terminal may
not exist in this
unit type
14 Cycle time
15 Code
16 DST
17 Checksum
18 EOF
Memory allocation The application is
too big
19.7 TAC Xenta Communication

Communication time-out, Time-out, Unknown error from
remote unit
Communication problems; the TAC Xenta unit is not answering. Try
again.
Communication failed, Upload failed, Download failed
The TAC Xenta unit may have stopped communicating. Try again or
reset the TAC Xenta unit manually. Before this error message, there
might have been another one, further explaining the problem.
Error restarting unit
The TAC Xenta unit was too busy to answer a question. Try again.
438 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 20 Programming Hints
20 Programming Hints
20.1 Program Cycle Time
The cycle time for the application program is variable. Take this into
account when drawing your application program.
Example: The INTEG block can be used for calculating Energy con-
sumption from the input Power. When resetting the block at the start of
a new calculation interval, the reset value must be the input signal times
the program cycle time !
20.2 Time Counter

An easily made time counter, counting in seconds, which takes care of
the actual application program cycle time. The counter is reset by a
Binary signal.
Fig. 20.1:
Time counters can also be made by means of the PULSE and RT blocks.
Designs using RT and INTEG can be reset during the count. The
INTEG counter can be used generally, whenever counting (time, power
etc.) over time.
20.3 Equality
If testing whether two values are equal, make sure that the tested values
are of the Binary or Integer type. Be sure to not carry out an equal test
on Real values.
TAC AB, Nov 2006 439 (450)

04-00030-01-en
20 Programming Hints TAC Menta, Technical Manual
20.4 Reset Counter

To reset, for example, an energy counter without losing any pulses dur-
ing the reset:
Fig. 20.2:
20.5 Bitwise Logical Operators

The output of, for instance, the bitwise AND (&) operator is an Integer
which represents the result of the AND operation on two Analog sig-
nals. By using this operation inside an expression block with a Binary
output and assigning the result of the AND operation to the output, you
obtain a Binary signal which will be zero if there is no match and one as
soon as there is a match in at least one bit position.
20.6 Multiplier Parameter in CNT Block

The internal multiplier parameter in the CNT block cannot be assigned
to a public constant since it is a configuration parameter. If you want to
be able to change this value from the operator’s panel, you will have to
make a special program to take care of the conversion from the number
of pulses to engineering units by other blocks.
Fig. 20.3:
440 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual 20 Programming Hints
20.7 Sliding Average Value

Programming example of the sliding average of three values:
Fig. 20.4:
20.8 TSCH Output

The output from the time schedule block is an integer, showing the
remaining number of minutes to the next change of state of the time
schedule. For making a Binary signal, there are different possibilities:
Fig. 20.5:
20.9 PIDI – DOPU

Normal use of the PIDI and the DOPU block;
Fig. 20.6:
TAC AB, Nov 2006 441 (450)

04-00030-01-en
20 Programming Hints TAC Menta, Technical Manual
20.10 Day Shift

It is possible to detect a day shift, if the new hour has a lower value than
the previous hour.
Fig. 20.7:
20.11 Expression Blocks

It is not possible to change the output type of an expression block, when
the output is connected to a node.
Expression blocks can be used to convert from a Real signal to an Inte-
ger signal and vice versa:
Fig. 20.8:
20.12 Start-Up Delay

Use the RST block to create a start-up delay following a warm start of
the TAC Xenta device. Set different delays for different AHUs etc. by
altering the DelayOff time (60 s in the example):
Fig. 20.9:
442 (450) TAC AB, Nov 2006

04-00030-01-en
TAC Menta, Technical Manual Index
binding parameters, modifying in online mode 315

Index bits per second 228
bitwise logical operators 440
Symbols block 252
block parameters, modifying 280
*.mta-files 29 BPS 228
*.xif-files 29
C
A
calculated magnitude 232
access rules 243
character set file, defining 295
ACCUM 332
CNT 238, 345
accumulator 332
cold start 18
actions on signals 273
COM pause 229
AHYST 333
COM port 228
AI 334
compatibility
ALARM 339
AUT files 322
alarm 339
COD files 322
alarm text table 265
OP menu tree files 323
alarm texts 244
TAC Menta v3 322
analog 232
connection
analog hysteresis 333
highlight 273
analog input 334
connections 231, 233, 255
analog output 342
break 256
analog waves
delete 256
amplitude 275
delete last segment 255
average value 275
draw 255
circular 275
end 255
period 275
highlight 256
phase 275
initiate 255
wave form 275
constants 231, 236, 244
AND 341
constants table 236, 263
AO 342
add a constant 263
application data upload 313
edit a constant 263
application program documentation, print 315
remove constant 263
application program download 312
control 18
application program ID 315
control loop 231
application program, execution 272
correct operation, verify 324
arithmetic expression 234
create COM log 229
associated text file 229
CURVE 346
associated text files 317
curve function 346
automatic generation, input vectors 274
cycle time 407
B D
B 18
DATE 348
baud rate 228
date and time 268
binary hysteresis 365
day 348
binary sequences
day shift 442
circular 276
defining character set file 295
period 276
DELAY 349
sequence 276
delayed On/Off 349
Binary Sequences, generation 275
DELB 350
binary value delay 350
DELI 350
binding 238
DELR 351
binding parameters 237
TAC AB, Nov 2006 443 (450)

04-00030-01-en
Index TAC Menta, Technical Manual
demo application 228 FBD 18, 231, 248

demo mode 228 feedback loop 231
destination blocks 231 File menu
Device Configuration Exit 297
Use LonMark 3.3 305 Export 297
device configuration 304 Import 297
add new network variables (SNVT) last in the XIF New 297
file 305 Open 297
base unit type 304 Print 297
hardware version 304 Print Preview 297
system version 304 Print Setup 297
XIF header generated accordnig to LonMark 305 Save 297
DI 351 Save As 297
digital input 351 FILT 363
digital output 356 first order filter 363
digital pulse output 358 Formats menu
disconnect block 254 Alarms 298
DO 356 Character Set File 298
Docnet 15 Date and Time 298
DOPU 238, 358 National Months Text 298
download application program 312 National Week Days Text 298
download wizard 319 Settings 299
dialog 320 Signal Properties 297
general downloading procedure 321 function block 18, 231, 233, 251
Function Block Diagram 18
E function keys 247–248
edit 249 functions 227
block 252
center selection 249 G
find 248 generate application programs 236
replace 249 generate executable code 308
edit mode 227, 247, 251 generation
Edit STR Wall module table 306 analog waves 275
ENTH 359 binary sequences 275
enthalpy 359 generic I/O blocks 237
equality 439
ERR 362 H
Error Block 362 Help menu
Error Block codes 362 About 301
exclusive OR 412 Contents 301
executable code HFB 242, 261
BIN 308 hierarchical function blocks 242, 261
CHR 308 create 261
COD 308 expand and compress 262
ESP 308 naming an HFB and connections 262
generate 308 printout 263
OPC 308 high/low signal limit 367
XIF 308 holiday charts 244
executable files, simulation 274 HOUR 364
expression blocks 237, 442 HYST 365
F I
FB 18 I/O configuration table 238
444 (450) TAC AB, Nov 2006

04-00030-01-en
Inch-Pound unit system 227 date and time/daylight saving 288

input signals 231 editing an existing tree 289
input vectors, automatic generation 274 moving menu items 290
inputs 234 status 286
INTEG 366 sub menu 286
integer value delay 350 TAC service menu 289
integer value parameter 392 menu structure display 284
integrator 366 MIN 368
intermediate blocks 231 minimum signal selector 368
internal constants 236 MINUTE 368
IO Expansion and Wall Module table 305 minute 368
IO expansion module table modifying binding parameters 315
fast CNT reporting 306 modifying block parameters 280
Min send time 306 alarm texts 281
module 305 constants 281
type 306 function block parameters 280
I/O binding data 281
K time schedules 280
K 18 modifying parameter blocks 314
modifying public constants 314
L module 232, 241
MONTH 369
library 229 month 369
LIMIT 367 mouse 247
logger tool 278 move a node 256
clear 280 multiple instances 229
diagram Setup 278 multiplier parameter in CNT block 440
presenting logged values 279
start 278 N
logical AND gate 341
logical operators 235 NCYC 369
LonWorks 18, 29 network address 242
network variable 239
M ninary value parameter 392
nodes 233
macro blocks 229 NOT 370
MAX 367 numeric 235
Maximum Signal Selector 367 numeric value 234
memory usage
application 309 O
application files 309
BPR size calculator 310 off-line mode 227
calculate 309 online 249
number of objects 310 online device 240
parameters 309 online functions 311
TACN/SNVT in/out 310 online mode 311
work area 309 online mode 227
menu options 296 OP 18
menu structure OP configuration 227
access code 288 OP configuration tool 18
adding Items 285 formats 297
alarm 288 menu bar 296
changing OP display layout 290 tree 300
copy and paste 290 OP configuration, signals list 284
creating 285 OP Description Files
TAC AB, Nov 2006 445 (450)

04-00030-01-en
ESP 292 PIDP 385

MENU 292 POLY 389
OPC 292 polynomial function 389
OP description files 291 power failure 18
access code 293 PRCNT 390
alarm 293 Preferences 229
data and declaration syntax 292 presentation 18
date and time 293 print application program documentation 317
daylight saving 293 priority 1 alarms 363
DOP 292 program cycle 231
edit access code 293 program cycle counter 369
example 294 program cycle time 439
exporting 295 program licenses 228
importing 294 Program Specification 303
OP menu tree Author 303
automatic generation 290 Blocks 303
operation Cycle time 303
manual mode 274 Date 303
operation modes 227 I/O signals 304
operations on groups 257 Name 303
center the selection rectangle 259 Public signal table 304
copy a selection rectangle to the clipboard 259 Standard App. 304
copy and paste 259 Type 303
delete 258 public constant 241
deselect 257 Public constants 235
disconnect 258 public constants 236
enter or edit the module name 258 modifying in on-line mode 314
load a macro block 261 public parameters 241
macro commands in comment blocks 259 PULSE 391
move 258 pulse generator 391
print the selection rectangle 259 PVB 392
save a macro block 260 PVI 392
select 257 PVR 394
OPT 371
optimization 371 R
OR 378 RAMP 394
OSC 379 ramp filter 394
oscillator 379 read/write 233, 237
output signal 234 read-only 233, 237
override of physical I/O signals 313 real value delay 351
real value parameter 394
P Recorder
packet size 229 Clear 277
parameter blocks, modifying in on-line mode 314 Place signal 277
parameters 231 Remove signal 277
percentage 390 Reset 277
physical inputs 231 Restart 277
physical magnitude 232 remove signal from recorder 277
physical terminal 239 Resends 229
PID Controller – Incremental Output 383 reset counter 440
PIDA 380 restart 18, 395
PIDI 383 RST 249, 395
PIDI – DOPU 441 RT 395
446 (450) TAC AB, Nov 2006

04-00030-01-en
runtime 231 time out 229

run-time measurement 395 time schedule 244, 408
time schedule table 264
S TPAI 236, 430
sample and hold binary value 399 TPAO 236, 430
sample and hold real value 401 TPDI 236, 431
sample time, define 278 TPDO 236, 432
SECOND 396 TREE
segments 233 Build 300
SEQ 397 Copy to clipboard 301
sequencer 397 Expand 300
SHB 399 Generate 300
SHR 401 Load Specification 300
SI (metric) unit system 227 Remove Specification 301
signal, place in recorder 277 Test 300
signals 243 Update Specification 301
simple blocks 234 View Specification 301
simulation 231 trend log 231
executable files 274 trend log, view 277
external inputs 274 trend logging 244, 265, 276
modifying block parameters 280 definition 266
test probes 276 local 265
simulation mode 227, 247, 249 logging type 267
sliding average value 441 select trend log 266
SNVT 18, 240 signal 267
source blocks 231 TRIG 407
SR 402 trigger 407
standard applications/controllers TSCH 244, 408
marking 315 TSCH output 441
Standard Network Variable Type 18
start-up delay 442 U
STR Wall module 306, 404–405 U 18
STRIN 237, 404 Undo 269
STROUT 237, 405 upgrading
structured type 241 AUT file 323
system error 362 system and application programs 323
System of Units 227 upgrading a TAC Xenta 300 to v3 323
T V
tabular 248 VECTOR 410
TAC Menta 18, 227 vectorial curve function 410
TAC Menta start 229 verify correct operation 324
TAC Menta v3 compatibility 322 view trend log 277
TAC Xenta 18
TAC Xenta, upgrading 323 W
TCYC 407 Wall module table
test probe for analog input 236, 430 Auxiliary Options 307
test probe for analog output 236, 430 Backlight timeout 307
test probe for digital input 236, 431 Display timeout 307
test probe for digital output 236, 432 HVAC Settings 307
test probes 235 Min send time 306
text file 229 Minimum change for update 306
time counter 439 module 306
TAC AB, Nov 2006 447 (450)

04-00030-01-en
Space temperature offset 306

Temperature display resolution 307
Temperature setpoint high limit 307
Temperature setpoint low limit 307
type 306
warm start 18
WDAY 412
week charts 244
week day 412
X
X 18
XOR 412
Y
Y 18
448 (450) TAC AB, Nov 2006

04-00030-01-en
Copyright © 2006, TAC AB Europe / Headquarters
All brand names, trademarks and registered trademarks are Malmö, Sweden
the property of their respective owners. Information con- +46 40 38 68 50
tained within this document is subject to changewithout no-
tice. All rights reserved. Americas
Dallas, TX
04-00030-01-en +1 972-323-1111
Asia-Pacific
Sydney, Australia
+61 2 9700 1555
www.tac.com
Last Manual Page

Vista V

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Vista V

Transféré par

Droits d'auteur :

Formats disponibles

TAC Menta

TAC AB, Nov 2006 5 (450)

4.5.2 Simulating the Design ................................................................................................ 64

6 (450) TAC AB, Nov 2006

6.4.4 Test Probes ................................................................................................................. 235

TAC AB, Nov 2006 7 (450)

8.4.1 Creating an HFB......................................................................................................... 261

8 (450) TAC AB, Nov 2006

10 OP Configuration Tool 283

TAC AB, Nov 2006 9 (450)

12.3 Upgrading a TAC Xenta 300 Device to v3 ................................................................ 323

10 (450) TAC AB, Nov 2006

14.34 PIDA – PID Controller – Analog Output................................................................... 380

TAC AB, Nov 2006 11 (450)

19.1 System Errors ............................................................................................................. 433

12 (450) TAC AB, Nov 2006

TAC AB, Nov 2006 15 (450)

16 (450) TAC AB, Nov 2006

TAC AB, Nov 2006 17 (450)

18 (450) TAC AB, Nov 2006

1.4 New in this Edition

1.5 Typographic Conventions

TAC AB, Nov 2006 19 (450)

20 (450) TAC AB, Nov 2006

2 Menta Programming Fundamentals.

2.1 Basic project analysis

2.2 System configuration

2.3 Application Programming Phases

Function phase Design phase Test phase

Functional System Delivery to plant,

TAC AB, Nov 2006 23 (450)

The Function Phase

2.4 Function Phase of the Application Programming

2.5 Design Phase of the Application Programming

2.5.2 Naming of Points and Alarms.

24 (450) TAC AB, Nov 2006

of acronyms or designations. The same applies, even in a higher degree,

2.5.3 Structuring the FBD

Data flow Connections

TAC AB, Nov 2006 25 (450)

2.5.4 Using Modules in the Application

2.5.5 Menus in the OP

26 (450) TAC AB, Nov 2006

Upper Levels Menus

Application Level Menus

TAC AB, Nov 2006 27 (450)

2.6 Test Phase of the Application Programming

28 (450) TAC AB, Nov 2006

3 Planning the Project

3.1 Folder Structure

3.1.1 Creating the Project Folder

A brief description of their intended use and content:

3.2 Case Study

3.2.1 Description of the Facility

TAC AB, Nov 2006 29 (450)

Accounts, Senior Management and the entrance lobby. The second

Marketing and Management

3.2.2 Device Description and Naming Convention

30 (450) TAC AB, Nov 2006

The rooftop unit serving Marketing and Senior Management will be

First Floor Second Floor

Xenta 301 RTU1 Xenta 104 RTU3

Xenta 401 RTU2 Xenta 401 RTU4