Engineering summary

Most engineering is expected to occur in the Supervisor station (see Figure 1), where:

All data from remote R2 stations is modeled under the Drivers/ObixNetwork, using the basic familiar AX driver architecture (e.g. network/devices/Points/proxyPoints). See AX station engineering summary.
All data from remote AX JACEs is modeled under the Drivers/NiagaraNetwork, as for any AxSupervisor. Refer to “About the Niagara Network” in the NiagaraAX Drivers Guide for more details.

R2 station engineering summary

Make pre-integration changes to the R2 station(s), if necessary. Then from the tridiumx/obix jar, add the ObixService to the Services container of any R2 station to be integrated.

Use of the other R2 “export” objects in the tridiumx/obix jar is optional, and may not apply. Depending on other integration features into AX, other station configuration changes may be necessary regarding slaved Schedule objects, and the station’s LogService and/or NotificationService.

For more details, see R2 station engineering.

See the Niagara Release 2 oBIX User Guide for details on copying the obixInternal.properties file to remote R2 JACEs, as well as other R2-specific topics.

AX station engineering summary

Add an ObixNetwork in the Supervisor’s Drivers container, either using the New command in the Driver Manager view, or by opening the obixDriver palette and copying/dragging the network. Then, under this network you manually add one R2ObixClient device component for each R2 host (station) to be included.

Once you configure an R2ObixClient with a few settings, it can connect (attach) to the host R2 oBIX server. Then you can “learn” an object space tree for that station, which has an expandable root node named the “lobby” (an oBIX term). The root lobby node appears in the Discovered pane of the manager view for each of the device’s extensions, notably Points, Alarms, Histories, and Schedules (all default device extensions).

For more details, see Supervisor engineering.