Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

The bCX and b3 controllers are BACnet compliant, why do they not support all defined BACnet object types?

Issue

 The bCX and b3 controllers are BACnet compliant, why do they not support all defined BACnet object types?

Environment

Continuum BACnet

3rd Party BACnet Device

Cause

Misunderstanding of what BACnet compliant means and/or misinterpretation of BACnet Product Information Conformance Statement (PICS).

Resolution

BACnet compliant devices are not required to support all of the defined object types. However, if an object is supported it must comply with the standard object model for that object type. This includes a number of required as well as optional properties.

The PICS for a BACnet device is used to define what LAN options the device supports as well as supported objects and optional properties (it’s implied that the required properties are supported and these may or may not be shown in the PICS).

In our current products, we do not support some optional objects such as Life Safety Point and Life Safety Zone, this is clearly stated by the omission of  these objects in our device PICS.

Looking at our bCX1-CR as an example, we support 19 of the optional standard BACnet object types.

The list of those objects below was taken from our device PICS located here.

Tags (1)
Labels (1)
Version history
Revision #:
3 of 3
Last update:
a week ago
Updated by:
 
Contributors