TAC impr oves indoor c limate
and reduces operating costs.
0-004-7516-1 (GB), 1999-08-18
Air flow
Heating
Changeover via
network variable
Cooling
Cooling
demand
Page 2
Page 3
TAC Xenta 102 HandbookForeword
Foreword
This is the technical handbook for the TAC Xenta 102 controller, a
zone controller for VAV applications in offices and other larger
buildings.
In this second edition of the handbook, sections that were earlier
complicated to the user, have been made clearer, and most of the
content has been reorganized. The trouble-shooting section has been
made into its own chapter, and there are now appendices in the end of
the handbook; one containing setpoint calculating examples, and one
containing a commissioning protocol which can be used together with
chapter 3 when commissioning.
The programs in TAC Xenta 102 now have new versions. For both the
system program and the application program in the controller, the
versions are 1.10. If there is a service replacement in the system, all
variable bindings—if the controller is run on a network—must be
remade when an older or newer version of the controller is fitted. Th is
is because the controller has got a new “Standard Program ID”. There
are also three new network variables.
This document contains information which is the property of TAC and is therefore only available for those using and maintaining TAC’s equipment. Disclosure,
reproduction or use of either the document or the information within for any other purpose are strictly prohibited.
TAC reservs the right to make necessary changes of and additions to the material.
Echelon, Lon, LonWorks, LonTalk, Neuron, 3150, LonMark and the LonMark logo are registered trademarks for Echelon Corporation, USA. TAC Xenta® is a
registered trademark for TAC AB in Sweden and other countries. All other trademarks are the property of their respective owners.
Revisions list
Part numberCommentEditorDate
0-004-7516-0First edition.KRRO1997-09-11
0-004-7516-1Second edition. System and application program in a newSUWA1999-08-18
3.3.6Function test ..................................................................................................................................... 3:10
5.2.6Control sequence with TAC Xenta 102-B ......................................................................................... 5:8
5.2.5Control sequence with TAC Xenta 102-EF and 102-VF .................................................................. 5: 8
5.3More about functions......................................................................................................................... 5:10
5.3.1Air flow control ................................................................................................................................ 5:10
5.3.2Heating and fan control ................................................................................................................... 5:11
5.3.3Air quality control ........................................................................................................................... 5:12
Appendix B: Commissioning protocol
Index
Reply form
2 (2), 0-004-7516-1 (GB)
TAC AB, 1999-08-18
Page 7
TAC Xenta 102 HandbookAbout this handbook
1Introduction
1.1The content of the handbook
•Chapter 1 Introduction,
gives an overview over the structure of this handbook,
additional information about the product, and has a short
terminology section.
•Chapter 2 The zone controller TAC Xenta 102,
briefly describes the wall module, the controller’s functions
and control examples of the three different models of TAC
Xenta 102.
•Chapter 3 Installation,
contains instructions on mechanical and electrical
installation of the controller, and instructions on
commissioning and network installation.
•Chapter 4 Configuration parameters,
describes the setting of the zone controller’s configuration
parameters.
• Chapter 5 Functional description,
gives detailed information about the zone controller’s basic
functions, operating modes, and other functions.
• Chapter 6 Trouble-shooting during operation and
commissioning,
contains trouble-shooting measures you can use to find and
remedy possible faults in the system.
• Chapter 7 Technical data,
lists all technical data and dimensions for TAC Xenta 102.
• Chapter 8 Communication,
describes the zone controller’s communication with other
units via the network by means of network variables.
• Appendix A, Setpoint calculation
contains calculating examples for the setpoint calculation in
chapter 5.
• Appendix B
contains a commissioning protocol, which can be used
together with chapter 3 during installation and
commissioning.
TAC AB, 1999-08-180-004-7516-1 (GB), 1:1 (4)
Page 8
TAC Xenta 102 HandbookAbout this handbook
• Index and Reply form,
are in the end of the handbook. Use the index to make your
search for information easier, and the reply form to let us
know whether there is something wrong or unclear in this
handbook.
1.2Documentation
Enclosed documentation
TAC Xenta 102 is delivered with an installation instruction for
each of the controllers below:
• TAC Xenta 102-B,
Installation instruction, part number 0FL-3857
• TAC Xenta 102-EF,
Installation instruction, part number 0FL-3859
• TAC Xenta 102-VF,
Installation instruction, part number 0FL-3861
Other documentation
There is additional information about TAC Xenta 102 in the
following documents:
• Data sheet for TAC Xenta 102-B,
part number 0-003-1611
• Data sheet f or TAC Xenta 102-EF,
part number 0-003-1617
• Data sheet f or TAC Xenta 102-VF,
part number 0-003-1623
• Data sheet for ZS 101–ZS 105,
part number 0-003-1661. Here the wall modules are described.
•TAC Xenta Network Guide,
part number 0-004-7460. Here you can find additional information on network installation.
• TAC Xenta OP Handbook,
part number 0-004-7506. Here you find information on how to
use TAC Xenta OP together with TAC Xenta 102 and the wall
modules.
• TAC Xenta, Zone System Guidelines
part number 0-004-7637. Here you find information on how a
zone system is built with TAC Xenta components.
•TAC Xenta 102 Handbook,
part number 0-004-7516-0. Here you find information on the
earlier version of the zone controller.
All the above mentioned documents can be found on the internet:
www.tac.se or they can be ordered from the nearest TAC service
point.
1:2 (4), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 9
TAC Xenta 102 HandbookAbout this handbook
1.3Terminology
In this handbook there are some abbreviations and terms which
are specific for the zone controller’s applications and network
communication. Therefore, the most common terms have been
gathered, together with a short explanation, in the list below.
neuron .................. communication processor with built-in
protocol
node ..................... communication unit on the network
SNVT ................... Standard Network Variable Type
nvixxx .................. variable which gets its value from another
unit on the network
nvoxxx ................. variable which value is sent out to another
unit on the network
ncixxx .................. configuration parameter; variable which gets
its value from another unit on the network
and which keeps it during a power failure
service pin ........... function which can be used during installation
on the network
wink ..................... confirmation that the connection to a controller
via the network is working (a light emitting
diode is lit for appr. 15 seconds)
LNS ...................... LonWork Network Services. System tool for
installation, configuration and maintenance of
LonWorks network
TAC AB, 1999-08-180-004-7516-1 (GB), 1:3 (4)
Page 10
TAC Xenta 102 HandbookAbout this handbook
This page is intentionally left blank.
1:4 (4), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 11
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
2The zone controller TAC Xenta 102
2.1General
The zone controller TAC Xenta 102 is intended for “Variable
Air Volume” (VAV) applications in offices and other large
buildings. A VAV controller usually controls the temperature in
a given zone by controlling the volume sub-tempered air which
is supplied to the zone.
The controller’ s basic functions
All controller models have a number of built-in functions which
handle the normal control situation. There are four operatingmodes to choose from (comfort, economy, bypass, and off) and
five modes to force the controller (only heating allowed, only
cooling allowed, night cooling, auto, and off).
Measuring the zone temperature is made by means of a
permanent thermistor sensor or a temperature node connected
to the network, and setpoint calculation is made according to
special methods.
There is a detailed functional description of all the basic
functions in chapter 5.2.
More about functions
Apart from the controller’s basic functions, there are
additional possibilities to control the climate in the zone. In
section 5.3, these are described in detail, and also which
external functions that may be connected, e.g. window contact
sensor and occupancy sensor.
TAC AB, 1999-08-180-004-7516-1 (GB), 2:1 (8)
Page 12
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
Communication possibilities
The controller can work either as a free-standing unit, without
being connected to a network during operation, or be a part of
a larger system with several other units such as TAC Xenta
300/400 and other zone controllers in the TAC Xenta family
(figure 2.1). A detailed description of how units work together
in a larger zone system, is found in “Guide lines for zone
applications”, part number 0-004-7637.
TAC Vista is an excellent tool for reading variables and as a
configuration tool during commissioning and/or operation.
When TAC Vista is not a part of the system, reading and
configuration of variables can be made from the operating
panel TAC Xenta OP, version 3.11 or later.
Figure 2.1 Zone controller in a larger system together with TA C Vista
2:2 (8), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 13
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
The controller is LONMARK® approved and communicates on a
LONTALK® TP/FT-10 network via a twisted-pair, unpolarized cable.
2.2Wall modules
Locking screw
COMFORT
Bypass key
ECONOMY
OFF
OP connection
Figure 2.2 Wall module in the ZS100 series
Position
indicator
Setpoint knob
In the controlled zone, there is usually a wall module from the
ZS 100 series, which measures the temperature. The wall
modules ZS 101–ZS 105 may very well be used together with
all controller models. On the wall module (figure 2.2) there are
among other things a setpoint knob and a bypass key with
setting possibilities.
The setpoint knob is used to adjust the zone temperature
setpoint with a maximum of ± 5 °C.
The bypass key is used to change the operating mode, and by
pressing the key, an internal timer in the controller, which runs
for two hours, is started. Read more about different operating
modes and ways to force the controller in sections 5.2.1–5.2.2.
On all ZS 100 wall modules, the current operating mode is
indicated by the position indicator (red light emitting diode) as
follows:
· Steady light:Comfort or bypass mode
· Slow flashing:Economy mode
· Fast flashing for appr. 15 s:Answer to “wink” command.
Confirmation that the OP is
connected to the correct
controller
· Off:Other operating modes
There is additional information on the wall modules and how the
temperatures can be adjusted locally in the zone by means of the
keys in “Data sheet for ZS 101–ZS 105”, part number 0-003-
1661.
TAC AB, 1999-08-180-004-7516-1 (GB), 2:3 (8)
Page 14
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
2.3Applications
2.3.1General
All models have this in common:
• they are intended for use together with a Belimo® VAV-Compact
air flow controller. TAC Xenta 102 sends air flow setpoints to the
VAV-Compact, and reads measured air flow from the air flow controller.
• they have air quality control as an option, which means that the
controller can control the air flow to keep down the carbon dioxide concentration in the zone. However, the function needs a carbon dioxide sensor to be connected to the controller, electronically or via the network.
• a window contact to stop the heating and cooling functions,
should a window be opened, can be connected. An occupancy
sensor can detect the presence of a person in the controlled zone
and change the controller from economy to comfort mode.
The window contact sensor, occupancy sensor, and air quality
control are described in detail in section 5.3.2–5.3.4.
2.3.2Air flow control only (TAC Xenta 102-B)
The controller controls the zone temperature by means of the
air damper via VAV-Compact. The air flow is minimum and
maximum limited. Usually the controller only uses one cooling
sequence (sub-tempered air in the duct), but it can be changed
to heating (hot air in the duct) given a central command.
Window
contact
Damper and air
flow controller
Wall
sensor
module
Carbon dioxide
Occupancy
sensor
Figure 2.3 Control application for TA C Xenta 102-B
2:4 (8), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 15
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
2.3.3Air flow control with modulating valve water reheat
(TAC Xenta 102-VF)
The controller controls the zone temperature by sequence controlling the air flow controller (VAV-Compact) and the heating coil.
The air flow is minimum and maximum limited. The heating
sequence controls the valve and minimum limits the air flow.
Wall
module
Carbon dioxide
sensor
Occupancy
sensor
Window
contact
Damper and air
flow controller
Heating
water coil
Valve and
actuator
Figure 2.4 Control application for TA C Xenta 102-VF
2.3.4Air flow control with modulating valve water reheat and fan
(TAC Xenta 102-VF)
The controller controls the zone temperature by sequence controlling the air flow controller (VAV-Compact) and the heating coil.
The airflow is minimum and maximum limited. The heating combines the valve control with the fan to increase the air circulation
through the heating coil.
Window
contact
Damper and air
flow controller
Fan
Heating
water coil
Wall
module
Carbon dioxide
sensor
Occupancy
sensor
Valve and
actuator
Figure 2.5 Control application for T A C Xenta 102-VF
TAC AB, 1999-08-180-004-7516-1 (GB), 2:5 (8)
Page 16
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
2.3.5Air flow control with one stage electric reheat (TAC Xenta
102-EF)
The controller maintains the zone temperature by sequence controlling the air flow controller (VAV-Compact) and the electric
heating coil. The air flow is minimum and maximum limited.
When heating, the controller controls the electric heating coil via a
relay in combination with setting the air flow to its minimum
value.
Window
contact
Damper and air
flow controller
Electric
heating coil
Wall
module
Carbon dioxide
sensor
Occupancy
sensor
Figure 2.6 Control application for T A C Xenta 102-EF
2.3.6Air flow control with one stage electric reheat and fan (TAC
Xenta 102-EF)
The controller controls the zone temperature by sequence
controlling the air flow controller (VAV-Compact) and the
electric heating coil. The air flow is minimum and maximum
limited. When heating, the controller controls the electric
heating coil by means of a relay in combination with the fan
running to increase the air circulation through the heating coil.
In this application (electric reheat + fan), the minimum limitation
may have separate settings for cooling and heating.
2:6 (8), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 17
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
Wall
Fan
module
Carbon dioxide
sensor
Occupany sensor
Window
contact
Damper and air
flow controller
El. heating
coil
Figure 2.7 Control application for T A C Xenta 102-EF
2.3.7Air flow control with thermo-actuator for radiators
(TAC Xenta 102-EF)
The controller controls the zone temperature by sequence
controlling the air flow controller (VAV-Compact) and the
themo-actuators for radiators. The air flow is minimum and
maximum limited.
Carbon dioxide
Window
contact
Damper and air
flow controller
Valve
Radiators
Figure 2.8 Control application for T A C Xenta 102-EF
Wall module
sensor
Occupancy
sensor
TAC AB, 1999-08-180-004-7516-1 (GB), 2:7 (8)
Page 18
TAC Xenta 102 HandbookThe zone controller TAC Xenta 102
This page is intentionally left blank.
2:8 (8), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 19
TAC Xenta 102 HandbookInstallation
3Installation
3.1Mechanical installation
3.1.1Fitting
TAC Xenta 102 can either be snapped onto a DIN rail (figure
3.1) or fastened with two screws to a level surface (figure 3.2).
On the controllers which controls equipment with 230 V supply,
a semi-protection which covers the relay terminals, should be
fitted (figure 3.3). A semi-protection is delivered together with
these controllers.
T o fasten the contr oller onto a DIN rail:
1. Place the controller on the top of the rail as is shown by arrow 1.
2. Turn the controller downwards until it snaps onto the rail as
is indicated by arrow 2.
3. To remove, place a screwdriver in the lock on the bottom of
the controller and pull down. Then it is possible to lift the
controller diagonally upwards and off the rail.
Figure 3.1 TA C Xenta 102 fastened on a DIN ra il
TAC AB, 1999-08-180-004-7516-1 (GB), 3:1 (10)
Page 20
TAC Xenta 102 HandbookInstallation
Fastening the controller on a level surface:
Use the two sockets provided for fastening the controller; the
maximum screw size is M4 or ST 3,5. The head of the screw
should not exceed 7,5 mm in diameter.
Figure 3.2 TA C Xenta 102 f astened on a le v el surface
T o fit the semi-protection:
When the cables are secured, the protection is fitted by means of
the enclosed screw.
Figure 3.3 Fitting the semi-protection
3:2 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 21
TAC Xenta 102 HandbookInstallation
3.2Electrical installation
3.2.1General
Warning! All 230 V supply cables must be
!!
1. Each controller or group of controllers must be fitted with
max. 6 A fuses.
2. Secure the cables to the controller by means of clamps or
similar, to limit their mobility.
3. Wire straps or shrinking tubing must prevent loose 230 V
cables from getting in contact with ELV cables—supply or
signal cables—and vice versa.
4. It must be simple to break the power supply for the
controller or for the complete installation.
5. When several Xenta controllers are supplied from a
common transformer, it is important that all G’s are
connected with each other and that all G0’s are connected
with each other. They must not be interchanged. An
important exception
connected with the other G0’s. Instead it should be
connected to the terminal OP on the controller. At the
transformer, G0 should be connected to protective earth.
This is to get an grounding point for interference diversion.
installed by authorised electricians.
: G0 on the wall module should not be
6. Connect the two M terminals to the wall module to get the
specified measuring accuracy for the room temperature.
Safety standard
Transformers supplying the controller must comply to the safety standard EN 60 742 or any other relevant safety standard
for ELV, 24 V AC. When equipment with a power supply of its
own is connected, e.g. an occupancy sensor, this power supply
must also comply with this norm.
Cable lengths
For information on communication cable lengths, see TAC
Xenta Network Guide, part number 0-004-7460. For all other
cables, maximum length is 30 m and min. area is 0,7 mm
2
.
Wall modules ZS 101–ZS 104
It is mainly the wall modules ZS 101–ZS 104 which are intended for use together with TAC Xenta 102. The wall module ZS
105 can also be used, but then the fan switch on this unit is not
used. The wiring diagrams on the following pages show how wiring with ZS 104 should be done, as this is the model that has all
connections.
TAC AB, 1999-08-180-004-7516-1 (GB), 3:3 (10)
Page 22
TAC Xenta 102 HandbookInstallation
Connection terminals
The designation of the connection terminals can be seen in two
places on the controller: on the edge of the printed circuit board,
and on the label on the front of the controller.
TerminDesign. FunctionType
no.
1C1TP/FT-10 communication channel2C2TP/FT-10 communication channel-
*1
3
4MMeasurement neutral-
*1
5
*1
6
7MMeasurement neutral-
8Z1Air flow from VAV-CompactAnalogue input
9D1LED on wall moduleDigital output
10MMeasurement neutral11X1Bypass key on wall moduleDigital input
13MMeasurement neutral14B1Room temperature sensorThermistor input
15G24 V AC (G)Input
16G024 V AC (G0)Input
*2
17
OP24 V AC supply for TAC Xenta OP-
18G24 V AC supply for TAC Xenta OP19V 1Fan on/off (102-EF and 102-VF)
20G24 V AC (G) supply for V1 and V2Output
21G024 V AC (G0)Output
22Y 2Control signal 0–10 V for heatingAnalogue output
valve (only 102-VF)
23MMeasurement neutral24Y1Control signal, air flow controllerAnalogue output
25—Not in use26—Not in use27K 1On/off, electric heating coil or
thermo-actuator (only 102-EF),
24 V or 230 V ACRelay
28K C1Supply for K1-
*1
See chapter 4 Configuration parameters
*2
Connected alone to G0 on the wall module. Must not be connected to G0 on
the controller.
3:4 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 23
TAC Xenta 102 HandbookInstallation
3.2.2Wiring of TAC Xenta 102-B
Note! Read section 3.2.1 “General” before you connect the
cables according to the wiring diagram in figure 3.4.
LONT
ALK
TP/FT-10
1516171819202122232425262728
®
Junction box
Wall module
Window
contact
Occupancy
GW1GQ1GX1
1234567891011121314
C2X3MMMMZ1X1R1B1
sensor
X2
+–
Z2
Carbon dioxide
sensor e.g. GKD 2001
V... 24 V AC/DC
10)(9
ZS 104
6
7
D1C1
5
1
3
2
Xenta 102-B
G0
G
OPV1Y1
GG
G0
M
C1
G
C2
G0
13
Belimo
VAV-Compact
2
5
Air flow controller
with damper
24 V AC (G)
24 V AC (G0)
Figure 3.4 Wiring of TA CXenta 102-B
TAC AB, 1999-08-180-004-7516-1 (GB), 3:5 (10)
Page 24
TAC Xenta 102 HandbookInstallation
3.2.3Wiring of TAC Xenta 102-EF
Note! Read section 3.2.1 “General” before you connect the
cables according to the wiring diagram in figure 3.5.
LONTALK
TP/FT-10
1516171819202122232425262728
®
Junction box
Wall module
Occupancy
contact
sensor
Carbon dioxide
+–
Z2
X2
sensor, e.g. GKD 2001
V... 24 V AC/DC
10)(9
ZS 104
6
7
D1C1
5
1
3
2
Window
GW1GQ1GX1
1234567891011121314
C2X3MMMMZ1X1R1B1
Xenta 102-EF
G0
G
OPV1Y1
GG
G0K1 KC1
13
M
Belimo
On/off, fan
VAV-Compact
2
5
Air flow
controller with
Electric
heating
coil
damper
27 28
24 V AC
C1
G
C2
G0
!
230 V AC (L)
230 V AC (N)
CAT III
(IEC 664)
Class II
(EN 61010-1)
Thermal actuator,
e.g. TSE 150 NC/NO
24 V AC (G)
24 V AC (G0)
Figure 3.5 Wiring of TACXenta 102-EF
3:6 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 25
TAC Xenta 102 HandbookInstallation
3.2.4Wiring of TAC Xenta 102-VF
Note! Read section 3.2.1 “General” before you connect the
cables according to the wiring diagram in figure 3.6.
LONT
ALK
TP/FT-10
1516171819202122232425262728
®
Junction box
Wall module
Window
contact
Närvaro-
givare
Koldioxidgi vare,
t.ex. GKD 2001 V...
24 V A C/DC
GW1GQ1GX1
10)(9
+–
1234567891011121314
Z2
C2X3MMMMZ1X1R1B1
X2
6
7
D1C1
5
ZS 104
3
1
2
Xenta 102-VF
G0
G
OPV1Y2Y1
GG
G0
M
C1
G
C2
G0
13
G G0 X1/X2M
Belimo
On/off,
fan
EM52L
Actuator, water
heating coil
VAV-Compact
2
5
Air flow
controller with
damper
24 V AC (G)
24 V AC (G0)
Figure 3.6 Wiring of TA C Xenta 102-VF
TAC AB, 1999-08-180-004-7516-1 (GB), 3:7 (10)
Page 26
TAC Xenta 102 HandbookInstallation
3.3Commissioning
3.3.1General
When the mechanical and electrical installation has been made,
you can commission the controller. This means:
·Installing the controller on the network, set node status
and give it an address.
·Set the controller's configuration parameters.
·Bind network variables.
·Test the function.
When it comes to commissioning of complete zone systems,
read the manual “TAC Xenta–Zone Systems Guideline”. Here
you will find a short description of what to do and when to do
it. In short: you could use TAC Xenta OP for setting the basic
parameters. Use a network management tool or TAC Vista for
commissioning the controller on the network and do the rest of
the commissioning.
3.3.2Node status
When TAC Xenta 100 should be used stand-alone, this is how:
1. Set node status to “Configured” with TAC Xenta OP.
2. Set the basic parameters with TAC Xenta OP.
3. Set the other parameters and variables with TAC Xenta
OP.
You could also use a network management tool for the commissioning.
The node status indicates which mode the controller is in, when
it comes to network configuration and program. The status can
be changed with TAC Vista (version 3.1 or later), network
management tool, or, to some extent, TAC Xenta OP. The
controller can be in these states:
Unconfigured
The controller is in this state when delivered from the factory.
Neither the program nor the network communication are
running. The service light emitting diode is flashing.
The controller cannot work on a network in this state. To do
so, it must be in configured, online state, see below.
You cannot set configuration parameters or network variables
in this state.
3:8 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 27
TAC Xenta 102 HandbookInstallation
Configured, online
By means of TAC Xenta OP, TAC Vista or a network
management tool, the status can be changed to configured.
Then, both the program and the network communication are
running. The service LED is off. This is the normal state for a
controller in operation.
Now the controller uses the address which it was given by the
tool during configuration. With TAC Xenta OP you cannot,
however, set an address. Therefore all controllers get default
addresses. This means that such a TAC Xenta 100 cannot
work on a network. It can only work stand-alone.
In this state you can set parameters and variables.
Configured, soft online
To get the controller into this state, you need a network
management tool. The controller has a program and a network
configuration, but the program and the communication are at a
standstill. The light emitting diode is off. If the controller is
reset, it will go into configured, online.
Configured, hard online
To get the controller into this state, you need a network
management tool. The controller has a program and a network
configuration, but the program and the communication are at a
standstill. The light emitting diode is off. If the controller is
reset, it will remain in this state.
Without a program and not configured
This states indicates that there is something wrong with the
controller. No program can be detected. The light emitting
diode is lit.
3.3.3Configuration parameters (nci’s)
TAC Xenta 100 has a number of configuration parameters,
where you can set how the controller should be working. Read
about them in chapter 4. There are also network variables
which controls the controller during operation.
Use the commissioning protocol in Appendix B to write down
your settings at commissioning. In chapter 8, there is
information on all parameters and variables, such as their
index, accepted values, default values. There are detailed
descriptions of the parameters and variables in chapter 4, 5,
and 6.
TAC AB, 1999-08-180-004-7516-1 (GB), 3:9 (10)
Page 28
TAC Xenta 102 HandbookInstallation
3.3.4Network installation
For network installation, you need a network management tool
(LNS based or not). Examples of network management tools
are MetraVision and LonMaker for Windows. Here you find
brief information on how this is made. You find more
information in “TAC Xenta, Guidelines for zone applications”.
The installation has two steps:
1. Feed information about the controllers’ unique neuron-ID
into the network management tool’s data base.
2. Let the network management tool install the controller on
the network. The controller will then also get an address.
There are two ways to feed the neuron-ID into the data base:
1. Manually feed the neuron-ID into the network management
tool. To make this easier you can use a bar code reader to
read the detachable ID-neuron label, which you find on all
controllers. It is convenient to gather these labels when you
go around and make the basic configuration, and stick them
to a form, drawing or similar. In the manual “TAC Xenta,
Guidelines for zone applications” there is a form for this
purpose.
2. Use the service pin function. You can only do this when the
controller is connected to the network. On the controller
there is a service pin key in a hole in the upper left corner, at
terminal C1. When you push this, the controller sends out its
neuron-ID. The network management tool can then read the
neuron-ID from the network, to save it in its data base.
3.3.5Network variable binding
How binding is done depends on which network management
tool is used. To get exact information, you should use the tool’s
documentation. In “TAC Xenta Network manual”, there is
however a description of how network variables are bound
with Metra Vision.
To bind network variables is not an issue when the controller is
used in stand-alone operation.
3.3.6Function test
You should also make sure that the control works as intended.
In chapter 5 all the controller’s functions are described.
In chapter 6 you find help, should a problem occur.
3:10 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 29
TAC Xenta 102 HandbookConfiguration parameters
4Configuration parameters
All communication with the controller is made by means of
network variables. nci’s are used to configure the controller,nvi’s controls the controller during operation, and nv o’s are
output variables, which the controller sends out on the network.
nci’s are normally set during commissioning, and are not
altered during normal operation (the parameters are stored in
a special memory, and can be changed a maximum of 10 000
times). In chapter 8, there is detailed information on accepted
values and default values for all parameters. All configuration
parameters have default values on delivery.
TAC AB, 1999-08-180-004-7516-1 (GB), 4:1 (4)
Page 30
TAC Xenta 102 HandbookConfiguration parameters
4.1Basic parameters
nciAppOptions
These parameters are used to set selectable functions in the controller. The parameter consists of 16 bits, where each bit
represents one functional choice. The bits 10 through 14 are
not used. When you look at nciAppOptions with TAC Xenta OP,
bit 0 is shown to the left.
There is an overview of all the bits’ functions in table 4.1 below.
Table 4.1 The function of different bits in nciAppOptions.
Bit no. Function
Bit 00Occupancy sensor not connected, terminal X2
1Occupancy sensor connected, terminal X2
Bit 10Energy hold off device (window contact) not connected,
terminal X3
1Energy hold off device (window contact) connected,
terminal X3
Bit 20Cooling sequence only disabled (only valid for
TAC Xenta 102-B)
1Cooling sequence only enabled (only valid for
TAC Xenta 102-B)
Bit 30Fan disabled
1Fan enabled (not valid for TAC Xenta 102-B)
Bit 40Ther mo-actuators normally closed (NC) (only valid for TAC
Xenta 102-EF)
1Ther mo-actuators normally open (NO) (only valid for TAC
Xenta 102-EF)
Bit 50Air quality control disabled
1Air quality control enabled
Bit 60Electric heating coil (only valid for TAC Xenta 102-EF)
1Thermo-actuator for radiators (only valid for
TAC Xenta 102-EF)
Bit 70Slave mode disabled
1Slave mode enabled
Bit 80Occupancy sensor: closed contact indicates occupancy
1Occupancy sensor: open contact indicates occupancy
Bit 90If
setpoints for the comfort and economy modes are
calculated using method B (see section 5.2.4).
1If
setpoints for the comfort and economy modes are
calculated using method A (see section 5.2.4).
nviSetpoint
nviSetpoint
has a valid value, the heating/cooling
has a valid value, the heating/cooling
Bit 15Reserved for production test. Should not be altered!
Bits 10 through 14 are not used.
4:2 (4), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 31
TAC Xenta 102 HandbookConfiguration parameters
4.2Other configuration parameters
The controller’s other configuration parameters are listed below together with a short description. See also chapter 8.
T ab le 4.2 Configuration parameters.
IndexNameDescription
0
nciLocation
25
nciSetpoints
26
nciSpaceTempDev
27
nciSpaceTempLow
28
nciVAVGain
29
nciVAVItime
30
nciGainHeat
31
nciItimeHeat
32
nciSpaceTempOfst
33
nciMinFlow
34
nciMaxFlow
35
nciMinFlowHeat
36
nciMinFlowStand
37
nciNomFlow
38
nciFlowOfstSlave
Location label
Occupancy temperature setpoints
Max. deviation of zone temperature
Low limit of zone temperqature
Gain fo VAV
Integral time for VAV
Gain for heating controller
Integral time for heating controller
Zone temperature sensor adjustment
Minimum flow
Maximum flow
Minimum flow heating
Minimum flow standby
Nominal flow
Flow offset for slave
39
nciCO2PerVolt
40
nciSpaceCO2Low
41
nciSpaceCO2High
44
nciHeatPrimMin
45
nciInstallType
46
nciSndHrtBt
47
nciRcvHrtBt
Conversion factor ppm CO2 per volt
Space CO2 level for closed damper
Space CO2 level for open damper
Minimum output heating controller
Network configuration source
Send heartbeat
Receive heartbeat
nciLocation
The parameter is used for naming the place where the controller is installed. In the operating panel, this parameter is shown
as the first variable (see section 8.1).
nciSetpoints
The parameter is used for setting the setpoint temperatures for
heating and cooling in comfort and economy mode (see section
5.2.1 and 5.2.4).
nciSpaceTempDev
The parameter is used for setting the maximum allowed deviation of the zone temperature (see section 5.3.7). Default value 2
°C.
nciSpaceTempLow
The parameter is used for setting the lowest allowed zone temperature (see section 5.3.7). Default value 10 °C.
nciV AVGain, nciGainHeat
The parameters give the cooling and heating sequence gain. Default value 25.
TAC AB, 1999-08-180-004-7516-1 (GB), 4:3 (4)
Page 32
TAC Xenta 102 HandbookConfiguration parameters
nciIV A Vtime, nciItimeHeat
The parameters holds the integral time for the cooling and heating sequence gain. Default value 900 s (15 min).
nciSpaceTempOfst
The parameter is used for adjusting the temperature setpoint.
Default value 0.0 °C.
nciMinFlow, nciMaxFlow
The parameters are used for setting the minimum and maximum flow allowed. Default values 0 l/s and 65535 l/s.
nciMinFlowHeat, nciMinFlowStand
The parameters are used for setting the min. flow allowed at active
heating (only relevant for applications with electrical reheat but
without a fan) and standby respectively. Default value 0 l/s.
nciFlowOfstSlave
The parameter is used for adjusting the flow of the slave controller (see section 5.3.8). Default value 0 l/s.
nciCO2PerVolt
The parameter is used for setting a conversion factor for the
signal from the carbon dioxide sensor to a concentration in
ppm. Default value 200 ppm/V.
nciSpaceCO2Low, nciSpaceCO2High
The parameters are used for setting the air quality control limits (se section 5.3.3). Default value 400 and 1000 ppm.
nciHeatPrimMin (only TAC Xenta 102-VF)
The parameter is used for setting the smallest heating valve
opening allowed (se section 5.3.6). Default value 0%.
nciInstallType
The parameter is used only at free-standing operation and is set
to show that the node should define its own address (see section
8.5.3).
nciSndHrtBt
The parameter is used for determining how often the nvo’s,
which are transmitted continuously on the net, should be sent
(see section 8.3).
nciRcvHrtBt
The parameter is used for determining how long time max. there may be between updating those nvi’s, for which the controller expects continuous updating (see section 8.3).
4:4 (4), 0-004-7516-1 (GB) TAC AB, 1999-08-18
Page 33
TAC Xenta 102 HandbookFunctional description
5Functional description
5.1General
The controller’s function is determined by its node status
(section 3.3.2), different operation modes (section 5.2.1) and the
ways to force the controller (section 5.2.2) for well-adapted
zone temperatur control. The controller measures the zone
temperature and uses different methods to calculate setpoints.
The air flow is controlled by an external air flow controller.
Apart from the basic functions in chapter 5.2, the controller
has a number of other possibilies to control the climate in the
zone. There are information about these functions in chapter
5.3.
Each section in this chapter is ended with information on which
network variables are used in the current control situation. If
you need details about the network variables’ characteristics,
such as default values and accepted values, you find this in
chapter 8.
TAC AB, 1999-08-180-004-7516-1 (GB), 5:1 (16)
Page 34
TAC Xenta 102 HandbookFunctional description
5.2The controller’s basic functions
5.2.1Operation modes
The controller has four selectable operation modes:
• Comfort
• Economy
• Bypass
• Off
The operation mode is controlled by nviManOccCmd, but is also
influenced by occupancy sensors and the bypass key on the wall
module. The connection between these is shown in table 5.1.
There you also find the controller’s values during stand-alone
operation.
T a ble 5.1 The relation betw een desired operation mode, bypass timer , occupancy sensor and current
operation mode.
Desired op. modeBypass timer
nviManOccCmdoperation mode
ComfortEnabledWithout signific.ComfortOC_OCCUPIED
At a standstillOccupancy detect.ComfortOC_OCCUPIED
OC_OCCUPIEDNo occupancyEconomyOC_STANDBY
1
Occupancy sensor2Current
nvoEffectOccup
EconomyEnabledWithout signific.BypassOC_BYPASS
OC_STANDBYAt a standstillWithout signific.EconomyOC_STANDBY
OffEnabledWithout signific.BypassOC_BYPASS
OC_UNOCCUPIED At a standstillWithout signific.OffOC_UNOCCUPIED
At a standstillOccupancy detect.ComfortOC_OCCUPIED
OC_NULNo occupancyOffOC_UNOCCUPIED
1
Activated by the bypass key on the wall module
2
See section 5.3.5 about occupancy sensors
Comfort mode
This is the default mode, when someone is in the zone, and the
controller should give the room a comfortable climate. The
controller is in this mode when nviManOccCmd=OC_OCCUPIED (or OC_NUL after a power down).
The LED on the wall module is lit with a steady red light and
you can use the setpoint knob on the wall module to make a
manual setting and air quality control is enabled. The setpoints
used are found in nciSetpoints (can be modified).
The alarms for the zone temperature deviation, high carbon
dioxide levels, and flow deviation can cut out, but the alarms
for window contact and low zone temperature are blocked.
5:2 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 35
TAC Xenta 102 HandbookFunctional description
Economy mode
In economy mode, the controller lowers the energy
consumption in the zone by using the heating and cooling
setpoints for economy in nciSetpoints (could be modified). The
controller is in this mode when nviManOccCmd =
OC_STANDBY and the bypass key has not been pressed.
The LED of the wall module flashes slowly. The bypass key can
be used, and also the setpoint knob, if you want to make a
manual setting.
The alarms for the zone temperature deviation, high carbon
dioxide levels, and flow deviation are blocked, but the alarms
for low zone temperature and window contact can cut out.
Bypass mode
The bypass key on the wall module is used if you want to turn
to comfort mode occasionally from economy or off mode.
When someone presses the bypass key on the wall module, the
bypass timer is started and the controller turns to bypass mode.
The bypass timer runs for two hours, and after those two hours
the controller changes operation mode according to table 5.1.
The controller’s bypass mode acts as the comfort mode during
those two hours. Both setpoints and alarms work as in comfort
mode.
Off mode
When the zone is not used for a longer period of time, the controller can be set in off mode. The controller is in this mode
when nviManOccCmd=OC_UNOCCUPIED.
The light emitting diode on the wall module is out. The setpoint
knob is blocked, but the bypass key is not. The alarms for the
zone temperature deviation, high carbon dioxide levels, and
flow deviation are blocked, but the alarms for low zone
temperature and window contact are enabled.
Index Variable nameDescription
1
nvoEffectOccup
13
nviManOccCmd
nciSetpoints
25
Effective occupancy output
Occupancy scheduler input
Occupancy temperature setpoints
TAC AB, 1999-08-180-004-7516-1 (GB), 5:3 (16)
Page 36
TAC Xenta 102 HandbookFunctional description
5.2.2Operation mode, manual mode and emergency mode
TAC Xenta 102 is designed to control both heating and cooling,
and to switch automatically between heating and cooling.
Heating
case
Heating
setpoint
Cooling
setpoint
Cooling
case
Cooling
demand
Figure 5.1 Changeover between heating and cooling cases.
It is possible to force the controller to heating only, cooling
only or night cooling. This is done with nviApplicMode,
according to the table below.
T a ble 5.2 The relation between nviApplicMode and f orcing.
nviApplicMode
HVAC_AUTOAutomaticThe controller automatically changes over between heating
HVAC_HEAT
HVAC_COOLCooling onlyThe controller can only cool. The heating setpoint is
ForcingDescription
(no forcing)and cooling by controlling with heating and cooling setpoints.
Heating onlyThe controller can only heat. The cooling setpoint is
neglected.
neglected.
HVAC_NIGHT_
PURGEcompletely open.
HV AC_OFFOffThe controller neither cools nor heats.
Night coolingThe controller can only cool with night air and the damper is
Manual mode
In this mode, the air flow can be set manually by means of
nviManOverride. The variable has three values, see the table
below. The heating sequence is disabled. The manual mode has
a higher priority than operation and operation mode.
T ab le 5.3 The relation betw een nviManOverride and forcing.
nviManOverride
HVO_OFFNormal operation
HVO_FLOW_VALUEOptional flow is set (l/s)
HVO_PERCENTThe damper is set to desired position (%)
5:4 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Description
Page 37
TAC Xenta 102 HandbookFunctional description
Emergency mode
In an emergency, the controller can force the damper to
completely opened or closed by means of nviEmergCmd, see the
table below. The heating sequence and the fan are disabled. The
emergency mode has a higher priority than all other modes.
T able 5.4 The relation between nviEmergCmd and f orcing.
nviEmergCmd
EMERG_NORMALNormal operation
EMERG_PURGECompletely open damper (100%)
EMERG_SHUTDOWNCompletely closed damper (0%)
EMERG_PRESSURIZECompletely open damper (100%)
EMERG_DEPRESSURIZECompletely closed damper (0%)
You can measure the zone temperature either with the wall
module (thermistor sensor) or with a LonTalk temperature
sensor node connected to nviSpaceTemp. If nviSpaceTemp has a
valid value, the controller will use this, otherwise the thermistor
value will be used. The thermistor value (or via the network)
can be adjusted by nciSpaceTempOfst having received a value;
this is added to the thermistor value. The value the controller
uses is also put out on nvoSpaceTemp. If neither value is valid,nvoSpaceTemp gets the off value. nvoSpaceTemp is sent out
when it has changed at least 0,1°C.
Index Variable nameDescription
5
nvoSpaceTemp
15
nviSpaceTemp
32
nciSpaceTempOfst
TAC AB, 1999-08-180-004-7516-1 (GB), 5:5 (16)
Zone temperature output
Zone temperature input
Zone temperature sensor adjustment
Cooling setpoint comfort10 °C35 °C23 °C
Heating setpoint comfort10 °C
Cooling setpoint economy10 °C35 °C25 °C
Heating setpoint economy10 °C
1
If the cooling setpoint is 10 °C, the heating setpoint is set to 9,5 °C.
1
1
The smallest accepted deviation between the heating and cooling
setpoints is 0,5 °C, and the heating setpoints must be lower than
the cooling setpoints. If the heating setpoints are higher or equal
to the cooling setpoints, the controller resets the heating setpoint
to 0,5 °C lower than the cooling setpoint. Table 5.2 shows accepted values and default values for the four temperature setpoints in
nciSetpoints.
35 °C21 °C
35 °C19 °C
The setpoints for comfort and economy mode are basic
setpoints, which can be changed with nviSetpoint,nviSetPntOffset and the setpoint knob.
Calculation
The current setpoint, nvoEffectSetpt, depends on the current op-
eration, nvoUnitStatus, the desired operation mode, nviApplic-
Mode, and nviSetpoint, nviSetpntOffset, nciAppOptions, nciSetpoints and a possible local setpoint adjustment via the wall
module. Figure 5.2 shows an overview over the relation
between the variables used for setpoint calculation.
nviSetpoint is used to allow the temperature setpoints in comfort
and economy mode to be changed via the network. If there is a
valid value on nviSetpoint, the controller calculates the setpoints
for comfort and economy mode with method A or method B
(the methods are described in Appendix A). The choice of
method is made via nciAppOptions, bit 9. If bit 9=0 method B is
used, and if 9=1 method A is used. If there is no valid value on
nviSetPoint, no recalculation of the temperature setpoints in
nciSetpoints is made.
5:6 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 39
TAC Xenta 102 HandbookFunctional description
nviSetPntOffset can be r egarded as a setpoint adjustment from a
wall module connected to the network. Its value is added to
setpoints for comfort and economy mode.
In Appendix A there are detailed calculation examples of
setpoint calculation.
Figure 5.6 The relation between variables for the setpoint calculation.
nviSetpntOf fset
Wall module
setpoint knob
nviSetpoint
nciAppOptions bit 9
1
Calculation
according to
method A or B
nciSetpoints
Comf., ool.setp.
2
Comf., heat.setp.
Econ., cool.setp.
if nviSetpoint
has a valid
2
value, otherwise
no recalculation
AdditionAddition
Econ., heat. setp.
1
The wall module’s setpoint knob only affects comfort and economy mode.
2
In comfort mode, the setpoints for method A and method B are the same.
Unit status output
Effective setpoint output
Application mode input
Temperature setpoint input
Setpoint offset input
Application options
Occupancy temperature setpoints
nvoEffectSetpt
TAC AB, 1999-08-180-004-7516-1 (GB), 5:7 (16)
Page 40
TAC Xenta 102 HandbookFunctional description
5.2.5Control sequence with TAC Xenta 102-B
The controller changes between the heating and the cooling
sequence by a central command from the network. The heating
sequence is enabled when the variable nviApplicMode has the
value HVAC_HEAT. The cooling sequence is enabled when
nciAppOptions bit 2=1 or when the variable nviApplicMode has
the value HVAC_AUTO, HVAC_COOL or HVAC_NIGHT_-PURGE. The diagram below shows the heating and the cooling
sequence for TAC Xenta 102-B:
Air flow
max.
Heating
Changeover via
network variable
Cooling
min.
Figure 5.3 Control sequence for TAC Xenta 102-B
Index Variable nameDescription
14
nviApplicMode
24
nciAppOptions
Application mode input
Application options
Cooling demand
5.2.6Control sequence with TAC Xenta 102-EF and 102-VF
The air flow (cooling) and an electric heating coil or radiators for
TAC Xenta 102-EF or a heating water coil for TAC Xenta 102-VF
sequence controls the temperature. When the cooling sequence
should be run, the controller calculates an air flow setpoint to
VAV-Compact. Then the air flow controller sets the air flow to the
desired flow.
If the heating sequence should be run, the controller sets an
output to the heating coil, the thermo-actuators or the heating
valve. The air flow is set to a minimum value.
If the controller has a fan as an option, the fan is on when the
heating valve is open in TAC Xenta 102-VF or the electric
heating coil is on in TAC Xenta 102-EF.
The diagrams below illustrates the fan’s function for the
different control sequences.
5:8 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 41
TAC Xenta 102 HandbookFunctional description
Air flow
100%
max.
min.
Air flow
TAC Xenta 102-EF
100%
max.
min. heat.
min.
Air flow
100%
max.
0%
0%
Heating
Heating
Heating
Fan enabled
Cooling
Cooling
demand
Fan disabled
Cooling
Cooling
demand
Fan enabled
Cooling
min.
0%
Air flow
TAC Xenta 102-VF
100%
max.
Heating
Fan disabled
Cooling
min. heat.
min.
0%
Figure 5.4 Control sequence for TAC Xenta 102-EF and TA C
Xenta 102-VF
Cooling
demand
Cooling
demand
TAC AB, 1999-08-180-004-7516-1 (GB), 5:9 (16)
Page 42
TAC Xenta 102 HandbookFunctional description
5.3More about functions
5.3.1Air flow control
The air flow is controlled by an external air flow controller, for
example Belimo™ VAV-Compact. The air flow controller gets
a setpoint from the VAV controller.
VAV controller
Type:PI
Gain:0-32,75; default value: 25
I-time:0-60 minutes; default 15 minutes
Dead band:0,2 °C
Control interval:60 s
Air flow setpoints
Either one of the output Y1 (0–10 V), or nvoFlowSetpoint, which
represent the flow in per cent, can be used for the setpoint.
nvoFlowControlPt, is the desired flow in l/s.
Air flow monitoring
TAC Xenta 102 receives the current air flow values from the
air flow controller, by means of input Z1 (0–10 V) or nviBoxFlow.
The controller uses the air flow measurement to monitor deviations. Current air flow can be read by means of the network variable nvoBoxFlow. The above also applies to the slave mode.
Air flow limits
Air flow is limited in comfort and standby mode. The maximum
flow limit nciMaxFlow is used during normal operation. The mini-
mum flow limit nciMinFlowHeat is used when the electric heating
coil is enabled and there is no fan. If radiators are used or the
electric heating coil is on and a fan is used, then nciMinFlow is
used instead. The controller uses the minimum flow limit nciMin-FlowStand in standby mode.
Nominal air flow
The configuration parameter nciNomFlow defines the nominal
flow through the VAV box. Both the air flow setpoints and
limits depend on the correct value being set in nciNomFlow.
5:10 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 43
TAC Xenta 102 HandbookFunctional description
Index Variable nameDescription
2
nvoUnitStatus
6
nvoFlowControlPt
7
nvoBoxFlow
nvoFlowSetpoint
11
22
nviBoxFlow
28
nciVAVGain
29
nciVAVItime
33
nciMinFlow
34
nciMaxFlow
nciMinFlowHeat
35
36
nciMinFlowStand
37
nciNomFlow
Unit status output
Effective flow control output
Box flow output
Flow setpoint output
Box flow input
Gain for VAV
Integral time for VAV
Minimum flow
Maximum flow
Minimum flow heating
Minimum flow standby
Nominal flow
5.3.2Heating and fan control
TAC Xenta 102-B
TAC Xenta 102-B changes to heating sequence by means of a
command via the network. When there is a heating demand in the
zone, the controller increases the hot air flow in the zone; at a
cooling demand, the controller increases the cold air flow. For this
reason, it is not appropriate to mix Xenta 102-B with other Xenta
102 models in an installation where Xenta 102-B is to control a
heating application, as TAC Xenta 102-EF and VF heat subtempered air instead.
Heating controller (102-VF)
Type:PI
Gain:0–32,75; default value: 25
I-time:0–60 minutes; default 15 minutes
Neutral zone:0,2 °C
Control interval:60 s
TAC Xenta 102-EF
Heating control in Xenta 102-EF is a one-stage on-off system. The
heating output control, K1, can control either an electric heating
coil or a thermo-actuator. Which model is valid is set by nciApp-Options. If the electric heating coil is used then the control is
made with a hysteresis of ± 0,25 °C. If the thermal actuators for
radiators are used, the hysteresis is ± 0,1 °C.
When the heating sequence runs and the fan is enabled, both the
coil/radiators and the fan are on when there is a heating demand.
The controller starts the electric heating coil with a 60 second delay. The fan is turned off with a 120 second delay.
TAC AB, 1999-08-180-004-7516-1 (GB), 5:11 (16)
Page 44
TAC Xenta 102 HandbookFunctional description
TAC Xenta 102-VF
The heating sequence consists of control of the heating coil
combined with a minimum air heating flow, nciMinFlowHeat
(without a fan). A separate PI controller controls the heating
sequence.
Unit status output
Application options
Gain for heating controller
Integral time for heating controller
5.3.3Air quality control
In order to maintain a good air quality TAC Xenta 102
controls the supply of air to the controlled zone. If the carbon
dioxide (CO
controller increases the air flow to the controlled zone.
) sensor indicates a high concentration of CO2, the
2
The air flow is proportional to the CO
level and is calculated
2
as a linear function between [nciSpaceCO2Low, nciMinFlow]
and [nciSpaceCO2High, nciMaxFlow].
The air flow is set to the highest value of those coming from the
air quality control and the cooling controller according to
figure 5.5 below.
Air flow
nciMaxFlow
nciMinFlow
CO2 level
nciSpaceCO2LownciSpaceCO2High
Figure 5.5 Air quality control
The air quality control can be enabled independent of the cooling
controller and is enabled in comfort and bypass mode only.
The carbon dioxide concentration can be measured by means of a
permanent carbon dioxide sensor. The controller transforms the
analogue 0–10 V signal into a concentration in ppm by
muliplying it with the variable nciCO2PerVolt (ppm/volt).
Alternatively, you can use a LonTalk carbon dioxide measuring
node connected to the variable nviSpaceCO2. If nviSpaceCO2
has a valid value, the variable has a higher priority than the
electrically connected sensor.
5:12 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 45
TAC Xenta 102 HandbookFunctional description
Not to open or close the damper in vain, the CO2 level must differ
by more than ±30 ppm from the latest read value.
nvoSpaceCO2 shows current carbon dioxide level in the zone. If
nviSpaceCO2 has a valid value, the current carbon dioxide level
will be identical to the input.
Current CO2 level is always sent, no matter which options are
set in the variable nciAppOptions. Air quality control is enabled
when bit 5=1 in nciAppOptions.
Index Variable nameDescription
9
nvoSpaceCO2
18
nviSpaceCO2
24
nciAppOptions
33
nciMinFlow
nciMaxFlow
34
39
nciCO2PerVolt
40
nciSpaceCO2Low
41
nciSpaceCO2High
Zone CO2 sensor output
Zone CO2 input
Application options
Minimum flow
Maximum flow
Conversion factor ppm CO2 per volt
Zone CO2 for closed damper
Zone CO2 for open damper
5.3.4Window contact
TAC Xenta 102 is designed to be able to limit the energy consumption when a window in the room is open. You can connect
a local sensor directly to the controller, digital input X3, or use
nviEnergyHoldOff. The energy hold off is enabled when either
of these signals indicate an open window. The energy hold off is
made by the controller being set to off mode.
To be able to use a sensor (local or connected to the network),
bit 1 in nciAppOptions must be set to 1.
nvoEnergyHoldOff has the value of the locally connected sensor.
This is true even if bit 1 in nciAppOptions is set to 0.
If the energy hold off has been active for 60 seconds the window
contact alarm cuts out, bit 2 in nvoAlarmstatus (only in economyand off modes).
Alarm status output
Energy hold off output
Energy hold off input
Application options
There can be a sensor connected to TAC Xenta 102 to
determine whether someone is in the room or not. If there is no
occupancy sensor connected, the controller supposes that there
is always someone in the room. The controller uses the
information to determine whether the operation mode should be
comfort or economy. When the controller is used stand-alone,
the sensor is used to choose between comfort mode or off mode.
See table 5.1 in chapter 5.2.1.
TAC AB, 1999-08-180-004-7516-1 (GB), 5:13 (16)
Page 46
TAC Xenta 102 HandbookFunctional description
The sensor can be connected either directly to the controller, input
X2, or via the network, nviOccSensor. To be able to use a directly
connected sensor, bit 0 in nciAppOptions must be set to 1. When
nviOccSensor has received a valid value, this is used, whether
there is a directly connected sensor or not.
Bit 8 in nciAppOptions indicates whether input X2 should mean
normally open (NO) or normally closed (NC). Bit 8=0 means
normally open, Bit 8=1 normally closed.
The directly connected sensor’s value is sent out on the network
in nvoOccSensor. If there is no sensor connected (according to
nciAppOptions), the value OC_NUL is sent out.
There is a 20 minute delay before the operation mode is
changed from comfort to economy in nvoEffectOccup. The
change in nvoOccSensor only takes 250 ms to make other uses
of the occupancy sensor possible (lighting, alarm etc.).
5.3.6Minimum value for heating valve (TAC Xenta 102-VF only)
During cold periods, there is often a back draught at the
windows in the room. To avoid this, TAC Xenta 102 offers a
possibility to have a little heat on even if it is not really
necessary to keep the temperature in the room.
This is done by setting a lowest permitted value for the opening
of the heating valve. TAC Xenta 102 makes sure that the
opening never falls below this value. The value is given as a
percentage in nciHeatPrimMin (min. output heating controller).
The function can only be used when using analogue actuators.
The values of the network variables, which shows how TAC
Xenta 102 positions the heating valve nvoUnitStatus
(heat_output_primary), and nvoTerminalLoad which shows the
position of the valve, should not be lower than nciHeatPrimMin.
Index Variable nameDescription
2
nvoUnitStatus
nvoTerminalLoad
8
44
nciHeatPrimMin
Unit status output
Heating/cooling demand output
Minimum output heating controller
5:14 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 47
TAC Xenta 102 HandbookFunctional description
5.3.7Alarm
When TAC Xenta 102 reports alarms to a monitoring system,
this is done with the network variable nvoAlarmStatus. The
variable has 16 bits, which correspond to different alarm
situations.
Alarm conditions for n v oAlarmStatus
Bit no.AlarmCuts out when...Is reset when...
0Deviating zone temperatureThe deviation in zone temp. isThe deviation in zone temp. is
larger than
for more than 60 min.
(comfort mode).0,5 °C).
1Low zone temperatureThe zone temp. is lower than the The zone temp. is more than
value in
more than 60 min. (Economy and
off mode).
2Window contact alarmEnergy hold off (window contact) The controller no longer
is enabled for more than 60 s.detects the state.
(Economy and off mode).
nciSpaceTempDev
nciSpaceTempLow
for2°C above the value in
smaller than the value in
nciSpaceTempDev
nciSpaceTempLow.
(hysteresis
3High CO
4Deviation in flow in VAV boxThe deviation is larger than 10% The controller no longer
10Not bound
receivedwork variable has been
11Adaptation of thermistor value Internal writing error in theThe controller must be
does not workcontroller memory.replaced.
12Bound network variables notBound network variables haveWhen network variables have
receivednot been received within set time. been received.
13Not valid value on inputA network variable for input goes The variable gets an accepted
14No application programNo valid application program.The application program is
15Cannot write toThe controller is faulty.The controller must be
EEPROMreplaced.
levelThe CO2 level is 200 ppm higherThe controller no longer
2
nvi’s
have not beenPower onWhen the first not bound net-
nciSpaceCO2High
than
than 60 minutes (comfort mode).
nciMaxFlow
of
30 min.
nciRcvHrtBt
outside its accepted value.value.
for more thandetects the state.
for more detects the state.
received.
loaded. Contact your nearest
TAC service point.
Index Variable nameDescription
3
nvoAlarmStatus
26
nciSpaceTempDev
nciSpaceTempLow
27
47
nciRcvHrtBt
TAC AB, 1999-08-180-004-7516-1 (GB), 5:15 (16)
Alarm status output
Maximum deviation of zone temperature
Low limit of zone temperature
Receive heartbeat
Page 48
TAC Xenta 102 HandbookFunctional description
5.3.8Master/slave operation
The controller can control a number of slave units, which
makes it possible to control several TAC Xenta 102 controllers
within the same zone. When bit 7 in nciAppOptions is enabled
(=1) the controller works as a slave, otherwise as a master. The
slave and the master controller must be of the same type.
Master
nvoBoxFlow
nvoHeatSlave
nciAppOptions
bit 7 = 0
Inputs
nviBoxFlow
nviHeatSlave
Slave
nciAppOptions
bit 7 = 1
Outputs
and
outputs
Wall
module
Figure 5.6 V ariable bindings between master/sla ve controllers.
The value sent by means of the network variable nvoBoxFlow is
the current flow in the master VAV box. The value which is
sent via the variable nvoHeatSlave is the state for heating, the
percentage and state for a possible fan.
A TAC Xenta 102 working as a slave controller only controls the
heating, the air flow and the fan (if it is selected) according to the
values sent by its master controller on the network. It does not
consider other inputs.
The application mode, which can be read by means of the
variable nvoUnitStatus, is set to off mode for the slave.
The communicating network variables between the master
controller and all the slave controllers are bound according to
figure 5.6.
Index Variab le nameDescription
7
nvoBoxFlow
12
nvoHeatSlave
22
nviBoxFlow
nviHeatSlave
23
24
nciAppOptions
38
nciFlowOfstSlave
5:16 (16), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Box flow output
Heating control output for slave
Box flow input
Heating control input for slave
Application options
Flow offset for slave
Page 49
TAC Xenta 102 HandbookTrouble-shooting
6Trouble-shooting
6.1General
TAC Xenta 102 is normally a very reliable controller. Should
any problems occur, you can use the trouble-shooting tips in
this chapter, preferably when the controller is run on a network, but also when it is used stand-alone. If you need further
help, please contact the nearest TAC service point.
TAC AB, 1999-08-180-004-7516-1 (GB), 6:1 (4)
Page 50
TAC Xenta 102 HandbookTrouble-shooting
6.2Inputs and outputs (nvi/nvo’s)
The most important variables for information on the current
status of the controller during operation, are the nvo’s and the
nvi’s.
With the help of these, you can check the controller’s operation
and redeem any faults or disturbances.
Below you find the nvi’s and the nvo ’s with a short description.
In chapter 8, you find complete information on all variables’ index, variable name, function, accepted values, default values
etc.
T a ble 6.1 Overview over all inputs and outputs.
Index NameDescription
nvoEffectOccup
1
2
nvoUnitStatus
nvoAlarmStatus
3
nvoEffectSetpt
4
nvoSpaceTemp
5
6
nvoFlowControlPt
nvoBoxFlow
7
nvoTerminalLoad
8
nvoSpaceCO2
9
nvoEnergyHoldOff
10
Effective occupancy output
Unit status output
Alarm status output (see section 5.3.7)
Effective setpoint output
Zone temperature output
Effective setpoint output (I/s)
VAV box flow output
Heating/cooling demand output. Positive value=cooling, negative value=heating
Zone CO2 sensor output
Energy hold off output, window contact status
nvoFlowSetpoint
11
nvoHeatSlave
12
nviManOccCmd
13
nviApplicMode
14
nviSpaceTemp
15
16
nviSetpoint
17
nviSetpntOffset
nviSpaceCO2
18
nviEnergyHoldOff
19
nviManOverride
20
nviEmergCmd
21
22
nviBoxFlow
nviHeatSlave
23
nvoOccSensor
42
nviOccSensor
43
Effective setpoint for VAV Compact (%)
Heating control output for slave
Occupancy scheduler input
Application mode input (forcing the controller)
Zone temperature input, replaces input B1 at a valid value
Temperature setpoint input, which at a valid value recalculates
Setpoint offset input
Zone CO2 input
Energy hold off input for window contact, determines operation mode together
with input X3
Manual override input
Emergency command input
VAV box flow input
Input heating sequence for slave
Occupancy sensor output, only input X2 is copied, see
information
Occupancy sensor input, determines operation mode together with input X2
nviOccSensor
nciSetpoints
for net
6:2 (4), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 51
TAC Xenta 102 HandbookTrouble-shooting
6.3Problems and solutions
What affects...
Operation?
Operation mode?
(Forcing of
controller)
Check...
•Bypass timer on wall module (X1). If
you have pressed the bypass key, it
takes 2 hours before the time expires.
•Occupancy sensor (X2) or similar network variabl e, nviOccSensor. If the
occupancy sensor has indicated presence, it takes 20 minutes before it is disabled.
•How the content in nvoEffectOccup
can be affected. See section 5.2.1
about operation modes.
• Order via network, nviManOccCmd.
•Chosen settings in nciAppOptions
• Order via net, nviApplicMode
• If a window contact (X3) or similar
network variable, nviEnergyHoldOff,
is enabled.
• Outputs heating, nvoUnitStatus and
nvoTerminalLoad which is affected by
normal control or nciHeatPrimMin.
Control setpoint?• Current operation, nvoEffectOccup
• Current unit status, nvoUnitStatus
• Set basic setpoints, nciSetpoints.
Chosen options in nciAppOptions concerning calculation method A or B
together with nviSetpoint control this.
An invalid value in nviSetpoint gives
the basic setpoints. See section 5.2.4
regarding setpoint calculation.
• nviSetpntOffset and/or the setpoint
knob on the wall module. These give
+/– influence.
Read room
temperature?
•Physical reading (B1) or similar network variable, nviSpaceTemp. A valid
value on the network overrides a physical reading. nciSpaceTempOfst can dis-
place the value.
cont.
TAC AB, 1999-08-180-004-7516-1 (GB), 6:3 (4)
Page 52
TAC Xenta 102 HandbookTrouble-shooting
What affects...Check...
Air flow?• Current values in nciMinFlow, nciMax-
Flow, nciMinFlowStand, nciMinFlowHeat, nciNomFlow, nvoFlowControlPt,
nvoFlowSetpoint and nvoBoxFlow.
• Current operation.
• Current operation mode.
That an alarm is set?
The LED on the wall
module?
• Influence from the CO
controller.
2
• Current operation, nvoEffectOccup
• Current values in nciSpaceTempDev
and nciSpaceTempLow.
• If a window is open (window contact).
See also section 5.3.7 on alarms.
• That the controller receives power
also when the LED is out.
• The controller, when the service LED
is lit. This indicates that the controller
does not work propertly and should be
replaced.
• The controller, when the service LED
is lit for 15 seconds and then goes out.
This is not a fault, but an indication
that the controller answers a “wink”
command from the network.
TAC Xenta 100 series ...............................................0-008-5582
7:2 (4), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 55
TAC Xenta 102 HandbookTechnical data
7.2Dimensions
7.2.1With semi-protection
126
98
126,8
110±0,2
118,2
Figure 7.1 Dimensions (mm) for TAC Xenta 102 with semi-protection
7.2.2Without semi-protection
110±0,2
112±1
126
98
118,2
50
122
112±1
50
Figure 7.2 Dimensions (mm) for TAC Xenta 102 without semi-protection
TAC AB, 1999-08-180-004-7516-1 (GB), 7:3 (4)
Page 56
TAC Xenta 102 HandbookTechnical data
This page is intentionally left blank.
7:4 (4), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 57
TAC Xenta 102 HandbookCommunication
8Communication
8.1General
The controller consists of two LonMark objects: the node object
(section 8.5) and the controller object (section 8.6). These objects
are monitored by means of the network variables nviRequest andnvoStatus.
The network variable nciLocation is used when configuring the
basic parameters (section 4.1) to give a detailed description of
the actual place where the controller is fitted. The variable
receives an arbitrary string of signs and dividers as long as the
string is no longer than 30 signs. You can program a certain
location label, e.g.
TAMF.main.floor3.room343/RC40
A LNS based network management tool uses nciLocation when
a data base should be recreated. The monitoring of an already
installed network is made by the LNS tool reading nciLocation,
and then using the information to give the node a sub-system
name and a unit name. The string should therefore consist of a
name and a search path for the sub-system, followed by a slash
and the unit name, i.e.
system.sub-system[.sub-system...]/unit name
8.2Default settings and power on
For all network variables the following default settings are
valid:
• Number of sent messages per time unit: NONE
• Service type: NOT CONFIRMED if not stated otherwise
• Access check: NO, possible to configure: YES.
•Polled: NO for all nvo and nci, YES for all nvi
(commissioning)
• Synchronized: NO
• Change/update only when the controller is not enabled on
the network; flags = NO
• Restart of TAC Xenta 102 after a change; flags = YES
TAC AB, 1999-08-180-004-7516-1 (GB), 8:1 (10)
Page 58
TAC Xenta 102 HandbookCommunication
All network variables have the same index as they have in the
menu tree in the operator panel TAC Xenta OP. They represent the
order, in which the y have been declared in the system program, as
the order is important for variables’ self documentatory string. The
variables are of standard type or so called SNVT, and the values
each SNVT can receive, are listed in the tables in this chapter.
Apart from SNVT, there are also standard configuration parameters (SCPT) and parameter types for user configuration (UCPT). If
you want general information about which SNVT/SCPT/UCPT
there are and which values they can receive, the “The SNVT Master List and Programmer's Guide” on the internet address
www.lonmark.org is a good source of information.
At power on, all variables for inputs and outputs (nvi and nvo)
receive their default values after a restart, as the configuration
parameters (nci) keep their earlier set values. After a restart
all nvi’s will send a request to the nvo ’s to which they are bound
(a poll).
8.3Monitoring network variables, Heartbeat
In TAC Xenta 102 there is a function, called Heartbeat, which can
be configured to monitor input and output variables on the network.
In the overviews in this chapter, you can see whether the variable
is monitored with Heartbeat in the column Hb.
Inputs
Some of the inputs in TAC Xenta 102 are monitored in a way that
the variable must receive values within a certain time for it to be
regarded as valid. If no value is received within this time, the variable will return to its default value. Also, an alarm is enabled, bit
12 in nvoAlarmStatus.
Which outputs are monitored in this way, you find in the list of
network variables in chapter 8.6.1.
The time is set with the variable nciRcvHrtBt. Its default value is
0.0, which means that no monitoring is performed.
Outputs
The bound outputs are normally sent out when they are changed.
Most outputs in TAC Xenta 102 are monitored, so even if the
values are not changed, they are sent out at even intervals.
Which outputs are monitored in this way, you find in the list of
network variables in chapter 8.6.2.
The time is set with the variable nciSndHrtBt. Its normal value
is 0.0, which means that no monitoring is performed.
8:2 (10), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 59
TAC Xenta 102 HandbookCommunication
8.4Not accepted values
All nvo’s are limited to their accepted values, and all nvi’s detect
whether the incoming value from the network is within the
accepted limits. If the value is not accepted, the controller
activates bit 13 in the variable for alarm handling, nvoAlarm-Status. For an nvi, the controller uses the off value, which is
also counted as an accepted value.
8.5The node object
The variables in the node object (figure 8.1) are separated into
three categories:
• Mandatory (M)
• Optional (O)
• Configuration properties (C)
*
According to LonMark
standardised function
profile for VAV
controllers.
The category “Mandatory” contains all compulsory variables*,
“Optional” contains selectable variables, and ”Configuration
properties” contains the configuration parameters.
Note! The network variables’ indeces are not the same as the
figure in “nv” in the figure.
0 - Node Object
Object Type: 0
nviRequest
nv1
SNVT_obj_request
Mandatory
Network
nvoStatus
nv2
SNVT_obj_status
Variables
nviFileReq
nv5
SNVT_file_req
Optional
Network
nvoFileStat
nv6
SNVT_file_status
Variables
Configuration Properties
nciInstallTypeSNVT_config_src
Figure 8.1 The node object
8.5.1The node object’s inputs (nvi)
Index Variable Hb*1SNVTAccepted valuesDefaultDescription
The variables in the controller object (figure 8.2) are separated
into four categories:
• Mandatory (M)
*
According to LonMark
standardised function
profile for VAV
controllers
•Optional (O)
• Configuration properties (C)
•Manufacturer Defined Section (MDS)
The category “Mandatory” contains all compulsory variables
“Optional” contains selectable variables, ”Configuration properties” contains configuration parameters, and “Manufacturer
Defined Section” is all other variables which make the
controller’s functions possible.
Figure 8.2 is on the next page. Note! The network variables’
indeces are not the same as the figure in “nv” in the figure.
There are two methods to calculate the setpoints: Method A and Method B.
Method A:
When
nviSetpoint
and heating setpoints are recalculated to be at the same distance from the new, basic setpoint as they
were from the earlier basic setpoint. Therefore, method A removes the existing asymmetry (see the example on the next page).
The controller calculates the different setpoints for heating and cooling in comfort and economy mode,
the cooling and heating setpoints for comfort and economy mode are set.
can be regarded as the basic setpoint for comfort mode, and the mean value of the econo-
receives a valid setpoint, this value becomes the new, common setpoint. The cooling
, plus or minus half the neutral zone in the comfort and economy modes, which are calcu-
nciSetpoints
.
. The controller takes the differnet heating and cooling setpoints in off mode
nviSetpoint
gives
Method B:
In economy mode you can chose method B to calculate the existing setpoints. In this case, the setpoints’
distance from the existing setpoint, is as far as the distance they were from the old, basic setpoint in
comfort mode. Method B only has influence when the two setpoints from
same value, i.e. when the four setpoints are not placed symmetrically around one value. With Method B
the asymmetry is therefore kept, as the old comfort setpoint is used (see the example on the next page).
The controller calculates the different setpoints for heating an cooling in comfort and economy modes
nciSetpoints
from
occupied_heat setpoint and the occupied_cool setpoint. The controller gets the different heating and cooling setpoints in off mode from
This protocol can be used when commissioning the VAV controller TAC Xenta 102. Note that the indices are
listed in numerical order, not in the order they are used during commissioning. If you need information on
accepted values, these are found in the tables in chapter 8.
Index FunctionVariableDefaultSetNote
valuevalue
0Location labelnciLocation0
13Occupancy scheduler inputnviManOccCmdOC_NUL
14Application mode inputnviApplicMode0=Auto
15Zone temperature inputnviSpaceTemp327,67 °C
16Temperature setpoint inputnviSetPoint327,67 °C
17Setpoint offset inputnviSetpntOffset0 °C
18Zone CO
19Energy hold off inputnviEnergyHoldOff0=Off, 0%
20VAV manual override inputnviManOverrideHVO_OFF
21Emergency command inputnviEmergCmdEMERG_
22Air flow VAV box inputnviBoxFlow0
23Heating control input for slavenviHeatSlave0=Off, 0%
24Application optionsnciAppOptions00000000
25Occupancy temp. setpointsnciSetpoints
(Heating setpoint economystandby_heat19 °C)
26Max. deviation of zone temp.nciSpaceTempDev2 °C
27Low limit of zone temperaturenciSpaceTempLow10 °C
28Gain for VA VnciVAVGain25
29Integral time for VAVnciVAVItime900 s
30Gain for heating controllernciGainHeat25
31Integral time for heat. control.nciItimeHeat900 seconds
32Zone temp. sensor adjustmentnciSpaceTempOfst0,0 °C
33Minimum flownciMinFlow0 l/s
34Maximum flownciMaxFlow65535 l/s
35Minimum flow heatingnciMinFlowHeat0 l/s
36Minimum flow standbynciMinFlowStand0 l/s
37Nominal flownciNomFlow0 l/s
38Flow offset for slavenciFlowOfstSlave0 l/s
39Conv. factor ppm CO
40Space CO
41Space CO2 level open dampernciSpaceCO2High1000 ppm
43Occupancy sensor outputnviOccSensorOC_NUL
air flow limits 5:10
air flow monitoring 5:10
air flow setpoints 5:10
nominal air flow 5:10
W
Wall modules2:3
Wall modules ZS 101–ZS
104 3:3
Window contact5:13
wink 1:3
Wiring of TAC Xenta 102-B3:5
Wiring of TAC Xenta 102-EF3:6
Wiring of TAC Xenta 102-VF 3:7
With semi-protection 7:3
Without semi-protection 7:3
TAC AB, 1999-08-180-004-7516-1 (GB), Reg:1 (2)
Page 72
TAC Xenta 102 HandbookIndex
This page is intentionally left blank.
Reg:2 (2), 0-004-7516-1 (GB)TAC AB, 1999-08-18
Page 73
TAC Xenta 102 HandbookReply form
You can help make this manual even better!
Please help us make our documentation as good as possible. Use this form to let us know of
any errors, unclear descriptions or suggested improvements.
Send the form to:Or e-mail to:
TAC ABhelpdesk@tac.se
Helpdesk
Jägershillgatan 18
SE-213 75 MALMÖ
SWEDEN
I have found the following errors and/or unclear descriptions in the “Zone controller Xenta
102 Handbook” (part number 0-004-7516-1 (GB)):
On page: ..................................................................................................................................................
On page: ..................................................................................................................................................
On page:..................................................................................................................................................
On page:..................................................................................................................................................