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.
Prerequisites: The station is open and a BACnet device has been added and is communicating in the station.
- Expand and double-click on the Config node in the Nav tree.
The Bacnet Config Manager view opens.
- Discover 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.
- After determining the referenced notification classes, delete unused config objects.
- Right-click the Notification Class config object, and select .
The Add Destination window opens.
- Expand the
Recipient property and enter the station’s device ID, replacing the -1 with value of the station’s , Object Id property.
- Specify the (integer)
Process Identifier to use in sending alarms to the station (the default is 0).
- Configure other properties, and click OK.
- To save the changes, click Save.
Alarms are now configured to send to the client station.
NOTE: 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.