Grass Valley Maestro Master Control Reference Manual v.2.4.0 - Manual (Page 98)

98 MAESTRO — Automation Interface Protocol Technical Reference Manual
Section 5 — Definition of Extended Maestro Commands
Sequential Transaction Queues Theory of Operation
In order to provide the means for execution of Maestro specific automation
commands in a successive manner, the following is implemented. It is
desired that an automation system have the ability to specify that a group
of commands be executed in a successive manner and only after the previ-
ously issued command in the sequence has completed.
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
0 1 2 3 4 199
Maestro Channel
Automation Processing
255
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
T
r
a
n
s
a
c
t
I
o
n
Q
u
e
u
e
Automation
A
S
A
P
C
h
a
n
n
e
l
Maestro
Automation
Figure 1.
255 Transaction Queues (0-199 are available for use by automation, 200-254
are reserved for internal use) will be created that will allow an automation
vendor to specify which queue a command message will be placed. Pro-
viding multiple queues allows an automation system to set up multiple
unrelated command sequences that will then be executed in parallel to
minimize the latency. All command messages within a queue will be exe-
cuted in a successive manner. In addition to the Sequential Transaction
Queues (0-254), an ASAP channel (with an identifier of 255) will exist that
will provide a channel for the execution of ALL existing Saturn Automa-