REMOTE OPERATION
Command Syntax
03_10 LDX-36000 Series 55
CHAPTER 4
Syntax Summary
GPIB commands must contain all of the letters shown in uppercase in the
command definition. Optional letters shown in lowercase for some device
dependent commands in the command reference (Chapter 5) 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. Do not use white space before the
question mark in a query command.
If problems are encountered with communications, the terminator string may be
the cause. Refer to the GPIB interface (controller) manual for additional
information. 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 <CR> (Carriage
Return) as white space. The LDX-36000 terminates its responses with
<CR><NL><^END>, unless the TERM command is used to change it.
More than one command may be on the same line (same command string) if the
commands are separated with semicolons.
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.
Following are examples of invalid syntax command strings that will produce
errors:
Table 4.6 Invalid Syntax Command Strings
Command Comment
LAS:MODE CW Missing colon; MODE? expected
LAS:OUT ON INC Missing semicolon; INC command generates an error
LAS:DIS ? Space not allowed before question mark; DIS command expected
Las:LDI5.4;dis? Space missing between LDI command and the parameter value 5.4
To Next Page
Loading...
Need help?
General
