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.
As 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:
Name
The AX name for the device component—by convention, enter the R2 station name. It must be unique among other child devices, and if using history ID defaults, also recommended to be unique from any NiagaraStation names (under the station’s NiagaraNetwork, for remote AX stations).
Lobby
The URI to the root of the R2 station’s oBIX server object tree (lobby), using syntax:
http://<host>[:port]/obix
where <host> is IP address or hostname, and [:port] is optional (if omitted, assumed as 80).
For example: http://192.168.1.94/obix for a typically-configured station at that IP address, or http://192.168.1.75:85/obix for a station running on httpPort 85 on a host at that IP address.
Auth User
Enter user name in that R2 station, typically with all admin-level privileges for most security groups.
On the NiagaraAX client side, if you attempt object writes without this user having the necessary security rights for those
objects (for example a command, or modify a property), it results in an "HTTP Error 401:Access Denied" error.
Auth Pass
Enter password for that user account in the R2 station.
Enabled
Defaults to true (must be true to attempt communications and operate).
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.
(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).
Copyright © 2000-2014 Tridium Inc. All rights reserved.