The WILTRON product(s) listed on the title page is (are) warranted against defects in materials and
workmanship for one year from the date of shipment.
WILTRON’s obligation covers repairing or replacing products which prove to be defective during the
warranty period. Buyers shall prepay transportation charges for equipment returned to WILTRON
for warranty repairs. Obligation is limited to the original purchaser. WILTRON is not liable for
consequential damages.
LIMITATION OF WARRANTY
The foregoing warranty does not apply to WILTRON connectors that have failed due to normal
wear. Also, the warranty does not apply to defects resulting from improper or inadequate
maintenance by the Buyer, unauthorized modification or misuse, or operation outside of the
environmental specifications of the product. No other warranty is expressed or implied, and the
remedies provided herein are the Buyer’s sole and exclusive remedies.
Page 3
CONTENTS
Tab / Section Title
1General GPIB Information
This section describes the manual and contains a brief description of the GPIB hardware and
the GPIB data transfer and control functions. It also describes the 360 VNA GPIB interface
function subset capability and response to IEEE-488 interface function messages.
2Introduction to GPIB Programming for the 360 VNA
This section contains a brief introduction to GPIB programming techniques and describes
procedures to be used when preparing GPIB programs for the 360 VNA. It includes information about 360 GPIB command syntax, programming tips and example programs.
3Commands for Basic Front Panel Operations
This section describes the 360 VNA GPIB commands that control the basic test and measurement functions a ssociated w ith fron t panel co ntrols and men u s. The comman d de scription s are
grouped by control function, for example: Data Entry Commands, Hard Copy Commands, etc.
4Commands for Calibration Functions
This section describes the 360 VNA GPIB commands used to perform system calibration
functions. As in Section III, the command descriptions are grouped by control function.
5Advanced GPIB Programming and GPIB Unique Functions
This section describes the 360 VNA GPIB commands that produce operations that are unique
to the GPIB mode of operation. Example commands included are: Data Transfer commands,
Group Execute commands, etc. As in the previous sections, the command descriptions are
grou ped b y cont rol funct ion .
6Supplements
Included behind this tab are two application notes that contain information about GPIB
programming for the 360 VNA:
AN360-8, Programming the Model 360 Vector Network Analyzer Using Microsoft C
AN360-9, Programming the Model 360 Vector Network Analyzer Using HP Basic
7GPIB Command Function Index
This index lists the GPIB commands for the 360 VNA by function. The paragraph number and
page number for each of 28 GPIB command function categories are reference in this index.
8GPIB Quick Reference Guide
This Quick Reference Guide is an alphabetical list of the GPIB commands for the 360 VNA.
The listing for each command includes a brief description of the command function and
attributes (such as associated parameters). This document is also an alphabetical index to the
360 Vector Network Analyzer GPIB Programming Manual. The listing for each command
includes a reference to the paragraph in the programming manual that includes the complete
description of the command.
Part No. 11410-00038
Part No. 11410-00039
Microsoft C is a registered trademark of Microsoft Corporation.
This manual describes remote operation of the WILTRON 360 Vector Network Analyzer usin g IEEE-488
Interface Function Messages and 360 GPIB Commands (i.e., Product Specific Commands). The software version supported by this manual is Version
3.07.
Included is a description of the IEEE-488 General
Purpose Interface Bus (G PIB) hardwar e and the bu s
data transfer and control functions. Also includ ed is
a brief intr oduction to GPIB pr ogrammin g, inclu ding
considerations for preparing GPIB programs for the
360 Vector Network Analyzer (VNA). All 360 VNA
GPIB commands currently used are listed and described.
The information about the IEEE-488 interface bus
presented in this manual is general in nature. For
complete and specific information, refer to the
ANSI/IEEE Std 488-1978 document entitled “IEEE
Standard Digital Interface for Programmable
Instrumentation”. This document precisely defines
the set of dedicated hardware signal lines, interface
functions, protocols, and messages for the interface
bus.
1-1.1Relat ion ship of T his Man ual t o Ot her
360 VNA M anu als
This manual is intended to be used in conjunction
with the 360 Vector Network Analyzer System Operation Manual. Refer to that manual for general
information about the 360 VNA, including equipment set up and manual mode operating instructions. Section I of that manual lists and describes all
360 VNA documen ta tion set manuals, including test
set and software manuals.
1-1.2How t o Use This Manu al
Only information pertinent to 360 VNA GPIB programming is provided in this manual. Familiarity
with manual (front panel) operation of the 360 VNA
is assumed. System operating details are given in
this manual only if they are unique to the GPIB
operating mode, o r are diffe rent th an w hen oper ated
in the normal manual mode.
This section of the man ual descr ibes the manual an d
contains a brief description of the GPIB hardware
and the GPIB data transfer and control functions. If
you are already familiar with this material, this
section may be skipped. The remainder of the manual is organized as follows:
Section II — Introdu ction to GPIB Programming
•
for the 360 VNA — contains a brief introduction
to GPIB programming techniques and describes
procedures to be used when preparing GPIB programs for the 360 VNA. If you are already familiar with this material, this section may be
skipped.
Sections III, IV and V — describe the 360 GPIB
•
commands used for Basic Front Panel Functions,
Calibration Functions and Advanced Programming/GPIB Unique Functions, respectively. The
programming information and tables containing
the command descriptions are grouped by func-tion in these sections. Use this information as a
tutorial and for reference when preparing programs.
The Functional Index Of Commands — lists the
•
360 GPIB commands by function and references
the paragraph, table and page number where the
descriptions for that group of commands are located in Sections III thru V.
360 GPIB Quick Reference Guide — This sepa-
•
rately bound document is located behind the last
section tab of this manual. It lists the 360 GPIB
commands alphabetically and references the loca-
tion in Sections III thru V of this manual where
information for each command is located. The listing in this guide for each command includes a
brief description of the command function and
associated parameters. Use this guide as a quick
reference when preparing programs.
360 GPIB PM1-3
Page 6
DESCRIPTION OF THE IEEE-488 (IEC-625) INT ERF ACE BUSI GENERAL INFORMATIO N
1-1.3Command Categories Used in This
Manual
The 360 VNA GPIB interface responds to more than
400 commands to implement the set of 360 network
analyzer functions. For descriptive purposes, these
commands are organized into the following functional classifications:
a. Basic Front Panel Functions
These commands produce basic 360 VNA measurement operations identical to those produced
by the corresponding key functions on the 360
front panel. These commands are described in
Section III.
b. Calibration Functions
The set of calibration commands can be used to
set up the calibration parameters under program control and to guide an operator through
the 360 VNA calibration process. These commands are described in Section IV.
c. GPIB Unique Functions
These commands produce 360 VNA operations
that are unique to the GPIB mode of operation
or are operations that are best done using computer control of the system. They are described
in Section V.
1-2DESCRIPTION OF THE IEEE-488
(IEC-625) INTERFACE BUS
The IEEE-488 General Purpose Interface Bus
(GPIB) is an instrumentation interface for integrating instruments, computers, and other controllers
into systems. The bus uses 16 signal lines to effect
transfer of data and commands to all instruments
connected on the bus.
No more than 15 instruments may be connected to
the interface bus (however, a system may contain
more than one interface bus). The maximum total
accumulative cable length for one interface bus may
not exceed twice the number of instruments connected (in meters) , or 20 meters—whichever is less.
The instruments on the bus are connected in
parallel, as shown in Figure 1-1. Eight of the signal
lines (DIO1 thru DIO 8) are used for the transfer of
data and other messag es in a byte-se rial, bit-parallel
form. The remainin g eight lines ar e used for communications timing (handshake), control, and status
information. Data are transmitted on the eight
GPIB data lines as a series of eight-bit characters,
referred to as bytes.
Data transfer is by means of an interlocked handshake technique (Figure 1-2). This technique
permits asynchronous communications over a wide
range of data rates. The following paragraphs
provide an overview of the data, and handshake
buses, and describe how these buses interface with
the 360 VNA.
1-2.1IEEE-488 Hardware Interface
The IEEE-488 interface bus hardware implementation is made up of 16 sign al lines that comp rise thr ee
functional groups; see Figure 1-1.
Data Bus (8 lines)
•
Data Byte Transfer Control Bus (3 lines)
•
General Interface Management Bus (5 lines)
•
The signal lines in each of the three groups are
designated according to function. Table 1-1 lists
these designations.
1-2.2Data Byte Transfer Control Bus De-
scription
Control of information transfer on the GPIB data
Bus is accomplished by a technique called the “threewire handshake”, which involves the three signal
lines of the Data Byte Transfer Control Bus. This
technique is described briefly below and is depicted
in Figure 1-2. For further information, refer to the
ANSI/IEEE Std 488-1978 document.
a. DAV (Data Valid)
This line goes TRUE (arrow 1) when the talker
has (1) sensed that NRFD is FALSE, (2) placed
a byte of data on the bus, and (3) waited an
appropriate length of time for the data to settle.
Table 1-1. Interface Bus Signal Line Designations
BUS TYPESIGNAL LINE
NameFunction
Data BusDIO1–
DIO8
Data Byte
Transfer
and Control
General
Interface
Control
DAV
NRFD
NDAC
ATN
IFC
SRQ
REN
EOI
Data Input/Ou tput, 1 th ru 8
Data Available
Not Ready For Data
Not Data Accepted
Attention
Interface Clear
Service Request
Remote Enable
End Or Identify
1-4360 GPIB PM
Page 7
I GENERAL INFORMAT IONDESCRIPTION OF THE IEEE-488 (IEC-625) INT ERF ACE BUS
IEEE-488 BUS (16 Lines)
DEVICE A
Able to talk, listen,
and control
(e.g. EXTERNAL
COMPUTER)
DEVI CE B
Data Bus
(8 signal lines)
DATA LINES
Able to talk and listen
(e.g. 360 VNA)
DEVICE C
Only able to listen
(e.g. OTHER
INSTRUMENT**)
DEVIC E D
Only able to talk
(e.g. OTHER
INSTRUMENT**)
Data Byte
Transfer Contr ol
(3 signal lines)
HANDSHAKE Lines
General Interface
Management
(5 signal lines)
DATA INPUT/OUTPUT, DIO 1 thru DIO 8
Management
CONTROL Lines
DATA VALID
NOT READY FOR DATA*
NOT DATA ACCEPTED*
-
INTERFACE CLEAR
ATTENTION
-
-
SERVICE REQUEST
-
REMOTE ENABLE
-
END OR INDENTIFY
NEGATION I S REPRESENTED
Note:
*
BY LOW STATE ON THESE
TWO LINES
IF USED
**
Figure 1-1. Interface Connections and Bus Structure
360 GPIB PM1-5
Page 8
DESCRIPTION OF THE IEEE-488 (IEC-625) INT ERF ACE BUSI GENERAL INFORMATIO N
b. NRFD (Not Ready For Data)
This line goes TRUE (arrow 2) when a listener
indicates that valid data has not yet been accepted. The time between the events shown by
arrows 1 and 2 is var iable an d depen ds up on the
speed with which a listener can accept the information.
c. NDAC (Not Data Accepted)
This line goes FALSE to indicate that a listener
has accepted the current data byte for internal
processing. When the data byte has been accepted, the listener releases its hold o n NDAC
and allows the line to go FALSE. However, since
the GPIB is constructed in a wired-OR configuration, NDAC will not go FALSE until all listeners participating in the interchange have also
released the line. As shown by arrow 3, when
NDAC goes FALSE, DAV follows suit a short
time later. The FALSE state of DAV indicates
that valid data has been removed; consequently,
NDAC goes LOW in preparation for the next
data interchange (arrow 4).
Arrow 5 shows the next action in time: NRFD
going FALSE after NDAC has returned TRUE.
The FALSE state of NRFD indicates that all
listeners are ready for the next information interchange. The time between these last two
events is variable and depends on how long it
takes a listener to p roce ss the data byte. In summation, the wired-OR construction forces a
talker to wait for the slowest instrument to accept the current data byte before placing a new
data byte on the bus.
1-2.3IEEE-488 Interface Functions and Pro-
tocols
The IEEE-488 standard document describes a total
of 11 different possible interface functions. Each of
these interface functions acts in accordance with a
specific protocol defined in the standard. This set of
functions an d protocols define every possible manner
that information and control can be passed between
devices connected to the GPIB.
Specific instruments, such as the 360 VNA, are
implemented using only a portion, or subset, of the
total set of interface functions defined by the standard. Table 1-2 lis ts the functional subset supported
by the 360 VNA.
There are three types of information transmitted
over t h e G PI B :
IEEE Interface Function Messages — These
•
messages are sent on the data lines and interface
management lines to control the state of the interface and the manner in which it responds to
commands. These messages are used to maintain
control of the interface. The user generally has
control over these signals; however, the extent of
user control is implementation-dependent and
varies with the specific hardware and software
used with the external controller.
Product-Specific Commands — These com-
•
mands are mnemonic codes sent by the external
computer to the 360 VNA to contr ol the setu p and
measurement operations of the 360 VNA. The
function and contents of these commands are not
specified by the IEEE-488 standard. They are
unique and specific to the WILTRON 360 VNA
and are described in Sec tio ns III , IV, and V of thi s
manual.
1-6360 GPIB PM
Page 9
I GENERAL INFORMAT IONDESCRIPTION OF THE IEEE-488 (IEC-625) INT ERF ACE BUS
These commands (also referred to as “360 GPIB
commands”) are transmitted over the data bus of
the GPIB interface to the 360 VNA in the form of
ASCII strings containing one or more codes. They
are decoded by the internal 360 VNA controller
and cause the various measurement functions of
the system to be performed. (The 360 VNA GPIB
interface doe s not dec od e these command s; it on ly
acts as the transmission channel to the internal
controller.)
Data and Instrument Status Messages —
•
These messages are sent by the 360 VNA to the
external computer via the GPIB. They contain
measurement data, setup information, or system
status information that the 360 VNA transmits
over the data bus in response to specific commands from the ex ter nal c ompu ter requ estin g the
data. The contents of these messages are specific
to the 360 VNA. They may be in the form of ASCII
strings, or binary data.
In some cases data messages will be transmitted
from the external computer to the 360 VNA. For
example, mess ages to load calibration data.
An SRQ (service request) is an interface function
message sent from the 360 VNA to the external
computer to request service from the computer,
usually due to some predetermined system condition or error. To send this message, the 360 VNA
sets the SRQ bit of the General Interface Manage-
ment Bus true and then sends a status byte on
the data bus lines.
An SRQ interfac e function message is also sent by
the 360 VNA in response to a serial poll message
from the computer, or upon receiving either an
OEB or OPB command from the computer. The
protocols associated with the SRQ functions are
defined in the ANSI/IEEE Std 488-1978 document. The 360 GPIB commands for these functions along with the SRQ status byte format information is contained in Paragraph 5-6 — SRQ
Status Bytes: Commands — in this manual.
The manner in which Interface Function Messages
and Product-Specific Commands are invoked in programs is implementation specific for the GPIB interface used with the external computer. Even though
both message types are represented by mnemonics,
they are implemented and used in different ways.
The Interface Function Messages normally are sent
automatically by the GPIB driver software in response to invocation of a software function. For example, to send the
one would call the
SDC interface function message,
ibclr function of the National
Instruments software driver. On the other hand, the
360 GPIB command
RST is sent in a string message
to the addressed device (e.g. 360 VNA). In the case
of the National Instruments example, this would be
done by using the
ibwrt function call.
DAV
1
4
2
NRFD
3
5
NDAC
Figure 1-2. Typical GPIB Handshake Operation
FALSE (0/HIGH)
TRUE (1/LOW)
FALSE (0/HIGH)
TRUE (1/LOW)
FALSE (0/HIGH)
TRUE (1/LOW)
360 GPIB PM1-7
Page 10
360 VNA GPIB OPERATION I GENERAL INFORMATIO N
1-3360 VNA GP IB O PER ATIO N
All of the front panel control functions of the 360
VNA, except for LINE ON/O FF, are controllable usin g
360 GPIB commands sent from the external computer. When in the GPIB operating mode, the 360
VNA functions as both a list ener and a talker (Table 1-2).
1-3.1Setting Default GPIB Operating Pa-
rameters
The 360 VNA GPIB address value is set to 6 at t he
factory. This value may be changed via the GPIBSETUP MENU (from the UTILITY MENU); refer to
Index A1 of th e 360 V ector Network Analy zer System
Operation Manual. The data delimiting terminator
is set as CR/CR-LF at the factory. This may also be
changed via the GPIB SETUP MENU.
1-3.2Response to GPIB Interface Function
Messages
Table 1-3 lists the set of IEEE–488 Interface Function Messages that the 360 VNA will rec ognize. W ith
the exception of the
DCL and SDC messages, these
messages affect only the operation of the 360 VNA
GPIB interface. The response of the 360 VNA GPIB
interface for each message is included in Table 1-3
(next page).
Interface function messages are transmitted on the
GPIB data lines and interface management lines as
either unaddressed or addressed commands. The
manner in wh ic h these messages are in vo ked in programs is implementation dependent. For programming information, refer to the documentation included with th e GPIB Inte rface for the external co mputer used.
1-3.3360 VNA Response To GPIB Error
Condi tions
The following par agrap hs describe ho w the 360 VNA
responds to error conditions during the GPIB mode
of ope rat ion
a. Sy nta x Er ror
The 360 beeps and sends a Service Request
(SRQ) to the external computer (if SRQs are
enabled). The 360 also ignores any further
commands until it is programmed to talk or be
unlistened.
b. Parameter Out Of Range Error
Upon detec ting th is condition , the 360 move s the
cursor adjacent to the erroneous entry, beeps,
and displays the entry in red. It also sends an
SRQ (if enabled) to the external computer. The
error is cleared upon execution of the next instruction.
c. Action Requested Not Possible
The 360 sends an SRQ (if enabled) to the external computer and ignores the command.
1-8360 GPIB PM
Page 11
I GENERAL INFORMAT I ON360 VNA GPIB OPERATI O N
Table 1-3. 360 VNA Response to IEEE-488 Interface Function Messages
Interface
Function
Message
DCL
SDC
Message Function
Device Clear
Selected Device Clear
Addressed
Command
No
Yes
360 VNA Response
Resets the 360 to its default state. Equivalent to the RST
command.
GTLGo To LocalYesReturns the 360 to local (control panel) control.
GETGroup Execute TriggerYesExecutes a string of commands defined by the DEF...END
mnemonics.
NOTE
The GET command is buffered and executed inline with oth er c o mma nds .
IFCInterface ClearNoStops the 360 GPIB from talking/listening.
LLOLocal LockoutNoDisables the control panel RETURN TO LOCAL key
RENRemote EnableNoPlaces the 360 in remote when addressed to listen
SPESerial Poll EnableNoOutputs the binary status byte
SPDSerial Poll DisableNoDisables the serial poll function
PPCParallel Poll ConfigureYesSets the assigned bus line to reflect its SRQ status
PPEParallel Poll EnableYesEnables the 360 for parallel poll operation
PPUParallel Poll UnconfigureNoCancels any previous parallel poll configurations
PPDParallel Poll DisableYe sDisables the parallel polling function
Note:These are
included with the GPIB Interface for the external co mputer used .
not
Device Specific Commands. These messages are implementation dependent — refer to the documentation
* Not used if Signal Source is 67XXB Series
(Refer to 360 VNA Operation Manual).
** Dedicated GPIB for 360 System use.
Figure 2-1. Minimum 360 VNA Configuration with GPIB Control
2-2360 GPIB PM
Page 14
SECTION II
INTRODUCTION TO GPIB PROG RAMMING
FOR THE 360 VNA
2-1INTRODUCTION
This section contains a brief introduction to GPIB
programming techniques and describes procedures
to be used when preparing GPIB programs for the
360 VNA. It includes information about equipment
requirements and configuration for GPIB control of
the 360 VNA, 360 GPIB command syntax, and programming tips. Example programs are pr ovided that
familiarize the user with the most frequently used
360 GPIB commands.
Familiarity with manual (front panel) operation of
the 360 is assumed. (Throughout this section, the
360 VNA is referred to simply as “360”.) A complete
description of front panel operation is contained in
the 360 Vector Network Analyzer System Operation
Manual.
2-2EQUIPMENT AND CONFIGURATION
The programming examples contained in this tutorial assume that the equipment listed below is present and configured as described.
4. Appropriate software:
•
Microsoft QuickBASIC, version 4.0 (or later);
•
Microsoft “C”, version 5.1 or later; or:
•
HP BASIC, version 5.0 or later (for HP computers).
•
Any other programming language that supports the National Instruments PC2 or PC2A
IEEE-488 interface c ar d (Pa scal, Fortr an, etc ).
5. A GPIB cable (preferably 2 meters long).
2-2.2 Configuration
Configure the 360 as shown in Figure 2-1 (facing
page). Apply power to the 360 and allow the system
software to load from disk. Once the software has
finished loading, the 360 is ready to be remotely
controlled via the GPIB. It is important to note that
the 360 will not re spond to GPIB commands unt il the
360 system software has been loaded.
If not previously done, connect a GPIB cable from
the computer/ contr oller to the “360 GPIB” connec tor
on the rear panel of the 360 Network Analyzer.
2-2.1Required Equipment
The following equipment represents a minimum
GPIB controllable 360 VNA system:
1. A 360 Ve ctor Network Analyzer consisting of:
•
A 360 Network Analyzer unit
•
A 3600A Series Test Set
•
A compatible WILTRON Signal Source
(360SSXX, 66XXB, 67XXB, etc).
2. A computer/controller that supports the
IEEE-488 GPIB standard. The examples in
this section address the following two computer
types:
•
IBM XT, AT, and PS/2 compatibles,
•
Hewlett Packard 9000 and Vectra series
3. An IEEE-488 GPIB interface (built in, or add-in
peripheral card) with appropriate driver software. The National Instruments PC2 or PC2A
IEEE-488 interface card is assumed for all
IBM compatible computers.
360 GPIB PM2-3
The 360 Network Analyzer has two GPIB
busses: the “360 GPIB” that connects the
360 Network Analyzer unit to the computer/controller and the “SYSTEM
CONTROL” bus (which connects to the
signal source(s) and a system plotter—if
used).
Apply power to the computer /c ontroller and load the
appropriate programming language software
(QuickBASIC, “C”, or HP BASIC). This tutorial contains programming examples written in each of
these three languages, as explained in paragraph 2-4.
2-2.3Default GPIB Operating Parameters
The default GPIB address for the 360 is 06, and the
default data delimitin g terminator is CR/CR-LF. The
default values for these GPIB operating parameters
NOTE
Page 15
360 GPIB
PROGRAMMING BASICS
II INTRODUCTIO N TO GPIB PRO GRAMM ING
FOR THE 360 VNA
may be changed via the GPIB SETUP MENU (from
the UTILITY MENU); refer to Index A1 of the 360
Vector Network An alyzer System O peration Manu al.
2-3360 GPIB PROGRAMMING BASICS
In the “remote” mode of op eration, the 360 is controlled using IEEE-488 Pr odu ct Spec ific Comman ds an d
Interface Function Messages. The Product Specific
Commands are a set of pre-defined mnemonics that
are unique to the WILTRON model 360 Vector Network Analyzer. (Refer to paragraph 1-2.3 for further
information .) In this manual, they are refer r ed to as
“360 GPIB commands” or simply “commands”.
These commands may be issued one at a time or in
a sequence (i.e., a command string). Commands,
command strings, and IEEE-488 Interface Function
Messages can be included as part of a program run
on an external computer/controller to remotely
stimulate the 360 to perform particular microwave
measurement operations.
2-3.1360 GPIB Command Set
There are approximately four hundred 360 GPIB
commands. These commands allow the user to program every front panel and menu function of the
360. These many commands reflec t the ability of the
360 to perform many specialized functions; however,
typical programs written for ATE applications usually use a small subset of these.
terminator code; example:
SRT 2 GHZ (start freq-
uency = 2 GHz).
The commands for all numeric entry, such as freq-
uency, scale, reference position, etc, include a data
entry followed by a terminator code. All commands
that require data must have a valid terminator code
following the data e ntry.
The 360 will accept multiple commands in string
format. Separator characters may be used to improve program readability, but are not required.
a. Termi nator Cod es
These terminators are codes which perform the
same function as the termination keys located
on the front panel of the 360. For example: to
enter a start fr equ en cy usin g th e 360 fr ont pan el
keys, type “40"; then press the ”MHz" terminator
key. Likewise, a numeric entry in a GPIB program must be termin a ted by one of the terminator codes listed in Table 3-2.
b. Separator Characters
Separator characters may be used between commands and between data or other mnemonics to
improve program readability. Their use is optional. The more common permitted separator
characters are: space, comma, and semicolon.
2-3.3Programming Tips
The list of GPIB commands may seem intimidating
at first glance; however, it can actually be broken
down into a few, easy-to-remember categories that
reflect th e major f unction s and operation s of the 360.
The GPIB Command Function Index located behind
its section tag at the rear of this manual provides
and overview (and index to) these command group
categories. A complete listing and description of all
360 GPIB commands is provided in Sections III, IV,
and V.
2-3.2Command Syntax
The 360 GPIB commands are nothing more than a
shorthand method for repr esenting instr u ment commands. Most 360 GPIB commands are three character contractions of their titles or descriptions; for
example:
RST (reset). Depending on function, some
commands must be followed by a numeric value and
The 360 is a “channel-based” instrument, which
means that most commands apply only to the current active channel. Therefore, to set up a desired
state for multiple channels, a
This command string sets up a quad display (D14)
and then sets the S-parameter and graph type desired for each Channel:
Channel 1:
Channel 2:
Channel 3:
Channel 4:
S11, Smit h chart;
S12, log magnitude and phase;
S21, log magnitude;
S22, inverted Smith chart).
Other commands are “global” in their extent, meaning they apply to all channels. Examples of these
commands: start/stop frequency (
ing (
AVG,AOF), and source power (PWR).
SRT,STP), averag-
2-4360 GPIB PM
Page 16
II INTRODUCTION TO GPIB PROGRAM MI NG
FOR THE 360 VNATYPICAL GPIB PROGRAM STRUCTURE
2-4TYPICAL GPIB PROGRAM
STRUCTURE
A typical GPIB program may be composed of the
following basic functional program groups:
Preliminary GPIB Control Establishment
•
Calibration
•
Front Panel Setup
•
Measurement
•
Data Transfer
•
QuickBASIC example:
CALL IBFIND (“DEV6", vna%)
CALL IBCLR
Microsoft C example:
int vna;
vna = ibfind(“DEV6");
ibclr(vna);
Each of these topics will be covered in detail in order
to provide the user with the basic tools needed to
develop complete programs.
This tutorial contains programming examples written in three languages: QuickBASIC, Microsoft C,
and HP BASIC. The language used is stated for each
example.
HP BASIC example:
100 ASSIGN @gpib TO 7
110 ASSIGN @vna TO 706
120 FORMAT OFF
130 REMOTE @gpib
140 ABORT @gpib
150 CLEAR @vna
2-4.1Establishing GPIB Control
The first step in any GPIB program should be the
initialization of the GPIB inter face an d any at tached
instruments. This step insures that:
1. Communication has been established between
the computer/controller and the instrument(s),
and,
2. The instrument(s) are restored to a “known”
initial state.
The process used to initialize the 360 will differ,
depending on the computer/controller used.
Examples of initialization ro utines wr itten in Quic kBASIC and “C” for use with the National
Instruments PC2/PC2A card and HP BASIC for the
Hewlett-Packard GPIB interface are shown in Figure 2-2.
NOTE
In order for communication to take place
over the GPIB, the controlling program
must contain correct GPIB addresses for
the 360 and any other controlled instruments. Also, the data delimiting terminator used must be correct for the GPIB
interface used with the external computer/controller; refer to paragraph 2-2.3.
2-4.2Front Panel Setup
Figure 2-2. Example Initialization Routines
Front panel setup involves the configuration of the
360 for a particular measurement. In the “Setup”
subroutine, the 360 is setup to display all four S-Parameters (
is set to Log Magnitude and Phase (
Calibration, as it applies to network analysis, is a
technique used to remove most measurement errors
due to imperfections in the measurement system.
The calibration process ch arac ter izes the systematic
measurement errors. The resulting data is stored
and subtracted from subsequent measurement data
to yield the corr ect measuremen t data for th e deviceunder-test.
360 GPIB PM2-5
Page 17
II INTRODUCTIO N TO GPIB PRO GRAMM ING
TYPICAL GPIB PROGRAM STRUCTUREF OR THE 360 VNA
As performed using the 360 front pan el con tr ols, the
calibration process requires the user to define the
characteristics of the test set test ports, perform the
calibration steps, and then verify the quality of the
calibration. (Refer to Paragraph 4-9 — Measurement Calibration — in the 360 Vector Network Analyzer System Operation Manual.)
As shown in the example programs contained in
Section IV of this manual, it is possible to use the
external computer to guide the system operator
through the calibration process using a suitably
written program. The various 360 GPIB commands
that are used to perform the calibration process are
described in the first portion of Section IV. Listings
of example HP BASIC and “C” pr ogram se gments fo r
360 calibration are presented in Section IV, paragraphs 4-2.4 through 4-2.6.
2-4.4Measurement and Data Output
The commands that control the measurement functions of the 360VNA are listed and described in par agraph 3-4 — Measurement Control Commands.
These commands mimic the measurement operations that are performed using the 360 front panel
keys and menus.
An example of a main program and associated program functions written in “C” that initialize the 360
and perform c alibration, measurement an d data output functions is listed and described in Application
Note AN360-8. A similar example of a main prog ram
and associated subprograms wri tten in HP BASIC is
presented in Application Note AN360-9. These
application notes are included at the rear of this
manual behind the tab labeled “Supplements”.
2-4.5Data Transfer Programming
The commands that control the transfer of data
to/from the 360 are listed and described in paragraph 5-3 — Data Transfer Commands. The functions performed by many of these commands are
unique—most do not have direct counterparts when
operating from the front panel keys and menus.
Figures 2-4 through 2-7 contain listings of an
example program written in “C”. This example is a
complete program that automates data transfer
to/from the 360. The fou r parts of the prog ram shown
in the figures are described in paragraphs b
through e below.
a. Programming Considerations
When writing a program for data transfer
to/from the 360, the following items should be
considered:
•
Data Transfer Sequence — Data may be
transferred from the 360 to the external com-
puter in any order. However, the 360 should
be put in HOL D to prevent th e data fr om bein g
overwritten.
Data should be transferred from the external computer to the 360 in the following order:
Front Panel Setup
Measurement Frequencies
Calibration Coefficients
Measurement Data.
•
Front Panel Setup and Measurement
Frequency Data — Front panel setup data,
including frequency information, is contained
in the data transfers performed by the OFP
and IFP commands. However, when Discrete
Fill is used to enter frequency data, or when
access to individual frequency values is important, the OF V an d IF V comman ds mu st be
used.
•
Data Transfer Formats — Use of the FMA
and FMB commands is the preferred method
of data transfer for Binary floatin g point data.
ASCII data transfer is significantly slower
than for binary floating point data. Also, ASCII data must be converted to a numeric format using a suitable “C” program to be useful
for most applications.
b. Example Program: Variable Declaration
The program segment shown in Figure 2-4 contains the variable declarations for the example
program. These variable dec larations define and
2-6360 GPIB PM
Page 18
II INTRODUCTION TO GPIB PROGRAM MI NG
FOR THE 360 VNATYPICAL GPIB PROGRAM STRUCTURE
initialize the variables common to the main program and program functions.
c. Example Main Program
The main pro gram show n in Figur e 2-5 perfor ms
the following operations:
1. T he 360 and GPIB are initialized to a known
state by the first two program functions so
that the program starts under identical
conditions each time it is run:
•
GPIB function
ibfind() enables the GPIB
to control the 360 (this assumes that the
360 address is set t o 6.)
•
GPIB function
ibclr() instructs the 360 to
reset to the default state. It is used before 360 parameters are established by
the program.
2. The program function
xfr_from_360() is called
to transfer data from the 360.
3. The program function
xfr_to_360() is called to
transfer data to the 360.
4. T he last program function of the main program,
ibloc(), instructs the external com-
puter to return the 360 to local operation
and end program execution.
d. Data Transfer from the 360 VNA to the
External Computer
The program function
xfr_from_360() shown in
Figure 2-6 performs the following operations:
1. T he GPIB function
to return to local operation (
ibwrt() instructs the 360
RTL).
2. T he operator is instructed to perform a Reflection Only calibration, set up the front
panel as desired and install the device to
be measured. They are then instructed to
press any key on the external computer
keyboard to output data from the 360.
3. The next
to the 360 to trigger a sweep (
full sweep(
/*************************************************************/
/* Program to Transfer Data over the GPIB */
/* to/from a Wiltron 360 Vector Network Analyzer */
/* using an IBM AT Computer with National Instruments GPIB */
/* Written in Microsoft C */
/*************************************************************/
#include <stdio.h>
/*—————————————————————————————
Variable Declaration
Define and Initialize variables common to all functions.
——————————————————————————————-*/
int ans, vna, count, points;
char freq[12800], setup[5000];
struct header
{
char preamble [2];
int size;
}
cal_headr, data_headr;
struct cal
{
double real;
double imag;
}
cal1[512], cal2[512], cal3[512];
struct data
{ float real;
float imag;
}
data[512];
Figure 2-4. Variable Declaration for Example Data Transfer Program (Microsoft “C”)
/*—————————————————————————————
Main Program
Initialize GPIB and put 360 under GPIB control,
call program functions to transfer data,
and return 360 to local operation.
—————————————————————————————*/
main()
{
vna = ibfind(“DEV6"); /*enables GPIB to control 360*/
ibclr(vna); /*resets 360 to default parameters*/
xfr_from_360(vna); /*calls data output function*/
xfr_to_360(vna); /*calls data input function*/
ibloc(vna); /*returns 360 to_local control*/
} /*ends program*/
Figure 2-5. Main Program for Example Data Transfer Program (Microsoft “C”)
2-8360 GPIB PM
Page 20
II INTRODUCTION TO GPIB PROGRAM MI NG
FOR THE 360 VNAEXAMPLE DATA TRANSFER PROGRAM
4. T he 360 is then instructed to output the
data types listed below to the external computer. The external computer reads the
data sent from the 360 using multiple
ibrd() functions. The data types transferred
are:
•
Front panel setup data in binary string
format (
•
Measurement frequency values (
ASCII format (
OFP),
OFV) in
FMA),
/*—————————————————————————————
Data Output Function
Setup, calibrate and measure a_device,
transfer data from 360 to controller,
and return 360 to local operation.
—————————————————————————————*/
xfr_from_360(vna)
{
ibwrt(vna,"RTL",3);
printf(“\n\t\t* INSTRUCTIONS *”);
printf(“\n\t\t* Perform a Reflection Only calibration, *”);
printf(“\n\t\t* set up front panel as desired, *”);
printf(“\n\t\t* and connect device to be measured._ *\n”);
printf(“\n\t\t* PRESS ANY KEY TO OUTPUT DATA FROM 360 *\n”);
ans = getch();
ibwrt(vna,"TRS WFS HLD",11);
•
Calibration coefficients (
OC1, OC2, and
OC3) in binary floating point - double
precision (
byte first (
•
Corrected measurement data (
FMB) with the least significant
LSB),
OCD) from
the active channel in binary floating
point - single precision (
least significant byte first (
FMC) with the
LSB).
5. When the data transfer is completed, the
360 is again returned to local operation.
printf(“\n\t\tTransferring front panel setup to controller...”);
ibwrt(vna,"OFP",3);
ibrd(vna,setup,sizeof(setup));
printf(“\n\t\tTransferring frequencies to controller...”);
ibwrt(vna,"FMA OFV",7);
ibrd(vna,freq,sizeof(freq));
printf(“\n\t\tTransferring cal coefficients to controller...”);
ibwrt(vna,"FMB LSB OC1 OC2 OC3",19);
ibrd(vna,&cal_headr,4);
ibrd(vna,&cal1[0],cal_headr.size);
ibrd(vna,&cal_headr,4);
ibrd(vna,&cal2[0],cal_headr.size);
ibrd(vna,&cal_headr,4);
ibrd(vna,&cal3[0],cal_headr.size);
printf(“\n\t\tTransferring measurement data to controller...”);
ibwrt(vna,"FMC LSB OCD",11);
ibrd(vna,&data_headr,4);
ibrd(vna,&data[0],data_headr.size);
printf(“\n\n\t\t —- 360 returned to local operation.—-\n”);
ibwrt(vna,"RTL",3);
Figure 2-6. Output Data Transfer Program Function for Example Data Transfer Program (Microsoft “C”)
360 GPIB PM2-9
Page 21
II INTRODUCTIO N TO GPIB PRO GRAMM ING
EXAMPLE DATA TRANSF ER PRO GRAMFOR THE 360 VNA
e. Data Transfer from the External Computer
to the 360 VNA
The program function
xfr_to_360() shown in Fig-
ure 2-7 performs the following sequence of operations:
1. T he operator is instructed to press any key
on the external computer keyboard to output data to the 360.
2. The program function
prn_data() (shown in
Figure 2-7, sheet 2) then displays the meas-
/*———————————————————————————— Data Input Function
Reset 360 to default parameters,
transfer data from controller to 360,
and turn on calibration.
————————————————————————————-*/
xfr_to_360(vna)
{
printf(“\n\t\t* PRESS ANY KEY *”);
printf(“\n\t\t* TO DISPLAY CAL DATA AND OUTPUT DATA TO 360*\n”);
ans = getch();
ibwrt(vna,"RST",3);
urement frequency data and calibration coefficients on the external computer monitor
(Figure 2-8).
3. The 360 is then instructed to input the data
types listed below from the external computer. The external computer sends the
data to the 360 using multiple
ibwrt() func-
tions. The data types transferred are:
•
Front panel setup (
IFP) in bina ry s tring
format,
prn_data();
points=data_headr.size/8;
printf(“\n\t\tTransferring front panel setup to 360...”);
ibwrt(vna,"IFP",3);
ibwrt(vna,setup,sizeof(setup));
printf(“\n\t\tTransferring frequencies to 360...”);
ibwrt(vna,"FMA IFV",7);
ibwrt(vna,freq,points*25);
printf(“\n\t\tTransferring cal coefficients to 360...”);
ibwrt(vna,"ARF FMB LSB IC1 IC2 IC3",24);
ibwrt(vna,&cal_headr,4);
ibwrt(vna,&cal1[0],cal_headr.size);
ibwrt(vna,&cal_headr,4);
ibwrt(vna,&cal2[0],cal_headr.size);
ibwrt(vna,&cal_headr,4);
ibwrt(vna,&cal3[0],cal_headr.size);
ibwrt(vna,"CON",3);
printf(“\n\t\tTransferring measurement data to 360...”);
ibwrt(vna,"FMC LSB ICD",11);
ibwrt(vna,&data_headr,4);
ibwrt(vna,&data[0],data_headr.size);
printf(“\n\n\t\t —- 360 data transfer completed —-”);
}
Figure 2-7. Input Data Transfer Program Function for Example Data Transfer Program (1 of 2)
2-10360 GPIB PM
Page 22
II INTRODUCTION TO GPIB PROGRAM MI NG
FOR THE 360 VNAEXAMPLE DATA TRANSFER PROGRAM
3-17 MILLIMETER-WAVE TEST SET COMMANDS . . . . . . . . . . . . . 3-18
360 GPIB PM3-1/3-2
Page 24
SECTION III
COMMANDS FOR BASIC
FRONT PANEL FUNCTIONS
3-1INTRODUCTION
This section describes the GPIB Product Specific
Commands that control the basic test and measurement functions associated with the 360 VNA front
panel c ontrols an d menus. In th is section , the se m essages are refered to as “360 GPIB commands” or
simply “commands”. The command information is
grouped by control function; example: Data Entry
Commands, Hard Copy Commands, etc., (see Table
of Contents, page 3-1).
To find command information not in this section,
refer to the GPIB Command Function Index for a
listing of all 360 GPIB commands, grouped by function. Refer also to the 360 Quick Reference Guide,
which lists all commands alphabetically and
includes a brief description of the function of each
command. (See section tabs at rear of manual.)
3-2CHANNEL CONTROL COMMANDS
The commands listed in T able 3-1 set up the curr ent
display mode and active channel for the 360 VNA.
Commands D13, D14, D24 and DSP select which
channels are to be displayed. Commands CH1–CH4
select the active channel. The active channel is that
channel to which any channel-based changes are
applied.
Table 3-1. Channel Control Commands
360 GP IB
Command
Description
3-3DATA ENTRY TERMINATOR CODES
The codes listed in table 3-2 are used as terminator
statements in conjunction with commands that
require numeric values. (Almost all commands that
require numeric values also require the use of an
appropriate terminator.) The appropriate terminators for commands requiring them are listed along
with the description of the command in the tables
throughout this section and in Sections IV and V.
Table 3-2. Data Entry Terminator Codes
Terminator
Code
CMTSelect centimeter as terminator
DBLSelect dB log as terminator
DBMSelect dBm as terminator
DEGSelect degrees as terminator
GHZSelect gigahertz as terminator
IMUSelect imaginary units as terminator
KHZSelect kilohertz as terminator
MHZSelect megahertz as terminator
MMTSelect millimeter as terminator
MTRSelect meter as terminator
Description
DSPSelect single channel of active display
D13Select dual channel display, channels 1 & 3
D14Select quad display, all four channels
D24Select dual channel display, chans 2 & 4
CH1 Select channel 1 as active channel
CH2Select channel 2 as active channel
CH3Select channel 3 as active channel
CH4Select channel 4 as active channel
NSCSelect nanoseconds as terminator
PSCSelect picoseconds as terminator
REUSelect real units as terminator
USCSelect microseconds as terminator
VLTSelect volts as terminator
XM3Select unitless terminator, x 10E-3
XX1Select unitless terminator, x 1
XX3Select unitless terminator, x 10E+3
360 GPIB PM3-3
Page 25
MEASUREMENT CONT ROL COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-4MEASUREMENT CONTROL
COMMANDS
The commands listed in Table 3-3 control the parameter being measured on the active channel (S11,
S21, S22, and S12) and the basic measurement
setup. All commands except S11, S21, S22, and S12
are global; that is, they apply to the entire instrument.
The SA1, SA2, and TA2 commands can only be used
with the Models 3620, 3621 and 3622 Test Sets (i.e.,
test sets with attenuators). Note th a t the two sou rce
attenuators have ranges of 0 to 70 dB while the test
attenuator has a range of 0 to 40 dB.
Table 3-3. Measurement Control Commands (1 of 2)
360 GP IB
Command
BH0Set bias off while in holdN/AN/A
BH1Set bias on while in holdN/AN/A
CTNContinue sweeping from current pointN/AN/A
CWF (value)CW turned on and CW frequency set to
value
DescriptionValuesTerminators
The HLD command holds the sweep at the current
point; the CTN command continues sweeping from
the current poin t. T he TRS command eithe r restart s
the sweep (continuous sweep mode) or triggers a
single sweep (in hold mode). The SWP command
puts the 360 into continuous swept mode.
The WFS command causes the 360 to wait a full
sweep so that any data on the display is valid. This
is useful for scaling the display. It is requi re d wh en
outputting data from the 360, so as to e nsure that
the data being output is valid (see Section V, paragraph 5-3.1, Data Transfer Program Example and
Prog ram N ot es).
Start sweep frequency to
stop sweep frequency
GHZ, MHZ, KHZ
DA1Select a1=Ra as denominator for parameter
being defined
DA2Select a2=Rb as denominator for parameter
being defined
DB1Select b1=Ta as denominator for parameter
being defined
DB2Select b2=Tb as denominator for parameter
being defined
DE1Select unity as denomitor for parameter
being
defined
FHISet data points to maximumN/AN/A
FLOSet data points to minimumN/AN/A
FMESet data points to normalN/AN/A
HLDHold instrument at current pointN/AN/A
LA1Select a1=Ra as phase lock for parameter
being defined
LA2Select a2=Rb as phase lock for parameter
being defined
NA1Select a1=Ra as numerator for parameter
being defined
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
3-4360 GPIB PM
Page 26
III BASIC FRONT PANEL GPIB COMMANDSMEASUREMENT CONTROL COMMANDS
Table 3-3. Measurement Control Commands (2 of 2)
360 GP IB
Command
NA2Select a2=Rb as numerator for parameter
DescriptionValuesTerminators
N/AN/A
being defined
NB1Select b1=Ta as numerator for parameter
N/AN/A
being defined
NB2Select b2=Tb as numerator for parameter
N/AN/A
being defined
NU1Select unity as numerator for parameter
N/AN/A
being defined
PW2 (value)Set source 2 power level in dBmDepends on power range
DBM, XX1, XX3, XM3
of source
PWR (value)Set source 1 power level in dBmDepends on power range
DBM, XX1, XX3, XM3
of source
RH0Set RF off while in holdN/AN/A
RH1Set RF on while in holdN/AN/A
S11Measure S
S12Measure S
S21Measure S
on active channelN/AN/A
11
on active channelN/AN/A
12
on active channelN/AN/A
21
S22Measure S
on active channelN/AN/A
22
SA1 (value)Set source attenuator, port 10 dB to 70 dBDBL, DBM, XX1, XX3,
XM3
SA2 (value)Set source attenuator, port 20 dB to 70 dBDBL, DBM, XX1, XX3,
XM3
SRT (value)Set start frequencyStart sweep frequency to
GHZ, MHZ, KHZ
stop sweep frequency
STP (value)Set stop frequencyStart sweep frequency to
GHZ, MHZ, KHZ
stop sweep frequency
SWPFrequency sweep modeN/AN/A
TA1 (value)Test set port 1 test attenuator0 to 100
(Depends on test set)
TA2 (value)Set test attenuator, port 20 to 100
(Depends on test set)
DBL, DBM,
XX1, XX3, XM3
DBL, DBM,
XX1, XX3, XM3
TRSTrigger/restart sweepN/AN/A
US1-US4Measure user parameter 1-4 on active channelN/AN/A
USL (string)Enter user parameter label string5 characters maxN/A
WFSWait full sweep until all display data is validN/AN/A
360 GPIB PM3-5
Page 27
DISPLAY CONTRO L COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-5DISPLAY CONTROL COMMANDS
The commands listed in Table 3-4 set up the graph
type on the active channel. Most of these commands
are straightfor w ard with the exc eption of SME, ISE,
SMC and ISC. Both the SME and ISE commands
require values and terminators to be included with
the command (see Table 3-4). The allowable values
for these commands are 10, 20, and 30.
Example: “SME 20 DBL” This code selects a 20 dB
expanded Smith chart on the active channel.
Commands SMC and ISC also require values and
only allow the value 3.
Example: “SMC 3 DBL” This code selects a 3 dB
compressed Smith chart on the active channel. Additional considerations for commands SCL and REF
are as follows:
a. SCL Command
The SCL command sets the scaling-per-division
of the graph on the active channel. Notice that
for graph types with two types of information,
the unitless terminators alway s apply to the first
type of information. T he first type of infor m ation
is always displayed on the top graph
Example: “MPH SCL 10 XX1" This code will
select a log magnitude and phase display on the
active channel and set the magnitude scaling to
10 dB/div. The only way to scale the degrees part
of the graph is by explicit use of the DEG
terminator.
Example: “MPH SCL 45 DEG” This code se-
lects a log magnitude and phase display on the
active channel and sets the phase scaling to 45
degrees/div.
NOTE
Smith charts and inverted Smith
charts can not be scaled using the
SCL command—the different charts
are selected using the SME, ISE,
SMC, and ISC commands.
b. REF Command
The REF command selects which graticule line
will be con sidered the “refer enc e.” Notice th at for
graphs with one type of information—such as
MAG or PHA—the allowable reference line values are 0 to 8, while for graphs with two types
of information the reference line value can only
be 0 to 4. As described for the SC L comman d, for
graphs having two types of information present,
the unitless terminators apply to the first type
of information. There is no referen ce line defin ed
for Smith charts, inverted Smith charts, linear
polar, or log polar displays.
Table 3-4. Display Control Commands (1 of 2)
360 GPIB
Command
APR (value)Set group delay aperture for display on
active channel
ASCAutoscale display on active channelN/AN/A
ASP (value)Set polar stop sweep position angle0 to 360 (–360 to +360)DEG
AST (value)Set polar start sweep position angle0 to 360 (–360 to +360)DEG
DLASelect group delay display for active
channel
IMGSelect imaginary display for active
channel
ISC (value)Select inverted compressed Smith chart
for active channel
ISE (value)Select inverted expanded Smith chart
for active channel
ISMSelect normal inverted Smith chart for
active channel
Descri pt ionValuesTerm in ato rs
0 to 20XX1, XX3, XM3
N/AN/A
N/AN/A
3DBL, XX1
10, 20, 30DBL, XX1
N/AN/A
3-6360 GPIB PM
Page 28
III BASIC FRONT PANEL GPIB COMM ANDSDISPLAY CONTROL COMMANDS
Table 3-4. Display Control Commands (2 of 2)
360 GPIB
Command
LINSelect linear magnitude display for
Descri pt ionValuesTerm in ato rs
N/AN/A
active channel
LPHSelect linear magnitude and phase
N/AN/A
display for active channel
MAGSelect log magnitude display for active
N/AN/A
channel
MPHSelect log magnitude and phase display
N/AN/A
for active channel
OFF (value)Set offset for display on active channelMag offset:
–999.99 – 999.99
Depends on graph type
Phase offset: –360 to e360
Polar offset: 0
Lin polar offset: 5E
PCPSelect measurement phase polar chart
– 999.99
-9
– 1000. 0
N/AN/A
mode
PCSSelect sweep position polar chart modeN/AN/A
PHASelect phase display for active channelN/AN/A
PHO (value)Set phase offset for display on active
0 to 360 (–360 to +360)Depends on graph type
channel
PLGSelect log polar display for active
N/AN/A
channel
PLRSelect linear polar display for active
N/AN/A
channel
REF (value)Set reference line for display on active
channel
If single graph: 1– 8
If two graphs: 1 –4
Depends on graph type
RELSelect real display for active channelN/AN/A
RIMSelect real and imaginary display for
N/AN/A
active channel
SCL (value)Set resolution for display on active
channel
Mag resolution: 0.001 – 50
Phase resolution: 0.01 – 90
Polar resolution: 1E
-9
– 999.99
Depends on graph type
Lin polar resolution: 200 max
SMC (value)Select compressed Smith chart for
3DBL, XX1
active channel
SME (value)Select expanded Smith chart for active
10, 20, 30DBL, XX1
channel
SMISelect normal Smith chart for active
N/AN/A
channel
SWRSelect SWR display for active channelN/AN/A
360 GPIB PM3-7
Page 29
ENHANCEMENT COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-6ENHANCE MENT COM MAND S
include IF bandwidth, averaging, and smoothing.
Note that for the averaging function the maximum
The commands listed in Table 3-5 control the data
enhancement functions of the 360 VNA. These
Table 3-5. Enchancement Commands
360 GPIB
Command
AOFTurn off averagingN/AN/A
AVG (value)Turn on averaging and set to value1 to 4095XX1, XX3, XM3
IFMSelect minimum I.F. bandwidthN/AN/A
IFNSelect normal I.F. bandwidthN/AN/A
IFRSelect reduced I.F. bandwidthN/AN/A
SOFTurn off smoothingN/AN/A
SON (value)Turn on smoothing and set to value (%)0 to 20XX1, XX3, XM3
DescriptionValuesTerminators
averaging number is 4095. For the smoothing func-
tion, the maximum smoothing number is 20 (%).
3-8360 GPIB PM
Page 30
III BASIC FRONT PANEL GPIB COMMANDSREFERENCE DELAY COMMANDS
3-7REFERENCE DELAY COMMANDS
channel reference delay while commands DIA, DIT,
DIP, DIM, and DIE change the system dielectric
The commands listed in Table 3-6 are used to set up
both the r efer ence delay ap plied to a ch anne l an d the
relative dielectric constant of the system. Note that
constant—which is a global change. The command
RDA should only be used if at least one valid sweep
has been previously completed.
commands RDD, RDT, and RDA change the active
Table 3-6. Reference Delay Commands
360 GPIB
Command
DIASelect air as active dielectricN/AN/A
DIE (value)Set active dielectric to value1 to 999.999XX1, XX3, XM3
DIMSelect microporous teflon as active dielectric
(1.69)
DIPSelect polyethylene as active dielectric (2.26)N/AN/A
DITSelect teflon as active dielectric (2.1)N/AN/A
RDASet automatic reference delay calculationN/AN/A
RDD (value)Set reference delay in distance for active
channel
RDT (value)Set reference delay in time for active channel
DescriptionValuesTerminators
N/AN/A
–999.999 to 999.999MMT, CMT, MTR
–999.999 to 999.999 µs
PSC, NSC, USC
360 GPIB PM3-9
Page 31
TRACE MEMORY COM MANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-8TRACE MEMORY COMMANDS
The commands listed in Table 3-7 control the trace
memory function on the active chan nel and the trace
math that can be applied to it. Before using the
Store data to memory (STD).
•
Select complex division as the trace math (DIV).
•
Display the data normalized to memor y u sing th is
•
trace math (DNM).
commands MEM, DTM or DNM to view a display
that involves trac e memory, or to store trace me mory
to disk, the data from th e selected c hannel mu st firs t
be stored to memory using the STD command.
Example: “WFS STD DIV DNM”
This example code causes the 360 to:
Wait a full sweep until data is valid (WFS).
•
Table 3-7. Tra ce Me mory Comm and s
360 GPIB
Command
ADDSelect addition as trace math for active channel
DATDisplay measurement data on active channel
DIVSelect division as trace math for active channel
DNMDisplay data normalized to trace memory on active channel
DTMDisplay measurement data and trace memory on active channel
MEMDisplay trace memory on active channel
The SDK and RCK commands that are
used to store an d retr ieve the active chan nel trace memory to an d f rom th e di sk ar e
described in Section V, paragraph 5-5,
Disk Functions Commands.
Description
NOTE
MINSelect subtraction as trace math for active channel
MULSelect multiplication as trace math for active channel
STDSto re trace to m e mo ry
3-10360 GPIB PM
Page 32
III BASIC FRONT PANEL GPIB COMMANDSMARKER COMMANDS
3-9MARKER COMMANDS
The commands listed in Table 3-8 control the location and display of the markers and the functions
related to the markers. The MK1–MK6 commands
are used to set a marke r to a desired fr equenc y, time,
or distance. The terminator mnemonics used must
match the active channel domain (frequency point,
time, or distance)—Otherwise, an action-not-possible error will result.
Example: “MK1 1.0000 NSC” trying to use this
code for a frequency domain channel will generate
an action-not-possible error.
Markers can be individually turned off using the
MO1–MO6 comman ds. These comman ds remove the
specified marker and the readout from the screen
display.
All markers can be disabled using the MOF com-
mand. This command removes the marker from the
display, but the marker readout remains.
A marker is turned on w he ne ve r any of th e following
conditions occur:
When the marker is set to a value, for example:
•
“MK2 4.5632 GHZ”.
When the marker is selected for readout, for
•
example:
“MR2"
When the marker is selected as the delta refer-
•
ence marker, for example : “DR2"
The MMN and MMX commands move the active
marker to the minimum and maximum trace values
on the active channel, respectively. There must be
an active marke r selected fo r th ese comman d to ex ecute.The M1S–M6S, M1E–M6E and M1C–M6C
command are used to define a marker sweep using
the specified mark er for either the start, stop, or CW
frequenc y.
Example: “WFS MR1 MMX M1S”
This code sequence causes the 360 to:
Wait for a full sweep of data to be present (WFS).
•
Turn on marker 1 and select it for readout (MR1).
•
Move marker 1 to the maximu m value of the trace
•
on the active channel (MMX).
Set the start frequency equal to the marker
•
frequency (M1S).
Table 3-8. Marker Commands
360 GPIB
Command
DR1-DR6Select marker 1 - 6 as delta reference markerN/A
DRFTu rn delta reference mode onN/A
DROTurn delta reference mode offN/A
M1C-M6CSet marker 1-6 sweep CW frequencyN/A
M1E-M6ESet marker 1-6 sweep/zoom end freq, time or distanceN/A
M1S-M6SSet marker 1-6 sweep/zoom start freq, time or distanceN/A
MK1 (value) –
MK6 (value)
MMNSet active marker to minimum trace valueN/A
MMXSet active marker to maximum trace valueN/A
MO1-MO6Turn off marker 1-6N/A
MOFMarker display offN/A
MONMarker display onN/A
MR1-MR6Read-out frequency at marker 1-6 (through GPIB)N/A
Turn on marker 1-6 and set to valueLimited t o current sw e ep /zo om
DescriptionValues
range
360 GPIB PM3-11
Page 33
LIMITS COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-10LIMITS COMMANDS
The Limits Commands listed in Table 3-9:
Set up the upper and lower limit values for the
•
active channel.
Set the limit delta for the limit frequency readout
•
function. The range of values and allowable terminator mnemonics are dependent on the graph
type of the active channe l, mu c h like th e SCL and
REF commands described in paragraph 3-5.
For graph types that have two types of information,
the unitless terminators always apply to the first
type of information. The first type of information is
always displayed on the top graph. The second type
of limit line value is accessed by explicit use of the
appropriate data terminator mnemonic.
Examples:
1.“LUP 20 XX1" for a log magnitude and phase
display: sets the upper limit on the magnitude
display to 20 dB.
Table 3-9. Limits Commands
2. “LUP 45 DEG” must be used to set the upper
limit on the phase graph.
NOTE
The LFR, LFP, and LFD commands that
deal with limit frequency readouts, are
only available on the following graph
types: log magnitude (MAG), log magnitude and phase (MPH), phase (PHA), linear magnitude (LIN), linear magnitude
and phase (LPH), standing wave ratio
(SWR), an d group delay (DLA). The ac tive
channel must be a frequency domain
channel.
The LFP command can be used to select
phase limit frequency readouts on log
magnitude and phase and linear magnitude and phase graph types. If the LFR
command is used for eith er of these g rap h
types, the magnitude limit frequency
readout menu for the channel is
displayed.
360 GPIB
Command
LFD (value)Set limit frequency read-out delta valueDepends on graph typeDepends on graph type
LFPSelect limit frequency read-out for phase
displays
LFRSelect limit frequency read-out for active
channel
LLO (value)Turn on lower limit and set to valueDepends on graph typeDepends on graph type
LOFTurn limits display offN/AN/A
LONTurn limits display onN/AN/A
LUP (value)Turn on upper limit and set to valueDepends on graph typeDepends on graph type
DescriptionValuesTerminators
N/AN/A
N/AN/A
3-12360 GPIB PM
Page 34
III BASIC FRONT PANEL GPIB COMMANDSHARD COPY COMMANDS
3-11HARD COPY COMMANDS
The commands concerned with hard copy output are
listed in Tables 3-10 and 3-11. These commands are
straightforward with the exception of commands
PT0–PT9. The PT0–PT9 commands are used to:
(1) Specify the density of tabular data points out-
put to the printer when using the PTB and
PMT commands, and
(2) Specify the number of data points included in
the output file used with the TDD command.
The value used with the PT0–PT9 commands specifies the number of points that are skipped during
printing. Therefore, PT0 selects the densest printing
mode while PT9 gives the fewest number of data
points. The HD0 command disables headers and
page for matting f or tabular pr intou ts. Th e HD 1 co mmand enables headers and page formatting.
The hard copy outpu t comman ds cons ist of two categories: setup and action:
Setup commands are those that specify the desired size and location of the plot and the pen
numbers for each element of the plot. These
commands are described in Table 3-10.
Action commands actually initiate a plot for the
subset of the display specified by the setup commands. These commands are described in Table 3-11.
The LMS, LID, LDT, and LNM commands require a
string of characters to be sent over the GPIB along
with the command. A string input to the 360 must
have the quote characters (“ ”) surrounding the desired char ac te rs f or the s tring an d cannot exceed the
maximum number of characters specified for the
command. An example of embedding quote characters in a string sent to the 360 is shown in Figure 3-1. This example is in HP 85 BASIC:
The TDD and TTB commands enable the user to
store tabular data to the disc and recall it for output
to the printer with the tabular printout points controlled by commands PT0–PT9. These commands
are described in Section V, paragraph 5-5, Disk
Function Commands.
Table 3-10. Setup Commands for Hard Copy Output (1 of 2)
360 GPIB
Command
DPN (value)Enter pen number for data 1 to 8XX1
FFDForm feed to printer/stop print/plotN/AN/A
GPN (value)Enter pen number for graticule1 to 8XX1
HD0Turn off tabular data headers and page
formatting
HD1Turn on tabular data headers and page
formatting
HPN (value)Enter pen number for header1 to 8XX1
LDT (string)Enter label string for operator’s nameString of characters up
LID (string)Enter label string for device I.D.String of characters up
LMS (string)Enter label string for model/serial numberString of characters up
LNM (string)Enter label string for operator’s nameString of characters up
MPN (value)Enter pen number for markers and limits1 to 8XX1
DescriptionValuesTerminators
N/AN/A
N/AN/A
to 12 characters long
to 12 characters long
to 12 characters long
to 12 characters long
N/A
N/A
N/A
N/A
PBLSelect quarter-size plot, bottom left cornerN/AN/A
PBRSelect quarter-size plot, bottom right cornerN/AN/A
PFLSelect full-size plot N/AN/A
360 GPIB PM3-13
Page 35
HARD COPY COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
Table 3-10. Setup Commands for Hard Copy Output (2 of 2)
360 GPIB
Command
PT0-PT9Select tabular printout points skipped, 0-9N/AN/A
PTLSelect quarter-size plot, top left cornerN/AN/A
PTRSelect quarter-size plot, top right cornerN/AN/A
SPD (value)Enter pen speed percentage10 to 100XX1, XX3, XM3
360 GPIB
Command
PFSPrint full screen imageN/AN/A
PGRPrint graph area screen imageN/AN/A
PGTPlot graticuleN/AN/A
PLDPlot data area onlyN/AN/A
PLHPlot headerN/AN/A
PLMPlot markers and limitsN/AN/A
PLSPlot entire screenN/AN/A
PLTPlot data traces onlyN/AN/A
DescriptionValuesTerminators
Table 3-11. Action Commands for Hard Copy Output
DescriptionValuesTerminators
PMKPrint t a bular da ta f o r marke rsN/AN /A
PMNPlot menuN/AN/A
PMTPrint tabular data for traces and markersN/AN/A
PSTStop print/plotN/AN/A
PTBPrint tabular data for tracesN/AN/A
10 ! EXAMPLE ON USE OF STRINGS
20 Q$=CHR$(34) ! QUOTE SYMBOL
30 M$="4_TO_8_FILTR" ! MODEL
40 I$="456789" ! I.D.
50 D$="8/25/87" ! DATE
60 O$="GPIB_WHIZ" ! OPERATOR
70 OUTPUT 706 “LMS”Q$&M$&Q$
80 OUTPUT 706 “LID”&Q$&I$&Q$
90 OUTPUT 706 “LDT”&Q$&D$&Q$
100 OUTPUT 706 “LNM”&Q$&O$&Q$
110 END
Figure 3-1. An Example of Hard Copy Code Using Embedded Quotes
3-14360 GPIB PM
Page 36
III BASIC FRONT PANEL GPIB COMMANDSSYSTEM STATE COMMANDS
3-12SYSTEM STATE COMMANDS
Table 3-12 lists the system state commands. These
commands are used to specify CRT display parameters, information display format, and other parame-
Table 3-12. System State Commands (1 of 2)
360 GPIB
Command
ACFAccept 360 system configurationN/A
BC0Set CRT blanking on (screen blanked)Allows for the ultimate in security — a totally blank
BC1Set CRT blanking off (screen active)Screen blanking is turned off .
BLUSelect blue as third color Allows selection of the third color used by the 360 for
CYNSelect cyan as third colorAllows selection of the third color used by the 360 for
DC1Display channel 1 and 2 operating
parameters
DC3Display channel 3 and 4 operating
parameters
DefinitionNotes
ters that control the operation of the system. The
function of approximately half of these commands is
to display test set connector type information on the
system screen.
screen. In this mode, the 360 is fully operational over
the GPIB but nothing appears on display.
markers, limits, and some menu annotation
markers, limits, and some menu annotation.
Displays channels 1 and 2 operating parameters in the
data area of the screen.
Displays channels 1 and 2 operating parameters in the
data area of the screen.
DCPDisplay calibration parameters Displays calibration parameters in the data area of the
screen.
DF2Display 2.4 mm female connector
information
DF3Display GPC-3.5 female connector infor-
mation
DFKDisplay K female connector information N/A
DFNDisplay TYPE N female connector
information
DFPDisplay front panel instrument state Displays global operating parameters in the dat a area of
the screen.
DFSDisplay SMA female connector information N/A
DFTDisplay TNC female connector information N/A
DFVDisplay V female connector information N/A
DG7Display GPC-7 male connector informationN/A
DGSDisplay GPIB status informationDIsplays the GPIB system parameters in the data area
of the screen.
DM2Display 2.4 mm male connector information N/A
DM3Display GPC-3.5 male connector
information.
N/A
N/A
N/A
N/A
DMKDisplay K male connector information N/A
DMNDisplay TYPE N male connector information
DMSDisplay SMA male connector information N/A
N/A
360 GPIB PM3-15
Page 37
SYSTEM STATE COM MANDSIII BASIC FRONT PANEL GPIB COMM ANDS
Table 3-12. System State Commands (2 of 2)
360 GPIB
Command
DMTDisplay TNC male connector information N/A
DMVDisplay V male connector information N/A
DWGDisplay waveguide parameters N/A
FOFFrequency information blanked Instructs the 360 to blank any frequency information
FONFrequency information displayed Frequency blanking can be turned off using this code.
INTInitialize (format) data-only disk in drive See Paragraph 5-5
RSTReset instrument to default parameters Similiar to pressing the “DEFAULT PROGRAM” key
RTLReturn to local (front panel) control Performs the same function as the control panel
TSTPerform self testPerforms the same self-test function as the SELF TEST
DefinitionNotes
from the screen and any hard copy output. This code is
useful
for security reasons.
RETURN TO LOCAL key. This code has no effect if the
360 is in local lockout.
menu selection from the TESTS menu. Returns a string
of 20 zeros if self test passes. Returns up to 20 error
numbers if fail. For a listing of error messages that
correspond to the error numbers, refer to the ERROR
AND STATUS MESSAGES information contained in
Section IV of the 360 Vector Network Analyzer
Operation Manual.
3-16360 GPIB PM
Page 38
TEST SET MULTIPLEXER
INTERNAL
SIGNAL
360 NETWORK ANALYZER
EXTERNAL
VGA MONITOR
EXTERNAL
COMPUTER
INTERNAL
SCREEN
DISPLAY
CIRCUITS
EXTERNAL
SIGNAL
III BASIC FRONT PANEL GPIB COMMANDSAND VIDEO SWITCH COMM ANDS
3-13TEST SET MULTIPLEXER CONTROL
COMMANDS
Table 3-13 list the test set multiplexer commands.
These commands control the 360 Test Set Multiplexer during remote (GPIB) system operation.
Command ACF—Accept 360 System Configuration—is normally used in conjunction with these
commands (refer to paragraph 3-12—System State
Commands). Commands SFA and SFB are used to
control an external A/B RF switch (if used).
NOTE
The 360 Test Set Multiplexer is an option
to the 360 VNA. The external A/B RF
switch is customer supplied.
Table 3-13. Test Set Multiplexer Control Commands
360 GPIB
Command
MP0Set non-selected test set stand by power off
MP1Set non-selected tes t set standby power on
RFASet RF switch to A position
Definition
3-14VIDEO SWITCH CONTROL
COMMANDS
Table 3-14 list the video output control commands
that control the internal 360 video switching paths.
These switching paths are shown in Figure 3-2.
The video output control commands perform the
same functions as the U7 menu selections. (The U7
menu is invoked from the VIDEO CONFIGURATION selection of the U1 Utility Menu; refer to the
360 Vector Network Analyzer Operation Manual.)
Table 3-14. Video Output Redirection Control Codes
360 GPIB
Command
VEEVideo – External signa l to external m onit or
VEIVideo – External signal to internal screen
VIEVideo – Internal signal to external monitor
VIIVideo – Internal signal to internal screen
Definition
RFBSet RF switch to B position
SRASet signal source to A
SRBSet signal source to B
TSASet test se t to A
TSBSet test set to B
Figure 3-2. 360 VNA Video Signal Paths
360 GPIB PM3-17
Page 39
PULSE SYSTEM , NOISE FIG URE AN D
MILLIMETER-WAVE TEST SET COMMANDSIII BASIC FRONT PANEL GPIB COMMANDS
3-15PULSE SYSTEM COMMAND
The PMC mnemonic is the only command used with
the 360PS20A Pulsed VNA system. This command
provides control of the 3636A Pulsed/CW Test Set
pulse modulators by writing a control byte image to
the modulator c ontro l re gister of the test set (via the
360 VNA). Refer to the 360PS20A Pulsed/CW Vector
Network Analyzer Operation Manual for further information about operation of the 360PS20A Pulsed
VNA system and system components.
The bit assignment of the register byte image is
shown in Figure 3-3; n ote that only the up per nibble
(i.e, four most significant bits) are used. If bit = 1,
the corresponding modulator will be turned on full
to override the profile pulse. If bit = 0, the profile
pulse will control the modulator. The example code
shown below is a prog ram fu nction to tur n o n all four
modulators. Note that byte is shown in hexadecimal
format (example is written in “C”.)
The commands listed in Table 3-15 are used to
control the function s of the 3642A Noise Figu re Module and to read the status byte from that module.
The 3642A Noise Figure Module is part of the
360NF20A Noise Figure Vector Network Analyzer
System. Refer to the 360NF20A Noise Figure/Vector
Network Analyzer Operation Manual for information about the bit structure and bit functions of the
control registers affected by these commands.
Table 3-15. Noise Figure System Commands
360 GPIB
Command
MC1 (value)Write control byte to
MC2 (value)Write control byte to
RSB (value)Read Status Register (ID
Descri pt ionValues
3642A Noise Figure
Module Primary Control
Register
3642A Noise Figure
Module Secondary
Control Register
byte)
Binary,
8 bit
Binary,
8 bit
Binary,
8 bit
3-17MILLIMETER-WAVE TEST SET
COMMANDS
The commands listed in Table 3-16 control the functions of the 3635A Millimeter Wave Test Set when
operated in the GPIB mode.
Table 3-16. Millimeter-Wave Test Set Commands
Upper NibbleLower Nibble
Figure 3-3. Pulse System Control Byte Bit Structure
360 GPIB
Command
LDMLoad new modules (must be specified for
the band and head changes that are to take
place). The mnemonic “LDM” must be
specified after band.
P2ASelect model number 3640 “A” for port 2
P2BSelect model number 3641 “B” for port 2
Q22Select Q band (33-50 GHz) with WR-22
U19Select U band (40-60 GHz) with WR-19
V15Select V band (50-75 GHz) with WR-15
W10Select W band (75-110 GHz) with WR-10
An Example “C” Program Function . . . . . . . . . . . . . . . . . . . . . 4-7
360 GPIB PM4-1/4-2
Page 41
SECTION IV
COMMANDS FOR
CALIBRATION F UNCTIONS
4-1INTRODUCTION
This section describes the GPIB Product Specific
Commands used to perform system calibration fu nctions. In this section, these messages are referred to
as “360 GPIB commands” or simply “commands”.
These commands perform the following functions.
Specify the calibration method desired.
•
Specify the type of calibration desired.
•
Specify the calibration standards to be used.
•
Specify the transmission line type and associated
•
characteristics.
Control the calibration data-taking process.
•
4-2DESCRIPTION OF CALIBRATION
COMMANDS
Table 4-2 located at the rear of this section lists all
GPIB commands that are used to perform the 360
VNA calibration func tion under remote c on trol. This
table provides a brief description of the function for
each command and lists permissible values and terminators, if required. Programming examples showing typical usage of these commands are provided in
paragraphs following the table.
NOTE
The 360 VNA calibration function
requires operator intervention. However,
it is possible to use the external c ontrolle r
to guide the operator thr ough the calibration process using a suitable program
containing the calibration commands described in this section.
a. Specify Normal 501 Point Calibration
(NOC)
This command sets up a normal frequency r ange
calibration.
b. Enter Start Frequency for Normal
Calibration (SRT)
This command sets the lower limit of the range
of frequencies used for the calibration process.
c. Enter Stop Frequency for Normal
Calibration (STP)
This command sets the upper limit of the range
of frequencies used for the calibration process.
d. Specify Discrete Frequency Calibration
(DFC)
This command sets up a calibration at discrete
frequencies only.
1. Only the points entered using the DFQ, IFV,
FRS, FRI, FRP, or FIL commands are used in
calibration (2 ≤ number of points ≤ 501) .
2. The IFV command allows for a frequency list
input of calibration frequencies. Refer to
paragraph 5-3, Data Transfer Commands, for
more details.
3. The DFQ, FRS, F RI, F R P, FIL, and DFO c ommands can also be used to specify frequencies
outside of calibration.In this application, any
calibration data is lost.
e. Specify CW Calibration (CWC)
This command sets up a continuous wave (CW)
calibration.
4-2.1Major Calibration Commands
The following paragraphs provide detailed descriptions of the major GPIB commands used for calibration. They also provide programming information
and techniques for the use of these commands.
360 GPIB PM4-3
f.Set up to Specify Port One Calibration
Standards (P1C)
This command specifies port one as the port to
which subsequent connector-related commands
will apply.
Page 42
DESCRIPTION OF CALIBRATION COMMANDSIV CALIBRATION COMMANDS
g. Set up to Specify Port Two Standards
(P2C)
This command specifies port two as the port to
which subsequent connector-related commands
will apply.
Example:
“P1C CFK P2C CMK”
This sequence of commands sets up a female K
connector for port 1 (
connector for port 2 (
P1C CFK) and a male K
P2C CMK).
h. Other Connector Specification (CND)
This command allows a non-standard connector
to be specified. This is the same as selecting
OTHER from the control panel menu. When
specifying the CND command, the connector offset for the open and/or short device and the capacitance coefficients for the open device are entered to characterize the connector.
i.Specify Sliding Load for Calibration (SLD)
This command specifies a sliding load. If specifying the SLD command, the data-taking proces s
for the load includes six slide positions. If any
frequencies are below 2 GHz, you must use a
broadband load.
4-2.2Required Calibration Command
Sequence
A program to control the calibration process must
use a specific order for the GPIB calibration commands. Table 4-1 lists t his acceptable order.
4-2.3Other Calibration Related Commands
The following commands are used for special types
of calibrations and to simulate a calibration process.
a. A12, A8T, ARF, AFR, AFT, and ARL
These commands simulate the completion of a
calibration. When used in this manner, commands associated with calibration coefficients
(IC1–IC9, ICA–ICC, OC1–OC9, OCA–OCC) are
matched with the corr esponding err or terms. For
additional information, refer to Section V, paragraph 5-3, Data Transfer Commands.
IV CALIBRATION COMMANDSDESCRIPTION OF CALIBRATION COMMANDS
NOTE
The A8T, A12, ARF, AFR, AFT, and
ARL commands match up with corresponding calibration type commands.
These commands can be used for advanced applications that input calibration coefficients into the 360 (refer
to Section V, paragraph 5-3).
b. CON and COF
These commands are not used during calibration. They are used during normal measurements to apply the current calibration (CON) or
to turn off any applied calibration (COF).
c. LM2 and LM3
These commands are used to select a match for
the second or the third device respectively during a LRM type calibration. Example:
ibwrt(pna, “LM2", 3);/∗ match as second
device ∗/
d. U10, U15, and U25
These commands are used to select 10, 15, or 25
mil UTF calibration kits respectively. These cal ibration kits are used to perform a 360 calibration for microstrip device measurements. Example:
ibwrt(pna, “U10", 3);/∗ select 10 mil
calibration ∗/
4-2.4A Simple Exam ple Cali brat ion
Program
The following is an example program to set up a
typical calibration sequence for the 360 VNA:
This example code sets up a calibration u sing standard calibration mode (
and 12-term calibration type (
SCM), coax cable media (LTC),
C12). A discrete set of
points is defined for frequency operation starting at
1 GHz (
100MHZ
This range is confirmed or “filled” (
pleted (
FRS 1.0 GHZ), spaced 100 MHz apart (FRI
), at 41 consecutive points (FRP 41 XX1).
FIL), then com-
DFD).
The Port 1 test port connector is defined as a female
type K connector (
connector is defined as a male K type con ne ctor (
). Broadband loads are selected as the default
CMK
P1C CFK) and the Port 2 test port
P2C
load type (
BBL). The BEG command instructs the
360 to begin the calibration-data-taking-process.
The calibration control prog ram should contain com-
mands to control the data-collection portion of the
calibration process. Typical commands used for this
proces s are :
Take Calibration Data for Current Standard
•
(TCD)
Go on to the Next Calibration Step (NCS)
•
Averaging On and Set to Value (AVG)
•
Averaging Off (AOF)
•
Set IF Bandwith to Normal (IFN)
•
Set IF Bandwith to Reduced (IFR)
•
Set IF Bandwith to Minimum (IFM)
•
Any Graph Type Specification or Scaling Change
•
Active Channel Specification (CH1–CH4)
•
The TCD and NCS commands control the data-taking process. Commands AVG, AOF, IFN, IFR, and
IFM control the data-enhanc ement func tion used for
a particu lar measuremen t (r efer to Section III, paragraph 3-6, Enhancement Commands).
Before the TCD and NCS commands are invoked in
the program, the system operator mus t be instr ucted
to perform the exact steps necessary to setup the
calibration sequence for the type of 360 calibration
to be used. An example program segme nt to continue
the 12-term calibration started in the previous
example is shown in Figure 4-1. This example program segment is in written in HP-BASIC.
The calibration control program should determine if
the 360 is ready for the next step of the calibration
sequence before prompting the system operator to
connect new calibration standards to the test ports.
This can be don e by mon itor in g the status of the 360
or by requesting “dummy” data output from the 360
after executing the NCS command.
For example, the command in the example below
instructs the 360 to take calibration data (TCD), go
to the next calibration step (NCS), and output the
number of points it is measuring (ONP). When the
controller is able to read the points string from the
360, the calibration step is complete.
260 OUTPUT 706;"TCD NCS ONP"
270 ENTER 706; N$ ! READ #POINTS WHEN
STEP IS COMPLETE
280 DISP “CALIBRATION STEP COMPLETE”
A listing of an example calibration subprogram is
shown in Figure 4-1. This program guides the 360
system operator through a 12 term calibration
sequence. Th e calibration is perfo rmed at 41 discr ete
frequencies with 100 MHz spacing from 1 to 5 GHz
(see explanation o f lin e 330 in pr ec edin g par ag r aph ).
DFD P1C CFK P2C CMK BBL BEG ONP”
340ENTER @vna;N$
350DISP “CONNECT BROADBAND LOADS TO PORT 1 AND PORT 2"
360GOSUB Continue
370DISP “CONNECT OPEN TO PORT 1 AND SHORT TO PORT 2"
380GOSUB Continue
390DISP “CONNECT SHORT TO PORT 1 AND OPEN TO PORT 2"
400GOSUB Continue
410DISP “CONNECT PORT 1 TO PORT 2"
420GOSUB Continue
430DISP “l2 TERM CALIBRATION COMPLETE”
440SUBEXIT
450 Continue: BEEP
460LOOP
470ON KEY 5 LABEL “TAKE CAL DATA” GOTO 490
480END LOOP
490DISP “TAKING CALIBRATION DATA...”
500OUTPUT @vna;"TCD NCS ONP"
510ENTER @vna;N$
520RETURN
530SUBEND
540!
In this example, the same technique is used as described in paragraph 4-2.4 to determine if the 360 is
ready for the next calibration step.
An example of a main program that calls this and
other subprograms is described in application note,
AN360-9, which is includ ed be hind the Supp lemen t s
tab in this manual.
Figure 4-1. Example Program Segment to Control Calibration Data Collection (HP BASIC)
4-6360 GPIB PM
Page 45
EXAMPLE CALIBRATION PROGRAMMINGIV CALIBRATION COMMANDS
4-2.6An Example “C” Program Function
An example “C” program function, “cal_12_term()”,
is shown in Figure 4-2. This program function performs the same calibration sequence described in
paragraphs 4-2.4 and 4-2.5. In this example, the
program function “cal_data()” instructs the 360 to
/*————————————————————————————-
Calibration Function
Setup for a 12-Term Calibration and prompt the operator
to install cal devices as required.
————————————————————————————-*/
cal_12_term(vna)
int vna;
{
static char
a[]="LTC SCM C12 DFC FRS 1 GHZ FRI 100 MHZ FRP 41 XX1",
b[]="FIL DFD P1C CFK P2C CMK BBL BEG ONP",
point_str[40];
printf(“\n\t\t\t\tCALIBRATION\n”);
ibwrt(vna,a,sizeof(a));
ibwrt(vna,b,sizeof(b));
ibrd(vna,point_str,40);
printf(“\nConnect BROADBAND LOADS to Port 1 and Port 2:\n”);
cal_data(vna);
printf(“\nConnect OPEN to Port 1 and SHORT to Port 2:\n”);
cal_data(vna);
printf(“\nConnect SHORT to Port 1 and OPEN to Port 2:\n”);
cal_data(vna);
printf(“\nConnect Port 1 to Port 2:\n”);
cal_data(vna);
printf(“\n\t\t 12-Term Calibration Complete\n”);
}
take calibration data (TCD) and advan ce to the next
step (NCS) after determining if the 360 is ready.
An example of a main program that calls this and
other subprograms is described in the application
note, AN360-8, w h ich is in c luded behind the Supplements tab in this manual.
cal_data(vna) /* function to take cal data */
int vna;
{
static char
key,
c[]="TCD NCS ONP",
point_str[40];
printf(“\tPress ENTER key to Take Cal Data\n”);
while((key = getch())!=’\r’);
printf(“Taking Calibration Data...\n”);
ibwrt(vna,c,sizeof(c));
ibrd(vna,point_str,40);
}
Figure 4-2. Example “C” Program Function to Perform a 12 Term Calibration
360 GPIB PM4-7
Page 46
DESCRIPTION OF CALIBRATION COMMANDSIV CALIBRATION COMMANDS
Table 4-2. Calibration Commands (1 of 4)
360 GPIB
Command
A8TSimulate 8-term (1-path) calibrationN/AN/A
A12Simulate 12-term calibrationN/AN/A
AFRSimulate frequency response calibrationN/AN/A
AFTSimulate transmission-only frequency
response calibration
ARFSimulate reflection only calibrationN/AN/A
ARLSimulate reflection-only frequency response
calibration
BBLSelect broadband load for calibrationN/AN/A
BEGBegin calibration data-collection stepsN/AN/A
BPF (value)Break point frequency for 3 line LRL onlyStart sweep frequency to
port
CF3Select female GPC-3.5 connect or for curre nt
port
CFCSelect female TNC connector for current portN/AN/A
CFKSelect female K connector for current portN/AN/A
CFNSelect female Type N connector for current
port
CFRSelect transmission and reflection frequency
response calibration
CFSSelect female SMA connector for current
port
CFTSelect transmission-only frequency
response calibration
CFVSelect female V connector for current portN/AN/A
CM2Select male 2.4 mm connector for current
port
CM3Select male GPC-3.5 connector for current
port
CMCSelect male TNC connector for current portN/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
CMKSelect male K connector for current portN/AN/A
4-8360 GPIB PM
Page 47
IV CALIBRATION COMMANDSDESCRIPTION OF CALIBRATION COMMANDS
Table 4-2. Calibration Commands (2 of 4)
360 GPIB
Command
CMNSelect male Type N connector for current
port
CMSSelect male SMA connector for current portN/AN/A
CMVSelect male V connector for current portN/AN/A
CNDSelect user-specified connector for current
port
CNGSelect GPC-7 connector for current portN/AN/A
COFTurn off vector error correctionN/AN/A
CONTurn on vector error correctionN/AN/A
COO (value)Enter offset for open for user-specified
connector
COS (value)Enter offset for short for user-specified
connector
CRFSelect reflection only calibrationN/AN/A
CRLSelect reflection-only frequency response
calibration
CWCSelect CW frequency calibration data pointsN/AN/A
DescriptionValuesTerminators
N/AN/A
N/AN/A
–999.9999 to +999.9999MMT, CMT, MTR
–999.999 m to 999.999 mMMT, CMT, MTR
N/AN/A
DFCSelect discrete frequency calibration data
DFDDone specifying discrete frequency rangesN/AN/A
DFQ (value)Enter single discrete frequencyStart sweep frequency to
FILFill defined discrete frequency rangeN/AN/A
FRCClear all defined discrete frequency rangesN/AN/A
FRI (value)Set discrete frequency fill range increment
FRP (value)Set discrete frequency fill range number of
FRS (value)Set discr ete f requency fill range start
ISFExclude isolation N/AN/A
ISNInclude isolation N/AN/A
KECKeep existing calibration dataN/AN/A
LCMSelect LRL calibration methodN/AN/A
LL1 (value)Enter length of line 1 for LRL calibration0 to +999.9999MMT, CMT, MTR
points
frequency
points
frequency
stop sweep frequency
Start sweep frequency to
stop sweep frequency
1 to (501 — current
number of points)
Start sweep frequency to
stop sweep frequency
N/AN/A
GHZ, MHZ, KHZ
GHZ, MHZ, KHZ
XX1, XX3, XM3
GHZ, MHZ, KHZ
LL2 (value)Enter length of line 2 for LRL calibration0 to +999.9999MMT, CMT, MTR
360 GPIB PM4-9
Page 48
DESCRIPTION OF CALIBRATION COMMANDSIV CALIBRATION COMMANDS
Table 4-2. Calibration Commands (3 of 4)
360 GPIB
Command
LL3 (value)Enter length of line 3 for 3 line LRL
calibration
LLZ (value)Enter line impedance for LRL calibration0.001 to 1x10E+3XX1, XX3, XM3
LM2Select a match for the second device during
a LRM type calibration
LM3Select a match for the third device during a
LRM type calibration
LR2Specify 2 line LRLN/AN/A
LR3Specify 3 line LRLN/AN/A
LTCSelect coaxial transmission line for
calibration
LTUSelect microstrip transmission line for
calibration
LTWSelect waveguide transmission line for
calibration
NCSGo on to next calibration stepN/AN/A
NOCSelect normal calibration data points
This code
DescriptionValuesTerminators
0 to +999.9999MMT, CMT, MTR
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
N/AN/A
OCMSelect o ffset short calibration methodN/AN/A
P1CSelect port 1 for connector specificationN/AN/A
P2CSelect port 2 for connector specificationN/AN/A
RGZSelect reflective device greater than Z0
RLZSelect reflective device less than Z0 (LRL)N/AN/A
RM1Select reference plane at line 1 midpoint
ROL (value)Enter reflective device offset length for LRL
RPCRepeat previous calibrationN/AN/A
RRPSelect reference plane at reflection plane
SBD (value)Enter substrate dielectric for microstrip
SBT (value)Enter substrate thickness for microstrip
SCMSelect standard calibration methodN/AN/A
(LRL)
(LRL)
–999.999 to +999.999MMT, CMT, MTR
calibration
(LRL)
calibration
0.001 mm to 1 .0 m MMT, CMT, M TR
calibration
N/AN/A
N/AN/A
N/AN/A
1.0 to 9999.99XX1, XX3, XM3
4-10360 GPIB PM
Page 49
IV CALIBRATION COMMANDSDESCRIPTION OF CALIBRATION COMMANDS
Table 4-2. Calibration Commands (4 of 4)
360 GPIB
Command
SH1 (value)Set offset short 1 offset length–999.999 to +999.999MMT, CMT, MTR
SH2 (value)Set offset short 2 offset length–999.999 to +999.999MMT, CMT, MTR
SLDSelect sliding load for calibrationN/AN/A
TCDTake calibration data for current standardN/AN/A
TDCSelect time domain harmonic frequency
calibration data points
TDL (value)Through DC coefficient for loss–999.999 to +999.999XX1
TFE (value)Through frequency exponent for loss–9.999 to +9.999XX1
TFL (value)Through frequency coefficient for loss–999.999 to +999.999XX1
TOL (value)Through offset length–999.9999 to +999.9999MMT, CMT, MTR
U10Select 10 mil UTF calibration kit for
calibration for microstrip device
measurements
U15Select 15 mil UTF calibration kit for
calibration for microstrip device
measurements
U25Select 25 mil UTF calibration kit for
calibration for microstrip device
measurements
DescriptionValuesTerminators
N/AN/A
N/AN/A
N/AN/A
N/AN/A
USE (value)Enter effective dielectric for microstrip
calibration
USW (value)Enter microstrip width for microstrip
calibration
USZ (value)Enter microstrip impedance for microstrip
calibration
WCO (value)Set waveguide cutoff frequency for user-
defined kit
WKDSelect user-defined wa veguide c alibration kitN/ AN/A
WKISelect installed waveguide calibration kitN/AN/A
This section describes the GPIB Product Specific
Commands that produce operations that are unique
to the GPIB mode of operation. Example commands
included in this group are: Data Tr ansfer commands,
Group Execute commands, etc. (see Table of
Contents, page 5-1). In this section, these messages
are referred to as “360 GPIB commands” or simply
“commands”.
Table 5-1. Save/Recall Commands
360 GPIB
Command
SV1-SV4Save front panel setup to internal memory
location 1-4
DescriptionValuesTerminators
5-2 SAVE/RECALL COMMANDS
The Save/Recall commands listed in Table 5-1 allow
the system user to save and recall:
• (1) front panel setup data to and from internal
memory, and
(2) calibration and front panel setup data to/from
•
the disk. The syntax for entering a file name
string to the 360 is the same as the syntax for the
strings in the LMS, LID, LDT and LNM commands described in Section III, paragraph 3-11.
The double quote characters must enclose the string
sent to the 360. The 360 accepts only MS-DOS
compatible file name characters. Refer to paragraph
5-5, Disk Fun ction Comman ds, for more inf or ma tion
about file naming conventions.
N/AN/A
RC1-RC4Recall front panel setup data from internal
memory location 1-4
360 GPIB PM5-3
N/AN/A
Page 52
DATA TRANSFER COMMANDSV ADVANCED GPIB PROGRAMMING
5-3DATA TRANSFER COMMANDS
T able 5-2 desc ribes the data tran sfer c ommands. The
360 transfers data to/from an external computer via
the GPIB in two basic formats: binary and ASCII.
All ASCII data values either output by the 360 or
expect ed as i nput must have the following form:
Where:
S
x x x . y y y y y y y y y y y y y y y E s z z
S = sign, either blank or “–”
x = digits to the left of the decimal (3)
y = digits to the right of the decimal (15)
E = exponential notation indicator
s = exponent sign, either ’+’ or ’–’
z = digits for exponent (2)
.
= decimal point
Separate all ASCII transfers that involve data pairs
(such as real and imaginary elements) by commas.
For transfers involving more than one item of information, separate each item by a line feed.
For example, the 360 response to the commands
“FMA OCD” would be:
(Repeated Number of Points)
Real ASCII>, <Imaginary ASCII
<
EOI on Last Byte
<LF>
>
Binary data transfers involving numerical values
use 32-bit or 64-bit floating point numbers in
IEEE-754 format. The format of string data, such as
that used for front panel setup data, is not user
controllable. Binary da ta is alway s sen t in the standard block format shown in Figures 5-1 and 5-2.
The data-format commands (FMA, FMB and FMC)
and the byte-ordering commands (LSB and MSB)
control the format of the data that is input or outpu t
by the 360 VNA under control of many of the data
transfer commands (Table 5-2). However, the commands that transfer binary data strings and ASCII
data are not affected by the data format and byteordering commands. (These commands always input/output binary data strings and ASCII data regardless of the curren tly selec ted data format.) Refe r
to Table 5-2 and Figure 5-2 for details.
BYTE COUNT = 8 bytes x 501 data points = 4008 bytes
(“Byte Count” bytes will contain the value 4008.)
Figure 5-2. Example of Binary Data Transfer
Table 5-2. Data Transfer Commands (1 of 2)
360 GPIB
Command
CCDCollect corrected data for parameter of active channel5-3 m.N/A
CFDCollect final (display format) data for parameter of active channel5-3 m.N/A
Brief Description
Descript.
(Para.)
Data Formats
CRDCollect raw data for parameter of active channel5-3 m.N/A
FMASelect ASCII data transfer format5-3 e.N/A
FMBSelect IEEE-754 64-bit data transfer format5-3 e.N/A
FMCSelect IEEE-754 32-bit data transfer format5-3 e.N/A
IC1 (value) –
IC9 (value)
ICA (value),
ICB (value),
ICC (value)
ICD (value)Input corrected data for parameter of active channel5-3 l.FMA, FMB, FMC
ICF (Binary string)Input information for front panel setup
ICL (Binary string)Input all 12 calibration coefficients in binary string format5-3 g.Binary string
IFD (value)Input final (display format) data for parameter of active channel5-3 l.FMA, FMB, FMC
IFP (Binary string)Input information for current front panel setup in binary string
Input calibration coefficient A, B, C5-3 g.FMA, FMB, FMC
and
string format
calibration in binary
format
Input information for front panel setups in binary string format5-3 i.Binary string
5-3 n.Binary string
5-3 i.Binary s tring
360 GPIB PM5-5
Page 54
V GPIB OPERATION — ADVANCED PROG RAMM INGDATA TRANSFER COM MAND CO DES
Table 5-2. Data Transfer Commands (2 of 2)
360 GPIB
Command
LSBSelect least significant byte first binary transfers5-3 f.N/A
MSBSelect most significant byte first binary transfers5-3 f.N/A
OAP (value)Output active parameter value5-3 b.ASCII
OC1 (value) –
OC9 (value)
OCA (value),
OCB (value),
OCC (value)
OCD (value)Output corrected data for parameter of active channel5-3 l.FMA, FMB, FMC
OCF (Binary string)Output information for front panel setup
OCL (Binary string)Output all 12 calibration coefficients in string form5-3 g.Binary string
OCSOutput collected data5-3 m.N/A
ODR (Binary string)Output disk directory5-3 k.Binary string
OFD (value)Output final (disp. format) data for parameter of active channel5-3 l.FMA, FMB, FMC
OFP (Binary string)Output information for current front panel setup in binary string
Output calibration coefficient A, B, C5-3 g.FMA, FMB, FMC
string format
format
Brief Description
and
calibration in binary
Descript.
(Para.)
5-3 o.Binary string
5-3 j.Binary s tring
Data Formats
OFV (value)Output frequency values5-3 h.FMA, FMB, FMC
OID (value)Output instrument identification string5-3 d.40 byte ASCII strg
OKP (value)Output number of front panel key pressed5-3 c.ASCII
OM1 (value) –
OM6 (value)
ONP (value)Output number of points currently being measured5-3 p.ASCII
ORD (value)Output raw data for parameter of active channel5-3 l.FMA, FMB, FMC
OS1 (Binary string ) –
OS4 (Binary string)
The most important points to consider about data
transfer are (1) the data format to use and (2) the
byte ordering desired. When using the FMA data
format, the byte ordering selected by the LSB or
Output marker 1-6 value (display format)5-3 a.ASCII
Ouput information for front panel setups (1–4) in binary string
format
5-3 j.Binary s tring
active byte ordering. Conversely, even if you select
FMB or FMC data format, some transfers will always occur in ASCII and are unaffected by the LSB
or MSB commands.
MSB commands is irrelevant.
NOTE
ASCII data is not dependent on the active byte order .
However, even if the 360 is using FMA format, some
transfers ( suc h a s the O S1–O S4 commands) still use
the binary transfer format, which is affected by the
The byte ordering mode (LSB or MSB)
also affects the orde r of the tw o by tes th at
comprise the byte count portion of the
standard preamble (Figure 5-1.)
5-6360 GPIB PM
Page 55
V ADVANCED GPIB PROGRAMMINGDATA TRANSFER COMMANDS
Table 5-3. Output Values Vs Various Graph Types
Display TypeOutput Values
Log magnitudedB, degrees
PhasedB, degrees
Log mag & phasedB, degrees
Linear magnitudeLin Mag (Rho or Tau), degrees
Linear mag & phaseLin Mag (Rho or Tau), degrees
Smith chartOhms, Ohms (r + jx)
Inverted SmithSiemens, Siemens (g + jb)
Group delaySeconds, degrees
Log polardB, degrees
Linear polar Lin Mag (Rho or Tau), degrees
RealReal, imag
ImaginaryReal, imag
Real & ImaginaryReal, imag
SWRSWR, D egree s
5-3.1Descriptions of Data Transfer
Commands
A detailed description of each of the data transfer
commands follows:
a. OM1 - OM 6
These commands output the value of the trace
on the active chan n el at mark er 1–6. Th e outpu t
is always a pair of ASCII values and is dependent upon the graph type used for the active chan nel (See Table 5-3).
b. OAP
This command outputs the value of the active
parameter as a single ASCII valu e. If the re is no
active parameter, a zero value is output.
c. OKP
This command outputs a single ASCII value
representing the number of the key pressed on
the front panel of the 360 VNA.
d. OID
This command outputs a 40-byte ASCII string
defining the current 360 VNA system configuration. The format of the OID string is shown in
Table 5-4.
Table 5-4. OID Response String
Number of Bytes
4 99 666
xxxx
Model
No.
xx.xxxxxx
Low
Freq.
GHZ
xx.xxxxxx
High
Freq.
GHZ
Sxx.x
Low
Pwr
dBM
Sxx.x
High
Pwr
dBM
xxx.xx
S.W.
Rev.
e. FMA, FMB, F MC
These commands set up the current active data
transfer format.When the current transfer format is unknown, it is a good practice to precede
any data transfer commands which depend on
these formats with the desired format c ommand.
f.LSB, MSB
These two commands control the ordering of
bytes for floating point data transfer s. Th ey also
control the ordering of the two bytes that
comprise the byte count in the standard block
header for binary data transfers. LSB specifies
that transfers are to be least significant byte
first while MSB specifies most significant byte
first.
g. IC1-IC9, ICA, ICB, ICC, OCL, ICL,
OC1–OC9, OCA, OCB, OCC
These commands provide for calibration coefficient transfers. Table 5-5 shows the ordering of
the calibration coefficients for various calibration types. For example, if you desire the ETF
error term from an 8-ter m calibr ation, y ou wou ld
use the OC4 or IC4 commands.
NOTE
Calibration coefficients are output, or
expected as input, only for the
currently defined set of sweep frequencies. If data points are not at
maximum and/or the frequency range
has been zoome d-in ( with error co rrection turned on), not all calibration coefficients will be output or used as
input.
If a request is made for an unavailable calibration coefficien t array, the 360 VNA treats it as an
impossible request and ignores the command.
360 GPIB PM5-7
Page 56
DATA TRANSFER COMMANDSV ADVANCED GPIB PROGRAMMING
h. OFV, IFV
The OFV command outputs the current 360
VNA measurement frequencies.
The IFV command can be used to input an
arbitrary list of frequencies into the 360 VNA
(2 ≤ number of frequencies ≤ 501). This code
can be used to spec ify a set of fre quencies to used
for calibration (after a calibration type has bee n
specified). Comman d IF V can a lso be used in the
normal measurement mode to input frequencies
for a special application. In this usage, any existing calibration data is lost.
i.IFP, IS1–IS4
These commands input a binary string of data
as information f or store d setups (I S1– IS4), or a s
information for the current front panel setup
(IFP). The data string mus t be exactly the length
of the string output by the OFP or OS1–OS4
commands and is checked for validity before the
operation is performed. If either the number of
bytes, or the contents of the string are invalid, a
parameter out of range error is generated.
For the IFP command, if the setup data is valid
the 360 VNA will change its setup based on the
new front panel setup information.
j.OFP, OS1–OS4
These commands output a binary string of data
from either one of the four stored setups (OS1–
OS4) or from the current front panel setup
(OFP). The size of a fron t panel setup is 3 kBytes
(3072 bytes).
k. ODR
This command ou tputs a binar y str ing that is an
image of the directory table of the current disk
mounted in th e floppy disk drive of the 360 VNA.
If a disk error occurs, the 360 does a disk-errorstatus-update and transfers no data. The data
string for the directory is exactly 3.5 kBytes
(3584 bytes) long.
l.ICD, IFD, ORD, OCD, OFD
These commands transfer data for the
S-parameter o n the active channel. O nly the cur-rent measurement points will be output (ORD,
OCD, OFD) or expected as input (ICD, IFD).
1. The ORD and OCD commands both output
data for the parameter on the active channel
in (real, imaginary) pairs (real, imaginary).
Similarly, ICD expects corrected data for the
parameter on the active chan n el in pair s.
2. The OFD command outputs data values for
the parameter on the active channel that depend on the current graph type being used
(see Table 5-3). The IFD command expects the
data being input to match the graph type on
the active chann el in the same way.
3. When parameter data input to the 360 VN A is
complete (ICD and IFD) the 360 redraws the
parameter on the active channel using this
data. To prevent the newly drawn data from
being overwritten by new measurement data
the instrument should be in hold prior to inputting the data.
m. CRD, CCD, CFD, OCS
The CRD, CCD , and CFD commands co llec t data
in the current data format for the parameter on
the active chann el until either another comman d
is received or data buffer space has been exhausted. The OCS command outputs the collected data.
NOTE
Any comman d after the CRD , CCD, or
CFD commands will terminate the
collection mode. This includes Group
Execute Triggers (GETs) defined using the DEF...END commands. Measurement trigger GETs set up by the
TIB command are permitted. Error
correction must be turned off before
executing CRD.
Upon receipt of the CRD, CCD, or CFD command the 360 VNA will:
1. Clear bit 7 of the main status register.
2. Abort any current sweep.
3. Set up for the collection sweep.
When the system is ready to begin a new sweep,
bit 7 of the main status register is set. If the
instrument is in CW mode, it will phase lock at
that frequency before bit 7 of the main status
register is set. The number of data points that
can be collected is determin ed by th e data for mat
shown in Table 5-6.
n. ICF
This command inputs a binary string of data as
information for the current front panel setup
and calibration.
5-8360 GPIB PM
Page 57
V ADVANCED GPIB PROGRAMMINGDATA TRANSFER COMMANDS
o. OCF
This command outputs the current front panel
setup and calibration information in binary
string data format.
p. ONP
This command outputs the number of data
Tab le 5-6. Maximum Data Points vs Data Format
Data Format
FMC (32-bit)6137
FMB (64-bit)3068
FMA (ASCII)983
Maximum Number of
Collected Points
points curren tly being measured by the 360 VNA
as a single ASCII value.
Figure 5-3 is a listing of an example program
written in Microsoft “C”. It uses a number of
data transfer commands as well as various commands from Section III. The program is written
to run on an IBM-PC or compatible computer
with a National Instruments GPIB-PCIIA board
and “C” language interface drivers. The functions performed by the program are:
Reset the 360 to its default state.
•
Read a full array of frequencies from the 360.
•
Input a subset of these frequencies into the
•
360.
Take S21 transmission data.
•
Loop this data back in to the 360 as e rror term
•
ETF for a transmission frequency response
calibration.
Turn on correction in the 360 and read in a
•
full corrected sweep of data using this as the
error term.
Print the results on the computer screen.
•
b. Data Transfer Program Notes:
This program uses a large time-ou t value (100
•
seconds). This prevents the controller from
quitting while the 360 is busy. For example,
after sending “TRS WFS FMC LSB ORD”
, enough time must be allocated to allow the
360 to complete a new sweep and format the
data for output.
A structure was defined (struct std_header)
•
for manipulatin g the standard block he ader so
that message byte counts are easily accessed
.
All transfers use LSB mode to be compatible
•
with INTEL microprocessors.
FMB is equivalent to “double” in “C”, FMC
•
is equivalent to “float”.
Before measurement data is read from the
•
360, the controller sends a “WFS” command
to ensure the data is valid.
Reads can be terminated by (1) reading the
•
header and th en using the by te count valu e or
(2) by specifying a maximum value for the
transfer count and letting the transfer terminate when the 360 sets the EOI line sign alin g
the end of information.
The program defines a structure for the S21
•
(mag, phase) data pairs output by the 360 for
the OFD command. This allows for easy access to each frequency point’s two data values
using array indexing.
The AFT command must be sent before the
•
IC1 command so that the 360 can discern
what calibration coefficient #1 corresponds to
(ETF in this example).
It is good practice to preface a data transfer
•
command with a format and byte-order command (ie., “FMB LSB OFV”), although both
the format and the byte-order carry on to the
next transfer.
A section of a string may be read (such as the
•
header) followed by the remainder of the
string. Howeve r the entire data stream must
be read before any subsequent data will be
available.
5-10360 GPIB PM
Page 59
V ADVANCED GPIB PROGRAMMINGDATA TRANSFER COMMANDS
Figure 5-3. A “C” Language Example Program for Data Transfer Using the 360 (1 of 2)
360 GPIB PM5-11
Page 60
DATA TRANSFER COMMANDSV ADVANCED GPIB PROGRAMMING
Figure 3-4. A “C” Language Example Program for Data Transfer Using the 360 (2 of 2)
5-12360 GPIB PM
Page 61
V ADVANCED GPIB PROGRAMMINGGROUP EXECUTE TRIGGER COMMANDS
5-4GROUP EXECUTE TRIGGER
COMMANDS
The 360 is extremely flexible in its implementation
of group execute trigger (GET) functions. The two
360 GPIB commands specifically designated for implementing the normal group execute trigger func-
tions are D EF and END (Table 5-7). However, almost
all 360 GPIB commands—in any combination—can
be set up as part of the DEF—END response to the
receipt of a GET (IEEE-488 interface function message) from the external computer.
NOTE
The DEF—END response to the receipt of
a GET interface function message is
turned-off by the receipt of the TIB command earlier in the program. (The TIB
command provides a sweep trigger upon
receipt of a GET interface function message—refer to paragraph 5-9.)
The response to the GET interfac e func tion message
is set up by issuing the DEF command followed by
a sequence of commands terminated with the END
command. The sequence may be comprised of any
sequence of 360 GPIB commands that does not include a data input command. If a data input command is included, the 360 reads the data as additional commands. This usu ally cause s a syntax error
to be issued. The entire DEF—END string is preparsed and compacted. The maximum compacted
string size is 255 characters.
An example of the use of the DEF and END commands is shown in the following command string:
When this sequence of commands is sent to the 360,
it is stored as the response to the group execute
trigger. The commands between the DEF and END
commands will not be execu ted as part of the normal
program flow. The DEF—END sequence will be
executed every time the 360 receives a GET interface function message from the external computer
provided that a TIB command has not been issued
earlier in the program. For the example shown
above, the 360 will perform the following sequence
every time it is triggered by a GET interface function
message:
• Perform a transmission frequency response calibration from 1 to 18 GHz (
STP 18 GHZ BEG TCD NCS
• Turn on marker (
MR1).
• Wait for a full sweep of data (
CFT NOC SRT 1 GHZ
).
WFS).
• Move marker 1 to the maximum value on the
trace (
• Output the maximum value (
MMX).
OM1).
• Move marker 1 to the minimum v alue on the trace
(
MMN).
Output the minimum value (
•
OM1).
Thus, every time the 360 receives a GET interface
function message , it outputs the maximum and
minimum values for the new calibration just performed.
NOTE
1. When the 360 VNA is triggered via the
GPIB, the 360 puts the trigger command
(GET) into the command buffer behind
any preceding instructions. The commands in the DEF ... END string are executed upon completion of the commands
issued prior to the GET command.
2. When the TIB = GPIB coding method
is used for measur ement tr iggering , group
execute triggers will not execute the commands in the DEF... END string. The
group execu te trig ger will initiate a measurement. See paragraph 5-9, Sweep Control Commands, for more details.
Table 5-7. Group Execute Trigger Commands
360 GPIB
Command
DEFBegin definition of group execute trigger actionN/A
ENDEnd definition of group execute trigger actionN/A
DescriptionData Formats
360 GPIB PM5-13
Page 62
DISK FUNCTION CO MM ANDSV ADVANCED GPIB PROGRAMMING
5-5DISK FUNCTION COMMANDS
The Disk Function commands listed in table 5-6 are
used for the following:
• Reading files from the disk.
• Writing files to the disk.
• Deleting files.
• Formatting a data-only disk.
Loading c alibration kit information f ro m th e disk.
•
All of the Disk Function commands, except the INT
and LKT commands, require a file name string. File
name strings can be up to 8 characters long and
must be enclosed by double quote characters (“); see
the descriptions of the LMS, LDT, LID, and LNM
commands in Section III, paragraph 3-11. Examples
of the disk function commands usage are shown in
Figure 5-4.
The TDD and TTB commands enable the user to
store tabular data to the disc and recall it for output
to the printer with the tabular printout points controlled by commands PT0–PT9 (Commands PT0–
PT9 are described in Section III, paragraph 3-11).
NOTE
The maximum file size that can be
handled with the RTB command is 58
kbytes.
Only file name characters accepted by MS-DOS are
valid for use with these commands. Characters that
are not acceptable as file names are:
.— Period/Decimal Point
” — Quotation Marks
/— Slash
\ — Back slash
[ ] — Brackets
:— Colon
| — Pipe
> — Greater Than
< — Less Than
+ — Plus sign
= — Equal Sign
; — Semicolon
, — Comma
And: All ASCII characters with a value lower
than the value of the space character (32 deci-
mal).
CAUTIO N
The INT command immediately formats
the disk loaded in the 360 floppy drive.
Any data on the disk will be destroyed.
Use this command carefully.
Table 5-8. Disk Functions Commands (1 of 2)
360 GPIB
Command
DEC(filename)Delete calibration and front panel setup file from
disk
DED(filename)Delete tabular printout data file from diskString up to 8 characters long for file name
DEN(filename)Delete trace memory file from diskString up to 8 characters long for file name
INTInitialize (format) disk in drive as a data-only diskN/A
LKTLoad calibration kit information from diskN/A
RCK(filename)Recall active channel’s trace memory from disk fileString up to 8 characters long for file name
RLD(filename)Recall calibration data and front panel setup
information from disk file
RTB(filename)Recall tabular data file from disk for output to printerString up to 8 characters long for file name
DescriptionValues
Spaces are ac ce ptable be fore and after the
characters of a command, value or terminator. They are not acceptable between
the characters of these program items.
String up to 8 characters long for file name
String up to 8 characters long for file name
NOTE
5-14360 GPIB PM
Page 63
V ADVANCED GPIB PROGRAMMINGDISK FUNCTION COMMANDS
Table 5-8. Disk Functions Commands (2 of 2)
360 GPIB
Command
SDK(filename)Store active channel’s trace memory to disk fileString up to 8 characters long for file name
STO(filename)Store calibration data and front panel setup
information to disk file
TDD(filename)Store tabular printout data to ASCII disk fileString up to 8 characters long for file name
! EXAMPLE 1 - SAVE CAL AND FRONT
! PANEL SETUP TO DISK
Q$ = CHR$(34) ! DOUBLE QUOTE SYMBOL(“)
C$ = “12_TERM” ! FILE NAME FOR CAL DATA
! STORE TO DISK FILE “12_TERM.CAL”
OUTPUT 706;"STO"&Q$&C$&Q$
! EXAMPLE 2 - SAVE TABULAR DATA
! TO DISK FILE
Q$ = CHR$(34) ! DOUBLE QUOTE SYMBOL(“)
T$ = “S21_THRU” ! FILE NAME FOR TAB DATA
! STORE TO DISK FILE “S21_THRU.DAT”
OUTPUT 706;"TDD"&Q$&T$&Q$
! EXAMPLE 3 - SAVE TRACE MEMORY
! TO DISK, RECALL IT ON A DIFFERENT
! CHANNEL AND THEN DELETE FILE
OUTPUT 706;"CH1 D13 S11 CH3 S21 FHI WFS"
OUTPUT 706;"CH1 STD" ! STORE TRACE TO MEMORY
Q$ = CHR$(34) ! DOUBLE QUOTE SYMBOL(“)
N$ = “S11TRACE” ! FILE NAME FOR TRACE DATA
! STORE TO DISK FILE “S11TRACE.NRM”
OUTPUT 706;"SDK"&Q$&N$&Q$
! RECALL SAME DATA ON CHANNEL 3
OUTPUT 706;"CH3 RCK"&Q$&N$&Q$
! DELETE THE TRACE MEMORY FILE
OUTPUT 706;"DEN"&Q$&N$&Q$
DescriptionValues
String up to 8 characters long for file name
Figure 5-4. Disk Function Commands Example
360 GPIB PM5-15
Page 64
SRQ STATUS BYTE STRUCTURE AND COMM ANDSV ADVANCED GPIB PROGRAMMING
5-6SRQ STATUS BYTE STRUCTURE
AND COMMANDS
The status of the 360 is defined by primary and
secondary status bytes. The structure and contents
of these status bytes are described in the following
paragraphs.
5-6.1Primar y St atu s By te
The bit structure o f the primary status byte is show n
in Table 5-9. The function of each bit is described
below. All bits of the primary status byte are res et
whenever a CSB command is received.
• Cal. Sweep Complete. This bit is set when a
calibration sw eep is c ompleted after the TCD command has been received.
• Sweep Complete In Hold. This bit is set when
a full sweep is completed in hold after the TRS
command has been received.
• Syntax Error. This bit is set is set when a syntax
error occurs
• Parameter Out Of Range. This bit is set when
data values are out of the allowable range or the
data was found to be invalid.
• Action Not Possi bl e. Th is bit is set when a com-
mand can not execute in the current instrument
state.
• 2nd Byte Has Status. This bit is set when a
condition represented by a set bit in the Secondary Status Byte is true.
• SRQ. The Service Request bit is set during the
serial poll response when the 360 is requesting
service.
• Ready for Measurement. This bit is cleared at
the start of both the GPIB measurement trigger
command (TIB) and by the data collection commands (CRD, CCD, CFD). The bit is set after a
point has been measured subsequent to a GET in
the GPIB measurement trigger mode when the
instrument is ready for data collection.
• Self Test Failed. This bit is set true if any por-
tion of the self test fails.
• Hardware Error. This bit is set when there is a
problem with the system hardware.
• Key Pressed. This bit is set when a key on the
front panel is pressed.
Power On. Th is bi t is set when the sy stem is firs t
•
powered on.
Table 5-11 lists the status byte commands. These
commands are used to:
• Output the status of the 360 to t he external computer.
• Input service request enable masks.
Clear the primary and secondary status bytes.
•
In order for the 360 to generate a service requ est for
a particular c on dition , both th e con dition bit an d the
SRQ bit in the Primary Status Byte Mask must be
enabled. The binary valu e of eac h bit in the byte sent
will be:
Bit Value = 1 – Status Condition Enabled.
When the 360 requests service, the serial poll re-
sponse byte will show only one enabled bit set. The
controller can then always tell which enabled condition generated the Service Request (SRQ). This also
implies that the primary status byte and the serial
Tab le 5-9. Primary Status Byte Bit Structure
Bit Number
765 4 3 2 1 0
Ready
for
Meas.
SRQ2nd
Byte
Has
Status
Action
Not
Possible
Out of
Range
Syntax
Error
Com-
plete
in
Hold
Sweep
Com-
plete
5-6.2Secondary Status Byte
Table 5-10. Secondary Status Byte Bit Structure
The bit structure of the Secondary Status Byte is
shown in Table 5-10. The function of each bit is
described below. All bits of the sec ondar y status byte
7 6 543 21 0
Bit Number
are reset whenever a CSB command is received.
• Disk Error. This bit is set when a disk error
Power OnKey
Pressed
X*XXHardware
Error
Self
Test F ail
Disk
Error
occurs.
5-16360 GPIB PM
Page 65
V ADVANCED GPIB PROGRAMMINGSRQ STATUS BYTE STRUCTURE AND COMMANDS
poll response byte will not necessarily be equal. Any
true bits for conditions not enabled will show up
the serial poll response byte. Figure 5-5 shows
listing of an example program that performs
byte-enable mask setup for the primary status
and service request handling operations.
Table 5-11. Status Byte Commands
360 GPIB
Command
CSBClear primary and secondary status bytes N/A
<
<
byte
byte
>
>
IEM
IPM
OEBOutput extended (secondary) status byteOne binary byte
OPBOutp ut pri mar y sta tus by teOne bina ry by te
SQ0Disable service requestsN/A
SQ1Enable any unmarked service requestsN/A
Input extended (secondary) status maskOne binary byte
Input prim ary statu s mask One bina ry by te
in
a
status-
byte
Data transfers for the OPB, OEB, IPM
and IEM commands involve a single
binary data byte. The c ondition mask byte
for the IPM and IEM commands must
immediately follow the command.
DescriptionValues
NOTE
! SET UP SERVICE REQUEST SUBROUTINE ADDRESS
ON INTR 7 GOSUB 1000
! ENABLE SRQ CONDITION AS AN INTERRUPT
ENABLE INTR 7;8
REMOTE 706
! ENABLE SRQ, SYNTAX, PARAM,
! OUT OF RANGE AND ACTION
! NOT POSSIBLE ERRORS = BITS
! 2,3,4 & 6
! MASK = 4+8+16+64 = 92
OUTPUT 706 USING “#,AAA,B”;"IPM",92
1000 ! SRQ SERVICE ROUTINE
1010 STATUS 7,1;A ! READ INTERRUPT CAUSE REGISTER
1020 R=SPOLL(706) ! POLL THE 360
1030 IF BIT(R,2) 1 THEN GOTO 1050
1040 DISP “SYNTAX ERROR”
1050 IF BIT(R,3) 1 THEN GOTO 1070
1060 DISP “PARAMETER OUT OF RANGE”
1070 IF BIT(R,4) 1 THEN GOTO 1090
1080 DISP “ACTION NOT POSSIBLE”
1090 ! READ THE PRIMARY STATUS BYTE
1100 OUTPUT 706;"OPB"
1110 ENTER 706 USING “#,B”;B
1120 DISP “PRIMARY STATUS = ”,B
1130 ! RE-ENABLE INTERRUPT AND RETURN
1140 ENABLE INTR 7;8 @ RETURN
Figure 5-5. Example of Status-Byte-Enable-Mask Setup and Service Request Handling
360 GPIB PM5-17
Page 66
TIME DOMAIN COMMANDSV ADVANCED GPIB PROGRAMMING
5-7TIME DOM AIN COMM ANDS
The time domain commands for the 360 VNA are
listed below in Table 5-12. Option 2A (High-Speed
Time Domain [Distanc e] Software o ption) adds these
The time domain commands are used to:
1. S pecify the domain of a channel.
2. S et up operating modes and parameters for
the selected processing type of the channel.
commands to the 360 VNA software.
Table 5-12. Time Domain Commands (1 of 2)
360 GPIB
Command
DBPSelect distance bandpass mode for active
channel
DCASelect automatic D.C. term calculation for
lowpass
DCOSelect open for D.C. term for lowpassN/AN/A
DCSSelect short for D.C. term for lowpassN/AN/A
Enter value for D.C. term for lowpass
DCV (value)
DCZSelect line impedance for D.C. term for
DLPSelect distance lowpass mode for active
*
lowpass
channel
DescriptionValuesTerminators
N/AN/A
N/AN/A
-1000 MΩ to 1000 MΩ
N/AN/A
N/AN/A
XX1, XX3, XM3
DPISelect distance phasor impulse mode for
active channel
FGTSelect frequency with time gate for active
FQDSelect frequency domain for active channelN/AN/A
GCT (value)Set gate center value
GDSDisplay gate symbols on active channelN/AN/A
GLSSelect low sidelobe gate shapeN/AN/A
GMSSelect minimum sidelobe gate shapeN/AN/A
GNMSelect nominal gate shapeN/AN/A
GOFTurn off gating on active channelN/AN/A
GONTurn on gating on active channelN/AN/A
GRTSelect rectangular gate shapeN/AN/A
GSN (value)Set gate span value
GSP (value)Set gate stop value–999.9999 to +999.9999PSC, NSC, USC,
GST (value)Set gate start value–999.9999 to +999.9999PSC, NSC, USC,
channel
0.0000 to 999.999 µs
0.0000 to 999.999 m
0.0000 to 999.999 µs
0.0000 to 999.999 m
N/AN/A
N/AN/A
PSC, NSC, USC,
MMT, CMT, MTR
PSC, NSC, USC,
MMT, CMT, MTR
∗ Certain time doma in codes can only be used with particular processing types or instrument states. For example, “DCV 25 XX1" sets the
d.c. term for low pass to 25 ohms. The 360 can only execute this comma nd string if the active channel is in the time domain low pass
mode (TLP or DLP) or if a valid lowp ass set of frequencie s exist for freque ncy domain (FQD) or freq uency gated by time (FGT).
5-18360 GPIB PM
Page 67
V ADVANCED GPIB PROGRAMMINGTIME DOMAIN COMMANDS
Table 5-12. Time Domain Commands (2 of 2)
360 GPIB
Command
LPISelect lowpass impulse responseN/AN/A
LPSSelect lowpass s tep responseN/AN/A
MRRRestore original marker rangeN/AN/A
TBPSelect time bandpass mode for active
channel
TLPSelect time lowpass mode for active channelN/AN/A
TPISelect time phasor impulse mode for active
channel
WLSSelect low sidelobe window shapeN/AN/A
WMSSelect minimum sidelobe window shapeN/AN/A
WNMSelect nominal window shapeN/AN/A
WRTSelect rectangular window shapeN/AN/A
ZCT (value)Set zoom range center value
ZSN (value)Set zoom range span value
DescriptionValuesTerminators
N/AN/A
N/AN/A
–999.999 to 999.999 µs
–999.999 to 999.999 m
0 to 999.999 µs
0 to 999.999 m
PSC, NSC, USC
MMT, CMT, MTR
PSC, NSC, USC
MMT, CMT, MTR
ZSP (value)Set zoom range stop value
ZST (value)Set zoom range stop value
–999.999 to 999.999 µs
–999.999 to 999.999 m
–999.999 to 999.999 µs
–999.999 to 999.999 m
PSC, NSC, USC
MMT, CMT, MTR
PSC, NSC, USC
MMT, CMT, MTR
360 GPIB PM5-19
Page 68
MULTIPLE SOURCE CONT RO L COMM ANDSV ADVANCED GPIB PROGRAMM ING
5-8MULTIPLE SOURCE CONTROL
COMMANDS
Table 5-13 lists the multiple source control commands. These commands are used to define up to
five different “multiple source control bands”. In
each, the device under test (DUT), source 1, source
2, and receiver frequency ranges may be different.
The DUT frequency range is entered using any of
the frequency entry commands. The MSD command
puts the 360 in the DEFINE mode, which allows
entry of arbitrary frequencies for the DUT. Band
equations for sou rce 1, sou rce 2, an d th e rec eiv er ar e
then set up using the ED1, ED2, EDR, etc, commands. The band equations used are shown below.
In these equations, “F” is the DUT frequency range.
For swept operation:
F = (m ult ipl ier/ di viso r) x (F + offset),
or, for CW operation: .
F = (m ult ipl ier/ di viso r) x (offset).
For a frequency band to be saved, the band equations must produce frequencies within the operating
range of the respective system component.
Figure 5-6 shows an example program using
multiple source control commands. This program is
for a fixed LO, swept IF mixer measurement. The
frequency values used are:
BD1 - BD5Select multiple source control band 1-5(Limited to current DUT range)N/A
BSP (value)Ent er band stop f requen cy for multiple so urc e cont rolStart sweep frequency to stop
BST (value)Enter band 1 startup frequency for multiple source
control
CLBClear all multiple source control band definitionsN/AN/A
ECWMultiple source control equation in CW modeN/AN/A
ED1Edit source 1 multiple source control equationN/AN/A
ED2Edit source 2 multiple source control equationN/AN/A
EDR Edit receiver multiple source control equationN/AN/A
EDV (value)Set multiple source control equation divisor–199 to –1, 1 to 199XX1, XX3, XM3
EML (value)Set multiple source control equation multiplier–199 to 199XX1, XX3, XM3
EOS (value)Set multiple source control equation offset frequency–999.9999 to 999.9999GHZ, MHZ, KHZ
ESW Multiple source control equation in sweep modeN/AN/A
MS0Multiple source control offN/AN/A
Description ValuesTerminators
GHZ, MHZ, KHZ
sweep frequency
Start sweep frequency to stop
sweep frequency
GHZ, MHZ, KHZ
MS1Multiple source control onN/AN/A
MSDMultiple source control define modelN/AN/A
SVBSave multiple source control band definitionN/AN/A
5-20360 GPIB PM
Page 69
V ADVANCED GPIB PROGRAMMINGSWEEP CONTROL COMMANDS
5-9SWEEP CONTROL COMMANDS
Table 5-14 lists the 360 GPIB commands that allow
control of sweep triggering. The TIN, TEX and TIB
commands select the measurement trigger source,
as follows:
• Command TIN selects internal triggering;
• Command TEX selects triggering via the rear-
panel input connector;
Command TIB selects triggering via the group
•
execute trigger, GET, which is an IEEE-488 interface function message that is issued by the external computer.
NOTE
The use of the TIB c ommand turns- off
the normal DEF—END response to
the GET interface function message;
refer to paragraph 5-4.
The HC0 command should be used to disable the
internal I.F. calibration when external or GPIB triggering is used (so that triggers are not missed while
Table 5-14. Sweep Control Commands
360 GPIB
Command
HC0Disable Internal I.F. Calibration
HC1Enable and Tr igger Internal I . F. Calibration
TEXSelect External Measurement Triggering
Description
the instrument performs an I.F. calibration). The
HC1 command can then be used to enable and
initiate an immediate I.F. calibration, when desired.
5-10REAR PANEL OUTPUT CONTROL
COMMANDS
Table 5-15 lists the commands for controlling the
rear-panel voltage output of the 360 VNA. The RV1
command enables the output and comman d RV0 disables it. The orientation of the output can be set to
either horizontal (RVH), vertical (RVV), or lock direction (RVL).
In the horizontal mode, the voltage output is a
digital ramp starting at the voltage start value set
by command VST and ending at the voltage stop
value set by command VSP. The start value
corresponds to the first point of the sweep and the
stop value corresponds to last point of the sweep. In
the vertical mode, the output voltage is a measure
of the instantaneous data point value. The output
voltage is related to the scaling of the graph for
channe l 1. Th e refe re nce line c orr espon ds to the zer o
volt value and each gratic le line is equal to a ±1 volt
value span. The values set by the VST and VSP
commands have no effect in the vertical mode.
In the lock direction mode, the start voltage value is
output for forward sweeps (lock to Ra). The stop
voltage value is output for reverse sweeps (lock
to Rb).
TIBSelect Measurement Triggering Via
Group Execute Trigger
TINSelect Internal Measurement Triggering
The RP0 command is used to set an intermediate
voltage value that is output at the rear panel connector. This command can be executed only if the
normal rear panel output voltage is disabled.
Table 5-15. Rear Panel Output Control Commands
360 GPIB
Command
RPO (value)Set value for direct rear panel voltage–10 to 9.96 voltsVLT
RV0Disable rear panel output voltage N/AN/A
RV1Enable rear panel output voltage N/AN/A
RVHSelect horizontal rear output voltage modeN/AN/A
RVLSelect lock direction output voltage modeN/AN/A
RVVSelect verticle rear output voltage modeN/AN/A
VSP (value)Set stop value for rear panel output voltage–10 to 9.96 voltsVLT
VST (value)Set start value for rear panel output voltage–10 to 9.96 voltsVLT
DescriptionValuesTerminators
360 GPIB PM5-21
Page 70
SCREEN DRAW AND RECEIVER MODE
COMMAND CODESV ADVANCED GPIB PROGRAMMING
5-11SCREEN DRAW COMMANDS
The commands listed in Table 5-16 control the
screen drawn functions of the 360 VNA in the GPIB
mode of operation.
Table 5-16. Screen Draw Commands
360 GPIB
Command
CWP (value)Enter numbe r of
DD0Turn off data
DD1Turn on data
DescriptionValues
points drawn in
CW
drawing
drawing
1 – 501XX1
N/AN/A
N/AN/A
Termin-
ators
5-12R ECE IVER MOD E COMM ANDS
The commands listed in Table 5-17 control the 360
VNA receiver mode functions in the GPIB mode of
operation.
Table 5-17. Receiver Mode Control Commands
360 GPIB
Command
SDRSelect standard receiver mode
SL0Selec t source lock mode with GPIB sour ce
control off
SL1Selec t source lock mode with GPIB sour ce
control on
ST0Select set on mode with GPIB source
control off
ST1Select set on mode with GPIB source
control on
TK0Select tracking mode with GBIB source
control off
TK1Select tracking mode with GBIB source
control on
Description
5-22360 GPIB PM
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.