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

K2 Edge Protocol Manual – document version 1.0 – Page 29
5.9.4. Feedback level 'full'
Coverage from the reception point up to and including the final stop point. Note that the stop point can
theoretically be hours away from the safe point.
path note field reception start error ready play error safe stop
success (7) fb-event
fb-stat
ack
ok
start
ok
ready
ok
play
ok
safe
ok
stop
ok
failure (2) fb-event
fb-stat
nak
error
failure (3) fb-event
fb-stat
ack
ok
start
error
failure (8) fb-event
fb-stat
fb-info
ack
ok
start
ok
error
error
asset
ready
error
play
error
safe
error
stop
error
failure (9) fb-event
fb-stat
fb-info
ack
ok
start
ok
ready
ok
play
ok
error
error
asset
safe
error
stop
error
Notes:
7) The command is considered valid at the reception point. The preload phase completed
successfully. The playback phase started and reached the safe point without errors. The template
will continue running until the stop point, and this event will be reported in the feedback.
8) The command is considered valid at the reception point. The preload phase started successfully
but preload errors were encountered before the ready point was reached. The template is played
though (with limited functionality). The template will continue to play and the events of reaching
the safe and stop point will both be reported in the feedback.
9) The command is considered valid at the reception point. The preload phase completed
successfully. The playback phase started successfully but errors were encountered before
reaching the safe point. The template will continue playing until the stop point is reached, but this
event is not reported in the feedback.
Example:
This third example of a preload-play command sent to nexos uses feedback level 'full'. The command
is again identical to the one used in the previous example (and again with incremented inst and exid
values).
{cmd=nre; subcmd=preload-play; template=ShowLogo; inst=44; exid=3;
fb-sw=true; fb-lev=full;}