Alcorn Mcbride AM-4, Справочное руководство по аппаратному и программному обеспечению

Страница: 34 / 77

28 Scheduler
Command Event
Example 1:
T:13:46 D:01/1/2010 E:Command 1:"1PL"
Each event exists on one line and is made up of several fields. Example 1 shows the
minimum number of fields you need to define an event, which are an Event, a Start
Time, possibly a required data field, and a Start Date. Each field begins with a
delimiter as shown in the following table:
Delimiter Field
T: Starting time (hh:mm) (military time – leading zeros for hours required)
D:
Starting date (mm/dd/yy or mm/dd/yyyy . You can use periods, slashes,
or dashes to separate dates)
I: Ending time (hh:mm) (military time)
A: Ending date (mm/dd/yy or mm/dd/yyyy . You can use periods, slashes,
or dashes to separate dates)
E: Event
1: Parameter 1 for the event
2: Parameter 2 for the event
3: Parameter 3 for the event
4: Parameter 4 for the event
R: Repeat Number: repeat after this number of periods has expired
P: Repeat Period: Time to wait between executions, used with Repeat
Number and Set when necessary
S: Repeat Set: special case usage described below
; Although not a field, this marks a comment
Now that we have seen a table of the event fields, let’s look at Example 1. Here are
its fields:
Start Time: 1:46pm in the afternoon (
13:46
military)
Start Date: January 1
st
2010 .
Note: The carriage
return is automatically
inserted by the
scheduler, so do not
include it.
Event: Command event, which is a generalized event allowing the scheduler to send a
custom string to the AM-4’s serial processing section.
Field 1, the command string, specified as “1PL”, commands the AM4 to play file
number 1.
Notice that the string, ”1PL”, matches the command that would be used to play the file
if the unit were being controlled by an external serial controller.