User`s guide

Schedules 65
Scheduler
E:COMMAND 1:<command here>
An event has a variety of parameters that can be applied to it, in order to
customize the Information Station’ s control to your show. In order to understand
how you define an event in Information Station, let’ s take this simplest example
and build it to the most feature-rich example.
Example 1: T:13:46 D:01/1/2000 E:COMMAND 1:"Hello, world!" BT
An event exists on one line. It 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, and the required data field, and a Start Date. Each field begins with
a delimiter.
Here is a table of delimiters for your reference:
Delimite
r
Field
T:
Starting time (hh:mm) (military time)
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 – always set to COMMAND
1:
The actual command you would use on any IS interface
2:
(not used for Information Station)
3:
(not used for Information Station)
4:
(not used for Information Station)
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