Ezfc 424 R 424

eZFC-424R4-24
Application Guide
Edition 2.6
Table of Contents
Copyright 7
About the eZFC-424R4-24 8
About This Guide 8
Upgrading Firmware 8
Upgrading From 1.x to 2.2 8
Upgrading From 2.x to 2.2 9
Object Restriction Settings (ORS) 9
ORS Troubleshooting 9
Connecting to the Controller 9
Setting the MS/TP Address 9
BACnet Device Addressing 10
About the enteliZONE ORCAview Configuration Graphic 11
Downloading the ORCAview Configuration Graphic 11
Installing the ORCAview Configuration Graphic 11
Opening the ORCAview Configuration Graphic 11
Method 1 (Recommended) 12
Method 2 12
Working with the ORCAview Configuration Graphic 12
Selecting Between Multiple Controllers 12
Save to Flash, Save to PC and Load from PC 13
Shortcuts 13
Configurable and Programmable enteliZONE Controllers 14
Differences Between Configurable and Programmable enteliZONE Controllers 14
eZFC-424R4-24 Application Guide Page 1 of 84

Edition 2.6
LINKnet Devices 14
Data Exchange 15
Alarming 15
Trend Logs 16
Programming 17
enOcean Integration (firmware 2.2 and higher) 18
Upgrade to Fully Programmable Using Flash Loader (firmware 2.2 and higher) 18
Fan Coil Programmable Objects 19
Fan Coil and Heat Pump Programmable Objects 19
Relationship Between Algorithm Unit Modules 20
General Tab 22
What is the General Tab? 22
Device Information 22
Network Settings 23
Global Settings 24
Local Inputs Tab 26
Setting Up a Hardwired Temperature Sensor 26
Set Up a Hardwired Temperature Sensor 26
Setting Up a Hardwired Occupancy Input 27
Set Up a Hardwired Occupancy Input 27
Setting Up a Hardwired CO2 Sensor 29
Setting Up a Fan Speed Switch 30
Setting Up a Fan Coil 2-Pipe Changeover Sensor 30
Setting Up a Condensate Level Switch 31
Setting Up Other Supporting Inputs 31
Page 2 of 84 eZFC-424R4-24 Application Guide

Edition 2.6
Set Up an Input 31
Setting Up Damper Feedback 32
Local Outputs Tab 33
Setting Up a Fan Coil or Heat Pump Output 33
Set up a Fan Coil Output 33
Setting Up a Fan Output 35
Set Up a Fan Output 35
Setting Up Other Outputs 37
Set Up an Output 37
Setting Up a Damper Output 38
Set Up a Damper Output 38
LINKnet I/O Tab 39
Configuring an eZNS-T100 Network Sensor 39
Set Up the Temperature Sensor 39
Set Up the Humidity Sensor 40
Set Up the CO2 Sensor 40
Set Up the Occupancy Sensor 40
Assign Functions to the Buttons and Slider 41
Set Up the LCD Display 41
Assigning Buttons and Slider Elements on eZNS-T100 Network Sensor 42
Introduction 42
Set Up the Buttons and Slider Elements 44
Configuring DNS-24L Network Sensor 47
Introduction 47
Set Up the Temperature Sensor 47

Edition 2.6
Set Up the Humidity Sensor 47
Set Up the CO2 Sensor 48
Set Up the Occupancy Sensor 48
Assign Functions to the Buttons 48
Set Up the LCD Display 48
Assigning Buttons on DNS-24L Network Sensor 48
Introduction 48
Set Up the Button Elements 49
Setpoints Tab 51
What is the Setpoints Tab? 51
Space Temperature Setpoints 51
Occupied Heating Setpoint (OccHeatingSetpoint) 51
Unoccupied Heating Setpoint (UnOccHeatingSetpoint) 51
Occupied Cooling Setpoint (OccCoolingSetpoint) 51
Unoccupied Cooling Setpoint (UnOccCoolingSetpoint) 51
Occupied Setpoint Offset Range (OccSetpointOffsetRange) 51
Eco Mode Setback (EcoModeSetBack) 52
Standby Setback (StandbySetback) 52
Discharge Air Temperature Limiting Setpoint Differentials 52
Discharge Air Temperature High Limit Setpoint Differential (DATHiLimitSetpointDiff) 52
Discharge Air Temperature Low Limit Setpoint Differential (DATLowLimitSetpointDiff) 52
Controllers Tab 53
What is the Controllers Tab? 53
Controller Type 53
Proportional Band 53

Edition 2.6
Deadband 53
Integral Rate 53
Reset Band 53
Outdoor Air Temperature Heating Lockout Setpoint (OAT Htg Lockout) 54
Heating Demand Limit (Htg Demand Limit) 54
Outdoor Air Temperature Cooling Lockout Setpoint (OAT Clg Lockout) 54
Cooling Demand Limit (Clg Demand Limit) 54
enteliZONE Sequence of Operations 55
Introduction 55
Setpoint Control 55
Setpoint Range Limits 55
Occupancy Modes 56
Switching Between Occupancy Modes 57
Setpoints and Occupancy Modes 59
Heating (Fancoil) 60
Cooling (Fancoil) 60
Time-Proportional Heating and Cooling 60
Auto Changeover 61
Discharge Air Temperature 61
Fan (Fancoil) 62
Manual Fan Speed Control 62
Automatic Fan Speed Control 62
Fan Stages 63
Demand Control Ventilation 71
Open Window Detection 72

Edition 2.6
Heat Pump 72
enteliZONE Database Configuration Objects 73
Introduction 73
Input Configuration Objects 73
Occupancy Configuration Objects 75
Output Configuration Objects 76
Setpoint Configuration Objects 77
Device Instance/ BACnet Address Object 79
Control Types 80
What are Control Types? 80
Open Source Licensing 82
lwIP 82
ST Microelectronics 83
Document Revision History 84

Edition 2.6
Copyright
Copyright © Delta Controls Inc. All rights reserved.
No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language (natural or computer), in any form or by any means, without the
prior written permission of Delta Controls Inc.
Limited permission is granted to reproduce documents released in Adobe® Portable Document
Format (PDF) electronic format in paper format. Documents released in PDF electronic format
may be printed by end-users for their own use using a printer such as an inkjet or laser device.
Authorized distributors of Delta Controls Inc. products (Delta Partners) may print PDF documents
for their own internal use or for use by their customers. Authorized Delta Partners may engage a
printing or copying company to produce copies of released PDF documents with the prior written
permission of Delta Controls Inc.
Information in this document is subject to change without notice and does not represent a
commitment to past versions of this document on the part of Delta Controls Inc. Delta Controls Inc.
may make improvements and/or changes to this document /the associated software/or associated
hardware at any time.
BACspec, BACstat, the Delta logo, ORCAview, ORCAweb, Earthright, enteliWEB, enteliBUS,
enteliMESH, enteliTOUCH, enteliZONE, enteliSTAT, and Virtual Stat are registered trademarks
of Delta Controls Inc.
All other trademarks are the property of their respective owners.
Document edition: 2.6
Published on Wednesday, August 23, 2017

Edition 2.6
About the eZFC-424R4-24

The eZFC-424R4-24 and eZFCP-424R4-24 controllers are native BACnet controllers optimized
for fan coil applications. It has multiple input and output configuration options covering a wide range
of fan coil configurations including single or multi-speed fans, 2-pipe or 4-pipe systems, with or
without change-over. The controller is also designed to be compatible with Delta Controls’ eZNS
and DNS-24L network sensors.
The eZFC-424R4-24 comes preloaded with algorithms which you configure using a configuration
graphic to match your site’s needs. There are 2 types of eZFC-424R4-24 controllers: both the
configurable (eZFC) and programmable (eZFCP) models use the configuration graphic for setup
but only the programmable controller allows you to overwrite the default sequences with General
Control Language (GCL) programming.
You can use ORCAview 3.40R3 and higher or enteliWEB 4.1 and higher to access the
configuration graphic.
About This Guide

This application guide introduces the controller and describes the differences between the
configurable and programmable models. The guide also shows you how to use the configuration
graphic in ORCAview 3.40 R3 and higher to set up your eZFC-424R4-24 controller. The product
name eZFC-424R4-24 in this guide refers to both the configurable and programmable models
unless stated otherwise.
The ORCAview configuration graphic version referenced in this guide is B-169041.1.
For help with the eZFC-424R4-24 configuration page in enteliWEB 4.3 and higher, go to the online
help in enteliWEB. enteliWEB users require the applicable object permissions to change the
settings on the configuration page.
The installation guide for the eZFC-424R4-24 can be found on the eZFC-424R4-24
product web page on the Delta Controls Support web site.
Upgrading Firmware
Upgrading From 1.x to 2.2
The configurable algorithm database on firmware version 1.01 is not compatible with the
configurable algorithm database on firmware 2.2. See the release notes of the firmware version
you are upgrading to for more information.

Edition 2.6
Upgrading From 2.x to 2.2
See the release notes of the firmware version you are upgrading to for more information.
Release notes are available on the Delta Controls Support web site
Object Restriction Settings (ORS)

The Object Restriction Settings (ORS) object allows the user to limit which database objects can be
viewed and edited. This is useful for hiding configuration settings which are not used in day-to-day
operation, to ensure a user cannot inadvertently change the configuration after initial system
commissioning. enteliZONE controllers support permission options of visible, read and write.
However, enteliZONE controllers do not support create or delete permissions as enteliZONE has a
fixed database structure where objects are editable but cannot be created or deleted. enteliZONE
controllers also do not support multiple ORS objects with temporary unlock permissions.
ORS security is turned on and off by locking and unlocking the controller. The ORS is unlocked in
the default database configuration. It must be unlocked in order to configure the controller. If the
controller is in a locked state, a message is displayed asking the user to unlock the controller.
To unlock the controller in ORCAview:
1. In the Navigator tree, right-click on the enteliZONE controller and point to Object Security
and then click Unlock.
2. Enter the unlock username and password. The default username is DELTA and the
password is login.
ORS Troubleshooting
If the controller time does not match the OWS time, the controller cannot be unlocked. To update
the controller time in ORCAview, on the Tools Menu, click Set Controller Time.
Without the correct username and password there is no way to unlock the controller. If the correct
username and password is unavailable, reload a copy of the default database into the controller,
this restores access to the controller, using the default username and password, however any
previous configuration changes will be lost.
Connecting to the Controller
Setting the MS/TP Address
The enteliZONE controller communicates using BACnet MS/TP. Before connecting to the
controller its MS/TP MAC address should be set using its DIP switches. Each controller on the
same MS/TP segment must have a unique MAC address. The enteliZONE controllers ship with a
default MS/TP MAC address of 1.

Edition 2.6
The DIP Switch is a binary switch. Each individual DIP switch represents a unique value, which
forms the controllers MS/TP MAC address when added together. To set the address, simply move
the switches that add up to the controllers desired address to the ON position. The picture below
shows the DIP switches with positions 1 and 4 on giving a MS/TP MAC address of 5.
BACnet Device Addressing
The enteliZONE controller supports both Derived Network Addressing (DNA) and software
addressing.
DNA
DNA speeds up network commissioning by automatically configuring the controllers’ BACnet

address based on its parent controller address and MS/TP address. DNA is a Delta Controls
proprietary function that can only be used when the parent controller is a Delta Controls device.
When DNA is enabled (by default), the first part of the BACnet address is inherited from the parent
controller. The last 2 digits of the BACnet address is equal to the MS/TP MAC address.
For example, a controller with a MS/TP MAC address of 1 and whose parent controller has a
BACnet address of 40100 would have a BACnet address (using DNA) of 40101.
If there is no parent controller when the enteliZONE controller powers up, the enteliZONE
controller’s BACnet address will be equal to its MS/TP MAC address.
For more information about addressing BACnet devices, see KbA 1802: Comprehensive
Guide to BACnet networking on the Delta Controls Support web site.
Software Addressing
To switch to software addressing, you must first turn off DNA on the controller. In ORCAview, open
the controller’s DEV object dialog and clear the DNA check box. Once this box is cleared, enter the
software address in the Software Address field. You can also turn off DNA and enter a software
address on the General tab of the enteliZONE configuration graphic.

Edition 2.6
About the enteliZONE ORCAview Configuration Graphic
The enteliZONE controller configuration graphic in ORCAview provides a user-friendly interface to
configure the controller’s algorithm and its corresponding objects and IO points. Each time a
change is made to a field or option,ORCAview updates the corresponding object references. The
topic enteliZONE Database Configuration Objects lists the fields and options, and their object
references.
In enteliWEB, the configuration page is available as a tab on the Object List page.
Downloading the ORCAview Configuration Graphic

You can download the configuration graphic from the enteliZONE controller product web page on
the Delta Controls Support web site and install it on your operator workstation.
Installing the ORCAview Configuration Graphic

To install the configuration graphic in ORCAview:
1. On your operator workstation, go to the graphic folder C:\Users\Public\Delta

Controls\3.40\Sites\<site name>\Graphics. The site name refers to the site where the
enteliZONE controller you are configuring resides.
2. Copy and paste the configuration graphic zip file into the Graphics folder.
3. Unzip the file.
There are 7 configuration (.gpc) files associated with the enteliZONE controller. Each file
corresponds to a tab on the configuration graphic. The balancing file is not enabled on the eZFC-
424R4-24 or eZ-440R4-230 controller.
Opening the ORCAview Configuration Graphic

There are 2 ways to open the configuration graphic in ORCAview. Make sure the configuration
graphic is installed on your operator workstation before attempting any of these steps.

Edition 2.6
About the enteliZONE ORCAview Configuration Graphic
Method 1 (Recommended)
1. In the left window of the ORCAview navigator, right-click on the enteliZONE controller you
want to configure and click Open.
If this is your first time using the configuration graphic, the DEV object dialog opens.
2. On the Configuration tab, click and browse to the graphics folder and select the Main.gpc file
for the enteliZONE controller. Click OK.
3. In the left window of the ORCAview navigator, right-click on the enteliZONE controller again.
Click Open. Because you have set it up in step 2, the configuration graphic window should
open and will open this way each time you select Open from the right-click menu.
Right-clicking does not work if you have changed the name of the configuration
graphic file or if the Controller Graphic field in the Device object (in the controller
database) has been edited.
Method 2
1. In the left window of the ORCAview navigator, open the Graphics folder and double-click on
one of the configuration files. A new graphic window opens. You can access all the
configuration files from this window.
2. In the numerical field at the top of the window, enter the BACnet address of the enteliZONE
controller you want to configure and click Connect.
Working with the ORCAview Configuration Graphic

This graphic is interactive and dynamic in real-time. When you select an option in a field, other fields
and options are displayed in response to the initial option selected. What this also means is that any
changes made to the fields are saved and applied instantly.
Selecting Between Multiple Controllers
If you have multiple enteliZONE controllers of the same kind on the same network, instead of
opening the configuration graphic individually for each controller in the ORCAview navigator, you
can switch between controllers within the configuration graphic.
When you switch between controllers, any changes made in a previous session will be
saved automatically before you switch to the next controller.

Edition 2.6
To select between multiple controllers:
In the numerical field at the top of the window, enter the BACnet address of the enteliZONE
controller you want to configure and click Connect.
Save to Flash, Save to PC and Load from PC
These buttons are displayed at the top of the configuration graphic dialog. They minimize the need
to switch between the configuration graphic and the ORCAview Navigator when you are working
with multiple controllers.
The Save to Flash button is used to save the controller database to the controller’s flash memory.
The Save to PC button is used to save the controller database .pdb file to your computer.
The Load from PC button is used to load a controller database .pdb file from your computer onto
the enteliZONE controller.
Both Save to PC and Load from PC allow you to save your configuration graphic settings and copy
them onto multiple enteliZONE controllers using ORCAview.
Shortcuts
There is a quick way to open the ORCAview object dialogs by right-clicking on the configured input
and output numbers in the configuration graphic.
In the example below, when you right-click on the number 1 and select Open SpaceTemp_AI1,
the AI1 object dialog opens onscreen.

Edition 2.6
Configurable and Programmable enteliZONE Controllers
Differences Between Configurable and Programmable enteliZONE Controllers

This topic describes the main differences between these 2 types of controllers.
Using the ORCAview or enteliWEB configuration page, variables and setpoints are entered into
the algorithm and written to the appropriate preset objects (100 to 199 range, 1000+ range for
LINKnet device configuration) in the factory controller database.
In the configurable type of controllers, there are no program (PG) objects.
In the programmable controllers, even though it is recommended that you use the configuration
page to set up your programmable controller, local programming can be used to overwrite the
algorithm by writing to the objects in the 800 to 899 range.
There is a limit to the number of specific object types in these controllers. The number limits are
summarized in the table below. You cannot exceed this number by creating any new objects.
Object Type Configurable Programmable

LINKnet objects (LNK) 1 4
Event objects (EV) 0 5
Trend Logs (TL) 4 8

Programs (PG) 0 3
Gateway Translation objects (GWT) 0 4
(firmware 2.2 and higher)
For a complete list of enteliZONE supported object types and the number of instances allowed for
each object, go to the enteliZONE overview page on the Delta Controls Support web site.
LINKnet Devices
Configurable controllers can only connect to 1 LINKnet device at a time. This LINKnet device has to
have a device address of "1" in order for it to work with the controller algorithm. Multiple LINKnet
devices (up to 4) are only supported by the programmable controllers.
LCD and LINKnet objects are located on the enteliZONE controller and are numbered LCDx001
and LNKx001 respectively where x is the network sensor’s device address.
enteliZONE controllers only support eZNS and BACstat LINKnet network sensors. Other LINKnet
devices like Delta Field Modules (DFM) are not supported.

Edition 2.6
Data Exchange
This section describes how the enteliZONE controllers accept and initiate data exchanges in the
network.
The enteliZONE controller accepts these data exchange requests:
l Poll. The default data exchange type set up in the Data Exchange Settings object (DES) is
Poll. The poll interval can be adjusted in the DES object, at a recommended minimum of 1
second per MS/TP device on a segment.
l Change of Value (Confirmed and Unconfirmed). The enteliZONE controller is limited to
a maximum of 12 subscriptions (Delta Exchange Local or DEL objects).
The controller does not support the Optimized Broadcast and Broadcast Data Exchange request
types. If a controller attempts to subscribe using any of these exchange types, the exchange types
will fail and revert to polling.
The programmable controllers can initiate up to 12 data exchange polling requests (Delta
Exchange Remote or DER objects). Other types of Data Exchange initiating request types are not
supported.
The DES object for the controller lists the number of DER and DEL requests that are in use.
The controller supports Bulk Data Exchange (BDE) but is limited to 2 BDE objects. Each BDE
object can hold up to 12 tag and object entries on the object’s Transmit Entries tab.
For more information about Data Exchange types, go to the George Support knowledge base
article KBA 1813.
Alarming
The programmable controller supports up to 5 EV objects as well as intrinsic alarming on up to 5

input and output points (see below for more information about intrinsic alarming). These EV objects
support these alarm types:
Alarm
Description
Type
Change of Used to monitor and alarm a binary value.
State
Command Used when you have a binary value with feedback. An alarm is generated if
monitored values do not match the feedback value.
Failure
Floating Used to alarm when an analog value varies more than a set limit from a variable
setpoint value.
Limit

Edition 2.6
Alarm
Description
Type
Out of Used to alarm when an analog value varies outside of a set of fixed limits.
Range
The enteliZONE family of controllers does not support Change of Value or Change of Bitstring
alarm types.
Even though the configurable controller versions do not have EV objects, intrinsic alarming can be
enabled on input and output points, specifically analog input (AI), binary input (BI), analog output
(AO) and binary output (BO).
EV objects will send out auto generated messages to notify users about alarms. enteliZONE
controllers do not support alarm acknowledgments.
Custom alarm messages are supported by the following firmware versions:
l eZV-440 controller firmware version 2.1 and higher for EV objects only.
l eZFC-424R4-24 controller firmware version 2.2 and higher for EV objects only.
l eZ-440R4-230 controller firmware version 2.1 and higher for EV objects only.
For more information about how to set up an intrinsic alarm, see the webinar Intrinsic
Alarms in ORCA 3.40 on the Delta Controls support web site.
Trend Logs
A programmable enteliZONE controller supports up to 8 trend logs, 4 of which are user-defined.

The configurable controller version supports 4 trend log objects (TL1 to 4) which are pre configured
in the default database to monitor specific heating and cooling objects. However, all TLs can be
modified to monitor objects other than the default set object. You can also change the method of
data collection (Change of Value or polling) as well as the polling interval. However, fields that
display the maximum and total sample size are read-only.
It is not recommended to use Change of Value for objects that are expected to change at a rate
faster than every 5 seconds. TL objects have a 5-second record limit. Events that occur faster than
this record limit will result in “Log Enabled” or “Log Interrupted” entries that can be hard to interpret.
The default database TL objects are listed in the following table.
Trend Log Monitored Object

1 SpaceTemp (AV1)
2 CurrentHeatSetpoint (AV800)

Edition 2.6
Trend Log Monitored Object
3 CurrentCoolSetpoint (AV801)
4 HeatCoolLoad (AV802)
5 User-defined
6 User-defined
7 User-defined
8 User-defined
The enteliZONE trend logs also support Historian archiving. The enteliZONE controllers don’t
support buffer full notification events so make sure the Historian update interval is frequent enough
to avoid missing samples.
Programming
In the programmable controller, the 3 programs that exist alongside the configurable algorithm
allow you to either create your own custom algorithm or override portions of the configurable
algorithm to suit your needs. The maximum size of each program is 5 KB.
The programmable controller also allows you to create new I/O, AV, BV and MV objects in the 900-
999 range for use in your custom program.
Supported GCL+ Programming Functions, Statements and Operators
The Call Statement is not used in the programmable enteliZONE controllers. Unlike other
programmable Delta Controls controllers, the 3 programs in the programmable enteliZONE
controllers are automatically scanned. The scan rate is also designed to be a constant 10
scans/second.
A list of supported and unsupported GCL+ functions and statements for the enteliZONE
programmable controllers is recorded in KBA 2137 on the George Support web site. The
ORCAview and enteliWEB GCL editors are not aware of these limitations, so using an
unsupported function in an enteliZONE programmable controller will not register a syntax error in
these GCL editors.
Overwriting the Algorithm
You can overwrite the algorithm by programming specific objects numbered in the 800 range. For
example, if you want to change how the algorithm determines the occupancy state, you could write
your own GCL+ program to set the occupancy MV800 state.
Your program must write more frequently than every 5 seconds else the factory algorithm will
recapture control.

Edition 2.6
Click on a link below to find out more information about these programmable objects.
l Fan Coil/ Heat Pump algorithm programmable objects
enOcean Integration (firmware 2.2 and higher)
Gateway Translation (GWT) and Gateway (GW) objects are available on the programmable
enteliZONE controllers so that you can integrate an enteliZONE programmable controller into an
enOcean wireless system using a CON-ENOC enOcean Gateway device.
For more information about how to configure the GWT objects, see the CON-ENOC Application
Guide on the CON-ENOC George Support product page.
Upgrade to Fully Programmable Using Flash Loader (firmware 2.2 and higher)
Delta Controls Flash Loader (Version 3.40 R4) can be used to upgrade controllers from
configurable to fully programmable versions. Flash Loader is part of the ORCAview suite of
software.
Flash Loader connects to and upgrades 1 controller at a time over the BACnet Ethernet network.
This upgrade requires 3 Flash credits on a Flash Loader key. Go to the Flash Loader page
on the George Support web site for more information.
1. Insert a Flash Loader key with sufficient credits into a USB port on your workstation.
2. Download the .FLS upgrade file from the George Support web site onto your workstation.
Save the file in the Flash Loader folder that was created when you installed Flash Loader,
like C:\Program Files(x86)\ Delta Controls\3.40\Flash Loader.
3. Back up the controller database by saving it. Flash Loader does not save the database
before the upgrade.
4. Open Flash Loader version 3.40 R4 on your workstation.
5. In the Filename dropdown list, select the upgrade file on your workstation.
For example, for firmware 2.1, the file name will be eZONE R2.1 B-xxxxxx.fls, where xxxxxx
is the build number.
6. Click the Enables Features box to check it. The eZONE section is displayed.
7. Click the Settings button.
1. In the Protocol dropdown list, select BACnet Network.
2. In the Adapter dropdown list, select the Ethernet adapter that connects the
workstation to the controller network.

Edition 2.6
3. Leave the Password field blank unless a password is defined in the Flash Loader
Password field on the Configuration tab of the controller’s DEV object.
4. Click OK to save changes made in the Settings window.
8. In the device Address field, enter the BACnet device address of the controller you want to
flash. This is the address displayed next to the controller in ORCAview Navigator.
9. In the eZONE section, click the Upgrade to Programmable box to check it.
10. Click Add Features.
Flash Loader transmits the new firmware to the controller. The Status and Progress fields in
the Flash Loader window display the status of the transmission.
11. When the upgrade is complete, the Status field displays an Update Complete message.
12. Close the Flash Loader program.
Fan Coil Programmable Objects
Fan Coil and Heat Pump Programmable Objects
The following table displays all the programmable objects in the fan coil and heat pump enteliZONE
algorithm.
For more information about programmable objects, go to the help topic about programmable
controllers.
Algorithm Unit
Unit Module's Function Programmable Object
Module
Fan Manager Controls the fan sequence. AV810 Fan1
AV811 Fan2
AV812 Fan3
Controller Manager Determines the heating and cooling load AV802 HeatCoolLoad
on the system.
Cooling Stage Controls the cooling sequence. AV806 Cool1
Manager AV807 Cool2
AV810 Fan1
AV811 Fan2
AV812 Fan3

Edition 2.6
Algorithm Unit
Unit Module's Function Programmable Object
Module
Heat Stage Manager Controls heating sequence of operations. AV803 Heat1
AV804 Heat2
AV805 Heat3
AV810 Fan1
AV811 Fan2
AV812 Fan3
Occupancy Manager Determines the occupancy mode in the MV800 Occu-
space at any time.
pancyMode
Temperature Controls the active heating and cooling AV800
Setpoint Manager setpoints in the space. CurrentHeatingSetpoint
AV801
CurrentCoolingSetpoint
Heat Cool Manager Determines whether the space requires AV802 HeatCoolLoad
heating or cooling.
Relationship Between Algorithm Unit Modules
The PDF displays the relationships between unit modules.

Edition 2.6
enteliZONE FCU Algorithm Flowchart
Occupancy
Manager
MV800 Occupancy
Mode
Temp Setpoint
Manager
AV800 CurrentHeating AV801 CurrentCooling

Setpoint Setpoint
Heat Cool
Manager
AV802 HeatCool Load

Manager
AV810 Fan1
Fan
AV811 Fan2
AV812 Fan3
Cooling Stage
Manager
AV806 Cool1
AV807 Cool2
Heating Stage
Manager
AV803 Heat1
AV804 Heat2
AV805 Heat3
Point(s) in each algorithm manager box can be used to override the

algorithm manager
Relationship between points

Edition 2.6
General Tab
General Tab
What is the General Tab?

The General tab on the enteliZONE controller configuration page is divided into 3 main sections.
The Device Information section contains basic controller information such as model number and
firmware version, and a device description field.
The Network Settings section contains the controller BACnet address, the network number as well
as the network speeds (baud rates).
In the Global Settings section, the options set here are applied to all tabs on the configuration page.
Device Information
The following fields are found in the Device Information section.
Field
Description
Name
Name Displays the name of the controller as it appears in the Device Object.
Model Displays the controller's Delta Controls model number.
Name
Application Displays the controller's algorithm version.
Version In the ORCAview configuration graphic, this field is called the Firmware
Version.
Firmware Displays the controller's firmware build number.
Version In the ORCAview configuration graphic, this field is called the Firmware Build.
Controller Displays the configuration graphic file that opens every time you right-click on
Graphic the controller in the ORCAview navigator. You can also enter the name of a
(ORCAview dashboard graphic file and set it as the default graphic.
only) If you leave this field blank, the Device Object dialog opens instead.
Device You can enter and modify the controller's text description, up to 64 characters.
Description

Edition 2.6
Network Settings
The following fields are found in the Network Settings section.
Field
Description
Name
BACnet Displays the controller's BACnet address. This field is read-only when the DNA
box is checked. If you want to enter a new address, clear the DNA box.
Address
Click here for more information about the BACnet address object.
NFC Displays the password that secures access to the controller’s NFC chip. The
value range is 0 to 65535. The password is stored on the AV96 object.
Password
The Device Password field on the Delta Controls mobile applications must match
the NFC password before any data can be written to the NFC chip.
DNA Turns on or off Derived Network Addressing (DNA) automatic addressing. DNA
is turned on when the box is checked; the BACnet address also becomes read-
only. To manually enter a new address, clear the DNA box.
Delta Controls products have the option to use DNA or Derived Network
Addressing, a system of organizing and configuring controllers in a network.
When DNA is enabled, addresses are automatically assigned to a device based
on the BACnet network type and the Delta Controls product type, so that a
device can work out-of-the-box without much set up.
NET1 Displays the network protocol currently enabled for the NET1 port. This is a read-
Protocol only field.
NET1 Displays the baud rate for the NET1 port. Any changes to the baud rate will be
Speed applied immediately to all Delta Controls controllers in the network.
NET1 Displays the controller's BACnet network number.
Number
NET1 Displays the controller’s network address typically set up by the controller’s DIP
MAC switches.
Address
NET2 Displays the network protocol currently enabled for the NET2 port. This is a read-
Protocol only field.
NET2 Displays the baud rate for the NET2 port. Any changes to the baud rate will be
Speed applied immediately to all Delta Controls controllers in the network.

Edition 2.6
General Tab
Global Settings
The following fields are found in the Global Settings section.
Field Name Description

Application Select the main HVAC system application for this controller. This determines
the algorithm that will be used for the controller.
Type
The options for the eZFC-424R4-24 and eZ-440R4-230 controllers are
FanCoil_ (Fan Coil Unit), HeatPump_ (Heat Pump), RadiantHeat_ (Radiant
Heat) and None.
The configurable controller has no functional state until you select an
algorithm.
In a fully programmable controller, when you select an algorithm, you can
override portions of the internal algorithm to suit your needs. See the section
in this guide about overwriting the algorithm. Select None if you want to
program a fully custom sequence of operations. When you select None, the
internal algorithms are disabled and all preconfigured algorithm I/O points and
variables are removed from the default database. Other object types, like AIC,
that were part of the algorithm can be used as is or reconfigured.
If you change an application type for another, the settings of the
previous application type will be deleted. You can save your
controller database before switching application types.
Temperature Displays the temperature units used by the controller.

Units
Child If this controller reports to a parent controller, select this box. The child
Controller controller polls these variables from its parent controller:
(enteliWEB l HeatCoolLoad (AV802)
only)
l OccupancyMode (MV800)
l DemandCtrlVent (AV813)
l ManualFanSpeedCmd (AV17)
l FanMode (BV1)
When FanMode is set to Automatic in the parent controller, the child

controller’s fan speed is controlled automatically based on demand. When
FanMode is set to Manual, the child controller’s fan speed follows the
ManualFanSpeedCmd value polled from the parent. In this mode, local fan
speed switch or stat fan control button will be suppressed.

Edition 2.6
Field Name Description
Parent This field is enabled when the Child Controller box is checked. Enter the
Address parent's BACnet address in this field. If you are setting up a parent controller,
(enteliWEB leave this field at its default zero value.
only) If the parent’s BACnet address changes in the future, you must manually
update this value to match the new address.
Parent Child If this controller reports to a parent controller, enter the parent’s BACnet
Address address in this field. In all other cases, including setting up a parent controller,
(ORCAview leave this field at its default zero value.
only) If the parent’s BACnet address changes in the future, you must manually
update this value to match the new address.
The child controller polls these variables from its parent controller:
l HeatCoolLoad (AV802)
l OccupancyMode (MV800)
l DemandCtrlVent (AV813)
l ManualFanSpeedCmd (AV17)
l FanMode (BV1)
When FanMode is set to Automatic in the parent controller, the child

controller’s fan speed is controlled automatically based on demand. When
FanMode is set to Manual, the child controller’s fan speed follows the
ManualFanSpeedCmd value polled from the parent. In this mode, local fan
speed switch or stat fan control button will be suppressed.

Edition 2.6
Local Inputs Tab
Local Inputs Tab
Setting Up a Hardwired Temperature Sensor

This topic describes how to set up a temperature sensor using the Local Inputs tab on the
configuration page.
Occupancy overrides can share the same input as the temperature sensor.
If you are setting up a LINKnet DNS-24L or eZNS network sensor to provide occupancy
input, use the LINKnet I/O tab on the configuration page.
Set Up a Hardwired Temperature Sensor
1. Wire your sensor to the controller's physical input.

2. Next to the input number that you've assigned to the sensor, in the Function field, select one
of the following options:
Function Select this option if you are using a:

DischargeAirTemp_ Duct temperature sensor that is located downstream from any
local heating or cooling stages that supply the air to that space.
SpaceTemp_ Space temperature sensor, or a network value from a DNS or
eZNS network sensor on LINKnet.
You can set up multiple SpaceTemp inputs and by default the
algorithm will calculate the average of all inputs and assign that
value to the AV1 object.
SpcTemp+ Space temperature sensor and the occupancy override push
OccOvrdButton_ button are wired into the same input.
This can be a normally open contact wired in parallel or a
normally closed contact wired in series with the temperature
sensor.
SpcTemp+ Space temperature sensor and the occupancy toggle push
OccToggleButton_ button are wired into the same input.
sensor.

Edition 2.6
When setting up a temperature sensor, majority of the cases would require you to select
Temp_10K3DegC or Temp_10K3DegF as an option under Action/Scale, depending on
the temperature units set up on the General tab.
3. If you had selected the DischargeAirTemp_ option, in the additional settings, in the
DATHiLimitSetpointDiff and DATLowLimitSetpointDiff fields, enter the discharge air
temperature high limit and low limit setpoints differentials respectively.
4. (enteliWEB only) The Input Name field displays the object's name. You can change this
name by clearing the field and entering a new name.
Multiple Space Temperature Inputs

You can set up multiple SpaceTemp inputs and by default the algorithm will calculate the
average of all inputs and assign that value to the AV1 object.
Setting Up a Hardwired Occupancy Input

This topic describes how to set up an occupancy input using the Local Inputs tab on the
configuration page.
Occupancy inputs can either be maintained-contact or momentary contact types. Occupancy
overrides can share the same input as the temperature sensor.
See the sequence of operations topic to learn more about occupancy modes in the algorithm.
Set Up a Hardwired Occupancy Input
1. Next to the input number that you've assigned to the input, in the Function field, select one or
more of the following options:

OccMotion_ Hardwired latching, momentary contact sensor type, or a
network sensor with an integrated motion sensor and want
to enable it for occupancy control.
OccMaintainedContact_ Any maintained contact device like a hotel keycard holder,
manual switch or mechanical time clock input.

Edition 2.6
Local Inputs Tab

OccOvrdButton_ Network sensor button as an occupancy override button.
When pushed during unoccupied mode it starts an
occupancy override timer. When an override has been
activated, pushing the button will extend the override time by
resetting the timer back to its max value.
During scheduled occupancy periods, you cannot switch
occupied to standby mode using the button. However if
occupancy is in standby mode, pressing the button will
switch the room back to occupied mode until the next
occupancy event change.
OccToggleButton_ Network sensor button to toggle between standby and
occupied modes during scheduled occupancy periods.
When pushed during unoccupied mode it starts an
occupancy override timer. When an override has been
activated, pushing the button again will cancel the override
and reset the override timer back to zero.
SpcTemp+ Space temperature sensor and the occupancy override
OccOvrdButton_ push button are wired into the same input.
sensor.
SpcTemp+ Space temperature sensor and the occupancy toggle push
OccToggleButton_ button are wired into the same input.
sensor.
In most cases Direct (contact closed = occupied) is the default action.

2. If you had selected the OccMotion_ option, in the additional settings, in the MotionOvrdTime
field, enter how long the occupancy override should last. This setting allows the use of
momentary contact style occupancy signals.
If you are using maintained-contact occupancy devices, enter zero in this field. In this case,
occupancy state is only based on contact position.
3. If you had selected any occupancy button options, in the additional settings, in the
PushButtonOvrdTime field, enter how long the button override should last.

Edition 2.6
With the OccToggleButton option, With the OccToggleButton option, it is recommended

to display the occupancy status on your network sensor. The occupancy status allows the
user to determine if a button press will start an override or cancel an active override.
Multiple Temp+Occ Inputs
You can set up multiple SpcTemp+OccOvrdButton and SpcTemp+OccToggleButton inputs

and by default the algorithm will calculate the average of all these temperature inputs. With multiple
occupancy inputs, the value will reflect the last value written.
Setting Up a Hardwired CO2 Sensor

This topic describes how to set up a carbon dioxide sensor using the Local Inputs tab on the
configuration page.
Set Up a Hardwired CO2 Sensor
1. Wire your sensor to the controller's physical input.

2. Next to the input number that you've assigned to the input, in the Function field, select
SpaceCO2_. The default option in the Action/Scale column is CO2 0-2000ppm.
3. If you are using demand controlled ventilation with the CO2 sensors, in the additional
settings,
l In the DemandVentEnable field, select Enabled or On (enteliWEB only).
l In the CO2DemandVentSetpoint field, enter the CO2 setpoint value. Levels higher
than this setpoint will maintain the demand for ventilation.
4. In the additional settings, if you are using CO2 sensors to determine occupancy,
l (enteliWEB only) In the CO2 Occupancy On Setpoint field, enter the CO2 setpoint
value that will trigger an occupancy event. To disable CO2-based occupancy
detection, set this value to 2000 ppm.
l (enteliWEB only) In the CO2 Occupancy Off Setpoint field, enter the CO2 setpoint
value that will cancel an occupancy event.

Edition 2.6
Local Inputs Tab
For more information about using CO2 levels to trigger occupancy events, see the Sequence of
Operations topic.
Setting Up a Fan Speed Switch

This topic describes how to set up a fan speed switch using the Local Inputs tab on the
configuration page.
The fan coil algorithm supports up to 3 fan speeds.
Set Up a Fan Speed Switch
1. Next to the input number that you’ve assigned to the switch, in the Function field, select
FanSpdCtrl.
2. Leave the Action/Scale field blank.
3. In the additional settings, do one of the following steps:
l For a simple on/off switch, select FanSpdSwitchOffResistance and
FanSpdSwitchFan1Resistance. Using the switch specifications, enter the
resistance values.
l For multiple fan speed control, select the boxes that correspond to the different
speeds available on your switch.
Setting Up a Fan Coil 2-Pipe Changeover Sensor
1. Next to the input number that you’ve assigned to the switch, in the Function field, select
2PipeChangeOverTemp_.
2. Under Scale, Temp_10K3DegC or Temp_10K3DegF is selected, depending on the
temperature units set up on the General tab.
3. The Input Name field displays the object's name. You can change this name by clearing the
field and entering a new name.
For more information about the auto changeover works, see the Sequence of Operations help
topic.

Edition 2.6
Setting Up a Condensate Level Switch
This input is used for a level switch in a condensate pan which alerts the system when a specific
water level in the pan has been exceeded. When the condensate input is active, the algorithm
automatically turns off any active ductal cooling stage to prevent the condensate pan from
overflowing.
1. Next to the input number that you’ve assigned to the condensate pump or control, in the
Function field, select CondensateSwitch.
2. In the Action/Scale field, choose between direct or reverse control.
Setting Up Other Supporting Inputs

This topic describes how to set up supporting inputs like fault and window monitoring using the
Local Inputs tab on the configuration page
Set Up an Input
1. Next to the input number that you've assigned to the device, in the Function field, select the
option that applies to your setup:

AnalogMUX_ Creating an analog input that will be used for monitoring and
will not be used by the algorithm in the controller.
BinaryMUX_ Creating an binary input that will be used for monitoring and
will not be used by the algorithm in the controller.
WindowContact_ Setting up a window contact switch to detect open windows.
When an open window is detected, local heating or cooling
can be disabled as needed to save energy.
FilterStatus_ Adding a filter switch to detect if the fan coil filter is clean or
dirty.
Fault_ Creating an input to monitor the fault status of an equipment.
SpaceTempSetpoint_ Resistive slider or dial to control the space setpoint. The
resistance range must be within 0 to 20 kohms.
2. Select the associated action/scale option for the input.
3. If you had selected the SpaceTempSetpoint_ option to set up a resistive slider, in additional
settings, in the SetpointSliderMinResistance field, enter the minimum resistance of the

Edition 2.6
Local Inputs Tab
setpoint slider. In the SetpointSliderMaxResistance field, enter the maximum resistance

of the setpoint slider.
To enter the occupancy setpoint offset range for this resistive slider, go to the Setpoints tab
and enter the ± offset in the OccSetpointOffsetRange field.
For a list of input configuration software objects that correspond to each function, see the Input
Configuration Objects topic.
Setting Up Damper Feedback

This topic describes how to set up damper position feedback using the Local Inputs tab on the
configuration page. The actuator must have a position feedback feature.
Set Up Damper Feedback
1. Wire the actuator to the controller's physical input.

2. Next to the input number that you've assigned to the actuator, in the Function field, select
Damper1Feedback_.
If a tristate output is assigned to a damper, the algorithm will use this feedback signal rather
than a calculated damper position based on runtime.
3. In the Action/Scale Range field, select the input scale range that matches your damper
feedback signal. If you do not select a scale range, the default scale range is assumed to be
zero to full scale 0 to 100%.

Edition 2.6
Local Outputs Tab
Setting Up a Fan Coil or Heat Pump Output

This topic describes how to set up fan coil outputs (fan, heat and cooling) on the Local Outputs tab
of the enteliZONE configuration page.
The eZFC-424R4-24 and eZ-440R4-230 enteliZONE controllers support the fan coil and heat
pump algorithms.
The fan coil and heat pump algorithms support:
l 3-speed fan stages (Fan1, Fan2 and Fan3) or ECM (Electronically Commutated Motor) fan
(Fan1)
l 3 heat stages: Heat1, Heat2 and Heat3
l 2 cooling stages: Cool1, Cool2
l Single heat/cool stages: HeatCool1 and HeatCool2
For more information about the enteliZONE algorithm's sequence of operations, go to the
Sequence of operations help.
Set up a Fan Coil Output
1. In the Function field, make the following selections depending on the type of fan coil unit you
are setting up: (start a new line for every additional heat/cool/fan stage).
Each numbered line should correspond to the physical output used to connect to the output
device.
Duct heat or cooling will only be enabled in the algorithm when a supply fan is configured.
For a list of output configuration software objects that correspond to each function, see the
Output Configuration Objects help topic.
Stage or Output
Examples of Systems Function
Stage
4-pipe (duct heat) fan coil HydronicDuct_ Heat1_
HydronicDuct_ Cool1_
SupplyFan_ Fan1_
2-pipe (duct heat) fan coil HydronicDuct_ HeatCool1_
SupplyFan_ Fan1_

Edition 2.6
Local Outputs Tab
Stage or Output
Examples of Systems Function
Stage
4-pipe (2 stage heat) fan coil HydronicDuct_ Heat1_
HydronicDuct_ Cool1_
ElectriBaseBoard_ Heat2_
SupplyFan_ Fan1_
Heat pump with external signal for DXCompressor HeatCool1
reversing valve ReversingValve HeatCoolChangeOver
SupplyFan_ Fan1_
Dual stage heat pump DXCompressor Heat1_
DXCompressor Heat2_
DXCompressor Cool1_
DXCompressor Cool2_
SupplyFan_ Fan1_
If you are configuring an output signal to a reversing valve, you must use
HeatCoolx as the output stage for the compressor. In all other cases, use Heatx
and Coolx as output stages for the compressor. If you are configuring an output
signal to a 2-pipe fan coil, you must use HeatCoolx as the output stage.
2. In the Control Type field, select the method of control used on the output device signal.
The control types available in the drop-down list changes depending on the option selected
in the Function field as well as the physical output used to connect to the output device. For
more information about control types, see the Control Types topic.
3. In the Action field, choose between direct or reverse control.
4. If you selected a tri-state valve in the Control Type field, in the additional settings,
l OP1-2Runtime. Allows you to enter in seconds how long the floating valve actuator to
stroke from one end point to the other. This allows the algorithm to estimate the valve
position by keeping track of how many seconds it runs in each direction.
5. Complete this task by setting up a fan output.

Edition 2.6
Setting Up a Fan Output
This topic describes how to set up fan outputs on the Local Outputs tab of the enteliZONE
configuration page.
The enteliZONE controllers support up to 3 fan stages (Fan1, Fan2 and Fan3). Typically a 3-speed
fan stages uses Fan1, Fan2 and Fan3, and an ECM (Electronically Commutated Motor) fan uses
Fan1.
Sequence of Operations topic.
Set Up a Fan Output
1. In the Function field, select the option that applies to your setup:
Function Select this option if you are:

SupplyFan_ Setting up a fan for fan coil system.
For examples of typical fan coil set ups using the configuration page, go
to the fan coil output topic.
ExhaustFan_ Setting up a exhaust fan based on occupancy.
Output Configuration Objects topic.
2. In the Stage field, select the corresponding fan stage for the output device. If you are using
ORCAview,select the heat stage in the Output Stage field.
Start a new line for every additional fan stage.
The ExhaustFan function defaults to OccInterlock or occupancy interlock.
The control types available in the drop-down list will change depending on the option that
was selected in the Function field and the physical output used to connect to the output
device. For more information about control types, see the Control Types topic.
5. (enteliWEB only) The Output Name field displays the object's name. You can change this
6. In the additional settings available for some fan types:
l Constant Fan Modes. Allows you to select the occupancy mode in which the fan
runs constantly. In occupancy modes where the fan is not running constantly, the
algorithm assumes the fan is running intermittently.

Edition 2.6
Local Outputs Tab
Always The fan always runs regardless of the heating or cooling

Constant demand in the space.
Occupied/ The fan runs constantly during the occupied and unoccupied
Unoccupied override occupancy modes. Outside of these modes, the fan
runs intermittently.
Occupied/ The fan runs constantly during the occupied, unoccupied
Unoccupied override occupancy and standby modes. Outside of these
Override/ modes, the fan runs intermittently.
Standby
Always The fan does not run constantly at all and only turns on when
Intermittent heat is required.
l Manual Fan Occupancy Interlock. Select On if you want a manual fan command to
act as an occupancy signal. Otherwise select Off if occupancy is determined by a
schedule. This field is not applicable for VAV and VVT systems. Note: If you select On,
you need to set up FanSpdCtrl on the Inputs tab or a Fan Select button on your
LINKnet network sensor.
l HeatxFanMin/CoolxFanMin. These fields display the fan speeds that will run at a
specific heat or cooling stage ("x" is the stage number). For ductal heat/cool outputs,
with multi-speed fans, "1" is the default value. With ECM fans, FanMinSpeed (see the
section below) is the default value. "0" is the default value for non-ductal outputs.
When you modify these values, the fan speed associated with that output is changed.
For example, if you enter “3” in Heat2FanMin, the fan will respond to the heating
demand at Heat 2 stage by increasing to fan speed 3.
For HeatCoolx output stage, both the Heatx and Coolx fan minimums are set
together.
For more information about the interlock fields, see the fan sequence of operations
help topic.
l FanMinSpeed. The minimum supported supply fan speed. This field is enabled when
you select analog control type for supply fan with a default value of 20%. When you
select a binary control type for a single or multi-speed fan, this field displays the
minimum supported fan speed with a default value of 1 for ductal fans.
l FanMaxSpeed. The maximum supported supply fan speed. This field is enabled
when you select analog control type for supply fan with a default value of 100%. When
you select a binary control type for a single or multi-speed fan, this field displays the
maximum supported fan speed.

Edition 2.6
Setting Up Other Outputs
This topic describes how to set up supporting outputs like occupancy indicator on the Local Outputs
tab of the enteliZONE configuration page.
Set Up an Output
Select this option if you

Function
are:
OccIndicator_ Setting up an occupancy
output signal.
Any one of the following: ElectricBaseboard_, Controlling radiant heating
equipment.
HydronicBaseboard_
2PipeChangeOverValve Controlling a binary water
valve.
GCL-controlled AO_* Creating a custom AO object.
GCL-controlled BO_* Creating a custom BO object.
* Available only with programmable enteliZONE models and only on output terminals that
support AO or BO objects.
2. In the Stage field, for the radiant heating equipment, select the radiant heating equipment's
heat stage in the control sequence. If you are using ORCAview,select the heat stage in the
Output Stage field.
Function Stage or Output Stage

OccIndicator_ OccIndicator_ is the default
option.
Any one of the following: ElectricBaseboard_, Select one: Heat1_, Heat2_ or
HydronicBaseboard_ Heat3_.
2PipeChangeOverValve HeatCoolChangeOverCmd is the
default option.
GCL-controlled AO_ None_ is the default option.
GCL-controlled BO_ None_ is the default option.

Edition 2.6
Local Outputs Tab
The control types available in the drop-down list will change depending on the option that
was selected in the Function field and the physical output used to connect to the output
device. For more information about control types, see the Control Types topic.
Setting Up a Damper Output

This topic describes how to set up damper outputs on the Local Outputs tab of the enteliZONE
configuration page.
Sequence of Operations topic.
Set Up a Damper Output
Function Select this option if you are:

VentilationDamper_ Setting up a fresh air ventilation damper in a fan coil system.
This damper responds to CO2 levels only, not heating or cooling
demands. You need to set up a corresponding CO2 input.
2. In the Stage field, IAQ_ (Internal Air Quality) is selected automatically for fan coil
applications.
3. In the Control Type field, select the method of control used on the damper signal.
For more information about control types, see Control Types.

Edition 2.6
LINKnet I/O Tab
Configuring an eZNS-T100 Network Sensor

The enteliZONE controller is designed to work with the eZNS network sensor on a LINKnet
network.
This topic describes how to set up the eZNS network sensor's built-in components using the
LINKnet I/O tab on the enteliZONE configuration page.
Configurable controllers can only connect to 1 LINKnet device at a time. This LINKnet
device has to have a device address of "1" in order for it to work with the controller
algorithm. Multiple LINKnet devices (up to 4) are only supported by the programmable
controllers.
On the configuration page, the controller detects the network sensor that is connected to it and
displays only the fields that are relevant for that network sensor.
(enteliWEB only) If you do not have any network sensors online, you can still configure the settings
by selecting your network sensor and model from the Device Information field.
Red Box on LINKnet Tab
(enteliWEB only) When you switch between different network sensor models, active
settings that are not shared between network sensor models become outlined in red. You
need to select the None option to disable these fields.
Set Up the Temperature Sensor
1. In the Sensor Options section, next to Space Temperature sensor type, select the Function
option that is most appropriate for your needs:
Function Select this option if:

None The built-in temperature sensor on the eZNS sensor is not used.
SpaceTempControl The built-in temperature sensor is used to control the space
temperature. An input object (AI1001) is created the sensor
value which will be used by the algorithm to control space
temperature.
MonitoringOnly Input object AI1001 created but its value will not be used by the
internal algorithm for space temperature control.

Edition 2.6
LINKnet I/O Tab
Set Up the Humidity Sensor
1. In the Sensor Options section, next to Space Humidity sensor type, select the Function

None The humidity sensor on the eZNS sensor is not used.
MonitoringOnly The input object AI1003 is created for monitoring only.
Set Up the CO2 Sensor
1. In the Sensor Options section, next to Space CO2 sensor type, select the Function option
that is most appropriate for your needs:

None The CO2 sensor on the eZNS sensor is not used.
DemandControlVentilation Demand controlled ventilation system is used with the
CO2 sensors.
MonitoringOnly The input object AI1004 created but its value will not be
used by the internal algorithm for space CO2 control.
2. If you selected DemandControlVentilation, in the additional settings, in the

CO2DemandVentSetpoint field, enter the CO2 demand ventilation setpoint value.
3. If you are using CO2 levels to determine occupancy, in the additional settings,
(enteliWEB only) In the CO2 Occupancy On Setpoint field, enter the CO2 setpoint value that
will trigger an occupancy event. To disable CO2-based occupancy detection, set this value to
2000 ppm.
(enteliWEB only) In the CO2 Occupancy Off Setppoint field, enter the CO2 setpoint value
that will cancel an occupancy event.
Set Up the Occupancy Sensor
1. In the Sensor Options section, next to Occupancy Motion sensor type, select the Function

None The occupancy sensor on the eZNS sensor is not used.
OccupancyDetection The motion sensor on the eZNS network sensor is used to
detect occupancy.

Edition 2.6
MonitoringOnly Input object BI1005 created but its value will not be used by the
internal algorithm.
2. If you selected OccupancyDetection, in the additional settings, in the MotionOvrdTime field,

enter how long the occupancy override should last. This setting allows the use of momentary
contact style occupancy signals.
If you are using maintained-contact occupancy devices, enter zero in this field. In this case,
occupancy statue is only based on contact position.
Assign Functions to the Buttons and Slider
See Assigning Buttons and Slider Elements On eZNS-T100 Network Sensor.
Set Up the LCD Display
You can select which icons are displayed on the network sensor's LCD screen.
1. In the Display Options section, next to Occupancy, select the occupancy symbols you would
like displayed on the LCD screen.
Display
Select this option if you are setting up:
Option
NotDisplayed_ No occupancy status to be displayed.
ManInHouse_ Occupancy status: when a room is occupied, the man in a house icon
is displayed; when the room is unoccupied the icon changes so that
the man appears outside the house. When the occupancy sensor is
disabled, neither icon is displayed.
SunMoon_ Sun or Moon icon to be displayed. These icons can be used to show
day and night occupancy modes.
2. In the Display Setpoints, select how the setpoint of the current heating or cooling stage is
displayed on the LCD screen.
Display
Select this option if you are setting up:
Option
On Button The setpoint is displayed when the Temp Select, Temp Up or Temp
Down buttons are pressed.
Press
Always The setpoint is always displayed on the LCD in occupied mode.

Edition 2.6
LINKnet I/O Tab
3. In the Temp Setpoint Type, select the type of setpoint displayed.
Temperature
Description
Setpoint Type
NotDisplayed_ Setpoint will not be displayed.
DualSetpoint_ Separate setpoints are used during heating mode and cooling mode.
SingleSetpoint_ The average of both the heating and cooling setpoints.
SetpointOffset_ The offset that you can enter to adjust the occupied heating and
cooling setpoints. The range available for this offset is determined by
the OccSetpointOffsetRange field on the Setpoints tab.
4. Complete each option to determine how the backlight should appear onscreen.
Backlight
Do the following:
Options
Backlight Select a color from the list of available backlight colors.
Color
Backlight On Enter the desired backlight intensity when the screen is turned on with a
button press. 100% is the most intense.
Intensity
Backlight Off Enter the desired backlight intensity when the network sensor is idle.
100% is the most intense.
Intensity
Assigning Buttons and Slider Elements on eZNS-T100 Network Sensor
Introduction
The enteliZONE controller is designed to work with the eZNS network sensor on a LINKnet
network.
This topic describes how to assign specific functions to every button and slider element on the
eZNS network sensor using the LINKnet I/O tab on the enteliZONE configuration page.
There are as many as 95 button overlay combinations available for the eZNS network sensor.
Fortunately, all these combinations are based on this single layout which consists of 8 buttons and
the slider element:

Edition 2.6
Not all the buttons are used in every button overlay. In some cases, the slider element can be
converted into 2 additional up and down buttons, or omitted. In overlays where there are less than 8
buttons, button areas are merged together and counted as one (see the examples below).
(click to view larger version of image or images)

Edition 2.6
LINKnet I/O Tab
For more information about the button overlays, see the Button Overlay Selection Summary
document on George Support.
Set Up the Buttons and Slider Elements
The graphic supports all standard Delta button functions but other custom button behaviors require
GCL programming on a programmable controller. To designate a button to a custom button
behavior, select NotUsed_ from the Function field and refer to the button’s KeyPress property in
the GCL program.

Edition 2.6
1. On the LINKnet I/O tab, in the Button Options section, next to the button number that you
want to program, select one of the following functions that you want to assign to that button:
Function Select this option if you want to:

NotUsed_ Designate custom button behavior using GCL or if you want a
blank button.
EcoModeToggle_ Turns on the occupancy eco mode. In eco mode, the setpoints
are widened.
OccupancyOff_ Turn on the standby occupancy mode.

In the additional settings, in the PushButtonOvrdTime field, you
can enter how long the button override should last.
OccupancyOn_ Turn on the occupied mode.

OccupancyToggle_ Toggle between standby and occupied modes during scheduled

occupancy periods.
When pushed during unoccupied mode it starts an occupancy
override timer. When an override has been activated, pushing
the button again will cancel the override and reset the override
timer back to zero.
TempUnitsToggle_ Toggle between displaying the temperature in Celsius and the
temperature in Fahrenheit.
TempDown_ Decrease the temperature setpoint by 0.5 degrees with each

buttonpress. The 0.5 degree amount cannot be changed in the
enteliZONE configurable controller model. In the programmable
controller model, this setting can be overridden using GCL.
In the additional settings, in the OccSetpointOffsetReset field,
you can turn on the Occupancy Setpoint Offset Reset function*.

Edition 2.6
LINKnet I/O Tab
Function Select this option if you want to:

TempUp_ Increase the temperature setpoint by 0.5 degrees with each
buttonpress. The 0.5 degree amount cannot be changed in the
enteliZONE configurable controller model. In the programmable
controller model, this setting can be overridden using GCL.
TempSelect_ Set up the button to display the current temperature and setpoint
(if enabled). This button is usually used to switch to temperature
display mode from fan mode.
FanDown_ Decrease the displayed fan speed or toggle through fan stages
after FanCycle is pressed. With analog fans, fan speed will
change by this amount = (FanMaxSpeed – FanMinSpeed) / 6.
FanUp_ Increase the displayed fan speed or toggle through fan stages
after FanCycle is pressed. With analog fans, fan speed will
change by this amount = (FanMaxSpeed – FanMinSpeed) / 6.
FanCycle_ Set up the button to display the current fan stage. When the up
and down buttons are not available, toggle this button to select a
fan speed.
FanSelect_ Toggle between automatic and manual fan control. Can be used
together with the slider to manually change the fan speed.
Info_ Toggles between all built-in and input sensor measurements that
the eZNS is reading.
* Occupancy Setpoint Offset Range resets the occupancy setpoint offset at the start of a new
occupancy period.
2. In the Slider field, select a function that you want to assign to the slider:

Edition 2.6
Function Description
NotUsed_ Designate custom behavior using GCL or if you want a blank
slider icon.
AnalogSlider_ Select this if your button overlay contains a slider. A slider
enables users to set values by moving their finger along the
range.
UpDownButton_ Select this to use the “+” and “-“ icons on the slider as buttons to
increase or decrease values or to toggle between available
options.
Configuring DNS-24L Network Sensor
Introduction
The enteliZONE controller is designed to work with the DNS-24L network sensor on a LINKnet
network.
This topic describes how to set up the DNS-24L network sensor built-in components using the
LINKnet I/O tab on the enteliZONE configuration page.
Configurable controllers can only connect to 1 LINKnet device at a time. This LINKnet
device has to have a device address of "1" in order for it to work with the controller
algorithm. Multiple LINKnet devices (up to 4) are only supported by the programmable
controllers.
On the configuration page, the controller detects the network sensor that is connected to it and
displays only the fields that are relevant for that network sensor.
(enteliWEB only) If you do not have any network sensors online, you can still configure the settings
by selecting your network sensor and model from the Device Information field.
Red Box on LINKnet Tab
(enteliWEB only) When you switch between different network sensor models, active
settings that are not shared between network sensor models become outlined in red. You
need to select the None option to disable these fields.
Set Up the Temperature Sensor
See the temperature sensor set up section for the eZNS network sensor.
Set Up the Humidity Sensor
See the humidity sensor set up section for the eZNS network sensor.

Edition 2.6
LINKnet I/O Tab
Set Up the CO2 Sensor
See the CO2 sensor set up section for the eZNS network sensor.
Set Up the Occupancy Sensor
See the occupancy sensor set up section for the eZNS network sensor.
Assign Functions to the Buttons
See Assigning Buttons On DNS-24L Network Sensor.
Set Up the LCD Display
See the LCD display set up section for the eZNS Network Sensor. You cannot enter backlight
options for the DNS-24L in the configuration graphic.
Assigning Buttons on DNS-24L Network Sensor
Introduction
The enteliZONE controller is designed to work with the DNS-24L network sensor on a LINKnet
network.
This topic describes how to assign specific functions to every button on the DNS-24L network
sensor using the LINKnet I/O tab on the enteliZONE configuration page. The buttons on the DNS-
24L are numbered 1 to 4 in the graphic.
The graphic supports all standard Delta button functions but custom button behaviors require GCL
programming on a programmable controller type. To designate a button to a custom button
behavior, select NotUsed_ from the Function field and refer to the button’s KeyPress property in
the GCL program.

Edition 2.6
Set Up the Button Elements
On the LINKnet I/O tab, in the Button Options section, next to the button you want to program,
select one of the following functions that you want to assign to that button:
Recommended
Function corresponding Select this option if you want to:
DNS-24L button
NotUsed_ Not applicable Designate custom button behavior using GCL or
if you want a blank button.
OccupancyOff_ Button 1 Turns on the standby occupancy mode.
In the additional settings, in the
PushButtonOvrdTime field, you can enter how
long the button override should last.
OccupancyOn_ Button 2 Turns on the occupied mode.
OccupancyToggle_ Button 1 (DNS Toggle between standby and occupied modes
during scheduled occupancy periods.
Fan model)
When pushed during unoccupied mode it starts
an occupancy override timer. When an override
has been activated, pushing the button again will
cancel the override and reset the override timer
back to zero.
TempUnitsToggle_ Not applicable Recommended for use with the eZNS network
sensor. Toggles between displaying the
temperature in Celsius and the temperature in
Fahrenheit.

Edition 2.6
LINKnet I/O Tab
Recommended
Function corresponding Select this option if you want to:
DNS-24L button
TempDown_ Button 3 Decrease the temperature setpoint by 0.5
degrees with each buttonpress. The 0.5 degree
amount cannot be changed in the enteliZONE
configurable controller model. In the
programmable controller model, this setting can
be overridden using GCL.
OccSetpointOffsetReset field, you can turn on
the Occupancy Setpoint Offset Reset function*.
TempUp_ Button 4 Increase the temperature setpoint by 0.5
degrees with each buttonpress. The 0.5 degree
amount cannot be changed in the enteliZONE
configurable controller model. In the
programmable controller model, this setting can
be overridden using GCL.
OccSetpointOffsetReset field, you can turn on
the Occupancy Setpoint Offset Reset function*.
TempSelect_ Not applicable Recommended for use with the eZNS network
sensor.
FanDown_ Button 3 (DNS Decrease the displayed fan speed or toggle
through fan stages after FanCycle is pressed.
Fan model)
With analog fans, fan speed will change by this
amount = (FanMaxSpeed – FanMinSpeed) / 4.
FanUp_ Button 4 (DNS Increase the displayed fan speed or toggle
through fan stages after FanCycle is pressed.
Fan model)
With analog fans, fan speed will change by this
amount = (FanMaxSpeed – FanMinSpeed) / 4.
FanCycle_ Not applicable Recommended for use with the eZNS network
sensor.
FanSelect_ Not applicable Recommended for use with the eZNS network
sensor.
* Occupancy Setpoint Offset Range resets the occupancy setpoint offset at the start of a new
occupancy period.

Edition 2.6
Setpoints Tab
What is the Setpoints Tab?

Use the Setpoints tab on the enteliZONE configuration page to enter the temperature setpoints for
the system controlled by the enteliZONE controller.
The absolute minimum value for all occupied and unoccupied setpoints is 10°C (50°F). The
absolute maximum value is 30°C (86°F).
To change the temperature units, go to the General tab on the configuration page.
Space Temperature Setpoints

This section defines each setpoint on the configuration page.
Occupied Heating Setpoint (OccHeatingSetpoint)
When the controller is in occupied mode, heating is turned on when the space temperature drops
below this setpoint.
Unoccupied Heating Setpoint (UnOccHeatingSetpoint)
When the controller is in unoccupied mode, heating is turned on when the space temperature
drops below this setpoint.
Occupied Cooling Setpoint (OccCoolingSetpoint)
When the controller is in unoccupied mode, cooling is turned on when the space temperature rises
above this setpoint.
Unoccupied Cooling Setpoint (UnOccCoolingSetpoint)
When the controller is in unoccupied mode, cooling is turned on when the space temperature rises
above this setpoint.
Occupied Setpoint Offset Range (OccSetpointOffsetRange)
The offset range available at a LINKnet stat interface or a hardwired setpoint adjustment input. The
offset is added to the Occupied Heating and Cooling setpoints to set the values of the Current
Heating and Cooling setpoints in occupied mode.
For example, when you enter a value of 2.0, the offset range is ±2.0 from the heating setpoint and
±2.0 from the cooling setpoint.

Edition 2.6
Setpoints Tab
When a zero value is entered in this field, there is no offset and you will not be able to enter a
setpoint offset on the LINKnet tab nor will a user will able to adjust the setpoint at a stat interface.
Eco Mode Setback (EcoModeSetBack)
The setback amount when the network sensor is in Eco mode.

For example, when you enter a value of 1.0, the setback is -1.0 from the heating setpoint and +1.0
from the cooling setpoint.
Standby Setback (StandbySetback)
The setback amount when the network sensor is in Standby occupancy mode.
For example, when you enter a value of 1.0, the setback is -1.0 from the heating setpoint and +1.0
from the cooling setpoint.
Discharge Air Temperature Limiting Setpoint Differentials

These setpoint fields are only enabled if you had configured a discharge air temperature sensor on
the Local Inputs tab.
Discharge Air Temperature High Limit Setpoint Differential (DATHiLimitSetpointDiff)
Discharge Air Temperature High Limit Setpoint Differential. Used to calculate the maximum limit
above the CurrentHeatSetPoint (AV800) maintained by the enteliZONE algorithm during ducted
heating stages.
Discharge Air Temperature Low Limit Setpoint Differential (DATLowLimitSetpointDiff)
Discharge Air Temperature Low Limit Setpoint Differential. Used to calculate the minimum limit
below the CurrentCoolSetpoint (AV801) maintained by the enteliZONE algorithm during ducted
cooling stages.

Edition 2.6
Controllers Tab
What is the Controllers Tab?

Use the Controllers tab on the enteliZONE controller configuration page to fine tune the controller's
control feedback algorithm.
This section defines each field on the controller tab.
Controller Type
The control algorithm used by the controller. The algorithms are PI (Proportional-Integral), P
(Proportional), PID (Proportional-Integral Derivative) and I (Integral).
Proportional Band
The temperature range which the input must vary to cause a change in the controller output from 0
to 100%.
Deadband
The controller deadband is a small range in which temperature variation is allowed. When the input
is within the deadband, the controller output is fixed.
Deadbands should be small enough so that the occupant does not notice the temperature
variations within the deadband. However, making deadband ranges too small will make the
actuators adjust frequently and cause unnecessary wear on the equipment.
Integral Rate
The integral rate is defined as the amount of bias change per minute. It is expressed as percentage
change per minute.
The integral rate determines how fast the controller bias is adjusted to make the necessary
correction so that there is no offset between the signal and the setpoint.
Reset Band
The reset band provides a dynamic means to adjust the amount of output bias added to the
controller output.
When the input is outside of the reset band, the effective reset rate is equal to the specified reset
rate. When the input is within the reset band, the effective reset rate is proportionally reduced.
When the input is within the deadband, no further reset action occurs.

Edition 2.6
Controllers Tab
Outdoor Air Temperature Heating Lockout Setpoint (OAT Htg Lockout)
The heating system does not operate above this outside air temperature. The default value is 99°C
(210°F).
Heating Demand Limit (Htg Demand Limit)
Heating Demand Limit is the limit placed on the heating capacity for that zone. The limit is typically
left at the default value of 100%, or is a calculated value passed over the network from a
supervisory controller.
The limit affects the heating stages in a reverse order, starting with the last stage to the first stage.
Outdoor Air Temperature Cooling Lockout Setpoint (OAT Clg Lockout)
The cooling system does not operate below this outside air temperature. The default value is 99°C
(-146.2°F). This field is not used for the VAV and VVT systems.
Cooling Demand Limit (Clg Demand Limit)
Cooling Demand Limit is the limit placed on the cooling capacity for that zone. The limit is typically
left at the default value of 100%, or is a calculated value passed over the network from a
supervisory controller. This field is not used for the VAV and VVT systems.

Edition 2.6
enteliZONE Sequence of Operations
Introduction
This section describes the control sequences in the enteliZONE controller algorithm.
Setpoint Control
The controller determines heating and cooling modes by comparing the space temperature to the
CurrentHeatSetpoint (AV800) and the CurrentCoolSetpoint (AV801).
The active space temperature setpoint (AV829) displays the setpoint that is currently operating. In
heating mode, the active setpoint will display the heating setpoint, and in cooling mode the active
setpoint will display the cooling setpoint.
When there is no call for heating or cooling, the controller is in deadband mode. In deadband mode
(between unoccupied heating and cooling setpoints), the active setpoint displays the current space
temperature.
Setpoint Range Limits
The heating setpoint can never be higher than its corresponding cooling setpoint. If one setpoint is
adjusted, the other setpoints will dynamically adjust to maintain their relative positions (see above
diagram). Eco mode and standby setbacks also are limited to the range between unoccupied
heating and cooling setpoints.
The absolute minimum value for all occupied and unoccupied setpoints is 10°C (50°F). The
absolute maximum value is 30°C (86°F).

Edition 2.6
Occupancy Modes
The occupancy modes are used to determine how minimum air quality ventilation rates are
maintained. The enteliZONE controller operates in several modes:
Occupancy
Description
Mode
Occupied Occupied mode is on when either a remote or local schedule is active.
Unoccupied Overrides are initiated when both the local and remote schedule inputs are off
Override and motion sensor inputs or pushbutton presses are detected.
Standby With standby mode, the space is unoccupied but is assumed to become
occupied at any time. Standby mode saves energy by dropping the minimum
ventilation rates and relaxing the occupied setpoints by a setback. This standby
setback is less than the setback in unoccupied mode so that the standby space
can quickly reach its occupied setpoints when the space becomes occupied
again.
Set up standby mode by creating an active occupancy schedule, one or more
motion or pushbutton occupancy inputs, and entering a value greater than zero
in the StandbySetback field on the Setpoints Tab. Standby mode can be
disabled by setting the StandbySetback field to zero.
Unoccupied The space enters unoccupied mode when all occupancy inputs are off and any
timed overrides have expired. The setpoints are allowed to relax further than
standby mode for increased energy savings.

Edition 2.6
Switching Between Occupancy Modes
The enteliZONE controller switches between the occupancy modes based on several types of
inputs. Inputs can be local or network in origin.
l Schedule-based input using the Local Schedule (SCH1) and Remote Schedule (MV1)
software objects. SCH1 is a BACnet object that supports binary (on/off) 7-day recurring
schedules. It does not support exception scheduling or non-binary schedule types. MV1 can
be written over the network.
When either one of these objects is turned on, schedule-based occupancy is enabled and
switches between Occupied and Standby modes in response to any event-based occupancy
signals.
When scheduling is off, event-based occupancy signals cause the space to switch between
Unoccupied and Unoccupied Override modes.
l CO2 input. Working with an input CO2 sensor, the algorithm supports using CO2 levels as a
method of detecting occupancy.
This sequence uses 2 setpoints:
l CO2OccOnSetpoint (AV182). When the CO2 level exceeds this setpoint, a CO2
occupancy signal is generated. To disable CO2-based occupancy detection, set this
value to 2000 ppm.
l CO2OccOffSetpoint (AV183) which specifies the CO2 level the space has to drop to
before a CO2 occupancy event is cancelled.
When the CO2 level drops below the level set at CO2OccOffSetpoint, the current
occupancy mode does not immediately change due to a built-in hysteresis factor =
(CO2OccOnSetpoint - CO2OccOffSetpoint) / 10. Occupancy mode changes when
CO2 level is lower than this amount (CO2OccOffSetpoint – hysteresis factor).
CO2 Level Occupancy Mode

Above OccupancyMode toggles between Occupied and Unoccupied_
CO2OccOnSetpoint Ovrd as scheduled inputs turn on and off.
Between both If there is a schedule, OccupancyMode will go to Occupied.
setpoints If there is no schedule, OccupancyMode will go to Unoccupied.
Below OccupancyMode toggles between Standby and Unoccupied as
CO2OccOffSetpoint scheduled inputs turn on and off.

Edition 2.6
l Motion or pushbutton occupancy inputs, like occupancy contact signals. These can be
further divided into maintained contact and momentary contact signals. When scheduling is
off, motion or pushbutton inputs cause the space to switch between Unoccupied and
Unoccupied Override modes.
The following table describes the supported types of motion or pushbutton occupancy inputs:
Motion or
pushbutton
Description
occupancy
input
Motion Motion sensor starts a timed override when motion is detected in the
space.
Occupancy This is a pushbutton located in the space that when pressed starts or
Override button renews a timed occupancy override.
Occupancy This is a pushbutton located in the space that when pressed starts or
Toggle button renews a timed occupancy override.
Occupancy This is a pushbutton located in the space that when pressed cancels
Cancel button any existing occupancy override. This option is only available with the
eZNS or DNS network sensors.
Occupancy This is a maintained contact occupancy signal such as a mechanical
Maintained time clock signal or a 2-position switch.
Contact

Edition 2.6
Setpoints and Occupancy Modes
The occupancy modes determine which temperature setpoints are used for the space.
Occupied Mode
In occupied mode:
Current heating setpoint = Occupied heating setpoint + Occupied setpoint offset
Current cooling setpoint = Occupied cooling setpoint + Occupied setpoint offset
In occupied mode (with Eco Mode set up on network sensor or enabled using MV13 object):
Current heating setpoint = Occupied heating setpoint + Occupied setpoint offset - Eco Mode
Setback
Current cooling setpoint = Occupied cooling setpoint + Occupied setpoint offset + Eco Mode
Setback
Occupant setpoint sits between the occupied heating and cooling setpoints. The occupied setpoint
offset is restricted to be within the occupied setpoint offset range.
In Eco Mode, the occupied setpoint offset range is relaxes by the amount specified by the Eco
Mode Setback.
For night overrides, a pushbutton or motion override initiates the Night override mode.
Standby Mode
In standby mode:
Current heating setpoint = Occupied heating setpoint + Occupied setpoint offset - Standby
Setback
Current cooling setpoint = Occupied cooling setpoint + Occupied setpoint offset + Standby
Setback
In standby mode (with Eco Mode set up on network sensor or enabled using MV13 object):
Current heating setpoint = Occupied heating setpoint + Occupied setpoint offset - Eco Mode
Setback - Standby Setback
Current cooling setpoint = Occupied cooling setpoint + Occupied setpoint offset + Eco Mode
Setback + Standby Setback
Unoccupied Mode
In unoccupied mode:
Current heating setpoint = Unoccupied heating setpoint
Current cooling setpoint = Unoccupied cooling setpoint

Edition 2.6
Heating (Fancoil)
Heating load is present when the HeatCoolLoad (AV802) value is between 0 and 100.
The available heating stages in the algorithm are sequential and are as follows: Heat1, Heat2, and
Heat 3. The heating load is evenly divided by the number of heat stages that you’ve set up, plus any
unused fan capacity.
For example, in a system that has 3 stages of heat plus an ECM fan,
l HeatCoolLoad from 0 to 25% is for the first stage heat, from 25 to 50% for the second stage
heat, from 50 to 75% for the third stage heat, and 75 to 100% will modulate the fan.
l If the second stage heat was binary, the heat stage would turn ON when HeatCoolLoad rose
above 50% and turn OFF when HeatCoolLoad fell below 25%.
l If the second stage heat were analog, the heat stage would modulate from 0% at
HeatCoolLoad of 25%, to 100% at HeatCoolLoad of 50%.
l Without heating interlocks, the ECM fan would run at FanMinSpeed until HeatCoolLoad
reached 75%, and then ramp to FanMaxSpeed as HeatCoolLoad went to 100%.
If outdoor air temperature (AV9) rises above outdoor air temperature heating lockout setpoint
(OATHeatLockoutSetpoint), then all heating is disabled. The outdoor air temperature will have to
drop by 1.0 °C below this setpoint before the heating is re-enabled.
Cooling (Fancoil)
Cooling load is present when the HeatCoolLoad (AV802) value is between 0 and -100.
The available cooling stages in the algorithm are sequential and are as follows: Cool1 and Cool2.
The cooling load is evenly divided by the number of cooling stages that you’ve set up.
Like the heating stages, the cooling load is evenly divided by the number of cooling stages that
you’ve set up, plus any unused fan capacity. Other than fewer stages, the cooling sequence is the
same as the heating sequence.
If outdoor air temperature (AV9) falls below outdoor air temperature cooling lockout setpoint
(OATCoolLockoutSetpoint), then all cooling is disabled. The outdoor air temperature will have to
rise by 1.0 °C above this setpoint before the cooling is re-enabled.
Time-Proportional Heating and Cooling
Time-proportional heating and cooling outputs are modulated based on a pulse with a period equal
to the TimePropPeriod (AV154) object value. TimePropPeriod (AV154) has a default value of 100
seconds. The algorithm supports a range between 10 to 600 seconds.

Edition 2.6
The time-proportional algorithm scales the heating and cooling output using these maximum and
minimum values:
l the minimum (TimePropHtgMin AV152) and maximum heat output (TimePropHtgMax

AV153)
l the minimum (TimePropClgMin AV150) and maximum cooling output (TimePropClgMax
AV151)
For each heating or cooling stage, the algorithm calculates how long the active heating or cooling
output object is turned on using the following formula: (heating used as an example)
Hydronic outputs "active" time = TimePropPeriod/100 * (heating stage output% *
(TimePropHtgMax - TimePropHtgMin)/100 + TimePropHtgMin)
Electric output "active" time = TimePropPeriod /100 * heating stage output% *
TimePropHtgMax/100
The time period when the output object is turned off = TimePropPeriod - "Active" time.
For electric duct or electric baseboard outputs set up as time-proportional, the minimum heat
output % is ignored by the algorithm to prevent overheating, even when the minimum heat output is
greater than 0. The maximum heat output % still applies to honour the system's upper safety limits.
For hydronic heat outputs, both minimum and maximum heat output % are used.
For programmable controllers, if custom output objects are used, the pulse has a 100% duty cycle.
The output is directly controlled by a GCL program and the custom AV objects are used to
modulate the pulse.
Auto Changeover
The temperature of the supply water delivered to the hydronic coils in a 2-pipe fan coil configuration
automatically determines what its output (HeatCoolx) will do.
When the supply water temperature is below 20°C (68°F), the HeatCoolx output is in cooling
mode. At temperatures above 25°C (77°F), the HeatCoolx output is in heating mode. Between 20
and 25°C, the output can either be heating or cooling.
The active output mode is saved in the MV803 object (HeatCoolChangeOverStatus).
Discharge Air Temperature
The discharge air temperature (DAT) is the duct temperature downstream from any local heating
or cooling stages that supply the air to that space. This section applies to a space with a DAT
sensor and ducted heating or cooling stages.

Edition 2.6
The heating or cooling output is limited by the discharge air limited controller that maintains a
maximum limit above the CurrentHeatSetPoint (AV800) in heating, and a minimum limit below the
CurrentCoolSetpoint (AV801) during cooling. The maximum limit is calculated by adding the
discharge air temperature high limit setpoint differential (DATHiLimitSetpointDiff) to the
CurrentHeatSetPoint, and the minimum limit is calculated by subtracting the discharge air
temperature low limit setpoint differential from the CurrentCoolSetpoint.
Limiting the ducted heating and cooling stages ensures the temperature differential between space
air and supply air is not large enough to cause hot air to build up near the ceiling. Limiting heating
and cooling outputs also encourages cold air to spread out via the diffuser and mix well with the
room air. Cold air that drops down without mixing can create complaints of cold drafts.
Fan (Fancoil)
The section describes the supply fan sequences supported by the fan coil algorithm for duct heating
and cooling.
Duct heat or cooling will only be enabled in the algorithm when a supply fan has been
configured.
Manual Fan Speed Control
The algorithm allows you to manually change the fan speed when you set up a fan speed control
switch as an input or on your network sensor.
In both manual and automatic fan speed control, when you switch between fan stages, there is a 1-
second delay where the prior stage turns off before the next stage can turn on.
If the fan is turned off while in manual mode, when the space temperature falls outside of the
unoccupied setpoints, the algorithm will override the fan to prevent temperature extremes.
Automatic Fan Speed Control
When there is no manual fan speed control switch configured, the algorithm assumes automatic
fan speed control. In automatic fan speed mode, the occupancy state of the space, heat/cool
demand and the constant fan mode statuses determine when a fan runs and its speed: the
algorithm can either run the fan continuously, or intermittently (runs only when there is a heat or
cooling demand). For a fuller description of the various constant fan modes, see the fan coil set up
procedure.
Run the fan continuously if you want the fan coil to provide both ventilation and temperature control.
If the fan coil does not provide ventilation, then running the fan intermittently will save energy. While
the fan is in constant mode:

Edition 2.6
l If the system uses a multi-speed fan, the minimum fan speed that the fan can run at is its
lowest speed.
l If the system uses an ECM fan, the minimum fan speed that the ECM fan will run at is its
stated minimum speed.
When there is no heat/cooling demand for the fan, the fan (when set to run intermittently) will run
for a certain time (FanDelayOffTime AV143) before it turns off completely.
Fan Stages
The algorithm supports up to 3 fan stages for binary fans (multi-speed) and analog fans (ECM).
The fan must be running for duct heating or cooling to be active.
Heating and cooling demands are determined by the HeatCoolLoad (AV802) object. Heating load
is present when the HeatCoolLoad value is between 0 and 100. Cooling load is present when the
HeatCoolLoad value is between 0 and -100. The algorithm divides the overall heating or cooling
load equally between all heating or cooling stages.
Stage load is the portion of the HeatCoolLoad that is dedicated to a particular stage of heating or
cooling.
In the configuration graphic, a fan stage can be associated with a single or multiple heat or cooling
stages, or multiple fan stages can be associated with a single heat or cooling stage.
Single Speed Fans
The following table describes the duct fan stage behavior for a fan with intermittent fan mode
setting. A fan set at constant fan mode is always running.
Heat/
Cooling Occupied Mode Unoccupied Mode
Stage
Binary Fan turns on when there is a duct heating or Fan turns on at 100% overall
cooling demand. Turns off when duct heating or load and turns off when the
cooling demand is 25% to reduce overshoot. demand drops down to 25%.
Analog Fan turns on at 25% stage load and stays on. Fan turns on at 100% overall
Fan turns off when demand drops to 0%. load and turns off when the
demand drops down to 0%.

Edition 2.6
Interlocking Fan Speeds for Multiple Speed and ECM Fans
Interlocking fan speed settings allow you to set a specific fan speed for a heating or cooling stage.
On the Local Outputs tab, there are additional supply fan settings to enable fan speed interlocks,
specifically in the HeatxFanMin and CoolxFanMin fields where x is the heat/cool output stage
number.
By default, when duct heating or cooling output is set up, the default fan speed interlock
(HeatxFanMin or CoolxFanMin field) for that duct stage is automatically given a value of 1 (for
single and multiple speed fans) or FanMinSpeed (for ECM fans). Space heating stages are left
unchanged at the value of zero. This ensures the fan stage is always running for the duct heating
and cooling stages.
When HeatxFanMin or CoolxFanMin equals zero for active stages, the current fan speed will not
change when that heating or cooling stage x is active.
As a result, in some cases, higher fan speeds may remain unused at the end of active heating or
cooling stages. The algorithm takes this into account and uses these unused fan speeds as the final
heat or cool stage. This is referred in this application guide as the “unused fan capacity”.
ECM Fans
When an ECM fan is running, the fan speed is at least its minimum fan speed or whatever greater
value is entered in the FanMinSpeed field in the fan settings section.
Any value larger than the FanMinSpeed in the HeatxFanMin/CoolxFanMin fields will cause the fan
to run faster when stage x is active (also known as interlocking). However, any value between zero
and FanMinSpeed will cause the fan to run at FanMinSpeed.
The behavior of an ECM fan running in intermittent mode is described in the following table and
images. Even though the images only describe heat stages, the cooling stages are identical in
behavior.
Heat/
Stage
Binary Fan turns on at FanMinSpeed Fan turns on at 100% duct stage load at
when there is a duct heating or FanMaxSpeed and turns off when the
cooling demand. demand drops down to 25%.
Turns off when duct heating or
cooling demand is 25% to
reduce overshoot.

Edition 2.6
Heat/
Stage
Analog Fan turns on at 25% stage load Fan turns on at 100% duct stage load at
at FanMinSpeed and stays on. FanMaxSpeed and turns off when the
Fan turns off when demand demand drops down to 0%.
drops to 0%.

Edition 2.6

Edition 2.6
In an analog duct stage, the ECM fan ramps up to 10% per second.

Edition 2.6
Multi-Speed Fans
The behavior of a multiple speed fan running in intermittent mode is described in the following table
and images. Even though the images only describe heat stages, the cooling stages are identical in
behavior.
When a multi-speed fan runs at its lowest speed, Fan1 is on while Fan2 and Fan2 are off.
Heat/
Stage
Binary Fan turns on for the duct heating or Fan turns on at 100% duct stage
cooling stage. Turns off when stage load is load and turns off when the demand
25% to reduce overshoot. drops down to 25%.
Analog Fan turns on at 25% duct stage load and Fan turns on at 100% duct stage
stays on. Fan turns off when demand load and turns off when the demand
drops to 0%. drops down to 0%.

Edition 2.6
Edition 2.6

Edition 2.6
Demand Control Ventilation
Demand control ventilation (DCV) control sequence determines the amount of fresh air in the
space. The sequence only operates during occupied modes and is disabled when the building is
unoccupied. To use the DCV algorithm, on the Local Inputs tab of the configuration graphic, you
should have a CO2 input (AV3) set up with the DemandVentEnable setting (BV103) turned on.
You should also enter a CO2 demand setpoint in the CO2DemandVentSetpoint (AV185) field.
The CO2 demand is reflected in the demand control ventilation (AV813) object. The algorithm
determines the airflow setpoint needed to meet this demand. The demand increases when the
Space CO2 remains above the CO2DemandVentSetpoint and decreases when the Space CO2
falls below the CO2DemandVentSetpoint.
This airflow setpoint is not only controlled by the CO2 demand, it is also affected by the temperature
control airflow demand via a high select logic. This means a higher CO2 airflow demand could
overheat or overcool a space if that zone does not have any local temperature controls.

Edition 2.6
Open Window Detection

When the opening of windows is being monitored and an open window is detected, all heating and
cooling stages are disabled. Heating is re-enabled when the space temperature falls below 6 °C.
Heat Pump
The algorithm supports one or more heat and cooling stages for heat pump devices. This section
describes what to expect when you’re setting up a heat pump in the configuration graphic.
If you want to control the reversing valve using the configuration graphic, the reversing valve will
switch between the heat and cooling stages in response to the heat and cooling loads at each
stage. Heat and cooling demands are indicated by the HeatCoolLoad (AV802) value. For more
information about HeadCoolLoad and how the heat and cooling loads are divided between the
different heat and cooling stages, see the Heating and Cooling sections in this Sequence of
Operations section.
When switching between heating and cooling, the algorithm will not change the state of the
reversing valve until all compressor outputs have been off for at least 60 seconds.
With no reversing valve output configured, the algorithm turns the Heatx outputs on when there is
heating demand, and turns the Coolx outputs on when there is cooling demand.

Edition 2.6
enteliZONE Database Configuration Objects
Introduction
The following tables list the database objects that are used to configure the enteliZONE controllers.
Typically these object values are not adjusted directly but are entered in the configuration graphic
(ORCAview 3.40) or on the configuration page (enteliWEB 4.1 and higher).
For Binary Inputs (which map to destination MV objects), when they are set to the NotUsed_ state,
the inputs are ignored by the algorithm and any dependent functions are disabled. With input states
other than NotUsed_, the input is considered enabled by the algorithm.
When not being controlled by a local input this destination MV will typically remain in its last state.
Once enabled, you must manually set the MV back to the NotUsed_ state to disable.
For Analog Inputs (which map to destination AV objects), if they are not linked to a local input, the
inputs can still be enabled by writing to the value remotely or from GCL. The algorithm looks at the
lastwriter property for the input destination; the input is enabled by the algorithm if the lastwriter
property isn't null. To disable this point, you must reset the point to clear its lastwriter value.
Programs are prevented from writing to algorithm configurable MV objects, I/O
configurable MV objects and network setting variables. These include MV110-147 and
MV1001-1006. See the eZFC-424R4-24 or eZ-440R4-230 controller 2.2 release notes
for more information.
Input Configuration Objects

Object Name Object Ref Default Description
SpaceTemp AV1 0 Celsius Temperature. Default is to
average if multiple inputs are
configured.
SpaceCO2 AV3 0 ppm Carbon dioxide levels.
SpaceHumidity AV4 0 %RH Humidity.
Discharge AV6 0 Celsius Duct temperature downstream
from any local heating or
AirTemp
cooling stages that supply the
air to that space.
2PipeChange AV7 0 Celsius Temperature of a 2-pipe
OverTemp hydronic loop of a fan coil unit.
OutdoorAirTemp AV9 0 Celsius Outdoor air temperature.

Edition 2.6

Damper1 Feed- AV13 0% Position feedback signal from a
damper.
back
FanSpdCtrl AV1 % Manual supply fan input.
(ManualFanSpeedCmd)
FanSpdSwitch AV192 0 kohm Resistance of the fan speed
OffResistance switch when it is in the off
position.
FanSpdSwitch AV193 100,000 Resistance of the fan speed
AutoResistance kohm switch when it is in the Auto
position.
Fan1Resistance switch when it is in the Fan
Speed 1 position.
Speed 2 position.
Speed 3 position.
FanStatus MV7 NotUsed_ Status of the zone supply fan.
WindowContact MV6 NotUsed_ Window contact to detect open
windows in order to control
local heating or cooling.
Condensate MV9 NotUsed_ Used to disable cooling when
condensate is detected in the
Switch
bottom of the unit.
Fault MV10 NotUsed_ Used to display equipment
working status.
Filter Status MV11 NotUsed_ Switch placed across an air
filter to provide a signal to let
operators know when it is time
to change the filter.
HeatCool MV803 NotUsed_ The output status of the 2-pipe
fan coil.
ChangeOver
Status

Edition 2.6
Button 1 to 8 MV1010 to MV1017 NotUsed_ Options for the buttons of the
LINKnet network sensor used
with the enteliZONE controller.
Occupancy Configuration Objects

Object
Object Name Default Description
Ref
Local Schedule SCH1 N/A Local schedule object on the controller. It is
used to provide local scheduled operations
based on a 7-day recurring schedule.
Exception scheduling is not supported.
Remote Sched- MV1 NotUsed_ An object that can be written over the network
to provide a remote schedule input.
ule
OccOvrdButton MV2 NotUsed_ Network sensor button used as an occupancy
override button.
OccToggle But- MV3 NotUsed_ Network sensor button to toggle between
standby and occupied modes during scheduled
ton
occupancy periods.
OccMotion MV4 NotUsed_ Motion sensor that is integrated into the
network sensor. Object can be set up to be a
maintained contact or a momentary contact
type.
OccMaintained MV5 NotUsed_ Used for any maintained contact signal type
like a hotel keycard holder, manual switch or
Contact
mechanical time clock input.
Occupancy MV800 Unoccupied_ Occupancy modes.
Mode
OccIndicator MV806 NotUsed_ Used to display the occupancy icon on the
network sensor LCD screen.

Edition 2.6
Output Configuration Objects

Object
Ref
TimePropClgMin AV150 0% The minimum cooling output value. The
time-proportional algorithm scales the
cooling output using this minimum value.
TimePropClgMax AV151 100% The maximum cooling output value. The
cooling output using this maximum value.
TimePropHtgMin AV152 0% The minimum heating output value. The
heating output using this minimum value.
TimePropHtgMax AV153 100% The maximum heating output value. The
heating output using this maximum value.
TimePropPeriod AV154 100s The period of the pulse that is used to
modulate the time-proportional heating
and cooling outputs.
Heat1FanMin AV199 0 The optional fan speed interlock when
duct Heat 1 stage is running.
Cool1FanMin AV202 0 The optional fan speed interlock when
duct Cool 1 stage is running.
Cool2FanMin AV203 0 The optional fan speed interlock when
duct Cool 2 stage is running.
HeatCoolLoad AV802 0% Monitors if the system is in heating or
cooling mode (<0 = cooling, >0 =
heating).
Heat1 AV803 100 % First heating stage.
Heat2 AV804 0% Second heating stage.
Heat3 AV805 0% Third heating stage.
Cool1 AV806 0% First cooling stage.
Cool2 AV807 0% Second cooling stage.

Edition 2.6
Object
Ref
Fan1 AV810 0% First fan stage.
Fan2 AV811 0% Second fan stage.
Fan3 AV812 0% Third fan stage.
DemandCtrlVent AV813 0% Demand Control Ventilation. Directly
controls ventilation damper position (fan
coil).
Custom1* AV815 0% Custom stage associated with GCL
controlled output.
Custom2* AV816 0% Custom stage associated with GCL
controlled output.
HeatCool ChangeOver- MV805 NotUsed_ Used to display the status of the reversing
valve in a heat pump.
Cmd
ManualFanOccInterlock BV104 Off Select On if you want a manual fan
command to act as an occupancy signal.
Otherwise select Off if occupancy is
determined by schedule.
* Available only with enteliZONE programmable models.
Setpoint Configuration Objects

Object
Ref
OccHeating Setpoint AV100 21 Base heating setpoint in occupied mode
Celsius
OccCooling Setpoint AV101 24 Base cooling setpoint in occupied mode
Celsius
UnOccHeating Set- AV102 17 Unoccupied heating setpoint
point Celsius
UnOccCooling Set- AV103 21 Unoccupied cooling setpoint
point Celsius

Edition 2.6
Object
Ref
HeatCool AV104 5 Time delay between heating and cooling to
prevent overshoot when the heating and
ChangeoverDelay minutes
cooling setpoints are close together. Range
between 1 to 30 minutes.
Standby Setback AV105 1 Extra setpoint offset added in standby mode.
Celsius
EcoMode Setback AV106 1 Amount of setback that gets subtracted from
heating and added the cooling setpoints when
Celsius
controller is in eco mode.
OccSetpoint Off- AV107 3 Determines the offset range available to
change the Occupied Heating and Cooling
setRange Celsius
setpoints at a LINKnet stat interface or a
hardwired setpoint adjust input.
OATHeat Lock- AV160 99 Outside air temperature heat lockout setpoint.
outSetpoint Celsius
DATHiLimit Set- AV161 25 Discharge air temperature high limit setpoint
differential.
pointDiff Celsius
HeatingDemandLimit AV163 100% Heating demand limit.
OATCool Lock- AV165 -99 Outside air temperature cooling lockout
setpoint. Not used by VAV/VVT systems.
outSetpoint Celsius
DATLowLimit Set- AV166 15 Discharge air temperature low limit setpoint.
pointDiff Celsius
CoolingDemand AV167 100% Cooling demand limit.
Limit
CO2OccOnSetpoint AV182 900 CO2 high limit occupancy setpoint.
ppm
CO2OccOffSetpoint AV183 700 CO2 low limit occupancy setpoint.
ppm
CO2Demand AV185 1100 CO2 demand ventilation setpoint.
VentSetpoint ppm

Edition 2.6
Object
Ref
FanMinSpeed AV197 20 Minimum supported fan speed.
(ECM)
1
(binary)
FanMaxSpeed AV198 100 Maximum supported fan speed.
(ECM)
1
(binary)
CurrentHeat Set- AV800 0 Current heating setpoint reading.
point Celsius
CurrentCool Setpoint AV801 0 Current cooling setpoint reading.
Celsius
ActiveSpace Tem- AV829 Celsius Current active setpoint (reading either heating
or cooling setpoint, reads space temperature in
pSetpoint
deadband).
In manual mode, the active setpoint will
override the current heating and cooling
setpoints.
Device Instance/ BACnet Address Object

The BACnet address is a unique address given to every controller and device in a Delta Controls
network.
You can set or change the enteliZONE controller’s BACnet address by writing to the AV97 object
(BACnetAddress) in these versions:
l eZ-440R4-230 controller firmware version 2.1 and higher

l eZFC-424R4-24 controller firmware 2.2 and higher
The BACnet address can range from 1 to 4 million+. Since AV objects can only store 6 digits of the
BACnet address, the seventh or millionth digit is stored in the AV97 description field.
When a value is manually written to AV97 object, enteliWEB recognizes that the user is trying to
software address the controller and so DNA, if enabled, will automatically turn off. To turn DNA
back on, you need to access the DEV object in enteliWEB and select the DNA checkbox.

Edition 2.6
Control Types
Control Types
What are Control Types?

On the Local Outputs tab of the enteliZONE configuration page, control types refer to the methods
of control used on the output device signal. The enteliZONE controllers support 5 control types:
Control Types Description

Analog Provides modulating control using a 0-10V analog signal.
Binary Provides 2 position ON/OFF control using a TRIAC or relay output.
Time Provides modulating control for wax valves using a time-proportioned

signal.
Proportioned
Tri-State Open Used to open a tri-state valve.
Tri-State Close Used to close a tri-state valve.
The control types that are available in the Control Type field drop-down list depend on the previous
selection made in the Function field. For example, a binary control type would be the only control
type available if the occupancy indicator function is selected. The table below lists the output
functions and their associated control types.
Output Function Control Type

Hydronic Duct Analog, binary, time proportioned, tri-state open, tri state close
Hydronic Baseboard
Electric Duct Analog, binary, time proportioned
Electric Baseboard
DX Compressor Binary
Reversing Valve
2PipeChangeOverValve
Occupancy Indicator Binary
Supply Fan Analog, binary
Exhaust Fan
The Control Type field is also affected by the physical output on the controller used to connect to
the output device. For example, if you are using the TRIAC physical output, the analog control type
does not appear in the Control Type field drop-down list. The following table lists all the physical
outputs and their associated control types.

Edition 2.6
Physical Output Control Types
Universal Analog, binary, time proportioned, tri-state open, tri-state close
Relay Binary, tri-state open, tri-state close
TRIAC Binary, time proportioned, tri-state open, tri-state close
Analog Analog, binary
As another example, the physical outputs of the eZFC-424R4-24 controller support specific control
types. See the screenshot below for more details. In this case, outputs 1 to 4 do not support analog
control because they are TRIAC physical outputs. If you select HydronicDuct as a Function option
in outputs 1 to 4 in enteliWEB, the analog Control Type option is absent.

Edition 2.6
Open Source Licensing
Open Source Licensing

The enteliZONE controller uses open source and third party components and therefore must
include the below licensing information.
lwIP
lwIP is licenced under the BSD licence:
Copyright © 2001-2004 Swedish Institute of Computer Science. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The name of the author may not be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Edition 2.6
ST Microelectronics
Copyright © 2015 STMicroelectronics International N.V.. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted,
provided that the following conditions are met:
1. Redistribution of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. Neither the name of STMicroelectronics nor the names of other contributors to this software may
be used to endorse or promote products derived from this software without specific written
permission.
4. This software, including modifications and/or derivative works of this software, must execute
solely and exclusively on microcontroller or microprocessor devices manufactured by or for
STMicroelectronics.
5. Redistribution and use of this software other than as permitted under this license is void and will
automatically terminate your rights under this license.
THIS SOFTWARE IS PROVIDED BY STMICROELECTRONICS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL
PROPERTY RIGHTS ARE DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW.
IN NO EVENT SHALL STMICROELECTRONICS
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Edition 2.6
Document Revision History
Document Revision History
Document
Date
Edition Change Description
Published
Number
2.5 May 21, First Release of document.
2013
2.5 June 4, Added the Data Exchange section that describes the default
2015
data exchange method.
2.5 July 13, Added page numbers to the footer.
2015
2.5 June 24, Added open source licensing section.
2016
2.6 July 2017 Added support for firmware 2.2 features:
l New heat pump and radiant heat algorithms

l New heat pump sequence of operations
l enOcean integration section
l Upgrade from configurable to programmable using flash
loader.
l New document style.
l Renamed the DATHiLimitSetpoint and
DATLowLimitSetpoint fields to DATHiLimitSetpointDiff
and DATLowLimitSetpointDiff respectively. Deleted
DATHiLimitPropBand field mentions.
l Added CO2 occupancy control in the Occupancy mode
section of Sequence of Operations.
Added time-proportional heating and cooling sequence of

operations. Revised the discharge air temperature sequence of
operations.
Corrected the image of eZNS mylar 047.

Edition 2.6

Ezfc 424 R 424

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Ezfc 424 R 424

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ezfc 424 R 424

Uploaded by

Copyright:

Available Formats

eZFC-424R4-24

About the eZFC-424R4-24 8

About This Guide 8

Upgrading From 1.x to 2.2 8

Upgrading From 2.x to 2.2 9

Object Restriction Settings (ORS) 9

Connecting to the Controller 9

Setting the MS/TP Address 9

BACnet Device Addressing 10

About the enteliZONE ORCAview Configuration Graphic 11

Downloading the ORCAview Configuration Graphic 11

Installing the ORCAview Configuration Graphic 11

Opening the ORCAview Configuration Graphic 11

Working with the ORCAview Configuration Graphic 12

Selecting Between Multiple Controllers 12

Save to Flash, Save to PC and Load from PC 13

Configurable and Programmable enteliZONE Controllers 14

Differences Between Configurable and Programmable enteliZONE Controllers 14

eZFC-424R4-24 Application Guide Page 1 of 84

enOcean Integration (firmware 2.2 and higher) 18

Fan Coil Programmable Objects 19

Fan Coil and Heat Pump Programmable Objects 19

Relationship Between Algorithm Unit Modules 20

What is the General Tab? 22

Local Inputs Tab 26

Setting Up a Hardwired Temperature Sensor 26

Set Up a Hardwired Temperature Sensor 26

Setting Up a Hardwired Occupancy Input 27

Set Up a Hardwired Occupancy Input 27

Setting Up a Hardwired CO2 Sensor 29

Setting Up a Fan Speed Switch 30

Setting Up a Fan Coil 2-Pipe Changeover Sensor 30

Setting Up a Condensate Level Switch 31

Setting Up Other Supporting Inputs 31

Page 2 of 84 eZFC-424R4-24 Application Guide

Setting Up Damper Feedback 32

Local Outputs Tab 33

Setting Up a Fan Coil or Heat Pump Output 33

Set up a Fan Coil Output 33

Setting Up a Fan Output 35

Set Up a Fan Output 35

Setting Up Other Outputs 37

Setting Up a Damper Output 38

Set Up a Damper Output 38

LINKnet I/O Tab 39

Configuring an eZNS-T100 Network Sensor 39

Set Up the Temperature Sensor 39

Set Up the Humidity Sensor 40

Set Up the CO2 Sensor 40

Set Up the Occupancy Sensor 40

Assign Functions to the Buttons and Slider 41

Set Up the LCD Display 41

Assigning Buttons and Slider Elements on eZNS-T100 Network Sensor 42

Set Up the Buttons and Slider Elements 44

Configuring DNS-24L Network Sensor 47

Set Up the Temperature Sensor 47

eZFC-424R4-24 Application Guide Page 3 of 84