Agilent Technologies X Series Manual

Agilent Technologies
Agilent X-Series
Signal Analyzer
X-Series Programmer’s
Guide
This manual provides documentation for the
following X-Series Analyzers:
MXA Signal Analyzer N9020A
EXA Signal Analyzer N9010A

Notices
© Agilent Technologies, Inc. 2008
No part of this manual may be reproduced
in any form or by any means (including
electronic storage and retrieval or transla-
tion into a foreign language) without prior
agreement and written consent from Agi-
lent Technologies, Inc. as governed by
United States and international copyright
laws.
Manual Part Number
N9020-90084
Supersedes:N9020-90077
Print Date
August 2008
Printed in USA
Agilent Technologies, Inc.
1400 Fountaingrove Parkway
Santa Rosa, CA 95403
Warranty
The material contained in this doc-
ument is provided “as is,” and is
subject to being changed, without
notice, in future editions. Further,
to the maximum extent permitted
byapplicablelaw,Agilentdisclaims
all warranties, either express or
implied, with regard to this manual
and any information contained
herein, including but not limited to
the implied warranties of mer-
chantability and fitness for a par-
ticular purpose. Agilent shall not
be liable for errors or for incidental
or consequential damages in con-
nection with the furnishing, use, or
performance of this document or of
any information contained herein.
Should Agilent and the user have a
separate written agreement with
warranty terms covering the mate-
rial in this document that conflict
with these terms, the warranty
terms in the separate agreement
shall control.
Technology Licenses
The hardware and/or software described
in this document are furnished under a
license and may be used or copied only in
accordance with the terms of such license.
Restricted Rights Legend
If software is for use in the performance
of a U.S. Government prime contract or
subcontract, Software is delivered and
licensed as “Commercial computer soft-
ware” as defined in DFAR 252.227-7014
(June 1995), or as a “commercial item” as
defined in FAR 2.101(a) or as “Restricted
computer software” as defined in FAR
52.227-19 (June 1987) or any equivalent
agency regulation or contract clause. Use,
duplication or disclosure of Software is
subject to Agilent Technologies’ standard
commercial license terms, and non-DOD
Departments and Agencies of the U.S.
Government will receive no greater than
Restricted Rights as defined in FAR
52.227-19(c)(1-2) (June 1987). U.S. Gov-
ernment users will receive no greater than
Limited Rights as defined in FAR 52.227-
14 (June 1987) or DFAR 252.227-7015
(b)(2) (November 1995), as applicable in
any technical data.
Safety Notices
CAUTION:
A CAUTION notice denotes a
hazard. It calls attention to an
operating procedure, practice, or
the like that, if not correctly per-
formed or adhered to, could result
in damage to the product or loss of
important data. Do not proceed
beyond a CAUTION notice until
the indicated conditions are fully
understood and met.
WARNING:
A WARNING notice denotes a
hazard. It calls attention to an
operating procedure, practice,
or the like that, if not correctly
performed or adhered to, could
result in personal injury or
death. Do not proceed beyond a
WARNING notice until the indi-
cated conditions are fully
understood and met.
Trademark
Acknowledgements
Microsoft “ is a U.S. registered
trademark of Microsoft
Corporation.
Windows “ and MS Windows “
are U.S. registered trademarks
of Microsoft Corporation.
Adobe Reader “ is a U.S.
registered trademark of Adobe
System Incorporated.
Java™ is a U.S. trademark of
Sun Microsystems, Inc.
MATLAB “ is a U.S. registered
trademark of Math Works, Inc.
Norton Ghost™ is a U.S.
trademark of Symantec
Corporation.

Warranty
This Agilent technologies instrument product is warranted against defects in material
and workmanship for a period of one year from the date of shipment. during the
warranty period, Agilent Technologies will, at its option, either repair or replace
products that prove to be defective.
For warranty service or repair, this product must be returned to a service facility
designated by Agilent Technologies. Buyer shall prepay shipping charges to Agilent
Technologies shall pay shipping charges to return the product to Buyer. However,
Buyer shall pay all shipping charges, duties, and taxes for products returned to Agilent
Technologies from another country.
Where to Find the Latest Information
Documentation is updated periodically. For the latest information about this analyzer,
including firmware upgrades, application information, and product information, see
the following URLs:
http://www.agilent.com/find/mxa
http://www.agilent.com/find/exa
To receive the latest updates by email, subscribe to Agilent Email Updates:
http://www.agilent.com/find/emailupdates
Information on preventing analyzer damage can be found at:
http://www.agilent.com/find/tips

Contents
5
1. Introduction to Programming X-Series Applications
What Programming Information is Available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using Embedded Help for Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Using the Help System on Your PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Help System Features Especially Useful for Programmers . . . . . . . . . . . . . . . . . . . . . . . 10
Communicating SCPI Using Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SCPI Measurement Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Measurement Group of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Common Measurement Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
STATus Subsystem (Remote Only Commands) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
:STATus Subsystem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
:STATus Subsystem Commands and Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2. Programming Fundamentals
SCPI Language Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Command Keywords and Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating Valid Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Special Characters in Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Parameters in Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Putting Multiple Commands on the Same Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Improving Measurement Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Turn off the display updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Use binary data format instead of ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Minimize the number of GPIB transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Consider using USB or LAN instead of GPIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Minimize DUT/instrument setup changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Avoid unnecessary use of *RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Avoid automatic attenuator setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Avoid using RFBurst trigger for single burst signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
N9071A: Optimize your GSM output RF spectrum switching measurement . . . . . . . . . 82
Making power measurements on multiple bursts or slots? Use CALCulate:DA-
TA<n>:COMPress? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3. Measurement Synchronization with LXI-B
IEEE 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Synchronizing Time on the MXA and MXG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Verifying Time Synchronization on the MXA and MXG . . . . . . . . . . . . . . . . . . . . . . . . 86
Peer to Peer Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
MXA Instrument Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Outputting LAN Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6
Contents
Configuring LXI Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Configuring an LXI Trigger Using SCPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Configuring an LXI Trigger Using the Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Verifying an LXI Trigger using LXI Interactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Configuring an LXI State Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Using the LXI Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Setting Up and Executing a List Sweep Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Synchronizing a List Sweep Measurement Between an MXA and an MXG . . . . . . . . . .96
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
4. Programming Examples
X-Series Spectrum Analyzer Mode Programing Examples . . . . . . . . . . . . . . . . . . . . . . . . .108
89601X VXA Signal Analyzer Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . .110
5. Installing Application Software
Installing Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Viewing a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Obtaining and Installing a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Missing and Old Measurement Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . .115

7
1Introduction to Programming
X-Series Applications
This chapter provides overall information regarding programming Agilent X-Series Signal
Analyzers with SCPI, and the how to use the programming documentation provided with
your product.

8Chapter 1
Introduction to Programming X-Series Applications
What Programming Information is Available?
What Programming Information is Available?
The following resources are available to help you create programs for automating your
X-Series measurements:
•X-Series Programmer’s Guide (this manual, N9020-90084):
—Chapter 1 , “Introduction to Programming X-Series Applications,” on page 7
The Introduction includes sections on the following programming topics:
—“What Programming Information is Available?” on page 8
—“Using Embedded Help for Programming” on page 10
—“Communicating SCPI Using Telnet” on page 13
—“SCPI Measurement Commands” on page 16
—“STATus Subsystem (Remote Only Commands)” on page 30
—Chapter 2 , “Programming Fundamentals,” on page 71 includes the following:
—“SCPI Language Basics” on page 71
—“Improving Measurement Speed” on page 78
—Chapter 3 , “Measurement Synchronization with LXI-B,” on page 85
—Chapter 4 , “Programming Examples,” on page 107
—Chapter 5 , “Installing Application Software,” on page 113
•Getting Started Guide (N9020-90074):
A copy of the Getting Started Guide is shipped with your analyzer, is accessible in the
Help system on the "Additional Documentation" page, and is also available online here:
http://cp.literature.agilent.com/litweb/pdf/N9020-90074.pdf
The Getting Started Guide has valuable sections related to programming including:
— Configuring instrument LAN Hostname, IP Address, and Gateway Address
— Using the Windows XP Remote Desktop to connect to the instrument remotely
— Using the Embedded Web Server Telnet connection to communicate SCPI
•Embedded Help in your Instrument - embedded Help provides SCPI command
parameters and other important details associated with measurements and all
front-panel and soft keys. See “Using Embedded Help for Programming” on page 10.
•User’s and Programmer’s Reference manuals - Printable PDF versions of User’s
References for all Measurement Applications are accessible in the instrument Help
system under the "Additional Documentation" link, and are also provided on the
Documentation CD ROM, and in the instrument here:
C:\Program Files\Agilent\SignalAnalysis\Infrastructure\Help\bookfiles
•Agilent Application Notes- Printable PDF versions of many Application Notes are
accessible in the instrument Help system under the "Additional Documentation" link,
and are also provided on the Documentation CD ROM, and in the instrument here:
C:\Program Files\Agilent\SignalAnalysis\Infrastructure\Help\otherdocs

Chapter 1 9
Introduction to Programming X-Series Applications
What Programming Information is Available?
•Agilent VISA User’s Guide - describes the Agilent Virtual Instrument Software
Architecture (VISA) library and shows how to use it to develop I/O applications and
instrument drivers on Windows PCs. Available online here:
http://cp.literature.agilent.com/litweb/pdf/5989-6135EN.pdf
This document is also provided on the Documentation CD ROM, and in the instrument
here:
C:\Program Files\Agilent\SignalAnalysis\Infrastructure\Help\otherdocs

10 Chapter 1
Introduction to Programming X-Series Applications
Using Embedded Help for Programming
Using Embedded Help for Programming
The embedded Help system in your analyzer contains context-sensitive reference
information for each Measurement Application installed. While using the instrument, just
push the green Help key to see the Help topic for the active function or key.
Using the Help System on Your PC
The Compiled Help Metafile (CHM) is also provided on the Documentation CD ROM for
access locally on your PC for reference. In Microsoft Windows, use Windows Explorer to
navigate to the <mode_name>.chm file on the CD ROM, and double-click the file to launch
Help.
Help System Features Especially Useful for Programmers
Help System Contents Pane
The following programming-specific features described below are shown in the Help
system Contents Pane (see Figure 1-1 on page 10) and explained below:
•“Help Topics” on page 11
•“List of Commands” on page 12
• A Section called “Remote Only Commands” may be shown.
Figure 1-1 Example Help System “Contents” Pane

Chapter 1 11
Introduction to Programming X-Series Applications
Using Embedded Help for Programming
Under the “Using Help” section, all lower “books” are SCPI reference sections sorted by
front-panel key “groups”, as marked on the front panel. For example “Marker Functions”
contains all the Marker-related hard keys.
Help Topics
Included in each Help topic are:
• Definitions for the current active function or Key
• SCPI Command parameters, including limits, presets, variables, and queries
• Associated Remote-Only commands (if used)
Figure 1-2 Example Help Topic - FFT Window

12 Chapter 1
Introduction to Programming X-Series Applications
Using Embedded Help for Programming
List of Commands
The List of Commands is an alphabetically sorted list of all commands in the current
measurement application. Each listing shown is a link to the specific Help Topic that
contains the command or query. See a partial example of a List of Commands in Figure 1-3
on page 12.
Figure 1-3 Example List of Commands
NOTE You can query the analyzer for all supported SCPI commands in the
current mode by sending the “SYST:HELP:HEAD?” query. For details on
how to query the instrument see “Communicating SCPI Using Telnet”
on page 13.

Chapter 1 13
Introduction to Programming X-Series Applications
Communicating SCPI Using Telnet
Communicating SCPI Using Telnet
You can easily communicate SCPI via a Telnet connection from your PC to the analyzer.
The following procedure describes connecting a PC with a Windows operating system to
the analyzer. You will need to know the IP address of the analyzer.
NOTE In addition to the procedure described below, you can open a Telnet
connection with the analyzer using an internet connection to the
Embedded Web Server. This procedure is described in the Getting
Started guide.
To initiate a Telnet session and communicate SCPI using the LAN connection to the
analyzer:
Step 1. Obtain the IP address of the analyzer: If you don’t know it, a good
way to find it is as follows:
• In your analyzer, using a mouse or the keyboard, on the Taskbar select Start, Run, and
enter “cmd” to open a DOS session.

14 Chapter 1
Introduction to Programming X-Series Applications
Communicating SCPI Using Telnet
• Enter the DOS command “ipconfig”, and press Enter, and the results should resemble
the window shown below. The IP Address is given under Ethernet adapter Local Area
Connection.
Step 2. Make sure the analyzer Telnet socket is On
•Press
System, I/O Config, SCPI LAN, and make sure SCPI Telnet (Port 5023) is toggled to
On.
Step 3. Test your connection over the LAN
• On your PC using Microsoft Windows, in the Taskbar select Start, Run, and enter “cmd”
to open a DOS session.
• Enter the DOS command “ping”, a single space and the IP address of the analyzer, and
press Enter, and the results should resemble the window shown below. If the LAN
connection is working, you will get statistics for Packets Sent and Packets Received.

Chapter 1 15
Introduction to Programming X-Series Applications
Communicating SCPI Using Telnet
Step 4. In the DOS window, type “telnet <your analyzer IP address>
5023”.
A Telnet window will open with a Welcome answerback from the
analyzer Host Name, and the command prompt will be shown as
“SCPI>”. You can enter any valid SCPI command at the prompt and
receive responses to queries sent.
NOTE You can query the analyzer for all supported SCPI commands in the
current mode by sending the “SYST:HELP:HEAD?” query.

16 Chapter 1
Introduction to Programming X-Series Applications
SCPI Measurement Commands
SCPI Measurement Commands
Specific analyzer commands for setup and initiation of measurements are provided in the
User’s and Programmer’s Reference and in the instrument Help system under the
:MEASure command and under the specific measurement Meas soft key.
Once measurement parameters have been correctly configured, in general, there are 2
methods of obtaining measurement results remotely: by using the Measure family of
commands, and by using common :CALCulate queries of data parameters.
Measurement Group of Commands
The Measure family of commands is comprised of the MEASure command that executes
the entire measurement, and other separate commands, CONFigure, FETCh, INITiate
and READ, which each accomplish only a part of the overall measurement. FETch and
READ are queries. You can optimize your measurements by creating programs which use
MEASure and CONFigure a minimum number of times, and concentrating on repeating
READ, INITiate, and FETCh commands. For more information on optimizing your
measurements see “Improving Measurement Speed” on page 78.
The following graphic illustrates the interactions between the Measurement family of
commands: MEASure, CONFigure, FETCh, INITiate and READ:
NOTE Not all measurements support all MEASure, CONFigure, FETCh,
INITiate and READ commands. See the User’s and Programmer’s
Reference for specific MEASure family command information.
READ
FETCh
INITiate
CONFigure
MEASure (use CONFigure DEFault)
Measurement
on, sets the
default state.
Initialize
taking of
data.
Current
acquired data
is calculated
and returned.
ABORt
returns to
this point vsd26
Start from
any instrument
state.
Measurement
on, waiting in
current state.
CONFigure NDEF
SENSe & CALCulate
commands change the
settings from the
defaults
INITiate:RESTart

Chapter 1 17
Introduction to Programming X-Series Applications
SCPI Measurement Commands
Measure Commands:
:MEASure:<measurement>[n]?
This is a fast single-command way to make a measurement using the factory default instrument
settings. These are the settings and units that conform to the Mode Setup settings (e.g. radio
standard) that you have currently selected.
• Stops the current measurement (if any) and sets up the instrument for the specified
measurement using the factory defaults
• Initiates the data acquisition for the measurement
• Blocks other SCPI communication, waiting until the measurement is complete before
returning results.
• If the function does averaging, it is turned on and the number of averages is set to 10, 25, or
50, depending upon the current measurement.
• After the data is valid it returns the scalar results, or the trace data, for the specified
measurement. The type of data returned may be defined by an [n] value that is sent with the
command.
The scalar measurement results will be returned if the optional [n] value is not included, or is
set to 1. If the [n] value is set to a value other than 1, the selected trace data results will be
returned. See each command for details of what types of scalar results or trace data results
are available.
ASCII is the default format for the data output. The binary data formats should be used for
handling large blocks of data since they are smaller and faster than the ASCII format. Refer
to the FORMat:DATA command for more information.
If you need to change some of the measurement parameters from the factory default settings you
can set up the measurement with the CONFigure command. Use the commands in the
SENSe:<measurement> and CALCulate:<measurement> subsystems to change the settings.
Then you can use the READ? command to initiate the measurement and query the results.
If you need to repeatedly make a given measurement with settings other than the factory
defaults, you can use the commands in the SENSe:<measurement> and
CALCulate:<measurement> subsystems to set up the measurement. Then use the READ?
command to initiate the measurement and query results.
Measurement settings persist if you initiate a different measurement and then return to a
previous one. Use READ:<measurement>? if you want to use those persistent settings. If you
want to go back to the default settings, use MEASure:<measurement>?.

18 Chapter 1
Introduction to Programming X-Series Applications
SCPI Measurement Commands
Configure Commands:
:CONFigure:<measurement>
This command stops the current measurement (if any) and sets up the instrument for the
specified measurement using the factory default instrument settings. It does not initiate the
taking of measurement data unless INIT:CONTinuous is ON. If you change any measurement
settings after using the CONFigure command, the READ command can be used to initiate a
measurement without changing the settings back to their defaults.
:CONFigure:NDEFault<measurement> stops the current measurement and changes to the
specified measurement. It does not change the settings to the defaults. It does not initiate the
taking of measurement data unless INIT:CONTinuous is ON.
The CONFigure? query returns the current measurement name.
Fetch Commands:
:FETCh:<measurement>[n]?
This command puts selected data from the most recent measurement into the output buffer. Use
FETCh if you have already made a good measurement and you want to return several types of
data (different [n] values, for example, both scalars and trace data) from a single measurement.
FETCh saves you the time of re-making the measurement. You can only FETCh results from the
measurement that is currently active, it will not change to a different measurement. An error is
reported if a measurement other than the current one, is specified.
If you need to get new measurement data, use the READ command, which is equivalent to an
INITiate followed by a FETCh.
The scalar measurement results will be returned if the optional [n] value is not included, or is set
to 1. See each command for details of what types of scalar results or trace data results are
available. The binary data formats should be used for handling large blocks of data since they are
smaller and transfer faster then the ASCII format. (FORMat:DATA)
FETCh may be used to return results other than those specified with the original READ or
MEASure command that you sent.

Chapter 1 19
Introduction to Programming X-Series Applications
SCPI Measurement Commands
INITiate Commands:
:INITiate:<measurement>
This command is not available for measurements in all the instrument modes:
• Initiates a trigger cycle for the specified measurement, but does not output any data. You
must then use the FETCh<meas> command to return data. If a measurement other than the
current one is specified, the instrument will switch to that measurement and then initiate it.
• For example, suppose you have previously initiated the ACP measurement, but now you are
running the channel power measurement. If you send INIT:ACP? it will change from channel
power to ACP and will initiate an ACP measurement.
• Does not change any of the measurement settings. For example, if you have previously
started the ACP measurement and you send INIT:ACP? it will initiate a new ACP
measurement using the same instrument settings as the last time ACP was run.
• If your selected measurement is currently active (in the idle state) it triggers the
measurement, assuming the trigger conditions are met. Then it completes one trigger cycle.
Depending upon the measurement and the number of averages, there may be multiple data
acquisitions, with multiple trigger events, for one full trigger cycle. It also holds off additional
commands on GPIB until the acquisition is complete.
READ Commands:
:READ:<measurement>[n]?
• Does not preset the measurement to the factory default settings. For example, if you have
previously initiated the ACP measurement and you send READ:ACP? it will initiate a new
measurement using the same instrument settings.
• Initiates the measurement and puts valid data into the output buffer. If a measurement other
than the current one is specified, the instrument will switch to that measurement before it
initiates the measurement and returns results.
For example, suppose you have previously initiated the ACP measurement, but now you are
running the channel power measurement. Then you send READ:ACP? It will change from
channel power back to ACP and, using the previous ACP settings, will initiate the
measurement and return results.
• Blocks other SCPI communication, waiting until the measurement is complete before
returning the results
If the optional [n] value is not included, or is set to 1, the scalar measurement results will be
returned. If the [n] value is set to a value other than 1, the selected trace data results will be
returned. See each command for details of what types of scalar results or trace data results
are available. The binary data formats should be used when handling large blocks of data
since they are smaller and faster then the ASCII format. (FORMat:DATA)

20 Chapter 1
Introduction to Programming X-Series Applications
SCPI Measurement Commands
Common Measurement Commands
Current Measurement Query (Remote Command Only)
This command returns the name of the measurement that is currently running.
Test current results against all limits (Remote Command Only)
Queries the status of the current measurement limit testing. It returns a 0 if the measured
results pass when compared with the current limits. It returns a 1 if the measured results
fail any limit tests.
Data Query (Remote Command Only)
Returns the designated measurement data for the currently selected measurement and
subopcode.
n = any valid subopcode for the current measurement. See the measurement command
results table for your current measurement, for information about what data is returned
for the subopcodes.
This command uses the data setting specified by the FORMat:BORDer and
FORMat:DATA commands and can return real or ASCII data. (See the format command
descriptions under Input/Output in the Analyzer Setup section.)
Calculate/Compress Trace Data Query
Returns compressed data for the currently selected measurement and sub-opcode [n].
n = any valid sub-opcode for that measurement. See the MEASure:<measurement>?
command description of your specific measurement for information on the data that can be
returned.
The data is returned in the current Y Axis Unit of the analyzer. The command is used with
Remote Command :CONFigure?
Example CONF?
Remote Command :CALCulate:CLIMits:FAIL?
Example CALC:CLIM:FAIL? queries the current measurement to see if it
fails the defined limits.
Returns a 0 or 1: 0 it passes, 1 it fails.
Remote Command :CALCulate:DATA[n]?
Remote Command Notes The return trace depends on the measurement.
In CALCulate:<meas>:DATA[n], n is any valid subopcode for the
current measurement. It returns the same data as the
FETCh:<measurement>? query where <measurement> is the
current measurement.