R2ObixClient R2 Schedule exports

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 27.

Figure 27. 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 28.

Figure 28. 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 an AX BooleanSchedule.

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 JACE) may also be needed.

AX Schedule to R2 Schedule operation

Although the AX BooleanSchedule and the R2 Schedule seem to have similar “weekly” schedule event programming, they in fact use different “schedule models.” Therefore, AX schedule mastering of an R2 Schedule is implemented by writing the AX schedule’s events to the Special Events in that R2 Schedule.

Note that unlike AX schedule special events (which “intermingle” with weekly events), R2 schedule special events replace the normal weekly schedule. As shown in Figure 29, schedule events that are written to the R2 Schedule from the AX master appear in the “Special Events” tab of the JDE Schedule Editor view, in a block of around four weeks. Each has a “weekday” name (monday, tuesday, monday2, tuesday2, etc.) seen at the top of the tab.

Figure 29. R2 JDE Scheduler Editor view, Special Events tab, showing received AX schedule events

As a contingency measure, you may consider creating additional Schedule objects in the R2 station, along with any necessary additional logic, to provide scheduling control in the case that communications with the AX master station are lost for long periods. Or, continue to maintain the weekly schedule portion of these Schedule objects, because this is not affected by any schedule downloads from the Supervisor.