Bacnet Alarm Class Reassigner

The purpose of this module is to allow multiple BACnet Notification Classes to map to multiple Niagara Alarm Classes. By default, without this addition, the Niagara BACnet driver maps multiple NC's to a single Alarm Class defined on the BACnet Devices Alarm Ext.

Any alarm received by the Niagara Device is passed to all possible NC Alarm Class Reassign children until it has been published to an alarm class, as a result of an exact match to a Notification Class. If no matching pair is found the fallback class set by the user via the fallback property (described below) will be used to determine the destination Alarm Class.

In order to enable routing to the reassigner, set the process Id in the Bacnet Devices Alarm Ext (parent component of the CustomEventProcessor) to a numeric value not anticipated to be used by the BACnet network. If the process Id of the incoming alarm is found to match the Devices Alarm Device Ext current value, then the alarm will not be routed via the Alarm Class Reassigner logic.

Expected Parent Type: BacnetDevice

Bacnet Device
 |
 |-Alarms                       [ Change process Id to unused value to pass alarm to event processor below ]
 |  |
 |  |-CustomEventProcessor      [ Set process Id here to a desired/used value ]
 |
 |-BacnetAlarmClassReassigner   [ Set config properties eg fallback class ]
    |
    |-NCAlarmClassReassign1     [ Match NC Id to Alarm Class here ]
    |-NCAlarmClassReassign2
    ...

Usage Instructions

Property Descriptions

Troubleshooting

If alarms are being routed as normal, check the process Id configuration beneath the BACnet Device Alarm Ext does not match a process Id in use by the source device.

The logging for this component is enabled via bacnet.alarmClassReassigner.



See Also

Niagara Bacnet Alarm Operation