BACnet Fire 3rd Party Library
The BACnet Fire 3rd Party extension is the common library required to allow integrating BACnet Fire 3rd party devices in Desigo CC.
Safety functions
Observe all applicable standards for the country as well as regional or local regulations when integrating safety functions.
Dependencies
The BACnet Fire 3rd Party extension is configured to depend on the following extension, which will be automatically added, if it is not already installed in the system, when the BACnet Fire 3rd Party installation feature is selected:
- Fire Domain Libraries Common
To be able to work with EDE files, you must manually add the following extension:
- Desigo System (Core)
Engineering for BACnet Fire 3rd Party Devices
BACnet Fire 3rd party devices data can be configured in Desigo CC in one of the following ways:
- Online engineering. In online mode, the panel must be connected to the management station and from there you can start the discovery of the devices online data. For instructions, see Integrating BACnet Fire 3rd Party Devices Through Online Discovery.
- Offline mode. In offline configuration, you prepare an Engineering Data Exchange (EDE) file that contains BACnet devices project data and then you import the configuration. For instructions, see Integrating BACnet Fire 3rd Party Devices Through Offline Configuration.
Before performing the online discovery or offline configuration, a BACnet driver and network must be created.
Avoid potential data loss
Use the same configuration type for each manufacturer and network to avoid potential data loss.
Type of Configuration | Engineering | Advantage | Disadvantage |
Online discovery | For online engineering, Desigo CC is connected to the devices and you perform an online discovery of project data. |
|
|
Offline import | For offline engineering, you must edit and import an Engineering Data Exchange (EDE). An online connection with the BACnet device is not required. |
|
|
PICS
The Protocol Implementation Conformance Statement (PICS) document lists all devices of the manufacturer and describes the supported BACnet Interoperability Building Blocks (BIBBs), object types, characters sets, and options of communication. PICS of the respective manufacturers are listed here:
The following PICS documents are available for vendors’ devices:
- BACnet Advanced Operator Workstation (B-AWS)
- BACnet Building Controller (B-BC)
- BACnet Advanced Application Controller (B-AAC)
- BACnet Application Specific Controller (B-ASC)
- Other BACnet Devices (B-Oth)
Supported Object Types
Both online discovery and offline import support standard BACnet objects only. This means that BACnet extensions made by the manufacturer are not supported by these Desigo CC features. The current version supports the defined BACnet objects in the following library: Project > System settings > Libraries > Fire (HQ) > Devices > BACnet > Object models.
Object Models and Object Types in the Library Fire_Device_BACnet_HQ_1 | ||
Object Model | Short Name | Full Name |
GMS_BACNET_EO_FI_AI | AI | Analog Input |
GMS_BACNET_EO_FI_AO | AO | Analog Output |
GMS_BACNET_EO_FI_AV | AV | Analog Value |
GMS_BACNET_EO_FI_BI | BI | Binary Input |
GMS_BACNET_EO_FI_BO | BO | Binary Output |
GMS_BACNET_EO_FI_BV | BV | Binary Value |
GMS_BACNET_EO_FI_DEV | DEV | Device |
GMS_BACNET_EO_FI_LSP | LSP | Life Safety Point |
GMS_BACNET_EO_FI_LSZ | LSZ | Life Safety Zone |
GMS_BACNET_EO_FI_MSI | MSI | Multistate Input |
GMS_BACNET_EO_FI_MSO | MSO | Multistate Output |
GMS_BACNET_EO_FI_MSV | MSV | Multistate Value |
GMS_BACNET_EO_FI_NC | NC | Notification Class |
GMS_BACNET_EO_FI_SV | SV | Structured View |
Supported EoTypes and Functions from EDE File
The EDE file contains a list of items where you can set a specific Function and EoType for fire objects.
For details, see BACnet Fire 3rd Party EDE File Formats.