Fluke 9100 Series, Руководство пользователя

Страница: 30 / 274

6-24 Section 6: 9100 System Operation — SCPI Language
Final Width = 215mm
6.6 9100 SCPI Language - Commands and Syntax
The command subsystems are placed in alphabetical order.
6.6.1 Introduction
This Sub-Section lists and describes the set of SCPI-compatible remote commands used to operate the 9100.
To provide familiar formatting for users who have previously used the SCPI reference documentation, the command descriptions
are dealt with in a similar manner. In particular, each sub-system's documentation starts with a short description, followed by a table
showing the complete set of commands in the sub-system; finally the effects of individual keywords and parameters are described.
Some extra identification of style and syntax is detailed in paras 6.6.1.1 and 6.6.1.2 to clarify shorthand meanings.
6.6.1.1 SCPI Syntax and Styles
Where possible the syntax and styles used in this section follow those defined by the SCPI consortium. The commands on the
following pages are broken into three columns; the KEYWORD, the PARAMETER FORM, and any NOTES.
The KEYWORD column provides the name of the command. The actual command consists of one or more keywords since SCPI
commands are based on a hierarchical structure, also known as the tree system.
Square brackets ( [ ] ) are used to enclose a keyword that is optional when programming the command; that is, the 9100 will process
the command to have the same effect whether the optional node is omitted by the programmer or not.
Letter case in tables is used to differentiate between the accepted shortform (upper case) and the long form (upper and lower case).
The PARAMETER FORM column indicates the number and order of parameter in a command and their legal value. Parameter
types are distinguished by enclosing the type in angle brackets ( < > ). If parameter form is enclosed by square brackets ( [ ] ) these
are then optional (care must be taken to ensure that optional parameters are consistent with the intention of the associated keywords).
The vertical bar ( | ) can be read as "or" and is used to separate alternative parameter options.
6.6.1.2 Legend
<DNPD>
= Decimal Numeric Program Data, used to identify numerical information needed to set controls to required
values. The numbers should be in 'Nrf' form as described in the IEEE 488.2 Standard Specification.
<CPD>
= Character Program Data. This normally represents alternative groups of unique 'literate' parameter names,
available for the same keyword. In the notation the set of alternatives will follow the
<CPD>
in the Parameter
Form column of the Sub-System table, enclosed in a pair of braces. For example, in the OUTPut sub-system,
the compound command header (keyword):
OUTPut:COMPensation
is followed by the parameter form
<CPD>{ON|OFF|0|1} . The <CPD> gives the denomination of 'Character' program data, and
{ON|OFF|0|1} gives the actual characters to be used to command each unique parameter.
<SPD>
= String Program Data. This is a string of variable literate characters which will be recognized by the internal
9100 software. They are used for such inputs as passwords, serial numbers and date/time.
?
= Indicate query commands with no associated command form, and no attached parameters.
(for example:
CALibration:TRIGger?
).
(?)
= All commands which may include parameters in the command form, but also have an additional query form
without parameters.
(for example: OUTPut:COMPensation(?) <CPD>{HIGHi|LOWi} )
The response from this query will be one of the parameters listed in association with the command.