ObixClient proxy point tips

When creating Obix proxy points for an R2 controller under the Points extension, the following tips may be useful:

As needed, use the column sort features when traversing the lobby tree in the Discovered pane. This can save scrolling time.
When creating ObixPointFolders for organizing proxy points (double-clicking R2 container type objects, or using the New Folder button), be aware of the current database level. Each ObixPointFolder has its own Obix Point Manager view, seen when you double-click it—note this collapses the lobby tree in the discovered pane. However, you can simply re-expand the lobby to find and add child Obix proxy points.
For any R2 object for which you need standard AX alarming, create a root-level proxy point for it, then add the AX alarm extension to it (for example, an OutOfRangeAlarmExt, duplicating the same alarm and fault (min/maxPresentValue) limits as in the R2 source object). Or, to avoid limits duplication in AX, you can add a StatusAlarmExt and simply select the alarm states in the algorithms for OffNormal and Fault.
NOTE: Alternatively, you can configure the Alarms device extension under the R2ObixClient to process R2 native alarms within the AX station’s alarm subsystem. This works best for R2 objects that are already being proxied in the AX station. For more details, see “R2ObixClient Alarms” on page 2-18.
Understand the “forceUpdate” action of an Obix proxy point can cause issues in certain cases. For details, see “About forceUpdate” on page 2-13.