Installation & Operation Manual - Model AVR6000
Contents of this Manual are Subject to Change Without Notification
Page 51
AVR6000 BACnet Points List Notes
Note 1
: Writing a value of (1) to the BACnet Object BV1 will cause the controller to copy the active
configuration stored in volatile (RAM) memory and write it to nonvolatile (Flash memory). Nonvolatile
Flash memory has a limited number of Lifetime Write Cycles. Reference Section 7.1.1 for details.
Note 2
: The AVR6000 Controller can operate in 4 different setpoint control modes, each of which is briefly
described in the table. BACnet object MSV1 is used to identify and select which mode the controller is
operating in. The AVR Dry Contact Inputs, DI-1 and DI-2 can also be used to switch between modes.
Note 3
: The AVR control module includes a USB port and an optional Bluetooth transceiver to provide local
connectivity for configuring the AVR using the PC based software tool “Insight”. For BACnet operation, the
PC USB and/or Bluetooth must be disconnected from the AVR controller to avoid communication conflicts.
Note 4:
The points list will reflect the points that are active based on the App Configuration.
7.1.1
Save Active Configuration to Nonvolatile Flash Memory
The AVR has both volatile (RAM) and nonvolatile (Flash) memory types. RAM memory
has an infinite number of write cycles however Flash memory has a finite number of
write cycles which if exceeded will damage the device. RAM memory is used by the
controller to store and retrieve active values which are to be used for control. Any
values in RAM are lost when the controller is powered down. The values stored in Flash
memory are copied to RAM memory during the power up sequence of the controller.
Writing a value of one (1) to the BACnet Object BV1 will cause the controller to copy the
values stored in RAM to Flash memory, which is retained through power cycles. To
protect the microcontroller from damage due to excessive flash writes, the AVR
controller limits the number of flash write cycles to 10,000. The number of write cycles
remaining are counted and made available via BACnet Object AI7.
7.2
Commanded Points
Object AO1- AO7 supports BACnet command prioritization for writable Present_Values.
These AOs shall include the Priority_Array and Relinquish_Default properties and their
corresponding behaviors with respect to controlling the value written to the object’s
Present_Value. The AVR proactively manages each of these Priority_Arrays and updates the
Present_Value accordingly.
7.3
Unsubscribed COV
The AV12 object Present_Value shall specify an interval in whole seconds at which the AVR
shall periodically issue Unsubscribed COV Notifications as local segment broadcasts. An
AV12 value of zero shall disable this behavior. When non-zero, the Unsubscribed COV shall
also be issued if the Present_Value of any object changes by more than the
COV_INCREMENT for the corresponding object. If COV_INCREMENT is zero for a given
object, it shall also disable Unsubscribed COV for that object, even if AV12 is non-zero.
7.4
COV
The AVR supports a pool of 40 subscription resources that may be applied to track COV
subscriptions for change of value of any of the objects; AI1, AI2, AI3, AI4, AI5, AI6, AI7, AV1,
or
AO1. Each subscription shall include the objectID, the last transmitted value, the
remaining subscription lifetime in seconds, the subscriber process ID, a flag indicating
whether confirmed or unconfirmed notifications should be used and the (network number,
MAC address) of the subscriber.
