Anritsu 69167B SCPI Programmers Guide

SERIES
693XXB

SYNTHESIZED HIGH PERFORMANCE

SIGNAL GENERATOR

SCPI PROGRAMMING MANUAL

490 JARVIS DRIVE
MORGAN HILL, CA 95037-2809

P/N: 10370-10350

REVISION: A

PRINTED: JANUARY 1999

COPYRIGHT 1999 ANRITSU CO.

WARRANTY

The Anritsu product(s) listed on the title page is (are) warranted against defects in materials and
workmanship for one year from the date of shipment.

Anritsu'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 Anritsu for
warranty repairs. Obligation is limited to the original purchaser. Anritsu is not liable for consequen­tial damages.

LIMITATION OF WARRANTY

The foregoing warranty does not apply to Anritsu 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 specifi­cations of the product. No other warranty is expressed or implied, and the remedies provided herein
are the Buyer's sole and exclusive remedies.

TRADEMARK ACKNOWLEDGEMENTS

Adobe Acrobat is a registered trademark of Adobe Systems Incorporated.

NOTICE

Anritsu Company has prepared this manual for use by Anritsu Company personnel and customers
as a guide for the proper installation, operation, and maintenance of Anritsu Company equipment
and computor programs. The drawings, specifications, and information contained herein are the
property of Anritsu Company, and any unauthorized use or disclosure of these drawings, specifica­tions, and information is prohibited; they shall not be reproduced, copied, or used in whole or in part
as the basis for manufacture or sale of the equipment or software programs without the prior writt­ten consent of Anritsu Company.

Table of Contents

Chapter 1 - General GPIB Information

1-1 SCOPE OF MANUAL.................1-3

Electronic Manual ................1-3

GPIB Programming Manual ...........1-3

1-2 INTRODUCTION ...................1-5

1-3 IEEE-488 INTERFACE BUS DESCRIPTION ...1-5

Functional Elements...............1-6

Bus Structure ..................1-7

Data Bus Description ..............1-7

Data Byte Transfer Control Bus Description ...1-8

General Interface Management Bus Description . 1-9

Device Interface Function Capability ......1-10

Message Types .................1-11

1-4 693XXB GPIB OPERATION.............1-13

Setting GPIB Operating Parameters ......1-13

Selecting the Interface Language ........1-13

Response to GPIB Interface Function Messages . 1-13

Chapter 2 - Programming with SCPI Commands

2-1 INTRODUCTION ...................2-3

2-2 INTRODUCTION TO SCPI PROGRAMMING ...2-3

SCPI Command Types ..............2-3

Common Commands ...............2-4

Required and Optional SCPI Commands .....2-4

Query Commands ................2-4

Command Names ................2-5

Hierarchical Command Structure ........2-6

Data Parameters ................2-7

Unit Suffixes ..................2-7

2-3 NOTATIONAL CONVENTIONS ...........2-8

General Notations ................2-8

Parameter Notations...............2-9

Notational Examples ..............2-10

2-4 SCPI INTERFACE LANGUAGE SELECTION. . . 2-11

Front Panel Selection..............2-11

693XXB SCPI PM i

Table of Contents (Continued)

Remote Selection ................2-11

2-5 STATUS SYSTEM PROGRAMMING........2-12

Status Group Registers .............2-12

Status Group Reporting.............2-14

2-6 TRIGGER SYSTEM PROGRAMMING .......2-19

Trigger System Operation............2-19

Chapter 3 - Programming Commands

3-1 INTRODUCTION ...................3-7

3-2 COMMON COMMANDS ...............3-7

IEEE 488.2 Mandated Commands ........3-7

Optional Common Commands ..........3-9

3-3 SUBSYSTEM COMMANDS.............3-10

3-4 ABORT COMMAND (SUBSYSTEM) ........3-11

3-5 CONTROL SUBSYSTEM ..............3-12

3-6 DIAGNOSTIC SUBSYSTEM ............3-17

3-7 DISPLAY SUBSYSTEM ...............3-18

3-8 INITIATE SUBSYSTEM ..............3-19

3-9 OUTPUT SUBSYSTEM ...............3-21

3-10 SOURCE SUBSYSTEM ...............3-25

3-11 STATUS SUBSYSTEM...............3-133

3-12 SYSTEM SUBSYSTEM ..............3-145

3-13 TRIGGER SUBSYSTEM..............3-149

3-14 :TSWeep COMMAND................3-154

3-15 UNIT SUBSYSTEM ................3-155

Chapter 4 - Error Messages

4-1 INTRODUCTION ...................4-3

4-2 ERROR QUERY ....................4-3

4-3 ERROR QUEUE....................4-4

4-4 ERROR CODES ....................4-4

4-5 NO ERROR ......................4-4

ii 693XXB SCPI PM

Table of Contents (Continued)

4-6 COMMAND ERRORS.................4-5

4-7 EXECUTION ERRORS ...............4-10

4-8 DEVICE-SPECIFIC ERRORS............4-16

4-9 QUERY ERRORS ..................4-18

4-10 PARSER ERRORS ..................4-19

4-11 SELF-TEST ERRORS ................4-20

Appendix A - Overall Command Tree

A-1 INTRODUCTION...................A-1

Appendix B - SCPI Conformance Information

B-1 INTRODUCTION...................B-1

693XXB SCPI PM iii/iv

Chapter 1
General GPIB Information

Table of Contents

1-1 SCOPE OF MANUAL.................1-3

Electronic Manual ................1-3

GPIB Programming Manual ...........1-3

1-2 INTRODUCTION ...................1-5

1-3 IEEE-488 INTERFACE BUS DESCRIPTION ...1-5

Functional Elements...............1-6

Bus Structure ..................1-7

Data Bus Description ..............1-7

Data Byte Transfer Control Bus Description ...1-8

General Interface Management Bus Description . 1-9

Device Interface Function Capability ......1-10

Message Types .................1-11

1-4 693XXB GPIB OPERATION.............1-13

Setting GPIB Operating Parameters ......1-13

Selecting the Interface Language ........1-13

Response to GPIB Interface Function Messages . 1-13

Chapter 1
General GPIB Information

1-1

SCOPE OF MANUAL

This manual provides information for remote operation of the Series
693XXB Synthesized High Performance Signal Generator using com­mands sent from an external controller via the IEEE-488 General Pur­pose Interface Bus (GPIB). It includes the following:

A general description of the GPIB and the bus data transfer and

q

control functions.
A listing of the IEEE-488 Interface Function Messages recog-

q

nized by the signal generator with a description of its response.
A complete listing and description of all the Standard Commands

q

for Programmable Instruments (SCPI) commands that can be
used to control signal generator operation with examples of
command usage.

This manual is intended to be used in conjunction with the Series
693XXB Synthesized High Performance Signal Generator Operation
Manual, P/N 10370-10348. Refer to that manual for general informa­tion about the 693XXB, including equipment set up and front panel
(manual mode) operating instructions.

Electronic
Manual

This manual is available on CD ROM as an Adobe
Acrobat Portable Document Format (*.pdf) file. The
file can viewed using Acrobat Reader, a free pro­gram that is also included on the CD ROM. The file
is “linked” such that the viewer can choose a topic to
view from the displayed “bookmark” list and “jump”
to the manual page on which the topic resides. The
text can also be word-searched. Contact Anritsu
Customer Service for price and availability.

GPIB Pro­gramming
Manual

In addition to the SCPI programming commands
described in this manual, the signal generator's
GPIB interface also accepts and implements a set of
693XXB GPIB Product-Specific (“NATIVE”) com­mands. These GPIB commands are listed and de­scribed in the Series 693XXB Synthesized High
Performance Signal Generator GPIB Programming
Manual, P/N 10370-10349.

693XXB SCPI PM 1-3

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

IE EE -488 B U S (16 Lines)

DEVICE A

A b le to ta lk , lis te n ,
and control

(e.g. CO M PUTER)

DEVICE B

A b le to t a lk a n d lis t e n

(e.g . 693XX B
SIGNAL
GENERATO R)

DEVICE C

D a ta B u s

(8 signal lines)

D a ta B y te T ra n s fe r
Control Bus

(3 signal lines)

DATA LINES

HANDSHAKE Lines

O n ly a b le t o lis te n

(e.g. O THER
IN STR UM ENT**)

DEVICE D

O n ly a b le to ta lk

(e.g. O THER
IN STR UM ENT**)

G eneral Interface
M anagem ent B us

(5 signal lines)

DATA INPUT/OUTPUT,
DIO 1 thru DIO 8

DAV - DATA VALID
NRFD - NO T READY FOR DATA*
NDAC - NO T DATA ACCEPTED*

IFC - INTERFACE CLEAR
ATN - ATTENTION
SRQ - SER VIC E REQ UEST
REN - REMO TE ENABLE
E O I - E N D O R ID E N T IF Y

* N EG ATIO N IS REPR ESENTED B Y
LOW STATE ON THESE TW O LINES

** IF U S E D

Figure 1-1. Interface Connections and GPIB Bus Structure

M anagem ent
C O N TR O L Lines

1-4 693XXB SCPI PM

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

1-2

1-3

INTRODUCTION

IEEE-488 INTERFACE
BUS DESCRIPTION

This chapter provides a general description of the GPIB and the bus
data transfer and control functions. It also contains a listing of the
693XXB's GPIB interface function subset capability and response to
IEEE-488 interface function messages.

The GPIB information presented in this chapter is general in nature.
For complete and specific information, refer to the following docu­ments: ANSI/IEEE Std 488.1-1987 IEEE Standard Digital Interface

for Programmable Instrumentation and ANSI/IEEE Std 488.2-1987
IEEE Standard Codes, Formats, Protocols and Common Commands.

These documents precisely define the total specification of the
mechanical and electrical interface, and of the data transfer and
control protocols.

The IEEE-488 General Purpose Interface Bus (GPIB) is an instrumen­tation interface for integrating instruments, computers, printers, plot­ters, and other measurement devices into systems. The GPIB uses 16
signal lines to effect transfer of information between all devices con­nected on the bus.

The following requirements and restrictions apply to the GPIB.

q No more than 15 devices can be interconnected by one contiguous

bus; however, an instrumentation system may contain more than
one interface bus.

q

The maximum total cumulative cable length for one interface bus
may not exceed twice the number of devices connected (in
meters), or 20 meters—whichever is less.

q

A maximum data rate of 1 Mb/s across the interface on any
signal line.

q

Each device on the interface bus must have a unique address,
ranging from 00 to 30.

The devices on the GPIB are connected in parallel, as shown in Figure
1-1. The interface consists of 16 signal lines and 8 ground lines in a
shielded cable. Eight of the signal lines are the data lines, DIO 1 thru
DIO 8. These data lines carry messages (data and commands), one
byte at a time, among the GPIB devices. Three of the remaining lines
are the handshake lines that control the transfer of message bytes
between devices. The five remaining signal lines are referred to as
interface management lines.

The following paragraphs provide an overview of the GPIB including a
description of the functional elements, bus structure, bus data transfer
process, interface management bus, device interface function require­ments, and message types.

693XXB SCPI PM 1-5

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

Functional
Elements

Effective communications between devices on the
GPIB requires three functional elements; a talker,a
listener, and a controller. Each device on the GPIB is
categorized as one of these elements depending on
its current interface function and capabilities.

Talker

A talker is a device capable of sending device­dependent data to another device on the bus when
addressed to talk. Only one GPIB device at a time
can be an active talker.

Listener

A listener is a device capable of receiving device­dependent data from another device on the bus
when addressed to listen. Any number of GPIB
devices can be listeners simultaneously.

Controller

A controller is a device, usually a computer, capable
of managing the operation of the GPIB. Only one
GPIB device at a time can be an active controller.
The active controller manages the transfer of
device-dependent data between GPIB devices by
designating who will talk and who will listen.

System Controller

The system controller is the device that always
retains ultimate control of the GPIB. When the
system is first powered-up, the system controller is
the active controller and manages the GPIB. The
system controller can pass control to a device, mak­ing it the new active controller. The new active con­troller, in turn, may pass control on to yet another
device. Even if it is not the active controller, the
system controller maintains control of the Interface
Clear (IFC) and Remote Enable (REN) interface
management lines and can thus take control of the
GPIB at anytime.

1-6 693XXB SCPI PM

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

Bus
Structure

The GPIB uses 16 signal lines to carry data and
commands between the devices connected to the
bus. The interface signal lines are organized into
three functional groups.

Data Bus (8 lines)

q

Data Byte Transfer Control Bus (3 lines)

q

General Interface Management Bus (5 lines)

q

The signal lines in each of the three groups are des­ignated according to function. Table 1-1 lists these
designations.

Table 1-1. Interface Bus Signal Line Designations

Bus Type

Data Bus DIO1–DIO8 Data Input/Output, 1 thru 8
Data Byte

Transfer
Control Bus

General
Interface
Management
Bus

Signal Line

DAV
NRFD
NDAC

ATN
IFC
SRQ
REN
EOI

Name

Data Available
Not Ready For Data
Not Data Accepted

Attention
Interface Clear
Service Request
Remote Enable
End Or Identify

Function

Data Bus
Description

The data bus is the conduit for the transfer of data
and commands between the devices on the GPIB. It
contains eight bi-directional, active-low signal lines
—DIO 1 thru DIO 8. Data and commands are trans­ferred over the data bus in byte-serial, bit-parallel
form. This means that one byte of data (eight bits) is
transferred over the bus at a time. DIO 1 represents
the least-significant bit (LSB) in this byte and
DIO 8 represents the most-significant bit (MSB).
Bytes of data are normally formatted in seven-bit
ASCII (American Standard Code for Information In­terchange) code. The eighth (parity) bit is not used.

Each byte placed on the data bus represents either a
command or a data byte. If the Attention (ATN) in­terface management line is TRUE while the data is
transferred, then the data bus is carrying a bus
command which is to be received by every GPIB de­vice. If ATN is FALSE, then a data byte is being
transferred and only the active listeners will receive
that byte.

693XXB SCPI PM 1-7

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

1st Data Byte 2nd Data Byte

DIO1-DIO8

(composite)

DAV

Valid

Not

Valid

Valid

Not

Valid

All

NRFD

NDAC

Figure 1-2. Typical GPIB Handshake Operation

Data Byte
Transfer
Control Bus
Description

Ready

None

Accept

Control of the transfer of each byte of data on the
data bus is accomplished by a technique called the
“three-wire handshake”, which involves the three
signal lines of the Data Byte Transfer Control Bus.

None

Ready

Accept

All

Accept

This technique forces data transfers at the speed of
the slowest listener, which ensures data integrity in
multiple listener transfers. One line (DAV) is con­trolled by the talker, while the other two (NRFD and
NDAC) are wired-OR lines shared by all active lis­teners. The handshake lines, like the other GPIB
lines, are active low. The technique is described
briefly in the following paragraphs and is depicted
in Figure 1-2. For further information, refer to
ANSI/IEEE Std 488.1.

All

Ready

None

None

Ready

All

Accept

DAV (Data Valid)

This line is controlled by the active talker. Before
sending any data, the talker verifies that NDAC is
TRUE (active low) which indicates that all listeners
have accepted the previous data byte. The talker
then places a byte on the data lines and waits until
NRFD is FALSE (high) which indicates that all ad­dressed listeners are ready to accept the informa­tion. When both NRFD and NDAC are in the proper
state, the talker sets the DAV line TRUE (active
low) to indicate that the data on the bus is valid
(stable).

NRFD (Not Ready For Data)

This line is used by the listeners to inform the
talker when they are ready to accept new data. The
talker must wait for each listener to set the NRFD

1-8 693XXB SCPI PM

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

line FALSE (high) which they will do at their own
rate. This assures that all devices that are to accept
the data are ready to receive it.

NDAC (Not Data Accepted)

This line is also controlled by the listeners and is
used to inform the talker that each device addressed
to listen has accepted the data. Each device releases
NDAC at its own rate, but NDAC will not go FALSE
(high) until the slowest listener has accepted the
data byte.

General
Interface
Management
Bus
Description

The general interface management bus is a group of
five signal lines used to manage the flow of informa­tion across the GPIB. A description of the function of
each of the individual control lines is provided be­low.

ATN (Attention)

The active controller uses the ATN line to define
whether the information on the data bus is a com­mand or is data. When ATN is TRUE (low), the bus
is in the command mode and the data lines carry
bus commands. When ATN is FALSE (high), the bus
is in the data mode and the data lines carry device­dependent instructions or data.

EOI (End or Identify)

The EOI line is used to indicate the last byte of a
multibyte data transfer. The talker sets the EOI line
TRUE during the last data byte.

The active controller also uses the EOI line in con­junction with the ATN line to initiate a parallel poll
sequence.

IFC (Interface Clear)

Only the system controller uses this line. When IFC
is TRUE (low), all devices on the bus are placed in a
known, quiescent state (unaddressed to talk, unad­dressed to listen, and service request idle).

REN (Remote Enable)

Only the system controller uses this line. When
REN is set TRUE (low), the bus is in the remote
mode and devices are addressed either to listen or to
talk. When the bus is in remote and a device is ad­dressed, it receives instructions from the GPIB
rather than from its front panel. When REN is set
FALSE (high), the bus and all devices return to local
operation.

693XXB SCPI PM 1-9

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

SRQ (Service Request)

The SRQ line is set TRUE (low) by any device re­questing service by the active controller.

Device
Interface
Function
Capability

An interface function is the GPIB system element
which provides the basic operational facility through
which a device can receive, process, and send mes­sages. Each specific interface function may only
send or receive a limited set of messages within par­ticular classes of messages. As a result, a set of
interface functions is necessary to achieve complete
communications among devices on the GPIB.
ANSI/IEEE Std 488.1 defines each of the interface
functions along with its specific protocol.

ANSI/IEEE Std 488.2 specifies the minimum set of
IEEE 488.1 interface capabilities that each GPIB
device must have. This minimum set of interface
functions assures that the device is able to send and
receive data, request service, and repond to a device
clear message. Table 1-2 lists the interface function
capability of the series 693XXB signal generator.

Table 1-2. 693XXB Interface Function Capability

Function
Identifier

AH1 Acceptor Handshake Complete Capability

Function 693XXB Capability

SH1 Source Handshake Complete Capability

T6 Talker No Talk Only (TON)

L4 Listener No Listen Only (LON)
SR1 Service Request Complete Capability
RL1 Remote/Local Complete Capability
PP1 Parallel Poll Complete Capability
DC1 Device Clear Complete Capability
DT1 Device Trigger Complete Capability

C0, 1, 2, 3,28Controller Capability

Options

E2 Tri-State Drivers Three-state bus drivers

C0, No Capability;
C1, System Controller;
C2, Send IFC and Take Charge;
C3, Send REN;
C28, Send IF Messages

1-10 693XXB SCPI PM

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

Message
Types

There are three types of information transmitted
over the GPIB—interface function messages,
device-specific commands, and data and instrument
status messages.

Interface Function Messages

The controller manages the flow of information on
the GPIB using interface function messages, usually
called commands or command messages. Interface
function messages perform such functions as initial­izing the bus, addressing and unaddressing devices,
and setting device modes for remote or local opera­tion.

There are two types of commands—multiline and
uniline. Multiline commands are bytes sent by the
active controller over the data bus (DIO1-DIO8)
with ATN set TRUE. Uniline commands are signals
carried by the individual interface management
lines.

The user generally has control over these com­mands; however, the extent of user control depends
on the implementation and varies with the specific
GPIB interface hardware and software used with
the external controller.

Device-Specific Commands

These commands are keywords or mnemonic codes
sent by the external controller to control the setup
and operation of the addressed device or instru­ment. The commands are normally unique to a par­ticular instrument or class of instruments and are
described in its documentation.

Device-specific commands are transmitted over the
data bus of the GPIB to the device in the form of
ASCII strings containing one or more keywords or
codes.They are decoded by the device's internal con-
troller and cause the various instrument functions
to be performed.

Data and Instrument Status Messages

These messages are sent by the device to the exter­nal controller via the GPIB. They contain measure­ment results, instrument status, or data files that
the device transmits over the data bus in response
to specific requests from the external controller. The
contents of these messages are instrument specific
and may be in the form of ASCII strings or binary
data.

693XXB SCPI PM 1-11

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

In some cases data messages will be transmitted
from the external controller to the device. For exam­ple, messages to load calibration data.

An SRQ (service request) is an interface function
message sent from the device to the external control­ler to request service from the controller, usually
due to some predetermined status condition or error.
To send this message, the device sets the SRQ line
of the General Interface Management Bus true,
then sends a status byte on the data bus lines.

An SRQ interface function message is also sent by
the device in response to a serial poll message from
the controller, or upon receiving an Output Status
Byte(s) command from the controller. The protocols
associated with the SRQ functions are defined in the
ANSI/IEEE Std 488.2 document.

The manner in which interface function messages
and device-specific commands are invoked in pro­grams is implementation specific for the GPIB inter­face used with the external controller. Even though
both message types are represented by mnemonics,
they are implemented and used in different ways.

Normally, the interface function messages are sent
automatically by the GPIB driver software in re­sponse to invocation of a software function. For ex­ample, to send the IFC (Interface Clear) interface
fuction message, one would call the ibsic function of
the National Instruments software driver. On the
other hand, the command *RST (Reset) is sent in a
command string to the addressed device. In the case
of the National Instruments example, this would be
done by using the ibwrt function call.

1-12 693XXB SCPI PM

GENERAL GPIB 693XXB
INFORMATION GPIB OPERATION

1-4

693XXB GPIB
OPERATION

All Series 693XXB Synthesized High Performance Signal Generator
functions, settings, and operating modes (except for power on/standby)
are controllable using commands sent from an external controller via
the GPIB. When in the remote (GPIB) mode, the signal generator
functions as both a listener and a talker. The GPIB interface function
capability of the 693XXB is listed in Table 1-2 (page 1-10).

Setting GPIB
Operating
Parameters

Selecting the
Interface
Language

The 693XXB leaves the factory with the GPIB ad­dress value set to 5 and the data delimiting termi­nator set to carriage return and line feed (CR/LF). A
different address value can be entered from the
front panel using the Configure GPIB menu. Using
this same menu, the data delimiting terminator can
be changed to carriage return (CR) only. Refer to
Chapter 2 of the Series 693XXB Synthesized High
Performance Signal Generator Operation Manual
for the procedure.

Series 693XXB Synthesized High Performance Sig­nal Generators with Option 19 can be remotely op­erated using one of two external interface languages
—Native or SCPI. The Native interface language
uses a set of 693XXB GPIB Product Specific com­mands to control the instrument; the SCPI interface
language uses a set of the Standard Commands for
Programmable Instruments commands to control
the unit. Selecting which of these external interface
languages is to be used can be made from the front
panel using the Configure GPIB menu. Refer to
page 2-11 for the procedure.

Response to
GPIB
Interface
Function
Messages

Table 1-3 (page 1-14) lists the GPIB Interface Func­tion Messages that the 693XXB will recognize and
respond to. With the exception of the Device Clear
and Selected Device Clear messages, these mes­sages affect only the operation of the 693XXB GPIB
interface. The signal generator's response for each
message is indicated.

Interface function messages are transmitted on the
GPIB data lines and interface management lines as
either unaddressed or addressed commands. The
manner in which these messages are invoked in
programs is implementation dependent. For pro­gramming information, refer to the documentation
included with the GPIB Interface used for the
external controller.

693XXB SCPI PM 1-13

GENERAL GPIB 693XXB GPIB
INFORMATION OPERATION

Table 1-3. 693XXB Response to GPIB Interface Function Messages

Interface Function Message

Device Clear (DCL)
Selected Device Clear
(SDC)

Go To Local (GTL) Yes Returns the 693XXB to local (front

Group Execute Trigger
(GET)

Interface Clear (IFC) No Stopsthe 693XXB GPIB interface

Local Lockout (LLO) No Disables the front panel menu

Remote Enable (REN) No Places the 693XXB under remote

Serial-Poll Enable (SPE) No Outputs the serial-poll status byte.
Serial-Poll Disable (SPD) No Disables the serial-poll function.
Parallel-Poll Configure (PPC) Yes Responds to a parallel-poll message

Addressed

Command

No

Yes

Yes Executes a string of commands, if

Resets the 693XXB to its default
state. (Equivalent to sending the
*RST command.)

panel) control.

programmed.

from listening or talking. (The front
panel controls are not cleared.)

RETURN TO LOCAL soft-key.

(GPIB) control when it has been ad­dressed to listen.

(PPOLL) by setting assigned data
bus line to the logical state (1,0) that
indicates its correct SRQ status.

693XXB Response

Parallel-Poll Unconfigure
(PPU)

No Disables the parallel-poll function.

1-14 693XXB SCPI PM

Chapter 2
Programming with
SCPI Commands

Table of Contents

2-1 INTRODUCTION ...................2-3

2-2 INTRODUCTION TO SCPI PROGRAMMING ...2-3

SCPI Command Types ..............2-3

Common Commands ...............2-4

Required and Optional SCPI Commands .....2-4

Query Commands ................2-4

Command Names ................2-5

Hierarchical Command Structure ........2-6

Data Parameters ................2-7

Unit Suffixes ..................2-7

2-3 NOTATIONAL CONVENTIONS ...........2-8

General Notations ................2-8

Parameter Notations...............2-9

Notational Examples ..............2-10

2-4 SCPI INTERFACE LANGUAGE SELECTION. . . 2-11

Front Panel Selection..............2-11

Remote Selection ................2-11

2-5 STATUS SYSTEM PROGRAMMING........2-12

Status Group Registers .............2-12

Status Group Reporting.............2-14

2-6 TRIGGER SYSTEM PROGRAMMING .......2-19

Trigger System Operation............2-19

Chapter 2
Programming with
SCPI Commands

2-1

2-2

INTRODUCTION

INTRODUCTION TO SCPI
PROGRAMMING

This chapter provides an introduction to SCPI programming that in­cludes descriptions of the command types, hierarchial command struc­ture, data parameters, and notational conventions. Information on
693XXB status system and trigger system programming is also pro­vided.

The Standard Commands for Programmable Instruments (SCPI) de­fines a set of standard programming commands for use by all SCPI
compatible instruments. SCPI is intended to give the ATE user a con­sistent environment for program development. It does so by defining
controller messages, instrument responses, and message formats for
all SCPI compatible instruments. The IEEE-488 (GPIB) interface for
the 693XXB was designed to conform to the requirements of SCPI

1993.0. The set of SCPI commands implemented by the 693XXB GPIB
interface provides a comprehensive set of programming functions cov­ering all the major functions of the 693XXB signal generator.

SCPI
Command
Types

SCPI commands, which are also referred to as SCPI
instructions, are messages to the instrument to per­form specific tasks. The 693XXB command set in­cludes:

q

“Common” commands (IEE488.2 mandated
commands)

q

SCPI required commands

q

SCPI optional commands (per SCPI 1993.0)

q

SCPI compliant commands that are unique to
the 693XXB.

The SCPI conformance information for the 693XXB
signal generator command set is contained in Ap­pendix B— SCPI Conformance Information.

693XXB SCPI PM 2-3

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Common Commands

*CLS *RST
*ESE *SRE
*ESE? *SRE?
*ESR? *STB?
*IDN? *TST?
*OPC *WAI
*OPC?

SCPI Required Commands

:STATus

:OPERation

[:EVENt]?
:CONDition?

:ENABle
:PRESet
:QUEStionable

[:EVENt]?

:CONDition?

:ENABle

:SYSTem

:ERRor?
:VERSion?

Common
Commands

Required
and Optional
SCPI
Commands

Query
Commands

The required common commands are IEEE-488.2
mandated commands that are defined in IEEE-

488.2 and must be implemented by all SCPI com­patible instruments. These commands (see table at
left) are identified by the asterisk (*) at the begin­ning of the command keyword. These commands are
used to control instrument status registers, status
reporting, synchronization, and other common func­tions. The common commands and their syntax are
described in detail in Chapter 3, paragraph 3-2.

The required SCPI commands are listed in the table
at left and are described in detail in Chapter 3,
paragraphs 3-11 and 3-12. The optional SCPI com­mands and 693XXB unique commands comprise the
remainder (major portion) of the 693XXB command
set. They control the majority of the programmable
functions of the 693XXB. They are described in de­tail in Chapter 3 starting at paragraph 3-3.

All commands, unless specifically noted in the syn­tax descriptions in Chapter 3, have a query form. As
defined in IEEE-488.2, a query is a command with a
question mark symbol appended (examples: *ESR?,
and :FREQuency:CENTer?). When a query form of a
command is received, the current setting associated
with the command is placed in the output buffer.

2-4 693XXB SCPI PM

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Command
Names

Typical SCPI commands consist of one or more key­words, parameters, and punctuation. SCPI com­mand keywords can be a mixture of upper and lower
case characters. Except for common commands,
each keyword has a long and a short form. In this
manual, the long form is presented with the short
form in upper case and the remainder in lower case.
For example, the long form of the command keyword
to control the instrument display is: DISPlay.

The short form keyword is usually the first four
characters of the long form (example: DISP for
DISPlay). The exception to this is when the long
form is longer than four characters and the fourth
character is a vowel. In such cases, the vowel is
dropped and the short form becomes the first three
characters of the long form. Example: the short form
of the keyword POWer is POW.

Some command keywords may have a numeric
suffix to differentiate between multiple instrument
features such as dual channel inputs. For example:
keywords EXTernal1 and EXTernal2 (or EXT1 and
EXT2) are used to differentiate between the 693XXB
front panel and rear panel MODULATION connec­tors.

As with any programming language, the exact
command keywords and command syntax must be
used. The syntax of the individual commands is
described in detail in Chapter 3. Unrecognized
versions of long form or short form commands, or
improper syntax, will generate an error. Error
reporting is described in Chapter 4.

693XXB SCPI PM 2-5

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Hierarchical
Command
Structure

:ABORt :CONTrol :DIAGnostic :DISPLAY :INITiate

:OUTPut :SOURce :STATus :SYSTem :TRIGger :UNIT

All SCPI commands, except the common commands,
are organized in a hierarchical structure similar to
the inverted tree file structure used in most comput­ers. The SCPI standard refers to this structure as
“the Command Tree.” The command keywords that
correspond to the major instrument control func­tions are located at the top of the command tree.
The command keywords for the 693XXB SCPI com­mand set are shown in the diagram below.

root

All 693XXB SCPI commands, except the ABORt
command, have one or more subcommands (key­words) associated with them to further define the
instrument function to be controlled. The subcom­mand keywords may in turn also have one or more
associated subcommands (keywords). Each subcom­mand level adds another layer to the command tree.
The command keyword and its associated subcom­mand keywords form a portion of the command tree
called a command subsystem. The :CONTrol com­mand subsystem is shown below.

:CONTrol

:BLANking :RAMP :PENLift

:POLarity :REST [:STATe] :TIME :POLarity

An overall command tree for the 693XXB SCPI com­mand set is shown in Figure A-1 of Appendix A.

2-6 693XXB SCPI PM

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Data
Parameters

Data parameters, referred to simply as “parame­ters,” are the quantitative values used as arguments
for the command keywords. The parameter type
associated with a particular SCPI command is
determined by the type of information required to
control the particular instrument function. For
example, Boolean (ON | OFF) type parameters are
used with commands that control switch functions.

The command descriptions in Chapter 3 specify the
type of data parameter to be used with each com­mand. The most commonly used parameter types
are numeric, extended numeric, discrete, and
Boolean.

Numeric

Numeric parameters comprise integer numbers, or
any number in decimal or scientific notation and
may include polarity signs. This includes <NR1>,
<NR2>, and <NR3> numeric data as defined in
Parameter Notations on page 2-9. This type of
numeric element is abbreviated as <NRf> through­out this document.

Extended Numeric

Extended numeric parameters include values such
as MAXimum and MINimum.

Discrete

Discrete parameters, such as INTernal and EXTernal,
are used to control program settings to a predeter­mined finite value or condition.

Boolean

Boolean parameters represent binary conditions and
may be expressed as ON, OFF or 1, 0.

Unit Suffixes Unit suffixes are not required for data parameters,

provided the values are scaled for the global default
units. The 693XXB SCPI default units are: HZ
(Hertz) for frequency related parameters and S (sec­onds) for time related parameters. For example, the
command below sets the 693XXB output frequency
to 3 GHz.

:SOURce:FREQuency:CW 3000000000

The global default units may be changed via use of
the :UNIT Subsystem commands described in Chap­ter 3, paragraph 3-15.

693XXB SCPI PM 2-7

PROGRAMMING WITH NOTATIONAL
SCPI COMMANDS CONVENTIONS

2-3

NOTATIONAL
CONVENTIONS

The SCPI interface standardizes command syntax and style which
simplifies the task of programming across a wide range of instrumen­tation. As with any programming language, the exact command key­words and command syntax must be used. Unrecognized commands,
or improper syntax, will generate an error (refer to Chapter 4 for error
reporting).

General
Notations

The syntax conventions that are used for all SCPI
command keywords and data parameter descrip­tions in this manual are described below.

: A colon links command keywords together to

form commands. The colon is not an actual part
of the keyword but is a signal to the SCPI inter­face parser. A colon must precede a root key­word immediately following a semicolon. (See
Notational Examples on page 2-10.)

; A semicolon separates commands if multiple

commands are placed on a single program line.
(See Notational Examples on page 2-10.)

[] Square brackets enclose one or more optional

parameters.

{} Braces enclose one or more parameters that

may be included one or more times.

| A vertical bar indicates “or” and is used to sepa-

rate alternative parameter options.
Example: ON | OFF is the same as ON or OFF.

<> Angle brackets enclose parameter descriptions.
::= means “is defined as.” For example:

<a>::=<b><c> indicates that <b><c> can
replace <a>.

sp space(s), referred to as whitespace, must be

used to separate keywords from their associ­ated data parameters. It must not be used be­tween keywords, or inside keywords.

XXX indicates a root command name.
For further information about SCPI command syn-

tax and style, refer to the Standard Commands for
Programmable Instruments (SCPI) 1993.0 docu­ment.

2-8 693XXB SCPI PM

PROGRAMMING WITH NOTATIONAL
SCPI COMMANDS CONVENTIONS

Parameter
Notations

The following syntax conventions are used for all
data parameter descriptions in this manual.

<arg> ::=a generic command argument consisting

of one or more of the other data types.

<bNR1> ::=boolean values in <NR1> format;

numeric 1 or 0

<boolean> ::=ON | OFF. Can also be represented as

1 or 0, where 1 means ON and 0 means
OFF. Boolean parameters are always

returned as 1 or 0 in <NR1> format by
query commands.

<integer> ::=an unsigned integer without a decimal

point (implied radix point)

<NR1> ::=a signed integer without a decimal point

(implied radix point).

<NR2> ::=a signed number with an explicit radix

point.

<NR3> ::=a scaled explicit decimal point numeric

value with and exponent (e.g., floating point
number)

<NRf> ::=<NR1>|<NR2>|<NR3>
<nv> ::=SCPI numeric value: <NRf>|MIN|MAX|UP

|DOWN|DEF|NAN|INF|NINF or other types

<char> ::=<CHARACTER PROGRAM DATA>.

Examples: CW, FIXed, UP, and DOWN

<string> ::=<STRING PROGRAM DATA>.

ASCII characters surrounded by double
quotes, example: "OFF”

<block> ::=IEEE-488.2 block data format
<NA> ::=Not Applicable

693XXB SCPI PM 2-9

PROGRAMMING WITH NOTATIONAL
SCPI COMMANDS CONVENTIONS

Notational
Examples

The following is an example showing command syn­tax (It is not an actual command):

[SOURce]:POWer[:LEVel][:IMMediate][:AMPLitude]
:STEP[:INCRement] sp dBm|DOWN|UP

Command statements read from left to right and
from top to bottom. In the command statement
above, the :STEP keyword immediately follows the
:AMPLitude keyword with no separating space.A
space ( sp ) is used between the command string
and its argument (a <nv> type data parameter).

Note that the first keyword in the command string
does not require a leading colon; however, it is good
practice to always use a leading colon for all key­words. Note also that the :SOURce keyword is op­tional. This is a SCPI convention for all voltage or
signal source type instruments that allows shorter
command statements to be used.

The following is an example of a multiple command
statement that uses two seperate commands in a
single statement. Note the semicolon used to join
the commands. (Also note the leading colon used
immediately after the semicolon.)

:FREQuency:STARt 10E6;:FREQuency:STOP 20E9

2-10 693XXB SCPI PM

PROGRAMMING WITH SCPI INTERFACE
SCPI COMMANDS LANGUAGE SELECTION

2-4

SCPI INTERFACE
LANGUAGE SELECTION

The Series 693XXB Synthesized High Performance Signal Generator
can be remotely operated using one of two external interface lan­guages—Native or SCPI. (The Native interface language uses a set of
693XXB GPIB Product Specific commands to control the instrument.)
Before programming with SCPI commands it is necessary to select
SCPI as the external interface language.

Front Panel
Selection

Remote
Selection

SCPI can be selected as the 693XXB interface lan­guage from the front panel Configure GPIB menu.

To access the Configure GPIB Menu, first press the

SYSTEM main menu key on the front panel to

access the System Menu. At the menu display, press

Config to access the System Configuration Menu.
Then, press GPIB . The Configure GPIB Menu is
displayed.

The Configure GPIB menu has an additional menu
display. Language selection is made from this addi­tional menu. To access the additional menu, press

More . At the menu, press SCPI/Native to select
SCPI. The language selection will appear on the dis­play.

SCPI can be selected as the 693XXB interface lan­guage during remote operations.

To change the interface language from Native to
SCPI use the command

SYST:LANG “SCPI”

Do not use the long form of the command and do
not use a leading colon (:) with the command. The

command :SYSTem:LANGuage "SCPI" results in a
syntax error.

NOTE

When the 693XXB signal generator is re­motely operated using the SCPI interface
lanuage, cycling the power returns the in­strument to a reset condition.

693XXB SCPI PM 2-11

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

2-5

STATUS SYSTEM
PROGRAMMING

The 693XXB status system (shown in Figure 2-1) consists of the fol­lowing SCPI-defined status-reporting structures:

The Instrument Summary Status Byte Group

q

The Standard Event Status Group

q

The Operational Status Group

q

The Questionable Status Group

q

The following paragraphs describe the registers that make up a status
group and explain the status information that each status group pro­vides.

Status Group
Registers

In general, a status group consists of a condition
register, a transition filter, an event register, and an
enable register. Each component is briefly described
in the following paragraphs.

Condition Register

The condition register is continuously updated to
reflect the current status of the 693XXB. There is no
latching or buffering for this register, it is updated
in real time. Reading the contents of a condition reg­ister does not change its contents.

Transition Filter

The transition filter is a special register that speci­fies which types of bit state changes in the condition
register will set corresponding bits in the event reg­ister. Negative transition filters (NTR) are used to
detect condition changes from True (1) to False (0);
postive transition filters (PTR) are used to detect
condition changes from False (0) to True (1). Setting
both positive and negative filters True allows an
event to be reported anytime the condition changes.
Transition filters are read-write. Transition filters
are unaffected by queries or *CLS (clear status) and
*RST commands.

The command :STATus:PRESet sets all negative
transition filters to all 0's and sets all positive tran­sition filters to all 1's.

Event Register

The event register latches transition events from
the condition register as specified by the transition
filter. Bits in the event register are latched, and
once set they remain set until cleared by a query or
a *CLS command. Event registers are read only.

2-12 693XXB SCPI PM

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

:STAT:QUES:EVEN?

:STAT:QUES:NTR

:STAT:QUES:PTR

:STAT:QUES:COND?
Not Used
Not Used
Not Used
RF Unleveled
Not Used
Lock Error or RF Unlocked
Not Used
Modulation Range Error
Not Used
SELF TEST FAILED
ANALOG SWEEP LOCK ERROR
XTAL OVEN FAILURE
Not Used
Not Used
Not Used
Not Used (= 0)

:STAT:OPER:COND? NTRPTR

Not Used
Not Used
Not Used
Sweeping
Measuring
Waiting for Trigger
Not Used
Not Used
Not Used
Self Test In Progress
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used (= 0)

CONDition EVENt ENABle

b0
b1
b2
b3
b4
b5
b6
b7
b8

b9
b10
b11
b12
b13
b14
b15

:STAT:OPER:EVEN?

:STAT:OPER:NTR

:STAT:OPER:PTR

CONDition EVENt ENABle

b0

b1

b2

b3

b4

b5

b6

b7

b8

b9
b10
b11
b12
b13
b14
b15

QUESTIONABLE STATUS

b0
b1
b2
b3
b4
b5
b6
b7
b8

b9
b10
b11
b12
b13
b14
b15

OPERATIONAL STATUS

b0
b1
b2
b3
b4
b5
b6
b7
b8

b9
b10
b11
b12
b13
b14
b15

:STAT:QUES:ENAB?

NTRPTR

b0

b0

b1

b1

b2

b2

b3

b3

b4

b4

b5

b5

b6

b6

b7

b7

b8

b8

b9

b9

b10

b10

b11

b11

b12

b12

b13

b13

b14

b14

b15

b15

*CLS

:STAT:OPER:ENAB?

b0

b0

b1

b1

b2

b2

b3

b3

b4

b4

b5

b5

b6

b6

b7

b7

b8

b8

b9

b9

b10

b10

b11

b11

b12

b12

b13

b13

b14

b14

b15

b15

Error Queue

b0
b1
b2
b3
b4
b5
b6

&

&

b7
b8

b9
b10
b11
b12
b13
b14
b15

b0-b15

b0

b1

b2

b3

b4

b5

b6

b7

b8

b9
b10
b11
b12
b13
b14
b15

b0-b15

QUESTIONABLE

EVENT

Operation Complete (OP)
Not Used
Query Error
Device Dependent Error
Execution Error
Command Error
Not Used
Not Used

OPERATIONAL

EVENT

STANDARD EVENT STATUS

*ESR?

EVENt

b0
b1
b2
b3
b4
b5
b6
b7

*CLS

*ESE n
*ESE?

&

ENABle

b0
b1
b2
b3
b4
b5
b6
b7

b0-b7

STANDARD

EVENT

Error Code/Error Description

Mssg Available (MAV)

Master Summary Status (MSS/RQS)

NOTE: Not Used bits are always cleared to 0.

Error Queue
not empty

INSTRUMENT SUMMARY

*STB?

Summary

STATUS BYTE
Not Used
Not Used

ERRQ
QUEST

MAV
STD

OPER

b0
b1
b2
b3
b4
b5
b6
b7

STATUS BYTE

b0
b1
b2
b3
b4
b5
b6
b7

*CLS

b0-b7

Bit Weight

1
2
4

8
16
32
64

128

*SRE n
*SRE?

*CLS

Summary

ENABle

b0
b1
b2

b8

b9
b10
b11
b12
b13
b14
b15

b3
b4
b5
b6
b7

256

512
1024
2048
4096
8192

16384
32768

&

Figure 2-1. 693XXB Status-Reporting Structure

693XXB SCPI PM 2-13

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Enable Register

The enable register specifies the bits in the event
register that can produce a summary bit. The
693XXB logically ANDs corresponding bits in the
event and enable registers, and ORs all the result­ing bits to obtain a summary bit. Summary bits are
recorded in the Summary Status Byte. Enable regis­ters are read-write. Querying an enable register
does not affect it.

The command :STATus:PRESet sets the Operational
Status Enable register and the Questionable Status
Enable register to all 0's.

Status Group
Reporting

The state of certain 693XXB hardware and opera­tional events and conditions can be determined by
programming the status system. As shown in Figure
2-1, the three lower status groups provide status in­formation to the Summary Status Byte group. The
Summary Status Byte group is used to determine
the general nature of an event or condition and the
other status groups are used to determine the spe­cific nature of the event or condition.

NOTE

Programming commands for the status sys­tem, including examples of command usage,
can be found in Chapter 3.

The following paragraphs explain the information
that is provided by each status group.

2-14 693XXB SCPI PM

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Summary Status Byte Group

The Summary Status Byte group, consisting of the
Summary Status Byte Enable register and the Sum­mary Status Byte, is used to determine the general
nature of a 693XXB event or condition. The bits in
the Summary Status Byte provide the following in­formation:

Bit Description

0,1 Not Used. These bits are always set to 0.

2 Set to indicate the Error Queue contains data. The

Error Query command can then be used to read
the error message(s) from the queue.

3 Set to indicate the Questionable Status summary

bit has been set. The Questionable Status Event
register can then be read to determine the specific
condition that caused the bit to be set.

4 Set to indicate that the 693XXB has data ready in

its output queue.

5 Set to indicate that the Standard Event Status

summary bit has been set. The Standard Event
Status register can then be read to determine the
specific event that caused the bit to be set.

6 Set to indicate that the 693XXB has at least one

reason to require service. This bit is also called
the Master Summary Status Bit (MSS). The indi­vidual bits in the Status Byte are ANDed with their
corresponding Service Request Enable Register
bits, then each bit value is ORed and input to this
bit.

7 Set to indicate that the Operational Status sum-

mary bit has been set. The Operational Status
Event register can then be read to determine the
specific condition that caused the bit to be set.

693XXB SCPI PM 2-15

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Standard Event Status Group

The Standard Event Status group, consisting of the
Standard Event Status register (an Event register)
and the Standard Event Status Enable register, is
used to determine the specific event that set bit 5 of
the Summary Status Byte. The bits in the Standard
Event Status register provide the following informa­tion:

Bit Description

0 Set to indicate that all pending 693XXB operations

were completed following execution of the “∗OPC”
command.

1 Not Used. The bit is always set to 0.

2 Set to indicate that a query error has occurred.

Query errors have SCPI error codes from –499 to
–400.

3 Set to indicate that a device-dependent error has

occurred. Device-dependent errors have SCPI
error codes from –399 to –300 and 1 to 32767.

4 Set to indicate that a execution error has occurred.

Execution errors have SCPI error codes from
–299 to –200.

5 Set to indicate that a command error has occurred.

Command errors have SCPI error codes from
–199 to –100.

6,7 Not Used. The bits are always set to 0.

2-16 693XXB SCPI PM

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Operational Status Group

The Operational Status group, consisting of the Op­erational Condition register, the Operational Posi­tive Transition register, the Operational Negative
Transition register, the Operational Event register,
and the Operational Event Enable register, is used
to determine the specific condition that set bit 7 in
the Summary Status Byte. The bits in the Opera­tional Event register provide the following informa­tion:

Bit Description

0-2 Not Used. The bits are always set to 0.

3 Set to indicate that a sweep is in progress.

4 Set to indicate that the 693XXB is measuring.

5 Set to indicate that the 693XXB is in an armed

“wait for trigger” state.

6 Not Used. The bit is always set to 0.

7 Not Used. The bit is always set to 0.

8 Not Used. The bit is always set to 0.

9 Set to indicate that 693XXB self-test is in prog-

ress.

10-14 Not Used. The bits are always set to 0.

*15 Always 0. The use of Bit 15 is not allowed by

SCPI.

693XXB SCPI PM 2-17

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Questionable Status Group

The Questionable Status group, consisting of the
Questionable Condition register, the Questionable
Positive Transition register, the Questionable Nega­tive Transition register, the Questionable Event reg­ister, and the Questionable Event Enable register, is
used to determine the specific condition that set bit
3 in the Summary Status Byte. The bits in the
Questionable Event register provide the following
information:

Bit Description

0-2 Not Used. The bits are always set to 0.

3 Set to indicate an RF unleveled condition.

4 Not Used. The bit is always set to 0.

5 Set to indicate a phase-lock error or RF unlocked

condition.

6 Not Used. The bit is always set to 0.

7 Set to indicate a modulation range error.

8 Not Used. The bit is always set to 0.

9 Set to indicate that self-test failed.

10 Set to indicate an analog sweep phase-lock error.

11 Set to indicate a failure of the crystal oven.

12-14 Not Used. The bits are always set to 0.

*15 Always 0. The use of Bit 15 is not allowed by

SCPI.

2-18 693XXB SCPI PM

PROGRAMMING WITH TRIGGER SYSTEM
SCPI COMMANDS PROGRAMMING

2-6

TRIGGER SYSTEM
PROGRAMMING

The 693XXB trigger system is used to synchronize signal generator
actions with software trigger commands. The 693XXB follows the lay­ered trigger model used in SCPI instruments. The following para­graphs describe operation and programming of the signal generator
trigger system. The structure and components of the 693XXB trigger
model are shown in Figure 2-2.

:INIT:CONT OFF

:INIT:CONT OFF

:INIT:CONT ON

IMMediate

BUS

*RST or :ABORt

:INIT[:IMM] or

:INIT:CONT ON

:TRIG [:SEQ][:IMM]

:TRIG[:SEQ]:

SOURce?

IDLE

INITIATE

(ARMED)

TRIGGER

EVENT

DETECTION

SWEEP GENERATION

(Frequency, Power,

Stepped, Analog)

Figure 2-2. 693XXB TriggerModel

Trigger
System
Operation

Turning power on, or sending *RSTor :ABORt forces
the trigger system into the idle state. The trigger
system remains in the idle state until it is initiated.
Trigger system initiation can happen on a continu­ous basis (:INITiate:CONTinuous ON) or on a demand
basis (:INITiate:CONTinuous OFF). When the com­mand :INITiate:CONTinuous is set to OFF, the trigger
system is initiated by the :INITiate[:IMMediate] com­mand. Note that *RST sets :INITiate:CONTinuous to
OFF.

693XXB SCPI PM 2-19

PROGRAMMING WITH TRIGGER SYSTEM
SCPI COMMANDS PROGRAMMING

Once initiated, the trigger system enters an armed
(wait for trigger) state. The trigger signal selected
by the command :TRIGger[:SEQuence]:SOURce is
examined until a TRUE condition is detected. The
trigger signal selections are:

IMMediate the trigger signal is always TRUE.
BUS the trigger signal is either the GPIB

<GET> (Group Execute Trigger)

message or the *TRG command.

HOLD the trigger signal is never TRUE.

When a TRUE condition is detected, sweep genera­tion of the selected sweep starts.

The command :TRIGger[:SEQuence][:IMMediate] pro­vides a one-time override of the normal downward
path in the trigger-event-detection state by forcing a
TRUE trigger signal regardless of the setting for
:TRIGger[:SEQuence]:SOURce.

Upon sweep completion, if :INITiate:CONTinuous is
set OFF, the trigger system returns to the idle state.
If :INITiate:CONTinuous is set to ON, the trigger sys­tem returns to the armed (wait for trigger) state.

Auto Trigger Mode

Setting the command :INITiate:CONTinuous to ON
and the command :TRIGger[:SEQuence]:SOURce to
IMMediate, places the trigger system in an auto
trigger mode. This causes continuous generation of
the selected sweep.

ABORt

The :ABORt command resets any sweep in progress
and immediately returns the trigger system to the
idle state. Unlike *RST, :ABORt does not change the
settings programmed by other commands.

2-20 693XXB SCPI PM

Chapter 3
Programming
Commands

Table of Contents

3-1 INTRODUCTION ...................3-7

3-2 COMMON COMMANDS ...............3-7

*CLS (Clear Status Command)..........3-7

*ESE (Standard Event Status Enable Command). 3-7
*ESE? (Standard Event Status Enable Query) . . 3-7
*ESR? (Standard Event Status Register Query) . 3-7

*IDN? (Identification Query) ...........3-8

*OPC (Operation Complete Command) ......3-8

*OPC? (Operation Complete Query) .......3-8

*RST (Reset Command) .............3-8

*SRE (Service Request Enable Command) ....3-8

*SRE? (Service Request Enable Query)......3-8

*STB? (Read Status Byte Query).........3-9

*TST? (Self-Test Query) .............3-9

*WAI (Wait-to-Continue Command)........3-9

*OPT? (Option Identify) .............3-9

*RCL (Recall Stored State) ............3-9

*SAV (Save Current State)............3-9

*TRG (Trigger Command)............3-10

3-3 SUBSYSTEM COMMANDS.............3-10

3-4 ABORt COMMAND (SUBSYSTEM) ........3-11

Table of Contents (Continued)

3-5 CONTROL SUBSYSTEM ..............3-12

:CONTrol:BLANking:POLarity .........3-12

:CONTrol:PENLift:POLarity ..........3-13

:CONTrol:RAMP:REST .............3-14

:CONTrol:RAMP[:STATe] ............3-15

:CONTrol:RAMP:TIME .............3-16

3-6 DIAGNOSTIC SUBSYSTEM ............3-17

:DIAGnostic:SNUM? ..............3-17

3-7 DISPLAY SUBSYSTEM ...............3-18

:DISPlay[:WINDow]:TEXT:STATe ........3-18

3-8 INITIATE SUBSYSTEM ..............3-19

:INITiate[:IMMediate] .............3-19

:INITiate:CONTinuous .............3-20

3-9 OUTPUT SUBSYSTEM ...............3-21

:OUTPut[:STATe] ................3-21

:OUTPut:PROTection ..............3-22

:OUTPut:PROTection:RETRace .........3-23

:OUTPut:IMPedance?..............3-24

3-10 SOURCE SUBSYSTEM ...............3-25

[:SOURce]:AM:LOGSens ............3-29

[:SOURce]:AM:SENSitivity ...........3-30

[:SOURce]:AM:LOGDepth............3-31

[:SOURce]:AM:INTernal:WAVE .........3-32

[:SOURce]:AM:INTernal:FREQuency ......3-33

[:SOURce]:AM:DEPTh .............3-34

[:SOURce]:AM:EXTernal:IMPedance ......3-35

[:SOURce]:AM:SOURce .............3-36

[:SOURce]:AM:STATe ..............3-37

[:SOURce]:AM:TYPE ..............3-38

[:SOURce]:CORRection[:STATe] .........3-39

[:SOURce]:CORRection:CSET:SELect ......3-40

[:SOURce]:FM:INTernal:WAVE .........3-41

[:SOURce]:FM:INTernal:FREQuency ......3-42

[:SOURce]:FM:DEViation ............3-43

[:SOURce]:FM:MODE..............3-44

3-2 693XXB SCPI PM

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

[:SOURce]:FM:BWIDth .............3-45

[:SOURce]:FM:EXTernal:IMPedance ......3-46

[:SOURce]:FM:SENSitivity ...........3-47

[:SOURce]:FM:SOURce .............3-48

[:SOURce]:FM:STATe ..............3-49

[:SOURce]:FREQuency[:CW |:FIXed] ......3-50

[:SOURce]:FREQuency[:CW |:FIXed]

:STEP[:INCRement] .............3-52

[:SOURce]:FREQuency:CENTer .........3-53

[:SOURce]:FREQuency:MODE .........3-54

[:SOURce]:FREQuency:SPAN ..........3-55

[:SOURce]:FREQuency:SPAN:FULL.......3-56

[:SOURce]:FREQuency:SPAN2 .........3-57

[:SOURce]:FREQuency:SPAN2:FULL ......3-58

[:SOURce]:FREQuency:STARt .........3-59

[:SOURce]:FREQuency:STARt2 .........3-60

[:SOURce]:FREQuency:STOP ..........3-61

[:SOURce]:FREQuency:STOP2 .........3-62

[:SOURce]:FREQuency:MULTiplier .......3-63

[:SOURce]:LIST<n>:INDex ...........3-64

[:SOURce]:LIST<n>:FREQuency ........3-65

[:SOURce]:LIST<n>:FREQuency:POINts? ....3-66

[:SOURce]:LIST<n>:POWer...........3-67

[:SOURce]:LIST<n>:POWer:POINts? ......3-68

[:SOURce]:LIST<n>:DWELl...........3-69

[:SOURce]:LIST<n>:STARt ...........3-70

[:SOURce]:LIST<n>:STOP ...........3-71

[:SOURce]:LIST<n>:CALCulate.........3-72

[:SOURce]:MARKer<n>:AOFF .........3-73

[:SOURce]:MARKer<n>:FREQuency ......3-74

[:SOURce]:MARKer<n>:STATe .........3-75

[:SOURce]:MARKer<n>:INTensity........3-76

[:SOURce]:MARKer<n>:VIDeo .........3-77

[:SOURce]:MARKer<n>:POLarity ........3-78

[:SOURce]:PM:BWIDth .............3-79

[:SOURce]:PM:DEViation ............3-80

[:SOURce]:PM:INTernal:WAVE .........3-81

[:SOURce]:PM:INTernal:FREQuency ......3-82

693XXB SCPI PM 3-3

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

[:SOURce]:PM:EXTernal:IMPedance ......3-83

[:SOURce]:PM:SENSitivity ...........3-84

[:SOURce]:PM:SOURce .............3-85

[:SOURce]:PM:STATe ..............3-86

[:SOURce]:POWer[:LEVel][:IMMediate]

[:AMPLitude].................3-87

[:SOURce]:POWer[:LEVel][:IMMediate]

[:AMPLitude]:STEP[:INCRement].......3-89

[:SOURce]:POWer[:LEVel]:ALTernate ......3-90

[:SOURce]:POWer:ALC:SOURce.........3-91

[:SOURce]:POWer:ATTenuation .........3-92

[:SOURce]:POWer:ATTenuation:STEP

[:INCRement] ................3-93

[:SOURce]:POWer:ATTenuation:AUTO .....3-94

[:SOURce]:POWer:DISPlay:OFFSet .......3-95

[:SOURce]:POWer:DISPlay:OFFSet:STATe . . . 3-96

[:SOURce]:POWer:SLOPe............3-97

[:SOURce]:POWer:SLOPe:STEP[:INCRement]. . 3-98

[:SOURce]:POWer:SLOPe:STATe ........3-99

[:SOURce]:POWer:SLOPe:PIVot ........3-100

[:SOURce]:POWer:MODE ...........3-101

[:SOURce]:POWer:CENTer...........3-102

[:SOURce]:POWer:SPAN............3-103

[:SOURce]:POWer:SPAN:FULL ........3-104

[:SOURce]:POWer:STARt ...........3-105

[:SOURce]:POWer:STOP............3-106

[:SOURce]:PULM:INTernal:FREQuency ....3-107

[:SOURce]:PULM:POLarity ..........3-108

[:SOURce]:PULM:SOURce...........3-109

[:SOURce]:PULM:STATe ............3-110

[:SOURce]:PULSe:COUNt ...........3-111

[:SOURce]:PULSe:DELay<n> .........3-112

[:SOURce]:PULSe:PERiod ...........3-113

[:SOURce]:PULSe:WIDTh<n> .........3-114

[:SOURce]:PULSe:STEP ............3-115

[:SOURce]:PULSe:STEP:STARt ........3-116

[:SOURce]:PULSe:STEP:STOP.........3-117

[:SOURce]:PULSe:STEP:INCRement......3-118

3-4 693XXB SCPI PM

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

[:SOURce]:PULSe:STEP:TIME.........3-119

[:SOURce]:SWEep<n>:DIRection........3-120

[:SOURce]:SWEep<n>:DWELl .........3-121

[:SOURce]:SWEep<n>:DWELl:AUTO .....3-123

[:SOURce]:SWEep<n>:GENeration.......3-125

[:SOURce]:SWEep<n>:POINts .........3-126

[:SOURce]:SWEep<n>[:FREQuency]:STEP . . . 3-127

[:SOURce]:SWEep<n>:POWer:STEP ......3-128

[:SOURce]:SWEep<n>:SPACing ........3-129

[:SOURce]:SWEep<n>:TIME..........3-130

[:SOURce]:SWEep<n>:TIME:LLIMit ......3-131

[:SOURce]:SWEep<n>:TIME:AUTO ......3-132

3-11 STATUS SUBSYSTEM...............3-133

:STATus:OPERation[:EVENt]? .........3-133

:STATus:OPERation:CONDition?........3-134

:STATus:OPERation:ENABle..........3-135

:STATus:OPERation:PTRansition .......3-136

:STATus:OPERation:NTRansition .......3-137

:STATus:PRESet................3-138

:STATus:QUEStionable[:EVENt]? .......3-139

:STATus:QUEStionable:CONDition? ......3-140

:STATus:QUEStionable:ENABle ........3-141

:STATus:QUEStionable:PTRansition ......3-142

:STATus:QUEStionable:NTRansition ......3-143

:STATus:QUEue[:NEXT]? ...........3-144

3-12 SYSTEM SUBSYSTEM ..............3-145

:SYSTem:ERRor? ...............3-145

:SYSTem:LANGuage..............3-146

:SYSTem:PRESet ...............3-147

:SYSTem:VERSion? ..............3-148

3-13 TRIGGER SUBSYSTEM..............3-149

:TRIGger[:SEQuence |:STARt][:IMMediate] . . 3-149

:TRIGger[:SEQuence |:STARt]:SOURce ....3-150

:TRIGger:SEQuence3:SLOPe..........3-151

:TRIGger:SEQuence3:TYPE ..........3-152

:TRIGger:SEQuence3:SOURce .........3-153

693XXB SCPI PM 3-5

Table of Contents (Continued)

3-14 TSWeep COMMAND ................3-154

3-15 UNIT SUBSYSTEM ................3-155

:UNIT:FREQuency ..............3-155

:UNIT:TIME .................3-156

3-6 693XXB SCPI PM

Chapter 3
Programming
Commands

3-1

3-2

INTRODUCTION

COMMON COMMANDS

This chapter contains information on all SCPI programming com­mands accepted and implemented by the Series 693XXB Synthesized
High Performance Signal Generator.

Common commands are used to control instrument status registers,
status reporting, synchronization, data storage, and other common
functions. All common commands are identified by the leading aster­isk in the command word. The common commands are fully defined in
IEEE 488.2.

IEEE 488.2
Mandated
Commands

The 693XXB implements the following IEEE-488.2
mandated common commands.

*CLS (Clear Status Command)

Clear the Status Byte, the Data Questionable Event
Register, the Standard Event Status Register, the
Standard Operation Status Register, the error
queue, the OPC pending flag, and any other regis­ters that are summarized in the Status Byte.

*ESE sp <nv> (Standard Event Status Enable
Command)

Sets the Standard Event Status Enable Register
bits. The binary weighted <NR1> data parameter
used with this command must have a value between
0 to 255. Refer to “Status System Programming” in
Chapter 2.

*ESE? (Standard Event Status Enable Query) ?

Returns the value of the Standard Event Status En­able Register in <NR1> format. Refer to “Status Sys­tem Programming” in Chapter 2.

*ESR? (Standard Event Status Register Query)

Returns the value of the Standard Event Status
Register in <NR1> format. This command clears the
Standard Event Status Register. Refer to “Status
System Programming” in Chapter 2.

693XXB SCPI PM 3-7

PROGRAMMING COMMON
COMMANDS COMMANDS

*IDN? (Identification Query)

This query returns an instrument identification
string in IEEE- 488.2 specified <NR1> format (four
fields separated by commas). The fields are: <Manu-

facturer>, <Model>, <Serial #>, <Firmware revision
level>; where the actual model number, serial

number, and firmware version of the 693XXB que­ried will be passed.

*OPC (Operation Complete Command)

Enables the Operation Complete bit in the Standard
Event Status Register after all pending operations
are complete.

*OPC? (Operation Complete Query)

Places an ASCII “1” in the Output Queue and sets
the MAV bit true in the Status Byte when all pend­ing operations are completed (per IEEE-488.2 sec­tion 12.5.3). Message is returned in <NR1> format.

*RST (Reset Command)

Resets the 693XXB to a pre-defined condition with
all user programmable parameters set to their de­fault values. These default parameter values are
listed under each SCPI command in this manual.
This command does not affect the Output Queue,
Status Byte Register, Standard Event Register, or
calibration data.

NOTE

This command clears the current front panel
setup. If this setup is needed for future test-

ing, save it as a stored setup using the *SAV
command before issuing the *RST com­mand.

*SRE sp <nv> (Service Request Enable Com-
mand)

Sets the Service Request Enable Resister bits. The
integer data parameter used with this command
must have a value between 0 to 255. A zero value re­sets the register. Refer to “Status System Program­ming” in Chapter 2.

*SRE*? (Service Request Enable Query)

Returns the value of the Service Request Enable
Register in <NR1> format. Bit 6 is always zero.

3-8 693XXB SCPI PM

PROGRAMMING COMMON
COMMANDS COMMANDS

*STB? (Read Status Byte Query)

Returns the content of the Status Byte Register
(bits 0–5 and 7). Bit 6 is the Master Summary
Status bit value. This command does not reset the
status byte values.

*TST? (Self-Test Query)

CAUTION

693XXB self-test requires RF
output power to be on. Always
disconnect sensitive equipment
from the unit before performing
a self-test.

Causes the 693XXB to perform a full internal self­test. Status messages which indicate self-test re­sults are placed in the error queue in the order they
occur. Bits in the status register are also affected.

Returns the number of errors placed in the error
queue. 0 means the unit passed self-test.

*WAI (Wait-to-Continue Command)

This command suspends the execution of any fur­ther commands or queries until all operations for
pending commands are completed. For example, the
command *TRG;*WAI permits synchronous sweep
operation. It causes the 693XXB to start a sweep
and wait until the sweep is complete before execut­ing the next command.

Optional
Common
Commands

The 693XXB implements the following IEEE 488.2
optional common commands:

*OPT? (Option Identification Query)

This command returns a string identifying any
device options.

*RCL sp <n> (Recall Stored State)

This command restores the 693XXB to a front panel
setup state that was previously saved to local (in­strument) memory using the *SAV command (be­low). The *RCL sp <n> command restores setup
<n>, where n shall be in the range of 0 to 9.

*SAV sp <n> (Save Current State)

Saves the current front panel setup parameters in
local (instrument) memory. The new stored setup
state will be assigned the Setup Number specified
by <n>, where n shall be in the range of 0 to 9.

693XXB SCPI PM 3-9

PROGRAMMING SUBSYSTEM
COMMANDS COMMANDS

*TRG (Trigger Command)

Triggers instrument if :TRIGger:SOURce command
data parameter is BUS. Refer to INITiate and TRIG-
ger subsystem commands.)

Performs the same function as the Group Execute
Trigger <GET> command defined in IEEE 488.1.

3-3

SUBSYSTEM
COMMANDS

Subsystem commands control all signal generator functions and some
general purpose functions. All subsystem commands are identified by
the colon used between keywords, as in :INITiate:CONTinuous.

The following information is provided for each subsystem command.

The path from the subsystem root command.

q

The data parameters used as arguments for the command. This

q

includes the parameter type, the available parameter choices, the
range for numeric parameters, and the default parameter that is
set by the *RST command.

q A description of the purpose of the command.
q The query form of the command (if applicable).
q An example of the use of the command.
q Where necessary, notes are included to provide additional infor-

mation about the command and its usage.

An overall command tree for the 693XXB SCPI command set is shown
in Figure A-1 of Appendix A.

3-10 693XXB SCPI PM

PROGRAMMING :ABORt SUBSYSTEM
COMMANDS :ABORt

3-4

ABORT COMMAND
(SUBSYSTEM)

The :ABORt command is a single command subsystem. There are no
subcommands or associated data parameters, as shown below. The
:ABORt command, along with the :TRIGger and :INITiate commands,
comprise the “Trigger Group” of commands.

:ABORt

Parameters: None

Description: Forces the trigger system to the idle state. Any sweep

in progress is aborted as soon as possible.

Query Form: None

Example: :ABORt

Sets 693XXB trigger system to idle state.

Associated
commands: :TRIGger and :INITiate

693XXB SCPI PM 3-11

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :BLANking:POLarity

3-5

CONTROL SUBSYSTEM

The :CONTrol subsystem sets the state of the following rear panel con­trol outputs; RETRACE BLANK OUT, PENLIFT OUT, and HORIZ OUT.
The subsystem commands and parameters are described below.

KEYWORD PARAMETER FORM NOTES

:CONTrol

:BLANking

:POLarity NORMal|INVerted Default: NORmal

:PENLift

:POLarity NORMal|INVerted Default: NORmal

:RAMP

:REST
[:STATe]
:TIME

STARt|STOP
<boolean>
<numeric_value>

Default: STOP
Default: OFF
Default: 30 ms

:CONTrol

:BLANking

:POLarity

Parameters: NORMal | INVerted

Type: <char>

Default: NORMal

Description: Sets the level of the retrace blanking signal output

(rear panel AUX I/O connector, pin 6) during sweep
retrace as follows:

NORMal cause the blanking signal to be a +5V level.
INVerted causes the blanking signal to be a –5V level.

Query Form :CONTrol:BLANking:POLarity?

Examples: :CONTrol:BLANking:POLarity sp INVerted

Set a –5V level for the rear panel blanking signal out­put during sweep retrace.

:CONTrol:BLANking:POLarity?

Requests the currently programmed level for the rear
panel blanking signal output during sweep retrace.

3-12 693XXB SCPI PM

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :PENLift:POLarity

:CONTrol

:PENLift

:POLarity

Parameters: NORMal | INVerted

Type: <char>

Default: NORMal

Description: Sets the internal penlift relay contacts to control the

state of the penlift relay output (optionally available
at the rear panel) as follows:

NORMal sets the relay contacts to be normally open.
INVerted sets the relay contacts to be normally closed.

Query Form: :CONTrol:PENLift:POLarity?

Examples: :CONTrol:PENLift:POLarity sp INVerted

Set the penlift relay contacts to be normally closed.

:CONTrol:PENLift:POLarity?

Requests the currently programmed state of the penlift
relay contacts.

693XXB SCPI PM 3-13

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :RAMP:REST

:CONTrol

:RAMP

:REST

Parameters: STARt | STOP

Type: <char>

Default: STOP

Description: Sets the sweep rest point for the rear panel HORIZ

OUT sweep ramp as follows:
STARt sets the sweep to rest at the bottom of the

sweep ramp.
STOP sets the sweep to rest at the top of the sweep
ramp.

Query Form: :CONTrol:RAMP:REST?

Examples: :CONTrol:RAMP:REST sp STOP

Set the sweep to rest at the top of the sweep ramp.

:CONTrol:RAMP:REST?

Requests the currently programmed rest point for the
sweep ramp.

3-14 693XXB SCPI PM

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :RAMP[:STATe]

:CONTrol

:RAMP

[ :STATe]

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: Turns the rear panel HORIZ OUTsweep ramp signal

on/off.

Query Form: :CONTrol:RAMP[:STATe]?

Examples: :CONTrol:RAMP:STATe sp ON

Turns the rear panel HORIZ OUTsweep ramp signal
on.

:CONTrol:RAMP:STATe?
Requests the currently programmed state of the HORIZ

OUT sweep ramp signal.

693XXB SCPI PM 3-15

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :RAMP:TIME

:CONTrol

:RAMP

:TIME

Parameters: sweep time (in seconds) | MIN | MAX

Type: <nv>

Range: 30 ms to 99 sec

Default: 30 ms

Description: Sets the rear panel HORIZ OUT sweep ramp signal

time by changing the analog sweep time.
[:SOURce]:SWEep:TIME will also be changed.
May not be changed while the unit is sweeping.

Query Form: :CONTrol:RAMP:TIME?

Examples: :CONTrol:RAMP:TIME sp 100 ms

Sets the rear panel HORIZ OUT sweep ramp signal
time to 100 ms.

:CONTrol:RAMP:TIME?

Requests the currently programmed time for the
HORIZ OUT sweep ramp signal.

3-16 693XXB SCPI PM

PROGRAMMING :DIAGnostic SUBSYSTEM
COMMANDS :SNUM?

3-6

DIAGNOSTIC
SUBSYSTEM

The :DIAGnostic subsystem consists of the query command described
below.

KEYWORD

:DIAGnostic

:SNUM?

:DIAGnostic

:SNUM?

Description: Allows the serial number of the instrument to be read.

Query Form :DIAGnostic:SNUM?

693XXB SCPI PM 3-17

PROGRAMMING :DISPlay SUBSYSTEM
COMMANDS :WINDow:TEXT:STATE

3-7

DISPLAY SUBSYSTEM

The :DISPlay subsystem controls the display of all frequency, power
level, and modulation parameters on the front panel data display.

KEYWORD PARAMETER FORM NOTES

:DISPlay

[:WINDow]

:TEXT

:STATe <boolean> Default ON

:DISPlay

[:WINDow]

:TEXT

: STATe

Parameters: ON|OFF|1|0

Type: <boolean>

Default: ON

Description: Turns the display of the frequency, power level, and

modulation parameters on the front panel data dis­play on/off.

Query Form :DISPlay:TEXT:STATe?

Example: :DISPlay:TEXT:STATe sp OFF

Turns off the display of the frequency, power level, and
modulation parameters on the 693XXB front panel
data display (Secure mode of operation).

3-18 693XXB SCPI PM

PROGRAMMING :INITiate SUBSYSTEM
COMMANDS [:IMMediate]

3-8

INITIATE SUBSYSTEM

The :INITiate subsystem controls the state of the 693XXB trigger sys­tem. The subsystem commands and parameters are described below.
The :INITiate commands, along with the :ABORt and :TRIGger com­mands, comprise the Trigger Group of commands.

KEYWORD PARAMETER FORM NOTES

:INITiate

[:IMMediate] (none)
:CONTinuous <boolean> Default: OFF

:INITiate

[:IMMediate]

Parameters: none

Description: Places the 693XXB trigger system into the armed

state from the idle state. If trigger system is not in
idle state, or if :INITiate:CONTinuous is ON, will pro­duce error –213.

Query Form: None

Example: :INITiate:IMMediate

Sets 693XXB trigger to the armed state.

Associated
commands: :ABORt and :TRIGger

NOTES:
When :INITiate or :TSWeep is received by the 693XXB, all sweep-

related parameters are checked for compatibility and bounds. The sys­tem will not arm is any errors exist. These errors are reported in the
error queue.

693XXB SCPI PM 3-19

PROGRAMMING :INITiate SUBSYSTEM
COMMANDS :CONTinuous

:INITiate

:CONTinuous

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: Continuously rearms the 693XXB trigger system after

completion of a triggered sweep.

Query Form: :INITiate:CONTinuous?

Examples: :INITiate:CONTinuous sp ON

Sets 693XXB trigger to continuously armed state.

Associated
commands: :ABORt and :TRIGger

NOTE:
:INITiate:CONTinuous ON has the same action as :INITiate:IMMediate

plus it sets an internal flag that causes the trigger system to rearm af­ter completing a triggered action.

If :TRIGger:SOURce IMMediate, :INITiate will start a sweep if one is not
already in progress. In this case, to abort and restart a sweep either
send :ABORt;:INITiate or :TSWeep .

If the trigger system is not idle, :INITiate will cause the error:

–213, "Init ignored, trigger not idle”

3-20 693XXB SCPI PM

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS [:STATe]

3-9

OUTPUT SUBSYSTEM

The :OUTPut subsystem controls the 693XXB RF output power. The
commands are used to turn the RF output power on/off and to set the
state of the RF output power during frequency changes in CW and
step sweep modes and during sweep retrace. The subsystem com­mands and parameters are described below.

KEYWORD PARAMETER FORM NOTES

:OUTPut

[:STATe] <boolean> Default: OFF
:PROTection <boolean> Default: ON

:RETRace <boolean> Default: OFF

:IMPedance?

:OUTPut

[ :STATe]

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF (see notes below)

Description: Turns 693XXB RF output power on/off.

Query Form :OUTPut[:STATe]?

Example: :OUTPut:STATe sp ON

Turns 693XXB RF output power on.

NOTES:
The SCPI programming mode reset default for RF output power state

is OFF.
The 693XXB Native GPIB programming mode reset default for the RF

output power state is ON.

693XXB SCPI PM 3-21

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :PROTection

:OUTPut

:PROTection

Parameters: ON|OFF|1|0

Type: <boolean>

Default: ON

Description: ON causes the 693XXB RF output to be turned off

(blanked) during frequency changes in CW or step
sweep mode. OFF leaves RF output turned on (un­blanked).

Query Form :OUTPut:PROTection?

Example: :OUTPut:PROTection sp OFF

Causes the 693XXB RF output signal to be left on dur­ing frequency changes in CW or step sweep mode.

:OUTPut:PROTection?

Requests the currently programmed state of the
693XXB RF output during frequency changes in CW or
step sweep mode.

3-22 693XXB SCPI PM

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :PROTection:RETRace

:OUTPut

:PROTection

:RETRace

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: ON causes the 693XXB RF output to be turned off

during sweep retrace. OFF leaves RF output turned
on.

Query Form :OUTPut:PROTection:RETRace?

Example: :OUTPut:PROTection:RETRace sp ON

Turns the 693XXB RF output off during sweep retrace.

:OUTPut:PROTection:RETRace?

Requests the currently programmed state of the
693XXB RF output during sweep retrace.

693XXB SCPI PM 3-23

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :IMPedance?

:OUTPut

:IMPedance?

Description: Queries the 693XXB RF output impedance. The im-

pedance is nominally 50 ohms and is not settable.

Query Form :OUTPut:IMPedance?

3-24 693XXB SCPI PM

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

3-10

SOURCE SUBSYSTEM

:SOURce Subsystem Commands (1 of 4)

KEYWORD PARAMETER FORM NOTES

[:SOURce]

:AM

:LOGSens
:SENSitivity
:LOGDepth
:INTernal

:WAVE

:FREQuency
:DEPTh
:EXTernal

:IMPedance
:SOURce
:STATe
:TYPE

:CORRection

[:STATe]
:CSET

:SELect

:FM

:INTernal

:WAVE

:FREQuency
:DEViation
:MODE
:BWIDth
:EXTernal

:IMPedance
:SENSitivity
:SOURce
:STATe

The [:SOURce] subsystem provides control of a majority of the
693XXB functions. The subsystem commands are used to control the
frequency, power level, and modulation of the RF output signal. The
[:SOURce] subsystem commands and parameters are listed in the ta­ble contained on this and the following three pages. The subsytem
commands are described in detail on following pages.

Note that the [:SOURce] keyword is optional for all command state­ments in the :SOURce subsystem.

<numeric_value>
<numeric_value>
<numeric_value>

SINE | GAUSsian | RDOWn | RUP |
SQUare | TRIangle | UNIForm
<numeric_value>
<numeric_value>

50 | 600 | MIN | MAX
INTernal | EXTernal1 | EXTernal2
<boolean>
LINear | LOGarithmic

<boolean>

NONE | USER1 | USER2 | USER3 |
USER4 | USER5

SINE | GAUSsian | RDOWn | RUP |
SQUare | TRIangle | UNIForm
<numeric_value>
<numeric_value>
LOCKed1 | LOCKed2 | UNLocked
MIN | MAX

50 | 600 | MAX | MIN
<numeric_value>
INTernal | EXTernal1 | EXTernal2
<boolean>

Default: 3 dB/V
Default: 50 PCT/V
Default: 3 dB

Default: SINE

Default: 1 kHz
Default: 50 PCT

Default: 600
Default: EXTernal1
Default: OFF
Default: LINear

Default: OFF

Default: NONE

Default: SINE

Default: 1 kHz
Default: 1 MHz
Default: UNLocked
Default: MIN

Default: 600
Default: 1 MHz/V
Default: EXTernal1
Default: OFF

693XXB SCPI PM 3-25

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (2 of 4)

KEYWORD PARAMETER FORM NOTES

[:SOURce]

:FREQuency

[:CW | :FIXed]

STEP

[:INCRement]
CENTer
:MODE

:SPAN

:FULL
:STARt
:STOP
:MULTiplier

:LIST<n>

:INDex
:FREQuency

:POINts?
:POWer

:POINts?
:DWELl
:STARt
:STOP
:CALCulate

:MARKer<n>

:AOFF
:FREQuency
:STATe
:INTensity
:VIDeo
:POLarity

:PM

:BWIDth
:DEViation
:INTernal

:WAVE

:FREQuency
:EXTernal

:IMPedance
:SENSitivity
:SOURce
:STATe

<numeric_value>

<numeric_value>
<numeric_value>
CW |FIXed| SWEep[1] | SWCW | ALSW |
LIST[1] | LIST2 | LIST3 | LIST4
<numeric_value>

<numeric_value>
<numeric_value>
<numeric_value>

<numeric_value>
<numeric_value>{,<numeric_value>}

<numeric_value>{,<numeric_value>}

<numeric_value>
<numeric_value>
<numeric_value>

<numeric_value>
<boolean>
<boolean>
<boolean>
POSitive | NEGative

MIN | MAX
<numeric_value>

SINE | GAUSsian | RDOWn | RUP |
SQUARe | TRIangle | UNIForm
<numeric_value>

50 | 600 | MIN | MAX
<numeric_value>
INTernal | EXTernal1 | EXTernal2
<boolean>

Default: (MIN+MAX)/2

Default: 0.1 GHz
Default: (MIN+MAX)/2
Default: CW

Default: MAX–MIN

Default: MIN
Default: MAX
Default: 1

Where: 1 £ n £ 4
Default: 0
Default: 5 Ghz

Default: 0 dBm

Default: 50 ms
Default: 0
Default: 1999

Where: 1 £ n £ 10

Default: OFF
Default: OFF
Default: OFF
Default: POSitive

Default: MIN
Default: 1.0000 radians

Default: SINE

Default: 1 kHz

Default: 600
Default: 1.0000 radians
Default: EXTernal1
Default: OFF

3-26 693XXB SCPI PM

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (3 of 4)

KEYWORD PARAMETER FORM NOTES

[:SOURce]

:POWer

[:LEVel]

[:IMMediate]

[:AMPLitude]

:STEP

[:INCRement]
ALTernate
:SOURce

:ATTenuation

:STEP

[:INCRement]

:AUTO

:DISPlay

:OFFSet

:STATe

:SLOPe

:STEP

[:INCRement]
:STATe
:PIVot

:MODE

:CENTer
:SPAN

:FULL

:STARt
:STOP

:PULM

:INTernal

:FREQuency

:POLarity
:SOURce

:STATe

<numeric_value>

<numeric_value>
<numeric_value>
INTernal | DIODe[1] | DIODe[2] |
FIXed | PMETer[1] | PMETer[2]
<numeric_value>

<numeric_value>
<boolean>

<numeric_value>
<boolean>
<numeric_value>

<numeric_value>
<boolean>
<numeric_value>
CW | FIXed | SWEep[1] | SWEep2 | ALSW |
LIST[1] | LIST2 | LIST3 | LIST4
<numeric_value>
<numeric_value>

<numeric_value>
<numeric_value>

<numeric_value>
NORMal | INVerted
INTernal1 | INTernal2 |
EXTernal1 | EXTernal2
<boolean>

Default: 0 dBm

Default: 0.1 dB
Default: 0 dBm
Default: INTernal

Default: 0 dB

Default: 10 dB
Default: ON

Default: 0 dB
Default: OFF
Default: 128

Default: 1
Default: OFF
Default: 2 GHz
Default: FIXed

Default: (MIN+MAX)/2
Default: (See Command)

Default: MIN
Default: MAX

Default: 1 kHz
Default: NORMal
Default: INTernal1

Default: OFF

693XXB SCPI PM 3-27

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (4 of 4)

KEYWORD PARAMETER FORM NOTES

[:SOURce]

:PULSe

:COUNt
:DELay<n>
:PERiod
:WIDTh<n>
:STEP

:STARt
:STOP
:INCRement
:TIME

:SWEep<n>

:DIRection
:GENeration
:DWELl

:AUTO
:POINts
[:FREQuency]

:STEP
:POWer

:STEP
:SPACing
:TIME

:LLIMint

:AUTO

<numeric_value>
<numeric_value>
<numeric_value>
<numeric_value>
<boolean>
<numeric_value>
<numeric_value>
<numeric_value>
<numeric_value>

UP | DOWN
ANAlog | STEPped
<numeric_value>
<boolean>
<numeric_value>

<numeric_value>

<numeric_value>
LINear | LOGarithmic
<numeric_value>
<numeric_value>
<boolean>

Default: 1
Default: 100 ms
Default: 1 ms
Default: 500 ms
Default: OFF
Default: 100 ms
Default: 100 ms
Default: 100 ms
Default: 1 ms

SWEep1 = freq sweep;
SWEep2 = power sweep
(see text).
Default: 1
Default: UP
Default: (See Command)
Default: 1 ms
Default: ON
Default: (See Command)

Default: (See Command)

Default: (See Command)
Default: LINear
Default: (See Command)
Default: 2 ms
Default: ON

3-28 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:LOGSens

The [:SOURce]:AM command and its subcommands comprise the AM
Subsystem within the :SOURce subsystem. These commands control
the Amplitude Modulation function of the 693XXB.

[:SOURce]

:AM

:LOGSens

Parameters: sensitivity (in dB/V)

Type: <NRf>

Range: 0 to 25 dB/V

Default: 3 dB/V

Description: Sets the AM sensitivity for the external AM Log

mode.

Query Form: [:SOURce]:AM:LOGSens?

Example: [:SOURce]:AM:LOGSens sp 20 dB/V

Set the AM sensitivity for the external AM Log mode to
20 dB/V.

[:SOURce]:AM:LOGSens?

Requests the currently programmed AM sensitivity
value for the external AM Log mode.

693XXB SCPI PM 3-29

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:SENSitivity

[:SOURce]

:AM

:SENSitivity

Parameters: sensitivity (in Pct/V)

Type: <NRf>

Range: 0 to 100 %/V

Default: 50 %/V

Description: Sets the AM sensitivity for the external AM Linear

mode.

Query Form: [:SOURce]:AM:SENSitivity?

Example: [:SOURce]:AM:SENSitivity sp 80 Pct/V

Set the AM sensitivity for the external AM Linear
mode to 80 %/V.

[:SOURce]:AM:SENSitivity?

Requests the currently programmed AM sensitivity
value for the external AM Linear mode.

3-30 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:LOGDepth

[:SOURce]

:AM

:LOGDepth

Parameters: modulation depth (in dB)

Type: <NRf>

Range: 0to25dB

Default: 3dB

Description: Sets the modulation depth of the AM signal in the

internal AM Log mode.

Query Form: [:SOURce]:AM:LOGDepth?

Example: [:SOURce]:AM:LOGDepth sp 20 dB

Set the modulation depth in the internal AM Log mode
to 20 dB.

[:SOURce]:AM:LOGDepth?

Requests the currently programmed modulation depth
value for the internal AM Log mode.

693XXB SCPI PM 3-31

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:INTernal:WAVE

[:SOURce]

:AM

:INTernal

:WAVE

Parameters: SINE | GAUSsian | RDOWn | RUP | SQUare |

TRIangle | UNIForm

Type: <char>

Default: SINE

Description: Selects the modulating waveform (from the internal

AM generator) for the internal AM function, as fol­lows:

SINE = Sine wave
GAUSsian = Guassian noise
RDOWn = Negative ramp
RUP = Positive ramp
SQUare = Square wave
TRIangle = Triangle wave
UNIForm = Uniform noise

Query Form: [:SOURce]:AM:INTernal:WAVE?

Example: [:SOURce]:AM:INTernal:WAVE sp TRIangle

Selects a triangle wave as the modulating waveform
for the internal AM function.

[:SOURce]:AM:INTernal:WAVE?

Requests the currently selected modulating waveform
for the internal AM function.

3-32 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:INTernal:FREQuency

[:SOURce]

:AM

:INTernal

:FREQuency

Parameters: frequency

Type: <NRf>

Range: 0.1 Hz to 1 MHz for sine wave;

0.1 Hz to 100 kHz for square, triangle, and ramp wave­forms

Default: 1 kHz

Description: Sets the frequency of the modulating waveform for the

internal AM function (see :AM:INTernal:WAVE).

Query Form: [:SOURce]:AM:INTernal:FREQuency?

Example: [:SOURce]:AM:INTernal:FREQuency sp 50 kHz

Sets the frequency of the modulating waveform for the
internal AM function to 50 kHz.

[:SOURce]:AM:INTernal:FREQuency?

Requests the currently programmed modulating wave­form frequency value for the internal AM function.

693XXB SCPI PM 3-33

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:DEPTh

[:SOURce]

:AM

:DEPTh

Parameters: modulation depth (in Pct)

Type: <NRf>

Range: 0 to 100%

Default: 50%

Description: Sets the modulation depth of the AM signal in the in-

ternal AM Linear mode.

Query Form: [:SOURce]:AM:DEPTh?

Example: [:SOURce]:AM:DEPTh sp 80 Pct

Set the modulation depth in the internal AM Linear
mode to 80%.

[:SOURce]:AM:DEPTh?

Requests the currently programmed modulation depth
value for the internal AM Linear mode.

3-34 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:EXTernal:IMPedance

[:SOURce]

:AM

:EXTernal

:IMPedance

Parameters: 50 | 600 | MIN | MAX

Type: <nv>

Range: MIN = 50; MAX = 600

Default: 600

Description: Sets the input impedance of the selected (front panel

or rear panel) AM IN connector. The two valid numeric
values are 50 and 600 (ohms). The extended numeric
values MIN or MAX may also be used.

Query Form: [:SOURce]:AM:EXTernal:IMPedance?

Example: [:SOURce]:AM:EXTernal:IMPedance sp 600

Sets the input impedance of the selected AM IN connec­tor to 600 ohms.

693XXB SCPI PM 3-35

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:SOURce

[:SOURce]

:AM

:SOURce

Parameters: INTernal | EXTernal1 | EXTernal2

Type: <char>

Default: EXTernal1

Description: Selects the source of the AM modulating signal, as fol-

lows:

INTernal = Internal AM generator
EXTernal1 = Front panel AM IN connector
EXTernal2 = Rear panel AM IN connector

Query Form [:SOURce]:AM:EXTernal:SOURce?

Example: [:SOURce]:AM:SOURce sp EXTernal2

Selects the rear panel AM IN connector as the active
AM modulating signal source.

[:SOURce]:AM:SOURce?

Requests the currently programmed AM modulating
signal source.

3-36 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:STATe

[:SOURce]

:AM

: STATe

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: Enable/disable amplitude modulation of 693XXB RF

output signal.

Query Form [:SOURce]:AM:STATe?

Example: [:SOURce]:AM:STATe sp ON

Turns amplitude modulation on.

[:SOURce]:AM:STATe?

Requests currently programmed amplitude modula­tion state (on/off).

693XXB SCPI PM 3-37

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:TYPE

[:SOURce]

:AM

:TYPE

Parameters: LINear | LOGarithmic

Type: <char>

Default: LINear

Description: Selects the AM operating mode.

Query Form [:SOURce]:AM:TYPE?

Example: [:SOURce]:AM:TYPE sp LOGarithmic

Selects the AM Log mode.

[:SOURce]:AM:TYPE?

Requests the currently programmed AM operating
mode.

3-38 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :CORRection[:STATe]

The [:SOURce]:CORRection command and its subcommands comprise
the Correction Subsystem within the :SOURce subsystem. These com­mands are used to select and apply level flatness correction to the
693XXB RF output. (Refer to “Leveling Operations” in Chapter 3 of
the 693XXB Operation Manual.)

[:SOURce]

:CORRection

[ :STATe]

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: Turns the selected user level flatness correction

power-offset table on/off.

Query Form [:SOURce]:CORRection[:STATe]?

Example: [:SOURce]:CORRection:STATe sp ON

Turns on the selected user level correction power-offset
table.

NOTE:
If :CORRection:CSET:SELect is NONE, sending the command

:CORRection:STATe ON returns an error.

693XXB SCPI PM 3-39

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :CORRection:CSET:SELect

[:SOURce]

:CORRection

:CSET

:SELect

Parameters: NONE | USER1 | USER2 | USER3 | USER4 | USER5

Type: <char>

Default: NONE

Description: Selects the user level flatness correction power-offset

table to be applied to the 693XXB output by the com­mand [:SOURce]:CORRection:STATe ON.

Query Form [:SOURce]:CORRection:CSET:SELect?

Example: [:SOURce]:CORRection:CSET:SELect sp

USER3

Selects user level flatness correction power-offset table
#3.

3-40 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:INTernal:WAVE

The [:SOURce]:FM command and its subcommands comprise the FM
Subsystem within the :SOURce subsystem. These commands control
the Frequency Modulation function of the 693XXB.

[:SOURce]

:FM

:INTernal

:WAVE

Parameters: SINE | GAUSsian | RDOWn | RUP | SQUare |

TRIangle | UNIForm

Type: <char>

Default: SINE

Description: Selects the modulating waveform (from the internal

FM generator) for the internal FM function, as fol­lows:

SINE = Sine wave
GAUSsian = Guassian noise
RDOWn = Negative ramp
RUP = Positive ramp
SQUare = Square wave
TRIangle = Triangle wave
UNIForm = Uniform noise

Query Form: [:SOURce]:FM:INTernal:WAVE?

Example: [:SOURce]:FM:INTernal:WAVE sp SQUare

Selects a square wave as the modulating waveform for
the internal FM function.

[:SOURce]:FM:INTernal:WAVE?

Requests the currently selected modulating waveform
for the internal FM function.

693XXB SCPI PM 3-41

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:INTernal:FREQuency

[:SOURce]

:FM

:INTernal

:FREQuency

Parameters: frequency

Type: <NRf>

Range: 0.1 Hz to 1 MHz for sine wave;

0.1 Hz to 100 kHz for square, triangle, and ramp wave­forms

Default: 1 kHz

Description: Sets the frequency of the modulating waveform for the

internal FM function (see :FM:INTernal:WAVE).

Query Form: [:SOURce]:FM:INTernal:FREQuency?

Example: [:SOURce]:FM:INTernal:FREQuency sp 50 kHz

Sets the frequency of the modulating waveform for the
internal FM function to 50 kHz.

[:SOURce]:FM:INTernal:FREQuency?

Requests the currently programmed modulating wave­form frequency value for the internal FM function.

3-42 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:DEViation

[:SOURce]

:FM

:DEViation

Parameters: modulation deviation (in Hz)

Type: <NRf>

Range: 10 kHz to 20 MHz in Locked, Locked Low-Noise, and

Unlocked Narrow modes;
100 kHz to 100 MHz in Unlocked Wide mode

Default: 1 MHz

Description: Set the modulation deviation of the FM signal for the

internal FM function.

Query Form [:SOURce]:FM:DEViation?

Example: [:SOURce]:FM:DEViation sp 10 MHz

Set the modulation deviation of the FM signal for the
internal FM function to 10 MHz.

[:SOURce]:FM:DEViation?

Requests the currently programmed modulation devia­tion of the FM signal for the internal FM function.

693XXB SCPI PM 3-43

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:MODE

[:SOURce]

:FM

:MODE

Parameters: LOCKed[1] | LOCKed2 | UNLocked

Type: <char>

Default: UNLocked

Description: Sets the synthesis mode employed in generating the

FM signal, as follows:

LOCKed[1] = Locked Narrow FM
LOCKed2 = Locked Narrow Low-Noise FM
UNLocked = Unlocked FM

If LOCKed[1] or LOCKed2 is set, the YIG phase-locked
loop is used in synthesizing the FM signal. If UN-
Locked is set, the YIG phase-lock loop is disabled and
the FM signal is obtained by applying the modulating
signal to the tuning coils of the YIG-tuned oscillator.

Query Form [:SOURce]:FM:MODE?

Example: [:SOURce]:FM:MODE sp LOCKed[1]

Set the synthesis mode used to generate the FM signal
to Locked Narrow FM.

[:SOURce]:FM:MODE?

Requests the currently programmed synthesis mode
used to generate the FM signal.

NOTES:
UNLocked FM synthesis mode can be set for wide or narrow mode of

operation. (See [:SOURce]:FM:BWIDth)

3-44 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:BWIDth

[:SOURce]

:FM

:BWIDth

Parameters: MIN | MAX

Type: <nv>

Range: MIN = narrow mode; MAX = wide mode

Default: MIN

Description: Sets the Unlocked FM synthesis mode to wide or nar-

row mode of operation.
The Unlocked Wide FM synthesis mode allows maxi-

mum deviations of ±100 MHz for DC to 100 Hz rates.
The Unlocked Narrow FM synthesis mode allows

maximum deviations of ±10 MHz for DC to 8 MHz
rates.

Query Form [:SOURce]:FM:BWIDth?

Example: [:SOURce]:FM:BWIDth sp MAX

Set the Unlocked FM synthesis mode to Wide mode of
operation.

[:SOURce]:FM:BWIDth?

Requests the currently programmed Unlocked FM syn­thesis mode of operation (narrow or wide).

693XXB SCPI PM 3-45

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:EXTernal:IMPedance

[:SOURce]

:FM

:EXTernal

:IMPedance

Parameters: 50 | 600 | MIN | MAX

Type: <nv>

Range: MIN = 50; MAX = 600

Default: 600

Description: Sets the input impedance of the selected (front panel

or rear panel) FM IN connector. The two valid numeric
values are 50 and 600 (ohms). The extended numeric
values MIN or MAX may also be used.

Query Form [:SOURce]:FM:EXTernal:IMPedance?

Example: [:SOURce]:FM:EXTernal:IMPedance sp 50

Sets the input impedance of the selected FM IN connec­tor to 50 ohms.

3-46 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:SENSitivity

[:SOURce]

:FM

:SENSitivity

Parameters: sensitivity (in Hz/V)

Type: <NRf>

Range: ±10 MHz/V to ±20 MHz/V in Locked, Locked Low-

Noise, and Unlocked Narrow modes;
±100 kHz/V to ±100 MHz/V in Unlocked Wide mode

Default: 1 MHz/Volt

Description: Sets the FM sensitivity for the external FM function.

Query Form [:SOURce]:FM:SENSitivity?

Example: [:SOURce]:FM:SENSitivity sp 20 MHz/V

Set the FM sensitivity for the external FM function to
20 MHz/Volt.

[:SOURce]:FM:SENSitivity?

Requests the currently programmed FM sensitivity for
the external FM function.

693XXB SCPI PM 3-47

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:SOURce

[:SOURce]

:FM

:SOURce

Parameters: INTernal | EXTernal1 | EXTernal2

Type: <char>

Default: EXTernal1

Description: Selects the source of the FM modulating signal, as fol-

lows:

INTernal = Internal FM generator
EXTernal1 = Front panel FM IN connector
EXTernal2 = Rear panel FM IN connector

Query Form [:SOURce]:FM:SOURce?

Example: [:SOURce]:FM:SOURce sp EXTernal2

Selects the rear panel FM IN connector as the active
external FM modulating signal source.

[:SOURce]:FM:SOURce?

Requests the currently programmed FM modulating
signal source.

3-48 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:STATe

[:SOURce]

:FM

: STATe

Parameters: ON|OFF|1|0

Type: <boolean>

Default: OFF

Description: Enable/disable frequency modulation of 693XXB RF

output signal.

Query Form [:SOURce]:FM:STATe?

Example: [:SOURce]:FM:STATe sp ON

Turns frequency modulation on.

[:SOURce]:FM:STATe?

Requests the currently programmed frequency modula­tion state (on/off).

693XXB SCPI PM 3-49

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency[:CW |:FIXed]

The [:SOURce]:FREQuency command and its subcommands make up
the Frequency Subsystem within the :SOURce subsystem. These com­mands control the frequency characteristics of the 693XXB.

[:SOURce]

:FREQuency

[:CW | :FIXed]

Parameters: frequency (in Hz) | UP | DOWN | MIN | MAX

Type: <nv>

Range: MIN to MAX (see notes below)

Default: (MIN + MAX) / 2

Description: Sets the RF output frequency of the 693XXB to the

value entered. Parameters UP | DOWN increment/dec­rement the frequency by the value set by
[:SOURce]:FREQuency:STEP:INCRement command.

Query Form: [:SOURce]:FREQuency[:CW]?

Examples: [:SOURce]:FREQuency:CW sp 3 GHz

or:

Sets the RF output frequency to 3 GHz.

[:SOURce]:FREQuency:CW?

Requests the current value of the frequency parameter.

NOTES:
Keywords :CW and :FIXed are equivalent and may be used inter-

changeably; they also are optional and may be omitted.
MIN £ frequency ³ MAX; values for the MINimum and MAXimum fre-

quencies for each 693XXB model are listed in the table on the follow­ing page.

The query [:SOURce]:FREQuency:CW? sp MAX will return the upper
frequency to which the particular model 693XXB may be programmed.
Similarly, the query [:SOURce]:FREQuency:CW? sp MIN will return
the lower frequency limit.

:FREQ sp 3 GHz

3-50 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency[:CW |:FIXed]

Model 693XXB MINimum and MAXimum Frequencies

Model MINimum MAXimum

69217B/69317B 10 MHz 8.4 GHz
69237B/69337B 2 GHz 20 GHz
69247B/69347B 10 MHz 20 GHz
69267B/69367B 10 MHz 40 GHz
69277B/69377B 10 MHz 50 GHz
69287B/69387B 10 MHz 60 GHz
69297B/69397B 10 MHz 65 GHz

693XXB SCPI PM 3-51

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency[:CW |:FIXed]:STEP[:INCRement]

[:SOURce]

:FREQuency

[:CW | :FIXed]

:STEP

[:INCRement]

Parameters: frequency (in Hz)

Type: <NRf>

Range:

Default: 0.1 GHz

Description: Sets the step increment size used with the

Query Form: [:SOURce]:FREQuency[:CW]:STEP

1 kHz to (MAX – MIN) (see note below)

:FREQuency:CW command.

[:INCRement]?

Examples: [:SOURce]:FREQuency:CW:STEP

:INCRement sp 1 MHz

or:

Set the step increment value for the frequency parame­ter to 1 MHz.

[:SOURce]:FREQuency:CW:STEP:INCRement?

or:

Requests the current step increment value of the
frequency parameter.

NOTE:
For 693XXBs equipped with Option 11, the minimum value for fre-

quency step increment is 0.1 Hz. (The frequency resolution for stan­dard models is 1.0 kHz; for models with Option 11 it is 0.1 Hz.)

:FREQ:STEP sp 1 MHz

:FREQ:STEP?

3-52 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:CENTer

[:SOURce]

:FREQuency

:CENTer

Parameters: frequency ( in Hz)

Type: <NRf>

Range: MIN to MAX (See Notes)

Default: (MIN + MAX) / 2

Description: Sets the 693XXB RF output center frequency to the

value entered. :CENTER and :SPAN frequencies are
coupled values. Entering the value for one will cause
the other to be recalculated. (See notes under
:FREQuency :SPAN)

Query Form: [:SOURce]:FREQuency:CENTer?

Examples: [:SOURce]:FREQuency:CENTer sp 4GHz

Set the 693XXB RF output center frequency to 4 GHz.

[:SOURce]:FREQuency:CENTer?

Requests the current value of the RF output center fre­quency.

NOTES:
Stepped Sweep Center Range = MIN to MAX, where:

MIN = MIN + minimum step size
MAX = MAX – minumum step size

Analog Sweep Center Range = MIN to MAX, where;

MIN = MIN + (minimum analog span)/2
MAX = MAX – (minimum analog span)/2

693XXB SCPI PM 3-53

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:MODE

[:SOURce]

:FREQuency

:MODE

Parameters: CW | FIXed | SWEep[1] | SWCW | ALSW |

LIST[1] | LIST2 | LIST3 | LIST4

Type: <char>

Default: CW

Description: Specifies which command subsystem controls the

693XXB frequency, as follows:

CW | FIXed = [:SOURce]:FREQuency:CW | FIXed
SWEep[1] = [:SOURce]:SWEep[1] (see notes)
SWCW = (see notes)
ALSW = (see notes)
LIST<n> = [:SOURce]:LIST<n> (see notes)

:SWEep and :SWEep1may be used interchangeably.

Query Form: [:SOURce]:FREQuency:MODE?

Examples: [:SOURce]:FREQuency:MODE sp CW

Specifies that the 693XXB RF frequency output is to be
controlled by [:SOURce]:FREQuency :CW | FIXed com­mands.

[:SOURce]:FREQuency:MODE?

Requests the currently selected programming mode for
frequency control.

NOTES:
In SWEep[1] mode, frequency will be determined by programmed val-

ues for the following :FREQuency subsystem commands: :CENTer and
:SPAN,or, :STARt and :STOP.

In LIST mode, frequency is determined by programmed values for

:LIST<n>:FREQuency, where LIST<n> = LIST[1], LIST2, LIST3,or
LIST4. :LIST and :LIST1 may be used interchangeably.

Setting ALSW will cause the 693XXB to do alternate sweeping when
properly triggered.

Setting FIXed will return CW upon query.
Setting SWCW will set CW and turn on CW ramp, the same as the

command statement :FREQuency:MODE CW;:CONTrol:RAMP ON
A query returns CW.

3-54 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:SPAN

[:SOURce]

:FREQuency

:SPAN

Parameters: frequency (in Hz)

Type: <NRf>

Range: 1 kHz to (MAX – MIN)

Default: MAX – MIN

Description: Sets sweep span for SWEep[1] to value entered. :SPAN

and :CENTer are coupled values (see notes below).

Query Form: [:SOURce]:FREQuency:SPAN?

Examples: [:SOURce]:FREQuency:SPAN sp 2 GHz

or:

Set the SWEep[1] sweep span to 2 GHz.

:FREQ:SPAN sp 2 GHz

[:SOURce]:FREQuencySPAN:?
Requests the current value for SWEep[1] sweep span.

NOTES:
:SPAN, :CENTer, :STARt, and :STOP are coupled values. Entering the

value for :SPAN causes the values for :STARt and :STOP to be recalcu­lated.

At *RST, :SPAN = Fmax – Fmin

693XXB SCPI PM 3-55

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:SPAN:FULL

[:SOURce]

:FREQuency

:SPAN

:FULL

Parameters: None

Description: Sets frequency span for SWEep[1] to (MAX – MIN)

(see notes under [:SOURce]:FREQuency:CW | FIXed).

Query Form: None

Example: [:SOURce]:FREQuency:SPAN:FULL

Set the SWEep[1] frequency span to its maximum
value.

3-56 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:SPAN

[:SOURce]

:FREQuency

:SPAN2

Parameters: frequency (in Hz)

Type: <NRf>

Range: 1 kHz to (MAX – MIN)

Default: MAX – MIN

Description: Sets sweep span for the alternate sweep to value

entered. :SPAN and :CENTer are coupled values (see
notes below).

Query Form: [:SOURce]:FREQuency:SPAN2?

Examples: [:SOURce]:FREQuency:SPAN2 sp 2 GHz

or:

Set the sweep span for the alternate sweep to 2 GHz.

:FREQ:SPAN2 sp 2 GHz

2

[:SOURce]:FREQuencySPAN2:?

Requests the current value of the sweep span for the
alternate sweep.

NOTES:
:SPAN, :CENTer, :STARt, and :STOP are coupled values. Entering the

value for :SPAN causes the values for :STARt and :STOP to be recalcu­lated.

At *RST, :SPAN = Fmax – Fmin

693XXB SCPI PM 3-57

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:SPAN2:FULL

[:SOURce]

:FREQuency

:SPAN2

:FULL

Parameters: None

Description: Sets the alternate sweep frequency span to

(MAX – MIN) (see notes under [:SOURce]
:FREQuency:CW | FIXed).

Query Form: None

Example: [:SOURce]:FREQuency:SPAN:FULL

Set the frequency span for the alternate sweep to its
maximum value.

3-58 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:STARt

[:SOURce]

:FREQuency

:STARt

Parameters: frequency (in Hz) | MIN

Type: <nv>

Range:

Default: MIN

Description: Sets start frequency for SWEep[1] to the value en-

Query Form: [:SOURce]:FREQuency:STARt?

Examples: [:SOURce]:FREQuency:STARt sp 2.5 GHz

MIN to MAX (see notes)

tered. (MIN is defined in the notes under [:SOURce]
:FREQuency:CW | FIXed).

Set the start frequency for SWEep[1] to 2.5 GHz .
[:SOURce]:FREQuency:STARt?

Requests the current value for SWEep[1] start
frequency.

NOTES:
Stepped Sweep Start Range = MIN to MAX, where:

MAX = MAX –2´ minimum frequency step size

Analog Sweep Start Range = MIN to MAX, where;

MAX = MAX – minimum analog span

693XXB SCPI PM 3-59

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:STARt

[:SOURce]

:FREQuency

:STARt2

Parameters: frequency (in Hz) | MIN

Type: <nv>

Range: MIN to MAX (see notes)

Default: MIN

Description: Sets start frequency for the alternate sweep to the

value entered. (MIN is defined in the notes under
[:SOURce]:FREQuency:CW | FIXed).

Query Form: [:SOURce]:FREQuency:STARt2?

Examples: [:SOURce]:FREQuency:STARt2 sp 3.5 GHz

Set the start frequency for the alternate sweep to

3.5 GHz .

2

[:SOURce]:FREQuency:STARt2?

Requests the current value for the alternate sweep start
frequency.

NOTES:
Stepped Sweep Start Range = MIN to MAX, where:

MAX = MAX –2´ minimum frequency step size

Analog Sweep Start Range = MIN to MAX, where;

MAX = MAX – minimum analog span

3-60 693XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:STOP

[:SOURce]

:FREQuency

:STOP

Parameters: frequency (in Hz) | MAX

Type: <nv>

Range: MIN to MAX (see notes)

Default: MAX

Description: Sets stop frequency for SWEep[1] to the value entered.

(MAX is defined in the notes under [:SOURce]
:FREQuency:CW | FIXed).

Query Form: [:SOURce]:FREQuency:STOP?

Examples: [:SOURce]:FREQuency:STOP sp 15 GHz

Set the stop frequency (for SWEep[1] to 15 GHz.
[:SOURce]:FREQuency:STOP?

Requests the current value for SWEep[1] stop fre­quency.

NOTES:
Stepped Sweep Stop Range = MIN to MAX, where:

MIN = MIN +2´ minimum frequency step size

Analog Sweep Stop Range = MIN to MAX, where;

MIN = MIN + minimum analog span

693XXB SCPI PM 3-61

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:STOP

[:SOURce]

:FREQuency

:STOP2

Parameters: frequency (in Hz) | MAX

Type: <nv>

Range: MIN to MAX (see notes)

Default: MAX

Description: Sets stop frequency for the alternate sweep to the

value entered. (MAX is defined in the notes under
[:SOURce]:FREQuency:CW | FIXed).

Query Form: [:SOURce]:FREQuency:STOP2?

Examples: [:SOURce]:FREQuency:STOP2 sp 13 GHz

Set the stop frequency for the alternate sweep to 13
GHz.

2

[:SOURce]:FREQuency:STOP2?

Requests the current value for the alternate sweep stop
frequency.

NOTES:
Stepped Sweep Stop Range = MIN to MAX, where:

MIN = MIN +2´ minimum frequency step size

Analog Sweep Stop Range = MIN to MAX, where;

MIN = MIN + minimum analog span

3-62 693XXB SCPI PM