Description:
This command will execute DVC and SMIL files which may include placeholders and
wildcards. DVC files are subclassed by the first 3 letters of the filename.
The next 5 letters are for user use, with the exception of "AUTO", which is
used to signify autoexecuting files at power up or reset. The currently
supported subclasses of DVC are: "CMD" (Command files), "LST" (List files),
"SCH" (Schedule files), "PAR" (Parallel command map files).
LST files: This is a text file which has one spot name per line. Typical actions
associated with running are an implicit "initilization" which clears the current
playlist and an implicit "finalization" which immediately starts the new list
upon load.
Form:
Command Handler: SYSD
RUN|RUN|RU <OPTION> [ARGUMENT]
Argument List:
Options Description
D Debug output
I Do not initialize, relevant to "LST" and "SCH' files only
F Do not finalize, relevant to "LST" and "SCH' files only
M Add using multiples, relevant to "LST" only
C Always evaluate initialize directive, used for wildcard UNITS_NAMED mode
Tn Which tuner to direct a tuner type DVC file where 'n' is the tuner number.
Argument Description
filename Placeholders and wildcards valid
[file path]CMDxxxx.[DVC]
[file path]SCHxxxx.[DVC]
[file path]LSTxxxx.[DVC]
[file path]PARxxxx.[DVC]
[file path]TNRxxxx.[DVC]
[file path]MODxxxx.[DVC]
[file path]Any type of smil file
note: xxxx could be the name of any file
Information between brackets is optional
Response:
"OK\r\n" to acknowledge receipt of command, or
"ERROR- [Description]\r\n" if error, ending command
"\r\n" concludes modify responses (empty line)
Examples:
*.SYSD RUN LSTCLIP1
Response is: OK\r\n
r\n
The command runs a list file (right now, only smil clips are implemented)
*.SYSD RUN CMDAUTO
Response is: OK\r\n
\r\n
*.SYSD RUN CMDtest.DVC
Response is: OK\r\n
\r\n
The command runs a CMD dvc file.
*.SYSD RUN /var/loca/lib/sysd/file1.smil
Response is: OK\r\n
\r\n
The command runs a smil file
*.SYSD RUN T0 /media/hd0/dvc/tnrfile1.dvc
Response is: OK\r\n
\r\n
The command runs a tuner dvc file directed at tuner 0.
*.SYSD RUN /media/hd0/dvc/modfile1.dvc
Response is: OK\r\n
\r\n
The command runs a modulator dvc file directed at tuner 0.
Notes:
CMDxxxxx.DVC Files
Description- A Notepad file stored on an ADTEC unit’s hard drive that contains a list of
control commands. These commands can be RUN from any interrupt, Schedule,
Parallel Port, Terminal, or External Controller.
Form- CMDxxxxx.DVC
NAME Structure
CMD – File name MUST start with CMD
xxxxx – user definable name, limited to a maximum of 5 characters
.DVC - File MUST end with a “.DVC”
FILE FORMAT
CMD1 | CMD2 | CMD3
File Protocol Rules- Use all capital letters within the file and in the file name. Files
can be created in Notepad, saved, and then imported to an ADTEC unit
using the FTP applet. Files can also be created or edited in a text
editor such as notepad.
A command is placed into the CMDxxxx.DVC file on the first line of the
file. At the end of all command lines you MUST hit the RETURN Key,
leaving the courser on the line below the last command line.
Multiple commands are placed into the CMDxxxx.DVC file in a continuous
line. A pipe character MUST separate each command. To place the pipe,
hold the shift key and hit the backslash key. A pipe looks like a
vertical line ( | ).
The maximum number of commands is limited not by number of commands but
by characters in a single line. The maximum number of characters allowed
in a single line of commands is 1000. The 1000 max character number
includes spaces and pipes. (Spaces at the beginning and end of a
command are not required but will make it easier to read and edit a file.)
A file saved to an ADTEC unit’s hard drive must be “RUN” for it to be
loaded into volatile memory, and perform its tasks. The tasks in the
file will start as soon as the interrupt trigger is sent.
EX) “RUN CMD0001” <ENTER KEY>
In the above example the first command in CMD0001 will start when the
ENTER key is hit.
If the file name is CMDAUTO.DVC it will run automatically when the unit
is powered up.
At this time you cannot nest a RUN command with in a CMDxxxxx.DVC file.
SCHxxxxx.DVC Files
Description- A Notepad file stored on an ADTEC unit’s hard drive that contains a list of
times followed by a command. Commands associated with specific times will be
executed when the ADTEC Unit’s internal clock hits the desired time in the
command line.
Form- SCHxxxxx.DVC
NAME Structure
SCH – File name MUST start with SCH
xxxxx – user definable name, limited to a maximum of 5 characters
.DVC - File MUST end with a “.DVC”
FILE FORMAT
DAY, DATE, TIME, COMMAND
File Protocol Rules- Files can be created in Notepad, saved, and then imported to an ADTEC
unit using the FTP applet. Files can also be created or edited in a
text editor such as notepad.
Events are placed into the SCHxxxx.DVC file one time per line. After
the each event hit the RETURN key. After the last event you MUST hit
the RETURN Key, leaving the courser on the line below the last event.
Multiple commands are placed into the SCHxxxx.DVC file in a continuous
line. A pipe character MUST separate each command. To place the pipe,
hold the shift key and hit the backslash key. A pipe looks like a
vertical line ( | ).
The day abbreviations are MO, TU, WE, TH, FR, SA, and SU.
“--“ can be used as a wild cards. You can wild card any part of the
DAY, DATE, TIME
EX) MO -- -- -- 09 00 00 PLAY = every Monday @ 9 AM start to PLAY
If you name the file SCHAUTO.DVC it will run automatically when the
unit is powered up.
Form- TNRxxxxx.DVC
This file follows typical DVC format, except that it must contain a directive #TUNER_TYPE
followed by the tuner type from the SATUPGRADE command such as NTC7044 or ADT7201. This is
used to verify that commands will match the tuner type.
Form- MODxxxxx.DVC
This file follows typical DVC format, except that it must contain a directive #TUNER_TYPE
followed by the modulator type from the SATUPGRADE command such as NTC7039. This is
used to verify that commands will match the modulator type.
See Also: