R2ObixClient Alarms

The Alarms extension of an R2ObixClient for the R2 station allows you to add “alarm feed” sources, such that native R2 events (alarms and alerts) in the station can be visible in the AX station’s AlarmService.

Figure 31. Obix Alarm Manager view used to add alarm feeds from R2 NotificationClass objects

To configure, double-click the R2ObixClient’s Alarms extension, and in the Obix Alarm Manager view, perform a Discover. Expand the services node, and then the NotificationService node. As shown above, each R2 NotificationClass object is represented as a separate alarm feed, in addition to a “global” “ObixService” alarm feed.

Double-click any feed for the Add dialog. If desired, you can select a non-default local Alarm Class, but other properties are typically left at default.

NOTE: If your AX station has an Alarm Class with the same AX name (as the discovered R2 NotificationClass node), then all imported R2 alarms using that NotificationClass are automatically routed to that local Alarm Class—this overrides any Alarm Class specified in the Add dialog.

Click OK to add the ObixAlarmImport descriptor(s). These are the only objects added in this view, and they requires no further configuration.

NOTE: Typically, you add all nodes discovered under the NotificationService, but not the node for the single discovered “ObixService”. This provides the ability for mapping different R2 NotificationClasses to different AX AlarmClasses, rather than just “lumping” all native R2 alarms from the R2 station into a single feed with only one designated AX Alarm Class.

See the following subsections for additional R2 alarm import details:

R2 alarm import operation
Example R2 alarm imports
Final notes on imported R2 alarms

R2ObixClient Alarms

Figure 31. Obix Alarm Manager view used to add alarm feeds from R2 NotificationClass objects

Related Links