Tektronix 2230, Руководство по обслуживанию

Страница: 238 / 483

Options— 2230 Service
in mnemonics that are related to the functions imple­
mented. For example, the command INIt initializes instru­
ment settings to states that would exist if the instrument's
power was cycled. To further facilitate programming, com­
mand mnemonics are similar to front-panel control names.
NOTE
All measurement results returned by the options
have the same accuracy as the main instrument.
Commands
Commands for this instrument, like those for other
Tektronix instruments, follow the conventions established
in a Tektronix Codes and Formats Standard. The com­
mand words were chosen to be as understandable as pos­
sible, while still allowing a familiar user to shorten them as
much as necessary, as long as the result is not ambigu­
ous. Syntax is also standardized to make the commands
easier to learn.
In the command lists (Tables 7-13 through 7-24),
headers and arguments are listed in a combination of
uppercase and lowercase characters. The instrument
accepts any abbreviated header or argument containing at
least the characters shown in uppercase. Any characters
added to the abbreviated (uppercase) version must be
those shown in lowercase. For a query, the question mark
must immediately follow the header. For example, any of
the following formats are acceptable:
VMO?
VMOd?
VMOde?
Headers
A command consists of at least a header. Each com­
mand has a unique header, which may be all that is
needed to invoke a command; e.g.,
INIt
OPC
Arguments
Some commands require the addition of arguments to
their headers to describe exactly what is to be done. If
there is more to the command than just the header (includ­
ing the question mark if it is a query), then the header
must be followed by at least one space.
In some cases, the argument is a single word; e.g.,
REFF REF4
PLOt STArt
In other cases, the argument itself requires another
argument. When a second argument is required, a colon
must separate the two arguments; e.g.,
ACQuisition REPetitive:SAMple
WFMpre XINcr:1.0E-3
Where a header has multiple arguments, the arguments
(or argument pairs, if the argument has its own argument)
must be separated by commas; e.g.,
DATa ENCdg:BINary,CHAnnel:CH2
VMOde? CHI ,CH2,ADD
Default Argum ents
Arguments shown within brackets ([argument]) are
defaults. In any command that has a default, omitting the
default argument selects the default. Do not confuse
default arguments with power-up default conditions; the
power-up defaults may differ from the argument default in
the same function. The default argument may be sent in
any command. Do not send the brackets as part of the
default argument. All commands that do not have a default
must always include a argument, where one or more
exists.
Command Separator
It is possible to put multiple commands into one mes­
sage by separating the individual commands with a semi­
colon; e.g.,
DATa ENCdg:BINary,CHAnnel:CH2;WFMpre XINcr:1.0E-3
Command Formatting
Commands sent to the oscilloscope must have the
proper format (syntax) to be understood; however, this
format is flexible in that many variations are acceptable.
The following paragraphs describe this format and the
acceptable variations.
The oscilloscope expects all commands to be encoded
as either uppercase or lowercase ASCII characters. All
data output is in uppercase.
Spaces, Carriage Returns, and Line-Feed characters
are all formatting characters that can be used to enhance
the readability of command sequences. As a general rule,
these characters can be placed either after commas and
semicolons or after the space that follows a header.
7-11