Agilent Technologies N9340B Manual


Agilent N9340B
Spectrum Analyzer
Programmer’s Guide

Notices
© Agilent Technologies, Inc. 2009-2010
No part of this manual may be reproduced
in any form or by any means (including
electronic storage and retrieval or
translation into a foreign language) without
prior agreement and written consent from
Agilent Technologies, Inc. as governed by
United States and international copyright
laws.
Edition
Second Edition, April. 2010
Agilent Technologies, Inc.
No. 116 Tuo Xin West 1st Street
Hi-Tech Industrial Zone (South)
Chengdu 610041, China
Warranty
The material contained in this
document is provided “as is,” and is
subject to being changed, without
notice, in future editions. Further, to
the maximum extent permitted by
applicable law, Agilent disclaims 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 merchantability
and fitness for a particular purpose.
Agilent shall not be liable for errors
or for incidental or consequential
damages in connection 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 material in this
document that conflict with these
terms, the warranty terms in the
separate agreement shall control.
Restricted Rights Legend
U.S. Government Restricted Rights.
Software and technical data rights granted
to the federal government include only
those rights customarily provided to end
user customers. Agilent provides this
customary commercial license in Software
and technical data pursuant to FAR 12.211
(Technical Data) and 12.212 (Computer
Software) and, for the Department of
Defense, DFARS 252.227-7015 (Technical
Data - Commercial Items) and DFARS
227.7202-3 (Rights in Commercial Computer
Software or Computer Software
Documentation).
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.
Safety Notices
CAUTION
A CAUTION 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 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
indicated conditions are fully
understood and met.
Software Revision
This guide is valid for Version A.01.10 and
above of the N9340B handheld spectrum
anyalzer firmware.

N9340B Programmer’s Guide
In This Guide…
This guide contains programming information for the
N9340B Spectrum Analyzer.
1 Getting Started
Prepare for the remote control.
2 Programming Fundamentals
A quick overview of the SCPI programming.
3StatusRegisters
Introduction of the status registers.
4 Programming Example
How to accomplish the basic applications in programming.
5 Command Reference
Describe every programming command ant the related
softkeys’ functions in detail.
For more information about N9340B handheld spectrum
analyzer, please refer to
www.agilent.com/find/n9340b

N9340B Programmer’s Guide

N9340B Programmer’s Guide
Contents
1 Getting Started 1
Remotely Operating Your N9340B 2
2 Programming Fundamentals 9
Overview 10
Command Categories 12
Command Syntax 13
Creating Valid Commands 15
Program and Response Messages 16
Parameters in Commands 17
3StatusRegisters 19
Overview 20
How to use the Status Registers 23
Status Register System 25
4 Programming Example 31
Overview 32
Programming in C using the VTL 33
Checking USB Connection 39
Using C with Marker Peak Search and Peak Excursion 40
Using Marker Delta Mode and Marker Minimum Search 44
Measuring Phase Noise 48

N9340B Programmer’s Guide
Contents
5 Command Reference 51
IEEE Common Commands 52
CALCulate Subsystem 56
Limit Line Subsection 56
CALCulate:MARKer Subsection 57
DEMOdulation Subsystem 62
DISPlay Subsystem 63
INITiate Subsystem 65
INSTrument Subsystem 67
MEASure Subsystem 68
OBW Subsection 68
ACPR Subsection 69
Channel Power Subsection 71
SEM Subsection 72
SENSe Subsystem 81
[:SENSe]:AVERage Subsection 81
[:SENSe]:BANDwidth Subsection 82
[:SENSe]:DETector Subsection 85
[:SENSe]:FREQuency Subsection 87
[:SENSe]:POWer Subsection 89
[:SENSe]:SWEep Subsection 90
SYSTem Subsystem 92
TGENerator Subsystem 94
TRACe Subsystem 97
TRIGger Subsystem 98
UNIT Subsystem 100

s
Agilent N9340B Handheld Spectrum Analyzer
Programmer’s Guide
1
1
Getting Started
The purpose of this chapter is to serve as a reminder of
SCPI (Standard Commands for Programmable Instruments)
fundamentals to those who have previous experience in
programming SCPI. This chapter is not intended to teach
you everything about the SCPI programming language. If you
are using an optional programming compatibility modes, you
should refer to the manual that came with the option.

2 N9340B Programmer’s Guide
1 Getting Started
Remotely Operating Your N9340B
The N9340B provides both the USB and LAN connection
which allows you to set up a remote operation environment
with a controller computer. A controller computer could be a
personal computer (PC), a minicomputer. Some intelligent
instruments also function as controllers.
Computer Requirement for Remote Operation
Usually, you need to prepare an compatible PC with the
following requirements to set up a remote operation
environment:
Processor: 450 MHz Pentium®II or higher required
Operating system: Microsoft®Windows®XP or Home Editon,
Service Pack 1 or later; Windows®2000 Professional, service
pack 4 or later
Available memory: 128 MB or higher required
Available disk space: 175 MB or greater required

Getting Started 1
N9340B Programmer’s Guide 3
Connecting the N9340B to a PC via the USB Port
No extra driver is required to connect the N9340B via the
USB port to a PC. All you need is the Agilent IO libraries
suite and you can find this IO libraries suite in the
documentation CD in the shipment along with your N9340B.
Or download the IO libraries suite from Agilent website:
http://www.agilent.com/find/iolib
Refer to the following steps to finish the connection:
1Install Agilent IO libraries suite on your PC
2Switch on the N9340B
3Connect the analyzer to a PC with a USB cable.
Connecting instrument
Connecting PC

4 N9340B Programmer’s Guide
1 Getting Started
4After a while, the PC finds your N9340B as a new hardware
and prompts a message saying “Found new hardware...”. A
Found New Hardware Wizard is initiated immediately.
5Select Display a list...

Getting Started 1
N9340B Programmer’s Guide 5
7PC will detect the instrument automatically. The item “USB
Test and Measurement Device” displays in the pop- up window.
Select it and press Next.
The wizard will guide you through the rest of installation till
the driver is installed. Run Agilent IO libraries suite, the
N9340B will be detected automatically.

6 N9340B Programmer’s Guide
1 Getting Started
Connecting the N9340B to a PC via the LAN Port
No extra driver is required to connect the N9340B via the
LAN port to a PC. All you need is the Agilent IO libraries
suite and you can find this IO libraries suite in the Product
CD N9340B Help Kit in the shipment. Or download the IO
libraries suite from the website:
http://www.agilent.com/find/iolib
Please refer to the following steps to finish the connection:
1Switch on the analyzer.
2Connect the spectrum analyzer to a PC with a LAN cable.
3Press [SYS] > {Setting} > {IP Admin} > {IP address} to set IP
address for the instrument. For example, set “10.0.0.5” as the
IP address for the instrument. Press {Apply} as
4Run Agilent Connection Expert in IO libraries suite.
Right- click on the LAN (TCPIP0) icon, select “Add Instrument’
in the pop- up menu. The “Add LAN Instruments” window
displays for the IP configuration.
5Select “Add Address”, check “Use IP Address” in the window
and input the IP address as the instrument IP address you
set before.

Getting Started 1
N9340B Programmer’s Guide 7
6Press “Test Connection” to check the LAN connection. The
figure below indicates that the connection is ready.
7Check “*IDN query” and press “Identify Instrument”. The
instrument information shows the firmware revision and
product number. The analyzer is ready for your further
programming.

8 N9340B Programmer’s Guide
1 Getting Started

s
Agilent N9340B Handheld Spectrum Analyzer
Programmer’s Guide
9
2
Programming Fundamentals
Overview 10
Command Categories 12
Command Syntax 13
Creating Valid Commands 15
Program and Response Messages 16
Parameters in Commands 17
The purpose of this chapter is to serve as a reminder of
SCPI (Standard Commands for Programmable Instruments)
fundamentals to those who have previous experience in
programming SCPI. This chapter is not intended to teach
you everything about the SCPI programming language. If you
are using an optional programming compatibility modes, you
should refer to the manual that came with the option.

10 N9340B Programmer’s Guide
2 Programming Fundamentals
Overview
This section is not intended to teach you everything about
the SCPI (Standard Commands for Programmable
Instruments) programming language. The SCPI Consortium
or IEEE provides that level of detailed information.
Programming with SCPI requires knowledge of:
•Computer programming languages, such as C, C++, and
Microsoft®Visual Basic®.
•The language of your instrument. The N9340B employs
SCPI as its programming language.
The semantic requirements of your controller’s language
determine how the programming commands and responses
are handled in your application program.
SCPI Language Basics
SCPI is an ASCII- based instrument command language
designed for test and measurement instruments, with the
goal of reducing automatic test equipment (ATE) program
development time.
SCPI accomplishes this goal by providing a consistent
programming environment for instrument control and data
usage. This consistent programming environment is achieved
by the use of defined program messages, instrument
responses, and data formats across all SCPI instruments.
By providing a consistent programming environment,
replacing one SCPI instrument with another SCPI instrument
in a system will usually require less effort than with
non- SCPI instrument.
SCPI is not a standard which completely provides for
interchangeable instrumentation. SCPI helps move toward
interchangeability by defining instrument commands and
responses, but not functionality, accuracy, resolution, etc.

Programming Fundamentals 2
N9340B Programmer’s Guide 11
Common Terms used in this Book
The SCPI Consortium or IEEE can provide detailed
information on the subject of SCPI programming. Refer to
IEEE Standard 488.1- 1987, IEEE Standard Digital Interface
for Programmable Instrumentation. New York, NY, 1987, or
to IEEE Standard 488.2- 1992, IEEE Standard Codes,
Formats, Protocols and Common Commands for Use with
ANSI/IEEE Std 488.1- 1987. New York, NY, 1992.
Terms Description
Controller Any computer used to communicate with an instrument. A
controller can be a personal computer (PC), a minicomputer, or a
plug- in card in a card cage. Some intelligent instruments can also
function as controllers.
Instrument Any device that implements SCPI. Most instruments are electronic
measurement or stimulus devices, but this is not a requirement.
Similarly, most instruments use a GPIB or RS- 232 or USB
interface for communication. The same concepts apply regardless
of the instrument function or the type of interface used.
Command An instruction. You combine commands to form messages that
control instruments to complete a specified task. In general, a
command consists of mnemonics (keywords), parameters and
punctuation.
Query A special type of command. Queries instruct the instrument to
make response data available to the controller. Query keywords
always end with a question mark, ? .

12 N9340B Programmer’s Guide
2 Programming Fundamentals
Command Categories
The SCPI command falls into two categories:
•Subsystem commands that simulate front panel keystrokes
•Common commands that are unique and have no front
panel equivalent
Use a computer to control the instrument (but operate the
power/standby switch manually). Computer programming
procedures for the instrument involve selecting a
programming statement and then adding the specified
programming codes to that statement to achieve the desired
operating conditions.
For more specific command instructions, please refer to
Chapter 5, “Command Reference,” starting on page 51.

Programming Fundamentals 2
N9340B Programmer’s Guide 13
Command Syntax
A command consists of mnemonics (keywords), parameters
and punctuation. Before you start to program your signal
generator, familiarize yourself with the standard notation of
each of them.
Command
Mnemonics
(keywords)
Many commands have both a long and a short form: use either
one. (a combination of the two is not allowed). Consider the
:FREQuency command for example:
•Short form :FREQ
•Long form :FREQUENCY
SCPI is not case sensitive, so fREquEncy is just as valid as
FREQUENCY, but FREQ and FREQUENCY are the only valid forms
of the FREQuency command.
In this documentation, upper case letters indicate the short form
of the keyword. The lower case letters indicate the long form of
the keyword.
Punctuation •A vertical bar "|" dictates a choice of one element from a list.
For example: <A>|<B> indicates that either A or B can be
selected, but not both.
•Square brackets "[ ]" indicates that the enclosed items are
optional.
•Angle brackets "< >" indicates a variable items to be entered to
represent user choices.
•A question mark "?" after a subsystem command indicates that
the command is a query. The returned information, <value>
varies in format according to the type of the field.
Separator •A colon ":" seperates keywords of different levels. The colon
before the root keyword is usually omitted.
•A space separates a keyword and a parameter, as well as a
parameter and a unit.

14 N9340B Programmer’s Guide
2 Programming Fundamentals
Command Statement Rules Overview
Besides the standard notation of SCPI described above,
please remember the following rules in programming:
• command statements read from left to right
• use either long form or short form of keywords, but do
not use both
• no separating space between the keywords, only use a
colon to separate keywords of different levels
• always separating a keyword from a variable with a space
•always separating a variable from its unit with a space (if
variable has a unit).
Command Example
A typical command is made up of key words set off by
colons. The key words are followed by parameters that can
be followed by optional units.
Example 1 :TRIGger:SEQuence:VIDeo:LEVel 2.5V
The instrument does not distinguish between upper and
lower case letters. In the documentation, upper case letters
indicate the short form of the key word. The upper and
lower case letters, together, indicate the long form of the key
word. Either form may be used in the command.
Example 2 :Trig:Seq:Vid:Lev 2.5V is the same as
:trigger:sequence:video:level 2.5V.
NOTE The command :TRIGG:Sequence:Video:Level 2.5V is not
valid because :TRIGG is neither the long, nor the short form of the
command.