Anritsu 68247B SCPI Programming Manual

SERIES

682XXB/683XXB

SYNTHESIZED SIGNAL GENERATORS

SCPI PROGRAMMING MANUAL

490 JARVIS DRIVE
MORGAN HILL, CA 95037-2809

P/N: 10370-10288

PRINTED: NOVEMBER 1996

COPYRIGHT 1994 WILTRON CO.

REVISION: D

WARRANTY

The WILTRON product(s) listed on the title page is (are) warranted against defects in materials
and workmanship for one year from the date of shipment, except for YIG-tuned oscillators and all
WILTRON manufactured microwave components, which are warranted for two years.

WILTRON’s obligation covers repairing or replacing products which prove to be defective during the
warranty period. Buyers shall prepay transportation charges for equipment returned to WILTRON
for warranty repairs. Obligation is limited to the original purchaser. WILTRON is not liable for
consequential damages.

LIMITATION OF WARRANTY

The foregoing warranty does not apply to WILTRON connectors that have failed due to normal wear.
Also, the warranty does not apply to defects resulting from improper or inadequate maintenance by
the Buyer, unauthorized modification or misu se, or operation outside of the environmental spec ifi­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

WILTRON Company has prepared this manual for use by WILTRON Company personnel and
customers as a guide for the proper installation, operation, and maintenance of WILTRON Company
equipment and computor programs. The drawings, specifications, and information contained herein
are the property of WILTRON Company, and any unauthorized use or disclosure of these drawings,
specifications, 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 wit hout the
prior writtten consent of WILTRON Company.

TABLE OF CONTENTS

Chapter 1 — General GPIB Information

Chapter 1 provides a general description of the General Purpose Interface Bus (GPIB) and the bus

data transfer and control functions. It also contains a listing of the 682XXB/683XXB’s GPIB inter­face function subset capability and response to IEEE-488 interface function messages. Chapter con­tents are detailed immediately following the tab.

Chapter 2 — Programming with SCPI Commands

Chapter 2 provides an introduction to SCPI programming that includes descriptions of the com­mand types, hierarchial command structure, data parameters, and notational conventions. Informa­tion on 682XXB/683XXB stat us system and trigger sys tem programming is also prov ided. Chapter
contents are detailed immediately follo wing the tab.

Chapter 3 — Programming Commands

Chapter 3 contains information on all SCPI programming commands accepted and implemented by
the Series 682XXB/683XXB Synthesized Signal Generators. Chapter contents are detailed immedi­ately following the tab.

Chapter 4 — Error Messages

Chapter 4 lists and describes each of the error messages related to 682XXB/683XXB signal gener­ator operation. In addition, it provides information about the error message elements, the error
query command, the error queue, and the classes of error messages . Chapter contents are detailed
immediately following the tab.

Appendix A — Overall Command Tree

Appendix A provides an overall command tree for the Series 682XXB/683XXB SCPI command set.

Appendix B — SCPI Conformance Information

Appendix B provides SCPI conformance information for the Series 682XXB/683X XB SCPI com­mand set in the form of a command summary.

Subject Index

Provides a subject index.

682XXB/683XXB SCPI PM i/ii

Chapter 1
General GPIB Information

Table of Contents

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

Electronic Man ual . . . . . . . . . . . . . . . . . 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 682XXB/683XXB 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
682XXB/683XXB Synthesized Signal Generators using commands
sent from an external controller via the IEEE-488 General Purpose In­terface Bus (GPIB). It includes the following:

A general description of the GPIB and the bus data transfer and
control functions.
A listing of the IEEE-488 Interface Function Messages recog­nized by the signal generator with a description of its response.
A c omplete listing and description of all the Standard Commands
for Programmable Instruments (SCPI) commands that can be
used to control signal generator operation with examples of com­mand usage.

This manual is intended to be used in conjunction with the Series
682XXB/683XXB Synthesized Signal Generators Operation Manual,
P/N 10370-10284. Refer to that manual for general information about
the 682XXB/683XXB, 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 be 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 WILTRON
Custormer 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
682XXB/683XXB GPIB Product-Specific
(“NATIVE”) commands. These GPIB commands are
listed and described in the Series 682XXB/683XXB
Synthesized Signal Generators GPIB Programming
Manual, P/N 10370-10286.

682XXB/683XXB SCPI PM 1-3

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

IEEE-488 BUS (16 Lines)

DEVICE A

Able to talk, listen,
and control

(e.g. COMPUTER)

DEVIC E B

Able to talk and listen

(e.g. 682XXB/683XXB
SIGNAL
GENERATOR)

DEVICE C

Data Bus
(8 signal lines)

Data Byte Transfer
Control Bus

(3 sign al l in es )

DATA LINES

HANDSHAKE Lines

Only able to listen

(e.g. OTHER
INSTRUMENT**)

DEVICE D

Only able to talk

(e.g. OTHER
INSTRUMENT**)

General Interface
Management Bus

(5 sign al l in es )

DATA
INPUT/OUTPUT, DIO
1 thru DIO 8
DAV - DATA VALID

NRFD - NOT READY FOR DATA*
NDAC - NOT DATA ACCEPTED*

IFC - INTERFACE CLEAR
ATN - ATTENT ION
SRQ - SERVI CE REQUE ST
REN - REMOTE ENABLE
EOI - END OR IDEN TI FY

* NEGATION IS REPRESENTED BY
LOW STATE ON THESE TWO
LINES

** IF USED

Figure 1-1. Interface Connections and GPIB Bus Structure

Management
CONTROL Lines

1-4 682XXB/683XXB 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

682XXB/683XXB’s GPIB interface function subset capability and re­sponse 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 me­chanical 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.

No more than 15 devices can be interconnected by one contiguous
bus; however, an instrumentation system may contain more than
one interface bus.
The maximum total cumulative cable length for one interface
bus may not exceed twic e the number of devices connected (in me­ters), or 20 meters—whichever is less.
A maximum data rate of 1 Mb/s across the interface on any sig­nal line.
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 be­tween devices. The five remaining signal lines are referred to as inter­face management lines.

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

682XXB/683XXB 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-de­pendent data to another device on the bus when ad­dressed to talk. Only one GPIB device at a time can
be an active talker.

Listener

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

Controller

A c on troller 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 designat­ing who will talk and who will listen.

System Controller

The system controller is the device that always re­tains ultimate control of the GPIB. When the sys­tem is first powered-up, the system controller is the
active controller and manages the GPIB. The sys­tem controller can pass control to a device, making
it the new active controller. The new active control­ler, in turn, may pass control on to yet another de­vice. 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 con trol of the
GPIB at anytime.

1-6 682XXB/683XXB 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)
Data Byte Transfer Control Bus (3 lines)
General Interface Management Bus (5 lines)

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

Table 1-1. Interface Bus Signal Line Designations

DAV
NRFD
NDAC

ATN
IFC
SRQ
REN
EOI

Signal Line

Name

Function

Data Availa ble
Not Ready For Data
Not Data Accepted

Attention
Interface Clear
Service Request
Remote Enable
End Or Identify

Bus Type

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

Transfer
Control Bus

General
Interface
Management
Bus

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 repre­sents 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 com­mand which is to be received by every GPIB device.
If ATN is FALSE, then a data byte is being trans­ferred and only the active listeners will receive that
byte.

682XXB/683XXB SCPI PM 1-7

GENERAL GPIB IEEE-488 INTERFACE

1st Data Byte 2nd Data Byte

Valid

Not

Valid

Valid

Not

Valid

All

Ready

None

Ready

All

Ready

None

Ready

All

Accept

None

Accept

None

Accept

All

Accept

DIO1-DIO8

(composite)

DAV

NRFD

NDAC

INFORMATION BUS DESCRIPTION

Figure 1-2. Typical GPIB Handshake Operation

Data Byte
Transfer
Control Bus
Description

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.
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
listeners. 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.

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
line FALSE (high) which they will do at their own

1-8 682XXB/683XXB SCPI PM

GENERAL GPIB IEEE-488 INTERFACE
INFORMATION BUS DESCRIPTION

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 ad­dressed 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 ac­cepted 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
addressed, 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 lo­cal operation.

682XXB/683XXB 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 messages. Each specific interface function may
only send or receive a limited set of messages
within particular 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 de­vice must have. This minimum set of interface func­tions 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 682XXB/683XXB signal gen­erators.

Table 1-2. 682XXB/683XXB Interface Function Capability

Function
Identifier

AH1 Acceptor Handshake Complete Capability

Function 682XXB/683XXB Capability

SH1 Source Handshake Compl et e C ap ab il ity

T6 Talker No Talk Only (TON)

L4 Listener No Listen Only (LON)
SR1 Service Request Complete Capabil it y
RL1 Remote/Local Complete Capab il it y
PP1 Parallel Poll Complete Capability
DC1 Device Clear Complete Capability
DT1 Device T r ig ge r Complete Capab il it y

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 682XXB/683XXB 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, usu­ally called commands or command messages. Inter-
face function messages perform such functions as
initializing the bus, addressing and unaddressing
devices, and setting device modes for remote or local
operation.

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.

682XXB/683XXB 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 er­ror. 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
fuction message, one would call the
the National Instruments software driver. On the
other hand, the command
command string to the addressed device. In the case
of the National Instruments example, this would be
done by using the

IFC (Interface Clear) interface

ibsic function of

*RST (Reset) is sent in a

ibwrt function call.

1-12 682XXB/683XXB SCPI PM

GENERAL GPIB 682XXB/683XXB
INFORMATION GPIB OPERATION

1-4

682XXB/683XXB GPIB
OPERATION

All Series 682XXB/683XXB Synthesized Signal Generator functions,
settings, and operating modes (except for power on/standby) are con­trollable using commands sent from an external controller via the
GPIB. When in the remote (GPIB) mode, the signal generator func­tions as both a listener and a talker. The GPIB interface function capa­bility of the 682XXB/683XXB is listed in Table 1-2 (page 1-10).

Setting GPIB
Operating
Parameters

Selecting the
Interface
Language

The 682XXB/683XXB leaves the factory with the
GPIB address value set to
terminator 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 (
only. Refer to Chapter 2 of the Series 682XXB/
683XXB Synthesized Signal Generators Operation
Manual for the procedure.

Series 682XXB/683XXB Synthesized Signal Gener­ators with Option 19 can be remotely operated us-

ing one of two external interface languages—Native
or SCPI. The Native interface language uses a set of
682XXB/683XXB GPIB Product Specific commands
to control the instrument; the SCPI interface lan­guage uses a set of the Standard Commands for Pro­grammable Instruments commands to control the
unit. Selecting which of these external interface lan­guages is to be used can be made from the front
panel using the Configure GPIB menu. Refer to
page 2-11 for the procedure.

5 and the data delimiting

CR)

Response to
GPIB
Interface
Function
Messages

Table 1-3 (page 1-14) lists the GPIB Interface Func­tion Messages that the 682XXB/683XXB will recog­nize and respond to. With the exception of the
Device Clear and Selected Device Clear messages,
these messages affect only the operation of th e
682XXB/683XXB GPIB interface. The signal gener­ator’s response for each message is indicated.

Interface function messages are transmitted on the
GPIB data lines and interface management lines as
either unad dressed or addressed commands. The
manner in which these messages are invoked in pro­grams is implementation dependent. For program­ming information, refer to the documentation
included with the GPIB Interface used for the exter­nal controller.

682XXB/683XXB SCPI PM 1-13

GENERAL GPIB 682XXB/683XXB GPIB
INFORMATION OPERATION

Table 1-3. 682XXB/683XXB Response to GPIB Interface Function Messages

Interface Function Message

Device Clear (DCL)
Selected Device Clear (SDC)

Go To Local (GTL) Yes Returns the 682XXB/ 68 3XXB to

Group Execute Trigger
(GET)

Interface Clear (IFC) No Stops the 682XXB/683XXB GPIB

Local Lockout (LLO) No Disables the front panel menu

Remote Enable (REN) No Places the 682XXB/683XXB unde r

Serial-Poll Enable (SPE) No Outputs the serial-poll status byte.
Serial-Poll Disable (SPD) No Disables the serial-poll func ti on .
Parallel-Poll Configure (PPC) Yes Responds to a parallel -po ll

Addressed

Command

No

Yes

Yes Execute s a st r in g of commands, if

682XXB/683XXB Response

Resets the 682XXB/683XXB to its
default state. (Equivalent to sending
the *RST command.)

local (front panel) control.

programmed.

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

RETURN TO LOCAL soft-key.

remote (GPIB) control when it has
been addressed to listen.

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

Parallel-Poll Unconfigure
(PPU)

No Disables the parallel-poll func ti on.

1-14 682XXB/683XXB 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 Ty pes . . . . . . . . . . . . . . . 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

T rigger 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
682XXB/683XXB status system and trigger system programming is
also provided.

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 682XXB/683XXB was designed to conform to the requirements of
SCPI 1993.0. The set of SCPI commands implemented by the 682XXB/
683XXB GPIB interface provides a comprehensive set of programming
functions covering all the major functions of the 682XXB/683XXB sig­nal generators.

SCPI
Command
Types

SCPI commands, which are also referred to as SCPI
instructions, are messages to the instrument to per­form specific tasks. The 682XXB/683XXB command
set includes:

“Common” commands (IEE488.2 mandated
commands)

SCPI required commands
SCPI optional commands (per SCPI 1993.0)
SCPI compliant commands that are unique to

the 682XXB/683XXB.

The SCPI conformance information for the 682XXB/
683XXB command set is contained in Appendix B —
SCPI Conformance Information.

682XXB/683XXB 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 Com­mands

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 compatible in­struments. These commands (see table at left) are
identified by the asterisk (∗) at the beginning of the
command keyword. These commands are used to
control instrument status registers, status reporting,
synchronization, and other common functions. 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, para­graphs 3-11 and 3-12. The optional SCPI commands
and 682XXB/683XXB unique commands comprise
the remainder (major portion) of the 682XXB/
683XXB command set. They control the majority of
the programmable functions of the 682XXB/683XXB.
They are described in detail 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 682XXB/683XXB SCPI PM

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Command
Names

Typical SCPI commands consist of on e 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 man­ual, 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:

The short form keyword is usually the first four char­acters of the long form (example:
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 fea­tures such as dual channel inputs. For example: key­words
are used to differentiate between the 682XXB/
683XXB front panel and rear panel MODULATION con­nectors.

EXTernal1 and EXTernal2 (or EXT1 and EXT2)

DISPlay.

DISP for DISPlay).

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

682XXB/683XXB SCPI PM 2-5

PROGRAMMING WITH INTRODUCTION TO
SCPI COMMANDS SCPI PROGRAMMING

Hierarchical
Command
Structure

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 functio ns
are located at the top of the command tree. The com­mand keywords for the 682XXB/683XXB SCPI com­mand set are shown in the diagram below.

root

:ABORt :CONTrol :DIAGnostic :DISPLAY :INITiate

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

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

:CONTrol com-

:CONTrol

:BLANking :RAMP :PENLift

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

An overall command tree for the 682XXB/683XXB
SCPI command set is shown in Figure A-1 of Appen­dix A.

2-6 682XXB/683XXB 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 as­sociated with a particular SCPI command is deter­mined by the type of information required to control
the particular instrument function. For example,
Boolean (
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
<NR2>, and <NR3> numeric data as defined in Pa­rameter Notations on page 2-9. This type of numeric
element is abbreviated as
document.

Extended Numeric

Extended numeric parameters include values such
as MAXimum and MINimum.

ON | OFF) type parameters are used with

<NR1>,

<NRf> throughout this

Discrete

Discrete parameters, such as INTernal and EXTer­nal, are used to control program settings to a prede­termined finite value or condition.

Boolean

Boolean parameters represent binary conditions and
may be expressed as

Unit Suffixes Unit suffixes are not required for data parameters,

provided the values are scaled for the global default
units. The 682XXB/683XXB SCPI default units are:
Hz (Hertz) for frequency related parameters and S
(seconds) for time related parameters. For example,
the command below sets the 682XXB/683XXB out­put frequency to 3 GHz.

:SOURce:FREQuency:CW 3000000000

The global default units may be changed via use of

:UNIT Subsystem commands described in Chap-

the
ter 3, paragraph 3-15.

ON, OFF or 1, 0.

682XXB/683XXB 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 instrumenta­tion. 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 re­porting).

General
Notations

The syntax conventions that are used for all SCPI
command keywords and data parameter descriptions
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

separate alternative parameter options.
Example:

<> 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 associated data
parameters. It must not be used between key­words, 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 document.

ON|OFF is the same as ON or OFF.

2-8 682XXB/683XXB 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

<boolean>

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

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

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

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

<NRf> ::=<NR1>|<NR2>|<NR3>

::=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.

point (implied radix point)

(implied radix point).

point.

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

1 or 0

<nv>

::=SCPI numeric value: <NRf>|MIN|MAX|UP

|DOWN|DEF|NAN|INF|NINF

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

Examples: CW, FIXed, UP, and DOWN,

<string>

<block>
<NA> ::=Not Applicable

::=<STRING PROGRAM DATA>.
ASCII characters surrounded by double
quotes, example:

::=IEEE-488.2 block data format

“OFF”

or other types

682XXB/683XXB 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]

sp

:STEP[:INCRement]

Command statements read from left to right and
from top to bottom. In the command statement
above, the
:AMPLitude keyword with no separating space. A
space (
its argument (a

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
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 sin­gle statement. Note the semicolon used to join the
commands. (Also note the leading colon used immedi­ately after the semicolon.)

:STEP keyword immediately follows the

sp

) is used between the command string and

<nv> type data parameter).

dBm|DOWN|UP

:SOURce keyword is op-

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

2-10 682XXB/683XXB SCPI PM

PROGRAMMING WITH SCPI INTERFACE
SCPI COMMANDS LANGUAGE SELECTION

2-4

SCPI INTERFACE
LANGUAGE SELECTION

The Series 682XXB/683XXB Synthesized Signal Generators can be re-

motely operated using one of two external interface languages—Native
or SCPI. (The Native interface language uses a set of 682XXB/683XXB
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

SCPI can be selected as the 682XXB/683XXB inter­face language 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 ac-

cess the System Menu. At the menu display, press
Config to access the System Configuration Menu.
Then, press
played.

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. The language selection will appear on the dis­play.

GPIB . The Configure GPIB Menu is dis-

SCPI/Native to select

Remote
Selection

SCPI can be selected as the 682XXB/683XXB inter­face language 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 no t
use a leading colon (:) with the command. The com-

:SYSTem:LANGuage "SCPI" results in a syn-

mand
tax error.

NOTE

When the 682XXB/683XXB signal generator
is remotely operated using the SCPI inter­face lanuage, cycling the power returns the
instrument to a reset condition.

682XXB/683XXB SCPI PM 2-11

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

2-5

STATUS SYSTEM
PROGRAMMING

The 682XXB/683XXB status system (shown in Figure 2-1) consists of
the following SCPI-defined status-reporting structures:

The Instrument Summary Status Byte Group
The Standard Event Status Group
The Operational Status Group
The Questionable Status Group

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 reg­ister, a transition filter, an event register, and an en­able register. Each component is briefly described in
the following paragraphs.

Condition Register

The condition register is continuously updated to re­flect the current status of the 682XXB/683XXB.
There is no latching or buffering for this register, it
is updated in real time. Reading the contents of a
condition register 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 regis­ter. Negative transition filters (NTR) are used to de­tect 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 ∗

RST commands.

∗

The command

sition filters to all 0’s and sets all positive transition
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 ∗
command. Event registers are read only.

:STATus:PRESet sets all negative tran-

CLS (clear status) and

CLS

2-12 682XXB/683XXB 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)

Error Queue
not empty

INSTRUMENT SUMMARY

Not Used
Not Used

ERRQ
QUEST

MAV
STD

OPER

*STB?

Summary

STATUS BYTE

STATUS BYTE

b0
b1
b2
b3
b4
b5
b6
b7

*CLS

*SRE n
*SRE?

b0-b7

NOTE: Not Used bits are always cleared to 0.

Bit Weight

1

b0

2

b1
b2

4
8

b3

16

b4

32

b5

64

b6

128

b7

*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. 682XXB/683XXB Status-Reporting Structure

682XXB/683XXB 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
682XXB/683XXB logically ANDs corresponding bits
in the event and enable registers, and ORs all the re­sulting bits to obtain a summary bit. Summary bits
are recorded in the Summary Status Byte. Enable
registers are read-write. Querying an enable register
does not affect it.

Status Group
Reporting

The command
Status Enable register and the Questionable Status

Enable register to all 0’s.
The state of certain 682XXB/683XXB hardware and

operational events and conditions can be determined
by programming th e st atu s sy st em. As s ho wn i n Fi g­ure 2-1, the three lower status groups provide status
information 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.

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.

:STATus:PRESet sets the Operational

NOTE

2-14 682XXB/683XXB 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 682XXB/683XXB event or condition. The
bits in the Summary Status Byte provide the follow­ing information:

Bit Description

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

2 Set to indicate the Error Queue cont ai ns da ta . T he

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 rea d to determine the specif ic
condition that caused the bit to be set.

4 Set to indicate that the 682XXB/683XXB has data

ready in its outpu t qu eue.

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 682XXB/683XXB has at

least one reason to require service. This bit is also
called the Master Summary Status Bit (MSS). The
individual 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 Operatio nal Status

summary bit has been set. The Oper at io na l Status
Event register can then be read to determine the
specific condition that caused the bit to be set.

682XXB/683XXB SCPI PM 2-15

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Standard Eve nt S ta tus 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 682XXB/683XXB

operations were com pl et ed following execution of

the “∗OPC” comman d.
1 Not Used. The bit is always set to 0.
2 Set to indicate tha t a qu ery error ha s oc cu rred.

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 fr om –399 to –300 and 1 to 32767.
4 Set to indicate that a ex ec ut io n erro r has occurre d.

Execution errors have SCPI error codes from

–299 to –200.
5 Set to indicate tha t a co mm an d erro r has

occurred. Command errors have SCPI error

codes from –199 to –1 00 .

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

2-16 682XXB/683XXB 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 682XXB/68 3XXB is

measuring.

5 Set to indicate that the 682XXB/68 3XXB 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 682XXB/683XXB se lf -te st is in

progress.

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

*15 Alwa ys 0. Th e us e of Bit 15 is not allowed by

SCPI.

682XXB/683XXB SCPI PM 2-17

PROGRAMMING WITH STATUS SYSTEM
SCPI COMMANDS PROGRAMMING

Questionable St at us G r o up

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 Ques­tionable Event register provide the following infor­mation:

Bit Description

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

3 Set to indicate an R F unleveled cond it io n.
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 ph as e-l oc k erro r.
11 Set to indicate a fai lu r e of the crystal oven.

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

*15 Alw a ys 0. The use of Bit 15 is not allo w ed by

SCPI.

2-18 682XXB/683XXB SCPI PM

PROGRAMMING WITH TRIGGER SYSTEM
SCPI COMMANDS PROGRAMMING

2-6

TRIGGER SYSTEM
PROGRAMMING

The 682XXB/683XXB trigger system is used to synchronize signal gen­erator actions with software trigger commands. The 682XXB/683XXB
follows the layered trigger model used in SCPI instruments. The follow­ing paragraphs describe operation and programming of the signal gen­erator trigger system. The structure and components of the 682XXB/
683XXB 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. 682XXB/683XXB Trigger Model

Trigger
System
Operation

Turning power on, or sending ∗
the trigger system into the idle state. The trigger
system remains in the idle state until it is initiated.

RST or :ABORt forces

Trigger system initiation can happen on a continu­ous basis (
basis (
mand
system is initiated by the
mand. Note that ∗

:INITiate:CONTinuous ON) or on a demand
:INITiate:CONTinuous OFF). When the com-
:INITiate:CONTinuous is set to OFF, the trigger

:INITiate[:IMMediate] com-

RST sets :INITiate:CONTinuous to

OFF.

682XXB/683XXB 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
ined 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

HOLD the trigger signal is never TRUE.

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

:TRIGger[:SEQuence]:SOURce is exam-

<GET> (Group Execute Trigger) mes-

sage or th e ∗

TRG command.

The command
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

OFF, the trigger system returns to the idle state.

set

:INITiate:CONTinuous is set to ON, the trigger sys-

If
tem returns to the armed (wait for trigger) state.

Auto Trigger Mode

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

ABORt

:ABORt command resets any swee p in progress

The
and immediately returns the trigger system to the
idle state. Unlike ∗
settings programmed by other commands.

:TRIGger[:SEQuence][:IMMediate] pro-

:INITiate:CONTinuous is

:INITiate:CONTinuous to ON

RST, :ABORt does not change the

2-20 682XXB/683XXB SCPI PM

Chapter 3
Programming
Commands

Table of Contents

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

3-2 COMMON COMMAND S . . . . . . . . . . . . . . 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 (T rigger 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

:DIAGnost ic: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

3-2 682XXB/683XXB SCPI PM

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

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

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

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

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

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

[:SOURce]:FM:ST ATe . . . . . . . . . . . . . . . . 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]:MARKer<n>:AOFF . . . . . . . . . . . 3-64

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

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

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

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

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

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

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

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

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

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

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

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

[:SOURce]:PM:ST ATe . . . . . . . . . . . . . . . . 3-77

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

[:AMPLitude] . . . . . . . . . . . . . . . . . . . 3-78

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

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

682XXB/683XXB SCPI PM 3-3

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

[:SOURce]:POWer[:LEVel]:AL Ternate . . . . . . . 3-81

[:SOURce]:POWer:ALC:GAIN . . . . . . . . . . . 3-82

[:SOURce]:POWer:ALC:GAIN:STEP

[:INCRement] . . . . . . . . . . . . . . . . . . . 3-83

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

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

[:SOURce]:POWer:ATTenuation:STEP

[:INCRement] . . . . . . . . . . . . . . . . . . . 3-86

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

[:SOURce]:POWer:DISPlay:OF FSet . . . . . . . . 3-88

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

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

[:SOURce]:POWer:SLOPe:STEP[:I NCRement] . . 3-91

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

[:SOURce]:POWer:SLOPe:PIV ot . . . . . . . . . . 3-93

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

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

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

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

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

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

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

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

[:SOURce]:PULM:SOURc e . . . . . . . . . . . . 3-102

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

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

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

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

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

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

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

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

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

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

[:SOURce]:SCAN:STATe . . . . . . . . . . . . . 3-113

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

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

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

3-4 682XXB/683XXB SCPI PM

Table of Contents (Continued)

3-10 SOURCE SUBSYSTEM (Continued)

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

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

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

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

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

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

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

3-11 S TATUS SUBSYSTEM . . . . . . . . . . . . . . 3-126

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

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

:STATus:OPERation:ENABle . . . . . . . . . . . 3-128

:STATus:OPERation:PTRansition . . . . . . . . 3-129

:STATus:OPERation:NTRansition . . . . . . . . 3-130

:STATus:PRESet . . . . . . . . . . . . . . . . . 3-131

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

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

:STATus:QUEStionable:ENABle . . . . . . . . . 3-134

:STATus:QUEStionable:PTRansition . . . . . . 3-135

:STATus:QUEStionable:NTRansition . . . . . . 3-136

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

3-12 SYSTEM SUBSYSTEM . . . . . . . . . . . . . . 3-138

:SYSTem:ERRor? . . . . . . . . . . . . . . . . . 3-138

:SYSTem:LANGuage . . . . . . . . . . . . . . . 3-139

:SYSTem:PRESet . . . . . . . . . . . . . . . . . 3-140

:SYSTem:VERSion? . . . . . . . . . . . . . . . . 3-141

3-13 TRIGGER SUBSYSTEM . . . . . . . . . . . . . 3-142

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

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

:TRIGger:SEQuence3:SLOPe . . . . . . . . . . . 3-144

:TRIGger:SEQuence3:TYPE . . . . . . . . . . . 3-145

:TRIGger:SEQuence3:SOURce . . . . . . . . . . 3-146

3-14 TSWeep COMMAND . . . . . . . . . . . . . . . . 3-147

682XXB/683XXB SCPI PM 3-5

Tables of Contents (Continued)

3-15 UNIT SUBSYSTEM . . . . . . . . . . . . . . . . 3-148

:UNIT:FREQuency . . . . . . . . . . . . . . . . 3-148

:UNIT:TIME . . . . . . . . . . . . . . . . . . . . 3-149

3-6 682XXB/683XXB 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 682XXB/683XXB
Synthesized Signal Generators.

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 asterisk
in the command word. The common commands are fully defined in
IEEE 488.2.

IEEE 488.2
Mandated
Commands

The 682XXB/683XXB 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 St at u s E nable

∗

Command)

Sets the Standard Event Status Enable Register
bits. The binary weighted
used with this command must have a value between

0 to 255. Refer to “Status System Programming” in
Chapter 2.

<NR1> data parameter

ESE? (Standard Event Status Enable Query) ?

∗

Returns the value of the Standard Event Status En­able Register in
tem Programming” in Chapter 2.

ESR? (Standard Event St at us Re gister Query)

∗

Returns the value of the Standard Even t Status Reg­ister in
Standard Event Status Register. Refer to “Status
System Programming” in Chapte r 2.

<NR1> format. This command clears the

<NR1> format. Refer to “Status Sys-

682XXB/683XXB SCPI PM 3-7

PROGRAMMING COMMON
COMMANDS COMMANDS

∗IDN? (Identification Query)

This query returns an instrument identification
string in IEEE- 488.2 specified
fields separa ted by commas). The fields are:

facturer>, <Model>, <Serial #>, <Firmware revision

; where the actual model number, serial num-

level>

ber, and firmware version of the 682XXB/683XXB
queried 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 (four

<manu-

<NR1> format.

RST (Reset Command)

∗

Resets the 682XXB/683XXB to a pre-defined condi­tion with all user programmable parameters set to
their default values. These default parameter values
are listed under each SCPI command in this man­ual. This command does not affect the Output
Queue, Status Byte Register, Standard Event Regis­ter, or calibration data.

NOTE

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

ing, save it as a stored setup using the ∗
command before issuing the ∗RST command.

SRE sp <nv> (Service Request Enab l e C om-

∗

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
resets the register. Refer to “Status System Program­ming” in Chapter 2.

SRE? (Service Request Enable Q uery )

∗

Returns the value of the Service Request Enable
Register in

<NR1> format. Bit 6 is always zero.

SAV

3-8 682XXB/683XXB 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

682XXB/683XXB self-test re­quires RF output power to be
on. Always disconnect sensi­tive equipment fro m the unit
before performing a self-test.

Causes the 682XXB/683XXB to perform a full inter­nal self-test. Status messages which indicate self­test results 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 C omma nd)

∗

This command su spends the execution of any fur­ther commands or queries until all operations for
pending commands are completed. For example, t he
command ∗
eration. It causes the 682XXB/683XXB to start a
sweep and wait until the sweep is complete before
executing the next command.

TRG;∗WAI permits synchronous sweep op-

Optional
Common
Commands

The 682XXB/683XXB implements the following
IEEE 488.2 optional common commands:

OPT? (Option Identification Query)

∗

This command returns a string identifying any de­vice options.

RCL sp <n> (Recall Stored St at e)

∗

This command restores the 682XXB/683XXB to a
front panel setup state that was previously saved to
local (instrument) memory using the ∗
(below). The ∗
<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 lo­cal (instrument) memory. The new stored setup state
will be assigned the Setup Number specified by
where

n shall be in the range of 0 to 9.

RCL sp <n> command restor es setup

SAV command

<n>,

682XXB/683XXB SCPI PM 3-9

PROGRAMMING SUBSYSTEM
COMMANDS COMMANDS

∗TRG (Trigger Co mmand)

Triggers instrument if
data parameter is
TRIGger subsystem commands.)

Performs the same function as the Group Execute
Trigger

<GET> command defined in IEEE 488.1.

:TRIGger:SOURce command

BUS. Refer to INITiate and

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

The following information is provided for each subsystem command.

The path from the subsystem root command.
The data parameters used as arguments for the command. This

includes the parameter type, the available parameter choices, the
range for numeric parameters, and the default parameter that is
set by the ∗

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

mation about the command and its usage.

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

RST command.

:INITiate:CONTinuous.

3-10 682XXB/683XXB 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:

Associated
commands:

:ABORt

Sets 682XXB/683XXB trigger system to idle state.

:TRIGger and :INITiate

682XXB/683XXB 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 P ARAMETER FORM NOTES

:CONTrol

:BLANking

:POLarity NORMa l|INVerted Default: NORmal

:PENLift

:POLarity NORMa l|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 rear panel RETRACE BLANK OUT

blanking signal output 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:BLANkin g:POLarity?

Examples: :CONTrol:BLANki ng:POLarity sp INVerted

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

:CONTrol:BLANkin g:POLarity?

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

3-12 682XXB/683XXB 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 rear panel PENLIFT OUT signal as fol­lows:

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

Query Form:

Examples: :CONTrol:PENLift:POLarity sp INVerted

:CONTrol:PENLift:POLarity?

Set the penlift relay contacts to be normally closed.

:CONTrol:PENLift:POLarity?

Requests the currently programmed state of the penlift
relay contacts.

682XXB/683XXB 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

sweep ramp as follows:

OUT
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:

Examples: :CONTrol:RAMP:REST sp STOP

:CONTrol:RAMP:REST?

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 682XXB/683XXB SCPI PM

PROGRAMMING :CONTrol SUBSYSTEM
COMMANDS :RAMP[:STATe]

:CONTrol

:RAMP

[:STA Te]

Parameters: ON | OFF | 1 | 0

Type: <boolean>

Default: OFF

Description: Turns the rear panel HORIZ OUT sweep ramp signal

on/off.

Query Form:

Examples: :CONTrol:RAMP:STATe sp ON

:CONTrol:RAMP[:STATe]?

Turns the rear panel HORIZ OUT sweep ramp signal on.

:CONTrol:RAMP:STATe?

Requests the currently programmed state of the HORIZ

sweep ramp signal.

OUT

682XXB/683XXB 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:

Examples: :CONTrol:RAMP:TIME sp 100 ms

:CONTrol:RAMP:TIME?

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

:CONTrol:RAMP:TIME?

Requests the currently programmed time for the HORIZ

sweep ramp signal.

OUT

3-16 682XXB/683XXB 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?

682XXB/683XXB 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 P ARAMETER 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 display
on/off.

Query Form

Example: :DISPlay:TEXT:STATe sp OFF

:DISPlay:TEXT:STATe?

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

3-18 682XXB/683XXB SCPI PM

PROGRAMMING :INITiate SUBSYSTEM
COMMANDS [:IMMediate]

3-8

INITIATE SUBSYSTEM

The :INIT iate subsystem controls the state of the 682XXB/683XXB trig­ger system. The subsystem commands and parameters are described
below. The
commands, comprise the Trigger Group of commands.

KEYWORD P ARAMETER FORM NOTES

:INITiate

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

:INITiate

[:IMMediate]

Parameters: none

Description: Places the 682XXB/683XXB trigger system into the

:INITiate commands, along with the :ABORt and :TRIGger

armed state from the idle state. If trigger system is
not in idle state, or if

produce error –213.

:INITiate:CONTinuous is ON, will

Query Form: None

Example:

Associated
commands:

NOTES:

:INITiate or :TSWeep is received by the 682XXB/683XXB, all

When
sweep-related parameters are checked for compatibility and bounds.
The system will not arm is any errors exist. These errors are reported
in the error queue.

:INITiate:IMMedia te

Sets 682XXB/683XXB trigger to the armed state.

:ABORt and :TRIGger

682XXB/683XXB SCPI PM 3-19

PROGRAMMING :INITiate SUBSYSTEM
COMMANDS :CONTinuous

:INITiate

:CONTinuous

Parameters: ON | OFF | 1 | 0

Type: <boolean>

Default: OFF

Description: Continuously rearms the 682XXB/683XXB trigger sys-

tem after completion of a triggered sweep.

Query Form:

Examples: :INITiate:CONTinuous sp ON

Associated
commands:

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

:ABORt;:INITiate or :TSWeep .

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

–213, “Init ignored, trigger not idle”

:INITiate:CONTinuous?

Sets 682XXB/683XXB trigger to continuously armed
state.

:ABORt and TRIGger

3-20 682XXB/683XXB SCPI PM

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS [:STATe]

3-9

OUTPUT SUBSYSTEM

The :OUTPut subsystem controls the 682XXB/683XXB 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
commands and parameters are described below.

KEYWORD PARAMETER FORM NOTES

:OUTPut

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

:RETRace <boolean> Default: OFF

:IMPedance?

:OUTPut

[:STA Te]

Parameters: ON | OFF | 1 | 0

Type: <boolean>

Default:

OFF (see note below)

Description: Turns 682XXB/683XXB RF output power on/off.

Query Form

Example: :OUTPut:STATe sp ON

NOTE:
The SCPI programmin g mode reset default for RF output power state

is OFF.
The 682XXB/683XXB Native GPIB programming mode reset default
for the RF output power state is ON.

:OUTPut[:STATe]?

Turns 682XXB/683XXB RF output power on.

682XXB/683XXB SCPI PM 3-21

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :PROTection

:OUTPut

:PROTection

Parameters: ON | OFF | 1 | 0

Type: <boolean>

Default: ON

Description: ON causes the 682XXB/683XXB RF output to be

turned off (blanked) during frequency changes in CW
or step sweep mode.
(unblanked).

OFF leaves RF output turned on

Query Form

Example: :OUTPut:P ROTect ion sp OFF

:OUTPut:PROTection?

Causes the 682XXB/683XXB RF output signal to be
left on during frequency changes in CW or step sweep
mode.

:OUTPut:PROTection?

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

3-22 682XXB/683XXB SCPI PM

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :PROTection:RETRace

:OUTPut

:PROTection

:RETRace

Parameters: ON | OFF | 1 | 0

Type: <boolean>

Default: OFF

Description: ON causes the 682XXB/683XXB RF output to be

turned off d uring sweep r etrace.
turned on.

OFF leaves RF output

Query Form

Example: :OUTPut: PROTection:RETRace sp ON

:OUTPut:PROTection:RETRace?

Turns the 682XXB/683XXB RF output off during
sweep retrace.

:OUTPut:PROTection:RETRace?

Requests the currently programmed state of the
682XXB/683XXB RF output during sweep retrace.

682XXB/683XXB SCPI PM 3-23

PROGRAMMING :OUTPut SUBSYSTEM
COMMANDS :IMPedance?

:OUTPut

:IMPedance?

Description: Queries the 682XXB/683XXB RF output impedance.

The impedance is nominally 50 ohms and is not set­table.

Query Form

:OUTPut:IMPedance?

3-24 682XXB/683XXB SCPI PM

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

3-10

SOURCE SUBSYSTEM

:SOURce Subsystem Commands (1 of 4)

KEYWORD P ARAMETER FORM NOTES

[:SOURce]

:AM

:CORRection

The [:SOURce] subsystem provides control of a majority of the 682XXB/
683XXB 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 table
contained on this and the following three pages. The subsytem com­mands are described in detail on following pages.

Note that the
ments in the

:LOGSens
:SENSitivity
:LOGDepth
:INTernal

:WAVE

:FREQuency
:DEPTh
:EXTernal

:IMPedance
:SOURce
:STATe
:TYPE

[:STATe]
:CSET

:SELect

[:SOURce] keyword is optional for all command state-

: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

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

:FM

:INTernal

:WAVE

:FREQuency
:DEViation
:MODE
:BWIDth
:EXTernal

:IMPedance
:SENSitivity
:SOURce
:STATe

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: SINE

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

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

682XXB/683XXB SCPI PM 3-25

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (2 of 4)

KEYWORD PARAMETER FORM NOTES

[:SOURce]

:FREQuency

[:CW | :FIXed]

STEP

[:INCRement]
CENT er
:MODE
:SPAN

:FULL
:STARt
:STOP
:MULTiplier

<numeric_value>

<numeric_value>
<numeric_value>
CW |FIXed| SWEep[1] | SWCW | ALSW
<numeric_value>

<numeric_value>
<numeric_value>
<numeric_value>

Default: (MIN+MAX)/2

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

Default: MAX–MIN

Default: MIN
Default: MAX
Default: 1

:MARKer<n>

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

:PM

:BWIDth
:DEViation
:INTernal

:WAVE

:FREQuency
:EXTernal

:IMPedance
:SENSitivity
:SOURce
:STATe

<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>

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 682XXB/683XXB SCPI PM

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (3 of 4)

KEYWORD P ARAMETER FORM NOTES

[:SOURce]

:POWer

[:LEVel]

[:IMMediate]

[:AMPLitude]

:STEP
[:INCRement]

ALTernate

:ALC

:GAIN

:STEP

[:INCRement]

:SOURce

:ATTe nuation

:STEP

[:INCRement]

:AUTO

:DISPlay

:OFFSet

:STATe

:SLOPe

:STEP

[:INCRement]
:STATe
:PIVot

:MODE

:CENTer
:SPAN

:FULL

:STARt
:STOP

<numeric_value>

<numeric_value>
<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
<numeric_value>
<numeric_value>

<numeric_value>
<numeric_value>

Default: 0 dBm

Default: 0.1 dB
Default: 0 dBm

Default: 128

Default: 1
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

682XXB/683XXB SCPI PM 3-27

PROGRAMMING SOURCE
COMMANDS SUBSYSTEM

:SOURce Subsystem Commands (4 of 4)

KEYWORD P ARAMETER FORM NOTES

[:SOURce]

:PULM

:INTernal

:FREQuency
:POLarity
:SOURce

:STATe

:PULSe

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

:STARt

:STOP

:INCRement

:TIME

:SCAN

:STATe <boolean> Default: OFF

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

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

Default: 1 kHz
Default: NORMal
Default: INTernal1

Default: OFF

Default: 1
Default: 100 µs
Default: 1 ms
Default: 500 µs
Default: OFF
Default: 100 µs
Default: 100 µs
Default: 100 µs
Default: 1 ms

:SWEep<n>

:DIRection
:GENeration
:DWELl

:AUTO
:POINts
[:FREQuency]

:STEP
:POWer

:STEP
:TIME

:LLIMint

:AUTO

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

<numeric_value>

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

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

Default: 1,999,900 Hz

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

3-28 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:LOGSens

The [:SOURce]:AM command and its subcommands comprise the AM
Subsystem within the
the Amplitude Modulation function of the 682XXB/683XXB.

[: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.

:SOURce subsystem. These commands control

Query Form:

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

[:SOURce]:AM:LOGSens?

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.

682XXB/683XXB 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:

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

[:SOURce]:AM:SENSitivity?

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 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :AM:LOGDepth

[:SOURce]

:AM

:LOGDepth

Parameters: modulation depth (in dB)

Type: <NRf>

Range: 0 to 25 dB

Default: 3 dB

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

ternal AM Log mode.

Query Form:

Example: [:SOU Rce]:AM:LOGD epth sp 20 dB

[:SOURce]: AM:LOGDepth ?

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.

682XXB/683XXB 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 follows:

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

Query Form:

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

[:SOURce]:AM:INTernal:WAVE?

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 682XXB/683XXB 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:WA VE).

Query Form:

Example: [:SOU Rce]:AM:INTernal:FREQuenc y sp 50 kHz

[:SOURce]:A M:INTe rnal:FREQuency?

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

[:SOURce]:A M:INTer nal:FREQuency?

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

682XXB/683XXB 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:

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

[:SOURce]:AM:DEPTh?

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 682XXB/683XXB 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:

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

[:SOURce]:AM:EXTernal:IMPedance?

Sets the input impedance of the selected AM IN connector
to 600 ohms.

682XXB/683XXB 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

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

[:SOURce]:AM:EXTernal:SOURce?

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 682XXB/683XXB 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 682XXB/

683XXB RF output signal.

Query Form

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

[:SOURce]:AM:STATe?

Turns amplitude modulation on.

[:SOURce]:AM:STATe?

Requests currently programmed amplitude modulation
state (on/off).

682XXB/683XXB 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

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

[:SOURce]:AM:TYPE?

Selects the AM Log mode.

[:SOURce]:AM:TYPE?

Requests the currently programmed AM operating
mode.

3-38 682XXB/683XXB SCPI PM

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

The [:SOURce]:CORRection command and its subcommands comprise
the Correction Subsystem within the
mands are used to select and apply level flatness correction to the
682XXB/683XXB RF output. (Refer to "Leveling Operations" in Chap­ter 3 of the 682XXB/683XXB Synthesized Signal Generators 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.

:SOURce subsystem. These com-

Query Form

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

NOTE:

:CORRection:CSET:SELect is NONE, sending the command :CORRec-

If

tion:STATe ON

[:SOURce]:CORRection[:STATe]?

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

returns an error.

682XXB/683XXB 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 682XXB/683XXB output by
the command

[:SOURce]:CORRection:STATe sp ON.

Query Form

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

[:SOURce]:CORRection:CSET:SELect?

USER3

Selects user level flatness correction power-offset ta ble
#3.

3-40 682XXB/683XXB SCPI PM

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

The [:SOURce]:FM command and its subcommands comprise the FM
Subsystem within the
the Frequency Modulation function of the 682XXB/683XXB.

[:SOURce]

:FM

:INTernal

:WAVE

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

Type: <char>

Default: SINE

Description: Selects the modulating waveform (from the internal

:SOURce subsystem. These commands control

UNIForm

FM generator) for the internal FM function, as follows:

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

Query Form:

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

[:SOURce]:FM:INTernal:WAVE?

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.

682XXB/683XXB 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:

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

[:SOURce]:FM: INTer nal:FREQuency?

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

[:SOURce]:FM: INTerna l:FREQuency?

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

3-42 682XXB/683XXB 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

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

[:SOURce]:FM:DEViation?

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.

682XXB/683XXB 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

LOCKed[1] or LOCKed2 is set, the YIG phase-locked

If
loop is used in synthesizing the FM signal. If

Locked

the FM signal is obtained by applying the modulating
signal to the tuning coils of the YIG-tuned oscillator.

is set, the YIG phase-lock loop is disabled and

UN-

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 sy nthesis 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 682XXB/683XXB 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 maxi-

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

Query Form

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

[:SOURce]:FM:BWIDth?

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 (nar row or wide).

682XXB/683XXB 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 sel e cted (front panel

or rear panel)
values are 50 and 600 (ohms). The extended numeric
values

MIN or MAX may also be used.

FM IN connector. The two valid numeric

Query Form

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

[:SOURce]:FM:EXTernal:IMPedance?

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

3-46 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FM:SENSitivity

[:SOURce]

:FM

:SENSitivity

Parameters: sensitivity (in Hz/V)

Type: <NRf>

Range:

Default: 1 MHz/Volt

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

±

10 kHz/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

Query Form

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

[:SOURce]:FM:SENSitivity?

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.

682XXB/683XXB 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

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

[:SOURce]:FM:SOURce?

Selects the rear panel
ternal FM modulating signal source.

[:SOURce]:FM:SOURce?

Requests the currently programmed FM modulating
signal source.

FM IN

connector as the active ex-

3-48 682XXB/683XXB 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 682XXB/

683XXB RF output signal.

Query Form

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

[:SOURce]:FM:STATe?

Turns frequency modulation on.

[:SOURce]:FM:STATe?

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

682XXB/683XXB 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
mands control the frequency characteristics of the 682XXB/683XXB.

[:SOURce]

:FREQuency

[:CW | :FIXed]

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

Type: <nv>

Range: MIN to MAX (see notes below)

Default:

Description: Sets the RF output frequency of the 682XXB/683XXB

(MIN + MAX) / 2

to the value entered. Parameters
ment/decrement the frequency by the value set by

[:SOURce]:FREQuency:STEP:INCRement command.

:SOURce subsystem. These com-

UP | DOWN incre-

Query Form:

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

NOTES:
Keywords

ably; they also are optional and may be omitted.
MIN ≤ frequency ≥ MAX; values for the MINimum and MAXimum frequen-

cies for each 682XXB/683XXB model are listed in the table on the fol­lowing page.

The query
frequency to which the particular model 682XXB/683XXB may be pro­grammed. Similarly, the query
will return the lower frequency limit.

:CW and :FIXed are equivalent and may be used interchange-

[:SOURce]:FREQuency[:CW]?

or:

Sets the RF output frequency to 3 GHz.

[:SOURce]:FREQuency:CW?

Requests the current value of the frequency parameter.

[:SOURce]:FREQuency:CW? sp MAX will return the upper

:FREQ

sp

3 GHz

[:SOURce]:FREQuency:CW? sp MIN

3-50 682XXB/683XXB SCPI PM

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

Model 682XXB/683XXB MINimum and MAXimum Frequencies

Model MINimum MAXimum

68237B/68337B 2 GHz 20 GHz
68245B/68345B 500 MHz 20 GHz
68247B/68347B 10 MHz 20 GHz
68253B/68353 B 2 GHz 26.5 GHz
68255B/68355B 500 MHz 26.5 GHz
68259B/68359B 10 MHz 26.5 GHz
68263B/68363B 2 GHz 40 GHz
68265B/68365B 500 MHz 40 GHz
68269B/68369B 10 MHz 40 GHz
68275B/68375B 500 MHz 50 GHz
68277B/68377B 10 MHz 50 GHz
68285B/68385B 500 MHz 60 GHz
68287B/68387B 10 MHz 60 GHz
68295B/68395B 500 MHz 65 GHz
68297B/68397B 10 MHz 65 GHz

682XXB/683XXB 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: 1 kHz to (MAX – MIN) (see note below)

Default:

Description: Sets the step increment size used with the

0.1 GHz

:FREQuency:CW command.

Query Form:

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

NOTE:
For 682XXB/683XXBs equipped with Option 11, the minimum value

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

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

sp

:INCRement

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 fre­quency parameter.

:FREQ:STEP

:FREQ:STEP?

1 MHz

sp

1 MHz

3-52 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:CENTer

[:SOURce]

:FREQuency

:CENTer

Parameters: frequency ( in Hz)

Type: <NRf>

Range: MIN to MAX (See Notes)

Default:

Description: Sets the 682XXB/683XXB RF output center frequency

(MIN + MAX) / 2

to the value entered.
are coupled values. Entering the value for one will
cause the other to be recalculated. (See notes under

:FREQuency :SPAN)

:CENTER and :SPAN frequencies

Query Form:

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

NOTES:
Stepped Sweep Center Range =

Analog Sweep Center Range =

[:SOURce]:FREQuency:CENTer?

Set the 682XXB/683XXB RF output center frequency
to 4GHz.

[:SOURce]:FREQuency:CENTer?

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

MIN to MAX, where:
MIN = MIN + minimum step size
MAX = MAX – minumum step size

MIN to MAX, where;
MIN = MIN + (minimum analog span)/2
MAX = MAX – (minimum analog span)/2

682XXB/683XXB SCPI PM 3-53

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:MODE

[:SOURce]

:FREQuency

:MODE

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

Type: <char>

Default: CW

Description: Specifies which command subsystem controls the

682XXB/683XXB frequency, as follows:

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

:SWEep[1] mode, output frequency is controlled by

In

:STARt, :STOP, CENTer, and :SPAN commands.
:SWEep and :SWEep1may be used interchangeably.

(see notes)

Query Form:

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

NOTES:

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

In
ues for the following
:SPAN, or, :STARt and :STOP.

Setting ALSW will cause the 682XXB/683XXB to do alternate sweeping
when properly triggered.

Setting
Setting

command statement
A query returns CW.

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

[:SOURce]:FREQuency:MODE?

Specifies that the 682XXB/683XXB RF frequency out­put is to be controlled by

commands.

FIXed
[:SOURce]:FREQuency:MODE?

Requests the currently selected programming mode for
frequency control.

:FREQuency subsystem commands: :CENTer and

:FREQuency:MODE CW;:CONTrol:RAMP ON

[:SOURce]:FREQuency:CW |

3-54 682XXB/683XXB 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:

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

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

value for
lated.

At ∗

:SPAN causes the values for :STARt and :STOP to be recalcu-

RST, :SPAN = Fmax – Fmin

[:SOURce]:FREQuency:SPAN?

or:

Set the SWEep[1] sweep span to 2 GHz.
[:SOURce]:FREQuencySPAN:?

Requests the current value for SWEep[1] sweep span.

:FREQ:SPAN sp 2 GHz

682XXB/683XXB 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:

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

None

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

3-56 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:SPAN

[:SOURce]

:FREQuency

:SPAN2

Parameters: frequency (in Hz)

Type: <NRf>

Range: 1 kHz to (MAX – MIN)

Default:

Description: Sets sweep span for the alternate sweep to value en-

MAX – MIN

:SPAN and :CENTer are coupled values (see

tered.
notes below).

2

Query Form:

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

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

value for
lated.

At ∗

:SPAN causes the values for :STARt and :STOP to be recalcu-

RST, :SPAN = Fmax – Fmin

[:SOURce]:FREQuency:SPAN2?

or:

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

[:SOURce]:FREQuencySPAN2:?

Requests the current value of the sweep span for the al­ternate sweep.

:FREQ:SPAN2 sp 2 GHz

682XXB/683XXB SCPI PM 3-57

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

[:SOURce]

:FREQuency

:SPAN2

:FULL

Parameters: None

Description: Sets frequency span for the alternate sweep to (MAX –

)

MIN

(see notes under

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

Query Form:

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

None

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

3-58 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:STARt

[:SOURce]

:FREQuency

:STARt

Parameters: frequency (in Hz) | MIN

Type: <nv>

Range: MIN to MAX (See Notes)

Default:

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

MIN

tered. (

:FREQuency:CW | FIXed

MIN is defined in the notes under [:SOURce]

).

Query Form:

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

NOTES:
Stepped Sweep Start Range =

Analog Sweep Start Range =

[:SOURce]:FREQuency:STARt?

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

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

MIN to MAX, where:

MAX = MAX – 2 × minimum frequency step size

MIN to MAX, where;

MAX = MAX – minimum analog span

682XXB/683XXB 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:

Description: Sets start frequency for the alternate sweep to the

MIN

value entered. (

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

MIN is defined in the notes under

2

Query Form:

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

NOTES:
Stepped Sweep Start Range =

Analog Sweep Start Range =

[:SOURce]:FREQuency:STARt2?

Set the start frequency for the alternate sweep to

3.5 GHz .

[:SOURce]:FREQuency:STARt2?

Requests the current value for the alternate sweep start
frequency.

MIN to MAX, where:

MAX = MAX – 2 × minimum frequency step size

MIN to MAX, where;

MAX = MAX – minimum analog span

3-60 682XXB/683XXB 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:

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

MAX

MAX is defined in the notes under [:SOURce]

(

:FREQuency:CW | FIXed

).

Query Form:

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

NOTES:
Stepped Sweep Stop Range =

Analog Sweep Stop Range =

[:SOURce]:FREQuency:STOP?

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

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

MIN to MAX, where:

MIN = MIN + 2 × minimum frequency step size

MIN to MAX, where;

MIN = MIN + minimum analog span

682XXB/683XXB 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:

Description: Sets stop frequency for the alternate sweep to the

MAX

value entered. (

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

MAX is defined in the notes under

2

Query Form:

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

NOTES:
Stepped Sweep Stop Range =

Analog Sweep Stop Range =

[:SOURce]:FREQuency:STOP2?

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

[:SOURce]:FREQuency:STOP2?

Requests the current value for the alternate sweep stop
frequency.

MIN to MAX, where:

MIN = MIN + 2 × minimum frequency step size

MIN to MAX, where;

MIN = MIN + minimum analog span

3-62 682XXB/683XXB SCPI PM

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :FREQuency:MULTiplier

[:SOURce]

:FREQuency

:MULTiplier

Parameters: reference multiplier value | MIN | MAX

Type: <nv>

Range: 0.1 to 14; MIN = 0.1; MAX = 14

Default: 1

Description: Sets the value of the reference multiplier for the fre-

quency scaling function. This command affects all en­tered and displayed frequencies, but it does not affect
the output of the instrument.

Query Form:

Examples: [:SOURce]:FREQuency:MULTiplier sp 4

NOTES:
The coupling equation is:

Entered/Disp layed Frequency = (Hardware Frequency x Multiplier)

RST, the value is set to 1.

At ∗

[:SOURce]:FREQuency:MULTiplier?

Set the frequency scaling reference multiplier value to 4.

[:SOURce]:FREQuency:MULTiplier?

Requests the current value for the frequency scaling ref­erence multiplier.

682XXB/683XXB SCPI PM 3-63

PROGRAMMING [:SOURce] SUBSYSTEM
COMMANDS :MARKer<n>:AOFF

The [:SOURce]:MARKer command and its subcommands comprise the
Marker Subsystem within the
control the Frequency Marker function of the 682XXB/683XXB.

[:SOURce]

:SOURce subsystem. These commands

:MARKer<n>

:AOFF

Parameters: None

Description: Turns all markers off. This command is an event,

Query Form:

Examples: [:SOURce ]:MARKer:AO FF

NOTE:
A numeric suffix

mand headers. This specifies which of the 10 markers (1 to 10) is being
altered by the command. In some cases, the command function is
global to all 10 markers, such as the command
markers off). In these cases, the

(see note)

therefore there is no data parameter and no query
form.

None

Turn all markers off.

<n> may be appended to any of the MARKer com-

:MARKers<n>:AOFF (all

<n> in the command header is ignored.

3-64 682XXB/683XXB SCPI PM