Delta Controls DNS-24, DNT-T103, DNT-T221 Application Manual
Annons
Annons
A
PPLICATION
G
UIDE
Delta Network Thermostat: BACstat II
DNT-T103 & DNT-T221
Document Edition 4.1
Product Description
The DNT-T103 and the DNT-T221 are intelligent room thermostats with custom 3-value, 96 segment, LCD displays. The DNT products can communicate directly on a BACnet MS/TP network or Delta’s proprietary
LINKnet network.
They are capable of displaying a wide-range of digital or analog values, including setpoints, temperature, air flow, heating and cooling status, fan speed, valve and damper position, and more. When connected on a BACnet
MS/TP network the DNT-T103 and T221 function as independent BACnet thermostats. When connected to a Controller on a LINKnet network they provide programmable remote sensor and expanded I/O capabilities. This version’s firmware can be flash loaded over the network, and have termination resistors that are jumper selectable.
The DNT-T103 has 1 extra input, 3 binary outputs and a number of built-in application control strategies. The
DNT-T221 has 2 extra inputs, 2 analog and 1 binary output and built-in application control strategies. As a result, these BACstats are capable of stand-alone control when directly connected on an MS/TP network.
Contents
OTHER RELEVANT DOCUMENTS .................................................................................................. 2
IMPORTANT INFORMATION .......................................................................................................... 2
SETUP & CONFIGURATION ............................................................................................................. 2
N ETWORK C OMMUNICATIONS ........................................................................................................... 2
D EVICE C ONFIGURATION (K EYPAD ) .................................................................................................. 2
S ERVICE T OOL M ODE (K EYPAD ) ....................................................................................................... 7
I NPUT C ALIBRATION .......................................................................................................................... 8
I NPUT S CALE R ANGES ...................................................................................................................... 8
SOFTWARE & PROGRAMMING...................................................................................................... 9
O BJECTS ............................................................................................................................................ 9
P
ROGRAMMING
............................................................................................................................... 12
CONTROL FUNCTIONS ................................................................................................................... 12
O
VERVIEW
...................................................................................................................................... 12
S OFTWARE L OOP C ONTROLLER
S ETPOINTS ...................................................................................................................................... 18
C ONTROL D IAGRAM ........................................................................................................................ 19
C ONTROL A PPLICATIONS (M UX , VAV, VVT, HPU, FCU, R AD , H UM ) ............................................ 20
O UTP UT F UNCTIONS & T YPES ......................................................................................................... 28
OWS FUNCTIONS .............................................................................................................................. 33
A PPENDIX A: P ROGRAMMING N OTES .................................................................................................... 31
A PPENDIX B: LINK NET ......................................................................................................................... 32
Document Edition 4.1
Page 1 of 41
DNT-T103 & DNT-T221 Application Guide
Other Relevant Documents
•
Associated BACstat II Installation Guide (DNT-T103 or DNT-221)
•
•
Delta Controls Wiring and Installation Guidelines
ORCAview Operator Guide
•
ORCAview Technical Reference Manual
•
Release Notes for relevant firmware and BACstat products
Important Information
This document has been updated to include features and capabilities of Release 4 firmware and hardware for the BACstat II DNT-T103 and the DNT-T221 products. Although BACstat firmware is independent from ORCAview, DCU, and Application Controllers, certain BACstat capabilities require support in the other products. The firmware for the DNT-T103 and the DNT-T221 can be flash loaded over the network.
1.
V3.22
F IRMWARE & S OFTWARE OR H IGHER
When BACstats are used with ORCAview, DCU, and Application Controllers loaded with V3.22 firmware/software please be aware of the following issues.
For an MS/TP Network Connection:
•
A DSC is required
•
Local BACstat display handling and control strategies may be enabled
• Data exchange may be done in GCL+ programming in any DCU or Application Controller on the MS/TP network
Setup & Configuration
NETWORK COMMUNICATIONS
On an MS/TP network BACstats communicate at a default speed of 76,800 bps. Refer to the
Technical Reference Manual for further detail on configuring the MS/TP network or changing baud rates. Also refer to the associated BACstat II Installation Guide for network installation details.
Flash Programming
The BACstat II Release 4 product now offers flash loadable firmware across its network connection. It is supported by Flashloader V3.33, and operates the same way as other Delta controllers. Please ensure that all the databases have been backed up prior to upgrading the flash firmware. Refer to the Flashloader V3.33 User's Guide for further details on using the
Flashloader to upgrade the firmware on the BACstat II Release 4 product.
DEVICE CONFIGURATION (KEYPAD)
To use ORCAview OWS to configure BACstats refer to OWS Functions on page 33.
1.
C ONFIGURATION M ENU U SER A CCESS
Access to the Configuration Menu is protected by an access code or PIN. You must enter the valid PIN before access is granted, which works as follows:
•
First press the Up Arrow (
▲), and then press the Down Arrow (▼) while still pressing the Up
Arrow, and hold them both down for at least 5 seconds.
Page 2 of 41 Document Edition 4.1
Delta Controls
•
When the
text is displayed you are being prompted for the valid PIN or access code, a preconfigured
4-digit code, which you must enter before you can gain access to the Configuration Menu. The buttons on the left side of the BACstat have a value of 0, while the buttons on the right side have a value of 1. Press the proper button sequence to match the password.
•
The default PIN is 1011 . The PIN access code, contained in AV31, can be changed through the
OWS when the BACstat is connected to an MS/TP network.
•
Once you have entered the valid 4-digit code you will gain access to the Configuration Menu, and
will be displayed immediately to indicate you are now in Configuration mode. If you haven’t entered a valid code (or if you do not press a button within about 10 seconds), the process will be aborted and you will be returned to normal display mode.
•
If at any time after you have gained access to the Configuration Menu you do not press a button for
2 minutes, the BACstat will exit the Configuration Menu and return to normal display mode.
2.
B UTTON & N AVIGATION F UNCTIONS
The Button functions are as follows within the Configuration Menu:
Button
Top Left
Top Right
Bottom Left
(Down:
▼)
Bottom Right
(Up:
▲)
Description
•
Represents a value of 0 when entering the PIN access code.
•
P REVIOUS : Enter the current setting (and go backward in the menu).
•
Represents a value of 1 when entering the PIN access code.
•
N EXT : Enter the current setting (and go forward to the next item in the menu).
•
Represents a value of 0 when entering the PIN access code.
•
Rotates downward through menu items and options.
•
Decreases a numeric value with each button press.
•
Represents a value of 1 when entering the PIN access code.
•
Rotates upward through menu items and options.
•
Increases a numeric value with each button press.
Use the N EXT and P REVIOUS buttons to navigate through the menu options. Once you have navigated to the desired item you wish to display or change, use the arrow buttons to make any necessary changes.
Once the changes are made or you wish to move on, press N EXT or P REVIOUS .
Document Edition 4.1
Page 3 of 41
DNT-T103 & DNT-T221 Application Guide
3.
C ONFIGURATION M ENU O PTIONS
The Configuration Menu is a list of items that you can navigate through to make changes for setup purposes. The Configuration Menu items are as follows:
Menu Item
[ Application ]
Description
Displayed momentarily to indicate you have successfully entered the Configuration
Menu.
The Control Application (AV12). You may choose from any of the following applications:
•
This disables all control strategies and allows the outputs and control icons to be controlled remotely from another device.
• This enables the VAV control strategy and allows you to configure the outputs for your VAV application.
•
This enables the VVT control strategy and allows you to configure the outputs for your VVT application.
•
This enables the HPU control strategy and allows you to configure the outputs for your Heat Pump Unit application.
•
This enables the FCU control strategy and allows you to configure the outputs for your Fan Coil Unit application.
• This is no longer an option. Configure control for a Unit Heater using the FCU application.
•
This enables the Radiation control strategy and allows you to configure the outputs for your Radiant Heating application.
• This enables the Humidity control strategy and allows you to configure the outputs for your Humidity application.
Available when the Application = VAV. The air flow units setting (CFM or LPS)
[ More ]
Output 1 Configuration. This includes the output function and type (what it will control and how) and other setup parameters as required (such as delays or limits).
Output 2 Configuration. This includes the output function and type (what it will control and how) and other setup parameters as required (such as delays or limits).
Output 3 Configuration. This includes the output function and type (what it will control and how) and other setup parameters as required (such as delays or limits).
Additional parameters to set, which are dependent on the Application and Output
Configuration, may include:
•
Actuator Runtime in seconds (AV24)
•
Air Flow Factor for VAV only (AV25)
•
•
Minimum Air Flow for VAV and Damper Minimum for VVT (AV26)
Maximum Air Flow for VAV and Damper Maximum for VVT (AV27)
The Temperature Units Setting (degrees C or F).
[ Settings ] Additional control settings, which are particularly useful when an Application is selected for local control, typically include:
•
Day Setpoint (AV6)
•
Max. Day Setpoint (AV8)
• Day Differential (AV9)
• CO Proportional Band (AV19)
•
Min. Day Setpoint (AV7)
•
CO Reset Rate (AV20)
Page 4 of 41 Document Edition 4.1
Delta Controls
Menu Item
Description
The LCD Display Code Setting (AV15), a 4-digit value (ABCD) configures local display and button handling as follows:
A Line 1 (Top Left – i.e., Outside Value): 1 to 4
B
C
D
1 - Disabled
2 - Value from AV5 (i.e., remote value such as OAT)
3 - Value from AI2 (i.e., external sensor)
4 - Value from AI3 (i.e., Humidity)
Line 2 (Center – i.e., Inside Value): 1 to 4
1 - Disabled
2 - Temperature from AI1
3 - Humidity from AI3
4 - Alternates between Temperature (AI1) & Humidity (AI3)
5 - Value from AI2 (i.e., external sensor)
6 - Value from AV5 (i.e., remote value
7 - Setpoint
8 - Setpoint with adjust
9 - User Setpoint with adjust (-3 to +3 degrees)
Line 3 (Bottom – i.e., Setpoint Value): 1 to 5
1 - Disabled
2 - No Setpoint until an arrow button is pressed (adjustable)
3 - Setpoint is always displayed (adjustable)
4 - No Setpoint until an arrow button is pressed (not adjustable)
5 - Setpoint is always displayed (not adjustable)
6 - Temperature from AI1
7 - Value from AI2
8 - Humidity from AI3
9 - Value from AV5
House & Day/Night Mode Icons: 1 to 9
H OUSE O UTLINE O N /O FF T EXT M AN
1 No No No
S UN /M OON
No
2
3
4
5
6
No
No
No
Yes
Yes
Flash
Yes
No
No
Yes
No
No
No
No
No
No
No
Yes
No
No
7
8
Yes
Yes
Yes
No
Yes
Yes
No
No
9 Yes No No Yes
N OTE : When connected to MS/TP, the Display Code may be set to any valid value – making it unnecessary to write GCL+ programs for display and button handling.
Whenever an application is selected, a matching default Display Code is also set automatically (typically 1237), but this can be set to something else if so desired.
Document Edition 4.1
Page 5 of 41
DNT-T103 & DNT-T221 Application Guide
Menu Item
Menu Item
Description
The Service Tool Mode access setting (AV32) has the following options:
0 Disables all access to Service Tool Mode
1 Provides limited access for VAV, or full access for other applications
2 Provides full access with advanced Air Balancer functions for VAV
Time Clock feature allows the ability for a signal from an external source to directly control Alg Mode (AV13) via IP2. This feature is only available in non-VAV algorithms. The Time Clock is enabled by setting the units of AI2 to “Day” or by selecting for the option in the configuration menu.
IP2
Short
Alg Mode
0
Occupancy
Unoccupied
Open 1 Occupied
This feature works on edge changes and not constantly held. This means if a signal changes Alg Mode to 0, a new value can be overwritten from key presses or direct writes to Alg Mode (AV13).
The LINKnet Communications Setting (O N or O FF ), to match the connection method. The should be set to O FF when connecting to MS/TP. For use with
LINKnet, see Appendix B : LINKnet.
The DNA Setting (O N or O FF ), for inheriting a derived address from system level devices above the BACstat on the MS/TP network. This option is not available when
LINKnet is On.
Description
The device Address (1 to 99), which is used internally as the MAC Address. As the
BACstat can only be a Subnet device on MS/TP, this address is always mapped in as the Subnet value. On MS/TP the complete BACnet address is in the form of
“OEM_Area_System_Subnet”
These options are only available when DNA and LINKnet are Off. When DNA is
On, these options are automatically inherited from the system level device above the
BACstat.
The System number (0 to 99) can only be set manually when on MS/TP and DNA is turned O FF .
The Area number (0 to 99) can only be set manually when on MS/TP and DNA is turned O FF .
The OEM number (0 to 3) can only be set manually when on MS/TP and DNA is turned O FF .
The Network Speed (9.6 KB, 19.2 KB, 38.4 KB, or 76.8 KB). The default for
MS/TP is 76.8 KB.
The clear database feature (Yes or NO) resets the configuration settings to the default (refer to page 9).
Note
: The following are not cleared: Baud Rate, Device Address, DNA/LINKnet,
MaxMaster and Max Info Frame.
To exit the Configuration Menu (Yes or No). If you do not press a button within 1 minute the device will automatically exit and return to its normal display mode.
Page 6 of 41 Document Edition 4.1
Delta Controls
N OTE : AI2 (and AI3 for the DNT-T221) are not configured through the Configuration
Menu. These objects must be configured through the OWS (i.e., for Scale/Units) – except
when AI2 is used for VAV airflow. Refer to OWS Functions on page 33
for more information.
SERVICE TOOL MODE (KEYPAD)
A new BACstat II Quick Reference Card for Service Tool Mode (product number REF-817) is available for quick and easy reference, and for navigation of the Service Tool features. One is shipped with the product, and additional copies can be ordered as necessary.
1.
S ERVICE T OOL M ODE U SER A CCESS & N AVIGATION
Access to Service Tool Mode and its associated menu options is not protected by an access code or PIN.
However, user access must be enabled (via AV32 or the setting located in the Configuration Menu) and the valid key sequence must be entered.
•
To enter Service Tool mode, first press the Down Arrow (
▼) and then the Up Arrow (▲), and hold them both down for at least 5 seconds (which is the opposite sequence to the Configuration menu).
There is no PIN or password.
•
Once you have entered the valid user key sequence you will gain access to Service Tool Mode, and
SEr will be displayed immediately along with a main menu of several options.
•
You may now use the up and down arrow buttons to navigate through the main menu options, and the N EXT or P REVIOUS buttons to navigate the submenus and their associated options.
•
Once you have navigated to the desired item you wish to display or change, use the arrow buttons to make any necessary changes. Once the changes are made or you wish to move on, press N EXT or
P REVIOUS .
•
If at any time you do not press a button for 30 minutes, the BACstat will exit Service Tool Mode and return to normal display mode. Any outputs commanded manually will remain in manual, and a
VAV box commanded to various Air Balancer modes (Minimum, Maximum, Close, Open, Zero
Calibration) will also remain as commanded. A subsequent user command ( CtL ) is required to put the BACstat and associated outputs back under control (or Auto).
2.
S ERVICE T OOL M ENU O PTIONS
Service Tool Mode contains two menus: the Main menu and an Air Balancer menu (which is only available when the application is configured for VAV).
Air Balancer Menu Options
Menu
Item
Description
Displayed on line 2 of the LCD (center screen) to indicate you are at the Main menu of the
Service Tool Mode.
[ Option ] Service Tool Mode has these following main menu options, which you rotate through using the arrow keys. Press the N EXT or P REVIOUS buttons to select the option and navigate the submenus.
•
To calibrate Inputs AI1 to AI3 as compared to an external measuring device.
Navigate past the inputs you don’t wish or need to calibrate.
• To manually command AV1 to AV3 (0-100% for tri-state or PWM, and O FF or
O N for binary outputs), associated with OP1 to OP3 respectively. This allows for end-to-end commissioning of output devices. Navigate past the outputs you
Document Edition 4.1
Page 7 of 41
DNT-T103 & DNT-T221 Application Guide
Air Balancer Menu Options
Menu
Item
Description do not need to command. [When outputs are defined as tri-state in the
Configuration menu, modifications can only be made to the primary output – the other output cannot be modified.]
•
To enter Air Balancing mode, which is only an option when VAV is selected as the Application in the Configuration Menu.
•
To exit Service Tool mode (Yes or No). At any time within the Service Tool menus, if you do not press a button within 30 minutes the device will automatically revert to its normal display mode (but retains manually commanded outputs and stays in any forced VAV box mode: MIN, MAX,
CLOSED, OPEN).
Displayed on line 1 of the LCD (top left) to indicate you are in the Air Balancer Mode.
[ Option ] Air Balancer Mode has these following menu options, which you rotate through using the arrow keys. Press the N EXT or P REVIOUS buttons to select the option and navigate the submenus.
•
Displays the current Air Flow, use the arrow keys to navigate the submenus and view the internal Air Flow Setpoint and the Air Flow Factor (with possible adjustment).
•
Displays the current Minimum Air Flow setting, use the arrow keys to navigate the submenus to adjust the value and force the box to the minimum value.
•
Displays the current Maximum Air Flow setting, use the arrow keys to navigate the submenus to adjust the value, force the box to the maximum value, and calibrate the display value to match a measured value.
•
Use the arrow keys to navigate the submenus and select options to force the box fully closed, and then auto-calibrate for zero flow.
• Use the arrow keys to navigate the submenus and select options to force the box fully open.
•
Use the arrow keys to navigate the submenus and select options that put the box back under control (releasing the box from forced modes: MIN, MAX,
CLOSED, OPEN, or ZERO Calibrate).
•
To exit Service Tool mode (Yes or No). At any time within the Service Tool menus, if you do not press a button within 30 minutes the device will automatically revert to its normal temperature display mode (but retains manually commanded outputs and stays in any forced VAV box mode: MIN,
MAX, CLOSED, OPEN, or ZERO Calibrate).
INPUT CALIBRATION
MS/TP CONNECTION
The inputs are typically calibrated in their associated local AI objects. These same calibration fields are also mapped to variables (AV16 to 18) to allow other vendors in a multi-vendor installation to calibrate the inputs. The inputs may also be calibrated right at the BACstat using the Service Tool Menu.
Page 8 of 41 Document Edition 4.1
Delta Controls
INPUT SCALE RANGES
Local Input Scale Ranges are selected by setting the units, from the following available options.
Input Valid Units Scale Description
1 C / F Standard 10K Thermistor (in ºC or ºF)
2 C / F Standard 10K Thermistor (in ºC or ºF)
3
% 0-5 or 0-10v input signal (depending on jumper) converted to a 0-100% value
CFM / LPS Air Flow (in CFM or LPS) using a 0-1”
DP Sensor (Kavlico or Setra)
C / F Standard 10K Thermistor (in ºC or ºF)
%
%RH
0-5 or 0-10v input signal (depending on jumper) converted to a 0-100% value
Built-in Custom Humidity Sensor
(optional)
Application Notes
Only available options for AI1.
Available whenever the VAV application is not enabled.
Available whenever the VAV application is not enabled.
Fixed whenever the VAV application is enabled.
Available whenever the HUM application is not enabled.
Available whenever the HUM application is not enabled.
Fixed whenever the HUM application is enabled.
Unless inputs are multiplexed, many of the input units and associated scale ranges are automatically set when a built-in application is selected. Also refer to page 34 for configuring AI2 and AI3.
MS/TP CONNECTION
Only those units and associated scale ranges resident locally in the BACstat may be used.
Software & Programming
OBJECTS
The following is a list of predefined objects that reside in the BACstat II products that cannot be created or deleted. When connected to an MS/TP network, these objects are readily accessible over the network.
Object Name Description
DEV<address> BACstat<address> * Device Object
AI1 Temperature Input 1 (10K Thermistor Value)
AI2
AI3
Input 2 *
Humidity
Input 2 (Available Input)
Input 3 (Humidity on DNT-H103 DNT-H121)
AV1
AV2
AV3
AV4
AV5
Input 3 *
Output 1 *
Output 2 *
Output 3 *
KeyPress
External *
Input 3 (Extra Input on DNT-T103 DNT-T221)
Output 1 (0 – 100%, Name Changes)
Output 2 (0 – 100%, Name Changes)
Output 3 (0 – 100%, Name Changes)
KeyPress Value
External Object Value (i.e., OAT)
Used for User Setpoint Adjust when display code
‘B’ is set to 9
AV6
AV7
AV8
AV9
AV10
Day Setpoint
Day Minimum
Day Maximum
Day Differential
Night Heat Setpoint
Room Setpoint
Minimum Adjustable Day Setpoint
Maximum Adjustable Day Setpoint
Room Setpoint Differential
Night Setpoint for Heating (or Humidity)
Default Value
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
ºC = 21; ºF = 71; % = 30
ºC = 18; ºF = 65; % = 20
ºC = 25; ºF = 77; % = 55
ºC = ±0.5; ºF = ±1, % = ±2.5
ºC = 16; ºF = 60; % = 30
Document Edition 4.1
Page 9 of 41
DNT-T103 & DNT-T221 Application Guide
AV11
AV12
AV13
AV14
AV15
AV16
AV17
AV18
AV19
AV20
AV21
AV22
AV23
AV24
AV25
AV26
AV27
AV28
AV29
AV30
AV31
AV32
AV33
AV34
AV35
Night Cool Setpoint
Application
Alg Mode
Controller Status
Display Code
AI1 Calibration
AI2 Calibration
AI3 Calibration
Proportional Band
Reset Rate
Output 1 Config
Output 2 Config
Output 3 Config
Setup 1
Setup 2
Setup 3
Setup 4
Setup 5
Setup 6
Baud Rate
PIN
Service Tool Mode
Box Mode
System Stats
System Log
Night Setpoint for Cooling
Control Application (Name Changes)
Algorithm Mode
Status of Internal Control Loop
Local Display & Button Handling
Input 1 Calibration (Temperature)
Input 2 Calibration (MUXed IP)
Input 3 Calibration (Humidity)
Control Loop Tuning Parameter
Control Loop Tuning Parameter
Output 1 Configuration Variable
Output 2 Configuration Variable
Output 3 Configuration Variable
Setup Variable 1 (Name Changes)
Setup Variable 2 (Name Changes)
Setup Variable 3 (Name Changes)
Setup Variable 4 (Name Changes)
Setup Variable 5 (Name Changes)
Setup Variable 6 (Name Changes)
Network Baud Rate
PIN (4-Bit Configuration Access Code)
Service Tool Access Disable/Enable (0-2)
Heating & Cooling Modes for VAV/VVT
System Statistics
System Event Log
* Names are user settable (to a maximum of 32 characters), and only on outputs when they are controlled remotely (i.e.,
MUXed).
These are the typical objects that may be commanded on the fly by a user or from GCL++, and also include the Outputs
(AV1-3) when they are MUXed. Never command the Configuration Variables (AV12, AV21-13) on the fly.
ºC = 30; ºF = 86; % = 30
None
0 (O FF or Night)
N/A
1237
0.0
0.0
0.0
ºC = 1; ºF = 2; % = 10
1.0
As per Application Setup
As per Application Setup
As per Application Setup
As required
As required
As required
As required
As required
As required
*
1011
1 (or 2 when AV12 = VAV)
0 (Cooling)
N/A
N/A
System Events and Statistics
H04
H05
H06
H08
C01
C02
C03
C04
C05
System Stats (AV34)
The Description field in this object provides a count of notable events that have occurred. Each statistic consists of an event code (H- Hardware, C- Communication, S-Service + two-digit code) and an event count. With the exception of the reset count (H04) and the flash programming count (H05), event counts are reset on power up. The PresentValue indicates how many different types of events have occurred since power up.
Code Description
Reset count
Flash programming count
Flash operation failure
I2C communication failure
Communication overflow
Buffer unavailable
Into Sole Master
DNA conflict
MAC address conflict
Page 10 of 41 Document Edition 4.1
Delta Controls
C06
C07
C08
C09
C10
C11
C12
C13
C14
S03
Receive overrun
CRC error
MSTP pass token timeout
Out of Sole Master
Invalid state
Invalid frame
Minimum Token cycle time (ms)
Maximum Token cycle time (ms)
Average Token cycle time (ms)
COV subscription failure
System Log (AV35)
The Description field in this object provides a log of the ten most recent events from the least to the most recent. If the time and date were previously set then the event time can also be determined. Each log entry has the format [dd/mm/yy hh:mm:ss ***] where *** is the event code. Each event type is specified by a letter, (H- Hardware, C- Communication, S-Service or O-Other) which is followed by a two-digit code. For example, 02/05/06 10:12:47 S04. The PresentValue indicates how many items are in the log.
Code Description
C02
C03
C04
C05
S01
S02
S03
H01
H02
H03
H04
H05
H06
H07
H08
H09
C01
S04
S05
S06
R00-07
R10-15
R21
R22
R23
O00
EEPROM communication failure
RTC communication failure
LCD communication failure
Reset
Flash programming
Flash failure
Input failure
I2C communication failure
Humidity sensor failure
Communication overflow
Buffer unavailable
Into Sole Master
DNA conflict
MAC address conflict
Communication disabled
Communication enabled
COV subscription failure
TimeSync received
Database cleared
Speed Changed
MS/TP state machine lockup
MS/TP timeout lockup
BACnet application processing error
Object execution error
UI manager error
Other
Document Edition 4.1
Page 11 of 41
DNT-T103 & DNT-T221 Application Guide
PROGRAMMING
MS/TP CONNECTION
Objects
All of the existing predefined BACstat II objects are readily accessible over the MS/TP network.
Control Applications
BACstats with I/O may be configured to run one of six possible built-in control applications.
Another option disables local control altogether.
GCL+ Programming
BACstats are not programmable devices – GCL+ does not reside in a BACstat. Rather, when connected to an MS/TP network you configure a BACstat for local operation and write GCL+ located elsewhere as necessary to do additional functions. In this way you configure the BACstat for local operation (both display & button handling and local control) and then write any necessary
GCL+ in another controller for additional strategies.
For example: Through the Configuration Menu, you typically configure the BACstat II display and buttons to functional locally, so GCL+ programs are not necessary for handling the display value or adjusting setpoint (i.e., AV15 = 1237). You may also select a suitable control application for local control. Then, using GCL+ programming located in another controller (i.e., DCU or other System
Device) you make mode and setpoint changes based on Time-of-Day or other conditions.
W ITH V3.21
F IRMWARE : All GCL+ programming for mode changes (DCU, DSC or DAC), data exchange, and other strategies must be written in the DCU.
W ITH V3.22
F IRMWARE OR H IGHER : GCL+ programming for mode changes, or other strategies may be written in any appropriate controller on the network.
Refer to the Programming Notes in Appendix A of this document, and also the appropriate
Appendix within the ORCAview Technical Reference Manual for further programming information.
Control Functions
OVERVIEW
1.
C ONTROL A PPLICATIONS
When connected to an MS/TP network, the BACstat may configured to operate according to one of 7 possible application control strategies, and displayed in the Application variable (AV12).
Application
None (MUX)*
VAV
VVT
HPU
FCU
Unit Heater
Radiation/Reheat
Humidity
Description
Provides remote control of the outputs from another device.
Provides control of a simple VAV box and optional fan.
Provides control of a simple VVT box and optional fan.
Provides control of a Heat Pump Unit with a reversing valve and a fan.
Provides control of a Fan Coil Unit with heating/cooling and a fan.
No longer supported. Use FCU instead.
Provides control of single or multi-stage heating with no fan.
Provides control of a Humidifier and assumes a model of the BACstat with a humidity sensor. (DNT-H103B and DNT-H121B)
3
4
5
6
AV12
0
1
2
Page 12 of 41 Document Edition 4.1
Delta Controls
Refer to the Application section of this guide for further detail on each of these control strategies, on page 20.
*Although possible, this is not recommended because it can cause excessive network traffic.
2.
A LGORITHM M ODE
The application control strategy operates in one of the following basic modes, as determined by the
Algorithm Mode variable (AV13).
Algorithm Mode
Unoccupied (Night)
Occupied (Day)
Minimum
Description
Uses Night Setpoints
Uses Day Setpoints
VAV Only: Forces the box to its minimum position
Maximum
Closed
Open
Zero Calibration
VAV Only: Forces the box to its maximum position
VAV Only: Forces the box to its fully closed position
VAV Only: Forces the box to its fully open position
VAV Only: Forces calibration of the bias so the airflow reads zero at current conditions. This assumes that the Air Handler has been shut down and that there is no air flow at the box.
Heating Lockout
Cooling Lockout
All heating control and associated icons are completely disabled
(as though no heating stages even exist)
All cooling control and associated icons are completely disabled
(as though no cooling stages even exist)
Heating/Cooling Lockout Both heating and cooling control and their icons are disabled
11
12
13
14
AV13
0
1
10
20
21
22
Unless the fourth digit of the Display Code (AV15) is set to 1 or 5, or Fan Control is configured as
Manual, the top two buttons on the BACstat – O FF ( O ) and O N ( I ) – will switch between Night and Day modes. Changing to the other modes for VAV is keypad accessible in Air Balancer mode within the
Service Tool menus. The Alg. Mode (AV13) is also fully accessible from another device over the network (via GCL+ or ORCAview OWS or 3 rd
Party devices), to command it to any mode as required
(including the lockouts).
Lockout Modes
Heating and cooling lockout modes are operational for all Control Applications.
Basically, once a BACstat has been configured for various stages of heating and cooling, either the heating and/or cooling may be disabled on the fly as necessary for various control strategies simply by commanding the Alg. Mode (AV13). In all other regards, control continues to function the same as it would when in Occupied mode.
Communications Reset Enable
The Alg mode (AV13) variable also has a property represented by a Comm Reset Enable checkbox in the object dialog. This can be enabled or disabled, depending on installation requirements.
Disabled
•
The BACstat does not try a reset if
Enabled
•
(the default as of Release 3 Firmware)
The BACstat will reset once if
Document Edition 4.1
Page 13 of 41
DNT-T103 & DNT-T221 Application Guide communication is lost.
•
If the device resets, the mode reverts to whatever it was just prior to the reset (i.e., last value as stored in non-volatile memory) communication is lost, to try and re-establish communication
•
Should the device reset, the mode is set to
DAY
Page 14 of 41 Document Edition 4.1
Delta Controls
3.
B OX M ODE (DNT-T103 AND DNT-T221 O NLY )
When the application control strategy is configured for VAV or VVT, the Box Mode (variable AV33) can be set to either cooling (default) or heating. When set to cooling, the air supply is treated as the first stage of cooling. When set to heating, the cooling controller is inverted and the air supply is treated as the first stage of heating.
Box Mode
Cooling
Heating
Description
Duct Supply Air to the box provides cooling (default)
Duct Supply Air to the box provides heating
AV33
0
1
This variable cannot be commanded or changed from the BACstat. As this function is completely dependent on the air supplied to the boxes from another source, this variable would normally be commanded over the network (i.e., typically via GCL+) whenever the air system changes between heating and cooling.
N OTE : As of Release 3, VAV and VVT applications can no longer be configured with more than 1 stage of cooling. In earlier releases of firmware, do not configure a BACstat with more than 1 stage of cooling, as additional stages of cooling don’t work properly when Box Mode is ever set to heating.
Software Controller Loop
1.
G ENERAL
The operation of the BACstat II is centered around a software controller. The controller uses the following parameters in its operation.
Parameter
Room Temperature
Temperature Setpoint*
Object
AI1
Proportional Band
Reset Rate
Default Value
N/A
Notes
Input 1 **
O CCUPIED : Uses Day Setpoint (AV6)
U NOCCUPIED : Uses Night Heat Setpoint
(AV10) if the Input is below the Night Heat
Setpoint (AV6); and uses the Night Cool
Setpoint (AV11) if the Input is above the Night
Cool Setpoint (AV6); otherwise it is in a null zone.
AV19 2.0 ºF / 1.0 ºC Degrees F or C as configured for AI1
AV20 1.0 Resets per hour
Day Differential AV9 1.0 ºF / 0.5 ºC Degrees F or C as configured for AI1
* Humidity Setpoint if operating as a Humidity controller ** Input 3 (AI3) if operating as a
Humidity controller
Document Edition 4.1
Page 15 of 41
DNT-T103 & DNT-T221 Application Guide
2.
C ONTROLLER O PERATION
100%
NORMAL CONTROLLER ACTION
-100%
Controller
Output
(Heating)
Day
Differential
Controller
Output
(Cooling)
Deadband
Heating Cooling
0%
Proportional Band
Temperature
Proportional Band
Heating
Setpoint
Cooling
Setpoint
Day Setpoint
Deadband is a span of 0.2 around setpoint (heating or cooling) over which neither heating nor cooling takes place.
Here are a few rules and restrictions to how the internal Loop Controller functions:
•
Heating and Cooling will not be O N at the same time
•
If the Input temperature is less than ( Day Setpoint – ( Day Differential + ½ Deadband )) then the controller is in H EATING
•
If the Input temperature is greater than ( Day Setpoint + ( Day Differential + ½ Deadband )) then the controller is in C OOLING
•
If the Input temperature is between these two extents for Heating and Cooling, then the controller is in A null zone
For all control applications (except when Box Mode is heating in VAV or VVT) the Controller Status
(AV14) will modulate from -100 to 100% and sequence any necessary output stages. A value of 0 to
100% represents heating output from the controller, while a value of 0 to -100% represents cooling output from the controller.
0%
Page 16 of 41 Document Edition 4.1
Delta Controls
200%
WITH BOX MODE = HEATING
Day
Differential
Auxilary
Heating
100%
Flow
Damper
Controller
Output Deadband
0%
Proportional Band
Temperature
Proportional Band
Heating
Setpoint
Day Setpoint
Cooling
Setpoint
For VAV or VVT applications, when the Box Mode is changed to heating, cooling is inverted and used for controlling the flow damper as the first stage of heating, and the null zone is placed on the far right.
Moving from right to left, away from setpoint, the Controller Status (AV14) will modulate from 0 to
200% and sequence all the necessary heating stages. The flow damper modulates open over the first 0 to
100% and in so doing provides the first stage of heating. Any additional stages of heating modulate open over 100 to 200%. Therefore, only when the Box Mode is in heating does the Controller Status
(AV14) modulate to a value greater than 100%, where 200% indicates all heating is fully open.
For heating lockout (in all applications), the heating output from the controller is forced to 0%, and the heating icon is disabled on the LCD. Similarly, for cooling lockout, the cooling output from the controller is forced to 0%, and the cooling icon is disabled on the LCD. As a result, the Controller
Status (AV14) will be limited accordingly.
3.
C ONTROLLER S TAGING
Each controller can be split up into as many as three stages. The number of stages is automatically determined by the output configuration associated with the selected application control strategy. The controller stages are cascaded.
100%
0%
100%
0%
C1 C2
Cooling
Controller
C3
Document Edition 4.1
Page 17 of 41
DNT-T103 & DNT-T221 Application Guide
4.
R ESET A CTION (R ESET R ATE IN REPEA TS PER HOUR )
If the Reset Rate is non-zero, reset action is enabled. As long as there is a difference (or error) between the input value (i.e., space temperature) and setpoint value, reset action will increment or decrement the
Controller Status value (AV14) over time - in proportion to the value of the reset rate and the magnitude of the error - in an attempt to remove the error. In this way, the Controller Status value is continually fluctuating in order to reach setpoint.
The amount of reset does not decrease internally as the input value approaches setpoint, but the reset value is frozen while in deadband. The only time reset action has no affect on the controller output is when the input is equal to the setpoint (no error). For this reason, be cautious about applying too much reset action, otherwise you may cause unnecessary movement on actuators. By setting Reset Rate to 0, you disable reset action altogether.
SETPOINTS
The BACstat II uses a series of setpoints for various purposes, most of which interact with one another. For a complete list of these setpoints and other objects and their defaults, refer to the
Object table on page 9. When you change the units setting between ºC and ºF all of these setpoints revert back to their matching default values – the BACstat does not do a conversion on the fly. What follows hereafter is a working description for each of these setpoints. If the particular setpoint is settable in the Configuration Menu it is indicated with its LCD text.
Day Setpoint (AV6) –
This is the setpoint used when in D AY mode. With the Display Code (AV15) set to an appropriate value the setpoint can be adjusted up or down by pressing the buttons. Whether or not this setpoint is displayed or is adjustable on the LCD, it is used internally for control. The units for the setpoint are ºC or ºF (as per AI1) unless the second digit of the Display Code (AV15) is set to 3
(for Humidity), in which case the units become %RH. The value for Day Setpoint can also be set in the Configuration Menu, or by commanding the variable (via GCL+ or ORCAview OWS or 3 rd
Party devices).
Day Minimum Setpoint (AV7) –
This is the minimum value a user can adjust the Day Setpoint to. If an attempt is made to adjust the Day Setpoint lower, it will not change. If a lower value is commanded from the OWS or another device, it will not accept the change. The value for Day Minimum Setpoint can be set in the Configuration Menu, or by commanding the variable (via GCL+ or ORCAview OWS or 3 rd
Party devices).
Day Maximum Setpoint (AV8) –
This is the maximum value a user can adjust the Day Setpoint to. If an attempt is made to adjust the Day Setpoint higher it will not change. If a higher value is commanded from the OWS or another device, it will not accept the change. The value for Day Maximum Setpoint can be set in the Configuration Menu, or by commanding the variable (via GCL+ or ORCAview OWS or 3 rd
Party devices).
Page 18 of 41 Document Edition 4.1
Delta Controls
Day Differential (AV9) –
This is the differential setting between the Day Setpoint and the internal Heating Setpoint (which is used for heating control), and between the Day Setpoint and the internal Cooling Setpoint
(which is used for cooling control). The one value is used for both, one on each side of the Day
Setpoint . Refer to the diagram on page 16.
The purpose of this setting is to separate heating from cooling so as to prevent overlap, and to create a reasonable null zone, within which no modulating control takes place – preventing unnecessary actuator wear when the measured value is close to or on setpoint. The value for Day
Differential can be set in the Configuration Menu, or by commanding the variable (via GCL+ or
ORCAview OWS or 3 rd
Party devices).
Day Heating Setpoint (Internal)
This is the setpoint used internally for heating control (which is the Day Setpoint - Day
Differential ). This value is not directly adjustable. It can only be adjusted by setting either the
Day Setpoint or the Day Differential .
Day Cooling Setpoint (Internal)
This is the setpoint used internally for cooling control (which is the Day Setpoint + Day
Differential ). This value is not directly adjustable. It can only be adjusted by setting either the
Day Setpoint or the Day Differential .
Night Heating Setpoint (AV10)
This is the setpoint used when in N IGHT mode and night setback heating is required. If the current temperature is below the current Day Setpoint when in N IGHT mode, this value will be displayed on the BACstat LCD (depending on how setpoint display has been defined by the Display Code ).
This value is not adjustable by a user. It can only be adjusted through the configuration menu or by commanding the variable (via GCL+ or ORCAview OWS or 3 rd
Party devices). Pressing the up or down arrow will cycle to show the Night Cooling Setpoint .
Night Cooling Setpoint (AV11)
This is the setpoint used when in N IGHT mode and night setback cooling is required. If the current temperature is above the current Day Setpoint when in N IGHT mode, this value will be displayed on the BACstat LCD (depending on how setpoint display has been defined by the Display Code ).
This value is not adjustable by a user. It can only be adjusted through the configuration menu or by commanding the variable (via GCL+ or ORCAview OWS or 3 rd
Party devices). Pressing the up or down arrow will cycle to show the Night Heating Setpoint .
Document Edition 4.1
Page 19 of 41
DNT-T103 & DNT-T221 Application Guide
CONTROL DIAGRAM
The following diagram displays occupied mode and helps illustrate the relationship between the internal software loop controller and various objects, including outputs.
Input (AI1)
Heating
Heating Stage 1 (H1)
Heating Stage 2 (H2)
Heating Stage 3 (H3)
Output 1
Binary (Dir or Rev)
PWM (Dir or Rev)
Analog (Dir or Rev)
Analog VAV Flow Damper
Tri-State Actuator
Tri-State VAV Flow Damper
∗
∗
∗
∗
∗ ∗
∗ ∗
Setpoint (AV6)
BACstat Buttons
(or remote command via
GCL or OWS)
Controller &
Sequencing
Algorithm Mode
(AV13)
Cooling
Cooling Stage 1 (C1)
Cooling Stage 2 (C2)
Cooling Stage 3 (C3)
Fan
Constant Fan Operation (C)
Intermittent Fan Operation (I)
Output 2
Binary (Dir or Rev)
PWM (Dir or Rev)
Analog (Dir or Rev)
Time Proportioned (D or R)
Tri-State Actuator
Tri-State VAV Flow Damper
∗
∗
∗
∗
∗
∗ ∗
Manual Fan Operation (M)
Notes:
1.
∗
indicates the output type is only applicable for the DNT-T103.
2.
∗ ∗
indicates the output type is only applicable for the DNT-T221.
3. An analog output type for outputs 1 & 2 on a DNT-T221 when HPU has been
selected provides a 0 or 10v signal - it is not a 0 to 10v signal nor a dry contact.
4. The output functions and types that are available are dependent on the control
application selected and what was selected for the previous output.
5. This is not a comprehensive diagram and does not include all output functions.
Refer to Output Functions and Types later in this document.
Output 3
Binary (Dir or Rev)
PWM (Dir or Rev)
Time Proportioned (D or R)
Binary Fan (On/Off)
CONTROL APPLICATIONS
1.
NONE (or MUX) – [Application (AV12) = 0]
Function: No local control strategy, allowing the outputs (via AV1 to AV3) to be directly controlled from a remote device.
•
Triac outputs may be configured as Binary (which are not delayed; their values are transferred immediately upon being received), PWM, and Tri-state (on Outputs 1 & 2).
•
Analog outputs may be configured for 0-10v actuators (DNT-T221 only).
•
Outputs configured as Pulse Width Modulation require that their “Low” and “High” variables be appropriately configured for the particular type of device the outputs are connected to. Default values of 59 and 293 are suitable for Belimo PWM actuators (representing 0.59 and 2.93 seconds respectively).
Page 20 of 41 Document Edition 4.1
Delta Controls
•
Outputs 1 and 2 configured as a Tri-State pair require that the “Tri-State Runtime” (AV24) be configured for the associated Tri-State actuator. The default of 120 seconds is suitable for certain
Honeywell actuators.
N OTE : Although “MUXing” is possible, it is not recommended because it can cause excessive network traffic. DNT’s that are connected to a BACnet MS/TP network are designed to operate as stand-alone devices using a local control application.
2.
VAV – [Application (AV12) = 1]
Function: Control of a simple VAV box with air flow measured with a Kavlico sensor (DFT740-A) or
Setra sensor on Input 2 (0 to 1” range), a Tri-State damper on Outputs 1 and 2 (for DNT-T103) or an analog damper on Output 1 (for DNT-T221), and various options on the remaining outputs (some no longer available in Release 3).
DNT-T103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
N/A Optional OAT Room Temp. Air Flow
(0 to 1”)
Room Temp. Air Flow
(0 to 1”)
Room Temp. Air Flow
(0 to 1”)
N/A
N/A
Optional OAT
Optional OAT
Output 2 Output 3
Tri-State Flow
Damper (Open)
Tri-State Flow
Damper (Close)
Heating 1
Tri-State Flow
Damper (Open)
Tri-State Flow
Damper (Close)
Fan
Tri-State Flow
Damper (Open)
Tri-State Flow
Damper (Close)
None
(MUX)
DNT-T221 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
N/A Optional OAT Room Temp. Air Flow
(0 to 1”)
Room Temp. Air Flow
(0 to 1”)
Room Temp. Air Flow
(0 to 1”)
Room Temp. Air Flow
(0 to 1”)
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Analog Flow
Damper
Analog Flow
Damper
Analog Flow
Damper
Analog Flow
Damper
Room Temp. Air Flow
(0 to 1”)
N/A Optional OAT Analog Flow
Damper
Output 2
Heating 1
Heating 1
Output 3
Heating 2
Fan
Heating 1 None
(MUX)
MUX
(not in R3 or >)
Fan
None
(MUX)
None
(MUX)
N OTES :
For fan-powered boxes, series fans should always be configured for continuous operation – never intermittent or the fan could run backwards on startup. When a parallel fan is used in a heating application it should be configured as the 1st stage of heating (and wired to the appropriate output accordingly), rather than as a fan output.
Document Edition 4.1
Page 21 of 41
DNT-T103 & DNT-T221 Application Guide
Setup Parameters
Setup Variable Function
AV24
AV25
AV26
AV27
AV28
AV29
Tri-state Flow Damper Runtime
Air Flow Factor
Air Flow Minimum
Air Flow Maximum
PWM minimum value or Binary On Delay (or
Binary Off Delay for a Fan)
PWM maximum value or Time Proportioned
Heating Controller Limit
Notes
Default of 120 seconds
Converts Duct size and Air flow velocity to CFM or Liters/Second
Minimum Air Flow Setpoint
Maximum Air Flow Setpoint
Depends on OP3 configuration
Depends on OP3 configuration
Sequence of Operation
The airflow setpoint is generated from the Cooling Minimum setpoint, Cooling Maximum Setpoint and the Cool 1 value as shown below.
Air flow Setpoint
Controller Output (Cooling 1)
0
Max Flow
Max
Cooling flow
Min
Cooling flow
N OTE : To prevent a series fan from starting backwards, the damper stays shut in all night modes – it does not modulate. If heating is required during the night, a radiant panel can be used to meet the Night Heating
Setpoint (AV10). Since the damper will not modulate for night cooling
(AV11), if night cooling is required write a GCL program in an associated DSC controller on the network to put the box/BACstat into
Occupancy mode and bring on the air system until the setpoint is achieved.
0% 100%
The Air Flow input is compared to the current Airflow setpoint by the flow control loop. On the DNT-
T103, the Tri-State damper outputs 1 and 2 are used to control the damper to adjust the flow to match the current airflow setpoint. The rate of the damper from closed to open is adjusted using AV24 –
Damper Run Time. The default value is 120 seconds. On the DNT-T221, the analog damper output 1 is used to control airflow, but also requires that an appropriate runtime be set for the actuator (via Setup variable AV24).
In Unoccupied Deadband mode the Airflow Setpoint is set to zero.
Output 3 may be selected as a fan for fan-powered boxes. Alternatively, the output may be selected to be Heating 1 or supplementary Cooling 2, which may be of type Binary or PWM or Timed
Proportional.
Variable AV25 (Air Flow Factor) represents a value that includes duct size and any other constants or conversion factors so Input 2 reads air flow (in CFM or L/S), and requires that:
• a 0 to 1” H
2
O (0 to 250 Pa) sensor is connected to Input 2 (AI2); and
• the air flow units of either CFM or L/S is selected
•
AFF = box K factor * Area in in
2
/ 144 [which is then divided by 2.1188 to get L/S, if desired] (Refer to page 14 for information on Box Mode and Controller Operation)
Page 22 of 41 Document Edition 4.1
Delta Controls
3.
VVT – [Application (AV12) = 2]
Function: Control of a simple VVT box with a Tri-State damper on Outputs 1 and 2 (for DNT-T103) or an analog damper on Output 1 (for DNT-T221), and various options on the remaining outputs (of which some options are no longer available in Release 3 firmware).
DNT-T103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp. N/A Optional OAT Tri-State
Damper - Cool
(Open)
Room Temp. N/A Optional OAT
Room Temp. N/A Optional OAT
Tri-State
Damper - Cool
(Open)
Tri-State
Damper - Cool
(Open)
Output 2
Tri-State
Damper - Cool
(Close)
Tri-State
Damper - Cool
(Close)
Tri-State
Damper - Cool
(Close)
Output 3
Heating 1
Fan
None
(MUX)
DNT-T221 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Analog Damper
(Cooling 1)
Analog Damper
(Cooling 1)
Analog Damper
(Cooling 1)
Analog Damper
(Cooling 1)
Analog Damper
(Cooling 1)
Output 2
Heating 1
Heating 1
Heating 1
None
(MUX)
None
(MUX)
Output 3
Heating 2
Fan
None
(MUX)
None
(MUX)
Fan
N OTE : For fan-powered boxes series fans should always be configured for continuous operation – never intermittent or the fan could run backwards on startup. And, in order for a parallel fan to be properly sequenced it should generally be configured as the 1st stage of heating (and wired to OP1), rather than as a fan.
Setup Parameters
Setup Variable
AV24
AV25
AV26
AV27
AV28
AV29
Function
Damper Runtime (Tri-state or Analog)
N/A
Damper Minimum
Damper Maximum
PWM minimum value or Binary On Delay
(or Binary Off Delay for a Fan)
PWM maximum value or Time Proportioned
Heating Controller Limit
Notes
Default of 120 seconds
Damper Minimum Position
Damper Maximum Position
Depends on OP3 configuration
Depends on OP3 configuration
Document Edition 4.1
Page 23 of 41
DNT-T103 & DNT-T221 Application Guide
Sequence of Operation
The current damper position is generated from the Cooling Minimum setpoint, Cooling Maximum
Setpoint and the Cool 1 value.
Max Damper Position
Max
Damper
Position
Damper Position
Min
Damper
Position
0
Controller Output (Cooling 1)
0% 100%
For the DNT-T103 the desired damper position is compared to the current estimated damper position by the Tri-State controller loop. The Tri-State damper outputs (1 & 2) are used to control the damper and adjust the estimated position to match the current desired position. The rate of the damper from closed to open is adjusted using AV24 – Damper Run Time (seconds). The default value is 120 seconds. On the DNT-T221, the analog damper output 1 is used to control damper position, but also requires a runtime value set in AV24.
In Unoccupied Deadband mode the damper position is set to zero.
Output 3 may be selected as a fan, which would operate according to the above table. Alternatively, the output may be selected to be Heating 1 or supplementary cooling 2, which may be of type Binary or
PWM or Timed Proportional. Also refer to page 14 for operating information on Box Mode and
Controller Operation.
4.
H EAT P UMP U NIT (HPU) – [Application (AV12) = 3]
Function: Control of a single-stage Heat Pump Unit with reversing valve and optional fan.
DNT-T103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Compressor
Compressor
Compressor
Compressor
Output 2 Output
3
Reversing
Valve
Heating
2
Reversing
Valve
Reversing
Valve
Reversing
Valve
Cooling
2
Fan
None
(MUX)
Page 24 of 41 Document Edition 4.1
Delta Controls
DNT-T221 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp. N/A Optional OAT
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Compressor
(0/10v)
Compressor
(0/10v)
Compressor
(0/10v)
Compressor
(0/10v)
Output 2
Reversing
Valve (0/10v)
Reversing
Valve (0/10v)
Reversing
Valve (0/10v)
Reversing
Valve (0/10v)
Output 3
Heating 2
Cooling 2
Fan
None
(MUX)
Setup Parameters
Setup Variable
AV24
AV25
AV26
AV27
AV28
AV29
Function
Binary Delay
N/A
Binary Delay
N/A
PWM minimum value or Binary On Delay
PWM maximum value or Time Proportioned
Heating Controller Limit
Notes
Transition Timer for Compressor
Transition Timer for Rev. Valve
Depends on OP3 configuration
Depends on OP3 configuration
Sequence of Operation
START
Heating &
Cooling = 0
N
Heating > 90%
N
Y
DEADBAND
Y
HEATING
Rev. Valve is OFF
N
Y
Switch to HEATING
Turn Rev. Valve ON
Wait Delay Time
Cooling > 90%
N
Y
COOLING
Rev. Valve is ON
Y
Switch to COOLING
Turn Rev. Valve OFF
Wait Delay Time
N
Turn Compressor OFF
Turn Fan OFF
Turn Compressor ON
Turn Fan ON
Document Edition 4.1
Page 25 of 41
DNT-T103 & DNT-T221 Application Guide
If the Heating and Cooling controllers are both zero the control logic is in deadband and the compressor output is turned O FF .
If the Heating controller value exceeds 90% the control logic will switch to heating, and the reversing valve is turned O N if isn’t on already. After the transition timer has expired the compressor output will be turned O N . The transition timer will then be reset (to the value set in the Setup variable AV24).
If the Cooling controller value exceeds 90% the control logic will switch to cooling, and the reversing valve is turned O FF if isn’t off already. After the transition timer has expired the compressor output will be turned O N . The transition timer will then be reset.
The HPU algorithm may use a fan on Output 3, or have an auxiliary heating or cooling output of type
Binary or PWM or Timed Proportional.
When the fan type is ‘Intermittent’ the fan will start when the compressor starts. When the compressor stops the fan will be turned off when the delay time has expired (Setpoint 28, Output 3 Binary Delay ).
N OTE : The analog outputs on the DNT-T221 do not modulate, but provide a 0 or 10v signal for the compressor and reversing valve, and require interface relays for switching purposes.
5.
F AN C OIL U NIT (FCU) – [Application (AV12) = 4]
Function: Control of a simple Fan Coil Unit with fan.
DNT-T103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp. N/A Optional OAT Heating 1
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Heating 1
Heating 1
Cooling 1
Cooling 1
Cooling 1
Tri-State
Heating (Open)
Tri-State
Cooling (Open)
Output 2
Heating 2
Cooling 1
MUX
Heating 1
Cooling 2
MUX
Tri-State
Heating (Close)
Tri-State
Cooling (Close)
Output 3
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
DNT-T221 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Heating 1
Heating 1
Heating 1
Cooling 1
Cooling 1
Cooling 1
Output 2
Heating 2
Cooling 1
MUX
Heating 1
Cooling 2
MUX
Output 3
Fan
Fan
Fan
Fan
Fan
Fan
Setup Parameters
Setup Variable
AV24
AV25
AV26
Function
PWM minimum value or Binary On Delay or
Actuator Runtime (Tri-State Valves)
PWM maximum value
PWM minimum value or Binary On Delay
Notes
Depends on OP1 configuration
Depends on OP1 configuration
Depends on OP2 configuration
Page 26 of 41 Document Edition 4.1
Delta Controls
AV27
AV28
AV29
PWM maximum value Depends on OP2 configuration
Binary Off Delay For the Fan
Time Proportioned Heating Controller Limit Depends on OP3 configuration
Sequence of Operation
The fan will operate according to the selected fan type as described under Fan Control in the Output section of this document (on page 32). For hotel applications you may want to define the fan type as
Manual .
The selected heating and cooling outputs will operate according to their type and the controller stage that they are associated with.
DNT-T103 Only: When the fan type is ‘Intermittent’ the fan will start when the first stage controller value for heating or cooling becomes greater than 99.9%. When the first stage controllers for heating and cooling both become less than 1% a delay counter for stopping the fan will be started. Once the delay time has expired (Setpoint 28, Output 3 Binary Delay ) the fan output will be turned off.
6.
U NIT H EATER
This application is no longer supported as of Release 3 firmware for BACstat II products. Use the FCU application to configure control for a Unit Heater . [And refer to Edition 1.6 for earlier firmware releases.]
7.
R ADIATION & R EHEAT – [Application (AV12) = 5]
Function: Control of simple single stage or multi-stage heating, typically using wall fin radiation or reheat.
DNT-T103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
Room Temp.
Room Temp.
Room Temp.
Room Temp.
N/A
N/A
N/A
N/A
N/A
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Optional OAT
Heating 1
Heating 1
Heating 1
Tri-State
Heating (Open)
Tri-State
Heating (Open)
Output 2
Heating 2
Heating 2
MUX
Tri-State
Heating (Close)
Tri-State
Heating (Close)
Output 3
Heating 3
MUX
MUX
Heating 2
MUX
DNT-T221 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp. N/A Optional OAT Heating 1
Room Temp.
Room Temp.
N/A
N/A
Optional OAT
Optional OAT
Heating 1
Heating 1
Output 2
Heating 2
Heating 2
MUX
Output 3
Heating 3
MUX
MUX
Setup Parameters
Setup Variable
AV24
AV25
AV26
AV27
Function
PWM minimum value or Binary On Delay or Actuator Runtime (Tri-State Valves)
Notes
Depends on OP1 configuration
PWM maximum value Depends on OP1 configuration
PWM minimum value or Binary On Delay Depends on OP2 configuration
PWM maximum value Depends on OP2 configuration
Document Edition 4.1
Page 27 of 41
DNT-T103 & DNT-T221 Application Guide
AV28
AV29
PWM minimum value or Binary On Delay Depends on OP3 configuration
PWM maximum value or Time
Proportioned Heating Controller Limit
Depends on OP3 configuration
Sequence of Operation
The selected heating outputs will be operated according to their type and the controller stage that they are associated with. There can be up to three stages of heating, depending on the heating type and configuration of the outputs. Also, Outputs 1 to 3 may be defined as Time Proportioned instead.
8.
H UMIDITY – [Application (AV12) = 6]
Function: Simple control of a humidifier.
DNT-TH103 I/O (Outputs 1 to 3 are Triacs)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
(Optional)
Room
Humidity
Optional OAT Humidifier
DNT-H121 I/O (Outputs 1 & 2 are Analog, and Output 3 is a Triac)
Input AI1 Input AI2 Input AI3 Remote AV5 Output 1
Room Temp.
(Optional)
Room
Humidity
Optional OAT Humidifier
Output 2
MUX
Output 2
MUX
Output 3
MUX
Output 3
MUX
Setup Parameters
Setup Variable
AV24
AV25
AV26
AV27
AV28
AV29
Function Notes
PWM minimum value or Binary On Delay Depends on OP1 configuration
PWM maximum value Depends on OP1 configuration
PWM minimum value or Binary On Delay Depends on OP2 configuration
PWM maximum value Depends on OP2 configuration
PWM minimum value or Binary On Delay Depends on OP3 configuration
PWM maximum value Depends on OP4 configuration
Sequence of Operation
Input 3 represents the built-in humidity sensor and becomes the input to the internal controller. The adjustable room setpoint (AV6) becomes the humidity setpoint. And the controller proportional band is used for humidity control, now in units of percent. Output 1 (via AV1) will operate according to its selected output type and the value of the controller output, typically turning O N when the humidity is low and O FF when the setpoint value has been reached.
OUTPUT FUNCTIONS & TYPES
Regardless of model, any triac outputs are capable of switching up to 24 VAC at a maximum of 0.5 A each, and may be configured for any of a number of output functions and types. Only the DNT-T221 supports two
0-10v outputs, up to a maximum of 20 mA each. Not all applications support all the options listed.
FUNCTIONS
Function
MUX
Heating
Description
The associated output will be MUXed and not controlled by the local algorithm, or not used at all.
The associated output is connected to 1st stage heating.
LCD Code
0
10
Page 28 of 41 Document Edition 4.1
Delta Controls
Cooling
Fan
Compressor
The associated output is connected to 2nd stage heating.
The associated output is connected to 3rd stage heating.
The associated output is connected to 1st stage cooling.
The associated output is connected to 2nd stage cooling.
The associated output is connected to an intermittent fan.
The associated output is connected to a constant fan.
The associated output is connected to a manually controlled fan.
The associated output is connected to a HPU compressor.
Reversing Valve The associated output is connected to a HPU reversing valve.
Humidifier The associated output is connected to a humidifier.
* Only available in HPU and FCU applications.
20
30
40
50
70
80
90 *
100
110
120
TYPES
Output Type
Binary
PWM
Analog
Flow Damper
(Analog)
Time
Proportioned
Tri-State
Flow Damper
(Tri-State)
Description
Provides O N /O FF control with a triac output.
Action LCD Code
Direct 0.0
Reverse 0.1
Direct 0.2 Provides modulating control using a Pulsed Width
Modulation signal with a triac output.
Provides modulating control using a 0-10v analog signal (DNT-T221).
Provides modulating control using a 0-10v analog flow damper (DNT-T221 & VAV).
Provides modulating control using a Time
Proportioned signal with a triac output.
Reverse
Direct
Reverse
N/A
Direct
Reverse
Provides modulating control using triac outputs 1 & 2 for a tri-state actuator (DNT-T103).
Provides modulating control, using triac outputs 1 & 2 for a tri-state flow damper (DNT-T103 & VAV).
N/A
N/A
Box Mode affects how the flow damper functions in both VAV and VVT applications. Refer to page 14 for operating information on Box Mode, and page 16 regarding Controller Operation.
0.3
0.4
0.5
0.6
0.8
0.9
1.0
1.1
OWS Configuration
It is of course possible to configure the outputs via ORCAview OWS, rather than through the keypad
Configuration Menu at the BACstat. Variables AV21 to 23 are used to configure each of the three outputs, but you must configure these variables in the proper sequence (refer to page 33 for further information). For a complete list of these variables and other objects, refer to the Object table on page 9.
When configuring the BACstat through the keypad, configuration codes are automatically determined for each of the output configuration variables. When using ORCAview OWS you manually enter an appropriate configuration code for each variable (in the proper sequence). The configuration code for an
Document Edition 4.1
Page 29 of 41
DNT-T103 & DNT-T221 Application Guide output is a combination of its function and type (as obtained from the tables on the previous page) according to the following formula:
Output Configuration Code = Output Function Code + Output Type Code
For example: To configure Output 1 on a DNT-T221 as a direct acting analog output for first stage heating, enter the number 10.4 into AV21 (where 10 is the function and 0.4 is the type , so 10 + 0.4
=10.4).
1.
B INARY O UTPUTS
If the binary output is selected as M UX it simply transfers the value written to the corresponding variable
(AV1, AV2 or AV3) to the physical output. There is no delay.
If the binary output is controlled internally by the BACstat II, then it will have a delay-on that is specified by its corresponding setup variable. This value is in seconds.
Physical Output
OP1
OP2
OP3
Associated AV
AV1
AV2
AV3
Delay Setup Variable
AV24
AV26
AV28
2.
P ULSE W IDTH M ODULATION O UTPUTS (PWM)
The Pulse Width Modulation scheme used on the BACstat II is applicable to the Belimo NM24 actuator.
An analog value is converted to a variable duty cycle pulse that has minimum and maximum pulse times as determined by setup variables. For example, a Belimo PWM actuator uses a minimum value of
0.59 sec., and a maximum value of 2.93 sec. The O N portion of the pulse then stretches from 0% @
0.59 to 100% @ 2.93.
2.93 Sec.
0.59 Sec.
0%
100%
If the output using PWM is also configured as reverse acting then the output device will be considered to be reverse acting (i.e., Normally Open) and the input value will be inverted internally before being applied to the physical output. The actual action of the physical output will be direct.
If the PWM output is not being used for a Belimo device then the minimum and maximum values can be changed to what ever is required. Also, Belimo actuators may be configured to use a 0.5 to 25.5 signal instead, which may be more suitable in many cases (i.e., variable values of 50 and 2550).
Physical Output Associated Output AV Min. Setup Variable Max. Setup Variable
OP1 AV1 AV24 AV25
OP2
OP3
AV2
AV3
AV26
AV28
AV27
AV29
The value (in seconds) is shifted by two decimal places when entered in the variable. Default values are,
Minimum PWM Value = 59 Maximum PWM Value = 293
3.
T IME P ROPORTIONED (TP)
The DNT-T103 can have up to two stages of Time Proportioned heat (Outputs 2 and 3), while the
DNT-T221 can have one stage (Output 3). These are similar to the PWM outputs except:
Page 30 of 41 Document Edition 4.1
Delta Controls
•
The cycle time is fixed at ten seconds
•
At a controller value of 0% the outputs are always O FF
•
At a controller value of 100% the outputs are always O N
•
The controller value, from 0 to 100%, is mapped into the duty cycle directly (i.e., 50% is 5 seconds O N and 5 seconds O FF , for a single output).
100%
Time Proportioned input
20%
0%
On
2 seconds 8 Seconds
Off
10 Seconds
Cycle time is fixed at 10 seconds
When the Input = 0%, the Output is Off all the time
When the Input = 100%, the Output is On all the time
Output Staging is limited by the Setup 6 variable (AV29)
Heating Controller Limiting
Setup variable AV29 is used as a heating controller limit . A value of 0 to 100% entered into this variable will limit the main heating controller accordingly, and by default is set to 100%.
By limiting the controller value itself you are able to limit the output staging, which may be used for load limiting purposes. However, this limit is only applicable for heating, not cooling applications.
4.
T RI -S TATE OR F LOATING P OINT (DNT-T103 O NLY )
Tri-State uses a pair of outputs (always Outputs 1 and 2). Output 1 opens the device, and Output 2 closes the device. It is assumed that when neither output is on the device does not change position. The
Tri-State device has a runtime property, the time that it takes to go from fully open to fully closed. It is assumed that the device will take as long to close as it does to open and that the open and close rate is linear.
At start up the Tri-State algorithm establishes a closed position reference by closing continuously for
1.25 x the Run Time. It will also enter this state each time that it first receives a zero position valve. A signal of 100% will cause the algorithm to open the device for 1.25 run times to establish an open reference.
Document Edition 4.1
Page 31 of 41
DNT-T103 & DNT-T221 Application Guide
The Algorithm estimates the position of the Tri-state device by mapping run time against desired percent open/closed. Therefore it is important to enter an accurate runtime parameter. The algorithm also has an internal dead band of 6% to minimize hunting of the valve position.
If a reverse acting valve is to be used, cross connect the Open and Close outputs.
5.
F AN C ONTROL
There are three modes of operation:
Fan Type
Continuous Fan
Intermittent Fan
Manual Fan
Occupied Mode
O N constantly.
O N when the Controller is not in deadband. O FF in deadband.
Fan O N and O FF controlled by user button presses.
Unoccupied Mode
O N when the Controller is not in deadband for night setback.
O N when the Controller is not in deadband for night setback.
O N when the Controller is not in deadband for night setback.
If Fan is selected it is always connected to Output 3, and can be configured for reverse or direct acting.
Setup variable AV28 is the Fan delay value in seconds, which is used for ‘delay off’. [In some cases the fan should be connected to OP1 and configured as the 1st stage of heating, not as a fan – see the note below.]
Each configuration has a specific sequence of operation that is tailored to control that type of terminal unit.
The fan is single speed O N / O FF control. With the limited number of outputs, neither the DNT-T103 nor the DNT-T221 support 2 or 3 speed fans in any of the built-in control strategies. If you need to control a
FCU or other equipment with multi-speed fans, you will need to connect the BACstat to a LINKnet network, disable local control applications and write your own fan control program in the DAC the
BACstat is connected to.
When the application is set to FCU on a DNT-T103 and the fan type is Intermittent , the fan will start when the first stage controller value for heating or cooling becomes greater than 99.9%. When the first stage controllers for heating and cooling both become less than 1% and the Output 3 Binary Delay
(AV28) has timed out, the fan output will be turned off. [Only exists in Release 2 Firmware and higher.]
When the application is set to HPU on a DNT-T103 and the fan type is Intermittent , the fan will start when the compressor starts. When the compressor stops and the Output 3 Binary Delay (AV28) has timed out, the fan output will be turned off. [Only exists in Release 2 Firmware and higher.]
N OTE : For fan-powered boxes series fans should always be configured for continuous operation – never intermittent or the fan could run backwards on startup. And, in order for a parallel fan to be properly sequenced it should generally be configured as the 1st stage of heating (and wired to OP1), rather than as a fan.
6.
A NALOG (DNT-T221 O NLY )
Only the DNT-221 supports two analog outputs, which provide a 0 to 10v signal. Selecting Outputs 1
&2 as analog are not even options in the Configuration Menu for the DNT-T103.
For VAV and VVT, Output 1 is configured as an analog damper (flow for VAV and cooling for VVT).
The other analog output may be configured as a modulating output for auxiliary heating or cooling. Due to the internal controller logic, an analog flow damper also requires that an appropriate runtime be set for the actuator (via Setup variable AV24), which is set to control the speed with which the damper will move and needs to be equal to or greater than the actual run time of the analog actuator. Analog outputs for auxiliary heating or cooling do not have an associated runtime setting.
Page 32 of 41 Document Edition 4.1
Delta Controls
If the application is something other than VAV or VVT, then both analog outputs may be configured for either heating or cooling. Analog outputs for heating or cooling may be either direct or reverse acting.
For the HPU application, 2-position control is provided for the compressor and reversing valve, 0 or 10v
(typically requiring an appropriate interface relay), rather than modulating the two analog outputs.
OWS Functions
1.
D EVICE C ONFIGURATION
The BACstat can be configured and commissioned using the keypad buttons, via the Configuration
Menu, without additional software. It can also be configured using the ORCAview OWS if the BACstat is connected to an MS/TP network.
However, to do this requires a minimum configuration for each device to ensure they are all configured the same and are communicating properly on the designated network. These essential configuration items include:
•
N ETWORK C ONNECTION : LINKnet O FF (MS/TP).
•
DNA: O N or O FF
•
D EVICE A DDRESS : 1-99 for MS/TP
•
B
AUD
R
ATE
: Set the speed to match the network it will be
connected
to (76,800 bps is the default)
Configuration Settings
When the ORCAview OWS is able to access the BACstat and its objects, you may then configure the following BACstat settings at the OWS (which are usually configured once and rarely ever changed thereafter). However, these must be configured in the sequence provided (which is the same as the
Configuration Menu). Any change to these settings from an OWS requires the BACstat to be reset
(locally or via user command).
•
A PPLICATION : AV12 (refer to page 12)
•
O UTPUT C ONFIGURATION 1: AV21 (refer to page 28, and associated Application information)
•
O UTPUT C ONFIGURATION 2: AV22 (refer to page 28, and associated Application information)
•
O UTPUT C ONFIGURATION 3: AV23 (refer to page 28, and associated Application information)
•
A DDITIONAL P ARAMETERS : AV24 to AV29 (as per associated Application information)
Control Settings
These are other settings you may want to set from the OWS, which may also be commanded on the fly by a user or from a GCL+ program:
•
A LGORITHM M ODE : AV13 (which defaults to Night)
•
D AY S ETPOINT : AV6
•
D AY M INIMUM : AV7
•
D AY M AXIMUM : AV8
•
D AY D IFFERENTIAL : AV9
•
N IGHT H EAT S ETPOINT : AV10 (which can only be changed remotely, not via the keypad)
•
N IGHT C OOL S ETPOINT : AV11 (which can only be changed remotely, not via the keypad)
Document Edition 4.1
Page 33 of 41
DNT-T103 & DNT-T221 Application Guide
Additional Settings
These are additional settings you may also want to set from the OWS, and may be commanded as necessary, but rarely are once they have been set (or the control loop has been tuned).
•
P ROPORTIONAL B AND : AV19
•
R ESET R ATE : AV20
•
D ISPLAY C ODE : AV15 (refer to page 5)
•
PIN A CCESS C ODE : AV31 (which can only be changed remotely, not via the keypad)
•
S ERVICE T OOL M ODE : AV32 (to enable or disable access)
7.
AI2 ( AND AI3) C ONFIGURATION
While AI1 is typically configured from the Configuration Menu, by setting the Temperature Units setting (degrees C or F), additional inputs such as AI2 (and AI3 on the DNT-T221) are configured through the OWS. Once you have ensured that the input is correctly wired and the hardware jumper is appropriately set, use ORCAview to verify that the AI object is not in manual mode and the units are properly set for the sensor. An exception to this is if AI2 is used for VAV airflow – setting the application will configure AI2 accordingly.
8.
C OPYING THE C ONFIGURATION FROM O NE D EVICE TO A NOTHER
It is possible to copy the configuration setup of one BACstat to another. It is a simple 1-2-3 procedure:
1.
Configure one BACstat for the desired application with the settings you want.
2.
Save the BACstat settings to a file on ORCAview (as described below, under Save As ).
3.
Load this file into the other BACstats on the network, one at a time.
This should replicate the same configuration (i.e., object values) from one BACstat to another, and provide you a backup copy of the configuration settings in a file. The BACstat that you are copying the configuration to must have its application set either to NONE or to the exact same application as the saved setup.
9.
N AVIGATOR R IGHT -M OUSE C LICKS
By clicking the right-mouse button on the BACstat icon in the left pane of Navigator you gain access to a number of device commands.
Command
CLEAR DATABASE : The clear database feature (YES or NO) resets the configuration settings to the default. The following are not cleared: Baud Rate, Device Address, DNA/LINKnet, MaxMaster and
Max Info Frame.
U PDATE A CTIVE A LARM L IST : Not supported at this time.
C OMMUNICATION C ONTROL : This allows an OWS user to enable or disable a remote device from initiating and responding to all BACnet services, except for Device Communication Control services and Reinitialize Device services. It is primarily used for diagnostic purposes. Passwords are not supported (and need not be entered) for BACstats, and the time duration is infinite.
R ECONFIGURE : If DNA is enabled on the BACstat, this will re-configure its address by deriving portions of it from other higher-level devices (for Area and System numbers). BACstat DNA addressing limited to 4194199.
R ESET : This will reset the device, similar to powering it off and then back on again.
Reload
D ESCRIPTORS : This will reload the BACstat descriptors up into ORCAview OWS. This is particularly useful if for some reason the OWS is out-of-sync with what objects and object names the BACstat has.
S YSTEM O BJECTS : Not supported at this time.
Page 34 of 41 Document Edition 4.1
Delta Controls
A CTIVE A LARMS : Not supported at this time.
N
OTE
:
Loading databases between different models may cause database load failures. For example, DNT-T103
↔DNT
-H103
↔ DNT
-T221, etc.
Load
This provides the capability of loading a BACstat file (which you have previously saved) into a
BACstat, and in so doing will configure it with the settings contained in the file. You can reload the file either back into the source BACstat or into another BACstat. You can even use the same BACstat file to load into multiple BACstats and thus copy the same configuration settings from one device to another.
Refer to Copying in item 3 above.
Save As
This provides the ability to save the BACstat object names and values to a file. You are not saving the entire object structure as is done when saving DCU or Application Controller databases – you are only saving object properties (names and values) – an important distinction since you cannot create or delete objects in a BACstat. But since all the essential configuration information is contained in object values, you are in fact saving the BACstat configuration to a file.
APPENDIX A: Programming Notes
The following provides additional important programming information.
1.
C ONFIGURATION V ARIABLES (AV12 & AV21-23): These variables should never be commanded on the fly from a GCL+ program (or user command). They must be configured in the proper sequence and they radically alter operation too much to make frequent changes. Besides, changing the application configuration from an OWS requires that you reset the BACstat (either locally or via user command). Also refer to the
Configuration Menu options on page 4 for further information.
2.
C OMMANDING V ARIABLES : When commanding other variables (such as setpoints and alg mode) from GCL++ in an Application Controller write your programs so they are not being commanded on every program scan. Use IFONCE or DOEVERY statements to key the execution of specific events or time intervals, and thereby limit the frequency of such commands. Otherwise you will create excessive network traffic.
3.
C OMMAND P RIORITY : Both GCL+ programs and user commands (i.e., manual mode) have the same write priority for all objects in a BACstat. There are no priority arrays or command hierarchy. Whatever commands the object last is the value the object will have.
Therefore, write your GCL+ programs so as to minimize any conflicts with acceptable user commands (such as temporary or fixed overrides).
4.
GCL++ P ROGRAMMING TO R ESET THE K EY P RESS V ALUE TO 0: Normally the
KeyPress value (AV4) only changes when a new button or button-combination is pressed, and under these conditions it is not possible to detect that the same button has been pressed again. With Release 3 (and higher) firmware you can now reset the KeyPress value after you have read it, allowing you to detect when the same button gets pressed again. The following is an example of resetting the KeyPress value back to zero (using a mapped AV in the DAC), assuming you have already read the value.
AV104 = 0
BACstat #1]
[where AV104 is the mapped AV in the DAC associated with AV4 in
Document Edition 4.1
Page 35 of 41
DNT-T103 & DNT-T221 Application Guide
APPENDIX B: LINKnet
Configuration Menu Options
Menu Item DSP On LINKnet BACstats communicate at 76,800 bps. Refer to the Working with MS/TP and LINKnet appendix within the Technical Reference Manual .
Menu Item Add On LINKnet, this address is the physical address for the device (limited to 1 to 12) and the other address settings are irrelevant.
Menus Item
Lnt
The LINKnet Communications Setting (O N or O FF ), to match the connection method. The Lnt should be set to O FF when connecting to MS/TP.
As the temperature units ( º C or º F) can only be set via the Configuration Menu at the device (when connected on LINKnet), you may want to set this at the same time.
Input Calibration
LINKnet Connection
With local handling of the LCD display and buttons disabled (AVx15 = 1111) , the BACstat sends A/D values to its associated AI objects in the Application Controller, where calibration and filtering is applied. Calibrate the AI objects in the Application Controller.
With local handling of the LCD display and buttons enabled (AVx15 > 1111) , the BACstat sends actual values to its associated AI objects in the Application Controller – all calibration and filtering is done in the BACstat. Calibrate the BACstats locally (via Service Tool Menu) or use the mapped AV objects (See the Objects table). Do not calibrate the AI objects in the Application Controller.
Device Limitations
Note that there are inherent limitations to the total number of devices per LINKnet network, as well as the number of devices that have outputs. Refer to the appropriate Appendix in the ORCAview
Technical Reference Manual for further information.
Control Applications
BACstats with I/O should have their built-in control applications disabled . If you wish to have
BACstats running a local control strategy, then it should be connected to an MS/TP network instead.
Objects
Only the BACstat information that is represented by objects resident in the Application Controller is readily accessible over the network. The objects resident within each BACstat are not directly accessible to other devices in the system. To gain access to BACstat objects, you create objects in the
Application Controller that correspond to the objects located in its respective BACstats.
Object Name Description Creation
LCDx01
AIx01, 02, 03
LinkLCD#
[User Specified]
Object for BACstat LCD &
Button Presses
Matching object for the Input
Value
Automatic
Manually
AVx01, 02, etc. [User Specified]
Matching object for the corresponding AV
Manually where “x” refers to the device address (1 to 12).
An LCD object is automatically created for each BACstat connected to the LINKnet network.
However, the associated AI objects representing the room temperature in each BACstat must be created manually, and must follow a predefined numbering scheme. The object instance number is the
LINKnet device address (1 to 12) multiplied by 100, plus 1. For example, you would create AI501 in
Page 36 of 41 Document Edition 4.1
Delta Controls the Application Controller to represent the 10K Thermistor value on a BACstat with a LINKnet device address of 5.
With V3.22 or higher loaded in the Application Controller, AV objects may be created in a similar fashion to the AI objects, which map to corresponding AV objects in the BACstat. You can then use these in GCL+ programming as well. With V3.21, mapped AV objects are not supported.
Software & Programming
OBJECTS
The following is a list of predefined objects that reside in the BACstat II products that cannot be created or deleted. When connected to an MS/TP network, these objects are readily accessible over the network.
Object Name Description
AIx01
AIx02
AIx03
BO1
BO2
Temperature
Input 2 *
Humidity
Input 3 *
Output 1 *
Output 2 *
Input 1 (10K Thermistor Value)
Input 2 (Available Input)
Input 3 (Humidity on DNT-H103 DNT-H121)
Input 3 (Extra Input on DNT-T103 DNT-T221)
Output 1 on DNT-T103
Output 2 on DNT-T103
BO3
AO1
Output 3 *
Output 1 *
Output 3 on DNT-T103
Output 1 on DNT-T221
AO2 Output 2 * Output 2 on DNT-T221
BO3 Output 3 * Output 3 on DNT-T221
AVx04 KeyPress
AVx06
Day Setpoint
AVx07
Day Minimum
AVx08
Day Maximum
KeyPress Value
Room Setpoint
Minimum Adjustable Day Setpoint
Maximum Adjustable Day Setpoint
AVx09
Day Differential
AVx10
Night Heat Setpoint
Room Setpoint Differential
Night Setpoint for Heating (or Humidity)
AVx11
Night Cool Setpoint Night Setpoint for Cooling
AVx15 Display Code Local Display & Button Handling
AVx16
AVx17
AI1 Calibration
AI2 Calibration
Input 1 Calibration (Temperature)
Input 2 Calibration (MUXed IP)
AVx18
AVx30
AVx31
AI3 Calibration
Baud Rate
PIN
Input 3 Calibration (Humidity)
Network Baud Rate
PIN (4-Bit Configuration Access Code)
Default Value
1237
0.0
0.0
0.0
*
1011
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
ºC = 21; ºF = 71; % = 30
ºC = 18; ºF = 65; % = 20
ºC = 25; ºF = 77; % = 55
ºC = ±0.5; ºF = ±1, % = ±2.5
ºC = 16; ºF = 60; % = 30
ºC = 30; ºF = 86; % = 30
* Names are user settable (to a maximum of 32 characters), and only on outputs when they are controlled remotely (i.e.,
MUXed).
These are the typical objects that may be commanded on the fly by a user or from GCL++, and also include the
Outputs when they are MUXed.
GCL++ Programming
All GCL+ programming for BACstats on a LINKnet network is written in the Application Controller that the BACstats are connected to, using the mapped objects resident in the Application Controller.
The LCD object is used for display and button handling. The mapped AI objects are used for reading values. And with at least V3.22 firmware on the Application Controller, the mapped AV objects are used for outputs, setpoints, and various other settings.
Document Edition 4.1
Page 37 of 41
DNT-T103 & DNT-T221 Application Guide
With V3.21 Firmware : When connected to LINKnet, local display and button handling should be disabled (i.e., AVx15 = 1111), which is the default when you set the LINKnet Communications
Setting to On. This way, the LCD and buttons are fully accessible from the Application Controller for custom programming. Then, with GCL+ and the LCD and AI objects resident up in the Application
Controller, you program the BACstat to operate as you want (similar to how ISTATs were programmed) – all BACstat functionality is written in GCL+ located in the Application Controller.
Note that none of the AV objects are accessible with V3.21 firmware.
With V3.22 Firmware or Higher : You may disable local display and button handling (i.e., AVx15 =
1111) and program everything in GCL+ in the Application Controller as previously described for
V3.21 firmware. Or, by setting the Display Code to something other than 1111, the display and buttons may be configured to function locally and GCL+ commands from the Application Controller for display and button handling (via the LCD object) are ignored. This may be the preferred method as no GCL+ needs to be written to handle setpoint adjust and the display of values on the LCD.
LCD Object Property Values (for GCL+ Programming)
The following is a table of LCD object properties and associated values that can be used in GCL+ programming in a DAC/DSC product for BACstats when connected on its LINKnet network.
(Display code set to = 1111)
LCD Property Name Values & Description
Line1
Line2
Line3
Line1Units
Line2Units
Line3Units
Blink
Occupancy
0
1
2
3
4
5
1
0
1
0
1
2
6
0
1
For sending a value to Line 1
For sending a value to Line 2
For sending a value to Line 3
0 = º icon is turned off
= º icon is turned on
= º icon is turned off
= º icon is turned on
= No Unit icons
= º icon only
= ºC
= ºF
= %
= AM
= PM
= Blinking is disabled
= Entire LCD display blinks
= No House/Man (Disabled)
= House only (Unoccupancy)
= House & Man (Occupancy)
Sun
Moon
SunMoon
Fan
1
2
0
1
2
0
1
0
1
0
= Sun icon is turned off
= Sun icon is turned on
= Moon icon is turned off
= Moon icon is turned on
= No Sun or Moon (Disabled)
= Moon only
= Sun only
= No Fan icons - All turned off
= Fan icon only
= Fan with Air Flow Wave 1
Notes
Only available with V3.30
DAC/DSC firmware.
Only available with V3.30
DAC/DSC firmware.
Only available with V3.30
DAC/DSC firmware.
The values shown are for V3.30
DAC/DSC firmware. For V3.22 firmware, the values of 1 and 2 are reversed.
Applicable only for V3.22
DAC/DSC firmware.
Applicable only for V3.22
DAC/DSC firmware.
Applicable only for V3.30
DAC/DSC firmware.
Page 38 of 41 Document Edition 4.1
Delta Controls
Heating
Cooling
Humidity
Calibrate
On
Off
Time
Minimum
Maximum
Set
0
1
0
1
0
1
0
1
0
1
0
1
0
1
3
4
0
1
0
1
0
1
= Fan with Wave 1 & Wave 2
= Fan with Wave 1, Wave 2, Wave 3
= Heating icon is turned off
= Heating icon is turned on
= Cooling icon is turned off
= Cooling icon is turned on
= Humidity icon is turned off
= Humidity icon is turned on
= Calibrate text is turned off
= Calibrate text is turned on
= On text is turned off
= On text is turned on
= Off text is turned off
= Off text is turned on
= Time text is turned off
= Time text is turned on
= Min text is turned off
= Min text is turned on
= Max text is turned off
= Max text is turned on
= Set text is turned off
= Set text is turned on
Examples
With a BACstat II connected on a LINKnet network with an address of 1 (which is associated with
LCD1 in the DAC) and the Application set to None, here is a simple example of GCL+ programming using the LCD properties.
IF SCH1 ON THEN
ELSE
LCD1.OCCUPANCY = 2
ENDIF
LCD1.OCCUPANCY = 1
Note
: It is recommended practice to place this program strategy within an appropriate DoEvery.
As a result, the BACstat LCD will display the Man in the House during occupancy hours (according to
SCH1), and the House without the Man during unoccupancy hours. Note, however, that the command for either occupancy or unoccupancy is sent every program scan (or the DoEvery interval, as per recommendations). This means that a user would not be able to do any local override at the stat (which may be desirable for certain applications). If the user tries to do an override at the stat it will be over-written the next time the program in the DAC is executed (possibly within split-seconds).
The following program is the same as above, except that the command for either occupancy or unoccupancy is only sent when the SCH1 changes. This allows user override at the stat between schedule changes, and the stat will revert back to matching the SCH1 object on the next change.
IFONCE SCH1 ON THEN
LCD1.
OCCUPANCY = 2
ENDIF
IFONCE SCH1 OFF THEN
LCD1.
OCCUPANCY = 1
ENDIF
Note: It is recommended practice to place this program strategy within an appropriate DoEvery .
Document Edition 4.1
Page 39 of 41
DNT-T103 & DNT-T221 Application Guide
Programming Notes (LINKnet)
The following provides additional important programming information.
C OMMANDING V ARIABLES : When commanding all other variables for LINKnet devices from
GCL++ in an Application Controller write your programs so they are not being commanded on every program scan. Use I F O NCE or D O E VERY statements to key execution to specific events or time intervals, and thereby limit the frequency of such commands.
N OTE : This is not quite the same issue when controlling the LCD display by commanding properties of the LCD object in GCL+ programming. You may command these values and properties as often as you require, but it is still recommended practice to use D O E VERY statements. And of course, you may read any object value as often as you can – there is no issue with reading.
GCL+ P ROGRAMMING WITH T EMPERATURE U NITS : It is possible in GCL+ programming to specify the temperature units when writing to lines 2 and 3 of the LCD display. Here is a table of example programming, which is dependent on the firmware version loaded in the Application Controller.
Description GCL+ used with V3.22
Firmware
GCL+ used with V3.30
Firmware
Temperature on line 2 with º symbol:
Temperature on line 3 with ºC symbol:
Temperature on line 3 with ºF symbol:
LCD101.LINE2 = AI101 &
“^”
LCD101.LINE3 = AI101 &
“^C”
LCD101.LINE3 = AI101 &
“^F”
LCD101.LINE2 = AI101
LCD101.LINE2UNITS = 1
LCD101.LINE3 = AI101
LCD101.LINE3UNITS = 2
LCD101.LINE3 = AI101
LCD101.LINE3UNITS = 3
GCL++ P ROGRAMMING TO R ESET THE K EY P RESS V ALUE TO 0: Normally the KeyPress value
(AVx04) only changes when a new button or button-combination is pressed, and under these conditions it is not possible to detect that the same button has been pressed again. With Release 3 firmware you can now reset the KeyPress value after you have read it, allowing you to detect when the same button gets pressed again. The following is an example of resetting the KeyPress value back to zero (using a mapped AV in the DAC), assuming you have already read the value.
AV104 = 0 [where AV104 is the mapped AV in the DAC associated with BACstat #1]
Note : Keypress value is not updated while the BACstat is in Configuration or Service Tool Menu.
GCL+ P ROGRAMMING & K EY P RESS V ALUES : In GCL+ programming you can evaluate the
KeyPress object to determine which BACstat button has been pressed, or any 2-button combination.
Where two buttons are pressed, the first button represents the hundreds digit and the second button represents the units digit of a 3 digit number. Note that processing KeyPress values is disabled when using the Configuration or Service Tool menu. Here is the list of KeyPress values.
If the display code is enabled AVx15 (>1111) use Avx04, from the BACstat, to evaluate the Key presses. If the display code is disabled (1111) use the LCDx01.Key press, from the DAC, to evaluate the Key presses.
Button Value Button Value Button Value Button Value Button Value
O
I
▼
▲
1
2
3
4
O + I
O +
O +
▼
▲
102
103
104
I + O
I +
I +
▼
▲
201
203
204
▼ + O
301
▼ + I
302
▼+ ▲
304
▲ + O
401
▲ + I
402
▲
+
▼
403
Page 40 of 41 Document Edition 4.1
Delta Controls
Document Edition 4.1
Page 41 of 41
Ladda ner
Annons