
iPump 6420 User’s Manual
the receiver is unaffected by command execution (or the lack thereof). These commands must often be synchronized to other external events. For example, a closure arriving from a customer’s media automation system, requesting the play of a commercial spot must cause a command to edge iPump6420s to insert a particular file, to be aligned precisely with a network “avail” (local spot opportunity).
•
•Satellite File download operations: A special command and functions to go with it that allow the download of media files to edge receivers. This is discussed more thoroughly in Section 3.3.
•HTTP File download operations: A special command to request that receivers pull media file content from Compel, by HTTP, over the internet.
•Playlist build commands: Commands to build playlists on edge receivers who support that function. Playlists are discussed more thoroughly in Section 3.4.2.
•Miscellaneous commands: Commands that affect the remote receiver state, but are not retained in the Compel database. For example, a command to pipe a terminal command to iPump6420 may be sent using the Compel SCRIPT TERMINAL command.
•Scheduling commands: Commands to add or delete line items in receiver’s Local Scheduler, where supplied. See the discussion following on Local Scheduler.
•Refreshes: Not formally a type of “command”. This is a special Compel function to keep remote receiver settings equal to that specified in the Compel database. It uses many receiver state commands to do this. There is an “immediate” version, where a fairly complete refresh is done on command of a human user. And there is a “background” version, where, as time permits, Compel will regularly and automatically refresh edge receivers on a rolling basis.
Command Structure:
Compel commands are structured as Header, Sequence number, Address, Device, Command, and Data fields. The Header may be a generic
Addressing Rules:
Except for the
www.wegener.com |
| Chapter 3, Page 41 |