Delta DNS-14 User guide

Document Edition 1.9 Page 1 of 12
INSTALLATION & APPLICATION GUIDE
Delta Network Sensor: BACstat I
DNS-14 (Rev 1.6)
Document Edition 1.9
Product Description
The DNS-14 BACstat I is an intelligent room sensor with four buttons and
a 3-digit LCD display that is used with Delta’s product line of BACnet
Application Controllers. It is capable of communicating on Delta’s
proprietary LINKnet network or directly on a BACnet MS/TP network
using the MS/TP BACnet protocol.
When connected to an Application Controller on a LINKnet network the
DNS-14 provides programmable remote sensor capabilities to the
controller. Up to 12 devices may be connected to the LINKnet network,
depending on the controller, where associated BACnet objects located in
the Application Controller make the DNS-14 accessible to the rest of the
system. These same objects in the Application Controller are used in
programming each DNS-14 for various functions and applications.
When connected on an MS/TP network the DNS-14 functions as an independent Native BACnet sensor
device, similar to any other MS/TP device. Each DNS-14 is configured for operation (including the use of its
buttons and display), and can receive commands for mode and setpoint changes from another device across
the network (i.e., DCU or other System Controller with V3.22 firmware).
Model Numbers
Product Number Product Description
DNS-14 Standard Model (with default button template)
The appended button template codes specify the desired icons embossed on the template as follows:
[default] Bottom 2 buttons are ▼and ▲(Setpoint Adjust), top 2 are OFF and ON
INT Bottom 2 buttons are ▼and ▲(Setpoint Adjust), top 2 are Oand I– International
Package Contents
•Delta Network Sensor: BACstat I Product, DNS-14 (Rev 1.6)
•DNS-14 (Rev 1.6) Installation Guide

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 2 of 12 Document Edition 1.9
Other Relevant Documents
•RS-485 Network Installation Guide (DOC818-11)
•ORCAview Operator Guide (V3.21 or later)
•ORCAview Technical Reference Manual (V3.22 or later)
•Release Notes for V3.21 Firmware, V3.22 Firmware, and BACstats
Product Specifications
Power Requirements
•24 VAC
•2 VA
•Class II
Ambient Ratings
•32º to 131º F (0º to 55º C)
•10 to 90% RH (non-condensing)
Communication Port
LINKnet Connection
•Communications Speed @ 76,800 bps
•Maximum of 12 devices (depending on the controller)
BACnet MS/TP Connection
•Communications Speed @ 9,600 or 19,200 or 38,400 or 76,800 bps (the default)
•Maximum of 99 nodes per MS/TP segment (50 without a repeater)
Input (Temperature Sensor)
•Thermistor Input – 10,000 ohm @ 77 ºF (25 ºC)
•Accuracy of +/- 0.36 ºF from 32 - 158 ºF (+/- 0.2 ºC from 0 - 70 ºC)
•Display Resolution of 0.1 º
•Stability of 0.24 ºF over 5 years (0.13 ºC)
Technology
•8-bit Processor c/w internal A/D, Flash, and RAM
•3-digit LCD (7 segment characters)
•4 momentary push buttons with tactile feedback
Device Addressing
LINKnet Connection
•Set via Keypad Configuration Setup
•Address Range: 1 to 12
BACnet MS/TP Connection
•Set via Keypad Configuration Setup, or Software Setup
•Keypad Address Range: 1 to 99 per network segment
•Software Address Range: As per the BACnet standard
•Supports DNA – Delta’s intuitive addressing scheme

Delta Controls
Document Edition 1.9 Page 3 of 12
Size
•4.5” x 2.75”x 1” (11.4 cm x 7 cm x 2.5 cm)
Weight
•0.16 lb. (71 g.)
PCB Board Layout & Wiring
NOTE: Do not use 4-wire multi-conductor cable. It will not meet the balanced cable
requirements for the MS/TP or LINKnet networks. Use two separate cables: one for
the network and the other for power.
Network
2-Wire Connection
(MS/TP or LinkNet)
Power
2-Wire Connection
(24 VAC)
Network Notes:
!
Ensure you use the specified balanced cable
and follow documented RS-485 installation
guidelines for MS/TP or LinkNet networks.
!
Do not terminate the shield on the BACs tat,
but ensure conductivity is maintained.
Power Notes:
!
If connected to LinkNet, Power may be
supplied from the Power Out port on a DAC
product.
!
Ensure polarity is observed when the same
transformer is connected to more than one
device.
!
If the same transformer is used for more than
one device, ensure it is sized properly.

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 4 of 12 Document Edition 1.9
Mounting
The DNS-14 backplate is designed for mounting directly on a standard North American electrical box, but
may be mounted in other ways as well.
Power
The DNS-14 BACstat requires a 24 VAC @ 2 VA power supply, typically an isolated Class II transformer.
More than one device – not including DCUs or V2 products – may be connected to the same transformer,
providing the transformer is properly sized, including line losses, and polarity is observed between controllers
(in regards to 24~ and GND). The transformer must ONLY be used to provide power to other MS/TP or
LINKnet devices. Auxiliary field devices (i.e., 4-20 mA devices) that don’t use ½ wave rectification must be
powered separately.
Network & Cabling Requirements
To ensure network stability and reliable communications, particularly at high speeds on the RS-485 MS/TP or
LINKnet networks, it is imperative that you adhere to the following network and cabling requirements:
Item Description
Cabling For MS/TP and LINKnet networks it is recommended that you use network cabling that
matches the following specifications:
•Balanced 100 to 120 ohm nominal impedance Twisted Shielded Pair (TSP) Cable
•Nominal capacitance of 16 PF/FT or lower
•Nominal velocity of propagation of 66% or higher
Topology For MS/TP and LINKnet networks, ensure the cable is installed as a daisy-chain from one
device to the next.
Max. Nodes •MS/TP: The maximum number of devices per MS/TP network without any repeaters is 50.
•LINKnet: The maximum number of devices per LINKnet network is 12, depending on the
Application Controller used. Refer to Appendix G in the Technical Reference Manual.
Termination
Boards •MS/TP: A termination board (TRM-768) must be installed at each end of each MS/TP
network segment – or two per MS/TP or LINKnet network. Ensure you do not overlook this
in laying out your network architecture and ordering product.
•LINKnet: Termination boards need not be installed for only one or two nodes.
However, install a termination board on each end of the network when there are more
than 2 nodes.
Repeater •MS/TP: A repeater (RPT-768) is not necessary unless more than 50 nodes will be installed
on a network or you need to extend the network beyond 4000 ft (1220 m).
•LINKnet: Repeaters should not be necessary. Ensure the maximum distance is no
more than 1000’ (300 m).
For more detailed information, including wiring, refer to the RS-485 Network Installation Guide (DOC818-11).

Delta Controls
Document Edition 1.9 Page 5 of 12
Network Topology
1. BACstats Configured as MS/TP Subnet Devices
With V3.21 firmware or higher, one possible MS/TP network architecture has the MS/TP devices configured as
Subnet devices, allowing BACstats to reside on the MS/TP network with other Subnet devices. Note that
V3.21 requires a DCU, while V3.22 or higher may use any System Controller instead.
2. BACstats Configured as LINKnet Devices
The BACstat may reside on LINKnet instead of MS/TP. However, this requires a controller that supports a
LINKnet network for I/O expansion. The maximum LINKnet devices with or without I/O depends on the
controller.
DCU/DSC
(System Device)
BACnet (MS/TP) - Level 3 Network (Subnet)
DAC
(Subnet
Device)
TRM
DAC
(Subnet
Device)
TRM
Level 4
Network
(LINKnet)
!
16x16 Controller
!
12x12 Controller
!
12x8 Controller
!
6x6 Controller
!
Room Controller
!
VAV/VVT Controller
!
Lighting Controller
!
BACstat I
!
BACstat II
(with or without I/O)
!
Input Field Modules
Subnet Devices
!
DSC-1616EX [DCU]
!
DSC-1616(H/E)
!
DSC-1212(H/E)
!
DSC-1280(H/E)
!
DSC-T305
System Devices RS-485
NET1 NET2 NET1 NET2
RS-232
!
BACstat I
!
BACstat II
(with No I/O)
!
BACstat II
(with muxed I/O)
!
I/O Field Modules
LINKnet Devices
TRM
Level 4
Network
(LINKnet)
DFM
DFM
TRM
LINKnet Notes:
1. Ensure you use the recommended
balanced cable.
2. Ensure the cable is installed as a
daisy-chain from one device to the
next. (1000' or 300m maximum).
3. Ensure you install MS/TP terminator
boards when you have more than 1 or
2 devices.
4. Depending on the controller, up to 12
devices are supported on a LINKnet
network, with limitations on how many
of these may have I/O. (Refer to
the Technical Reference Manual.)
ORCAview
OWS
DFM
Ethernet Note:
If the DCU or DSC has Ethernet capability, it may exist on an
Ethernet network with other controllers in the same building, on which
the ORCAview OWS could reside as well (instead of PTP).
PTP
MS/TP Notes:
1. Ensure you use the recommended balanced cable.
2. Ensure the cable is installed as a daisy-chain from one device to
the next (4,000' or 1220m maximum).
3. Ensure you install an MS/TP terminator board (TRM-768) on each
end of each MS/TP network.
4. The maximum nodes per MS/TP network is 50 without a repeater,
or up to 99 with at least one repeater (RPT-768).
Network Diagram
(with V3.22 Firmware)

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 6 of 12 Document Edition 1.9
Network Communications Setup
BACstats communicate on an MS/TP network at a default speed of 76,800 bps. Refer to the ORCAview
Technical Reference Manual for further detail on configuring the MS/TP network or changing baud
rates, etc.
On LINKnet, BACstats communicate at 76,800 bps. Refer to the ORCAview Technical Reference
Manual for further detail on the NET1 object located in the MS/TP Application Controller.
Device Configuration
1. Configuration Menu PIN Access Code
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.
•When the Pin
PinPin
Pin text is displayed you are being prompted for the valid PIN or access code, a pre-configured
4-digit code, which you must enter before you can gain access to the Configuration Menu. The buttons on the
left side of the Stat 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.
NOTE: The PIN access code, contained in AV31, can be changed through the OWS when the BACstat is
connected to an MS/TP network, but not over LINKnet or through the keypad.
•Once you have entered the valid 4-digit code you will gain access to the Configuration Menu, and CFg
CFgCFg
CFg 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 10 seconds), the process will be aborted and you will be returned to normal
display mode.
2. Button & Navigation Functions
The Button functions are as follows within the Configuration Menu:
Button Description
Top Left •Represents a value of 0 when entering the PIN access code.
•ESC (or abort) the current setting (and go to the next menu item, without making
any changes).
Top Right •Represents a value of 1 when entering the PIN access code.
•ENTER the current setting (and go to the next menu item).
Bottom Left
(Down: ▼)•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.
Bottom Right
(Up: ▲)•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.
Both Arrows
(▼and ▲)•ENTER, both simultaneously (an alternate method, particularly necessary for
2-button models, or when entering the PIN).

Delta Controls
Document Edition 1.9 Page 7 of 12
Use the arrow buttons to navigate through the menu options. Once you have navigated to the desired item you
wish to display or change, wait a brief moment for the current value to begin blinking, whereby you can use the
arrow buttons to make any necessary changes. Once the changes are made or you wish to move on, press ENTER.
3. Configuration Menu Options
The Configuration Menu is a list of items which you can navigate through and make changes to as you need for
setup purposes. You may use either the down arrow or the up arrow to navigate through the menu items (in
direct or reverse order). Waiting momentarily on an item will eventually display the current setting and allow
you to make changes. The Configuration Menu items are as follows:
Menu Item Description
CFg
CFgCFg
CFg Displayed momentarily to indicate you have successfully entered the Configuration
Menu.
DEG
DEGDEG
DEG The Temperature Units Setting (C or F).
DSP
DSPDSP
DSP The LCD Display Code Setting (AV15) configures local display and button
handling and has the following definitions:
1.0 No Value. The LCD & buttons are fully available for remote programming.
2.0 Local Temperature (AI1) only is always displayed.
3.0 Local Setpoint (AV6) only is always displayed, and can be adjusted.
4.0 Temperature is displayed by default, and pressing an arrow button displays
the Setpoint for adjustment.
5.0 Temperature and Setpoint are alternated on the display every 2 seconds, until
pressing an arrow button displays just the Setpoint for adjustment.
6.0 Setpoint only is always displayed, but cannot be adjusted.
7.0 Temperature is displayed by default, and pressing an arrow button displays
the Setpoint for 3 seconds but cannot be adjusted.
8.0 Temperature and Setpoint are alternated on the display every 2 seconds, but
the Setpoint cannot be adjusted.
NOTE: When connected to LINKnet the Display Code should be set to 1.0 (whereby
the display and buttons are controlled through GCL in the host DAC device), while
a setting of 4.0 is a typical choice when connected directly to an MS/TP network.
Lnt
LntLnt
Lnt The LINKnet Communications Setting (On or Off), to match the connection
method. When turned On the network communications is set to LINKnet, and when
Off the communications is set to MS/TP.
dNA
dNAdNA
dNA The DNA Setting (On or Off), for inheriting a derived address from higher-up
devices on an MS/TP network, or not.
Add
AddAdd
Add 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 LINKnet, this address is the physical address for the device
(limited to 1 to 12) and the other address settings are irrelevant. Note: On MS/TP
the complete BACnet address is in the form of “OEM_Area_System_Subnet”
SYS
SYSSYS
SYS The System number (0 to 99), which can only be set manually when on MS/TP and
DNA is turned off – and is inherited when DNA is on.
ArE
ArEArE
ArE The Area number (0 to 99), which can only be set manually when on MS/TP and
DNA is turned off – and is inherited when DNA is on.
OEM
OEMOEM
OEM The OEM number (0 to 3), which can only be set manually when on MS/TP and
DNA is turned off – and is inherited when DNA is on.
BAU
BAUBAU
BAU The Network Speed (9,600 or 19,200 or 38,400 or 76,800 bps). The default for both
LINKnet and MS/TP is 76,800 bps. While the baud rate for MS/TP devices may
need to be adjusted to suite, the speed for LINKnet networks should remain at
76,800 bps.

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 8 of 12 Document Edition 1.9
Menu Item Description
End
EndEnd
End To exit the Configuration Menu (Yes or No). Otherwise, if you do not press a
button within 1 minute the device will automatically exit and return to its display
mode. All changes are always saved (or set) however you exit.
Calibration Mode (for the Temperature Sensor Value)
•To enter Calibration mode, first press the Down Arrow (▼), and then the Up Arrow (▲), and hold them
both down for at least 5 seconds. No PIN or access code is required to enter into Calibration mode.
•You may now adjust the calibration of the temperature from -9.9 to 99.9 (which acts as a bias to the display
value) using the Down (▼) and the Up (▲) Arrows.
•Press the ENTER button sequence to accept the adjusted value and exit Calibration mode.
Application Notes
OBJECTS
The following is a list of predefined or “fixed” objects that reside in the DNS-14, which you cannot create
or delete. When connected to an MS/TP network, these objects are readily accessible over the network.
When connected to a LINKnet network, many of these objects are mapped into matching AI or AV objects
residing in the Application Controller above.
Object Name Description Default Value
DEV1 BACstat * Device Object N/A
AI1 Temperature Input 1 (10K Thermistor Value) N/A
AV4 KeyPress KeyPress Value N/A
AV5 External * External Object Value (i.e., OAT) N/A
AV6 Setpoint Room Setpoint ºC = 21; ºF = 71
AV7 Day Min Minimum Adjustable Day Setpoint ºC = 18; ºF = 65;
AV8 Day Max Maximum Adjustable Day Setpoint ºC = 25; ºF = 77
AV13 Alg Mode Algorithm Mode 0 (Off or Night)
AV15 Display Code Local Display & Button Handling 1 (Disabled)
AV16 AI1 Calibration Input 1 Calibration (Temperature) 0.0
AV30 Baud Rate Network Baud Rate 76,800 bps
AV31 PIN PIN (Configuration Access Code) 1011
* Names are User settable (to a maximum of 8 characters)
PROGRAMMING
MS/TP CONNECTION
Objects
All of the predefined objects are readily accessible over the MS/TP network. Note that you can
modify the name of some of the objects to something perhaps more suitable for the application.

Delta Controls
Document Edition 1.9 Page 9 of 12
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 DNS-14 display and
buttons to functional locally, so GCL programs are not necessary for handling the display value or
adjusting setpoint (i.e., AV15 = 4.0). 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.
WITH V3.21 FIRMWARE: All GCL programming for mode changes, data exchange, and other
strategies must be written in the DCU.
WITH V3.22 FIRMWARE OR HIGHER: A DCU is no longer necessary and since data exchange is
supported across MS/TP-based products, no specific GCL is required for this. GCL programming
for mode changes or other strategies may be written in any appropriate controller on the network.
Refer to Appendix G in the V3.22 ORCAview Technical Reference Manual for further programming
information.
LINKNET CONNECTION
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 Appendix G in the V3.22 ORCAview Technical
Reference Manual for further information.
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 LinkLCD# Object for BACstat LCD & Button Presses Automatic
AIx01 [User Specified] Object for the 10K Temperature Value Manually
Avx01, 02, etc. [User Specified] Matching object for the corresponding AV Manually
where “x” refers to the device address (1 to 12) multiplied by 100.
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 the Application Controller to represent the 10K thermistor value on a BACstat with a
LINKnet device address of 5.
With V3.22 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.

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 10 of 12 Document Edition 1.9
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 AI1 object is used for reading
the temperature value. And with at least V3.22 firmware on the Application Controller, the mapped
AV objects are used for setpoints and various other settings.
Note: Always use the LCD object for processing button presses over a LINKnet connection,
rather than AV4.
WITH V3.21 FIRMWARE: When connected to LINKnet local display and button handling should be
disabled (i.e., AV15 = 1.0), 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.,
AV15 = 1.0) 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 1.0 (i.e., 4.0, which is
a typical setting), 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. In addition to this, setpoints and other settings are also accessible
through their corresponding AV objects.
Refer to Appendix G in the V3.22 ORCAview Technical Reference Manual for further programming
information.

Delta Controls
Document Edition 1.9 Page 11 of 12
Cautions and Warnings
WARNING
The DNS-14BACstat isan Electro-staticallysensitive device. However, since theelectronics
arecontainedwithinthe housing, and ifsufficient careistaken in handling, properESD
protection (groundstrap) should be unnecessary.
Compliance Declarations
FCC Compliance Information
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to
Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one
or more of the following measures:
•Reorient or relocate the receiving antenna.
•Increase the separation between the equipment and receiver.
•Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
•Consult the dealer or an experienced radio/TV technician for help.
Industry Canada Compliance Statement
ICES-003 This Class B digital apparatus meets all requirements of the Canadian Interference-Causing
Equipment Regulations.
Cet appareil numérique de la Classe B Respecte toutes les exigences du Règlement sur le matérial
brouiller du Canada.
UL Compliance Information
This product conforms to the following UL requirements:
•UL916: Energy Management Equipment

Delta Network Sensor: BACstat I DNS-14 (Rev 1.6) Installation Guide
Page 12 of 12 Document Edition 1.9
CE - DECLARATION OF CONFORMITY
according to ISO/IEC Guide 22 and EN 45014
Manufacturer's Name: Delta Controls
Manufacturer's Address: 17850 56th Avenue
Surrey, British Columbia
Canada
V3S 1C7
declares that the product (s):
Product Name: BACstat I
Model Numbers: DNS-14
Product Options: All
conforms to the following Product Specifications:
EMC: EN 55022:1994 Radiated and Conducted Emissions Class B
EN 50082-1:1997 Generic Immunity Standard
EN 61000-4-2:1995 + A1:1999 ESD Immunity Level A
EN 61000-4-3:1996 RF Electromagnetic Field Immunity Level A
ENV 50204:1995 RF Electromagnetic Field Immunity (Keyed) Level A
EN 61000-4-4:1995 EFT/Burst Immunity Level B
EN 61000-4-5:1995 Surge Immunity Level B
EN 61000-4-6:1996 Conducted RF Disturbances Immunity Level A
EN 61000-4-11:1994 Voltage Dips / Interruptions Level B/C
Supplementary Information:
The product(s) herewith comply with the requirements of the EMC Directive
89/336/EEC. The product(s) were tested in a typical configuration.
Lee Dickson
Quality Assurance Manager