Table 3.2 Invalid Syntax Command Strings - ILX Lightwave FPM-8200 User Manual

Fiber optic power meter
Table of Contents

Advertisement

3
C H A P T E R
characters are also interpreted as white space. Do not use white space before the
question mark in a query command.
If you encounter problems with GPIB communications, the terminator string can
be the cause. Refer also to your GPIB interface (controller) manual. The FPM-
8200 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 FPM-8200 ignores <CR> (Carriage Return) as white space. The
FPM-8200 terminates its responses with <CR><NL><^END>, unless you use the
TERM command to change it.
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 FPM-8200 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 3.2 Invalid Syntax Command Strings

COMMAND
Mode dB
Mode:dBm Range:Auto
DIS ?
Ran3;dis?
Disply ON
Wave
30
FPM-8200
R E M O T E O P E R A T I O N
Command Syntax
COMMENT
Compound command, missing colon between MODE and DB.
Missing semicolon between commands.
Space not allowed before question mark in queries.
Missing space between Ran and parameter 3.
Optional letters must follow the correct order.
Wavelength parameter missing.

Advertisement

Table of Contents
loading

Table of Contents