By default, each R2ObixClient has 4 device extensions: Alarms, Histories, Points and Schedules. Expand the R2ObixClient and
double-click Schedules (R2ScheduleDeviceExt) for the Obix Schedule Manager view, and then perform a Discover. Expand the config branch of the lobby to locate target Schedules in the R2 station. Schedules are added as ObixScheduleExport descriptors, as shown in Figure 2-27.
Figure 34. Obix Schedule Manager view of Schedules device extension to designate R2 slave schedules
In the Add/Edit dialog for a schedule export descriptor, assign component values, including a unique name for the descriptor.
In this dialog you must specify which local
AX BooleanSchedule will serve as the supervisor (master) schedule for the target R2 schedule. To do this, click the folder icon
on the right side of the Supervisor field, which by default opens the Component Chooser (Select Ord dialog) as shown in Figure 2-28.
Figure 35. Add/Edit dialog for ObixScheduleExport descriptor, showing Supervisor
In the Select Ord dialog of the component chooser, select a schedule and then OK. The Supervisor field should now have a valid ord, for example: station:|slot:/Schedules/BooleanSchedule1
Add an export descriptor for each R2 Schedule object in the R2 station that you wish to master from the
AX BooleanSchedule.
NOTE: Any target R2 Schedule should not already be “slaved” to an R2 Schedule in another station (typically in the R2 Web Supervisor
station), otherwise the
AX schedule supervisor function may not be successful. To remove a Schedule from R2 slaved control, delete the externalSubscription
link on its “slaveIn” input. A station restart on the slaved station (typically controller) may also be needed.
