Usage Notes:
1. If you export a native BooleanSchedule object, make sure you select the “Boolean” datatype. If you export an EnumeratedSchedule object, make sure you set the datatype in the native schedule to “unsigned” and select “Multistate” as the datatype in the SendExceptionSchedule action.
2. The AX schedule control does not allow changing (BACnet) event priorities on exception schedules. All exceptions entered by a user are fixed at event priority 16 (lowest priority). The “priority” up/down arrow only re-arrange the order of the exceptions list regardless of the event priority assigned to each exception. If E2H sends an exception at priority 15 or lower, these events will show up above any user entered special events and calendar references. If E2H sends at priority 16, then any non calendar reference events will be deleted and replaced with E2H events. Calendar reference events will remain at the top of the list so they will take priority over E2H priority 16 events.
3. If an existing Niagara schedule object has a large number of special events entered by users or a 3rd party integration, the E2H BACnet command to the exported proxy schedule may timeout and fail to send E2H schedules. To remedy this, remove the extra special events in Niagara and try again.