Use the ObixAlarmManager to discover, add, and manage alarm feeds of a selected ObixClient or R2ObixClient. The ObixAlarmManager is the default view of the Alarms device extension (ObixAlarmDeviceExt, R2AlarmDeviceExt) under these devices. To view, double-click the Alarms extension, or right-click and select ->.
Although not a standard view in the driver architecture, it is similar to typical point and history manager views. As in those views, there is a Discovered table (if in Learn mode) and a Database table. In the discovery pane, objects with a value in the “Feed” column are valid alarm sources, and can be added as alarm imports (ObixAlarmImport or R2AlarmiImport, depending on parent device type).
During discovery, results are cached. Therefore if the server database is modified after a discovery has occurred (or while a discovery is in progress), the discovery pane may be inaccurate. Click the button again to clear the cache.
For details in a Niagara R2 to AX application, see the “R2ObixClient Alarms” section in the engineering notes document Niagara R2 to NiagaraAX via oBIX.
The Discovered table in the ObixAlarmManager view has the following available columns:
-
Obix Name
Name of the object on the oBIX server.
-
Href
The URI of the object on the oBIX server.
-
Feed
The URI of the object on the oBIX server, with “.alarm” suffix to denote a valid alarm feed.
By default, the following columns appear in the Discovered table of the ObixAlarmManager view:
-
Name
Niagara name of the alarm import descriptor, often left the same as its oBIX Name.
-
Href
The URI of the object on the oBIX server.
-
Alarm Class
The local station’s AlarmClass to use to process native alarms received via this alarm feed.
In addition (using the table options control), the following additional data column is available:
-
Subscription
Reflects whether the alarm import is Subscribed, Unsubscribed, or Pending subscription.