Schneider Electric TAC Xenta 102-ES Users Manual

Download

TAC Vista

TAC Pangaea

WorkStation

TAC Xenta 102-ES

Product Manual

TAC Vista

TAC Xenta 102-ES

Product Manual

Copyright © 2004-2010 Schneider Electric Buildings AB. All rights reserved. This document, as well as the product it refers to, is only intended for licensed users. Schneider Electric Buildings AB owns the copyright of

this document and reserves the right to make changes, additions or deletions. Schneider Electric Buildings AB assumes no responsibility for possible mistakes or errors that might appear in this document.

Do not use the product for other purposes than those indicated in this document. Only licensed users of the product and the document are permitted to use the document or any information therein. Distribution, disclosure,

copying, storing or use of the product, the information or the illustrations in the document on the part of non-licensed users, in electronic or mechanical form, as a recording or by other means, including photo copying or information storage and retrieval systems, without the express written permission of Schneider Electric Buildings AB, will be regarded as a violation of copyright laws and is strictly prohibited.

Trademarks and registered trademarks are the property of their respective owners.

Zone Controller, TAC Xenta 102-ES Contents

INTRODUCTION

1 Documentation and Terminology 9

1.1 Documentation........................................................................................................... 9

1.2 Terminology............................................................................................................... 9

REFERENCE

2 Zone Controller TAC Xenta 102-ES 13

2.1 General....................................................................................................................... 13

2.2 Wall Modules............................................................................................................. 15

2.2.1 STR350/351 ............................................................................................................... 15

2.2.2 STR150 ...................................................................................................................... 16

2.2.3 STR100-104............................................................................................................... 17

2.2.4 Wall Module Configuration....................................................................................... 18

2.3 Applications ............................................................................................................... 19

2.3.1 General....................................................................................................................... 19

2.3.2 The Zone Controller TAC Xenta 102-ES .................................................................. 19

3 Installation 23

3.1 Mechanical Installation.............................................................................................. 23

3.1.1 Fitting......................................................................................................................... 23

3.2 Electrical Installation ................................................................................................. 24

3.2.1 General....................................................................................................................... 24

3.2.2 Wiring of Xenta 102-ES, Application with Damper Control Only ........................... 27

3.2.3 Wiring of Xenta 102-ES, Application with Damper and Reheat Control.................. 28

3.2.4 Wiring of Xenta 102-ES, Application with Damper and Two- Stages of Reheat Control 29

3.2.5 Connecting to STR150............................................................................................... 30

3.2.6 Air Flow Balancing Procedure................................................................................... 30

3.3 Commissioning .......................................................................................................... 32

3.3.1 General....................................................................................................................... 32

3.3.2 Node Status ................................................................................................................32

3.3.3 Configuration Parameters (nci´s)............................................................................... 33

3.3.4 Network Installation.............................................................. ..... ................................ 33

3.3.5 Network Variable Binding.................................................... ..... ................................ 34

3.3.6 Function Test..............................................................................................................34

4 Configuration Parameters 35

4.1 Basic Parameters...................................................... .................................................. 36

4.2 Other Configuration Parameters ................................................................................ 37

Schneider Electric Buildings AB, Mar 2010 5 (88) 04-00069-01-en

Contents Zone Controller, TAC Xenta 102-ES

5 Functional Description 41

5.1 General ....................................................................................................................... 41

5.2 The Controller’s Basic Functions............................................................................... 41

5.2.1 Operation Modes ......................................................................... .... ........................... 41

5.2.2 Application, Manual and Emergency Modes............................................................. 43

5.2.3 Measuring Zone Temperature .................................................................................... 45

5.2.4 Setpoint Calculation ................................................................................................... 46

5.2.5 Temperature Control Sequence for TAC Xenta 102-ES............................................ 48

5.3 More About Functions................................................................................................ 49

5.3.1 Cooling Control............................................................................................. ............. 49

5.3.2 Heating Control .......................................................................................................... 50

5.3.3 Fan Control................................................................................................................. 50

5.3.4 Air Quality Control..................................................................................................... 51

5.3.5 Window Contact......................................................................................................... 52

5.3.6 Occupancy Sensor ...................................................................................................... 52

5.3.7 Alarm.......................................................................................................................... 53

5.3.8 Master/slave Operation............................................................................................... 54

5.3.9 Additional Features ................................................... .... ............................................. 55

6 Troubleshooting 57

6.1 General ....................................................................................................................... 57

6.2 Inputs and Outputs (nvi/nvo)...................................................................................... 57

6.3 Troubleshooting Guide............................................................................................... 59

7 Technical Data 61

7.1 Technical Data............................................................................................................ 61

7.2 Dimensions................................................................................................................. 64

8 Communication 65

8.1 General ....................................................................................................................... 65

8.2 Default Settings and Power On .................................................................................. 65

8.3 Monitoring Network Variables, Heartbeat................................................................. 66

8.4 Not Accepted Values.................................................................................................. 66

8.5 The Node Object......................................................................................................... 67

8.5.1 The Node Object’s Inputs (nvi).................................................................................. 68

8.5.2 The Node Object’s Outputs (nvo) .............................................................................. 68

8.5.3 The Node Object’s Configuration Parameters (nci)................................................... 68

8.6 The Controller Object................................................................................................. 69

8.6.1 The Controller Objects Inputs (nvi) ........................................................................... 71

8.6.2 The Controller Objects Outputs (nvo)........................................................................ 72

8.6.3 The Controller Object’s Configuration Parameters (nci)........................................... 73

APPENDIX

A Setpoint Calculation 77

B Commissioning Protocol 81

Index 85

6 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

INTRODUCTION

1 Documentation and Terminology

Zone Controller, TAC Xenta 102-ES 1 Documentation and Terminology

1 Documentation and Terminology

1.1 Documentation

Enclosed Documentation

TAC Xenta 102-ES is delivered with an installation instruction: TAC Xenta 102-ES, Installation instruction

1.2 Terminology

Some useful terms and abbreviations regarding the zone controller's application and network communication are explained in the table below.

Table 1.1: Terminology

or can be ordered from your

neuron

node SNVT Standard Network Variable Type

Schneider Electric Buildings AB, Mar 2010 9 (88) 04-00069-01-en

communication processor with built-in protocol

communication unit on the network

1 Documentation and Terminology Zone Controller, TAC Xenta 102-ES

Table 1.1: Terminology

nvixxx variable that gets its value from another

unit on the network

nvoxxx variable that is sent to another unit on the

network

ncixxx configuration parameter; variable that gets

its value from another unit on the network and keeps it during a power failure

service pin function that can be used during installa-

tion on the network

wink

confirmation that the connection to a controller via the network is working (a LED is lit for appr. 20 seconds)

LNS

LonWork

Network Services. System tool for installation, configuration and maintenance of LonWorks network

TAO Thermal Actuator Output.

10 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

REFERENCE

2 Zone Controller TAC Xenta 102-ES

3 Installation

4 Configuration Parameters

5 Functional Description

6 Troubleshooting

7 Technical Data

8 Communication

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

2 Zone Controller TAC Xenta 102-ES

2.1 General

The zone controller TAC Xenta 102-ES is intended for VAV applications in offices and other large buildings. The VAV controller maintains a constant temperature in the zone by regulating the flow of air at a constant temperature into the room.

The Controller’s Basic Functions

The controller have a number of built-in functions that are designed to handle normal control situations. There are four operating modes to choose from (comfort, economy, bypass and off) and five modes to force the controller (auto, heating, cooling, night purge and off). The air flow is measured with a built-in air flow sensor. The zone temperature is measured using a permanent thermistor sensor or a temperature node connected to the network. Setpoint calculations are made in line with defined methods. The controller is equipped with an air qu ality function if it has been connected to a carbon dioxide sensor.

There is a detailed description of all the basic functions in Section 5.2, “The Controller’s Basic Functions”, on page 41.

More About Functions

Apart from the controller’s basic functions, there are a number of other functions for controlling the climate in the zone; these are described in detail in Section 5.3, “More About Functions”, on page 49. Additional external functions that can be connected are also described in this chapter, these include window contact sensor and occupancy sensor.

Communications

The controller can work either as a stand-alone 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 (Fig. 2.1). A detailed description of how units work together in a larger zone system, is found in “Zone Systems Guidelines”, part number 0-004-7637.

TAC Vista is an excellent tool for reading variables as well as a configuration tool for commissioning and/or operation purposes. When TAC Vista is not part of the system, reading and configuration of variables can be made from the operating panel TAC Xenta OP, version 3.11 or later.

Schneider Electric Buildings AB, Mar 2010 13 (88) 04-00069-01-en

103-A103-A103-A103-A

102-EF102-EF102-EF102-EF102-EF

102-ES102-ES102-ES102-ES102-ES102-ES

102-B 102-B102-B

101-1VF 101-2VF101-1VF101-1VF101-1VF101-1VF101-1VF101-1VF101-1VF

Analog

I/O

Digital

I/O

TAC

Xenta

300

Router

TAC

Xenta

400

TAC

Xenta

400

3rd

floor

Office 3:1 Office 3:2

Office 3:3 Office 3:4

Office 3:5

Office 3:6 Office 3:7 Office 3:8 Office 3:9

2nd

floor

Office 2:1

Office 2:2

Office 2:3

Office 2:4 Office 2:5

Office 2:6Room 2:1

Master

Room 2:2

Slave

Room 2:3

Slave

TAC Vista

1st

floor

Room

1:1

Slave

Room 1:2

Slave

Room

1:4

Slave

Room 1:3

Slave

Room 1:5

Master

Office 1:1

Office 1:2

Office 1:3

Office 1:4

4th

floor

Ground

floor

Fig. 2.1: Zone controller in a larger system together with TAC Vista

2 Zone Controller TAC Xenta 102-ES Zone Controller, TAC Xenta 102-ES

The controller is LonMark® approved and communicates on a Lon-

TP/FT-10 network via a twisted-pair, unpolarized cable. If you

Talk want to know more about the LonWorks

technology, visit the internet

addresses www.echelon.com or www.lonmark.org.

14 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

Select button

Increase/Decrease buttons

Bypass/On-Off button

Display

2.2 Wall Modules

A temperature sensor must be mounted somewhere in the controlled zone. In the STR series of wall modules the temperature sensor is combined with various types of user interfaces. Several STR models are well suited for TAC Xenta 102-ES regarding desired functionality and user interface.

• STR350/351. Wall unit with temperature sensor and LCD display. Extensive functionality for zone control. Communicates with the controller over LonWorks.

• STR150. Wall unit with temperature sensor and LCD display. Have the most common functions for zone control. One-way serial communication with the controller.

• STR100-104. Wall module with temperature sensor and controls for the most common functions for zone control. STR100-107 signals are hard-wired to TAC Xenta 102-ES.

2.2.1 STR350/351

STR350/351 communicates on LonWorks. LonWorks is used for all data exchange between the room unit and the controller.

Regarding TAC Xenta 102-ES, STR350/351 has the following functionality:

• Temperature sensor . Use either the built in thermistor element or another temperature sensor available on the LonWorks network

• Actual temperature display. The actual zone temperature can be displayed on the LCD, but can also be hidden if desired.

• Temperature setpoint display. The temperature setpoint can be displayed, either as an absolute value or as an offset.

Schneider Electric Buildings AB, Mar 2010 15 (88) 04-00069-01-en

2 Zone Controller TAC Xenta 102-ES Zone Controller, TAC Xenta 102-ES

Fig. 2.2: Wall module STR150

Bypass button

Increase/Decrease buttons

Fan speed control

Display

• Temperature setpoint adjustment. The temperature setpoint can

be adjusted, either as an absolute value or as an offset.

• Bypass or on/off button. There is a bypass function which forces

the controller to comfort mode for a configurable period of time. The same button can alternatively be used as an on/off button.

• Mode Indicator. An On/Off symbol in the LCD indicates the

mode of the control.

For technical details of the functionality listed above, additional functionality and for configuration details, see the STR350/351 configuration and data sheets.

Use the LNS plug-in to configure STR350/351.

2.2.2 STR150

16 (88) Schneider Electric Buildings AB, Mar 2010

STR150 connects to TAC Xenta 102-ES with two or three wires. The third wire is used only if mode indication in the LCD is desired. On the other two wires information is sent from the wall unit to the controller:

• Zone temperature. The temperature sensed by the thermistor ele-

• Temperature setpoint. The temperature setpoint, which is dis-

• Bypass button. The bypass button forces the controller to comfort

The mode indication signaled on the third wire is connected to the man symbol in the LCD:

• Comfort mode (On) is indicated by a steady man symbol

ment.

played as an absolute temperature, but transmitted as an offset to the configured reference temperature.

mode for a fixed period of time (2 h).

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

Fig. 2.3: Wall module STR104

Mode indicator On/Off

Bypass button

Temperature setting wheel

Fan speed control

• Economy (Standby) mode is indicated by a flashing man symbol.

• Unoccupied (Off-mode) is indicated by the man symbol being off.

There is no communication from the controller to the unit so if a setpoint is changed from TAC Vista, this new value cannot be displayed on STR150.

Configuration of STR150 is done using the buttons and display on the unit. See STR150 configuration and data sheets for details.

2.2.3 STR100-104

STR100-104 is a series of room units that connects to I/O terminals of TAC Xenta 102-ES. The functionality of the various models is given in the Table 2.1, “STR100-104 functionality”.

Table 2.1: STR100-104 functionality

Model Temp Sensor

STR100 X STR101 X X STR102 X X X STR103 X X X STR104 X X X X

Mode

Indicator

Setpoint

Adjustment

STR104 is shown in Fig. 2.3 as an example.

Bypass Button

Note

• The T AC Xenta OP is normally connected direct ly to the controller, not the wall module. The TAC Xenta 101-VF has a TAC Xenta OP access connecter (type RJ-10) on the controller instead of dedicated terminals for the wall module.

Schneider Electric Buildings AB, Mar 2010 17 (88) 04-00069-01-en

2 Zone Controller TAC Xenta 102-ES Zone Controller, TAC Xenta 102-ES

Depending on model the following functionality may be present:

• Temperature Sensor. All models have a 1.8Kohms@25°C ther-

mistor element.

• Temperature Adjustment. The temperature setpoint can be

adjusted. Using the plastic keys on the rear of the core panel the adjustment range can be set.

• Mode Indicator. The green LED indicates the control mode:

• Comfort mode (On) is indicated by a steady green light

• Economy (Standby) mode is indicated by a flashing green light.

• Unoccupied (Off-mode) is indicated by the LED being off.

• Bypass button. The bypass button forces the controller to comfort

mode for a configurable period of time.

Refer to STR100-107 data sheet and installation sheet for details.

2.2.4 Wall Module Configuration

Wall Module Choice

STR150 is enabled by nciAppOptions bit 14:

• 0 = ZS and STR100-104 or STR350/351 (default)

• 1 = STR150 This can be set using the LonMaker Xenta100 plug-ins in Toolp ack ver-

sion 2.01 or higher, or by means of TAC Xenta OP.

Initial Start Up Status

• SpaceTemp in the application is set to +20.00 Celsius (This can be read in the nvoSpaceTemp, but not in nviSpaceTemp.)

• Fan is set to Fan Auto

TAC Xenta is now waiting for data from the STR module. If no room temperature readings are received within 10 minutes, the

SpaceTemp in the application is set to “invalid”. This is shown as “invalid” in nvoSpaceTemp.

When the first update is received , then the 10 minute limit is changed to 5 minutes.

18 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

Unless there is a restart, the Offset + Fan values are not cleared and the last value is valid..

Note

• Fore more information on how to configure and engineer the STR series of wall modules see the documents for each product respectively.

2.3 Applications

2.3.1 General

The TAC Xenta 102-ES controller incorporates several features including

• a built-in air flow sensor and controller algorithms.

• the facility to connect a window contact sensor to stop the heating and cooling functions should a window be opened (Section 5.3.5, “Window Contact”, on page 52).

• an occupancy sensor that can detect the presence of a person in the controlled zone and change the controller from economy to comfort mode (Section 5.3.6, “Occupancy Sensor”, on page 52).

• an air quality control function that can be activated if a carbon dixoide sensor is connected. When a sensor is connected, the controller ensures that the concentration of carbon dioxide in the zone between preset limits (Section 5.3.4, “Air Quality Control”, on page 51).

• an auxiliary temperature sensor that can be connected to measure any temperature and present it as a SNVT (Section 5.3.9, “Additional Features”, on page 55).

2.3.2 The Zone Controller TAC Xenta 102-ES

The controller is designed for the following applications:

• Damper control only

• Damper control with primary heating and one free network output

• Damper control with primary and secondary heating

For fan control applications see Section 5.3.3, “Fan Control”, on page 50.

Damper Control Only

The zone temperature is maintained by controlling of the airflow damper. The airflow is limited to maximum and minimum.

An optional occupancy and/or a CO2 sensor can be connected.

Schneider Electric Buildings AB, Mar 2010 19 (88) 04-00069-01-en

2 Zone Controller TAC Xenta 102-ES Zone Controller, TAC Xenta 102-ES

Fig. 2.4: Damper control for TAC Xenta 102-ES

Widow contact

Air flow sensor

Damper

Free Network

control output

sensor

Wall module

Occupancy sensor

Auxiliary temperature

sensor

The free network output (V6) can be used in this application. For applications with fan control, see Section 5.3.3, “Fan Control”, on

page 50.

Damper and Primary Heating Control

The zone temperature is maintained by sequence control of the airflow damper and primary reheating. The airflow is limited to maximum and minimum. The reheat control is achieved by an increase/decrease or thermal actuator.

An optional occupancy and/or a CO2 sensor can be connected. The free network controlled output (V6) can be used in this application

(see Section 5.3.9, “Additional Features”, on page 55).

20 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

Fig. 2.5: Damper and reheat control for TAC Xenta 102-ES

Widow contact

Air flow sensor

Damper

Free Network

control output

sensor

Wall module

Occupancy sensor

Auxiliary temperature

sensor

Fan

Relay

Actuator

Valve reheat

For applications with fan control, Section 5.3.3, “Fan Control”, on page 50.

Damper Control and Two Stages of Reheat Control

The zone temperature is maintained by sequence control of the airflow damper, primary reheating and secondary reheating. The airflow is limited to maximum and minimum. The reheat control is achieved by an increase/decrease or a thermal actuator for primary reheat and thermal actuator for secondary reheat.

An optional occupancy sensor and a CO2 sensor can be connected.

Schneider Electric Buildings AB, Mar 2010 21 (88) 04-00069-01-en

2 Zone Controller TAC Xenta 102-ES Zone Controller, TAC Xenta 102-ES

Fig. 2.6: Damper and two stages of reheat control for TAC Xenta 102-ES.

Widow contact

Air flow sensor

Damper

Thermal actuator

sensor

Wall module

Occupancy sensor

Auxiliary temperature

sensor

Fan

Relay

Actuator

Radiators

For applications with fan control, see Chapter 5.3.3, “Fan Control”, on page 50.

22 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

Fig. 3.1: TAC Xenta 102-ES fixed to a DIN rail

3 Installation

3.1 Mechanical Installation

3.1.1 Fitting

TAC Xenta 102-ES can either be snapped onto a DIN rail (Fig. 3.1) or fixed to a level surface with two screws. (Fig. 3.2).

To fasten the controller onto a DIN rail:

1 Place the controller on the top of the rail as shown by arrow 1. 2 Twist the controller downwards until it snaps onto the rail as

shown by arrow 2.

3 To remove, use a screwdriver to locate the lock on the bottom of

the controller and pull down. Then lift the controller diagonally upwards and off the rail.

Schneider Electric Buildings AB, Mar 2010 23 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

Fig. 3.2: TAC Xenta 102-ES fixed to a level surface

Fixing the Controller to on a Level Surface:

Use the two sockets provided for fixing the controller; the maximum screw size is M4 or ST 3,5 (Ø 0.15"). The head of the screw should not exceed 7,5 mm (0.3") in diameter.

3.2 Electrical Installation

3.2.1 General

Warning

• All mains supply cables must be installed by authorized electricians.

1 Each controller or group of controllers must use max. 6 A fuses. 2 Avoid hanging or loose cables by using clamps to secure them to

the controller.

3 A switch to cut off the power supply to the controller or compete

unit must be easily accessible.

4 When no carbon dioxide sensor is connected to the terminals a

jumper must be used to connect U1 and M.

5 When several Xenta controllers receive power from a common

transformer, it is important that all Gs are connected to each other and that all G0s are connected to each other. NB! the connections are not interchangeable. Important exception: the G0 on the wall module should be connected to the terminal OP on the controller and not to the other G0's. The G0 should be grounded at the transformer to prevent interference. At the transformer, G0 should be connected to protective earth. This is to get an grounding point for interference diversion.

24 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

6 To ensure that the spec ified measuring accuracy is achieved, the

two M terminals must be connected to the wall module.

Note that this equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

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, 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 (100 feet) and min. area is 0,7 mm

(AWG-19).

The Wall Modules

The STR100-104 is primarily intended for use with the Xenta 103. The wall module STR150 can also be used, but in this case the fan speed button is not used. For more information about how to connect and configure wall modules, please refer to the documentation for each respective product.

Schneider Electric Buildings AB, Mar 2010 25 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

Connection Terminals

The designation of the connection terminals can be found on the label on the front of the controller and the numbers of the terminals can be found on the edge of the printed circuit board.

Termin. Design. Function Type

1 C1 TP/FT-10 communication channel 2 C2 TP/FT-10 communication channel -

4 M Measurement neutral -

5 6 B2 Optional temperature sensor Thermistor input 7 M Measurement neutral 8 U1 Carbon dioxide sensor or jumper Thermistor input 9 D1 LED on wall module Digital output 10 M Measurement neutral 11 X1 Bypass key on wall module Digital input 12 R1 Setpoint adjustment on wall module 10k Ohm linear potentiometer 13 M Measurement neutral 14 B1 Zone temperature sensor Thermistor input 15 G24 V AC (G) Input 16 G0 24 V AC (G0) Input

17 18 G24 V AC supply for TA C Xenta OP 19 V1 Damper actuator: increase Triac 20 G24 V AC (G) supply for V1, V2 21 V2 Damper actuator: decrease Triac 22 V3 Reheat actuator: increase

23 G 24 V AC (G) supply for V3, V4 24 V4 Reheat actuator: decrease

25 V5 Fan on/off control Triac 26 G 24 V AC (G) supply for V5, V6 27 V6 Thermal actuator or free network output Triac 28 Y1 Primary reheat demand Output 0-10 V

a. See chapter 4 Configuration parameters b. Connected to G0 on the wall module. Do not connect to G0 on the controller..

X3 Window contact

Closed contact=closed window)

X2 Occupancy sensor Digital input

OP 24 V AC supply for TAC Xenta OP -

Thermo actuator: on/off parallel V4

Thermo actuator: on/off parallel V3

Digital input

Triac

26 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

Optional temperature input

Carbon dioxide sensor

Occupancy sensor

Window contact

Junction Box

TAC Xenta 102-ES

GW1 GX1 GQ1

Lon Talk" TP/FT-10



COM

INC.

24 VAC

Damper actuator

Network controlled output

DEC.

6 9

(mm)

–

Wall Module

21 22

2423

Therm

LED

Pot/Pot+R

Switch

STR101-104

U1 should not be left unconnected. If no sensor will be used, connect U1 to M.

Tubing. Should be connected before the controller is mounted on the wall.

Air flow sensor, e.g. TAC GV

Fig. 3.3: Wiring of TAC Xenta 102-ES

3.2.2 Wiring of Xenta 102-ES, Application with Damper Control Only

Read Section 3.2.1, “General”, on page 24 before you connect the cables as shown in the wiring diagram in Fig. 3.3.

Schneider Electric Buildings AB, Mar 2010 27 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

U1 should not be left unconnected. If no sensor will be used, connect U1 to M.

Tubing. Should be connected before the controller is mounted on the wall.

Air flow sensor, e.g. TAC GV

Fig. 3.4: Wiring of TAC Xenta 102-ES

3.2.3 Wiring of Xenta 102-ES, Application with Damper and Reheat Control

Read Section 3.2.1, “General”, on page 24 before you connect the cables as shown in the wiring diagram in Fig. 3.4.

Lon Talk" TP/FT-10

TAC Xenta 102-ES

Junction Box

Window contact

Optional temperature input

Occupancy sensor

GW1 GX1 GQ1

Carbon dioxide sensor

–



Wall Module

STR101-104

LED

Switch

Pot/Pot+R

21 22

Therm

2423



6 9

(mm)

INC.

COM

DEC.

INC.

COM

DEC

Fan on/off

Reheat valve actuatorDamper actuator

22 23 23 24

Network controlled output

Thermal actuator

24 VAC

28 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

TAC Xenta 102-ES

GW1 GX1 GQ1



COM

INC.

COM

INC.

22 23

24 VAC



DEC.

6 9

23 24

Thermal actuator

Fan on/off

Reheat valve actuatorDamper actuator

(mm)

Reheat valve actuator

Optional temperature input

Carbon dioxide sensor

Occupancy sensor

Window contact

Junction Box

Lon Talk" TP/FT-10

–

Wall Module

21 22

2423

Therm

LED

Pot/Pot+R

Switch

STR101-104

U1 should not be left unconnected. If no sensor will be used, connect U1 to M.

Tubing. Should be connected before the controller is mounted on the wall..

Air flow sensor, e.g. TAC GV

Fig. 3.5: Wiring of TAC Xenta 102-ES

3.2.4 Wiring of Xenta 102-ES, Application with Damper and TwoStages of Reheat Control

Read Section 3.2.1, “General”, on page 24 before you connect the cables as shown in the wiring diagram in Fig. 3.5.

Schneider Electric Buildings AB, Mar 2010 29 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

Fig. 3.6: Connecting to STR150

3.2.5 Connecting to STR150

Wall Module

STR150

TAC Xenta 104-A

3.2.6 Air Flow Balancing Procedure

Air-flow balancing can be made on site or at VAVbox-factory. The balancing is done on specific box-type (and for individual boxes if necessary). Use the minimum amount of hose necessary to achieve the job and make sure that the hose is not squashed or kinked.. The controller is preset at the factory for the TAC GV sensor.

Follow these steps: 1 Enter Balancing mode by means of setting bit 10 in nciAppOp-

tions to 1 by using the TAC Xenta OP.

Mode

11 1213

VC1

VC2

Data

KC1

30 (88) Schneider Electric Buildings AB, Mar 2010

2 MIN and MAX flow is automatically reset to zero by the control-

ler.

3 Use the TAC Xenta OP to set the required MIN flow (true air flow

will be measured by a reference instrument). Use nviManOverrride (HVO_POSITION) to set the damper position in the desired position: use the + and - buttons to increase(>0)/decrease(<0) and stop the damper by entering 0. (alternative: the damper can be manually set to the desired position when disconnected from the actuator).

4 When required air flow has been obtained, use the TAC Xenta OP

to enter this value in nciMinFlow. Whe n Ente r is pressed the display shows 0 and the controller can read the current air velocity value for 15 sec. (0-100% of range 0-15 m/sec, 0-2950 f/m). On completion the display will show the value entered earlier. NB! If the air flow is allowed to fluctuate during the 15-second period the value recorded will be incorrect..

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

5 Apply required MAX flow following the same method as with the

MIN-flow (above).

6 The controller will now calculate scale factor, offset value, and

nominal airflow. The Balance mode will be reset automatically (nciAppOptions bit 10 reset to 0).

7 Scale factor and of fse t value ar e now available as SNVTs (nciBox-

Scale and nciBoxOffset), these values can now be entered in other equivalent box installations. nciNomFlow is calculated automatically and should not be entered using the TAC Xenta OP. The nciMinFlow and nciMaxFlow parameters can have other values than those used during the balancing procedure. The balancing procedure values are only used by application software once the balancing has been done, to limit the MIN- and MAX airflow.

Schneider Electric Buildings AB, Mar 2010 31 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

3.3 Commissioning

3.3.1 General

Once the mechanical and electrical installations have been completed the controller can be commissioned. This means:

Installing the controller on the network, setting node status and giving it an address.

• Set the controller's configuration parameters.

• Bind network variables.

• Test the functions. Before commissioning a complete zone system, read the "TAC Xenta -

Zone Systems Guideline" manual. The TAC Xenta OP can be used to set the basic parameters. Use a net-

work management tool or TAC Vista for commissioning the controller on the network and do the rest of the commissioning.

When TAC Xenta 100 will be used stand-alone, this is how:

3.3.2 Node Status

• Set node status to “Configured” with TAC Xenta OP.

• Set the basic parameters with TAC Xenta OP.

• Set the other parameters and variables with TAC Xenta OP. Commissioning can also be achieved using a network management tool.

The node status indicates which mode the controller is in, when it comes to network configuration and program. The statu s can b e chan ged 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 not configured when it leaves the factory. Neither the program nor the network communication are running. The service light emitting diode is flashing.

The controller must be configured before it can operate in a network (on line), see below.

Configuration parameters or network variables cannot be set in this state.

Configured, Online

Use TAC Xenta OP, TAC Vista or a network management tool to change the status to configured. When this has been done, the program and the network communication will be fully operational. The service LED is off. This is the normal state for a controller when it is operating.

32 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 3 Installation

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.

The parameters and variables can now be set.

Configured, Soft Offline

To get the controller into this state, you need a network management tool. The controller is programed and configured for a network, but the program and communications are idle. The light emitting diode is off. If the controller is reset, it will go into configured, online.

Configured, Hard Offline

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.3 Configuration Parameters (nci´s)

TAC Xenta 100 has a number of configuration parameters, that can be used to set the parameters of the controller. There are also network variables to control the controller when it is operating.

Use the commissioning protocol in Appendix B to write down your settings when commissioning. See Chapter 8, “Communication”, on page 65, for information about all parameters and variables, such as their index, accepted values, normal values. A detailed description of the parameters and variables can be found in chapters 4, 5, and 6.

3.3.4 Network Installation

For network installation, you need either a network management tool (LNS based or not) or TAC Vista. Examples of network management tools are MetraVision and LonMaker for Windows. For more information see “TAC Xenta, Guidelines for Zone Applications”.

The installation requires two steps: 1 Feed information about the controllers’ unique neuron-ID into the

network management tool’ s data base.

2 Allow the network management tool to install the controller on the

network. The controller will automatically be given an address.

Schneider Electric Buildings AB, Mar 2010 33 (88) 04-00069-01-en

3 Installation Zone Controller, TAC Xenta 102-ES

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, that is attached to every controller. It can be a good idea to collect these labels when you make the basic configuration, and stick them to a form, drawing or similar. There is a form for this purpose in the ?TAC Xenta, Guidelines for zone applications? manual.

2 Use the service pin function. You can only do this when the con-

troller is connected to the network. There is a service pin key in a hole in the upper left hand corner of the controller by terminal C1. Push the key to instruct the controller to send out its neuron-ID. The network management tool can then read the neuron-ID from the network and save it in its data base.

3.3.5 Network Variable Binding

The binding method is determined by the type of network management tool to be used. Detailed information can be found in the tool’s documentation. A description of how network variables are bound with Metra Vision can be found in the "TAC Xenta Network manual".

3.3.6 Function Test

Binding network variables is not an issue when the controller is used in a stand-alone operation.

Check that the controller works as intended. In Chapter 5, “Functional Description”, on page 41, all the controller’s

functions are described. In the event of a problem see Chapter 6, “Troubleshooting”, on page 57.

34 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 4 Configuration Parameters

4 Configuration Parameters

All communication with the controller is made using network variables.

• nci’s are used to configure the controller. 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).

• nvi’s control the controller during operation.

• nvo’s are output variables, which the controller sends out on the network.

In Chapter 8, “Communication”, on page 65, there is detailed information about accepted values and normal values for all parameters. All configuration parameters have normal values on delivery.

Schneider Electric Buildings AB, Mar 2010 35 (88) 04-00069-01-en

4 Configuration Parameters Zone Controller, TAC Xenta 102-ES

4.1 Basic Parameters

nciAppOptions

These parameters are used to set selectable functions in the controller. The parameter consists of 16 bits, where each bit represents one function choice. The bits 13 through 14 are not used. When you look at nciAppOptions with TAC Xenta OP, bit 0 is shown to the left.

Table 4.1: The Function of Different bits in nciAppOptions

Bit No. Function

Bit 0 0 1Occupancy sensor not connected

Occupancy sensor connected

Bit 1 0 1Energy hold off device (window contact) not connected

Energy hold off device (window contact) connected

Bit 2 0 1Fan control parallel mode

Fan control serial mode

Bit 3 0 1Fan disabled

Fan enabled

Bit 4 0 1Air quality controller disabled

Air quality controller enabled Bit 5 Heating setup options (see table below) Bit 6 Heating setup options (see table below) Bit 7 0 1Slave mode disabled

Slave mode enabled Bit 8 0 1Occupancy sensor: closed contact indicates presence

Occupancy sensor: open contact indicates presence Bit 9 0 If nviSetpoint has a valid value, the heating/cooling setpoints for the comfort

and economy modes are calculated using method B (see section 5.2.4).

1 If nviSetpoint has a valid value, the heating/cooling setpoints for the comfort

and economy modes are calculated using method A (see section 5.2.4). Bit 10 0 1Balancing mode disabled (see section 3.2.5)

Balancing mode enabled (see section 3.2.5). Bit 11 0 1Thermal actuators normally closed (NC)

Thermal actuators normally open (NO) Bit 12 0 1Stage 1 Heat Cut-Off at 2 l/sec. (4 cf/m)

Stage 1 & 2 Heat Cut-Off at 80% of nciMinFlowHeat

(valid for application SW 1.22 or higher) Bit 14 0 1ZS or STR101-104 and STR350/351 wall modules

STR150 wall module with display Bit 15 Reserved for production test. Should not be altered!

36 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 4 Configuration Parameters

Table 4.2: Heating option modes

Option Bits Outputs

B5 B6 V3/V4 V6 00 Inc./dec. TAO 10 TAO TAO 0 1 Inc./dec. Aux. output 1 1 TAO Aux. output

4.2 Other Configuration Parameters

The controller’s other configuration parameters are listed below together with a short description. See also Chapter 8, “Communication”, on page 65.

Index Name Description

0 nciLocation Location label 33 nciMinFlow Minimum flow 34 nciMaxFlow Maximum flow 35 nciBoxScale Air flow scale factor VAV-box 36 nciBoxOffset Air flow offset VAV-box 37 nciNomFlow Nominal flow 38 nciMinFlowHeat Minimum flow for heat 39 nciMinFlowStand Minimum flow standby 40 nciSetpoints Occupancy temperature setpoints 41 nciSpaceTempDev Max. deviation of zone temperature 42 nciSpaceTempLow Low limit of zone temperature 43 nciVAVGain Gain for VAV 44 nciVAV Itime Integral time for VAV 45 nciGainDamp Gain for damper 46 nciDampActStTime Stroke time for damper actuator 47 nciGainHeat Gain for heating controller 48 nciItimeHeat Integral time heating controller 49 nciHeatActStTime Stroke time for heating actuator 50 nciSpaceTempOfst Zone temperature sensor adjustment 51 nciFlowOfstSlave Flow offset for slave 52 nciCO2PerVolt Conversion factor ppm CO2 per volt 53 nciSpaceCO2Low Space CO2 level for closed damper 54 nciSpaceCO2High Space CO2 level for open damper 55 nciInstallType Source for network configuration 56 nciSndHrtBt Send heartbeat 57 nciRcvHrtBt Receive heartbeat

Schneider Electric Buildings AB, Mar 2010 37 (88) 04-00069-01-en

4 Configuration Parameters Zone Controller, TAC Xenta 102-ES

nciLocation

Used to make a label for the actual place where the controller is installed. In the operating panel, this parameter is shown as the first variable (Section 8.1, “General”, on page 65).

nciMinFlow

Used to set the minimum limit of the flow in the occupied mode (Section 5.2.5, “Temperature Control Sequence for TAC Xenta 102ES”, on page 48). Default value 12 l/s (25 cf/m).

nciMaxFlow

Used to setg the maximum limit of the flow. Default value 55 l/s (116 cf/m).

nciBoxScale

Used for airflow calibration (Section 3.2.6, “Air Flow Balancing Procedure”, on page 30). Default value 5.

nciBoxOffset

Used for airflow calibration (Section 3.2.6, “Air Flow Balancing Procedure”, on page 30). Default value 0.

nciNomFlow

Used to show the calculated nominal flow through the VAV box and is calculated in the airflow calibration (Section 3.2.6, “Air Flow Balancing Procedure”, on page 30). Default value 75 l/s (159 cf/m).

nciMinFlowHeat

Used to set the minimum value when heating is activated. Default value 10 l/s (21 cf/m).

nciMinFlowStand

Used to set the minimum limit of the flow in the standby mode (Section 5.2.5, “Temperature Control Sequence for TAC Xenta 102ES”, on page 48). Default value 5 l/s (10.5 cf/m).

nciSetpoints

Used to set the setpoint temperatures for heating and cooling in the different operation modes: comfort, economy, and off mode (Section 5.2.1, “Operation Modes”, on page 41 and Section 5.2.4, “Setpoint Calculation”, on page 46).

nciSpaceTempDev

Used to set the maximum allowed deviation of the zone temperature. Default value 2 °C (3.6 °F) . If larger deviations occur, bit 0 in nvoAlarmStatus is set (Section 5.3.7, “Alarm”, on page 53).

38 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 4 Configuration Parameters

nciSpaceTempLow

Used to set the lowest allowed zone temperature. Default value 10 °C (50 °F). If larger deviations occur, bit 1 in nvoAlarmStatus is set (Section 5.3.7, “Alarm”, on page 53).

nciVAVGain, nciGainHeat

Used to set the gain for the cooling/heating controllers. Default value

25.

nciGainDamp

Used to set the gain for the damper (air flow) controller. Default value 1.

nciVAVItime, nciItimeHeat

Used to set the I-time for the cooling/heating controllers. Default value 900 s (15 min).

nciDampActStTime and nciHeatActStTime

These parameters are set according to the runtime of the damper/heating actuators. Default value 165 s.

nciSpaceTempOfst

Used to adjust the reading from the temperature sensor or nviSpaceTemp. Default value 0.0 °C.

nciFlowOfstSlave

Used to add an offset to the flow of the slave controller (Section 5.3.8, “Master/slave Operation”, on page 54). Default value 0 l/s.

nciCO2PerVolt

Used to set a conversion factor for the signal from the carbondioxide sensor to the concentration in ppm. Default value 200 ppm/V.

nciSpaceCO2Low and nciSpaceCO2High

Used to set the limits for the air quality control. (Section 5.3.4, “Air Quality Control”, on page 51). Default values 400 ppm and 1000 ppm.

nciInstallType

This parameter is only used for free-standing operations and is set to show that the node itself should define its address (Section 8.5.3, “The Node Object’s Configuration Parameters (nci)”, on page 68).

nciSndHrtBt

Used to decide how often the nvo’s, that are sent out on the network regularly, should be sent (Section 8.3, “Monitoring Network Variables, Heartbeat”, on page 66).

Schneider Electric Buildings AB, Mar 2010 39 (88) 04-00069-01-en

4 Configuration Parameters Zone Controller, TAC Xenta 102-ES

nciRcvHrtBt

Used to decide the maximum period of time that can elapse between updating the nvi’s, for which the controller expects continuous updating (Section 8.3, “Monitoring Network Variables, Heartbeat”, on page 66).

40 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

5 Functional Description

5.1 General

The controller’s function is determined by its node status, operations and the methods used to force the controller to initiate well-adapted zone temperatur control. The co ntroller controller, which has a buil t-in air flow sensor, measures the zone temperature, and uses various methods to calculate setpoints. Apart from the basic functions, the controller can also be used to to control the climate in the zone.

Each section in this chapter ends with information about how 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, see Chapter 8, “Communication”, on page 65.

5.2 The Controller’s Basic Functions

5.2.1 Operation Modes

The controller has four selectable operation modes:

• Comfort

•Economy

•Bypass

•Off The operation mode is controlled by nviManOccCmd, but is aslo influ-

enced by occupancy sensors and the bypass key on the wall module.

Schneider Electric Buildings AB, Mar 2010 41 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

The relationship between operation modes is shown in Table 5.1, “The relationship between desired operation, bypass timer, occupancy sensor and current operation mode.”. There you also will find the controller’s values during stand-alone operation.

Table 5.1: The relationship between desired operation, bypass timer, occupancy sensor and current operation mode.

Desired operation

nviManOccCmd

Comfort Enabled No Effect. Comfort OC_OCCUPIED OC_OCCUPIED At a stand-still Occupancy detect.

Economy Enabled No Effect. Bypass OC_BYPASS OC_STANDBY At a stand-still No Effect. Economy OC_STANDBY Off Enabled No Effect. Bypass OC_BYPASS OC_UNOCCUPIED At a stand-still No Effect. Off OC_UNOCCUPIED Stand-alone Enabled Occupancy detect.

OC_NUL At a stand-still Occupancy detect.3

OC_BYP ASS Without significance No Effect Bypass OC_BYPASS

Bypass timer

Occupancy sens.

No occupancy

Current op. mode

Comfort Economy

Comfort Bypass

Comfort Off

nvoEffectOccup

OC_OCCUPIED OC_STANDBY

OC_OCCUPIED OC_BYPASS

OC_OCCUPIED OC_STANDBY

a. Activated by the bypass key on the wall module b. See section 5.3.6 occupancy sensors c. No sensor connected will result in OC_OCCUPIED

Comfort Mode

Comfort mode is the default mode, that is to say when someone is in the zone, ensure that the climate in the room is comfortable. 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 manual settings. The setpoints used are found in nciSetpoints (can be modified).

The alarm for zone temperature deviation, high CO2 concentration and air flow deviation can cut out, but the alarms for window contact and low zone temperature are blocked.

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 (can be modified). The controller is in this mode when nviManOccCmd = OC_STANDBY and the bypass key has not been

pressed. The air quality function is off. The LED of the wall module flashes slowly. The bypass key and the set-

point knob can be used to mak manual settings.

42 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

The alarm for zone temperature deviations, high CO2 concentration and air flow deviation are blocked, but the alarm for low zone temperature and window contact can cut out.

Bypass Mode

The bypass key on the wall module is used if you occasionally want to change to comfort mode from economy or off mode.

The nviOccManCmd variable is used to bypass an old value, which is stored, and start a timer, which will run according to nciBypassTime. When nciBypassTime has elapsed, nviOccManCmd resumes it’s previous state.

If the nviOccManCmd SNVT is updated thi s will have a higher priority, and the Bypass mode is left.

To avoid this, the nvo bound to the nviOccManCmd should not propagate on periond (set to 0). Only on Delta.

Off Mode

When the zone is not used for a longer period of time, the controller can be set to off mode. The controller is in this mode when nviManOccCmd=OC_UNOCCUPIED. In the off mode the controller does not control the environment and the damper is closed.

The light emitting diode on the wall module is out. The setpoint knob is blocked, but the bypass key is not. The alarm for zone temperature deviations, high CO2 concentration and air flow deviation are blocked, but the alarm for low zone temperature and window contact are enabled.

Index Variable Name Description

1 nvoEffectOccup Actual occupancy output 18 nviManOccCmd Occupancy scheduler input 40 nciSetpoints Occupancy temperature setpoints

5.2.2 Application, Manual and Emergency Modes

Application Modes

TAC Xenta 102-ES is designed to control both heating and cooling, and to automatically change from heating to cooling as necessary.

Schneider Electric Buildings AB, Mar 2010 43 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

Heating Case

Cooling Case

Heating Setpoint

Cooling Setpoint

Cooling Demand

Fig. 5.1: Changeover between heating and cooling cases

The controller changes control sequence by comparing the room temperature with each respective setpoint.

You can force the controller to heat only, cool only or night purge, just as you can force it to neither heat nor cool. This is achieved using nviApplicMode, see the table Table 5.2, “The relation between nviApplicMode and forcing.”.

Table 5.2: The relation between nviApplicMode and forcing.

nviApplicMode Forcing Description

HVAC_AUTO Automatic

(no forcing) HVAC_HEAT Heating only The controller can only heat. The cooling setpoint is neglected. HVAC_COOL Cooling only The controller can only cool. The heating setpoint is neglected. HVAC_NIGHT_PURGE Night purge The controller can only cool with night air and the damper fully open. HVAC_OFF Off The controller neither cools nor heats.

The controller automatically changes over between heating and cooling by comparing the room temperature with cooling and heating setpoints.

Manual Mode

To make it possible to manually force the air flow or the heating actuator to the desired level, the value can be set by using nviManOverride. Heating control is disabled in the manual mode. Manual mode has higher priority than the application and occupancy modes.

Table 5.3: The relation between nviManOverride and forcing.

nviManOverride Description

HVO_OFF Normal control HVO_POSITION Damper actuator (table 5.4 below) HVO_FLOW_VALUE Sets required airflow (l/s) HVO_FLOW_PERCENT Sets damper to required percentage (% of nciNomFlow) HVO_POSITION_1 Heating actuator (stage 1) (table 5.4 below) HVO_OPEN_2 Heating actuator (stage 2), on HVO_CLOSE_2 Heating actuator (stage 2), off

44 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

Table 5.4: HVO_POSITION and HVO_POSITION_1

nciAppOptions bit 5 0 1

HVO_POSITION V1 V2 HVO_POSITION_1 V3 V4 V3 V4 0 off off 0 off off off off >0 on off >0 on off on on <0 off on <0 off on off off

Emergency Mode

In some situations, the damper has to be forced fully opened or closed. This is done with nviEmergCmd. The Heating and fan control are disabled in emergency mode. The emergency mode has higher priority than all the other modes.

Table 5.5: The relation between nviEmergCmd and forcing.

nviEmergCmd Description

EMERG_NORMAL Normal control EMERG_PURGE Fully open damper (100%) EMERG_SHUTDOWN Fully closed damper (0%) EMERG_PRESSURIZE Fully open damper (100%) EMERG_DEPRESSURIZE Fully closed damper (0%)

Index Variable name Description

19 nviApplicMode Application mode input 25 nviManOverride VAV manual override input 26 nviEmergCmd Emergency command input 32 nciAppOptions Application options 37 nciNomFlow Nominal flow

5.2.3 Measuring Zone Temperature

You can measure the zone temperature either with a hard-wired thermistor sensor (usually in the wall module) or with a LonTalk temperature sensor node connected to nviSpaceTemp. If nviSpaceTemp has a valid value the controller will use it, if it doesn't the thermistor value will be used. The thermistor value can be adjusted by nciSpaceTempOfst when it receives a value; this is added to the thermistor value. The value the controller uses is also sent to nvoSpaceTemp.

Schneider Electric Buildings AB, Mar 2010 45 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

If neither value is valid, nvoSpaceTemp will receive the off value. nvoSpaceTemp is sent when it has changed by at least 0,1°C.

Index Variable name Description

5 nvoSpaceTemp Zone temperature output 20 nviSpaceTemp Zone temperature input 50 nciSpaceTempOfst Zone temperature sensor adjustment

5.2.4 Setpoint Calculation

Zone Temperature Setpoints

nciSetpoints define four temperature setpoints; heating setpoint comfort mode, cooling setpoint comfort mode, heating setpoint economy mode, cooling setpoint economy mode.

The smallest accepted deviation between the heating and cooling setpoints is 0,5 °C, and the cooling setpoints must be higher than the heating 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.6, “The setpoints in nciSetpoints.” shows accepted values and default values for the four temperature setpoints in nciSetpoints.

The setpoints for comfort and economy mode are basic setpoints, which can be changed with nviSetpoint, nviSetPntOffset and the setpoint knob.

Table 5.6: The setpoints in nciSetpoints.

Setpoint Min. Max. Normal

Cooling setpoint comfort 10 °C 35 °C 23 °C Heating setpoint comfort 10 °C Cooling setpoint economy 10 °C 35 °C 25 °C Heating setpoint economy 10 °C

a. If the cooling setpoint is 10 °C, the heating setpoint is set to 9,5 °C.

35 °C 21 °C

35 °C 19 °C

Calculation

The current setpoint, nvoEffectSetpt, depends on the current operation mode (nvoEffectOccup), current operation mode (nvoUnitStatus; mode) and nviSetpoint, nviSetpntOffset, nciAppOptions, nciSetpoints and a

46 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

nviSetpntOffset

Wall module Setpoint knob

nviSetpoint

nciAppOptions bit 9

nciSetpoints

Calculation according to method A or B if nviSetpoint has a valid value, otherwise no recalculation

Addition

Controller

nvoEffectSetpt

Econ., heat. setp.

Econ., cool.setp.

Comfort, heat.setp.

Comfort, cool.setp.

Fig. 5.2: The relationship between variables for the setpoint calculation.

The wall module’s setpoint knob only affects comfort and economy mode.

In comfort mode, the setpoints for method A and method B are the same.

possible local setpoint adjustment via the wall module. Fig. 5.2 shows the relationship 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.

Schneider Electric Buildings AB, Mar 2010 47 (88) 04-00069-01-en

nviSetPntOffset can be seen as a setpoint adjustment from a wall module connected to the network. Its value is added to setpoints for comfort and economy mode.

5 Functional Description Zone Controller, TAC Xenta 102-ES

Output signal

Heating stage 1

Heating stage 2

Cooling

100%

Cooling demand

Neutral zone

Fig. 5.3: Control sequence

In Appendix A there are detailed calculation examples of setpoint calculations.

Index Variable name Description

2 nvoUnitStatus Unit status output 4 nvoEffectSetpt Actual setpoint output 19 nviApplicMode Application mode input 21 nviSetpoint Temperature setpoint input 22 nviSetpntOffset Setpoint offset input 32 nciAppOptions Application options 40 nciSetpoints Occupancy temperature setpoints

5.2.5 Temperature Control Sequence for TAC Xenta 102-ES

The zone temperature is controlled by the airflow (cooling) and reheat coils/radiators. Fig. 5.3 shows the control sequence:

48 (88) Schneider Electric Buildings AB, Mar 2010

If cooling is required, a setpoint for the airflow is determined, nvoFlowControlPt. nvoFlowSetpoint describes the position of the damper in percent.

If heating is required, reheat stage 1 is activated. The airflow is controlled by the minimum airflow setpoint in nciMinFlowHeat.

When cooling, the airflow is controlled by nciMinFlow (occupied mode) or nciMinFlowStand (standby mode).

The zone temperature used for setpoint calculations, nvoSpaceTemp, is obtained either from a LonTalk temperature sensor (see Section 5.2.3, “Measuring Zone Temperature”, on page 45) or by the hard-wired temperature sensor.

For applications with fan control, see Section 5.3.3, “Fan Control”, on page 50.

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

The window contact overrides the current application mode and sets the forcing mode to “off” to save energy, see Section 5.3.5, “Window Contact”, on page 52.

Index Variable name Description

5 nvoSpaceTemp Zone temperature output

6 nvoFlowControlP Flow setpoint output

9 nvoFlowSetpoint Damper position output in percent

33 nciMinFlow Minimum flow

38 nciMinFlowHeat Minimum flow for heat

39 nciMinFlowStand Minimum flow standby

5.3 More About Functions

5.3.1 Cooling Control

The cooling value in nvoUnitStatus shows the current cooling output level. Accepted values for these variables range from 0% to 100% of the cooling capacity. The value 163.83% is sent as an invalid value to show that the damper is blocked. nvoBoxFlow shows the controlled air flow.

nvoTerminalLoad (current output heating/cooling) shows the current heating or cooling demand. Negative values indicate a heating demand and positive values indicate a cooling demand.

VAV controller

Type: PI Gain: 0-32.75; normal value: 25 I-time: 0-60 minutes; normal value: 15 minutes Dead band: 0.2 °C Control interval: 60 s

Index Variable name Description

2 nvoUnitStatus Unit status output

6 nvoFlowControlPt Flow setpoint output

7 nvoBoxFlow Box flow output

8 nvoTerminalLoad Heating/cooling demand output

43 nciVAVGain Gain for VAV

44 nciVAVItime Integral time for VAV

45 nciGainDamp Gain for damper

Note: The damper controller has a fixed integral time (90 sec).

Schneider Electric Buildings AB, Mar 2010 49 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

5.3.2 Heating Control

nvoHeatOutputPri, nvoHeatOutputSec and the heating value in nvoUnitStatus show the current heating output level. Accepted values

for these variables range from 0% to 100% of the heating capacity. The value 163.83% is sent as an invalid value to show that the heating stage is blocked.

Heating controller

Type: PI Gain: 0-32.75; normal value: 25 I-time: 0-60 minutes; normal value: 15 minutes Dead band: 0.2 °C Control interval: 60 s

If the airflow is less than 2 l/s (4 cf/m) [hysterezes 1 l/s (2 cf/m)] and the fan is not enabled, the heating control on outputs V3/V4 will be stopped (applies if nciOptions bit 12=0).

If the airflow is less than 80 % of nciMinFlowHeat, and the fan is not enabled, both heating stages will be stopped (applies if nciAppOptions bit 12=1 and only from application SW 1.22)

5.3.3 Fan Control

The analog output Y1 (0-10 V) repeats the value in nvoHeatOutputPri. When a thermal actuator is used, nciGainHeat and nciItimeHeat do not

work as they do with an increase/decrease actuator. The thermal actuator only uses on/off control with a hystrezes of 0.1°C.

Index Variable name Description

2 nvoUnitStatus Unit status output

11 nvoHeatOutputPri Heating output stage 1

12 nvoHeatOutputSec Heating output stage 2

47 nciGainHeat Gain for heating controller

48 nciItimeHeat Integral time for heating controller

49 nciHeatActStTime Stroke time for heating actuator

The TAC Xenta 102-ES also supports applications with fans. To enable the fan, set bit 3 in nciAppOptions to 1.

The fan can be in one of two modes:

• the fan is active during heating only (for paralell boxes). Bit 2 in nciAppOptions is set to 0 (default).

• the fan is continuosly active in the occupied mode or during heating or cooling in standby mode (for serial boxes). Bit 2 in nciAppOptions is set to 1.

50 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

Airflow

High limitLow limit

level

Fig. 5.4: Air quality control sequence

max

mini

In the manual mode and the emergency mode the fan is off.

Index Variable name Description

32 nciAppOptions Application options

5.3.4 Air Quality Control

In order to ensure the quality of air is good the TAC Xenta 102-ES controls the supply of fresh air to the controlled zone. If the carbon dioxide (CO2) sensor indicates a high concentracion of CO2, the damper opens and the air flow will increase. The air quality control can only be activated during cooling.

The air quality control can be enabled with the configuration parameter nciAppOptions, by setting bit 4 to 1. The CO2 sensor should be connected to input U1. When air quality control is enabled, the CO2-controller calculates an airflow setpoint based on the current CO2 concentration. The highest value from the VAV- or CO2-controllers is selected for use as the effective air flow setpoint.

The setpoints for CO2 concentration can be set in nciSpaceCO2Low (default value 400 ppm) and nciSpaceCO2High (default value 1000 ppm). The CO2 concentration can be measured either with a LonTalk CO2 sensor node connected to nviSpaceCO2 or with the hard-wired CO2 sensor.

nvoSpaceCO2 is used to monitor the current CO2 concentration. nvoSpaceCO2 is sent out when the value has changed more than 30

ppm. If nviSpaceCO2 receives an invalid value, the value from the hardwired sensor will be used.

100%

Index Variable name Description

14 nvoSpaceCO2 Zone CO2 sensor output 23 nviSpaceCO2 Zone CO2 sensor input 32 nciAppOptions Application options

Schneider Electric Buildings AB, Mar 2010 51 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

5.3.5 Window Contact

TAC Xenta 102-ES 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 sec. the window contact

alarm cuts out, bit 2 in nvoAlarmstatus (this only applies to Economy and Off-modes).

Index Variable name Description

3 nvoAlarmstatus Alarm status output 15 nvoEnergyHoldOff Energy hold off output 24 nviEnergyHoldOff Energy hold off input 32 nciAppOptions Application options

5.3.6 Occupancy Sensor

A sensor can be connected to TAC Xenta 102-ES to determine whether someone is in the room or not. If no occupancy sensor is 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 as a standalone unit, the sensor is used to choose between comfort mode or off mode. (See Section 5.2.1, “Operation Modes”, on page 41).

The sensor can be connected either directly to the controller, input X2, or via the network, nviOccSensor. To be able to use a sensor that is directly connected, bit 0 in nciAppOptions must be set to 1. When nviOccSensor has received a valid value, this is used, whether the sensor is directly connected or not.

Bit 8 in nciAppOptions indicates whether an open or closed input X2 should signify presence. Bit 8=0 signifies that a closed input X2 indicates presence. Bit 8=1 signifies that an open input X2 indicates presence.

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 delay of 20 minutes before the occupancy mode is changed from comfort to economy mode. The change in nvoOccSensor only

52 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

takes 250 ms to make it possible to use the occupancy sensor in other applications (light, alarm etc.).

Index Variable name Description

1 nvoEffectOccup Effective occupancy output 16 nvoOccSensor Occupancy sensor output 28 nviOccSensor Occupancy sensor input 32 nciAppOptions Application options

5.3.7 Alarm

When TAC Xenta 102-ES reports alarms to a monitoring system, it is achieved using the network variable nvoAlarmStatus. The variable has 16 bits, each of which correspond to to different alarm situations.

Table 5.7: Alarm modes for nvoAlarmStatus

Bit no Alarm Cuts out when... Is reset when...

0 Deviating zon e

temperature

1 Low zone tempera-

ture

2 Window contact

alarm

3 High CO2 level The CO2 concentration is 200 ppm more

4 Deviation of box

flow

10 Not bound vari-

ables have been set to default values.

11 Adaptation of ther-

mistor

12 Bound network

variables not received

13 Not valid value on

input

14 No application

program

15 Cannot write to

EEPROM

The deviation in zone temp. is larger than nciSpaceTempDev for more than 60 minutes (Comfort mode).

The zone temp. is lower than the value in nciSpaceTempLow formore than 60 min (Off and economy mode).

Energy hold off (window contact)is active for more than 60 s (Off and economy mode).

than nciSpaceCO2High for more than 60 min. (Comf. mode).

The deviation in the box flow is more than 10% of nciMaxFlow for more than 30 min. (Comf. mode).

Power on. (Power cycle)

Internal memory error. The controller must be changed.

Bound network variables have not been received within set time. nciRcvHrtBt

An input network variable falls outside its accepted values.

No valid application program. The application program is loaded. Con-

The controller is faulty. The controller must be changed.

The deviation in zone temp. is smaller than the value in nciSpaceTempDev (hys- teresis 0.5 °C).

The zone temp. is more than 2°C above the value in nciSpaceTempLow.

The controller no longer detects the state.

When the first not bound variables have been updated.

When network variables have been received.

The variable is given an accepted value.

tact the nearest Schneider Electric service point.

Schneider Electric Buildings AB, Mar 2010 53 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

Master

nvoHeatSlaveSec

nciAppOptions

bit 7 = 0

nvoHeatSlaveR

nvoBoxFlow

nviBoxFlowSlave

nviHeatSlaveR

nviHeatSlaveSec

nciAppOptions

bit 7 = 1

Slave

Wall Module

Inputs and Outputs

Airflow input

Outputs

Fig. 5.5: Variable bindings between master/slave controllers

Index Variable name Description

3 nvoAlarmStatus Alarm status output 41 nciSpaceTempDev Max. deviation of zone temperature 42 nciSpaceTempLow Low limit of zone temperature 57 nciRcvHrtBt Receive heartbeat

5.3.8 Master/slave Operation

As the controller can control a number of slave units, it is possible to control several TAC Xenta 102-ES controllers within the same zone. When bit 7 in nciAppOptions is active (=1) the controller works as a slave, at all other times it works as as a master. The slave and the master controller must be of the same type, that is the actuator run times must be identical.

The communicating network variables between the master controller and all slave controllers are bound according to Fig. 5.5. Apart from nvoUnitStatus, no other nvo’s have reliable values, and therefore they should not be bound to other units. If a slave is equipped with fan control, nviEmergCmd in both master and slave must be bound for proper emergency handling.

A TAC Xenta 102-ES working as a slave controller only controls the airflow in the VAV-box, heating stage 1 and stage 2 according to the values sent by its master controller on the network. It does not consider other inputs. The forcing mode of the controller that can be read using nvoUnitStatus, is set to off for the slave.

54 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 5 Functional Description

Index Variable name Description

2 nvoUnitStatus Unit status output 7 nvoBoxFlow Box flow output 10 nvoHeatSlaveR Heating control output stage 1 for slave 13 nvoHeatSlaveSec Heating control output stage 2 for slave 26 nviEmergCmd Emergency command input 27 nviHeatSlaveR Heating control input stage 1 for slave 30 nviHeatSlaveSec Heating control input stage 2 for slave 31 nviBoxFlowSlave Box flow input for slave 32 nciAppOptions Application options 51 nciFlowOfstSlave Flow offset for slave

5.3.9 Additional Features

The TAC Xenta 102-ES has three additional features not found in any of the other zone controllers in the TAC Xenta 100 family.

Free Network Controlled Output (V6)

The output can be used in two ways: If bit 6 in nciAppOptions=1 (see section 4.1), the output can be used

freely for other purposes and is controlled by nviAuxInput. If bit 6 in nciAppOptions=0 (see section 4.1), the output is used for con-

trolling the second stage of reheating.

Output Heating Stage 1 (Y1)

The output has the same value as nvoHeatOutputPri. The range of the output is 0-10 V (0-100% of heating demand).

Auxiliary Temperature Sensor (B2)

An auxiliary temperature sensor can be connected to the controller and be presented as a SNVT, nvoAuxTemp.

Index Variable name Description

5 nvoSpaceTemp Zone temperature output 11 nvoHeatOutputPri Heating stage 1 output 17 nvoAuxTemp Auxiliary temperature output 29 nviAuxInput V6 used as a free network controlled output 32 nciAppOptions Application options

Schneider Electric Buildings AB, Mar 2010 55 (88) 04-00069-01-en

5 Functional Description Zone Controller, TAC Xenta 102-ES

56 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 6 Troubleshooting

6 Troubleshooting

6.1 General

The TAC Xenta 102-ES is a reliable controller. However, if problems do occur, use the trouble-shooting tips in this chapter. If you need further help, please contact your nearest Schneider Electric service point.

6.2 Inputs and Outputs (nvi/nvo)

The most important variables for information on the current status of the controller during operation, are the nvo’s and the nvi’s.

You can use these to check the controller’s operation and remedy any faults or disturbances.

Schneider Electric Buildings AB, Mar 2010 57 (88) 04-00069-01-en

6 Troubleshooting Zone Controller, TAC Xenta 102-ES

A list and short description of all the nvi’s and the nvo’s can be found in below. In Fig. 8, you can find a comprehensive information about all the variables including index, variable name, function, accepted values, normal values etc.

Index Name Description

1 nvoEffectOccup Effective occupancy output 2 nvoUnitStatus Unit status output 3 nvoAlarmStatus Alarm status output 4 nvoEffectSetpt Effective setpoint output 5 nvoSpaceTemp Zone temperature output 6 nvoFlowControlPt Flow setpoint output 7 nvoBoxFlow Box flow output 8 nvoTerminalLoad Heating/cooling demand output 9 nvoFlowSetpoint Damper position output (%) 10 nvoHeatSlaveR Heating control output stage 1 for slave 11 nvoHeatOutputPri Heating stage 1 12 nvoHeatOutputSec Heating stage 2 13 nvoHeatSlaveSec Heating control output stage 2 for slave 14 nvoSpaceCO2 Zone CO2 sensor output 15 nvoEnergyHoldOff Energy hold off output, window contact status, input X3 16 nvoOccSensor Occupancy sensor output. Only input X2 is copied. See nviOccSensor for net information. 17 nvoAuxtemp Auxiliary temperature output. 18 nviManOccCmd Choice of operating mode 19 nviApplicMode Application mode input (forcing the controller) 20 nviSpaceTemp Zone temperature input, replaces input B1 at a valid value 21 nviSetpoint Temperature setpoint input, which at a valid value, recalculates nciSetpoints 22 nviSetpntOffset Setpoint deviation 23 nviSpaceCO2 Zone carbondioxide level input 24 nviEnergyHoldOff Energy hold off input, window contact, determines operation mode together with input X3 25 nviManOverride VAV manual override input 26 nviEmergCmd Emegency command input 27 nviHeatSlaveR Heating control input stage 1 for slave 28 nviOccSensor Occupancy sensor input, determines operation mode together with input X2 29 nviAuxInput Output V6 controlled as a free network output 30 nviHeatSlaveSec Heating control input stage 2 for slave 31 nviBoxFlowSlave Flow control input for slave

58 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 6 Troubleshooting

6.3 Troubleshooting Guide

What affects... Check...

Operation?

Operation mode? (Forcing of controller)

Control setpoint?

Read room temperature?

Air flow?

• 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 variable, nviOccSensor. If the occupancy sensor has indicated presence, it takes 20 minutes before it is disabled.

• How the content in nvoEffectOccup can be af fected. See Section 5.2.1, “Operation Modes”, on page 41.

• Order via network, nviManOccCmd.

• Chosen settings in nciAppOptions

• Order via network, nviApplicMode

• If a window contact (X3) or similar network variable, nviEnergyHoldOff, is enabled.

• Outputs heating/cooling, nvoUnitStatus, nvoTerminalLoad, nvoHeatOutputPri, nvoHeatOutputSec which are affected by normal control.

• Current operation mode, nvoEffectOccup

• Current unit status, nvoUnitStatus

• Set basic setpoints, nciSetpoints. Controlled by options chosen nciAppOptions with respect to calculation methods A or B together with nviSetpoint control this. Not a valid value in nviSetpoint gives the basic setpoints. See Section 5.2.4, “Setpoint Calculation”, on page 46.

• nviSetpntOffset and/or the setpoint knob on the wall module. Results in +/- influence.

• Physical reading (B1) or similar network variable, nviSpaceTemp. A valid value on the net- work overrides a physical reading. nciSpaceTempOfst can displace the value.

• Current values in nciMinFlow, nciMaxFlow, nciMinFlowStand, nciMinFlowHeat, nciNom- Flow, nvoFlowContrlPt and nvoBoxFlow.

• Current application mode.

• Current operation mode.

• CO2 controller influence.

That an alarm is set?

The LED on the wall module?

Schneider Electric Buildings AB, Mar 2010 59 (88) 04-00069-01-en

• Current operation mode, nvoEffectOccup

• Current values in nciSpaceTempDev and nciSpaceTempLow.

• Current values in nciSpaceCO2High

• Current values in nciMaxFlow (10% deviation).

• If a window is open (window contact). See Section 5.3.7, “Alarm”, on page 53.

• The controller receives power when the LED is out.

• The controller when the se rvice LED is lit. This indicates that the controller does not work correctly and should be replaced.

• The controller when the service LED is lit for ap pr. 20 seconds and then goes out. This is not a fault, but an indication that the controller answers a “wink” command from the network.

• Current operation.

6 Troubleshooting Zone Controller, TAC Xenta 102-ES

60 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 7 Technical Data

7 Technical Data

7.1 Technical Data

Power

Supply voltage:

102-ES 24 V AC +/-20% 50–60 Hz

Power consumption:

Controller with TAC Xenta OP 6 VA Digital outputs max. 6 x 19 = 114 VA Total max. 120 VA

Ambient temperature:

Operation 0 to 50 °C (32 to 122 °F) Storage -20 to 50 °C (-4 to 122 °F) Humidity max. 90% RH, non-condensing

Enclosure:

Material ABS/PC plastic Enclosure rating IP 30 Color grey/red Dimensions 122 x 126 x 50 mm (4.8 x 5 x 2 in) Weight 0.4 kg (0.88 lb)

Schneider Electric Buildings AB, Mar 2010 61 (88) 04-00069-01-en

7 Technical Data Zone Controller, TAC Xenta 102-ES

Inputs/Outputs

Input for occupancy sensor, X2:

Voltage across open contact 23 V DC ± 1 V DC Current through closed contact 4 mA Minimum pulse input duration 250 ms Input for window contact, X3: Voltage across open contact 23 V DC ± 1 V DC Current through closed contact 4 mA Minimum pulse input duration 18 s

Outputs for damper actuator, V1-V2, reheat actuator, V3-V4, fan, V5, reheat actuator or free network output, V6:

Minimum output voltage supply voltage – 1.5 V AC Maximum load (per output) 0.8 A

Input for bypass button on wall module, X1:

Minimum pulse input duration 250 ms Maximum current, LED 2 mA, for STR100 series

Inputs for zone and auxiliary temperature sensor, B1-B2:

Thermistor type 1800 . at 25 °C (77 °F) Measuring range -10 to 50 °C (14 to 122 °F) Accuracy ±0.2 °C (±0.4 °F) Input for carbon dioxide sensor, U1: Measuring range 0–10 V DC Accuracy ±0.1 V

Air flow input based on TAC GV sensor characteristics at duct velocity 1 to 15 m/s (3 to 50 ft./s).

Input setpoint adjustment on wall module, R1:

Type Adjustment range Accuracy Output heating stage 1, Y1: Output range Max current Accuracy

10 k. linear potentiometer

±5 °C (±9 °F)

±0.1 °C (±0.2 °F)

0 – 10 V

.2 mA

0.2 V at full load

Application program:

Cycle time 6 s

62 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 7 Technical Data

LED (light emitting diode) colors:

Power green Service red

Interoperability:

Standard

TAC Xenta 102-ES conforms to LONMARK Interoperability Guidelines

LONMARK Functional Profile: VAV Controller Communication protocol LONTALK Physical channel TP/FT-10, 78 kbps

Neuron

type 3150®, 10 MHz

Conformance to standards:

Emission C-Tick, EN 50081-1, FCC Part 15 Immunity EN 50082-1 Safety: CE EN 61010-1 UL 916 Energy Management Equipment ETL listing UL 3111-1, first edition

CAN/CSA C22.2 No. 1010.1-92

Flammability class, materials UL 94 V-0

Part numbers:

TAC Xenta 102-ES Controller 007305370 Manual (GB) 0-004-7663 Plug-in Terminal Blocks TAC Xenta 100 007309140

Disk with external interface files (XIF) for the TAC Xenta 100 series

000855824

Schneider Electric Buildings AB, Mar 2010 63 (88) 04-00069-01-en

7 Technical Data Zone Controller, TAC Xenta 102-ES

126 (4.96")

110 (4.33")

112 (4.41")

98 (3.86")

118 (4.65")

122 (4.80")

50 (2")

Fig. 7.1: Dimensions for TAC Xenta 102-ES

7.2 Dimensions

64 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 8 Communication

8 Communication

8.1 General

The controller consists of two LonMark objects: the node object and the controller object. These objects are monitored using the network variables nviRequest (object request) and nvoStatus (object status).

The network variable nciLocation (position mark) is used when configuring the basic parameters 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 the following location label:

TAMF.main.floor3.room343/RC40

A LNS based network management tool uses nciLocation when a data base needs to be recreated. The monitoring of an installed network is made by the LNS tool reading nciLocation, and then using the informa- tion to give the node a subsystem name and a unit name. The string should therefore consist of a name and a search path for the subsystem, followed by a slash and the unit name, that is:

system.subsystem[.subsystem...]/unit name

8.2 Default Settings and Power On

For all network variables the following 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 (starting up)

• Synchronized: NO

• Change/update only when the controller is not active on the network; flags = NO

• Restart of TAC Xenta 102-ES after change; flags = YES

All network variables have the same index as they have in the operator panel TAC Xenta OP. They represent the order in which th ey have been declared in the system program; as the order is important for the variables’ self documentatory strings. The variables are of a standard type

Schneider Electric Buildings AB, Mar 2010 65 (88) 04-00069-01-en

8 Communication Zone Controller, TAC Xenta 102-ES

or so called SNVT. The values that 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). To learn more about SNVT/SCPT/UCPT see “The SNVT Master List and Programmer's Guide” on the internet address www.lonmark.org.

At power on, all variables for inputs and outputs (nvi and nvo) receive their default values. On a restart the configuration parameters (nci) retain their earlier set values. After a restart, every nvi’s will send a request to all the nvo’s they are bound to (a poll).

8.3 Monitoring Network Variables, Heartbeat

The Heartbeat function in TAC Xenta 102-ES 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-ES 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. An alarm will also be enabled, bit 12 in nvoAlarmStatus.

The outputs monitored in this way, are found in the list of network variables. (Section 8.6.1, “The Controller Objects Inputs (nvi)”, on page 71)

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-ES are monitored, so even if the values are not changed, they are sent out at even intervals.

The outputs monitored in this way, are found in the list of network variables. (Section 8.6.2, “The Controller Objects Outputs (nvo)”, on page 72)

The time is set with the variable nciSndHrtBt. Its normal value is 0.0, which means that no monitoring is performed.

8.4 Not Accepted Values

All nvo’s are limited to their accepted values, and all nvi’s detect whether the incoming value is within the accepted limits. If the value is not accepted, the controller activates bit 13 in the variable for alarm

66 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 8 Communication

nv1

nv2

nv6

nviRequest SNVT_obj_request

nvoStatus SNVT_obj_status

nvoFileStat SNVT_file_status

nciInstallType SNVT_config_src

Configuration Properties

Mandatory Network Variables

Optional Network Variables

0 - Node Object

Object Type: 0

nv5

nviFileReq SNVT_file_req

Fig. 8.1: The node object

handling, nvoAlarmStatus. For a nvi, the controller uses the invalid value, which is also counted as an accepted value.

8.5 The Node Object

The variables in the node object (figure 8.1) are divided into three categories:

• Mandatory (M)

• Optional (O)

• Configuration properties (C)

The category “Mandatory” contains all compulsory variables “Optional” contains selectable variables, and ”Configuration properties” contains the configuration parameters.

Note

• The network variables’ indexes are not the same as the figure in “nv” in the figure.

Schneider Electric Buildings AB, Mar 2010 67 (88) 04-00069-01-en

1. According to LonMark standardised function profil for VAV controllers

8 Communication Zone Controller, TAC Xenta 102-ES

8.5.1 The Node Object’s Inputs (nvi)

Table 8.1: The Node Object’s Inputs (nvi)

Index Variable Hb

58 nviRequest No SNVT_obj_request 0=RQ_NORMAL

60 nviFileReq No SNVT_file_req see “SNVT Master List” FR_NUL

SNVT

Accepted values (Service type)

2=RQ_UPDATE_STATUS 5=RQ_REPORT_MASK

Default value

RQ_NUL Confirmed

Confirmed

a. Hb=Heartbeat

8.5.2 The Node Object’s Outputs (nvo)

Table 8.2: The Node Object’s Outputs (nvo)

Index Variable Hb

59 nvoStatus No SNVT_obj_status invalid_id (0..1)

61 nvoFileStat Yes SNVT_file_status see ”SNVT Master List” FS_NUL

SNVT

Accepted values (Service type)

invalid_request(0..1)

Default value

Alla = 0 (Confirmed)

(Confirmed)

a. Hb=Heartbeat

8.5.3 The Node Object’s Configuration Parameters (nci)

Description (self doc. string)

Object request @0|1

File request @0|5

Description (self doc. string)

Object status @0|2

File status @0|6

Table 8.3: The Node Object’s Configuration Parameters (nci)

SNVT

Index Variable Hb

55 nciInstallType No SNVT_config_rsc

SCPT/UCPT

SCPT_nwrk_config (25)

Accepted values

0=CFG_LOCAL 1=CFG_EXTERNAL CFG_NUL

a. Hb=Heartbeat

Default value

0=CFG_LOCAL Network configu-

Description (self doc. string)

ration source &0,,0\x80,25

68 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 8 Communication

8.6 The Controller Object

The variables in the controller object (figure 8.2) are divided into four categories:

• Mandatory (M)

• 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” includes all other variables that make the controller’s functions possible.

1. According to LonMark standardised function profil for VAV controllers

Schneider Electric Buildings AB, Mar 2010 69 (88) 04-00069-01-en

8 Communication Zone Controller, TAC Xenta 102-ES

nv1

nv2

nv3

nv4

nv6

nv7

nv8

nv9

nv11

nv17

nv18

nv19

nv11

nv12

nv13

nv14

nviSpaceTemp SNVT_temp_p

nviSetpoint SNVT_temp_p

nviManOccCmd SNVT_occupancy

nviSetpntOffset SNVT_temp_p

nviEnergyHoldOff SNVT_switch

nviHeatSlaveR SNVT_count_f

nvoSpaceTemp SNVT_temp_p

nvoUnitStatus SNVT_hvac_stat

nvoFlowControlPt SNVT_flow

nvoBoxFlow SNVT_flow

Configuration Properties

Manufacturer Defined Section

Mandatory Network Variables

Optional Network Variables

1 - VAV Controller Object

Object Type: 8010

nv16

nvoEffectSetpt SNVT_temp_p

nvoTerminalLoad SNVT_lev_percent

nviApplicMode SNVT_hvac_mode

nv5

nv13

nviManOverride SNVT_hvac_overid

nviEmergCmd SNVT_hvac_emerg

nviSpaceCO2 SNVT_ppm

nciLocation SNVT_str_asc nciSetpoints SNVT_temp_setpt nciMinFlow SNVT_flow nciMaxFlow SNVT_flow nciNomFlow SNVT_flow nciMinFlowHeat SNVT_flow nciMinFlowStand SNVT_flow nciVAVGain SNVT_multiplier nciSndHrtBt SNVT_time_sec nciRcvHrtBt SNVT_time_sec

nciAppOptions SNVT_state nciGainDamp SNVT_multiplier nciGainHeat SNVT_multiplier nciItimeHeat SNVT_time_sec nciHeatActStTime SNVT_time_sec nciVAVItime SNVT_time_sec nciDampActStTime SNVT_time_sec nciCO2PerVolt SNVT_ppm nciSpaceCO2Low SNVT_ppm nciSpaceCO2High SNVT_ppm nciFlowOfstSlave SNVT_flow_f nciSpaceTempDev SNVT_temp_p nciSpaceTempLow SNVT_temp_p nciSpaceTempOfst SNVT_temp_p nciBoxOffset SNVT_count_f nciBoxScale SNVT_count_f

nv6

nv7

nv8

nv9

nv10

nv2

nv3

nvoAlarmStatus SNVT_state

nv4

nvoOccSensor SNVT_occupancy

nvoFlowSetpoint SNVT_lev_percent

nvoHeatSlaveR SNVT_count_f

nv5

nvoHeatOutputPri SNVT_lev_percent

nvoHeatOutputSec SNVT_lev_percent

nvoHeatSlaveSec SNVT_lev_disc

nvoSpaceCO2 SNVT_ppm

nvoAuxTemp SNVT_temp_p

nv15

nviOccSensor SNVT_occupancy

nvoAuxInput SNVT_lev_disc

nviHeatSlaveSec SNVT_lev_disc

nviBoxFlowSlave SNVT_flow

nv20

nvoEffectOccup SNVT_occupancy

nv1

nvoEnergyHoldOff SNVT_switch

Fig. 8.2: The controller object

Note! The network variables’ indexes are not the same as the figure in “nv” in the figure.

70 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 8 Communication

8.6.1 The Controller Objects Inputs (nvi)

Table 8.4: The Controller Objects Inputs (nvi)

Index Variable Hb

18 nviManOccCmd No SNVT_occupancy 0=OC_OCCUPIED

19 nviApplicMode Yes SNVT_hvac_mode 0=HVAC_AUTO

20 nviSpaceTemp Yes SNVT_temp_p –10 °C to 50 °C,

21 nviSetpoint No SNVT_temp_p 10 °C to 35 °C,

22 nviSetpntOffset Yes SNVT_temp_p –10 °C to 10 °C

23 nviSpaceCO2 Yes SNVT_ppm 0 to 5000 ppm

24 nviEnergyHoldOff Yes SNVT_switch 0=Off, 1=On,

25 nviManOverride No SNVT_hvac_overid

26 nviEmergCmd No SNVT_hvac_emerg 0=EMERG_NORMAL

27 nviHeatSlaveR Yes SNVT_count_f –50 to 50 0 Heating control

28 nviOccSensor Yes SNVT_occupancy 0=OC_OCCUPIED

29 nviAuxInput No SNVT_lev_disc 0=OFF or ST_NUL

30 nviHeatSlaveSec No SNVT_lev_disc 0=OFF or ST_NUL

31 nviBoxFlowSlave No SNVT_flow 0 to 65534 l/s

a. Hb=Heartbeat b. Invalid value

SNVT Accepted values Default value

OC_NUL Occupancy sched-

HVAC_AUTO Application mode

327,67 °C

0 °C (32 °F) Setpoint offset

65535b ppm Zone CO2 input

Off, 0% Energy hold off

HVO_OFF Manual override

EMERG_ NORMAL

OC_NUL Occupancy sensor

0 Contr. V6 as free

0Heat contr. inp.

0 Flow control input

state percent flow

1=OC_UNOCCUPIED 3=OC_STANDBY other values=OC_NUL 255=OC_NUL

1=HVAC_HEAT 3=HVAC_COOL 4=HVAC_NIGHT_PURGE 6=HVAC_OFF other values= HVAC_AUTO

(14 °F to 122 °F) 327,67 °C(*2)

(50 °F to 95 °F) 327, 67 °C(*2)

(14 °F to 50 °F)

65535*2

0% to 100%

HVO_OFF 1=HVO_POSITION 2=HVO_FLOW_VALUE 3=HVO_FLOW_PERCENT 17=HVO_POSITION_1 36=HVO_OPEN_2 37=HVO_CLOSE_2 oth. values=HVO_OFF

1=EMERG_PURGE 2=EMERG_SHUTDOWN 3=EMERG_PRESSURIZE 4=EMERG_DEPRESSURIZE, all others= EMERG_NORMAL

1=OC_UNOCCUPIED other values=OC_NUL

1=all other states

0 to 138 200 cf/m

description (Self doc. string)

uler input @1|8

input @1|5

Zone temperature Input @1|1 Temperature setpoint input @1|2

input @1|7

@1|13

input Enabled at 1=On and ¹ 0%, @1|11

input @1|6

Emergency command input @1|9

input for slave, @1#11

input @1#12

network contr. output @1#13

stage 2 for slave, @1#14

for slave, @1#15

Schneider Electric Buildings AB, Mar 2010 71 (88) 04-00069-01-en

8 Communication Zone Controller, TAC Xenta 102-ES

8.6.2 The Controller Objects Outputs (nvo)

Table 8.5: The Controller Objects Outputs (nvo)

Index Variable Hb

SNVT Accepted values Default value

1 nvoEffectOccup Yes SNVT_occupancy 0=OC_OCCUPIED

1=OC_UNOCCUPIED

OC_OCCUPIED Effective occupancy

Description (Self doc. string)

output, @1#1 2=OC_BYPASS 3=OC_STANDBY

2 nvoUnit Status Yes SNVT_hvac_status mode

heat_output_primary

heat_output_secondary

cool_output

econ_output fan_output

in_alarm

3 nvoAlarmStatus Yes SNVT_state 16 bits, 0=normal,

4 nvoEffectSetpt Yes SNVT_temp_p 10 °C to 35 °C

5 nvoSpaceTemp Yes SNVT_temp_p –10 °C to 50 °C,

6 nvoFlowControlPt Yes SNVT_flow 0 to 65534 l/s

7 nvoBoxFlow Yes SNVT_flow 0 to 65534 l/s

1=HVAC_HEAT 3=HVAC_COOL 4=HVAC_NIGHT_PURGE 6=HVAC_OFF 0% to 100% 163,83%(*2) 0% to 100% 163,83%(*2) 0% to 100% 163,83%(*2) 163,83%(*2) 0% to 100%, 163,83%(*2) 255(*2)

1 = alarm

327,67 °C(*2)

65534(*2)

HVAC_HEAT

Unit status output)

@1|4

163,83%

255 00000000

00000000 327,67 °C

Alarm status output

@1#2

Actual setpoint out-

put,@1|16

327,67 °C

Zone temp. output

@1|3

0 l/s Flow setpoint output,

@1|17

0 l/s Box flow output @1|18

65534(*2)

8 nvoTerminalLoad Yes SNVT_lev_percent –163,84% to 163,84% 0% Heat./cool. demand

output, @1|19

9 nvoFlowSetpoint Yes SNVT_lev_percent 0% to 100% 0% Damper position output

(%), @1#3

10 nvoHeatSlaveR Yes SNVT_count_f –50 to 50 0 Heat. contr. out put

stage 1 slave, @1#4

11 nvoHeatOutputPri No SNVT_lev_percent 0% to 100% 0% Heating stage 1 out-

put,@1#5

12 nvoHeatOutput Sec No SNVT_lev_percent 0% to 100% 0% Heating stage 2 out-

put,@1#6

13 nvoHeatSlave

Sec

14 nvoSpaceCO2 Yes SNVT_ppm 0 to 5000

15 nvoEnergy

HoldOff

No SNVT_lev-disc 0=OFF or ST_NUL

1=all other states

0 Heat. contr. output

stage 2 slave @1#7

65535(*2) ppm Zone CO2 sensor

65535(*2)

Yes SNVT_switch 0=Off, 1=On

Off, 0% Energy hold off out-

0% to 100%

output, @1#8

put. Off, 0% = no hold

off, @1|20

16 nvoOccSensor Yes SNVT_occupancy 0=OC_OCCUPIED

1=OC_UNOCCUPIED

OC_NUL Occupancy sensor out-

put, @1#9 255=OC_NUL

17 nvoAuxTemp No SNVT_temp_p –10 °C to 50 °C,

(14 °F to 122 °F)

Aux. temperature out-

put, @1#10

a. Hb=Heartbeat b. Invalid value

72 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES 8 Communication

8.6.3 The Controller Object’s Configuration Parameters (nci)

Table 8.6: The Controller Object’s Configuration Parameters (nci)

SNVT

Index Variable Hb

nciLocation

32 nciAppOptions No SNVT_state

33 nciMinFlow No SNVT_flow

34 nciMaxFlow No SNVT_flow

35 nciBoxScale No SNVT_count_f

36 nciBoxOffset No SNVT_count_f

37 nciNomFlow No SNVT_flow

38 nciMinFlowHeat No SNVT_flow

39 nciMinFlowStand No SNVT_flow

40 nciSetpoints No SNVT_temp_setpt

41 nciSpaceTempDev No SNVT_temp_p

42 nciSpaceTempLow No SNVT_temp_p

43 nciVAVGain No SNVT_multiplier

44 nciVAVItime No SNVT_time_sec

45 nciGainDamp No SNVT_multiplier

46 nciDampActStTime No SNVT_time_sec

47 nciGainHeat No SNVT_multiplier

48 nciItimeHeat No SNVT_time_sec

49 nciHeatActStTime No SNVT_time_sec

SCPT/UCPT

No SNVT_str_asc

SCPT_location (17)

UCPT (1)

SCPTminFlow(54)

SCPTmaxFlow(51)

UCPT (32)

SCPTnomAirFlow (57)

SCPTminFlowHeat (55)

SCPTminFlowStby (56)

SCPTsetPnts (60)

UCPT (16)

UCPT (17)

SCPTgainVAV(66)

UCPT (3)

UCPT (2)

UCPT (3)

UCPT (2)

UCPT (3)

Accepted values Default value

31 ASCII signs All = 0 Location label

16 bits, 0–1 00000000

00000000

0 to 65535 12 l/s (25 cf/m) Minimum flow

0 to 65535 55 l/s (116 cf/m) Minimum flow

-50 to 50 5 Air flow scale factor

-50 to 50 0 Air flow offset VAV

0 to 65535 75 l/s (159 cf/m) Nominal flow

0 to 65535 10 l/s (21 cf/m) Minimum flow for heat

0 to 65535 5 l/s (10.5 cf/m) Minimum flow

10 °C to 35 °C (50 °F to 95 °F)

0°C to 10°C (32 °F to 50 °F)

0 °C to 20 °C(32 °F to 68 °F)

0 to 32,7675 25 Gain for VAV

0 s to 3600 s (60 minutes)

0 to 32,7675 1 Gain for damper

0 s to 3600 s (60 minutes)

0 to 32,7675 25 Gain for heating con-

0 s to 3600 s (60 minutes)

occ cool = 23 °C (73 °F) stby cool = 25°C (77 °F) (unoc cool = 28°C) (82 °F) occ heat = 21°C (70 °F) stby heat = 19°C (66 °F) unoc heat = 16°C) (61 °F)

2 °C (3.6 °F) Max.dev.of zone temp

10 °C (50 °F) Low lim. of zone temp.

900 s (15 minutes)

165 s Stroke time for

900 s (15 minutes)

165 s Stroke time for heating

Description (Self doc. string)

&1,1,0\x80,17 Application options

&1,1,3\x8A,1

&1,1,0\x80,54

&1,1,0\x80,51

VAV, &1 ,1, 3\x 80, 32

&1,1,3\x80,32

&1,1,0\x80,57

&1,1,0\x80,55

&1,1,0\x80,56

Occupancy temperature setpoints &1,1,0\x80,60, 10:35|10:35|10:35| 10:35|10:35|10:35

&1,1,3\x80,16,0:10

&1,1,3\x80,17,0:20

&1,1,3\x80,66 Integral time for VAV

&1,1,3\x80,3,0:3600

&1,1,3\x80,2

damper actuator &1,1,3\x80,3,0:3600

troller, &1,1,3\x80,2 Integral time heating

controller &1,1,3\x80,3,0:3600

actuator &1,1,3\x80,3,0:3600

Schneider Electric Buildings AB, Mar 2010 73 (88) 04-00069-01-en

8 Communication Zone Controller, TAC Xenta 102-ES

Table 8.6: The Controller Object’s Configuration Parameters (nci)

SNVT

Index Variable Hb

50 nciSpaceTempOfst No SNVT_temp_p

51 nciFlowOfstSlave No SNVT_lev_percent

52 nciCO2PerVolt No SNVT_ppm

53 nciSpaceCO2Low No SNVT_ppm

54 nciSpaceCO2High No SNVT_ppm

56 nciSndHrtBt No SNVT_time_sec

57 nciRcvHrtBt No SNVT_time_sec

SCPT/UCPT

UCPT (20)

UCPT (15)

UCPT (9)

UCPT (10)

UCPT (11)

SCPTmaxSend Time (49)

SCPTmaxR cvTime (48)

a. Hb=Heartbeat

Accepted values Default value

-10,0°C to 10,0°C (14 °F to 50 °F)

-1500 to 1500 0 l/s Flow offset for slave

0 to 2500 200 ppm Conv. fact. CO2 / volt

0 to 1000 400 ppm Zone CO2 level for

0 to 1000 1000 ppm Zone CO2 level for

5,0 s to 6553,4 s 0,0 s = disabled

0,0 s to 6553,4 s 0,0 s = disabled

0,0 °C Zone temperature sen-

0,0 s (disabled)

Description (Self doc. string)

sor adjustment &2,15,3\x80,20

-10.0:10.0

&1,1,3\80,15,

-1500:1500

&1,1,3\80,9, 0:2500

closed damper &1,1,3\80,10, 0:1000

open damper &1,1,3\80,11, 0:1000

Send heartbeat &2,1.2.3.4.5.6.7.8.9.

10.14.15.16,0\x8A,49 Receive heartbeat

&2,19.20.22.23.24.27. 28,0\x8A,48

74 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

APPENDIX

A Setpoint Calculation

B Commissioning Protocol

Zone Controller, TAC Xenta 102-ES A Setpoint Calculation

A Setpoint Calculation

Definitions:

Deadband = Neutral zone

Occupied = Comfort mode

Standby = Economy mode

Unoccupied = Off mode

nviSetPoint = Input temperature setpoint (nviSetpoint)

nciSetPoints = Six basic setpoints for temperature (nciSetpoints)

Occupied_cool = Cooling setpoint comfort

Standby_cool = Cooling setpoint economy

Unoccupied_cool = Cooling setpoint off

Occupied_heat = Heating setpoint comfort

Standby_heat = Heating setpoint economy

Unoccupied_heat = Heating setpoint off

Effective = Existing

In nciSetpoints, the cooling and heating setpoints for co mfort and economy mode are set. nviSetpoint allows you to to move all four setpoints with only one value. The mean value of the comfort setpoints in nciSet- points can be seen as the basic setpoint for comfort mode, and the mean value of the economy setpoints can be seen as the basic setpoint for economy mode. The temperature scale for the setpoints must be as follows:

unoccupied_heat < standby_cool <

standby_heat < occupied_heat < occupied_cool <

unoccupied_cool.

There are two methods to calculate the setpoints: Method A and Method B.

Method A

When nviSetpoint receives a valid setpoint, this value becomes the new, common setpoint. The cooling and heating setpoints are recalculated to be at the same distance from the new, basic setpoint as they were from

Schneider Electric Buildings AB, Mar 2010 77 (88) 04-00069-01-en

A Setpoint Calculation Zone Controller, TAC Xenta 102-ES

the previous 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, from nviSetpoint, plus or minus half the neutral zone in the comfort and economy modes. These are calculated from the nciSetpoints. The controller takes the two heating and cooling setpoints in off mode from nciSetpoints.

deadband_occupied = occupied_cool – occupied_heat deadband_standby = standby_cool – standby_heat

effective_occupied_cool = nviSetPoint + 0,5 (deadband_occupied) effective_occupied_heat = nviSetPoint – 0,5 (deadband_occupied) effective_standby_cool = nviSetPoint + 0,5 (deadband_standby) effective_standby_heat = nviSetPoint – 0,5 (deadband_standby)

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 had from the old, basic setpoint in comfort mode. Method B only works when the two setpoints from nciSetpoints do not have the same value, i.e. when the four setpoints are not placed symmetrically around one value. With Method B the asymmetry is kept, as the old comfort setpoint is used (see the example on the next page).

The controller calculates the different setpoints for heating and cooling in comfort and economy modes from nciSetpoints. and the actual absolute setpoint deviation is calculated as the mean value of the occupied_heat setpoint and the occupied_cool setpoint. The controller gets the different heating and cooling setpoints in off mode from nciSet- points.

effect_abs_setpoint_ offset = nviSetpoint – (occupied_cool + occupied_heat) /2

effective_occupied_cool= occupied_cool+ effect_abs_setpoint_offset effective_occupied_heat= occupied_heat+ effect_abs_setpoint_offset effective_standby_cool= standby_cool+ effect_abs_setpoint_offset effective_standby_heat= standby_heat+ effect_abs_setpoint_offset

78 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES A Setpoint Calculation

3635343332313029282726252423222120191817161514

occupied_heat

standby_heat

occupied_cool

standby_cool

nviSetpoint

3635343332313029282726252423222120191817161514

occupied_heat

standby_heat

occupied_cool

standby_cool

1) Assume that you have the following temperatures in

nciSetpoints:

2)The basic setpoint for both comfort and economy modes is 22 °C. By using nviSetpoint this is moved to 23 °C.

3)By using Method A or Method B you will get the following result:

Example 2.

3635343332313029282726252423222120191817161514

occupied_heat

standby_heat

occupied_cool

standby_cool

3635343332313029282726252423222120191817161514

nviSetpoint

3635343332313029282726252423222120191817161514

occupied_heat

standby_heat

occupied_cool

standby_cool

3635343332313029282726252423222120191817161514

occupied_heat

standby_heat

occupied_cool

standby_cool

1) Assume that you have the following temperatures in nciSetpoints:

2)You can allow up to 29 °C before you start cooling in economy mode with nviSetpoint. The basic setpoint for comfort is 22 °C and for economy 24 °C.

3a) Results achieved using Method A:

3b) Results achieved using Method B:

Example 2.

The following two examples show how nviSetpoint works and Method A and Method B.

3635343332313029282726252423222120191817161514

Schneider Electric Buildings AB, Mar 2010 79 (88) 04-00069-01-en

A Setpoint Calculation Zone Controller, TAC Xenta 102-ES

80 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES B Commissioning Protocol

B Commissioning Protocol

This protocol can be used when commissioning the VAV controller TAC Xenta 102-ES. Note that the indices are listed in numerical order, not in the order they are accessed during commissioning. To find information about accepted values,see the tables in chapter 8.

Index Function Variable Default value Set value Note

0 Config. location label nciLocation 0

18 Occupancy scheduler

input

19 Application mode input nviApplicMode 0=Auto

20 Zone temperature input nviSpaceTemp 327,67 °C

21 Temperature setpoint

input

22 Setpoint offset input nviSetpntOffset 0 °C

23 Zone CO

24 Energy hold off input nviEnergyHoldOff 0=Off, 0 %

25 VAV manual override

input

26 Emergency command

input

27 Heating control input for

slave

28 Occupancy sensor

input

29 V6 as free network out-

put

input nviSpaceCO2 65535 ppm

nviManOccCmd OC_NUL

nviSetPoint 327,67 °C

nviManOverride HVO_OFF

nviEmergCmd EMERG_NOR

MAL

nviHeatSlaveR 0

nviOccSensor OC_NUL

nviAuxInput 0

30 Heat contr. input stage

2 for slave

31 Flow control input for

slave

32 Config. application

options

33 Config. minimum flow nciMinFlow 12 l/s

34 Config. maximum flow nciMaxFlow 55 l/s

Schneider Electric Buildings AB, Mar 2010 81 (88) 04-00069-01-en

nviHeatSlaveSec 0

nviBoxFlowSlave 0

nciAppOptions 00000000

B Commissioning Protocol Zone Controller, TAC Xenta 102-ES

Index Function Variable Default value Set value Note

35 Config. air flow scale

nciBoxScale 5

factor VAV

36 Config. air flow offset

nciBoxOffset 0

VAV

37 Config. nominal flow nciNomFlow 75 l/s

38 Config. minimum flow

nciMinFlowHeat 10 l/s

for heat

39 Config. minimum flow

nciMinFlowStandby 5 l/s

standby

40 Config. occup. temp.

setpoints (Cooling setpoint comfort (Cooling setpoint econ-

nciSetpoints occupied_cool standby_cool occupied_heat standby_heat

23 °C) 25 °C) 21 °C)

19 °C) omy (Heating setpoint comfort (Heating setpoint economy

41 Config. max. dev. zone

nciSpaceTempDev 2 °C

temp.

42 Config. min. low limit

nciSpaceTempLow 10 °C

zone temp.

43 Config. gain for VAV nciVAVGain 25

44 Config. integral time for

nciVAVItime 900 s

VAV

45 Config. gain for damper nciGainDamp 1

46 Config. stroke time

nciDampActStTime 165 s

damper

47 Config. gain for heating

nciGainHeat 25

contr.

48 Config. integral time

nciItimeHeat 900 s

heat. contr.

49 Config. stroke time

nciHeatActStTime 165 s

heat. actuator

50 Config. zone temp. sen-

nciSpaceTempOfst 0,0 °C

sor adj.

51 Config. flow offset for

nciFlowOfstSlave 0 l/s

slave

52 Config. conv. factor

53 Config. zone CO

level

nciCO2PerVolt 200 ppm

nciSpaceCO2Low 400 ppm

for closed damper

82 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES B Commissioning Protocol

Index Function Variable Default value Set value Note

54 Config. zone CO2 level

for open damper

55 Config. network conf.

source

56 Config. send heartbeat nciSndHrtBt 0,0 s

57 Config. receive heart-

beat

58 Object request input nviRequest RQ_NUL

60 File request input nviFileReq FR_NUL

nciSpaceCO2High 1000 ppm

nciInstallType 0=LOCAL

nciRcvHrtBt 0,0 s

Schneider Electric Buildings AB, Mar 2010 83 (88) 04-00069-01-en

B Commissioning Protocol Zone Controller, TAC Xenta 102-ES

84 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Zone Controller, TAC Xenta 102-ES Index

LNS

Index

Additional features 55 Air flow balancing Air quality control Alarm

Ambient temperature

Balancing, air flow 30 Basic parameters

Calculation 46 Commissioning protocol Communication Configuration parameters

33, 35, 68, 73

Master/slave Operation 54 Measuring zone temperature

Power consumption 61

Standard 63 Supply voltage

Terminals, connection 26 Terminology

wall module configuration 18

Dimensions 64 Documentation

Electrical installation 24 Enclosure

Fan control 50 Functional description

Heartbeat 66 Heating control

Inputs and Outputs (nvi/nvo’s) 57 Inputs/Outputs (Hardware) Installation Installation, mechanical Installation, network

LED (light emitting diode) 63

Schneider Electric Buildings AB, Mar 2010 85 (88) 04-00069-01-en

Index Zone Controller, TAC Xenta 102-ES

86 (88) Schneider Electric Buildings AB, Mar 2010

04-00069-01-en

Last Manual Page

Schneider Electric TAC Xenta 102-ES Users Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

INTRODUCTION

Zone Controller, TAC Xenta 102-ES 1 Documentation and Terminology

1.1 Documentation

1.2 Terminology

REFERENCE

Zone Controller, TAC Xenta 102-ES 2 Zone Controller TAC Xenta 102-ES

2.1 General

2.2 Wall Modules

2.2.1 STR350/351

2.2.2 STR150

2.2.3 STR100-104

2.2.4 Wall Module Configuration

2.3 Applications

2.3.1 General

2.3.2 The Zone Controller TAC Xenta 102-ES

Zone Controller, TAC Xenta 102-ES 3 Installation

3.1 Mechanical Installation

3.1.1 Fitting

3.2 Electrical Installation

3.2.1 General

3.2.2 Wiring of Xenta 102-ES, Application with Damper Control Only

3.2.3 Wiring of Xenta 102-ES, Application with Damper and Reheat Control

3.2.5 Connecting to STR150

3.2.6 Air Flow Balancing Procedure

3.3 Commissioning

3.3.1 General

3.3.2 Node Status

3.3.3 Configuration Parameters (nci´s)

3.3.4 Network Installation

3.3.5 Network Variable Binding

3.3.6 Function Test

Zone Controller, TAC Xenta 102-ES 4 Configuration Parameters

4.1 Basic Parameters

4.2 Other Configuration Parameters

Zone Controller, TAC Xenta 102-ES 5 Functional Description

5.1 General

5.2 The Controller’s Basic Functions

5.2.1 Operation Modes

5.2.2 Application, Manual and Emergency Modes

5.2.3 Measuring Zone Temperature

5.2.4 Setpoint Calculation

5.2.5 Temperature Control Sequence for TAC Xenta 102-ES

5.3 More About Functions

5.3.1 Cooling Control

5.3.2 Heating Control

5.3.3 Fan Control

5.3.4 Air Quality Control

5.3.5 Window Contact

5.3.6 Occupancy Sensor

5.3.7 Alarm

5.3.8 Master/slave Operation

5.3.9 Additional Features

Zone Controller, TAC Xenta 102-ES 6 Troubleshooting

6.1 General

6.2 Inputs and Outputs (nvi/nvo)

6.3 Troubleshooting Guide

Zone Controller, TAC Xenta 102-ES 7 Technical Data

7.1 Technical Data

7.2 Dimensions

Zone Controller, TAC Xenta 102-ES 8 Communication

8.1 General

8.2 Default Settings and Power On

8.3 Monitoring Network Variables, Heartbeat

8.4 Not Accepted Values

8.5 The Node Object

8.5.1 The Node Object’s Inputs (nvi)

8.5.2 The Node Object’s Outputs (nvo)

8.5.3 The Node Object’s Configuration Parameters (nci)

8.6 The Controller Object

8.6.1 The Controller Objects Inputs (nvi)

8.6.2 The Controller Objects Outputs (nvo)

8.6.3 The Controller Object’s Configuration Parameters (nci)

APPENDIX

Zone Controller, TAC Xenta 102-ES A Setpoint Calculation

Zone Controller, TAC Xenta 102-ES B Commissioning Protocol