Delta Controls
Document Edition 4.1 Page 39 of 41
3 = Fan with Wave 1 & Wave 2
4 = Fan with Wave 1, Wave 2, Wave 3
0 = Heating icon is turned off
1 = Heating icon is turned on
0 = Cooling icon is turned off
1 = Cooling icon is turned on
0 = Humidity icon is turned off
1 = Humidity icon is turned on
0 = Calibrate text is turned off
1 = Calibrate text is turned on
0 = On text is turned off
1 = On text is turned on
0 = Off text is turned off
1 = Off text is turned on
0 = Time text is turned off
1 = Time text is turned on
0 = Min text is turned off
1 = Min text is turned on
0 = Max text is turned off
1 = Max text is turned on
0 = Set text is turned off
1 = Set text is turned on
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.
Examples
IF SCH1 ON THEN
LCD1.OCCUPANCY = 2
ELSE
LCD1.OCCUPANCY = 1
ENDIF
Note
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).
: It is recommended practice to place this program strategy within an appropriate DoEvery.
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.