Adding the Obix Network

Only one ObixNetwork is supported (or needed) in a station, regardless of whether you are using ObixClient or server functions, or both. This procedure adds an ObixNetwork component under the station’s Drivers container.

Expand Config and double-click the station’s Drivers container.
The Driver Manager view opens.
Click the New button.
The New network window opens.
Select ObixNetwork, number to add: 1 and click OK.
This opens a window to name the network to something other than the default. A station may have only one ObixNetwork.
Name the network or leave the default name and click OK.
The ObixNetwork under the Drivers folder should show a status of {ok} and Enabled as true.
Configure properties and click Save.

The network’s Monitor properties verify child oBIX client component(s). These are the “pingable” devices in the oBIX driver.

The Thread Pool property has special importance. It controls the number of threads used by the station to execute all actions of all oBIX objects in the network. This includes most communications with remote devices, which you can set up for multi-threading. In this case, if there are performance issues, you can increase the number of threads. The default value is four (4).

The network-level Tuning Policies slot with a single Default Policy container configures network-wide performance. You can add new tuning policies (duplicate and modify) as needed.

As in other driver networks, the network’s ObixClient has an available Alarm Source Info container slot you can use to differentiate Obix alarms from other component alarms in the station.

As with most fieldbus drivers, the status of an ObixNetwork is either the normal {ok} or in {fault} (fault might result from licensing error). The Health property contains historical timestamp properties that record the last network status transitions from {ok} to any other status. The Fault Cause property further explains any fault status.

Adding the Obix Network

Related Links