
LongRanger 2050 Operator’s Manual
9
6.1
Command syntax
The command interpreter in the
LongRanger 2050
is designed to accommodate both a novice as
well as an expert operator. All commands and parameters have descriptive names so that they are
easily remembered and their meaning is clear. In order to be descriptive however, those
commands are sometimes long. As the operator becomes familiar with the command language,
typing the complete words could become cumbersome. The
LongRanger
command interpreter
recognizes any abbreviations to commands and parameter names, as long as they are
unambiguous. If an ambiguous command is entered, the radio will output all possible choices.
Commands have the following generic form:
command parameter=value parameter=value
Following is a brief list of syntax rules:
•
Words (for commands, parameters, or values) can be abbreviated to a point where they are
unambiguous.
•
Some commands or parameters consist of compound words separated by an hyphen. With
compound words, the hyphen is optional. Additionally each word in a compound word can
be abbreviated separately. For example, the following are all valid abbreviations for the
command “data-port”: “data”, “datap” d-p” “dp”.
•
The parameter and value lists are context sensitive, i.e., in order to solve ambiguities the
command interpreter only considers parameters valid for current command, or values valid
for the current parameter.
•
Arguments (parameter/value pairs) can be listed in any order.
•
Even though parameters can be listed in any order, there is a “natural” order known by the
command interpreter. This allows the user to specify parameter values without having to type
the parameter names. For example the command
>copy-configuration source=factory-master dest=current
can be entered as (using abbreviation rules as well):
>copy fm cur
•
Using the preceding rule, for commands that have a single argument, the “parameter name”
part of the argument is always optional, i.e., you can enter:
>
command value
•
Not all parameters associated with a command need to be specified. Depending on the
command, when a parameter is omitted it either assumes a default value or keeps the last
value assigned to that parameter.