document and reserves the right to make changes, additions or deletions. Schneider Electric Buildings 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 Schneider Electric Buildings, will be regarded as a violation of copyright laws and is strictly prohibited.
Trademarks and registered trademarks are the property of their respective owners.
Schneider Electric Buildings, Dec 20117 (126)
04-00035-02-en (EN)
ContentsTAC Xenta, TAC Xenta 120
APPENDIX
ASetpoint Calculation109
BSNVT-lists113
B.1The Node Object Inputs and Outputs (nvi, nvo) ........................................................ 113
B.2The Control Object Inputs (nvi)................................................................................. 113
B.3The Control Object Outputs (nvo).............................................................................. 117
Index121
8 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
INTRODUCTION
1About this Manual
TAC Xenta, TAC Xenta 1201 About this Manual
1About this Manual
This manual describes a particular process. For information on certain
products, we refer you to the manual or the Help for the product in question.
For information on how to install software, we refer you to the instructions delivered with the software.
For information on third party products, we refer you to the instructions
delivered with the third party product.
If you discover errors and/or unclear descriptions in this manual, please
contact your TAC representative.
Note
1.1Structure
We are continuously improving and correcting our documentation.
This manual may have been updated.
Please check our product documentation site at www.tac.com for the
latest version.
The manual is divided into the following parts:
•Introduction
The Introduction section contains information on how this manual
is structured and how it should be used to find information in the
most efficient way.
•Getting Started
The Getting Started section contains a step-by-step description of
how to engineer or carry out different tasks. It also gives you
guided instructions on how to complete a sample project. If you
want more information, see the corresponding chapter in the Reference section of the manual.
•Reference
The Reference section contains more comprehensive information
about various parts of the Getting Started section. It also provides
you with information on alternative solutions not covered by the
Getting Started section.
•Appendix
At the end of the manual we have collected some detailed descrip-
Schneider Electric Buildings, Dec 201111 (126)
04-00035-02-en (EN)
1 About this Manual TAC Xenta, TAC Xenta 120
!
tions and lists. This information may be useful during special circumstances, but is normally not required.
1.2Typographic Conventions
Throughout the manual the following specially marked texts may occur.
Warning
Alerts you that failure to take, or avoid, a specific action might result
in physical harm to you or to the hardware.
Caution
Alerts you to possible data loss, breaches of security, or other more
serious problems.
Important
Alerts you to supplementary information that is essential to the completion of a task.
Note
Alerts you to supplementary information.
Tip
Alerts you to supplementary information that is not essential to the
completion of the task at hand.
Advanced
Alerts you that the following information applies to complex tasks or
tasks restricted by access.
1.3Prerequisites
To be able to profit from the contents in this manual, it is recommended
that you read the following documentation:
•TAC ZBuilder Programming Tool for TAC Xenta 120, Datasheet,
0-003-3010.
12 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
TAC Xenta, TAC Xenta 1201 About this Manual
•TAC Xenta 121-FC Programmable Fan Coil Application,
Datasheet, 0-003-3057.
•TAC Vista IV Engineering Classic Networks, manual, 0-004-7841.
•TAC Vista IV Engineering LNS Network, manual, 0-004-7842.
1.4Terminology
TAC Xenta Devices
•All programmable T AC Xentas, 280/300/401, will be called Xenta
devices throughout this manual.
•The Xenta 422, 452, and so on will be referred to as I/O modules.
LonWorks Devices
•All other devices will be called LonWorks devices, including the
Xenta 100.
Classic Network
•A Classic Network refers to a TA C Vista system with a Lon-
Works 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
•An 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) application,
LonMaker 3 and an LNS database. This type of LTA port is
referred to as an LNS port in TAC Vista IV.
TAC Vista Modes
•Engineering Mode. This mode is used when commissioning the
network. In this mode, you can send information to the network
devices as well as service pin each device.
•Operating Mode. This mode provides full communication
between the server and the network device. If the connection
between the server and the device on the network is disrupted, you
will receive an alarm.
Schneider Electric Buildings, Dec 201113 (126)
04-00035-02-en (EN)
1 About this Manual TAC Xenta, TAC Xenta 120
Some useful terms and abbreviations regarding the zone controller's
application and network communication are explained in the table
below.
TermDescription
ASCApplication Specific Controller
CCDClimate Control Device
CFRConfiguration record, a file included with the
XIF file for devices with many configuration
parameters. Example: TAC Xenta 120 series.
configurationProcedure to design the software for an ASC
DATDischarge Air Temperature
device plug-inTAC Vista: controller configuration tool
LNS: application to provide custom user inter-
face for devices.
FBFunctional Block
Exception ModeSpecial, configurable behavior of the controller
triggered by certain events.
hardwiredan I/O that is physically connected, as opposed
to a SNVT binding
HPHeat Pump
FCFan Coil
I/OInput/Output
LNSL
ONWORKS Network Servic es; network man-
agement software for L
ONWORKS networks
MSMultiStage
nciconfiguration parameter; variable that gets its
value from a configuration tool and keeps it
during a power failure
NeuronA microprocessor optimized for control net-
works. Neuron chips have three 8-bit inline
processors: two are dedicated to the communi-
cations protocol and one is a general-purpose
applications processor.
nvivariable that normally gets its value from
another unit on the network through binding
14 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
TAC Xenta, TAC Xenta 1201 About this Manual
TermDescription
nvovariable that is sent to another unit on the net-
work
OADOutside Air Damper
OATOutside Air Temperature
PWM (Pulse Width Modulat ion) One type of actuator
control signal
SCCSpace Comfort Controller
scptStandard Configuration Property Type
sequence dia-
gram
A diagram with the Terminal Load on the x-
axis and the (symbolical) controller output sig-
nals on the y-axis. The principal usage of the
TCDs depending on the TL value is shown.
SPIDStandard Program ID
SNVTStandard Network Variable Type
STRRoom temperature sensor (STR series)
stand-aloneThe T AC ZBuilder does not run directly ag ainst
a controller or as a plug-in. Generated configu-
rations can only be saved to a file, not down-
loaded to a physical controller or saved to a
database.
TCDTemperature Control Device - Heating and/or
cooling equipment
templateA standard configuration file that can be used
as a starting-point for a specific ZBuilder appli-
cation. File name: *.zbt.
TL,
Terminal Load
Terminal Load is a value in the range –100% to
+100%. The value indicates the amount of
power (<0: heating, >0: cooling), needed to
reach the required temperature.
ucptUser Configuration Property Type
XFB-file / XFO-
file
When the XIF-file is imported to L
ONMAKER
Integration Tool it is compiled into two files:
the XFB-file and the XFO-file.
XIF fileeXternal InterFace file is a file that, in short,
describes which network variables the device
can handle.
Schneider Electric Buildings, Dec 201115 (126)
04-00035-02-en (EN)
1 About this Manual TAC Xenta, TAC Xenta 120
TermDescription
.zbcFile name extension for ZBuilder configuration
files.
.zbtFile name extension for ZBuilder template
files. See also template.
16 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
GETTING STARTED
2Planning the Project
3Creating the TAC Xenta 120 Con-
figuration
4Installing TAC Xenta 120 in a
Classic Network
TAC Xenta, TAC Xenta 1202 Planning the Project
2Planning the Project
Planning the LonWorks Network in advance saves a lot of time and
effort later in the process. Issues like network structure (groups),
device-naming conventions, and so on should be considered before
actually creating the network.
2.1Folder Structure
Another consideration is the location(s) on the hard drive where files are
stored. A well-organized project requires a well-organized file structure.
2.1.1Creating a Project Folder
When starting a new project, you should prepare a directory containing
folders and subfolders as shown below. In this example, we call our
project ACME.
A short description of their intended use and content:
•DeviceDescr – *.mta-files and *.xif-files for the LonWorks net-
work devices.
•Documentation – subfolder with more general information. For
example, useful manuals, data sheets, and technical product information (TPI). I/O-lists, functional descriptions, and other files created by DesignBuilder could also be saved here.
•Reports – reports from Vista Server.
•VistaDb – the Vista database.
•VistaGraphics – Vista graphics files.
Once the engineering work is finished, the complete project folder is
transferred from the engineering PC to the site PC. Save the folder
structure as a compressed file (*.zip) to avoid problems with the readonly attributes when storing on a CD.
Schneider Electric Buildings, Dec 201119 (126)
04-00035-02-en (EN)
2 Planning the Project TAC Xenta, TAC Xenta 120
2.2Case Study
The following chapters describe how to configure and add a TAC Xenta
120 to a LonWorks network using TAC ZBuilder. Our network example is based on the case described below.
2.2.1Description of Facility
We are creating a system for a fictional company that we call ACME
Inc.
The facility is a typical, small two-story office building, served by packaged rooftop equipment. The first floor area serves Marketing,
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. This unit has central station cooling
and central station heating. The space is divided into control 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. A laboratory within the
engineering area is temperature-controlled by a fan-coil unit. The staff
can supervise the system from a PC-based presentation system.
20 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
TAC Xenta, TAC Xenta 1202 Planning the Project
RTU1
RTU3
RTU2
RTU4
Engineering
Support
Lobby
Accounts
Conference Room
Marketing and Management
Lobby
Conf_Room
2.2.2Device Description and Naming Convention
Within the first floor area, the rooftop unit serving the Accounting area
is controlled by a Xenta 301, called RTU1.
The secondary air handling unit serving Marketing and Senior Management is controlled by a Xenta 281, called Conf_Room.
The rooftop unit serving Marketing and Senior Management is controlled by a Xenta 401, called RTU2, using four I/O modules.
The air handling unit serving the lobby area is controlled by a Xenta
104, called Lobby.
Within the second floor area, the rooftop unit serving the Customer Support area will be controlled by a Xenta 104, named RTU3.
The rooftop unit serving the Engineering area is controlled by a Xenta
401, called RTU4, using five I/O modules.
The fan-coil unit in the engineering lab area is controlled by a Xenta
121-FC, called Engr_Lab, configured with TAC ZBuilder.
Schneider Electric Buildings, Dec 201121 (126)
04-00035-02-en (EN)
2 Planning the Project TAC Xenta, TAC Xenta 120
First FloorSecond Floor
RTU1
Xenta 301
Conf_Room
Xenta 281
Lobby
Xenta 104
RTU3
Xenta 104
RTU4
Xenta 401
RTU2
Xenta 401
Engr_Lab
Xenta 121-FC
VistaSRV1
Engr_lab
The PC where the presentation system is installed is called VistaSRV1
(in some pictures called VistaSrv_1, but the character “_” should be
avoided) and is located in the Support area.
2.2.3Devices in the Example
In our example, we use a part of the above network to illustrate how a
Xenta 120 is added.
On the second floor, we have selected the engineering lab fan-coil unit
to illustrate how to configure and install a TAC Xenta 120.
22 (126)Schneider Electric Buildings, Dec 2011
04-00035-02-en (EN)
TAC Xenta, TAC Xenta 1202 Planning the Project
First FloorSecond Floor
Engr_Lab
Xenta 121-FC
RTU4
Xenta 401
VistaSRV1
LTA Card
I/O Modules
(1 & 3)
Conf_Room
Lobby
LonWorks Group 1st_Floor_LW
Xenta Group 1st_Floor
Xenta Group 2nd_Floor
LonWorks Group 2nd_Floor_LW
Engr_Lab
We work with the following device:
2.2.4Network Structure and Naming Convention in the Example
When adding the Xenta 120 using Vista Workstation, the name of the
network is the name of the company – ACME_Inc. Since the building
has two floors, the network is built with the devices divided into two
Xenta groups called 1st_Floor and 2nd_Floor.
Xenta devices placed on the first floor belong to the Xenta group
1st_Floor and Xenta devices placed on the second floor belong to the
Xenta group 2nd_Floor.
The Xenta 104 is a member of the LonWorks group 1st_Floor_LW and
the Xenta 121-FC is a member of the LonWorks group 2nd_Floor_LW.
Schneider Electric Buildings, Dec 201123 (126)
04-00035-02-en (EN)
ZBuilder is a software tool designed to create a set of configuration
parameters for a specific application, for example a fan-coil with an
electric reheater or a heat pump with a reversing valve.
The parameters are saved in a configuration file which is used by TAC
Vista or LonMaker to install and commission the corresponding TAC
Xenta 120 controller.
For a thorough description of the tool and the working methods, please
refer to Chapter 5, “ZBuilder - the Configuration Tool”, on page 49, and
the other chapters in the Reference section of the manual.
In this chapter you will learn how to use ZBuilder to:
•Start ZBuilder stand-alone
•Select a configuration template
•Adjust the Configuration
•Specify an Exception Mode
•Configure the Inputs/Outputs
•Save and Document the Configuration
3.2Starting ZBuilder
ZBuilder can be run stand-alone, but can also be started as a plug-in
from TAC Vista or L
To start ZBuilder as a plug-in, the Xenta 120 must be added to a LonWorks network:
•For more information on how to start ZBuilder as a plug-in from
Vista Workstation, see Section 6.1.1, “Starting ZBuilder from
TAC Vista”, on page 57.
•For more information on how to start ZBuilder as a plug-in from
LonMaker, see Section 6.2.1, “Starting ZBuilder from LonMaker”, on page 58.
ONMAKER.
Schneider Electric Buildings, Dec 201125 (126)
04-00035-02-en (EN)
In the example, we start ZBuilder stand-alone to create the configuration file before the Xenta 120 is added to the Lonworks network.
To start ZBuilder as a stand-alone tool
•Click Start, point to All Programs, point to T A C, point to
TAC ZBuilder, and then click TAC ZBuilder.
The TAC ZBuilder Select File window now opens.
3.3Selecting a Template
To simplify the configuration procedure, you start with a template or
another configuration file similar to the application that you are going
to create.
For more information on how to select files, see Chapter 5.3.1, “Selecting a File”, on page 52.
In the example, you will start with a template for a 4-pipe fan-coil.
To select a Template
1In the Select File dialog box, make sure the Select from a list of
Templates option is selected.
2In the templates list select the required template. In the example,
FanCoil 4-pipe.zbt.
3Click OK.
3.4Adjusting the Configuration
Normally you need to adjust the default configuration for the current
application.
In the example, we will adjust the settings to achieve the following:
•The fan will always run for at least 30 seconds when the second
heating stage is turned off.
•When the window is opened, the controller will be turned off.
•Increase/decrease actuators need to be resynchronized. This can
be done towards the open or closed position. The specified direction will be used for all active increase/decrease actuators in the
configuration. The default value is Resync actuator towa rd
closed position. For more information, see Section 10.5, “Actuator Resync and End-points Adjustment”, on page 90.
•The Cooling icon in the tree to the left has been changed to a
green I/O icon.
You will now have a blue sloping line, showing how the valve will
open with increasing Terminal Load (increasing need of cooling).
5In the tree structure, select Sequences\Primary heating.
6In the Primary heating area, in the device type list, select the
required device type. In the example, Increase/decrease.
7Make sure the Hardwired output checkbox is selected.
Note that you will get a red sloping line, showing how the valve
will close with increasing Terminal Load (decreasing need of heating).