Non-Volatile Variables - Delta enteliZONE eZNT-Wi Series Application Manual

Database Objects
enteliZONE products use AV/BV/MVs up to 999 for configuration variables
and up to 9999 for enteliZONE controllers that support Linknet. With the
eZNT-Wi/ eZNTW, it is recommended practice to start at 1000 for user
created variables to avoid future firmware that may include additional
configuration variables in the 1-999 range. Linknet variable are within the
range of 1000 to 4000.

Non-Volatile Variables

Many of the AVs in the previous Variables table are stored locally in non-volatile NFC
memory on the thermostat itself. There are multiple ways that some of these
properties can be changed, but the non-volatile NFC location is the 'master' location.
This allows changes to be made even when the thermostat is powered off; however
this approach can have some unexpected consequences.
These local values can be modified in several ways:
Use an Android NFC App such as Stat Configurator for eZNx specific settings or
l
Net Builder for network and address settings. The thermostat does not need to
be powered on and can even be inside its shipping box. It takes about 10
seconds to configure each controller and so this approach can save significant
time in many cases.
Configure some properties through the on-screen enteliZONE Configuration
l
Menu such as Motion Sensitivity or USB enable/disable.
Change the AV objects in the thermostat controller database.
l
In normal powered operation, the database AV values match the local values stored
on the enteliZONE thermostat.
When changes are made from the database side, they are written to the local
l
thermostat non-volatile memory.
When changes are made from the NFC/Configuration Menu, they are written
l
down to the controller database AVs. If NFC is used while the thermostat is not
powered up, the next time that it is powered up, the changed values are
written to the database variables. If GCL is rewriting to that object, attempted
changes made from the NFC/Config Menu may not actually occur.
When you load a database into a thermostat, the values in the database and the
values in the non-volatile memory may differ. On power-up, an thermostat attempts
to write back its existing local value to the AVs. If values such as On/Off brightness
Page 70 of 126 eZNT-Wi Programmable Wi-Fi Thermostat Application Guide
Edition 1.4