36
S:\agilent\e8285\USRGUIDE\BOOK\CHAPTERS\getstart.fb
Chapter 1, Getting Started
GPIB Command Guidelines
Command Punctuation
NOTE:
Programming Language Considerations: The punctuation rules for the Test Set’s GPIB
commands conform to the IEEE 488.2 standard. It is possible that some programming
languages used on external controllers may not accept some of the punctuation requirements.
It is therefore necessary that the equivalent form of the correct punctuation, as defined by the
language, be used for GPIB operation. Improper punctuation will result in
GPIB Error: -
102 Syntax Error
.
Using Quotes for String Entries
Quotation marks are used to select non-numeric field settings. The value is
entered into the command line as a quoted alphanumeric string.
Quotes are used with all underlined (toggling) and one-of-many (menu choice)
fields. (See
"To Change a Field’s Setting" on page 31
.)
For example: to set the RF Generator’s
Output Port
field to duplex, the menu
choice
Dupl
would be entered into the command string.
“RFG:OUTP ’Dupl’”
Using Spaces
When changing a field’s setting, a space must always precede the setting value in
the command string, regardless of the field type.
RFG:FREQ
space
850MHZ
RFG:ATT
space
’OFF’
Using Colons to Separate Commands
The GPIB command syntax is structured using a control hierarchy that is
analogous to manual operation.
The control hierarchy for making a manual instrument setting using the front-
panel controls is as follows: first the screen is accessed, then the desired field +is
selected, then the appropriate setting is made. GPIB commands use the same
hierarchy. The colon (:) is used to separate the different levels of the command
hierarchy.
For example: To set the AF Analyzer’s input gain to 40 dB, the following
command syntax would be used:
“DISP AFAN”
“AFAN:INP:GAIN ’40 dB’”
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com