oBIX driver
oBIX uses the standard Framework network architecture. ObixClient components in the station interface to oBIX objects in one
or more oBIX servers. oBIX proxy points under an ObixClient device, which, in turn, resides under an ObixNetwork container in the station’s Drivers node, model real-time data.
Hierarchically, the component architecture is: network, device, points extension, points.
Figure 1. oBIX network in the Nav tree
The ObixNetwork is the top-level container component for “everything oBIX” in a station and resides under the station’s Drivers container.
NOTE: Only one ObixNetwork component is valid in a station regardless of how many oBIX servers a station may make a client connection to.
- The ObixNetwork component has the typical collection of slots and properties as do most other network components. One exception is the location of the network’s poll components (Poll Scheduler), which is not at the network level, but under each ObixClient component.
- Like a few other drivers, oBIX client devices have a full range of device extensions—including Points, Alarms, Histories, and Schedules.
- The default view for the ObixNetwork is the Obix Client Manager. This view is equivalent to the Device Manager view in most other drivers. Other standard views are available to the network, however, apart from the Obix Client Manager, you typically access only each component’s Property Sheet rather than its manager view.