Filter
Top Products
4 - 2 COMMAND REFERENCE
Notes:
(1) A message that is specified as a sequency of literals can be sent to the
instrument in any upper or lower case combination. The case of the
characters has no semantical meaning.
(2) Upper and lower case characters in a syntax specification are used to
distinguish between the short and long form of a mnemonic. Upper case
specifies the mandatory short form of a mnemonic. The lower case
characters specify the remaining part of the (optional) long form.
(3) Literals that are non-printable ASCII characters are underlined. For example,
the symbol NL
is used to specify the New Line character (0A
hexadecimal
).
(4) Some syntax specifications use the control symbol ^. The characters that
follow this symbol specify a special message that is concurrently sent with
the preceding data byte. For example, NL
^End specifies that the NL code is
sent concurrently with the End message (via the EOI line of the GPIB
interface).
META SYMBOL: MEANING: EXPLANATION:
= Is defined to be Specifies equality.
Example: <manufacturer> = FLUKE
| Alternative Specifies an "either" "or" choice.
Example: <result> = 0 | 1
< ... > Non-terminal A non-terminal is a message element
symbol whose syntax specification is defined
elsewhere. Example:
A node can be specified as INPut<n>.
The definition of <n> = [1] | 2 is specified
at another line or even somewhere else.
[ ... ] Default This means that the syntax may or may
not contain the message element in
between the square brackets, without
changing the semantical meaning. Example:
MEASure[:VOLTage][:DC]? means that
MEASure:VOLTage:DC? is the same
as MEASure? or MEASure:VOLTage?
or MEASure:DC?
{ ... } Repetition Specifies that the message element in
between the curly brackets may be
repeated 0 or more times. Example:
<parameter> {,<parameter>} specifies
a comma separated sequence of one or
more <parameter>’s.