User`s guide

72 Schedules
Order of Operations
Here is a listing of times when Information Station checks the schedule and the
operations afterwards.
1. Information Station loads the schedule from sch00000.txt (default) at:
a. Boot up
b. Every night at midnight.
1. Information Station gets today’ s date (or already knows it) from built in RTC.
2. Information Station parses the schedule and loads all of today’ s active events.
3. If it is a bootup that caused the schedule load, the Bootup event gets loaded.
4. If there has been a bootup delay set via the INI file is.ini, then the unit will
wait until that time has expired before starting. This allows Information
Station to wait on products that boot slower than it does before starting a
show. An example is a slow booting projector. Information Station has to wait
until it has booted before playing video.
Coincident Events
If you plan on having a fairly complicated show, you may want to be sure you
don’ t have events competing with each other for execution when their time and
date come around. This discussion looks at what happens when two events end
up on the same time and date. It explains the rules used to determine which
event wins.
¾Definitions
The following are previously undefined terms used in the Scheduler Rules
discussion below
• Timestamp - time portion of the event's starting point (T: and D: )
• Datestamp - date portion of the event's start point (T: and D: )
• Slot - the event's timestamp + datestamp
• Startslot - slot when the event begins (required)
• Endslot - slot when the event ends (not required)
• Profile - an event’ s startslot, endslot, type (defined below)