Configuring a station to receive alarms

The BACnet driver converts incoming alarms from remote BACnet devices to Framework alarms, which can then be routed through the Framework’s alarm subsystem to recipients (console, station, printer, email, and so on). A console operator acknowledges a BACnet alarm just as they acknowledge a native Framework alarm.
  1. In the receiving station, create BacnetDevice components for all devices from which the station will receive alarms.
  2. It is also recommended to create BACnet proxy points for all BACnet objects that will send alarms to the station.
  3. 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).
  4. Link the AlarmClass components into whatever alarm recipient objects are needed (AlarmConsole, etc.).
  5. 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.
  6. 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 > Local Device Object Id property.