Apply Changes To Parameter Configuration Updates; Save Changes To Parameter Configuration Updates; Error Handling In The Cli - VBrick 9000 Getting Started Manual

Command Line Interface
Single Index Example
This example shows how to read and change the parameter on Channel 1.
Brightness
VBrick# gvar vbrickEncoderVideoCommonBrightness.1
$!vbrickEncoderVideoCommonBrightness.1=50
VBrick# svar vbrickEncoderVideoCommonBrightness.1=75
$!vbrickEncoderVideoCommonBrightness=75
Double Index Example
This example shows how to read and change the Rate 1 parameter on Channel 1.
Resolution
VBrick# gvar vbrickEncoderVideoH264Resolution.1.1
$!vbrickEncoderVideoH264Resolution.1.1=15
VBrick# svar vbrickEncoderVideoH264Resolution.1.1=2
$!vbrickEncoderVideoH264Resolution=2

Apply Changes to Parameter Configuration Updates

The command is used to apply changes to configuration updates. There is one
ApplySet
command per program group in the MIB and the syntax varies slightly according to
ApplySet
the group.
Use this command, for example , to actually apply the
vbrickProgramTransmitterApplySet
change(s) you made with a or a . An is always written in the following
SVAR STAB ApplySet
format with the trailing .
=2
VBrick# svar vbrickEncoderVideoCommonApplySet.1=2
It is important to note that some ApplySets can cause the encoder to send unsolicited
messages. For example, the encoder may reboot with the following message:
$!Rebooting ...

Save Changes to Parameter Configuration Updates

Once you are done, you must save to persistent storage if you want your edits saved in the
configuration file. Unless you save the configuration, any changes you have made will be lost
if the encoder reboots.
A save is always written in the following format with the trailing . Note that some changes
=2
to the configuration will reboot the encoder in which case you must wait for it to reset. Note
that you can also use the command as a shortcut.
SAVE
VBrick> svar vbrickSysSaveConfiguration=2

Error Handling in the CLI

Programming errors, for example syntax errors, illegal values, and so forth display
informational messages in the CLI; for example . Other system
$!ERROR=Value out of range
or network issues, for example a dropped connection or a failed save (see below) are shown
in the System Log (VBAdmin > Monitor > System Logs > Configuration Log).
You can also see all configuration errors using the command. Potential errors may
ERRORS
be detected in advance by getting the value of various status parameters in the encoder. For
example, if you are writing a script, you might want to check or
Transmitter State FTP Status
before you set parameters for a related task.
Encoder Getting Started 43