Grass Valley K2 Edge Protocol Manual v1.0 - Manual (Page 31)

K2 Edge Protocol Manual – document version 1.0 – Page 31
5.10. Sub command preload
Sub command preload prepares a template instance for a later play command.
5.10.1. Life cycle diagram
The following diagram shows the life cycle of the preload sub command. The start point can be
scheduled with the stm (start time) field, and if not defined the preload phase starts ASAP.
5.10.2. Feedback level 'basic'
Coverage from the reception point up to and including the start point. Any event beyond the start point is
suppressed in the feedback. The only information the initiator will receive is whether or not the command
was successfully started.
path note field reception start error ready
success (1) fb-event
fb-stat
ack
ok
start
ok
failure (2) fb-event
fb-stat
nak
error
failure (3) fb-event
fb-stat
ack
ok
start
error
Notes:
1) The command is considered valid at the reception point and the preload command has
successfully started. No feedback is provided on any of the following events, including possible
errors. The command will run until it reaches the ready point, possibly with limited functionality
due to errors encountered during the preload process.
2) The command is considered invalid at the reception point. The command is not executed.
3) The command is considered valid at the reception point but failed to start (for example due to a
bad template name). The command is not executed.