ObixNetwork and R2ObixClient devices

In the Supervisor you add a single ObixNetwork under Drivers, then manually add R2ObixClient devices, where each represents an R2 station. For each new R2ObixClient, you enter a few properties in the New dialog, shown with non-working default values in Figure 7.

Figure 7. Add R2ObixClients using New button in Obix Client Manager view of ObixNetwork


Add R2ObixClients using New button in Obix Client Manager view of ObixNetwork

NoteAs shown above, there are two types of “client device” choices: ObixClient and R2ObixClient. Always select R2ObixClient for any R2 station, as it provides additional capabilities. Also, note the general “client/server” naming in NiagaraAX follows a “convention” used in some other drivers, for example the OPC driver and Modbus drivers, where a “client” device actually represents a server device (here, an oBIX server), and associated NiagaraAX components are named “client” because a client connection is used to retrieve data.

Set properties in the New dialog as follows:

After entering data and clicking OK, the device is added to the database, and the “State” column value for the new row quickly changes from “Detached” to “Attaching”, and finally to “Attached”, as in Figure 8.

Figure 8. Entering new ObixClient and subsequent State change to Attached


Entering new ObixClient and subsequent State change to Attached

Note(Troubleshooting) If after entering the R2ObixClient it remains Detached, review its Lobby syntax, including IP address of the R2 JACE (open a command prompt window and issue a Ping command to that IP address). Also, verify the R2 station user credentials for Auth User and Auth Pass are correct. Note also that you should be able to open a browser connection to the R2 station using the URI entered for Lobby, and after entering user credentials, see its oBIX lobby (see Figure 2).