Note: Only BACnet schedules are supported for this action.
The SendExceptionSchedule action sends exception schedules to a BACnet schedule object that is exposed in Desigo CC. The exception schedules are calculated the same way as the StartStop action, but the list of schedules for the next 24 hours is sent to the BACnet schedule object instead of queuing up the individual commands in the command queue.
At each event query (manual or automatic), 24 hours of event schedules are calculated, any pre-start and post-stop times are added, overlapping schedules are combined, and the final list is pushed down the schedule object. Events2HVAC will retain the last scheduled command state so current state is maintained correctly for the present time.
If Enable Schedule Push Optimization setting is NOT set, all SendExceptionSchedule actions will be pushed at each poll interval.
If Enable Schedule Push Optimization setting is set, all SendExceptionSchedule actions will be evaluated at each poll interval to determine if a schedule push is needed for each action. This option is more efficient since it only pushes schedules when there is a change in schedule between the last push and the current schedules. See the Schedules Tab for more details on these settings.
The schedule object that is the target of the schedules should be setup as follows for a basic setup:
Recommended Schedule Object Setup
Weekly
Schedules: None
Exception Schedules: Event Priority 13 - Only sent
by Events2HVAC and no other sources or calendar references.
Schedule
Default: Off or Unoccupied
Priority for Writing: 15 or higher to
allow any additional overrides or fallback priorities.
Write output to a dedicated intermediate binary value (recommended) at appropriate priority to show current scheduled state from Events2HVAC. Incorporate this value with any failure logic or schedule overrides to command the zone devices.
Additional Usage Notes:
Using a non-dedicated schedule object: If you decide to use a schedule object that has weekly schedules, calendar object references (holiday exceptions, etc), or other exception schedules from other sources at different priorities, then you must enable midnight initial values in the BACnet options – Schedules tab. This will ensure E2H will enforce the priority for exceptions for the entire day.
No Re-Sync: Re-Sync feature doesn’t work with SendExceptionSchedule actions. If the command to send the schedules fails due to a network or controller offline error, it will notify users of the failure, but will not re-attempt to send until the next scheduled or manual update occurs. A manual re-sync or re-sync all equipment from the user only synchronizes the actions that command the state of the rooms, not the schedules sent.
No Forced Re-Sync: For the same reasons as above, if you do a Force All Resync command, these actions will not be forced to send schedules. A re-sync doesn’t not use a 24 hr query window for schedules which is required for schedule push. Use a manual query update command instead to push all the exception schedules to their schedule objects.
This action only applies to the following event triggers:
•EventStartStop
•EventSetupTeardown
•ZoneFirstLastEventStartStop
•ZoneFirstLastSetupTeardown
|
Field Name |
Description |
Range |
|
Object Id |
This is the unique point id of the point to control |
Selectable from the list of points available from the view. |
|
Object Name |
Friendly object name |
|
|
Type |
Type of point |
|
|
Property |
Present Value |
Present Value |
|
Event Priority |
Priority value assigned to the exception schedule item. This is not the same as the priority written to the object(s). |
1-16 (1=highest) 16 = recommended default |
|
StartValue |
Value to write to the exception schedule when an event start is triggered. |
Depends on the object that is written by the schedule object. |
|
StopValue |
Value to write to the exception schedule when an event stop is triggered. |
Depends on the object that is written by the schedule object. |
|
Release Priority |
To relinquish a commandable property, select the priority of the command to relinquish and click the NULL checkbox. This will clear the command value at that priority and the next highest non-null command in the schedule object will take over. |
|
|
Overwrite ALL Exception Schedules |
When this is checked, any exception schedules in the schedule object will be overwritten. When unchecked, only the schedules at the priority level will be overwritten. |
Default = overwrite ALL schedules |
|
Initialize Midnight |
Ensures that every scheduled day has an initial value at midnight |
|
Verify Button
Click on the Verify button to verify that the selected object and properties can be read. The results of the verification will be shown in the Results window. Any existing exception schedules and weekly schedules will also be shown in the Exceptions Schedules and Weekly Schedule tabs.
Send Test Schedules Button
Click on the Send Test Schedules button to attempt to retrieve the current event schedules from the rooms associated with the equipment item for the next 24 hours. Once the schedules are processed, the exception schedules are written to the schedule object. Click on the verify button to read the properties and verify that the items were added.
Warning: If there are no schedules found for the day, the exception schedules will be cleared and the output of the schedule will first be evaluated by any active weekly schedules and if none are found, the output will return to the schedule default property.
Delete Exception Schedules Button
Click on the Delete Exception Schedules button to attempt to delete all the single calendar date exception schedules in the schedule object. Calendar object reference exceptions and non-single date exceptions (date range or week/month exceptions) will remain.
Warning: After your exception schedules are deleted, the output of the schedule object will return to the value defined in the schedule default property, unless there is a weekly schedule defined.
Delete Weekly Schedules Button
Click on the Delete Weekly Schedules button to attempt to delete all the weekly schedules in the schedule object. Normally you would not want any weekly schedules unless your zones needed a default base schedule throughout the week and only after hours schedules would be scheduled as exceptions (with NULL stops).
Warning: After your weekly schedules are deleted, the output of the schedule object will return to the value defined in the schedule default property, unless there is an active exception schedule defined.