Error! No text of specified style in document. DNS-24, DNT-T103, & DNT-T221 Application Guide
Page 10 of 35
Document Edition 3.1
NOTE: The DNS-24 model does not have any extra inputs, any outputs, and does not support
control applications, so it only contains a subset of these objects (highlighted in bold).
The DNT-T103 and DNT-T221 models support the full compliment.
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 seven 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). With a BACstat that has additional I/O, 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 FIRMWARE: All GCL programming for mode changes, data exchange, and other
strategies must be written in the DCU.
W
ITH 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, and the Programming Notes on page 34.
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.
To Next Page
Loading...
Need help?
General
