Add ObixService

For each R2 station to be integrated, you open it in the JDE, open the Local Library and expand the tridiumx/obix jar, and copy and paste the ObixService into the station’s Services container. No further configuration of that service is needed; however, you must restart that station for it to become an “oBIX server.” R2 object data from the station is then immediately available from the AX station running the Obix driver.

Note you can quickly verify if an R2 station is operating as an oBIX server. Simply open a web browser connection to that station, using the 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.

As shown, after you login with station credentials you see an HTML representation of the station’s oBIX lobby, including hyperlinks to traverse into the object tree structure.

Figure 11. Example browser connection to confirm R2 station oBIX server operation

Note R2 oBIX is server only. Client access of remote oBIX servers is unavailable—no R2 “shadow objects” exist to get remote oBIX data (e.g. from the AX station). This simplifies engineering on the R2 side.

NOTE: For this reason, the AX Supervisor station’s “Exports” folder under its ObixNetwork is not used when integrating Niagara R2 stations as ObixClients. However, AX to R2 schedule exports are possible using a different method.

Add ObixService

Figure 11. Example browser connection to confirm R2 station oBIX server operation

Related Links