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.
W
ITH
V3.21 F
IRMWARE
: All GCL programming for mode changes, data exchange, and other
strategies must be written in the DCU.
W
ITH
V3.22 F
IRMWARE OR
H
IGHER
: 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.
