Delta Controls
Document Edition 4.1
Page 35 of 41
A
CTIVE
A
LARMS
: Not supported at this time.
N
OTE
:
Loading databases between different models may cause database
load failures. For example, DNT-T103
↔DNT
-H103
↔ DNT
-T221, etc.
Load
This provides the capability of loading a BACstat file (which you have previously saved) into a
BACstat, and in so doing will configure it with the settings contained in the file. You can reload the file
either back into the source BACstat or into another BACstat. You can even use the same BACstat file to
load into multiple BACstats and thus copy the same configuration settings from one device to another.
Refer to Copying in item 3 above.
Save As
This provides the ability to save the BACstat object names and values to a file. You are not saving the
entire object structure as is done when saving DCU or Application Controller databases – you are only
saving object properties (names and values) – an important distinction since you cannot create or delete
objects in a BACstat. But since all the essential configuration information is contained in object values,
you are in fact saving the BACstat
configuration
to a file.
APPENDIX A: Programming Notes
The following provides additional important programming information.
1.
C
ONFIGURATION
V
ARIABLES
(AV12 & AV21-23):
These variables should never be
commanded on the fly from a GCL+ program (or user command). They must be
configured in the proper sequence and they radically alter operation too much to make
frequent changes. Besides, changing the application configuration from an OWS requires
that you reset the BACstat (either locally or via user command). Also refer to the
Configuration Menu options on page 4 for further information.
2.
C
OMMANDING
V
ARIABLES
:
When commanding other variables (such as setpoints and
alg mode) from GCL++ in an Application Controller write your programs so they are not
being commanded on every program scan. Use
IFONCE
or
DOEVERY
statements to key
the execution of specific events or time intervals, and thereby limit the frequency of such
commands. Otherwise you will create excessive network traffic.
3.
C
OMMAND
P
RIORITY
:
Both GCL+ programs and user commands (i.e., manual mode)
have the same
write
priority for all objects in a BACstat. There are no priority arrays or
command hierarchy. Whatever commands the object last is the value the object will have.
Therefore, write your GCL+ programs so as to minimize any conflicts with acceptable
user commands (such as temporary or fixed overrides).
4.
GCL++
P
ROGRAMMING TO
R
ESET THE
K
EY
P
RESS
V
ALUE TO
0:
Normally the
KeyPress value (AV4) only changes when a new button or button-combination is pressed,
and under these conditions it is not possible to detect that the same button has been
pressed again. With Release 3 (and higher) firmware you can now reset the KeyPress
value after you have read it, allowing you to detect when the same button gets pressed
again. The following is an example of resetting the KeyPress value back to zero (using a
mapped AV in the DAC), assuming you have already read the value.
AV104 = 0
[where AV104 is the mapped AV in the DAC associated with AV4 in
BACstat #1]
