<< Click to Display Table of Contents >> Navigation:  Scheduler > Slave schedule

It is possible to create a slave-schedule, for a secondary entrance of a library. This secondary entrance then has a separate entrance unit but not a separate schedule - it follows the master schedule to change state. This enables a library with more than one entrace to control entry using the entrance panel, but only have to maintain one schedule to set periods for each of them.

It is of course possible for each entrance with a separate controller to have a separate schedule. This is perhaps a more flexible option but in reality probably not needed except in vary specific scenarios.

When using a slave schedule, the difference in operation is that the slave controller then does not have it's own IO or other requests; the slave does not set lights or play audio on a schedule, only the master controller does. The slave controller only operates the door lock based on the lock trigger settings in Management Utility, and only for schedule period changes: when the schedule period changes to "Open", the configured trigger channels are opened (set). For any other period type ("Closed" or "Self operated"), the trigger channels are closed (reset).

Normal entry using the entrance unit opens (sets) the triggers just as they are defined; the slave schedule system does not affect that.

It is also possible to create a schedule in the slave schedule and override periods of the main schedule. We strongly recommend that this would only be done for full days - for example closing a side-entrance on weekends by overriding the schedule for full days on saturday and sunday. More precise control is possible but can easily become difficult to maintain, and thus negating the original idea of having a slave schedule in the first place.