Scheduler (Event Type)
From Zenitel Wiki
Contents
Event description
| Event Owner: | Scheduler |
| Event type: | 22 - Minute Tick |
| Subevent: | N/A |
| When change to ON: | Real time minute tick |
| When change to OFF: | Catch-up minute tick |
| When related to: | Scheduling rules, Week day or Date |
Additional information
- Each minute the “22 Minute Tick” event is triggered
- If the “Minute Tick” time matches the scheduling rules, the event is executed
- There are two variants of time conditions:
- - Date and time: yy-mm-dd hh:mm
- Each digit can be a wild card *, matching all tick-values in that position
- Example: The rule “**-**-** 12:00” will be triggered every day at 12:00
- - List of weekdays and a time: mtwtfss hh:mm
- In AlphaPro there is a checkbox for each weekday
- Each digit in the time can be a wild card *
- Example: The rule “mtwtf-- **-**-** **:00” will be triggered every hour Monday to Friday
- Catch up mechanism in case of Power off or if the clock is moved forward
- - Up to 24 hours catch up, 1 minute per second
- - During this periode the scheduling time is different from the real time
- - Can be diabled by setting: When Change to: On
Application examples
- Transfer at fixed times
- Time signaling
Testing the Scheduler
The scheduling has a "catch-up" mechanism which is operational when the time is forward adjusted. During the catch-up period (max 24 minutes) the real-time scheduling events is not executed. This might cause some confusion during testing.
When you need to adjust the time forward for testing of scheduling events, you should do it in this way:
- Set the time and date to a value minimum 24 hours past the scheduling point
- Wait for minimum one minute
- Set the time and date back to were you want to start the test
In this way you omit the "catch-up" time.
Let's say you want to set the time and date to 21/10 01:57 to test the wintertime event at 01:59. Do the following:
- Set date and time to 22/10 11:00
- Wait for minimum one minute
- Set the time and date to 21/10 01:57