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

VT8600 Series BACnet
®
Integration Manual 35
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 F1)
Physical hardware output objects.
Object examples in this category: BO95 / BO4 High Speed fan, AO123 / UO11 Analog Status. All physical
hardware output objects are writable.
CAUTION NEEDS TO BE EXERCISED since bypassing the internal
control functions of the controller CAN RESULT in damage to the equipment.
The behaviour is similar to the behaviour described in NOTE F 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, 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.
General Notes on BACnet Writing and Binding Behaviour.
• If in doubt as to whether a point is overridden using BACnet priority array 1 to 16 or not, open the
controller configuration menu, the service view or the test output view. An overridden point will appear in
RED in the tables.
• ALL entries in priority array 1 to 16 MUST be set to “null” if normal operation using the internal control
functions and factory application program is to be used.
• Reinitializing the controller to factory default directly from the configuration interface at the controller WILL
release ANY and ALL write entries into priority array 1 to 16 on ALL objects.
Summary for Integrators
• AI’s, BI’s & MI’s are not writable and are typically only used for status
• Configuration properties and user HMI objects
o Write and bind to relinquish default if you want the local interface to still be able to modify these
settings
o Write and bind to priority array 4 to 16 if you desire to override the local application but not save that
override after a power reset
o Write and bind to priority array 1 to 3 if you desire to override the local application and save that
override after a power reset
• Status objects and physical hardware output objects
o Write and bind to relinquish default has no effect since the internal application program constantly
overrides the last network command value
o Write and bind to priority array 4 to 16 if you desire to override the local application but not save that
override after a power reset
o Write and bind to priority array 1 to 3 if you desire to override the local application and save that
override after a power reset