VTR8300 AND VT8300 SERIES PROTOCOL IMPLEMENTATION
CONFORMANCE STATEMENT (PICS)
Vendor Name: Viconics Technologies
Supported BACnet
all requirements for designation as an Application Specific Controller (B-ASC). The
BACnet controller supports the following BACnet Interoperability Building Blocks
(BIBBs).
Application ServiceDesignation
Data Sharing – Read Property - BDS-RP-B
Data Sharing – Read Property Multiple - BDS-RPM-B
Data Sharing – Write Property - BDS-WP-B
Data Sharing - Write Property Multiple Service - B DS-WPM-B
Device Management - Time Synchronization - BDM-TS-B
Device Management - Device Communication Control - BDM-DCC-B
The following figure shows which objects from the controller can be monitored and controlled from the BAS front-end.
Global Command Control LevelDevice Level
VTR8300 / VT8300 Series
27
MSTP
Network
BAS
Front End
All Devices(All controllers)
Outdoor Temperature
Outdoor Temperature & Outdoor Humidity (Enthalpy)
Outdoor Temperature and HVAC plant current mode
Specific Devices
(Specific area controllers)
Schedule
Schedule & Outdoor Temperature
VTR8300/VT8300 Series
controller
Outdoor Temperature (AV10)
Dehumidification Lockout (MV13)
Sequence of Operation (MV15)
System mode (AV16)
Occupancy Command (MV10)
Fan Mode (MV17)
Occupied Heating Setpoint (AV39)
Unoccupied Heating Setpoint (AV43)
Occupied Cooling Setpoint (AV40)
Unoccupied Cooling Setpoint (AV44)
Restrict user access to controller
Room temperature for testing and override
Figure 1 : Global commands from a BAS front-end to a typical VT83xx series controller
Main Password (AV56)
Room Temperature (AV100)
Note: For information about integrating ZigBee wireless sensors with BACnet, refer to
the ZigBee wireless sensor installation guide "Pairing VT8000 Series Room Controllers
with ZigBee Sensors"
If your BAS allows you to remove objects, Viconics recommends removing all configuration objects
once your setup is complete. This prevents unnecessary network
polling and traffic.
WIRING GUIDE
Overview
Viconics uses EIA-485 as the physical layer between their devices and supervisory controllers. A
"Device” represents any product with an active EIA-485 network connection, including Viconics and
non-Viconics controllers.
A summary of network specifications are listed below.
1. Devices are installed at both ends of the MS/TP
network: 120 Ohms resistor should be installed at each
end.
2. A device is installed at one end of the MS/TP network
and a third-party device is installed at the other end.
Install an End-Of-Line resistor value that matches the
third-party device instruction regarding the End-Of-Line
resistors.
3. Third-party devices are installed at both ends of
the MS/TP network. Follow the third-party device
instructions regarding the End-Of-Line resistors.
Viconics recommends the use of balanced 22-24 AWG twisted pair with a characteristic impedance of 100130 ohms and capacitance of 30 pF/ft or lower. A braided shield is also recommended.
Impedance
A value based on the inherent conductance, resistance, capacitance, and inductance that represent the
impedance of an infinitely long cable. The nominal impedance of the cable should be between 100 ohms and
120 ohms. Using 120 ohms results in a lighter load on the network.
Capacitance (pF/ft)
The amount of equivalent capacitive load of the cable (per foot basis). One factor limiting total cable length is
the capacitive load. Systems with long lengths benefit from using low capacitance cable (17pF/ft or lower).
NETWORK CONFIGURATION
EIA-485 networks use a daisy chain configuration. A daisy chain has only one main cable and every network
device is connected directly along its path.
Figure 3 illustrates two improper network configurations and the proper daisy chain configuration.
Figure 3 : Three different network configurations: star, bus, and daisy chain. Only the daisy chain configuration is
correct for an EIA-485 network
Other methods of wiring an EIA-485 network may give unreliable and unpredictable results. There are no
troubleshooting methods for these types of networks. Site experimentation may be required with no guarantee
of success. As a result, Viconics only supports daisy chain configurations.
Recommended Maximum Number of Devices
For reasons of network performance, a maximum of 64 nodes is recommended on a single daisy-chain
segment. A node is defined as any device (panel, zone, or Repeater) connected to the RS485 network.
Terminators do not count as a node.
Add the following to determine the number of nodes on a network:
*NOTE: End Of Line resistors do not count as nodes.
31
EOL
Resistor
SC
Supervisory
EOL
Resistor
Controller
Node 1Node 2Node 3Node 4Node 5
Figure 4 : Exa mple Network - 5 Nodes
Figure 4 shows one node for the main SC panel and 4 for the controllers, for a total of 5 nodes. If more than
64 devices are needed on the network, install repeaters to create additional network segments. However, the
BACNet MS/TP protocol may exhibit slow performance on large networks with more than 64 total nodes.
Maximum Cable Length
The maximum length of a chain is related to its transmission speed. The longer the chain, the slower the
speed. Using proper cable, the maximum length of an EIA-485 daisy chain is 4000-ft (1200 m). This only works
reliably for data rates up to 100,000 bps. Viconics' maximum data rate is 76,800 bps.
network length of more than 4000 feet, repeaters are required to extend the network.
EIA-485 Repeaters
If you have more than 64 devices, or require a maximum network length of more than 4000 feet, repeaters are
required to extend the network. Note that long networks or networks with more than 64 nodes may experience
slow performance due to limitations of the BACnet MS/TP protocol.
If you require a maximum
EOL
Resistor
SC
Supervisory
Controller
EOL
Resistor
Repeater
EOL
Resistor
Repeater
EOL
Resistor
Repeater
EOL
Resistor
EOL
Resistor
EOL
Resistor
EOL
Resistor
Figure-5 Correct Repeater Use in an EIA-485 Network
The ideal configuration is to daisy chain the repeaters to the main panel. From each of these repeaters, a
separate daisy chain branches off. Figure 5 demonstrates a valid use of repeaters in an EIA-485 network.
Do not install repeaters in series as this may result in network reliability problems. Incorrect use of a repeater
in an EIA-485 network is illustrated in Figure 6.
Figure-6 Incorrect Repeater Use in an EIA-485 Network
End Of Line (EOL) Resistors
A MS/TP network must be properly terminated. For daisy chain configurations, you must install an EOL
resistor at each end of the daisy chain. Depending on your MSTP network configuration, the resistance value
of the EOL resistor may change.
•If Viconics's devices are installed at both ends of the MSTP network, a 120 Ohm resistor should be
installed at each end.
•If a Viconics device is installed at one end of the MSTP network and a 3rd party device is installed at the
other end, make sure you install an EOL resistor value that matches the 3rd party devices instructions
regarding its EOL resistor value, and install a 120 Ohm resistor at the Viconics device end.
•If 3rd party devices are installed at both ends of the MSTP network, both must use EOL resistors with
values matching the those described in the instructions for the devices.
The polarity of the connection to the cable is important. From one module to the other it is important that the
same colored wire be connected to “plus” or “+” and the other colored wire be connected to the “minus” or
”-“. Figure 7 shows the proper MS/TP connections.
NOTE: The Ref terminal should NEVER be used to wire shields. The 2 shields from each feed of the network
connection to a controller should be wired
any accidental connection to the ground.
The joined shield connection should then be grounded at a SINGLE point on the whole segment. More than
one ground connection to a shielded wire may induce ground loop noises and affect communication.
DEFAULT DEVICE NAME AND ID
Default Device Name set to Model number – MAC where:
•MACisthecurrentMACaddressofthedevice.
•ModelnumberisViconicspartnumber.
The device name upgrades as soon as there is a change to the device MAC address.
The Device Name and Device ID properties are writable. Both properties can be renamed from any BACnet®
network management tool as long as the tool itself can write to these properties.
VTR8300/VT8300 Models
Default Device ID is set to: 83000 + MAC where MAC is the current MAC address of the device.
The device ID upgrades as soon as there is a change to the device’s MAC. For example, when a VTR8300
controller with a MAC address of 63 is connected to a network, its default Device ID is 83063.
INTEGRATING VICONICS DEVICES ON A BACNET MS/TP NETWORK
Before doing any BACnet® integration, make sure you refer to a Viconics PICS document (Protocol Implementation
Conformance Statement). The PICS document lists all the BACnet® Services and Object types supported by a
device. You can find the document at www.viconics.com.
Viconics devices do not support the COV service. COV reporting allows an object to send out notices when its
Present-Value property is incremented by a pre-defined value. Since this is not supported at Viconics, special
attention should be given to the polling time settings at the Supervisory Controller and Workstation level when
using a graphic interface or an application program to read or write to a Viconics object.
Graphical Interfaces
A graphic interface might poll all data linked to the graphic page on a COV basis. If the third-party device does
not support COV, the graphical interface relies on a pre-configured polling interval, which is usually in hundredths
of milliseconds. Any device containing a monitored object could be subject to network traffic congestion if such a
polling interval is used. Viconics strongly recommends a polling interval of 5 seconds (minimum) for any graphical
interface. This becomes even more critical in graphics where a single representation might poll many devices. If
the proper poll rate is not respected, devices may be reported offline by certain front-ends by saturating the traffic
handling capacity of BACnet® MS/TP without COV subscription.
VTR8300 / VT8300 Series
together in the back of the controller and properly protected to prevent
Read and write MS/TP data on an “If Once” basis or a “Do Every Loop" basis instead of reading or writing to a
third-party device’s object directly in the program. Otherwise, any read or write request occurs at the Supervisory
Controller’s program scan rate, which may be in hundredths of milliseconds. This can bog down a network as
single commands can be sent to all ASC devices down the MS/TP trunks every hundredths of milliseconds
Programs writing to the devices should have a structure similar to the following:
If Once Schedule = On then
MV10 = Occupied
End If
If Once Schedule = Off Then
MV10 = Unoccupied
End If
OR
Do Every 5min
If Schedule = On Then
MV10= Occupied
Else
MV10 = Unoccupied
End If
End Do
Retries and Timeouts
In BACnet® integration, you should note the device object of the Supervisory Controller and Operator’s
Workstation. This object contains the two following required properties:
1) Retry Timeout
2) Number of APDU Retries
The Retry Timeout specifies the time between re-transmissions if the acknowledgement is not received.
Increasing this value may help if you are experiencing problems with controllers dropping off line.
The Number of APDU Retries specifies the number of times unsuccessful transmissions are repeated. If the
receiving controller has not received the transmission successfully after this many attempts, no further attempts
will be made.
For example, if one of the controllers does not reply to a Supervisory Controller (SC) request, and the SC’s Retry
Timeout is set to 2000 milliseconds and the Number of APDU Retries is set to 1 (SC level), the SC sends one
other request 2 seconds later. If the MS/TP device does not reply, it is considered off line by the workstation.
Having a Retry Timeout value of 10450 milliseconds and a Number of APDU Retries property set to 3 at the SC
level may prevent the device from dropping off line. These properties should also be changed at the workstation
level since the workstation issues requests to any MS/TP devices when the graphics are used.
Object examples in this category: AI2 / Light Sensor Level, BI29 / UI16 Status, MI33 / Effective Occupancy.
VTR8300 / VT8300 Series
35
All input objects are read only and cannot be written to independently of the priority array used. These types of
points are typically used for statuses and external logic functions.
Note B) Configuration Properties and User HMI objects.
Object examples in the configuration property category: AV57 / User Password, BV6 / Force High Level Backlight, MV2 / HMI color.
Object examples in the User HMI category: AV40 / Occupied Cool Setpoint, MV16 / System Mode, MV17 /
Fan Mode.
Writing and binding to the relinquish default property is the preferred method to use when setting up network
logic using the configuration properties and user HMI objects.
When writing and binding to the relinquish default, the control will store and archive the new written present
value in flash over the network. As soon as the new present value is received, the controller will use this new
present value in all its internal control logics and functions.
When writing and binding to the relinquish default, the controller internal control logics and functions are NOT
by-passed, and the controller will still operate normally.
When writing and binding to the relinquish default, a user can still change user HMI values and an installer
can still change configuration properties. In this case, the present value used by the controller internal control
logics and functions is the last one received. Either the network present value or a value changed locally at the
controller HMI.
Note C) Configuration Properties and User HMI objects.
Writing and binding to the priority arrays 4 to 16 property is a method to use IF the required intent is to lock
the local HMI and prevent local adjustments made by the user HMI values or the configuration property
values. If preventing the local user from accessing or tampering with the local HMI is the goal there are other
simpler and more elegant ways to do so:
• Proper selection of the user experience of the local HMI. AV2 / User HMI can tailor the user screen to
properly present to the user the only local adjustments allowed. In total 12 different HMI user screen
options are available. Locking the object by writing to array 4 to 16 is not required.
• AV56 / Main Password will prevent unauthorized installers from tampering with the configuration
properties. Locking the object by writing to array 4 to 16 is not required.
• AV57 / User Password will prevent unauthorized users from tampering with the user HMI value. Locking
the object by writing to array 4 to 16 is not required.
When writing and binding to the priority array 4 to 16, the control will NOT store and archive to flash memory
and will simply use it in RAM. As soon as the new present value is received in priority arrays 4 to 16, the controller will use this new present value in all its internal control logics and functions.
When writing and binding to the priority array 4 to 16, the controller internal control logics and functions
ARE bypassed, and the controller will NOT operate with its own present values, but will be forced to use the
last write commands received on priority arrays 4 to 16 for its built-in internal control logics and functions.
HOWEVER, since these present values are only stored in RAM and not in flash, if a power reset occurs, the
override type function will be lost and the controller will start to operate using the relinquish default value. If the
override type function is required, a new write command to priority arrays 4 to 16 is needed.
The controller fully supports native and BACnet compliant priority array 1 to 16 write commands. This simply
means that a write value at level 4 has a higher authority than a write at level 9.
When writing and binding to priority array 4 to 16, a user cannot change user
HMI values and an installer cannot change configuration properties. In this case,
the present value used by the controller internal control logics and functions is
the last write command received at priority array 4 to 16.
You can easily identify an overridden point at the controller in either configuration
view, the setpoint view, the service view or the test outputs view. The point will
be highlighted in RED indicating a write command to priority array 4 to 16.
The ONLY way to release the override due to the use of writing to priority array
4 to 16 is to send a write NULL command to the proper priority array currently
locking the controller.
BACnet Priority
Array 4 to 16 value
BACnet Relinquish
Default value
Local HMI
Last
value
in
New present value
process output based
on priority array 4 -16
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.
VTR8300 / VT8300 Series
37
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.
Internal controller program
under normal operaon
BACnet Relinquish
Default value
Status and outputs
are processed by the
controller for normal
operation
Object examples in this category: BV36 / Filter Alarm, AV21 / PI Heating Demand. All status objects are
writable.
Writing and binding to the priority array 4 to 16 property is a method to use IF the requirement is to lock the
controller program and prevent statuses from being flagged based on the internal operation of the controller
application programming.
When writing and binding to the priority array 4 to 16, the control will NOT store and archive to flash memory
and will simply use it in RAM. As soon as the new present value is received in priority array 4 to 16, the
controller will use this new present value in all its internal control logics and functions.
When writing and binding to the priority array 4 to 16, the controller internal control logics and functions ARE
bypassed, and the controller will NOT operate with its own present values, but will be forced to use the last
write commands received on priority array 4 to 16 for its built-in internal control logics and functions. HOWEV-ER, since these present values are only stored in RAM and not in flash, if a power reset occurs, the override
type function will be lost and the controller will start to operate using the relinquish default value. If the override
type function is required, a new write command to priority array 4 to 16 is needed.
The controller fully supports native and BACnet compliant priority array 1 to 16
write commands. This simply means that a write value at level 4 has a higher
authority than a write at level 9.
When writing and binding to priority array 4 to 16, you locally identify if an
override is effective on a status object using the service view. The point will be
highlighted in RED indicating a write command to priority array 4 to 16. In this
case, the present value used by the controller internal control logics is by-passed
and the value displayed and used is the last write command received at priority
array 4-16.
The ONLY way to release the override due to the use of writing to priority array
4 to 16 is to send a write NULL command to the proper priority array currently
locking the controller.
Object examples in this category: BV36 / Filter Alarm, AV21 / PI Heating Demand. All status objects are
writable.
The behaviour is similar to the behaviour described in NOTE E 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.
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.
Writing and binding to the priority array 4 to 16 property is a method to use IF the requirement is to lock the
controller program and prevent physical hardware output objects from being powered based on the internal
operation of the controller application programming.
When writing and binding to the priority array 4 to 16, the control will NOT store and archive to flash memory
and will simply use it in RAM. As soon as the new present value is received in priority array 4 to 16, the controller will use this new present value in all its internal control logics and functions.
When writing and binding to the priority array 4 to 16, the controller internal control logics and functions
ARE bypassed, and the controller will NOT operate with its own present values, but will be forced to use
the last write commands received on priority array 4 to 16 for its built-in internal control logics and functions.
HOWEVER, since these present values are only stored in RAM and not in flash, if a power reset occurs, the
override type function will be lost and the controller will start to operate using the relinquish default value. If the
override type function is required, a new write command to priority array 4 to 16 is needed.
The controller fully supports native and BACnet compliant priority array 1 to 16
write commands. This simply means that a write value at level 4 has a higher
authority than a write at level 9.
When writing and binding to priority array 4 to 16, you locally identify if an override is effective on a status object using the test output view or the service view.
The point will be highlighted in RED indicating a write command to priority array
4 to 16. In this case, the present value used by the controller internal control
logics is bypassed and the value displayed and used is the last write command
received at priority array 4-16.
The ONLY way to release the override due to the use of writing to priority array
4 to 16 is to send a write NULL command to the proper priority array currently
locking the controller.
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.
VTR8300 / VT8300 Series
41
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
• Each controller is delivered from the factory with the default MAC address set at 254. At this value, the
BACnet® communication is not active and the device does not participate in the token pass. To enable the
BACnet® communication, set the local MAC address configuration property of the controller to any valid value
from 0 to 127.
• After the initial configuration of your device and if your BAS allows you to remove objects, you should remove
all configuration objects to prevent unnecessary polling of unused objects and to help speed up the network.
• In default mode of operation, the device automatically matches its baud rate to the baud rate of the network.
Automatic baud rate detection occurs when the MS-TP communication port is initialized (on power up). If the
network speed is changed, the device keeps listening at the previously detected speed for 10 minutes before
resuming auto-baud. Re-powering the devices forces the auto-baud.
• If the device goes off line, the following bound controller parameters are released:
Room Temperature
Outdoor Temperature
Occupancy
• The BACnet® Data Link layer has two key parameters, the device object name and the device object ID. The
device object name must be unique from any other BACnet® device object name on the BACnet® network
(not just the MS-TP sub-network). The device object ID must be unique from any other BACnet® device
object ID on the entire BACnet® network (not just the MS-TP sub-network).
• Time synchronization can be made through a network even if the controller does not support the full date.
Therefore, the device cannot claim conformance to the Device Management – Time Synchronization - B (DMTS-B) service. The device object does not have the Local_Time or Local_Date properties.
• Device Name and Device ID properties are writable in Viconics device objects. Both properties can be
renamed from any BACnet® network management tool as long as the tool itself gives access to write to these
properties.
TROUBLESHOOTING
Error / FaultPossible CauseSolution
Controller does not
come online
Two or more controllers have the same
MAC address.
The MS-TP network has too many
devices.
Too many devices were installed without
any repeaters.
The MS-TP cable runs are brokenLocate the break and correct the wiring.
MS-TP connections at the module are
reversed
The controller does not have powerApply power to the controller
Modify each duplicate address to a unique
number.
Do not exceed the maximum number of devices
and maximum length allowed by the EIA-485
specifications.
For all intents and purposes, BO95 / BO 4 High Speed Fan Output is used on all examples below.
Where BO95 is the object BACnet instance and BO 4 is the terminal location on the controller
Using native Niagara Set Command for an object
Typically when BACnet device objects are discovered under a BACnet device in Niagara, objects are proxied
under the local server database using standard Niagara device and object management processes.
VTR8300 / VT8300 Series
43
As such using the simple add object command, Niagara creates local proxy extensions of certain of the object
properties including the BACnet object present value.
When using the “set” command under Niagara, the local server issues a BACnet write command to the controller without specifying any specific priority array from 1 to 16. As per the BACnet standard, when a controller receives an unspecified write command, the controller automatically assigns it to priority array level 16.
As such, the controller now has an entry in priority array 16 of an object which effectively “overrides” it and
by-passes the local control application program.
The know issue with this is that by default, Niagara does not poll or update any of the priority arrays of an
object and it is NOT reflected under the proxied object property sheet.
So although you do see the real present value of the object under present value “Out” extension of the object,
the displayed priority array 16 “In16” shows a value of NULL. But in effect, it is not NULL.
Viewing if a BACnet array 1 to 16 is actually being used
The only way to positively confirm if a point has an entry in any of the 16 priority array levels is to use the
Niagara BACnet “Config” view. Simply open the view and add the objects as needed.
Now to confirm if there is an entry, simply view the property sheet of the BACnet object.
In this view you will confirm an entry at level 16 or any other priority array level.
VTR8300 / VT8300 Series
45
If the point was overridden by accident and the normal controller operation is required and desired, simply set
the overridden priority array to NULL to resume the controller normal operation under the relinquish default
property value.
Binding to a point using the Fallback
Caution need to be taken when binding objects to specific server logic for central control and applications. The
same cautions that apply to the “set” command apply to the binding of a point using the Niagara “fallback”
proxy extension.
Binding a logic block or function to the “fallback” sets the same behaviour as using the Niagara “set” command.
The local server issues a BACnet write command to the controller without specifying any
specific priority array from 1 to 16. As per the BACnet standard, when a controller receives an unspecified
write command, the controller automatically assigns it to priority array level 16.
As such, the controller now has an entry in priority array 16 of an object which effectively overrides it and by-passes the local control application program.
If the intent of the central logic block or sequence is simply to reset local values and still allow local users to
change certain settings (such as setpoints and system mode for example) then the easiest way is to bind the
logic block to the BACnet relinquish default property value as described below.
Adding the relinquish default object property for binding
In the Niagara point manager under the device, click on the plus (+) icon to expand all the options and
properties of the desired object.
Locate the relinquish default property value and add it to the local server database of proxied objects.
Make sure it is added as a writable object and that it is enabled.
Now when binding your logic block simply point to the relinquish default property of an object at the “fallback”
value. This will directly issue the write command to the relinquish default property value insuring you are not
locking down the application at priority array 16.
VTR8300 / VT8300 Series
47
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.