The ObixNetwork is the top-level container component for “everything oBIX” in a station.
Only one ObixNetwork component is valid in a station—regardless of how many Obix servers the station will make client connections to.
The ObixNetwork should reside in the station’s DriverContainer (“Drivers”). The simplest way to add an ObixNetwork is from
the “Driver Manager” view, using the command. Or, you can simply copy the ObixNetwork from the obixDriver palette into Drivers.
The ObixNetwork component has the typical collection of slots and properties as most other network components. For details, See “Common network components” in the Drivers Guide. One exception is the location of poll components (Poll Scheduler), which is not at the network-level, but under each ObixClient or R2ObixClient (device-level) component.
In addition, the following ObixNetwork property has special importance:
-
Thread Pool
Controls the number of threads used to execute all actions of all Obix objects in the network. This includes most communications with remote devices, which can be multi-threaded. In this case, if there are performance issues, you can increase the number of threads. The default value is 4.
The following sections provide additional ObixNetwork details: