3rd Party BACnet Integration

The workflow is only necessary if there is no available BACnet driver for the BACnet network for third-party devices.

Creating BACnet Driver

Starting a BACnet Driver

Configure BT BACnet stack

If setting up multiple BACnet drivers, you can assign them to the same network card (Network Interface Card, NIC) or different NICs. To avoid configuration conflicts, apply the following guidelines to the physical port configuration:

• The network number of each physical port must be unique.
• The IP address and UDP port (default: 47808) of each physical port must be unique. This means that the Physical Ports must have a different IP address or a different UDP port. For instance, if two Drivers are assigned to the same NIC, you can use the value 47809 for the UDP port of the Physical Port of the second Driver.

A network can be created manually or with the network wizard.

2a – Create a Network Using the Network Wizard

2b – Manually Create Network for AutoDiscovery

To manually create a network, proceed as follows:

Create the Network

Assign the Driver

Create the Views

2c – Manually Create a Network for EDE File

Proceed as follows to manually create a network:

Create the Network

Assign the Driver

Determine the Views from the Import File

Views can only be determined by importing the EDE file in the system.

Create the Views

Assign the Hierarchies

The Discovery function scans the entire BACnet network for BACnet devices. We recommend using available filter criteria for the scan to avoid unnecessarily impairing the network.

Restrictions

The following restrictions apply when using online import with Discovery:

• Only standard BACnet objects are supported. Proprietary object and object extensions are lost.
• The objects are displayed alphabetically in System Browser.

Scan for Devices

The BACnet Object Browser scans a BACnet network for devices and their status.

Start a Network Scan

Vendor ID

• The vendor ID list is available at: http://www.bacnet.org/VendorID/.
• The vendor ID list is mapped in the library TxG_BACnetVendorId.

NOTE:
Some suppliers, such as Siemens Ltd., have multiple Vendor IDs.

Import Data Points

Assign/Change a Function

Link Objects

The Discovery function imports data points to the Management View. They must be manually linked for the data points to also be available in the Logical View or User View. The following workflows use the Logical View as an example but they also apply to any other view.

Create a Hierarchy Structure

Create Related Items

Creating/Modifying Configuration Files

Example for Hierarchy-User.txt or Hierarchy-Logical.txt file with three languages (en-US, fr-FR and de-DE):

!encoding!utf-8

#separators-1#;

#separators-2#,;

#separators-3#|

:column-name:keyname

,_,1,15,Location|Location|Standort

,:,1,15,Building|Bâtiment|Gebäude

,_,1,15,Floor|Plancher|Stockwerk

,_,1,20,Plant|Installation|Anlage

,_,1,20,Object|Objet|Objekt

,_,1,25,Data point|Point|Datenpunkt

(Optional) Extension family name

The selected files are checked for proper syntax prior to import. If an error message is displayed, click Open Log for additional information.
If the Hierarchy-User.txt and Hierarchy-Logical.txt files are used, the minimum and maximum length of the hierarchy level of the data point is checked. An error message is displayed if it is too short or too long. The data point is created in the database, but not visible for the corresponding view.

Supplement EDE File with Function

1. In Excel, open the EDE file (CSV or XLSX).
2. Add the column name Function on the same line as the keyword Keyname.
3. In the Function column, enter a unique function-key for each data point.
4. Click Save.

Creating a Function Key

Add the Function to the EDE file, if:

• The third-party BACnet device has a standardized data point name
• Multiple data points have the same function
• Future projects have the same data point names of the third-party BACnet device

Workflow

1. Supplement function key in the EDE file.
2. Extend import rules for third-party BACnet devices.
3. (Optional) Export the import rules for additional projects.
4. (Optional) Import import rules to the new project

Exporting a Function Key

Scenario: You want to reuse the configuration in another project.

Importing Function Keys

Scenario: You created a configuration for another project and want to reuse it on this project.

Conduct Initial EDE Data Import

Supplement Texts for Hierarchy Folder

The various objects in System Browser receive different names by supplementing file Hierarchy-Logical-Map.csv and Hierarchy-User-Map.csv.

Conduct Second or Additional EDE Data Imports

Assigning/Changing a Function

If third-party BACnet devices are integrated in Desigo CC, the alarm table must be checked in accordance with the alarm priorities of the applicable vendor or adapted where applicable. The changes are made per device (recommended) or data point.

Alarm Table Configurations

The following figure displays how an alarm is configured in the management platform to display in the correct alarm class on the Alarm Overview bar. The example shows the behavior on a data point. The same can be done at the device level.

Check Notification Class

In order to ensure a correct display on the Alarm Overview bar, the notification class must be properly set up in the field network. This has to happen at the individual devices or data point as well as on the notification class (NC) object. The example shows the behavior on a data point. The same can be done at the device level.

There are field networks that automatically calculate the notification class from the alarm function and alarm class. In this case, the notification class cannot be edited on the alarm object. Change the alarm function or alarm class to receive another notification class.

Create a New Alarm Table

Assign a New Alarm Table

NOTE:
If the Valid check box is displayed in gray (see the color-coded check boxes below), the library entries for the object model and function are not considered.

Inheritance Rules for Object Model, Function, and Object
Icon	Color	Description
	White	No value is inherited.
	Gray	The project instance value is inherited.
	Green	The function inherits the value.
	Blue	The object model inherits the value.
	Question mark with a yellow background.	The value is undefined until the instance is saved.

While you change inheritance properties, you cannot disable an inheritance. As a result, the state changes from to or when editing. This display for the inheritance function is used for the Main, Properties, Details, and Alarm Configuration expanders.