See Prerequisites and restrictions to receive BACnet alarms
The following procedures explain how to get started receiving BACnet alarms.
To configure to receive BACnet alarms
In the station, create BacnetDevice components for all devices from which you wish to receive alarms. It is also recommended to create Bacnet proxy points for all BACnet objects that will send alarms to the station. See Create BacnetDevices and Create Bacnet proxy points.
Under the station’s AlarmService, add AlarmClass components as needed, setting ack requirements and priorities. Each BacnetDevice can use only one AlarmClass (either used by other devices, or unique to that device.).
Link the AlarmClass components into whatever alarm recipient objects are needed (AlarmConsole, etc).
For each BacnetDevice in the station, in its Alarms device extension:
Specify the AlarmClass component to use.
Set the “Niagara Process Id” to match the BACnet process identifier (integer value) used in sending alarms to the station.
See BacnetAlarmDeviceExt (reference) for related details.
Using third-party tools for each remote BACnet device, configure the Notification Class object that routes alarms to include (add) the Device object ID of the station to its “Recipient_List” property. This is the numerical value seen in the station’s BacnetNetwork, LocalDevice, “Object Id” property.
You may be able to use Niagara for this. See To configure a BACnet device to send alarms to Niagara
To configure a BACnet device to send alarms to Niagara
Sometimes a remote BACnet device may not allow this configuration. In this case, you must use third-party tools to configure
Notification Class objects in a BACnet device as described below.
With the station opened, and a BacnetDevice already added and communicating in the station:
Go to the
Config device extension’s Config Manager view.
the objects in the device.
Add the Notification Class config object for the alarms you wish to receive.
To determine which one to add, add a config object for an object that will be alarming, and inspect its Notification Class
property. This specifies which Notification Class object will route those alarms. Delete unused config objects after determining
referenced notification classes.
Right-click the Notification Class config object, and select ->.
In the Add Destination dialog, expand the Recipient field and enter the station’s device ID, replacing the “-1” (with value of the station’s BacnetNetwork, LocalDevice, “Object Id” property).
Specify the (integer) Process Identifier to use in sending alarms to the station (default is 0).
You may configure other properties as desired for when you wish alarms to be sent.
Click .
changes.
Alarms should now be sent to the (client) station.
For BACnet alarms from a device to be successfully received in a client station, the Process Identifier in the Recipient List
entry for the station (in the BACnet Notification Class object of the sending device) must be matched when configuring the BacnetDevice’s Alarms device extension, “Niagara Process Id” property. See BacnetAlarmDeviceExt (reference) for related details.
Copyright © 2000-2016 Tridium Inc. All rights reserved.