Agilent Technologies 8712ES, 8714ES, 8714ET Programmer's Manual

Programmer’s Guide

Agilent Technologies 8712ET/ES and 8714ET/ES

RF Network Analyzers

Part No. 08714-90015

Printed in USA

Print Date: June 2000

Supersedes: October 1999

© Copyright 1998-2000 Agilent Technologies, Inc.

Notice

The information contained in this document is subject to change without notice.

Agilent Technologies makes no warranty of any kind with regard to this material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

Agilent Technologies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Key Conventions

This manual uses the following conventions:

FRONT PANEL KEY analyzer (a “hardkey”).

: This represents a key physically located on the

Softkey : This indicates a “softkey”-- a key whose label is determined by the instrument’s firmware, and is displayed on the right side of the instrument’s screen next to the eight unlabeled keys.

Firmware Revision

This manual documents analyzers with firmware revisions E.06.00 and above.

ii Programmer’s Guide

GPIB Programming

This document is an introduction to programming your analyzer over the general purpose interface bus (GPIB). Its purpose is to provide concise information about the operation of the instrument under GPIB control.

It provides some background information on the GPIB and some short programming examples to demonstrate the remote operation of the analyzer.

Example programs can be run on the analyzer’s internal controller or on an external controller. These programs can be found in the following three locations:

• Example Programs Disk (included with the analyzer)— DOS Format : part number 08714-10003.

A LIF version of the Example Programs Disk is available, but is not shipped with your analyzer:

ExamplePrograms Disk – LIF Format part number 08714-10004.

Contact the nearest Agilent Technologies sales office for ordering information. A list of Agilent Technologies sales and service offices can be found in the “Specifications” chapter of the User’s Guide.

• Example Programs Guide (included with the analyzer): part number

08714-90016. (This document may not include all of the example programs found on the disk or on the Web site.)

• Web site http://www.agilent.com. Use the search function to find

Web pages related to 8712 example programs.

You should become familiar with the operation of your network analyzer before controlling it over GPIB. This document is not intended to teach programming or to discuss GPIB theory except at an introductory level.

Related information can be found in the following references:

• Information on making measurements with the analyzer is available in the analyzer’s User’s Guide.

• Information on HP Instrument BASIC is available in the

HP Instrument BASIC User’s Handbook.

Programmer’s Guide iii

• Information on HP BASIC programming is available in the manual set for the BASIC revision being used. For example: BASIC 7.0

Programming Techniques and BASIC 7.0 Language Reference.

• Example programs are described in Example Programs Guide.

• Information on using the GPIB is available in the Tutorial

Description of the Hewlett-Packard Interface Bus (HP literature no. 5021-1927).

• Information on using the analyzer to make automated measurements is available in Automated Measurements User’s Guide Supplement.

• Information on using the analyzer with a Local Area Network (LAN) is available in The LAN Interface User’s Guide.

Contact the nearest Agilent Technologies sales office for ordering information. A list of sales and service offices can be found in the

“Specifications” chapter of the User’s Guide.

iv Programmer’s Guide

Agilent Technologies 8712ET/ES and

8714ET/ES Network Analyzer

Documentation Map

The CDROM provides the contents of all of the documents listed below.

The User’s Guide shows how to make measurements, explains commonly-used features, and tells you how to get the most performance from the analyzer.

The LAN Interface User’s Guide Supplement shows how to use a local area network (LAN) for programming and remote operation of the analyzer.

The Automating Measurements User’s Guide

Supplement provides information on how to configure and control test systems for automation of test processes.

The Programmer’s Guide provides programming information including GPIB and SCPI command references, as well as short programming examples.

Programmer’s Guide v

vi

The Example Programs Guide provides a tutorial introduction using BASIC programming examples to demonstrate the remote operation of the analyzer .

The Service Guide provides the information needed to adjust, troubleshoot, repair, and verify analyzer conformance to published specifications.

The HP Instrument BASIC User’s Handbook describes programming and interfacing techniques using

HP Instrument BASIC, and includes a language reference.

The HP Instrument BASIC User’s Handbook

Supplement shows how to use HP Instrument BASIC to program the analyzer.

The Option 100 Fault Location and Structural Return

Loss Measurements User’s Guide Supplement provides theory and measurement examples for making fault location and SRL measurements. (Shipped only with Option 100 analyzers.)

The CATV Quick Start Guide provides abbreviated instructions for testing the quality of coaxial cables.

(Shipped only with Option 100 analyzers.)

The Cellular Antenna Quick Start Guide provides abbreviated instructions for verifying the performance of cellular antenna systems. (Shipped only with Option 100 analyzers.)


Contents

1. Introduction to GPIB Programming

Introduction to GPIB Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Bus Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Data Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Handshake Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Control Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Sending Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

GPIB Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Interface Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Programming Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Controller Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Response to Bus Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Message Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

2. Synchronizing the Analyzer and a Controller

Synchronizing the Analyzer and a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Overlapped Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Controlling Execution of Overlapped Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Using *WAI and *OPC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

3. Passing Control

Passing Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

4. Data Types and Encoding

Data Types and Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Numeric Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Character Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

String Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Expression Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Block Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Data Encoding for Large Data Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

ASCII Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Binary Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Byte Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Programmer’s Guide Contents-vii

Contents

5. Using Status Registers

Using Status Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

General Status Register Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

Condition Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

Transition Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

Event Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

Enable Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

How to Use Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6

The Service Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7

Generating a Service Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8

The Analyzer's Status Register Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10

Status Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

Device Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15

Limit Fail Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16

Questionable Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19

Standard Event Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-20

Measuring Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23

Averaging Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23

Operational Status Register Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24

Settings for STATus:PRESet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25

Analyzer Register Set Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26

6. Trace Data Transfers

Trace Data Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

Querying the Measurement Trace Using BASIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

Smith Chart and Polar Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4

Querying the Measurement Trace Using SICL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

Using Binary Data Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6

Trace Data Transfer Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

Transferring Data with IBASIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

Taking Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

CALC:DATA? versus TRACE:DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

Querying Single Data Points Using Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

Accessing Other Measurement Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

Applying Gain Correction Using the Memory Trace . . . . . . . . . . . . . . . . . . . . . . . . . .6-16

Performing Your Own Data Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18

Contents-viii Programmer’s Guide

Contents

Downloading Trace Data Using Binary Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

Internal Measurement Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Raw Data Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Ratio Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

Error Coefficient Arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23

Averaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Corrected Data Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Corrected Memory Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Trace Math Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Electrical Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Transform (Option 100 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Formatted Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Offset and Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27

7. Using Graphics

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Window Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

The Graphics Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

8. Front Panel Keycodes

Front Panel Keycodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Controlling the Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Monitoring the Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

9. Introduction to SCPI

Introduction to SCPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

The Command Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Sending Multiple Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Command Abbreviation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Implied Mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Numeric Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Character Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Boolean Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

Programmer’s Guide Contents-ix

Contents

String Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13

Block Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13

Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-14

IEEE 488.2 Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16

10. Menu Map with SCPI Commands

How to Enter Numbers and Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

How to Enter Frequency Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

How to Enter Time Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6

How to Enter Power and Voltage Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

How to Enter Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

Menu Map for 8712ET/ES and 8714ET/ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-9

11. SCPI Command Summary

Queries, Forms, and Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2

Parameter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3

SCPI Device Command Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4

12. SCPI Conformance Information

SCPI Conformance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2

SCPI Standard Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3

Instrument Specific Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-10

13. SCPI Error Messages

SCPI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-2

Command Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-3

Execution Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-8

Device-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-15

Query Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-17

Contents-x Programmer’s Guide

1 Introduction to GPIB

Programming

1-1

Introduction to GPIB Programming

Introduction to GPIB Programming


GPIB—the general purpopse interface bus—is a high-performance bus that connects individual instruments and computers together to make integrated test systems. The bus and its associated interface operations are defined by the IEEE 488.1 standard. The IEEE 488.2 standard defines the interface capabilities of instruments and controllers in a measurement system, including some frequently used commands.

GPIB cables provide the physical link between devices on the bus. There are eight data lines on each cable that are used to send data from one device to another. Devices that send data over these lines are called

Talkers. Listeners are devices that receive data over the same lines.

There are also five control lines on each cable that are used to manage traffic on the data lines and to control other interface operations.

Controllers are devices that use these control lines to specify the talker and listener in a data exchange. When a GPIB system contains more that one device with controller capabilities, only one of the devices is allowed to control data exchanges at any given time. The device currently controlling data exchanges is called the Active Controller.

Also, only one of the controller-capable devices can be designated as the

System Controller, the one device that can take control of the bus even if it is not the active controller. The network analyzer can act as a talker, listener, active controller or system controller at different times.

GPIB addresses provide a way to identify devices on the bus. Each device on the bus must have a unique address. The active controller uses GPIB addresses to specify which device talks and which device listens during a data exchange. Device addresses are set on each device using either a front-panel key sequence or a rear-panel switch.

To set the GPIB address on the analyzer, use the softkeys located in the

SYSTEM OPTIONS analyzer is 16.

GPIB menu. The factory default address for the

1-2 Programmer’s Guide

NOTE



Throughout this manual, the following conventions are used:

• Square brackets ( [ ] ) are used to enclose a keyword that is optional or implied when programming the command; that is, the instrument will process the command to have the same effect whether the option node is omitted or not.

• Parameter types ( < > ) are distinguished by enclosing the type name in angle brackets.

• A vertical bar ( | ) can be read as “or” and is used to separate alternative parameter options.

• A HARDKEY is a labeled button on the instrument front panel.

• A Softkey is one of the eight unlabeled buttons along the right side of the instrument display. The function of each Softkey is indicated next to the Softkey on the instrument display.

Programmer’s Guide 1-3


Bus Structure

Bus Structure

Data Bus

The data bus consists of eight lines that are used to transfer data from one device to another. Programming commands and data sent on these lines are typically encoded in the ASCII format, although binary encoding is often used to speed up the transfer of large arrays. Both

ASCII and binary data formats are available to the analyzer. In addition, every byte transferred over GPIB undergoes a handshake to ensure valid data.

Handshake Lines

A three-line handshake scheme coordinates the transfer of data between talkers and listeners. This technique forces data transfers to occur at the speed of the slowest device, and ensures data integrity in multiple listener transfers. With most computing controllers and instruments, the handshake is performed automatically, which makes it transparent to the programmer.



Bus Structure

Control Lines

The data bus also has five control lines that the controller uses both to send bus commands and to address devices:

IFC

ATN

SRQ

REN

EOI

Interface Clear. Only the system controller uses this line. When this line is true (low), all devices (addressed or not) are deselected, and go to an idle state.

Attention. The active controller uses this line to define whether the information on the data bus is a

command or is data. When this line is true (low), the bus is in the command mode and the data lines carry bus commands. When this line is false (high), the bus is in the data mode and the data lines carry device-dependent instructions or data.

Service Request. This line is set true (low) when a device requests service: the active controller services the requesting device. The analyzer can set the SRQ line true (low) for a variety of reasons.

Remote Enable. Only the system controller uses this line. When this line is set true (low), the bus is in the remote mode and devices are addressed either to listen or talk. When the bus is in remote mode and a device is addressed, the device receives instructions from GPIB rather than from its front panel (pressing the

Return to Local softkey returns the device to front panel operation). When this line is set false (high), the bus and all devices return to local operation.

End or Identify. This line is used by a talker to indicate the last data byte in a multiple byte transmission, or by an active controller to initiate a parallel poll sequence.

The analyzer recognizes the EOI line as a terminator and it sets the EOI line true (low) with the last byte of a message output (data, markers, plots, prints, error messages). The analyzer does not respond to parallel poll.



Sending Commands

Sending Commands

Commands are sent over the GPIB via a controller's language system, such as IBASIC, QuickBASIC or C. The keywords used by a controller to send GPIB commands vary among systems. When determining the correct keywords to use, keep in mind that there are two different kinds of GPIB commands:

• Bus management commands, which control the GPIB interface.

• Device commands, which control analyzer functions.

Language systems usually deal differently with these two kinds of GPIB commands. For example, HP BASIC uses a unique keyword to send each bus management command, but always uses the keyword OUTPUT to send device commands.

The following example shows how to send a typical device command:

OUTPUT 716;"CALCULATE:MARKER:MAXIMUM"

This sends the command CALCULATE:MARKER:MAXIMUM to the GPIB device at address 716. If the device is an analyzer, the command instructs the analyzer to set a marker to the maximum point on the data trace.



GPIB Requirements

GPIB Requirements

Number of Interconnected Devices:

15 maximum

Interconnection Path/Maximum Cable Length:

20 meters maximum or 2 meters per device, whichever is less.

Message Transfer Scheme:

Byte serial/bit parallel asynchronous data transfer using a

3-line handshake system.

Data Rate:

Maximum of 1 megabyte per second over limited distances with tri-state drivers. The actual data rate is the transfer rate of the slowest device involved.

Address Capability:

Primary addresses: 31 talk, 31 listen. A maximum of 1 talker and 14 listeners at one time.

Multiple Controller Capability:

In systems with more than one controller (like the analyzer system), only one can be active at a time. The active controller can pass control to another controller, but only the system controller can assume unconditional control. Only one system controller is allowed. The system controller is hard-wired to assume bus control after a power failure.


Table 1-1


Interface Capabilities

Interface Capabilities

The analyzer has the following interface capabilities, defined by the

IEEE 488.1 standard:

Analyzer Interface Capabilities (IEEE 488.1)

L4

LE0

SR1

RL1

SH1

AH1

T6

TE0 full Source handshake capability full Acceptor handshake capability basic Talker, Serial Poll, no Talk Only, unaddress if MLA no Extended Talker capability basic Listener, no Listen Only, unaddress if MTA no Extended Listener capability full Service Request capability full Remote/Local capability

DC1

C1 full Device Clear capability

System Controller capability

C2

C3

C4

1

C8

1

C12

2 send IFC and take charge Controller capability send REN Controller capability respond to SRQ send IFC, receive control, pass control, pass control to self

E2

DT1

PP0 send IF messages, receive control, pass control tri-state drivers full device trigger capability no parallel poll capability

1. only when an HP Instrument BASIC program is running

2. only when an HP Instrument BASIC program is not running



Programming Fundamentals


This section includes specific information for programming your network analyzer. It includes how the analyzer interacts with a controller, how data is transferred between the analyzer and a controller, and how to use the analyzer's status register structure to generate service requests.

Controller Capabilities

The analyzer can be configured as a GPIB system controller or as a talker/listener on the bus. To configure the analyzer, select either the

System Controller or the

SYSTEM OPTIONS GPIB

Talker Listener

menu.

softkey in the

The analyzer is not usually configured as the system controller unless it is the only controller on the bus. This setup would be used if the analyzer only needed to control printers or plotters. It would also be used if HP

Instrument BASIC was being used to control other test equipment.

When the analyzer is used with another controller on the bus, it is usually configured as a talker/listener. In this configuration, when the analyzer is given control it can function as the active controller.




Response to Bus Management Commands

The GPIB contains an attention (ATN) line that determines whether the interface is in command mode or data mode. When the interface is in command mode (ATN TRUE), a controller can send bus management commands over the bus. Bus management commands specify which devices on the interface can talk (send data) and which can listen

(receive data). They also instruct devices on the bus, either individually or collectively, to perform a particular interface operation.

This section describes how the analyzer responds to the GPIB management commands. The commands themselves are defined by the

IEEE 488.1 standard. Refer to the documentation for your controller's language system to determine how to send these commands.

Device Clear (DCL)

When the analyzer receives this command, it does the following:

• clears its input and output queues

• resets its command parser (so it is ready to receive a new program message)

• cancels any pending *OPC command or query

The command does not affect the following:

• front panel operation

• any analyzer operations in progress (other than those already mentioned)

• any instrument settings or registers (although clearing the output queue may indirectly affect the status byte's Message Available

(MAV) bit)

Go To Local (GTL)

This command returns the analyzer to local (front-panel) control. All keys on the analyzer's front-panel are enabled.




Interface Clear (IFC)

This command causes the analyzer to halt all bus activity. It discontinues any input or output, although the input and output queues are not cleared. If the analyzer is designated as the active controller when this command is received, it relinquishes control of the bus to the system controller. If the analyzer is enabled to respond to a Serial Poll, it becomes Serial Poll disabled.

Local Lockout (LLO)

This command causes the analyzer to enter the local lockout mode, regardless of whether it is in the local or remote mode. The analyzer only leaves the local lockout mode when the GPIB Remote Enable (REN) line is set FALSE.

Local Lockout ensures that the analyzer's remote softkey menu

(including the Return to Local softkey) is disabled when the analyzer is in the remote mode. When the key is enabled, it allows a front-panel operator to return the analyzer to local mode, enabling all other front-panel keys. When the key is disabled, it does not allow the front-panel operator to return the analyzer to local mode.

Parallel Poll

The analyzer ignores all of the following parallel poll commands:

• Parallel Poll Configure (PPC)

• Parallel Poll Unconfigure (PPU)

• Parallel Poll Enable (PPE)

• Parallel Poll Disable (PPD)




Remote Enable (REN)

REN is a single line on the GPIB. When it is set TRUE, the analyzer will enter the remote mode when addressed to listen. It will remain in remote mode until it receives the Go to Local (GTL) command or until the REN line is set FALSE.

When the analyzer is in remote mode and local lockout mode, all front panel keys are disabled. When the analyzer is in remote mode but not in local lockout mode, all front panel keys are disabled except for the softkeys. The remote softkey menu includes seven keys that are available for use by a program. The eighth softkey is the

Return to Local key which allows a front-panel operator to return the analyzer to local mode, enabling all other front-panel keys.

Selected Device Clear (SDC)

The analyzer responds to this command in the same way that it responds to the Device Clear (DCL) command.

When the analyzer receives this command it does the following:

• clears its input and output queues

• resets its command parser (so it is ready to receive a new program message)

• cancels any pending *OPC command or query

The command does not affect the following:

• front-panel operation

• any analyzer operations in progress (other than those already mentioned)

• any analyzer settings or registers (although clearing the output queue may indirectly affect the status byte's MAV bit) passed

Serial Poll

The analyzer responds to both of the serial poll commands. The Serial

Poll Enable (SPE) command causes the analyzer to enter the serial poll mode. While the analyzer is in this mode, it sends the contents of its status byte register to the controller when addressed to talk.




When the status byte is returned in response to a serial poll, bit 6 acts as the Request Service (RQS) bit. If the bit is set, it will be cleared after the status byte is returned.

The Serial Poll Disable (SPD) command causes the analyzer to leave the serial poll mode.

Take Control Talker (TCT)

If the analyzer is addressed to talk, this command causes it to take control of the GPIB. It becomes the active controller on the bus. The analyzer automatically passes control back when it completes the operation that required it to take control. Control is passed back to the address specified by the *PCB command (which should be sent prior to passing control).

If the analyzer does not require control when this command is received, it immediately passes control back.

Message Exchange

The analyzer communicates with the controller and other devices on the

GPIB using program messages and response messages. Program messages are used to send commands, queries, and data to the analyzer.

Response messages are used to return data from the analyzer. The syntax for both kinds of messages is discussed in

Chapter 9,

“Introduction to SCPI.”

There are two important things to remember about the message exchanges between the analyzer and other devices on the bus:

• The analyzer only talks after it receives a terminated query (see

“Query Response Generation” on page 1-16 ).

• Once it receives a terminated query, the analyzer expects to talk before it is told to do something else.




GPIB Queues

Queues enhance the exchange of messages between the analyzer and other devices on the bus. The analyzer contains the following:

• an input queue

• an error queue

• an output queue

Input Queue

The input queue temporarily stores the following until they are read by the analyzer's command parser:

• device commands and queries

• the GPIB END message (EOI asserted while the last data byte is on the bus)

The input queue also makes it possible for a controller to send multiple program messages to the analyzer without regard to the amount of time required to parse and execute those messages. The queue holds up to 128 bytes. It is cleared when the following actions occur:

• the analyzer is turned on

• the Device Clear (DCL) or Selected Device Clear (SDC) command is received

Error Queue

The error queue temporarily stores up to 20 error messages. Each time the analyzer detects an error, it places a message in the queue. When you send the SYST:ERR?

query, one message is moved from the error queue to the output queue so it can be read by the controller. Error messages are delivered to the output queue in the order they were received.

The error queue is cleared when the following actions occur:

• all the error messages are read using the SYST:ERR?

query


• the *CLS command is received




Output Queue

The output queue temporarily stores a single response message until it is read by a controller. It is cleared when the following actions occur:

• the message is read by a controller


• the Device Clear (DCL) or Selected Device Clear (SDC) command is received

Command Parser

The command parser reads program messages from the input queue in the order they were received from the bus. It analyzes the messages to determine what actions the analyzer should take.

One of the parser's most important functions is to determine the position of a program message in the analyzer's command tree (described in

Chapter 9

). When the command parser is reset, the next command it receives is expected to arise from the base of the analyzer's command tree.

The parser is reset when the following actions occur:


• The Device Clear (DCL) or Selected Device Clear (SDC) command is received.

• a colon immediately follows a semicolon in a program message. (For more information see

“Sending Multiple Commands” on page 9-7

.)

• A program message terminator is received. A program message terminator can be an ASCII carriage return (

C

R

) or newline character or the GPIB END message (EOI set true).




Query Response Generation

When the analyzer parses a query, the response to that query is placed in the analyzer's output queue. The response should be read immediately after the query is sent. This ensures that the response is not cleared before it is read. The response is cleared when one of the following message exchange conditions occurs:

• Unterminated condition—the query is not properly terminated with an ASCII carriage return character or the GPIB END message (EOI set true) before the response is read.

• Interrupted condition—a second program message is sent before the response to the first is read.

• Buffer deadlock—a program message is sent that exceeds the length of the input queue or that generates more response data than fits in the output queue.


2 Synchronizing the Analyzer and a Controller

2-1

Synchronizing the Analyzer and a Controller

Synchronizing the Analyzer and a Controller

Synchronizing the Analyzer and a

Controller

The IEEE 488.2 standard provides tools that can be used to synchronize the analyzer and a controller. Proper use of these tools ensures that the analyzer is in a known state when you send a particular command or query.

Device commands can be divided into two broad classes:

• Sequential commands

• Overlapped commands

Most of the analyzer's commands are processed sequentially. A sequential command holds off the processing of subsequent commands until it has been completely processed.

Some commands do not hold off the processing of subsequent commands; they are called overlapped commands.



Overlapped Commands


Typically, overlapped commands take longer to process than sequential commands. For example, the INITIATE:IMMEDIATE command restarts a measurement. The command is not considered to have been completely processed until the measurement is complete. This can take a long time with a narrow or fine system bandwidth or when averaging is enabled.

The analyzer has the following overlapped commands:

ABORt

CALibration:SELF: ALL

CALibration:SELF: <ON|OFF|ONCE>

CALibration:SELF:METHod:<ONEPort|TWOPort>

CALibration:ZERO:AUTO

CONFigure[1|2]

DIAGnostic:CCONstants:LOAD

DIAGnostic:CCONstants:STORe:DISK

DIAGnostic:CCONstants:STORe:EEPRom

DIAGnostic:DITHer

DIAGnostic:SPUR:AVOid

HCOPy[:IMMediate]

INITiate[1|2]:CONTinuous

INITiate[1|2][:IMMediate]

MMEMory:LOAD:STATe

OUTPut[:STATe]

POWer[1|2]:MODE

PROGram[:SELected]:EXECute

ROUTe[1|2]:PATH:DEFine:PORT?

ROUTe[1|2]:PATH:DEFine:PORT <num1>, <num2>

ROUTe[1|2]:REFLection:DEFine:PORT <num>




ROUTe[1|2]:TRANsmission:DEFine:PORT <num>

SENSe[1|2]:AVERage:CLEar

SENSe[1|2]:AVERage:COUNt

SENSe[1|2]:AVERage[:STATe]

SENSe[1|2]:BWIDth[:RESolution]

SENSe[1|2]:CORRection:CLASs[:SELect]?

SENSe[1|2]:CORRection:COLLect[:ACQuire]

SENSe[1|2]:CORRection:COLLect[:ACQuire] STANdard1-7

SENSe[1|2]:CORRection:COLLect:CKIT:PORT[1|12]

[:SELECT]

SENSe[1|2]:CORRection:COLLect:ISTate[:AUTO]

SENSe[1|2]:CORRection:COLLect:METHod

SENSe[1|2]:CORRection:COLLect:METHod TWOPort

SENSe[1|2]:CORRection:COLLect:SAVE

SENSe[1|2]:CORRection:CSET[:SELect]

SENSe[1|2]:CORRection[:STATe]

SENSe[1|2]:CORRection:ONEPort:REFLection[:IMMediate]

SENSe[1|2]:CORRection:ONEPort:TRANSmission

[:IMMediate]

SENSe[1|2]:CORRection:TWOPort[:IMMediate]

SENSe:COUPle

SENSe[1|2]:DETector[:FUNCtion]

SENSe[1|2]:DISTance:STARt (Option 100 only)

SENSe[1|2]:DISTance:STOP (Option 100 only)

SENSe[1|2]:FREQuency:CENTer

SENSe[1|2]:FREQuency:MODE (Option 100 only)

SENSe[1|2]:FREQuency:SPAN

SENSe[1|2]:FREQuency:SPAN:MAXimum

SENSe[1|2]:FREQuency:STARt




SENSe[1|2]:FREQuency:STOP

SENSe[1|2]:FUNCtion

SENSe[1|2]:FUNCtion ‘FLOC . . .

SENSe[1|2]:FUNCtion ‘SRL . . .

SENSe[1|2]:FUNCtion ‘XFR:GDEL:RAT . . .

SENSe[1|2]:FUNCtion ‘XFR:POW . . .

SENSe[1|2]:FUNCtion ‘XFR:POW:RAT . . .

SENSe[1|2]:FUNCtion ‘XFR:S . . .

SENSe[1|2]:FUNCtion:SRL:SCAN[:IMMediate] (Option 100 only)

SENSe:ROSCillator:SOURce

SENSe[1|2]:STATe

SENSe[1|2]:SWEep:POINts

SENSe[1|2]:SWEep:TIME

SENSe[1|2]:SWEep:TIME:AUTO

SENSe:SWEep:TRIGger:SOURce

SOURce[1|2]:POWer[:LEVel][:IMMediate][:AMPLitude]

SYSTem:PRESet

TRACe[:DATA]

TRACe:CORRection:SIMulate:SAVE-?<TRANsmission1|...>

TRIGger[:SEQuence]:SOURce



Controlling Execution of Overlapped Commands


Each overlapped command is executed in two stages: initiation and completion. When both stages are complete for a given command, the command has “completed execution.”

*WAI

*OPC?

*OPC

Holds off the processing of subsequent commands until the initiation stage of all preceding commands is finished. If used after each overlapped command, this command ensures that commands in the analyzer’s input queue complete initiation in the order received.

Use of the *WAI command is explained later in this section and is demonstrated in the SETUP example program.

Places a 1 in the analyzer's output queue when all preceding commands have completed execution. If the program reads the output queue before it continues, this effectively pauses the controller until all executing overlapped commands are completed. This command is generally preferred to *WAI for control of command execution.

Use of the *OPC?

command is explained later in this chapter and is demonstrated in the TRANCAL and

REFLCAL example programs.

Sets bit 0 of the Standard Event Status event register to 1 when all preceding commands have completed execution. The analyzer's status registers can then be used to generate a service request when all overlapped commands are completed. This synchronizes the controller to the completion of an overlapped command, but also leaves the controller free to perform other tasks while the command is executing within the analyzer.


NOTE

NOTE

CAUTION



*OPC only informs you when all currently executing commands have completed execution. It does not hold off the processing of subsequent commands. No commands should be sent to the analyzer between sending the *OPC command and receiving the service request. Any commands sent will be executed and may affect how the instrument responds to the previously sent *OPC .

The *CLS and *RST commands cancel any preceding *OPC ? or * OPC .

Executing overlapped commands are still completed, but their completion is not reported in either the status register or the output queue. Two GPIB bus management commands — Device Clear (DCL) and Selected Device Clear (SDC) — also cancel any preceding *OPC? or

*OPC.

Use *WAI , *OPC?

or *OPC whenever overlapped commands are used. A recommended technique is to send *OPC?

at the end of each group of commands.

ALWAYS trigger an individual sweep (using *OPC?

and waiting for the reply) before reading data over the bus or executing a marker function.

The analyzer has the ability to process the commands it receives faster than it can make a measurement. If the measurement is not complete when the data is read or a marker search function is executed, the results are invalid.

The command to use (in an IBASIC OUTPUT statement) is:

OUTPUT @Hp8711;"ABOR;:INIT:CONT OFF;:INIT;*OPC?"

ENTER @Hp8711;Opc_done or another form of the INITiate[1|2][:IMMediate] command combined with the *OPC?

query.

Refer to “Taking Sweeps” in the Example Programs Guide for more information.


NOTE



Using *WAI and *OPC?

*WAI

The following example describes the use of the *WAI command. For this discussion, remember that a sequential command holds off the processing of subsequent commands until it has been completely processed. An overlapped command does not.

10 OUTPUT @Rfna;"command1"

20 OUTPUT @Rfna;"command2;*WAI"

30 OUTPUT @Rfna;"command3;"


50 END

In the example above, commands are sent and completed in the following order:

• Commands 1 through 4 are sent to the analyzer as fast as the GPIB bus traffic will allow. The program sending the commands may very well end before any command has been completed.

• Command 1 begins execution first.

• If both commands 1 and 2 are overlapped types, the order in which they finish initiation depends on the commands. The order of completion is unknown.

• Commands 3 and 4 will not be started until both commands 1 and 2 have finished initiation.

• Command 3 will begin execution before command 4.

• If all four commands are overlapped types, the order in which they complete execution is unknown.

Because *WAI only controls the order of the initiation stage of commands, rather than the order of completion, it is strongly recommended that *OPC? be used whenever sequential operation of overlapping commands is required.




*OPC

The following example describes the use of the *OPC?

command. For this discussion, remember that a sequential command holds off the processing of subsequent commands until it has been completely processed. An overlapped command does not.


20 OUTPUT @Rfna;"command2;*OPC?"

30 ENTER @Rfna;Opc_done

40 OUTPUT @Rfna;"command3;"

50 OUTPUT @Rfna;"command4;*OPC?"


70 END

In the example above, commands are sent and completed in the following order:

• Commands 1 and 2 are sent to the analyzer as fast as the GPIB bus traffic will allow.


• If both commands 1 and 2 are overlapped commands, the order of command completion is unknown.

• When both commands 1 and 2 have completed execution, commands 3 and 4 will be sent to the analyzer as fast as the GPIB bus traffic will allow.


• If both commands 3 and 4 are overlapped commands, the order of command completion is unknown.

• This program will not end until the Opc_done, located in line 60, is returned indicating that both commands have completed execution.

Use *OPC?

to ensure commands complete before proceeding.

This can be done by calling a subroutine that issues the

*OPC?

command, and reads the analyzer response with ENTER :

100 Command_done !Example of subroutine using *OPC?

110 OUTPUT @Rfna;"*OPC?"


130 RETURN

Call the Command_done subroutine after each overlapped command to ensure the desired order of command execution.


3 Passing Control

3-1

NOTE

Passing Control

Passing Control

Passing Control

When an external controller is connected to the analyzer with a GPIB cable, passing control may be needed to control devices such as printers and plotters that are also connected on the GPIB. For some operations the active controller must pass control to the analyzer. When the analyzer completes the operation, it automatically passes control of the bus back to the external controller.

An example program, PASSCTRL , demonstrates passing control to the analyzer. In this example program, control is passed so the analyzer can control a printer for hardcopy output. See the Example Programs Guide.

Pass Control is not needed to control peripherals connected to the serial, parallel, or LAN ports.

For smooth passing of control, take steps that ensure the following conditions are met:

• The analyzer must know the controller's address so it can pass control back.

• The controller must be informed when the analyzer passes control back.


NOTE

Passing Control

Passing Control

The following is a procedure for passing control:

1. Send the controller's GPIB address to the analyzer with the *PCB command.

2. Clear the analyzer's status registers with the *CLS command.

3. Enable the analyzer's status registers to generate a service request when the Operation Complete bit is set. (Send *ESE with a value of 1 and *SRE with a value of 32.)

4. Enable the controller to respond to the service request.

5. Send the command that requires control of the bus followed by the

*OPC command.

6. Pass control to the analyzer and wait for the service request. The service request indicates that the command has been completed and control has been passed back to the controller.

For this procedure to work properly, only the command that requires control of the bus should be pending. Other overlapped commands should not. For more information on overlapped commands, see

Chapter 2,

“Synchronizing the Analyzer and a Controller.”


4 Data Types and Encoding

4-1

Data Types and Encoding

Data Types and Encoding

Data Types and Encoding

Data is transferred between the analyzer and a controller via the GPIB data lines, DIO1 through DIO8. Such transfers occur in a byte-serial (one byte at a time), bit-parallel (8 bits at a time) manner. This section discusses the following aspects of data transfer:

• the different data types used during data transfers

• data encoding used during transfers of numeric block data



Data Types

Data Types

The analyzer uses a number of different data types during data transfers. Data transfer occurs in response to a query. The data type used is determined by the parameter being queried. Data types described in this section are:

• Numeric Data

• Character Data

• String Data

• Expression Data

• Block Data

Numeric Data

The analyzer returns three types of numeric data in response to queries:

NR1 data

NR2 data

NR3 data

Integers (such as +1 , 0 , -1 , 123 , -12345 ). This is the response type for boolean parameters as well as some numeric parameters.

Floating point numbers with an explicit decimal point

(such as 12.3

, +1.234

, -0.12345

).

Floating point numbers in scientific notation (such as

+1.23E+5 , +123.4E-3 , -456.789E+6 ).

Character Data

Character data consists of ASCII characters grouped together in mnemonics that represent specific instrument settings (such as

MAXimum , MINimum or MLOGarithmic ). The analyzer always returns the

short form of the mnemonic in upper-case alpha characters.



Data Types

String Data

String data consists of ASCII characters. The string must be enclosed by a delimiter, either single quotes ( 'This is string data.' ) or double quotes ( “This is also string data.” ). To include the delimiter as a character in the string, it must be typed twice without any characters in between. The analyzer always uses double quotes when it returns string data.

Expression Data

Expression data consists of mathematical expressions that use character parameters. When expression data is sent to the analyzer, it is always enclosed in parentheses (such as (IMPL/CH1SMEM) or (IMPL) ). The analyzer returns expression data enclosed in double quotes.

Block Data

The block data mode is typically used to transfer large quantities of related data (like a data trace). Blocks can be sent as definite length blocks or indefinite length blocks — the instrument will accept either form. The analyzer always returns definite length block data in response to queries.

Definite Block Length

The general form for a definite block length transfer is:

#<num_digits><num_bytes><data_bytes>

In the definite length block, two numbers must be specified. The single decimal digit <num_digits> specifies how many digits are contained in

<num_bytes> . The decimal number <num_bytes> specifies how many data bytes will follow in <data_bytes> . An example IBASIC (or HP

BASIC) statement to send ABC+XYZ as a definite block length parameter is shown; note that the data block contains seven bytes ( 7 ) and only one digit is needed to describe the block length 1 .

OUTPUT 716;"#17ABC+XYZ"


NOTE

NOTE


Data Types

This analyzer will send an additional <

C

R

> with EOI asserted for definite block length transfers. The definite length block form for your analyzer is: #<num_digits><num_bytes><data_bytes><

C

R

><EOI> .

<num_bytes> is the number of <data_bytes> without counting

<

C

R

><EOI> .

Indefinite Block Length

The general form for an indefinite block length transfer is:

#0<data_bytes><

C

R

><EOI>

After the last data byte is sent, the indefinite length block must be terminated by sending a carriage return or newline with EOI asserted.

This forces the termination of the program message. An example IBASIC

(or HP BASIC) statement to send ABC+XYZ as an indefinite block length parameter is shown; note that END is used to properly terminate the message.

OUTPUT 716;"#0ABC+XYZ",END

Files are transferred as indefinite length blocks.


CAUTION


Data Encoding for Large Data Transfers


The FORMat:DATA command selects the type of data and the type of data encoding that is used to transfer large blocks of numeric data between the analyzer and a controller. There are two block specifiers and one numeric data type specifier:

REAL specifies the block data type. Either the definite or indefinite length syntax can be used. The block is transferred as a series of binary-encoded floating-point numbers. Data transfers of the REAL,64 data type are demonstrated in the REALDATA example program.

INTeger specifies the block data type. Either the definite or indefinite length syntax can be used. The block is transferred as an array of binary-encoded data with each point represented by a set of four 16-bit integers.

This is the instrument's internal format — it should only be used for data that will be returned to the instrument for later use. Data transfers of the

INTeger 16 data type are demonstrated in the

INTDATA and LOADCALS example programs.

ASCii specifies the numeric data type (NR1, NR2 or NR3 syntax). The data is transferred as a series of

ASCII-encoded numbers separated by commas.

ASCii formatted data transfers are demonstrated in the

ASCDATA example program.

Blocks that contain mixed data — both numbers and ASCII characters

— ignore the setting of FORMat:DATA . These blocks always transfer as either definite length or indefinite length block data. The following commands transfer blocks of mixed data:

PROGram[:SELected]:DEFine

SYSTem:SET

INTeger 16 data for the Agilent 8711/12/13/14/ A-, B-, and C-series instruments is represented by sets of three 16-bit integers. The

Agilent 8712ET/ES and 8714ET/ES instruments use sets of four 16-bit integers.




ASCII Encoding

The ANSI X3.4-1977 standard defines the ASCII 7-bit code. When an

ASCII-encoded byte is sent over the GPIB, bits 0 through 6 of the byte

(bit 0 being the least significant bit) correspond to the GPIB data lines

DIO1 through DIO7. DIO8 is ignored.

When ASCII encoding is used for large blocks of data, the number of significant digits to be returned for each number in the block can be specified. For example, the following command returns all numbers as

NR3 data with 7 significant digits.

FORMat:DATA ASCii,7

Binary Encoding

When binary encoding is used for large blocks of data, all numbers in the block are transferred as 32-bit or 64-bit binary floating point numbers or as an array of 16-bit integers. The binary floating-point formats are defined in the IEEE 754-1985 standard.

FORMat:DATA REAL,32 selects the IEEE 32-bit format (not supported by IBASIC or HP BASIC)

FORMat:DATA REAL,64 selects the IEEE 64-bit format.

FORMat:DATA INTeger,16 selects the 16-bit integer format.

Byte Swapping

PC compatibles frequently use a modification of the IEEE floating point formats with the byte order reversed. To reverse the byte order for data transfer into a PC, the FORMat:BORDer command should be used.

FORMat:BORDer SWAPped

FORMat:BORDer NORMal selects the byte-swapped format selects the standard format


5 Using Status Registers

5-1

Using Status Registers

Using Status Registers

Using Status Registers

The analyzer's status registers contain information about the condition of the network analyzer and its measurements. This section describes the registers and their use in GPIB programming.

Example programs using the status registers are included in the

Example Programs Guide. These programs include SRQ and GRAPHICS which use service request interrupt routines, PASSCTRL which uses the status byte to request control of the GPIB, and LIMITEST which uses the

Limit Fail condition register.



General Status Register Model

Figure 5-1


The analyzer's status system is based on the general status register model shown in

Figure 5-1 . Most of the analyzer's register sets include

all of the registers shown in the model, although commands are not always available for reading or writing a particular register. The information flow within a register set starts at the condition register and ends at the register summary bit (see

Figure 5-2 on page 5-5 for actual

connections between the registers). This flow is controlled by setting bits in the transition and enable registers.

Two register sets — the Status Byte and the Standard Event Status

Register — are 8-bits wide. All others are 16-bits wide, but the most significant bit (bit 15) in the larger registers is always set to 0.





Condition Register

Condition registers continuously monitor the instrument's hardware and firmware status. Bits in a condition register are not latched or buffered, they are updated in real time. When the condition monitored by a specific bit becomes true, the bit is set to 1. When the condition becomes false, the bit is reset to 0. Condition registers are read-only.

Transition Registers

Transition registers control what type of change in a condition register will set the corresponding bit in the event register. Positive state transitions (0 to 1) are only reported to the event register if the corresponding positive transition bit is set to 1. Negative state transitions (1 to 0) are only reported if the corresponding negative transition bit is set to 1. Setting both transition bits to 1 causes both positive and negative changes to be reported. Transition registers are read-write, and are unaffected by *CLS (clear status) or queries. They are reset to instrument default conditions at power up and after *RST and SYSTem:PRESet commands.

Event Register

Event registers latch any reported condition changes. When a transition bit allows a condition change to be reported, the corresponding event bit is set to 1. Once set, an event bit is no longer affected by condition changes. It remains set until the event register is cleared. Event registers are read-only.

An event register is cleared when you read it. All event registers are cleared when you send the *CLS (clear status) command.


Figure 5-2



Enable Register

Enable registers control the reporting of events (latched conditions) to the register summary bit. If an enable bit is set to 1, the corresponding event is included in the logical ORing process that determines the state of the summary bit. (The summary bit is only set to 1 if one or more enabled event bits are set to 1.) Summary bits are recorded in the instrument's status byte. Enable registers are read-write and are cleared by *CLS (clear status).

Flow of Information Within a Register Set



How to Use Registers

How to Use Registers

There are two methods of accessing the information in status registers:

• the direct-read method

• the service request (SRQ) method

In the direct-read method, the analyzer is passive. It only tells the controller that conditions have changed when the controller asks the right question. In the SRQ method, the analyzer is more active. It tells the controller when there has been a condition change without the controller asking. Either method allows you to monitor one or more conditions.

The following steps are used to monitor a condition with the direct read method:

1. Determine which register contains the bit that monitors the condition.

2. Send the unique GPIB query that reads that register.

3. Examine the bit to see if the condition has changed.

The direct-read method works well when it is not necessary to know about changes the moment they occur. It does not work well if immediate knowledge of the condition change is needed. A program that used this method to detect a change in a condition would need to continuously read the registers at very short intervals. The SRQ method is better suited for that type of need.



The Service Request Process


The following steps are used to monitor a condition with the SRQ method:

1. Determine which bit monitors the condition.

2. Determine how that bit reports to the request service (RQS) bit of the

Status Byte.

3. Send GPIB commands to enable the bit that monitors the condition and to enable the summary bits that report the condition to the RQS bit.

4. Enable the controller to respond to service requests.

When the condition changes, the analyzer sets its RQS bit and the

GPIB's SRQ line. The controller is informed of the change as soon as it occurs. The time the controller would otherwise have used to monitor the condition can now be used to perform other tasks. The controller's response to the SRQ is determined by the program being run.


Figure 5-3



Generating a Service Request

A service request is generated using the Status Byte. As shown in

Figure

5-3

, the analyzer's other register sets report to the Status Byte. Some of them report directly while others report indirectly through other register sets.

Generating a Service Request


NOTE



The process of preparing the analyzer to generate a service request, and the handling of that interrupt when it is received by a program, are demonstrated in the SRQ example program.

When a register set causes its summary bit in the Status Byte to change from 0 to 1, the analyzer can initiate the service request (SRQ) process. If both the following conditions are true, the process is initiated:

• The corresponding bit of the Service Request enable register is also set to 1.

• The analyzer does not have a service request pending. (A service request is considered to be pending between the time the analyzer's

SRQ process is initiated and the time the controller reads the Status

Byte register with a serial poll.)

The SRQ process sets the GPIB's SRQ line true and sets the Status

Byte's request service (RQS) bit to 1. Both actions are necessary to inform the controller that the analyzer requires service. Setting the SRQ line informs the controller that some device on the bus requires service.

Setting the RQS bit allows the controller to determine that the analyzer was the device that initiated the request.

When a program enables a controller to detect and respond to service requests, it should instruct the controller to perform a serial poll when the GPIB's SRQ line is set true. Each device on the bus returns the contents of its Status Byte register in response to this poll. The device whose RQS bit is set to 1 is the device that requested service.

When the analyzer's Status Byte is read with a serial poll, the RQS bit is reset to 0. Other bits in the register are not affected.

As implied in

Figure 5-3

, bit 6 of the Status Byte register serves two functions: the request service function (RQS) and the master summary status function (MSS). Two different methods for reading the register allow you to access the two functions. Reading the register with a serial poll allows you to access the bit's RQS function. Reading the register with *STB allows you to access the bit's MSS function.


NOTE


The Analyzer's Status Register Sets


The analyzer uses eight register sets to keep track of instrument status:

Status Byte *STB?

and *SRE

Device Status STATus:DEVice

Limit Fail STATus:QUEStionable:LIMit

Questionable

Status STATus:QUEStionable

Standard Event

Status *ESR?

and *ESE

Measuring

Status

Averaging

Status

STATus:OPERation:MEASuring

STATus:OPERation:AVERaging

Operational

Status STATus:OPERation

Their reporting structure is summarized in

Figure 5-4

. They are described in greater detail in the following section.

Register bits not explicitly presented in the following sections are not used by the analyzer. A query to one of these bits returns a value of 0.


Figure 5-4 Analyzer Register Sets




Figure 5-5



Status Byte

The Status Byte register set summarizes the states of the other register sets and monitors the analyzer's output queue. It is also responsible for generating service requests see

“Generating a Service Request” on page 5-8 . See

Figure 5-5

.

The Status Byte Register Set

The Status Byte register set does not conform to the general status register model described at the beginning of this chapter. It contains only two registers: the Status Byte register and the Service Request enable register. The Status Byte register behaves like a condition register for all bits except bit 6. The Service Request enable register behaves like a standard enable register except that bit 6 is always set to 0.




Bits in the Status Byte register are set to 1 under the following conditions:

Device Status Summary

(bit 2) is set to 1 when one or more enabled bits in the Device

Status event register are set to 1.

Questionable Status Summary

(bit 3) is set to 1 when one or more enabled bits in the

Questionable Status event register are set to 1.

Message Available

(bit 4) is set to 1 when the output queue contains a response message.

Standard Event Status Summary

(bit 5) is set to 1 when one or more enabled bits in the Standard

Event Status event register are set to 1.

Master Summary Status

(bit 6, when read by *STB ) is set to 1 when one or more enabled bits in the Status Byte register are set to 1.

Request Service

(bit 6, when read by serial poll) is set to 1 by the service request process (see

“Generating a Service Request” on page 5-8 ).

Operational Status Summary


Operational Status event register are set to 1.




The commands used to read and write to the Status Byte registers are listed below:

SPOLL an IBASIC (or HP BASIC) command used in the service request process to determine which device on the bus is requesting service.

*STB?

*SRE <num>

*SRE?

reads the value of the instrument's status byte. This is a non-destructive read—the Status Byte is cleared by the *CLS command.

sets bits in the Service Request Enable register. The current setting of the Service Request Enable register is stored in non-volatile memory. If *PSC has been set, it will be saved at power on.

reads the current state of the Service Request Enable register.




Device Status Register Set

The Device Status register set monitors the state of device-specific parameters.

Bits in the Device Status condition register are set to 1 under the following conditions:

Key Pressed

(bit 0) is set to 1 when one of the analyzer's front panel keys has been pressed.

Any Softkey Pressed

(bit 1) is set to 1 when one of the analyzer's softkeys has been pressed.

Any External Keyboard Key Pressed

(bit 2) is set to 1 when a key has been pressed on an external keyboard connected to the DIN KEYBOARD connector on the rear panel of the analyzer.

Front Panel Knob Turned

(bit 3) is set to 1 when the analyzer's front panel knob is turned.




Limit Fail Register Set

The Limit Fail register set monitors limit test results for both measurement channels.

The inputs for the bits in the Limit Fail condition register are latched.

(See

Figure 5-6

.) The two bits for measurement channel 1 are latched when the Limit Test is OFF for channel 1 or when MEAS 1 is OFF. The two bits for measurement channel 2 are latched when Limt Test is OFF for channel 2 or when MEAS 2 is OFF.

The following conditions determine the state for each of the bits when the corresponding Limit Test is ON.

Measurement Channel 1 Limit Failed

(bit 0) is set to 1 when limit testing is enabled and any point on measurement channel 1 fails the limit test, or when any enabled marker limit on measurement channel

1 has failed.

Measurement Channel 2 Limit Failed

(bit 1) is set to 1 when limit testing is enabled and any point on measurement channel 2 fails the limit test, or when any enabled marker limit on measurement channel

2 has failed.

Measurement Channel 1 Marker Limit Failed

(bit 2) is set to 1 when any enabled marker limit on measurement channel 1 has failed.

Measurement Channel 2 Marker Limit Failed

(bit 3) is set to 1 when any enabled marker limit on measurement channel 2 has failed.


cw61e

IN

BISTABLE

LATCH *

C

OUT

IN

BISTABLE

LATCH *

C

OUT

IN

C

BISTABLE

LATCH * OUT

IN

C

BISTABLE

LATCH *

OUT

*

CONDITIONS:

BISTABLE LATCH

Transparent when C (Control) is high (ON).

Latched when C (Control) is low (OFF).

CIRCUIT:

IN

OUT

C

Fig. 5-6



Questionable Status Register Set

The Questionable Status register set monitors conditions that affect the quality of measurement data.

Bits in the Questionable Status condition register are set to 1 under the following conditions:

Limit Fail

(bit 9) is set to 1 when one or more enabled bits in the Limit

Fail event register are set to 1.

Data Questionable

(bit 10) is set to 1 when a change in the analyzer's configuration requires that new measurement data be taken.


Figure 5-7



Standard Event Status Register Set

The Standard Event Status register set monitors GPIB errors and synchronization conditions. See

Figure 5-7

.

The Standard Event Status Register Set

The Standard Event Status register set does not conform to the general status register model described at the beginning of this section. It contains only two registers: the Standard Event Status event register and the Standard Event Status enable register. The Standard Event

Status event register is similar to other event registers, but behaves like a register set that has a positive transition register with all bits set to 1.

The Standard Event Status enable register is the same as other enable registers.




Operation Complete

(bit 0) is set to one when the following two events occur (in the order listed):

1. The *OPC command is sent to the analyzer.

2. The analyzer completes all pending overlapped commands.

Request Control

(bit 1) is set to 1 when both of the following conditions are true:

• The analyzer is configured as a talker/listener for

GPIB operation.

• The analyzer is instructed to do something (such as plotting or printing) that requires it to take control of the bus.

Query Error

(bit 2) is set when the command parser detects a query error. A query error indicates that one or both of the following actions occurred:

• an attempt to read data from the Output Queue when no data was present.

• that data in the Output Queue was lost. An example of this would be queue overflow.

Device Dependent Error

(bit 3) is set to 1 when the command parser detects a device-dependent error. A device-dependent error is any analyzer operation that did not execute properly due to some internal condition such as overrange. This bit indicates that the error was not a command, query, or an execution error.




Execution Error

(bit 4) is set to 1 when the command parser detects an execution error. Execution errors occur when the following conditions occur:

• a <PROGRAM DATA> element received in a command was outside the legal range for the analyzer, or inconsistent with the operation of the analyzer.

• the analyzer could not execute a valid command due to some analyzer condition.

Command Error

(bit 5) is set to 1 when the command parser detects a command error. The following events cause a command error:

User Request

(bit 6) is not implemented. For keypress related functions, see

“Device Status Register Set” on page 5-15

.

Power On

(bit 7) is set to 1 when you turn on the analyzer.

The commands used to read and write the Standard Event

Status registers are listed below:

*ESR?

*ESE?

• An IEEE 488.2 syntax error occurred. This means that the analyzer received a message that did not follow the syntax defined by the 488.2 standard.

• A semantic error occurred. For example, the analyzer received an incorrectly spelled command.

Another example would be that the analyzer received an optional 488.2 command that it does not implement.

*ESE <num> reads the value of the standard event status register.

sets bits in the standard event status enable register. The current setting of the standard event statue enable register is stored in non-volatile memory. If *PSC has been set, it will be saved at power on.

reads the current state of the standard event status enable register.




Measuring Status Register Set

The Measuring Status register set monitors conditions in the analyzer's measurement process.

Bits in the Measuring Status condition register are set to 1 under the following conditions:

Channel 1

Measuring (bit 0) is set to 1 while the analyzer is collecting measurement data on channel 1.

Channel 2

Measuring (bit 1) is set to 1 while the analyzer is collecting measurement data on channel 2.

Averaging Status Register Set

The Averaging Status register set monitors conditions in the analyzer's measurement process when the trace averaging function is in use.

Bits in the Averaging Status condition register are set to 1 under the following conditions:

Measurement

Channel 1

Averaging (bit 0) is set to 1 while the analyzer is sweeping on measurement channel 1 and the number of sweeps completed (since “average restart”) is less than the averaging factor.

Measurement

Channel 2

Averaging (bit 1) is set to 1 while the analyzer is sweeping on measurement channel 2 and the number of sweeps completed (since “average restart”) is less than the averaging factor.




Operational Status Register Set

The Operational Status register set monitors conditions in the analyzer's measurement process, disk operations, and printing/plotting operations.

It also monitors the state of the current HP Instrument BASIC program.

Bits in the Operational Status condition register are set to 1 under the following conditions:

Calibrating (bit 0) is set to 1 while the instrument is zeroing the broadband diode detectors.

Settling

Measuring

(bit 1) is set to 1 while the measurement hardware is settling.


Measuring Status event register are set to 1.

Correcting

Averaging

Hardcopy

Running (bit 9) is set to 1 while the analyzer is performing a hardcopy (print or plot) function.

Test Running (bit 10) is set to 1 when one of the analyzer's internal service tests is being run.

Program

Running

(bit 7) is set to 1 while the analyzer is performing a calibration function.


Averaging Status event register are set to 1.

(bit 14) is set to 1 while an HP Instrument BASIC program is running on the analyzer's internal controller.




Table 5-1

Settings for STATus:PRESet

Executing the STATus:PRESet command changes the settings in the enable ( ENAB ), positive transition ( PTR ), and negative transition ( NTR ) registers. The table below shows the settings after the command is executed.

Status Register States After PRESet Command

Register Set ENABle PTRansition NTRansition

STATus:DEVice

STATus:QUEStionable:LIMit all 0 s all 1 s

STATus:QUEStionable all 0 s

STATus:OPERation:MEASuring all 1 s

STATus:OPERation:AVERaging all 1 s

STATus:OPERation all 0 s all all all all all all

1

1

1

0

0

1 s s s s s s all all all all all all

0

0

0

1

1

0 s s s s s s


Figure 5-8



Analyzer Register Set Summary

Register Set Summary


6 Trace Data Transfers

6-1

Trace Data Transfers

Trace Data Transfers

Figure 6-1

Trace Data Transfers

This chapter explains how to read (query) the measurement data trace from the analyzer into your program. It also describes how to send data from your program to the analyzer's measurement arrays. Accessing the measurement arrays is done using SCPI commands. If you are using

IBASIC, you can also access the measurement arrays using high-speed subroutines. Refer to the HP Instrument BASIC User's Handbook for more details.

Figure 6-1 is a data processing flow diagram that represents the flow of

numerical data. The data passes through several math operations, denoted in the figure by single-line boxes. Most of these operations can be selected and controlled with the front panel CONFIGURE block menus. The data is stored in arrays along the way, denoted by double-line boxes. These arrays are places in the flow path where data is accessible via GPIB. While only a single flow path is shown, two identical paths are available, corresponding to measurement channels 1 and 2.

Numeric Data Flow Through the Network Analyzer



Querying the Measurement Trace Using BASIC

Querying the Measurement Trace Using

BASIC

After making a measurement, you can read the resultant measurement trace out of the analyzer using the SCPI query:

"TRACE:DATA?

CH1FDATA"

The BASIC program segment below shows how to read the trace from the analyzer into an array in your program.

10

20

30

40

50

60

70

REAL Trace(1:201)

ASSIGN @Hp8711 TO 716

! Take sweep here

OUTPUT @Hp8711;"FORM:DATA ASCII,5"

OUTPUT @Hp8711;"TRACE:DATA? CH1FDATA"

ENTER @Hp8711;Trace(*)

DISP Trace(1),Trace(2),Trace(3),". . . ."

In this program, the TRACE:DATA?

query returns all of the measurement points as a single block. The analyzer computes the value for each point using the measurement format selected by the [FORMAT] menu ( CALC:FORM SCPI command), and returns a block of data called the formatted data array. The values of each point correspond to the values displayed on the screen, or those shown in the marker readouts.

The frequency stimulus value (X-axis) of each point is not returned by the TRACE:DATA?

query; only the measurement response (Y-axis) values are returned.

When transferring the block of trace data, you may select either binary or ASCII data encoding. This is explained in

Chapter 4, “Data Types and

Encoding,” in the section titled

“Data Encoding for Large Data

Transfers” on page 4-6

. Notice that the terms "encoding format" and

"measurement format" are not the same. The encoding format determines how the numbers are represented as bytes, while the measurement format corresponds to the meaning of the value of the numbers.

The easiest way to transfer a measurement data trace is to use ASCII data encoding.



Querying the Measurement Trace Using BASIC

In the previous BASIC program segment, the array Trace(1:201) contains 201 real (floating point) numbers. The SCPI command

"FORM:DATA ASCII,5" specifies ASCII data encoding, with 5 significant digits. The command "TRACE:DATA? CH1FDATA" instructs the analyzer to send the measurement trace. The ENTER statement reads the measurement data sent by the analyzer into the Trace(1:201) array.

It is important to make sure that the Trace array declared in your program is the same size as the measurement trace on the analyzer, or an error will occur. The ENTER statement attempts to read data from the analyzer until it completely fills the Trace array, at which point it expects to receive an end-of-data terminator from the analyzer. To be safe, your program should use the "SENS:SWE:POIN" SCPI command to set the number of measurement data points to the desired value.

Refer to the example program ASCDATA in the Example Programs

Guide for a complete example.

10

20

30

40

50

60

70

2)

Smith Chart and Polar Formats

Each measurement point is represented by a single floating point number. This is the case for all of the analyzer's measurement formats except Smith Chart and Polar. When Smith Chart or Polar format is selected, each point is represented by two numbers, the first one being the real portion and the second being the imaginary portion of the complex measurement value.

Below is a modified example program that will work when using Smith

Chart or Polar formats.

REAL Trace(1:201,1:2)


! Take sweep here

OUTPUT @Hp8711;"FORM:DATA ASCII,5"


ENTER @Hp8711;Trace(*)

DISP Trace(1,1),Trace(1,2),". . . .",Trace(201,1),Trace(201,



Querying the Measurement Trace Using SICL

Querying the Measurement Trace Using

SICL

This section includes a complete SICL C program that shows how to read the measurement trace from the analyzer.

/**************************************************************************

* This program takes a sweep, reads the trace, and prints it.

* It uses SICL (Standard Instrument Control Library) to talk

* to the analyzer over HP-IB.

*

* On HP-UX, compile using: cc -Aa -o query_trace query_trace.c -lsicl

**************************************************************************/

#include <sicl.h> /* For iopen(), iprintf(), iscanf(), INST, ... */

#include <stdio.h> /* For printf() */ int main(void) {

INST analyzer; float data_buf[1601]; int num_trace_bytes;

/* Handle used to talk to analyzer */

/* measurement trace.

int pt; num_trace_bytes = sizeof(data_buf);

32-bit floats */

/* Set to max allowable bytes */

/* Open the network analyzer at address 16 */ analyzer = iopen("hpib,16");

/* Clear the bus */ iclear(analyzer);

/* Abort current sweep and put analyzer sweep in hold */ iprintf(analyzer, "ABORT\n"); iprintf(analyzer, "INIT:CONT OFF\n");

/* Take one sweep, wait until done */ iprintf(analyzer, "INIT1\n"); iprintf(analyzer, "*OPC?\n"); iscanf(analyzer, "%*s");

/* Request the trace data in 32-bit floating point format */ iprintf(analyzer, "FORM:BORD NORM\n"); iprintf(analyzer, "FORM:DATA REAL,32\n");

/* Query the trace, read into data_buf[]. */ iprintf(analyzer, "TRAC? CH1FDATA\n"); iscanf(analyzer, "%#b%*c", &num_trace_bytes, &data_buf[0]);

/* Print the trace values. */ for (pt = 0; pt < num_trace_bytes/sizeof(float); pt++) { printf("%4d %g\n", pt, data_buf[pt]);

}

/* Close analyzer and exit. */ iclose(analyzer); return 0;

}


Table 6-1


Using Binary Data Encoding


The previous section describes how to query the measurement trace, and transfer it into your program using ASCII encoding. Binary encoding can be used for faster data transfers, as shown in the table below:

Trace Transfer Times (typical)

Number of Trace

Points

51

201

401

1601

Transfer Times (ms)

Binary

Transfer

21

23

30

82

ASCII

Transfer

47

164

314

1200

When using binary data transfers, the entire trace is sent from the analyzer to your program in a block called a definite length block. The details of block data are described in detail in

Chapter 4, “Data Types and Encoding.”

The definite length block contains a header and a data section. The header indicates how many bytes are in the data section.

In order to read the definite length block, your program must first read the header, and then read the data section. Refer to the example program

REALDATA in the Example Programs Guide for an example of how to do this.

In the REALDATA program, you will notice the following lines which read the definite block header:

180

190

ENTER @Hp8711 USING "%,A,D";A$,Digits

ENTER @Hp8711 USING "%,"&VAL$(Digits)&"D";Bytes and these lines which read the data section:

200

210

ASSIGN @Hp8711;FORMAT OFF

ENTER @Hp8711;Data1(*)




Each measurement point in the data section is represented as 4 or 8 bytes (32 or 64 bits), depending on whether single precision or double precision numbers are requested. When using HP BASIC or IBASIC, you must select double precision numbers to match BASIC's "REAL" data type. Do this using the SCPI command "FORM:DATA REAL,64" . If you are using another language that supports single precision data types, you can select single precision using the SCPI command "FORM:DATA

REAL,32" . Languages such as QuickBASIC and C have support for both single and double precision floating point numbers.

When transferring data using binary encoding, you may need to reverse the order of the bytes in each measurement point, since PCs frequently store IEEE floating point numbers with the byte order reversed. To instruct the analyzer to reverse the byte order of the data, send the command "FORMAT:BORDer SWAPped" before querying the trace data.




Table 6-2

Format Type

( FORMat:DATA )

REAL,32

Trace Data Transfer Sizes

The following table shows how many bytes are transmitted during trace data transfers. The left column shows the format of the data, which you can specify using the SCPI command Format:DATA . As you can see, the size of the measurement point data and trace data varies as you change format.

Trace Data Transfer Size Using TRACE:DATA Command

Type of

Data

Size of Single

Measurement Point

(bytes)

Real

4

Size of 201 Point

Complex

8

Real

809

Trace

(bytes)

Complex

1614

REAL,64

ASCII,5

ASCII,3

INT,16

IEEE 32-bit

Floating

Point

IEEE 64-bit

Floating

Point

ASCII numbers

ASCII numbers

Internal

Binary

8

13

11

—

16

26

22

8

1614

2613

2211

—

3222

5226

4422

1614

When transmitting data in "REAL" or "INT" format, a header is sent before the data block. The header indicates the size of the data block. The header size varies in length from 3 to 11 bytes. Refer to

Chapter 4, “Data

Types and Encoding,” for details on the header.

Transmitting ASCII data requires no header. The ASCII values are separated by commas, and a linefeed is sent after the last value. The sizes shown in the table include the size of the comma(s) and terminating linefeed. Typical data in ASCII,5 format:

-1.2254E+000,+5.0035E-001,+4.5226E-001,...




The analyzer stores its internal data with approximately 5 significant digits of resolution. Using REAL,32 or ASCII,5 format provides sufficient precision for data transfers. However, REAL,64 may be necessary when using a programming language which does not support IEEE 32-bit floating point.



Transferring Data with IBASIC

Table 6-3

Number of Trace Points

51

201

401

1601

Transferring Data with IBASIC

If you are using IBASIC, your IBASIC program can avoid the overhead of using OUTPUT and ENTER to transfer trace data, and instead use the analyzer's built-in high-speed subprograms. These built-in subroutines let you quickly move data between the analyzer's measurement arrays and your program's data arrays. For example, to read the analyzer's formatted data array, use the following:

10 DIM Fmt(1:201)

20 INTEGER Chan

30 LOADSUB Read_fdata FROM "XFER:MEM 0,0"

40 Chan=1

50 Read_fdata(Chan,Fmt(*))

Refer to the HP Instrument BASIC User's Handbook for more details.

The table below compares the speed of IBASIC using high-speed transfer subroutines with that of a fast external controller using the SCPI

TRACE:DATA? CH1FDATA query.

High-Speed Trace Transfer Times

Controller Using Binary

TRACE:DATA?

(ms)

21

23

30

82

IBASIC Using

Read_fdata

(ms)

7

10

13

32



Taking Sweeps

Taking Sweeps

When making measurements and querying traces, your program should perform the following steps:

1. Place the analyzer's sweep in hold.

2. Initiate a single sweep.

3. Wait for the sweep to complete.

4. Query the measurement trace.

Use the following program lines to perform these steps:

10 OUTPUT @Hp8711;"ABORT;:INIT1:CONT OFF"

20 OUTPUT @Hp8711;"INIT1"

30 OUTPUT @Hp8711;"*OPC?"

35 ENTER @Hp8711;Opc

40 OUTPUT @Hp8711;"TRACE:DATA? CH1FDATA"

45 ENTER @Hp8711;Fmt(*)

If you query the measurement trace while the analyzer is in continuous sweep, the query will still work, but the data may not be correct. Using

INIT and *OPC?

ensures that a complete sweep has finished before you query the measurement data. In many cases, you can also use the command " *WAI " in place of the " *OPC?

" query, replacing lines 30 and 35 above with:

30 OUTPUT @Hp8711;"*WAI"

However, there are cases where "*WAI" will produce incorrect results.

One case is when using IBASIC's high-speed subprograms to query the trace data.

"*WAI" only ensures that the SCPI commands following the

"*WAI" are not executed until the commands before the "*WAI" are complete. Since IBASIC subprograms don't use SCPI commands to access the trace data, "*WAI" is ineffective, and "*OPC?" should be used.

When using "*OPC?" , the ENTER statement following the "*OPC?" will wait until the previous SCPI commands are complete, preventing your program from executing beyond the ENTER statement. When using

"*WAI" , your program can continue to run and send SCPI commands, and the analyzer will buffer them and act upon them in order.

Chapter 2, “Synchronizing the Analyzer and a Controller,”

provides additional details.



CALC:DATA? versus TRACE:DATA?

CALC:DATA? versus TRACE:DATA?

The SCPI command "CALC1:DATA?" is functionally equivalent to the command "TRACE:DATA? CH1FDATA" . The two can be used interchangeably for trace queries of the formatted measurement data.

The "TRACE:DATA" command is more flexible, allowing you to query other measurement arrays and to download data to measurement arrays.



Querying Single Data Points Using Markers

Querying Single Data Points Using

Markers

If you only need to query a single data point, you can use a marker query instead of a trace query. The program segment below shows how to do this using the SCPI command CALC:MARK .

10

20

30

40

50

60

70


! Take sweep here

OUTPUT @Hp8711;"CALC1:MARK ON" ! turn on marker

OUTPUT @Hp8711;"CALC1:MARK1:X 177 MHz" ! set frequency

! read marker OUTPUT @Hp8711;"CALC1:MARK1:Y?"

ENTER @Hp8711;Marker_y

DISP Marker_y

You can also use the CALC:MARK:FUNC:RES?

query to return the results of a bandwidth search. The following program steps accomplish these tasks:

10

20

30

40

50

! Select -3 dB bandwidth

OUTPUT @Hp8711;"CALC:MARK:BWID -3"

! Get result of bandwidth search

OUTPUT @Hp8711;"CALC:MARK:FUNC:RES?"

ENTER @Hp8711;Bwidth,Center_freq,Q,Loss

For more information on using markers, refer to the Example Programs

Guide.



Accessing Other Measurement Arrays

Figure 6-2


The preceding sections describe how to query the formatted data array using the TRACE:DATA?

query with the argument CH1FDATA. The formatted array is the last array in the analyzer's data processing chain, and is generally of most interest.

The analyzer also allows you to query other measurement arrays which are earlier in its data processing chain.

Figure 6-2

shows the data processing chain.


The first array is the Raw Data Array, which contains each of the separate input components (A, B, R, B*, R*, X, Y, AUX) immediately after they are measured. These arrays can be queried and set, but doing so is of limited use, since the data values contained in the arrays are uncorrected, and are not directly correlated to any meaningful reference, such as 0 dBm.




The Error Coefficient arrays contain default correction values or values created during a measurement calibration. These arrays can be queried and set, but care should be exercised in setting them since incorrect measurements may result. If you wish to apply your own corrections in addition to the analyzer's current correction, the best technique is to use the Corrected Memory array and the Data/Memory feature, explained below.

The Corrected Data array contains the results of the currently selected measurement (Transmission, Reflection, etc.) after error correction and averaging have been applied. The measurement data in these arrays is represented as complex number pairs. When measuring the transmission response of a through cable, the magnitude of the complex numbers will be very close to 1.0. When measuring an open circuit, the magnitude of the complex numbers will be very close to 0.0. When measuring an amplifier, the magnitude of the complex numbers will be greater than 1.0.

The Corrected Memory array is filled with a copy of the Corrected Data array when the Data

−

> Memory operation is performed. It can be used to apply a gain correction to the measured data. This is described in the following section.

The Formatted Data array contains the measurement data after it has been formatted using the format selected by the [FORMAT] menu.

Querying the Formatted Data array is described in detail at the beginning of this chapter. You can also download data to this array, and the analyzer will display the data using the current Scale and Reference values.



Applying Gain Correction Using the Memory Trace

Applying Gain Correction Using the

Memory Trace

The Corrected Memory array is filled with a copy of the Corrected Data array when the Data

−

> Memory operation is performed. By setting the analyzer to perform Data/Memory trace math, you can apply your own correction factor to the measurement data trace by filling the Corrected

Memory array with the appropriate complex numbers.

In general, you should use the analyzer's calibration feature to correct for errors in your system. However, there may be cases where you wish to simulate the effect of adding a cable in series with your DUT, and observe how this imaginary cable will attenuate the measured response versus frequency. Or you may wish to apply an absolute offset to simulate the effect of adding or removing a pad from the measurement.

These simulations are easily accomplished using the Corrected Memory array and the Data/Memory feature.

The Corrected Data and Memory arrays contain complex linear data, as opposed to logged data. When displaying the traces using Lin Mag format, the result of the Data divided by Memory operation (Data/Mem) will be to divide each point of the data trace by each point of the memory trace. When displaying data in Log Mag format, the result of

Data/Memory will be equivalent to subtracting the Log Mag value of the

Memory trace from that of the Data trace.



Applying Gain Correction Using the Memory Trace

The following example BASIC code segment shows how to download a complex array from your program to the analyzer's Memory trace. The program's "Mem" array is initialized with the proper values such that when the analyzer computes Data divided by Memory, the desired increasing gain will be applied.

100

110

120

130

140

150

160

170

180

190

200

210

220

230

240

250

260

270

280

290

300

310

320

REAL Mem(1:201,1:2)


! Fill memory array (denominator in Data/Mem)

! with values that will result in an

! upward sloping gain factor vs. frequency.

! Used to compensate for cable loss vs. frequency

! Adds 0 dB of gain at start freq; 3 dB at stop freq

FOR Pt=1 TO 201

Gain_factor_db=3.0*(Pt

−

1)/200 ! 0..3 dB Power

Gain_factor_lin=10^(Gain_factor_db/20)

Mem(Pt,1)=1.0/Gain_factor_lin ! real

Mem(Pt,2)=0.0

NEXT Pt

! imag

! Download to the memory trace

OUTPUT @Hp8711;"FORM:DATA ASCII"

OUTPUT @Hp8711;"TRACE:DATA CH1SMEM";

FOR Pt=1 TO 201

! Note the ";"

FOR I=1 TO 2

OUTPUT @Hp8711;",";Mem(Pt,I);

NEXT I

NEXT Pt

! Note the ";"

OUTPUT @Hp8711;"" ! Send linefeed

OUTPUT @Hp8711;"CALC1:MATH (IMPL/CH1SMEM)" ! Data/Mem

The example above downloads data to the corrected memory array. The data is sent by the program to the analyzer using ASCII encoding. The data is sent as ASCII characters, separated by commas. The analyzer accepts the comma separated list of numbers until it receives a linefeed to terminate the command. The program uses semicolons at the end of some OUTPUT statements to avoid sending a linefeed until all of the data has been sent. After the last number is sent, the program sends a linefeed, and the analyzer accepts the data.

Remember, for faster transfers, use binary data encoding instead of

ASCII.



Performing Your Own Data Processing


After the analyzer has made a measurement, you can read the measurement trace and perform your own post-processing on it, and display the result on the screen. This is done using these steps:

1. Initiate a sweep.

2. Wait for the sweep to finish.

3. Read the measurement data into an array in your program.

4. Perform your post-processing on the measurement data.

5. Write (download) the post-processed data to the analyzer's memory trace.

You may want to instruct the analyzer to display only the memory trace and not the data trace, so that only your post-processed data is seen.




The program below demonstrates how to perform data post-processing. It takes the measurement data and reverses it, such that the low frequency data is displayed on the right end of the trace, and the high frequency data is displayed on the left.

100

110

120

130

140

150

160

170

180

190

200

210

220

230

235

240

250

260

270

280

290

! Display the measurement data backwards

REAL Fmt(1:201)


!

OUTPUT @Hp8711;"FORM:DATA ASCII"

OUTPUT @Hp8711;"ABOR;INIT:CONT OFF;*WAI"

OUTPUT @Hp8711;"DISP:WIND:TRAC1 OFF;TRAC2 ON"

LOOP

! Take sweep

OUTPUT @Hp8711;"INIT1;*WAI"

! Read the trace from the formatted data array


ENTER @Hp8711;Fmt(*)

! Download the trace, backwards,

! to the formatted memory array

OUTPUT @Hp8711;"TRACE:DATA CH1FMEM";

FOR Pt=1 TO 201

OUTPUT @Hp8711;",";Fmt(202-Pt);

NEXT Pt

OUTPUT @Hp8711;""

END LOOP

! Send linefeed

! Note the ";"

! Note the ";"

This example program uses ASCII trace data transfers. Higher speed can be achieved using binary data transfers. If using IBASIC, high-speed subroutines can be used for even greater performance. Refer to the

IBASIC Handbook for details.



Downloading Trace Data Using Binary Encoding

Downloading Trace Data Using Binary

Encoding

Data traces can be downloaded to the analyzer using binary encoding.

Using binary encoding is faster than using ASCII encoding. As mentioned in

“Using Binary Data Encoding” on page 6-6 , the binary

encoded trace is transferred as a block; the block contains a header and a data section. There are two different types of blocks that can be used: a definite length block, and an indefinite length block.

To send trace data using a definite length block, your program must calculate the number of bytes in the data segment of the block, and create a block header which tells the analyzer how many bytes are in the data segment.

For example, if you are sending a trace with 201 data points and using

64-bit floating point numbers for each data point ( FORM:DATA

REAL,64 ), the block's data segment will contain 1608 bytes (201 points *

8 bytes/point). The header characters for a 1608 byte block are: "#41608".

The first digit after the "#", "4" tells how many following digits are used to specify the size. In this case, 4 digits follow, and those digits are

"1608", meaning that the block contains 1608 bytes.

When you send a definite length block to the analyzer, the analyzer will read the data segment bytes, stopping when it receives the number specified in the block header.

To send trace data using an indefinite length block, your program sends a block header of "#0", followed by the data segment. After sending the data segment, your program must terminate the data block by sending an EOI. The analyzer will read the data segment bytes, stopping when it receives an EOI. To send an EOI using BASIC, you can use the statement:

OUTPUT @Hp8711;END



Internal Measurement Arrays

Figure 6-3


The following sections describe the sequence of math operations and the resulting data arrays as the measurement information flows from the raw data arrays to the display. This information explains the measurement arrays accessible via GPIB.

Figure 6-3 is a data processing flow diagram that represents the flow of

numerical data. The data passes through several math operations, denoted in the figure by single-line boxes. Most of these operations can be selected and controlled with the front panel CONFIGURE block menus. The data is stored in arrays along the way, denoted by double-line boxes. These arrays are places in the flow path where data is accessible via GPIB. While only a single flow path is shown, two identical paths are available, corresponding to measurement channels 1 and 2.


Raw Data Arrays

These arrays are linear measurements of the inputs used in the selected measurement. Note that these are pairs of complex numbers. The arrays are directly accessible via GPIB and are referenced as CH[1|2]AFWD ,


Table 6-4



CH[1|2]BFWD and CH[1|2]RFWD . Raw data for AUX INPUT is not available via GPIB. Use the corrected data array to access AUX INPUT data.

Raw Data Arrays

Selected Measurement Raw Arrays

A

B

Transmission (B/R)

Reflection (A/R)

B = CH[1|2]BFWD , R= CH[1|2]RFWD

A = CH[1|2]AFWD , R= CH[1|2]RFWD

A = CH[1|2]AFWD

B = CH[1|2]BFWD

R

Power (B*)

R = CH[1|2]RFWD

B*= CH[1|2]BFWD

Conversion Loss (B*/R*) B*= CH[1|2]BFWD , R*= CH[1|2]RFWD

R* R*= CH[1|2]RFWD

AM Delay (Y/X)

X

Y

Y/R*

Y/X, X/Y

Y = CH[1|2]BFWD , X = CH[1|2]RFWD

X = CH[1|2]RFWD

Y = CH[1|2]BFWD

Y = CH[1|2]BFWD , R* = CH[1|2]RFWD

Y = CH[1|2]BFWD , X = CH[1|2]RFWD

Ratio Calculations

These are performed if the selected measurement is a ratio (e.g. A/R or

B/R). This is simply a complex divide operation. If the selected measurement is absolute (e.g. A or B), no operation is performed.

Error Correction

Error correction is performed next if correction is turned on. Error correction removes repeatable systematic errors (stored in the error coefficient arrays) from the raw arrays. The operations performed depend on the selected measurement type.


NOTE



Error Coefficient Arrays

The error coefficient arrays are either default values or are created during a measurement calibration. These are used whenever correction is on. They contain complex number pairs, are accessible via GPIB, and are referenced as CH[1|2]SCORR1 , CH[1|2]SCORR2 , CH[1|2]SCORR3 and CH[1|2]SCORR4 .

Error Coefficient Arrays Table 6-5

Selected Measurement Error Coefficient Arrays

Transmission (B/R) Response CH[1|2]SCORR1 Tracking

Transmission (B/R) Response & Isolation CH[1|2]SCORR1 Tracking

CH[1|2]SCORR2 Isolation Term

Transmission (B/R) Enhanced Response CH[1|2]SCORR1 Directivity

CH[1|2]SCORR2 Source Match

CH[1|2]SCORR3 Reflection Tracking

CH[1|2]SCORR4 Transmission Tracking

Reflection (A/R)

Broadband Internal

CH[1|2]SCORR1 Directivity

CH[1|2]SCORR2 Source Match

CH[1|2]SCORR3 Tracking

CH[1|2]SCORR1 R* Response

These arrays do not apply to Broadband External measurements.




Table 6-6

Forward

2-Port Error Coefficient Arrays

Direction Error Coefficient Arrays


CH[1|2]SCORR2 Source match

CH[1|2]SCORR3 Reflection tracking

Reverse

CH[1|2]SCORR4 Transmission tracking

CH[1|2]SCORR5 Load match

CH[1|2]SCORR6 Isolation


CH[1|2]SCORR8 Source match

CH[1|2]SCORR9 Reflection tracking

CH[1|2]SCORR10 Transmission tracking

CH[1|2]SCORR11 Load match

CH[1|2]SCORR1 2 Isolation




Averaging

Averaging is a noise reduction technique. This calculation involves taking the complex exponential average of several consecutive sweeps.

This averaging calculation is different than the System Bandwidth setting. System Bandwidth uses digital filtering, applying noise reduction to the measured data before it is stored into the Raw Data

Arrays.

Corrected Data Arrays

The combined results of the ratio, error correction and averaging operations are stored in the corrected data arrays as complex number pairs. These arrays are accessible via GPIB and referenced as

CH[1|2]SDATA .

Corrected Memory Arrays

If the Data

−

>Mem or Normalize operations are performed, the corrected data arrays are copied into the corrected memory arrays. These arrays are accessible via GPIB and referenced as CH[1|2]SMEM .




Trace Math Operation

This selects either the corrected data array, or the corrected memory array, or both to continue flowing through the data processing path. In addition, the complex ratio of the two (Data/Memory) can also be selected. If memory is displayed, the data from the memory arrays goes through exactly the same data processing flow path as the data from the data arrays.

Electrical Delay

This block adds or subtracts phase, based on the settings of Phase Offset,

Electrical Delay, and Port Extension. The Electrical Delay and Port

Extension features add or subtract phase in proportion to frequency. This is equivalent to "line stretching" or artificially moving the measurement reference plane. (See your analyzer’s User Guide for more details on these features.)

Transform (Option 100 only)

This block converts frequency domain data into distance domain, or into an SRL impedance value when measuring fault location or SRL. The transform employs an inverse fast Fourier transform (FFT) algorithm to accomplish the conversion.

Formatting

This converts the complex number pairs into a scalar representation for display, according to the selected format (e.g. Log Mag, SWR, etc). These formats are often easier to interpret than the complex number representation. Note that after formatting, it is impossible to recover the complex data.

Formatted Arrays

The results so far are stored in the formatted data and formatted memory arrays. It is important to note that marker values and marker functions are all derived from the formatted arrays. Limit testing is also performed on the formatted arrays. These arrays are accessible via GPIB and referenced as CH[1|2]FDATA and CH[1|2]FMEM .




Offset and Scale

These operations prepare the formatted arrays for display. This is where the reference position, reference value, and scale calculations are performed, as appropriate for the format.





7 Using Graphics

7-1

NOTE

Using Graphics

Introduction

Introduction

The analyzer has a set of user graphics commands that can be used to create graphics and messages on the display. The GRAPHICS example program in the Example Programs Guide uses some of these commands to draw a simple setup diagram. These commands, listed below, are of the form:

DISPlay:WINDow[1|2|10]:GRAPhics:<mnemonic>.

The number specified in the WINDow part of the command selects where the graphics are to be written.

WINDow1 draws the graphics to the channel 1 measurement screen. (This is the default if no window is specified in the mnemonic.)

WINDow2

WINDow10 draws the graphics to the channel 2 measurement screen.

draws the graphics to an IBASIC display partition. The graphics can only be output in red on a PCL printer.

When graphics commands are used to write directly to a measurement screen, they write to the static graphics plane (the same plane where the graticule is drawn). There is no sweep-to-sweep speed penalty once the graphics have been drawn.


Using Graphics

Introduction

Unless otherwise specified, the graphics commands listed below start at the current pen location. All sizes are dimensioned in pixels.

DISPlay:WINDow[1|2|10]:GRAPhics:CIRCle <y_radius>

DISPlay:WINDow[1|2|10]:GRAPhics:CLEar

DISPlay:WINDow[1|2|10]:GRAPhics:COLor <pen>

• color choices are: 0 for erase, 1 for bright, 2 for dim

DISPlay:WINDow[1|2|10]:GRAPhics[:DRAW] <new_x>,<new_y>

DISPlay:WINDow[1|2|10]:GRAPhics:LABel <string>

DISPlay:WINDow[1|2|10]:GRAPhics:LABel:FONT <font>

• font choices are: SMALl , HSMall , NORMal , HNORmal , BOLD , HBOLd ,

SLANt , HSLant ( H as the first letter of the font name indicates highlighted text – inverse video).

DISPlay:WINDow[1|2|10]:GRAPhics:MOVE <new_x>,<new_y>

DISPlay:WINDow[1|2|10]:GRAPhics:RECTangle

<width>,<height>

DISPlay:WINDow[1|2|10]:GRAPhics:SCALe

<xmin>,<xmax>,<ymin>,<ymax>

DISPlay:WINDow[1|2|10]:GRAPhics:STATe?


Using Graphics

Window Geometry

Figure 7-1

Window Geometry

Even though there are only three graphics windows, these windows can have different sizes and locations.

The size and location of the graphics window are determined by the display configuration currently in use — split screen measurements, full screen measurements, and full or partial IBASIC display partitions will affect the dimensions of the graphics window in use.

The sizes of the different graphics windows are listed below.

Figure 7-1

shows the display partitions.

• Measurement channel 1 or 2 full screen measurement:

• Measurement channel 1 or 2 split screen measurement:

• IBASIC full screen display:

• IBASIC upper display:

• IBASIC lower display:

Pixel Dimensions with Available Display Partitions


NOTE

Using Graphics

Window Geometry

There is a set of queries that can be used to determine the size and location of the display window in use.

These queries, listed below, return the width and height of the window or the absolute location of its lower left or upper right corners. All the coordinates and sizes are dimensioned in pixels.

• DISPlay:WINDow[1|2|10]:GEOMetry:LLEFt?

• DISPlay:WINDow[1|2|10]:GEOMetry:SIZE?

• DISPlay:WINDow[1|2|10]:GEOMetry:URIGht?

The origin of every graphics window is its lower left corner. The locations returned in response to the LLEFt and URIGht are relative to the

absolute origin of the entire display, not to the graphics window.


NOTE

Using Graphics

The Graphics Buffer

The Graphics Buffer

The analyzer has a graphics buffer that is used to refresh the graphics display if needed. When the buffer is full, additional graphics can still be drawn — but they will not be refreshed. The graphics buffer can be turned on and off using the following command (which is used in the

GRAPHICS example program).

DISPlay:WINDow:GRAPhics:BUFFer[:STATe] <ON|OFF>

The graphics buffer will hold up to:

• 500 lines

• 40 circles

• 40 rectangles

• 50 strings (60 characters long)

Use the following command to clear the graphics buffer and user-graphics display.

DISPlay:WINDow:GRAPhics:CLEar

Only graphics that can be refreshed will be printed or plotted. If you intend to print or plot your graphics, make sure they will fit within the graphics buffer.


8 Front Panel Keycodes

8-1

Front Panel Keycodes

Front Panel Keycodes


Your program can control or monitor the analyzer's front panel with the use of the SCPI SYSTem:KEY commands.

Controlling the Front Panel

The front panel can be controlled by sending commands to execute the function of specific keys. The SCPI command SYSTem:KEY <char> sends a key name to the analyzer which executes the same function as the corresponding front panel key. For example, SYSTem:KEY FREQ will execute the function of the FREQ hardkey.

Every hardkey and softkey has a unique key name. Refer to the last table in this chapter for a list of all key names.

Monitoring the Front Panel

The front panel can be monitored to determine when a key has been pressed or when the knob (RPG — rotary pulse generator) has been turned. Key presses from an attached PC keyboard can also be captured.

When keys are pressed or when the knob is turned, the analyzer detects this event, sets bit 0 of the Device Status Register (see

Chapter 5, “Using

Status Registers”

), and stores the associated information in a key queue.

Your program can use the SCPI SYSTem:KEY commands to read the contents of the key queue.


Table 8-1

Table 8-2



The SCPI query SYSTem:KEY:TYPE?

returns a string indicating the type of key press event:

Key Press Return Values

Return Value

NONE

KEY

RPG

ASC

Meaning

No key has been pressed.

A front panel key has been pressed.

The analyzer's knob has been turned.

A key on the ASCII PC DIN keyboard has been pressed.

The SCPI query SYSTem:KEY[:VALue]?

returns a number describing the type of key press. The meaning of the number depends on the key type returned by the SYSTem:KEY:TYPE?

query:

Key Press Types

SYST:KEY:TYPE

NONE

KEY

RPG

ASC

SYST:KEY:VALUE Meaning

No meaning. Returns

−

1.

A number from 0 to 56 representing the "key code" of the front panel key. See following table for list.

The number of knob "ticks." Positive values indicate a clock-wise turn; negative numbers indicate counter-clockwise. Larger numbers indicate the knob has been turned faster or further.

The ASCII value of the pressed key.




Key Queue

The SYSTem:KEY[:VALue]?

query removes the key from the key queue, so that you can read the next key. For this reason, you must perform the

SYSTem:KEY:TYPE?

query before performing the

SYSTem:KEY[:VALue]?

.

The Key Queue stores up to 32 key press events. After 32 key presses, the queue is full, and no more key press events can be stored without reading from the queue (using SYSTem:KEY[:VALue]?

). Subsequent key presses or knob ticks will be ignored when the queue is full.

You can query the queue length using this command:

SYSTem:KEY:QUEue:MAXimum?

You can clear the queue using this command:

SYSTem:KEY:QUEue:CLEar

You can check how many key presses or knob tick events have occurred using this command:

SYSTem:KEY:QUEUE:COUNt?

You can turn the key queue on or off using this command:

SYSTem:KEY:QUEUE[:STATe] <ON|OFF>

When the queue is turned off, your program must read each key before a following key is pressed, or information will be lost. It is generally best to leave the queue enabled.

Example Program

For a complete example of how to read the front panel keys and knob, refer to the KEYCODE example program in the Example Programs

Guide.


Table 8-3



Key Codes

Key Label

3

4

5

0

1

2

8

9

6

7

ENTER

Softkey 1

Softkey 2

Softkey 3

Softkey 4

Softkey 5

Softkey 6

Softkey 7

Softkey 8

16

17

18

19

20

12

13

14

15

6

7

4

5

2

3

0

1

10

11

Key Code

GPIB Key

Name

SOFTkey1

SOFTkey2

SOFTkey3

SOFTkey4

SOFTkey5

SOFTkey6

SOFTkey7

SOFTkey8

ZERO

ONE

TWO

THRee

FOUR

FIVE

SIX

SEVen

EIGHt

NINE

ENTer




Key Label

.

−

8-6

BEGIN

MEAS 12

MEAS 2

POWER

MENU

FREQ

SWEEP

CAL

DISPLAY

SCALE

AVG

FORMAT

MARKER

SAVE RECALL

SYSTEM OPTIONS

HARD COPY

PRESET

Key Code

GPIB Key

Name

POINt

MINus

UP

DOWN

BEGin

MEAS1

MEAS2

POWer

MENU

FREQ

SWEep

CAL

DISPLAY

SCALe

AVG

FORMat

MARKer

SAVE

SYSTem

HARDcopy

PRESet

46

47

48

43

44

45

49

50

51

52

53

40

41

42

21

22

23

24

54

55

56


9 Introduction to SCPI

9-1

Introduction to SCPI

Introduction to SCPI

Introduction to SCPI

This chapter is a guide to GPIB control of the analyzer. Its purpose is to provide concise information about the operation of the analyzer under

GPIB control. The reader should already be familiar with making measurements with the analyzer and with the general operation of

GPIB.

Standard Commands for Programmable Instruments (SCPI) is a programming language designed specifically for controlling instruments by Agilent Technologies and other industry leaders. SCPI provides commands that are common from one instrument to another. This elimination of "device specific" commands for common functions allows programs to be used on different instruments with very little modification.

SCPI was developed to conform to the IEEE 488.2 standard (replacing

IEEE 728-1982). The IEEE 488.2 standard defines the syntax and data formats used to send data between devices, the structure of status registers, and the commands used for common tasks. For more information, refer to the IEEE standard itself. SCPI defines the commands used to control device-specific functions, the parameters accepted by these functions, and the values they return.


Figure 9-1


The Command Tree


The SCPI standard organizes related instrument functions by grouping them together on a common branch of a command tree (see

Figure 9-2 on page 9-6 for an example command tree). Each branch is assigned a

mnemonic to indicate the nature of the related functions. The analyzer has 16 major SCPI branches or subsystems. See

Figure 9-1

for a model of how these subsystems are organized to manage the measurement and data flow for the analyzer.

Measurement and Data Flow of the Analyzer




The analyzer's major SCPI subsystems and their functions are described below.

ABORt Aborts any sweep in progress.

CALCulate Configures post-measurement processing of the measured data (such as marker and limit testing functions).

CALibration Controls zeroing the broadband diode detectors.

CONFigure Configures the analyzer to measure a specific device type, including amplifiers, mixers, filters, and cables.

CONTrol

DIAGnostic

DISPlay

Configures the analyzer for use with a multiport test set. Used with the 87075C multiport test set only.

Performs a number of diagnostic and I/O functions.

Includes LAN diagnostics, port reads and writes, correction constants utilities, and other miscellaneous functions.

Controls the display of measurement data, annotation and user graphics.

FORMat

HCOPy

INITiate

Controls the format of data transfers over the GPIB.

For more information about GPIB data transfers, refer to

Chapter 4, “Data Types and Encoding.”

Controls hardcopy (printer and plotter) output.

Controls the triggering of sweeps.

MMEMory

OUTPut

POWer

PROGram

ROUTe

Controls mass storage of instrument states and data

(disk and internal memory interface functions).

Turns on/off the source output power (power to the device under test).

Specifies frequency sweeps or power sweeps.

Interfaces IBASIC programs and commands with an external controller. For more information on IBASIC programming, refer to HP Instrument BASIC User's

Handbook.

Selects transmission and reflection ports.

Selects ports on multiport test sets (used with the

87075C multiport test set only).


NOTE



SENSe

SOURce

Configures parameters (such as the frequency and measurement parameters) related to the sweep and the measured signal (from the device under test). This subsystem also controls the narrowband calibration routines.

Controls the RF output power level of the source

(power to the device under test).

STATus

SYSTem

Contains the commands for using the SCPI status registers. (For more information about using the status registers, refer to

Chapter 5, “Using Status Registers.”

)

Contains miscellaneous system configuration commands (such as I/O port, clock and softkey control).

Performs instrument self-test functions.

TEST

TRACe Interfaces with the internal data arrays (functions such as data transfer and trace memory).

Controls the source of the sweep triggering.

TRIGger

When many functions are grouped together on a particular branch, additional branching is used to organize these functions into groups that are even more closely related. The branching process continues until each analyzer function is assigned to its own branch. For example, the function that turns on and off the marker tracking feature is assigned to the TRACKING branch of the FUNCTION branch of the MARKER branch of the CALCULATE subsystem. The command looks like this:

CALCULATE:MARKER:FUNCTION:TRACKING ON

Colons are used to indicate branching points on the command tree. A parameter is separated from the rest of the command by a space.


Figure 9-2



Partial Diagram for the CALCulate Subsystem Command Tree



Sending Multiple Commands

Sending Multiple Commands

Multiple commands can be sent within a single program message by separating the commands with semicolons. For example, the following program message — sent within an HP BASIC OUTPUT statement — turns on the marker reference and moves the main marker to the highest peak on the trace:

OUTPUT 716;"CALCULATE:MARKER:MODE

RELATIVE;:CALCULATE:MARKER:MAXIMUM"

One of the analyzer's command parser main functions is to keep track of a program message's position in the command tree. This allows the previous program message to be simplified. Taking advantage of this parser function, the simpler equivalent program message is:

OUTPUT 716;"CALCULATE:MARKER:MODE RELATIVE;MAXIMUM"

In the first version of the program message, the semicolon that separates the two commands is followed by a colon. Whenever this occurs, the command parser is reset to the base of the command tree. As a result, the next command is only valid if it includes the entire mnemonic path from the base of the tree.

In the second version of the program message, the semicolon that separates the two commands is not followed by a colon. Whenever this occurs, the command parser assumes that the mnemonics of the second command arise from the same branch of the tree as the final mnemonic of the preceding command.

MODE , the final mnemonic of the first command, arises from the MARKER branch. So MAXIMUM , the first mnemonic of the second command, is also assumed to arise from the

MARKER branch.

The following is a longer series of commands — again sent within

HP BASIC OUTPUT statements — that can be combined into a single program message:

OUTPUT 716;"CALCULATE:MARKER:STATE ON"

OUTPUT 716;"CALCULATE:MARKER:MODE RELATIVE"

OUTPUT 716;"CALCULATE:MARKER:MAXIMUM"

OUTPUT 716;"CALCULATE:MARKER:FUNCTION:TRACKING ON"

The single program message is:

OUTPUT 716;"CALCULATE:MARKER:STATE ON;MODE

RELATIVE;MAXIMUM;FUNCTION:TRACKING ON"


NOTE


Command Abbreviation

Command Abbreviation

Each command mnemonic has a long form and a short form. The short forms of the mnemonics allow you to send abbreviated commands. Only the exact short form or the exact long form is accepted.

The short form mnemonics are created according to the following rules:

• If the long form mnemonic has four characters or less, the short form is the same as the long form. For example, DATA remains DATA .

• If the long form mnemonic has more than four characters and the fourth character is a consonant, the short form consists of the first four characters of the long form. For example, CALCULATE becomes

CALC .

• If the long form mnemonic has more than four characters and the fourth character is a vowel, the short form consists of the first three characters of the long form. For example, LIMIT becomes LIM .

The short form of a particular mnemonic is indicated by the use of

UPPER-CASE characters in this manual.

SCPI is not case sensitive so any mix of upper and lower-case lettering can be used when sending commands to the analyzer.

If the rules listed in this section are applied to the last program message in the preceding section, the statement:

OUTPUT 716;"CALCULATE:MARKER:STATE ON;MODE

RELATIVE;MAXIMUM;FUNCTION:TRACKING ON" becomes:

OUTPUT 716;"CALC:MARK:STAT ON;MODE REL;MAX;FUNC:TRAC ON"


NOTE


Implied Mnemonics

Implied Mnemonics

Some mnemonics can be omitted from GPIB commands without changing the effect of the command. These special mnemonics are called implied mnemonics, and they are used in many subsystems. In addition to entire mnemonics, variable parts of some mnemonics may also be implied. These are usually a number indicating a particular measurement channel, marker, or similar choice.

When a number is not supplied for an implied variable, a default choice is assumed; this choice is always 1 .

The INITIATE subsystem contains both the implied mnemonic

IMMEDIATE at its first branching point and an implied variable for the measurement channel. The command to trigger a new sweep is shown in the "SCPI Command Summary" as:

OUTPUT 716;"INITiate[1|2][:IMMediate]

Any of the following forms of the command can be sent to the analyzer

(using HP BASIC) to trigger a new sweep on measurement channel 1:

OUTPUT 716;"INITIATE1:IMMEDIATE"

OUTPUT 716;"INITIATE:IMMEDIATE"

OUTPUT 716;"INITIATE1"

OUTPUT 716;"INITIATE"

If the sweep is to be triggered for measurement channel 2, the channel number must be specified:

OUTPUT 716;"INITIATE2:IMMEDIATE"

OUTPUT 716;"INITIATE2"



Parameter Types

Parameter Types

Parameters are used in many commands. The analyzer uses several types of parameters with different types of commands and queries. When a parameter is sent with a SCPI command, it must be separated from the command by a space. If more than one parameter is sent, they are separated from each other by commas.

Numeric Parameters

Most subsystems use numeric parameters to specify physical quantities.

Simple numeric parameters accept all commonly used decimal representations of numbers, including optional signs, decimal points, and scientific notation. If an instrument setting programmed with a numeric parameter can only assume a finite number of values, the instrument automatically rounds the parameter. In addition to numeric values, all numeric parameters accept MAXimum and MINimum as values (note that

MAXimum and MINimum can be used to set or query values).

<num> is used in this document to denote a numeric parameter.

An example is the command to set the stop frequency for a measurement. The first command below sets the stop frequency to a specific value. The second command below sets the stop frequency to its maximum possible value (1300 MHz for 8712ET/ES or 3000 MHz for

8714ET/ES).

OUTPUT 716;"SENSE1:FREQUENCY:STOP 1300 MHZ"

OUTPUT 716;"SENSE1:FREQUENCY:STOP MAX"



Parameter Types

Query Response

When a numeric parameter is queried, the number is returned in one of the three numeric formats.

NR1

NR2

Integers (such as +1, 0, -1, 123, -12345)

Floating point number with an explicit decimal point

(such as 12.3, +1.234, -0.12345)

NR3 Floating point number in scientific notation (such as

+1.23E+5, +123.4E-3, -456.789E+6)

An example is the response to a query of the stop frequency after executing the above commands (this response is of the NR3 type).

OUTPUT 716;"SENSE1:FREQUENCY:STOP?" returns the value 1.3E+9 .

Character Parameters

Character parameters (sometimes referred to as discrete parameters) consist of ASCII characters. They are typically used for program settings that have a finite number of values.

These parameters use mnemonics to represent each valid setting. They have a long and a short form which follow the same rules as command mnemonics.

<char> is used in this document to denote a character parameter.

An example of a command using a character parameter is the command that selects the format in which the measurement data is displayed:

OUTPUT 716;"CALCULATE1:FORMAT MLOGARITHMIC"

Query Response

When a character parameter is queried the response is always the short form of the mnemonic that represents the current setting. An example is the response to a query of the data format after executing the above command.

OUTPUT 716;"CALCULATE1:FORMAT?" returns the value MLOG .



Parameter Types

Boolean Parameters

Boolean parameters are used for program settings that can be represented by a single binary condition. Commands that use this type of parameter accept the values ON (or 1 ) and OFF (or 0 ).

<ON|OFF> is used in this document to denote a boolean parameter.

An example of a command that uses a boolean parameter is the command that makes the analyzer continuously trigger (or stop triggering) measurements.

OUTPUT 716;"INITIATE:CONTINUOUS ON"

A special group of commands uses boolean parameters to control automatic functions of the instrument, such as automatically selecting the fastest possible sweep speed. With these automatic functions an additional value is available for the parameter. This value ONCE causes the function to execute once before turning off.

Query Response

The response when a boolean parameter is queried is a single NR1 number indicating the state 1 for on or 0 for off. An example is the response to a query on the sweep trigger status after executing the above command.

OUTPUT 716;"INITIATE:CONTINUOUS?" returns the value 1 .



Parameter Types

String Parameters

String parameters can contain virtually any set of ASCII characters. The string must begin with a single quote ( ' ) or a double quote ( " ) and end with the same character (called the delimiter). The delimiter can be included as a character (embedded) inside the string by typing it twice without any characters in between. For example:

OUTPUT 716;"DISP:ANN:TITL:DATA 'DUT''S PHASE'"

<string> is used in this document to denote a string parameter.

An example of a command that uses a string parameter is the

CONFIGURE command:

OUTPUT 716;"CONFIGURE 'FILTER:TRANSMISSION'"

Some of the string parameters used by the analyzer, like

'FILTER:TRANSMISSION' in the example above, follow the same rules that apply to mnemonics. They may have branching

( 'FILTER:REFLECTION' is a related command) and abbreviated versions.

Query Response

The response when a string parameter is queried is a string. The only difference is that the response string will only use double quotes as delimiters. Embedded double quotes may be present in string response data. When the string follows the "SCPI" mnemonic rules, the string returned in response to a query is in the abbreviated form. An example is the response to the configuration status of the analyzer (after executing the last command).

OUTPUT 716;"CONFIGURE?" returns the value "FILT:TRAN" .

Block Parameters

Block parameters are typically used to transfer large quantities of related data (like a data trace). Blocks can be sent as definite length blocks or indefinite length blocks — the instrument will accept either form. For more information on block data transfers refer to

Chapter 4,

“Data Types and Encoding.”

<block> is used in this document to denote a block parameter.



Syntax Summary

Figure 9-3

Syntax Summary

The following conventions are used throughout this manual whenever

SCPI mnemonics are being described.

angle brackets

(< >) are used to enclose required parameters within a command or query. The definition of the variable is usually explained in the accompanying text.

square

brackets ([ ]) are used to enclose implied or optional parameters within a command or query.

UPPERlower case are used to indicate the short form (upper-case) of a given mnemonic. The remaining (lower-case) letters are the rest of the long form mnemonic.

SCPI Command Syntax



Syntax Summary

The following elements have special meanings within a SCPI program message (or combination or mnemonics).

colon (:) When a command or query contains a series of mnemonics, they are separated by colons. A colon immediately following a mnemonic tells the command parser that the program message is proceeding to the next level of the command tree. A colon immediately following a semicolon tells the command parser that the program message is returning to the base of the command tree.

semicolon (;) When a program message contains more than one command or query, a semicolon is used to separate them from each other.

comma (,) A comma separates the data sent with a command or returned with a response.

space ( ) One space is required to separate a command or query from its data (or parameters). Spaces are not allowed inside a command or query.



IEEE 488.2 Common Commands


IEEE 488.2 defines a set of common commands. All instruments are required to implement a subset of these commands, specifically those commands related to status reporting, synchronization and internal operations. The rest of the common commands are optional. The following list details which of these IEEE 488.2 common commands are implemented in the analyzer and the response of the analyzer when the command is received.

*CLS Clears the instrument Status Byte by emptying the error queue and clearing all event registers, also cancels any preceding *OPC command or query (does not change the enable registers or transition filters).

*ESE <num>

*ESE?

*ESR?

*IDN?

Sets bits in the Standard Event Status Enable Register

— current setting is saved in non-volatile memory.

Reads the current state of the Standard Event Status

Enable Register.

Reads and clears the current state of the Standard

Event Status Register.

Returns a string that uniquely identifies the analyzer.

The string is of the form

*LRN?

"HEWLETT-PACKARD,8712,<serial number>,<software evision>"

This returns a string of device specific characters that, when sent back to the analyzer will restore the instrument state active when *LRN?

was sent. Data formatting ( ENTER USING "-K" in HP BASIC) or a similar technique should be used to ensure that the transfer does not terminate on a carriage return or line feed (both

C

R

and

L

F

are present in the learn string as part of the data).


*OPC

*OPC?

*OPT?



Operation complete command. The analyzer will generate the OPC message in the Standard Event

Status Register when all pending overlapped operations have been completed (e.g. a sweep, or a preset). For more information about overlapped operations, refer to

“Overlapped Commands” on page 2-3 .

Operation complete query. The analyzer will return an

ASCII "1" when all pending overlapped operations have been completed.

Returns a string identifying the analyzer's option configuration. The string is of the form "1E1,100" .

The options are identified by the following:

*PCB <num>

*PSC <num>

1EC 75 ohm

1E1 60 dB step attenuator

100 SRL and Fault Location

Sets the pass-control-back address (the address of the controller before a pass control is executed).

Sets the state of the Power-on Status Clear flag — flag is saved in non-volatile memory. This flag determines whether or not the Service Request enable register and the Event Status enable register are cleared at powerup.




*RST Executes a device reset and cancels any pending *OPC command or query. The contents of the instrument's nonvolatile memory are not affected by this command.

This command is different from the front panel

PRESET function in the state of the commands (and their reset states) listed below.

The preset instrument state is described in the User's

Guide.

*SRE <num>

*SRE?

*STB?

*TRG

*TST?

*WAI

INITiate:CONTinuous

OUTPut[:STATe]

CALibration:ZERO:AUTO

SENSe:CORRection[:STATe]

SENSe:SWEep:POINts

SOURce:POWer

= OFF

= OFF

= OFF

= OFF

= MAX

= MIN

Sets bits in the Service Request Enable Register.

Current setting is saved in non-volatile memory.

Reads the current state of the Service Request Enable

Register.

Reads the value of the instrument Status Byte. This is a non-destructive read—the Status Byte is cleared by the *CLS command.

Triggers a sweep on the active measurement channel when in Trigger Hold mode. Ignored if in continuous sweep.

Returns the result of a complete self-test. An ASCII 0 indicates no failures found. Any other character indicates a specific self-test failure. Does not perform any self-tests. See the Service Guide for further information.

Prohibits the instrument from initiating any new commands until all pending overlapped commands have been initiated.


10 Menu Map with SCPI

Commands

10-1

NOTE

NOTE

Menu Map with SCPI Commands

This chapter shows all softkey menu choices available. Each hardkey on the instrument front panel has a corresponding table in this chapter showing all softkey choices available after pressing the hardkey.

Hardkeys and softkeys are shown as HARDKEY and Soft Key .

Each softkey is shown with an associated SCPI command, if one exists.

SCPI commands are shown as the short form.

The configuration of the currently active measurement channel determines the order of appearance and the content of the softkey menus.

Command Conventions

Commands requiring a choice of measurement channel are shown with both choices: SENS[1|2]: (for example). The command is entered with the appropriate channel given: SENS1: (channel 1 chosen) or SENS2: (channel 2 chosen).

Parameter Types

<num> and <string> refer to parameter types described in the

“Parameter Types” section.

<string> parameters are enclosed in single quotes: ‘the string data’ .

<value> parameters include <num> and an optional <unit> .

Softkey Menus

Most softkey choices and associated SCPI commands are shown in the following Menu Map tables. Because the analyzer provides great flexibility in measurement configuration, and because many softkey menus and user operations are very similar to each other, not every variation of each softkey menu is shown.

SCPI commands that are associated with menu selections can be found by reading the program that is created after keystroke recording has been enabled and the desired keys have been pressed.

Refer to the Hardkey/Softkey Reference in your instrument’s User’s

Guide for a description of each key.



Entering Frequency, Power, and Other Numeric Values

Entry of frequency, power, and other numeric values requires a choice of measurement unit. All entries of this type follow the same sequence:

Enter the number then choose the appropriate unit, or press Enter for default units.

Menu Map Tables and Instrument Types

The instrument displays menu choices based on the instrument type and the active measurement channel configuration. In the tables of softkey menu choices that follow, the instrument type is shown in the table title, and the channel configuration is shown in the table body. See

Figure

10-1

, below.

Figure 10-1

Table 10-8

Example Menu Map Table

CAL Functions, 8712ES/8714ES

CAL (Reflection)

Default 1-Port

KEYSTROKES

Default 2-Port

User 1-Port

Softkey

Channel configuration

Hardkey

SCPI COMMAND

(hardkey entry)

SENS[1|2]:CORR:CSET DEF; *WAI

SENS[1|2]:CORR:CLASS DEF2; *WAI



SCPI command

Applicable models



How to Enter Numbers and Characters


For many tasks in the following menus, you enter numeric values or characters. You might enter 10.0 MHz to set a marker location, or

“state5” for a file name. The following pages show you how to enter values for frequency, time, power and voltage, and how to enter text characters.


Figure 10-2



How to Enter Frequency Values

You enter frequency values the same way each time. First select a numeric value (“100”) and then select a frequency unit (“MHz”).

*RPG knob does not allow unit entry.

Frequency—Enter the Value

Figure 10-3

Enter the frequency using the front panel keypad or knob, or an attached keyboard.

Frequency—Enter the Unit

Enter the unit by pressing the softkey.


Figure 10-4



How to Enter Time Values

You enter time values the same way each time. First select a numeric value (“100”) and then select a time unit (“Sec”).

Time—Enter the Value

Figure 10-5

Enter the time value using the front panel keypad or knob, or an attached keyboard.

Time—Enter the Unit



Figure 10-6



How to Enter Power and Voltage Values

You enter power and voltage values the same way each time. First select a numeric value (“10”) and then select a unit (“W”).

Power and Voltage—Enter the Value

Enter the frequency using the front panel keypad or knob, or an attached keyboard.

Figure 10-7 Power and Voltage—Enter the Unit



Figure 10-8



How to Enter Text

Choose characters with the front panel knob and press Select Char , or use the keyboard. The numeric key pad can be used to select numbers.

Edit the text using the softkeys or keyboard.

Text—Choose the Character

Choose the character with the front panel knob, or enter using keyboard.

Figure 10-9 Text—Select or Edit the Character

Select or edit the text by pressing a softkey.



Menu Map for 8712ET/ES and 8714ET/ES


Table 10-1

AVG

Functions, 8712ES and 8714ES

KEYSTROKES

1

SCPI COMMAND

AVG

Average on OFF

Restart Average

Average Factor

System Bandwidth

Wide (6500 Hz)

Med Wide (4000 Hz)

Medium (3700 Hz)

Med Narrow (1200 Hz)

Narrow (250 Hz)

Fine

Fault Window

2

(15 Hz)

(hardkey entry)

SENS[1|2]:AVER[ON|OFF];*WAI

SENS[1|2]:AVER:CLE;*WAI

SENS[1|2]:AVER:COUN <num>;*WAI

(menu selection only)

SENS[1|2]:BWID 6500 HZ;*WAI







Minimum SENS[1|2]:WIND RECT

SENS[1|2]:WIND HAMM Medium

Maximum

Delay Aperture

3

SENS[1|2]:WIND KBES


Aperture (Hz)

(enter value)

Aperture (%)

(enter value)

CALC[1|2]:GDAP:SPAN 9950000 Hz;*WAI

CALC[1|2]:GDAP:APER <%/100>;*WAI

1. The active measurement channel configuration determines the order of appearance and the content of the softkey menus.

2. Option 100 (SRL and Fault Location) only.

3. Use with Delay format only.




Table 10-2 BEGIN Functions, 8712ET and 8714ET (1 of 3)

KEYSTROKES SCPI COMMAND

BEGIN

1

Amplifier

Filter

Broadband Passive

Mixer

Transmissn

Reflection

Power

Transmissn

Reflection

Transmissn

Reflection

Conversion Loss

(hardkey entry)


CONF 'AMPL:TRAN';*WAI

CONF 'AMPL:REFL';*WAI

CONF 'AMPL:POW';*WAI


CONF ‘FILT:TRAN’;*WAI

CONF ‘FILT:REFL’;*WAI


CONF ‘BBAN:TRAN’;*WAI

CONF ‘BBAN:REFL’;*WAI


CONF ‘MIX:CLOS’;*WAI

Reflection

Cable

2

Transmissn

Reflection

CONF ‘MIX:REFL’;*WAI


CONF[1|2] ‘CABL:TRAN’;*WAI

CONF[1|2] ‘CABL:REFL’;*WAI

Fault Location

Start Distance

CONF[1|2] ‘CABL:FAULT’;*WAI

SENS[1|2]:DIST:STAR <num>[FEET|MET];*WAI

Stop Distance SENS[1|2]:DIST:STOP <num>[FEET|MET];*WAI







KEYSTROKES

BEGIN

1

, Cable

2

, (continued)

Fault Location , (continued)

Feet

SRL

Meters

Low Pass

Band Pass

Center Frequency

Start Freq

(enter value

and units)

Stop Freq

(enter value

and units)

Connector Model

Measure Connector

Connector Length

SCPI COMMAND

SENS:DIST:UNIT FEET

SENS:DIST:UNIT MET

SENS:FREQ:MODE LOWP;*WAI

SENS:FREQ:MODE CENT;*WAI

SENS[1|2]:FREQ:CENT <value>;*WAI

CONF[1|2] ‘CABL:SRL’;*WAI

DISP:ANN:FREQ[1|2]:MODE SSTOP

SENS[1|2]:FREQ:STAR <num>

[MHZ|KHZ|HZ];*WAI

DISP:ANN:FREQ[1|2]:MODE SSTOP

SENS[1|2]:FREQ:STOP <num>

[MHZ|KHZ|HZ];*WAI


SENS[1|2]:CORR:MODEL:CONN

SENS[1|2]:CORR:LENG:CONN <num>

Connector C

Z Cutoff Frequency

SENS[1|2]:CORR:CAP:CONN <num>

SENS:FREQ:ZST <num>

Auto Z ON off SENS1:FUNC:SRL:MODE [MANUAL|AUTO]

Manual Z SENS1:FUNC:SRL:IMP <num>







KEYSTROKES

BEGIN

1

, Cable

2

, (continued)

SRL , (continued)

Connector Fault

SCPI COMMAND

SRL Cable Scan

SENS1:FUNC:FAULT:CONN; *WAI

SENS[1|2]:FUNC:SRL:SCAN; *WAI

Autost

Number of Points SENS[1|2]:SWE:POIN <num>;*WAI


User Begin on OFF (menu selection only)






Table 10-3 BEGIN Functions, 8712ES and 8714ES (1 of 3)


BEGIN

1

Amplifier

Filter

S11 Refl Port1

S21 Fwd Trans

S12 Rev Trans

S22 Refl Port2

Power

S11 Refl Port1

S21 Fwd Trans

Broadband Passive


CONF ‘AMPL:REFL’; *WAI

CONF ‘AMPL:TRAN’; *WAI

CONF ‘AMPL:TRAN:REV’; *WAI

CONF ‘AMPL:REFL:REV’; *WAI

CONF ‘AMPL:POW’; *WAI


CONF ‘FILT:REFL’; *WAI

CONF ‘FILT:TRAN’; *WAI


Mixer

S11 Refl Port1

S21 Fwd Trans

S12 Rev Trans

S22 Refl Port2

Conversion Loss

CONF ‘BBAN:REFL’; *WAI

CONF ‘BBAN:TRAN’; *WAI

CONF ‘BBAN:TRAN:REV’; *WAI

CONF ‘BBAN:REFL:REV’; *WAI


CONF ‘MIX:CLOS’; *WAI

S11 Refl Port1 CONF ‘MIX:REFL’; *WAI







BEGIN ,(continue)

Cable

1

(continue)

Transmissn

Reflection

Fault Location

Start Distance

Stop Distance

Feet

Meters

Low Pass

CONF[1|2] ‘CABL:TRAN’;*WAI

CONF[1|2] ‘CABL:REFL’;*WAI

CONF[1|2] ‘CABL:FAULT’;*WAI

SENS[1|2]:DIST:STAR <num>[FEET|MET];*WAI

SENS[1|2]:DIST:STOP <num>[FEET|MET];*WAI

SENS:DIST:UNIT FEET

SENS:DIST:UNIT MET

SENS:FREQ:MODE LOWP;*WAI

Band Pass

Center Frequency

SENS:FREQ:MODE CENT;*WAI

SENS[1|2]:FREQ:CENT <value>;*WAI

SRL CONF[1|2] ‘CABL:SRL’;*WAI

DISP:ANN:FREQ[1|2]:MODE SSTOP Start Freq

(enter value and units)

SENS[1|2]:FREQ:STAR <num>[MHZ|KHZ|HZ];*WAI

Stop Freq DISP:ANN:FREQ[1|2]:MODE SSTOP

(enter value and units)

SENS[1|2]:FREQ:STOP <num>[MHZ|KHZ|HZ];*WAI







BEGIN, Cable,

1,2

(continued)

SRL , (continued)

Connector Model



Connector C

Z Cutoff Frequency

Auto Z ON off

Manual Z

Connector Fault





SENS:FREQ:ZST <num>

SENS1:FUNC:SRL:MODE [MANUAL|AUTO]

SENS1:FUNC:SRL:IMP <num>

SENS1:FUNC:FAULT:CONN; *WAI

SRL Cable Scan SENS[1|2]:FUNC:SRL:SCAN; *WAI

Autost

Number of Points SENS[1|2]:SWE:POIN <num>;*WAI


User Begin on OFF (menu selection only)






Table 10-4 CAL Functions, 8712ES and 8714ES (1 of 3)


CAL, (Reflection)

Default 1-Port

Default 2-Port

User 1-Port

Default 1-Port

User 1-Port

Measure Standard

1

User 2-Port

(hardkey entry)





SENS[1|2]:CORR:COLL:IST OFF;METH REFL3;

*WAI

SENS[1|2]:CORR:COLL STAN[1|2|3];*WAI


Default 2-Port

User 2-Port


SENS[1|2]:CORR:COLL:IST OFF;METH TWOP;

*WAI


2

Isolation on OFF

SENS[1|2]:CORR:COLL STAN[1|2|...|7];*WAI

SENS:CORR:ISOL ON; *WAI

Normalize on OFF TRAC CH[1|2]SMEM,CH[1|2]SDATA;:CALC[1|2]:

MATH (IMPL/CH[1|2]SMEM);:DISP:WIND[1|2]:

TRAC[1|2] ON;TRAC[1|2] OFF

More Cal (see

Table 10-11

) (menu selection only)

1. Pressing this key begins a guided calibration procedure using three standards.

When the calibration is complete, the command *WAI;:SENS[1|2]:CORR:COLL:

SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2 configurations.

2. Pressing this softkey begins a guided 2-port calibration procedure, using seven standards. When the calibration is complete, the command *WAI;:SENS[1|2]

:CORR:COLL:SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2 configurations.




Table 10-4 CAL , Functions, 8712ES and 8714ES (2 of 3)


CAL , (Transmissn) (continued)

Default Response

Default 2-Port

User Response





SENS1:CORR:CSET DEF; *WAI

Response


1

Response & Isolation


2

SENS[1|2:CORR:COLL:IST OFF;METH TRAN1; *WAI




Enhanced Response


3



1. Pressing this key begins a guided calibration procedure using one standard. When the calibration is complete, the command

*WAI;:SENS[1|2]:CORR:COLL:SAVE;*WAI is executed.

2. Pressing this key begins a guided calibration procedure using two standards. When the calibration is complete, the command


3. Pressing this key begins a guided calibration procedure using four standards.


SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2 configuration.




Table 10-4 CAL , Functions, 8712ES and 8714ES (3 of 3)


CAL, (Transmissn) (continued)

User 2-Port

Default 2-Port

User 2-Port



SENS[1|2]:CORR:COLL:IST OFF;METH TWOP;

*WAI


1


SENS[1|2]:CORR:COLL STAN[1|2|...|7];*WAI

SENS[1|2]:ISOL [ON|OFF];*WAI




(menu selection only) More Cal

(see

Table 10-11 on page 10-26

)

See

Table 10-11 on page 10-30 for Test Set calibration.

See


for Fault Location calibration.

See


for SRL calibration.

See


for Power or Conversion Loss calibration.

1. Pressing this softkey begins a guided 2-port calibration procedure, using seven standards. When the calibration is complete, the command *WAI;:SENS[1|2]

:CORR:COLL:SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2 configurations.




Table 10-5 CAL Functions, 8712ET and 8714ET (1 of 3)


CAL, (Reflection)

Default 1-Port

1-Port


1

Measure Standard — Open

Measure Standard — Short

(hardkey entry)



*WAI


*WAI

SENS[1|2]:CORR:COLL STAN1;*WAI


Measure Standard — Load SENS[1|2]:CORR:COLLSTAN3;*WAI;

:SENS[1|2]:CORR:COLL:SAVE;*WAI




Cal Check

(see

Table 10-10 on page 10-25 )


1. Pressing this softkey begins a guided 1-port calibration procedure, using three standards. When the calibration is complete, the command *WAI;:SENS[1|2]

:CORR:COLL:SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2.





KEYSTROKES

CAL, (Transmissn)


Response


Response & Isolation

Measure Standard -

Load

Measure Standard -

Through

Enhanced Response




-

Open

-

Short

-

Load

SCPI COMMAND

(hardkey entry)


SENS[1|2]:CORR:COLL:IST OFF;METH TRAN1;

*WAI




*WAI




*WAI



SENS[1|2]:CORR:COLLSTAN3;*WAI;


Measure Standard -

Through SENS[1|2]:CORR:COLL STAN4;*WAI







CAL, (continued) (Transmissn)




(menu selection only) Cal Check

(see


More Cal

(see



See


for Test Set calibration.

See

Table 10-7 on page 10-22 for Fault Location calibration.

See

Table 10-8 on page 10-23 for SRL calibration.

See

Table 10-9 on page 10-24 for Power or Conversion Loss calibration.




Table 10-7 CAL , Functions, 8712ET/ES and 8714ET/ES


CAL, (Fault Location)

Default Cal

Full Band Cal


1

Velocity Factor

Cable Loss

Calibrate Cable

Specify Length

Measure Cable

Multi Peak

Multi Peak Corr on OFF


SENS[1|2]:CORR:EXT [ON|OFF]


SENS[1|2]:CORR:RVEL:COAX <value>

SENS[1|2]:CORR:LOSS:COAX <value>


SENS[1|2]:CORR:LENG:COAX <value>; *WAI

SENS[1|2]:CORR:RVEL; *WAI


SENS[1|2]:CORR:PEAK:COAX ON

Multi Peak Threshold

Connector Values


SENS[1|2]:CORR:THRESHOLD:COAX -10.00


SENS[1|2]:CORR:LENG:CONN <value>

Connector C SENS1:CORR:CAP:CONN <value>

(menu selection only) More Cal

(see


)



SAVE;*WAI is executed. The order of appearance and the content of the softkey menus depend on the measurement channel 1 and measurement channel 2 configuration.




Table 10-8 Functions, 8712ET/ES and 8714ET/ES


CAL, (SRL)

Default Cal

Full Band Cal


1

Connector Model


Measure


Connector C

Z cutoff Frequency









SENS:FREQ:ZST <num>

Auto Z ON off SENS[1|2]:FUNC:SRL:MODE [MANUAL|AUTO]

Manual Z

Connector Fault

SENS[1|2]:FUNC:SRL:IMP <num>

(sets instrument to connector fault display)

(menu selection only) Cal Check

(see


More Cal

(see




When the calibration is complete, the command





Table 10-9

KEYSTROKES

CAL, (Power or Conversion Loss)

Auto Zero

Manual Zero

Normalize on OFF

More Cal

CAL , Functions, 8712ET/ES and 8714ET/ES

SCPI COMMAND

(see


CAL:ZERO:AUTO ON

CAL:ZERO:AUTO ONCE

TRAC CH[1|2]SMEM,CH[1|2]SDATA;:CALC[1|2]:







Table 10-10 CAL , Cal Check Functions, 8712ET/ES and 8714ET/ES

KEYSTROKES

CAL , Cal Check

Do Cal Check


1

View Cal Check

1

Directivity

Source Match

Reflection Tracking

Load Match

Transmissn

Tracking

SCPI COMMAND


SENS1:CORR:COLL:IST OFF;METH VERIFY;*WA I

SENS[1|2]:CORR:COLL:VER:REFL

STAN[1|2|3];*WAI;


DIAG:MDIS[1|2]:CORR C_DIRECT; *WAI

DIAG:MDIS[1|2]:CORR C_SRCMATCH; *WAI

DIAG:MDIS[1|2]:CORR C_RTRACKING; *WAI

DIAG:MDIS[1|2]:CORR C_LDMATCH; *WAI

DIAG:MDIS[1|2]:CORR C_TTRACKING; *WAI

Isolation DIAG:MDIS[1|2]:CORR C_ISOLATION; *WAI

Restore Meas DIAG:MDIS[1|2]:REST; *WAI

1. Only those calibration checks valid for the current measurement type are active, other choices are dimmed. For example, Transmission Tracking is not valid for reflection measurements.




Table 10-11 CAL, More CAL Functions, 8712ET/ES and 8714ET/ES (1 of 4)

KEYSTROKES

CAL, More Cal

1, 2

Port Extensions

Port Ext’s ON off

Port 1 Extension

3, 4

(Refl Port Extensions)

3, 5

Port 2 Extension

3, 4

(Trans Port Extensions)

3, 5

SCPI COMMAND




SENS[1|2]:CORR:EXT:REFL:TIME <num> s

SENS[1|2]:CORR:EXT:TRAN:TIME <num> s

Velocity Factor

Smith Chart Z0

System Z0

SENS[1|2]:CORR:RVEL:COAX <num>

SENS[1|2]:CORR:IMP:INP:MAGN <num> OHM

SENS[1|2]:CORR:IMP:INP:MAGN:SEL

Z0_[50|75]

SENS[1|2]:CORR:EXT:REFL:TIME <num> s 50

Ω

75

Ω

Cal Kit

Type-N(f) (Default)

SENS[1|2]:CORR:EXT:REFL:TIME <num> s


SENS:CORR:COLL:CKIT:PORT[1|2]

‘COAX,7MM,TYPE-N,75,FEMALE’

Type-N(m) SENS:CORR:COLL:CKIT:PORT[1|2]

‘COAX,7MM,TYPE-N,75,MALE’

1. The port number in each command is the port selected from the screen using the up and down keys.

2. The instrument system impedance determines the set of valid connector choices in this menu. Connectors with a characteristic impedance other than the instrument system impedance are dimmed on the screen.

3. This Key is active if port extensions are on.

4. For 8712ES and 8714ES analyzers.

5. For 8712ET and 8714ET analyzers.




Table 10-10

Type-F

APC-7

7-16

CAL, More CAL Functions, 8712ET/ES and 8714ET/ES (2 of 4)

KEYSTROKES

CAL, More Cal (continued)

Cal Kit (continued)

3.5 mm

SCPI COMMAND



SENS:CORR:COLL:CKIT:PORT1

‘COAX,3.5MM,APC-3.5,50,IMPLIED’


‘COAX,7MM,TYPE-F,75,IMPLIED’


‘COAX,7MM,APC-7,50,IMPLIED’


‘COAX,7MM,TYPE-7-16,50,IMPLIED’


‘USER,IMPLIED,IMPLIED,IMPLIED,IMPLIED’


‘USER2,IMPLIED,IMPLIED,IMPLIED,IMPLIED’

User Cal

Kit A

1

User Cal

Kit B

1

User Cal

Kit C

1

User Cal

Kit D

1

User Cal

Kit E

1

User Cal

Kit F

1

User Cal

Kit G

1











1. The port number in each command is the port selected from the screen using the up and down keys.





SCPI COMMAND KEYSTROKES

CAL, More Cal (continued)

Cal Kit (continued)

User Cal

Kit H

1

User Cal

Kit I

1

User Cal

Kit J

1

Modify ( Cal Kit Type)







Open:

C0

C1

C2

C3

Delay

Loss

Z0

SENS[1|2]:CORR:CKIT:MOD[:SEL][TYPenf|

TYPenm|UD1|TYPe35mm|TYPeff|TYPe716f|

TYPe716m|UD2|TYPeapc7|UD3|4|...10]


SENS[1|2]:CORR:CKIT:OPEN:MOD:CZER <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:CONE <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:CTWO <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:CTHR <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:DEL <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:LOSS <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:ZOFF <num>






CAL, More Cal, (continued)

Cal kit, (continued)

Modify ( Cal Kit Type)

(continued)

Short:

Delay

Loss

Load:

Z0

Delay

Loss

Z0

Thru

Delay

Loss

Z0

Mod Kit Save Recall

Save

Recall

Add Kit Description

Preset User Kit

Preset All User Kits


SENS[1|2]:CORR:CKIT:SHOR:MOD:DEL <num>

SENS[1|2]:CORR:CKIT:SHOR:MOD:LOSS <num>

SENS[1|2]:CORR:CKIT:OPEN:MOD:ZOFF <num>


SENS[1|2]:CORR:CKIT:LOAD:MOD:DEL <num>

SENS[1|2]:CORR:CKIT:LOAD:MOD:LOSS <num>

SENS[1|2]:CORR:CKIT:LOAD:MOD:ZOFF <num>


SENS[1|2]:CORR:CKIT:THRU:MOD:DEL <num>

SENS[1|2]:CORR:CKIT:THRU:MOD:LOSS <num>

SENS[1|2]:CORR:CKIT:THRU:MOD:ZOFF <num>


SENS:CORR:CKIT:SAVE-? <KIT1|2...|10>

SENS:CORR:CKIT:MOD <UD1|2|...10>

SENS:CORR:CKIT:NAME <KIT1|2...|10> ,

<STRING>


SENS:CORR:CKIT:PRES[:IMM]-?

[{KIT1|2|...|10}]




Table 10-11 CAL , Test Set Cal Functions, 8712ET/ES and 8714ET/ES

KEYSTROKES

CAL , Test Set Cal

1

Create “TSET_CAL”

2

XX Ports

Enh Resp 1 - Port

3

2 - Port

3

SCPI COMMAND

SENS[1|2]:CORR:TESTSET;*WAI

SENS[1|2]:CORR:COLL:METHOD TEST;

SENS[1|2]:CORR:COLL:PORTS

<2|4|6|8|10|12>

SENS[1|2]:CORR:COLL:METHOD TEST 1

SENS[1|2]:CORR:COLL:METHOD TEST 2

Measure Opens

Measure Shorts

Measure Loads

Measure Thrus

SENS[1|2]:CORR:COLL:MP:OPEN

<STAN1|STAN2|…|STAN12>;*WAI;

SENS[1|2]:CORR:COLL:MP:SHORT


SENS[1|2]:CORR:COLL:MP:LOAD


SENS[1|2]:CORR:COLL:MP:THRU


All Stds Done

Periodic SelfCal

SelfCal Once

SelfCal Timer

SENS[1|2]:CORR:COLL:SAVE;*WAI;

CAL:SELF ON

CAL:SELF ONCE

CAL:SELF:TIMER <num>

SelfCal All Ports

2-Port Cal on OFF

3


3

CAL:SEL0F:ALL

CAL:SELF:METHOD [ONEP|TWOP]*WAI

SENS[1|2]:CORR:ISOL [ON|OFF]*WAI

1. For use with multiport test sets only.

2. You select the number of test set ports, and a guided calibration procedure begins.

3. For 8712ES and 8714ES analyzers only.




Table 10-12 DISPLAY Functions, 8712ET/ES and 8714ET/ES (1 of 5)


DISPLAY

1

Normalize

(hardkey entry)

TRAC CH[1|2]SMEM,CH[1|2]SDATA;:

CALC[1|2]:MATH (IMPL/CH[1|2]SMEM);:

DISP: WIND[1|2]:TRAC1 ON;TRAC2 OFF

Data ->Mem

Data

Memory

Data/Mem

Data and Memory

TRAC CH[1|2]SMEM,CH[1|2]SDATA

CALC[1|2]:MATH (IMPL);:DISP:

WIND[1|2]:TRAC1 ON;TRAC2 OFF

DISP:WIND[1|2]:TRAC1 OFF;TRAC2 ON

CALC[1|2]:MATH (IMPL/CH[1|2]SMEM);:

DISP:WIND[1|2]:TRAC1 ON;TRAC2 OFF

CALC[1|2]:MATH

(IMPL);:DISP:WIND[1|2]:TRAC1 ON;TRAC2 ON

Limit Menu

2

Add Limit

Add Max Line

Begin Frequency

End Frequency

CALC[1|2]:LIM:DISP ON


CALC[1|2]:LIM:SEGM[n]:TYPE LMAX;STAT ON

3

CALC[1|2]:LIM:SEGM[n]:FREQ:STAR <num> HZ

CALC[1|2]:LIM:SEGM[n]:FREQ:STOP <num> HZ

Begin Limit

End Limit

CALC[1|2]:LIM:SEGM[n]:AMPL:STAR <num>

CALC[1|2]:LIM:SEGM[n]:AMPL:STOP <num>

Marker CALC[1|2]:MARK1:X <num>


2. Limit Menu choices are provided based on the current measurement channel configuration. If the instrument is configured for fault location measurements, the limit values are distances, for example.

3. Limit segments are numbered by the instrument as they are entered. At the same time the Limit menu is displayed, the currently defined limits are displayed.





KEYSTROKES

DISPLAY

1

, Limit Menu , (continued)

Add Limit (continued)

Add Min Line

SCPI COMMAND

Begin Frequency

End Frequency

Begin Limit

End Limit

Marker

Add Max Point

CALC[1|2]:LIM:SEGM[n]:TYPE LMIN;STAT ON

2





CALC[1|2]:MARK1:X <num>

CALC[1|2]:LIM:SEGM[n]:TYPE PMAX;STAT ON

2

Frequency

Limit

Marker

Add Min Point




CALC[1|2]:LIM:SEGM[n]:TYPE PMIN;STAT ON

2

Frequency

Limit



Marker

Delete Limit

3



Delete all Limits CALC1:LIM:DISP [ON|OFF]


2. Limit segments are numbered by the instrument as they are entered. At the same time the Limit menu is displayed, the currently defined limits are displayed.

3. Select the limit with the up and down keys or the RPG knob on the Limit Menu display, and select Delete Limit .





KEYSTROKES

DISPLAY

1

, Limit Menu , (continued)

Delete Limit

(continued)

Edit Limit

2

SCPI COMMAND


Begin Frequency

(Begin Distance)

2

End Frequency

(End Distance)

2



Begin Limit

End Limit

Limit Options



CALC[1|2]:LIM:SEGM[n]:TYPE PMAX;STAT ON

2

Limit Line ON off

Limit Text ON off

Limit Icon ON off

CALC[1|2]:LIM:DISP [ON|OFF]

DISP:ANN:LIM:ICON2:TEXT [ON|OFF]

DISP:ANN:LIM:ICON2:FLAG [ON|OFF]

DISP:ANN:LIM:ICON1:POS:X <value> Limit Icon X Position

Limit Icon Y Position

Mkr Limits

Edit Limit (Min/Max)

3

DISP:ANN:LIM:ICON1:POS:Y <value>



CALC[1|2]:LIM:MARK:STAT:MEAN:MAX <value> Max Limit

Min Limit

Mkr Limit on OFF

CALC[1|2]:LIM:MARK:STAT:MEAN:MIN <value>

CALC[1|2]:LIM:MARK:STAT:MEAN [ON|OFF]

Limit Test ON off CALC[1|2]:LIM:STAT [ON|OFF]


2. For fault location measurements.

3. After Edit Limit (Min/Max) is pressed, the up key can be used to increase the limit

( CALC[1|2]:LIM:MARK:STAT:MEAN:MAX UP ) and the down key can be used to decrease the limit ( CALC[1|2]:LIM:MARK:STAT:MEAN:MAX DOWN ).





KEYSTROKES

DISPLAY

1

, (continued)

Split Disp FULL split

SCPI COMMAND

Expand ON off

Title and Clock

Enter Line 1 (enter text,

press Enter )

Enter Line 2 (enter text,

press Enter )

Show Clock on Line 1

DISP:FORM [ULOW|SING]

DISP:FORM:EXPAND [ON|OFF]

DISP:ANN:TITL ON

DISP:ANN:TITL[1|2]:DATA, ‘text’

DISP:ANN:TITL[1|2]:DATA, ‘text’

Show Clock on Line 2

Clock Off

Title+Clk ON off

Color Options

Factory default

Default 2

DISP:ANN:CLOC:MODE LINE1

DISP:ANN:CLOC:MODE LINE2

DISP:ANN:CLOC:MODE OFF

DISP:ANN:TITL [ON|OFF]


DISP:CMAP:SCHEME DEFAULT

DISP:CMAP:SCHEME DEFAULT2

Grey Scale DISP:CMAP:SCHEME GREY

Inverse Video DISP:CMAP:SCHEME INV






KEYSTROKES

DISPLAY

1

, Color Options , (continued)

Custom Colors

2

SCPI COMMAND

Select Item

Hue

Saturation

Luminance

Int Disp Intensity

Annotation Options

Meas Annot ON off

Freq Annot ON off

Mkr Annot ON off

Mkr Number ON off


(select item, 1-16)

DISP:CMAP:COL[1|2|...|16]:HSL h,s,l

3


3


3

DISP:CMAP:COL16:GREY [0-1.00]


DISP:ANN:CHAN[1|2] [ON|OFF]

DISP:ANN:FREQ[1|2] [ON|OFF]

DISP:ANN:MARK[1|2] [ON|OFF]

DISP:ANN:MARK[1|2]:NUMB [ON|OFF]

Y-Axis Lbl ON off

Y-Axis Lbl rel ABS

DISP:ANN:YAX [ON|OFF]

DISP:ANN:YAX:MODE [REL|ABS]

Graticule ON off DISP:WIND1:TRAC:GRAT:GRID [ON|OFF]


2. First choose an item (Background=1, User Graphics Pen 1=2 through User Graphics Pen 7=8, Inactive Text=9, Warning Text=10, Graticule=11, Trace 1=12, Mem

1=13, Trace 2=14, Mem 2=15, Text=16) with Select Item , then choose a color item to change, and enter a new value. The softkey menu displays Enter and Cancel . Press

Enter to save your changes.

3.

COL[1|2|...|16] selects one of the 16 items listed in

Footnote 2 , above.

HSL h,s,l sets the hue, saturation and luminance values, respectively.




Table 10-13 FORMAT Functions, 8712ET/ES and 8714ET/ES


FORMAT

1

Log Mag

Lin Mag

SWR

Delay

Phase

Smith Chart

Polar

More Format

(hardkey entry)

CALC[1|2]:FORM MLOG

CALC[1|2]:FORM MLIN

CALC[1|2]:FORM SWR

CALC[1|2]:FORM GDEL

CALC[1|2]:FORM PHAS

CALC[1|2]:FORM SMIT

CALC[1|2]:FORM POL


Real

Imaginary

Impedance Magnitude

Mag Units

2 dBW dBm dBuW dBV

CALC[1|2]:FORM REAL

CALC[1|2]:FORM IMAG

CALC[1|2]:FORM MIMP


CALC[1|2]:FORM:UNIT:MLOG DBW

CALC[1|2]:FORM:UNIT:MLOG DBMW

CALC[1|2]:FORM:UNIT:MLOG DBUW

CALC[1|2]:FORM:UNIT:MLOG DBV dBmV CALC[1|2]:FORM:UNIT:MLOG DBMV dBuV CALC[1|2]:FORM:UNIT:MLOG DBUV


2. This menu lists the units available for selection using Log Mag or Lin Mag format only.




Table 10-14 FREQ Functions, 8712ET/ES and 8714ET/ES


FREQ

1

Start

Stop

Center

Span

CW

Fault Loc Frequency

2

Low Pass

Band Pass

Band Pass Max Span

Displ Freq Resolution

(hardkey entry)

DISP:ANN:FREQ1:MODE SSTOP

SENS[1|2]:FREQ:STAR <value> HZ;*WAI

DISP:ANN:FREQ1:MODE SSTOP

SENS[1|2]:FREQ:STOP <value> HZ;*WAI

DISP:ANN:FREQ1:MODE CSPAN

SENS[1|2]:FREQ:CENT <value> HZ;*WAI

DISP:ANN:FREQ1:MODE CSPAN

SENS[1|2]:FREQ:SPAN <value> HZ;*WAI

DISP:ANN:FREQ1:MODE CW;:

SENS[1|2]:FREQ:SPAN 0 HZ;;*WAI

SENS[1|2]:FREQ:CENT 300000 HZ;*WAI


SENS:FREQ:MODE LOWP; *WAI

SENS:FREQ:MODE CENT

SENS[1|2]:FREQ:SPAN:MAX <value>

CALC[1|2]:FORM IMAG

MHz kHz

DISP:ANN:FREQ:RES MHZ

DISP:ANN:FREQ:RES KHZ

Hz DISP:ANN:FREQ:RES HZ


2. Available for fault location measurements only.




Table 10-15 HARD COPY Functions, 8712ET/ES and 8714ET/ES (1 of 4)


HARD COPY

Start

Abort

Select Copy Port

Restore Defaults

Select

LAN Printr IP Addr

Print/Plot GPIB Addr

Baud Rate

Xon/Xoff

DTR/DSR

Define PCL5


Monochrome

Color

Auto Feed ON off

Portrait

Landscape

HCOP;*WAI

HCOP:ABOR


(no SCPI command)

HCOP:DEV:LANG<PCL|HPGL|IBM|EPSON|PCX>;

PORT <CENT|SER|GPIB|MMEM|LAN>

SYST:COMM:LAN:PRIN:HOST <addr>

SYST:COMM:GPIB:HCOP:ADDR <addr>

(no SCPI command)

SYST:COMM:SER:TRAN:HAND XON

SYST:COMM:SER:TRAN:HAND DTR


(no SCPI command)

HCOP:DEV3:COL [ON|OFF]

HCOP:DEV3:COL [ON|OFF]

HCOP:ITEM3:FFE:STAT [ON|OFF]

HCOP:DEV3:PAGE:ORI PORT

HCOP:DEV3:PAGE:ORI LAND






HARD COPY , (continued)

Define PCL5 , (continued)

More PCL5


Top Margin

Left Margin

Print Width

Define Printer


Monochrome

Color

Portrait

Landscape

Auto Feed ON off

More Printer


Printer Resolution

Top Margin

Left Margin

Print Width


(no SCPI command)

HCOP:DEV3:PAGE:MARG:TOP <num>

HCOP:DEV3:PAGE:MARG:LEFT <num>

HCOP:DEV3:PAGE:WIDT <num>


(no SCPI command)

HCOP:DEV1:COL OFF

HCOP:DEV1:COL ON

HCOP:DEV3:PAGE:ORI PORT

HCOP:DEV3:PAGE:ORI LAND

HCOP:ITEM3:FFE:STAT [ON|OFF]


(no SCPI command)

HCOP:DEV:RES <num>

HCOP:PAGE:MARG:TOP <num>

HCOP:PAGE:MARG:LEFT <num>

HCOP:PAGE:WIDT <num>






HARD COPY, (continued)

Define Plotter


Monochrome


(no SCPI command)

HCOP:DEV2:COL OFF

Color

Set Pen Numbers

Monochrome Pen

1

Default Pen Colors

Trace 1 Pen

Trace 2 Pen

Memory 1 Pen

Memory 2 Pent

Graticule Pen

Graphics Pen

HCOP:DEV2:COL ON


(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

Auto Feed ON off HCOP:ITEM2:FFE:STAT ON

1. This selection available when monochrome is selected.






HARD COPY , (continued)

Define Hardcopy


Graph and Mkr Table

Graph Only

Mkr Table Only

List Trace Values

Define Graph


Trace Data ON off

Graticule ON off

Annotation ON off

Mkr Symbol ON off

Title + Clk ON off


(no SCPI command)

HCOP:DEV:MODE GMAR

HCOP:DEV:MODE GRAP

HCOP:DEV:MODE MARK

HCOP:DEV:MODE TABL


(no SCPI command)

HCOP:ITEM:TRAC:STAT [ON|OFF]

HCOP:ITEM:GRAT:STAT [ON|OFF]

HCOP:ITEM:ANN:STAT [ON|OFF]

HCOP:ITEM:MARK:STAT [ON|OFF]

HCOP:ITEM:TITL:STAT [ON|OFF]




Table 10-16

MARKER

KEYSTROKES

1 : (enter value and units)

Active Marker Off

All Off

MARKER Functions, 8712ET/ES and 8714ET/ES (1 of 3)

2: (enter value and units)







SCPI COMMAND

(hardkey entry)

CALC[1|2]:MARK1 ON

CALC[1|2]:MARK1:X <num> [MHZ|KHZ|HZ]

CALC[1|2]:MARK2 ON


CALC[1|2]:MARK3 ON


CALC[1|2]:MARK4 ON


CALC[1|2]:MARK5 ON


CALC[1|2]:MARK6 ON


CALC[1|2]:MARK7 ON


CALC[1|2]:MARK8 ON

CALC[1|2]:MARK8:X <num> MHZ|KHZ|HZ]

CALC[1|2]:MARK[1|2| 8] OFF

CALC[1|2]:MARK:AOFF




Table 10-16 MARKER Functions, 8712ET/ES and 8714ET/ES (2 of 3)


MARKER, (continued)

Marker Functions

Delta Mkr on OFF

Marker -> Center

Marker -> Reference

Marker -> Elec Delay

Marker Math

Statistics

Flatness

RF Filter Stats

Math Off

Marker Search

Max Search

Mkr -> Max

Next Peak Left

Next Peak Right

Min Search

Marker -> Min


CALC[1|2]:MARK:MODE <REL|ABS>

SENS[1|2]:FREQ:CENT

(CALC[1|2]:MARK[1|2|…8]:X:ABS?);*WAI

DISP:WIND[1|2]:TRAC:Y:RLEV

(CALC[1|2]:MARK[1|2|…8]:Y?);*WAI

SENS[1|2]:CORR:EDEL:TIME

(CALC[1|2]:MARK[1|2|…8]:GDEL?);*WAI


CALC[1|2]:MARK:FUNC STAT

CALC[1|2]:MARK:FUNC FLAT

CALC[1|2]:MARK:FUNC FST

CALC[1|2]:MARK:FUNC OFF


CALC[1|2]:MARK:FUNC MAX

CALC[1|2]:MARK:FUNC MAX

CALC[1|2]:MARK:MAX:LEFT

CALC[1|2]:MARK:MAX:RIGH

CALC[1|2]:MARK:FUNC MIN

CALC[1|2]:MARK:FUNC MIN




Table 10-16 MARKER Functions, 8712ES and 8714ES (3 of 3)


MARKER, Marker Search , (continued)

Min Search, (continued)

Next Min Left

Next Min Right

Target Search

Target Value (enter value, and units)

Search Left (enter value, and units)

Search Right (enter value, and units)

Bandwidth (enter value, and units)

Notch (enter value, and units)

More

Multi Peak

MultiNotch

Search Off

Tracking ON off

CALC[1|2]:MARK:MIN:LEFT

CALC[1|2]:MARK:MIN:RIGH

CALC[1|2]:MARK:FUNC TARG

CALC[1|2]:MARK:TARG <LEFT|RIGH>,<num>

[DB]

CALC[1|2]:MARK:TARG LEFT,<num> [DB]

CALC[1|2]:MARK:TARG RIGH,<num> [DB]

CALC[1|2]:MARK:FUNC BWID

CALC[1|2]:MARK:BWID <num> [DB]

CALC[1|2]:MARK:FUNC NOTC

CALC[1|2]:MARK:NOTC <num> [DB]


CALC[1|2]:MARK:FUNC MPE

CALC[1|2]:MARK:FUNC MNOT

CALC[1|2]:MARK:FUNC OFF

CALC[1|2]:MARK:FUNC:TRAC [ON|OFF]




Table 10-17 MEAS1 | MEAS2 Functions, 8712ES and 8714ES (1 of 2)


MEAS1 | MEAS2

S11 Refl Port1

S21 Fwd Trans

S12 Rev Trans

S22 Refl Port2

Fault Location

SRL

Power

SENS[1|2]:STAT ON; *WAI

SENS[1|2]:FUNC ‘XFR:S 1,1’;DET NBAN; *WAI




SENS[1|2]:FUNC ‘FLOC 1,0’;DET NBAN; *WAI

SENS[1|2]:FUNC ‘SRL 1,0’;DET NBAN; *WAI

SENS[1|2]:FUNC ‘XFR:POW 2’;DET BBAN; *WAI

-

Conversion Loss

Detection Options

Narrowband Internal

SENS[1|2]:FUNC ‘XFR:POW:RAT 2,0’;DET BBAN; *WAI



A

B

SENS[1|2]:FUNC ‘XFR:POW 1’;DET NBAN; *WAI


R

-> Path

FWD rev

A/R

B/R




ROUT[1|2]:PATH:DEF:PORT [(2,1)|(1,2)]; *WAI




Table 10-17 MEAS1 | MEAS2 Functions, 8712ES and 8714ES (2 of 2)

KEYSTROKES

MEAS1 | MEAS2 , (continued)

Broadband Internal

SCPI COMMAND

B*

R*

B*/R*

Broadband External

X

Y

X/Y

Y/X

Y/R*

Aux Input

--> Path

FWD rev

(menu selection only



SENS[1|2]:FUNC ‘XFR:POW:RAT 2,0’;DET BBAN;

*WAI




SENS[1|2]:FUNC ‘XFR:POW:RAT 11,12’;DET

BBAN; *WAI


BBAN; *WAI


*WAI

SENS[1|2]:FUNC ‘XFR:VOLT’; *WAI

ROUT[1|2]:PATH:DEF:PORT [(2,1)|(1,2)]; *WAI

Meas OFF SENS[1|2]:STAT OFF; *WAI

See

Table 10-19 on page 10-49 for Multiport Test Set.




Table 10-18 MEAS1 | MEAS2 Functions, 8712ET and 8714ET (1 of 2)


MEAS1 | MEAS2 , (continued)

Transmissn

Reflection

Fault Location

SRL

Power

Conversion Loss

Detection Options

Narrowband Internal

A

B

R

A/R

B/R

SENS1:FUNC ‘XFR:S 2,1’;DET NBAN; *WAI


SENS1:FUNC ‘FLOC 1,0’;DET NBAN; *WAI

SENS1:FUNC ‘SRL 1,0’;DET NBAN; *WAI

SENS1:FUNC ‘XFR:POW 2’;DET BBAN; *WAI

SENS1:FUNC ‘XFR:POW:RAT 2,0’;DET BBAN;

*WAI











Table 10-18 MEAS1 | MEAS2 Functions, 8712ET and 8714ET (2 of 2)


MEAS1 | MEAS2 ,(continued)

Broadband Internal

B*

R*

B*/R*

Broadband External





*WAI


X

Y

X/Y

Y/X




BBAN; *WAI


BBAN; *WAI

Aux Input

Y/R* SENS[1|2]:FUNC ‘XFR:POW:RAT 12,0’;DET

BBAN; *WAI

SENS[1|2]:FUNC ‘XFR:VOLT’; *WAI

Meas OFF SENS[1|2]:STAT OFF; *WAI

See

Table 10-20 on page 10-49 for Multiport Test Set.




Table 10-19 MEAS Multiport Test Set Functions, 8712ES and 8714ES


MEAS1 | MEAS2 , (Multiport)

S11 ReflPort

S21 Tran

S12 Tran

S22 ReflPort

Multiport Selection

( S11) Port

( S22) Port








Table 10-20 MEAS Multiport Test Set Functions, 8712ET and 8714ET


MEAS1 | MEAS2 , (Multiport)

Reflection

Transmissn

Multiport Selection

Reflection Port Num

Transmissn Port Num




ROUT[1|2]REFL:PATH:DEF:PORT[1|2|...|10]

ROUT[1|2]TRAN:PATH:DEF:PORT[1|2|...|10]




Table 10-21 MENU Functions, 8712ET/ES and 8714ET/ES (1 of 2)


MENU

Trigger

Continuous

Hold

Single

Trigger Source

(hardkey entry)


ABOR;:INIT1:CONT ON;*WAI

ABOR;:INIT1:CONT OFF;*WAI

ABOR;:INIT1:CONT OFF;:INIT1;*WAI


Internal

External Sweep

TRIG:SOUR IMM;:SENS:SWE:TRIG:SOUR

IMM;*WAI

TRIG:SOUR EXT;:SENS:SWE:TRIG:SOUR

IMM;*WAI

External Point TRIG:SOUR EXT;:SENS:SWE:TRIG:SOUR

EXT;*WAI

SENS[1|2]:SWE:POIN <num>; *WAI Number of Points (enter value, press Enter )

Distance

1

Start Distance (enter value,

press Enter )

Stop Distance (enter value, press Enter )

Feet


SENS[1|2]:DIST:STAR <num>; *WAI

SENS[1|2]:DIST:STOP <num>; *WAI

SENS:DIST:UNIT FEET

Meters SENS:DIST:UNIT MET

1. Used with fault location measurements only.




Table 10-21 MENU Functions, 8712ET/ES and 8714ET/ES (2 of 2)


MENU , (continued)

SRL Cable Scan

1

Ext Ref on OFF

Spur Avoid Options

SENS[1|2]:FUNC:SRL:SCAN; *WAI

SENS:ROSC:SOUR [EXT|INT]; *WAI


None

Dither

DIAG:SPUR:METH NONE;*WAI

DIAG:SPUR:METH DITH;*WAI

Spur Avoid DIAG:SPUR:METH AVO;*WAI

1. Used with SRL measurements only. This softkey starts an automated SRL cable scan.




Table 10-22 POWER Functions, 8712ET/ES and 8714ET/ES (1 of 2)


POWER

Level

1

(enter value, and unit) dBm

(hardkey entry)

SOUR[1|2]:POW <value>; *WAI dBW dBuW dBV dBmV dBuV

Cancel

(units choice)

(units choice)

(units choice)

(units choice)

(units choice)

(units choice)

(cancels entry)

RF ON off

Start Power

2

(enter value,

and unit)

OUTP[ON|OFF]; *WAI

SOUR:POW:STAR <value>; *WAI dBm dBW dBuW dBV

(units choice)

(units choice)

(units choice)

(units choice) dBmV dBuV

(units choice)

(units choice)

Cancel

(cancels entry)

1. This softkey is valid for frequency sweeps only.

2. This softkey is valid for power sweeps only.




Table 10-22 POWER Functions, 8712ET/ES and 8714ET/ES (2 of 2)


POWER, (continued)

Stop Power

1

(enter value,

and unit) dBm

SOUR:POW:STOP <value>; *WAI dBW dBuW dBV dBmV dBuV

Cancel

(units choice)

(units choice)

(units choice)

(units choice)

(units choice)

(units choice)

(cancels entry)

Pwr Level at Preset (enter value, and unit)

SOUR:POW:PRESET<value> dBm dBW dBuW dBV

(units choice)

(units choice)

(units choice)

(units choice) dBmV dBuV

(units choice)

(units choice)

Cancel (cancels entry)

1. This softkey is valid for power sweeps only.




Table 10-23

KEYSTROKES

PRESET

Factory Preset

User Preset

MENU Functions, 8712ET/ES and 8714ET/ES

SCPI COMMAND

SYST: Preset (hardkey entry)






Table 10-24 SAVE RECALL

KEYSTROKES

Functions, 8712ET/ES and 8714ET/ES (1 of 5)

SCPI COMMAND

SAVE RECALL

Save State

Re-Save State (enter file name, press Enter )

Define Save

(hardkey entry)

MMEM:STOR:STAT 1,’MEM:STATE1.STA’

MMEM:STOR:STAT 1,’MEM:STATE1.STA

’

Inst State ON off

Cal on OFF

Data on OFF

TSet Cal on OFF

1

File Format

8711A/B Compatible

8711C Compatible

8712/14E Compatible


MMEM:STOR:STAT:IST [ON|OFF]

MMEM:STOR:STAT:CORR[ON|OFF] .

MMEM:STOR:STAT:TRAC [ON|OFF]

MMEM:STOR:STAT:TSCAL [ON|OFF]


MMEM:STOR:STAT:FORM B8711

MMEM:STOR:STAT:FORM C8711

MMEM:STOR:STAT:FORM E8711


Save ASCII

Lotus 123 Format

Touchstone Format

MMEM:STOR:TRAC:FORM LOT

MMEM:STOR:TRAC:FORM TOUC

Save Meas 1 MMEM:STOR:TRAC CH1FDATA, ‘MEM:TRACE0.S1P’

MMEM:STOR:TRAC CH2FDATA, ‘MEM:TRACE1.S1P’ Save Meas 2

Recall State

Programs

Save Program

Re-Save Program

MMEM:LOAD:STAT 1,’MEM:STATE2.STA’


(no SCPI command)

(no SCPI command)

(no SCPI command)

File Type bin ASCII

1. A multi-port test set is required for this softkey choice.




Table 10-24 SAVE RECALL Functions, 8712ET/ES and 8714ET/ES (2 of 5)


SAVE RECALL, Programs, (continued)

Recall Program

Run

Continue

Step

Edit

Key record on OFF

Utilities

Clear Program

Stack Size

Secure

IBASIC DISPLAY

(no SCPI command)

PROG:STAT:RUN

PROG:STAT:CONT

(no SCPI command)

(no SCPI command)

(no SCPI command)


(no SCPI command)

(no SCPI command)

(no SCPI command)


None

Full

DISP:PROG OFF

DISP:PROG FULL

Upper DISP:PROG UPP

Lower

Save AUTOST

IBASIC

Run

1

Continue

1

Step

1

Edit

1

DISP:PROG LOW

(no SCPI command)


(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

1. This action valid with key record off.






SAVE RECALL, programs, (continued)

Key Record on OFF

Utilities

1

Clear Program

Stack Size

Secure

IBASIC Display

None

Full

Upper

Lower

Select Disk

Non-Vol RAM Disk

Volatile RAM Disk

Internal 3.5” Disk

NFS Device

Configure VOL_RAM


Modify Size

Current Size

File Utilities

Rename File (edit name,

press Enter )

(no SCPI command)


(no SCPI command)

(no SCPI command)

(no SCPI command)


DISP:PROG OFF

DISP:PROG FULL

DISP:PROG UPP

DISP:PROG LOW


MMEM:MSIS ‘MEM:’

MMEM:MSIS ‘RAM:’

MMEM:MSIS ‘INT:’



(no SCPI command)

(no SCPI command)

(no SCPI command)


MMEM:MOVE ‘<loc>:<name>’, ‘<loc>:<name>’






SAVE RECALL, File Utilities, (continued)

Delete File

Delete All Files

Copy File

Copy to NonVol RAM

Copy to Vol RAM

Copy to 3.5” Disk

Copy to NFS Device

Copy All Files

Copy to NonVol RAM

Copy to Vol RAM

Copy to 3.5” Disk

Copy to NFS Device

Format Disk Menu

MMEM:DEL ‘<loc>:<name>’

MMEM:DEL ‘MEM:*.*’

MMEM:COPY ‘<loc>:<name>’,‘<loc>:<name>’

MMEM:COPY [‘MEM:NAME

1

’|‘RAM:NAME

1

’

|‘INT:NAME

1

’|‘\NAME

1

’], ‘MEM:NAME

1

’


1

’|‘RAM:NAME

1

’

|‘INT:NAME

1

’|‘\NAME

1

’], ‘RAM:NAME

1

’


1

’|‘RAM:NAME

1

’

|‘INT:NAME

1

’|‘\NAME

1

’], ‘INT:NAME

1

’


1

’|‘RAM:NAME

1

’

|‘INT:NAME

1

’|‘\NAME

1

’], ‘\:NAME

1

’

MMEM:COPY ‘*.*’, ‘<loc>’

MMEM:COPY ‘*.*’, ‘MEM:NAME’

1

MMEM:COPY ‘*.*’, ‘RAM:NAME’

1

MMEM:COPY ‘*.*’, ‘INT:NAME’

1

MMEM:COPY ‘*.*’, ‘\ NAME’

1


Format NonVol RAM

Format Vol RAM

MMEM:INIT ‘MEM:’, DOS

MMEM:INIT ‘RAM:’, DOS

Format 3.5” Disk MMEM:INIT ‘INT:’, DOS

1. The name can include directory, for example: ‘MEM:\DIRNAME\NAME’.






SAVE RECALL, File Utilities, (continued)

Directory Utilities

Change Directory

Make Directory

Remove Directory

Fast Recall on OFF


MMEM:CDIR ‘<name>’

MMEM:MDIR ‘<name>’

MMEM:RDIR ‘<name>’

DISP:MENU:RECALL:FAST [ON|OFF]




Table 10-25 SCALE Functions, 8712ET/ES and 8714ET/ES

KEYSTROKES

SCALE

Autoscale

Scale/Div (enter value,

press Enter )

Reference Level (enter value, press Enter )

Reference Position (enter value, press Enter )

Reference Tracking

Off

Track Peak

Track Frequency

Set Track Frequency (enter value and unit press Enter)

Phase Offset (enter value, press Enter )

Electrical Delay (enter value and unit, press Enter )

SCPI COMMAND

(hardkey entry)

DISP:WIND[1|2]:TRAC:Y:AUTO ONCE

DISP:WIND[1|2]:TRAC:Y:PDIV <num>

DISP:WIND1:TRAC:Y:RLEV <num>

DISP:WIND1:TRAC:Y:RPOS <num>


DISP:WIND[1|2]:TRAC:Y:TRACK [ON|OFF]

DISP:WIND[1|2]:TRAC:Y:TRACK PEAK

DISP:WIND[1|2]:TRAC:Y:TRACK FREQ

DISP:WIND[1|2]:TRAC:Y:TRACK:FREQ <num>

SENS[1|2]:CORR:OFFS:PHAS <num> DEG

SENS[1|2]:CORR:EDEL:TIME <num> <unit>




Table 10-26 SWEEP Functions, 8712ET/ES and 8714ET/ES

KEYSTROKES

SWEEP

Sweep Time (enter value, and unit)

Sweep Time AUTO man

Alt Sweep on OFF

Step Sweep on OFF

Frequency Sweep

Power Sweep

SCPI COMMAND

(hardkey entry)

SENS[1|2]:SWE:TIME <num>[s|ms]; *WAI

SENS[1|2]:SWE:TIME:AUTO [ON|OFF]; *WAI

SENS:COUP [NONE|ALL]; *WAI

SENS[1|2]:SWE:GEN STEPPED; *WAI

POWER:MODE FIXED; *WAI

POWER:MODE SWEEP; *WAI




Table 10-27 SYSTEM OPTIONS Functions, 8712ET/ES and 8714ET/ES (1 of 9)


SYSTEM OPTIONS

IBASIC

Run

1

Continue

1

Step

1

Edit

1

(hardkey entry)


PROG:STAT:RUN

PROG:STAT:CONT

(no SCPI command)

(no SCPI command)

Key Record on OFF

Utilities

1

(no SCPI command)


Clear Program

Stack Size

Secure

IBASIC Display

None

Full

(no SCPI command)

(no SCPI command)

(no SCPI command)


DISP:PROG OFF

DISP:PROG FULL

Upper DISP:PROG UPP

LAN

Lower DISP:PROG LOW


Login User Setup (menu selection only)

1. Key record must be off to use this softkey.






SYSTEM OPTIONS, Lan, (continued)

Add Login User SYST:COMM:LAN:LOG:USER:ADD-?

<STRING>,<STRING>

User Name

Password

Confirm Password

SYST:COMM:LAN:LOG:USER:LIST: NAME?

<STRING>



Delete Login User SYST:COMM:LAN:LOG:USER:DEL-?

<STRING>,<STRING>

User Name

Password

SYST:COMM:LAN:LOG:USER:LIST: NAME?

<STRING>


Display User Lis t

Delete All Users

SYST:COMM:LAN:LOGin:USER:LIST:

COUN?


(menu selection only) LAN Port Setup

1

8712/14ES IP Address

(enter address, press Enter )

SYST:COMM:LAN:IPAD <IP address>

Gateway IP Address


Subnet Mask


SYST:COMM:LAN:ROUT:GAT

<IP address>

SYST:COMM:LAN:ROUT:SMAS

<IP address>

1. The analyzer model number appears here.

8712ES IP Address is shown as an example.







Diagnostic Utilities

IP Address to Ping


Perform Ping

Network stat Capture

Ethernet Address

NFS Device Setup

Mount NFS Device

Remote IP Addr/Host

Remote Path

Local Path

Automount At Powerup

Unmount NFS Device

Authentication

User ID

Group ID


DIAG:COMM:LAN:PING:IPAD

<IP address>

DIAG:COMM:LAN:PING:IMM

DIAG:COMM:LAN:NETW:STAT

SYST:COMM:LAN:EADD?


SYST:COMM:LAN:NFS:MOUN-?

<STRING>,<STRING>,<STRING>

SYST:COMM:LAN:NFS:MOUNT:LIST:REMH?

<#1-7>, <[STRING]>

SYST:COMM:LAN:NFS:MOUNT:LIST:REMF?

<#1-7>, <[STRING]>

SYST:COMM:LAN:NFS:MOUNT:LIST:LOCF?

<#1-7>, <[STRING]>

SYST:COMM:LAN:NFS:AUTO:ADD-?

<string>,<string>,<string>

SYST:COMM:LAN:NFS:UNMOUN-? <STRING>


SYST:COMM:LAN:NFS:AUTH:ID:

USER #0~4.74836e+07#

SYST:COMM:LAN:NFS:AUTH:ID:

GRO #0~4.74836e+07#





KEYSTROKES


Automount Setup

Remote IP Addr/Host

Remote Path

Local Path

Automount at Powerup

Remove Automount

Automount Dev Table

NFS Device Table

BOOTP Setup

BOOTP on OFF

TFTP

FTP

FTP User Name

FTP Password

Timeout

Optional Boot Host

SCPI COMMAND


SYST:COMM:LAN:NFS:AUTO:LIST:

REMH? <#1-7>, [,STRING]>

SYST:COMM:LAN:NFS:MOUNT:LIST:REMF?

<#1-7>, [,STRING]>

SYST:COMM:LAN:NFS:MOUNT:LIST:LOCF?

<#1-7>, [,STRING]>

SYST:COMM:LAN:NFS:AUTO:ADD-?


SYST:COMM:LAN:NFS:AUTO:REM-?

<string>

SYST:COMM:LAN:NFS:AUT:LIST:COUN?

SYST:COMM:LAN:NFS:MOUN:LIST:COUN?


SYST:COMM:LAN:BOOT:STAT <OFF|0|ON|1>

SYST:COMM:LAN:BOOT:TRAN:METH <TFTP>

SYST:COMM:LAN:BOOT:TRAN:METH <FTP>

SYST:COMM:LAN:BOOT:TRAN:FTP:USER

<STRING>

SYST:COMM:LAN:BOOT:TRAN:FTP:PASS-?

<STRING>

SYST:COMM:LAN:BOOT:TIM

#1~MAX_AUTO_CAL_TIME[S]#

SYST:COMM:LAN:BOOT:HOST <STRING>






SYSTEM OPTIONS , Lan (continued)

Optional File Path

Parameters Received

SICL LAN Setup


GPIB Name

GPIB Log. Unit

GPIB Dev Address

SCPI Sock. Setup


Socket Port No.

SYST:COMM:LAN:BOOT:TRAN:FILE:

NAME <STRING>



(no SCPI command)

SYST:COMM:LAN : SICL:GPIB:

NAME <STRING>


LU #0~1024#


ADDR #0~20, \22~23#


(no SCPI command)

SYST:COMM:LAN:SCPI:SOCK:DATA:PORT:

NUM #0~4.74836e+07#


SYST:COMM:GPIB:ADDR <address>

GPIB

8712ES Address


Talker Listener

System Controller

GPIB Echo ON off

8712ES Address


SYST:COMM:GPIB:CONT OFF

SYST:COMM:GPIB:CONT ON

SYST:COMM:GPIB:ECHO [ON|OFF]

SYST:COMM:GPIB:ADDR <address>




Table 10-28 SYSTEM OPTIONS Functions, 8712ET/ES and 8714ET/ES (6 of 9 )


SYSTEM OPTIONS , GPIB , (continued)

Talker Listener

System Controller

GPIB Echo ON off

System Config

Set Clock

Set Year

Set Day

(enter year, press Enter )

Set Month (enter month, press Enter )

(enter day, press Enter )

Set Hour (enter hour, press Enter )

Set Minute (enter minute, press Enter )

Round Seconds

Clock Format

YYYY-MM-DD

HH:MM

MM-DD-YYYY

HH:MM

DD-MM-YYYY

HH:MM

Numeric

SYST:COMM:GPIB:CONT OFF

SYST:COMM:GPIB:CONT ON

SYST:COMM:GPIB:ECHO [ON|OFF]



SYST:DATE <yyyy>,<m>,<d>



SYST:TIME <h>,<m>,<s>

SYST:TIME <h>,<m>,<s>

(no SCPI command)


DISP:ANN:CLOC:DATE:FORM YMD

DISP:ANN:CLOC:DATE:FORM MDY

DISP:ANN:CLOC:DATE:FORM DMY

DISP:ANN:CLOC:DATE:MODE NUM






SYSTEM OPTIONS, Sys Config, (continued)

Alpha

Seconds ON off

Beeper Volume (enter value, press Enter )

CRT Adjust


Vertical Position

Horizontal Position

Sync Green on OFF

Remove Pattern


Vertical Back Porch

Vertical Frnt Porch

Horizontal Back Porch

Horizontal Frnt Porch

Options Setup

Install Option (enter keyword, press Enter )

Special Option (enter key, press Enter )

DISP:ANN:CLOC:DATE:MODE ALPH

DISP:ANN:CLOC:SEC [ON|OFF]

SYST:BEEP:VOL <num>


(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)


(no SCPI command)

(no SCPI command)






SYSTEM OPTIONS, Sys Config, (continued)

User TTL Config

Default


SYST:COMM:TTL:USER:FEED DEFAULT

Softkey Auto-Step

Sweep Out

SYST:COMM:TTL:USER:FEED KEY

SYST:COMM:TTL:USER:FEED SWEEP

(menu selection only) Switching Test Set

Multiport ON off

1

Special Test Set

Operating Parameters (seven pages of parameters)

Hardcopy Screen

CONT1:MULT:STATE [ON|OFF]

(special test set use)


Hardcopy All

(no SCPI command)

(no SCPI command)

Abort

Next Screen

Previous Screen

Service

HCOP:ABOR

(screen selection only)

(screen selection only)


Tests and Adjustments

Select Self-Test

Select Adjustment

Execute Test


(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

Stop Test

Instrument Info

(no SCPI command)







SYSTEM OPTIONS, Service, (continued)

Update Corr Const

Install CC from Disk

Help Message

Load CC from Disk

Store CC to EPROM

Store CC to Disk

Update Corr Const

Install CC from Disk

Store CC to Disk


(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)

(no SCPI command)


(no SCPI command)

(no SCPI command)


11 SCPI Command Summary

This chapter describes all device commands recognized by the analyzer.

Example programs using these commands are given in the Example

Programs Guide. IEEE 488.2 common commands are described in

Chapter 9, “Introduction to SCPI.”

11-1

SCPI Command Summary

Queries, Forms, and Parameter Types


All device commands have both command and query forms unless specified as command only or query only. To create the query form of a command, replace the command parameter with a " ?

". For example, the following command and parameter selects the log magnitude format

( MLOGarithmic ) for the data display:

CALCulate[1|2]:FORMat:MLOGarithmic

To find which format is active, use the corresponding query command:

CALCulate[1|2]:FORMat?

The analyzer returns the short form of the mnemonic for the active state or value. In this example, the string MLOG (the short-form of

MLOGarithmic ) is returned to the device that sent the query.

<num> , <char> , <string> and <block> refer to the parameter type expected by the instrument as part of the command.




Parameter Types

In the following tables, the FORM column gives the parameter type returned by the instrument in response to a query. NR1, NR2 and NR3 refer to the different types of numeric data. CHAR (character data),

STRING (string data) and BLOCK (block data) are also used to describe response types. The parameter types expected by the instrument as part of a command are summarized below:

NR1

NR2

NR3

CHAR

STRING

BLOCK

Integers (such as +1, 0,

−

1, 123,

−

12345)

Floating point numbers with an explicit decimal point

(such as 12.3, +1.234,

−

0.12345)

Floating point numbers in scientific notation (such as

+1.23E+5, +123.4E-3, -456.789E+6)

Character parameters (sometimes referred to as discrete parameters) consisting of ASCII characters.

They are typically used for program settings that have a finite number of values.

String parameters can contain virtually any set of

ASCII characters. The string must begin with a single quote ( ' ) or a double quote ( " ) and end with the same character.

Block parameters are typically used to transfer large quantities of related data (like a data trace).

Some numeric parameters may be followed by an appropriate suffix.

Commands that accept a suffix also allow standard metric multipliers to be combined with the suffix. For example, commands that set a frequency will accept HZ, KHZ, MHZ and GHZ. Commands that set a time will accept S, MS, US, NS, PS, FS and AS. Note that case is ignored.

The multiplier "M" is interpreted as either milli- (10

-3

) or mega- (10

6

), depending on context. If no suffix is included, the default units for the parameter are used.



SCPI Device Command Summary

NOTE

NOTE


This SCPI command reference is also available online. It is stored inside your analyzer in electronic form. To use it, you must connect your instrument to the network, and access it using your Web browser. See the The LAN Interface User’s Guide Supplement for details.

Throughout this chapter, the following conventions are used:

• Square brackets ( [ ] ) are used to enclose a keyword that is optional or implied when programming the command; that is, the instrument will process the command to have the same effect whether the option node is omitted or not.

• Parameter types ( < > ) are distinguished by enclosing the type name in angle brackets.

• A vertical bar ( | ) can be read as “or” and is used to separate alternative parameter options.

• UPPER -case letters (as found in the command MODify , for example) are used to indicate the short form of a given mnemonic. The remaining lower-case letters are the rest of the long form mnemonic.

Table 11-1 ABORt

SUBSYSTEM COMMANDS

ABORt

FORM command only

DESCRIPTION

Aborts and resets the sweep in progress.




Table 11-2 CALCulate (1 of 7)

SUBSYSTEM

COMMANDS

CALCulate[1|2]:DATA?

1

CALCulate[1|2]:FORMat

<char>


:UNIT:MLIN <char>


:UNIT:MLOG <char>

FORM query only

BLOCK or NR3

CHAR

CHAR

CHAR

2

DESCRIPTION

Queries the formatted data trace — functionally equivalent to the command

TRAC? CH<1|2>FDATA .

Selects the display format for measurement data — choose from MLOGarithmic|

MLINear|SWR or PHASe|SMITh|POLar|

GDELay|REAL|IMAGinary|MIMPedance .

Selects linear magnitude units for Y-axis display. Choose from W|MW|UW|V|MV|UV .

Selects log magnitude units for Y-axis display.

Choose from

DBW|DBM|DBUW|DBV|DBMV|DBUV .

Sets the group delay aperture as a ratio of desired aperture / measured frequency span.

CALCulate[1|2]

:GDAPerture:APERture

<num>

NR3

CALCulate[1|2]

:GDAPerture:SPAN <num>

NR3 Specifies the group delay aperture in Hertz.

1. Refer to

Chapter 6 , "Trace Data Transfers," and to the ASCDATA and REALDATA

example programs in the Example Programs Guide for more information on this command.

2. The parameter type of the data is determined by the format selected — FORMat

REAL uses BLOCK data, FORMat ASCii uses NR3 data separated by commas.





SUBSYSTEM COMMANDS FORM DESCRIPTION

CALCulate[1|2]:LIMit:DISPlay

1

<ON|OFF>

NR1 Turns display of limit lines on/off.

CALCulate[1|2]:LIMit:MARKer

:FLATness:MAXimum <num>


:FLATness:MINimum <num>

NR3

NR3

Sets the maximum value for a flatness limit test.

Sets the minimum value for a flatness marker limit test.

Turns flatness marker limit test on/off.


:FLATness:STATe <ON|OFF>

1

NR1


:FREQuency:MAXimum <num>

2


:FREQuency:MINimum <num>

2

NR3

NR3

Sets the maximum value for delta frequency marker limit test.

Sets the minimum value for delta frequency marker limit test.


:FREQuency [:STATe] <ON|OFF>

1

NR1 Turns delta frequency marker limit testing on or off.


:STATistic:MEAN:MAXimum <num>


:STATistic:MEAN:MINimum <num>

NR3

NR3

Sets the maximum value for a statistic mean limit test.

Sets the minimum value for a statistic mean limit test.

Turn statistic mean marker limit test on/off.


:STATistic:MEAN:STATe

<ON|OFF>

1

NR1


:STATistic:PEAK:MAXimum <num>


:STATistic:PEAK:MINimum <num>

NR3

NR3

Sets the maximum value for a statistic peak-to-peak limit test.

Sets the minimum value for a statistic peak-to-peak limit test.

1. Binary parameters accept the values of 1 (on) and 0 (off) in addition to ON and OFF .

2. Numeric parameters may include an appropriate suffix; if no suffix is included, the default ( HZ for frequency or S for time) is assumed.







:STATistic:PEAK:STATe

<ON|OFF>

1

NR1 Turns statistic peak-to-peak marker limit test on/off.


:TILT:MAXimum <num>

2

NR3 Sets the maximum value for delta amplitude marker limit test.


:TILT:MINimum <num>

2


:TILT [:STATe] <ON|OFF>

1

NR3

NR1

Sets the minimum value for delta amplitude marker limit test.

Turns delta amplitude marker limit testing on or off.

CALCulate[1|2]:LIMit:SEGMent

[1|2|12]:AMPLitude:STARt

<num>

2

NR3 Sets the Begin Limit for the specified limit segment.


[1|2|12]:AMPLitude:STOP

<num>

2

NR3 Sets the End Limit for the specified limit segment.


:AOFF


[1|2|12]:DISTance:STARt

2

<num> command only

NR3

Turns off all limit segments for a given channel — deletes all segments in the channel's limit table.

Sets the Begin Distance for the specified limit segment.

(Option 100 only)


[1|2|12]:DISTance:STOP <num>


[1|2|12]:FREQuency:STARt

2

<num>

2

NR3

NR3

Sets the End Distance for the specified limit segment.

(Option 100 only)

Sets the Begin Frequency for the specified limit segment.

1. Binary parameters accept the values of 1 (on) and 0 (off) in addition to ON and OFF.








[1|2|12]:FREQuency:STOP

<num>

2

NR3 Sets the End Frequency for the specified limit segment.


[1|2|12]:POWer:STARt

<num>

2

NR3 Sets the Begin Power for the specified limit segment.


[1|2|12]:POWer:STOP

<num>

2

NR3 Sets the End Power for the specified limit segment.


[1|2|12]:STATe

<ON|OFF>

1

NR1 Turns the specified limit segment on/off

— adds or deletes the segment.


[1|2|12]:TYPE

<char>

CHAR Sets the limit type for the specified segment, choose from

LMAX|LMIN|PMAX|PMIN (Max Line,

Min Line, Max Point, Min Point) — sets all of the segment's limit parameters to their default values.

Turns the limit test on/off.

CALCulate[1|2]:LIMit:STATe

<ON|OFF>

1

NR1

CALCulate[1|2]:MARKer:AOFF command

only

Turns off all markers for a given channel — this has the effect of turning off marker functions and tracking as well.

CALCulate[1|2]:MARKer:BWIDth

<num>

2

NR3 Calculates the bandwidth of a bandpass filter — num is the target bandwidth

(

−

3 for the 3 dB bandwidth).








CALCulate[1|2]:MARKer

:FUNCtion:RESult?


:FUNCtion[:SELect] <char> query only

NR3

[,NR3,

NR3,

NR3]

CHAR

Queries the results of the active marker function — MAX and MIN return the amplitude; TARG returns the frequency;

BWID returns bandwidth, center frequency, Q and loss; STAT returns the frequency span, the mean and standard deviation of the amplitude response, and the peak-to-peak ripple; FLAT returns the frequency span, gain, slope and flatness; and FSTAT returns the insertion loss and peak-to-peak ripple of the passband of a filter, as well as the maximum signal amplitude in the stopband. Refer to the MARKERS example program in the Example

Programs Guide for more information.

Selects the active marker function — choose from

OFF|MAXimum|MINimum|TARGet

|BWIDth|NOTCh|MPEak|MNOTch

|STATistics|

FLATness|FSTATistics .

Turn marker function tracking on/off.


:FUNCtion:TRACking

1

<ON|OFF>

NR1


[1|2|8]:GDELay?


[1|2|8]:MAXimum query only command only

Returns the group delay value, in seconds, at the specified marker.

Sets the specified marker to the maximum value on the trace.


[1|2|8]:MAXimum:LEFT command only

Moves the specified marker to the next local maximum to the left.








[1|2|8]:MAXimum:RIGHt


[1|2|8]:MINimum


[1|2|8]:MINimum:LEFT


[1|2|8]:MINimum:RIGHt


:MODE <char>


:NOTCh <num>

3

command only command only command only command only

CHAR

NR3

Moves the specified marker to the next local maximum to the right.

Sets the specified marker to the minimum value on the trace.

Moves the specified marker to the next local minimum to the left.

Moves the specified marker to the next local minimum to the right.

Turns delta marker state on/off — choose ABSolute or RELative .

Calculates the notch width of a notch filter — num is the marker search level

(

−

6 for the default 6 dB bandwidth).

Sets the specified marker point.

CALCulate[1|2]

:MARKer[1|2|8]:POINt

1

NR3

CALCulate[1|2]

:MARKer:REFerence:X?

CALCulate[1|2]

:MARKer:REFerence:Y?

query only NR3 query only NR3

NR1

Queries the frequency of the reference marker.

Queries the amplitude of the reference marker.

Turns the specified marker on/off.

CALCulate[1|2]

:MARKer[1|2|8][:STATe]

<ON|OFF>

2

CALCulate[1|2]

:MARKer[1|2|8]:TARGet

<char>,<num>

3

CHAR,

NR3

Performs a marker search for a target value — char is the direction LEFT or

RIGHt .

1. Refer to "Displaying Measurement Results" in Chapter 7 of the User's Guide for more information on using this command.

2. Binary parameters accept the values of 1 (on) and 0 (off) in addition to ON and

OFF.







CALCulate[1|2]

:MARKer[1|2|8]:X <num>

CALCulate[1|2]

:MARKer[1|2|8]:X:ABS <num>

NR3

NR?

Sets the specified marker frequency

(or power if in power sweep).

Sets a marker to an absolute value

(such as frequency or amplitude). The set value is not relative to a reference marker if one is enabled.

Queries the specified marker amplitude.

CALCulate[1|2]

:MARKer[1|2|8]:Y?

CALCulate[1|2]

:MARKer[1|2|8]:Y:INDuctance?

CALCulate[1|2]

:MARKer[1|2|8]:Y:MAGNitude?

CALCulate[1|2]

:MARKer[1|2|8]:Y:PHASe?

query only NR3 query only NR3 query only NR3 query only NR3 query only NR3

Queries the specified marker's inductance when in Smith chart format.

Queries the specified marker's magnitude when in polar format.

Queries the specified marker's phase value when in polar format.

CALCulate[1|2]

:MARKer[1|2|8]:Y:REACtance?

CALCulate[1|2]

:MARKer[1|2|8]:Y:RESistance?

query only NR3

Queries the specified marker's reactance value when in Smith chart format.

Queries the specified marker's resistance value when in Smith chart format.

CALCulate[1|2]

:MATH[:EXPRession] <expr>

1

EXPR Selects a trace math expression — choose measurement trace from

(IMPL) for "data only" or

(IMPL/CH<1|2>SMEM) for "data / memory”.

1.

<expr> and EXPR represent expressions, a parameter type that consists of mathematical expressions that use character parameters and are enclosed in parentheses.




Table 11-3 CALibration


CALibration

:SELF:ALL

CALibration

:SELF:METHod

<ONEPort|TWOPort> command only

CHAR

Initiates a SelfCal on all ports that were calibrated during the Test Set Cal.

1

Selects the method of SelfCal: enhanced response/1-port or 2-port.

CALibration

:SELF <ON|OFF|ONCE>

2

NR1

CHAR

Initiates a SelfCal on the currently selected ports and selects Periodic

SelfCal ( ON ) or SelfCal Once ( OFF or

ONCE ).

1

CALibration

:SELF:TIMER <num>

CALibration

:ZERO:AUTO <ON|OFF|ONCE>

2

NR1

NR1

Sets the time interval for automatic

SelfCals.

1

Turns the broadband detector autozeroing function on/off.






Table 11-4 CONFigure


CONFigure <string>

FORM DESCRIPTION

STRING Configures the analyzer to measure a specific device type and parameter (the BEGIN function) — choose from one of the following strings:

'AMPLifier:TRANsmission'

'AMPLifier:REFLection'

'AMPLifier:TRANsmission:REVerse'

1

'AMPLifier:REFLection:REVerse'

1

'AMPLifier:POWer'

'FILTer:TRANsmission'

'FILTer:REFLection'

'BBANd:TRANsmission'

'BBANd:REFLection'

'BBANd:TRANsmission:REVerse'

1

'BBANd:REFLection:REVerse'

1

'MIXer:CLOSs'

'MIXer:GDEL'

'MIXer:REFLection'

'CABLe:TRANsmission'

'CABLe:REFLection'

'CABLe:FAULT'

'CABLe:SRL'

1. For use with 8712ES and 8714ES only.




Table 11-5 CONTrol

SUBSYSTEM COMMANDS FORM

CONTrol[1|2]:MULTiport

:STATE <ON|OFF>

NR1


DESCRIPTION

When on, configures analyzer for use with a multiport test set.

1

Table 11-6 DIAGnostic (1 of 4)


DIAGnostic:CCONstants:INSTalled?

DIAGnostic:CCONstants:LOAD

DIAGnostic:CCONstants:STORE:DISK

DIAGnostic:CCONstants:STORE

:EEPRom

DIAGnostic:COMMunicate:LAN

:NETWork:STAT

DIAGnostic:COMMunicate:LAN:PING

:IMM

DIAGnostic:COMMunicate:LAN:PING

:IPAD <string> query only NR1 command only command only command only

Queries if correction constants are installed in flash. Returns a 1 if true, and a 0 if false.

Loads default factory calibration constants from floppy disk to memory.

Stores default factory calibration constants from memory to floppy disk.

Stores default factory calibration constants from memory to flash

EEPROM.

command only command only

Displays the menu to set the IP address to ping and to perform ping.

"Pings" a remote user-specified

IP address. Used in troubleshooting or verifying a

LAN connection.

STRING Sets the IP address to ping.






DIAGnostic:COMMunicate:LAN:SEND

<IP_address>,<port_num>,<string> , < timeout>

FORM

NR1,

STRING

DESCRIPTION

Instructs the analyzer to open a socket to the specified IP address and port number, and send the string specified.

<timeout> is an integer <num> in the range 0-75 specifying the number of seconds allocated for a successful transmission. If 0 is specified, a minimum interval of

0.10 seconds is used. If

<timeout> is not specified, the default interval of 75 seconds is used.

DIAGnostic:MDISplay[1|2]

:CORRection

<I_Direct|I_SRcmatch|I_TRacking

|I_Response|I_LDmatch|I_ISolation

|M_Direct|M_ISolation|M_SRcmatch

|M_TRacking|M_Response|M_LDmatch

|M_XScalar|C_Direct|C_SRcmatch

|C_RTracking|C_LDmatch

|C_TTracking|C_Isolation> command only

DIAGnostic:COMMunicate:LA

N:SEND ? returns 0 if the last socket connection was successful, and -1 if the last socket connection failed. This may not be the last socket connection made by the IBASIC program. Multiple socket connections are possible, and telnet sessions may be interspersed among programmed socket connections.

Return to measurement mode and auto scales after viewing calibration uncertainties.







:CORRection <string>

FORM command only

DESCRIPTION

Displays corrected measurement uncertainties. Choose from one of the following strings:

Cal check

C_DIRECTivity

C_LDMATCH

C_ISOLATION

C_RTRACKING

C_SRCMATCH

C_TTRACKING

Interpolated Array (accessed through the service menu.)

I_DIRECTivity

I_RESPONSE

I_SRCMATCH

I_TRACKING

I_LDMATCH

I_ISOLATION

Master Array (accessed through the service menu.)

M_DIRECTivity

M_RESPONSE

M_SRCMATCH

M_TRACKING

M_XSCALAR

M_LDMATCH

I_ISOLATION


:RESTore command only

Returns to measurement mode and autoscales after viewing calibration uncertainties.






DIAGnostic:PORT:READ?

<port><register>

1

DIAGnostic:PORT:WRITE

<port><register>

2 query only

NR1,

NR1

NR1,

NR1,

NR1

Reads the rear panel I/O ports.

Writes to the rear panel I/O ports.

DIAGnostic:SNUMber <string>?

query only

STRING

NR1

Queries the instrument's serial number.

DIAGnostic:SPUR:METHod

<NONE|DITHer|AVOid>

Selects the spur avoid mode.

1. Refer to "Controlling Peripherals" in Chapter 7 of the User's Guide for more information on using this command. See also


and

Table 11-8 on page 11-19 .

2. See “Controlling Peripherals” in Chapter 7 of the User’s Guide for more information on using this command. See also


and

Table 11-8 on page 11-19 .


NOTE



Table 11-7

15

Port

Number

15

15

15

9

Writeable Ports

0

1

2

3

0

Register Description

Outputs 8-bit data to the Cent_D0 through D7 lines of the

Centronics port. Cent_D0 is the least significant bit,

Cent_D7 is the most significant bit. Checks Centronics status lines for:

• Out of Paper

• Printer Not on Line

• BUSY

• ACKNOWLEDGE

Sets/clears the user bit according to the least significant bit of A. A least significant bit equal to 1 sets the user bit high.

A least significant bit of 0 clears the user bit.

Sets/clears the limit pass/fail bit according to the least significant bit of A. A least significant bit equal to 1 sets the pass/fail bit high. A least significant bit of 0 clears the pass/fail bit.

Outputs 8-bit data to the Cent_D0 through D7 lines of the

Centronics port. Cent_D0 is the least significant bit,

Cent_D7 is the most significant bit. Does not check

Centronics status lines.

Outputs a byte to the serial port. The byte is output serially according to the configuration for the serial port.

When using the WRITEIO(15,0) or WRITEIO(15,3) command, the

Printer_Select Line is set high. However, when the instrument is doing hardcopy, the Printer_Select Line is set low. The Printer_Select line may or may not be used by individual printers. Check with your printer manual.




Table 11-8

9

15

15

15

15

Port

Number

Readable Ports

1

2

0

0

10

Register Description

Reads the serial port.

Reads the 8-bit data port Cent_D0 through D7.

Reads the user bit.

Reads the limit test pass/fail bit.

Reads the 8-bit status port.

• D0 — Cent_acknowledge

• D1 — Cent_busy

• D2 — Cent_out_of_paper

• D3 — Cent_on_line

• D4 — Cent_printer_err


Table 11-9



DISPlay (1 of 7)


DISPlay:ANNotation:CHANnel[1|

2][:STATe] <OFF|ON>

DISPlay:ANNotation

:CHANnel[1|2]:USER:LABel:DATA

2

<string>

1

NR1

STRING Specifies the string to be displayed in the measurement channel annotation area (above the graticule).

NR1

Enables/disables measurement channel annotation.

Enables user-defined measurement channel annotation.

DISPlay:ANNotation

:CHANnel[1|2]:USER:STATe<OFF|

ON>

1,2

DISPlay:ANNotation:CLOCk

:DATE:FORMat <char>


:DATE:MODE <char>


:MODE <char>

CHAR

CHAR

CHAR

Selects the Year/Month/Day ordering of the date in the clock display — choose from YMD|MDY|DMY .

Selects the format for the date in the clock display — choose NUMeric or

ALPHa .

Selects how the clock will appear in the measurement display title area — choose from LINE1|LINE2|OFF .

Turns on/off display of seconds in the clock display.


:SEConds[:STATe]<ON|OFF>

1

NR1

DISPlay:ANNotation

:FREQuency[1|2]:MODE <char>

DISPlay:ANNotation

:FREQuency[1|2]:RESolution

<char>

CHAR

CHAR

Sets the frequency annotation on the display — choose SSTOP (start/stop),

CSPAN (center/span) or CW .

Sets the resolution of display frequency values — choose from

MHZ|KHZ|HZ .

Enables/disables frequency annotation.

DISPlay:ANNotation:FREQuency

[1|2] [:STATe] <OFF|ON>

1

NR1


[1|2]:USER:LABel:DATA<string>

STRING A user-defined X-axis label.


2. Refer to "Displaying Measurement Results" in Chapter 7 of the User's Guide for more information on using this command.




Table 11-9 DISPlay (2 of 7)



[1|2]:USER:STARt<num>

2

NR3 Specifies the start value for user-defined frequency annotation.


[1|2]:USER:STATe[OFF|ON]

1,2

NR1 Enables user-defined frequency annotation.


[1|2]:USER:STOP<num>

2

NR3 Specifies the stop value for user-defined frequency annotation.


[1|2]:USER:SUFFix[:DATA]

<string>

2

STRING Specifies the suffix for user defined frequency annotation.

DISPlay:ANNotation:LIMit:ICON

[1|2]:FLAG[:STATe] <ON|OFF>

1

NR1 Enables/disables the display of the limit test fail icon.


[1|2] :POSition:X <num>


[1|2] :POSition:Y <num>

NR1

NR1

Positions the limit test pass/fail text and icon on the display. Accepts whole number values from 0 (flush left) to 100 (flush right).

Positions the limit test pass/fail text and icon on the display. Accepts whole number values from 0 (bottom of display) to 100 (top of display).

Turns the limit test "PASS/FAIL" text on or off.


[1|2] :TEXT[:STATe] <ON|OFF>

1

NR1

DISPlay:ANNotation:MARKer[1|2]

:NUMBers [:STATe] <OFF|ON>

1

NR1 Enables/disables the display of marker numbers on trace markers.

DISPlay:ANNotation:MARKer[1|2]

[:STATe]<ON|OFF>

1

NR1 Enables/disables the active marker annotation for measurement channels 1 and 2.


2. Refer to “Displaying Measurement Results” in Chapter 7 of the User’s Guide for more information on using this command.






DISPlay:ANNotation:MESSage:AOFF

DISPlay:ANNotation:MESSage

:CLEar

1


:DATA <string>

:STATe <ON|OFF>

1


1


STRING

NR1

Turns off any currently showing message window — includes message window, active entry and IBASIC window.

Removes a user-defined pop-up message window.

Displays a user-defined message in the pop-up message window.

Optional argument specifies the timeout: choose from

NONE|SHORt|MEDium|LONG .

Enables/disables the message window — CAUTION: this suppresses display of all messages (even ERROR messages).

Enters a string for the specified title line.

DISPlay:ANNotation:TITLe[1|2]

:DATA <string>

1

STRING

DISPlay:ANNotation:TITLe[:STATe]

<ON|OFF>

1

NR1 Turns on/off display of the title and clock.

DISPlay:ANNotation:YAXis:MODE

<char>

CHAR Sets mode for the Y-axis labels — choose RELative or ABSolute

Turns on/off Y-axis labels.

DISPlay:ANNotation:YAXis[:STATe]

2

<ON|OFF>

NR1

DISPlay:CMAP:COLor[1|2|…16]

:GREYscale <num>

NR2 Changes the default intensity of the selected item on the analyzer's internal monitor.

1. Refer to "Operator Interaction" in Chapter 7 of the User's Guide for more information on using this command.








:HSL <num>,<num>,<num>


:RGB <num,num,num>

DISPlay:CMAP:DEFault

DISPlay:CMAP:SCHeme <char>

NR2

NR2 command

only

CHAR

For use with an external VGA compatible monitor. Sets hue, saturation, and luminance for the selected display item. Accepted values for each parameter are 0 to 1.

For use with an external monitor.

Sets the color map based on the

Red/Green/Blue model. Accepted values for each parameter are 0 to 1.

For use with an external monitor.

Sets the color scheme to the factory default.

Sets the color scheme for an external monitor. Choose from

DEFault|DEFault2|GREY|

INVerse|CUSTom .

DISPlay:FORMat <char>

DISPlay:FORMat:EXPAND

<ON|OFF>

DISPlay:MENU:KEY[1|2|7]

<string>

1

CHAR Selects the format

(full or split screen) for displaying trace data — choose SINGle (overlay) or ULOWer (split).

NR1 Enables/disables expand measurement mode.

STRING Specifies the softkey menu labels from a remote controller or IBASIC

STRING Specifies the softkey menu labels when using user-defined BEGIN key.

DISPlay:MENU[2]:KEY[1|2|7]

<string>

1

DISPlay:MENU:RECall:FAST

2

[:STATe] <ON|OFF>

NR1 Turns on/off fast recall mode.

1. Refer to "Operator Interaction" in Chapter 7 of the User's Guide for more information on using this command.







DISPlay:PROGram[:MODE]

<char>

DISPlay:WINDow[1|2|10]

:GEOMetry:LLEFT?


:GEOMetry:SIZE?


:GEOMetry:URIGHT?

DISPlay:WINDow:GRAPhics

:BUFFer[:STATe]<ON|OFF>


:GRAPhics :CIRCle <num>

2

1

CHAR query only NR1,

NR1 query only

NR1, NR1 query only

NR1,NR1

NR1 command only

Selects the portion of the analyzer's screen to be used as an HP Instrument

BASIC display — choose from

OFF|FULL|UPPer|LOWer .

Queries the absolute pixel coordinates of the lower left corner of the selected display window.

Queries the width and height (in pixels) of the selected display window.

Queries the absolute pixel coordinates of the upper right corner of the selected display window.

Turn on/off buffering of user graphics commands.

Draws a circle of the specified Y-axis radius centered at the current pen location — num is the radius in pixels.

3

Clears the user graphics and graphics buffer for the specified window.


:GRAPhics :CLEar

3

command only


:GRAPhics :COLor <num>


:GRAPhics [:DRAW]

<num1>,<num2>

3

3

NR1 command only

Sets the color of the user graphics pen — choose from 0 for erase, 1 for bright, and

2 for dim.

Draws a line from the current pen position to the specified new pen position

— num1 and num2 are the new absolute

X and Y coordinates in pixels.

3


2. Refer to

Chapter 7, “Using Graphics,” for more information.

3. Refer to

Chapter 7 , and to the example program titled "GRAPHICS" in the Example

Programs Guide for more information.







:GRAPhics:LABel <string>


:GRAPhics:LABel:FONT <char>



:GRAPhics:RECTangle

<num1>,<num2>

1

1

:GRAPhics :MOVE <num1>,<num2>

1

command only

CHAR

Draws a label with the lower left corner at the current pen location.

Selects the user graphics label font

— choose from

SMALl|HSMall|NORMal|HNORmal|

BOLD|HBOLd|SLANt|HSLant .

NR1,NR1 Moves the pen to the specified new pen position — num1 and num2 are the new absolute X and Y coordinates in pixels.

1

command only

Draws a rectangle of the specified size with lower left corner at the current pen position — num1 and num2 are the width and height in pixels.

1

NR1 Specifies new coordinates for window.


:GRAPhics:SCALe

<xmin>,<xmax>,<ymin,<ymax>


:GRAPhics :STATe?

query onlyNR1

Queries whether a window is enabled for user graphics commands.

Turns display graticule on/off.

DISPlay:WINDow[1|2]:TRACe

:GRATicule:GRID[:STATe]<ON|OF

F>

2

NR1

DISPlay:WINDow[1|2]

:TRACe[1|2][:STATe]<ON|OFF>

2

NR1 Turns the display of trace and memory data from the specified measurement channel on/off.


:Y[:SCALe]:AUTO ONCE command only

Scales the measurement data for a best fit display.

1. Refer to “Using Graphics” in Chapter 7 and the “GRAPHICS” program in the

Example Programs Guide for more information on using this command.








:Y[:SCALe]:PDIVision<num>


:Y[:SCALe]:RLEVel<num>

1


1

:Y[:SCALe]:RPOSition <num>

1

NR3

NR3

NR3

Specifies the height (dB or units per division) of each vertical division of the specified measurement channel.

Specifies the value for the Y-axis reference position for the specified measurement channel.

Specifies the Y-axis reference position for the specified measurement channel.

Selects the method for reference offset tracking.


:TRACe[1|2]:Y:TRACk

<OFF|PEAK|FREQ>

CHAR


:TRACe[1|2]:Y:TRACk:FREQuency

<num>

1

NR3 Selects frequency to track with reference tracking.





Table 11-10 FORMat


FORMat:BORDer <char>

FORMat[:DATA] <char>[,<num>]

FORM

CHAR

CHAR

[,NR1]

DESCRIPTION

Specifiesa the byte order used for

GPIB data transfer — choose

NORMal or SWAPped (for

PC-compatible systems).

Specifies the data format for use during data transfer — choose from

REAL,64|REAL,32|INTeger,16

|ASCii .




Table 11-11 HCOPy (1 of 2)


HCOPy:ABORt

HCOPy:DEVice[1|2|3]:COLor

<ON|OFF>

1, 2 command

only

NR1

Aborts any hardcopy currently in progress.

Selects monochrome

ON

OFF or color

mode for hardcopy output.

HCOPy:DEVice[1|2|3]:LANGuage

<char>

2

HCOPy:DEVice[1|2|3]:MODE <char>

2

CHAR

CHAR

Selects the language for hardcopy output — choose from

PCL|HPGL|EPSon|IBM|PCX|

PCL5

3

Selects the graph and/or table(s) to appear on a hardcopy plot — choose from

GMARker|GRAPh|ISETtings|M

ARKer|TABLe .

Sets the left margin (for printer output) in millimeters.

HCOPy:DEVice[1|2|3]:PAGE:MARGin

:LEFT <num>

2

NR2

HCOPy:DEVice[1|2|3]:PAGE:MARGin

:TOP <num>

2

NR2 Sets the top margin (for printer output) in millimeters.

HCOPy:DEVice[1|2|3]:PAGE

:ORIentation <char>

2

HCOPy:DEVice[1|2|3]:PAGE:WIDTh

<num>

2

HCOPy:DEVice[1|2|3]:PORT <char>

2

CHAR

NR2

Sets printer output page orientation — choose PORTrait or LANDscape .

Sets the print width (for printer output) in millimeters.

CHAR Selects the communications port for hardcopy output — choose from

CENTronics|SERial|GPIB|MM

EMory|LAN .


2. For DEVice , use 1 for PCL/Epson printers, 2 for plotters, and 3 for PCL5 printers.

3.

EPSon and IBM produce the same results.




Table 11-11 HCOPy (2 of 2)


HCOPy:DEVice[1|2]:RESolution

<num>

1

HCOPy[:IMMediate]

HCOPy:ITEM[1|2|3]:ANNotation

:STATe <ON|OFF>

HCOPy:ITEM[1|2|3]:FFEed:STATe

<ON|OFF>

1, 2

1, 2

NR1 command

only

NR1

NR1

Sets the printer resolution in dots per inch.

Initiates a hardcopy output (print or plot).

For DEVice , use 1 for PCL/Epson printers, or 2 for plotters.

Turns on/off channel and frequency annotation as part of hardcopy output.

Turns on/off an automatic form feed at the completion of hardcopy output — use item 1 for printers and 2 for plotters.

Turns on/off graticule as part of hardcopy output.

HCOPy:ITEM[1|2|3]:GRATicule

:STATe <ON|OFF>

1, 2

NR1

HCOPy:ITEM[1|2|3]:MARKer:STATe

<ON|OFF>

2, 3

NR1 Turns on/off marker symbols as part of hardcopy output.

HCOPy:ITEM[1|2|3]:TITLe:STATe

<ON|OFF>

2, 3

NR1 Turns on/off title and clock lines as part of hardcopy output.

HCOPy:ITEM[1|2|3]:TRACe:STATe

<ON|OFF>

2, 3

NR1 Turns on/off trace data as part of hardcopy output.

1. For DEVice , use 1 for PCL/Epson printers, or 2 for plotters.

2. For DEVice , use 1 for PCL/Epson printers, 2 for plotters, and 3 for PCL5 printers.





Table 11-12 INITiate


INITiate[1|2]:CONTinuous

<ON|OFF>

1

NR1 Sets the trigger system to continuously sweep or to stop sweeping.

INITiate[1|2][:IMMediate] command only

Initiates a new measurement sweep.


Table 11-13 INPut


INPut:GAIN:AUTo <R|A|B>,<ON|OFF> command only

INPut:GAIN:SETTing <R|A|B>,

<HIGH|MEDHIGH|MEDIUM|LOW> command only

Sets the R, A, or B IF input automatic gain control on or off.

Sets the R, A, or B IF input gain to one of four choices: high, medium-high, medium, or low.




Table 11-14 MMEMory (1 of 3)


MMEMory:CATalog?<string>

1

MMEMory:CDIRectory <string>

MMEMory:COPY <string1>,

<string2>

1, 2

MMEMory:DELete <string>

MMEMory:INITialize

1, 2

[<string>[,<char>[,<num>]]]

FORM query only

STRING

STRING command only command only command only

DESCRIPTION

Lists the names of the files in memory.

(a directory listing, file names only.)

Changes the current directory on a DOS formatted disk — new directory must be on the same mass storage device.

Copies a file — string1 is the source file, string2 is the destination file.

Deletes a file — string is the filename.

Formats a disk — string is the mass storage device MEM:

(internal memory), or INT:

(internal floppy disk). Disk format char is DOS , and the interleave factor num .

MMEMory:LOAD:STATe 1, <string>

1, 3

command only

Recalls an instrument state from mass storage — string is the filename.

Recalls a user cal kit.

MMEMory:LOAD:CKIT:USER[:SELect]

<KIT1|KIT2...KIT10>

MMEMory:FILE:INFO?<string>

1

command only query only

STRING

Returns file information such as date/time.

(a directory listing, file names and more info.)

MMEMory:MDIRectory <string>

2

command only

Makes a new directory on a DOS formatted disk.

1. Filenames may include the mass storage device — MEM: (internal non-volatile memory), RAM: (internal volatile memory), INT: (internal 3.5 disk drive) or NFS local path. Wildcards ? and * may be used.

2. Be sure to catalog the desired disk using MMEM:MSIS before using this command.

3. Refer to "Automated Measurement Setup and Control" in Chapter 7 of the User's Guide for more information on using this command.






MMEMory:MOVE

<string1>,<string2>

1, 2

MMEMory:MSIS <string>

MMEMory:RDIRectory <string>

MMEMory:STORe:STATe 1,

<string>

<ON|OFF>

1, 2, 3

2

MMEMory:STORe:STATe:CORRection

3

command only

STRING command only command only

NR1

Moves or renames a file — string1 is the source (or old) filename and string2 is the destination (or new) filename.

Selects a mass storage device — choose MEM: (internal memory),

INT: (internal floppy disk drive), etc.

Deletes a directory from a DOS formatted disk.

Saves an instrument state to mass storage — string is the filename.

Turns the calibration on/off — part of the definition of a saved file.

MMEMory:STORe:STATe:FORMat

<char>

MMEMory:STORe:STATe:ISTate

<ON|OFF>

3

CHAR

NR1

Saves instrument state files to be compatible with older "A/B" model analyzers (choose B8711 ), or with current "C" model analyzers (choose C8711 ).

Turns the instrument state on/off — part of the definition of a saved file.

MMEMory:STORe:STATe:TRACe

<ON|OFF>

3

NR1 Turns the data trace on/off — part of the definition of a saved file.

1. File names may include the mass storage device name— MEM: (internal non-volatile memory), RAM: (internal volatile memory), INT: (internal 3.5” disk drive), or NFS

local path. Wildcards ?

and * may be used.

2. Be sure to catalog the desired disk using MMEM:MSIS before using this command.







MMEMory:STORe:STATe:TSCAL

<ON|OFF>

MMEMory:STORe:TRACe:FORMat

<char>

1

MMEMory:STORe:TRACe

<char>,<string>

2, 3

NR1 command only

CHAR

When on, the saved state will be the test set cal only.

Stores an ASCII list of trace and frequency values to a file — char is the formatted data trace

CH<1|2>FDATA and string is the filename.

Selects the format that the ASCII data will be saved in. Choose from LOTus 123 or TOUChstone .

Copies a file to or from the analyzer's disk drive.

5

MMEMory:TRANsfer:BDAT

<string>

2

[,<block>]

4

STRING,

BLOCK

MMEMory:TRANsfer[:HFS]

<string>

2

[,<block>]

4

STRING, Copies a file to or from the analyzer's disk drive.

5


2. File names may include the mass storage device name— MEM: ( internal non-volatile memory), RAM: (internal volatile memory), INT: (internal 3.5” disk drive), or NFS

local path. Wildcards ?

and * may be used.

3. Refer to “Automated Measurement and Control” in Chapter 7 of the User’s Guide for more information on using this command

4. Refer to the Example Programs Guide for more information on using this command.

5. Refer to the example programs PUTFILE and GETFILE in the Example Programs

Guide.




Table 11-15 OUTPut


OUTPut[:STATe] <ON|OFF>

1


NR1 Turns RF power from the source on/off.


Table 11-16 POWer

DESCRIPTION


POWer[1|2]:MODE <char> CHAR Specifies either frequency sweep

( FIXed ) or power sweep ( SWEep ).




Table 11-17 PROGram (1 of 2)


PROGram

1

:CATalog?

FORM DESCRIPTION query only

STRING

Lists the names of the defined

IBASIC programs — response is

"PROG" (if a program is present) or the null string ( "" ).

Downloads an IBASIC program from an external controller.

PROGram

1

[:SELected]

2

:DEFine

<block>

PROGram

1

[:SELected]

2

:DELete:ALL

BLOCK

PROGram

1

[:SELected]

:DELete[:SELected]

2

command

only command

only

Deletes all IBASIC programs from the program buffer — equivalent to an HP BASIC

SCRATCH A command.

Deletes the active IBASIC program — equivalent to an HP

BASIC SCRATCH A command.

Executes an IBASIC command.

PROGram

1

[:SELected]

2

:EXECute

<string> command

only

PROGram

1

<num>

[:SELected]

2

:MALLocate

NR1 Allocates memory space for

IBASIC programs — choose an integer between 2048 and

4000000 bytes.

1. IBASIC programs can be generated and controlled in the instrument.

2. Commands grouped under the SELected mnemonic in the PROGram subsystem operate on the active program buffer.




Table 11-17 PROGram (2 of 2)


PROGram [:SELected]

1

:NAME 'PROG'


PROGram [:SELected]

1

<string>,<data>

2

PROGram [:SELected]

<char>

PROGram [:SELected]

<string1>,<string2>

1

1

:NUMBer

:STATe

:STRing

STRING Selects the IBASIC program in the program buffer to be active.

BLOCK or NR3

2

Loads a new value for a numeric variable string in the active

IBASIC program — num is the new value.

CHAR Selects the state of the active

IBASIC program — choose from

STOP|PAUSe|RUN|CONTinue .

STRING Loads a new value for a string variable string1 in the active

IBASIC program — string2 is the new value.

PROGram [:SELected]

1

:WAIT

NR1 Waits until the IBASIC program completes.

1. Commands grouped under the SELected mnemonic in the PROGram subsystem operate on the active program buffer.






Table 11-18 ROUTe


ROUTe[1|2]:REFLection:PATH

:DEFine:PORT<1|2|…|12>

ROUTe[1|2]:TRANsmission:PATH

:DEFine: PORT <1|2|…|12>

ROUTe[1|2]:PATH:DEFine

: PORT <num>,<num>

FORM

NR1

NR1

NR1


2. For use with the 8712ES and 8714ES models only.

DESCRIPTION

Selects which port of the test set is connected to the REFLECTION port of the analyzer.

1

Selects which port of the test set is connected to the TRANSMISSION port of the analyzer.

1

Selects which port of the analyzer is to function as the reflection (RF out) port and which port is to function as the transmission (RF in) port. Choose from 1,2

(forward), or 2,1 (reverse).

2




Table 11-19 SENSe (1 of 16)


SENSe[1|2]:ACTIVE?

SENSe[1|2]:AVERage:CLEar

SENSe[1|2]:AVERage:COUNt

<num>

SENSe[1|2]:AVERage[:STATe]

<ON|OFF>

1

SENSe[1|2]:BWIDth

[:RESolution] <num> HZ query only command only

NR1

NR1

NR2

Returns true (1) if the channel is active, false (0) if the channel is not active. (Only one channel can be

“active” at a time.)

Re-starts the trace averaging function.

Specifies a count or weighting factor for the averaged measurement data.

Turns the trace averaging function on/off.

Specifies the bandwidth of the IF receiver (fine, narrow, medium or wide) to be used in the measurement

— choose

15 (fine)

250 (narrow)

1200 (medium narrow)

3700 (medium)

4000 (medium wide)

6500 (wide)

SENSe[1|2]:CORRection:

[OFF/ON]

1


ANNotation?

NR1 query only

NR3

Turns measurement calibration function on/off. Uncorrected readings are used when “off.”

Returns the current calibration annotation: "C", "C?", “Cx”, or "".


CAPacitance:CONNector <num>

Selects a connector compensating capacitance value. (For use with structural return loss measurements on analyzers with Option 100 only.)

1. NR1 values of 1 (on) and 0 (off) can be used in place of CHAR values ON and OFF.




Table 11-19 SENSe (2 of 16)


SENSe[1|2]:CORRection:CKIT:LOAD

:MODify:DELay? #0~1e-06[S]#


:MODify:LOSS? #0~1e+12#


:MODify:ZOFFset? #25~100[OHM]#

SENSe[1|2]:CORRection:CKIT:MODify

[:SElect]

<TYPenf|TYPenm|UD1|TYPe35mm

|TYPeff|TYPe716f|TPe716m|UD2

|TYPeapc7|UD3|UD4|...|UD10>

SENSe[1|2]:CORRection:CKIT:NAME

<KIT1|KIT2|...|KIT10>,<STRING>

SENSe[1|2]:CORRection:CKIT:OPEN

:MODify:CONE? #-10000~1[FARAD]#


:MODify:CTHRee? #-10000~1[FARAD]#


:MODify:CTWO? #-10000~1[FARAD]#


:MODify:CZERo? #-10000~1[FARAD]#



FORM

NR3

NR3

NR1

CHAR

STRING

NR3

NR3

NR3

NR3

NR3

DESCRIPTION

Sets or queries the cal kit load standard offset delay time.

Sets or queries the cal kit load standard offset loss value.

Sets or queries the cal kit load standard offset impedance value.

Selects or queries the cal kit connector type. Select

TYPe716f or TYPe716m for modifiable cal kit.

Sets the description of the user-defined calibration kit.

Sets or queries the cal kit open standard fringe capacitance C1

(f

1

, Farad/Hz) value.


(f

3

, Farad/Hz

3

) value.


(f

2

, Farad/Hz

2

) value.

Sets or queries the cal kit open standard fringe capacitance model C0 (f

0

, Farad) value.

Modifies or queries the cal kit open standard offset delay time.




Table 11-19 SENSe (3 of 16)






SENSe[1|2]:CORRection:CKIT:PRESet

[:IMMediate]-?

[<KIT1|KIT2|...|KIT10>]

SENSe[1|2]:CORRection:CKIT:SAVE?

<KIT1|KIT2|...|KIT10>

SENSe[1|2]:CORRection:CKIT:SHORt






SENSe[1|2]:CORRection:CKIT:THRU






FORM

NR3

Command

Only

CHAR

NR3

NR3

NR1

NR3

NR3

NR3

NR3

DESCRIPTION

Modifies or queries the cal kit open standard offset loss value.

Modifies or queries the cal kit open standard offset impedance value.

Sets all values of all user-defined cal kits to the default values.

Saves the user-defined cal kit or queries whether the selected user-defined cal kit has been saved.

Modifies or queries the cal kit short standard offset delay time.

Modifies or queries the cal kit short standard offset loss value.

Modifies or queries the cal kit short standard offset impedance value.

Modifies or queries the cal kit thru standard offset delay time.

Modifies or queries the cal kit thru standard offset loss value.

Modifies or queries the cal kit thru standard offset impedance value.




Table 11-19 SENSe (4 of 16)


SENSe[1|2]:CORRection:CLASs

[:SELect]?

SENSe[1|2]:CORRection:CLASs

[:SELect] <item>

SENSe[1|2]:CORRection:COLLect

:ABORt

CHAR command

only

Returns the current calibration choice. Returns string from the

<item> list (below). (ES models only)

Selects an existing calibration from the following <item> list:

DEFault1

DEFault2

REFLection3 *

TRANsmission1 *

TRANsmission2

TRANsmission3

TESTset1

TWOPort * calibration

*

*

Default factory one-port calibration

Default factory two-port calibration

User one-port calibration

User response calibration

User response and isolation calibration

User enhanced response calibration

Multi-port testset calibration

User two-port calibration Multi-port testset

* The requested user calibration may or may not be stored in memory, and may or may not be valid for the current instrument settings. If the requested user calibration is invalid, a valid user calibration will be selected, if found.

If no valid user calibration is found, the default factory calibration will be selected. The instrument can be queried with

SENSe[1|2]:CORRection:CLASs[:SELect]?

to determine the current calibration choice.

command

only

Aborts the calibration that is currently in progress.




Table 11-19 SENSe (5 of 16)



COLLect[:ACQuire] <char>

SENSe[1|2]:CORRection

:COLLect:CKIT:PORT[1|2|…|12

][:SELect]<string>

SENSe[1|2]:CORRection:COLLe ct:CKIT[:SELect]<string>

FORM DESCRIPTION command

only

Measures a calibration standard — select <char> from:

STANdard1

STANdard2

STANdard3

STANdard4

STANdard5

STANdard6

STANdard7

STRING Selects which port of the analyzer or multiport test set will be assigned a Cal

Kit. Also, selects a Cal Kit— choose from one of the following strings:



‘COAX,3.5MM,APC-3.5,50,IMPLIED’

‘USER|USER1|USER2,IMPLIED,

IMPLIED,IMPLIED, IMPLIED’

‘COAX,7MM,TYPE-F,75,IMPLIED’



‘COAX,7MM,APC-7,50,IMPLIED’

‘COAX,7MM,TYPE-7-16,50,FEMALE’

STRING Selects a Cal Kit— choose from one of the following strings:

'COAX,7MM,TYPE-N,50,FEMALE'

'COAX,7MM,TYPE-N,50,MALE'

'COAX,3.5MM,APC-3.5,50,IMPLIED'

'USER|USER1|USER2,IMPLIED,

IMPLIED,IMPLIED, IMPLIED'

'COAX,7MM,TYPE-F,75,IMPLIED'

'COAX,7MM,TYPE-N,75,FEMALE'

'COAX,7MM,TYPE-N,75,MALE'

‘COAX,7MM,TYPE-7-16,50,FEMALE’

‘COAX,7MM,TYPE-7-16,50,MALE’




Table 11-19 SENSe (6 of 16)


SENSe[1|2]:CORRection:COLL ect:ISTate[:AUTO]<ON|OFF>


COLLect:METHod <char>

1

NR1 command only

Selects the instrument state for calibration — choose Full Band ( ON ) or

User Defined ( OFF ).

Selects the type of calibration — choose from:

TRAN1 — Transmission response

TRAN2 — Transmission response &

Isolation

TRAN3 — Transmission enhanced response

REFL3 — Reflection one port

TESTset — Test Set Calibration

(Enhanced Response/1-Port)

1

TESTset1 — Test Set Calibration

(Enhanced Response/1-Port)

1

TESTset2 — Test Set Calibration

(2-Port)

1

VERIFY — Calibration Check

TWOPort — Two-port calibration

NONE — No calibration

Measures an open on the port selected during a test set calibration.

2

SENSe[1|2]:CORRection:COLL ect:MP:OPEN

<STAN1|STAN2|…|STAN12> command only

SENSe[1|2]:CORRection:COLL ect:MP:SHORT


Measures a short on the port selected during a test set calibration.

2






Table 11-19 SENSe (7 of 16)



:MP:LOAD


Measures a load on the port selected during a test set calibration.

2


:MP:THRU


Measures a thru on the port selected during a test set calibration.

2


:PORTS <2|4|6|8|10|12>


:SAVE


:VERify:REFLection

<STAN1|STAN2|…|STAN12>


:VERify:TRANsmission

<STAN1|STAN2|…|STAN12>;

NR1 command only command only command only

Selects the number of ports to perform a test set calibration on.

1

Completes and saves current calibration.

Measures a calibration standard during a cal check procedure for reflection measurements.

Measures a calibration standard during a cal check procedure for transmission measurements.

SENSe[1|2]:CORRection:CSET

[:SELect] DEFault

SENSe[1|2]:CORRection:CSET

[:SELect]?


CHAR

Restores the "factory" default calibration for the current measurement and channel.

Queries the current calibration type

— returns DEF (factory default),

FULL (full band) or USER (user defined).

SENSe[1|2]:CORRection:EDELay

:TIME <num>

2

SENSe[1|2]:CORRection:EXTensi on:REFLection[:TIME]<num>

2

NR3

NR3

Specifies the electrical delay in seconds.

Specifies the port extension at the reflection port, in seconds.






Table 11-19 SENSe (8 of 16)


SENSe[1|2]:CORRection:EXTension[:

1

STATe]<ON|OFF>

NR1 Enables port extensions.

SENSe[1|2]:CORRection:EXTension

:TRANsmission[:TIME] <num>

2

SENSe[1|2]:CORRection:IMPedance

:INPut:MAGNitude<num>

2


:INPut:MAGNitude:SELect ZO_50


:INPut:MAGNitude:SELect ZO_75

NR3

NR3

NR1

NR1

Specifies the port extension at the transmission port, in seconds.

Specifies the reference impedance for the Smith chart display. The default is the analyzer's system impedance.

Selects 50 ohms as the system impedance.

Selects 75 ohms as the system impedance.

SENSe[1|2]:CORRection:ISOLation

[:STATe] {OFF|0|ON|1}

SENSe[1|2]:CORRection:LENGth

:COAX <num>

2

NR1

NR2

Enables or disables use of isolation error correction when

2-port calibrations are selected.

Specifies the length of cable to be calibrated, in feet or meters.

3

SENSe[1|2]:CORRection:LENGth

:CONNector <num>

2

NR2 Specifies the length of an interface connector, in mm or inches.

3

SENSe[1|2]:CORRection:LOSS

:COAX <num>

2

NR2 Specifies the loss of a cable under test, in dB/100 ft.

3


2. Numeric parameters may include an appropriate suffix; if no suffix is included, the default ( HZ for frequency or S for time) is used.

3. For use with structural return loss measurements using analyzers with Option 100 only.




Table 11-19 SENSe (9 of 16)


SENSe[1|2]:CORRection:MODel

:CONNector[:IMMediate] command only

Measures the cable connector and determine the optimum values for connector length and connector capacitance.

3

Specifies the phase offset.

SENSe[1|2]:CORRection:OFFSet

:PHASe

NR3

SENSe[1|2]:CORRection:ONEPort

:REFLection[:IMMediate]

SENSe[1|2]:CORRection:ONEPort

:TRANSmission[:IMMediate]

SENSe[1|2]:CORRection:TWOPort

[:IMMediate] command only command only command only

Retrieves the user one-port reflection error correction factors from internal memory and applies them to the current measurement.

Retrieves the user one-port transmission error correction factors from internal memory and applies them to the current measurement.

Retrieves the user two-port error correction factors from internal memory and applies them to the current measurement.

Turns multi-peak correction on or off.

2

SENSe[1|2]:CORRection:PEAK

1

:COAX[:STATe]<ON|OFF>

NR1

SENSe:CORRection:RVELocity

:COAX <num>

SENSe[1|2]:CORRection:RVELocity

[:IMMediate]

3

NR3 command only

Specifies the velocity factor to be used when displaying the distance for electrical length and port extensions. 1.0 the speed of light.

Measures the cable and determine the optimum values for cable loss and velocity factor.

2


2. For use with fault location measurements on analyzers with Option 100 only.

3. Numeric parameters may include an appropriate suffix; if no suffix is included, the default (H Z for frequency or S for time) is assumed.




Table 11-19 SENSe (10 of 16)


SENSe[1|2]:CORRection:TESTSET command only

NR2

Brings up the Test Set Cal menu.

2

SENSe[1|2]:CORRection:THReshol d:COAX <num>

SENSe[1|2]:COUPle <char>

SENSe[1|2]:DETector[:FUNCtion]

<char>

SENSe[1|2]:DISTance:CENTer

<num>

SENSe[1|2]:DISTance:STARt

<num>

SENSe[1|2]:DISTance:UNITs

<char>

SENSe[1|2]:DISTance:STOP <num>

SENSe[1|2]:FREQuency:CENTer

2

<num>

CHAR

CHAR

NR3

NR3

CHAR

NR3

NR3

Selects multi-peak threshold value, in dB.

1

Turns the alternate sweep mode on/off — choose ALL (coupled sweep) or NONE (alternate sweep).

Specifies which detection mode is used to make the measurement — choose BBANd (broadband) or NBANd

(narrowband).

Sets the center distance for a fault location measurement, in feet or meters.

1

Sets the start distance for a fault location measurement, in feet or meters.

1

Specifies distance units. Choose

METers or FEET .

1

Sets the stop distance for a fault location measurement, in feet or meters.

1

Sets the center frequency of the RF source.






Table 11-19 SENSe (11 of 16)


SENSe[1|2]:FREQuency:MODE <char>

SENSe[1|2]:FREQuency:SPAN <num>

SENSe[1|2]:FREQuency:SPAN

:MAXimum <num>

1

SENSe[1|2]:FREQuency:STARt <num>

SENSe[1|2]:FREQuency:STOP <num>

1

1

1

CHAR

NR3

NR3

NR3

NR3

Sets the fault location measurement to CENTer

(bandpass) or LOWPass .

2

Sets the frequency span of the

RF source.

Sets the maximum frequency span of the RF source for bandpass fault location measurements.

2

Sets the start frequency of the

RF source.

Sets the stop frequency of the

RF source.

SENSe[1|2]:FREQuency:ZSTOp

<num>

1

SENSe[1|2]:FUNCtion?

NR3 query only

STRING

Sets the Z cutoff frequency for

cable impedance calculations.

2

See SENSe [1|2]:FUNction

‘. . . . .’ commands for string definitions .

Queries the measurement function — returns a string that defines the current measurement function.






Table 11-19


SENSe[1|2]:FUNCtion ‘FLOC

<num>,<num>’

SENSe (12 of 16)

FORM command only

SENSe[1|2]:FUNCtion

'XFRequency:POWer <num>' command only

DESCRIPTION

Specifies that the receiver will measure the ratio of the power (fault location) into the specified measurement channel.

For 8712ET/8714ET models—choose

1,0 (Forward A/R).

For 8712ES/8714ES models—choose

1,0 (Forward A/R), or 22, 20 (Reverse

B/R).

(For use with fault location measurement on analyzers with Option

100 only.)

Specifies that the receiver will measure the power into a specific detector on the specified measurement channel.

For 8712ET/8714ET models— choose from detectors 0 (R), 1 (A), 2 (B), 11 (Ext

X) or 12 (Ext Y).

For 8712ES/8714ES models—choose from detectors:

0 ( Forward R )

20 (Reverse R)

1 (Forward A)

21 (Reverse A)

11 (Forward Ext X)

12 (Forward Ext Y)

2 (Forward B)

22 (Reverse B)




Table 11-19


SENSe[1|2]:FUNCtion

'XFRequency:GDELay:RATio

<num>,<num>'

SENSe (13 of 16)

FORM command only

DESCRIPTION

Specifies that the receiver will measure the ratio of the power ( group delay) into the specified measurement channel. For

8712ET/8714ET models—choose ratio

2,0 (B/R).

For 8712ES/8714ES models—choose from ratios 2,0 (Forward B/R), or

21,20 (Reverse A/R).

SENSe[1|2]:FUNCtion

'XFRequency:POWer:RATio

<num>,<num>' command only

Specifies that the receiver will measure a ratio of the power into the specified measurement channel.

For 8712ET/8714ET models— choose from ratios 1,0 (A/R), 2,0 (B/R), 12,0

(Ext Y/R), 11,12 (Ext X/Ext Y), or

12,11 (Ext Y/Ext X).

For 8712ES/8714ES models—choose from ratios:

1,0 (Forward A/R)

21,20 (Reverse A/R)

2,0 (Forward B/R)

22,20 (Reverse B/R)

12,0 (Forward Ext Y/R)

11,12 (Forward Ext X/Ext Y)

12,11 (Forward Ext Y/Ext X)




Table 11-19 SENSe (14 of 16)


SENSe[1|2]:FUNCtion

'XFRequency:S <num>,<num>'

NR1,NR1 Specifies that the receiver will measure an s-parameter into the specified measurement channel. The s-parameter choices will depend on the number of ports. For example, with a 2-port device, choose from 1,1 ( S

11

), 1,2 ( S

12

), 2,2

( S

22

), or 2,1 ( S

21

).

As another example, with a 12-port device using the 87075C multiport test set, some choices would include 1,8

(S

18

), or 12,1 ( S

12

,

1

), or 7,7 (S

77

).

This command may be used in place of:

SENS[1|2]:FUNC ‘XFR:POW:RAT and ROUT[1|2}:PATH:DEF:PORT .

If using the 87075C multiport test set, this command may be used in place of the two commands just listed, as well as:

ROUT[1|2]:REFL:PATH:DEF:PORT and

OUT[1|2]:TRAN:PATH:DEF:PORT .

1

SENSe[1|2]:FUNCtion:FAULt

:CONNector [:IMMediate] command only

Forces a connector verification measurement on the alternate channel.

(For use with SRL measurements on analyzers with Option 100 only.)

1. For use with the 8712ES and 8714ES models only.




Table 11-19 SENSe (15 of 16)


SENSe[1|2]:FUNCtion:SRL

:<num>,<num>

1


NR1,NR1 Specifies that the receiver will measure the ratio of the power (SRL) into the specified measurement channel

2

.

For 8712ET/8714ET models—choose

1,0 (Forward A/R).

For 8712ES/8714ES models—choose

1,0 (Forward A/R), or 22, 20 (Reverse

B/R).


:IMPedance <num>

1

NR2

Sets the cable impedance.

2


:MODE <char>

CHAR Sets the auto z function to AUTO or

MANual

.

2

Starts a cable scan.

2


:SCAN[:IMMediate] command only

CHAR SENSe[1|2]:ROSCillator

:SOURce <char>

Specifies the source of the reference oscillator — select INTernal or

EXTernal .

SENSe[1|2]:STATe <ON|OFF>

3

NR1 Turns the specified channel on/off .


2. For use with structural return loss measurements on analyzers with Option 100 only.





Table 11-19 SENSe (16 of 16)


SENSe[1|2]:SWEep:POINts <num> NR1 Sets the number of data points for the measurement — choose from

3|5|11|21|51|101|201|401|8

01|1601 .

SENSe[1|2]:SWEep:TIME <num>

SENSe[1|2]:SWEep:TIME:AUTO

<ON|OFF|ONCE>

2

1

NR3

CHAR or

NR1

CHAR

Sets the sweep time.

Turns the automatic sweep time function on/off.

SENSe:SWEep:TRIGger:SOURce

<char>

SENSe[1|2]:WINDow[:TYPE] <char> CHAR

Sets the trigger source for each point in a sweep — choose

IMMediate or EXTernal (used in conjunction with

TRIGger[:SEQuence]:SOURce ).

Sets the window selection for fault location measurements.

Choose from RECTangular

(Minimum), HAMMing (Medium), or KBESsel (Maximum). (For use with fault location measurements on analyzers with

Option 100 only.)


2. Binary parameters accept the values of 1 (on) and 0 (off) in addition to ON and OFF

S

21

.




Table 11-20 SOURce

DESCRIPTION


SOURce[1|2]:POWer[:LEVel]

[:IMMediate][:AMPLitude]<num>

SOURce:POWer:PRESet <num>

1

NR3

NR3

Sets the RF power output from the source.

Sets the power level that the analyzer will always return to after an instrument preset.

SOURce[1|2]:POWer:RANGe <char> CHAR Specifies the power sweep range.

Choose from ATTen0

|ATTen10|ATTen20|ATTen30

|ATTen40 |ATTen50|ATTen60 .

SOURce[1|2]:POWer:STARt <num> NR3

NR3

Sets the power sweep start power.

Sets the power sweep stop power.

SOURce[1|2]:POWer:STOP <num>





Table 11-21 STATus (1 of 4)

DESCRIPTION


STATus:DEVice:CONDition?

STATus:DEVice:ENABle <num>

STATus:DEVice[:EVENt]?

STATus:DEVice:NTRansition <num>

STATus:DEVice:PTRansition <num>


:CONDition?

query only

NR1

NR1 query only

NR1

NR1

NR1 query only

NR1

Reads the Device Status condition register.

1

Sets and queries bits in the

Device Status enable register.

2

Reads and clears the Device

Status event register.

1


Device Status negative transition register.

2


Device Status positive transition register.

2

Reads the Averaging status condition register.

1

STATus:OPERation:AVERaging:

ENABle <num>


[:EVENt]?

NR1 query only

NR1


Averaging status enable register.

2

Reads and clears the Averaging status event register.

1


:NTRansition <num>

NR1 Sets and queries bits in the

Averaging status negative transition register.

2

1. Returns the sum of the decimal weights (2 n

where n is the bit number) of all bits currently set. For more information on using the status registers, refer to

Chapter

5, “Using Status Registers.”

2.

<num> is the sum of the decimal weights of all bits to be set.





DESCRIPTION



:PTRansition <num>

STATus:OPERation:CONDition?

STATus:OPERation:ENABle

<num>

STATus:OPERation[:EVENt]?


:CONDition?


:ENABle <num>


[:EVENt]?

NR1 query only

NR1

NR1 query only

NR1 query only

NR1

NR1 query only

NR1


Averaging status positive transition register.

1

Reads the Operational status condition register.

2


Operational status enable register.

1

Reads and clears the Operational status event register.

2

Reads the Measuring status condition register.

2


Measuring status enable register.

1

Reads and clears the Measuring status event register.

2


:NTRansition <num>


:PTRansition <num>

NR1

NR1


Measuring status negative transition register.

1


Measuring status positive transition register.

1

1.



where n is the bit number) of all bits currently set. For more information on using the status registers refer to

Chapter

5, “Using Status Registers.”





DESCRIPTION


STATus:OPERation:NTRansition

<num>

STATus:OPERation:PTRansition

<num>

STATus:PRESet

NR1

NR1 command only


Operational Status negative transition register.

1


Operational Status positive transition register.

1

Sets bits in most enable and transition registers to their default state.

Reads the Questionable Status condition register.

2

STATus:QUEStionable:CONDition?

query only

NR1

STATus:QUEStionable:ENABle <num> NR1

STATus:QUEStionable[:EVENt]?

STATus:QUEStionable:LIMit

:CONDition?

query only

NR1 query only

NR1


Questionable Status enable register.

1

Reads and clears the

Questionable Status event register.

2

Reads the Limit Fail condition register.

2

1.




Chapter 5,

“Using Status Registers.”





DESCRIPTION


STATus:QUEStionable:LIMit:

ENABle <num>


[:EVENt]?


:NTRansition <num>


:PTRansition <num>

NR1 query only

NR1

NR1

NR1

Sets and queries bits in the Limit

Fail enable register.

1

Reads and clears the Limit Fail event register.

2


Fail negative transition register.

1


Fail positive transition register.

1

STATus:QUEStionable:NTRansition

<num>

STATus:QUEStionable:PTRansition

<num>

NR1

NR1


Questionable Status negative transition register.

1


Questionable Status positive transition register.

1

1.




Chapter 5,

“Using Status Registers.”




Table 11-22 SYSTem (1 of 8)

DESCRIPTION


SYSTem:BEEPer[:IMMediate]

[<freq>[,<dur>[,<vol>]

1

SYSTem:BEEPer:VOLume <num>

NR3, NR3,

NR3

NR2

Instructs the analyzer to beep.

Arguments are frequency (Hz), duration (seconds), and volume

(0 to 1).

Sets the volume of the beeper

— num is a number between 0 for 0% and 1 for 100%.

Makes the analyzer the system controller.

SYSTem:COMMunicate:GPIB

:CONTroller[:STATe]<ON|OFF>

2,3

NR1

SYSTem:COMMunicate:GPIB:ECHO

<ON|OFF>

2

NR1 Turns GPIB mnemonic echo on/off .

SYSTem:COMMunicate:GPIB:HCOPy

:ADDRess <num>

SYSTem:COMMunicate:GPIB[:SELF]

:ADDRess <num>

4

NR1

NR1

Sets the address of an GPIB printer or plotter for hardcopy output — num must be an integer between 0 and 30.

Sets the analyzer's GPIB address — num must be an integer between 0 and 30.

SYSTem:COMMunicate:LAN:BOOTp

:HOST <string>


:STATE <OFF|0|ON|1>

STRING

NR1

Sets the host name or host IP address of the remote host that receives the BOOTP requests.

Sets a BOOTP request when the analyzer boots up.

1. <freq>, <dur>, and <vol> are optional <num> parameters.

2.

Binary parameters accept the values of 1 (on) and 0 (off) inaddition to ON and

OFF .

3. For use with IBASIC—this command cannot be executed from an external controller.

4. A delay of 5 seconds is required before a command is sent to the new address.





DESCRIPTION



:TIMeout

#1~MAX_AUTO_CAL_TIME[S]#


:TRANsfer:FILE:NAME <string>

NR1

STRING


:TRANsfer:FTP:PASSword-?

<string>


:TRANsfer:FTP:USERname

<string>


:TRANsfer:METHod <TFTP|FTP>

SYSTem:COMMunicate:LAN:EADDres s?

SYSTem:COMMunicate:LAN:IPADdre ss <string>

SYSTem:COMMunicate:LAN:LOGin

:USER:ADD-? <string>,<string>


:USER:DELETE-?

<string>,<string>


:USER:LIST:COUNt?


:USER:LIST:NAME? #1-7

SYSTem:COMMunicate:LAN:NFS

:AUTHentiation:ID:GROup

#0~4.74836e+07# command only

STRING

NR1 query only

STRING

STRING command only command only query only

NR1 query only

STRING

NR2

Sets the number of seconds the analyzer will retry the BOOTP requests at boot time.

Sets the path file name of the boot file you want to receive at boot time.

Selects the password of the remote

BOOTP host.

Selects the user name of the remote BOOTP host.

Selects TFTP as the file transfer program.

Queries the analyzer's ethernet address.

Sets the analyzer's Internet

Protocol address.

Selects the login user/password pairs.

Deletes the login user/password pairs.

Queries login user names.

Queries user name.

Selects the NFS remote file system for entering a Group ID.





DESCRIPTION



:AUTHentiation:ID:USER

#0~4.74836e+07#


:AUTOmount:ADD-?



:AUTOmount:LIST:COUNt?


:AUTOmount:LIST:LOCFilesys? #1-7


:AUTOmount:LIST:REMFilesys? #1-7


:AUTOmount:LIST:REMHost? #1-7

NR2 command only


:AUTOmount:REMove-? <string>


:MOUNT-?



:MOUNT:LIST:COUNt?


:MOUNT:LIST:LOCFilesys? #1-7


:MOUNT:LIST:REMFilesys? #1-7

Selects the NFS remote file system for entering a User ID.

Sets the mounted NFS device to the automount device table.

query only

NR1 query only

STRING query only

STRING query only

STRING

Selects the number of NFS devices in Automount list.

Selects the local file system name for an NFS device.

Queries the automount list.

command only command only query only

NR1 query only

STRING

STRING

Queries the remote host name

(or host IP address) for an NFS device.

Removes device from automount list.

Selects the remote host, file system, and local system name for an NFS device.

Queries the number of currently mounted NFS devices.

Queries the local file system name.

Selects the remote host file system name for an NFS device.





SYSTem:COMMunicate:LAN:SICL

:GPIB:ADDRess #0~20, 22~30#


:GPIB:LU #0~1024#


:GPIB:NAME <string>

NR1

NR1

STRING

DESCRIPTION



:MOUNT:LIST:REMHost? #1-7


:UNMount-? <string>

SYSTem:COMMunicate:LAN:PRINter

:HOSTname <string>

SYSTem:COMMunicate:LAN:ROUTe

:GATeway <string>

SYSTem:COMMunicate:LAN:ROUTe

:SMASk <string>

SYSTem:COMMunicate:LAN:SCPI

:SOCKet:PORT <num>

STRING

NONE

STRING

STRING

STRING

NR1

Selects the remote host name (or host IP address) for an NFS device.

Selects the NFS device table.

Specifies the IP address of the LAN printer.

Sets the IP address for a LAN gateway.

Sets the subnet mask.

Selects the port number for a socket connection to the analyzer for SCPI socket programming.

Sets the GPIB address for SICL

LAN.

Sets the GPIB logical unit number for SICL LAN.

Sets the GPIB name for SICL LAN.





DESCRIPTION


SYSTem:COMMunicate:SERial

:TRANsmit:BAUD <num>

SYSTem:COMMunicate:SERial

:TRANsmit:HANDshake <char>

NR1

CHAR

Sets the baud rate for hardcopy output to a device on the serial port

— choose from

1200|2400|4800|9600|19200 .

Sets the handshake for communication to a hardcopy device on the serial port — choose XON or

DTR .

SYSTem:COMMunicate:TTL:USER:

FEED <char>

SYSTem:DATE

<num1>,<num2>,<num3>

SYSTem:ERRor?

1

CHAR

NR1,

NR1,

NR1 query only

NR1,

STRING command

only

Selects the function of the USER

TTL IN/OUT port on the rear panel of the analyzer. Choose from

DEFault|KEY|SWEep .

Sets the year ( and day ( clock.

num3 num1 ), month ( num2

) of the real time

Queries the error queue — returns the error number and message.

SYSTem:KEY <char> Sends key names

2

which execute the same functions as front panel keys.

1. For more information on errors, refer to

Chapter 13, “SCPI Error Messages.”

2. A list analyzer front panel key codes is provided in

Chapter 8, “Front Panel Keycodes.”

)





DESCRIPTION


SYSTem:KEY:MASK?

query only

NR1

Queries the mask (shift, ctrl, alt) associated with a keypress on an external keyboard.

Clears the key queue.

SYSTem:KEY:QUEue:CLEar

SYSTem:KEY:QUEue:COUNt?


NR1

SYSTem:KEY:QUEue:MAXimum?

query only

NR1

Queries the number of key codes in the queue.

Queries the size of the key queue (the maximum number of key codes it can hold).

Turns on/off the key queue.

SYSTem:KEY:QUEue[:STATe]

1

<ON|OFF>

NR1

SYSTem:KEY:TYPE?

SYSTem:KEY:USER

SYSTem:KEY[:VALue]?

query only

CHAR command only query only

NR1

Queries the type of key that was pressed

— returns NONE , RPG , KEY (front panel key) or ASC (external keyboard).

Sets the User Request bit of the

Standard Event Status Register.

Queries the key code value for the last key pressed — RPG type returns the knob count, positive for clockwise rotation, KEY type returns the front panel keycode,

2

and ASC type returns the ASCII code number.


2. A list of the analyzer's front panel keycodes and key names is provided in

Chapter

8, “Front Panel Keycodes.”





DESCRIPTION


SYSTem:PRESet

SYSTem:SET <block>

SYSTem:SET:LRN? [<USER>]

1

SYSTem:SET:LRNLong? [<USER>]

1


BLOCK

BLOCK

Performs a system preset — this is the same as the front panel PRESET key.

Sends a learn string (obtained using *LRN?

) to the analyzer

— this command is included in the learn string.

Queries or set the instrument state.

Queries or set the instrument state, data, and calibration.

Similar to save/recall.

SYSTem:TIME <num1>,<num2>,<num3>

SYSTem:VERSion?

NR1, NR1,

NR1 query only

NR2

Sets the hour ( num1 ), minute

( num2 ) and second ( num3 ) of the real time clock.

Queries the SCPI version of the analyzer. See *IDN?

to query the firmware revision.

1. Refer to "Automated Measurement Setup and Control" in Chapter 7 of the User's

Guide for more information on using this command.






TEST:RESult?

TEST:SELect <num>

TEST:STATe <char>

TEST:VALue <num>

NR1

CHAR

NR1

DESCRIPTION

FORM query only

CHAR

Queries the result of the selected adjustment or self-test — the response will be

NULL|PASS|FAIL .

Selects the adjustment or self-test to execute.

Selects the state of the active adjustment or self-test — choose from RUN|CONTinue|STOP for the command. Query returns

NULL|RUN|PAUS|DONE .

Sets or queries a value for an adjustment or self-test.




Table 11-25 TRACe (1 of 2)


TRACe[:DATA]? <char> query only

BLOCK or NR3

1

Queries trace data — choose from the following array types:

CH<1|2>FDATA

CH<1|2>FMEM

Formatted data

2

Formatted memory data

2

CH<1|2>SDATA

CH<1|2>SMEM

Unformatted data

3

Unformatted memory data

3

CH<1|2><A|B|R>FWD Raw data

CH<1|2>SCORR<X> Two-port error correction terms.

Choose X from the list below:

Array choices for two-port error correction

1 Forward directivity

2 Forward source matching

3 Forward reflection tracking

4 Forward transmission tracking

5 Forward load matching

6 Forward isolation

7

8

9

10

11

12

Reverse directivity

Reverse source matching

Reverse reflection tracking

Reverse transmission tracking

Reverse load matching

Reverse isolation



2. Single magnitude value for each measured point.

3. Corrected data in real/imaginary pairs for each measured point.




Table 11-25 TRACe (2 of 2)


TRACe[:DATA] <char>,<data>

TRACe[:DATA] <char1>,<char2>

FORM command only command only

DESCRIPTION

Inputs trace data — choose from the above list of arrays. The data can be either BLOCK or NR3 type.

1

Note: See

Chapter 6

for more information.

Moves data from one internal array to another — char1 is the target array ( CH<1|2>SMEM ) while char2 is the source array

( CH<1|2>SDATA ). Note that the source and target arrays must be from the same measurement channel.

TRACe:CORRection:SIMulate

[:DATA] {STD1|STD2|...|STD12} command only

Reads simulated calibration standards. Loads pre-computed or stored measurements of calibration standards from a remote controller into the analyzer.

2

Computes cal error correction arrays.

TRACe:CORRection:SIMulate:SAVE

<TRAN1|TRAN2|TRAN3|REFL3|TESTset|

TESTset1|TESTset2|VERIFY||TWOPort

|NONE> command only

1.

The parameter type of the data is determined by the format selected — FORMat REAL uses

BLOCK data, FORMat ASCii uses NR3 data separated by commas.

2.

See the example program titled “SIMCAL.” This program demonstrates how to create 2-port correction arrays from measurements of the raw (uncorrected) calibration standards when using the analyzer’s simcal command.

Example programs can be found in the following four locations:

• Example Programs Disk, 8712ET/ES and 8714ET/ES (DOS format): part number

08714-10003

• Example Programs Disk, 8712ET/ES and 8714ET/ES (LIF format): part number 08714-10004

• Web site http://www.agilent.com. Use the search function to find Web pages related to

8712 example programs.

• Example Programs Guide, 8712ET/ES and 8714ET/ES: part number 08714-90016




Table 11-26 TRIGger


TRIGger[:SEQuence]:SOURce <char> CHAR Sets the source for the sweep trigger signal — choose IMMediate or EXTernal (used in conjunction with

SENSe:SWEep:TRIGger:SOURce ).


12 SCPI Conformance Information

12-1

SCPI Conformance Information

SCPI Conformance Information

SCPI Conformance Information

The 8712ET/ES and 8714ET/ES RF Network Analyzers conform to the

1996.0 version of SCPI.



SCPI Standard Commands


The analyzer implements the following IEEE 488.2 standard commands:

• *CLS

• *ESE

• *ESE?

• *ESR?

• *IDN?

• *LRN?

• *OPC

• *OPC?

• *OPT?

• *PCB

• *PSC

• *RST

• *SRE

• *SRE?

• *STB?

• *TRG

• *TST?

• *WAI

The analyzer implements the following SCPI 1996.0 standard commands:

• ABORt

• CALCulate[1|2]:DATA?

• CALCulate[1|2]:FORMat

• CALCulate[1|2]:FORMat?

• CALCulate[1|2]:GDAPerture:APERture




• CALCulate[1|2]:GDAPerture:SPAN

• CALCulate[1|2]:LIMit:STATe

• CALCulate[1|2]:LIMit:STATe?

• CALCulate[1|2]:MATH[:EXPRession]

• CALCulate[1|2]:MATH[:EXPRession]?

• CALibration:ZERO:AUTO

• CALibration:ZERO:AUTO?

• DISPlay:CMAP:COLor[1|2|…16]:HSL

• DISPlay:CMAP:COLor[1|2|…16]:HSL?

• DISPlay:CMAP:COLor[1|2|…16]:RGB

• DISPlay:CMAP:COLor[1|2|…16]:RGB?

• DISPlay:CMAP:DEFault

• DISPlay:MENU[1|2]:KEY[1|2|…7]?

• DISPlay:WINDow[1|2|10]:GEOMetry:LLEFT?

• DISPlay:WINDow[1|2|10]:GEOMetry:SIZE?

• DISPlay:WINDow[1|2|10]:GEOMetry:URIGHT?

• DISPlay:WINDow[1|2|10]:GRAPhics:CLEar

• DISPlay:WINDow[1|2|10]:GRAPhics:COLor

• DISPlay:WINDow[1|2|10]:GRAPhics:COLor?

• DISPlay:WINDow[1|2|10]:GRAPhics[:DRAW]

• DISPlay:WINDow[1|2|10]:GRAPhics:LABel

• DISPlay:WINDow[1|2|10]:GRAPhics:MOVE

• DISPlay:WINDow[1|2|10]:GRAPhics:MOVE?

• DISPlay:WINDow[1|2|10]:GRAPhics:STATe?

• DISPlay:WINDow[1|2]:TRACe:GRATicule:GRID[:STATe]

• DISPlay:WINDow[1|2]:TRACe:GRATicule:GRID[:STATe]?

• DISPlay:WINDow[1|2]:TRACe[1|2][:STATe]

• DISPlay:WINDow[1|2]:TRACe[1|2][:STATe]?


• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:AUTO

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:PDIVision

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:PDIVision?

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:RLEVel

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:RLEVel?

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:RPOSition

• DISPlay:WINDow[1|2]:TRACe:Y[:SCALe]:RPOSition?

• FORMat:BORDer

• FORMat:BORDer?

• FORMat[:DATA]

• FORMat[:DATA]?

• HCOPy:ABORt

• HCOPy:DEVice[1|2|3]:COLor

• HCOPy:DEVice[1|2|3]:COLor?

• HCOPy:DEVice[1|2|3]:LANGuage

• HCOPy:DEVice[1|2|3]:LANGuage?

• HCOPy:DEVice[1|2|3]:MODE

• HCOPy:DEVice[1|2|3]:MODE?

• HCOPy:DEVice[1|2|3]:RESolution

• HCOPy:DEVice[1|2|3]:RESolution?

• HCOPy[:IMMediate]

• HCOPy:ITEM:ANNotation:STATe

• HCOPy:ITEM:ANNotation:STATe?

• HCOPy:ITEM[1|2|3]:FFEed:STATe

• HCOPy:ITEM[1|2|3]:FFEed:STATe?

• INITiate[1|2]:CONTinuous

• INITiate[1|2]:CONTinuous?

• INITiate[1|2][:IMMediate]




12-5



• MMEMory:CATalog?

• MMEMory:CDIRectory

• MMEMory:CDIRectory?

• MMEMory:COPY

• MMEMory:DELete

• MMEMory:FILE:INFO?

• MMEMory:INITialize

• MMEMory:LOAD:STATe

• MMEMory:MOVE

• MMEMory:MSIS

• MMEMory:MSIS?

• MMEMory:STORe:STATe

• MMEMory:STORe:TRACe

• MMEMory:TRANsfer:BDAT

• MMEMory:TRANsfer[:HFS]

• OUTPut[:STATe]

• OUTPut[:STATe]?

• PROGram:CATalog?

• PROGram[:SELected]:DEFine

• PROGram[:SELected]:DEFine?

• PROGram[:SELected]:DELete:ALL

• PROGram[:SELected]:DELete[:SELected]

• PROGram[:SELected]:EXECute

• PROGram[:SELected]:MALLocate

• PROGram[:SELected]:MALLocate?

• PROGram[:SELected]:NAME

• PROGram[:SELected]:NAME?

• PROGram[:SELected]:NUMBer


• PROGram[:SELected]:NUMBer?

• PROGram[:SELected]:STATe

• PROGram[:SELected]:STATe?

• PROGram[:SELected]:STRing

• PROGram[:SELected]:STRing?

• PROGram[:SELected]:WAIT

• PROGram[:SELected]:WAIT?

• SENSe[1|2]:AVERage:COUNt

• SENSe[1|2]:AVERage:COUNt?

• SENSe[1|2]:AVERage[:STATe]

• SENSe[1|2]:AVERage[:STATe]?

• SENSe[1|2]:BWIDth[:RESolution]

• SENSe[1|2]:BWIDth[:RESolution]?

• SENSe[1|2]:CORRection:COLLect[:ACQuire]

• SENSe[1|2]:CORRection:COLLect:METHod

• SENSe[1|2]:CORRection:COLLect:SAVE

• SENSe[1|2]:CORRection:CSET[:SELect]

• SENSe[1|2]:CORRection:CSET[:SELect]?

• SENSe[1|2]:CORRection:EDELay:TIME

• SENSe[1|2]:CORRection:IMPedance:INPut:MAGNitude

• SENSe[1|2]:CORRection:OFFSet:PHASe

• SENSe[1|2]:CORRection:RVELocity:COAX

• SENSe[1|2]:CORRection[:STATe]

• SENSe[1|2]:CORRection[:STATe]?

• SENSe[1|2]:DETector[:FUNCTION]

• SENSe[1|2]:FREQuency:CENTer

• SENSe[1|2]:FREQuency:CENTer?

• SENSe[1|2]:FREQuency:SPAN




12-7



• SENSe[1|2]:FREQuency:SPAN?

• SENSe[1|2]:FREQuency:STARt

• SENSe[1|2]:FREQuency:STARt?

• SENSe[1|2]:FREQuency:STOP

• SENSe[1|2]:FREQuency:STOP?

• SENSe[1|2]:FUNCtion

• SENSe[1|2]:FUNCtion?

• SENSe:ROSCillator:SOURce

• SENSe:ROSCillator:SOURce?

• SENSe[1|2]:SWEep:POINts

• SENSe[1|2]:SWEep:POINts?

• SENSe[1|2]:SWEep:TIME

• SENSe[1|2]:SWEep:TIME?

• SENSe[1|2]:SWEep:TIME:AUTO

• SENSe[1|2]:SWEep:TIME:AUTO?

• SOURce[1|2]:POWer[:LEVel][:IMMediate][:AMPLitude]

• SOURce[1|2]:POWer[:LEVel][:IMMediate][:AMPLitude]?

• SOURce[1|2]:POWer:RANGe

• SOURce[1|2]:POWer:STARt

• SOURce[1|2]:POWer:STOP

• STATus:OPERation:CONDition?

• STATus:OPERation:ENABle

• STATus:OPERation:ENABle?

• STATus:OPERation[:EVENt]?

• STATus:OPERation:NTRansition

• STATus:OPERation:NTRansition?

• STATus:OPERation:PTRansition

• STATus:OPERation:PTRansition?


• STATus:QUEStionable:CONDition?

• STATus:QUEStionable:ENABle

• STATus:QUEStionable:ENABle?

• STATus:QUEStionable[:EVENt]?

• STATus:QUEStionable:NTRansition

• STATus:QUEStionable:NTRansition?

• STATus:QUEStionable:PTRansition

• STATus:QUEStionable:PTRansition?

• SYSTem:BEEPer[:IMMediate]?

• SYSTem:BEEPer:VOLume

• SYSTem:BEEPer:VOLume?

• SYSTem:COMMunicate:GPIB[:SELF]:ADDRess

• SYSTem:COMMunicate:GPIB[:SELF]:ADDRess?

• SYSTem:COMMunicate:SERial:TRANsmit:BAUD

• SYSTem:COMMunicate:SERial:TRANsmit:BAUD?

• SYSTem:DATE

• SYSTem:DATE?

• SYSTem:ERRor?

• SYSTem:KEY[:VALue]?

• SYSTem:PRESet

• SYSTem:SET

• SYSTem:SET:LRN?

• SYSTem:TIME

• SYSTem:TIME?

• SYSTem:VERSion?

• TRACe[:DATA]

• TRACe[:DATA]?

• TRIGger[:SEQuence]:SOURce

• TRIGger[:SEQuence]:SOURce?




12-9


Instrument Specific Commands


The following are instrument specific commands implemented by the 8712ET/ES and

8714ET/ES RF Network Analyzers which are not part of the present SCPI 1996.0 definition.

• CALCulate[1|2]:FORMat:UNIT:MLIN

• CALCulate[1|2]:FORMat:UNIT:MLIN?

• CALCulate[1|2]:FORMat:UNIT:MLOG

• CALCulate[1|2]:FORMat:UNIT:MLOG?

• CALCulate[1|2]:LIMit:DISPlay

• CALCulate[1|2]:LIMit:DISPlay?

• CALCulate[1|2]:LIMit:MARKer:FLATness:MAXimum

• CALCulate[1|2]:LIMit:MARKer:FLATness:MINimum

• CALCulate[1|2]:LIMit:MARKer:FLATness[:STATe]

• CALCulate[1|2]:LIMit:MARKer:FREQuency:MAXimum

• CALCulate[1|2]:LIMit:MARKer:FREQuency:MINimum

• CALCulate[1|2]:LIMit:MARKer:FREQuency[:STATe]

• CALCulate[1|2]:LIMit:MARKer:STATistic:MEAN:MAXimum

• CALCulate[1|2]:LIMit:MARKer:STATistic:MEAN:MINimum

• CALCulate[1|2]:LIMit:MARKer:STATistic:MEAN[:STATe]

• CALCulate[1|2]:LIMit:MARKer:STATistic:PEAK:MAXimum

• CALCulate[1|2]:LIMit:MARKer:STATistic:PEAK:MINimum

• CALCulate[1|2]:LIMit:MARKer:STATistic:PEAK[:STATe]

• CALCulate[1|2]:LIMit:MARKer:TILT:MAXimum

• CALCulate[1|2]:LIMit:MARKer:TILT:MINimum

• CALCulate[1|2]:LIMit:MARKer:TILT[:STATe]

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:AMPLitude:STARt

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:AMPLitude:STARt?

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:AMPLitude:STOP




• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:AMPLitude:STOP?

• CALCulate[1|2]:LIMit:SEGMent:AOFF

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:FREQuency:STARt

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:FREQuency:STARt?

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:FREQuency:STOP

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:FREQuency:STOP?

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:POWer:STOP

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:POWer:STOP?

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:STATe

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:STATe?

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:TYPE

• CALCulate[1|2]:LIMit:SEGMent[1|2|…12]:TYPE?

• CALCulate[1|2]:MARKer:AOFF

• CALCulate[1|2]:MARKer:BWIDth

• CALCulate[1|2]:MARKer:BWIDth?

• CALCulate[1|2]:MARKer:FUNCtion:RESult?

• CALCulate[1|2]:MARKer:FUNCtion[:SELect]

• CALCulate[1|2]:MARKer:FUNCtion[:SELect]?

• CALCulate[1|2]:MARKer:FUNCtion:TRACking

• CALCulate[1|2]:MARKer:FUNCtion:TRACking?

• CALCulate[1|2]:MARKer[1|2|…8]:GDELay?

• CALCulate[1|2]:MARKer[1|2|…8]:MAXimum

• CALCulate[1|2]:MARKer[1|2|…8]:MAXimum:LEFT

• CALCulate[1|2]:MARKer[1|2|…8]:MAXimum:RIGHt

• CALCulate[1|2]:MARKer[1|2|…8]:MINimum

• CALCulate[1|2]:MARKer[1|2|…8]:MINimum:LEFT

• CALCulate[1|2]:MARKer[1|2|…8]:MINimum:RIGHt

• CALCulate[1|2]:MARKer:MODE




• CALCulate[1|2]:MARKer:MODE?

• CALCulate[1|2]:MARKer:NOTCh

• CALCulate[1|2]:MARKer[1|2|…8]:POINt

• CALCulate[1|2]:MARKer[1|2|…8]:POINt?

• CALCulate[1|2]:MARKer:REFerence:X?

• CALCulate[1|2]:MARKer:REFerence:Y?

• CALCulate[1|2]:MARKer[1|2|…8][:STATe]

• CALCulate[1|2]:MARKer[1|2|…8][:STATe]?

• CALCulate[1|2]:MARKer[1|2|…8]:TARGet

• CALCulate[1|2]:MARKer[1|2|…8]:TARGet?

• CALCulate[1|2]:MARKer[1|2|…8]:X

• CALCulate[1|2]:MARKer[1|2|…8]:X?

• CALCulate[1|2]:MARKer[1|2|…8]:X:ABS

• CALCulate[1|2]:MARKer[1|2|…8]:Y?

• CALCulate[1|2]:MARKer[1|2|…8]:Y:INDuctance?

• CALCulate[1|2]:MARKer[1|2|…8]:Y:MAGNitude?

• CALCulate[1|2]:MARKer[1|2|…8]:Y:PHASe?

• CALCulate[1|2]:MARKer[1|2|…8]:Y:REACtance?

• CALCulate[1|2]:MARKer[1|2|…8]:Y:RESistance?

• CALibration:SELF

• CALibration:SELF:TIMER

• CALibration:SELF:ALL

• CONFigure

• CONFigure?

• CONTrol[1|2]:MULTiport:STATE

• DIAGnostic:CCONstants:INSTalled?

• DIAGnostic:CCONstants:LOAD

• DIAGnostic:CCONstants:STORe:DISK


• DIAGnostic:CCONstants:STORe:EEPRom

• DIAGnostic:COMMunicate:LAN:PING:IMM

• DIAGnostic:COMMunicate:LAN:PING:IPADress

• DIAGnostic:COMMunicate:LAN:SEND

• DIAGnostic:MDISplay[1|2]:CORRection C_DIRECT

• DIAGnostic:MDISplay[1|2]:CORRection C_ISOLATION

• DIAGnostic:MDISplay[1|2]:CORRection C_LDMATCH

• DIAGnostic:MDISplay[1|2]:CORRection C_RTRACKING

• DIAGnostic:MDISplay[1|2]:CORRection C_SRCMATCH

• DIAGnostic:MDISplay[1|2]:CORRection C_TTRACKING

• DIAGnostic:MDISplay[1|2]:CORRection I_DIRECTivity

• DIAGnostic:MDISplay[1|2]:CORRection I_RESPONSE

• DIAGnostic:MDISplay[1|2]:CORRection I_SRCMATCH

• DIAGnostic:MDISplay[1|2]:CORRection I_TRACKING

• DIAGnostic:MDISplay[1|2]:CORRection M_DIRECTivity

• DIAGnostic:MDISplay[1|2]:CORRection M_RESPONSE

• DIAGnostic:MDISplay[1|2]:CORRection M_SRCMATCH

• DIAGnostic:MDISplay[1|2]:CORRection M_TRACKING

• DIAGnostic:MDISplay[1|2]:CORRection M_XSCALAR

• DIAGnostic:MDISplay[1|2]:REST

• DIAGnostic:DITHer

• DIAGnostic:DITHer?

• DIAGnostic:SNUMber

• DIAGnostic:SNUMber?

• DIAGnostic:SPUR:AVOid

• DIAGnostic:SPUR:AVOid?

• DISPlay:ANNotation:CHANnel[1|2][:STATe]

• DISPlay:ANNotation:CHANnel[1|2]:USER:LABel[:DATA]






• DISPlay:ANNotation:CHANnel[1|2]:USER[:STATe]

• DISPlay:ANNotation:CLOCk:DATE:FORMat

• DISPlay:ANNotation:CLOCk:DATE:FORMat?

• DISPlay:ANNotation:CLOCk:DATE:MODE

• DISPlay:ANNotation:CLOCk:DATE:MODE?

• DISPlay:ANNotation:CLOCk:MODE

• DISPlay:ANNotation:CLOCk:MODE?

• DISPlay:ANNotation:CLOCk:SEConds[:STATe]

• DISPlay:ANNotation:CLOCk:SEConds[:STATe]?

• DISPlay:ANNotation:FREQuency[1|2]:MODE

• DISPlay:ANNotation:FREQuency[1|2]:MODE?

• DISPlay:ANNotation:FREQuency:RESolution

• DISPlay:ANNotation:FREQuency:RESolution?

• DISPlay:ANNotation:FREQuency[1|2][:STATe]

• DISPlay:ANNotation:FREQuency[1|2]:USER:LABel[:DATA]

• DISPlay:ANNotation:FREQuency[1|2]:USER:STARt

• DISPlay:ANNotation:FREQuency[1|2]:USER[:STATe]

• DISPlay:ANNotation:FREQuency[1|2]:USER:STOP

• DISPlay:ANNotation:FREQuency[1|2]:USER:SUFFIX

• DISPlay:ANNotation:LIMit:ICON[1|2]:FLAG

• DISPlay:ANNotation:LIMit:ICON[1|2]:POS:X

• DISPlay:ANNotation:LIMit:ICON[1|2]:POS:Y

• DISPlay:ANNotation:LIMit:ICON[1|2]:TEXT

• DISPlay:ANNotation:LIMit:ICON[1|2]:STATe

• DISPlay:ANNotation:MARKer[1|2]:NUMBers[:STATe]

• DISPlay:ANNotation:MARKer[1|2][:STATe]

• DISPlay:ANNotation:MARKer[1|2][:STATe]?

• DISPlay:ANNotation:MESSage:AOFF


• DISPlay:ANNotation:MESSage:CLEar

• DISPlay:ANNotation:MESSage[:DATA]?

• DISPlay:ANNotation:MESSage:STATe

• DISPlay:ANNotation:MESSage:STATe?

• DISPlay:ANNotation:TITLe[1|2]:DATA

• DISPlay:ANNotation:TITLe[1|2]:DATA?

• DISPlay:ANNotation:TITLe[:STATe]

• DISPlay:ANNotation:TITLe[:STATe]?

• DISPlay:ANNotation:YAXis:MODE

• DISPlay:ANNotation:YAXis:MODE?

• DISPlay:ANNotation:YAXis[:STATe]

• DISPlay:ANNotation:YAXis[:STATe]?

• DISPlay:CMAP:COLor[1|2|…16]:GREYscale

• DISPlay:CMAP:SCHeme

• DISPlay:FORMat

• DISPlay:FORMat?

• DISPlay:FORMat:EXPAND

• DISPlay:MENU:RECall:FAST[:STATe]

• DISPlay:PROGram[:MODE]

• DISPlay:PROGram[:MODE]?

• DISPlay:WINDow:GRAPhics:BUFFer[:STATe]

• DISPlay:WINDow:GRAPhics:BUFFer[:STATe]?

• DISPlay:WINDow[1|2|10]:GRAPhics:CIRCle

• DISPlay:WINDow[1|2|10]:GRAPhics:LABel:FONT

• DISPlay:WINDow[1|2|10]:GRAPhics:LABel:FONT?

• DISPlay:WINDow[1|2|10]:GRAPhics:RECTangle

• DISPlay:WINDow[1|2|10]:TRACe[1|2]:Y:TRACk

• HCOPy:DEVice:PAGE:MARGin:LEFT




12-15



• HCOPy:DEVice:PAGE:MARGin:TOP

• HCOPy:DEVice:PAGE:ORIentation

• HCOPy:DEVice:PAGE:WIDTh

• HCOPy:DEVice:PORT

• HCOPy:DEVice:PORT?

• HCOPy:ITEM:GRATicule:STATe

• HCOPy:ITEM:GRATicule:STATe?

• HCOPy:ITEM:MARKer:STATe

• HCOPy:ITEM:MARKer:STATe?

• HCOPy:ITEM:TITLe:STATe

• HCOPy:ITEM:TITLe:STATe?

• HCOPy:ITEM:TRACe:STATe

• HCOPy:ITEM:TRACe:STATe?

• HCOPy:PAGE:MARGin:LEFT

• HCOPy:PAGE:MARGin:LEFT?

• HCOPy:PAGE:MARGin:TOP

• HCOPy:PAGE:MARGin:TOP?

• HCOPy:PAGE:ORIentation

• HCOPy:PAGE:ORIentation?

• HCOPy:PAGE:WIDTh

• HCOPy:PAGE:WIDTh?

• INPut:GAIN:AUTO

• INPut:GAIN:SETTing

• MMEMory:MDIRectory

• MMEMory:RDIRectory

• MMEMory:STORe:STATe:CORRection

• MMEMory:STORe:STATe:CORRection?

• MMEMory:STORe:STATe:ISTate




• MMEMory:STORe:STATe:ISTate?

• MMEMory:STORe:STATe:TRACe

• MMEMory:STORe:STATe:TRACe?

• MMEMory:STORe:STATe:TSCAL

• MMEMory:STORe:TRACe

• MMEMory:STORe:TRACe:FORMat

• MMEMory:TRANsfer:BDAT

• MMEMory:TRANsfer[:HFS]

• POWer\[1|2]:MODE

• ROUTe[1|2]:REFLection:PATH:DEFine:PORT

• ROUTe[1|2]:TRANsmission:PATH:DEFine:PORT

• SENSe[1|2]:AVERage:CLEar

• SENSe[1|2]:CORRection:CAPacitance:CONNector (Option 100 only)

• SENSe[1|2]:CORRection:CAPacitance:CONNector?

(Option 100 only)

• SENSe[1|2]:CORRection:COLLect:ABORt

• SENSe[1|2]:CORRection:COLLect:CKIT[:SELect]

• SENSe[1|2]:CORRection:COLLect:CKIT[:SELect]?

• SENSe[1|2]:CORRection:COLLect:ISTate[:AUTO]

• SENSe[1|2]:CORRection:COLLect:ISTate[:AUTO]?

• SENSe[1|2]:CORRection:COLLect:PORTS

• SENSe[1|2]:CORRection:COLLect:MP:OPEN

• SENSe[1|2]:CORRection:COLLect:MP:SHORT

• SENSe[1|2]:CORRection:COLLect:MP:LOAD

• SENSe[1|2]:CORRection:COLLect:MP:THRU

• SENSe[1|2]:CORRection:COLLect:VERify:TRANsmission

• SENSe[1|2]:CORRection:COLLect:VERify:REFLection

• SENSe[1|2]:CORRection:EXTension[:STATe]

• SENSe[1|2]:CORRection:EXTension:REFLection[:TIME]




• SENSe[1|2]:CORRection:EXTension:TRANsmission[:TIME]

• SENSe[1|2]:CORRection:IMPedance:INPut:MAGNitude:SELect

• SENSe[1|2]:CORRection:LENGth:COAX (Option 100 only)

• SENSe[1|2]:CORRection:LENGth:COAX?

(Option 100 only)

• SENSe[1|2]:CORRection:LENGth:CONNector (Option 100 only)

• SENSe[1|2]:CORRection:LENGth:CONNector?

(Option 100 only)

• SENSe[1|2]:CORRection:LOSS:COAX (Option 100 only)

• SENSe[1|2]:CORRection:LOSS:COAX?

(Option 100 only)

• SENSe[1|2]:CORRection:MODel:CONNector[:IMMediate] (Option 100 only)

• SENSe[1|2]:CORRection:PEAK:COAX (Option 100 only)

• SENSe[1|2]:CORRection:PEAK:COAX?

(Option 100 only)

• SENSe[1|2]:CORRection:RVELocity[:IMMediate] (Option 100 only)

• SENSe[1|2]:CORRection:TESTSET

• SENSe[1|2]:CORRection:THReshold:COAX (Option 100 only)

• SENSe[1|2]:CORRection:THReshold:COAX?

(Option 100 only)

• SENSe:COUPle

• SENSe:COUPle?

• SENSe[1|2]:DETector[:FUNCtion]

• SENSe[1|2]:DETector[:FUNCtion]?

• SENSe:DISTance:STARt (Option 100 only)

• SENSe:DISTance:STARt?

(Option 100 only)

• SENSe:DISTance:STOP (Option 100 only)

• SENSe:DISTance:STOP?

(Option 100 only)

• SENSe:DISTance:UNITs (Option 100 only)

• SENSe:DISTance:UNITs?

(Option 100 only)

• SENSe:FREQuency:MODE (Option 100 only)

• SENSe:FREQuency:MODE?

(Option 100 only)

• SENSe:FREQuency:SPAN:MAXimum?

(Option 100 only)


• SENSe:FREQuency:SPAN:MAXimum (Option 100 only)

• SENSe:FREQuency:ZSTop (Option 100 only)

• SENSe:FREQuency:ZSTop?

(Option 100 only)

• SENSe:FUNCtion:SRL:IMPedance (Option 100 only)

• SENSe:FUNCtion:SRL:IMPedance?

(Option 100 only)

• SENSe:FUNCtion:SRL:MODE (Option 100 only)

• SENSe:FUNCtion:SRL:MODE?

(Option 100 only)

• SENSe:FUNCtion:SRL:SCAN[:IMMediate] (Option 100 only)

• SENSe[1|2]:STATe

• SENSe[1|2]:STATe?

• SENSe:SWEep:TRIGger:SOURce

• SENSe:SWEep:TRIGger:SOURce?

• SENSe:WINDow[:TYPE] (Option 100 only)

• SENSe:WINDow[:TYPE]?

(Option 100 only)

• STATus:DEVice:CONDition?

• STATus:DEVice:ENABle

• STATus:DEVice:ENABle?

• STATus:DEVice[:EVENt]?

• STATus:DEVice:NTRansition

• STATus:DEVice:NTRansition?

• STATus:DEVice:PTRansition

• STATus:DEVice:PTRansition?

• STATus:OPERation:AVERaging:CONDition?

• STATus:OPERation:AVERaging:ENABle

• STATus:OPERation:AVERaging:ENABle?

• STATus:OPERation:AVERaging[:EVENt]?

• STATus:OPERation:AVERaging:NTRansition

• STATus:OPERation:AVERaging:NTRansition?






• STATus:OPERation:AVERaging:PTRansition

• STATus:OPERation:AVERaging:PTRansition?

• STATus:OPERation:MEASuring:CONDition?

• STATus:OPERation:MEASuring:ENABle

• STATus:OPERation:MEASuring:ENABle?

• STATus:OPERation:MEASuring[:EVENt]?

• STATus:OPERation:MEASuring:NTRansition

• STATus:OPERation:MEASuring:NTRansition?

• STATus:OPERation:MEASuring:PTRansition

• STATus:OPERation:MEASuring:PTRansition?

• STATus:PRESet

• STATus:QUEStionable:LIMit:CONDition?

• STATus:QUEStionable:LIMit:ENABle

• STATus:QUEStionable:LIMit:ENABle?

• STATus:QUEStionable:LIMit[:EVENt]?

• STATus:QUEStionable:LIMit:NTRansition

• STATus:QUEStionable:LIMit:NTRansition?

• STATus:QUEStionable:LIMit:PTRansition

• STATus:QUEStionable:LIMit:PTRansition?

• SYSTem:COMMunicate:GPIB:CONTroller[:STATe]

• SYSTem:COMMunicate:GPIB:CONTroller[:STATe]?

• SYSTem:COMMunicate:GPIB:ECHO

• SYSTem:COMMunicate:GPIB:ECHO?

• SYSTem:COMMunicate:GPIB:HCOPy:ADDRess

• SYSTem:COMMunicate:GPIB:HCOPy:ADDRess?

• SYSTem:COMMunicate:GPIB:MMEMory:ADDRess

• SYSTem:COMMunicate:GPIB:MMEMory:ADDRess?

• SYSTem:COMMunicate:GPIB:MMEMory:UNIT


• SYSTem:COMMunicate:GPIB:MMEMory:UNIT?

• SYSTem:COMMunicate:GPIB:MMEMory:VOLume

• SYSTem:COMMunicate:GPIB:MMEMory:VOLume?

• SYSTem:COMMunicate:GPIB:MMEMory:VOLume?

• SYSTem:COMMunicate:LAN:EADDress?

• SYSTem:COMMunicate:LAN:IPADdress

• SYSTem:COMMunicate:LAN:IPADdress?

• SYSTem:COMMunicate:LAN:PRINter:HOSTname

• SYSTem:COMMunicate:LAN:PRINter:HOSTname?

• SYSTem:COMMunicate:LAN:ROUTe:GATeway

• SYSTem:COMMunicate:LAN:ROUTe:GATeway?

• SYSTem:COMMunicate:LAN:ROUTe:SMASk

• SYSTem:COMMunicate:LAN:ROUTe:SMASk?

• SYSTem:COMMunicate:LAN:STATe

• SYSTem:COMMunicate:LAN:STATe?

• SYSTem:COMMunicate:SERial:TRANsmit:HANDshake

• SYSTem:COMMunicate:SERial:TRANsmit:HANDshake?

• SYSTem:COMMunicate:TTL:USER:FEED

• SYSTem:COMMunicate:TTL:USER:FEED?

• SYSTem:KEY:MASK?

• SYSTem:KEY:QUEue:CLEar

• SYSTem:KEY:QUEue:COUNt?

• SYSTem:KEY:QUEue:MAXimum?

• SYSTem:KEY:QUEue[:STATe]

• SYSTem:KEY:QUEue[:STATe]?

• SYSTem:KEY:TYPE?

• SYSTem:KEY:USER

• SYSTem:SET:LRNLong




12-21

• TEST:RESult?

• TEST:SELect

• TEST:SELect?

• TEST:STATe

• TEST:STATe?

• TEST:VALue

• TEST:VALue?




13 SCPI Error Messages

13-1

NOTE

SCPI Error Messages

SCPI Error Messages

SCPI Error Messages

This chapter contains the same error message information that can be found in the SCPI 1994 Volume 2: Command Reference. There are four sections in this chapter:

•

“Command Errors” on page 13-3

•

“Execution Errors” on page 13-8

•

“Device-Specific Errors” on page 13-15

•

“Query Errors” on page 13-17

Your analyzer does not use all of the error messages listed in this chapter.


SCPI Error Messages

Command Errors

Command Errors

An error/event number in the range

−

199 to

−

100 indicates that an IEEE

488.2 syntax error has been detected by the instrument's parser. The occurrence of any error in this class shall cause the command error bit

(bit 5) in the event status register (IEEE 488.2, section 11.5.1) to be set.

One of the following events has occurred:

• An IEEE 488.2 syntax error has been detected by the parser. That is, a controller-to-device message was received which is in violation of the IEEE 488.2 standard. Possible violations include a data element which violates the device listening formats or whose type is unacceptable to the device.

• An unrecognized header was received. Unrecognized headers include incorrect device-specific headers and incorrect or unimplemented

IEEE 488.2 common commands.

• A Group Execute Trigger (GET) was entered into the input buffer inside of an IEEE 488.2 program message.

Events that generate command errors shall not generate execution errors, device-specific errors, or query errors; see the other error definitions in this chapter.


SCPI Error Messages

Command Errors

Table 13-1

Error

Number

−

100

−

−

−

−

−

−

−

−

−

101

102

103

104

105

108

109

110

111

SCPI Command Errors

Error Description

Command error — This is the generic syntax error for devices that cannot detect more specific errors. This code indicates only that a Command Error has occurred.

Invalid character — A syntactic element contains a character which is invalid for that type; for example, a header containing an ampersand,

SETUP&. This error might be used in place of errors

−

114,

−

121,

−

141, and perhaps some others.

Syntax error — An unrecognized command or data type was encountered; for example, a string was received when the device does not accept strings.

Invalid separator — The parser was expecting a separator and encountered an illegal character; for example, the semicolon was omitted after a program message unit, *EMC 1:CH1:VOLTS 5.

Data type error — The parser recognized a data element different than one allowed; for example, numeric or string data was expected but block data was encountered.

GET not allowed — A Group Execute Trigger was received within a program message.

Parameter not allowed — More parameters were received than expected for the header; for example, the *EMC common command only accepts one parameter, so receiving *EMC 0,1 is not allowed.

Missing parameter — Fewer parameters were received than required for the header; for example, the *EMC common command requires one parameter, so receiving *EMC is not allowed.

Command header error — An error was detected in the header. This error message should be used when the device cannot detect the more specific errors described for errors

−

111 through

−

119.

Header separator error — A character which is not a legal header separator was encountered while parsing the header; for example, no white space followed the header, thus *GMC"MACRO" is an error.


SCPI Error Messages

Command Errors

−

131

−

134

−

138

−

140

−

123

−

124

−

128

−

130

Error

Number

−

112

−

113

−

114

−

120

−

121


Program mnemonic too long — The header contains more that twelve characters.

Undefined header — The header is syntactically correct, but it is undefined for this specific device; for example, *XYZ is not defined for any device.

Header suffix out of range — The value of a numeric suffix attached to a program mnemonic makes the header invalid.

Numeric data error — This error, as well as errors

−

121 through

−

129, are generated when parsing a data element which appears to be numeric, including the nondecimal numeric types. This particular error message should be used if the device cannot detect a more specific error.

Invalid character in number — An invalid character for the data type being parsed was encountered; for example, an alpha in a decimal numeric or a

"9" in octal data.

Exponent too large — The magnitude of the exponent was larger than

32000.

Too many digits — The mantissa of a decimal numeric data element contained more than 255 digits excluding leading zeros.

Numeric data not allowed — A legal numeric data element was received, but the device does not accept one in this position for the header.

Suffix error — This error, as well as errors

−

131 through

−

139, are generated when parsing a suffix. This particular error message should be used if the device cannot detect a more specific error.

Invalid suffix — The suffix does not follow the correct syntax, or the suffix is inappropriate for this device.

Suffix too long — The suffix contained more than 12 characters.

Suffix not allowed — A suffix was encountered after a numeric element which does not allow suffixes.

Character data error — This error, as well as errors

−

141 through

−

149, are generated when parsing a character data element. This particular error message should be used if the device cannot detect a more specific error.


SCPI Error Messages

Command Errors

−

144

−

148

−

150

Error

Number

−

141

−

−

−

−

−

−

−

−

151

158

160

161

168

170

171

178


Invalid character data — Either the character data element contains an invalid character or the particular element received is not valid for the header.

Character data too long — The character data element contains more than twelve characters.

Character data not allowed — A legal character data element was encountered where prohibited by the device.

String data error — This error, as well as errors

−

151 through

−

159, are generated when parsing a string data element. This particular error message should be used if the device cannot detect a more specific error.

Invalid string data — A string data element was expected, but was invalid for some reason. For example, an END message was received before the terminal quote character.

String data not allowed — A string data element was encountered but was not allowed by the device at this point in parsing.

Block data error — This error, as well as errors

−

161 through

−

169, are generated when parsing a block data element. This particular error message should be used if the device cannot detect a more specific error.

Invalid block data — A block data element was expected, but was invalid for some reason. For example, an END message was received before the length was satisfied.

Block data not allowed — A legal block data element was encountered but was not allowed by the device at this point in parsing.

Expression error — This error, as well as errors

−

171 through

−

179, are generated when parsing an expression data element. This particular error message should be used if the device cannot detect a more specific error.

Invalid expression — The expression data element was invalid (for example, unmatched parentheses or an illegal character).

Expression data not allowed — A legal expression data was encountered but was not allowed by the device at this point in parsing.


SCPI Error Messages

Command Errors

−

181

−

183

−

184

Error

Number

−

180


Macro error — This error, as well as errors

−

181 through

−

189, are generated when defining or executing a macro. This particular error message should be used if the device cannot detect a more specific error.

Invalid outside macro definition — Indicates that a macro parameter placeholder ($<number) was encountered outside of a macro definition.

Invalid inside macro definition — Indicates that the program message unit sequence, sent with a *DDT or *DMC command, is syntactically invalid.

Macro parameter error — Indicates that a command inside the macro definition had the wrong number or type of parameters.


SCPI Error Messages

Execution Errors



−

299 to

−

200 indicates that an error has been detected by the instrument's execution control block. The occurrence of any error in this class shall cause the execution error bit

(bit 4) in the event status register to be set. One of the following events has occurred:

• A program data element following a header was evaluated by the device as outside of its legal input range or is otherwise inconsistent with the device's capabilities.

• A valid program message could not be properly executed due to some device condition.

Execution errors shall be reported by the device after rounding and expression evaluation operations have taken place. Rounding a numeric data element, for example, shall not be reported as an execution error.

Events that generate execution errors shall not generate Command

Errors, device-specific errors, or Query Errors; see the other error definitions in this section.


SCPI Error Messages


Table 13-2

Error

Number

−

200

−

−

−

−

−

−

−

−

−

201

202

203

210

211

212

213

214

215s

SCPI Execution Errors


Execution error — This is the generic syntax error for devices that cannot detect more specific errors. This code indicates only that an Execution Error has occurred.

Invalid while in local — Indicates that a command is not executable while the device is in local due to a hard local control; for example, a device with a rotary switch receives a message which would change the switches state, but the device is in local so the message can not be executed.

Settings lost due to rtl — Indicates that a setting associated with a hard local control was lost when the device changed to LOCS from REMS or to

LWLS from RWLS.

Command protected — Indicates that a legal password-protected program command or query could not be executed because the command was disabled.

Trigger error

Trigger ignored — Indicates that a GET , *TRG , or triggering signal was received and recognized by the device but was ignored because of device timing considerations; for example, the device was not ready to respond.

1

Arm ignored — Indicates that an arming signal was received and recognized by the device but was ignored.

Init ignored — Indicates that a request for a measurement initiation was ignored as another measurement was already in progress.

Trigger deadlock — Indicates that the trigger source for the initiation of a measurement is set to GET and subsequent measurement query is received.

The measurement cannot be started until a GET is received, but the GET would cause an INTERRUPTED error.

Arm deadlock — Indicates that the arm source for the initiation of a measurement is set to GET and subsequent measurement query is received.

The measurement cannot be started until a GET is received, but the GET would cause an INTERRUPTED error.


SCPI Error Messages


−

224

−

225

−

226

−

230

−

231

−

232

Error

Number

−

220

−

−

−

−

221

222

223

233


Parameter error — Indicates that a program data element related error occurred. This error message should be used when the device cannot detect the more specific errors

−

221 through

−

229.

Settings conflict — Indicates that a legal program data element was parsed but could not be executed due to the current device state.

Data out of range — Indicates that a legal program data element was parsed but could not be executed because the interpreted value was outside the legal range as defined by the device.

Too much data — Indicates that a legal program data element of block, expression, or string type was received that contained more data than the device could handle due to memory or related device-specific requirements.

Illegal parameter value — Used where an exact value, from a list of possible values, was expected.

Out of memory — The device has insufficient memory to perform the requested operation.

Lists not same length — Attempted to use LIST structure having individual LIST's of unequal lengths.

Data corrupt or stale — Possibly invalid data; new reading started but not completed since last access.

Data questionable — Indicates that measurement accuracy is suspect.

Invalid format — Indicates that a legal program data element was parsed but could not be executed because the data format or structure is inappropriate, such as when loading memory tables or when sending a

SYSTem:SET parameter from an unknown instrument.

Invalid version — Indicates that a legal program data element was parsed but could not be executed because the version of the data is incorrect to the device. This particular error should be used when file or block data formats are recognized by the instrument but cannot be executed for reasons of version incompatibility. For example, an unsupported file version, or an unsupported instrument version.


SCPI Error Messages


Error

Number

−

240

−

−

−

−

−

−

−

−

241

250

251

252

253

254

255

256


Hardware error — Indicates that a legal program command or query could not be executed because of a hardware problem in the device. Definition of what constitutes a hardware problem is completely device-specific. This error message should be used when the device cannot detect the more specific errors described for errors

−

241 through

−

249.

Hardware missing — Indicates that a legal program command or query could not be executed because of missing device hardware; for example, an option was not installed. Definition of what constitutes missing hardware is completely device-specific.

Mass storage error — Indicates that a mass storage error occurred. This error message should be used when the device cannot detect the more specific errors described for errors

−

251 through

−

259.

Missing mass storage — Indicates that a legal program command or query could not be executed because of missing mass storage; for example, an option that was not installed. Definition of what constitutes missing massstorage is device-specific.

Missing media — Indicates that a legal program command or query could not be executed because of a missing media; for example, no disk. The definition of what constitutes missing media is device-specific.

Corrupt media — Indicates that a legal program command or query could not be executed because of corrupt media; for example, bad disk or wrong format. The definition of what constitutes corrupt media is device-specific.

Media full — Indicates that a legal program command or query could not be executed because the media was full; for example, there is no room on the disk. The definition of what constitutes a full media is device-specific.

Directory full — Indicates that a legal program command or query could not be executed because the media directory was full. The definition of what constitutes a full media directory is device-specific.

File name not found — Indicates that a legal program command or query could not be executed because the file name on the device media was not found; for example, an attempt was made to read or copy a nonexistent file.

The definition of what constitutes a file not being found is device-specific.


SCPI Error Messages


Error

Number

−

257

−

−

−

−

−

−

−

−

258

260

261

270

271

272

273

274


File name error — Indicates that a legal program command or query could not be executed because the file name on the device media was in error; for example, an attempt was made to copy to a duplicate file name. The definition of what constitutes a file name error is device-specific.

Media protected — Indicates that a legal program command or query could not be executed because the media was protected; for example, the write-protect tab on a disk was present. The definition of what constitutes protected media is device-specific.

Expression error — Indicates that an expression program data element related error occurred. This error message should be used when the device cannot detect the more specific errors described for errors

−

261 through

−

269.

Math error in expression — Indicates that a syntactically legal expression program data element could not be executed due to a math error; for example, a divide-by-zero was attempted. The definition of math error is device-specific.

Macro error — Indicates that a macro-related execution error occurred.

This error message should be used when the device cannot detect the more specific errors

−

271 through

−

279.

Macro syntax error — Indicates that a syntactically legal macro program data sequence could not be executed due to a syntax error within the macro definition.

Macro execution error — Indicates that a syntactically legal macro program data sequence could not be executed due to some error in the macro definition.

Illegal macro label — Indicates that the macro label defined in the *DMC command was a legal string syntax, but could not be accepted by the device; for example, the label was too long, the same as a common command header, or contained invalid header syntax.

Macro parameter error — Indicates that the macro definition improperly used a macro parameter placeholder.


SCPI Error Messages


Error

Number

−

275

−

−

−

−

−

−

−

−

−

−

276

277

278

280

281

282

283

284

285

286


Macro definition too long — Indicates that a syntactically legal macro program data sequence could not be executed because the string or block contents were too long for the device to handle.

Macro recursion error — Indicates that a syntactically legal macro program data sequence could not be executed because the device found it to be recursive.

Macro redefinition not allowed — Indicates that a syntactically legal macro label in the *DMC command could not be executed because the macro label was already defined.

Macro header not found — Indicates that a syntactically legal macro label in the *GMC?

query could not be executed because the header was not previously defined.

Program error — Indicates that a downloaded program-related execution error occurred. This error message should be used when the device cannot detect the more specific errors

−

281 through

−

289. A downloaded program is used to add algorithmic capability to a device. The syntax used in the program and the mechanism for downloading a program is device-specific.

Cannot create program — Indicates that an attempt to create a program was unsuccessful. One reason for failure might include not enough memory.

Illegal program name — The name used to reference a program was invalid; for example, redefining an existing program, deleting a nonexistent program, or in general, referencing a nonexistent program.

Illegal variable name — An attempt was made to reference a nonexistent variable in a program.

Program currently running — Certain operations dealing with programs may be illegal while the program is running; for example, deleting a running program might not be possible.

Program syntax error — Indicates that a syntax error appears in a downloaded program. The syntax used when parsing the downloaded program is device-specific.

Program runtime error


SCPI Error Messages


Error

Number

−

290


Memory use error — Indicates that a user request has directly or indirectly caused an error related to memory or data_handles (this is not the same as

"bad" memory).

−

291

−

292

−

293

−

294

Out of memory

Referenced name does not exist

Referenced name already exists

Incompatible type — Indicates that the type or structure of a memory item is inadequate.

1. A DT0 device always ignores GET and treats *TRG as a Command Error.


SCPI Error Messages

Device-Specific Errors



−

399 to

−

300 or 1 to 32767 indicates that the instrument has detected an error which is not a command error, a query error, or an execution error. It indicates that some device operations did not properly complete, possibly due to an abnormal hardware or firmware condition. These codes are also used for self-test response errors. The occurrence of any error in this class should cause the device-specific error bit (bit 3) in the event status register to be set.

The meaning of positive error codes is device-dependent and may be enumerated or bit mapped; the error message string for positive error codes is not defined by SCPI and available to the device designer. Note that the string is not optional; if the designer does not wish to implement a string for a particular error, the null string should be sent (for example,

42). The occurrence of any error in this class should cause the device-specific error bit (bit 3) in the event status register to be set.

Events that generate device-specific errors shall not generate command errors, execution errors, or query errors; see the other error definitions in this section.


SCPI Error Messages


−

310

−

311

−

312

−

313

−

314

−

315

Table 13-3

Error

Number

−

300

−

−

−

−

−

−

330

350

360

361

362

363

SCPI Device-Specific Errors


Device-specific error — This is the generic device-dependent error for devices that cannot detect more specific errors. This code indicates only that a Device-Dependent Error has occurred.

System error — Indicates that some error, termed "system error" by the device, has occurred. This code is device-dependent.

Memory error — Indicates that an error was detected in the device's memory. The scope of this error is device-dependent.

PUD memory lost — Indicates that the protected user data saved by the

*PUD command has been lost.

Calibration memory lost — Indicates that nonvolatile calibration data used by the *CAL?

command has been lost.

Save/recall memory lost — Indicates that the nonvolatile data saved by the

*SAV?

command has been lost.

Configuration memory lost — Indicates that nonvolatile configuration data saved by the device has been lost. The meaning of this error is device-specific.

Self-test failed.

Queue overflow — A specific code entered into the queue in lieu of the code that caused the error. This code indicates that there is no room in the queue and an error occurred but was not recorded.

Communication error — This is the generic communication error for devices that cannot detect the more specific errors

−

361 through

−

363.

Parity error in program message — Parity bit not correct when data received, for example, on a serial port.

Framing error in program message — A stop bit was not detected when data was received, for example, on a serial port (for example, a baud rate mismatch).

Input buffer overrun — Software or hardware input buffer on serial port overflows with data caused by improper or nonexistent pacing.


SCPI Error Messages

Query Errors

Query Errors


−

499 to

−

400 indicates that the output queue control of the instrument has detected a problem with the message exchange protocol. The occurrence of any error in this class shall cause the query error bit (bit 2) in the event status register to be set. These errors correspond to message exchange protocol errors. One of the following is true:

• An attempt is being made to read data from the output queue when no output is either present or pending;

• Data in the output queue has been lost.

Events that generate query errors shall not generate command errors, execution errors, or device-specific errors; see the other error definitions in this section.


SCPI Error Messages

Query Errors

Table 13-4

Error

Number

−

400

−

−

−

−

410

420

430

440

SCPI Query Errors


Query error — This is the generic query error for devices that cannot detect more specific errors. This code indicates only that a Query Error has occurred.

Query INTERRUPTED — Indicates that a condition causing an

INTERRUPTED Query error occurred; for example, a query followed by DAB or GET before a response was completely sent.

Query UNTERMINATED — Indicates that a condition causing an

UNTERMINATED Query error occurred; for example, the device was addressed to talk and an incomplete program message was received.

Query DEADLOCKED — Indicates that a condition causing a DEADLOCKED

Query error occurred; for example, both input buffer and output buffer are full and the device cannot continue.

Query UNTERMINATED after indefinite response — Indicates that a query was received in the same program message after an query requesting an indefinite response was executed.


Index

Symbols

*CLS

,

2-7

,

5-4

,

9-16

,

12-3

*ESE

,

5-22

,

9-16

,

12-3

*ESE?

,

5-22

,

9-16

,

12-3

*ESR?

,

5-22

,

9-16

,

12-3

*IDN?

,

9-16

,

12-3

*LRN?

,

9-16

,

11-64

,

12-3

*OPC

,

2-6

,

5-21

,

9-16

,

9-17

,

9-

,

12-3

18

required use of

,

6-11

*OPC?

,

2-6

,

2-8

,

6-11

,

9-17

,

12-3

*OPT?

,

9-17

,

12-3

*PCB

,

1-13

,

9-17

,

12-3

*PSC

,

9-17

,

12-3

*RST

,

2-7

,

5-4

,

9-17

,

9-18

,

12-3

*SRE

,

5-14

,

9-17

,

9-18

,

12-3

*SRE?

,

5-14

,

9-18

,

12-3

*STB

,

5-9

*STB?

,

5-14

,

9-18

,

12-3

*TRG

,

9-18

,

12-3

*TST?

,

9-18

,

12-3

*WAI

,

2-6

,

2-8

,

6-11

,

9-18

,

12-3

, separating command and data

,

9-15

: separating a series of mnemonics

,

9-15

; separating commands

,

9-15

<block>

,

9-13

<char>

,

9-11

<num>

,

9-10

<ON|OFF>

,

9-12

<string>

,

9-13

[ ] enclosing implied or optional parameters

,

9-14

Numerics

CH

,

6-22

,

6-23

87075C

,

9-4

,

11-12

,

11-14

,

11-37

8712ET/ES

,

12-10

8714ET/ES

,

12-10

A abbreviation of commands

ABORt

,

9-8

,

9-4

,

9-5

,

11-4

absolute value set marker

,

11-11

ACKNOWLEDGE

,

11-18

active controller

,

1-9

defined

,

1-2

active IBASIC program selecting

,

11-36

active marker annotation enable/disable

,

11-21

address

GPIB

,

1-2

pass-control-back

,

9-17

address capability

,

1-7

AGC

See automatic gain control

AH1

,

1-8

allocate memory

,

11-35

,

11-36

for IBASIC programs

,

11-35

alternate sweep mode enable/disable

AMPLifier

,

,

11-13

11-47

amplitude marker query

,

11-11

ANNotation

,

11-22

annotation calibration

,

11-38

ANSI X3.4-1977

,

4-7

Any

,

5-15

aperture group delay arm deadlock

,

11-5

,

13-9

arm ignored

,

13-9

arrays data, corrected

,

6-25

formatted

,

6-26

measurement

,

6-21

memory, corrected

,

6-25

raw data

,

6-21

ASCII

,

1-4

,

6-3

characters ,

4-3

data format ,

11-33

encoding ,

4-7

ASCii ,

4-6

ASCII,3 (number format) ,

6-8

ASCII,5 (number format) ,

6-8

ATN ,

1-5 ,

1-10

attention control line ,

1-5

auto z ,

11-52

automatic gain control enable/disable ,

11-30

autozero detector ,

11-12

AVERage ,

11-43

averaging ,

6-25

averaging status ,

5-10

averaging status register set ,

5-

23

AVG hardkey ,

10-9

B bandwidth notch ,

11-10

receiver IF ,

11-38

BBANd ,

11-13

BEEPer ,

11-59

BEGIN hardkey (ES) ,

10-13

BEGIN hardkey (ET) ,

10-10

BEGIN key ,

11-23

BFWD ,

6-22

binary data encoding ,

6-6 ,

6-17

binary encoding ,

1-4 ,

4-7 ,

6-20

binary parameters ,

11-6 ,

11-7 ,

11-8 ,

11-9 ,

11-10

,

11-12

BLOCK ,

11-3

block length ,

4-4 ,

4-5 ,

6-6 ,

6-20

parameters ,

9-13

block data ,

4-4

block data error ,

13-6

block data not allowed ,

13-6

block header

Programmer’s Guide Index-1

Index calculating length ,

6-20

block length definite ,

4-4

indefinite ,

4-5

block parameters ,

9-13

blocks definite and indefinite length ,

4-4 ,

4-5

,

9-13

definite length ,

9-13

boolean parameters ,

9-12

brackets ,

11-4

use of in this manual ,

1-2 ,

9-

14

,

11-4

branching ,

9-5

brightness monitor ,

11-22

buffer graphics ,

7-6

buffering user graphics ,

11-24

bus data ,

1-4

bus management commands ,

1-6

BUSY ,

11-18

byte order ,

6-7 ,

11-27

reversed ,

4-7

byte swapping ,

4-7

bytes per point, during data transfer ,

6-8

C c programming language ,

6-5

,

6-

7

C_DIRECTivity ,

11-16

C_ISOLATION ,

11-16

C_LDMATCH ,

11-16

C_RTRACKING ,

11-16

C_SRCMATCH ,

11-16

C_TTRACKING ,

11-16

C1 ,

1-8

C12 ,

1-8

C2 ,

1-8

C3 ,

1-8

C4 ,

1-8

C8 ,

1-8

CABLe ,

11-13

cable fault location center distance ,

11-47

CENTer or LOWPass mode ,

11-48

frequency span selection ,

11-

48

start distance ,

11-47

stop distance ,

11-47

cable impedance ,

11-52

cable length measuring ,

11-46

specifying ,

11-45

units ,

11-47

cable loss ,

11-45

cable scan starting cables ,

1-2

,

11-52

cal check ,

11-16

CAL hardkey (ES) ,

10-16

CAL hardkey (ET) ,

10-19 ,

10-20 ,

10-21

CALC:MARK ,

6-13

CALC1:DATA?

,

6-12

CALCulate ,

9-4 ,

11-5 –

11-11

CALibration ,

9-4 ,

11-12

calibration correction factors ,

6-16

finding current type ,

11-44

full band ,

11-44

instrument state measuring a load

,

11-43

,

11-44

measuring a short ,

11-43

measuring a standard reflection ,

11-44

transmission ,

11-44

measuring a thru ,

11-44

measuring an open ,

11-43

restoring factory defaults ,

11-

44

saving ,

11-44

selecting the number of ports ,

11-44

standard ,

11-42

calibration annotation ,

11-38

calibration choice querying ,

11-41

setting ,

11-41

calibration kit port selection ,

11-42

selecting ,

11-42

calibration standard selecting ,

11-42

cannot create program ,

13-13

capacitance compensating ,

11-38

case-sensitivity ,

9-8

CATalog ,

11-35

,

11-36

Cent_acknowledge ,

11-19

Cent_busy ,

11-19

Cent_on_line ,

11-19

Cent_out_of_paper ,

11-19

Cent_printer_err ,

11-19

CENTer cable fault location mode ,

11-

48

center distance cable fault location center frequency

,

11-47

,

11-47

Centronics port ,

11-18

CH[1|2]AFWD ,

6-22

CH1AFWD ,

6-22

CH1BFWD ,

6-22

CH1RFWD ,

6-22

CH1SCORR1 ,

6-23

CH1SCORR2 ,

6-23

CH1SCORR3 ,

6-23

CH1SCORR4 ,

6-23

CH2AFWD ,

6-22

CH2BFWD ,

6-22

CH2RFWD ,

6-22

CH2SCORR1 ,

6-23

CH2SCORR2 ,

6-23

CH2SCORR3 ,

6-23

Index-2 Programmer’s Guide

Index

CH2SCORR4 ,

6-23

change directory ,

11-31

channel annotation enable user-defined ,

11-20

enable/disable ,

11-20

,

11-29

channel annotation text ,

11-20

channel on/off ,

11-52

CHAR ,

11-3

char.

See <char>.

character data ,

4-3

error ,

13-5

not allowed ,

13-6

too long ,

13-6

character parameters ,

9-11

circle drawing ,

11-24

clear graphics ,

11-24

clear status command ,

5-4

clearing registers ,

5-4

clock date display format ,

11-20

date format ,

11-20

display position ,

11-20

seconds display ,

11-20

clock lines printing enable/disable ,

11-29

colons use of ,

9-5

,

9-15

color map

VGA monitor ,

11-23

color of pen ,

11-24

color scheme external monitor ,

11-23

command error ,

13-3

,

13-4

execute IBASIC command ,

11-

35

header error protected

,

13-4

,

13-9

command abbreviation ,

9-8

command error ,

5-22

command parser ,

1-15 ,

9-7

command reference

SCPI ,

11-4

command sending ,

1-6

command tree ,

9-3

commands

ABORt ,

11-4

bus management ,

1-6

CALC:MARK ,

6-13

CALC1:DATA?

,

6-12

CALCulate ,

11-5 –

11-11

CALibration ,

11-12

clear status ,

5-4

CONFigure ,

11-13

CONTrol device

,

11-14

,

1-6

DIAGnostic ,

11-14 –

11-17

DISPlay echo

,

11-20 –

11-26

,

11-59

FORMat

DATA ,

4-6

IEEE 488.2

INITiate

,

9-16

,

11-30

INPut ,

11-30

long form ,

9-8

MMEMory ,

11-31 –

11-33

order of completion example

8 ,

2-9

OUTPut ,

11-34

overlapped ,

2-3 ,

9-17 ,

9-18

overlapped, defined ,

2-2

PROGram

ROUTe

,

11-35 –

11-36

,

11-37

SCPI standard ,

12-3

SENSe ,

11-38 –

11-51

,

2-2

sequential sequential, defined ,

2-2

short form ,

9-8

STATus:PRESet

SYSTem:PRESet

,

5-25

,

5-4

,

2-

commas use of ,

9-10 ,

9-15

common commands, IEEE 488.2

,

11-1

compensating capacitance ,

11-

38

condition register ,

5-3

,

5-4

CONFigure ,

9-4

,

11-13

connector corrections ,

11-46

connector length ,

11-45

Connector Length key ,

11-46

connector verification ,

11-51

CONTrol ,

9-4 ,

11-14

control passing ,

3-2

control lines ,

1-2

,

1-4 ,

1-5

controller ,

1-2

active ,

1-9

active, defined ,

1-2

defined external

,

1-2

,

3-2

multiple ,

1-7

system, defined ,

1-2

controller capabilities ,

1-9

conventions ,

1-3

,

11-4

commands in menu map ,

10-2

copy file ,

11-31 ,

11-33

corrected data array ,

6-25 ,

6-26

corrected memory array ,

6-15

,

6-

16 ,

6-26

corrected memory arrays ,

6-25

CORRection ,

11-38

,

11-42

,

11-

43

correction multi-peak enable/disable ,

11-46

correction constants flash memory query ,

11-14

load from floppy disk ,

11-14

store to flash memory ,

11-14

store to floppy disk correction factor

,

11-14

,

6-16

corrections connector ,

11-46

corrupt media ,

13-11

CSPAN (center/span) ,

11-20


Index

D

DATA

,

11-67

,

11-68

data block

,

4-4

character

,

4-3

corrupt or stale encoding

,

4-6

expression flow

,

9-3

,

4-4

,

13-10

format

,

11-27

numeric

,

4-3

out of range

,

13-10

post-processing

,

6-19

questionable rate

,

1-7

raw

,

6-21

string

,

4-4

,

5-19

,

13-10

types

,

4-2

,

4-3

data arrays

,

9-5

corrected

,

6-25

mnemonics raw

,

6-21

data bus

,

1-4

,

6-22

data points specifying number

,

11-53

data processing how to perform

,

6-18

data trace

,

4-4

enable/disable storage

,

11-32

data transfer

,

4-2

size

,

6-8

data type error

,

13-4

data types

,

4-3

date format clock display

,

11-20

DC1

,

1-8

DCL

,

1-10

,

1-12

,

1-15

definite length blocks

,

4-4

,

9-13

delay

,

11-44

electrical

,

6-26

delete active IBASIC program all IBASIC programs

,

11-35

,

11-35

directory ,

11-32

file ,

11-31

delete program ,

11-35

,

11-36

delimiter ,

4-4 ,

9-13

delimiters ,

9-13

delta frequency ,

11-6

detection mode selecting ,

11-47

detector, broadband ,

9-4

device clear ,

1-10 ,

1-12

commands ,

1-6

dependent error ,

5-21

reset ,

9-18

status ,

5-10

device clear ,

1-10 ,

1-12

device status register set ,

5-15

summary ,

5-13

device-specific errors ,

13-15

DIAGnostic ,

9-4 ,

11-14 –

11-17

directory create new directory ,

11-31

deleting ,

11-32

directory full ,

13-11

direct-read method of accessing registers ,

5-6

disable active marker annotation ,

11-

21

alternate sweep mode automatic gain control

,

11-47

,

11-30

automatic sweep time ,

11-53

channel annotation ,

11-20 ,

11-

29

data trace storage ,

11-32

expand measurement mode ,

11-23

fast recall mode form feed ,

11-29

,

11-23

frequency annotation ,

11-20 ,

11-29

limit test pass/fail icon ,

11-21

limit test pass/fail text ,

11-21

marker ,

11-10

message window ,

11-22

multi-peak error correction ,

11-46

printing clock lines ,

11-29

graticule ,

11-29

marker symbols ,

11-29

trace data ,

11-29

source power ,

11-34

storage of error correction values ,

11-32

storage of instrument state , title

11-32

,

11-22

trace averaging ,

11-38

y-axis labels ,

11-22

discrete parameters disk catalog ,

11-31

,

9-11

DISPlay ,

9-4 ,

11-20 –

11-26

display clock position ,

11-20

display format ,

11-5

display frequency resolution ,

11-

20

DISPLAY hardkey (ES/ET) ,

10-

31

display units linear ,

11-5

log ,

11-5

Display User List key ,

11-60

display window pixel coordinates ,

11-24

width and height ,

11-24

double quotes use of ,

9-13

download

IBASIC program ,

11-35

,

11-36

downloading data traces ,

6-20

draw circle ,

11-24


Index line ,

11-24

rectangle ,

11-24

E

E2 ,

1-8

echo GPIB commands ,

11-59

electrical delay ,

6-26 ,

11-44

enable active marker annotation ,

11-

21

alternate sweep mode automatic gain control

,

11-47

,

11-30

automatic sweep time ,

11-53

channel annotation ,

11-20 ,

11-

29

data trace storage ,

11-32

expand measurement mode ,

11-23

fast recall mode form feed ,

11-29

,

11-23


11-20 ,

11-29

limit test pass/fail icon limit test pass/fail text marker ,

11-10

message window ,

11-22

,

11-21

,

11-21

multi-peak error correction ,

11-46

port extension ,

11-45

printing clock lines ,

11-29

graticule ,

11-29

marker symbols ,

11-29

trace data ,

11-29

source power ,

11-34

storage of error correction values ,

11-32

storage of instrument state , title

11-32

,

11-22

trace averaging ,

11-38

user-defined channel annotation ,

11-20

y-axis labels ,

11-22

enable register ,

5-3 ,

5-5

encoding binary ,

6-6 ,

6-20

data ,

4-2 ,

4-6

format ,

6-3

END ,

1-14 ,

1-15 ,

1-16

end or identify control line ,

1-5

entering frequency values power values

,

10-5

,

10-7

text ,

10-8

time values ,

10-6

voltage values ,

10-7

entering values ,

10-3

EOI ,

1-5

,

1-14

,

6-20

EPSon ,

11-28

error command ,

5-22 ,

13-3 ,

13-4

device dependent ,

5-21

device-specific execution

,

13-15

,

5-22 ,

13-8

invalid character ,

13-4

query ,

5-21 ,

13-17

semantic ,

5-22

syntax ,

13-3

error bit ,

13-3

error coefficient arrays ,

6-15 ,

6-

22 ,

6-23

error correction ,

6-22 ,

11-16

one port reflection ,

11-46

transmission ,

11-46

two port ,

11-46

error correction values enable/disable storage ,

11-32

error messages ,

11-63 ,

13-2

error queue ,

1-14

querying ,

11-63

event register ,

5-4

event reporting ,

5-5

example menu map ,

10-3

execute IBASIC command ,

11-35

execution control block ,

13-8

error ,

5-22

,

13-8

,

13-9

error bit ,

13-8

expand measurement mode enable/disable ,

11-23

exponent too large ,

13-5

expression data ,

4-4

not allowed ,

13-6

expression error ,

13-6 ,

13-12

external controller ,

3-2

external monitor ,

11-23

color scheme ,

11-23

external VGA monitor ,

11-23

F fast Fourier transform ,

6-26

fast recall mode enable/disable ,

11-23

fault location ,

6-26

fault location, power ratio ,

11-49

FFT ,

6-26

file copying ,

11-31 ,

11-33

deleting ,

11-31

name error ,

13-12

name not found ,

13-11

return file information ,

11-31

files list in memory , 11-31

FILTer ,

11-13

firmware status ,

5-4

flag

NPO ,

2-6

power-on status clear ,

9-17

flash memory correction constants flatness ,

11-6

font

,

11-14


Index label ,

11-24

FORM column ,

11-3

form feed enable/disable

FORMat

,

11-29

,

9-4 ,

11-27

DATA command ,

4-6

format disk format ,

11-31

screen ,

11-23

FORMAT hardkey (ES/ET) ,

10-

36

format of numerics ,

9-11

formatted arrays ,

6-26

formatted data array ,

6-3

querying ,

6-14

formatting ,

6-26

FREQ hardkey (ES/ET) ,

10-37

FREQuency ,

11-47

frequency ,

11-21

center for RF source ,

11-47


11-20

enable/disable ,

11-20

,

11-29

start value ,

11-21

stop frequency ,

11-21

user defined suffix ,

11-21

frequency span

RF source ,

11-48

selection for cable fault location measurements ,

11-48

frequency values entering ,

10-5

storing to a file ,

11-33

frequency, stop how to set ,

9-10

front panel controlling with SCPI ,

8-2

front panel keycodes ,

8-2

function query ,

11-48

G gain correction ,

6-15

general status register ,

5-3

model ,

5-3

GET (group execute trigger) ,

13-

3

get not allowed ,

13-4

go to local ,

1-10

GPIB address ,

1-2

,

1-7

cables ,

1-2

controllers ,

1-7

maximum cable length ,

1-7

maximum data rate ,

1-7

maximum number of devices ,

1-7

message scheme ,

1-7

physical interface ,

1-2

programming ,

1-2

queues ,

1-14

requirements

GPIB address

,

1-7

,

1-2

GPIB echo command ,

11-59

graph printing

GRAPhics

,

11-28

,

11-24

graphics buffering ,

11-24

clearing ,

11-24

plotting or printing ,

7-6

refreshing ,

7-6

user ,

7-2

graphics buffer ,

7-6

graphics commands ,

7-2

graphics plane ,

7-2

graphics window origin ,

7-5

size ,

7-4

graticule printing enable/disable ,

11-29

group delay aperture ,

11-5

power ratio ,

11-50

group execute trigger (GET) ,

13-

3

GTL ,

1-10

H handshake ,

1-4

handshake lines ,

1-4

hardcopy ,

11-18

initiate ,

11-29

left margin ,

11-28

page orientation ,

11-28

print width ,

11-28

resolution ,

11-29

set port ,

11-28

start ,

11-29

top margin ,

11-28

HARDCOPY hardkey (ES/ET) ,

10-38

hardkey

AVG ,

10-9

BEGIN (ES) ,

10-13

BEGIN (ET) ,

10-10

CAL (ES) ,

10-16

CAL (ET) ,

10-19 ,

10-20 ,

10-21

DISPLAY (ES/ET) ,

10-31

FORMAT (ES/ET) ,

10-36

FREQ (ES/ET) ,

10-37

HARDCOPY (ES/ET) ,

10-38

MARKER (ES/ET) ,

10-42

MEAS1/MEAS2 (ES) ,

10-45

MEAS1/MEAS2 (ET) ,

10-47

MENU (ES/ET) ,

10-50

,

10-51

POWER (ES/ET) ,

10-52

SAVE RECALL (ES/ET) ,

10-55

SCALE (ES/ET)

SWEEP (ES/ET)

,

10-60

,

10-61

SYSTEM OPTIONS (ES/ET) ,

10-62

Test Set Cal ,

10-30

hardware error ,

13-11

hardware missing ,

13-11

hardware status ,

5-4

HCOPy ,

9-4 ,

11-28 ,

11-29

header ,

6-8


Index separator error ,

13-4

suffix out of range ,

13-5

unrecognized ,

13-3

HPGL ,

11-28

hue ,

11-23

I

I/O ports ,

11-17

I_DIRECTivity ,

11-16

I_LDMATCH ,

11-16

I_RESPONSE ,

11-16

I_SRCMATCH ,

11-16

I_TRACKING ,

11-16

IBASIC program deleting ,

11-35 ,

11-36

downloading ,

11-35 ,

11-36

loading a value ,

11-35

,

11-36

selecting ,

11-35 ,

11-36

starting and stopping ,

11-36

IBM ,

11-28

identifying analyzer options ,

9-

17

identifying the analyzer ,

9-16

IDN?

. See *IDN?

IEEE 32-bitFloating Point ,

6-8

IEEE 488.1

,

1-2 ,

1-8

,

1-10

IEEE 488.2

,

1-2 ,

2-2

,

5-22

,

9-2 ,

9-16 ,

12-3 ,

13-3

IEEE 488.2 common commands ,

9-16 ,

11-1

IEEE 64-bitFloating Point ,

6-8

IEEE 728-1982 ,

9-2

IEEE 754-1985 ,

4-7

IEEE floating point numbers ,

6-

IFC

7

,

1-5 ,

1-11

illegal macro label ,

13-12

parameter value ,

13-10

program name ,

13-13

variable name ,

13-13

impedance cable ,

11-52

specifying port values implied mnemonics ,

9-9

,

11-45

how identified in this manual ,

1-2

implied variables ,

9-9

how identified in this manual ,

1-2

indefinite block length ,

4-5

,

9-13

inductance marker query ,

11-11

INIT ,

6-11

init ignored ,

13-9

INITiate ,

9-4 ,

11-30

initiate sweep ,

11-30

INPut ,

11-30

input gain ,

11-30

input queue ,

1-14

instrument state compatible storage ,

11-32

enable/disable storage ,

11-32

save to mass storage ,

11-32

INT,16 (number format) ,

6-8

INTeger ,

4-6

intensity monitor ,

11-22

interface capabilities ,

1-8

interface clear ,

1-5 ,

1-11

internal measurement arrays ,

6-

21

interpolated array ,

11-16

invalid block data ,

13-6

character ,

13-4

character data ,

13-6

character in number ,

13-5

expression ,

13-6

format ,

13-10

inside macro definition ,

13-7

outside macro definition ,

13-7

separator ,

13-4

string data ,

13-6

suffix ,

13-5

version ,

13-10

while in local ,

13-9

IP address ,

11-14

K key press capturing ,

8-2

sensing key queue

,

5-15

,

8-4

knob turn sensing ,

5-15

L

L4 ,

1-8

label drawing ,

11-24

x-axis ,

11-20

y-axis enable/disable ,

11-22

label font ,

11-24

label mode y-axis ,

11-22

labels softkey menu ,

11-23

LAN ,

11-14

diagnostics ,

9-4

socket ,

11-15

LANDscape ,

11-28

LE0 ,

1-8

learn string ,

11-64

left margin set for hardcopy ,

11-28

LIMit ,

11-6 ,

11-8

limit bit pass/fail limit fail

,

11-18 ,

11-19

,

5-10

,

5-16

,

5-19

Limit Fail condition register ,

5-2

limit fail register set ,

5-16

limit lines display of ,

11-6

limit test delta frequency maximum ,

11-6


Index minimum ,

11-6

on⁄off ,

11-6

flatness maximum ,

11-6

minimum ,

11-6

on⁄off ,

11-6

pass/fail text position ,

11-21

statistic mean maximum ,

11-6

minimum ,

11-6

on/off ,

11-6

statistic peak-to-peak maximum ,

11-6

minimum ,

11-6

on/off ,

11-7

limit test pass/fail icon enable/disable display ,

11-21

position ,

11-21

limit test pass/fail text enable/disable ,

11-21

position ,

11-21

limitations length of GPIB cables ,

1-7

number of devices ,

1-7

line drawing ,

11-24

line stretching ,

6-26

linefeeds avoiding termination of program statements ,

6-17

list program names program names list ,

11-35

listener ,

1-2

defined ,

LLO ,

1-11

1-2

lists not same length ,

13-10

load a value in an IBASIC program ,

11-35 ,

11-36

local lockout ,

1-11

local mode ,

1-12

Local Path key ,

11-61

long form of commands ,

9-8

loss cable ,

11-45

lower-case use of ,

9-14

lower-case lettering ,

9-8

LOWPass cable fault location mode ,

11-

48

LRN?

. See *LRN?

LRNLong?

,

11-64

luminance ,

11-23

M

M_DIRECTivity ,

11-16

M_LDMATCH ,

11-16

M_RESPONSE ,

11-16

M_SRCMATCH ,

11-16

M_TRACKING ,

11-16

M_XSCALAR ,

11-16

macro definition too long ,

13-13

error ,

13-7

,

13-12

execution error ,

13-12

header not found ,

13-13

parameter error ,

13-7

,

13-12

recursion error ,

13-13

redefinition error ,

13-13

syntax error ,

13-12

magnitude marker query ,

11-11

manual conventions ,

1-3 ,

11-4

MARKer ,

11-8

marker absolute value amplitude

,

11-11

,

11-11

enable/disable ,

11-10

inductance ,

11-11

magnitude ,

11-11

phase ,

11-11

reactance ,

11-11

resistance ,

11-11

search ,

11-10

set frequency ,

11-11

set marker point ,

11-10

MARKER hardkey (ES/ET) ,

10-

42

marker limit fail ,

5-16

marker numbers, display of ,

11-

21

marker query ,

6-13

marker symbols printing enable/disable ,

11-29

mass storage device select ,

11-32

mass storage error ,

13-11

master array ,

11-16

master summary status ,

5-13

master summary status function ,

5-9

MATH ,

11-11

math trace ,

6-26

math error in expression ,

13-12

math expression trace selection ,

11-11

math operations ,

6-21

MAV bit ,

1-12

MAXimum ,

9-10

MEAS1/MEAS2 hardkey (ES) ,

10-45

MEAS1/MEAS2 hardkey (ET) ,

10-47

measurement s-parameters ,

11-51

measurement arrays ,

6-2 ,

6-21

internal ,

6-21

measurement format ,

6-3

measurement function query ,

11-48

measurement reference plane ,

6-

26

measurement uncertainties ,

11-

16

measuring


Index cable length ,

11-46

power ,

11-49

power ratio ,

11-50

measuring status ,

5-10

measuring status register set ,

5-

23

media full ,

13-11

media protected ,

13-12

memory allocate space for IBASIC programs ,

11-35

list of files , 11-31 memory arrays corrected ,

6-25

memory use error ,

13-14

menu test set calibration ,

11-47

MENU hardkey (ES/ET) ,

10-50

,

10-51

menu labels softkey ,

11-23

menu map command conventions ,

10-2

example ,

10-3

menus softkeys message

,

10-2

,

1-13

available ,

5-13

error ,

11-63 ,

13-2

exchange ,

1-13

transfer scheme user defined

,

1-7

,

11-22

message window clear current ,

11-22

disable ,

11-22

,

11-22

enable/disable off ,

11-22

remove user-defined ,

11-22

user defined

MINimum

,

11-22

,

9-10

missing mass storage ,

13-11

missing media ,

13-11

missing parameter ,

13-4

mixed data ,

4-6

MIXer ,

11-13

MMEM

MSIS ,

11-31

MMEMory ,

9-4

,

11-31 –

11-33

mnemonic implied ,

9-9

implied, how identified in this manual ,

1-2

short form ,

4-3

monitor external VGA ,

11-23

hue,saturation,luminance ,

11-23

intensity ,

11-22

More Cal Softkey ,

10-26

Mount NFS key ,

11-61

move file ,

11-32

MSS ,

5-9

multi-peak threshold value ,

11-

47

multiple commands ,

9-7

multiple controller capability ,

1-

7

multiport test set ,

10-18 ,

10-21

,

10-46

,

10-48 ,

11-14

N no pending operation ,

2-6

notch filter calculating notch width ,

11-10

NPO ,

2-6

NPO flag ,

2-6

NR1 ,

9-11 ,

11-3

NR1 data ,

4-3

NR2 ,

9-11 ,

11-3

NR2 data ,

4-3

NR3 ,

9-11 ,

11-3

NR3 data ,

4-3

num.

See <num>.

numeric data ,

4-3

data error data flow

,

13-5

,

6-2

data not allowed ,

13-5

formats ,

9-11

parameters ,

9-10 ,

11-6

numeric variable new value ,

11-36

O offset phase ,

11-46

offset and scale ,

6-27

ON|OFF . See <ON|OFF>.

one-shot sweep ,

11-30

operation complete ,

5-21

operational status ,

5-10

register set summary

,

5-24

,

5-13

OPT?

. See *OPT?

Option 100 ,

11-38

options ,

9-17

identifying ,

9-17

out of memory ,

13-10 ,

13-14

Out of Paper ,

11-18

OUTPUT ,

1-6

OUTPut ,

9-4

,

11-34

output queue ,

1-14 ,

1-15 ,

1-16 ,

5-12

overlapped commands ,

2-3 ,

9-

17 ,

9-18

defined ,

2-2

P page orientation hardcopy ,

11-28

parallel poll ,

1-11

parameter error ,

13-10

parameter not allowed ,

13-4

parameter type ,

11-2

,

11-3

,

9-10 ,

9-11 ,

9-12 ,

9-13

BLOCK ,

11-3

CHAR ,

11-3


Index defined ,

9-10

NR1

NR2

,

11-3

,

11-3

NR3 ,

11-3

STRING ,

11-3

parameter types ,

10-2

parser ,

1-15 ,

5-22 ,

9-7 ,

13-3

pass/fail icon position ,

11-21

pass/fail text position ,

11-21

pass-control-back address ,

9-17

passing control how to

PCL

,

3-3

,

11-28

,

3-2

PCL5 ,

11-28

PCX ,

11-28

pen moving ,

11-24

phase marker query ,

11-11

offset ,

6-26 ,

11-46

physical interface ,

1-2

ping ,

11-14

pixel coordinates display window ,

11-24

polar chart format ,

6-4

pop-up window message ,

11-22

user defined ,

11-22

port

Centronics ,

11-18

LAN ,

11-15

selecting from test set ,

11-37

set for hardcopy ,

11-28

port extension ,

11-44

enable ,

11-45

transmission ,

11-45

PORTrait ,

11-28

ports writable ,

11-18

POWer ,

9-4 ,

11-54

power set receiver to measure ,

11-49

POWER hardkey (ES/ET) ,

10-52

power measurement ,

11-49

power on bit ,

5-22

power ratio set receiver ,

11-49 ,

11-50 ,

11-

52

power ratio measurement ,

11-50

fault location ,

11-49

group delay ,

11-50

power values entering ,

10-7

power-on status clear flag ,

9-17

PPC ,

1-11

PPD ,

1-11

PPE ,

1-11

PPU ,

1-11

print width for hardcopy printer ,

11-18

,

11-28

page orientation

Printer_Select line

,

11-28

,

11-18

printing graph ,

11-28

table ,

11-28

PROGram ,

9-4 ,

11-35 –

11-36

program currently running downloading

,

13-13

,

11-35 ,

11-36

error ,

13-13

mnemonic too long runtime error

,

13-5

,

13-13

syntax error ,

13-13

program control starting and stopping IBASIC programs ,

11-36

programming fundamentals ,

1-9

GPIB ,

1-2

programming fundamentals ,

1-9

PSC.

See *PSC

Q query

,

11-2

error

,

5-21

,

13-17

error queue

,

11-63

marker

,

6-13

response

,

9-11

response generation

,

1-16

serial number

,

11-17

query response

,

11-2

questionable status

,

5-10

register set

,

5-19

summary

,

5-13

queue error

,

1-14

GPIB

,

1-14

input

,

1-14

output

,

1-14

,

1-15

,

1-16

queues, introduction to

,

1-14

QuickBASIC programming language

,

6-7

quotes use of

,

9-13

use with string parameters

,

9-

13

R ratio calculations

,

6-22

raw data arrays

,

6-21

reactance marker query

,

11-11

REAL

,

4-6

REAL,32 (number format)

,

6-8

REAL,64 (number format)

,

6-8

recall instrument state

,

11-31

receiver set for measurement of power ratio

,

11-49

,

11-50

,

11-52

set for power measurement

,

11-49

receiver bandwidth

,

11-38

rectangle drawing

,

11-24


Index reference impedance specifying ,

11-45

reference marker amplitude ,

11-10

frequency ,

11-10

reference oscillator ,

11-52

reference position ,

6-27

reference value ,

6-27

referenced name does not exist ,

13-14

reflection port ,

11-37

register service request enable ,

9-18

register model status ,

5-3

register sets ,

5-10 ,

5-11

register summary bit ,

5-3

registers ,

5-2

how to use ,

5-6

remote enable ,

1-12

control line ,

1-5

Remote IP Addr/Host key ,

11-61 ,

11-62

Remove Automount key ,

11-61

REN ,

1-5

,

1-12

rename a file ,

11-32

reporting of events ,

5-5

request service ,

5-13

Request Service bit ,

1-13

reset device ,

9-18

resistance marker query ,

11-11

resolution display frequency ,

11-20

hardcopy ,

11-29

resolution, data values ,

6-9

response to query ,

9-11

reversed byte order ,

4-7

RF in port ,

11-37

RF out port ,

11-37

RFWD ,

6-22

RGB color map ,

11-23

RL1 ,

1-8

ROUTe ,

9-4 ,

11-37

RPG ,

8-2

RQS ,

1-12 ,

1-13

RQS bit ,

5-7

S saturation ,

11-23

save instrument state ,

11-32

SAVE RECALL hardkey (ES/

ET) ,

10-55

scale and offset ,

6-27

scale calculations ,

6-27

SCALE hardkey (ES/ET) ,

10-60

SCORR1 ,

6-23

SCPI

1996.0 standard ,

12-3 ,

12-10

command reference ,

11-4

commands ,

8-2

conformance ,

12-2

defined errors

,

9-2

,

13-2

introduction to ,

9-2

standard commands ,

12-3

syntax conventions ,

9-14

SCPI commands menu association screen format

,

10-2

,

11-23

SDC ,

1-12 ,

1-15

search marker ,

11-10

seconds display ,

11-20

select active IBASIC program ,

11-36

ASCII data format ,

11-33

detection mode hardcopy port

,

11-47

,

11-28

mass storage device ,

11-32

program ,

11-35 ,

11-36

Selected Device Clear ,

1-12

selected device clear ,

1-12

self calibration automatic ,

11-12

enable periodic ,

11-12

initiation

SelfCal

,

11-12

,

11-12

self-test ,

9-5

,

9-18

semantic error ,

5-22

semicolons use of ,

9-7

,

9-15

sending commands ,

1-6

SENSe ,

9-5 ,

11-38 –

11-51

sequential command ,

2-2

defined example

,

2-2

,

2-9

serial number query ,

11-17

serial poll ,

1-12 ,

5-9

serial poll disable ,

1-13

serial port ,

11-18

,

11-19

service request ,

5-6 ,

5-7

control line ,

1-5

enable register generating ,

5-8

,

9-18

method of accessing registers ,

5-7

setting lost due to rtl ,

13-9

setting the stop frequency ,

9-10

settings conflict ,

13-10

SH1 ,

1-8

short form of commands ,

9-8

short form mnemonic ,

4-3

SICL ,

6-5

significant digits, number of ,

6-9

simcal command ,

11-68

single quotes use of ,

9-13

size trace data transfer ,

6-8

smith chart ,

6-4

Socket Port No. key ,

11-62

softkey menus ,

10-2

More Cal ,

10-26

softkey labels user-defined ,

11-22


Index softkey menu labels ,

11-23

softkey press sensing ,

5-15

softkeys

SCPI commands ,

10-2

SOURce ,

9-5

source set start frequency set stop frequency

,

11-48

,

11-48

spaces use of ,

9-10 ,

9-15

span frequency for RF source ,

11-48

s-parameters measurement ,

11-51

selecting

SPD ,

1-13

SPE ,

1-12

,

11-51

SPOLL ,

5-14

spur avoid selection

SR1 ,

1-8

,

11-17

SRE.

See *SRE

SRE?

. See *SRE?

SRL impedance ,

6-26

SRQ ,

1-5

,

5-6 ,

5-7

SRQ line ,

5-7

SRQ process ,

5-9

SSTOP (start/stop) ,

11-20

STANdard ,

11-42

Standard Commands for

Programmable Instruments

(SCPI) ,

9-2

standard event status ,

5-10

enable register ,

5-22

register ,

5-3

,

9-16

register set ,

5-20

summary ,

5-13

start distance cable fault location ,

11-47

start frequency set for RF source ,

11-48

start value frequency annotation ,

11-21

state recall ,

11-31

statistic mean ,

11-6

statistic peak-to-peak ,

11-6

STATus ,

9-5

PRESet command ,

5-25

PRESet Settings ,

5-25

status firmware ,

5-4

hardware ,

5-4

Status Byte ,

1-12

status byte ,

5-2 ,

5-8

,

5-10

,

9-18

clearing ,

9-16

status byte register ,

5-3

,

5-12

status port ,

11-19

status register model ,

5-3

status registers ,

5-2

STB?

. See *STB?

stop distance cable fault location ,

11-47

stop frequency frequency annotation how to set ,

9-10

,

11-21

set for RF source ,

11-48

storing calibration information ,

11-44

frequency values instrument state

,

11-33

,

11-32

trace values ,

11-33

STRING ,

11-3

string data ,

4-4

string data error ,

13-6

string data not allowed ,

13-6

string parameters ,

9-13

string variable loading a new value ,

11-36

string.

See <string>.

structural return loss.

See SRL.

subroutines ,

6-2

built in ,

6-10

high speed subsystems

,

6-19

,

9-3

suffix error ,

13-5

not allowed ,

13-5

too long ,

13-5

units ,

11-3 ,

11-6 ,

11-7 ,

11-8 ,

11-10

user defined frequency annotation ,

11-21

SWAPped ,

11-27

SWEep ,

11-52

sweep ,

11-30

set continuous/one-shot ,

11-30

set time ,

11-53

type frequency ,

11-34

power ,

11-34

SWEEP hardkey (ES/ET) ,

10-61

sweep time enable/disable automatic ,

11-

53

sweeps how to take ,

6-11

SWR ,

6-26

synchronizing the analyzer ,

2-2


1-3

error ,

5-22

,

13-3

,

13-4

summary and conventions ,

9-

14


11-4

SYSTem ,

9-5

PRESet command ,

5-4

system controller defined ,

1-2

system impedance ,

11-45

SYSTEM OPTIONS hardkey

(ES/ET) ,

10-62

SYSTEM OPTIONS, Test Set

Cal Functions (ES/ET) ,

10-

30


Index

T

T6

,

1-8

table printing

,

11-28

tables explained

,

10-3

take control talker

,

1-13

talker

,

1-2

defined

TCT

,

1-2

,

1-13

TE0

,

1-8

TEST

,

9-5

,

11-66

test set multiport

,

11-14

port selection

,

11-37

test set calibration enable storage of test set calibration only

,

11-33

menu

,

11-47

text channel annotation

,

11-20

entering

,

10-8

threshold value multi-peak

,

11-47

time values entering

,

10-6

title enable/disable

,

11-22

too many digits

,

13-5

too much data

,

13-10

top margin set for hardcopy

,

11-28

TRACe

,

9-5

,

11-67

,

11-68

trace storing to a file

,

11-33

trace averaging enable/disable

,

11-38

restarting

,

11-38

trace data

,

4-4

how to read

,

6-3

trace data printing enable/disable

,

11-29

trace data transfers

,

6-1

size ,

6-8

trace markers display of marker numbers ,

11-

21

trace math ,

11-11

trace math operation ,

6-26

trace selection math expression ,

11-11

transferring data ,

4-2

transform ,

6-26

transition registers ,

5-3

,

5-4

transmission port ,

11-37

TRG.

See *TRG

TRIGger ,

9-5

,

11-69

trigger deadlock ,

13-9

error ,

13-9

ignored ,

13-9

set source ,

11-53

system ,

11-30

TST?

. See *TST?

variables implied, how identified in this manual ,

1-2

velocity factor specifying ,

11-46

voltage values entering ,

10-7

W wait ,

11-36

Web browser ,

11-4

weighting factor ,

11-38

WINDow ,

11-24

,

11-25

window set selection for cable fault location measurements ,

11-53

window geometry ,

7-4

window queries ,

7-5

WINDow1 ,

7-2

WINDow10 ,

7-2

WINDow2 ,

7-2

writeable ports ,

11-18

WRITEIO ,

11-18

U uncertainties ,

11-16

undefined header ,

13-5

units cable length ,

11-47

suffix ,

11-3

,

11-6

,

11-7

,

11-8

,

11-10

unrecognized header ,

13-3

upper-case use of ,

9-14

upper-case lettering ,

9-8

user bit ,

11-18 ,

11-19

user-defined message ,

11-22

using graphics ,

7-2

X x-axis label ,

11-20

Y y-axis label mode ,

11-22

Z

Z cutoff frequency ,

11-48

zeroing auto ,

11-12

V values entering ,

10-3

variable implied ,

9-9
