Alcorn Mcbride AM-4, Hardware And Software Reference Manual

Page: 35 / 77

Scheduler 29
Example 2:
T:14:46 D:01/1/2010 E:Command 1:"RJ"
Two things have changed in this example.
Start Time: 2:46pm in the afternoon ( 14:46 military)
Start Date: January 1
st
2010 . (same as Example 1)
Event: Command event (same as Example 1)
Field 1, the string, defined as “RJ”, will cause the AM4 to stop playback.
So using the two examples together in a schedule file will cause file number one to
begin playback at 1:46PM on January 1
st
, 2010 and stop playback at 2:46PM the
same day.
The Command event actually has more fields associated it with it, that are not
required. So let’s look at it with those fields filled in:
Example3: (New fields are in bold. kept on one line for clarity.)
T:14:46 D:01/1/2010 R:30 P:minute A:1.3.00 I:3:00 E:Command1:"1PL” ;Repeats a while
We’ve now added:
Repeat Number: 30
Repeat Period: minute
Ending Time: 3am in the morning ( 3:00 military)
Ending Date: January 3
rd
2010
Comment: We also stuck a comment “ Repeats a while ” at the end of the line, by
prefixing it 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.
The Repeat Number acts as a multiplier of the Repeat Period. They should be
read in conjunction like this: “Repeat this event every 30 minutes”.
The only field not discussed yet is a set .
Example 4:
T:1:00 D:11-28-02 R:4 P:Thursday S:November E:Command1:"1PL”
A set defines a certain range of valid repeat periods. In Example 4, only the
Thursdays in November are eligible for this event. When a set is used in an event,
the Repeat Number takes on a different meaning. Instead of being a multiplier of the
Repeat Period,
it and the Repeat Period become an index of the set. These three
fields should be read in conjunction like this: “Repeat this event every 4
th
Thursday in November.”