Viconics VT8600 Series BACnet Integration Guide - Manual (Page 31)

VT8600 Series BACnet
®
Integration Manual 31
Viconics Technologies Inc. | 9245 Langelier Blvd. | St.-Leonard | Quebec | Canada | H1P 3K9 | Tel: (514) 321-5660 | Fax: (514) 321-4150
028-0437-00 www.viconics.com | [email protected] March 2015
©
2
01
5 V
ic
onic
s T
ec
hno
lo
gi
es
Inc
. A
ll r
ig
ht
s r
ese
rv
ed
.
Note C1)
Configuration Properties and User HMI objects.
The behaviour is similar to the behaviour described in NOTE C with the following exceptions and changes
When writing and binding to the priority array 1 to 3, the controller WILL store and archive to flash memory. As
soon as the new present value is received in priority array 1 to 3, the controller will use this new present value
in all its internal control logics and functions.
When writing and binding to the priority array 1 to 3, the controller internal control logics and functions ARE
bypassed the same way they are when writing to priority array 4 to 16. The controller will NOT operate with
its own present values, but will be forced to use the last write commands received on priority array 1 to 3
for its built-in internal control logics and functions.
HOWEVER, since writing to priority array 1 to 3 will store
the value in flash memory, if a power reset occurs, the override type function will be maintained and the
controller will start to operate right away using the last value written to priority array 1 to 3.
The ONLY way to release the override due to the use of writing to priority array 1 to 3 is to send a write NULL
command to the proper priority array currently locking the controller. Only then will the controller start using the
relinquish default value and allow the user or installer to change values.
Note D)
Status objects and Physical hardware output objects.
No override functions are effective when writing or binding to the relinquish default property of status objects
and physical hardware output objects. When writing to the relinquish default property, the internal program is
not bypassed and still has priority over the write command on the relinquish default property.
The internal program constantly writes internally to the same location used by the relinquish default property
hence a single BACnet write at relinquish default has no effect on status objects and physical hardware output
objects.
Status and outputs
are processed by the
controller for normal
operation
BACnet Relinquish
Default network write
Internal controller program
under normal operation
BACnet Relinquish
Default value