There are many reasons why oBIX network operations may fail.
A component indicates a status of “fault.”
Occurs when a platform is not licensed for a specific feature. For example to use an oBIX network, the license must have the
export=”true” attribute in the obixDriver feature line.
A component reports a fault cause.
If status is fault, this property explains why, such as Server not licensed.
When adding an oBIX device, the State of the device remains “Detached.”
- Review the syntax of the object’s Lobby, including the IP address of any R2 controller.
- Open a command prompt window and ping the IP address
- Verify that any R2 station’s user credentials for Auth User and Auth Pass are correct.
You should be able to open a browser connection to an R2 station using the URI entered for Lobby, and after entering user credentials, see its oBIX Lobby.
NOTE:
Niagara 4 requires basic digest authentication for browser clients to navigate to Obix server. Browser clients are restricted to use
basic digest authentication, because of this browser clients are not able to access Obix server.
For Browser Clients
NOTE:
Niagara 4 requires basic digest authentication for browser clients to navigate to Obix server. Browser clients are restricted to use
basic digest authentication, because of this browser clients are not able to access Obix server.