User`s guide

Scheduler 37
Restrictions
Since the Scheduler is very flexible, it is easier to explain what you cannot do,
than to explain what you can.
1. When using BOOT as the Repeat Period, the Repeat Number can only be
one. The unit does not keep track of the number of times it has rebooted.
You can put in other numbers, but it will ignore them.
2. Whatever combination you choose between Repeat Number and Repeat
Period should not multiply out to be greater than a century. For example,
don’t repeat an event every 102 years.
3. One event executes per minute. If you want more and you haven’t already
purchased a small show controller, like the InterActivator, then get on of
these. It can increase the amount of events you can generate from 1per
minute to 30 per second * 60 seconds per minute = 1800 events per minute!
Comments & Whitespace
Comments are prefixed with a semicolon (;). Anything found after a
semicolon is ignored by the scheduler. You can place a comment on its own
line, if you like. You can use spaces or tabs to organize your schedule. They
both are ignored.
Examples:
;This is a comment on its own line
T:1:00 D:1-1-01 E:COMMAND 1:1PL ;this is a comment too
Order of Operations
Here is a listing of times when the DVMHD checks the schedule and the
operations afterwards.
1. The DVMHD loads the searched schedule at:
a. Boot up
b. When the schedule is searched.
c. Every night at midnight.
2. The DVMHD gets today’s date from it’s Real-Time Clock.
3. The DVMHD parses the schedule and loads all of today’s active events.
4. If it is a bootup that caused the schedule load, the Bootup event gets loaded.
5. If there has been a bootup delay set via the INI file or remote command, then
the unit will wait until that time has expired before starting. This allows
DVMHD to wait on products that boot slower than it does before starting a
show. An example is a slow booting projector. The DVMHD has to wait until
it has booted before playing video.