Error! No text of specified style in document. DNS-24, DNT-T103, & DNT-T221 Application Guide
Page 2 of 35
Document Edition 3.1
Other Relevant Documents
• Associated BACstat II Installation Guide (DNS-24, DNT-T103, DNT-221, etc.)
• RS-485 Network Installation Guide (DOC818-11)
• ORCAview Operator Guide
• ORCAview Technical Reference Manual (particularly Appendix G)
• Release Notes for V3.21 Firmware, V3.22 Firmware, V3.30 Firmware, and BACstats
Important Information
This document has been updated to include features and capabilities of Release 3 firmware for BACstat II
products. And although BACstat firmware is independent from ORCAview, DCU, and Application
Controllers, certain BACstat capabilities require support in the other products. It is also important to note
that BACstats are not flash loadable in the field – an upgrade requires swapping out physical product.
1. V3.21
FIRMWARE & SOFTWARE
Note the following issues when BACstats are used with ORCAview, DCU, and Application Controllers loaded
with V3.21 firmware/software.
MS/TP NETWORK CONNECTION
• A DCU is required (to which the MS/TP network is connected)
• Local BACstat display handling and control strategies may be enabled
• All data exchange must be done in GCL programming in the DCU
LINKNET NETWORK CONNECTION
• The BACstat must be connected to an Application Controller that supports LINKnet devices
• Local BACstat display handling and control strategies must both be disabled
• Additional I/O cannot be MUXed
• All functionality for the BACstat must be done in GCL programming in the Application Controller
(i.e., display handling, setpoint adjust, and strategies using the space temperature)
2. V3.22
FIRMWARE & SOFTWARE OR HIGHER
Note the following issues when BACstats are used with ORCAview, DCU, and Application Controllers loaded
with V3.22 firmware/software.
MS/TP NETWORK CONNECTION
• A DCU is not necessarily required (as long as one System device exists on the MS/TP network)
• 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
LINKNET NETWORK CONNECTION
• The BACstat must be connected to an Application Controller that supports LINKnet devices
• Local BACstat display handling may be enabled (so GCL programming in the Application
Controller for setpoint adjust and LCD display is not necessary)
• Local BACstat control strategies must be disabled, as this is more suitable on an MS/TP connection
• Additional I/O may be MUXed
• Additional BACstat strategies may be done in GCL programming in the Application Controller
To Next Page
Loading...
Need help?
General
