Syntax Summary; Table 3.2 Invalid Syntax Command Strings - ILX Lightwave LDT-5900 Series User Manual

3
C H A P T E R

Syntax Summary

GPIB or RS-232 commands must contain all of the letters shown in upper case in
the command definition. Optional letters shown in lower case for some device
dependent commands in the command reference are useful for clarity, but must
be in the correct sequence.
A single white space must separate a command from its parameters or data.
White space is normally the space character (space bar). Other control characters
are also interpreted as white space.
If you encounter problems with remote communications, the terminator string can
be the cause. The instrument accepts <NL>, or <^END>, or <NL><^END> as a
command line terminator. Many computers terminate with <CR> <NL> <^END>
(Carriage Return - New Line - EOI). The instrument ignores the <CR> (Carriage
Return) and treats it as white space.
You can put more than one command on the same line (same command string) if
you separate them with a semicolon.
GPIB uses a flexible representation for numeric parameters: integer, floating point,
or engineering/scientific notation. There are no default values for omitted
parameters.
Some device-dependent GPIB commands are compound commands, in which
the first mnemonic opens a path to a set of commands relating to that path. The
second mnemonic then defines the actual command.
Table 3.2 shows examples of invalid syntax command strings that produce errors:

Table 3.2 Invalid Syntax Command Strings

COMMAND
MODE
MODE T DEC
DISP ?
48
LDT-5980/ 5948
R E M O T E O P E R A T I O N S
Remot e Comm unica t ion
Note: Do not use white space before the question mark in a query command.
COMMENT
Missing ?, MODE? expected.
Missing semicolon, DEC command generates an
error.
Space not allowed before question mark, DISP?
command expected.