volume 1: syntax and style - ivi foundation

Standard Commands for Programmable Instruments (SCPI)

Volume 1: Syntax and Style

VERSION 1999.0May, 1999Printed in U.S.A.

Hints

Click on any triangle in the left-hand pane to expand the headings list. Click on any heading to go directly to that part of the document. Click on the binoculars or press Ctrl-F (Command-F on the Mac) to open the Find function. Type in the search word or phrase, then click on the binoculars with a swirling arrow icon (or press Ctrl-G) to locate next instance of the word/phrase once the first instance is located. Minimize this note by clicking on it, then clicking on the "-" on the left end of the red title bar. Double-click on the minimized note to display it again.

NOTICE, STATEMENT of INTENT and

AUTHORIZATION TO COPY

© Copyright 1999 SCPI Consortium

This document defines the Standard-Commands-for-Programmable-Instruments (SCPI) Consortium’s SCPIstandard. Although the Consortium hereby expressly disclaims any and all warranties whatsoever regardingthe SCPI standard, the Consortium has published this document with the intent that the SCPI standard will beseriously considered and adopted, in whole, by the test and measurement marketplace. Consistent with thatintent, permission is hereby granted by the Consortium to make copies of this entire document as a whole,PROVIDED THAT this NOTICE, STATEMENT of INTENT and AUTHORIZATION TO COPY shallprominently appear on each such whole copy. Further consistent with that intent, permission is hereby grantedby the consortium to make copies of portions of this document, absent this NOTICE, STATEMENT ofINTENT and AUTHORIZATION TO COPY , PROVIDED THAT each such portion-copies shall only beused in a manner which is consistent with the purposes of implementing, promoting, disseminating, orenhancing (as opposed to deviating from) the SCPI standard as herein defined, such as the inclusion of such aportion-copy in an instrument (or instrument-related) product manual which implements SCPI (as definedherein) or in use for design of such an instrument (or instrument related) product. However, under nocircumstances may copies of this document, or any portion of this document, be made solely for purposes ofsale of the copy or copies.

For information, contact:

Fred Bode, Executive DirectorSCPI Consortium2515 Camino del Rio South, Suite 340San Diego, CA 92108

Phone: (619) 297-1210Fax: (619) 297-5955Email: [email protected] Page: http://www.scpiconsortium.org

European SCPI Consortium Contact:

John PieperACEAP.O. Box 1347640 AC WierdenThe Netherlands

Phone: +31 546 57 79 94Fax: +31 546 57 55 75Email: [email protected] Page: http://ourworld.compuserve.com/homepages/acea/

1999 SCPI Syntax & Style

i

ForewordCommercial computer-controlled test instruments introduced in the 1960s used a wide variety ofnon-standard, proprietary interfaces and communication protocols. In 1975, the Institute of Electrical andElectronic Engineers approved IEEE 488-1975. IEEE 488 defined a standard electrical and mechanicalinterface for connectors and cables. It also defined handshaking, addressing, and general protocol fortransmitting individual bytes of data to and from instruments and computers. This standard has been updatedand is now IEEE 488.1-1987.

Although it solved the problem of how to send bytes of data between instruments and computers, IEEE 488did not specify the data bytes’ meanings. Instrument manufacturers freely invented new commands as theydeveloped new instruments. The format of data returned from instruments varied as well. By the early 1980s,work began on additional standards to specify how to interpret data sent via IEEE 488.

In 1987, the IEEE released IEEE 488.2-1987, Codes, Formats, Protocols and Common Commands for Usewith IEEE 488.1-1987. This standard defined the roles of instruments and controllers in a measurementsystem and a structured scheme for communication. In particular, IEEE 488.2 described how to sendcommands to instruments and how to send responses to controllers. It defined some frequently used“housekeeping” commands explicitly, but each instrument manufacturer was left with the task of naming anyother types of command and defining their effect. IEEE 488.2 specified how certain types of features shouldbe implemented if they were included in an instrument. It generally did not specify which features orcommands should be implemented for a particular instrument. Thus, it was possible that two similarinstruments could each conform to IEEE 488.2, yet they could have an entirely different command set.

Standard Commands for Programmable Instruments (SCPI) is the new instrument command language forcontrolling instruments that goes beyond IEEE 488.2 to address a wide variety of instrument functions in astandard manner. SCPI promotes consistency, from the remote programming standpoint, between instrumentsof the same class and between instruments with the same functional capability. For a given measurementfunction such as frequency or voltage, SCPI defines the specific command set that is available for thatfunction. Thus, two oscilloscopes made by different manufacturers could be used to make frequencymeasurements in the same way. It is also possible for a SCPI counter to make a frequency measurement usingthe same commands as an oscilloscope.

SCPI commands are easy to learn, self-explanatory and account for both novice and expert programmer’susage. Once familiar with the organization and structure of SCPI, considerable efficiency gains can beachieved during control program development, independent of the control program language selected.


ii

Table of Contents

Chapter 1 Introduction

1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.3 SCPI Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.4 SCPI Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.5 Instrument Interchangeability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Chapter 2 References

Chapter 3 Life Cycle

3.1 Adding a Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 Obsoleting a Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.3 Device Dependent Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Chapter 4 SCPI Compliance Criteria

4.1 IEEE 488.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.1 IEEE Mandated Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.2 IEEE Optional Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.3 IEEE Common Command Implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.3.1 Overlapped and Sequential Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.3.2 *CLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.3.3 *OPC and *WAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.3.4 *OPC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.3.5 *RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3.5.1 Interaction With the Synchronization Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3.5.2 Implications For *SAV and *RCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3.5.3 *RST and *RCL as Overlapped Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3.6 *IDN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2 SCPI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.1 Required Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.2 Optional Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.3 Documentation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Chapter 5 Notation

5.1 Interpreting Command Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.2 Interpreting Syntax Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

v

Chapter 6 Program Headers

6.1 Common Command and Query Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16.2 Instrument-Control Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16.2.1 Mnemonic Generation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2.2 Building the Command Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.2.3 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-66.2.4 Traversal of the Header Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76.2.5 Multiple Capabilities and Numeric Keyword Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.5.1 Single Instrument with Many Electrical Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.5.2 Multiple Identical Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-86.2.5.3 Logical Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Chapter 7 Parameters

7.1 Character Program Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.2 Decimal Numeric Program Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17.2.1 <numeric_value> Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17.2.1.1 DEFault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17.2.1.2 MINimum|MAXimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.2.1.3 UP/DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-27.2.1.3.1 STEP Subsystem Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.2.1.3.2 [:INCRement] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-37.2.1.3.3 :PDECade <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.2.1.3.4 :MODE LINear|LOGarithmic|L125|L13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-37.2.1.3.5 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1.3.6 STEP Subsystem Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-47.2.1.4 INFinity and Negative INFinity (NINF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1.5 Not A Number (NAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2 Unit Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.3 Boolean Program Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.4 Coupling of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.4.1 Functional Coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.4.2 Value Coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.4.3 Automatic Coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-77.5 Units of Measure and Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-77.5.1 Units of Amplitude and Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.5.2 Expressing Unitless Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9

Chapter 8 Expressions

8.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18.2 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18.3 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.3.1 Numeric Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-28.3.1.1 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2


vi

8.3.1.2 Precedence Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.3.1.3 Semantics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.3.2 Channel Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.3.3 Numeric Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Chapter 9 Status Reporting

9.1 The Device-Dependent Register Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2 Transition Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.3 Operation Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.4 QUEStionable Data/Signal Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.5 Multiple Logical Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59.6 Status Structure for the Expanded Capability Trigger Model . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Chapter 10 *RST Conditions

Chapter 11 Naming Conventions

11.1 :DEFine <name>,<data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-211.2 :DEFine? <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-211.3 :DELete[:NAME] <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-211.4 :DELete:ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-211.5 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Chapter A Programming Tips


vii

1 Introduction

1.1 RequirementsThis volume, “Syntax and Style,” is global in nature and shall be used with all other volumesof the SCPI standard.

1.2 OrganizationThe first five chapters of Syntax and Style are an introduction to the overall concept of SCPI1999. They describe an overview of the standard, reference other standards, describe SCPIcompliance criteria, and how to interpret command tables and syntax flow diagrams. Thenext three chapters in this volume describe the program headers, parameters and expressionsfrom which SCPI commands and responses are built. Following this are chapters whichdescribe the status reporting model, style guidelines for creating new commands, the effectof *RST on parameter values, and facilities for managing named sets of data in aninstrument.

BodeThis volume, Syntax and Style, is the first of the four-volume set that makes up the SCPI1999 Standard. The second and largest volume is the SCPI Command Reference, whichcontains the actual language constructs which appear in instruments. The third volume, DataInterchange Format, defines a standard representation for data sets which may be usedbetween instruments and applications, between applications, or directly betweeninstruments. The fourth volume, Instrument Classes, defines the SCPI commands andbehavior needed to implement functionality sets associated with common classes ofinstruments. These four volumes form the complete 1999 SCPI Standard and should be usedas a set.

BodeThis document is intended to apply to “systems” instruments. It defines both organizationand content of messages at the controller-to-instrument and instrument-to-controllerinformation interchange level. This document was developed so that, an instrumentdesigned in accordance with it, shall be able to conform to IEEE Std. 488.1-1987 StandardDigital Interface for Programmable Instrumentation, and IEEE Std. 488.2-1987 Codes,Formats and Common Commands For Use With IEEE Std. 488.1-1987. Conformance toIEEE 488.1-1987 and IEEE 488.2-1987 is not required by this document, recognizing thatsome instruments implement physical interfaces other than the IEEE 488.1-1987. However,SCPI is based upon the concepts and terminology used within these standards.

This document may impact the related person-to-instrument and the instrument-to-personinformation interchange levels. Though the main purpose of this document is to define theinterface as it relates to remote control, implementation of these codes and formats mayaffect the “front panel” of the instrument involved.

1.3 SCPI GoalsThe goal of Standard Commands for Programmable Instruments (SCPI) is to reduceAutomatic Test Equipment (ATE) program development time. SCPI accomplishes this goalby providing a consistent programming environment for instrument control and data usage.This consistent programming environment is achieved by the use of defined program

1

2 3

4

5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Introduction 1-1

messages, instrument responses, and data formats across all SCPI instruments, regardless ofmanufacturer.

A consistent program environment uses the same commands and parameters to controlinstruments that have the same functionality. These program commands and parameters aresent from a controller to an instrument using IEEE 488.1, VXIbus, RS-232C, etc., interfaces.SCPI instruments are very flexible in accepting a range of command and parameter formats,which makes the instrument easier to program. The instrument resonses sent back to thecontroller can be either data or status information. SCPI instrument response format of aparticular query is well-defined and reduces the programming effort to understandinstrument data and status information. Data information can be formatted so that it isdevice- and measurement-independent.

SCPI programming consistency is both vertical and horizontal. Vertical programmingconsistency defines program messages within an instrument class. An example of verticalconsistency is using the same command for reading DC voltage from several differentmultimeters. Horizontal consistency is using the same command to control similar functionsacross instrument classes. For example, the trigger command would be the same for anidentical trigger function found among counters, oscilloscopes, function generators, etc.

A key to consistent programming is the reduction of multiple ways to control similarinstrument functions. The philosophy of SCPI is for the same instrument functions to becontrolled by the same SCPI commands. To simplify learning, SCPI uses industry-standardnames and terms that are manufacturer and customer supported.

SCPI provides several different levels of instrument control. Simple Measure commandsprovide users easy and quick control of SCPI instrumentation, while more detailedcommands provide traditional instrument control.

SCPI is designed to be expanded with new defined commands in the future without causingprogramming problems. As new instruments are introduced, the intent is to maintainprogram compatibility with existing SCPI instruments. SCPI ATE test programs designed torun with new instruments may not be compatible with existing instruments. In other words,the test programs are upward-compatible, but not downward-compatible.

To promote wide industry acceptance, SCPI is publicly available for implementation byanyone, whether or not they are a member of the SCPI Consortium.

The Consortium does not release working documents or provisional documentation. Onlyapproved standards are released to the public.

1.4 SCPI UsageThe advantage of SCPI for the ATE system programmer is reducing the time learning how toprogram new SCPI instruments after programming their first SCPI instrument.

Programmers who use programming languages such as BASIC, C, FORTRAN, etc., to sendinstrument commands to instruments will benefit from SCPI. Also, programmers whoimplement instrument device drivers for ATE program generators and/or softwareinstrument front panels will benefit by SCPI’s advantages. SCPI defines instrument

1

2 3

4

5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


1-2 Introduction

commands, parameters, data, and status. It is not an application package, programminglanguage, or software intended for instrument front panel control.

SCPI is designed to be layered on top of the hardware-independent portion of IEEE 488.2.SCPI can be used with controller-to-instrument interfaces such as IEEE 488.1, VXIbus,RS-232C, etc.

1.5 Instrument InterchangeabilityBy providing a consistent programming environment, replacing one SCPI instrument withanother SCPI instrument in an ATE system will usually require less effort than withnon-SCPI instruments. SCPI is not a standard which completely provides for interchangeableinstrumentation. SCPI helps move toward interchangeability by defining instrumentcommands and responses, but it does not define instrument functionality, accuracy,resolution, connectors, etc., which is needed to provide true instrument interchangeabilitywithout affecting the ATE system hardware and software.

1

2 3

4

5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Introduction 1-3

1

2 3

4

5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


1-4 Introduction

2 References“ANSI S1.4” HP019

ANSI X3.4-1977, American National Standard Code for Information Interchange;ISO Std.646-1983, ISO 7 bit Coded Character Set for Information Interchange

ANSI X3.42-1975, American National Standard Representation of NumericValues in Character Strings for Information Interchange; ISO Std. 6093-1985,Representation of Numeric Values in Character Strings for InformationInterchange

ANSI/EIA/TIA-562-1989, Electrical Characteristics for an Unbalanced DigitalInterface TK014

ANSI/IEEE Std 181-1977, IEEE Standard on Pulse Measurement and Analysis byObjective Techniques

ANSI/IEEE Std 194-1977, IEEE Standard Pulse Terms and Definitions

ANSI/IEEE Std. 260-1978, An American National Standard IEEE Standard LetterSymbols for Units of Measurement (SI Units, Customary Inch-Pound Units, andCertain Other Units); ISO Std.1000-1981, SI Units and Recommendations for theUse of Their Multiples and Certain Other Units

ANSI/IEEE Std 488.1-1987, IEEE Standard Digital Interface for ProgrammableInstrumentation

12-4-94 ltrANSI/IEEE Std 488.2-1992, IEEE Standard Codes, Formats, Protocols, andCommon Commands for use with ANSI/IEEE Std 488.1-1987

ANSI/IEEE Std 754-1985, IEEE Standard for Binary Floating-Point Arithmetic

Bell Telephone “Per BTSM 41004” HP019

“CCIR Recommendation 468-2” HP019

“CCITT Recommendation P53” HP019

CCITT Recommendation V.42, Fascile V111.1 (Blue book, 1988), ErrorCorrecting Procedures for DCE’s Using Asynchronous-to-SynchronousConversion TK014

“Dolby Labs Bulletin No 19/4” HP019

EIA RS-232-D, Interface Between Data Terminal Equipment and DataCommunication Equipment Employing Serial Binary Data Interchange TK014

EIA RS-422, Electrical Characteristics of Balanced Voltage Digital InterfaceCircuits TK014

“Fields and Waves in Communication Electronics,” Ramo, Whinnery, andVan Duzer HP056

“IEC Recommendation 179”

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


References 2-1

HP019

IEEE Micro, Volume 8, Number 4, August, 1988, pp 62-76

ISO Std. 2955-1983, Information processing–Representation of SI and other unitsin systems with limited character sets

“On the Use of Windows for Harmonic Analysis with the Discrete FourierTransform,” F.J. Harris, Proc. of the IEEE, Vol 66-1, January, 1978, pp 51-83

SAE J2264 1995-04 Chassis Dynamometer Simulation of Road Load Using CoastDown Techniques.

“Tuning a Control Loop Performance,” Gregory K. McMillan, InstrumentSociety of America, ISBN 0-87664-694-1 XSS01c

VXI Consortium INC, VMEbus Extensions for Instrumentation SystemsSpecification, Revision 2.0

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


2-2 References

3 Life CycleSCPI is a “living” standard. Additional commands will always be needed to meet the needsof new technologies and new instruments. The SCPI Consortium meets regularly to proposeand review extensions to the command set. New commands may be proposed by members ofthe Consortium, and by other interested parties.

Proposals accepted by the Consortium are published and distributed to member companiesand are available for immediate use. Approved proposals are reviewed annually. After theannual review, a new revision of the SCPI Standard is published, and the commands becomea permenant part of the standard.

All copies of the SCPI Standard contain a version year of issue. All SCPI instruments can bequeried to determine the version-year to which they conform.

3.1 Adding a CapabilityHP076,

Ed Change

In general, a command proposed as an extension to SCPI will be approved if it is wellformed according to the rules set forth in “Syntax and Style”, if it conforms in style tocommands in the subsystem where it is placed, and if there is not already a command tocontrol the same functionality. The Consortium rejects commands only on the basis ofobjective criteria.

SCPI is designed to grow in an upwardly compatible way. For a control program, this meansthat the aditions to SCPI will not change the meanings of existing commands, and standardprograms will not need to be rewritten except to add new functionality. For an instrument,upward compatibility means that the instrument functionality will not become inaccessabledue to additions to the language; existing instruments will not become obsolete by theextension of SCPI.

3.2 Obsoleting a CapabilityIt is possible that a command may someday have to be altered or deleted in order to permitimportant new functionality to be implemented. Such an event represents the failure of theextension process because it breaks upward compatibility. Proposals for changes that breakupward compatibility will only be accepted if there is overwhelming evidence that thebenefits to users and the member companies of the Consortium outweigh the cost to existingusers.

The following commands have been deleted from the SCPI Volume II, Command Referenceas a part of the SCPI life cycle process. Reuse is discouraged. Any reinstatement is to beaccompanied by a careful review of compatibility issues with all previous versions of theSCPI standard.

KEYWORD PARAMETER FORM NOTES DELETION DATESTATus 1996 :QUEue 1996 :ENABle <event_queue_list> 1996 [:NEXT]? [query only] 1996

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Life Cycle 3-1

3.3 Device Dependent CommandsFrom time to time manufacturers may elect to build instruments with capabilities that are notcovered by a current version of this standard. Presumably the manufacturer will submit thesenew commands into the SCPI Life Cycle process. If the consortium adopts commands thatare incompatible those originally used by the manufacturer, the manufacturer is permitted toprovide his original commands in subsequent products for compatibility. 1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-2 Life Cycle

4 SCPI Compliance CriteriaThis section indicates mandatory and optional capabilities of SCPI. These capabilities arefully specified elsewhere, in “Syntax and Style”, “Command Reference”, “Data InterchangeFormat” and IEEE 488.2, and an instrument designer shall fully comply with the referencedsections. Only designs conforming to these requirements shall be able to claim conformanceto the SCPI specification.

4.1 IEEE 488.2 RequirementsAll SCPI instruments shall conform to the specifications for devices in IEEE 488.2, exceptthat section 4.1 IEEE 488.1 Requirements shall be omitted where an instrument does notimplement an IEEE 488.1 interface.

Additionally, a SCPI instrument shall be able to parse <compound command programheader> and <compound query program header>, to handle the tree structured commands inSCPI.

4.1.1 IEEE Mandated CommandsAll SCPI instruments shall implement all the common commands declared mandatory byIEEE 488.2.

Mnemonic Name 488.2 Section*CLS Clear Status Command 10.3 *ESE Standard Event Status Enable Command 10.10 *ESE? Standard Event Status Enable Query 10.11 *ESR? Standard Event Status Register Query 10.12 *IDN? Identification Query 10.14 *OPC Operation Complete Command 10.18 *OPC? Operation Complete Query 10.19 *RST Reset Command 10.32 *SRE Service Request Enable Command 10.34 *SRE? Service Request Enable Query 10.35 *STB? Read Status Byte Query 10.36 *TST? Self-Test Query 10.38 *WAI Wait-to-Continue Command 10.39

4.1.2 IEEE Optional Common CommandsIEEE Std. 488.2 describes several optional commands which may be implemented in adevice. None of these commands are required by SCPI.

KI0054.1.3 IEEE Common Command ImplicationsProper implementation of some of the IEEE 488.2 common commands carry someimplications which are not immediately obvious. Primarily this has to do with thesynchronization commands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SCPI Compliance Criteria 4-1

4.1.3.1 Overlapped and Sequential CommandsKI005IEEE 488.2 defines a distinction between overlapped and sequential commands. As defined

in IEEE 488.2, a sequential command is one which finishes executing before the nextcommand starts executing. An overlapped command is one which does not finish executingbefore the next command starts executing. These types of commands are described in IEEE488.2, section 12. Examples are given in IEEE 488.2, appendix B.

KI005IEEE 488.2 defines three common commands (*OPC, *WAI, *OPC?) which a devicecontroller can use to synchronize its operation to the execution of overlapped commands.The definitions for these common commands appear in sections 10.18, 10.19, and 10.39 ofIEEE 488.2. All three are required by IEEE 488.2, even if none of the device’s commandsare overlapped.

KI005Implementing any device commands as overlapped will increase the complexity of theimplementation of the three synchronization common commands.

KI005Each overlapped command has associated with it a Pending Operation flag. The device setsthis flag TRUE when it passes the corresponding command from the Execution Controlblock to the Device Action block. The device sets the flag false when the device operation isfinished, or has been aborted.

KI005IEEE 488.2 defines a No Operation Pending flag. This flag is FALSE whenever any PendingOperation flag is TRUE, and is TRUE whenever all Pending Operation flags are FALSE.IEEE 488.2 also permits device designers to decide which overlapped commands areincluded in the No Operation Pending flag. A device may implement commands whichselect which overlapped commands are included in the No Operation Pending flag, althoughthe SCPI standard does not include such a command.

KI005IEEE 488.2 requires user documentation to clearly indicate which commands, if any, areoverlapped, and which overlapped commands are included and which are excluded from theNo Operation Pending flag.

KI0054.1.3.2 *CLSKI005This command clears all status data structures in a device. For a device which minimally

complies with SCPI, these registers are:

KI005 SESR (IEEE 488.2) OPERation Status Register (SCPI) QUEStionable Status Register (SCPI) Error/Event Queue (SCPI)

KI005Execution of *CLS shall also clear any additional status data structures implemented in thedevice. The corresponding enable registers are unaffected. See the table in CommandReference, 20.7.

KI005*CLS forces the device into OCIS and OQIS (see 4.1.3.3 and 4.1.3.4) without setting the NoOperation Pending flag TRUE and without setting the OPC bit of the SESR TRUE andwithout placing a “1” into the Output Queue.

KI005

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-2 SCPI Compliance Criteria

For example, suppose a device implements INITiate[:IMMediate] as an overlappedcommand. Assuming that the trigger model is programmed so that it will eventually return tothe IDLE state, and that INITiate[:IMMediate] takes longer to execute than *OPC, sendingthese commands to this device:

KI005 INITiate;*OPC

KI005results in initiating the trigger model and, after some time, setting the OPC bit in the SESR.However, sending these commands:

KI005 INITiate;*OPC;*CLS

KI005still initiates the trigger model. Since the operation is still pending when the device executes*CLS, the device does not set the OPC bit until it executes another *OPC command.

KI0054.1.3.3 *OPC and *WAIKI005A device is in the Operation Complete Command Active State (OCAS) after it has executed

*OPC. The device returns to the Operation Complete Command Idle State (OCIS) wheneverthe No Operation Pending flag is TRUE, at the same time setting the OPC bit of the SESRTRUE. See IEEE 488.2 Fig 12-4. The following events force the device into OCIS withoutsetting the No Operation Pending flag TRUE and without setting the OPC bit of the SESR:

KI005power onKI005receipt of the dcas message (device clear)KI005execution of *CLSKI005execution of *RST

KI005Implementation of the *OPC and *WAI commands is straightforward in devices whichimplement only sequential commands. When executing *OPC the device simply sets theOPC bit of SESR. Executing *WAI is a no-operation. The device is, in effect, always inOCIS.

KI005In devices which implement overlapped commands the implementation of *OPC and *WAIis a little more complicated. After executing *OPC the device must not set the OPC bit ofSESR until the device returns to OCIS, even though it continues to parse and executecommands. After executing *WAI the device must execute no further commands or queriesuntil the No Operation Pending flag is TRUE, or receipt of a dcas message, or a power on.

KI0054.1.3.4 *OPC?KI005SCPI adds the requirement that *OPC? is implemented as a sequential command.

KI005A device is in the Operation Complete Query Active State (OQAS) after it has executed*OPC?. The device returns to the Operation Complete Query Idle State (OQIS) wheneverthe No Operation Pending flag is TRUE, at the same time placing a “1" in the Output Queue.See IEEE 488.2 Fig 12-6. The following events force the device into OQIS without settingthe No Operation Pending flag TRUE and without placing a ”1" in the Output Queue:

KI005power onKI005receipt of the dcas message (device clear)

KI005

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Implementation of the *OPC? query is straightforward in devices which implement onlysequential commands. When executing *OPC? the device simply places a “1" in the OutputQueue.

KI005The implementation of overlapped commands in a device complicates the implementation of*OPC? and places some restrictions on the implementation of the Message ExchangeProtocol (MEP). IEEE 488.2 dictates that devices shall send query responses in the order thatthey receive the corresponding queries (IEEE 488.2 6.4.5.4). Although IEEE 488.2recommends that *OPC? be the last query in a program message, there is nothing to preventa controller program from ignoring this suggestion. This is why *OPC? must be sequential.

KI0054.1.3.5 *RSTThe “*RST Conditions” chapter of Volume 1 gives pretty a lucid description of the SCPIrequirements of *RST. There are, however, some implications.

KI0054.1.3.5.1 Interaction With the Synchronization CommandsKI005*RST stops the execution of any overlapped commands. The natural outcome of this is that

the No Operation Pending flag will go TRUE. Execution of *RST must place the device inOCIS before setting the No Operation Pending flag TRUE, so that the effect of any pending*OPC command is nullified (that is, the OPC bit of the SESR does NOT get set).

KI0054.1.3.5.2 Implications For *SAV and *RCLKI005In devices which implement the optional *SAV and *RCL common commands, the scope of

instrument settings affected by these commands shall be the same as that affected by *RST.This means that if *RST has any effect upon a command, then so must *RCL. Conversely, ifthe device designer wants *RCL to have an effect upon a command, then *RST must alsohave an effect upon that command. Inversely, and more importantly, if the device designerwants a command to be EXCLUDED from the scope of *SAV and *RCL, then it must alsobe excluded from the scope of *RST.

KI005KI0054.1.3.5.3 *RST and *RCL as Overlapped CommandsKI005While *RST stops the execution of running overlapped commands, the instrument designer

may find it useful to make the *RST command, itself, overlapped. For example, if resettingrequires the return to an initial position of a slow-reacting, electro-mechanical device. In thiscase, performance may be better served with *RST overlapped as subsequent commandsmay be parsed and executed while the resetting is completing. Even while overlapped, the*RST command shall always complete the resetting of device state variables beforesubsequent commands are processed to insure the integrity of *RST exception programming.For similar reasons, *RCL may be an overlapped command.

KI005If *RST or *RCL is overlapped, its Pending-Operation flag shall be reported in theNo-Operation-Pending flag.

KI005If execution of *RST or *RCL causes a device operation which is equivalent to executing anoverlapped command, the device shall set TRUE the Pending-Operation flag associated withthat command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KI0054.1.3.6 *IDN?

KI005IEEE 488.2 is purposefully vague about the content of each of the four fields in the responsesyntax. SCPI adds no further requirement, but here are some suggestions:

KI005All devices produced by a company should implement the *IDN? responseconsistently.

KI005Field 1, the Manufacturer field, should be identical for all devices produced by asingle company.

KI005Field 2, the Model field, should NOT contain the word “MODEL”.KI005Field 4, the Firmware level field, should contain information about all separately

revisable subsystems. This information can be contained in single or multiplerevision codes.

4.2 SCPI RequirementsIEEE 488.2 describes the syntax of programming and device behavior to a certain level.Further refinement of the syntax and addition rules are imposed by SCPI in order to giveinstruments a common “look and feel”. The “Syntax and Style” volume of this standarddescribes the concepts behind SCPI and sets guidelines for originating new commands. ASCPI device shall follow these guidelines and style requirements.

4.2.1 Required CommandsThe following commands are required in all SCPI instruments:

Mnemonic Command Reference Section Syntax and Style Section:SYSTem :ERRor 21.8 [:NEXT]? 21.8.3e (see Note 1) 1996 :VERSion? 19.16 (see Note 2) 1991 PH022

:STATus 18 5 :OPERation [:EVENt]? :CONDition? :ENABle :ENABle? :QUEStionable [:EVENt]? :CONDition? :ENABle :ENABle? :PRESet

Note 1: The requirement changed from SYSTem:ERRor? to SYSTem:ERRor[:NEXT]? inversion 1995.1.

Note 2: Requirement applies for all versions greater than 1990.0

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



PH022

4.2.2 Optional CommandsAll other commands in the “Command Reference” are considered optional, depending on thecapabilities of the instrument. That is, the control of any instrument capability that isdescribed in SCPI shall be implemented exactly as specified by using the appropriate SCPIdefined commands. For example, an instrument dedicated to voltage measurement wouldnot implement commands for sensing frequency. Certain commands, if implemented,require that other commands also be implemented.

When a device does not support all alternative parameter values that are allowed for a SCPIcommand, it may implement a subset of these values unless otherwise stated. For example,if an instrument implements only RECTangular and UNIForm data shaping for itsCALCulate:TRANSform:WINDow command, it may generate an error on receipt of anyother SCPI defined parameter value (FLATtop,HAMMing, etc). However, a device mustimplement all parameters of a multi-parameter SCPI command.

Commands required to implement a SCPI-described capability may be omitted under specialconditions. The special condition exists when a command to be implemented affects a partof the instrument in which the configuration is fixed, and that the fixed configuration for thatcommand corresponds to the value it would take on when an IEEE 488.2 *RST resetcommand is issued. For example, an instrument with a display that is configured to bepermanently on does not need to implement the command that turns the display ON or OFF,since at *RST it is required by SCPI to be ON. If an instrument has a fixed configuration inwhich a setting does not correspond to the *RST value, then the instrument shall implementthe command for that setting even though it has only a single legal value.

4.2.3 Documentation RequirementsThe documentation for a SCPI instrument shall list the version number for which theinstrument complies. This information shall appear on instrument specification sheets andrelated documents, as well as the programming manual.

HP076The manual for a SCPI instrument shall have a separate section titled “SCPI ConformanceInformation”. This section shall list separately:

The SCPI version to which the instrument complies

The syntax of all SCPI confirmed commands implemented by the instrument.Confirmed commands are those commands which are published in the latestversion of SCPI to which the instrument conforms. Commands in theDIAGnostic subsystem, and other commands which are not intended for end-useruse need not be documented in this section.

HP000,HP001

The syntax of all SCPI approved commands implemented by the instrument.Approved commands are those commands which have been approved by theSCPI Consortium, but are not contained in the version of SCPI to which theinstrument conforms.

HP000

The syntax of all commands implemented by the instrument, which are not part of

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



the SCPI definition.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5 NotationExtensive use is made of syntax flow diagrams and tables throughout this document.Associated with these are notational styles, which are described in this chapter.

5.1 Interpreting Command TablesCommand tables are used to define a set of SCPI commands. A table shows the commands,their hierarchical relationships, related parameters (if any), and associated notes. The table isbroken into 3 columns; the KEYWORD, the PARAMETER FORM, and any NOTES.

The KEYWORD column provides the name of the command. The actual name of thecommand consists of one or more keywords since SCPI commands are based on ahierarchical structure, also known as a tree system. In such a system, associated commandsare grouped together under a common node in the hierarchy, analogous to the way leaves ata same level are connected at a common branch. This and similar branches are connected tofewer and thicker branches, until they meet at the root of the tree. The closer to the root, thehigher a node is considered in the hierarchy. To obtain a particular leaf or a particularcommand, the full path to it must be specified. This path is represented in the tables byplacing the highest node in the hierarchy in the left-most position. Lower nodes in thehierarchy are indented one position to the right, below the parent node.

Square brackets ([]) are used to enclose a keyword that is optional when programming thecommand; that is, the instrument shall process the command to have the same effect whetherthe option node is omitted by the programmer or not. Such a node is called a default node.Letter case in tables is used to differentiate between the accepted short form (the uppercasecharacters) and the long form (the whole keyword). The significance of the short and longform keywords is explained in the “Program Headers” chapter.

The PARAMETER FORM column indicates the number and order of parameters in acommand and their legal values. A command may allow the use of a SCPI-definedparameter type, a literal, or a combination of the two. The SCPI-defined parameter types aredescribed in the “Parameters” chapter, and are distinguished by enclosing the type name inangle brackets (<>). A literal is typically a word that enumerates a setting that cannot bedescribed using the SCPI-defined parameter types.

In the PARAMETER FORM column, a number of characters have special significance.Square brackets ([]) are used to enclose one or more parameters that are optional whencontrolling the instrument. Braces ({}), or curly brackets, are used to enclose one or moreparameters that may be included zero or more times. The vertical bar (|) can be read as “or”and is used to separate alternative parameter options.

The query form of a command is generated by appending a question mark to the lastkeyword. However, not all commands have a query form, and some commands exist only inthe query form. The NOTES column is used to indicate this.

As an example, suppose the existance of the following table.

1

2

3

4 5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Notation 5-1

KEYWORD PARAMETER FORM COMMENTS:FREQuency [:CW] <numeric_value> :AUTO <Boolean> :CENTer <numeric_value> :SPAN <numeric_value>

To set the frequency value for a Continuous Wave signal, the following command would besent:

FREQuency:CW 2000000

Alternatively, since the CW node is optional the following command is also valid:FREQuency 2000000

To set the value of AUTO, either of the following commands are allowed, again due to theoptional CW node:

FREQuency:CW:AUTO OFF

FREQuency:AUTO OFF

The query form of the AUTO command is either of the following:FREQuency:CW:AUTO?FREQuency:AUTO?

In the “Command Descriptions,” the detailed descriptions of the individual commands areprovided immediately after the command table, in the order in which the commands appearin the table, reading from top to bottom.

5.2 Interpreting Syntax Flow DiagramsSyntax flow diagrams are used extensively throughout the SCPI document and IEEE 488.2to provide pictorial representations of syntax. These representations are also known asrailroad diagrams.

The flow through a diagram is given by lines and arrows. These link together the variousobjects used to form a command. Objects exist in the diagram as either a circle or a box.Circles indicate literal characters and the boxes represent a syntactic structure that is definedelsewhere in this document or in IEEE 488.2. Flow through the diagrams generally proceedsleft-to-right. Diagrams are entered on the left, and the syntax is satisfied when the diagramis exited on the right. When an element or group of elements in the diagram is repeatable, areverse, right-to-left path will be shown around and above the element(s), and is marked witha left-facing arrow. When an element or group of elements in the diagram are optional, aleft-to-right bypass path will be shown around and below the element(s). A branch in thepath indicates a choice of elements.

Lowercase and uppercase letters are considered equivalent; however, no attempt has beenmade to specify both alternatives in every instance. Whitespace characters (as defined inIEEE 488.2, section 7.4.1.2) are optional in many places, and no attempt has been made tospecify “optional whitespace” everywhere it may exist.

1

2

3

4 5

6 7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


5-2 Notation

6 Program HeadersProgram headers are keywords that identify the command. The program headers follow thesyntax described in section 7.6 of IEEE 488.2. Instruments shall accept both upper andlowercase characters without distinguishing between the cases. Program headers consist oftwo distinct types, common command headers and instrument-control headers.

6.1 Common Command and Query HeadersThe common command and query program header syntax is specified in IEEE 488.2 for usewith the IEEE 488.2-defined common commands and queries. Their syntax is:

6.2 Instrument-Control HeadersInstrument-control headers are used for all other instrument commands, typically thoserelated to source and measurement control. The syntax for instrument-control headers is:

The definition of the effect of the colons in an instrument-control header is covered later in“Traversal of the Header Tree.”

6.2.1 Mnemonic Generation RulesEach instrument-control header or keyword has both a long and a short form. A SCPIinstrument shall accept only the exact short and the exact long forms. Sending a header thatis not the short form, nor the complete long form to a SCPI instrument shall cause it togenerate an error. IEEE 488.2 limits the length of a header to 12 characters, including anynumeric suffix that may appear. The long form header is either a single word or anabbreviation of a phrase. The short form header is an abbreviation of the long form header.In order to maintain a consistent set of mnemonics, SCPI defines the rules to generate amnemonic.

The long form mnemonic is generated from either a single word or a phrase. If a single wordis used, then that word becomes the mnemonic. If a phrase is used, then the mnemonic is the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Program Headers 6-1

first letter of each word and the entire last word. For example the phrase “relative velocity”would generate RVELOCITY as the long form command header.

The short form mnemonic is usually the first four characters of the long form commandheader. The exception to this is when the long form consists of more than four characters andthe fourth character is a vowel. In such cases, the vowel is dropped and the short formbecomes the first three characters of the long form. For example, the short form of FREE isFREE, however, the short form of SWEEP is SWE. Note that elsewhere in this document aspecial notation is employed to differentiate the short form keyword from the longform ofthe same keyword. The long form of the keyword is shown, with the short form portionshown in uppercase characters, and the rest of the keyword is shown in lowercase characters.Thus Relative VELocity keyword would be shown as RVELocity.

The short form generation rules imply that phrases such as “Jump Start” and “Jump Stop”are not allowed. Although the long forms JSTART and JSTOP are unique, the short form isthe same in both cases, “JST.” This can be overcome by changing the phrases to “JumpBegin” and “Jump End”, thus creating unique long and short forms. Alternatively, themnemonic JUMP can become an additional level in the tree, allowing STARt and STOP tobecome their own mnemonics, giving JUMP:STARt and JUMP:STOP.

The mnemonic generation rules allow keywords such as “TIME” and “TIMer” at the sametree level, since these are unique in both forms. This is not recommended since an unfamiliaruser may select the wrong function unintentionally. If the two functions have the samenumber and type of parameters, the instrument may not signal an error, further exacerbatingthe situation.

All instrument command headers are allowed a numeric suffix to differentiate multipleinstances of the same structure, such as multi-channel instruments. The numeric suffix isapplied to both the long and short forms. For example, TRIG1 is the short form ofTRIGger1. A numeric suffix of 1 is implied on all instrument command headers that do notexplicitly define a suffix; thus, TRIG is equivalent to TRIG1.

1996As a general rule, a mnemonic should contain no digits. Ending a short or long formmnemonic in a digit creates an ambiguity in separating the mnemonic from any addednumeric suffix.

6.2.2 Building the Command TreeSCPI commands are based on a hierarchical structure. This allows the sameinstrument-control header (keyword) to be used several times for different purposes,providing that the mnemonic occurs in a unique position in the hierarchy. That is, themnemonic does not collide with any other mnemonics at the same level, or one leveldifferent where a default node exists.

Using hierarchical commands should eliminate the need for most multiword mnemonics.The use of multiword mnemonics is discouraged and they should only be used when:

A). The use of the hierarchical scheme would add several additional layers to the tree,and

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-2 Program Headers

B). No further growth at the level of those potentially intermediate nodes isanticipated.

These style guidelines should act as a starting point for creating new commands.

1. The lowest nodes should have the broadest base possible. For example, the centerfrequency command should be FREQuency:CENTer rather than CENTer:FREQuency. Sincecenter is an adjective to the noun frequency, the tree will build with fewer duplicate nodes ifFREQuency:CENTer is chosen.

2. If a function is broad-based and thought of as a separate subsystem, make it a separatesubsystem even if it could properly be classified under another subsystem. For example,bandwidth is a separate subsystem, even though it could be classified under frequency.Bandwidth is generally thought of as a separate subsystem and not classified with otherfrequency commands by customers.

3. Keep the tree as shallow as possible, usually three levels or less. If the tree for a givenimplementation is considerably deeper than it is wide, something may be wrong with thecommand structure.

4. Some nodes may be made optional. When choosing to define a node as the default at aparticular level, be sure that it is the most common choice at that level. Also, check carefullyfor conflicting keywords, since all nodes below a default are effectively promoted by onelevel when the default node is assumed.

5. Some root keywords are optional, depending on the instrument capabilities. In aninstrument which is primarily a source, the root mnemonic [SOURce] is optional. [SENSe]is optional for instruments which are primarily sensors, and [ROUTe] is optional forscanners. This is at the discretion of the device designer. For horizontal compatibilitypurposes, the instrument should accept this node if it is sent as part of a program message.

6. A complete tree path shall be unique within SCPI. Thus, if a path is assigned a particularfunction in any instrument, it must perform the same function in all instruments whichimplement that path.

7. SCPI also discourages the use of different keywords performing the same function. Thisproblem is more difficult because of industry-standard terminology. A good example issetting the output level on a source. Microwave sources call this power level, RF sources useamplitude level, and power supplies use voltage level, yet the function is the same in allthree. One of the tools available is to provide aliases for the function in order to provide bothsets of terminology. Whenever possible, SCPI shall implement as aliases those instanceswhere duplicate names are necessary. Where aliases are used, one term shall be definedwhich is the primary keyword. This keyword shall appear in all instruments.

8. The tree structure shall follow the general form of the instrument model described in the“Command Reference.”

9. Implementations shall use the language constructs described in the “CommandReference,” if a construct exists for the desired feature. If the feature does not exist, the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Program Headers 6-3

designer is responsible for following the life cycle described in an earlier chapter in order tointegrate the capability into SCPI.

10. The value or syntax of a parameter shall not change the type or number of otherparameters in that command. If such a condition is encountered, additional nodes should beadded to the tree.

For example, SCPI shall not include the structures such as: :SYSTem :BEEPer 1,<frequency> :BEEPer 2,<time>

Rather, SCPI uses a structure such as: :SYSTem :BEEPer :FREQuency <numeric_value> :TIME <numeric_value>

11. In general, parameters should only appear at the leaf nodes of the tree. In the undesirableexample below, the command to set a single frequency is placed at a different level to thecommands that are used for setting a range (span) of frequencies. Conceptually equivalentlevel commands are being placed at different levels, leading to possible misconceptions inuse. “Optional” nodes should be created as required to accomplish the same task. Forexample, suppose an instrument superficially wants the following set of commands: FREQuency <numeric_value> :CENTer <numeric_value> :SPAN <Boolean>

The SCPI implementation shall overcome this by creating a node under frequency thatrepresents a command to set a single frequency, such as CW (Continuous Wave). Causing allthe command parameters to be associated with leaf nodes. To retain simple operation as inthe case of setting a single frequency, the CW node can be made optional, providing it doesnot create a keyword conflict. Thus our example becomes: FREQuency [:CW] <numeric_value> :CENTer <numeric_value> :SPAN <Boolean>

Exceptions to this guideline are the AUTO and STEP constructs defined in this document.The AUTO and STEP commands are formed from the leaf node for the value. Otherexceptions may be defined. In these cases, the exception shall be noted in the commandstructure of the language document.

Nodes should not be added to a command tree simply to make the tree have a uniform depth.If the only usable names for a terminal seem not to have any meaning (for instance, VALue),the addition may not be helpful and the tree should be implemented unbalanced. An example

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-4 Program Headers

of this is the SOURce:FREQuency:SPAN node, which has the commands HOLD, LINK,and FULL beneath it.

12. If a particular device function is not alterable or does not exist, then the associated SCPIcommand need not be implemented unless the value of the function is different than thedefined *RST value for that function. If the *RST value is device-dependent, then thefunction need not be implemented. For example:

A. A source that has no amplitude modulation does NOT have to implementAM:STATe OFF because AM:STATe OFF is specified at *RST.

B. A device that only sweeps in frequency (and has no CW function) mustimplement FREQ:MODE SWEep because FREQ:MODE is specified as CW at*RST. However, it is permissable to allow only SWEep as a parameter toFREQ:MODE.

C. A device that produces a single, nonalterable CW frequency of 100 MHZ neednot accept FREQ[:CW] 100 MHZ since the *RST value of FREQ:CW isdevice-dependent.

The intent of this rule is to allow common features with varying complexities to be accessed.This rule specifies the minimum conditions of including a node. However, designers areencouraged to include additional degenerate nodes which are important to their market. Inexample A above, a designer may include AM:STATe OFF as a command, and isencouraged to do so if the instrument is being targeted into markets where AM modulation isa typical feature of instruments in this market.

FL00513. A new command may not be added if there is already a command to control the samefunctionality. This rule insures two instruments will not be needlessly incompatible whendesigners choose arbitrarily among multiple commands available to control a particularfunction. (Notice that SCPI assures compatibility when aliased commands are implementedby making one path required). A new command may not be added to the standard unless itcan be shown to control functions not controlled by any existing commands. The followingguidelines may help in determining whether a command controls new functionality orrepresents illegal duplication, and guide selection of one command over another.

Does the setting of the new command affect the measurement result returned?

Signal preconditioning commands (like ATTenuator, FILTer, GAIN) appear in the INPutsubsystem and in SENSe. These commands are not aliases; The setting ofINPut:ATTenuator changes the reported signal level, while SENSe:ATTenuator would becompensated for so the reported signal level would not be affected. Since these commandsaffect the returned value differently, they control different functions and are not duplicatecontrols.

Does the new command control a function with a different purpose than any existingcommand?

Numerical post-processing commands (like WINDow, AVERage, SMOothing) appear in thesensor and also in CALC. The function properly belongs in the sensor when its purpose is to

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Program Headers 6-5

enhance accuracy or correct for artifacts introduced by the sensor. The function belongs inCALCulate when its purpose is to change the presentation of the data or provide analyticaltools not directly related to measurement.

Does the command control measurement hardware?

Some functions (like SMOothing) may be performed directly on the signal in hardware or insoftware after A/D conversion. While this rule can be difficult to apply, the fact that acommand controls measurement hardware often indicates that it belongs in the sensor ratherthan CALCulate.

Does it make sense if the same operation may be done twice?

Another way to tell that a command controls new functionality is if it makes sense for thecontrolled function to appear twice in a single instrument. The AVERage subsystem is agood example; it is not unreasonable to build an instrument that averages several readings toimprove the accuracy of the measurement, and also provides averaging as a statisticalfunction in the CALCulate subsystem.

14. In general, SCPI commands which are only events without a query form do not have anyparameters. Including a parameter might mislead a user into believing the value could bequeried as most commands in SCPI have a query form, see 6.2.3.

HP082An exception to this guideline is when the action is performed on a named object within theinstrument and these objects cannot be enumerated. For example, <file_name>,<trace_name>, and <data_handle> are objects whose values cannot be entirely listed withinSCPI. The user can create any number of <file_names> or <trace_names>. The signalrouting concepts in SCPI allow a large number of possible <data_handles>.

HP082

6.2.3 QueriesAll commands, unless otherwise noted, have an additional query form. As defined in IEEE488.2, a query is a command header with a question mark symbol appended (for example,FREQ:CENT?). When a query form of a command is received, the current setting associatedwith the command is placed in the output buffer. Query responses do not include thecommand header. Execution of a query form has no side effects. It shall not cause anysettings or couplings within the instrument to change. An exception is in MEASurementsubsystem, where instrument settings may change as a result of the measurement.

HP095Both the command and query forms shall be implemented unless a comment or noteindicating otherwise appears in the keyword summary. Even when a command accepts onlya single selection, both the command and query forms shall still be implemented. A note ofthe form “[event; no query]” or “[no query]” indicates that only the command form and notthe query form shall be implemented. A note of the form “[query only]” indicates that onlythe query form and not the command form shall be implemented.

When character data is used for a parameter, both longform and shortform values shall berecognized. If the command has a query form with character response data, the shortformvalue is always returned.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-6 Program Headers

When numeric parameters are queried, the result shall be returned in fundamental unitsunless otherwise specified or requested. When several different units may be consideredfundamental (for example, dBuV or dBm), the units of the returned result shall bedocumented in the query response description for the command. A query may have a related:UNITs node to change the default units of the accepted or returned value, where this existsthe coupling shall be clearly indicated in the command description.

6.2.4 Traversal of the Header TreeIEEE 488.2 allows the designer some discretion on how compound headers are handledwithin the rules of section 7.6.1.5. SCPI imposes additional requirements regarding how acompound command is parsed.

Multiple <PROGRAM MESSAGE UNIT> elements may be sent in a <PROGRAMMESSAGE>. The first command is always referenced to the root node. Subsequentcommands, however, are referenced to the same tree level as the previous command in amessage unit. SCPI parsers shall follow the example presented in IEEE 488.2, section A.1.1.A SCPI parser shall NOT implement the enhanced tree walking implementation described insection A.1.2.

For example, if a hypothetical instrument had the command tree: FREQuency :STARt <numeric_value> :STOP <numeric_value> :SLEW <numeric_value> :AUTO <Boolean> | ONCE :BANDwidth <numeric_value> POWer :STARt <numeric_value> :STOP <numeric_value> BAND A|B|C|D

Then the following commands shall behave as described:

FREQ:STAR 3 MHZ;STOP 5 MHZ<nl> shall set the start frequency to 3 MHzand the stop frequency to 5 MHz.

FREQ:STAR 3 MHZ;:FREQ:STOP 5 MHZ<nl> shall set the start frequency to 3MHz and the stop frequency to 5 MHz.

FREQ:STAR 3 MHZ;POW:STOP 5 DBM<nl> may set the start frequency to 3MHz and shall generate an error because POW is not a node at the current parserlevel.

FREQ:STAR 3 MHZ;SLEW:AUTO ON<nl> shall set the start frequency to 3MHZ and couple the frequency slew rate.

FREQ:SLEW:AUTO ON;STOP 5 MHZ<nl> may couple the slew rate and shallgenerate a command error since the coupling command is not at the same level asthe stop command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Program Headers 6-7

FREQ:SLEW 3 MHZ/S;AUTO ON<nl> may set the frequency slew rate to 3MHZ/S and shall generate a command error because :AUTO is not at the samelevel.

FREQ:START 3 MHZ;BAND 1 MHZ<nl> shall set the start frequency to 3 MHzand the bandwidth to 1 MHz.

FREQ:START 3 MHz;:BAND A<nl> shall set the start frequency to 3 MHz andselect band A.

FREQ:SLEW:AUTO ON;3 MHZ/S<nl> may couple the frequency slew rate andshall generate a syntax error, because IEEE 488.2 specifies that headers must besent with each command.

Default nodes in the tree shall not alter the header path of the parser in order to follow theIEEE 488.2 rules for compound headers. IEEE 488.2, section 7.6.1.5 makes no mention ofdefault nodes, so adding something to the header path is not allowed. For example, if ahypothetical instrument had the command tree: DISPlay [:STATe] <Boolean> :DATA <string>

Then the following situations would have these results:

DISP:STAT ON;DATA “Hello, world!”<nl> shall turn the display on and display“Hello, world!”.

DISP ON;DATA “Hello, world!”<nl> may turn the display on and shall flag anerror (assuming that DATA is not a root mnemonic).

6.2.5 Multiple Capabilities and Numeric Keyword SuffixesMany instruments provide multiple capabilities, by duplicating internal functional blocks.One example is an instrument that can display more than one measurement at a time.Another example is an instrument that can make a particular measurement on one of severalinput channels. SCPI provides a mechanism to address this duplicate functionality whileretaining the same hierarchy for each duplication.

6.2.5.1 Single Instrument with Many Electrical PortsWhen only electrical ports (front panel terminals) are involved, the <channel_list> notationis sufficient to describe the measurement connection. An instrument which needs to selectone or more of several input terminals can be logically modeled as a simple instrument withone set of inputs connected to a scanner (signal multiplexor).

6.2.5.2 Multiple Identical CapabilitiesWhen an instrument has several independent measurement channels (or other capabilities,such as displays or sources), the selection of which to use is designated by a numeric suffixattached to a program mnemonic. If the suffix is absent, the command is treated as beingdesignated for capability number one. In this way, channel one of a multiple channelinstrument can accept the same commands as a single channel instrument to allow for

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-8 Program Headers

upward compatibility. Further, adding multiple channels or capabilities to an instrumentclass where multiple channels were not anticipated becomes possible.

The node that contains the numeric suffix is the one where the multiple capability occurs.This may be at any level of the tree: root, intermediate or terminal node. As an example,OUTP5:MOD3:FM2 would specify the second FM signal component of the thirdmodulation signal on the fifth output channel.

Devices which implement multiple channels/capabilities shall recognize nodes which do nothave numeric suffixes and treat them as channel/capability 1. Instruments with a singlechannel/capability are not required to accept a numeric suffix. This allows for upwardcompatibility.

6.2.5.3 Logical InstrumentsA complex instrument such as a VXI card cage can be logically modeled as separateinstruments, each with its own (secondary) bus address. For example, common functions forall instruments can be located at secondary address 00, and otherwise each instrumentresponds individually to IEEE 488.2 commands. This requires that each logical instrument(card) implement its own status model and I/O buffers.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Program Headers 6-9

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-10 Program Headers

7 ParametersSCPI uses the parameter forms described in IEEE 488.2, section 7.7, with some additionalrestrictions. Also note that SCPI specifies the values for all commands upon receipt of*RST. In some cases, these reset values are device-dependent, but all measurementparameters must be set to some deterministic value for that particular instrument, which inturn must be documented in the instrument manual.

7.1 Character Program DataWhere possible, the same truncation rules are used for parameters as for headers. However,in many cases industry standards take precedence. For example, IDC is a better choice forDC current than anything SCPI rules would define, simply because it is an existing standardwith wide acceptance. In addition, several character program data forms are predefined asextensions of <DECIMAL NUMERIC PROGRAM DATA>.

7.2 Decimal Numeric Program DataNumeric elements shall be used only for representing numeric quantities. They shall not beused for selecting functions on a “One of N” position switch.

Implementations shall accept numeric data as described in IEEE 488.2, section 7.7.2.4.However, any number which exceeds +-9.9 E 37 shall generate an execution error (-222,“Data out of range”). Numbers shall be rounded to the closest “correct” value that theinstrument accepts without error. This document does not define the value a parameter is setto if an out-of-range value is received.

7.2.1 <numeric_value> DefinitionThe decimal numeric element is abbreviated as <numeric_value> throughout this document.This is different from the <NRf> described in section 7.7.2.1 of IEEE 488.2 in several ways.

Several forms of <CHARACTER PROGRAM DATA> are defined as special forms ofnumbers. These are: MINimum, MAXimum, DEFault, UP, DOWN, Not A Number (NAN),INFinity, and Negative INFinity (NINF). Individual commands are required to accept MINand MAX. DEFault, UP, DOWN, NAN, INFinity, and NINFinity may be implemented at thediscretion of the designer, in which case it shall be noted in the instrument documentation.Where an optional form is accepted, it will be noted in the command description.

A <non-decimal numeric> (IEEE 488.2, section 7.7.4), a <numeric_expression>, or a<label> is part of <numeric_value> if an instrument implements these features.

7.2.1.1 DEFaultThe special <numeric_value> parameter DEFault may be provided to allow the instrument toselect a value for a parameter. When DEFault is sent, the instrument shall select a valuewhich is deemed to be convenient to the customer. The setting may be device-dependent, orit may be defined as part of this standard. The use of DEFault is optional on acommand-by-command basis. Individual commands shall document where DEFault isrequired.

For example, to use the SYST:TIME command to set a device’s clock ahead one hour(Daylight Savings Time), a program might send SYST:TIME UP,DEF,DEF<nl>.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Parameters 7-1

Another example is found in the MEASure commands. The syntax of the command whichmeasures DC voltage is:

MEASure:VOLTage:DC [<expected value>[,<resolution>]]

The MEASure command specifies that parameters are defaulted from the right and that anyparameter may be defaulted by using DEFault in place of the parameter. The followingcommand would measure DC voltage, defaulting the range to an instrument dependent value(possibly autorange), but specifying the resolution at 0.001 Volt:

MEASure:VOLTage:DC DEFault,0.001V

7.2.1.2 MINimum|MAXimumThe special form numeric parameters MINimum and MAXimum shall be provided whichassume the limit values for the parameter. The maximum and minimum shall be queryableby sending <header>? MAXimum|MINimum. The MAXimum value refers to the largestvalue that the function can currently be set to, and MINimum refers to the value closest tonegative infinity that the function can be currently set to.

Some commands have multiple parameters. The query form of these commands returns a listof values representing the current value of each of the parameters, in the order of theirnormal occurrence in a program message. If a MINimum/MAXimum query of multipleparameters is allowed, the keywords MINimum and MAXimum must occur as many times inthe query as there are parameters. MINimum requests that the instrument return the legalvalue which is closest to negative infinity for the parameter; MAXimum requests the legalvalue which is closest to positive infinity.

For example, suppose an instrument implements the SYST:TIME command, which requiresthree parameters, and allows MIN/MAX queries on this command. The following queriesshall have these results:

SYST:TIME?<nl> shall return the current setting of the time-of-day clock in theinstrument.

SYST:TIME? MAX,MAX,MAX<nl> could return 23,59,59.

SYST:TIME? MAX<nl> shall set an error (-109, “Missing parameter”), sincethree parameters are required and only one was sent.

7.2.1.3 UP/DOWNAn instrument may optionally allow the use of steps for some or all of its numeric entry. Ifsteps are used, the keywords UP and DOWN shall be used as numeric parameters whichperform stepping. Steps may be adjustable through the step node for each individualparameter.

The instrument may step a parameter when UP or DOWN is received in lieu of a numericvalue. This capability is optional. However, if the capability is implemented, the deviceshall include a node for each command which accepts step parameters. This node willspecify the step. The step may either be a fixed linear size or a logarithmic numberrepresenting number of decades/step.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-2 Parameters

7.2.1.3.1 STEP Subsystem Command SyntaxThe form of the step subsystem is as follows:

:STEP [:INCRement] <numeric_value> :PDECade <numeric_value> :MODE LINear|LOGarithmic|L125|L13 :AUTO <Boolean>|ONCE

7.2.1.3.2 [:INCRement] <numeric_value>This command controls the step size in absolute units when STEP:MODE LINear is selected.

At *RST, this value is device-dependent.

7.2.1.3.3 :PDECade <numeric_value>This command controls the number of steps per decade when STEP:MODE LOGarithmic isselected.


7.2.1.3.4 :MODE LINear|LOGarithmic|L125|L13This command controls the linearity of steps. The various parameters have the followingmeanings:

LINear: Steps are a fixed value added to or subtracted from the current value ofthe parameter.

LOGarithmic: Steps are placed at points spaced logarithmically. If the currentvalue of the function is x, the value of the function after executing an up shall bedetermined by the following formula:

10

log10(x)∗STEP:PDECade+ 1STEP:PDECade

and the value of the function after executing a DOWN shall be determined by:

10

log10(x)∗STEP:PDECade− 1STEP:PDECade

where is the symbol for floor, and is the symbol for ceiling.DT

L125 — Steps are determined by the sequence ... 0.1,0.2,0.5,1,2,5,10,20,50,100 ...

Executing UP will set the value of the function to the next higher value in the sequence.Executing DOWN will set the value of the function to the next lower value in the sequence.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Parameters 7-3

L13 — Steps are determined by the sequence ... 0.1,0.3,1,3,10,30,100 ...

Executing UP will set the value of the function to the next higher value in the sequence.Executing DOWN will set the value of the function to the next lower value in the sequence.


7.2.1.3.5 :AUTO <Boolean>|ONCEThe step mode and increment is coupled to other instrument settings and physical inputswhen AUTO is ON.

7.2.1.3.6 STEP Subsystem Examples FREQ:CENT:STEP 5 MHZ<nl> FREQ:CENT UP<nl>

sets the center frequency step to 5 MHz, and then increments the current value by 5 MHz.

BAND:RES 1MHZ<nl> BAND:RES:STEP:MODE LOG;PDEC 3<nl> BAND:RES UP<nl>

The above sequence would specify a logarithmic step, set three steps/decade, and thenincrement the resolution bandwidth by 1/3 decade (logarithmic) to a final value of 2.154MHz.

BAND:RES 1MHZ<nl> BAND:RES:STEP:MODE L125<nl> BAND:RES UP<nl>

The above sequence would specify a 125 logarithmic sequence, and then increment theresolution bandwidth to the next step in the sequence to a final value of 2.0 MHz.

7.2.1.4 INFinity and Negative INFinity (NINF)A special case is made for infinity. Positive infinity is represented as 9.9 E 37. Negativeinfinity is -9.9 E 37. Instruments shall accept numbers within this range as valid numericdata. They shall also limit response data to this range. If a valid instrument setting is infinityor negative infinity, the values 9.9 E 37 and -9.9 E 37 shall be accepted and returned torepresent positive and negative infinity respectively, and on input, the implementation shallaccept INFinity as an alias for positive infinity, and NINFinity as an alias for negativeinfinity.

The numeric values for positive and negative infinity were chosen so that they fit into a32-bit IEEE 754 floating point number. This allows easy implementation using standardtools in all popular languages and operating systems. Note that this does not limit thenumeric resolution. These values are larger than any quantities used or anticipated ininstruments.

7.2.1.5 Not A Number (NAN)Not a number is represented as 9.91 E 37. Not a number is defined in IEEE 754. Typicalapplications are dividing zero by zero or subtracting infinity from infinity. Not a number is

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-4 Parameters

also used to represent missing data. A typical application is when a portion of a trace has notbeen acquired yet. On input, devices shall accept NAN as an alias for not a number.

The numeric value for NAN was chosen so that it can be represented as a 32-bit IEEE 754floating point number. This allows easy implementation using standard tools in all popularlanguages and operating systems. Note that this does not limit the numeric resolution. Thisvalue is larger than any quantities used or anticipated in instruments.

7.2.2 Unit SuffixesThe <DECIMAL NUMERIC PROGRAM DATA> may be followed by an optional suffix.All parameters which have associated units shall accept a suffix. Only suffixes appropriatefor the command should be accepted. All suffixes must include the associated unit. SeeIEEE 488.2, 7.7.3, <SUFFIX PROGRAM DATA>, for a complete discussion of this topic.

Suffixes must accept multipliers except in cases where the multiplier is illogical, such asdBm or PCT. Table 7-2 in IEEE 488.2 lists the allowed multipliers. If any of the multipliersare allowed with a suffix, then all the multipliers shall be interpreted properly. Compoundsuffixes are allowed.

If a suffix is included, the suffix and associated multiplier, if implemented, are applied to theparameter. If the suffix is omitted, default units are used. The default unit is determinedeither from the :UNIT subsystem as described in 7.5 of Syntax & Style and in Chapter 23 ofthe Command Reference, or it is the fundamental unit associated with the parameter.Fundamental units are either described in the appropriate subsystem or in the one shown inIEEE 488.2, table 7-1.

7.3 Boolean Program DataThe form <Boolean> is used throughout this document as a shorthand for the formON|OFF|<NRf>. Boolean parameters have a value of 0 or 1 and are unitless.

On input, an <NRf> is rounded to an integer. A nonzero result is interpreted as 1. Thisalgorithm is the same as the one described in IEEE 488.2, section 10.25.3.

The <CHARACTER PROGRAM DATA> elements ON and OFF shall be accepted on inputfor increased readability. ON corresponds to 1 and OFF corresponds to 0.

Queries shall return 1 or 0, never ON or OFF.

7.4 Coupling of FunctionsThere are two forms of coupling: functional and value. A coupling occurs when sending acommand changes the value associated with another command. In general, functionalcouplings are discouraged except in the MEASure subsystem. Value couplings are allowedif the coupling equations are well specified.

Some functions may have the ability to be decoupled. If functions can be decoupled, theability to recouple them shall also exist. If a function cannot be decoupled, then a node to setits value shall not exist, or shall be implemented as query-only. If a node is settable undersome conditions, then the node may exist.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Parameters 7-5

Another level in the tree is used to control coupling. The keyword AUTO shall be used tocontrol coupling. For example, the command to couple resolution bandwidth would be:

BAND:RES:AUTO ON

Setting a value explicitly for a function shall cause the function to be decoupled (:AUTOOFF), if decoupling is possible. Otherwise an error shall be generated.

Selecting :AUTO ONCE shall cause the function to select the most appropriate value forcurrent conditions (range, signal level, etc), and then be decoupled. A subsequent query ofan :AUTO? will always return 0, since ONCE is an event which leaves the function inAUTO OFF mode.

7.4.1 Functional CouplingFunctional coupling occurs when a command causes side effects in the basic operatingmode of the device. An example is a command which sets the start frequency and also startsa sweep.

If a command which invokes a functional coupling is necessary, the instrument shall alsoimplement primitive commands which do not have functional couplings. The instrumentmay then implement a complex command which is described as a combination of theseprimitive commands. This complex command may contain functional couplings, and mustdocument the sequence of primitive commands used in its programming documentation.

For example, if a source needs a command which sets the AM modulation level, and whichhas the side effect of turning the modulation ON, the following could be implemented:

Primitives:AM :STATE <Boolean> [:DEPTh] <numeric_value>

Complex command added:AM :SDEPth <numeric_value>

Where AM:SDEPth is defined in the manual as:AM:DEPth <numeric_value>; :STATe ON

7.4.2 Value CouplingThe other form of coupling is called value coupling, which is allowed in SCPI. Values arecoupled when a command changes the value of other numeric settings in the instrument. Thecoupling relation would follow device-dependent equations. For example, bandwidth in areceiver may be coupled to the frequency span. The individual command descriptions definethese coupling equations.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-6 Parameters

Groups of functions may be coupled in complex ways which affect the values for each other.For example START, STOP, CENTER, and SPAN are all value-coupled. CENTER is thearithmetic average of START and STOP. SPAN is the difference between START andSTOP. Changing any one affects the value of two others.

7.4.3 Automatic CouplingA special type of coupling is the automatic coupling. This is when the device provides analgorithm to select the value of a parameter. This algorithm could be based upon physicalinputs or other settings. When it is desirable to turn this algorithm on and off, the keywordAUTO is added. The AUTO command may accept parameters of ON|OFF|ONCE. ONenables the instrument algorithm. OFF disables the instrument algorithm. ONCE causes thealgorithm to be employed once, changing the associated parameter, and then reverting toAUTO OFF.

7.5 Units of Measure and SuffixesMost of the information on units and suffixes is specified in IEEE 488.2, section 7.7.3.However, further clarification is needed for units of power and amplitude, and for unitlessquantities.

7.5.1 Units of Amplitude and Power

The fundamental unit of linear power is the Watt (W).

The fundamental unit of linear amplitude is the Volt (V).

The fundamental unit of logarithmic power is the dBm.

The fundamental unit of logarithmic amplitude is the dBV.

Industry practices have caused other units to become widely used in various disciplines,particularly the units of uV, dBuV, dBuW and dBmV. Furthermore, many instruments covera broad spectrum of applications where different units are considered the standard.Therefore, instruments which implement commands whose parameters might be expressed inseveral different amplitude or power units shall provide the following means of setting andmeasuring amplitude and power functions:

If the unit is not specified, the default unit shall be that specified with a command in theUNIT subsystem, or a UNIT command in the appropriate sub-tree. The *RST values ofsettings in the UNIT subsystem shall be device-dependent. However, if a *RST unit isdifferent than the specified default unit, or is a logarithmic unit, then the command in theUNIT subsystem for that unit must be implemented.

If a suffix is sent with an <NRf>, the unit corresponding to that suffix shall override thedefault unit for that parameter.

If an instrument accepts units from one of the classifications described above, it must acceptall suffixes of that classification. For example, if an instrument accepts Watts, it must alsoaccept uW, mW, etc. This includes all suffix multipliers described for that unit in IEEE488.2. However, it may, but is not required, to accept Volts as a unit. In instrument whichaccepts both requires a defined impedance for the conversion

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Parameters 7-7

(Power= Voltage2

Impedance)

either explicitly through an input or output impedance command or implicitly if theimpedance of the instrument is known and fixed. A further restriction, is that if aninstrument accepts logarithmic units, it shall also accept the comparable linear unit. Forexample, an instrument which accepts dBms must also accept Watts, MW, UW, etc. Forexample:

POW:UNIT DBUV<nl>POW:LEV 50<nl>

shall set the amplitude level to 50 dBuV.

POW:UNIT DBM<nl>POW:LEV 5V<nl>

would set the power level to 5 Volts.

Since some instruments are used in applications where both power and voltage units areappropriate, the system’s impedance may be important to the user. This impedance isneeded to do the conversion between power and voltage (and maybe even current). Allinstruments are encouraged to provide a node for at least querying this impedance. The nodeshall be called :IMPedance, and will generally appear under the INPut or OUTPutsubsystem. Open circuits shall be expressed by setting IMPedance INFinity. It is thereforepossible to express output power in Volts:

POW:UNIT V<nl>OUTP:IMP 50 OHM<nl>POW:LEV 5<nl>

would set the power level to 5 Volts into a 50 Ohm load, or 0.5 Watt.

It is also sometimes necessary to determine which amplitude measurement is being made.Therefore, a measurement qualification may be appended to the suffix. The suffixappendices are described as:

PK: Peak amplitude

PP: Peak-to-peak amplitude

RMS: RMS amplitude

If no suffix appendix is specified, the default is device-dependent. However, all instrumentsshall accept the suffix appendix for all types they support.

For example, a voltmeter which measures RMS voltage shall accept the suffixes V andVRMS. A function generator which outputs peak voltage would accept the suffixes V andVPK. An RF signal source might accept dBUV, dBUVRMS and dBUVPK.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-8 Parameters

7.5.2 Expressing Unitless QuantitiesThe ratio of two linear quantities shall default to a unitless ratio (A/B). For example, if theinput power for a system is 5 Watts, and the output power is 20 Watts, the power gain =20W/5W = 4.

The difference between two logarithmic quantities shall be expressed in dB. For example ifthe input power of a system is 3 dBm and the output power is 5 dBm then the gain of thesystem is 5 dBm-3 dBm=2 dB.

Under exceptional conditions other units may be used for the ratio of two quantities. A validexception would be if a standards-setting organization (Bell, CCITT, military, IEEE, IEC,etc.) specifies that a measurement shall be made using a special unit like PCT (percent).

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Parameters 7-9

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-10 Parameters

8 Expressions

8.1 FunctionDIF01TWV41CThe <EXPRESSION PROGRAM DATA> described in IEEE 488.2 is more tightly defined

in this section. SCPI defines five types of expressions, numeric expressions, channel lists,numeric lists, Data Interchange Format (dif) expressions, and instrument specifierexpressions. The dif expressions are defined in Volume 3, “Data Interchange Format.”Instrument specifiers are defined in Volume 4, “Instrument Class Applications.”

Other expression types may be added in future releases of this document, including but notlimited to logical expressions, trigger expressions, and sequence expressions. Other uses ofIEEE 488.2 expressions are legal, and may be documented in the individual commanddescriptions.

8.2 UsageDIF01The use of expressions is optional in SCPI. For expression types defined in this section, it is

permissible to use any subset. Only expression types which are required by a particularcommand may be recognized as parameters of that command.

8.3 SyntaxDIF01Inside expressions, white space as defined in IEEE 488.2, section 7.4.1.2 is allowed between

any lexical elements. For expressions defined in this section, a lexical element is defined asany operator, punctuation, or IEEE 488.2 syntactic element. For a <dif_expression>, spacesmay appear around block names, block modifiers, keywords, or value types. See DataInterchange Format, Section 3.2. Note that explicit white space may be required to separatelexical elements. No semantic meaning should be attached to the case of alpha characters

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Expressions 8-1

used in operators. For example, the following are instances of the same operator: AND and And

8.3.1 Numeric ExpressionA numeric expression is a collection of terms which evaluates to a trace, number, array, orother data element.

8.3.1.1 Syntax TEK002Where <numeric_operator> is defined as:

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


8-2 Expressions

Where <unary_numeric_operator> is defined as:

Unary operators should not be used with signed numbers.

Where <variable> or <trace_name> is defined as the diagram shows:

8.3.1.2 Precedence RulesExpressions shall be evaluated according to the following precedence rules: 1. Enclosed by parentheses 2. Unary operators (+ and -) 3. ^(exponentiation) 4. * (multiplication), / (division), MOD and DIV 5. + (addition) and - (subtraction) 6. NOT 7. AND 8. OR and EXOR 9. Left to right

8.3.1.3 SemanticsAs stated in the syntax diagram, expressions may contain terms which are numbers, traces,variables, or expressions.

Elements in a numeric expression are promoted to the size and type of the most complexelement, and the result of the expression is of that type. That is, an expression containing a<trace_name> will be evaluated according to the rules for arithmetic on traces, and the resultwill be a trace. If an expression contains both a <trace_name> and scalar data, a trace iscreated with all elements set to the value of the scalar data before arithmetic is performed.For example, if TREF is a trace_name, the expression (TREF-3) results in a trace the samesize as TREF, with each data element lower by three.

8.3.2 Channel ListsChannel lists are used to specify electrical ports on an instrument. They are typically used forsignal routing either in a standalone switch box or in an instrument with multiple inputchannels. An instrument with multiple channels may or may not do any signal switching as

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Expressions 8-3

the result of a channel list. Completely separate sensing channels are allowed, but mayappear to the language the same as channels which are switched.

A channel list may appear in measurement, configuration, and other such commands. Forexample, MEAS:VOLT? (@1,3,4:6) says measure the voltage on channels 1, 3, and 4through 6. Whether the measurements are performed simultaneously or in the order in thelist is unspecified. Channel lists are also used by the ROUTe subsystem, “CommandReference,” 15.1.

The syntax for a <channel_list> is:

Where <channel_range> is defined as:

Where both instances of <channel_spec> must contain the same number of dimensions.

Where <module_channel> is defined as:

KI004

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


8-4 Expressions

Where <channel_range> indicates all the channels from the first number through the secondnumber and where <module_specifier> is defined as:

Where <channel_spec> is defined as:

The number of dimensions in a <channel_spec> is one greater than the number ofoccurrances of the ‘!’ character in the <channel_spec>

When a <channel_range> of dimension greater than one is scanned, the right-most index ofthe <channel_spec> varies most rapidly.

The multidimensional channel range is to be considered as a list of single dimension channelranges. For example, (@1!1:2!3) means dimension 1 (row) ranges from 1 to 2 and dimension2 (column) ranges from 1 to 3. If the size of the matrix in this example is 2X8, then the range(@1!1:2!3) does not mean: row 1, column 1 through 8 and subsequently row 2, column 1through 3, but row 1, column 1 through 3 and next row 2 column 1 through 3. This methodprovides a functional compatibility between commands sent to matrix switches withdifferent row lengths.

PH020,DTChannel lists are order sensitive. For example: SCAN (@5:3) means close 5, 4, 3 in order. SCAN (@1!1:2!3) means close 1!1, 1!2, 1!3, 2!1, 2!2, 2!3 in order. SCAN (@1!3:2!1) means close 1!3, 1!2, 1!1, 2!3, 2!2, 2!1 in order.

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


Expressions 8-5

PH020,DT

8.3.3 Numeric ListsA numeric list is a an expression format for compactly expressing numbers and ranges ofnumbers in a single parameter.

The syntax for <numeric_list> is:

Where <numeric_range> is defined as:

The range is inclusive of the specified numbers.

1

2

3

4 5

6

7

8

9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


8-6 Expressions

9 Status ReportingSCPI requires the status mechanism described in chapter 11 of IEEE 488.2, including fullimplementation of the Event Status register structure.

Ed changeA SCPI device shall include the SCPI-defined OPERation status register and QUEStionabledata/signal status register with the associated condition, event, and enable commands. InFigure 9-1 on the following page, “Minimum Status Reporting Structure Required by SCPI”,a pictorial representation is given that shows the core of the SCPI-required status reportingcapability. Additional requirements are established for instruments that support eithermultiple logical INSTruments or the expanded capability TRIGger model.

TK046In general, a status register should fit into a 16-bit integer with the most-significant bitalways zero (positive logic).

In the figures in this chapter, an elongated box is used to represent the “Status DataStructure-Register Model,” which is defined in IEEE 488.2. SCPI consists of condition,event, enable and optional transition registers. Two concentric circles with a cross throughthe center one indicates a logical summing.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Status Reporting 9-1

Figure 9-1 Minimum Status Reporting Structure Required by SCPI

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


9-2 Status Reporting

9.1 The Device-Dependent Register ModelThe Device-Dependent Register model follows the structure described in IEEE 488.2,section 11.4.2. The transition filter described in figure 11-6 is actually a pair ofprogrammable transition filters which are described below.

The commands which access these registers are described in the “SCPI LanguageDescription.”

If the Error/Event Queue Summary is reported in the Status Model, then bit 2 of the StatusByte shall be used to reflect the Empty/Non-Empty status of the queue. A bit value of 1indicates the queue is not empty. See the SYSTem:ERRor subsystem, Command Reference,21.8.

TK012

9.2 Transition FiltersTransition filters are described in IEEE 488.2, section 11.4.2.2.1. SCPI allows the use ofprogrammable transition filters. When transition filters are used, SCPI requires the use ofseparate positive and negative transition filters. A positive transition filter allows an event tobe reported when a condition changes from false to true. A negative filter allows an event tobe reported when a condition changes from true to false. Setting both positive and negativefilters true allows an event to be reported anytime the condition changes. Clearing bothfilters disables event reporting.

The contents of transition filters are unchanged by *CLS and *RST.

9.3 Operation Status RegisterThe OPERation status register contains conditions which are part of the instrument’s normaloperation.

The definition of each of these bits (condition register) is as follows:

0-CALibrating — The instrument is currently performing a calibration.

1-SETTling — The instrument is waiting for signals it controls to stabilizeenough to begin measurements.

2-RANGing — The instrument is currently changing its range.

3-SWEeping — A sweep is in progress.

4-MEASuring — The instrument is actively measuring.

5-Waiting for TRIG — The instrument is in a “wait for trigger” state of thetrigger model.

6-Waiting for ARM — The instrument is in a “wait for arm” state of the triggermodel.

7-CORRecting — The instrument is currently performing a correction.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8-12 available to designer

13-INSTrument Summary Bit One of n multiple logical instruments isreporting OPERational status.

14-PROGram running — A user-defined programming is currently in the runstate.

15 always zero

9.4 QUEStionable Data/Signal Status RegisterThe QUEStionable status register set contains bits which give an indication of the quality ofvarious aspects of the signal.

A bit set in the condition register indicates that the data currently being acquired orgenerated is of questionable quality due to some condition affecting the parameter associatedwith that bit. For example, if the FREQ bit were set, this would mean that the frequencyaccuracy of the signal was of questionable quality.

Ed ChangeThe frequency bit might, in turn, have a register set associated with it, further refining theerror into device-dependent conditions such as loop unlocked, oven cold, or reference signalmissing. This layering of registers is called “fan-out”. See Figure 9-2 for an illustration ofthis technique. The device designer should be aware that adding registers to the status modelincreases complexity. At the same time, it may be the only way to communicate timesensitive status information to the instrument controller.

TK048Bit 14 is defined as the Command Warning bit. This bit indicates a non-fatal warning thatrelates to the instrument’s interpretation of a command, query, or one or more parameters ofa specific command or query. Setting this bit is a warning to the application that the resultantinstrument state or action is probably what was expected but may deviate in some manner.

Figure 9-2 Hierarchical Expansion of the QUEStionable Status Register

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK048For example, the Command Warning bit is set whenever a parameter in one of theMeasurement Instruction commands or queries is ignored during execution. Such aparameter may be ignored because it cannot be specified by a particular instrument.

Bit 13, INSTrument summary, is described later in this chapter in association with multiplelogical instruments.

Bits in both OPERation and QUEStionable status registers may be redefined by theapplication programmer. This optional feature allows an application program to configuretwo registers in whatever form it likes. Any error or event number from the entire pool oferrors/events the instrument can generate may be mapped into any bit of the OPERation orQUEStionable register.

For example, an application program controlling a voltmeter may choose to map VOLTageevent X, VOLTage event Y and VOLTage event Z directly into the QUEStionable registerso that it has more direct access to them. Another purpose for this feature is to minimize theneed for adding complex hierarchical registers to the status model. The mapping iscontrolled by the STATus:OPERation:MAP and STATus:QUEStionable:MAP commands.

9.5 Multiple Logical InstrumentsA SCPI device that supports multiple logical instruments may include an INSTrumentsummary status register and an individual instrument ISUMmary for each logical instrument.

Figure 9-3 Expansion of the INSTrument Summary Bit for Multiple Logical Instruments

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Ed ChangeThe ISUMmary registers shall report to the INSTrument register, which in turn shall reportto bit 13 of the QUEStionable or OPERation status register. This is shown pictorially inFigure 9-3, “Expansion of the INSTrument Summary Bit for Multiple Logical Instruments.”Such a multilogical instrument may also expand the QUEStionable and OPERation registerin the manner shown in Figure 9-4, “Expansion of QUEStionable Register for MultipleLogical Instruments.”

Ed Change

Using such a status register configuration allows a status event to be cross-referenced byinstrument and type of event. Further, when using a single logical instrument, the statusstructure is seen to behave in a manner that is directly compatible with a single physicalinstrument of the same capability. This affords upward compatibility.

For multiple logical instruments, the INSTrument register indicates which instrument(s)have generated an event. The ISUMmary register is a pseudo-questionable status register for

Figure 9-4 Expansion of QUEStionable Register for Multiple Logical Instruments

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



a particular logical instrument. There may be two INSTrument registers for each logicalinstrument in the device. For each event type, such as VOLTage, all the events may be ORedtogether from each logical instrument to provide a summary by event type to theQUEStionable status register.

9.6 Status Structure for the Expanded Capability Trigger ModelEd ChangeFor instruments that implement the expanded capability trigger model, those instruments

may implement status structures to indicate the exact point in which the wait for ARM orTRIGger is occurring. If multiple SEQuences are employed, then the status structure shallexist to indicate in which SEQuences the wait for ARM or TRIGger is occurring. If multipleARM LAYers are employed, then the status structure shall exist to indicate in which LAYerthe wait for ARM or TRIGger is occurring. Figure 9-5, “Expansion of the OPERationalRegister for the Expanded Capability Trigger Model,” shows the structure for an instrumentthat employs more than one TRIGger sequence, more than one ARM sequence, and multipleARM LAYers.

* The use of Bit 15 is not allowed since some controllers may have difficulty reading a 16 bitunsigned integer. The value of this bit shall always be 0.

** The extension bit is used, where required, to summarize the events in INSTrument15 and up.The extension of the status structure shall conform to IEEE 488.2

Figure 9-5 Expansion of OPERation Register for the Expanded Capability Trigger Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



10 *RST ConditionsAll instruments shall return to a known configuration when the IEEE 488.2 *RST commandis received. The “Command Reference” specifies the *RST condition for every command. Insome cases, the condition may be instrument-dependent. Instrument-dependent means thatthe designer may determine the setting at *RST. However, the setting shall be known for theinstrument. Leaving a setting undefined at *RST is not allowed, unless specifically permittedin the command description.

Consideration shall be given to safety if the instrument is capable of producing hazardousconditions.

Operation after a *RST is optimized for remote operation.

A *RST command returns the instrument to a state where it is waiting for a command toinitiate measurements or other instrument actions.

KI001aAll instruments shall place themselves in the trigger idle state. Source instruments should notbe sourcing power at any output port. This condition may be reached by lowering thepower/voltage level or by turning the output state to OFF. Input ranges should normally beset to AUTORANGE or minimum sensitivity. Settings which are normally coupled shouldbe coupled. Special modes, complex modulations, postprocessing, or similar functions whichare generally application-dependent should be disabled leaving the instrument in its mostfundamental mode of operation.

Finally, thought should be given to implementing *RST conditions so that the incrementalprogramming necessary after *RST for the applications be minimized.

The SYSTem:PRESet command performs the same action as the front panel preset key. Thistypically sets all instrument parameters to values for good local/human interaction. Inmanual operation, it is often desirable to have SYSTem:PRESet enable continuousmeasurements. This may be different from the *RST state and the power-on state.

Status structures are not affected by *RST. The status event bits are cleared by *CLS and byreading the event register. The error/event queue is also cleared by *CLS. Device-dependentand SCPI status registers and queues are preset with the SCPI required STATus:PRESetcommand.

TK012If a device is unable to implement the *RST condition of a function, it may choose adifferent *RST condition. However, under these circumstances, the command for thisfunction must be implemented, even if only one selection is available. If the deviceimplements the stated *RST setting, the function must assume that value at *RST.

1

2

3

4 5

6

7

8 9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


*RST Conditions 10-1

1

2

3

4 5

6

7

8 9

10

1112

13

14

1516

17

18

19

2021

22

23

24

2526


10-2 *RST Conditions

11 Naming ConventionsIn many SCPI subsystems there is the need for assigning names to structures or expressionsor arbitrary data memory.

This includes naming of windows in the DISPlay subsystem, traces in TRACe, expressionsto specify events and sequences in TRIGger, expressions to specify cards and channel lists inROUTe, and various items elsewhere. If possible, these naming operations should all havethe same form so that these operations in the various subsystems can be consistent. A usercan therefore transfer knowledge gained in one area to a similar task in another subsystem.

For this proposed general-purpose naming facility, there is no “enable” command; allcurrently defined names will be associated with their data at define/assign time and existuntil deleted. There are two forms of the “purge” command: one which operates onindividual names as well as one for the whole name space. Names have implicit types andmemory is allocated based on the subsystem in which the name is created. Names must beunique within the system to allow a designer to implement these commands using one globalname space.

The same keywords for naming will be used in all subsystems which allow names. Eventhough TRACe:DEFine and DISPlay:WINDow:DEFine require different parameters, theoperations are similar and the instrument programmer can expect similar keywords.

The name space is not affected by *RST, and names remain associated with their data afterthis operation.

KEYWORD PARAMETER FORM NOTESNaming Sub-subsystem::DEFine <name>,<data>:DEFine? <name>:DELete [:NAME] <name> :ALL [event; no query]:CATalog? [query only]

Command Descriptions

Differences among these commands and differences from the macro definition facility arenoted in the descriptions.

The name is sent as <character data> rather than as a string, because that is the simplestIEEE 488.2 type that meets the requirements. Macro definitions needed the <string> typebecause macro names could contain colons and queries, and their total length could be morethan 12 characters. Names do not have those extensions. When a name is returned (forexample, in a “CATalog?” query), it must be sent as <string response data> so that a nullstring ("") can indicate that nothing is defined.

1

2

3

4 5

6

7

8 9

10

11

12

13

14

1516

17

18

19

2021

22

23

24

2526


Naming Conventions 11-1

Names defined using these commands are not purged at *RST. The only way of deletingthem is through a DELete or DELete:ALL command.

11.1 :DEFine <name>,<data>This command associates a user-specified <name> with data <data>. The type of <data> isdependent on the subsystem in which the command occurs, and must be specified in thesyntax for that tree. The <data> field may be optional for some subsystems.

11.2 :DEFine? <name>This query requests the instrument to return the definition of <name>. The type of datareturned depends on the specific subsystem in which the command occurs. If possible (thatis, if IEEE 488.2 allows), it should be returned in the same form it was sent.

11.3 :DELete[:NAME] <name>This command undefines the name, disassociates it from any data, and frees the name and itsdata memory for use by other definitions. There is no query associated with this action.

11.4 :DELete:ALLThis command undefines all names in this subsystem, and frees any associated data memory.There is no query associated with this action.

11.5 :CATalog?This query requests a list of defined names in this subsystem. The instrument must return alist of one or more strings, each containing one name and separated by commas. If no namesare defined, a single null string is returned.

1

2

3

4 5

6

7

8 9

10

11

12

13

14

1516

17

18

19

2021

22

23

24

2526


11-2 Naming Conventions

A Programming Tips HP077By following a set of simple guidelines, a programmer can reduce the number of errorsencountered when using SCPI instruments. All references in this appendix are to Volume I:Syntax and Style, unless otherwise specified.

1. Avoid sending default nodes. See 5.1 and 6.2.2 item 5. Default nodes are used withinSCPI to allow the language to grow. Thus, older instruments will not have implemented thedefault node. A command is more likely to work with more instruments if the default nodesare omitted. For example, use:

INP:FILT ON

rather than:

INP:FILT:LPAS:STAT ON

2. Avoid sending a numeric suffix of 1 in applications that only use the default capability.See 6.2.5.2. An instrument with multiple capabilities is required to interpret a header withoutthe numeric suffix as if a numeric suffix of one had been used. Leaving off the numericsuffix means the same commands will work with an instrument that has multiple capabilitiesand an instrument that does not. For example, use:

OUTP ON

rather than

OUTP1 ON

3. Be careful when sending coupled commands. See 7.4.2. Many instruments adhere to thesuggestion in IEEE 488.2 section 6.4.5.3. If the coupled commands are contiguous in thesame program message, the instrument is more likely to resolve any conflict between thecurrent settings and the new settings. For example, use:

:FREQ:STAR 100;SPAN 100

which sets START to 100, STOP to 200, CENTER to 150, and SPAN to 100. Assume thatSTART was 200 and STOP was 500 before sending;

:FREQ:STAR 100

Now, START is 100, STOP is 500, CENTER is 300, and SPAN is 400. Then send:

:FREQ:SPAN 100

which sets START to 250, STOP to 350, SPAN to 100, and leaves CENTER at 300 . Thesestates are very different and the second is probably not the intended one.

4. Verify instrument settings when knowing their exact value is required. If the actual valueof a setting is important, query the setting after programming it. An instrument is required toround parameters. See 7.2. For example, sending:

1

2

3

4 5

6

7

8 9

10

11

A

13

14

1516

17

18

19

2021

22

23

24

2526


Programming Tips A-1

:VOLT 1.68:VOLT?

may return 1.68, 1.7, or 2 depending on the capability of the instrument.

5. Send commands and queries in different program messages.

The response from a query combined in a program message with commands that affect thequeried value is not predictable. Sending:

:FREQ:STAR 100;SPAN 100:FREQ:STAR?

always returns 100. When:

:FREQ:STAR 100;STAR?;SPAN 100

is sent, however, the result is not specified by SCPI. The result could be the value of STARTbefore the command was sent since the instrument might defer executing the individualcommands until a program message terminator is received. The result could also be 100 ifthe instrument executes commands as they are received.

6. Use the highest level commands possible for compatibility across instruments. Wheneverfeasible, use the MEASure, CONFigure, READ?, FETCh?, and INITiate commands. Use thelower level commands only when a special characteristic of an instrument must bemanipulated.

1

2

3

4 5

6

7

8 9

10

11

A

13

14

1516

17

18

19

2021

22

23

24

2526


A-2 Programming Tips

Index

<> 5-1[] 5-1{} 5-1| 5-1

A aliases 6-3ANSI

X3.4-1977 2-1X3.42-1975 2-1

ANSI/EIATIA-562-1989 2-1

ARM 9-3

B Bell Telephone BTSM 41004 2-1<Boolean> 7-5BTSM 41004 2-1building command trees 6-2

C CALibrating 9-3capability, multiple 6-8CATalog 11-2CCIR Recommendation

468-2 2-1CCITT Recommendation

P53 2-1V.42 2-1

channellists 8-3

channel list 8-1channel_list 6-8, 8-4<channel_range> 8-4 - 8-5<channel_spec> 8-5character

case 5-2character case 6-1<character data> 11-1CHARACTER PROGRAM DATA 7-5command table notation 5-1common command header 6-1common commands

effects of *RST 10-1

mandatory 4-1 optional 4-1

compliance criteria 4-1CORRecting 9-3coupling 7-5

functional 7-6value 7-6

D data interchange format 8-1<DECIMAL NUMERIC PROGRAM DATA>

7-1, 7-5DEFault 7-1default node 5-1DEFine 11-2

query 11-2definition, macro 11-1DELete 11-2device dependence 3-2devices 4-1dif 8-1display window naming 11-1Dolby Labs Bulletin No 19/4 2-1DOWN 7-1 - 7-2

STEP 7-3

E EIA

RS-232-D 2-1RS-422 2-1

elementlexical 8-1syntactic 8-1

expressionchannel list 8-1data interchange format 8-1dif 8-1instrument specifier 8-1numeric 8-1 - 8-2numeric list 8-1precedence rules 8-3

<EXPRESSION PROGRAM DATA> 8-1

Index - 1

F flow diagram notation 5-2form

long 5-1, 6-1short 5-1, 6-1

front panel 1-1

H header

command command 6-1command tree generation 6-2instrument control 6-1keyword generation 6-1longform 6-1numeric suffix 6-2, 6-8queries 6-6query 6-1short form 6-2tree traversal 6-7

hierarchical structure 5-1

I IEC Recommendation

179 2-1IEEE

Std. 181-1977 2-1Std. 194-1977 2-1Std. 260-1978 2-1Std. 488.1-1987 1-1, 2-1, 4-1Std. 488.2-1987 1-1, 1-3, 4-1, 6-1, 6-7Std. 488.2-1992 2-1Std. 754-1985 2-1

INFinity 7-1, 7-4INSTrument 9-6instrument control header 6-1instrument dependent 10-1instrument specifier expression 8-1INSTrument Summary Bit 9-4ISO

Std. 2955-1983 2-2ISUMmary 9-6

K KEYWORD 5-1keywords 6-1

L label 7-1lexical element 8-1life cycle 3-1 - 3-2living standard 3-1logical instruments 6-9long form 5-1, 6-1

M macro definition 11-1mandated commands 4-1MAXimum 7-1MEASuring 9-3MINimum 7-1 - 7-2<module_channel> 8-4<module_specifier> 8-5multiple

capabilities 6-8electrical ports 6-8indentical capabilities 6-8logical instruments status 9-5

N naming conventions 11-1

CATalog 11-2DEFine 11-2DELete 11-2

NAN (not a number) 7-4nomenclature

see notation 5-1<non-decimal numeric> 7-1Not A Number (NAN) 7-1notation 5-1

command tables 5-1query 5-1status structure diagrams 9-1syntax flow diagrams 5-2

NOTES 5-1<NRf> 7-1numeric expression 8-1 - 8-2numeric list 8-1<numeric_expression> 7-1<numeric_list> 8-6<numeric_operator> 8-2<numeric_range> 8-6


Index - 2

O obsolesence 3-1OFF 7-5ON 7-5OPERation 9-1OPERation Status Register 9-3optional

use of expressions 8-1commands 4-6common commands 4-1IEEE 488.1 interface 4-1nodes 6-4SCPI commands 4-6

P PARAMETER FORM 5-1parameters 7-1

<CHARACTER PROGRAM DATA> 7-1<NRf> 7-1<numeric_value> 7-1Boolean program data 7-5character program data 7-1decimal numeric program data 7-1DEFault 7-1DOWN 7-2INFinity 7-4MAXimum 7-2NAN (not a number) 7-4STEP UP/DOWN 7-3unit suffixes 7-5UP 7-2

precedence rules 8-3primary keyword 6-3program headers 6-1

queries 6-6<PROGRAM MESSAGE> 6-7<PROGRAM MESSAGE UNIT> 6-7PROGram running 9-4

Q queries 6-6QUEStionable 9-1QUEStionable Data 9-4

R railroad diagrams 5-2RANGing 9-3References 2-1

requirementsdocumentation 4-6IEEE 488.1 4-1IEEE 488.2 4-1IEEE mandated commands 4-1minimum status structure 9-1multiple capabilities 6-9safety 10-1SCPI 4-5SCPI commands 4-5

roundingnumeric program data 7-1

S SAE J2264 2-2safety requirements 10-1SCPI

requirements 4-5semantics 8-3SETTling 9-3short form 5-1, 6-1Signal Status Register 9-4square brackets 5-1status reporting 9-1

device dependent registers 9-3diagram notation 9-1effect of *CLS 9-3effect of *RST 9-3enhanced TRIGger model 9-7minimum requirement 9-1multiple logical instruments 9-5OPERation 9-1, 9-3QUEStionable 9-1, 9-4transition filters 9-3TRIGger model 9-1

STEP 7-3AUTO 7-4INCRement 7-3MODE 7-3PDECade 7-3

<string> 11-1<SUFFIX PROGRAM DATA> 7-5SWEeping 9-3Syntax and Style 1-1syntax flow diagram notation 5-2systems instruments 1-1

T trace naming 11-1<trace_name> 8-3


Index - 3

transition filters 9-3negative 9-3positive 9-3

Traversal of header tree 6-7tree system 5-1tree walking 6-7

enhanced 6-7TRIGger 9-3

LAYers 9-7SEQuences 9-7

U <unary_numeric_operator> 8-3unit

amplitude and power 7-7suffixes 7-5unitless quantities 7-9units of measure 7-7

UP 7-1 - 7-2STEP 7-3

V <variable or trace_name> 8-3VXI 2-2, 6-9


Index - 4


Volume 2: Command Reference


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2 Instrument Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 3 Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Chapter 4 CALCulate Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Chapter 5 CALibration Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Chapter 6 CONTrol Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Chapter 7 DIAGnostic Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Chapter 8 DISPlay Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Chapter 9 FORMat Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Chapter 10 HCOPy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Chapter 11 INPut Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Chapter 12 INSTrument Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Chapter 13 MEMory Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Chapter 14 MMEMorySubsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1Chapter 15 OUTPut Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Chapter 16 PROGram Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1Chapter 17 ROUTe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1Chapter 18 SENSe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1Chapter 19 SOURce Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1Chapter 20 STATus Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Chapter 21 SYSTem Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1Chapter 22 TEST Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1Chapter 23 TRACe | DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1Chapter 24 TRIGger Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1Chapter 25 UNIT Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1Chapter 26 VXI Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1

iii

1999 SCPI Command Reference

iv

Table of Contents


1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2 Instrument Model

2.1 Signal Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.1.1 Setting the Destination for Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.2 Measurement Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.2.1 INPut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.2.2 SENSe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.2.3 CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.3 Signal Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.3.1 OUTPut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.3.2 SOURce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.3.3 CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.4 TRIGger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.5 MEMory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.6 FORMat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.7 Internal Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.7.1 Data and Control Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62.7.2 Numeric Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.7.3 Lamina and Cloned Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.7.3.1 FEED Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.7.3.2 Amorphous SENSe Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.7.3.3 Other Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92.7.4 FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92.7.4.1 Sensor Function Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92.7.4.2 FEEDs from CALCulate Sub-Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.7.5 COMBine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.7.6 Memory Associated with Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.7.7 Querying the Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-142.7.8 <event_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Chapter 3 Measurement Instructions

3.1 CONFigure:<function> <parameters>[,<source list>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.2 FETCh[:<function>]? <parameters>[,<source list>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.3 READ[:<function>]? <parameters> [,<source list>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.4 MEASure:<function>? <parameters>[,<source list>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.5 <function> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

v

3.6 Presentation Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.6.1 Presentation Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.6.2 [:SCALar] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.6.3 :ARRay <size> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.7 Fundamental Measurement Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.7.1 Fundamental Measurement Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.7.2 :VOLTage [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.7.3 :CURRent [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.7.4 :POWer [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.7.5 :RESistance [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.7.6 :FRESistance [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.7.7 :TEMPerature [<transducer>[,<type> [,<expected_value>[,<resolution>]]]] . . . . . . . . . 3-83.8 Measurement Function Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1 Simple Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.1 Simple Measurements Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.2 :AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.3 [:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.4 :FREQuency [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.4.1 :BURSt [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.8.1.4.2 :PRF [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.8.1.5 :PERiod [<expected_value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.8.1.6 :PHASe [<expected value>[,<resolution>]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.8.2 Time Domain Waveform Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.8.2.1 Waveform Measurements Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.8.2.2 :AMPLitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113.8.2.3 :LOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.4 :HIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.5 :RISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.5.1 :TIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.5.2 :OVERshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.5.3 :PREShoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.6 :RTIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.8.2.7 :FALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.7.1 :TIME [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.7.2 :OVERshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.7.3 :PREShoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.8 :FTIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.9 :PWIDth [<reference>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.8.2.10 :NWIDth [<reference>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.8.2.11 :PDUTycycle|:DCYCle [<reference>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.8.2.12 :NDUTycycle [<reference>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14


vi

3.8.2.13 :TMAXimum Layer:Time Domain Waveform Measurements . . . . . . . . . . . . . . . . . 3-143.8.2.14 :TMINimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.8.2.15 :MINimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.8.2.16 :MAXimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.8.2.17 :PTPeak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Chapter 4 CALCulate Subsystem

4.1 :AVERage subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.1.1 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.1.2 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.1.2.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.1.3 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.1.4 :TCONtrol EXPonential | MOVing | NORMal | REPeat . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.1.5 :TYPE COMPlex | ENVelope | MAXimum | MINimum | RMS | SCALar . . . . . . . . . . . . 4-84.2 :CLIMits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.1 :FAIL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.2 :FLIMits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.2.1 [:DATA]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.2.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.3 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.3.1 :PREamble? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.4 :DERivative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.4.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.4.2 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.5 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.6 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1 [:GATE] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1 :TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1.2 [:TYPE ] BPASs|NOTCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1.3 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1.4 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1.1.5 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.6 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.7 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.7.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.8 :WINDow RECTangular|UNIForm|FLATtop|HAMMing

|HANNing|KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.9 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.10 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.6.1.1.11 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.6.1.2 :FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.6.1.2.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.6.1.2.2 [:TYPE ] BPASs|NOTCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13


vii

4.6.1.2.3 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.6.1.2.4 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.6.1.2.5 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.6 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.7 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.7.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.8 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.9 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.10 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.6.1.2.11 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.7 :FORMat NONE|MLINear|MLOGarithmic|PHASe|REAL |IMAGinary|SWR|GDELay |COMPlex|NYQuist|NICHols|POLar |UPHase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.7.1 :UPHase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164.7.1.1 :CREFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.7.1.2 :PREFerence <numeric value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.8 :GDAPerture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.8.1 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.8.2 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.9 :IMMediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.9.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.10 :INTegral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.10.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.10.2 :TYPE SCALar | MOVing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.11 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.11.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.2 :CONTrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.2.1 [:DATA] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.2.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.3 :UPPer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.3.1 [:DATA] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.11.3.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.4 :LOWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.4.1 [:DATA] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.4.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.4.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.5 :FAIL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.6 :FCOunt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.7 :REPort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.7.1 [:DATA]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.11.7.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.11.8 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21


viii

4.11.8.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.11.8.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.11.9 :INTerpolate <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.12 :MATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.12.1 [:EXPRession] <numeric_expression> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.12.1.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.12.1.2 [:DEFine] <numeric_expression> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.12.1.3 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.12.1.3.1 [:SELected] <expression_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.12.1.3.2 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.12.1.4 :NAME <expression_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.12.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.13 :SMOothing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.13.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.13.2 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.13.3 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.14 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.15 :TRANsform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.15.1 :HISTogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.15.1.1 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.15.1.2 :ORDinate RATio | PERCent | PCT | COUNt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.15.1.3 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.15.1.4 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.15.1.4.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.1.5 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2 :TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2.2 [:TYPE ] LPASs|BPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2.3 :STIMulus STEP|IMPulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2.4 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.15.2.5 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.6 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.7 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.8 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.8.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.9 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.15.2.10 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.2.11 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.2.12 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.3 :DISTance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.3.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.3.2 [:TYPE ] LPASs|BPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.3.3 :STIMulus STEP|IMPulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.15.3.4 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28


ix

4.15.3.5 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.15.3.6 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.15.3.7 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.15.3.8 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.15.3.8.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.15.3.9 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.3.10 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.3.11 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.3.12 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.4 :FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.4.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-294.15.4.2 [:TYPE ] LPASs|BPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.15.4.3 :STIMulus STEP|IMPulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.15.4.4 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.15.4.5 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.15.4.6 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.15.4.7 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.15.4.8 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.15.4.8.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.15.4.9 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.15.4.10 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.15.4.11 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.15.4.12 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.16 :PATH (MATH|TRANsform|FILTer|SMOothing|FORMat|LIMit|AVERage) {,(MATH|TRANsform|FILTER|SMOothing|FORMat|LIMit|AVERage)} . . . . . . . . . . . 4-31

Chapter 5 CALibration Subsystem

5.1 [:ALL] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.2 [:ALL]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.4 :BINertia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.4.1 :AVERage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.4.2 :HSPeed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.4.3 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.4.4 :LSPeed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.4.5 :NRUNs <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.4.6 :SDEViation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.4.7 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.5 :DATA <arbitrary block program data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.6 :PLOSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.6.1 :APCoeff <numeric_value>,<numeric_value>,<numeric_value>[,<numeric_value>] . . . 5-45.6.2 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4


x

5.6.3 :LATime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55.6.4 :STIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-55.6.5 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55.7 :SOURce INTernal|EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65.8 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65.9 :VALue <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65.10 :WARMup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65.10.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65.10.2 :SPEed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.10.3 :TIMeout <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.11 :ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.11.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.11.2 :FSENsor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.11.2.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.11.2.2 :LATime <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.11.2.3 :LEVel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.11.2.4 :SPEed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.11.2.5 :STIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.11.2.6 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Chapter 6 CONTrol Subsystem

6.1 :APOWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2 :BLOWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3 :BRAKe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.4 :COMPressor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.4.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.5 :COVer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.5.1 [:ADJust] OPEN|CLOSe|SOPEn|SCLOse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.5.2 :POSition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.6 :EBENch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.6.1 :CLEan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.6.1.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.6.1.2 :DURation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.7 :IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.7.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.8 :LIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.8.1 [:ADJust] UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.8.2 :POSition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.9 :MCONtrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.9.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.10 :ROTation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4


xi

6.10.1 [:DIRection] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.11 :VCDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.11.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.11.2 :TDIameter <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Chapter 7 DIAGnostic Subsystem

Chapter 8 DISPlay Subsystem

8.1 :ANNotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.1.1 [:ALL] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.1.2 :AMPLitude <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48.1.3 :FREQuency <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48.2 :BRIGhtness <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48.3 :CMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.3.1 :DEFault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.3.2 :COLor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.3.2.1 :HSL <hue>,<sat>,<lum> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.3.2.2 :RGB <red>,<green>,<blue> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.4 :CONTrast <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.5 :ENABle <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.6 :MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.6.1 [:NAME] <menu_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.6.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.6.3 :KEY <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.7 [:WINDow] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.7.1 :BACKground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.7.1.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.7.2 :GEOMetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.7.2.1 :LLEFt <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.2.2 :SIZE <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.2.3 :URIGht <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.3 :GRAPhics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.3.1 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.3.2 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.3.3 :CSIZe <numeric_value>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.7.3.4 [:DRAW] <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.5 :PCL <block> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.6 :HPGL <block> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.7 :IDRaw <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.8 :IMOVe <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.9 :LABel <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.10 :LDIRection <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.11 :LTYPe <numeric_value>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.7.3.12 :MOVE <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9


xii

8.7.3.13 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.4 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.5 :TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.5.1 :ATTRibutes <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.5.2 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.5.3 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.7.5.4 :CSIZe <numeric_value>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.5.5 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.5.6 [:DATA] <string> | <block> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.5.7 :LOCate <numeric_value>[,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.5.8 :PAGE <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.5.9 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.6 :TRACe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.6.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.6.2 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.7.6.3 :GRATicule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.1 :AXIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.1.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.2 :FRAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.3 :GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.3.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.3.3.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.4 :PERSistence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.4.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.5 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.7.6.6 :X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.1 :LABel <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.2 [:SCALe] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.2.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.2.2 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.2.3 :LEFT <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.7.6.6.2.4 :PDIVision <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.6.2.5 :RIGHt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.7 :Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.7.1 :LABel <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.7.2 :RLINe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.7.3 [:SCALe] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.7.6.7.3.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148.7.6.7.3.2 :BOTTom <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148.7.6.7.3.3 :PDIVision <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148.7.6.7.3.4 :RLEVel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-148.7.6.7.3.5 :RPOSition <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.7.3.6 :TOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.7.4 :SPACing LOGarithmic | LINear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15


xiii

8.7.6.8 :R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.8.1 :LABel <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.8.2 [:SCALe] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.8.2.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.8.2.2 :CPOint <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.7.6.8.2.3 :OEDGe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-168.7.6.8.3 :SPACing LOGarithmic | LINear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Chapter 9 FORMat Subsystem

9.1 :BORDer NORMal|SWAPped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.2 [:DATA] <type>[,<length>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.3 :DINTerchange <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.4 :SREGister ASCii | BINary | HEXadecimal | OCTal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Chapter 10 HCOPy

10.1 :ABORt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.3 :DESTination<data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.4 :DEVice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.4.1 :CMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.4.1.1 :COLor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.4.1.1.1 :HSL <hue>,<sat>,<lum> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.4.1.1.2 :RGB <red>,<green>,<blue> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.4.1.2 :DEFault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-610.4.2 :COLor <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-610.4.3 :LANGuage PCL[<n>] | HPGL[<n>] | POSTscript[<n>] . . . . . . . . . . . . . . . . . . . . . . . . 10-610.4.4 :MODE TABLe | GRAPh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.4.5 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.4.5.1 :UNIT <SUFFIX PROGRAM DATA> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.4.6 :SPEed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.4.6.1 :UNIT <SUFFIX PROGRAM DATA> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.5 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.6 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.7 :ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-710.7.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.1.1 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.1.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.2 :ANNotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.2.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.2.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.2.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.2.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.3 :CUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.7.3.1 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9


xiv

10.7.3.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.4 :FFEed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.4.1 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.4.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.4.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.5 :LABel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.5.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.7.5.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.5.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.5.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.5.5 :TEXT <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1010.7.6 :MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.6.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.6.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.6.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.6.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.7.7 :TDSTamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.7.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.7.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.7.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.7.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8 [:WINDow] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8.1 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8.4 :TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.7.8.4.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.4.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.4.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.4.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5 :TRACe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.3 :GRATicule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.3.1 :COLor <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.3.2 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.7.8.5.3.3 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.7.8.5.3.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.7.8.5.4 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.7.8.5.5 :LTYPe SOLid | DOTTed | DASHed | STYLe<n> . . . . . . . . . . . . . . . . . . . . . . 10-1310.7.8.5.6 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.8 :PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.8.1 :DIMensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.8.1.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13


xv

10.8.1.2 :LLEFt <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.1.3 :QUADrant[<n>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.1.4 :URIGht <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.2 :LENGth <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.3 :ORIentation LANDscape | PORTrait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.4 :SCALe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1410.8.5 :SIZE CUSTom|A|B|C|D|E|A0|A1|A2|A3|A4|B0|B1|B2|B3|B4|B5 . . . . . . . . . . . . . . . . 10-1510.8.6 :UNIT <SUFFIX PROGRAM DATA> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1510.8.7 :WIDTh <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1510.9 :SDUMp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1510.9.1 :DATA? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1510.9.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15

Chapter 11 INPut Subsystem

11.1 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.1.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.2 :BIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.2.1 :CURRent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.2.1.1 :AC <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.1.2 [:DC] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.3 :TYPE CURRent | VOLTage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.4 :VOLTage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.4.1 :AC <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.2.4.2 [:DC] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.3 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.4 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.1 :AWEighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.1.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.2 :HPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.2.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.3 [:LPASs] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.3.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.4.3.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-511.5 :GAIN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.5.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.5.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.6 :GUARd LOW|FLOat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.7 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.8 :LOW FLOat|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.9 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.9.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7


xvi

11.10 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.11 :POLarization <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.11.1 :HORizontal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.11.2 :VERTical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.12 :POSition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-711.12.1 [:X] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-811.12.1.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-911.12.1.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2 :Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1011.12.2.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1111.12.2.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3 :Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12


xvii

11.12.3.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1211.12.3.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1311.12.3.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1411.13 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1411.14 :TYPE <character data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14

Chapter 12 INSTrument Subsystem

12.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112.1.1 :FULL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112.2 :COUPle[:<subsystem>] ALL|NONE|<list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-212.3 :DEFine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-212.3.1 :GROup <identifier>,<identifier_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-212.3.2 [:NAME] <identifier>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-312.4 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-312.4.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-312.4.2 [:NAME] <identifier> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-312.5 :NSELect <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-412.6 [:SELect] <identifier> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-412.7 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Chapter 13 MEMory Subsystem

13.1 :CATalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-413.1.1 [:ALL]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-513.1.2 :ASCii? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-513.1.3 :BINary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-513.1.4 :MACRo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-513.1.5 :STATe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-513.1.6 :TABLe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-613.2 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-613.2.1 [:NAME] <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6


xviii

13.2.2 :TABLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-613.3 :COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-613.3.1 [:NAME] <name>,<name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-613.3.2 :TABLe <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.4 :DATA<name>,<data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.5 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.5.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.5.2 [:NAME] <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.6 :EXCHange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.6.1 [:NAME] <name>,<name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-713.6.2 :TABLe <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7 :FREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7.1 [:ALL]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7.2 :ASCii? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7.3 :BINary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7.4 :MACRo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-813.7.5 :STATe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.7.6 :TABLe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.8 :NSTates? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.9 :STATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.9.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.9.2 :DEFine <name> , <register_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.10 :TYPE? <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-913.11 :TABLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.1 :BNUMber <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.2 :CCURve <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.2.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.3 :CONCentration <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.3.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.4 :CONDition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1013.11.4.1 [:MAGNitude] <Boolean>{,<Boolean>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.4.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.5 :CPOint <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.5.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.6 :CURRent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.6.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.6.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.6.2 :PHASe <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1113.11.6.2.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1213.11.7 :DFACtory <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1213.11.7.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1213.11.8 :DLASt <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1213.11.8.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1313.11.9 :DLINearize <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13


xix

13.11.9.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1313.11.10 :EXPected <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1313.11.10.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1413.11.11 :DEFine <structure_string>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1413.11.12 :FORCe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1413.11.12.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1413.11.12.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1413.11.13 :FREQuency <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1513.11.13.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1513.11.14 :LABel <string> {,<string>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1513.11.14.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1513.11.15 :LLIMit <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1513.11.15.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1513.11.16 :LOG <string> {,<string>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1513.11.16.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.17 :LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.17.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.17.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.17.2 :PHASe <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.17.2.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.18 :NCURve <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.18.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1613.11.19 :POWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.19.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.19.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.20 :RAW <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.20.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.21 :RESistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.21.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.21.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1713.11.22 :SELect <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.23 :SPEed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.23.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.23.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.24 :TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.24.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.24.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.25 :TOLerance <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1813.11.25.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.26 :ULIMit <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.26.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.27 :VOLTage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.27.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.27.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1913.11.27.2 :PHASe <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19


xx

13.11.27.2.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2013.11.28 :WFACtor <numeric_value> {,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2013.11.28.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20

Chapter 14 MMEMorySubsystem

14.1 :CATalog? [<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-214.2 :CDIRectory [<directory_name>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-314.3 :CLOSe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-314.4 :COPY <file_source>,<file_destination> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-314.5 :DATA <file_name>, <data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-314.6 :DELete <file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-314.7 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.8 :INITialize [<msus>[,(LIF|DOS|HFS)[,<numeric_value>]]] . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9 :LOAD and :STORe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9.1 :DINTerchange <label>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9.1.1 :TRACe <label>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9.2 :MACRo <label>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9.3 :STATe <numeric_value>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-414.9.4 :TABLe <label>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-514.9.5 :TRACe <label>,<file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-514.10 :MSIS [<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-514.11 :MOVE (<src_file>,<dest_file>) |(<src_file>,<src_msus>,<dest_file>,<dest_msus>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-514.12 :NAME <file_name>[,<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-514.13 :OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-614.14 :PACK [<msus>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

Chapter 15 OUTPut Subsystem

15.1 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-315.2 :COUPling AC|DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-315.3 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-315.3.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-315.3.2 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-315.3.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.3 :HPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.3.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.3.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.3.3 :TYPE BESSel | CHEByshev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.4 [:LPASs] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.4.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.4.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.3.4.3 :TYPE BESSel | CHEByshev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-415.4 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-515.5 :LOW FLOat|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5


xxi

15.6 :POLarity NORMal | INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-515.7 :POLarization <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-515.7.1 :HORizontal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-515.7.2 :VERTical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-515.8 :POSition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-515.8.1 [:X] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-515.8.1.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-615.8.1.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.1.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-715.8.2 :Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-815.8.2.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.2.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-915.8.3 :Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1 :ANGLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10


xxii

15.8.3.1.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.1.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1015.8.3.2 [:DISTance] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.1 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.2 [:IMMediate] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.3 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.3.1 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.3.2 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.3.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.8.3.2.5 :VELocity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1115.9 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.9.1 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.9.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.9.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.9.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.10 :ROSCillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.10.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.11 :TTLTrg<n>|:ECLTrg<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.11.1 :IMMediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1215.11.2 :LEVel <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1315.11.3 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1315.11.4 :PROTocol SYNChronous|SSYNchronous|ASYNchronous . . . . . . . . . . . . . . . . . . . . . 15-1315.11.5 :WIDTh <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1315.11.6 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-1315.11.7 :SOURce <character data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1315.12 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1415.13 :TYPE <character data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14

Chapter 16 PROGram Subsystem

16.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2 [:SELected] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.1 :DEFine <program> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.2 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.2.1 [:SELected] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.2.2 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.3 :EXECute <program_command> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-216.2.4 :MALLocate <nbytes>|DEFault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3


xxiii

16.2.5 :NAME <progname> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-316.2.6 :NUMBer <varname>{,<nvalues>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-316.2.7 :STATe RUN|PAUSe|STOP|CONTinue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-316.2.8 :STRing <varname>{,<svalues>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-416.2.9 :WAIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-416.3 :EXPLicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-416.3.1 :DEFine <progname>,<program> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-416.3.2 :DELete <progname> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-516.3.3 :EXECute <progname>,<program_command> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-516.3.4 :MALLocate <progname>,(<nbytes>|DEFault) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-516.3.5 :NUMBer <progname>,<varname>{,<nvalues>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-516.3.6 :STATe <progname>,(RUN|PAUSe|STOP|CONTinue) . . . . . . . . . . . . . . . . . . . . . . . . . 16-516.3.7 :STRing <progname>,<varname>{,<svalues>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-616.3.8 :WAIT <progname> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6

Chapter 17 ROUTe Subsystem

17.1 :CLOSe <channel_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-117.1.1 :STATe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2 :MODule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2.2 [:DEFine] <module_name>,<module_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2.3 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2.3.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-217.2.3.2 [:NAME] <module_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.3 :OPEN <channel_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.3.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.4 :PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.4.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.4.2 [:DEFine] <path_name>,<channel_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-317.4.3 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.4.3.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.4.3.2 [:NAME] <path_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.5 :SAMPle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.5.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.5.2 [:OPEN] BAG|DILute|PRE|POST|MID|CEFFiciency

|NONE|ZERO|SPAN|VERify|MANifold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-417.6 :SCAN <channel_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-617.7 TERMinals FRONt|REAR|BOTH|NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

Chapter 18 SENSe Subsystem

18.1 AM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.1.1 [:DEPTh] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.1.1.1 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.1.1.1.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4


xxiv

18.1.1.1.2 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.1.1.1.3 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.1.2 :TYPE LINear|LOGarithmic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418.2 AVERage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-618.2.1 A typical device action for SENS:AVERage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-618.2.2 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-718.2.2.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-718.2.3 [:STATE] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-718.2.4 :TCONtrol EXPonential | MOVing | NORMal | REPeat . . . . . . . . . . . . . . . . . . . . . . . . . 18-718.2.5 :TYPE COMPlex | ENVelope | MAXimum | MINimum | RMS | SCALar . . . . . . . . . . . 18-818.3 BANDwidth|BWIDth Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.1 [:RESolution] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.1.2 :RATio <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.1.3 :TRACk <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.2 :VIDeo <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1018.3.2.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1118.3.2.2 :RATio <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1118.4 CONCentration Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-1218.4.1 :CSET <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1218.4.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1218.4.3 :LSET POLYnomial<n> | SRATional<n>,<numeric_value>{,<numeric_value>} . . 18-1218.4.4 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.4.1 :AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.4.1.1 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.4.1.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.4.1.3 :UPPer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.4.2 [:FIXed] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.5 :TALign <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1318.4.6 :UPPer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1418.5 CONDition Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1518.5.1 :LEVel <numeric_value> | TTL ECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1518.6 CORRection Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1618.6.1 :AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1718.6.2 :CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1718.6.3 :COLLect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1718.6.3.1 [:ACQuire] STANdard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1718.6.3.2 :METHod TPORt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1818.6.3.3 :SAVE [<trace_name>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1818.6.4 :CSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1818.6.4.1 [:SELect] <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1818.6.4.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1818.6.5 :EDELay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1918.6.5.1 :DISTance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1918.6.5.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19


xxv

18.6.5.3 [:TIME] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1918.6.6 :IMPedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1918.6.6.1 [:INPut]|:OUTPut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1918.6.6.1.1 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2018.6.6.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2018.6.7 :LOSS|:GAIN|:SLOPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2018.6.7.1 [:INPut]|:OUTPut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2018.6.7.1.1 :AUTO ON|OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2018.6.7.1.2 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.7.1.3 :PHASe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.7.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.8 :OFFSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.8.1 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.8.2 :PHASe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2118.6.8.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9 :RVELocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9.1 :COAX <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9.2 :MEDium COAX|WAVeguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9.4 :WAVeguide <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.9.4.1 :FCUToff <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2218.6.10 :SPOint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.10.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.10.2 :DTOLerance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.11 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.12 :ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.12.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.6.12.2 :DTOLerance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2318.7 CURRent Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2518.7.1 :AC|[:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2518.7.1.1 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2518.7.1.2 :NPLCycles <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.3 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.3.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.4 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.4.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.4.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.4.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-2618.7.1.4.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2618.7.1.5 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.1 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.3.1 :DIRection UP|DOWN|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.3.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-27


xxvi

18.7.1.5.3.3 :ULIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2718.7.1.5.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.1.5.5 :PTPeak <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.1.6 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.1.6.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.1.7 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.1.7.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2818.7.2 :DETector INTernal | EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2918.8 DETector Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3018.8.1 :BANDwidth | BWIDth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3018.8.2 [:FUNCtion] <detector function> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3018.8.2.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3118.8.3 :SHAPe LINear|LOGarithmic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3118.9 DISTance Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3218.9.1 :RESet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3218.10 FILTer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3318.10.1 [:LPASs] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3318.10.1.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3318.10.1.2 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3318.10.2 :HPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3318.10.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.2.2 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.3 :DEMPhasis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.3.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.3.2 :TCONstant <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.4 :CCITt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.4.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.5 :CMESsage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.5.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3418.10.6 :CCIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.10.6.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.10.7 :CARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.10.7.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.10.8 :AWEighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.10.8.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3518.11 FM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.11.1 [:DEViation] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.11.1.1 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.11.1.1.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.11.1.1.2 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.11.1.1.3 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3618.12 FREQuency Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3718.12.1 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3718.12.2 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3718.12.3 [:CW|:FIXed] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38


xxvii

18.12.3.1 :AFC <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3818.12.3.2 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3818.12.4 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3818.12.5 :MODE CW|FIXed|SWEep|LIST|SOURce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3818.12.6 :MULTiplier <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.7 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.8 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.8.1 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.8.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.8.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3918.12.9 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.9.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.10 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.10.1 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.10.2 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.10.3 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4018.12.11 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4118.12.12 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4118.13 FUNCtion & DATA Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4218.13.1 DATA? [<data_handle>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4218.13.1.1 SENSe <data_handle>s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4218.13.1.2 :PREamble? [<data_handle>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4318.13.2 :FUNCtion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4318.13.2.1 :CONCurrent <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4318.13.2.2 :OFF <sensor_function>{,<sensor_function>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4418.13.2.2.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4418.13.2.2.2 :COUNt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4418.13.2.3 [:ON] <sensor_function>{,<sensor_function>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4418.13.2.3.1 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4518.13.2.3.2 :COUNt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4518.13.2.4 :STATe? <sensor_function> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4518.13.2.5 <sensor_function> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4518.13.2.6 <presentation_layer> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-4718.13.2.6.1 [XNONe:] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-4718.13.2.6.2 XTIMe: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4718.13.2.6.3 XFRequency: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4718.13.2.6.4 XPOWer: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4718.13.2.6.5 XVOLtage: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4718.13.2.6.6 XCURrent: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4718.13.2.7 <function_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4818.13.2.8 <function> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4918.13.2.8.1 ACCeleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5018.13.2.8.2 AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5018.13.2.8.2.1 [:DEPTh] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5018.13.2.8.2.2 :DISTortion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-50


xxviii

18.13.2.8.2.3 :FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.2.4 :SNDRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.2.5 :SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.2.6 :THD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5118.13.2.8.3 CONCentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.3.1 :RAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5118.13.2.8.3.2 :SDEViation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.3.3 :TALign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.4 CONDition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.5 CURRent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.5.1 [:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.5.2 :AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5118.13.2.8.6 DISTance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7 FM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.1 :[DEViation] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.2 :DISTortion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.3 :FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.4 :SNDRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.5 :SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.7.6 :THD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5218.13.2.8.8 FERRor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.9 FORCe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5218.13.2.8.10 FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5218.13.2.8.11 FRESistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.12 PERiod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.13 PHASe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14 PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.1 [:DEViation] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.2 :DISTortion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.3 :FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.4 :SNDRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.5 :SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.14.6 :THD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.15 POWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5318.13.2.8.15.1 :AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.2 :ACHannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.3 :COHerence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.4 :CROSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.5 [:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.6 :DISTortion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.7 :PSDensity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.8 :S11|:S12|:S22|:S21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5418.13.2.8.15.9 :SNDRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.15.10 :SNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.15.11 :THD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55


xxix

18.13.2.8.16 PULM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.17 RESistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.18 SPEed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.18.1 :FRONt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5518.13.2.8.18.2 [:REAR] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5518.13.2.8.19 SSB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.20 TEMPerature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5618.13.2.8.21 TIMer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.21.1 COUNt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-5618.13.2.8.22 TINTerval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.23 TOTalize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.24 TPLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25 VOLTage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25.1 :AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25.2 :CDFunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25.3 [:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25.4 :HISTogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5618.13.2.8.25.5 :PDFunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5718.14 LIST Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5818.14.1 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5818.14.2 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5818.14.3 :DWELl <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5818.14.3.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5818.14.4 :FREQuency <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5918.14.4.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5918.14.5 :SEQuence <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5918.14.5.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5918.14.5.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5918.15 MIXer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.1 :BIAS <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.1.2 :LIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.2 :HARMonic <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.2.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6018.15.3 :LOSS <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6118.15.3.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6118.16 PM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.16.1 [:DEViation] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.16.1.1 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.16.1.1.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.16.1.1.2 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.16.1.1.3 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6218.17 POWer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6318.17.1 :ACHannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6318.17.1.1 :SPACing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63


xxx

18.17.1.1.1 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.1.1.1.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.1.1.2 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.2 :AC|[:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.2.1 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.2.2 :NPLCycles <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.2.3 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6418.17.2.3.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.4 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.4.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.4.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.4.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.4.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.5 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.5.1 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6518.17.2.5.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.3.1 :DIRection UP|DOWN|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.3.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.3.3 :ULIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.5.5 :PTPeak <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6618.17.2.6 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6718.17.2.6.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6718.17.2.7 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6718.17.2.7.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6718.17.3 :DETector INTernal | EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6718.18 RESistance|FRESistance Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6818.18.1 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6818.18.2 :NPLCycles <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6818.18.3 :OCOMpensated <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6818.18.4 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.1 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.3.1 :DIRection UP|DOWN|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.3.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.4.3.3 :ULIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6918.18.5 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7018.18.5.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7018.18.6 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7018.18.6.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7018.19 ROSCillator Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7118.19.1 [:INTernal] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7118.19.1.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71


xxxi

18.19.2 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7118.19.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7118.19.3 :SOURce INTernal|EXTernal|NONE|CLK10|CLK100 . . . . . . . . . . . . . . . . . . . . . . . . . 18-7118.19.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7218.20 SMOothing Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7318.20.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7318.20.2 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7318.20.3 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7318.21 SSB Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7418.21.1 :TYPE USB|LSB|A1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-7418.22 STABilize Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7518.22.1 :NTOLerance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7518.22.2 [:STATE] < Boolean > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-7518.22.3 :TIME<n> <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7618.23 SWEep Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7718.23.1 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7818.23.2 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7818.23.3 :DWELl <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7818.23.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.4 :GENeration STEPped|ANALog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.5 :MODE AUTO|MANual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.6 :OFFSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.6.1 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.6.2 :TIME <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7918.23.7 :OREFerence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8018.23.7.1 :LOCation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8018.23.7.2 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8018.23.8 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8018.23.9 :REALtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8118.23.9.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8118.23.10 :SPACing LINear|LOGarithmic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8118.23.11 :STEP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8218.23.12 :TIME <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8218.23.12.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8218.23.12.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8318.23.13 :TINTerval <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8318.24 VOLTage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8418.24.1 :AC|[:DC] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8418.24.1.1 :APERture <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8418.24.1.2 :NPLCycles <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.3 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.3.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.4 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.4.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.4.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-85


xxxii

18.24.1.4.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.4.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8518.24.1.5 :RANGe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.1 [:UPPer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.2 :LOWer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.3 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.3.1 :DIRection UP|DOWN|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.3.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.3.3 :ULIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8618.24.1.5.4 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.1.5.5 :PTPeak <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.1.6 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.1.6.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.1.7 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.1.7.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8718.24.2 :DETector INTernal | EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8818.25 WINDow Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8918.25.1 [:TYPE] RECTangular|UNIForm|FLATtop|HAMMing|HANNing |KBESsel|FORCe|EXPonential . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8918.25.1.1 :KBESsel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8918.25.1.2 :EXPonential <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8918.25.1.3 :FORCe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-89

Chapter 19 SOURce Subsystem

19.1 ACCeleration Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-519.1.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-519.2 AM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-619.2.1 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-619.2.2 [:DEPTh] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-619.2.3 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-619.2.3.1 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.3.2 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.3.3 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.4 :INTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.4.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.5 :MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-719.2.6 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-819.2.7 :SENSitivity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-819.2.8 :SOURce EXTernal|INTernal{,EXTernal|,INTernal} . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-819.2.9 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-819.2.10 :TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-919.3 COMBine Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1019.3.1 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-1019.4 CORRection Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11


xxxiii

19.4.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1119.4.2 :COLLect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.2.1 [:ACQUire] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.2.2 :METHod PMETer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.2.3 :SAVE [<name>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.3 :CSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.3.1 [:SELect] <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.3.2 STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1219.4.4 :OFFSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1319.4.4.1 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1319.4.4.2 :PHASe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1319.4.4.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1319.4.5 :LOSS|:GAIN|:SLOPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1319.4.5.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.5.2 [:OUTPut] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.5.2.1 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.5.2.2 :PHASe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.6 :EDELay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.6.1 [:TIME] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.6.2 :DISTance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1419.4.6.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7 :RVELocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7.1 :MEDIum COAX|WAVeguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7.2 :COAX <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7.3 :WAVeguide <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7.3.1 :FCUToff <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.4.7.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1519.5 CURRent Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1719.5.1 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1819.5.1.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1819.5.2 :ALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1819.5.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1819.5.2.2 :SEARch <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1819.5.2.3 :SOURce INTernal|DIODe|PMETer|MMHead . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.2.4 :BANDwidth|:BWIDth <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.2.4.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.3 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.4 [:LEVel] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.4.1 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1919.5.4.1.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2019.5.4.1.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2019.5.4.1.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2019.5.4.1.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2019.5.4.1.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2019.5.4.2 :TRIGgered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21


xxxiv

19.5.4.2.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.4.2.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.4.2.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.4.2.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.5 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.5.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2119.5.5.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.5.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.5.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.5.5 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.6 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.7 :MODE FIXed|SWEep|LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2219.5.8 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.8.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.8.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.8.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.8.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.9 :RANGe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.9.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.10 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2319.5.10.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.11 :SLEW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.12 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.12.1 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.12.2 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.12.3 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.13 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2419.5.14 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2519.6 DM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2619.6.1 :FORMat <modulation format> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-2719.6.3 :SOURce EXTernal|PRBS|CALibrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.4 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.4.1 [:SOURce] INTernal|EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.4.2 :ICORrection <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.4.3 :QCORrection <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2719.6.5 :IQRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.5.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.5.2 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.6 :LEAKage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.6.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.6.2 [:MAGNitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.6.3 :ANGLe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.7 :QUADrature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2819.6.7.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29


xxxv

19.6.7.2 :ANGLe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.8 :COUPling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.8.1 [:ALL] AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.8.2 :DATA AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.8.3 :CLOCk AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.9 :THReshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.9.1 [:ALL] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.9.2 :DATA <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.9.3 :CLOCk <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2919.6.10 :DMODe SERial|PARallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.11 :FRAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.11.1 :SOURce INTernal|EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.12 :POLarity [:ALL] NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.12.1 :I<n> NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.12.2 :Q<n> NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.12.3 :ICLock NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.12.4 :QCLock NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.13 :CLOCk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3019.6.13.1 :SOURce NONE|INTernal|EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3119.7 FM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3219.7.1 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3219.7.2 [:DEViation] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3219.7.3 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3219.7.3.1 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.3.2 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.3.3 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.4 :INTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.4.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.5 :MODE LOCKed|UNLocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3319.7.6 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3419.7.7 :SENSitivity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3419.7.8 :SOURce EXTernal|INTernal{,EXTernal|,INTernal} . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3419.7.9 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3419.8 FORCe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3519.8.1 :CDOWn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3519.8.1.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3619.8.1.2 :SOFFset <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3619.8.1.3 :NRUNs <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3719.8.1.4 :RLDerivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3719.8.1.4.1 :FACCeptance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3719.8.1.4.2 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3719.8.1.4.3 :RMAXimum <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3819.8.1.4.4 :RVERify <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3819.8.2 :CONFigure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.1 :ABRake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39


xxxvi

19.8.2.1.1 :GAIN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.1.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.1.3 :THReshold <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.2 :GRADe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.2.1 :LEVel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.2.2 :SOURce <INTernal|EXTernal> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3919.8.2.2.3 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4019.8.2.3 [:VEHicle] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4019.8.2.3.1 :DCOefficient <numeric_value>,<numeric_value>,<numeric_value>

[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4019.8.2.3.2 :DINertia <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4019.8.2.3.3 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4019.8.2.3.4 TCOefficient <numeric_value>,<numeric_value>,<numeric_value>

[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4119.8.2.3.5 :TINertia <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4119.8.2.3.6 :WEIGht <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4119.8.3 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4119.8.4 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4219.8.5 :RLSimulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4219.8.5.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4219.9 FREQuency Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-4319.9.1 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4319.9.2 [:CW|:FIXed] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4319.9.2.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4319.9.3 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4419.9.4 :MODE CW|FIXed|SWEep|LIST|SENSe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4419.9.5 :MULTiplier <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4419.9.6 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4419.9.7 :RESolution <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.7.1 AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.8 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.8.1 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.8.2 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.8.3 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4519.9.9 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4619.9.10 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4619.10 FUNCtion Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4719.10.1 [:SHAPe] <source_shape> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4719.10.2 :MODE <source_mode> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4719.11 LIST Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4819.11.1 :AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4919.11.1.1 :DEPTh <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4919.11.1.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4919.11.2 :APRobe <numeric_list>{,<numeric_list>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4919.11.2.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-49


xxxvii

19.11.3 :CONCurrent <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4919.11.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.3.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4 :CONTrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.1 :APOWer <Boolean>{,<Boolean>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.2 :BLOWer <Boolean>{,<Boolean>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.2.1 :POINTs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.3 :COMPressor <Boolean>{,<Boolean>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.4.3.1 :POINTs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.5 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.6 :CURRent <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.6.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5019.11.7 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.8 :DWELl <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.8.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.9 :FREQuency <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.9.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.10 :GENeration DSEQuence|SEQuence|DCONcurrent|CONCurrent . . . . . . . . . . . . . . . . 19-5119.11.11 :PULM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.11.1 :STATe <Boolean>{,<Boolean>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.11.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5119.11.12 :POWer <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.12.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.13 :RESistance <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.13.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.14 :RTIMe <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.14.1 :POINTs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.15 :SEQuence <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.15.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.15.2 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.16 :TEMPerature <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.16.1 :POINTs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5219.11.17 :VOLTage <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5319.11.17.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5319.12 MARKer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.1 :AMPLitude <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.2 :AOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.3 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.4 :MODE FREQuency|POSition|DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.5 :POINt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5419.12.6 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5519.12.7 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5519.13 PHASe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5619.13.1 [:ADJust] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-56


xxxviii

19.13.1.1 :STEP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5619.13.2 :SOURce INTernal|EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5619.13.3 :REFerence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5619.14 PM Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5719.14.1 [:DEViation] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5719.14.2 :SENSitivity <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5719.14.3 :MODE LOCKed|UNLocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5719.14.4 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5819.14.5 :SOURce EXTernal|INTernal{,EXTernal|,INTernal} . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5819.14.6 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5819.14.7 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5819.14.8 :INTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.14.8.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.14.9 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.14.9.1 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.14.9.2 :COUPling AC|DC|GROund . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.14.9.3 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5919.15 POWer Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6019.15.1 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6119.15.1.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6119.15.2 :ALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6119.15.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6119.15.2.2 :SEARch <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6119.15.2.3 :SOURce INTernal|DIODe|PMETer|MMHead . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.2.4 :BANDwidth|:BWIDth <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.2.4.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.3 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.4 [:LEVel] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.4.1 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6219.15.4.1.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6319.15.4.1.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6319.15.4.1.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6319.15.4.1.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6319.15.4.2 :TRIGgered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6319.15.4.2.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.4.2.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.4.2.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.4.2.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.5 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.5.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.5.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6419.15.5.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.5.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.5.5 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.6 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-65


xxxix

19.15.7 :MODE FIXed|SWEep|LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.8 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.8.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6519.15.8.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.8.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.8.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.9 :RANGe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.9.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.10 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.10.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-6619.15.11 :SLEW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6619.15.12 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6719.15.12.1 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6719.15.12.2 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6719.15.12.3 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6719.15.13 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6719.15.14 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-6719.16 PULse Modulation Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6819.16.1 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6819.16.1.1 :HYSTeresis <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6819.16.1.2 :IMPedance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6819.16.1.3 :LEVel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6819.16.1.4 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6919.16.2 :INTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6919.16.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6919.16.3 MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6919.16.4 :POLarity NORMal|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6919.16.5 :SOURce EXTernal|INTernal{,EXTernal|,INTernal} . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7019.16.6 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7019.17 PULSe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7119.17.1 :PERiod <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7119.17.2 :WIDTh <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7119.17.3 :DCYCle <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7119.17.4 :HOLD WIDTh|DCYCle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7119.17.5 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.6 :DOUBle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.6.1 [:STATE] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.6.2 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.7 :TRANsition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.7.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.7.2 [:LEADing] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7219.17.7.3 :TRAiling <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7319.17.7.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7319.17.8 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7319.17.9 :POLarity NORMal|COMPlement|INVerted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-73


xl

19.18 RESistance Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7419.18.1 [:LEVel] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.1 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.1.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.1.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.1.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.1.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.2 :TRIGgered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7519.18.1.2.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.1.2.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.1.2.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.1.2.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.2 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.2.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.2.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.2.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7619.18.2.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.3 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.3.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.3.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.3.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.3.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.4 :SLEW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.5 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.6 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7719.18.6.1 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.6.2 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.6.3 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.7 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.8 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.9 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7819.18.10 :MODE FIXed|SWEep|LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7919.18.11 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7919.18.11.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7919.18.12 :RANGe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7919.18.12.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7919.19 ROSCillator Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.1 [:INTernal] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.1.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.2 :EXTernal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.3 :SOURce INTernal|EXTernal|NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.19.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8019.20 SPEed Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8219.20.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-82


xli

19.20.2 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8219.20.3 :SSDLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8219.20.3.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8319.20.3.2 :LATime <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8319.20.3.3 :STIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8419.21 SWEep Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8519.21.1 :TIME <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8519.21.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8519.21.1.2 :LLIMit <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8519.21.2 :DWELl <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8519.21.2.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8619.21.3 :DIRection UP|DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8619.21.4 :MODE AUTO|MANual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8619.21.5 :SPACing LINear|LOGarithmic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8619.21.6 :GENeration STEPped|ANALog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8619.21.7 :STEP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8719.21.8 :POINts <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8719.21.9 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8719.22 TEMPeratureSubsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8819.22.1 :APRobe <numeric_list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-8819.22.2 :DWELl <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8819.22.3 :LCONstants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8919.22.3.1 :DERivative <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8919.22.3.2 [:GAIN] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8919.22.3.3 :INTegral <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8919.22.4 :MODE FIXed|LIST|PROGram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9019.22.5 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9019.22.5.1 [:HIGH] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9019.22.5.1.1 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9019.22.5.1.2 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9019.22.5.1.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.1.4 :TOUT <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.1.5 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.2 :LOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.2.1 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.2.2 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.2.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9119.22.5.2.4 :TOUT <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9219.22.5.2.5 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9219.22.6 :RTIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9219.22.7 [:SPOint] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9219.23 VOLTage Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9319.23.1 :ATTenuation <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9419.23.1.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9419.23.2 :ALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-94


xlii

19.23.2.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9419.23.2.2 :SEARch <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9419.23.2.3 :SOURce INTernal|DIODe|PMETer|MMHead . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.2.4 :BANDwidth|:BWIDth <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.2.4.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.3 :CENTer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.4 [:LEVel] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.4.1 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9519.23.4.1.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9619.23.4.1.1.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9619.23.4.1.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9619.23.4.1.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9619.23.4.1.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9619.23.4.2 :TRIGgered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.4.2.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.4.2.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.4.2.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.4.2.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.5 :LIMit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.5.1 [:AMPLitude] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9719.23.5.2 :OFFSet <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.5.3 :HIGH <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.5.4 :LOW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.5.5 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.6 :MANual <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.7 :MODE FIXed|SWEep|LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9819.23.8 :PROTection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.8.1 [:LEVel] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.8.2 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.8.3 :TRIPped? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.8.4 :CLEar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.9 :RANGe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.9.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.10 :REFerence <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9919.23.10.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.11 :SLEW <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.12 :SPAN <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.12.1 :HOLD <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.12.2 :LINK CENTer|STARt|STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.12.3 :FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.13 :STARt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10019.23.14 :STOP <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-101


xliii

Chapter 20 STATus Subsystem

20.1 :OPERation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-320.1.1 :BIT<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-320.1.2 :CONDition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-320.1.3 :ENABle <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-320.1.4 [:EVENt]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-420.1.5 :MAP <NRf>,<NRf> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-420.1.6 :NTRansition <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-420.1.7 :PTRansition <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-420.2 :PRESet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-420.3 :QUEStionable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.1 :BIT<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.2 :CONDition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.3 :ENABle <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.4 [:EVENt]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.5 :MAP <NRf>,<NRf> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.6 :NTRansition <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-720.3.7 :PTRansition <NRf> | <non-decimal numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7

Chapter 21 SYSTem Subsystem

21.1 :ALTernate <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-321.1.1 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-321.2 :BEEPer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-321.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-321.2.2 [:IMMediate][<frequency>[,<time>[,<volume>]]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.2.3 :STATe <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.2.4 :TIME <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-421.2.5 :VOLume <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.3 :CAPability? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.4 :COMMunicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.4.1 :CENTronics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-421.4.1.1 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2 :GPIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2.1 :RDEVice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2.1.1 :ADDRess <numeric_value>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2.1.2 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2.2 [:SELF] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.2.2.1 :ADDRess <numeric_value>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . 21-521.4.3 :SERial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-621.4.3.1 :CONTrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-621.4.3.1.1 :DTR ON|OFF|STANdard|IBFull . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-621.4.3.1.2 :RTS ON|OFF|STANdard|IBFull|RFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-621.4.3.2 :FEED <data_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-721.4.3.3 [:RECeive] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7


xliv

21.4.3.3.1 :BAUD <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-721.4.3.3.2 :BITS <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-721.4.3.3.3 :PACE XON|ACK|NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-721.4.3.3.3.1 :THReshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.3.4 :PARity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.3.4.1 :CHECk <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.3.4.2 [:TYPE] EVEN|ODD|ZERO|ONE|NONE|IGNore . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.3.5 :SBITs <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.4 :TRANsmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-821.4.3.4.1 :AUTO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.2 :BAUD <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.3 :BITS <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.4 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.5 :PACE XON|ACK|NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.6 :PARity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.6.1 [:TYPE] EVEN|ODD|ZERO|ONE|NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.3.4.7 :SBITs <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-921.4.4 :SOCKet <n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.1 :ADDRess <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.2 :CONNect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.3 :DISConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.4 :FEED <n> <data_handle>{,<data_handle>} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.4.1 :OCONdition <event_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.4.2 :SCONdition <event_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.5 :LISTen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.6 :PORT <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1021.4.4.7 :TYPE TCP|UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1121.5 :CPON <card_destination>|ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1121.6 :CTYPe? <card_destination> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1121.7 :DATE <year>,<month>,<day> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1121.8 :ERRor Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1121.8.1 The Error/Event Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-1321.8.2 Error/Event numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.3 No Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.4 ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.5 CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.5.1 ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.5.2 [NEXT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.6 COUNt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1421.8.7 :ENABle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1521.8.7.1 :ADD <numeric list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1521.8.7.2 :DELete <numeric list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1521.8.7.3 [:LIST] <numeric list> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1521.8.8 [NEXT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1521.8.9 Command Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15


xlv

21.8.10 Execution Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1921.8.11 Device-Specific Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2521.8.12 Query Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2621.8.13 Power On Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2721.8.14 User Request Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2721.8.15 Request Control Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2821.8.16 Operation Complete Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2821.9 :HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2821.9.1 :HEADers? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2821.9.2 :SYNTax? <command_header> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3121.10 :KEY <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3221.10.1 :CATalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3221.10.2 :DEFine <numeric_value>,<block>[,<string>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3221.10.3 :DELete <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3221.11 :KLOCk <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3321.12 :LANGuage <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3321.13 :LFRequency<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3321.13.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3321.14 :LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3421.14.1 :OWNer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3421.14.2 :RELease . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3421.14.3 :REQuest? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3421.15 :PASSword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3521.15.1 :CDISable <password> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21-3521.15.2 [:CENable] <password> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3521.15.2.1 :STATe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3521.15.3 :NEW <current password>,<new password> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3521.16 :PRESet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3521.17 :SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3621.17.1 :IMMediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3621.17.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3621.18 :SET <block data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3621.19 :TIME <hour>,<minute>,<second> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3721.19.1 :TIMer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3821.19.1.1 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3821.19.1.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3821.20 :TZONe <hour> [,<minute>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3821.21 :VERSion? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-38

Chapter 22 TEST Subsystem

Chapter 23 TRACe | DATA

23.1 :CATalog? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-223.2 :COPY <trace_name>, ( <trace_name> | <data_handle> ) . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2


xlvi

23.3 [:DATA] <trace_name>,(<block>|<dif_expression>| (<numeric_value>{,<numeric_value>})) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-223.3.1 :LINE <trace_name>,<numeric_value>,<numeric_value>, <numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-323.3.2 :PREamble? <trace_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-323.3.3 :VALue <trace_name>,<numeric_value>,<numeric_value> . . . . . . . . . . . . . . . . . . . . . 23-323.4 :DEFine <trace_name>[,(<numeric_value>|<trace_name>)] . . . . . . . . . . . . . . . . . . . . . . . . 23-323.5 :DELete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-423.5.1 [:NAME] <trace_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-423.5.2 :ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-423.6 :FEED <trace_name>, ( <data_handle> | NONE ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-423.6.1 :CONTrol <trace_name>, ALWays | OCONdition | NEXT | NEVer . . . . . . . . . . . . . . . 23-423.6.2 :OCONdition <trace_name>, <condition_expr> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-523.7 :FREE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-523.8 :POINts <trace_name>[,<numeric_value>] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-523.8.1 :AUTO <trace_name>,(<Boolean>|ONCE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5

Chapter 24 TRIGger Subsystem

24.1 ARM-TRIGger Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-124.2 Model Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-224.2.1 IDLE State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-224.2.2 Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-224.2.3 Event Detection Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-324.3 Sequence Event Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-424.4 Expanded Capability Trigger Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-524.4.1 LAYer Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-624.4.2 Standard SEQuences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-724.4.3 Subservient Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-724.5 ABORt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1224.6 ARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1224.6.1 [:SEQuence] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1224.6.1.1 :DEFine <sequence_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1224.6.1.1.1 MGRules <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1324.6.1.2 [:LAYer] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1424.6.1.2.1 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1424.6.1.2.2 :COUPling AC|DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1424.6.1.2.3 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1424.6.1.2.3.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1424.6.1.2.4 :ECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1524.6.1.2.5 :ECOunt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1524.6.1.2.6 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1524.6.1.2.6.1 :HPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1524.6.1.2.6.2 [:LPASs] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1524.6.1.2.7 :HYSTeresis <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-16


xlvii

24.6.1.2.8 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1624.6.1.2.9 :LEVel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1624.6.1.2.9.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1624.6.1.2.10 :LINK <event_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1724.6.1.2.11 PROTocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-1724.6.1.2.11.1 VXI SYNChronous|SSYNchronous|ASYNchronous . . . . . . . . . . . . . . . . . 24-1724.6.1.2.12 :SIGNal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1724.6.1.2.13 :SLOPe POSitive|NEGative|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1824.6.1.2.14 :SOURce <parameter> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1824.6.1.2.15 :TIMer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1924.6.1.2.16 :TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1924.6.1.2.17 :TYPE EDGE | VIDeo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1924.6.1.2.18 :VIDeo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1924.6.1.2.18.1 :FIELd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1924.6.1.2.18.2 :FORMat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2024.6.1.2.18.3 :LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2024.6.1.2.18.4 :SSIGnal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2024.7 INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2124.7.1 :CONTinuous <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2124.7.1.1 [:ALL] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2224.7.1.2 :NAME <sequence_name>,<Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2224.7.1.3 :SEQuence <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2224.7.2 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2224.7.2.1 [:ALL] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2224.7.2.2 :NAME <sequence_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.7.2.3 :SEQuence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.7.3 :POFLag INCLude | EXCLude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.8 TRIGger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.8.1 [:SEQuence] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.8.1.1 :ATRigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2324.8.1.1.1 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2424.8.1.2 :COUNt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2424.8.1.3 :COUPling AC|DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2424.8.1.4 : DEFine <sequence_name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2424.8.1.4.1 MGRules <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2524.8.1.5 :DELay <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2524.8.1.5.1 :AUTO <Boolean>|ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.6 :ECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.7 :ECOunt <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8 :FILTer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8.1 :HPASs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8.1.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8.1.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8.2 [:LPASs] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2624.8.1.8.2.1 :FREQuency <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-27


xlviii

24.8.1.8.2.2 [:STATe] <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2724.8.1.9 :HOLDoff <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2724.8.1.10 :HYSTeresis <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2724.8.1.11 [:IMMediate] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2724.8.1.12 :LEVel <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2824.8.1.12.1 :AUTO <Boolean> | ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2824.8.1.13 :LINK <event_handle> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2824.8.1.14 :PROTocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2824.8.1.14.1 :VXI SYNChronous|SSYNchronous|ASYNchronous . . . . . . . . . . . . . . . . . . . . 24-2924.8.1.15 :SIGNal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2924.8.1.16 :SLOPe POSitive|NEGative|EITHer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2924.8.1.17 :SOURce <parameter> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2924.8.1.18 :TIMer <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3024.8.1.19 :TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3024.8.1.20 :TYPE EDGE | VIDeo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21 :VIDeo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.1 :FIELd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.1.1 [:NUMBer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.1.2 :SELect ODD | EVEN | ALL | NUMBer . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.2 :FORMat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.2.1 :LPFRame <numeric_variable> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3124.8.1.21.3 :LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3224.8.1.21.3.1 [:NUMBer] <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3224.8.1.21.3.2 :SELect ALL | NUMBer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3224.8.1.21.4 :SSIGnal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-3224.8.1.21.4.1 :POLarity POSitive | NEGative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-32

Chapter 25 UNIT Subsystem

25.1 :ANGLe DEG|RAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-125.2 :CURRent, :POWer, and :VOLTage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-125.3 :TEMPerature C|CEL|F|FAR|K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-225.4 :TIME HOUR|MINute|SECond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2

Chapter 26 VXI Subsystem

26.1 :CONFigure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-326.1.1 :DNUMber? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-326.1.2 :HIERarchy? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-326.1.2.1 :ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-426.1.2.2 :VERBose? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-426.1.2.2.1 :ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-426.1.3 :INFormation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-426.1.3.1 :ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-626.1.3.2 :VERBose? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-626.1.3.3 :ALL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-6


il

26.1.4 :LADDress? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-626.1.5 :NUMBer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-726.2 REGister . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-726.2.1 :READ? <register> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-726.2.1.1 :VERBose? <register> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-826.2.2 :WRITe (<numeric_value> | <register>), <data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-826.3 :RESet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-826.3.1 :VERBose? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.4 :SELect <logical_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5 :WSPRotocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5.1 :COMMand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5.1.1 [:ANY] <data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5.1.2 :AHLine <hand_id>,<line_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5.1.3 :AILine <int_id>,<line_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-926.5.1.4 :AMControl <response_mask> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.5 :ANO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.6 :BAVailable <Boolean>,<byte> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.7 :BNO <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.8 :BRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.9 :CEVent <Boolean>,<event_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.10 :CLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1026.5.1.11 :CLOCk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.12 :CRESponse <response_mask> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.13 :ENO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.14 :GDEVice <logical_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.15 :ICOMmander <logical_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.16 :RDEVice <logical_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.17 :RHANdlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1126.5.1.18 :RHLine <hand_id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.19 :RILine <int_id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.20 :RINTerrupter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.21 :RMODid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.22 :RPERror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.23 :RPRotocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.24 :RSTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1226.5.1.25 :RSARea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.1.26 :SLModid <Boolean>,<MODID 6-0> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.1.27 :SLOCk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.1.28 :SUModid <Boolean>,<MODID 12-7> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.1.29 :TRIGger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.2 :MESSage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.2.1 :RECeive? <count>|<terminator> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.2.2 :SEND <message_string> [,(END|NEND)] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1326.5.3 :QUERy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.1 [:ANY]? <data> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-14


l

26.5.3.2 :AHLine? <hand_id>,<line_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.3 :AILine? <int_id>,<line_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.4 :AMControl? <response_mask> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.5 :ANO? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.6 :BNO? <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1426.5.3.7 :BRQ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.8 :CEVent? <Boolean>,<event_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.9 :CRESponse? <response_mask> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.10 :ENO? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.11 :RDEVice? <logical_address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.12 :RHANdlers? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.13 :RHLine? <hand_id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1526.5.3.14 :RILine? <int_id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.15 :RINTerrupter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.16 :RMODid? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.17 :RPERror? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.18 :RPRotocol? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.19 :RSTB? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.20 :RSARea? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1626.5.3.21 :SLModid? <Boolean>,<MODID 6-0> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1726.5.3.22 :SUModid? <Boolean>,<MODID 12-7> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1726.5.4 :RESPonse? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-17


li


lii

1 Introduction1.1 Requirements

This volume of the SCPI standard, “Command Reference,” shall be used in conjunction withthe “Syntax and Style” volume.

1.2 OrganizationThe first chapter in this volume of the SCPI standard describes the SCPI model that is usedin defining the functional areas of SCPI. The subsequent chapters describe each functionalarea, known as a subsystem, and are in alphabetic order by subsystem name.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Introduction 1-1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


1-2 Introduction

2 Instrument ModelA model is used within SCPI as a means of achieving compatibility. SCPI concerns itselfwith three types of compatibility. The first form of compatibility is called verticalcompatibility. Vertical compatibility is where two instruments of the same type haveidentical controls (e.g. two oscilloscopes both have the same controls for their timebases,triggers, and voltage settings).

The second form of compatibility is called horizontal compatibility. Horizontal compatibilityis where two instruments can make the same measurement, regardless of the actualmeasurement techniques used. To be horizontally compatible, both instruments would usethe same commands to make this measurement. For example, both an oscilloscope and acounter can perform a risetime measurement on a pulse. The two instruments are said to behorizontally compatible if the same command is used in both instruments.

The third form of compatibility is called functional compatibility. Functional compatibility iswhere two instruments which perform the same function do so with the same commands. Forexample, a spectrum analyzer and an rf source may both sweep in frequency. If the samefrequency and sweep commands are used in both instruments, they would be functionallycompatible in this area.

Figure 2-1, “Model of a Programmable Instrument,” represents the way in which instrumentfunctionality is viewed and categorized by SCPI. The purpose of this categorization is toprovide organization and consistency between the various commands available in SCPI forall the different types of instrumentation. The model defines where elements of the languagemust be assigned in the SCPI hierarchy. Major areas of signal functionality are shownbroken into blocks; each of these blocks are major command subtrees in SCPI. In thisvolume of the SCPI standard, each subtree is discussed in its own chapter.

The model describes the flow of measurement and applied signal data through theinstrument. The administrative data flows associated with commands, queries, performingcalibrations, mass memory accesses, and other related functions are not included in thismodel. The model does not define how an instrument handles or formats data internally. In

Figure 2-1 Model of a Programmable Instrument

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Instrument Model 2-1

Figure 2-1, data flow is represented by solid arrows and control flow is represented bydashed arrows.

Individual instruments shall only implement those blocks which apply to theirimplementation. For example, a voltmeter which has a single input and no user addressablememory might include the measurement function, TRIGger, and FORMat blocks.

Similarly, a non-triggered, single output power supply might include the signal generationand FORMat blocks.

An instrument with a particular block is not always required to implement a subtree or anycommands associated with that block. This occurs when the block exists in a fixedconfiguration that does not conflict with related commands, and that have the *RST defaultvalues. For example, an instrument might have a fixed TTL level external trigger, with noadjustable TRIGger parameters. In this case no part of the TRIGger subsystem need beimplemented. However, if trigger controls exist, those controls shall be implemented asdefined in the TRIGger subsystem.

2.1 Signal RoutingThe purpose of the signal routing block is to control the routing of signals between aninstrument’s signal ports and its internal signal functionality. Signal routing also controls theconnection from signal port to signal port, where such capability exists. The commandswhich control this block are described in the SCPI tree under the ROUTe subsystem. Theimplementation of this subsystem is optional for those instruments that have fixedconnections to the measurement function block or the signal generation block.

2.1.1 Setting the Destination for Data Flow HP063eThe FEED model works well when the user is focused on setting the source for the data flowinto a block. Occasionally, the user’s focus in on the destination of data flow from a block.When this view is appropriate, a DESTination <data_handle> command is used.

Figure 2-2 Simplified Model for a Sensor Instrument

Figure 2-3 Simplified Model for a Source Instrument

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


2-2 Instrument Model Signal Routing

DESTination is an event; it has no query form. The command sets one or more FEEDsettings to known values. Assume the subsystem where the DESTination command islocated could be accessed with a <data_handle> of <source_data_handle>. WhenDESTination <data_handle> is executed, any FEED command which is currently set to<source_data_handle> shall be set to “”. The FEED command under the <data_handle>subsystem shall be set to <source_data_handle>. Any subsystem which may appear in the<data_handle> shall contain a FEED command. An allowed value of the <data_handle> forthat FEED command shall be <source_data_handle>.

2.2 Measurement Function HP066

The measurement function block converts a physical signal into an internal data form that isavailable for formatting into bus data. It may perform the additional tasks of signalconditioning and post conversion calculation. The measurement function box is subdividedinto three distinct parts: INPut, SENSe, and CALCulate. These are shown as solid boxes inFigure 2-4, “Expanded Measurement Function Model.” The dotted boxes shown representblocks from Figure 2-1, “Model of a Programmable Instrument.”

The subdivisions INPut, SENSe, and CALCulate are not detailed in the “Model of aProgrammable Instrument” figure because at this lower level of division, functionality acrossdifferent instruments can no longer be considered horizontally compatible. For example,measuring the frequency of a signal is done in SENSe block on a counter, but is done in theCALCulate block in a spectrum analyzer. The two instruments are considered compatiblesince they both can perform the function. However, the horizontal compatibility only occursat the high level MEASurement commands.

2.2.1 INPutThe purpose of the INPut block is to condition the incoming signal before it is converted intodata by the SENSe block. INPut block functions include filtering, biasing, frequencyconversion (such as a mixer or prescaler function), and attenuation. The INPut block appearsin the SCPI tree under the INPut subsystem. The implementation of this subsystem isoptional for those instruments that have no INPut block characteristics.

Figure 2-4 Expanded Measurement Function Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Instrument Model Measurement Function 2-3

2.2.2 SENSeThe purpose of the SENSe block is to convert signal(s) into internal data that can bemanipulated by normal computer techniques. The commands associated with the SENSeblock control the various characteristics of the conversion process. Examples are range,resolution, gate time, normal mode rejection, etc. This block does not include anymathematical manipulation of the data after it has been converted.

The SENSe commands appear in the SCPI tree under the SENSe subsystem. The SENSeblock is required for all sensor instruments, since the nature of a bus programmableinstrument implies a conversion from an electrical signal to a “number.” However, theSENSe subsystem contains a large number of subservient subsystems, subdividing thedifferent signal characteristics being sensed. An instrument is required to only implement theappropriate commands from those subservient subsystems that apply.

2.2.3 CALCulateThe purpose of the CALCulate block is to convert or derive sensed data into a form moreuseful to the application. Typical calculations include converting units, and postprocessingcalculations (for example, calculation of rise time from a time domain waveform). TheCALCulate commands are described in the CALCulate subsystem.

2.3 Signal GenerationThe signal generation block is responsible for the conversion of data into physical signals. Itmay perform additional tasks of preconversion calculation and signal conditioning. Thesignal generation box is subdivided into three distinct parts: CALCulate, SOURce, andOUTPut. These are shown as solid boxes in Figure 2-5, “Expanded Signal GenerationModel.” The dotted boxes shown represent blocks from Figure 2-1, “Model of aProgrammable Instrument.”

The subdivisions CALCulate, SOURce, and OUTPut are not detailed in the “Model of aProgrammable Instrument,” because at this lower level of division, functionality acrossdifferent instruments can no longer be considered horizontally compatible.

2.3.1 OUTPutThe purpose of the OUTPut block is to condition the outgoing signal after it has beengenerated. The OUTPut block functions include filtering, biasing, frequency conversion(such as a mixer function), and attenuation. The OUTPut block appears in the SCPI tree

Figure 2-5 Expanded Signal Generation Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


2-4 Instrument Model Signal Generation

under the OUTPut subsystem. As with the INPut block in sensor-type instruments, this blockappears in all source-type instruments, though the commands may not.

2.3.2 SOURceThe purpose of the SOURce block is to generate a signal based on specified characteristicsand/or supplied data. The commands associated with this block describe the characteristicsof the generated signal.

The SOURce commands are described in the SOURce subsystem. The SOURce block isrequired for all source instruments. The SOURce subsystem contains a large number ofsubservient subsystems, sub-dividing the different signal characteristics being sourced. Aninstrument is only required to implement the appropriate commands from those subservientsubsystems that apply.

2.3.3 CALCulateThe purpose of the CALCulate block is to convert application data to account for anomaliesin generating a signal, such as correcting for external effects, converting units and changingdomains. The commands associated with the CALCulate block are defined in the CALCulatesubsystem.

2.4 TRIGgerThe purpose of the TRIGger block is to provide an instrument with synchronizationcapability with external events. The TRIGger block is described in chapter 22, and appearsin the SCPI tree as TRIGger, ARM, INITiate, and ABORt subsystems. Two models exist inthe TRIGger block, one complex and the other simple. Both models may be reduced to alevel that corresponds to the sophistication of an instrument’s trigger capabilities.

2.5 MEMoryThe purpose of the MEMory block is to hold data inside the instrument. The memory may beimplicit and inaccessible to the user (for example, internal calibration data), and may befixed (for example, current measurement data) or may be allocated and user-addressed.

The allocation of memory appears in SCPI under the MEMory subsystem. The manipulationof memory is performed by commands throughout the SENSe, SOURce, FORMat, DISPlay,and other subsystems. While every programmable instrument contains memory, not all suchinstruments provide the user with explicit control of this memory. In such cases there is norequirement to implement the MEMory subsystem.

2.6 FORMatThe purpose of the format block is to convert between data representations, especially on thedata that is transferred over the external interface. An example is conversion of internal dataformats to ASCII.

Formatting appears in SCPI under the FORMat subsystem. All instruments are required touse the formats described in IEEE 488.2.

2.7 Internal Routing TWIR01

The instrument model presented so far introduced the fundamental elements or blocks fromwhich an instrument is constructed, and defined a simple or lamina arrangement of theconnections between those blocks, known as the “Lamina Model.” This model is adequate

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Instrument Model TRIGger 2-5

for many instruments. In some instruments the connections may not be as shown, as multipleinstances of certain individual blocks from the Lamina Model may exist in the instrument. Insuch instruments the connections between blocks may be programmable. Each instance of ablock is differentiated by means of the numeric suffix used with the block name.

2.7.1 Data and Control Flow TWIR01

All of the solid lines in the Lamina Model represent data flow between the blocks. Theexternal signal (often electrical) can be considered as data, since it contains information. In asensor type instrument using the Lamina Model, this data is routed through the ROUTeblock into the INPut block, the data then flows into the SENSe block, then on to theCALCulate block, and finally into the DISPlay block or to the system controller over thebus. In a source type instrument using the Lamina Model, data from the controller flows overthe bus, through the CALCulate block, then through the SOURce block. Finally, the data inthe form of an external signal (often electrical) flows into the OUTPut block, and is thendistributed through the ROUTe block.

Obviously, each block has points where data flow is absorbed and emitted. Many blockshave only one point where the data is absorbed and one point where data is emitted, howeverthere is no restriction on how many of either of these points a block must have, further thenumber of points where data is absorbed and the number of points where data is emitted donot have to appear in equal numbers.

When describing the data flow, the SCPI model specifies for each point where data isabsorbed where that data is obtained from. This selection of data flow into a block is madewith the FEED command.

There are certain restrictions that apply to the data FEED for each block; these restrictionsare enumerated under each block’s command description for its FEED. That is, a particularblock’s FEED is only allowed access to certain points in the data stream, generally the FEEDmust select a block which is of the same type as the block that immediately precedes it in inthe instrument model described earlier. For example a SENSe block which deals withphysical signals, is not allowed to FEED data from a CALCulate block, which is in aninternal format, typically numeric data. Further, SENSe blocks are only allowed to FEEDdata from INPut blocks. Instruments that effectively have no INPut functionality, that is noform of signal conditioning, still are considered to have INPut blocks, so an INPut isavailable to be specified as the FEED of the SENSe block. A block, such as the INPut blockjust described, is called a null block.

Associated with the data flow is a control mechanism to ensure the coherent processing ofthe data. Each process has points where control flow is absorbed and emitted. There is norestriction on how many of either of these control flow points a block must have. A controlflow carries messages or events. These messages or events are absorbed from a control flowby a process, to control the progress and direction of the process. In turn, each process emitsmessages or events that are used by other processes. The action of moving from one processto another is an event. Each process may be sub-divided into a series of steps, the actionfrom moving from one step to another is also an event.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


2-6 Instrument Model Internal Routing

In a particular instrument, there will be a number of control flows established as part of theinstrument’s configuration. A typical example is found in the TRIGger block, where the finallayer in a trigger sequence generates an event that causes the “device action” to beperformed, and a subsequent event is returned by the block(s) performing the device actionto indicate its completion. Another example, is one where the completion of a dataacquistion by the SENSe block is an event that is used by the CALCulate block toautomatically start the calculation process.

In certain cases some of the control flows may be programmable, allowing a user to selectthe controlling events. When describing the control flow, the SCPI model specifies for eachpoint where control information flows in, where it obtains its control flow from. Theselection of a control flow into a block is made with the LINK command.

2.7.2 Numeric Suffixes TWIR01

Numeric suffixes are associated with each block to provide them with a unique identifier.The way in which a block with a particular suffix is related to other blocks in an instrumentdepends upon the model employed. The next section describes the Lamina Model and theclosely related Cloned Model, also described is the Amorphous SENSe Model.

2.7.3 Lamina and Cloned Models TWIR01

The Model of a Programmable instrument shows one instance of each of the major blocks(or subsystems) that are available in SCPI. In this case each block is given a numeric suffixof 1. This numeric suffix is not usually shown, as it may be defaulted. The relationshipbetween the blocks is fixed in the order shown. For example, Figure 2-6 shows the LaminaModel for a sensor instrument where the name of each block is shown in its explicit form.

The Cloned Model repeats the Lamina Model as many times as required. Each repetition ofthe Lamina Model is accompanied with a different numeric suffix, incremented by 1 fromthe last. The cloned model is suitable for instruments that have multiple independentcapabilities. For example, shown in Figure 2-7 is the Cloned Model that could be used torepresent a multiple independent capability source instrument.

Figure 2-6 Lamina Model for a Sensor Instrument

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Instrument Model Internal Routing 2-7

2.7.3.1 FEED Exceptions TWIR01

As mentioned earlier, a particular block’s FEED is only allowed access to certain points inthe data stream, generally the FEED must select a block which is of the same type as theblock that immediately precedes it, in the Instrument Model.

CALCulate typically follows this rule, obtaining data from the preceding block, which in thecase of a sensor instrument would be the SENSe block. However, where an implementationpermits, CALCulate blocks may be cascaded to provide complex functionality, it ispermissible for a CALCulate block to use another CALCulate block as its FEED, as shownin Figure 2-8:

DISPlay is also a special case, it may obtain data from any point where the data is in aninternal format, typically numeric data. Examples include a CALCulate block or a SENSeblock.

2.7.3.2 Amorphous SENSe Model TWIR01

In certain sensor instruments there are SENSe blocks that produce parallel independentresults, where certain parts of the SENSe subsystem are shared. A distinguishing feature ofthe Amorphous SENSe Model is that the SENSe block has more than one INPut block

Figure 2-7 Cloned Model for a Multi-Channel Instrument

Figure 2-8 Cascaded CALCulate Blocks

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



attached to it. In this model the numeric suffix associated with the INPut block is associatedwith the subsystems of the SENSe block, not the SENSe itself. Thus INPut<n>, where <n>is a number, would relate to the subsystems of SENSe such as, SENSe:VOLTage<n>,SENSe:CORRection<n> or SENSe:DETector<n>. This is typical, unless a particularsubsystem of SENSe has been explicitly configured differently, to provide different oradditional combinations of functionality.

One example, is where a SENSe block with two power sensors, provides two POWer resultsand a cross-product result such as a POWer:RATio. Another example, is where a SENSeblock with two voltage sensors and two independent time sweep capabilities can be arrangedto provide four different results.

2.7.3.3 Other Subsystems TWIR01

Only one instance of certain blocks (or subsystems) is permitted in an instrument, these areFORMat, INSTrument, MEMory, MMEMory, STATus, SYSTem and TRACe. In mostinstruments there is only one DISPlay, since it is rare to find instruments with two or moredisplays that are entirely separate and distinct.

2.7.4 FEED <data_handle> TWIR01

The parameter to a FEED command is <data_handle>. All <data_handle>s are defined to beIEEE 488.2 STRING PROGRAM DATA. Along a data stream there are discrete pointswhere data may be picked up. These points have names that are called <data_handle>s. Forblocks with a single point where data is emitted, the block name with its numeric suffix isthe <data_handle>. For example, the <data_handle> for CALCulate3 is the string“CALCulate3”.

Note that the <data_handle> in the FEED command may consist of either long or shortforms mnemonics. However the query shall return the short form and shall omit any defaultnodes. Thus, the query for the above example would return the string “CALC3”.

The <data_handle>s for the different SENSe block found in each of the model, is describedin the following sections.

2.7.4.1 Sensor Function Selection TWIR01

Selecting a sensor’s function effects the data flow inside of the SENSe block. Selecting aparticular <sensor_function> enables the data flow associated with it. If a <sensor_function>is enabled then there must be a <data_handle> associated with the data flow generated bythat function. A SENSe block that has only a single point where data is emitted has a singleSENSe:FUNCtion selected. The selections are mutually exclusive of one another, that isenabling one function would disable another. In the case shown in Figure 2-10, theSENSe:FUNCtion selected is “RESistance”, since it is the only data flow emitted from theblock, SENSe1 is all that is needed to create a unique <data_handle> for this case.

In instruments which have amorphous SENSe blocks one or more functions can be enabledsimultaneously within the same block, that is selecting a function adds to the list of currentlyenabled functions. Such a SENSe block has one or more points where data is emitted, thusthe SENSe block and its suffix is no longer sufficient to distinguish the different data flows.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



It is necessary for the <data_handle> for these data flows to include the SENSe:FUNCtionthat generated the flow, along with the SENSe block and its numeric suffix.

In Figure 2-9, the sensed characteristic alone is not sufficient, to uniquely specify a function,and therefore cannot be used to uniquely indentify a data flow. By including in the<sensor_function> the INPut block number(s) associated with a particular data flow, withinthe SENSe block, a unique specification for the <sensor_function> and thus a unique<data_handle> can be formed. Where the <sensor_function> is included in a <data_handle>,the SENSe node with the optional numeric suffix of 1, may be omitted altogether, sincemany instruments that employ an amorphous SENSe block, will have only one SENSeblock, that is SENSe1.

Figure 2-9 Amorphous SENSe Block with Cross-Product

Figure 2-10 Single Function Active SENSe Block

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



A specification of a <sensor_function> shall consist of the function and optionally the INPutblock number. The default INPut suffix is 1. For the cross-product POWer:RATio, bothINPuts must be included. To define an INPut block in the specification, only the INPutsuffix is included, and not the mnemonic INPut. For the example above the<sensor_function>s and corresponding <data_handle>s are, respectively from top to bottom:

DESCRIPTION <sensor_function> <data_handle>The power function on INPut1 "POWer 1" "SENSe:POWer 1"The power ratio on INPut1 & INPut2 "POWer:RATio 1,2" "SENSe:POWer:RATio 1,2"The power function on INPut2 "POWer 2" "SENSe:POWer 2"

The amorphous SENSe block has an additional level of complexity, where SENSesubsystems (or sub-blocks) are used in combination as shown in Figure 2-11.

Figure 2-11 shows an amorphous SENSe block with shared SWEep subsystems, and thecorresponding <sensor_function>s. It should be noted that the function part of thespecification indicates the physical characteristic being sensed, and not which subsystem ofSENSe is used. The subsystems used are specified by association with the INPut block, inthe example above VOLTage1 and CORRection1 are tied to the data flow associated withINPut1. Where the association is not as specified above, the subsystem with its numericsuffix is appended to the specification after the literal token ’ON’. Note how SWEep1associated with INPut1 and SWEep2 associated with INPut2 can be defaulted, as they followthe default relationship of an amorphous SENSe block.

(1) "VOLTage:AC 1 ON SWEep1" or "VOLTage:AC 1"(2) "VOLTage:AC 2 ON SWEep1"(3) "VOLTage:AC 1 ON SWEep2"(4) "VOLTage:AC 2 ON SWEep2" or "VOLTage:AC 2"

Figure 2-11 Amorphous SENSe Block with Shared SWEep

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The <data_handle> is then the <sensor_function> preceded by the SENSe block and itssuffix. Thus a FEED for a display trace from an amorphous SENSe block, as shown above,might look like:

DISPlay:WINDow:TRACe:FEED “SENSe1:VOLTage:AC 2 ON SWEep1"

2.7.4.2 FEEDs from CALCulate Sub-Blocks TWIR01

The CALCulate block has only one data stream through it. The CALCulate block is dividedinto smaller sub-blocks, which correspond to the subsystems found in the CALCulatesubsystem.

Due to the discrete way in which each active sub-block exists, the data stream is accessibleafter each sub-block, where permitted by the implementation. The name of the CALCulateblock and its numeric suffix is not sufficient to select the intermediate points. Therefore the<data_handle> to access these intermediate points is comprised of the CALCulate blockname and numeric suffix followed by a colon (:) and the name of a CALCulate sub-block.For example, if a CALCulate consists of MATH1, TRANsform, followed by MATH2, thenthe <data_handle> to select the data flow after the TRANsform, but before MATH2, wouldbe the string “CALCulate:TRANsform”

HP0862.7.5 COMBineThe COMBine block acts to combine several data streams or signals. Each separate input toa COMBine block has a FEED command.

The output is the sum of the inputs. For example if the inputs are complex vectorsrepresenting waveforms with certain phases, then the ouput is the linear combination of theinputs which is also a complex vector.

Several different FEED commands might possibly specify the same <data_handle>, in effectrouting a single data stream into multiple subsystems.

2.7.6 Memory Associated with Data Flow TWIR01

In the Model of a Programmable Instrument a MEMory block is shown adjacent to the otherblocks in the model. For the user area memory this appears to be the correct model, however,for “instrument data” this proves to be cumbersome. A better model for “instrument data” isobtained by imagining that memory is something that pervades the whole model, any pointalong the data flow potentially may have memory associated with it. In general termsmemory exists at all points along this flow of data.

The examples in Figure 2-12 show how memory is associated with the simplest of blocks, itthen shows how memory is associated with a CALCulate block consisting of threesub-blocks. This is a very simple model to present to the user; at every point along the dataflow memory exists. The fact that it exists, does not mean that a particular implementationhas to allow the user access to it, as the data may not be in a form useful to the user. If accessis provided to these intermediate memory stores, certain restrictions may apply depending onthe memory usage. Within this model there are two types of memory:

TRANSIENT - memory and data are retained only long enough to be used bynext step in data flow

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



STATIC - memory is permanently allocated and data is retained, until next“acquisition”

If the memory is transient then it is not possible to obtain data from it after the data hasflowed past this point. Thus, querying such a point will not return anything, until new dataflows into the newly created transient memory. This would occur if such a query were sentin the same program message as an INITiate command.

Static memory is permanently allocated to the specified point in the data flow. Any dataflowing past this point will fill this memory, and the data at that point may be queried at anytime. However, should a new data flow start, for example with an INITiate, then the contentsof the memory shall be replaced with the new data.

The names used in querying memory should reflect where they occur in the data flow. Tobest achieve this the “handles” given to these points for connecting blocks together are alsoappropriate in data query.

There is a third type of memory, user memory which is already defined in theTRACe|DATA subsystem.

Given the FEED mechanism it is possible for a TRACe name, such as MY-TRACE, to tapthe data flow. Every time that new data flows past the “tapped” point, MY-TRACE will beupdated with the new data. While this may be useful, a significant benefit can be achievedby providing a control mechanism that selectively allows data into the TRACe, upon aspecified condition of events. For example, it should be possible to set up the control so thatMY-TRACE will only receive new data when a limit test fails.

Figure 2-12 MEMory Association with a Generic and a CALCulate Block

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



It can be seen that a user can create a TRACe, such as MY- TRACE, that may track the“tapped” point, but MY-TRACE and the memory at the tapped point are distinct andseparate. Note that the memory at that point will always (while it exists) reflect the latestdata flow, while MY-TRACE may not since the data flow into it may be gated. It is notpermitted to create TRACe | DATA names identical to any data handles.

2.7.7 Querying the Data Flow TWIR01

SCPI allows the data flow to be queried, so that a system controller can obtain intermediateresults. This is only possible where the data flow is in an internal format, typically numericdata. That is, if the data flow is some physical characteristic such as an electrical signal, thenthe data flow at such a point is not queryable.

The form of the query is generally the block name followed by :DATA?. In certain cases,this either does not provide a unique data flow, or more resolution is required than just theblock level. The SENSe:DATA? query has an optional function name as a parameter todefine the particular data flow required out of the SENSe block. An implementation mayallow access to the data flow after each sub-block subsystem in the CALCulate block. Thus,the query becomes the heirarchical name of the sub-block followed by :DATA?, for examplethe data flow after MATH1 could be obtained with CALCulate:MATH1:DATA?. Thereturned data is affected by the format subsystem.

2.7.8 <event_handle> TWIR01

The <event_handle> is the way events are described that are used by the LINK commandsthroughout SCPI. Events may exist in all blocks of the Instrument Model, although aparticular implementation will dictate what events are available to be used with each LINKcommand implemented.

The general form of <event_handle> is: to be determined

Events that are commonplace in instruments, are those found in the TRIGger subsystem; theaction of exiting any layer generates an event. The <event_handle>s to reference theseTRIGger generated events are of the form:

“ARM[:SEQuence[:LAYer]]” or “TRIGger[:SEQuence]”

Other common examples include completion of a process in a block or an instrument statetransition.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3 Measurement InstructionsThe purpose of the MEASure group of instructions is to acquire data using a set of high-levelinstructions. The MEASure group of instructions have a duality, in that they exhibitcommand and query characteristics. The exception to this is CONFigure, which has distinctquery and command forms. These instructions are independent of the block diagram andrefer to the characteristics of the signal being measured. These instructions are intended to beused with the measurement <functions> referenced later in this chapter.

The MEASure group of commands are structured to allow the user to trade offinterchangeability with fine control of the measurement process. MEASure? provides acomplete capability where the instrument is configured, a measurement taken, and resultsreturned in one operation. Often, more precise control of the measurement is required.Therefore, MEASure? is complemented by providing two commands, CONFigure andREAD?. CONFigure performs the configuration portion of the measurement and READ?performs the data acquisition, postprocessing, and data output portions of the measurement.This allows the user to perform a generic configuration of the measurement throughCONFigure and then customize the measurement by changing particularinstrument-dependent functions. The READ? then completes the measurement process.

READ?, in turn, is broken down into two additional commands INITiate[:IMMediate] andFETCh?. INITiate[:IMMediate] performs the data acquisition. This command is described inchapter 22. FETCh? performs the postprocessing function and returns the data. This allowsthe user to perform several different FETCh? functions on a single set of acquired data. Forexample, an oscilloscope can acquire measurement data that can yield many different signalcharacteristics such as frequency or AC and DC voltages. Thus, a transient signal may becaptured once using a MEASure?, READ? or INITiate. A FETCh? may then be used toobtain each of the different signal characteristics without reacquiring a new measurement.

MEASure? provides the best compatibility between instruments because no knowledge ofthe instrument is required to perform the operation. CONFigure/READ? is less compatible ifinstrument reconfiguration is performed between the CONFigure and READ? operations.This is because the reconfiguration is, by necessity, instrument-specific. FETCh? is also lesscompatible because knowledge of the instrument is necessary to determine whether thenecessary information has been captured by the instrument. For example, an oscilloscopecan capture both rise time and pulse width in a single acquisition. Therefore, if pulse widthwas acquired through a MEASure? command, it would be possible to FETCh? rise time.However, if pulse width were measured with a counter, the rise time information might notbe available without performing another data acquisition. Therefore FETCh? could not beused.

Changing certain parts of an instrument’s configuration shall cause existing measurementdata to be invalidated. Specifically, in figure 2-1, “Generalized Model of a ProgrammableInstrument” in chapter 2, “Instrument Model,” any reconfiguration of signal routing,measurement function, signal generation and/or trigger shall cause existing readings to beinvalidated. For example, the sequence:

INITiate;CONFIGure:VOLTage;FETCh:VOLTage?

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Measurement Instructions 3-1

would cause an error to be generated as the data was invalidated by the CONFigurecommand. Reconfiguring the display or format blocks shall not have this effect.

KEYWORD PARAMETER FORM NOTESCONFigure:<function> <parameters>[,<source list>]FETCh[:<function>]? <parameters>[,<source list>] [query only]READ[:<function>]? <parameters>[,<source list>] [query only]MEASure:<function>?<parameters>[,<source list>] [query only]

3.1 CONFigure:<function> <parameters>[,<source list>]Sets up the instrument in order to perform the measurement specified by the function.Individual functions are described in <functions> later in this chapter. The parameters of thiscommand are described in the individual function descriptions. The execution of theCONFigure command may affect the value of any other setting in the instrument. The stateof the instrument is not specified after the execution of this command, except that asubsequent READ? QUERY operation would perform the specified function.

If parameters are omitted, they shall assume the values specified by the particular functiondescription. Parameters may be defaulted from the right by omitting them, or anywhere bysubstituting the keyword DEFault. DEFault must be accepted as a parameter for thiscommand.

The query form of the command, CONFigure?, returns the setup configured by the lastCONFigure or MEASure? query. If the instrument state has changed through receivingcommands other than CONFigure or MEASure?, the information returned by a CONFigure?may not reflect the actual measurement conditions. However, it is permissible for aninstrument to attempt to track these changes and construct an accurate CONFigure queryresponse. The format of the response data is <STRING RESPONSE DATA> which is of theform:

“<function> <parameters>”

For example, if the previous CONFigure command:CONFIGURE:VOLTage:AC 5,.001

had been executed, the query CONFigure? would return:“VOLT:AC 5.0,0.001"

A special parameter type is the <source list>. The <source list> is syntactically a <channellist> as described in “Syntax and Style.” The purpose of the <source list> is to specify thephysical port which is the source of the measurement. For example, (@2) would specify thatthe measurement should occur on channel 2. Multiple channels can be specified by usingmultiple channels in the channel list. For example, (@1,3:5,9) specifies that measurementsare to be taken on channels 1,3,4,5, and 9. SCPI does not specify if the acquisitions aresimultaneous or sequential. A function which requires multiple channels, such as timeinterval, would specify each channel as a separate list. For example, (@1),(@2) wouldspecify a two-channel measurement between channels 1 and 2. A multiple channel, multiplemeasurement is specified by using multiple channels in each of the lists. For example,

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-2 Measurement Instructions

(@1,2),(@3,4) specifies a pair of two-channel measurements, the first between channels 1and 3 and the second between channels 2 and 4.

At *RST, the configuration is set to a device-dependent value.

3.2 FETCh[:<function>]? <parameters>[,<source list>]Retrieves the measurements taken by the INITiate command and places them into thedevice’s output buffer. By specifying a function as part of a compound header, the devicewill retrieve the value of the function requested derived from the data taken by the latestINITiate command. For instance, even if a WAVeform was the original function when themeasurement was taken, functions that can be calculated from the stored data can beFETChed. When <function> is omitted, the last <function> fetched, read, or measured shallbe used.

The FETCh? query will return data any time that the last reading is valid. Data becomesinvalid under the following conditions:

When *RST is executed,

When an INITiate is executed.

When there is any reconfiguration of signal routing, measurement function, signalgeneration and/or trigger blocks.

When the sensor begins acquisition of a new reading.

If data is invalid, the FETCh? query shall not be complete until all data is valid. Theexceptions to this are, if the instrument is in the trigger IDLE state and the data is invalid, orthe instrument has been reconfigured as defined above and no new measurement has beeninitiated. In such cases, the FETCh? routine shall generate an error -230 and no result shallbe returned. A common cause for this error is receiving a FETCh? after a *RST.

Parameters are allowed in the FETCh? query. They may be defaulted from the right byomitting them, or in any other position by substituting the keyword DEFault. DEFault mustbe accepted as a parameter for this query. If a parameter is specified, it is used in thecalculation if applicable. If the parameter is invalid because it conflicts with the acquireddata, an error -221 shall be generated. If the instrument receives a parameter which isunexpected (too many parameters), it shall process the query and return the data. Theunexpected parameter shall be ignored, and the “command warning” bit of the “dataQUEStionable” status register shall be set.

PH018

A special parameter type is the <source list>. The <source list> is syntactically a <channellist> as described in “Syntax and Style.” The purpose of the <source list> is to specify thephysical port which is the source of the measurement. For example, (@2) would specify thatthe measurement should occur on channel 2. Multiple channels can be specified by usingmultiple channels in the channel list. For example, (@1,3:5,9) specifies that measurementsare to be taken on channels 1,3,4,5, and 9. SCPI does not specify if the acquisitions aresimultaneous or sequential. A function which requires multiple channels, such as timeinterval, would specify each channel as a separate list. For example, (@1),(@2) wouldspecify a two-channel measurement between channels 1 and 2. A multiple channel, multiple

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



measurement is specified by using multiple channels in each of the lists. For example,(@1,2),(@3,4) specifies a pair of two-channel measurements, the first between channels 1and 3 and the second between channels 2 and 4.

The format of the returned data is determined by the FORMat command.

3.3 READ[:<function>]? <parameters> [,<source list>]The READ? query is identical to:

ABORt;INITiate; FETCh[:<function>]? <parameters>[,<source list>]

The READ? function provides a method of performing a FETCh? operation on fresh data.

A common application is to use the READ? in conjunction with a CONFigure command inorder to provide a MEASure? capability in which the application programmer is allowed toprovide fine adjustments to the instrument’s block diagram. For example,

CONFigure:VOLTage:RISE:TIME 10 PCT, 90 PCT, 0.001 SSWEep:TIME .05 S VOLTage:AC:RANGe 5 V READ:VOLTage:RISE:TIME?

Allows the applications programmer to specify the amplitude sensitivity and sweep time inorder to provide the exact measurement needed.

If parameters are omitted, they are assumed to be those currently in use. Parameters may bedefaulted from the right by omitting them, or anywhere by substituting the keywordDEFault. DEFault shall be accepted as a parameter for this query. If the instrument receivesa parameter which is unexpected (too many parameters), it shall process the query and returnthe data, ignoring the unexpected parameter and shall also set the “command warning” bit ofthe “data QUEStionable” status register.

A special parameter set is the <source list>. The <source list> is syntactically a <channellist> as described in “Syntax and Style.” The purpose of the <source list> is to specify thephysical port which is the source of the measurement. For example (@2) would specify thatthe measurement should occur on channel 2. Multiple channels can be specified by usingmultiple channels in the channel list. For example, (@1,3:5,9) specifies that measurementsare to be taken on channels 1,3,4,5, and 9. SCPI does not specify if the acquisitions aresimultaneous or sequential. A function which requires multiple channels, such as timeinterval, would specify each channel as a separate list. For example, (@1),(@2) wouldspecify a two-channel measurement between channels 1 and 2. A multiple channel, multiplemeasurement is specified by using multiple channels in each of the lists. For example,(@1,2),(@3,4) specifies a pair of two channel measurements, the first between channels 1and 3 and the second between channels 2 and 4.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



If TRIGger:SOURce BUS is selected, execution of this query shall cause an error -214 to begenerated and no data shall be returned. If ARM:SOURce BUS is selected, the same actionshall occur, except that the error returned shall be -215.

3.4 MEASure:<function>? <parameters>[,<source list>]The MEASure? query is a query identical to:

ABORt; CONFigure:<function> <parameters>; READ:<function>? <parameters>[,<source list>];

The MEASure? query provides a complete measurement sequence, including configurationand reading of the data. MEASure? is used when the generic measurement is acceptable andfine adjustment of the instrument block diagram is unnecessary.

If parameters are omitted, they shall assume the values specified by the particular functiondescription. Parameters may be defaulted from the right by omitting them, or anywhere bysubstituting the keyword DEFault. DEFault must be accepted as a parameter for this query.If the instrument receives a parameter which is unexpected (too many parameters), it shallprocess the query and return the data, ignoring the unexpected parameter and shall also setthe “command warning” bit of the “Data questionable” status register.

A special parameter set is the <source list>. The <source list> is syntactically a <channellist> as described in “Syntax and Style.” The purpose of the <source list> is to specify thephysical port which is the source of the measurement. For example (@2) would specify thatthe measurement should occur on channel 2. Multiple channels can be specified by usingmultiple channels in the channel list. For example, (@1,3:5,9) specifies that measurementsare to be taken on channels 1,3,4,5, and 9. SCPI does not specify if the acquisitions aresimultaneous or sequential. A function which requires multiple channels, such as timeinterval, would specify each channel as a separate list. For example, (@1),(@2) wouldspecify a two-channel measurement between channels 1 and 2. A multiple channel, multiplemeasurement is specified by using multiple channels in each of the lists. For example,(@1,2),(@3,4) specifies a pair of two-channel measurements, the first between channels 1and 3 and the second between channels 2 and 4.


If TRIGger:SOURce BUS is selected, execution of this query shall cause an error -214 to begenerated and no data shall be returned. If ARM:SOURce BUS is selected, the same actionshall occur, except that the error returned shall be -215.

3.5 <function>Functions define the measurement operation to be used by the MEASure?, CONFigure,READ?, and FETCh? instructions and are used directly in combination with theseinstructions. The functions used in conjunction with the MEASure?instructions are differentthan those described in the SENSe chapter, in that the MEASure? functions aresignal-oriented and potentially independent of the hardware.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



A function is described as a subtree under the CONFigure, READ?, FETCH?, andMEASure? instructions. The functions are layered into presentation, fundamentalmeasurement, and measurement function layers as follows:

MEASure[:<presentation layer>] [:<fundamental measurement layer>] :<measurement function>?

For example, to measure an array of DC Voltage measurements, we specify the following: MEASure:ARRay:VOLTage:DC?

The presentation layer defaults to a simple scalar measurement. The fundamentalmeasurement layer has a device dependent default. For example, an oscilloscope woulddefault VOLTage as its <fundamental measurement layer>. Therefore to perform a rise timemeasurement on an oscilloscope, the instrument shall accept any and all of the followingcommands:

MEASure:SCALar:VOLTage:RISE:TIME?MEASure:VOLTage:RISE:TIME?MEASure:SCALar:RISE:TIME?MEASure:RISE:TIME?

Each layer of the function can have a set of parameters associated with it. Within each set,parameters default from the right. Any parameter in a set may be optional unless thecommand description states that the parameter is required. Further, any parameter which isallowed to be defaulted may be defaulted by substituting the keyword DEFault for theparameter.

Each set of parameters is separated from the others by enclosing them in parentheses. Theexception is that the rightmost parameter set may omit the parentheses. Therefore the syntaxis as follows:

MEASure:<presentation layer> :<fundamental measurement layer> :<measurement function>? [[[(<presentation parameters>)] ,(<fundamental measurement parameters>)] ,<measurement function parameters>] [,<source list>]

For example, if we wished to measure an array of voltage rise times, where we wished toacquire 100 readings, and the approximate voltage value was 5 V, and the expected 10-90rise time was 5 ms, we could write the following query:

MEASure:ARRay:VOLTage:RISE:TIME? (100),(5 V),10,90,5 MS

The parameter group is only allowed when the corresponding header is part of the command.For example, the command:

MEASure:RISE:TIME? (5 V),10,90,5 MS

would generate an error because the fundamental measurement parameters have beenspecified without specifying the fundamental measurement layer in the header. However, as

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



the syntax shows, it is permissible to default groups of parameters from the left. Therefore itis possible to default the fundamental measurement parameters while specifying thefundamental measurement layer as follows:

MEASure:VOLTage:RISE:TIME? 10,90,5 MS

A majority of the functions share two parameters, expected value and resolution. Expectedvalue is a guess as to the actual value of the measurement. It is used instead of range becauserange is a device-dependent concept, describing the actual sensor characteristics, whileexpected value is signal-oriented, describing the expected signal.

Resolution describes the absolute resolution of the measurement. If the parameter is omitted,the instrument selects a resolution. If the instrument cannot provide a measurement at thedesired resolution, an error -231 is generated, but an answer is still returned if possible.

3.6 Presentation LayerThe purpose of the presentation layer is to handle groups of data and present them in the waythe user specifies. This area is still under discussion, and therefore most of the presentationtypes (for example, histograms, time and frequency domain waveforms, and so on) are notincluded in this release.

3.6.1 Presentation Command SummaryPRESENTATION KEYWORD PARAMETER[:SCALar]:ARRay <size>

3.6.2 [:SCALar]A SCALar or single value of the desired measurement is taken. SCALar has no associatedparameters, and is a default node at this level.

3.6.3 :ARRay <size>An array of readings is specified. No domain information (time or frequency spacing) isimplied in the record. There is one associated parameter, size. This specifies the number ofreadings to be taken. This parameter cannot be defaulted.

3.7 Fundamental Measurement LayerThe purpose of the fundamental measurement layer is to specify the fundamental signalcharacteristic being measured.

3.7.1 Fundamental Measurement Command SummaryKEYWORD PARAMETERVOLTage [<expected_value>[,<resolution>]]CURRent [<expected_value>[,<resolution>]]POWer [<expected_value>[,<resolution>]]RESistance [<expected_value>[,<resolution>]]FRESistance [<expected_value>[,<resolution>]]TEMPerature [<transducer>[,<type>[,<expected value>[,<resolution>]]]]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3.7.2 :VOLTage [<expected_value>[,<resolution>]]Measures the voltage characteristics of the signal. If resolution is not specified, theinstrument chooses a resolution based on its own tradeoffs. If <expected_value> is notspecified, either autoranging or a default range is selected.

3.7.3 :CURRent [<expected_value>[,<resolution>]]Measures the current characteristics of the signal. If resolution is not specified, theinstrument chooses a resolution based on its own tradeoffs. If <expected_value> is notspecified, either autoranging or a default range is selected.

3.7.4 :POWer [<expected_value>[,<resolution>]]Measures the power characteristics of the signal. If resolution is not specified, the instrumentchooses a resolution based on its own tradeoffs. If <expected_value> is not specified, eitherautoranging or a default range is selected.

3.7.5 :RESistance [<expected_value>[,<resolution>]]Measures the resistance at the input. If resolution is not specified, the instrument chooses aresolution based on its own tradeoffs. If <expected_value> is not specified, eitherautoranging or a default range is selected.

3.7.6 :FRESistance [<expected_value>[,<resolution>]]Measures the four-wire resistance at the input. If resolution is not specified, the instrumentchooses a resolution based on its own tradeoffs. If <expected_value> is not specified, eitherautoranging or a default range is selected.

3.7.7 :TEMPerature [<transducer>[,<type> [,<expected_value>[,<resolution>]]]] Measures the temperature at the sensor. The <transducer> parameter is character data whichcan take on the following values:

KEYWORD DESCRIPTIONTCouple ThermocoupleTHERmistor ThermistorFTHermistor Four-wire thermistorRTD Resistive temperature deviceFRTD Four-wire resistive temperature deviceIf a transducer is not specified, the instrument-dependent default is used.

JP ChangeThe <type> parameter is either character data or <NRf> format data, depending on whichtransducer is specified. If TCouple is selected, the parameter is character data specifying thethermocouple type. Examples of valid values for thermocouple type are: J,K,R,S,T,B,E, andN14.

Thermistors and four-wire thermistors use the nominal resistance value for the type, as anumeric parameter. Typical values are 2250, 5000, and 10000.

RTDs and FRTDs use a <numeric_value> which is specified by the manufacturer. Typicalvalues are 85 and 92.

If a type is not specified, an instrument-dependent default is used.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



If resolution is not specified, the instrument chooses a resolution based on its own tradeoffs.If <expected value> is not specified, either autoranging or a default range is selected.

3.8 Measurement Function LayerThis layer presents the specific functions to be measured. This layer has been broken downinto groups of measurements to provide clarity. This is only done for purposes of clarifyingthe presentation and there is no grouping provided in the tree.

PH068

A trailing :RATio node may be added to the Measurement Function layer, to request for aRATio measurement between the characteristics of two signals. The RATio taken, relates tothe signal characteristics specified by the preceding nodes.

PH068

The <source_list> consists of two <channel_list> parameters if the RATio node is employedin the command. The first <channel_list> parameter specifies the numerator and the secondone is the denominator. For example, MEASure:FREQuency:RATio? (@1),(@2) measuresthe ratio of the signal frequency of channel 1 to the signal frequency on channel 2.

PH068

The parameters, specified with a ratio measurement command, relate to the signalcharacteristics of the first <channel_list>; this is the signal which determines the numerator.

3.8.1 Simple MeasurementsThe simple measurements set the fundamental characteristics of steady state signals.

3.8.1.1 Simple Measurements Command SummaryKEYWORD PARAMETER:AC[:DC]:FREQuency [<expected_value>[,<resolution>]] :BURSt [<expected_value>[,<resolution>]] 1992 PH029A

:PRF [<expected_value>[,<resolution>]] 1992 PH029A

:PERiod [<expected_value>[,resolution>]]:PHAse [<expected_value>[,resolution>]] 1992 PH031

3.8.1.2 :ACMeasures the AC RMS characteristic of the signal.

3.8.1.3 [:DC]Measures the DC level of the signal.

3.8.1.4 :FREQuency [<expected_value>[,<resolution>]]Measures the frequency of the signal. If resolution is not specified, the instrument chooses aresolution based on its own tradeoffs. If <expected_value> is not specified, eitherautoranging or a default range is selected.

3.8.1.4.1 :BURSt [<expected_value>[,<resolution>]] PH029A

Measures the frequency of an ON-OFF modulated signal during its ON period. Such signalsare often referred to as burst signals. The characteristic to be measured is the frequencyinside the burst as is shown in Figure 3-1. If <resolution> is not specified, the instrumentchooses a resolution based on its own tradeoffs. If <expected_value> is not specified eitherauto ranging or a device dependent, particular range is selected.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3.8.1.4.2 :PRF [<expected_value>[,<resolution>]] PH029A

Measures the repetition frequency of the ON-OFF modulation of a signal that is periodicallyswitched ON and OFF. This characteristic is often referred to as Pulsed RepetitionFrequency (PRF) as shown in Figure 3-1. If <resolution> is not specified, the instrumentchooses a resolution based on its own tradeoffs. If <expected_value> is not specified eitherauto ranging or a default range is selected.

3.8.1.5 :PERiod [<expected_value>[,<resolution>]]The period (that is, 1/frequency) of a signal. If resolution is not specified, the instrument

chooses a resolution based on its own tradeoffs. If <expected_value> is not specified, eitherautoranging or a default range is selected.

PH031

3.8.1.6 :PHASe [<expected value>[,<resolution>]] Measures the PHASe. If <resolution> is not specified, the instrument chooses a resolutionbased on its own tradeoffs. If <expected value> is not specified either auto ranging or adefault range is selected.

If two channel lists are specified, the second shall be the reference.

3.8.2 Time Domain Waveform MeasurementsThese functions measure the time domain characteristics of pulsed signals.

Figure 3-2 is used to illustrate the terms being used to describe pulse signal characteristics.PH037

3.8.2.1 Waveform Measurements Command SummaryKEYWORD PARAMETER FORM:AMPLitude :LOW :HIGH :RISE :TIME [<lower reference>[,<upper reference>

[,<expected_value>[,<resolution>]]]] :OVERshoot :PREShoot

Figure 3-1 Burst Signal

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM:RTIME [<lower reference>[,<upper reference>

[,<expected_value>[,<resolution>]]]]:FALL :TIMe [<lower reference>[,<upper reference>

[,<expected_value>[,<resolution>]]]] :OVERshoot :PREShoot:FTIME [<lower reference>[,<upper reference>

[,<expected_value>[,<resolution>]]]]:NWIDth [<reference>]:PWIDth [<reference>]:PDUTycycle|:DCYCle [<reference>]:NDUTycycle [<reference>]:TMAXimum:TMINimum:MINimum :MAXimum:PTPeak 1992 PH037

3.8.2.2 :AMPLitudeAmplitude is the signal amplitude calculated by taking HIGH - LOW.

Figure 3-2 Pulse Measurement Terminology

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3.8.2.3 :LOWThis command specifies the LOW signal level. LOW is defined as the less positive of theBASE and TOP signal levels as defined in IEEE Std 194 sections 3.2.1 and 3.2.2.

3.8.2.4 :HIGHThe HIGH signal level. HIGH is defined as the more positive of the BASE and TOP signallevels as defined in IEEE Std 194 sections 3.2.1 and 3.2.2.

3.8.2.5 :RISEThis node specifies measurements on a rising edge of a waveform. This node has noassociated parameters. This node specifies the first rising edge of the waveform.

3.8.2.5.1 :TIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]]

The time interval during which the instantaneous amplitude of a pulse increases from the lowreference to high reference of the normal pulse amplitude.

This function is an alias to RTIMe. If RISE:TIME is implemented, RTIMe shall also beimplemented. It is recommended that RISE:TIME also be implemented.

Default low and high references are 10% and 90% of normal high-signal level. Thesedefaults may be changed via the parameters. The reference parameters have a default unit ofpercent. An implementation may allow the references to be entered in absolute sensor units.For example, an implementation may choose to allow the following syntax:

MEASure:VOLTage:RISE:TIME 0.2V,4.5V,.005S

to measure the 0.2 to 4.5 Volt rise time of a voltage signal.

3.8.2.5.2 :OVERshoot The difference between the HIGH and the peak amplitude to which the instantaneous pulsewaveform initially rises. This function uses the first edge of the waveform, expressed as apercentage of the waveform amplitude.

3.8.2.5.3 :PREShootThe difference between the LOW signal level and the negative peak signal value to whichthe waveform initially falls expressed as a percentage of waveform amplitude.

3.8.2.6 :RTIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]]

The time interval during which the instantaneous amplitude of a pulse increases from the lowreference to high reference of the normal pulse amplitude.

RISE:TIME is an alias to this function. If RISE:TIME is implemented, RTIMe shall also beimplemented.

Default low and high references are 10% and 90% of normal high-signal level. Thesedefaults may be changed via the parameters. The reference parameters have a default unit ofpercent. An implementation may allow the references to be entered in absolute sensor units.For example, an implementation may choose to allow the following syntax:

MEASure:VOLTage:RISE:TIME 0.2V,4.5V,.005S

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



to measure the 0.2 to 4.5 Volt rise time of a voltage signal.

3.8.2.7 :FALLThis node specifies measurements on a falling edge of a waveform. This node has noassociated parameters. This node assumes the first falling edge of the waveform.

3.8.2.7.1 :TIME [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]]

The time interval during which the instantaneous amplitude of a pulse decreases from thehigh reference to low reference of the normal pulse amplitude.

This function is an alias to FTIMe. If FALL:TIME is implemented, FTIMe shall also beimplemented. It is recommended that FALL:TIME also be implemented.

Default low and high references are 10% and 90% of normal high-signal level. Thesedefaults may be changed via the parameters.The reference parameters have a default unit ofpercent. An implementation may allow the references to be entered in absolute sensor units.For example, an implementation may choose to allow the following syntax:

MEASure:VOLTage:FALL:TIME 0.2V,4.5V,.005S

to measure the 4.5 to 0.2 Volt fall time of a voltage signal.

3.8.2.7.2 :OVERshoot The difference between the LOW and the negative peak amplitude to which theinstantaneous pulse waveform initially falls, expressed as a percentage of the waveformamplitude.

3.8.2.7.3 :PREShootThe difference between the HIGH signal level and the positive peak signal value to whichthe waveform initially rises expressed as a percentage of waveform amplitude.

3.8.2.8 :FTIMe [<low reference>[,<high reference> [,<expected_value>[,<resolution>]]]]

The time interval during which the instantaneous amplitude of a pulse decreases from thehigh reference to low reference of the normal pulse amplitude.

FALL:TIME is an alias to this function. If FALL:TIME is implemented, FTIMe shall also beimplemented.

Default low and high references are 10% and 90% of normal high-signal level. Thesedefaults may be changed via the parameters.The reference parameters have a default unit ofpercent. An implementation may allow the references to be entered in absolute sensor units.For example, an implementation may choose to allow the following syntax:

MEASure:VOLTage:FALL:TIME 0.2V,4.5V,.005S

to measure the 4.5 to 0.2 Volt fall time of a voltage signal.

3.8.2.9 :PWIDth [<reference>]The positive width expressed in seconds from the first rising edge reference to the nextfalling edge reference. The same reference is used for the rising and falling edges. The

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



default reference is defined as midway between HIGH and LOW levels. Other positivereferences may be specified by the parameter.

3.8.2.10 :NWIDth [<reference>]The negative width expressed in seconds from the first falling edge reference to the nextrising edge reference. The same reference is used for the rising and falling edges. The defaultreference is midway between HIGH and LOW levels. Other references may be specified bythe parameter.

3.8.2.11 :PDUTycycle|:DCYCle [<reference>]Positive dutycycle. The ratio of PWIDth to PERiod. The reference specifies the point on thepulse where the duty cycle is determined. This parameter defaults to 50%.

3.8.2.12 :NDUTycycle [<reference>]Negative dutycycle. The ratio of NWIDth to PERiod. The reference specifies the point onthe pulse where the duty cycle is determined. This parameter defaults to 50%.

3.8.2.13 :TMAXimum Layer:Time Domain Waveform MeasurementsThe time at which the first occurrence of the maximum voltage occurs.

3.8.2.14 :TMINimumThe time at which the first occurrence of the minimum voltage occurs.

3.8.2.15 :MINimum The MINimum command calculates the minimum value of the waveform.

3.8.2.16 :MAXimum The MAXimum command calculates the maximum value of the waveform.

3.8.2.17 :PTPeak PH037

This command measures the Peak To Peak value of the signal which is (MAXimum -MINimum).

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



4 CALCulate SubsystemThe CALCulate subsystem exists to perform postacquisition data processing. Functions inthe SENSe subsystem are related to data acquisition, while the CALCulate subsystemoperates on the data acquired by a SENSe function.

The CALCulate subsystem is logically between the SENSe subsystem and data output toeither the bus or the display. When a measurement is triggered by a MEASure command, anINITiate command, or meeting the prevailing TRIGger conditions, the SENSe subsystemcollects data. This data is transformed by CALCulate, as specified, and then passed on to theselected output. In effect, the collection of new data triggers the CALCulate subsystem. TheCALCulate subsystem may also be directed by command to perform a transform, making itpossible to change the configuration of CALCulate and consequently derive a different set ofresults from the same SENSed data set without reacquiring sense data.

The CALCulate subsystem consists of a number of independent subsystems. Each of thesubsystems is a sub-block of the CALCulate block. The data flows through the sub-blocks ina serial fashion, through the first sub-block, then onto the second sub-block and so on. Themanner in which these sub-blocks are arranged is specified in the PATH command. It ispermissible for a CALCulate block to have more than one instance of any of the sub-blocks.Instances of the same sub-block are differentiated by a numeric suffix. For example, twoindependent filters would exist as the :CALCulate:FILTer1 and the :CALCulate:FILTer2subsystem sub-blocks.

TWIR01p13

Note: The notation Xn* indicates the complex conjugate of a number. So: XX* = MAG2(X) = |X|2

HP081bKEYWORD PARAMETER FORM NOTESCALCulate :AVERage 1992 HP054

:CLEar [no query] 1992 HP054

:COUNt <numeric_value> 1992 HP054

:AUTO <Boolean> | ONCE 1992 HP054

[:STATe] <Boolean> 1992 HP054

:TCONtrol EXPonential | MOVing | NORMal | REPeat 1992 HP054

:TYPE COMPlex | ENVelope | MAXimum | MINimum | RMS | SCALar 1992 HP054

:CLIMits 1991 HP007

:FAIL? [query only] 1991 HP007

:FLIMits 1991 HP007

[:DATA]? [query only] 1991 HP007

:POINts? [query only] 1991TK056 :DATA? [query only] 1995TK056 :DATA 1995

TK032a :PREamble? [query only] 1994 :DERivative 1993 PH071 :STATe <Boolean> 1993 PH071

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate 4-1

KEYWORD PARAMETER FORM NOTES :IMMediate :AUTO <Boolean> 1992

HP068 :INTegral 1993 PH071 :STATe <Boolean> 1993 PH071 :TYPE SCALar | MOVing 1993 PH071 :LIMit 1991 HP007

:STATe <Boolean> 1991,2 HP066HP007

:CONTrol 1991 HP007

[:DATA] <numeric_value>{,<numeric_value>} 1991 HP007

:POINts? [query only] 1991 HP007

:UPPer 1991 HP007



:STATe <Boolean> 1991 HP007

:LOWer 1991 HP007



:STATe <Boolean> 1991 HP007

:FAIL? [query only] 1991 HP007

:FCOunt? [query only] 1991 HP007

:REPort 1991 HP007

[:DATA]? [query only] 1991 HP007


:CLEar 1991 HP007

:AUTO <Boolean> 1991 HP007

[:IMMediate] [no query] 1991 HP007

:INTerpolate <Boolean> 1991 HP007

:MATH [:EXPRession] <numeric_expression> 1991 TWIR01

:CATalog? <query only> 1993 HP083a [:DEFine] <numeric_expression> 1993 HP083a :DELete 1993 HP083a [:SELected] <expression_name> 1993 HP083a :ALL 1993 HP083a :NAME <expression_name> 1993 HP083a :STATe <Boolean> 1992 HP066

:SMOothing [:STATe] <Boolean> 1992 HP066

:APERture <numeric_value> :POINts <numeric_value> :STATe <Boolean> 1992 HP066

:TRANsform :HISTogram 1993 PH070 :COUNt <numeric_value> 1993

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate 4-3

KEYWORD PARAMETER FORM NOTES PH070 :ORDinate RATio | PERCent | PCT | COUNt 1993 PH070 :POINts <numeric_value> 1993 PH070 :RANGe 1993 PH070 :AUTO <Boolean> 1993 PH070 :STATe <Boolean> 1993 PH070 :TIME :STATe <Boolean> 1992 HP066

[:TYPE ] LPASs|BPASs :STIMulus STEP|IMPulse :STARt <numeric_value> :STOP <numeric_value> :SPAN <numeric_value> :CENTer <numeric_value> :POINts <numeric_value> :AUTO <Boolean>|ONCE :WINDow RECTangular|UNIForm|FLATtop |HAMMing|HANNing |FORCe|EXPonential :KBESsel <numeric_value> :EXPonential <numeric_value> :FORCe <numeric_value> :DISTance :STATe <Boolean> 1992 HP066

[:TYPE ] LPASs|BPASs :STIMulus STEP|IMPulse :STARt <numeric_value> :STOP <numeric_value> :SPAN <numeric_value> :CENTer <numeric_value> :POINts <numeric_value> :AUTO <Boolean>|ONCE :WINDow RECTangular|UNIForm|FLATtop |HAMMing|HANNing |FORCe|EXPonential :KBESsel <numeric_value> :EXPonential <numeric_value> :FORCe <numeric_value> :FREQuency :STATe <Boolean> 1992 HP066

[:TYPE ] LPASs|BPASs :STIMulus STEP|IMPulse :STARt <numeric_value> :STOP <numeric_value> :SPAN <numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-4 CALCulate

KEYWORD PARAMETER FORM NOTES :CENTer <numeric_value> :POINts <numeric_value> :AUTO <Boolean>|ONCE :WINDow RECTangular|UNIForm|FLATtop |HAMMing|HANNing |KBESsel|FORCe|EXPonential :KBESsel <numeric_value> :EXPonential <numeric_value> :FORCe <numeric_value> :PATH (MATH|TRANsform|FILTer

|SMOothing|FORMat|LIMit 1991|AVERage) 1992 HP007HP054

{,(MATH|TRANsform|FILTer [query only]|SMOothing|FORMat|LIMit 1991|AVERage)} 1992 HP007HP054

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate 4-5

4.1 :AVERage subsystemCALCulate:AVERage

HP054FL005

This subsystem provides an analytical post-processing function. The AVERage subsystemcombines successive measurements to produce a new composite result. The new result hasthe same number of points and control axis as the original measurement.

A :COUNt command is provided to specify the number of measurements to combine. When:COUNT averages are reached, the TerminalCONtrol switch specifies the operation of theaverage subsystem. The TerminalCONtrol switch can be configured to continue replacingold values with new values (MOVing), to exponentially weight new measurements(EXPonential), to automatically repeat (REPeat), or to continue adding new measurements inthe NORMal fashon, as specified by :TYPE.

The average operation differs from CALC:SMOOthing in the fact that AVERage combinesthe jth point of each measurement with the jth point of preceeding measurements, whereas inSMOOthing the jth point is processed with adjacent points (...., j-2, j-1, j, j+1, j+2, ...) of thecurrent measurement set.

A typical device action for CALC:AVERagePH075

4.1.1 :CLEarCALCulate:AVERage:CLEar

HP054

This command causes the average data to be cleared and the average counter reset to zero.

Figure 4-1 AVERage device action

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-6 CALCulate:AVERage subsystem

4.1.2 :COUNt <numeric_value>CALCulate:AVERage:COUNt

HP054

Specifies the number of measurements to combine using the :TYPE setting. After :COUNtmeasurements have been averaged, the operation of the AVERage subsystem is controlledby the setting of the :TCONtrol node.

The count for array based results is independent of the number of points in the result array.For example, an instrument which normally provides a measurement result which is a 401point array would specify an average count of two to average two results, not 802.

When averaging is ON, some devices may automatically set :COUNt values in the TRIGgersubsystem based on the AVER:COUNt value, such that the TRIGger subsystem providesenough triggers for the average.

At *RST, this value is device dependent.

4.1.2.1 :AUTO <Boolean> | ONCECALCulate:AVERage:COUNt:AUTO

HP054

AUTO ON causes the device to select a value for :COUNt which is appropriate for thecurrent measurement. Selecting AUTO ONCE will have the effect of setting AUTO ON andthen OFF.

At *RST, this value is set to OFF.

4.1.3 [:STATe] <Boolean>CALCulate:AVERage:STATe

HP054

The STATe command is used to turn averaging ON and OFF.


4.1.4 :TCONtrol EXPonential | MOVing | NORMal | REPeatCALCulate:AVERage:TCONtrol

HP054

Ed ChangeTerminalCONtrol specifies the action of the AVERage subsystem when more thanAVERage:COUNt measurement results are generated.

The parameter has the following meanings:HP081b

EXPonential Continue the average with an exponential weighting applied to old values.The additional averages are weighted using:

For :TYPE SCALar when Xn is real and :TYPE COMPlex when Xn is eitherreal or complex

AVGn = 1k Xn +

k − 1k

AVGn − 1

For :TYPE SCALar when Xn is complex

AVGn = 1k MAG(Xn) +

k − 1k

AVGn − 1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:AVERage subsystem 4-7

For :TYPE RMS when Xn is real

AVGn = √ 1kXn

2 + k − 1

kAVGn − 1

2

For :TYPE RMS when Xn is complex

AVGn = √ 1kXnXn∗ +

k − 1k

AVGn − 12

Ed Change

The exponential factor k is equal to the AVERage:COUNt value. Someinstruments may use an approximation to true exponential.

Ed ChangeOperation with EXPonential :TCON is undefined with a :TYPE setting ofMINimum, MAXimum, or ENVelope.

MOVing As new data is added the oldest data is discarded.

REPeat Clear average data and counter and restart the average process.

NORMal Additional averages continue to be accumulated according to the :TYPEselection.


4.1.5 :TYPE COMPlex | ENVelope | MAXimum | MINimum | RMS | SCALarCALCulate:AVERage:TYPE

HP054

This command selects the type of averaging, as follows:

COMPlex The points in the summation are treated as real/imaginary pairs.

AVG(n) = 1n ∑ i = 1

n

Xi

ENVelope Both the MIN and MAX values are retained.

If X n is realHP081b

MAXimum AVG(n) = MAX(X 1... Xn )

MINimum AVG(n) = MIN(X1...Xn)

RMS AVG(n) = √1n ∑ i = 1

n

Xi2

SCALar The scalar magnitude of each point is averaged.

AVG(n) = 1n ∑ i = 1

n

Xi

If X n is complexHP081b

MAXimum AVG(n) = MAX( MAG(X 1)... MAG(Xn) )

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-8 CALCulate:AVERage subsystem

MINimum AVG(n) = MIN( MAG(X1)...MAG(Xn) )

RMS AVG(n) = √1n ∑ i = 1

n

XiXi∗


AVG(n) = 1n ∑ i = 1

n

| Xi |

At *RST, this value is device dependent.HP054

4.2 :CLIMitsCALCulate:CLIMits

HP007

This node defines commands to obtain Composite LIMit results within the specifiedCALCulate. It is permissible for CALCulate to contain two or more LIMit tests. These testsmay be active simultaneously. The commands under CLIMits provide a mechanism todetermine a summary of the PASS/FAIL information, and also a way to directly ascertainwhich particular LIMit tests are failing.

4.2.1 :FAIL?CALCulate:CLIMits:FAIL?

HP007

FAIL is a summary of all the individual LIMit:FAILs. If any of the individual LIMit:FAILshave a non-zero value, indicating a failure, the composite FAIL query shall return a 1. Ifthere are no failures then a 0 shall be returned. When all the failed LIMits have beenCLEared, then the composite FAIL shall also be cleared.

4.2.2 :FLIMitsCALCulate:CLIMits:FLIMits

HP007

This node provides the information to determine the Failed LIMits, that is, identify howmany and which LIMit tests have failed. When all the failed LIMits have been CLEared,then FLIMits shall also be cleared.

4.2.2.1 [:DATA]?CALCulate:CLIMits:FLIMits:DATA?

HP007

This query returns a number or list of numbers, each number corresponds to an instance ofthe LIMit subsystem within the CALCulate block. For example, if CALC:LIMit1,CALC:LIMit2 and CALC:LIMit3 existed, the query shall return 1,3, if LIMit1 and LIMit3had failed. If there are no failures then NAN shall be returned.

4.2.2.2 :POINts?CALCulate:CLIMits:FLIMits:POINts?

HP007

This query shall return the number of failed LIMits in DATA. If there are no failures then a 0shall be returned.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:CLIMits 4-9

4.3 :DATA?CALCulate:DATA?

Provides access to the result of the CALCulate subsystem. The query form outputs thepresent CALCulate results.

This command is query-only and therefore has no *RST condition.

TK0564.3.1 :PREamble?CALCulate:DATA:PREamble?

PREamble? returns the preamble information supporting the DATA(CURVe(VALues)) butomits the following data:

DIF blocks of waveform, measurement, and delta.

DIF curve block keywords VALues and CSUM and their parameters.

The DIF difid block must contain the keyword SCOPe with the parameter of PREamble.

While the PREamble? query is designed to efficiently transmit data relating directly to thecurve, the various notes and identification parameters may be sent if absolutely required.

4.4 :DERivativeCALCulate:DERivative PH071This subsystem calculates the derivative of the points in a data set. Each point in thedifferentiated data set is the derivative at the corresponding point in the original data set(note this requires some approximation at the end points). The units of the result of thisprocess is the quotient of the currently selected amplitude units of the differentiated data andthe units of the X-axis.

4.4.1 :STATe <Boolean>CALCulate:DERivative:STATe PH071Determines whether the derivative function is enabled.

At *RST this function is OFF

4.4.2 :POINts <numeric_value>CALCulate:DERivative:POINts PH071Specifies the number of points provided to the differential algorithm. They will be centeredabout the current data point.

At *RST this value is device dependent.

4.5 :FEED <data_handle>CALCulate:FEED

TWIR01p13

Sets or queries the data flow to be fed into the CALCulate block.

At *RST, FEED shall be set to a device dependent value.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-10 CALCulate:DATA?

4.6 :FILTerCALCulate:FILTer

This subsystem defines a filtering process to be performed on the SENSe data. A filter canoperate in domains, which may or may not be the domain of the acquisition data.

4.6.1 [:GATE]CALCulate:FILTer:GATE

Specifies the or modification of the data set according to the selected parameters in a specificdomain.

4.6.1.1 :TIMECALCulate:FILTer:GATE:TIME

This filter selection will modify the acquisition data to remove or modify information in aspecified time region. Units of time are seconds.

4.6.1.1.1 :STATe <Boolean>CALCulate:FILTer:GATE:TIME:STATe

HP066

Determines whether the time filter is enabled.

At *RST, this function is OFF.

4.6.1.1.2 [:TYPE ] BPASs|NOTChCALCulate:FILTer:GATE:TIME:TYPE

Specifies what occurs to the data in the specific time region. The parameters have thefollowing meanings:

BPASs — Pass all information in specified time region and reject all else.

NOTCh — Reject all information in specified time region and pass all else.


4.6.1.1.3 :STARt <numeric_value>CALCulate:FILTer:GATE:TIME:STARt

Specifies the start time of the filter. Range is instrument- and setup-dependent.

The couplings between STARt, STOP, CENTer, and SPAN are the same as described in theSENSe subsystem.

At *RST, STARt is set to MIN.

4.6.1.1.4 :STOP <numeric_value>CALCulate:FILTer:GATE:TIME:STOP

Specifies the stop time of the filter. Range is instrument- and setup-dependent.


At *RST, STOP is set to MIN.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:FILTer 4-11

4.6.1.1.5 :SPAN <numeric_value>CALCulate:FILTer:GATE:TIME:SPAN

Specifies the time span of the filter. Range is instrument- and setup-dependent.


At *RST, SPAN is set to MIN.

4.6.1.1.6 :CENTer <numeric_value>CALCulate:FILTer:GATE:TIME:CENTer

Specifies the center time of the filter. Range is instrument- and setup-dependent.


At *RST, CENTer is set to MIN.

4.6.1.1.7 :POINts <numeric_value>CALCulate:FILTer:GATE:TIME:POINts

Specifies the number of points output by the filter subsystem.


4.6.1.1.7.1 :AUTO <Boolean>|ONCECALCulate:FILTer:GATE:TIME:POINts:AUTO

Setting AUTO ON allows POINts to be set by device-dependent parameters (for example,the size of incoming SENSe data).

At *RST, AUTO is ON.

4.6.1.1.8 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential

CALCulate:FILTer:GATE:TIME:WINDow

Specifies the type and parameter of data windowing (shaping) done prior to the filter.

Individual windowing algorithms are defined in “On the Use of Windows for HarmonicAnalysis with the Discrete Fourier Transform,” F. J. Harris, Proc. of the IEEE, Vol. 66-1,January 1978, pp 51-83.


4.6.1.1.9 :KBESsel <numeric_value>CALCulate:FILTer:GATE:TIME:KBESsel

The Kaiser BESsel command sets the parametric window parameter for the Kaiser Besselwindow.


4.6.1.1.10 :EXPonential <numeric_value>CALCulate:FILTer:GATE:TIME:EXPonential

Enters the exponential decay time constant which characterizes the EXPonential window.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-12 CALCulate:FILTer


4.6.1.1.11 :FORCe <numeric_value>CALCulate:FILTer:GATE:TIME:FORCe

Enters the time value parameter corresponding to the width of the gated portion of the inputtime record for FORCe windows.


4.6.1.2 :FREQuencyCALCulate:FILTer:GATE:FREQuency

This filter selection will modify the acquisition data to remove or modify information in aspecified frequency region.

Units are Hertz.

4.6.1.2.1 :STATe <Boolean>CALCulate:FILTer:GATE:FREQuency:STATe

HP066

Determines whether the frequency filter is enabled.


4.6.1.2.2 [:TYPE ] BPASs|NOTChCALCulate:FILTer:GATE:FREQuency:TYPE

Specifies what occurs to the data in the specific frequency region. The parameters have thefollowing meanings:

BPASs — Pass all information in specified time region and reject all else.

NOTCh — Reject all information in specified frequency region and pass all else.


4.6.1.2.3 :STARt <numeric_value>CALCulate:FILTer:GATE:FREQuency:STARt

Specifies the start frequency of the filter. Range is instrument- and setup-dependent.



4.6.1.2.4 :STOP <numeric_value>CALCulate:FILTer:GATE:FREQuency:STOP

Specifies the stop frequency of the filter. Range is instrument- and setup-dependent.



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:FILTer 4-13

4.6.1.2.5 :SPAN <numeric_value>CALCulate:FILTer:GATE:FREQuency:SPAN

Specifies the frequency span of the filter. Range is instrument- and setup-dependent.



4.6.1.2.6 :CENTer <numeric_value>CALCulate:FILTer:GATE:FREQuency:CENTer

Specifies the center frequency of the filter. Range is instrument- and setup-dependent.



4.6.1.2.7 :POINts <numeric_value>CALCulate:FILTer:GATE:FREQuency:POINts

Specifies the number of points output by the filter subsystem.


4.6.1.2.7.1 :AUTO <Boolean>|ONCECALCulate:FILTer:GATE:FREQuency:POINts:AUTO

Setting AUTO ON allows POINts to be set by device-dependent parameters (for example,the size of incoming SENSe data).


4.6.1.2.8 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential

CALCulate:FILTer:GATE:FREQuency:WINDow

Specifies the type and parameter of data windowing (shaping) done prior to the filter.

Individual windowing algorithms are defined in “On the Use of Windows for HarmonicAnalysis with the Discrete Fourier Transform,” F. J. Harris, Proc of the IEEE, Vol. 66-1,January 1978, pp 51-83.


4.6.1.2.9 :KBESsel <numeric_value>CALCulate:FILTer:GATE:FREQuency:KBESsel



4.6.1.2.10 :EXPonential <numeric_value>CALCulate:FILTer:GATE:FREQuency:EXPonential


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-14 CALCulate:FILTer


4.6.1.2.11 :FORCe <numeric_value>CALCulate:FILTer:GATE:FREQuency:FORCe



4.7 :FORMat NONE|MLINear|MLOGarithmic|PHASe|REAL |IMAGinary|SWR|GDELay |COMPlex|NYQuist|NICHols|POLar |UPHaseCALCulate:FORMat

HP002,3

Determines a simple post-processing of SENSe data. This subsystem is limited to simplepoint-by-point post processing. SENSe data description is x + jy, and if no y data, assumey=0. Regardless of the unprocessed data form, the data shall be interpreted as x + jy for thepurposes of defining the formats in the table below.

HP002

NYQuist is an optional alias for COMPlex. If NYQuist is implemented, COMPlex shall alsobe implemented.

HP002

NAME EQUATION TYPE

NONE NONE Unprocessed data

MLINear √x2 + y2 (scalar)

MLOGarithmic 10∗log(x2 + y2) (scalar, LOG is base 10)

PHASe arctan (yx

) (scalar in current angle units, ±180 degrees)

IMAGinary y (linear scalar)

REAL x (linear scalar)

COMPlex|NYQuist pair (x,y) (linear scalar) 1991HP002

POLar pair (r1, r2) 1991 r1 = √x2 + y2 1991 r2 = arctan(y/x) 1991

HP002

NICHols pair (r1, r2) 1991 r1 = 10∗log(x2 + y2) 1991

r2 = arctan(y/x) 1991HP002

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:FORMat 4-15

NAME EQUATION TYPEHP002

SWR(1 + r)(1 − r) WHERE r = MagLIN(data) (scalar)

GDELay−d(phase)

360∗d(frequency) (Scalar; units areseconds. Phasespecified in currentangle units. If currentangle units are radians,replace the constant 360with 2*PI. Thed(frequency) term isreplaced withCALCulate:GDAPerture:APERture in practice.)

UPHase UNWRAP(arctan(y/x)) (scalar in current 1991angle units)

HP003


4.7.1 :UPHaseCALCulate:FORMat:UPHase

HP003

The UPHase subsystem is used to specify how unwrapped phase is computed. A referenceposition is specified which is used as an estimate of what the unwrapped phase of calculatedresult should be. The calculated result is constrained to be within +/- 180 degrees of thereference position. Other points are calculated to produce a result which is compatible withthe above constraint and does not “wrap” when cardinal points such as +/- 180 degrees arecrossed. The reference position would typically be a well known point in a measurementsuch as the center of a band pass filter.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-16 CALCulate:FORMat

4.7.1.1 :CREFerence <numeric_value>CALCulate:FORMat:UPHase:CREFerence

HP003

The Control REFerence command designates the reference position on the independentdimension, called the control axis (typically the X axis) where the phase unwrap referencepoint is located. This value in combination with the :PREF value identifies the phase unwrapreference point.


4.7.1.2 :PREFerence <numeric value>CALCulate:FORMat:UPHase:PREFerence

HP003

The Phase REFerence command designates the phase of the phase unwrap reference point.This value in combination with the :CREFerence value identifies the reference point. TheCALC result is constrained to be within +/- 180 degrees of this value at the pointcorresponding to the :CREFerence position.


4.8 :GDAPertureCALCulate:GDAPerture

Group Delay Aperture is defined as the negative of the derivative of phase with respect tofrequency. The group delay format requires specifying an aperture over which themeasurement is made. Since the frequency span of the measurement is known, the frequencystep over the entire span can be thought of as d(freq) This function permits the setting of thataperture. APERture is tightly coupled to SPAN by the equation:

APERture = GDAPerture:SPAN/(SENSe|SOURce):FREQuency:SPAN

4.8.1 :SPAN <numeric_value>CALCulate:GDAPerture:SPAN

Specifies the aperture in Hertz. Minimum value is instrument-dependent.

At *RST, this function is set to MIN.

4.8.2 :APERture <numeric_value>CALCulate:GDAPerture:APERture

Specifies the aperture as a ratio of desired aperture span/measured frequency span.

At *RST, this value is set to MIN.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:GDAPerture 4-17

4.9 :IMMediateCALCulate:IMMediate

Causes the CALCulate subsystem to reprocess existing SENSe data without reacquiring thedata. This permits the user to change a CALCulate subsystem, setting and output new resultswithout initiating a data acquisition.

Note that CALC:IMMediate? is semantically equivalent to CALC:IMM;DATA?. The queryform outputs the results of the new calculation.

This command describes an event and therefore has no associated *RST condition.

4.9.1 :AUTO <Boolean> CALCulate:IMMediate:AUTO

HP068

The AUTO command is used to specify if the CALCulate subsystem continually transformsthe data (AUTO ON) whenever any changes are made which would affect the CALCulatesubsystem output. With CALC:IMM:AUTO set to OFF, CALCulate only produces new datawhen data is received or when the CALC:IMMediate command is received. OnceCALC:IMM:AUTO is set to ON, the CALCulate Subsystem shall produce results when anyCALC subsystem command is processed, even when new data is not being received. Thisallows the user to make configuration changes in the CALCulate subsystem and immediatelyhave new CALC:DATA results on the same sensed data.


4.10 :INTegralCALCulate:INTegral PH071This subsystem provides a point to point integration of a data set. The result is an estimate ofthe integral of the input. The units of the result of this process is the product of the currentlyselected amplitude units of the integrated data and the units of the X- axis.

4.10.1 :STATe <Boolean>CALCulate:INTegral:STATe PH071Determines whether the integrate function is enabled.


4.10.2 :TYPE SCALar | MOVingCALCulate:INTegral:TYPE PH071Specifies whether the result is a single value (SCALar) or a set of data points (MOVing). IfSCALar is selected the result is an estimate of the definite integral over the entire data set. IfMOVing is selected each point in the integrated data set is the integral up to thecorresponding point in the original data set.

At *RST this function is set to a device dependent value.

4.11 :LIMitCALCulate:LIMit

HP007

The LIMit node collects together the commands associated with controlling and gettingreports from a single LIMit test. The LIMit test may defined as an UPPer limit, a LOWer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-18 CALCulate:IMMediate

limit, or both. A LIMit test may be defined as being scalar, that is UPPer or LOWer areprovided a single value each.

HP007

Alternatively, UPPer or LOWer may be defined as a series of points (a vector) representing awaveform limit. For such a vector limit test, each point in the series (vector) must bequalified by where it occurs with respect to the control (typically the X) axis. The CONTrolnode is used to define the points along the control axis. UPPer and LOWer represent thedependent (typically the Y) axis, and are given values corresponding to these control axispoints. That is, the first value for UPPer and LOWer corresponds to the first value ofCONTrol, the second value for UPPer and LOWer corresponds to the second value ofCONTrol, and so on. UPPer, LOWer and CONTrol shall contain the same number of points,or an error shall be generated when data processing commences. For scalar limit tests, asdescribed earlier, the CONTrol subsystem is not used.

HP007

If the data and the limit are scalar (single values), then LIMit shall produce results for eachpiece of scalar data tested. If the data and the limit are both vectors, then LIMit shall produceresults for each vector data tested. If the limit is scalar and the data is a vector, then LIMitshall perform a the limit test by treating the scalar limit as an equivalent vector (all pointshaving the same value).

4.11.1 :STATe <Boolean>CALCulate:LIMit:STATe

HP007

Is used to set or query if the LIMit test is active or not.

At *RST, this is set to OFF.

4.11.2 :CONTrolCALCulate:LIMit:CONTrol

HP007

This node collects the commands and queries used to set up the control axis of the limit data,where the limit test is not based on a single point.

4.11.2.1 [:DATA] <numeric_value>{,<numeric_value>}CALCulate:LIMit:CONTrol:DATA

HP007

Sets or queries the CONTrol axis data.

4.11.2.2 :POINts?CALCulate:LIMit:CONTrol:POINts?

HP007

The POINts? query returns the number of points currently in CONTrol:DATA.

4.11.3 :UPPerCALCulate:LIMit:UPPer

HP007

UPPer is used to define the upper limit to be used in the LIMit test. When the data is greaterthan the value specified in UPPer, LIMit shall report a fail. That is, when the data is equal tothe limit, a fail shall not be reported.

4.11.3.1 [:DATA] <numeric_value>{,<numeric_value>}CALCulate:LIMit:UPPer:DATA

HP007

Sets or queries the UPPer axis data.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:LIMit 4-19

4.11.3.2 :POINts?CALCulate:LIMit:UPPer:POINts?

HP007

The POINts? query returns the number of points currently in UPPer:DATA.

4.11.3.3 :STATe <Boolean>CALCulate:LIMit:UPPer:STATe

HP007

Sets or queries if the individual LIMit test is enabled.

At *RST, this is set to ON.

4.11.4 :LOWerCALCulate:LIMit:LOWer

HP007

LOWer is used to define the lower limit to be used in the LIMit test. When the data is lessthan the value specified in LOWer, LIMit shall report a fail. That is, when the data is equalto the limit, a fail shall not be reported.

4.11.4.1 [:DATA] <numeric_value>{,<numeric_value>}CALCulate:LIMit:LOWer:DATA

HP007

Sets or queries the LOWer axis data.

4.11.4.2 :POINts?CALCulate:LIMit:LOWer:POINts?

HP007

The POINts? query returns the number of points currently in LOWer:DATA.

4.11.4.3 :STATe <Boolean>CALCulate:LIMit:LOWer:STATe

HP007

Sets or queries if the individual LIMit test is enabled.

At *RST, this is set to ON.

4.11.5 :FAIL?CALCulate:LIMit:FAIL?

HP007

This query returns a 0 or 1, to indicate if the LIMit test has failed or not; 0 represents passand 1 represents fail.

4.11.6 :FCOunt?CALCulate:LIMit:FCOunt?

HP007

This Fail COunt query returns the number of times that the LIMit test has failed. With a 0indicating no failures. With vector limits and vector data, only one failure shall be recordedwith each (measurement) vector that is tested, even if many points are outside the limits.

4.11.7 :REPortCALCulate:LIMit:REPort

HP007

This node collects together commands to get a more detailed information on vector limittests.

4.11.7.1 [:DATA]?CALCulate:LIMit:REPort:DATA?

HP007

This query returns a number or list of numbers, each number corresponds to a value of theCONTrol variable where either the UPPer or LOWer limit test has failed. Note that: When

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-20 CALCulate:LIMit

INTerpolate ON has been selected, the returned DATA shall correspond to the points alongthe CONTrol axis where a failure has occured, which may or may not coincide with pointsdefined for CONTrol. If there are no failures then NAN shall be returned.

4.11.7.2 :POINts?CALCulate:LIMit:REPort:POINts?

HP007

This query shall return the number of points in the DATA. If there are no failures then a 0shall be returned.

4.11.8 :CLEarCALCulate:LIMit:CLEar

HP007

The CLEar node collects together the commands that are used to clear the information inDATA, FAIL and REPort.

4.11.8.1 :AUTO <Boolean> | ONCECALCulate:LIMit:CLEar:AUTO

HP007

Sets or queries if the information is to be CLEared with each INITiate command, or moreprecisely when the TRIGger state machine exits the “IDLE state.” Such an INITiate shallcause the information in FAIL, FCOunt and REPort to be cleared if AUTO is set to ON. IfAUTO is set to OFF, no such effect shall occur.

At *RST, AUTO shall be set to ON.

4.11.8.2 [:IMMediate]CALCulate:LIMit:CLEar:IMMediate

HP007

IMMediate shall cause the information in FAIL, FCOunt and REPort to be clearedIMMediately.

4.11.9 :INTerpolate <Boolean>CALCulate:LIMit:INTerpolate

HP007

Sets or queries whether or not limit tests will be performed at points between those specifiedby the CONTrol variable. The interpolation shall be straight line between points, howeverthe algorithm determining the number of samples between points is device dependent.

At *RST, it shall be OFF.

4.12 :MATHCALCulate:MATH

This subsystem permits processing of sense data in numerical expression format. Theoperators are +, -, *, / and use of constants and data arrays are permitted.

4.12.1 [:EXPRession] <numeric_expression>CALCulate:MATH:EXPRession

TWIR01p13

This subsystem controls which expression is used by the CALCulate block.

4.12.1.1 :CATalog?CALCulate:MATH:EXPRession:CATalog? HP083a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:MATH 4-21

The CATalog query lists all the defined expressions. Response is a list of comma-separatedstrings. Each string contains the name of an expression. If no expressions are currentlydefined, the response ia a null string ("").

4.12.1.2 [:DEFine] <numeric_expression>CALCulate:MATH:EXPRession:DEFine HP083aDefines the expression used for the math operations. The <numeric_expression> maycontain any of the following as operands and they may occur in any combination:

A <trace_name>

The reserved keyword IMPLied

The <data_handle> associated with another block

The reserved keyword IMPLied, refers to the IMPLied output of the previous CALCulatesub-block. The ordering of the sub-blocks is specified by the PATH command. If the MATHsubsystem appears first in the PATH, then the IMPLied keyword refers to the <data_handle>specified with the FEED command.

For example, to subtract a reference trace from the SENSe data, the following commandwould configure the MATH appropriately.

CALCulate:MATH:EXPRession (IMPLied - MY-TRACE)

This example assumes that the FEED command has been configured to select the appropriateSENSe <data_handle>. The IMPLied CALCulate data flow can be ignored and the SENSedata may be used directly in a <numeric_expression>:

CALCulate:MATH:EXPRession ( “SENSe1:POWer 3" - MY-TRACE)

At *RST, this function is undefined.

4.12.1.3 :DELeteCALCulate:MATH:EXPRession:DELete HP083aThe DELete subsytem deletes expressions.

4.12.1.3.1 [:SELected] <expression_name>CALCulate:MATH:EXPRession:DELete:SELected HP083aThis command causes the selected expression to be deleted.

4.12.1.3.2 :ALLCALCulate:MATH:EXPRession:DELete:ALL HP083aThis command causes the all expressions to be deleted.

4.12.1.4 :NAME <expression_name>CALCulate:MATH:EXPRession:NAME HP083aThe NAME command defines the name of the expression to be selected. If the expressionname, <expression_name>, already exists, then that existing expression shall be selected. Ifthe expression name does not exist, then the new name shall be selected, but no expressionshall be defined by this selection. <expression_name> is character data.

At *RST the value of NAME is device dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-22 CALCulate:MATH

4.12.2 :STATe <Boolean>CALCulate:MATH:STATe

HP066

Determines whether math processing is done.


4.13 :SMOothingCALCulate:SMOothing

This subsystem specifies point-to-point smoothing of a data set. A data point in a smootheddata set is the average of adjacent points from a single original data set. Smoothing differsfrom averaging, in which a given point is the average of corresponding points from multipledata sets or acquisitions.

4.13.1 [:STATe] <Boolean>CALCulate:SMOothing:STATe

HP066

Determines whether the smoothing algorithm is enabled.


4.13.2 :APERture <numeric_value>CALCulate:SMOothing:APERture

Specifies the size of the smoothing APERture as a ratio of smoothing aperture points/tracepoints.

At *RST, this function is device-dependent.

4.13.3 :POINts <numeric_value>CALCulate:SMOothing:POINts

Controls the number of points to be included in the running average. POINts is coupled toAPERture by the equation:

POINts = APERture * TRACe:POINts

4.14 :STATe <Boolean>CALCulate:STATe

HP066

Controls whether postprocessing is enabled. If disabled, this subsystem is effectivelytransparent.

At *RST, this is set ON.

4.15 :TRANsformCALCulate:TRANsform

TRANsform is the subsystem that permits sense data to be transformed from one domain toanother. Examples are from frequency domain to time domain or time domain to frequencydomain. This is different from a SENSe:FUNC selection of domain because in SENSe, thedata is actually collected in the selected domain, while in CALCulation:TRANsform, thedata is computed, for example, by use of Fourier Transform.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:SMOothing 4-23

4.15.1 :HISTogramCALCulate:TRANsform:HISTogram PH070This subsystem transforms the data into a histogram. The histogram provides an amplitudedistribution of the incoming signal. The points in a histogram specify the ratio between thenumber number of times a data point is within a particular amplitude belt and the totalnumber of incoming data points that participate in the transformation. The ratio is expressedas a percentage.

The resolution of the histogram is specified by the number of points of the output signal. Itdetermines the amplitude belt wherein the data points are counted, using the equation:

amplitude belt = amplitude range / histogram points

The units of the amplitude range are the currently selected amplitude units of the data to betransformed.

4.15.1.1 :COUNt <numeric_value>CALCulate:TRANsform:HISTogram:COUNt PH070This specifies the number of measurements to include in the histogram.

For scalar measurements, COUNt is the number of incoming data points that are used tocreate the histogram.

The COUNt for array based results is independent of the number of points in the result array.For example, an instrument which normally provides a measurement result which is a 401point array would specify a histogram count of two to create a histogram based on 802 datapoints.

At *RST this value is device dependent

4.15.1.2 :ORDinate RATio | PERCent | PCT | COUNtCALCulate:TRANsform:HISTogram:ORDinate PH070When ORDinate is set to RATio, the output of the HISTogram function is an absolute ratio.When ORDinate is set to PERCent, the output of the HISTogram function is PERCent(RATio*100). When ORDinate is set to COUNt, the output of the HISTogram function isthe number of points in that amplitude belt.

PCT is provided as a synonym for PERCent since IEEE 488.2 allows the use of PCT as anumeric suffix.


4.15.1.3 :POINts <numeric_value>CALCulate:TRANsform:HISTogram:POINts PH070Specifies the number of POINts (amplitude belts) in the histogram.


4.15.1.4 :RANGeCALCulate:TRANsform:HISTogram:RANGe PH070This node collects the commands used to control the size of the amplitude belts.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-24 CALCulate:TRANsform

4.15.1.4.1 :AUTO <Boolean>CALCulate:TRANsform:HISTogram:RANGe:AUTO PH070With AUTO ON, the number of output points is determined by the amplitude of theincoming data via a device dependent algorithm.

At *RST this function is set to a device dependent value.

4.15.1.5 :STATe <Boolean>CALCulate:TRANsform:HISTogram:STATe PH070Determines whether the histogram transformation is enabled.


4.15.2 :TIMECALCulate:TRANsform:TIME

Specifies a transformation of data into its equivalent time representation. The parametersspecify the time region over which the output data is transformed. The units are seconds.

4.15.2.1 :STATe <Boolean>CALCulate:TRANsform:TIME:STATe

HP066

Determines whether the time transform is enabled.


4.15.2.2 [:TYPE ] LPASs|BPASsCALCulate:TRANsform:TIME:TYPE

Selects a particular method to be used in band limiting information or the manner in whichwindows should be applied.

When LPASs is selected, the windowing shall affect only the end of the data set. LPASsrequires data to start from zero in the appropriate units, such as Hertz and seconds. If thedata set does not extend to zero, then the instrument shall either compute by extrapolationthe extra points needed to complete the data set, or shall generate an execution (-200) error.When BPASs is selected, the applied window shall affect both the start and end parts of thedata set.


4.15.2.3 :STIMulus STEP|IMPulseCALCulate:TRANsform:TIME:STIMulus

Specifies the type of stimulus to be simulated in the transform process.


4.15.2.4 :STARt <numeric_value>CALCulate:TRANsform:TIME:STARt

Specifies the start time of the output data record. Range is instrument- and setup-dependent.



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:TRANsform 4-25

4.15.2.5 :STOP <numeric_value>CALCulate:TRANsform:TIME:STOP

Specifies the stop time of the output data record. Range is instrument- and setup-dependent.



4.15.2.6 :SPAN <numeric_value>CALCulate:TRANsform:TIME:SPAN

Specifies the time span of the output data record. Range is instrument- and setup-dependent.



4.15.2.7 :CENTer <numeric_value>CALCulate:TRANsform:TIME:CENTer

Specifies the center time of the output data record. Range is instrument- and setup-dependent.



4.15.2.8 :POINts <numeric_value>CALCulate:TRANsform:TIME:POINts

Specifies the number of points output by the transform subsystem.


4.15.2.8.1 :AUTO <Boolean>|ONCECALCulate:TRANsform:TIME:POINts:AUTO

When AUTO is ON, the number of points is determined by the size of the incoming SENSeData.


4.15.2.9 :WINDow RECTangular|UNIForm|FLATtop|HAMMing |HANNing|KBESsel|FORCe|EXPonential

CALCulate:TRANsform:TIME:WINDow

Specifies the type and parameter of data windowing (shaping) done prior to thetransformation.



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



4.15.2.10 :KBESsel <numeric_value>CALCulate:TRANsform:TIME:KBESsel



4.15.2.11 :EXPonential <numeric_value>CALCulate:TRANsform:TIME:EXPonential



4.15.2.12 :FORCe <numeric_value>CALCulate:TRANsform:TIME:FORCe



4.15.3 :DISTanceCALCulate:TRANsform:DISTance

This subsystem specifies a transformation of data into its equivalent distance representation.The parameters specify the distance region over which the output data is transformed. Theunits are meters.

4.15.3.1 :STATe <Boolean>CALCulate:TRANsform:DISTance:STATe

HP066

Determines whether the distance transform is enabled.


4.15.3.2 [:TYPE ] LPASs|BPASsCALCulate:TRANsform:DISTance:TYPE

Selects a particular method to be used in limiting information or the manner in whichwindows shall be applied for the specified transform.

When LPASs is selected, the windowing shall affect only the end of the data set. LPASsrequires data to start from zero in the appropriate units, such as Hertz and seconds. If thedata set does not extend to zero, then the instrument shall either compute by extrapolationthe extra points needed to complete the data set, or shall generate an execution (-200) error.When BPASs is selected, the applied window shall affect both the start and end parts of thedata set.


4.15.3.3 :STIMulus STEP|IMPulseCALCulate:TRANsform:DISTance:STIMulus



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



4.15.3.4 :STARt <numeric_value>CALCulate:TRANsform:DISTance:STARt

Specifies the start distance of the output data record. Range is instrument- andsetup-dependent.



4.15.3.5 :STOP <numeric_value>CALCulate:TRANsform:DISTance:STOP

Specifies the stop distance of the output data record. Range is instrument- andsetup-dependent.



4.15.3.6 :SPAN <numeric_value>CALCulate:TRANsform:DISTance:SPAN

Specifies the distance span of the output data record. Range is instrument- andsetup-dependent.



4.15.3.7 :CENTer <numeric_value>CALCulate:TRANsform:DISTance:CENTer

Specifies the center distance of the output data record. Range is instrument- andsetup-dependent.



4.15.3.8 :POINts <numeric_value>CALCulate:TRANsform:DISTance:POINts


At *RST, this is set to a device-dependent value.

4.15.3.8.1 :AUTO <Boolean>|ONCECALCulate:TRANsform:DISTance:POINts:AUTO

When AUTO is ON, the number of points is determined by the size of the incoming SENSedata.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




CALCulate:TRANsform:DISTance:WINDow

Specifies the type and parameter of data windowing (shaping) done prior to thetransformation.



4.15.3.10 :KBESsel <numeric_value>CALCulate:TRANsform:DISTance:KBESsel



4.15.3.11 :EXPonential <numeric_value>CALCulate:TRANsform:DISTance:EXPonential



4.15.3.12 :FORCe <numeric_value>CALCulate:TRANsform:DISTance:FORCe



4.15.4 :FREQuencyCALCulate:TRANsform:FREQuency

This subsystem specifies a transformation of data into its equivalent frequencyrepresentation. The parameters specify the frequency region over which the output data istransformed. The units are Hertz.

4.15.4.1 :STATe <Boolean>CALCulate:TRANsform:FREQuency:STATe

HP066

Determines whether the frequency transform is enabled.


4.15.4.2 [:TYPE ] LPASs|BPASsCALCulate:TRANsform:FREQuency:TYPE

Selects a particular method to be used in limiting information or the manner in whichwindows shall be applied for the specified transform.

When LPASs is selected, the windowing shall affect only the end of the data set. LPASsrequires data to start from zero in the appropriate units, such as Hertz and seconds. If the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



data set does not extend to zero, then the instrument shall either compute by extrapolationthe extra points needed to complete the data set, or shall generate an execution (-200) error.When BPASs is selected, the applied window shall affect both the start and end parts of thedata set.


4.15.4.3 :STIMulus STEP|IMPulse CALCulate:TRANsform:FREQuency:STIMulus


At *RST, this selection is device-dependent.

4.15.4.4 :STARt <numeric_value>CALCulate:TRANsform:FREQuency:STARt

Specifies the start frequency of the output data record. Range is instrument- andsetup-dependent.



4.15.4.5 :STOP <numeric_value>CALCulate:TRANsform:FREQuency:STOP

Specifies the stop frequency of the output data record. Range is instrument- andsetup-dependent.



4.15.4.6 :SPAN <numeric_value>CALCulate:TRANsform:FREQuency:SPAN

Specifies the frequency span of the output data record. Range is instrument- andsetup-dependent.



4.15.4.7 :CENTer <numeric_value>CALCulate:TRANsform:FREQuency:CENTer

Specifies the center frequency of the output data record. Range is instrument- andsetup-dependent.



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



4.15.4.8 :POINts <numeric_value>CALCulate:TRANsform:FREQuency:POINts



4.15.4.8.1 :AUTO <Boolean>|ONCECALCulate:TRANsform:FREQuency:POINts:AUTO

When AUTO is ON, the number of points is determined by the size of the incoming SENSeData.



CALCulate:TRANsform:FREQuency:WINDow

This specifies the type and parameter of data windowing (shaping) done prior to thetransformation.



4.15.4.10 :KBESsel <numeric_value>CALCulate:TRANsform:FREQuency:KBESsel



4.15.4.11 :EXPonential <numeric_value>CALCulate:TRANsform:FREQuency:EXPonential



4.15.4.12 :FORCe <numeric_value>CALCulate:TRANsform:FREQuency:FORCe



4.16 :PATH (MATH|TRANsform|FILTer|SMOothing|FORMat|LIMit|AVERage) {,(MATH|TRANsform|FILTER|SMOothing|FORMat|LIMit|AVERage)}CALCulate:PATH

HP054HP007

This subsystem defines the order in which CALCulate subsystems are to be performed. Inmany instruments this will be fixed and instrument-dependent. If it is possible to order theoperations, then PATH is the method.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALCulate:PATH 4-31

For example, if TRANsform is first, then FILTer, and finally MATH, the following wouldbe sent:

CALCulate:PATH TRANsform,FILTer,MATH

Even if not settable, the query of PATH should return the actual order of operations.

The suffix of each subsystem used as a parameter in the PATH command corresponds to theinstance of the specified CALCulate subsystem sub-block. For example, the commandPATH FILTer1, FILTer2, sets up the data flow through the filter defined byCALCulate:FILTer1 and then through the filter defined by CALCulate:FILTer2.

TWIR01p14

At *RST, the PATH definition is set to a device-dependent setting.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-32 CALCulate:PATH

5 CALibration SubsystemThis subsystem has the function of performing system calibration.

Instrument CALibration commands tend to be very class specific. Such commands properlybelong in Volume 4 “Instrument Classes”. Therefore, expanded commands for controllinginstrument calibration may not be found in Volume 2 “Command Reference”.

KEYWORD PARAMETER FORM NOTESCALibration

TK029 [:ALL] [event; no query] 1994EDIT [:ALL]? [event; query]

:AUTO <Boolean>|ONCE :BINertia 1999 :AVErage? <numeric_value> [query only] 1999 :HSPeed <numeric_value> 1999 :INITiate [event; no query] 1999 :LSPeed <numeric_value> 1999 :NRUNs <numeric_value> 1999 :SDEviation? <numeric_value> [query only] 1999 :UPDate [event; no query] 1999 :DATA <arbitrary block program data> :PLOSs 1999 :APCoeffs <numeric_value>,<numeric_value>,... 1999 :INITiate [event; no query] 1999 :LATime <numeric_value> 1999 :STIMe <numeric_value> 1999 :UPDate [event; no query] 1999 :SOURce INTernal|EXTernal :STATe <Boolean> :VALue <numeric_value> :WARMup 1999 :INITiate [event; no query] 1999 :SPEed <numeric_value> 1999 :TIMeout <numeric_value> 1999 :ZERO :AUTO <Boolean>|ONCE :FSENsor 1999 :INITiate [event; no query] 1999 :LATime <numeric_value> 1999 :LEVel? [query only] 1999 :SPEed <numeric_value> 1999 :STIM <numeric_value> 1999 :UPDate [event; no query] 1999

TK029

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALibration 5-1

5.1 [:ALL]CALibration:ALL

TK029The CALibrate:ALL command performs the same function as the CALibrate:ALL? exceptthere is no response. An instrument shall report calibration errors through thestatus-reporting mechanism.

TK029If this command is implemented as overlapped it shall be included in the No OperationPending flag (see IEEE 488.2 chapter 12).

TK029While this command is executing the CALibrating bit of the Operation Status Conditionregister shall be set (see 9.3 of Syntax & Style).

5.2 [:ALL]?CALibration:ALL?

The ALL? query performs a full calibration of the instrument and responds with a<numeric_value> indicating the success of the calibration. A zero shall be returned ifcalibration is completed successfully; otherwise a nonzero value which represents theappropriate error number shall be returned. An instrument shall still report calibration errorsthrough the status-reporting mechanism, even though an error is reported by the value of thequery response.

5.3 :AUTO <Boolean>|ONCECALibration:AUTO

AUTO sets whether or not the instrument should perform auto calibration atdevice-dependent intervals without user intervention.

At *RST, AUTO OFF is selected.

5.4 :BINertia CALibration:BINertia

Base Inertia

For chassis dynamometers, this node describes the procedure to determine the basemechanical inertia of the dynamometer roll system (all rotating mechanical componentsoutside of the control loop). This procedure consists of an acceleration and deceleration ofthe dynamometer rolls, from which a mechanical inertia calculation is made. Thedynamometer is motored from an initial speed to a final speed at a given constantacceleration, and this interval is timed. Immediately, the dynamometer is motored back fromthe final speed to the initial speed at the same constant acceleration (inverted), and thisinterval is timed. For this pair of intervals, the force transducer output is continuouslymeasured, and the average interval force calculated. The average acceleration is calculatedusing the interval initial and final speed values, and the interval time. This data is used tocalculate the mechanical inertia (Inertia=Force/acceleration).

5.4.1 :AVERage?CALibration:BINertia:AVERage?

This query returns the running average of all base inertia values acquired since the lastCALibration:BINertia:INITiate was invoked.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-2 CALibration[:ALL]

5.4.2 :HSPeed <numeric_value>CALibration:BINertia:HSPeed

High Speed

The higher magnitude speed (m/s) of the speed interval.

At *RST, this value is set to 16.

5.4.3 :INITiateCALibration:BINertia:INITiate

Begin motoring the dynamometer through the ACCeleration/deceleration pairs, using:SOURce:ACCeleration as the acceleration/deceleration rate, from LSPeed to HSPeed andback, NRUNs times. All query commands must be accepted and responded to while thiscommand is executing. This command describes an event and therefore has no associated*RST condition.

When this command is initiated for dynamometers, the dynamometer must:

Check critical ancillaries, if any, for proper conditions: Brakes Off, Motor Contactor On,parameters within dynamometer safety limits. For conditions that prohibit operation ofthis procedure, issue appropriate warning messages, and execute the Idle Procedure.

Set the DYNO operation condition register Base Inertia Procedure bit indicating the BaseInertia is executing. Note: The DYNO operation condition register will be further definedin Volume 4.

Accelerate/decelerate the dynamometer through the speed intervals, recording time,average acceleration, average force for the specified number of runs. The data is placedin the BaseInertia table after each acceleration/deceleration is run. Update the:CALibration:BINertia:SDEViation value based on this run. End the procedure when thespecified runs are complete.

Clear the DYNO operation condition register Base Insrtia Procedure bit indicating theBase Inertia is not executing.

Issue the process complete message.

Execute the Idle Procedure.

Update the on-line mechanical inertia value, if desired.

5.4.4 :LSPeed <numeric_value>CALibration:BINertia:LSPeed

Low Speed

The lower magnitude speed (m/s) of the speed interval.


5.4.5 :NRUNs <numeric_value>CALibration:BINertia:NRUNs

Number of Runs - NRUNs

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALibration:BINertia 5-3

The number of ACCeleration/deceleration pairs to perform. NRUNs will equal the numberof base inertia values acquired.


5.4.6 :SDEViation?CALibration:BINertia:SDEViation?

Standard Deviation

This query returns the running standard deviation of all base inertia values acquired since thelast CALibration:BINertia:INITiate was invoked.

5.4.7 :UPDateCALibration:BINertia:UPDate

Place on-line the last determined average base mechanical inertia value.

This command describes an event and therefore has no associated *RST condition.

5.5 :DATA <arbitrary block program data>CALibration:DATA

Transfers the calibration data as arbitrary block program data. The query form returns thecurrent calibration data. The block is transferred into the current calibration data. If an erroroccurs during the transfer causing the calibration to be lost, an error -313 shall be generatedin addition to the execution error.

5.6 :PLOSs CALibration:PLOSs

Parasitic Loss

For chassis dynamometers this node describes the commands associated with the parasiticloss procedure. This procedure measures and, if requested, updates the parasitic losscorrections for the dynamometer. The parasitic losses are measured by operating thedynamometer at various selected speeds and measuring the force required to maintain theconstant speed. This procedure uses the :MEMory table ’PARasitic’ that defines the speedpoints at which parasitic loss measurements are taken. The parasitic loss coefficients arecalculated at the end of the procedure and reside in the memory table PCOefficient.

5.6.1 :APCoeff<numeric_value>,<numeric_value>,<numeric_value>[,<numeric_value>]:CALibration:PLOSs:APCoeff

Active Parasitic Coefficients - APCoefficients

This is the presently active parasitic loss curve used by the dynamometer. The dynamometerwill maintain coefficients for forward and reverse operations. The appropriate values mustbe placed in the APCoeff table, based on roll rotation.

5.6.2 :INITiate:CALibration:PLOSs:INITiate

This command starts the parasitic loss procedure. This is an overlapped command. Thiscommand describes an event and therefore has no associated *RST condition.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-4 CALibration:DATA



Set the DYNO operation condition register Parasitic Loss Procedure bit indicating theParasitic Loss procedure is executing. Note: The DYNO operation condition register willbe further defined in Volume 4.

Accelerate dynamometer to the first speed point defined in the PARasitic memory table.Stabilize at speed point for defined stabilization time.

Average the force at the roll surface required to maintain the speed set point over thelatency time. The average force value is placed in the PARasitic table for the specifiedspeed point. Continue until all speed points have been executed in the PARasitic table.The first zero speed in the PARasitic table ends the procedure.

Perform a curve fit on the PARasitic table data and place the coefficients in the memorytable PCoeff.

Clear the DYNO operation condition register Parasitic Loss Procedure bit indicating theparasitic loss procedure is not executing.



5.6.3 :LATime:CALibration:PLOSs:LATime

Loss Averaging Time - sec

The length of time in seconds to average the losses at a speed point.


5.6.4 :STIMe <numeric_value>CALibration:PLOSs:STIMe

Stabilization Time - sec

Time for stabilization prior to LATime.


5.6.5 :UPDate:CALibration:PLOSs:UPDate

Update the dynamometer parasitic loss coefficients contained in the table APCoeff with thecoefficients contained in memory table Pcoeff.

This command is an event and has no associated *RST condition.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALibration:PLOSs 5-5

5.7 :SOURce INTernal|EXTernalCALibration:SOURce

Controls the source of the calibration signal. If set to INTernal, a reference internal to theinstrument is selected. If SOURce is set to EXTernal, then an external reference shall beapplied.

5.8 :STATe <Boolean>CALibration:STATe

STATe is used to select if the calibration data is applied or not. If STATe is ON then theinstrument uses the calibration data for correction. If STATe OFF is selected, then nocorrection using the calibration data shall be made.

At *RST, STATe is set to ON.

5.9 :VALue <numeric_value>CALibration:VALue

Enters the value of the reference signal which is used in the calibration. For example, avoltmeter may calibrate its input to a reference signal which has a proven value of4.99327513 Volts.

5.10 :WARMupCALibration:WARMup

This node controls parameters relating to the warmup of the device.

For chassis dynamometers, this node describes the procedure to set up the conditionsrequired to ready the dynamometer for testing. The warm-up consists of running thedynamometer at a fixed speed over a period of time. Warm-up completion is defined byeither running the dynamometer for a fixed period of time, or by monitoring parasitic lossesand comparing them to a target value tolerance.

5.10.1 :INITiateCALibration:WARMup:INITiate

Start the warmup procedure.

For chassis dynamometers, motor the dynamometer roll to SPEed, and hold this speed for aTIMeout period of time. All query commands must be accepted and responded to while thiscommand is executing. This command describes an event and therefore has no associated*RST condition.



Set the DYNO operation condition register Warm up Procedure bit indicating theWarm-up is executing. Note: The DYNO operation condition register will be furtherdefined in Volume 4.

Accelerate dynamometer to the speed point defined by :CALibration:WARMup:SPEed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-6 CALibration:SOURce

Average the force at the roll surface required to maintain the speed set point over:CALIbrate:WARMup:LATime. The average force can be monitored by:SENSe:FORCe?

The procedure will end when the elapsed time is greater than:CALibration:WARMup:TIMeout.

Clear the DYNO operation condition register Warm up Procedure bit indicating theWarm-up is not executing.



5.10.2 :SPEed <numeric_value>CALibration:WARMup:SPEed

For chassis dynamometers this is the fixed roll speed (m/s) at which the warm-up will be run.


5.10.3 :TIMeout <numeric_value>CALibration:WARMup:TIMeout

For chassis dynamometers this is the length of time in seconds the warm-up will run beforeautomatically returning to zero speed.


5.11 :ZEROCALibration:ZERO

This subsystem controls the autozero calibration of the sensor.

For chassis dynamometers, this node describes the procedure to set up the conditionsrequired and perform a mathematical zero correction of the roll force measurement systemcalibration. The correction is determined from a measurement of the roll force sensor at agiven roll speed. The results are stored in the FSensorZero pre-defined table.

5.11.1 :AUTO <Boolean>|ONCECALibration:ZERO:AUTO

Controls whether autozeroing calibration occurs.


5.11.2 :FSENsor CALibration:ZERO:FSENsor

Force Sensor

For chassis dynamometers this node sets up the conditions required and performs amathematical zero correction of the roll force measurement system calibration. Thecorrection is determined from a measurement of the roll force sensor at a given roll speed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALibration:ZERO 5-7

5.11.2.1 :INITiateCALibration:ZERO:FSENsor:INITiate

This is an overlapped command. Perform the measurement of the roll force, acquiring for thelength of time specified by :LATime. This command describes an event and therefore has noassociated *RST condition.



Set the DYNO operation condition register Force Sensor Zero Procedure bit indicatingthe Zero is executing. Note: The DYNO operation condition register will be furtherdefined in Volume 4.

Accelerate dynamometer to the speed specified in :CALibration:ZERO:FSENsor:SPEed.Stabilize for :STIMe.

Average the force at the roll surface required to maintain the speed set point over the:LATime. The average force value is placed in :LEVel.

Clear the DYNO operation condition register Force Sensor Zero Procedure bit indicatingthe Zero is not executing.



5.11.2.2 :LATime <numeric_value>CALibration:ZERO:FSENsor:LATime


The length of time to average the measured zero reading.

At *RST, this value is set to 0.5.

5.11.2.3 :LEVel?CALibration:ZERO:FSENsor:LEVel?

Returns the measured force value used to determine the mathematical zero correction. Thisvalue is in units of force at the roll surface. This is query only.

5.11.2.4 :SPEed <numeric_value>CALibration:ZERO:FSENsor:SPEed

The roll speed set point for the force measurement period in m/s.


5.11.2.5 :STIMe <numeric_value>CALibration:ZERO:FSENsor:STIMe



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-8 CALibration:ZERO


5.11.2.6 :UPDateCALibration:ZERO:FSENsor:UPDate

Once the mathematical zero correction has been determined, apply the results to the on-linecalibration. This is not a queryable command and therefore has no *RST associated with it. 1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CALibration:ZERO 5-9

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-10 CALibration:ZERO

6 CONTrol SubsystemThe CONTrol subsystem is used to turn on and off electromechanical devices or controlsome dynamometer states that are used in a procedure.

KEYWORD PARAMETER FORM NOTES:CONTRol 1993 XSS01c :APOWer 1993 XSS01c [:STATe] <Boolean> 1993 XSS01c :BLOWer 1993 XSS01c [:STATe] <Boolean> 1993 :BRAKe 1999 [:STATe] <Boolean> 1999 XSS01c :COMPressor 1993 XSS01c [:STATe] <Boolean> 1993 :COVer 1999 [:ADJust] OPEN|CLOSe|SOPen|SCLOse [event; no query] 1999 :POSition? [query only] 1999 :EBENch 1999 [:CLEan] 1999 :INITiate [event; no query] 1999 :DURation <numeric_value> 1999 :IDLE 1999 :INITiate [event; no query] 1999 :LIFT 1999 [:ADJust] UP|DOWN [event; no query] 1999 :POSition? [query only] 1999 :MCONtrol 1999 [:STATe] <Boolean> 1999 :ROTation 1999 [:DIRection] FORWard|REVerse 1999 :VCDevice 1999 [:STATe] <Boolean> 1999 :TDIameter <numeric_value> 1999

6.1 :APOWer XSS01cCONTrol:APOWer

Controls the Auxiliary POWer. Auxiliary POWer are additional power outlets that can beused to power devices.

6.1.1 [:STATe] <Boolean> XSS01cCONTrol:APOWer[:STATe]

Turns the APOWer ON and OFF.

At *RST this value is set to OFF.XSS01c

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CONTrol Subsystem:APOWer 6-1

6.2 :BLOWer XSS01cCONTrol:BLOWer

Controls the BLOWer.

For example, in order to keep a uniform temperature inside the environment chamber, the airinside needs to be thoroughly mixed. This is usually accomplished using a blower.

6.2.1 [:STATe] <Boolean> XSS01cCONTrol:BLOWer[:STATe]

Turns the BLOWer ON and OFF.

At *RST this value is set to OFF.

6.3 :BRAKeCONTrol:BRAKe

This node contains the commands that control the brake.

6.3.1 [:STATe] <Boolean>:CONTrol:BRAKe[:STATe]

Sets or queries the state of the brake.


6.4 :COMPressor XSS01cCONTrol:COMPressor

Controls the COMPressor.

For example in an environmental chamber, a compressor is often needed additional controlof the heating and cooling.

6.4.1 [:STATe] <Boolean> XSS01cCONTrol:COMPressor[:STATe]

Turns the COMPressor ON and OFF.

At *RST this value is set to OFF.

6.5 :COVerCONTrol:COVer

This node contains the commands which control the cover.

6.5.1 [:ADJust] OPEN|CLOSe|SOPEn|SCLOseCONTrol:COVer[:ADJust]

This command controls the cover. This command is an event and has no associated *RSTcondition

OPEN - open covers

CLOSe - close covers

SCLose - step covers incrementally toward CLOSe

SOPen - step covers incrementally toward OPEN

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-2 CONTrol Subsystem:BLOWer

6.5.2 :POSition?CONTrol:COVer:POSition?

This command queries the position of the cover

OPEN - covers are fully open

CLOSe - covers are fully closed

MID - covers are partially open

6.6 :EBENchCONTrol:EBENch

This subsystem controls the state and activities of a gas analyzer emissions bench.

6.6.1 :CLEan:CONTrol:EBENch:CLEan

This subsystem controls the bench’s internal procedure to clean out its gas lines, commonlyknown as “purge” or “backflush”.

6.6.1.1 :INITiate:CONTrol:EBENch:CLEan:INITiate

Initiate the bench’s procedure to clean out its gas lines.

This command is an event and therefore has no *RST value.

6.6.1.2 :DURation <numeric_value>:CONTrol:EBENch:CLEan:DURation

This command sets or queries the duration in seconds of the “clean” procedure.


6.7 :IDLECONTrol:IDLE

This node contains commands that control the idle state of the device.

6.7.1 :INITiate:CONTrol:IDLE:INITiate

Returns the device to idle.

For chassis dynamometers, the dynamometer must decelerate to 0 m/s at the:SOURce:ACCeleration rate and wait for a command. The DYNO operation conditionregister Idle Procedure bit should be set indicating that :CONTrol:IDLE is executing. Note:The DYNO operation condition register will be further defined in Volume 4.


6.8 :LIFTCONTrol:LIFT

This node contains commands that control the lift.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CONTrol Subsystem:EBENch 6-3

6.8.1 [:ADJust] UP|DOWNCONTrol:LIFT[:ADJust]

This command controls the lift. This command is an event and has no associated *RSTcondition.

UP - raises lift

DOWN - lowers lift

6.8.2 :POSition?CONTrol:LIFT:POSition?

Queries the position of the lift.

UP - lifts are up.

DOWN - lifts are down.

MID - lifts are positioned between UP and DOWN.

6.9 :MCONtrolCONTrol:MCONtrol

Motor Control

Controls the motor.

6.9.1 [:STATe] <Boolean>:CONTrol:MCONtrol[:STATe]

Turns the power of motor ON or Off.


6.10 :ROTationCONTrol:ROTation

This node contains commands that control device rotation.

6.10.1 [:DIRection]CONTrol:ROTation[:DIRection]

For chassis dynamometers, configures the dynamometer rotation direction. Thedynamometer determines FORWard or REVerse based on configuration.

At *RST, this value is set to FORWard.

6.11 :VCDeviceCONTrol:VCDevice

Vehicle Centering Device

For chassis dynamometers, this node contains commands that control the Vehicle CenteringDevice.

6.11.1 [:STATe] <Boolean>CONTrol:VCDevice[:STATe]

When the state is ON, the dynamometer is performing the centering function. When the stateis OFF, centering is not being performed.


6-4 CONTrol Subsystem:MCONtrol


6.11.2 :TDIameter <numeric_value>CONTrol:VCDevice:TDIameter

Tire Diameter

Centering device uses tire diameter (m) as limit to center the vehicle on the dynamometer.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


CONTrol Subsystem:VCDevice 6-5


6-6 CONTrol Subsystem:VCDevice

7 DIAGnostic SubsystemThe purpose of the DIAGnostic subsystem is to provide a tree node for all of the instrumentservice and diagnostic routines used in routine maintenance and repair. The actualcommands in this subsystem are considered instrument-specific, and therefore are notincluded in this document. Instrument designers are free to add service and diagnosticcommands to meet the needs of individual instruments.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


DIAGnostic Subsystem 7-1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-2 DIAGnostic Subsystem

8 DISPlay SubsystemThe DISPlay subsystem controls the selection and presentation of textual, graphical, andTRACe information. This information includes measurement data, user-interaction displays,and data presented to the instrument by the controller. DISPlay is independent of, and doesnot modify, how data is returned to the controller.

Multiple DISPlay subsystems are used to represent independent display medium. A frontpanel mounted display and an attached terminal used only for information display areexamples of independent displays. Conversely, an instrument with many dedicatedindicators is considered to have one general display because of the dependencies in operationthat exist between the indicators.

Within a DISPlay, information may be separated into individual WINDows (this is alwaysthe case for instruments with dedicated indicators). Each window is considered to consist ofthree overlapped planes, one each for text, graphics, and trace data. Thus, text, graphics, andtrace information may be presented at the same time in a given window.

Most of the *RST conditions in the DISPlay subsystem are device-dependent, toaccommodate for typical display functions that exist for each of the various categories ofinstrumentation.

KEYWORD PARAMETER FORM NOTESDISPlay :ANNotation [:ALL] <Boolean> :AMPLitude <Boolean> :FREQuency <Boolean> :BRIGhtness <numeric_value> :CMAP :DEFault [event; no query] :COLor 1992 :HSL <hue>,<sat>,<lum> 1992 :RGB <red>,<green>,<blue> 1992 :CONTrast <numeric_value> :ENABle <Boolean> :MENU [:NAME] <menu_name> :STATe <Boolean> 1992 HP066

:KEY <string> [:WINDow] :BACKground :COLor <color number> :GEOMetry :LLEFt <numeric_value>,<numeric_value> :SIZe <numeric_value>,<numeric_value> :URIGht <numeric_value>,<numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


DISPlay 8-1

KEYWORD PARAMETER FORM NOTES :GRAPhics :CLEar [event; no query] :COLor <color number> :CSIZe <numeric_value> [:DRAW] <numeric_value>,<numeric_value> :PCL <block> :HPGL <block> :IDRaw <numeric_value>,<numeric_value> :IMOVe <numeric_value>,<numeric_value> :LABel <string> :LDIRection <numeric_value> :LTYPe <numeric_value>[,<numeric_value>] :MOVE <numeric_value>,<numeric_value> :STATe <Boolean> [:STATe] <Boolean> :TEXT :ATTRibutes <Boolean> :CLEar [event; no query] :COLor <numeric_value> :CSIZe <numeric_value> [:DATA] <string> | <block> :FEED <data_handle> 1991 TWIR01p15

:LOCate <row>[,<col>] :PAGE <numeric_value> 1991 HP005

:STATe <Boolean> :TRACe :COLor <numeric_value> :FEED <data_handle> 1991 TWIR01p15

:GRATicule :AXIS [:STATe] <Boolean> :COLor <numeric_value> :FRAMe [:STATe] <Boolean> :GRID :AUTO <Boolean> [:STATe] <Boolean> :PERSistence <numeric_value> :AUTO <Boolean>|ONCE [:STATe] <Boolean> :X :LABel <string> [:SCALe]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


8-2 DISPlay

KEYWORD PARAMETER FORM NOTES :AUTO <Boolean> | ONCE 1991 HP004

:CENTer <numeric_value> 1991 BalanHP006

:LEFT <numeric_value> :PDIVision <numeric_value> 1991 HP006

:LINK LEFT|CENTer|RIGHt 1991 HP006

:RIGHt <numeric_value> :SPACing LINear | LOGarithmic :Y :LABel <string> :RLINe <Boolean> 1991 HP006

[:SCALe] :AUTO <Boolean> | ONCE 1991 HP004

:BOTTom :PDIVision <numeric_value> 1991 HP006

:RLEVel <numeric_value> 1991 HP006

:AUTO <Boolean> 1991 HP006

:RPOSition <numeric_value> 1991 HP006

:TOP <numeric_value> :SPACing LINear | LOGarithmic :R :LABel <string> [:SCALe] :AUTO <Boolean> | ONCE 1991 HP004

:CPOint <numeric_value> :OEDGe <numeric_value> :SPACing LINear | LOGarithmic

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


DISPlay 8-3

8.1 :ANNotationDISPlay:ANNotation

This subsystem controls which annuciators are visible. ANNotation does not affect thevisibility of GRATicule. If SYSTem:SECurity is enabled, annotation cannot be switchedfrom OFF to ON.

The ANNotation parameters are set to ON at *RST, unless SYSTem:SECurity is enabled.

8.1.1 [:ALL] <Boolean>DISPlay:ANNotation:ALL

Controls ALL of the annotation information.

8.1.2 :AMPLitude <Boolean>DISPlay:ANNotation:AMPLitude

JP Change

Controls the amplitude annotation information.

8.1.3 :FREQuency <Boolean>DISPlay:ANNotation:FREQuency

Controls the frequency annotation information.

8.2 :BRIGhtness <numeric_value>DISPlay:BRIGhtness

Controls the intensity of the display. The range of the parameter is 0 to 1, where 1 is fullintensity and 0 is fully blanked.

8.3 :CMAPDISPlay:CMAP

The CMAP subsystem controls the physical color associated with logical color numbers inthe color map of the display. On a monochrome DISPlay, the CMAP may be used torepresent different intensity levels of the same shade. When a color is redefined, allinformation associated with that color number may change immediately.

Two methods are available for defining a particular color, HSL and RGB models. If both areimplemented in a device, then they shall be coupled such that redefining a color with onemodel shall be reflected in the values of the other model.

At *RST, COLor[1] shall represent “black,” and COLor2 shall represent “white” or theactual color of a monochrome display.

8.3.1 :DEFaultDISPlay:CMAP:DEFault

Sets the color map to the instrument’s default values for all colors, except that COLor[1]shall be represent “black,” and COLor2 shall represent “white” or the actual color of amonochrome display.

8.3.2 :COLorDISPlay:CMAP:COLor

This subsystem controls the color map for the instrument.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


8-4 DISPlay:ANNotation

8.3.2.1 :HSL <hue>,<sat>,<lum>DISPlay:CMAP:COLor:HSL

The HSL command sets the instrument’s color map based on the Hue/Saturation/Luminancelevels color model. A query of HSL shall return three <NR2>s separated by commas.

Hue ranges from zero to one, circularly, with a value of zero resulting in the same hue as avalue of one. The approximate color progression is (starting at zero): red, orange, yellow,green, cyan, blue, magenta, and back to red.

Saturation is the amount of pure color to be mixed with white. The saturation value rangesfrom zero to one, with zero specifying no color (only white or gray, depending on intensity)and one specifying no white.

Luminance specifies the brightness per unit area of the color. A luminance of zero results inblack; a luminance of one results in the brightest color available.

At *RST, these parameters are set to the DEFault values, equivalent to executing DEFaultcommand. The HSL command is coupled to the RGB command. Changing values in eitherwill affect the values of the other.

8.3.2.2 :RGB <red>,<green>,<blue>DISPlay:CMAP:COLor:RGB

The RGB command sets the instrument’s color map based on the Red/Green/Blue colormodel. A query of RGB shall return three <NR2>s separated by commas.

Red ranges from zero to one, with zero indicating “no red” and one indicating “full intensityred.”

Green ranges from zero to one, with zero indicating “no green” and one indicating “fullintensity green.”

Blue ranges from zero to one, with zero indicating “no blue” and one indicating “fullintensity blue.”

At *RST, these parameters are set to the DEFault values, equivalent to executing DEFaultcommand. The RGB command is coupled to the HSL command. Changing values in eitherwill affect the values of the other.

8.4 :CONTrast <numeric_value>DISPlay:CONTrast

Determines the relative difference in brightness between “full” intensity and “no” intensityas displayed. The parameter ranges in value from 0 to 1; 0 indicates no difference betweendata and background, and 1 indicates maximum contrast.

8.5 :ENABle <Boolean>DISPlay:ENABle

Controls whether the whole display is visible. If SYSTem:SECurity is enabled, DISPlaycannot be switched from OFF to ON.

ENABle is set to ON at *RST, unless SYSTem:SECurity is enabled.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


DISPlay:CONTrast 8-5

8.6 :MENUDISPlay:MENU

Allows selection of predefined device-dependent menus for display. A menu is basically asoftkey help screen, and it may consist of only key labels or more extensive information.

8.6.1 [:NAME] <menu_name>DISPlay:MENU:NAME

The NAME command selects a menu by name from an instrument-predefined list of validmenu names.

8.6.2 :STATe <Boolean>DISPlay:MENU:STATe

HP066

Turns the current menu page ON or OFF.

8.6.3 :KEY <string>DISPlay:MENU:KEY

Assigns the soft key label <string> to key. This affects only the displayed key label; it doesnot change the key definition.

8.7 [:WINDow]DISPlay:WINDow

The WINDow subtree contains commands to enable a window, to set its size and location,and control its contents. Multiple instances of WINDow may exist under a particularDISPlay.

8.7.1 :BACKgroundDISPlay:WINDow:BACKground

This subsystem controls the characteristics of the window background.

8.7.1.1 :COLor <numeric_value>DISPlay:WINDow:BACKground:COLor

Selects from the CMAP the value given by <numeric_value> to become the backgroundcolor.

8.7.2 :GEOMetryDISPlay:WINDow:GEOMetry

This subtree is used to define the position and size of the WINDow with respect to thedisplay. A window may be specified by using any two of LLEFt, URIGht or SIZEcommands, since SIZe = URIGht - LLEFt. If any one of these commands is implemented,then all three shall be implemented and the coupling between them shall be maintained.

For the GEOMetry subtree, the lower left corner of the whole display is defined to be (0,0);zero in the horizontal direction and zero in the vertical direction. The upper right corner isdefined to be (1,1).

The effect of changing the size or aspect ratio of a WINDow that already is displayinginformation is device-dependent. The device may choose to rescale the information to fit thenew WINDow or it may leave the information unchanged, clipping it where it exceeds theWINDow boundaries.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


8-6 DISPlay:MENU

8.7.2.1 :LLEFt <numeric_value>,<numeric_value>DISPlay:WINDow:GEOMetry:LLEFt

This specifies (or queries) the location of the lower left corner of the window in the range 0to 1.

8.7.2.2 :SIZE <numeric_value>,<numeric_value>DISPlay:WINDow:GEOMetry:SIZE

This specifies (or queries) the size of the display window. The first parameter represents thelength in the horizontal direction, and the second parameter represents the length in thevertical direction.

The parameters may be set in the range greater than zero to 1. Where the existence of awindow can be represented by an icon, the device shall accept SIZE 0,0 to indicate thewindow is to be replaced by an icon.

If a window is represented by an icon, any valid SIZE command with non-zero parametersshall reset the size of the window, and shall cause the icon to be replaced by the window.

8.7.2.3 :URIGht <numeric_value>,<numeric_value>DISPlay:WINDow:GEOMetry:URIGht

This specifies (or queries) the location of the upper right corner of the display window in therange 0 to 1.

8.7.3 :GRAPhicsDISPlay:WINDow:GRAPhics

The GRAPhics subtree allows for the display of graphical information in the WINDow. Forexample, it allows direct control of the WINDow by the controller, using it as a plotteroutput device.

For the GRAPhics subtree, the lower left corner of the WINDow is defined to be (0,0); zeroin the horizontal direction and zero in the vertical direction. The upper right corner is definedto be (1,1).

8.7.3.1 :CLEarDISPlay:WINDow:GRAPhics:CLEar

Erases the graphics from the WINDow.

This command defines an event and therefore has no query form or *RST value.

8.7.3.2 :COLor <numeric_value>DISPlay:WINDow:GRAPhics:COLor

Selects from the CMAP the value given by <numeric_value> to become the color for thenext GRAPhics operation. It is similar in function to selecting a pen on a plotter.

8.7.3.3 :CSIZe <numeric_value>[,<numeric_value>]DISPlay:WINDow:GRAPhics:CSIZe

Sets the size and optional aspect ratio (width/height) of the character cell used by the LABelcommand. The actual physical size of the resulting character is device-dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


DISPlay[:WINDow] 8-7

8.7.3.4 [:DRAW] <numeric_value>,<numeric_value>DISPlay:WINDow:GRAPhics:DRAW

Draws a line from the current “pen” position to the specified X and Y coordinate (the firstparameter is X, the second is Y; both parameters are required). The current line type and pennumber are used.

8.7.3.5 :PCL <block>DISPlay:WINDow:GRAPhics:PCL

Graphics and text data are sent to the instrument using Hewlett-Packard “<esc>*” terminal-and printer-style escape sequences. These are described in the Hewlett-Packard “PrinterCommand Language” document. Some escape sequences may interact with globalparameters such as color selection. The effect of these changes is global in scope and notrestricted to the :GRAPhics subsystem.

8.7.3.6 :HPGL <block>DISPlay:WINDow:GRAPhics:HPGL

Graphics and text data are sent to the instrument using HP-GL (Hewlett-Packard-GraphicsLanguage) plotter language. Some HP-GL sequences will interact with global parameterssuch as color selection; the effect of these changes is global in scope and not restricted to the:GRAPhics subsystem.

8.7.3.7 :IDRaw <numeric_value>,<numeric_value>DISPlay:WINDow:GRAPhics:IDRaw

Draws a line from the current pen position to a new position determined by adding an Xoffset (first parameter) and a Y offset (second parameter) to the current coordinates.

8.7.3.8 :IMOVe <numeric_value>,<numeric_value>DISPlay:WINDow:GRAPhics:IMOVe

Updates the current pen position by adding an X offset (first parameter) and a Y offset(second parameter) to the current coordinates. No line is drawn.

8.7.3.9 :LABel <string>DISPlay:WINDow:GRAPhics:LABel

Places text on the graphics display at the current pen position, using the current pen, with thelabel direction set by LDIR.

8.7.3.10 :LDIRection <numeric_value>DISPlay:WINDow:GRAPhics:LDIRection

Defines the angle (in radians) at which labels are drawn. An angle of 0 is normal horizontalprinting. The angle increases counter-clockwise; PI/2 is bottom-to-top.

8.7.3.11 :LTYPe <numeric_value>[,<numeric_value>]DISPlay:WINDow:GRAPhics:LTYPe

Selects a line type and optional repeat length for all subsequent lines drawn by IDRaw orDRAW. Although the specific line types are device-dependent, line type 1 is by tradition a“plain” line (solid), while other types include dots and dashes or combinations of dots anddashes.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


8-8 DISPlay[:WINDow]

8.7.3.12 :MOVE <numeric_value>,<numeric_value>DISPlay:WINDow:GRAPhics:MOVE

Updates the pen position without drawing a new line.

8.7.3.13 :STATe <Boolean>DISPlay:WINDow:GRAPhics:STATe

Controls whether the GRAPhics is visible or not.

8.7.4 [:STATe] <Boolean>DISPlay:WINDow:STATe

Controls whether the WINDow is visible or not. The command DISPlay <Boolean> refers tothis node. If SYSTem:SECurity is enabled, WINDow cannot be switched from OFF to ON.

At *RST, DISPlay[:WINDow][:STATe] is set to ON, unless SYSTem:SECurity is enabled.

8.7.5 :TEXTDISPlay:WINDow:TEXT

The TEXT subtree allows for the display of textual information in the WINDow. Forexample, it allows direct control of the WINDow by the controller, using it as a VDT (VisualDisplay Terminal) output device.

For the TEXT subtree, the upper left corner of the WINDow is defined to be (1,1). The lowerright corner is dependent on the WINDow:SIZE and the TEXT:Character SIZE selected.

8.7.5.1 :ATTRibutes <Boolean>DISPlay:WINDow:TEXT:ATTRibutes

ATTRibutes allows the device to interpret the ANSI Standard Terminal escape sequenceswhen displaying TEXT:DATA. Escape sequences that generate an inquiry are not permitted.The device may absorb escape sequences that it cannot interpret to prevent them fromappearing on the display.

If ATTRibutes is ON, escape sequences embedded in the data are used to control theattributes of the string, such as blinking, or underline. ATTRibutes set to OFF disables theinterpretation of display sequences, but does not affect the current display. A blinkingdisplay keeps on blinking until it is overwritten. The device may absorb the escapesequences to prevent them from appearing on the display.

8.7.5.2 :CLEarDISPlay:WINDow:TEXT:CLEar

Erases the text from the WINDow.

This command defines an event, and therefore has no query form or *RST value.

8.7.5.3 :COLor <numeric_value>DISPlay:WINDow:TEXT:COLor

Selects from the CMAP the value given by <numeric_value> to become the color for thenext DATA stream.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.5.4 :CSIZe <numeric_value>[,<numeric_value>]DISPlay:WINDow:TEXT:CSIZe

Sets the size and optional aspect ratio (width/height) of the character cell used by DATA.Actual physical size of the resulting character is device-dependent.

8.7.5.5 :FEED <data_handle>DISPlay:WINDow:TEXT:FEED

TWIR01p15

Sets or queries what data flow is fed into the TEXT display window.

At *RST, the <data_handle > is set to a device-dependent value.

8.7.5.6 [:DATA] <string> | <block>DISPlay:WINDow:TEXT:DATA

The data that gets written to the text display area. Note that writing to the display overwritesany data that may have already been written. The result of overwriting a string with a shorterstring is not defined; the excess characters may or may not be cleared.

8.7.5.7 :LOCate <numeric_value>[,<numeric_value>DISPlay:WINDow:TEXT:LOCate

This command selects the display ROW and display COLumn where the next LINE ofTEXT DATA is to appear. Row number 1 is the top row of the instrument display; columnnumber 1 is the left-most column.

8.7.5.8 :PAGE <numeric_value>DISPlay:WINDow:TEXT:PAGE

HP005

The PAGE command sets the page to be displayed. This command may accept UP andDOWN as defined in <numeric_value>.

8.7.5.9 :STATe <Boolean>DISPlay:WINDow:TEXT:STATe

Controls whether the TEXT is visible or not.

8.7.6 :TRACeDISPlay:WINDow:TRACe

The TRACe subtree allows for the display of trace data in the WINDow; for example,directly from measurement data or from MEMory. The format of the data (and associatedinformation) is used by the TRACe subsystem to define how commands are to be interpretedand whether on not they are valid.

8.7.6.1 :COLor <numeric_value>DISPlay:WINDow:TRACe:COLor

Selects from the CMAP the value given by <numeric_value> to become the color for theTRACe.

8.7.6.2 :FEED <data_handle>DISPlay:WINDow:TRACe:FEED

TWIR01p15

Sets or queries what data flow is fed into the TRACe display window.

At *RST, the <data_handle> is set to a device-dependent value.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.6.3 :GRATiculeDISPlay:WINDow:TRACe:GRATicule

The GRATicule subtree is used to set the type of graticule displayed in relation to theTRACe.

8.7.6.3.1 :AXISDISPlay:WINDow:TRACe:GRATicule:AXIS

The axes are either X and Y AXIS with markings (divisions), or the R AXIS with markings(divisions) with respect to the TRACe.

8.7.6.3.1.1 [:STATe] <Boolean>DISPlay:WINDow:TRACe:GRATicule:AXIS:STATe

Determines if the AXIS is visible or not.

8.7.6.3.2 :FRAMeDISPlay:WINDow:TRACe:GRATicule:FRAMe

The FRAMe is the perimeter boundary and markings with respect to the TRACe.

8.7.6.3.2.1 [:STATe] <Boolean>DISPlay:WINDow:TRACe:GRATicule:FRAMe:STATe

Determines if the FRAMe is visible or not.

8.7.6.3.3 :GRIDDISPlay:WINDow:TRACe:GRATicule:GRID

The GRID provides constant lines of X, Y or R with respect to the TRACe.

8.7.6.3.3.1 :AUTO <Boolean>DISPlay:WINDow:TRACe:GRATicule:GRID:AUTO

AUTO couples the subtree of GRID to FRAMe. Turning ON FRAMe, with AUTO set toON, shall cause GRID to turn on also.

8.7.6.3.3.2 [:STATe] <Boolean>DISPlay:WINDow:TRACe:GRATicule:GRID:STATe

Determines if the GRID is visible or not.

8.7.6.4 :PERSistence <numeric_value>DISPlay:WINDow:TRACe:PERSistence

Sets how long trace data written to the screen will remain visible. The parameter is inseconds.

8.7.6.4.1 :AUTO <Boolean>|ONCEDISPlay:WINDow:TRACe:PERSistence:AUTO

HP065

When AUTO is set to ON, the persistence is determined by the device.

At *RST, this value is set to ON.

8.7.6.5 :STATe <Boolean>DISPlay:WINDow:TRACe:STATe

Controls whether the TRACe and related information is visible or not.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.6.6 :XDISPlay:WINDow:TRACe:X

This subsystem controls the setting of the X axis. The X axis is displayed horizontally, and itis usually the independent variable of the data, such as time or frequency. The :X node isused to define the parameters associated with the X axis. It is only available when the formatof the data is Cartesian.

8.7.6.6.1 :LABel <string>DISPlay:WINDow:TRACe:X:LABel

Specifies custom axis labeling.

8.7.6.6.2 [:SCALe]DISPlay:WINDow:TRACe:X:SCALe

HP006

The SCALe subtree is used to define which portion of the (TRACe) data is to be displayed,by defining the end points of the axis as they appear in the WINDow. The values are in thesame UNITs as the UNIT of data for the x axis. The x scale can be defined in terms ofCENTer, LEFT, RIGHt and/or PDIVision, where the following equations express therelationship of these parameters:

RIGHt - LEFT = (RIGHt - CENTer) * 2 = PDIVision * # of graticule divisions.

If an instrument implements x axis scaling, the commands RIGHt and LEFT must beimplemented, while implementing PDIVision and CENTer are optional.

8.7.6.6.2.1 :AUTO <Boolean> | ONCEDISPlay:WINDow:TRACe:X:SCALe:AUTO

HP004

The AUTO ON command sets the display to always configure the scaling on the particularaxis to best display the data. This rescaling may affect the values of any of the parametersunder the SCALe node. When AUTO is ON the display may be rescaled after eachmeasurement or sweep. Setting AUTO to ONCE, turns auto ON, adjusting the scaling of theaxis for one measurement and then turns auto OFF. Turning AUTO ON can change any ofthe parameters which can be set under the SCALe node.

At *RST AUTO is set to OFF.

8.7.6.6.2.2 :CENTer <numeric_value>DISPlay:WINDow:TRACe:X:SCALe:CENTer

HP006

Set or queries the value represented by the center point of the x-axis. This value may bebounded by the range of the data. When a new CENTer value is entered, the PDIVisionvalue is kept constant and the RIGHT and LEFT values are changed.

At *RST, this parameter value is device dependent.

8.7.6.6.2.3 :LEFT <numeric_value>DISPlay:WINDow:TRACe:X:SCALe:LEFT

HP006

Set or queries the value represented by the minimum (left) edge of the x-axis. This valuemay be bounded by the range of the data. When a new LEFT value is entered, the PDIVisionvalue is kept constant and the CENTer and RIGHT values are changed.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.6.6.2.4 :PDIVision <numeric_value>DISPlay:WINDow:TRACe:X:SCALe:PDIVision

HP006

Set or query the value between two grid graticules (value “per division”). When a newPDIVision value is entered, the parameter set as the PDIVision:LINK is held constant andthe other two are changed.


8.7.6.6.2.4.1 :LINK LEFT | CENTer | RIGHtDISPlay:WINDow:TRACe:X:SCALe:PDIVision:LINK

HP006

LINK selects the parameter, either CENTer, LEFT or RIGHt that shall not be changed whenthe PDIVision value is changed. For example, if LINK is set to LEFT, then changingPDIVision shall cause CENTer and RIGHt, not LEFT, to change.

At *RST the value of LINK is device dependent.

8.7.6.6.2.5 :RIGHt <numeric_value>DISPlay:WINDow:TRACe:X:SCALe:RIGHt

HP006

Set or queries the value represented by the maximum (right) edge of the x-axis. This valuemay be bounded by the range of the data. When a new RIGHt value is entered, thePDIVision value is kept constant and the CENTer and LEFT values are changed.


8.7.6.7 :YDISPlay:WINDow:TRACe:Y

This subsystem controls the setting of the Y axis. The :Y node is displayed vertically, and itis usually the dependent variable of the data, such as power or voltage. The :Y node is usedto define the parameters associated with the Y axis. It is only available when the format ofthe data is Cartesian.

8.7.6.7.1 :LABel <string>DISPlay:WINDow:TRACe:Y:LABel


8.7.6.7.2 :RLINe <Boolean>DISPlay:WINDow:TRACe:Y:RLINe

HP006

Turn on/off a line which is positioned on the graticule at the current Reference POSition.

At *RST RLINe is off.

8.7.6.7.3 [:SCALe]DISPlay:WINDow:TRACe:Y:SCALe

HP006

The SCALe subtree is used to define which portion of the (TRACe) data is to be displayed,by defining the end points of the axis as they appear in the WINDow. The values are in thesame UNITs as the UNIT of data for the y axis. The y scale can be defined in terms of TOP,

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



BOTTom, PDIVision or Reference LEVel and Reference POSition. These values arecoupled together in the following manner:

TOP - BOTTom = PDIVision * # of graticule divisionsTOP = Reference LEVel when Reference POSition is 100 %BOTTom = Reference LEVel when Reference POSition is 0 %

If an instrument implements y axis scaling, the commands TOP and BOTTom must beimplemented, while implementing the RLEVel and RPOSition and PDIVision commandsare optional.

8.7.6.7.3.1 :AUTO <Boolean> | ONCEDISPlay:WINDow:TRACe:Y:SCALe:AUTO

HP004



8.7.6.7.3.2 :BOTTom <numeric_value>DISPlay:WINDow:TRACe:Y:SCALe:BOTTom

Sets or queries the value represented by the minimum (bottom) edge of the display. Thevalue may be bounded by the range of the data.

8.7.6.7.3.3 :PDIVision <numeric_value>DISPlay:WINDow:TRACe:Y:SCALe:PDIVision

HP006

Set or query the value between two grid graticules (value “per division”). When a newPDIVision value is entered, the current Reference LEVel is kept the same, while adjustingthe top and bottom scaling for the new PDIVision value.


8.7.6.7.3.4 :RLEVel <numeric_value>DISPlay:WINDow:TRACe:Y:SCALe:RLEVel

HP006

Set or query the value represented at the designated Reference POSition on the y-axis.Setting a new Reference LEVel does not affect the value of PDIVision.


8.7.6.7.3.4.1 :AUTO <Boolean>DISPlay:WINDow:TRACe:Y:SCALe:RLEVel:AUTO

HP006

Setting RLEVel:AUTO to ON causes the display to automatically choose a reference level tobest display the particular data. When AUTO is ON, a new reference level may be selectedeach time new data is received.

At *RST AUTO is off.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.6.7.3.5 :RPOSition <numeric_value>DISPlay:WINDow:TRACe:Y:SCALe:RPOSition

HP006

Set or query the point on the y-axis to be used as the reference position as a percentage of thelength of the y- axis. The top of the y axis is defined to have a Reference POSition of 100%,while the bottom of the y axis is defined to have a Reference POSition of 0%. The ReferencePOSition is the point on the y-axis which should equal the Reference LEVel.


8.7.6.7.3.6 :TOP <numeric_value>DISPlay:WINDow:TRACe:Y:SCALe:TOP

Sets or queries the value represented by the top edge of the display. The value may bebounded by the range of the data.

8.7.6.7.4 :SPACing LOGarithmic | LINearDISPlay:WINDow:TRACe:Y:SPACing

The SPACing command is used to set the scale to either linear or log.

8.7.6.8 :RDISPlay:WINDow:TRACe:R

This subsystem controls the R axis. The :R axis is displayed radially from the center pointand usually represents magnitude of complex data. It is only available when the format of thedata is in polar coordinates.

8.7.6.8.1 :LABel <string>DISPlay:WINDow:TRACe:R:LABel


8.7.6.8.2 [:SCALe]DISPlay:WINDow:TRACe:R:SCALe

The SCALe subtree is used to define which portion of the (TRACe) data is to be displayedby defining the end points of the axis as they appear in the WINDow. The values are in thesame UNITs as the UNIT of the data for that AXIS.

8.7.6.8.2.1 :AUTO <Boolean> | ONCEDISPlay:WINDow:TRACe:R:SCALe:AUTO

HP004



8.7.6.8.2.2 :CPOint <numeric_value>DISPlay:WINDow:TRACe:R:SCALe:CPOint

Sets or queries the value represented by the minimum (Center POint) of the circular display.The value may be bounded by the range of the data.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.7.6.8.2.3 :OEDGe <numeric_value>DISPlay:WINDow:TRACe:R:SCALe:OEDGe

Sets or queries the value represented by the Outside EDGe of the circular display. The valuemay be bounded by the range of the data.

8.7.6.8.3 :SPACing LOGarithmic | LINearDISPlay:WINDow:TRACe:R:SPACing

The SPACing command is used to set the scale to either linear or log.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



9 FORMat SubsystemThe FORMat subsystem sets a data format for transferring numeric and array information.This data format is used for both command and response data by those commands that arespecifically designated to be affected by the FORMat subsystem. The designation is eithergiven as part of a command description, or in the definition of block or array data used by acommand. The data format for command data may override the definition of FORMat if thedata received is self typing (indicates its type), for the duration of that data transfer.

KEYWORD PARAMETER FORM NOTESFORMat :BORDer NORMal|SWAPped [:DATA] <type> [,<length>] :DINTerchange <Boolean> :SREGister ASCii | BINary | HEXadecimal | OCTal 1992 PH066

9.1 :BORDer NORMal|SWAPpedFORMat:READings:BORDer

Byte ORDer. Controls whether binary data is transferred in normal or swapped byte order.

At *RST, this value is set to NORMal.

9.2 [:DATA] <type>[,<length>]FORMat:READings:DATA

TK055The DATA command selects the data format; the <type> and type <length>. Valid types areASCii, INTeger, UINTeger, REAL, HEXadecimal, OCTal, BINary, and PACKed. The<length> parameter is optional for all types; its meaning is dependent on the type selected.

TK033The <length> parameter is an <NRf>. In the query response <length> is returned as <NR1>.

TK055If the type INTeger, UINTeger, REAL, or PACKed is selected the data is transferred in ablock. The types ASCii, HEXadecimal, OCTal, and BINary are self typing. That is, thesyntax designates the type. In these cases, the FORMat subsystem is only necessary todetermine the output format.

At *RST, ASCii is selected as the default type, the type length is device-dependent.

The various types are defined as:

<type> Interpretation:

ASCii Numeric data is transferred as ASCii bytes in <NR1>, <NR2> or <NR3>format, as appropriate. The numbers are separated by commas as specifiedin IEEE 488.2. Forgiving listening allows ASCii input to always be valid.The optional <length> parameter specifies the number of significant digits tobe returned.

TK033A <length> value of zero indicates that the device selects the number ofsignificant digits to be returned. When a <length> of zero has been

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


FORMat:BORDer 9-1

specified, the FORMat[:DATA]? query shall return zero as its secondparameter.

BINary Data is encoded as a non-decimal numeric, base 2, preceded by “#B” asspecified in IEEE 488.2. The <length> parameter is the number of binarydigits in each number (not including the “#B”).

HEXadecimal Data is encoded as a non-decimal numeric, base 16, preceded by “#H” asspecified in IEEE 488.2. The <length> parameter is the number ofhexadecimal digits in each number (not including the “#H”).

INTeger Data is transferred in a definite length block as signed integers of the lengthspecified (in bits; default is 16). Scaling and offset, if required forinterpretation of measurement data, are determined by measurementparameters set in some other subsystem. Valid values of <length> forINTeger data are 8, 16 and 32.

OCTal Data is encoded as a non-decimal numeric, base 8, preceded by “#Q” asspecified in IEEE 488.2. The <length> parameter is the number of octaldigits in each number (not including the “#Q”).

PACKed Data is transferred in a definite length block, in a manner specified in thedevice documentation. The <length> parameter may be used to conveyadditional information about the device-dependent format.

REAL Data is transferred in a definite length block as IEEE 754 floating pointnumbers of the specified length (in bits; default is 64). Valid values of<length> for REAL data are 32 and 64.

TK055UINTeger Data is transferred in a definite length block as unsigned integers of thelength specified (in bits; default is 16). Scaling and offset, if required forinterpretation of measurement data, are determined by measurementparameters set in some other subsystem. Valid values of <length> forUINTeger data are 8, 16, 32 and 64.

9.3 :DINTerchange <Boolean>FORMat:READings:DINTerchange DIF01Determines whether measurement data is formatted as a <dif_expression>. See DataInterchange Format, Volume 3. When DINTerchange ON is selected, returned data isencapsulated in this structure.

TK032aThe commands which are affected by this switch are a device dependent subset of thoseaffected by the FORMat:DATA command, but at a minimum shall include SENSe:DATA?,CALCulate:DATA?, TRACe:DATA?, MEASure?, READ?, and FETCh?

TK032aThe DIF encoding format for its DATA(CURVe(VALues)) block follows that specified inFORMat[:DATA] and FORMat:BORDer.

At *RST this function is set to OFF.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


9-2 FORMat:DINTerchange

9.4 :SREGister ASCii | BINary | HEXadecimal | OCTalFORMat:SREGister

PH066

This command selects the data type of the response to queries for any CONDition, EVENtand ENABle register and for PTRansition and NTRansition filters that belong to the statussubsystem. Note that this includes the IEEE 488.2 status register queries.

ASCii The data is transferred as ASCii bytes in <NR1> format. This argument isrequired if the command is implemented.

BINary The data is encoded as non-decimal numeric, base 2, preceded by ‘#B’ asspecified in IEEE 488.2

HEXadecimal The data is encoded as non-decimal numeric, base 16, preceded by ‘#H’ asspecified in IEEE 488.2

OCTal The data is encoded as non-decimal numeric, base 8, preceded by ‘#Q’ asspecified in IEEE 488.2

At *RST, ASCii is selected as the default response data type.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


FORMat:SREGister 9-3

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


9-4 FORMat:SREGister

10 HCOPy HP063eThe Hard COPy subsystem controls the setup of plotting and printing to an external device.The Hard COPy subsystem does not perform any data formatting, that is it does not convertthe data from one representation to another, such as COMPlex to POLar. Instead HCOPyadds the necessary page formatting (dependent upon the hard copy device language) to turnthe data into an acceptable form for the hard copy device.

The HCOPy subsystem may FEED data from SENSe or CALCulate, and this data may beprinted or plotted. A FEED may be established from a DISPlay:WINDow. In this case theHCOPy output shall reflect what is currently displayed in that WINDow. In particular, anyscaling and offset that applies shall be employed.

The selection of the interface and any address information is accomplished in theSYSTem:COMMunicate subsystem. DATA may be streamed to an external device withoutsending it through the HCOPy subsystem, where no page formatting commands are needed.

The HCOPy subsystem gives a user several ways to select and initiate a plot or print. A usermay request all aspects of the data be plotted or printed, or the user may select a subset thatis of interest.

The ITEM subsystem provides the means to select the desired aspects of the data in one oftwo ways. First, the ITEM of interest can be directly plotted or printed. For example, theTRACe data can be plotted or printed immediately by using theHCOPy:ITEM:...:IMMediate command or the HCOPy:ITEM:...:DATA? query.Alternatively, the user may set the STATe to ON for all the ITEMs of interest, and then usethe HCOPy:IMMediate command or the HCOPy:DATA? query to plot or print the selecteditems in one transaction with the hard copy device.

If the user wishes to plot or print all the data, pointed to by the FEED, and does not want toindividually initiate each ITEM or change each ITEM’s STATe to ON, the user can send theHCOPy:ITEM:ALL[:IMMediate] command or the HCOPy:ITEM:ALL:DATA? query.

The :HCOPy:SDUMp:IMMediate command and the :HCOPy:SDUMp:DATA? query allowthe user to do a Screen DUMp of the whole DISPlay, mimicking the traditional role of acamera recorder, and provide a simple hard copy scheme for instruments with a DISPlay.

The HCOPy subsystem provides two schemes, IMMediate and DATA?, for getting hardcopy data out of an instrument. First, all of the IMMediate events can be implemented andused where the instrument is capable of directly controlling the interface. For example,RS-232, Centronics, or GPIB where the instrument can talk directly to the hard copy deviceby becoming the active controller. Any instrument which requires control of the systeminterface to execute the IMMediate command shall also implement the *PCB commoncommand, see IEEE 488.2 10.21.

IMMediate can also be used on GPIB when the active controller addresses the instrument totalk and the hard copy device to listen while monitoring the data flow by shadowhandshaking. The format of the data sent in response to an IMMediate command is notnecessarily an IEEE 488.2 format. This behavior is allowed by IEEE 488.2 section 8.1.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy 10-1

WARNING:The IEEE 488.2 message exchange protocol requirements are violated when theIMMediate command generates a response that is sent when the instrument is addressedto talk. The instrument shall revert to the normal message exchange protocol if itreceives a device clear or any data on the system interface. Designers should use thecontrol passing method rather than shadow handshaking method to avoid this escape ofthe IEEE 488.2 message exchange protocol.

Second, the DATA? query exists for use on buses, such as GPIB, where the data flow fromthe instrument to the hard copy device by way of a separate controller is acceptable ornecessary. It is also useful when the controller wants to store formatted data for later use.The instrument returns the formatted data in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element, see IEEE 488.2 section 8.7.10. This response data elementhas a leading #0 and a trailing NL^END. The controller could strip the header and trailer andsend the remainder to an appropriate printer or plotter. The indefinite form is used becausethe block’s size or nature may prevent the instrument from computing the block’s lengthuntil after it is sent.

A device may implement IMMediate or DATA? or both of these forms to plot or printresults.

The result from HCOPy can also be fed to the Mass MEMory subsystem. The user couldthen retreive the results from the stored files at a more convenient time.

KEYWORD PARAMETER FORM NOTESHCOPy 1993 :ABORt [event;no query] 1993 :DATA? 1993 :DESTination <data_handle> [event;no query] 1993 :DEVice 1993 :CMAP 1993 :COLor 1993 :HSL <hue>,<sat>,<lum> 1993 :RGB <red>,<green>,<blue> 1993 :DEFault [event;no query] 1993 :COLor <Boolean> 1993 :LANGuage PCL[<n>] | HPGL[<n>] | POSTscript[<n>] 1993 :MODE TABLe | GRAPh 1993 :RESolution <numeric_value> 1993 :UNIT <SUFFIX PROGRAM DATA> 1993 :SPEed <numeric_value> 1993 :UNIT <SUFFIX PROGRAM DATA> 1993 :FEED <data_handle> 1993 [:IMMediate] 1993 :ITEM 1993

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-2 HCOPy

KEYWORD PARAMETER FORM NOTES :ALL 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :ANNotation 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :CUT 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :FFEed 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :LABel 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :TEXT <string> 1993 :MENU 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :TDSTamp 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 [:WINDow] 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :TEXT 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 :TRACe 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy 10-3

KEYWORD PARAMETER FORM NOTES :GRATicule 1993 :COLor <numeric_value> 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993 :STATe <Boolean> 1993 [:IMMediate] [event;no query] 1993 :LTYPe SOLid | DOTTed | DASHed | STYLe<n> 1993 :STATe <Boolean> 1993 :PAGE 1993 :DIMensions 1993 :AUTO <Boolean> 1993 :LLEFt <numeric_value>,<numeric_value> 1993 :QUADrant<n> [event;no query] 1993 :URIGht <numeric_value>,<numeric_value> 1993 :LENGth <numeric_value> 1993 :ORIentation LANDscape | PORTrait 1993 :SCALe <numeric_value> 1993 :SIZE CUSTom |A | B | C | D | E 1993

| A0 | A1 | A2 | A3 | A4 1993| B0 | B1 | B2 | B3 | B4 | B5 1993

:UNIT <SUFFIX PROGRAM DATA> 1993 :WIDTH <numeric_value> 1993 :SDUMp 1993 :DATA? [query only] 1993 [:IMMediate] [event;no query] 1993

10.1 :ABORtHard COPy:ABORt

Abort the current hard copy operation. A new program message automatically aborts anyincomplete response from an :HCOPy:...:DATA? query as that is an INTERRUPTEDcondition.

10.2 :DATA?Hard COPy:DATA?

This query initiates the plot or print according to the current Hard COPy setup parameters.All of the items under the ITEM node which are turned ON (STATe ON) are encapsulated inan <INDEFINITE LENGTH ARBITRARY RESPONSE DATA> element.

10.3 :DESTination<data_handle>Hard COPy:DESTination

An event which sets all :FEED connections which had been set to “HCOPy” to “”. The:FEED connection pointed to by <data handle> is set to “HCOPy”. Any <data_handle>which can be used as a parameter to :DESTination shall have a :FEED command under itwhich can be set to “HCOPy”.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-4 HCOPy:ABORt

10.4 :DEViceHard COPy:DEVice

This subsystem is used to set and query characteristics relating to the hard copy device andits output.

10.4.1 :CMAPHard COPy:DEVice:CMAP

The CMAP subsystem controls the physical color associated with logical color numbers inthe color map of the display. On a monochrome DISPlay, the CMAP may be used torepresent different intensity levels of the same shade. When a color is redefined, allinformation associated with that color number may change immediately.

Two methods are available for defining a particular color, HSL and RGB models. If both areimplemented in a device, then they shall be coupled such that redefining a color with onemodel shall be reflected in the values of the other model.

At *RST, COLor[1] shall represent “black,” and COLor2 shall represent “white” or theactual color of a monochrome display.

10.4.1.1 :COLorHard COPy:DEVice:CMAP:COLor

This subsystem controls the color map for the instrument.

10.4.1.1.1 :HSL <hue>,<sat>,<lum>Hard COPy:DEVice:CMAP:COLor:HSL

The HSL command sets the instrument’s color map based on the Hue/Saturation/Luminancelevels color model. A query of HSL shall return three <NR2>s separated by commas.

Hue ranges from zero to one, circularly, with a value of zero resulting in the same hue as avalue of one. The approximate color progression is (starting at zero): red, orange, yellow,green, cyan, blue, magenta, and back to red.

Saturation is the amount of pure color to be mixed with white. The saturation value rangesfrom zero to one, with zero specifying no color (only white or gray, depending on intensity)and one specifying no white.

Luminance specifies the brightness per unit area of the color. A luminance of zero results inblack; a luminance of one results in the brightest color available.

At *RST, these parameters are set to the DEFault values, equivalent to executing DEFaultcommand. The HSL command is coupled to the RGB command. Changing values in eitherwill affect the values of the other.

10.4.1.1.2 :RGB <red>,<green>,<blue>Hard COPy:DEVice:CMAP:COLor:RGB

The RGB command sets the instrument’s color map based on the Red/Green/Blue colormodel. A query of RGB shall return three <NR2>s separated by commas.

Red ranges from zero to one, with zero indicating “no red” and one indicating “full intensityred.”

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:DEVice 10-5

Green ranges from zero to one, with zero indicating “no green” and one indicating “fullintensity green.”

Blue ranges from zero to one, with zero indicating “no blue” and one indicating “fullintensity blue.”

At *RST, these parameters are set to the DEFault values, equivalent to executing DEFaultcommand. The RGB command is coupled to the HSL command. Changing values in eitherwill affect the values of the other.

10.4.1.2 :DEFaultHard COPy:DEVice:CMAP:DEFault

Sets the color map to the instrument’s default values for all colors, except that COLor[1]shall be represent “black,” and COLor2 shall represent “white” or the actual color of amonochrome display.

10.4.2 :COLor <Boolean>Hard COPy:DEVice:COLor

Sets or queries whether color information should be sent as part of the plot or printinformation, in those languages that support both color and monochrome (black and white).

At *RST, the value of this parameter is OFF.

10.4.3 :LANGuage PCL[<n>] | HPGL[<n>] | POSTscript[<n>]Hard COPy:DEVice:LANGuage

Selects the control language or data format to be used when sending out plot or printinformation.

PCL Hewlett-Packard’s Printer Control Language.

HPGL Hewlett-Packard’s Graphics Language.

Information about PCL and HPGL is available by contacting: HP Peripheral Developer Program 16399 West Bernardo Drive San Diego, CA 92127-1899 (619) 487-4100

POSTscript Adobe Systems printer language.

Information about PostScript is available by contacting: Adobe Systems Incorporated 1585 Charleston Road Mountain View, CA 94039-7900 (415) 961-4400

The optional number, [<n>], following the languages, refers to a specific version of thatlanguage.

At *RST, the value of this parameter is device dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-6 HCOPy:DEVice

10.4.4 :MODE TABLe | GRAPhHard COPy:DEVice:MODE

Sets or queries how the data is to be represented in the hard copy. TABLe implies the data isformatted into a table rather than a pictorial form. Only characters appear on the output.GRAPh implies the format is a graph or picture. The graph may be generated using vectors,raster, or other available technology.

At *RST, the value of this setting is device dependent.

10.4.5 :RESolution <numeric_value>Hard COPy:DEVice:RESolution

Sets or queries the resolution of the result on the hard copy device. This setting is generallyused to affect the quality of the output from a raster printer.


10.4.5.1 :UNIT <SUFFIX PROGRAM DATA>Hard COPy:DEVice:RESolution:UNIT

Sets or queries the units of the RESolution setting.


10.4.6 :SPEed <numeric_value>Hard COPy:DEVice:SPEed

Sets or queries the speed at which vectors are drawn. This setting is generally used to affectthe quality of the output from a pen plotter.


10.4.6.1 :UNIT <SUFFIX PROGRAM DATA>Hard COPy:DEVice:SPEed:UNIT

Sets or queries the units of the SPEed setting.

At *RST, the value of this parameter is cm/sec.

10.5 :FEED <data_handle>Hard COPy:FEED

Sets or queries the data flow to be fed into the Hard COPy block.


10.6 [:IMMediate]Hard COPy:IMMediate

This command immediately initiates the plot or print according to the current Hard COPysetup parameters. All of the items under the ITEM node which are turned ON (STATe ON)are plotted or printed.

10.7 :ITEMHard COPy:ITEM

The :ITEM subsystem collects together commands to configure what items of data will beplotted or printed, and how that data shall appear.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:FEED <data_handle> 10-7

Most data item nodes have :COLor nodes to allow the user to set the color of the specificdata item. The parameter to the COLor node selects either the actual pen number of thehardcopy device, or the color map number, whichever value the hardcopy device expects.Some devices may elect not to support some or all of the COLor nodes. For example, adevice which has a color DISPlay may elect to use just the existing colors in the DISPlaywhen plotting or printing a color hardcopy.

10.7.1 :ALLHard COPy:ITEM:ALL

This subsystem is used to plot or print all ITEMs.

10.7.1.1 :DATA?Hard COPy:ITEM:ALL:DATA?

All ITEMs, regardless of their individual states, are encapsulated in an <INDEFINITELENGTH ARBITRARY RESPONSE DATA> element.

10.7.1.2 [:IMMediate]Hard COPy:ITEM:ALL:IMMeditate

Immediately plot or print all ITEMs, regardless of their individual states.

10.7.2 :ANNotationHard COPy:ITEM:ANNotation

Configures the plotting or printing of any display annotation.

10.7.2.1 :COLor <numeric_value>Hard COPy:ITEM:ANNotation:COLor

Sets or queries the color to be used for plotting or printing the display annotation.


10.7.2.2 :DATA?Hard COPy:ITEM:ANNotation:DATA?

Returns the display annotation encapsulated in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element.

10.7.2.3 [:IMMediate]Hard COPy:ITEM:ANNotation:IMMeditate

Immediately plot or print the display annotation.

10.7.2.4 :STATe <Boolean>Hard COPy:ITEM:ANNotation:STATe

Sets or queries whether ANNotation should be plotted or printed when theHCOPy:IMMediate command or HCOPy:DATA? query is sent.


10.7.3 :CUTHard COPy:ITEM:CUT

Configures cutting the page after the plot or print is complete.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-8 HCOPy:ITEM

10.7.3.1 :DATA?Hard COPy:ITEM:CUT:DATA?

Returns what would be sent to the hard copy device to cut the page encapsulated in an<INDEFINITE LENGTH ARBITRARY RESPONSE DATA> element.

10.7.3.2 [:IMMediate]Hard COPy:ITEM:CUT:IMMediate

Immediately cut the page.

10.7.3.3 :STATe <Boolean>Hard COPy:ITEM:CUT:STATe

Sets or queries whether a page cut should be performed as part of the HCOPy:IMMediatecommand or HCOPy:DATA? query.


10.7.4 :FFEedHard COPy:ITEM:FFEEd

Configures form-feeding after the plot or print is complete.

10.7.4.1 :DATA?Hard COPy:ITEM:FFEEd:DATA?

Returns what would be sent to the hard copy device to do a form feed encapsulated in an<INDEFINITE LENGTH ARBITRARY RESPONSE DATA> element.

10.7.4.2 [:IMMediate]Hard COPy:ITEM:FFEEd:IMMediate

Immediately form-feed the page.

10.7.4.3 :STATe <Boolean>Hard COPy:ITEM:FFEEd:STATe

Sets or queries whether a form feed should be performed as part of the HCOPy:IMMediatecommand or HCOPy:DATA? query.


10.7.5 :LABelHard COPy:ITEM:LABel

Configures the plotting or printing of the user entered label or title. The text for LABel is notsupplied by the source of the FEED connection. The TEXT is supplied by a setting in thissubsystem since it could only be generated by the user. It might reflect specific operatingconditions or refer to a specific part being tested. Where on the physical page theLABel:TEXT is actually plotted/printed is device dependent.

10.7.5.1 :COLor <numeric_value>Hard COPy:ITEM:LABel:COLor

Sets or queries the color to be used for plotting or printing the label.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:ITEM 10-9

10.7.5.2 :DATA?Hard COPy:ITEM:LABel:DATA?

Returns the label encapsulated in an <INDEFINITE LENGTH ARBITRARY RESPONSEDATA> element.

10.7.5.3 [:IMMediate]Hard COPy:ITEM:LABel:IMMediate

Immediately plot or print the label.

10.7.5.4 :STATe <Boolean>Hard COPy:ITEM:LABel:STATe

Sets or queries whether the label should be plotted or printed when the HCOPy:IMMediatecommand or HCOPy:DATA? query is sent.


10.7.5.5 :TEXT <string>Hard COPy:ITEM:LABel:TEXT

Sets or queries the contents of the user label. The contents of the <string> is placed in anappropriate place on the hard copy output. The string may contain formatting characters. Atextual label containing the empty string ("") shall be plotted/printed as a single blank line.

At *RST, all textual labels are set to the empty string.

10.7.6 :MENUHard COPy:ITEM:MENU

Configures the plotting or printing of the device menu.

10.7.6.1 :COLor <numeric_value>Hard COPy:ITEM:MENU:COLor

Sets or queries the color to be used for plotting or printing the menu.


10.7.6.2 :DATA?Hard COPy:ITEM:MENU:DATA?

Returns the menu encapsulated in an <INDEFINITE LENGTH ARBITRARY RESPONSEDATA> element.

10.7.6.3 [:IMMediate]Hard COPy:ITEM:MENU:IMMediate

Immediately plot or print the menu.

10.7.6.4 :STATe <Boolean>Hard COPy:ITEM:MENU:STATe

Sets or queries whether the menu should be plotted or printed when the HCOPy:IMMediatecommand or HCOPy:DATA? query is sent.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-10 HCOPy:ITEM

10.7.7 :TDSTampHard COPy:ITEM:TDSTamp

Configures the plotting or printing of a time and date stamp.

10.7.7.1 :COLor <numeric_value>Hard COPy:ITEM:TDSTamp:COLor

Sets or queries the color to be used for plotting or printing the time and date stamp.


10.7.7.2 :DATA?Hard COPy:ITEM:TDSTamp:DATA?

Returns the time and date stamp encapsulated in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element.

10.7.7.3 [:IMMediate]Hard COPy:ITEM:TDSTamp:IMMediate

Immediately plot or print the time and date stamp.

10.7.7.4 :STATe <Boolean>Hard COPy:ITEM:TDSTamp:STATe

Sets or queries whether the time and date stamp should be plotted or printed when theHCOPy:IMMediate command or HCOPy:DATA? query is sent.


10.7.8 [:WINDow]Hard COPy:ITEM:WINDow

Configures the plotting or printing of windows.

10.7.8.1 :DATA?Hard COPy:ITEM:WINDow:DATA?

Returns the window encapsulated in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element.

10.7.8.2 [:IMMediate]Hard COPy:ITEM:WINDow:IMMediate

Immediately plot or print the window.

10.7.8.3 :STATe <Boolean>Hard COPy:ITEM:WINDow:STATe

Sets or queries whether the window should be plotted or printed when theHCOPy:IMMediate command or HCOPy:DATA? query is sent.


10.7.8.4 :TEXTHard COPy:ITEM:WINDow:TEXT

Configures the plotting or printing of text blocks or textual labels.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:ITEM 10-11

10.7.8.4.1 :COLor <numeric_value>Hard COPy:ITEM:WINDow:TEXT:COLor

Sets or queries the color to be used for plotting or printing TEXT.


10.7.8.4.2 :DATA?Hard COPy:ITEM:WINDow:TEXT:DATA?

Returns the menu encapsulated in an <INDEFINITE LENGTH ARBITRARY RESPONSEDATA> element.

10.7.8.4.3 [:IMMediate]Hard COPy:ITEM:WINDow:TEXT:IMMediate

Immediately plot or print the text blocks or textual labels.

10.7.8.4.4 :STATe <Boolean>Hard COPy:ITEM:WINDow:TEXT:STATe

Sets or queries whether the text blocks or textual labels should be plotted or printed when theHCOPy:IMMediate command or HCOPy:DATA? query is sent.


10.7.8.5 :TRACeHard COPy:ITEM:WINDow:TRACe

Configures the plotting or printing of graphical trace data.

10.7.8.5.1 :COLor <numeric_value>Hard COPy:ITEM:WINDow:TRACe:COLor

Sets or queries the color to be used for plotting or printing the trace.


10.7.8.5.2 :DATA?Hard COPy:ITEM:WINDow:TRACe:DATA?

Returns the trace encapsulated in an <INDEFINITE LENGTH ARBITRARY RESPONSEDATA> element.

10.7.8.5.3 :GRATiculeHard COPy:ITEM:WINDow:TRACe:GRATicule

Configures the plotting or printing of the graticule.

10.7.8.5.3.1 :COLor <numeric_value>Hard COPy:ITEM:WINDow:TRACe:GRATicule:COLor

Sets or queries the color to be used for plotting or printing the graticule.


10.7.8.5.3.2 :DATA?Hard COPy:ITEM:WINDow:TRACe:GRATicule:DATA?

Returns the graticule encapsulated in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-12 HCOPy:ITEM

10.7.8.5.3.3 [:IMMediate]Hard COPy:ITEM:WINDow:TRACe:GRATicule:IMMediate

Immediately plot or print the graticule.

10.7.8.5.3.4 :STATe <Boolean>Hard COPy:ITEM:WINDow:TRACe:GRATicule:STATe

Sets or queries whether the graticule should be plotted or printed when theHCOPy:IMMediate command or HCOPy:DATA? query is sent.


10.7.8.5.4 [:IMMediate]Hard COPy:ITEM:WINDow:TRACe:IMMediate

Immediately plot or print the trace.

10.7.8.5.5 :LTYPe SOLid | DOTTed | DASHed | STYLe<n>Hard COPy:ITEM:WINDow:TRACe:LTYPe

Sets or queries the line type to be used for plotting or printing the trace.

For each value of <n> in the STYLe parameter, the appearance of the line type shall bedifferent. The STYLe line types should be chosen so they appear different on the specifichard copy device being used. The actual appearance is device dependent.


10.7.8.5.6 :STATe <Boolean>Hard COPy:ITEM:WINDow:TRACe:STATe

Sets or queries whether the trace should be plotted or printed when the HCOPy:IMMediatecommand or HCOPy:DATA? query is sent.


10.8 :PAGEHard COPy:PAGE

This subsystem contains commands to set up parameters relating to the medium of the plotor print output.

10.8.1 :DIMensionsHard COPy:PAGE:DIMensions

Sets the plot or print dimensions. Different plotters or printers allow the user to set the pagedimensions in different ways, such as length, width dimensions of the page, selecting astandard page size, or setting “corners” of the page in terms of plotter units (that is p1 andp2). A device will likely support the setting of plot or print dimensions in a subset of theseways, depending on which plotter or printer(s) it supports. The interaction of the variousdimension commands is device dependent.

10.8.1.1 :AUTO <Boolean>Hard COPy:PAGE:DIMensions:AUTO

When AUTO is on the device selects the default page dimensions. When AUTO is OFF thepage dimensions are set by the other setting in this subsystem.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:PAGE 10-13

At *RST, the value of this parameter is ON.

10.8.1.2 :LLEFt <numeric_value>,<numeric_value>Hard COPy:PAGE:DIMensions:LLEFt

Sets or queries the x,y position of lower left corner of the page. Units are percent of thewidth and length of the page.


10.8.1.3 :QUADrant[<n>]Hard COPy:PAGE:DIMensions:QUADrant

Sets dimensions so that the plot/print occupies one quadrant of the page.

<n> quadrant

1 upper right 2 1

2 upper left

3 lower left

4 lower right 3 4This command is an event only.

10.8.1.4 :URIGht <numeric_value>,<numeric_value>Hard COPy:PAGE:DIMensions:URIGht

Specifies the x,y position of upper right corner of the page. Units are percent of the widthand length of the page.


10.8.2 :LENGth <numeric_value>Hard COPy:PAGE:LENGth

Sets or queries the length of the page to be plotted or printed.


10.8.3 :ORIentation LANDscape | PORTraitHard COPy:PAGE:ORIentation

Sets or queries the orientation of the plot or print. Switching between LANDscape andPORTrait rotates the hardcopy result by 90 degrees. No other settings are changed.


10.8.4 :SCALe <numeric_value>Hard COPy:PAGE:SCALe

Sets or queries a scaling factor which is applied to the hard copy output. This factor appliesto both dimensions. The output from HCOPy shall not attempt to place anything on the pageoutside the limits set under :DIMensions even when :SCALe is greater than one.

At *RST, the value of this setting is one.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-14 HCOPy:PAGE

10.8.5 :SIZE CUSTom|A|B|C|D|E|A0|A1|A2|A3|A4|B0|B1|B2|B3|B4|B5Hard COPy:PAGE:SIZE

Sets or queries the size of the paper in terms of a standard paper size. If LENGth or WIDthare set, the value of this setting becomes CUSTom.


10.8.6 :UNIT <SUFFIX PROGRAM DATA>Hard COPy:PAGE:UNIT

Sets or queries the units for LENGth and WIDTh under DIMensions.


10.8.7 :WIDTh <numeric_value>Hard COPy:PAGE:WIDTh

Sets or queries the width of the page to be plotted or printed.


10.9 :SDUMpHard COPy:SDUMp

The Screen DUMp subsystem obtains its FEED from the whole DISPlay subsystem, andshall only be used where a DISPlay subsystem is present in an instrument.

10.9.1 :DATA?Hard COPy:SDUMp:DATA?

Returns the whole DISPlay encapsulated in an <INDEFINITE LENGTH ARBITRARYRESPONSE DATA> element.

10.9.2 [:IMMediate]Hard COPy:SDUMp:IMMediate

This event shall cause the whole DISPlay to be plotted or printed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


HCOPy:SDUMp 10-15

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


10-16 HCOPy:SDUMp

11 INPut SubsystemThe INPut subsystem controls the characteristics of a sensor’s input ports.

KEYWORD PARAMETER FORM NOTESINPut :ATTenuation <numeric_value> :AUTO <Boolean>|ONCE

RS013 :STATe <Boolean> 1994 :BIAS 1991 HP034

:CURRent 1991 HP034

:AC <numeric_value> 1991 HP034

[:DC] <numeric_value> 1991 HP034


:TYPE CURRent | VOLTage 1991 HP034

:VOLTage 1991 HP034

:AC <numeric_value> 1991 HP034

[:DC] <numeric_value> 1991 HP034

:COUPling AC|DC|GROund 1991 TWOS02

:FILTer :AWEighting 1991 HP036


:HPASs :FREQuency <numeric_value> [:STATe] <Boolean> [:LPASs] :FREQuency <numeric_value> [:STATe] <Boolean> :GAIN <numeric_value> :AUTO <Boolean>|ONCE

RS013 :STATe <Boolean> 1994 :GUARd LOW|FLOat :IMPedance <numeric_value> :LOW FLOat|GROund :OFFSet <numeric_value> 1991 TWOS01

:STATe <Boolean> 1991 TWOS01

TK019 :POLarity NORMal|INVerted 1994RS010a :POLarization <numeric_value> 1994RS010a :HORizontal [no query] 1994RS010a :VERTical [no query] 1994RS010a :POSition 1994RS010a [:X] 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut 11-1

KEYWORD PARAMETER FORM NOTESRS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a :Y 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a :Z 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-2 INPut

KEYWORD PARAMETER FORM NOTESRS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994

[:STATe] <Boolean> :TYPE <character data> 1992 RS007

11.1 :ATTenuation <numeric_value>INPut:ATTenuation

Sets the input ATTenuation. The default units are in the current relative amplitude units.

This should only be used where the setting is not reflected within the SENSe system. Forexample, setting the input attenuation to 10 dB will cause the measured signal to decrease inamplitude by 10 dB.

This setting is not coupled to INPut:GAIN. If both ATTenuation and GAIN were set to 10dB, the net result would be a signal of the original amplitude.


11.1.1 :AUTO <Boolean>|ONCEINPut:ATTenuation:AUTO

AUTO ON changes the ATTenuation to achieve maximum sensitivity without overloadingthe input channel. Programming a specified ATTenuation sets AUTO OFF.


RS01311.1.2 :STATe <Boolean>INPut:ATTenuation:STATe

Turns the input attenuator ON and OFF. OFF means, that any attenuation circuits are takenout of the signal path, thus, no distortion to the signal will happen.


11.2 :BIASINPut:BIAS

HP034

This subsystem is used to control the bias applied to an external tranducer/detector.

11.2.1 :CURRentINPut:BIAS:CURRent

HP034

Specifies the specific bias current being generated.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:ATTenuation 11-3

11.2.1.1 :AC <numeric_value>INPut:BIAS:CURRent:AC

HP034

Specifies the AC component of the bias current. The parameter is specified in Amperes.


11.2.1.2 [:DC] <numeric_value>INPut:BIAS:CURRent:DC

HP034

Specifies the DC component of the bias current. The parameter is specified in Amperes.


11.2.2 [:STATe] <Boolean>INPut:BIAS:STATe

HP034

Sets or queries whether or not input biasing is enabled.


11.2.3 :TYPE CURRent | VOLTage INPut:BIAS:TYPE CURRent

HP034

Specifies the type of bias to be generated. CURRent specifies a current bias and VOLTagespecifies a voltage bias.


11.2.4 :VOLTageINPut:BIAS:VOLTage

HP034

Specifies the specific bias voltage being generated.

11.2.4.1 :AC <numeric_value>INPut:BIAS:VOLTage:AC

HP034

Specifies the AC component of the bias voltage. The parameter is specified in Volts.


11.2.4.2 [:DC] <numeric_value>INPut:BIAS:VOLTage:DC

HP034

Specifies the DC component of the bias voltage. The parameter is specified in Volts.


11.3 :COUPling AC|DC|GROund INPut:COUPling

TWOS02

Selects AC or DC coupling for the specified signal. DC coupling allows the measurementsignal’s AC and DC component to pass. AC coupling passes only the measurement signal’sAC component. GROund coupling allows no signal to pass at all and grounds the inputamplifier without grounding the input signal.

TWOS02


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-4 INPut:COUPling AC|DC|GROund

11.4 :FILTerINPut:FILTer

The FILTer function allows a filter to be inserted in the path of the measurement signal. TheFREQuency function allows the programming of a specific break frequency. The STATecommand enables the filter.

11.4.1 :AWEightingINPut:FILTer:AWEighting

HP036

Controls the “A” weighting input filter. This is a human hearing compensation filterdescribed in the IEC Recommendation 179 and ANSI S1.4.

11.4.1.1 [:STATe] <Boolean>INPut:FILTer:AWEighting:STATe

HP036

Turns the “A” weighting input filter on and off.

At *RST this value is device-dependent.

11.4.2 :HPASsINPut:FILTer:HPASs

Controls the high pass filter.

11.4.2.1 :FREQuency <numeric_value>INPut:FILTer:HPASs:FREQuency

Determines the cutoff frequency of the high pass filter. Default units are Hertz.


11.4.2.2 [:STATe] <Boolean>INPut:FILTer:HPASs:STATe

Turns the high pass filter ON and OFF.


11.4.3 [:LPASs]INPut:FILTer:LPASs

Controls the low pass filter.

11.4.3.1 :FREQuency <numeric_value>INPut:FILTer:LPASs:FREQuency

Determines the cutoff frequency of the low pass filter. Default units are Hertz.


11.4.3.2 [:STATe] <Boolean>INPut:FILTer:LPASs:STATe

Turns the low pass filter ON and OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:FILTer 11-5

11.5 :GAIN <numeric_value>INPut:GAIN

Sets the input GAIN. The default units are in the current relative amplitude units.

This should only be used where the setting is not reflected within the SENSe system. Forexample, setting the input gain to 10 dB will cause the measured signal to increase inamplitude by 10 dB.

This setting is not coupled to INPut:ATTenuation. If both ATTenuation and GAIN were setto 10 dB, the net result would be a signal of the original amplitude.


11.5.1 :AUTO <Boolean>|ONCEINPut:GAIN:AUTO

AUTO ON changes the GAIN to achieve maximum sensitivity without overloading the inputchannel.

AT *RST, this value is set to ON.

RS01311.5.2 :STATe <Boolean>INPut:GAIN:STATe

Turns the input gain (preamplifier) ON and OFF. OFF means, that any preamplifier circuitsare taken out of the signal path, thus, no distortion to the signal will happen. OFF is not thesame as INPut:GAIN 0 dB, because an isolation preamplifier will have that gain.


11.6 :GUARd LOW|FLOatINPut:GUARd

Connects guard to signal low terminal or allows guard to float.


11.7 :IMPedance <numeric_value>INPut:IMPedance

Termination input impedance for the input signal specified in Ohms.


11.8 :LOW FLOat|GROundINPut:LOW

Connects the low signal terminal to ground or allows it to float.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-6 INPut:GAIN

11.9 :OFFSet <numeric_value>INPut:OFFSet

TWOS01

Sets or queries the input OFFSet. OFFSet may take on positive and negative values. TheOFFSet shall be subtracted from the input, thus making OFFSet more positive shall make thesignal more negative. The default units are in the current amplitude units

Introducing an OFFSet in the input has the effect of offsetting the input signal, prior todetection in the SENSe block. Any offset introduced in the input block shall not be correctedfor in the sensor and subsquently the sensor results. For example, if the current amplitudeunits are in volts, a value of 5 shall decrease the input signal by 5 volts.

At *RST, the value of OFFSet is device-dependent.

11.9.1 :STATe <Boolean>INPut:OFFSet:STATe

TWOS01

Turns the effect of OFFSet ON or OFF.

At *RST, STATe shall be OFF.

TK01911.10 :POLarity NORMal|INVertedINPut:POLarity

Sets or queries the input polarity. NORMal causes the input signal to pass through the INPutblock without inversion. INVerted causes the polarity of the input signal to be reversed. Anyinversion introduced in the INPut block shall not be corrected for in the sensor andsubsequently the sensor results.

At *RST, this value is NORMal.

RS010a11.11 :POLarization <numeric_value>INPut:POLarization

Sets the polarization of the input. The default units are radian.


RS010a11.11.1 :HORizontal INPut:POLarization:HORizontal

Sets the polarization of the input to zero. This command is an event. Therefore it has noassociated query or meaning at *RST.

RS010a11.11.2 :VERTicalINPut:POLarization:VERTical

Sets the polarization of the input to PI/2 radians. This command is an event. Therefore it hasno associated query or meaning at *RST.

RS010a11.12 :POSitionINPut:POSition

The characteristics of an incoming signal can be affected by the input’s spatial position andorientation relative to the origin. The definition of the origin is application specific. Thissubsystem uses a righthand coordinate system and has only one origin.

In this subsystem only the IMMediate commands initiate movement.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:OFFSet 11-7

In this subsystem velocity is always positive.

RS010a11.12.1 [:X]INPut:POSition:X

Controls the settings concerning the X-axis.

RS010a11.12.1.1 :ANGLeINPut:POSition:X:ANGLe

Specifies the angle of rotation around the X-axis.

RS010a11.12.1.1.1 :DIRection UP|DOWNINPut:POSition:X:ANGLe:DIRection

Controls the direction of the movement when started with INITiate.

At *RST, this is set to UP

RS010a11.12.1.1.2 [:IMMediate] <numeric_value>INPut:POSition:X:ANGLe:IMMediate

This command indicates that the input is moved to the specified position without waiting forfurther commands.

*RST has no effect on the IMMediate value except that movement shall stop.

RS010a11.12.1.1.3 :LIMitINPut:POSition:X:ANGLe:LIMit

Sets the maximum bounds on the physical POSition.

RS010a11.12.1.1.3.1 :HIGH <numeric_value>INPut:POSition:X:ANGLe:LIMit:HIGH

Sets the maximum for the POSition.

At *RST, this value is set to the clockwise physical limit.

RS010a11.12.1.1.3.2 :LOW <numeric_value>INPut:POSition:X:ANGLe:LIMit:LOW

Sets the minimum for the POSition.

At *RST, this value is set to the counterclockwise physical limit.

RS010a11.12.1.1.3.3 :STATe <Boolean>INPut:POSition:X:ANGLe:LIMit:STATe

Controls whether the LIMit is enabled.


RS010a11.12.1.1.4 :OFFSet <numeric_value>INPut:POSition:X:ANGLe:OFFSet

This defines a single value that is subtracted from the physical POSition.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-8 INPut:POSition

RS010a11.12.1.1.5 :VELocity <numeric_value>INPut:POSition:X:ANGLe:VELocity

Controls the velocity of the angular rotation around the x-axis.


RS010a11.12.1.2 [:DISTance]INPut:POSition:X:DISTance

Controls the settings in linear direction of the X-axis.

RS010a11.12.1.2.1 :DIRection UP|DOWN INPut:POSition:X:DISTance:DIRection



RS010a11.12.1.2.2 [:IMMediate] <numeric_value>INPut:POSition:X:DISTance:IMMediate



RS010a11.12.1.2.3 :LIMitINPut:POSition:X:DISTance:LIMit


RS010a11.12.1.2.3.1 :HIGH <numeric_value>INPut:POSition:X:DISTance:LIMit:HIGH


At *RST, this value is set to the upper physical limit.

RS010a11.12.1.2.3.2 :LOW <numeric_value>INPut:POSition:X:DISTance:LIMit:LOW


At *RST, this value is set to the lower physical limit.

RS010a11.12.1.2.3.3 :STATe <Boolean>INPut:POSition:X:DISTance:LIMit:STATe



RS010a11.12.1.2.4 :OFFSet <numeric_value>INPut:POSition:X:DISTance:OFFSet



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:POSition 11-9

RS010a11.12.1.2.5 :VELocity <numeric_value>INPut:POSition:X:DISTance:VELocity

Controls the velocity of the displacement on the x-axis.


RS010a11.12.2 :YINPut:POSition:Y

Controls the settings concerning the Y-axis.

RS010a11.12.2.1 :ANGLeINPut:POSition:Y:ANGLe

Specifies the angle of rotation around the Y-axis.

RS010a11.12.2.1.1 :DIRection UP|DOWNINPut:POSition:Y:ANGLe:DIRection



RS010a11.12.2.1.2 [:IMMediate] <numeric_value>INPut:POSition:Y:ANGLe:IMMediate



RS010a11.12.2.1.3 :LIMitINPut:POSition:Y:ANGLe:LIMit


RS010a11.12.2.1.3.1 :HIGH <numeric_value>INPut:POSition:Y:ANGLe:LIMit:HIGH



RS010a11.12.2.1.3.2 :LOW <numeric_value>INPut:POSition:Y:ANGLe:LIMit:LOW



RS010a11.12.2.1.3.3 :STATe <Boolean>INPut:POSition:Y:ANGLe:LIMit:STATe



RS010a11.12.2.1.4 :OFFSet <numeric_value>INPut:POSition:Y:ANGLe:OFFSet


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-10 INPut:POSition


RS010a11.12.2.1.5 :VELocity <numeric_value>INPut:POSition:Y:ANGLe:VELocity

Controls the velocity of the angular rotation around the y-axis.


RS010a11.12.2.2 [:DISTance]INPut:POSition:Y:DISTance

Controls the settings in linear direction of the Y-axis.

RS010a11.12.2.2.1 :DIRection UP|DOWNINPut:POSition:Y:DISTance:DIRection



RS010a11.12.2.2.2 [:IMMediate] <numeric_value>INPut:POSition:Y:DISTance:IMMediate



RS010a11.12.2.2.3 :LIMitINPut:POSition:Y:DISTance:LIMit


RS010a11.12.2.2.3.1 :HIGH <numeric_value>INPut:POSition:Y:DISTance:LIMit:HIGH



RS010a11.12.2.2.3.2 :LOW <numeric_value>INPut:POSition:Y:DISTance:LIMit:LOW



RS010a11.12.2.2.3.3 :STATe <Boolean>INPut:POSition:Y:DISTance:LIMit:STATe



RS010a11.12.2.2.4 :OFFSet <numeric_value>INPut:POSition:Y:DISTance:OFFSet



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:POSition 11-11

RS010a11.12.2.2.5 :VELocity <numeric_value>INPut:POSition:Y:DISTance:VELocity

Controls the velocity of the displacement on the y-axis.


RS010a11.12.3 :Z INPut:POSition:Z

Controls the settings concerning the Z-axis

RS010a11.12.3.1 :ANGLeINPut:POSition:Z:ANGLe

Specifies the angle of rotation around the Z-axis.

RS010a11.12.3.1.1 :DIRection UP|DOWNINPut:POSition:Z:ANGLe:DIRection



RS010a11.12.3.1.2 [:IMMediate] <numeric_value>INPut:POSition:Z:ANGLe:IMMediate



RS010a11.12.3.1.3 :LIMitINPut:POSition:Z:ANGLe:LIMit


RS010a11.12.3.1.3.1 :HIGH <numeric_value>INPut:POSition:Z:ANGLe:LIMit:HIGH



RS010a11.12.3.1.3.2 :LOW <numeric_value>INPut:POSition:Z:ANGLe:LIMit:LOW



RS010a11.12.3.1.3.3 :STATe <Boolean>INPut:POSition:Z:ANGLe:LIMit:STATe



RS010a11.12.3.1.4 :OFFSet <numeric_value>INPut:POSition:Z:ANGLe:OFFSet


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-12 INPut:POSition


RS010a11.12.3.1.5 :VELocity <numeric_value>INPut:POSition:Z:ANGLe:VELocity

Controls the velocity of the angular rotation around the z-axis.


RS010a11.12.3.2 [:DISTance]INPut:POSition:Z:DISTance

Controls the settings in linear direction of the Z-axis.

RS010a11.12.3.2.1 :DIRection UP|DOWNINPut:POSition:Z:DISTance:DIRection



RS010a11.12.3.2.2 [:IMMediate] <numeric_value>INPut:POSition:Z:DISTance:IMMediate



RS010a11.12.3.2.3 :LIMitINPut:POSition:Z:DISTance:LIMit


RS010a11.12.3.2.3.1 :HIGH <numeric_value>INPut:POSition:Z:DISTance:LIMit:HIGH



RS010a11.12.3.2.3.2 :LOW <numeric_value>INPut:POSition:Z:DISTance:LIMit:LOW



RS010a11.12.3.2.3.3 :STATe <Boolean>INPut:POSition:Z:DISTance:LIMit:STATe



RS010a11.12.3.2.4 :OFFSet <numeric_value>INPut:POSition:Z:DISTance:OFFSet



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INPut:POSition 11-13

RS010a11.12.3.2.5 :VELocity <numeric_value>INPut:POSition:Z:DISTance:VELocity

Controls the velocity of the displacement on the z-axis.


11.13 [:STATe] <Boolean>INPut:STATe

The STATe command connects the input terminal to the measurement signal path when ON.It can be turned OFF to allow maximum isolation of the measurement signal. Note that thisdoes not mean ground the input signal.

At *RST, STATe ON shall be selected.

11.14 :TYPE <character data>INPut:TYPE

RS007

Selects the input characteristic to be used if more than one is available.

The following characteristics are currently defined for instruments:

BALanced – balanced or differential input.

UNBalanced – unbalanced with respect to ground.

At *RST the TYPE is device-dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


11-14 INPut[:STATe]

12 INSTrument SubsystemAn instrument may support multiple logical instruments. A dual channel power supply forexample is considered as two logical instruments. The logical instruments are not required tohave identical functionality, nor does the functionality have to be available simultaneously.The INSTrument subsystem provides a mechanism to identify and select logical instrumentsby either name or number. In this way a particular logical instrument could be selected and itwould respond to commands, such as MEASure, in the same manner as a dedicatedinstrument having the same functionality as the logical instrument. The INSTrumentidentifiers have no fixed correspondence to the numeric suffixes allowed with commandheaders.

KEYWORD PARAMETER FORM NOTESINSTrument

TK026 :CATalog? [query only] 1994 TK026 :FULL? [query only] 1994

:COUPle [:<subsystem>] ALL|NONE|<list> :DEFine 1999 :GROup <identifier>,<identifier_list> 1999 [:NAME] <identifier>,<numeric_value> 1999

TK026 :DELete 1999TK026 [:NAME] <identifier> [event; no query] 1994TK026 :ALL [event; no query] 1994

:NSELect <numeric_value> JP Change

[:SELect] <identifier> 1999 :STATe <Boolean>

TK02612.1 :CATalog?INSTrument:CATalog?

The CATalog query returns a comma-separated list of strings which contains the names ofall logical instruments and groups. If no logical instruments are defined, a single null stringis returned.

TK026Some instruments may have one or more intrinsic (permanent) <identifier>’s. These arelisted along with any user-named <identifier>’s.

TK02612.1.1 :FULL?INSTrument:CATalog?:FULL?

TK026CATalog:FULL? query returns a list of string - number pairs. The string contains the nameof the logical instrument. The immediately following NR1-formatted number is itsassociated logical instrument number. All response data elements are comma separated. If nological instrument is defined, a null string followed by a zero is returned.

TK026Intrinsic <identifier>’s associated with logical instrument numbers are listed along with anyuser-named <identifier>’s and numbers.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INSTrument Subsystem 12-1

TK02612.2 :COUPle[:<subsystem>] ALL|NONE|<list>INSTrument:COUPle

Defines a coupling between various logical instruments or between various channels withinan instrument. The COUPle command consists of an optional subsystem node followed by asingle parameter.

The subsystem node denotes a SCPI subsection which can either affect each instrumentindividually, or affect all instruments/channels collectively. This node is used only when theuser can turn this coupling ON or OFF. Predefined couplings need not use this node. If nonode follows the COUPle command, then the entire instrument is assumed to be coupled.Coupling a node lower in the tree overrides any couplings which are assigned at a higherlevel.

The parameter indicates to which logical instruments the specified coupling is to apply. ALLindicates that specified coupling is to apply to all logical instruments. NONE indicates thatspecified coupling is to removed. A list of instruments specifies a particular set of logicalinstruments to be coupled.

Within SCPI certain subsystems, such as SYSTem, STATus, MEMory, MMEMory, TESTand DIAGnostic, are considered common to all logical instruments. That is, they appearcoupled across all logical instruments, and they cannot be uncoupled. The IEEE commoncommands are assumed to always operate on all logical instruments.

At *RST, all subsystems are uncoupled as far as the instrument hardware allows.

12.3 :DEFineINSTrument:DEFine

12.3.1 :GROup <identifier>,<identifier_list>INSTrument:DEFine:GROup

Defines or queries a group of instruments. The <identifier> is character data. The<identifier_list> is a comma-separated list of strings which contains the names of logicalinstruments. The defined instruments can be queried using :INSTrument:DEFine:GROup?<identifier>. No instrument selection is performed by this command. Any instrumentimplementing the :GROup command shall define which commands are affected by groups.

When groups are defined and used, and data is set or queried, the following rules shall applyunless otherwise noted:

When setting a list of values, each value will apply to the corresponding instrument in theselected group. If the number of values does not correspond to the number of instrumentsselected, no action is taken and error -115 is reported.

When a set of values is required by a command, one set of values may be sent for eachinstrument in the group. For instance, FOO a,b;

becomes

FOO a1,b1,a2,b2,...

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


12-2 INSTrument Subsystem

If a single parameter value is supplied for a command that expects one value per groupmember, the value is applied to every instrument in the currently selected group.

Note that commands that take an arbitrary number of optional parameters need to havesome way to determine how many parameters apply to each member of the group.

When queried, the command shall return the value(s) for each instrument in the currentlyselected group.

When groups are defined and used, events will be sent to all instruments in the currentlyselected group.

12.3.2 [:NAME] <identifier>,<numeric_value>INSTrument:DEFine[:NAME]

The command form defines a logical instrument name, <identifier>, and associates it with alogical instrument number, <numeric_value>. The <identifier> is in character data format.

The query form takes only <identifier> as a parameter and returns the logical instrumentnumber.

12.4 :DELeteINSTrument:DELete

The DELete subsystem disassociates <identifier>’s from logical instrument numbers orgroups of instrument <identifier>’s. After the :DELete command executes, the <identifier>is no longer accessible until it is redefined. The instrument behaves as if the <identifier>never existed.

12.4.1 :ALLINSTrument:DELete:ALL

This command is an event that disassociates all identifiers from their logical instrumentnumbers or identifier list, except for the currently selected identifier and any intrinsicidentifier definitions. There is no query form.

TK026The situation of “nothing to delete” does not cause an execution error.

TK026This command is an event, and therefore has no *RST value associated with it.

TK026*RST has no effect.

12.4.2 [:NAME] <identifier>INSTrument:DELete:NAME

This command is an event, which disassociates the named <identifier> from its logicalinstrument number or identifier list. There is no query form.

TK026Attempting to delete the currently selected logical instrument or any intrinsic (permanent)<identifier> - number associations results in an -221, (settings conflict) execution error.

TK026This command is an event, and therefore has no *RST value associated with it.

TK026

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


INSTrument Subsystem 12-3

12.5 :NSELect <numeric_value> JP Change

INSTrument:NSELectJP Change

This command is used in conjunction with the SELect command. It serves the same purpose,except that it uses a numeric value instead of the identifier used in the SELect command.When queried it shall return the logical instrument number. Note that the numbering used forlogical instruments shall directly correspond to the numbers used in status reporting formultiple instruments; specifically the STATus:QUEStionable:INSTrument andSTATus:OPERation:INSTrument commands. By selecting an instrument with either SELector NSELect and querying the selected instrument with the other command, the equivalencebetween the instrument number and identifier can be determined. For example, by selectinga logical instrument using the SELect command with its name identifier and then queryingwhich logical instrument is selected with the NSELect command, the corresponding numericvalue shall be returned.

Assigning numeric values to logical instrument identifiers is not appropriate for instrumentgroups. Therefore, NSELect returns an error if a group has been selected.

HP066, JP Change

12.6 [:SELect] <identifier>INSTrument:SELect

This command selects a path or entire instrument or group as the default. When a logicalinstrument or a group is selected, all other logical instruments or groups are unavailable forprogramming until selected. If group logical identifiers are not used, and either :SELect or:NSELect commands are implemented, then both of the commands must be implemented.

Character data names may be predefined by the instrument.

At *RST, a device-dependent instrument is selected.

12.7 :STATe <Boolean>INSTrument:STATe

Turns the selected logical instrument ON or OFF. A logical instrument does not have to beturned OFF before another logical instrument is selected. That is, several logical instrumentsmay be active, while only one may be selected. When an instrument is active, measurementsoccur and signals are generated. When inactive, measurements do not occur and signals arenot generated. When a logical instrument is selected, yet is inactive, all commands shall beprocessed so that the logical instrument shall reflect the state changes requested when thelogical instrument is turned on. The exception to this are commands which would normallycause trigger events in an active logical instrument. Any of these commands shall cause anexecution error (-200) to be generated.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


12-4 INSTrument Subsystem

13 MEMory SubsystemThe purpose of the memory subsystem is to manage instrument memory. This specificallyexcludes memory used for mass storage, which is defined in the MMEMory Subsystem.Instrument memory may be used to store several data types (e.g. ASCii, BINary, instrumentSTATe, TRACe or MACRo.) The data types available for a given instrument aredevice-dependent.

An instrument may support either fixed or dynamic allocation of instrument memory,between the different data types. With fixed allocation a certain amount of memory isdedicated to each of the supported data types. The dedicated memory is unavailable for useby any other data type. Alternatively, with dynamic allocation, instrument memory is sharedbetween the various data types supported on a demand basis.

In the MEMory:TABLe subsystems, many fundamental measurement are defined assubnodes below :TABLe, such as MEMory:TABLe:FREQuency, :VOLTage, :POWer, etc.These nodes define standardized entries in the table (note that these entries can beconceptualized as either a column or a row). While it makes sense to define widely usedentries in the SCPI Volume 2 standard, there is sometimes a desire to standardize veryinstrument class specific names. Where instrument class specific names requirestandardization, and little or no overlap is expected with other instrument classes, theseinstrument class specific MEMory:TABLe nodes are defined in the Volume 4, Instrumentclasses chapter to which they apply.

As an example, the SCPI commands for Chassis Dynamometers :FORCe :SPEed and TIMEare defined in Volume 2 under :MEMory:TABLe. These are fundamental measurements,and might be used by many instruments. However Deceleration RATe is deemed to bespecific to dynamometers and is defined in Volume 4.

KEYWORD PARAMETER FORM NOTESMEMory :CATalog [:ALL]? [query only] :ASCii? [query only] :BINary? [query only] :MACRo? [query only] :STATe? [query only] :TABLe? [query only] 1992 HP058A

:CLEar 1993 PH076 [:NAME] <name> [event; no query] 1993 PH076 :TABLe <name> [event; no query] 1993 PH076 :COPY 1993 PH076 [:NAME] <name>,<name> [event; no query] 1993 PH076 :TABLe <name> [event; no query] 1993 PH076

TK023B :DATA <name>,<data> 1994 :DELete :ALL [event; no query]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


MEMory Subsystem 13-1

KEYWORD PARAMETER FORM NOTES [:NAME] <name> [event; no query] :EXCHange 1993 PH076 [:NAME] <name>,<name> [event; no query] 1993 PH076 :TABLe <name> [event; no query] 1993 PH076 :FREE [:ALL]? [query only] :ASCii? [query only] :BINary? [query only] :MACRo? [query only] :STATe? [query only] :TABLe? [query only] 1992 HP058A

:NSTates? [query only]TK023B :STATe 1994TK023B :CATalog? [query only] 1994TK023B :DEFine <name>,<register_number> 1994TK023B :DEFine? <name> 1994

:TYPE? <name> [query only] :TABLe 1992 :BNUMber<n> <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :CCURve <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :CONCentration <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* HP058A

:CONDition 1993 PH074 [:MAGNitude] <Boolean> {,<Boolean>} 1993 PH074 :POINts? [query only] 1993 :CPOint <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* PH074 :CURRent 1992 HP058A

[:MAGNitude] <numeric_value>{,<numeric_value>} 1992 HP058A

:POINts? [query only] 1992 HP058A

:PHASe <numeric_value>{,<numeric_value>} 1992 HP058A


:DEFine <identifier>[,<identifier>] 1999 :DFACtory <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :DLASt <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :DLINearize <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :EXPected <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :FORCe 1999

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


13-2 MEMory Subsystem

KEYWORD PARAMETER FORM NOTES [:MAGNitude] <numeric_value> {,<numeric_value>} 1999 :POINts? [query only] 1999 HP058A

:FREQuency <numeric_value>{,<numeric_value>} 1992 HP058A

:POINts? [query only] 1992 :LABel <string>{,<string>} 1999* POINts [query only] 1999* :LLIMit <numeric_value>{,<numeric_value>} 1999 :POINts? [query only] 1999 :LOG <string>{,<string>} 1999* POINts [query only] 1999* HP058A

:LOSS 1992 HP058A




:POINts? [query only] 1992 :NCURve <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :POWer 1992 HP058A


:POINts? [query only] 1992 :RAW <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* HP058A

:RESistance 1992 HP058A



:SELect <identifier> 1999 :SPEed 1999 [:MAGNitude] <numeric_value> {,<numeric_value>} 1999 :POINts? [query only] 1999 :TIME 1999 [:MAGNitude] <numeric_value> {,<numeric_value>} 1999 :POINts? [query only] 1999 :TOLerance <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999* :ULIMit <numeric_value>{,<numeric_value>} 1999 :POINts? [query only] 1999 HP058A

:VOLTage 1992 HP058A




:POINts? [query only] 1992 :WFACtor <numeric_value>{,<numeric_value>} 1999* POINts [query only] 1999*

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



HP058A

* NOTE: The commands marked with an asterisk query or set values inside of predefinedemissions bench memory tables. The tables involved are as follows:

Table Column Name(s) DescriptionCPIxxRyy CPOint,TOLerance,WFACtorWT Linearization input cut point tablesGasBottle BNUMber,CONCentration,LABel Gas bottle tableLSIxxRyy CPOint,EXPected,RAW,CCURve,NCURve Linearization results tablesVERify BNUMber1,BNUMber2,...BNUMber Verify gas tableQLIxxRyy LOG Linearization log tablesQNIxxRyy LOG NOx efficiency log tablesSDRift DFACtory,DLASt,DLINearize Span Drift results tableSpanGas BNUMber1,BNUMber2,...BNUMber Span Gas tableTopGas BNUMber1,BNUMber2,...BNUMber Top Gas tableZDRift DFACtory,DLASt,DLINearize Zero Drift results tableZeroGas BNUMber1,BNUMber2,...BNUMber Zero Gas table

The <name> parameter is used to define a user label, which shall be <character programdata>. This label can then be used by the application in place of the specified data definedhere or in other subsystems. The <name> parameter is sent as <character data>, rather thanas a string, because that is the simplest IEEE 488.2 type that meets the requirements. When aname is returned, for example, in response to a CATalog? query, it must be sent as <stringresponse data>, so that a null string (“”) can indicate that nothing is defined.

The MEMory capabilities of an instrument are not part of the instrument state and are notaffected by *RST or *RCL. They may survive a power cycle, but this capability is optional.If the instrument implements SYSTem:SECure mode, MEMory:DELete:ALL must beexecuted when SYSTem:SEC OFF is executed.

13.1 :CATalogMEMory:CATalog

The CATalog queries return information on the current contents and state of the instrument’smemory. The returned data shall be in the following form:

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

The instrument shall return two numeric parameters and as many strings as there are items inthe directory list. The first parameter shall indicate the total amount of storage currentlyused, in bytes. The second parameter shall indicate the total amount of storage available, alsoin bytes. Each string parameter returned shall indicate the name, type and size of one in thedirectory list, thus:

<name>,<type>,<size>

The <name>, <type> and <size> are all character data. The <name> is the exact name of afile as it appears in the directory list, including an extension if present. The <size> providesthe size of the file in bytes. The <type> is indicated by the name of the major subsystem orone of the following:

Ed ChangeASCii — An ASCII text file

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Ed ChangeBINary — A binary file

Ed ChangeMACRo — An instrument macro

Ed ChangeSTATe — An instrument state

HP058ATABLe — A table of data

The qualified CATalog query for TRACe memory is specified in the TRACe subsystem.

13.1.1 [:ALL]?MEMory:CATalog:ALL?

If the CATalog query is qualified by the optional ALL node then the query shall return adirectory list and memory sizes related to all allocatable items in instrument memory. Notethat this includes all allocatable objects, such as trace, etc.

13.1.2 :ASCii?MEMory:CATalog:ASCii?

If the CATalog query is qualified by the ASCii node then the query shall return the directorylist related only to ASCii items in instrument memory. The memory usage and availabilityparameters shall reflect values that correspond to values for ASCii data. In an instrument thathas dedicated memory for ASCii data types, values reported shall be different from the totalgiven by a CATalog of ALL types.

13.1.3 :BINary?MEMory:CATalog:BINary?

If the CATalog query is qualified by the BINary node then the query shall return thedirectory list related only to BINary items in instrument memory. The memory usage andavailability parameters shall reflect values that correspond to values for BINary data. In aninstrument that has dedicated memory for BINary data types, values reported shall bedifferent from the total given by a CATalog of ALL types.

13.1.4 :MACRo?MEMory:CATalog:MACRo?

If the CATalog query is qualified by the MACRo node then the query shall return thedirectory list related only to MACRo items in instrument memory. The memory usage andavailability parameters shall reflect values that correspond to values for MACRo data. In aninstrument that has dedicated memory for MACRo data types, values reported shall bedifferent from the total given by a CATalog of ALL types.

13.1.5 :STATe?MEMory:CATalog:STATe?

If the CATalog query is qualified by the STATe node then the query shall return thedirectory list related only to STATe items in instrument memory. The memory usage andavailability parameters shall reflect values that correspond to values for STATe data. In aninstrument that has dedicated memory for STATe data types, values reported shall bedifferent from the total given by a CATalog of ALL types.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.1.6 :TABLe?MEMory:CATalog:TABLe?

HP058A

If the CATalog query is qualified by the TABLe node then the query shall return thedirectory list related only to TABLe items in instrument memory. The memory usage andavailability of parameters shall reflect values that correspond to values for TABLe data. Inan instrument that has dedicated memory for TABLe data types, the values reported shall bedifferent from the total given by a CATalog of ALL types.

HP058A

13.2 :CLEar PH076MEMory:CLEar

The commands from this subsystem remove the data that is stored in instrument memory.This subsystem differs from the DELete subsystem in that CLEar removes the data contentsbut does not affect the memory definitions such as memory type and structure, availablespace, and the name of the associated instrument memory.

13.2.1 [:NAME] <name> PH076MEMory:CLEar:NAME

This command is a default node and removes all data from the instrument memoryassociated with <name>. The NAMe command does not affect the related memorydefinitions.

This command is an event with no associated query form and *RST condition.

13.2.2 :TABLe PH076MEMory:CLEar:TABLe

The CLEar:TABLe command removes the data values from all element lists in the SELectedTABLe. This command does not affect the space and structure of the table as specified withthe table’s DEFine command. Executing a POINts? query for any table element after theCLEar:TABLe command, would return 0.


13.3 :COPY PH076MEMory:COPY

The COPY subsystem copies the data from an existing instrument memory item into another,named memory item.

13.3.1 [:NAME] <name>,<name> PH076MEMory:COPY:NAME

This command is a default node that copies the data contents from the memory itemassociated with the <name> specified in the first parameter to a memory item associatedwith the <name> specified by the second parameter.

When the memory item to which data is copied is of a different type, or has an incompatiblestructure, an execution error - 294 (Incompatible type) is generated. When the specifieddestination name does not exist, the device may create a new memory item of the same typeand structure as the source. In that case, the destination name is to be associated with thenew created memory item.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




13.3.2 :TABLe <name> PH076MEMory:COPY:TABLe

The COPY:TABLe command copies the data values of all element lists from the SELectedTABLe to the memory table associated with the specified <name>.

When the memory item to which data is copied is of a different type, or has an incompatiblestructure, an execution error -294 (Incompatible type) is generated. When the TABLe namedoes not exist, the device may define a new memeory table with the same structure as theselected table. In that case, the specified TABLe name is associated with the new createdmemory table.


TK023B13.4 :DATA<name>,<data>MEMory:DATA

TK023BThe command form is MEMory:DATA <name>,<data>. The command loads <data> intothe memory location <name>. <data> is in 488.2 block format. <name> is character data.

TK023BThe query form is MEMory:DATA? <name> with the response being the associated <data>in block format.

TK023BMEMory:DATA? response is not affected by the FORMat subsystem.

13.5 :DELeteMEMory:DELete

The DELete command purges the specified definition from instrument memory and makes itavailable for reuse.

13.5.1 :ALLMEMory:DELete:ALL

The ALL command removes all memory names, key definitions, and data, and it returnsmemory to “available.”

13.5.2 [:NAME] <name>MEMory:DELete:NAME

The NAME command is an optional node and deletes the definition associated with <name>.

13.6 :EXCHange PH076MEMory:EXCHange

The EXCHange subsystem allows for swapping the data contents between two memoryitems.

13.6.1 [:NAME] <name>,<name> PH076MEMory:EXCHange:NAME

This command is a default node which swaps the data contents between the memory itemsassociated with the <name> parameters.

When the memory items between which the data is swapped are of different type, or have anincompatible structure, an execution error -294 (Incompatible type) is generated.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




13.6.2 :TABLe <name> PH076MEMory:EXCHange:TABLe

This command swaps the data contents between the SELected TABLe and the memory tablethat is associated with the <name> parameter.

When the memory item associated with the specified <name> parameter is not a TABLe, orthe tables between which the data is swapped have an incompatible structure, an executionerror -294 (Incompatible type) is generated.


13.7 :FREEMEMory:FREE

Returns information on the user memory space as follows:<bytes available>,<bytes in use>

where the returned data for both shall be in <NR1> format.

The qualified FREE query for TRACe only memory usage is specified in the TRACesubsystem.

13.7.1 [:ALL]?MEMory:FREE:ALL?

If the FREE query is qualified by the optional ALL node then the query shall return memorysizes related to all items in instrument memory.

13.7.2 :ASCii?MEMory:FREE:ASCii?

If the FREE query is qualified by the ASCii node then the memory usage and availabilityshall reflect the values that correspond to values for ASCii data. In an instrument that hasdedicated memory for ASCii data types, these values reported shall be different from thetotal given by a FREE query of ALL types.

13.7.3 :BINary?MEMory:FREE:BINary?

If the FREE query is qualified by the BINary node then the memory usage and availabilityshall reflect the values that correspond to values for BINary data. In an instrument that hasdedicated memory for BINary data types, these values reported shall be different from thetotal given by a FREE query of ALL types.

13.7.4 :MACRo?MEMory:FREE:MACRo?

If the FREE query is qualified by the MACRo node then the memory usage and availabilityshall reflect the values that correspond to values for MACRo data. In an instrument that hasdedicated memory for MACRo data types, these values reported shall be different from thetotal given by a FREE query of ALL types.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.7.5 :STATe?MEMory:FREE:STATe?

If the FREE query is qualified by the STATe node then the memory usage and availabilityshall reflect the values that correspond to values for STATe data. In an instrument that hasdedicated memory for STATe data types, these values reported shall be different from thetotal given by a FREE query of ALL types.

13.7.6 :TABLe?MEMory:FREE:TABLe?

HP058A

If the FREE query is qualified by the TABLe node then the memory usage and availabilityshall reflect the values that correspond to values for TABLe data. In an instrument that hasdedicated memory for TABLe types, the values reported shall be different from the totalgiven by a FREE query of ALL types.

HP058A

13.8 :NSTates?MEMory:NSTates?

The Number of STates query requests that the instrument return the number of *SAV/*RCLstates available in the instrument. The instrument shall return a <NR1> value which is onegreater than the maximum that can be sent as a parameter to the *SAV and *RCL commands.

TK023B13.9 :STATe MEMory:STATe

TK023BCollects commands relating to memory STATe data.

TK023B13.9.1 :CATalog? MEMory:STATe:CATalog?

TK023BThis query requests a list of defined names in the MEMory:STATe subsystem. Theinstrument returns a list of defined <name>’s in a comma separated list. Each <name> isreturned in a quoted string. If no names are defined, a single null string is returned. There isno command form.

TK023B13.9.2 :DEFine <name> , <register_number>MEMory:STATe:DEFine

TK023B:DEfine associates a <name> with a *SAV/*RCL register number where <name> is incharacter data format. <register_number> is in <NRf> format.

TK023BThe query form of this command, MEMory:STATe:DEFine? <name> returns the associated<register_number> in <NR1> format.

TK023B*RST has no effect on this command.

13.10 :TYPE? <name>MEMory:TYPE?

The TYPE query requests information about a defined name. The instrument must return astring indicating the subsystem where the name was defined. If the name is not defined, anull string is returned. For example, if VAT3 was previously defined by:

ROUTe:MODule:DEFine VAT3,(@20000(0:9))

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



then the query:MEMory:TYPE? VAT3

requests a return of“ROUT:MOD:”

13.11 :TABLeMEMory:TABLe

HP058A

The MEMory:TABLe command allows the user to DEFine a TABLe and to write data toand read data from it.

13.11.1 :BNUMber <numeric_value> {,<numeric_value>}:MEMory:TABLe:BNUMber

BNUMber is the gas bottle number. This command sets the gas bottle number, which is apositive integer.

NOTE: For Emissions benches, BNUMber<n> are bottle ID number columns in theGasBottle, ZeroGas, SpanGas, Verify, and TopGas tables. In the ZeroGas, SpanGas, Verify,and TopGas tables, there are columns BNUMber<n>, where n corresponds to the analyzerrange number. In GasBottle, there is a single BNUMber column.

13.11.1.1 :POINts?:MEMory:TABLe:BNUMber:POINts?

This command returns the number of points in column BNUMber, for the currently selectedtable.

13.11.2 :CCURve <numeric_value> {,<numeric_value>}:MEMory:TABLe:CCURve

CCURve sets the value of concentration in ppm using the current curve in linearizationtables. This command sets the values of CCURve.

13.11.2.1 :POINts?:MEMory:TABLe:CCURve:POINts?

This command returns the number of points in column CCURve, for the currently selectedtable.

13.11.3 :CONCentration <numeric_value> {,<numeric_value>}:MEMory:TABLe:CONCentration

CONCentration is the gas concentration in ppm. This command sets the values ofCONCentration.

13.11.3.1 :POINts?:MEMory:TABLe:CONCentration:POINts?

This command returns the number of points in column CONCentration, for the currentlyselected table.

13.11.4 :CONDition PH074MEMory:TABLe:CONDition

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.4.1 [:MAGNitude] <Boolean>{,<Boolean>} PH074MEMory:TABLe:CONDition:MAGNitude

Specifies the CONDition[:MAGNitude] points of the TABLe. If there are more <Boolean>’sthan in the associated DEFine statement, execution error -223 (Too much data) will begenerated. This item list is included in the table DEFine command asCONDition[:MAGNitude]

At *RST, the contents of this list is device dependent.

13.11.4.1.1 :POINts?MEMory:TABLe:CONDition:MAGNituse:POINts?

Returns the number of points in the CONDition[:MAGNitude] list of the SELected TABLe.If no CONDition[:MAGNitude] value have been sent, POINts? returns a 0. If no TABLe hasbeen selected, POINts? returns a NAN.

13.11.5 :CPOint <numeric_value> {,<numeric_value>}:MEMory:TABLe:CPOint

CPOint is the linearization gas dilution percentage or “cut point”. This command sets thevalues of CPOint.

13.11.5.1 :POINts? :MEMory:TABLe:CPOint:POINts?

This command returns the number of points in column CPOint, for the currently selectedtable.

13.11.6 :CURRentMEMory:TABLe:CURRent

HP058A

13.11.6.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:CURRent:MAGNitude

HP058A

Specifies the CURRent[:MAGNitude] points of the TABLe. <numeric_value>’s mayinclude current units as listed in the UNIT subsystem. The default unit is specified byUNIT:CURRent. If there are more <numeric_value>’s than in the associated DEFinestatement, execution error -223 (Too much data) will be generated. This item list is includedin the table DEFine command as CURRent[:MAGNitude].

At *RST, the contents of this list item is device dependent.

13.11.6.1.1 :POINts?MEMory:TABLe:CURRent:MAGNitude:POINts?

HP058A

Returns the number of points in the CURRent[:MAGNitude] list of the SELected TABLe. Ifno CURRent[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.6.2 :PHASe <numeric_value>{,<numeric_value>}MEMory:TABLe:CURRent:PHASe

HP058A

Specifies the CURRent:PHASe points of the TABLe. <numeric_value>’s may include angleunits as listed in the UNIT subsystem. The default unit is specified by UNIT:ANGLe. Ifthere are more <numeric_value>’s than in the associated DEFine statement, execution error

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-223 (Too much data) will be generated. This item list is included in the table DEFinecommand as CURRent:PHASe.


13.11.6.2.1 :POINts?MEMory:TABLe:CURRent:PHASe:POINts?

HP058A

Returns the number of points in the CURRent:PHASe list of the SELected TABLe. If noCURRent:PHASE values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.7 :DFACtory <numeric_value> {,<numeric_value>}:MEMory:TABLe:DFACtory

DFACtory is the maximum allowable drift from factory settings.

For emissions benches, this is the zero or span factory setting in the tables ZDRift andSDRift respectively. This command sets the values of DFACtory. Drift from factory settingis calculated as follows:

Zero DriftZDf =

(Z∗− Zf)fs

∗ 100

Span DriftSDf =

(S∗− Sf)fs

∗ 100

where Z* and S* are the currently read zero and span values in ppmZf and Sf are the factory settings stored in DFACtory in ppmfs is the full scale CONCentration in ppmZDf is the zero drift in PCTSDf is the span drift in PCT

Note: a ratio of 1.0 = 100 PCT

13.11.7.1 :POINts?:MEMory:TABLe:DFACtory:POINts?

This command returns the number of points in column DFACtory, for the currently selectedtable.

13.11.8 :DLASt <numeric_value> {,<numeric_value>}:MEMory:TABLe:DLASt

DLASt is the maximum allowable drift from the most recently saved zero and set point.

For emissions benches, this is the most recently saved zero or span setting in the tablesZDRift and SDRift respectively. This command sets the values of DLASt. Drift from mostrecently saved zero or span (SPOint) setting is calculated as follows:

Zero DriftZD0 =

(Z∗− Z0)fs

∗ 100

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Span DriftSD0 =

(S∗− S0)fs

∗ 100

where Z* and S* are the currently read zero and span values in ppmZ0 and S0 are the most recently saved settings stored in DLAST in ppmfs is the full scale CONCentration in ppmZD0 is the zero drift in PCTSD0 is the span drift in PCT


13.11.8.1 :POINts?:MEMory:TABLe:DLASt:POINts?

This command returns the number of points, for the currently selected table.

13.11.9 :DLINearize <numeric_value> {,<numeric_value>}:MEMory:TABLe:DLINearize

DLINearize is the maximum allowable drift from the most recent linearization.

For emissions benches, this is the zero or span setting saved at the time of the most recentlinearization in the tables ZDRift and SDRift respectively. This command sets the values ofDLINearization. Drift from most recent linearization is calculated as follows:

Zero DriftZDl =

(Z∗− Zl)fs

∗ 100

Span DriftSDl =

(S∗− Sl)fs

∗ 100

where Z* and S* are the currently read zero and span values in ppmZl and Sl are the settings from the most recent linearization stored in DLINearizein ppmfs is the full scale CONCentration in ppmZDl is the zero drift in PCTSDl is the span drift in PCT


13.11.9.1 :POINts?:MEMory:TABLe:DLINearize:POINts?

This command returns the number of points in column DLINearize, for the currently selectedtable.

13.11.10 :EXPected <numeric_value> {,<numeric_value>}:MEMory:TABLe:EXPected

EXPected is the expected value.

For emissions benches, EXPected is the expected gas concentration in ppm. This commandsets the values of EXPected.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.10.1 :POINts?:MEMory:TABLe:EXPected:POINts?

This command returns the number of points in column EXPected , for the currently selectedtable.

13.11.11 :DEFine <structure_string>[,<numeric_value>]MEMory:TABLe:DEFine

HP058A

The DEFine subsystem is used to allocate space and define the structure of TABLe in theinstrument memory. The <name> of the TABLe is specified by SELect.

The string parameter <structure_string> specifies the structure of the TABLe being defined,it contains a comma separated list of the elements. Any item lists under MEMory:TABLe,such as FREQuency or VOLTage:PHASe, may be specified as elements in the tablestructure. The item lists maybe specified in long or short form, optional nodes if sent shall beaccepted without error. The item lists available and the legal combinations of these item listsare device dependent. All lists are empty (0 length) when DEFined.

The second parameter, is the size of the TABLe. This is the maximum number of POINts ineach of the lists. Computations based on device dependent internal data formats will be madeto determine the number of bytes. For example, if the TABLe will have two lists and theinternal storage requires 8 bytes for a number, then an entry of 10 will allocate 160 bytes. Ifthere is insufficient room, execution error -225 (Out of memory) will be generated. The sizeof the table parameter is optional. The algorithm to allocate memory is device dependentwhen this parameter is omitted.

The DEFine query returns both the <structure_string> and a numeric value for the size (inpoints) of memory allocated for the table. The elements of the structure string are returned inthe short form, with any optional nodes omitted.

13.11.12 :FORCeMEMory:TABLe:FORCe

Specifies the FORCe points of the TABLe.

13.11.12.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:FORCe:MAGNitude

Specifies the FORCe[:MAGNitude] points of the TABLe. The default units of this commandare newtons.


13.11.12.1.1 :POINts?MEMory:TABLe:FORCe:MAGNitude:POINts?

Returns the number of points in the FORCe[:MAGNitude] list of the selected TABLe. If noFORCe[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.13 :FREQuency <numeric_value>{,<numeric_value>}MEMory:TABLe:FREQuency

HP058A

Specifies the FREQuency points of the TABLe. If there are more <numeric_value>’s than inthe associated DEFine statement, execution error -223 (Too much data) will be generated.This item list is included in the table DEFine command as FREQuency.


13.11.13.1 :POINts?MEMory:TABLe:FREQuency:POINts?

HP058A

Returns the number of points in the FREQuency list of the SELected TABLe. If noFREQuency values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.14 :LABel <string> {,<string>}:MEMory:TABLe:LABel

LABel is the label name in a table in character string format. This command sets the valuesof LABel.

For emissions benches, LABel is the label name in the GasBottle table.

13.11.14.1 :POINts?:MEMory:TABLe:LABel:POINts?

This command returns the number of points in column LABel, for the currently selectedtable.

13.11.15 :LLIMit <numeric_value> {,<numeric_value>}:MEMory:TABLe:LLIMit

LLIMit is the lower limit value. This command sets the values of LLIMit. If there are more<numeric_value>’s than in the associated DEFine statement, execution error -223 (Toomuch data) will be generated. This item list is included in the table DEFine command asLLIMit.


13.11.15.1 :POINts?:MEMory:TABLe:LLIMit:POINts?

This command returns the number of points in column LLIMit, for the currently selectedtable. If no LLIMit values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.16 :LOG <string> {,<string>}:MEMory:TABLe:LOG

LOG is a series of string data elements.

For emissions benches, LOG is a collection of audit-related strings. This command sets thevalues of LOG.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.16.1 :POINts?:MEMory:TABLe:LOG:POINts?

This command returns the number of points in column LOG, for the currently selected table.

13.11.17 :LOSSMEMory:TABLe:LOSS

HP058A

13.11.17.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:LOSS:MAGNitude

HP058A

Specifies the LOSS[:MAGNitude] points of the TABLe. The default unit is DB. If there aremore <numeric_value>’s than in the associated DEFine statement, execution error -223 (Toomuch data) will be generated. This item list is included in the table DEFine command asLOSS[:MAGNitude].


13.11.17.1.1 :POINts?MEMory:TABLe:LOSS:MAGNitude:POINts?

HP058A

Returns the number of points in the LOSS[:MAGNitude] list of the SELected TABLe. If noLOSS[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.17.2 :PHASe <numeric_value>{,<numeric_value>}MEMory:TABLe:LOSS:PHASe

HP058A

Specifies the LOSS:PHASe points of the TABLe. <numeric_value>’s may include angleunits as listed in the UNIT subsystem. The default unit is specified by UNIT:ANGLe. Ifthere are more <numeric_value>’s than in the associated DEFine statement, execution error-223 (Too much data) will be generated. This item list is included in the table DEFinecommand as LOSS:PHASe.


13.11.17.2.1 :POINts?MEMory:TABLe:LOSS:PHASe:POINts?

HP058A

Returns the number of points in the LOSS:PHASe list of the SELected TABLe. If noLOSS:PHASE values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.18 :NCURve <numeric_value> {,<numeric_value>}:MEMory:TABLe:NCURve

NCURve sets the value of concentration in ppm using the newly calculated curve (NewCURve) in linearization tables. This command sets the values of NCURve.

13.11.18.1 :POINts?:MEMory:TABLe:NCURve:POINts?

This command returns the number of points in column NCURve, for the currently selectedtable.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.19 :POWerMEMory:TABLe:POWer

HP058A

13.11.19.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:POWer:MAGNitude

HP058A

Specifies the POWer[:MAGNitude] points of the TABLe. <numeric_value>’s may includePOWer units as listed in the UNIT subsystem. The default unit is specified by UNIT:POWer.If there are more <numeric_value>’s than in the associated DEFine statement, executionerror -223 (Too much data) will be generated. This item list is included in the table DEFinecommand as POWer[:MAGNitude].


13.11.19.1.1 :POINts?MEMory:TABLe:POWer:MAGNitude:POINts?

HP058A

Returns the number of points in the POWer[:MAGNitude] list of the SELected TABLe. If noPOWer[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.20 :RAW <numeric_value> {,<numeric_value>}:MEMory:TABLe:RAW

RAW is a collection of points in instrument internal units.

For emissions benches, it is the raw gas concentration in bench internal units from alinearization. This command sets the values of RAW.

13.11.20.1 :POINts?:MEMory:TABLe:RAW:POINts?

This command returns the number of points in column RAW, for the currently selected table.

13.11.21 :RESistanceMEMory:TABLe:RESistance

HP058A

13.11.21.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:RESistance:MAGNitude

HP058A

Specifies the RESistance[:MAGNitude] points of the TABLe. If there are more<numeric_value>’s than in the associated DEFine statement, execution error -223 (Toomuch data) will be generated. This item list is included in the table DEFine command asRESistance[:MAGNitude].


13.11.21.1.1 :POINts?MEMory:TABLe:RESistance:MAGNitude:POINts?

HP058A

Returns the number of points in the RESistance[:MAGNitude] list of the SELected TABLe.If no RESistance[:MAGNitude] values have been sent POINts? returns 0. If no TABLe hasbeen selected, POINts? returns NAN.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



13.11.22 :SELect <name>MEMory:TABLe:SELect

HP058A

Sets or queries the name of the TABLe selected. If the TABLe <name> already exists, thenthe existing TABLe shall be selected. If the TABLe <name> does not exist, then the newname shall be selected, but no TABLe shall be defined by this selection. The TABLe<name> is character data.

At *RST the <name> select shall be device dependent.

13.11.23 :SPEedMEMory:TABLe:SPEed

Specifies the SPEed points of the TABLe.

13.11.23.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:SPEed:MAGNitude

Specifies the SPEed[:MAGNitude] points of the TABLe. The default units of this commandare meters per second.


13.11.23.1.1 :POINts?MEMory:TABLe:SPEed:MAGNitude:POINts?

Returns the number of points in the SPEed[:MAGNitude] list of the selected TABLe. If noSPEed[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.24 :TIMEMEMory:TABLe:TIME

Specifies the TIME points of the TABLe.

13.11.24.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:TIME:MAGNitude

Specifies the TIME[:MAGNitude] points of the TABLe. The default units of this commandare seconds.


13.11.24.1.1 :POINts?MEMory:TABLe:TIME:MAGNitude:POINts?

Returns the number of points in the TIME[:MAGNitude] list of the selected TABLe. If noTIME[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.25 :TOLerance <numeric_value> {,<numeric_value>}:MEMory:TABLe:TOLerance

TOLerance is a series of tolerance values.

For emissions benches, it is the allowable deviation in gas concentration in percentage of fullscale (%FS) between expected and current (or new curve) values stored from a linearization.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The bench will set an error bit in the status register if the difference between expected andactual values exceed the tolerance. This command sets the values of TOLerance.

13.11.25.1 :POINts?:MEMory:TABLe:TOLerance:POINts?

This command returns the number of points in column TOLerance, for the currently selectedtable.

13.11.26 :ULIMit <numeric_value> {,<numeric_value>} :MEMory:TABLe:ULIMit

ULIMit is the upper limit value. This command sets the values of ULIMit. If there are more<numeric_value>’s than in the associated DEFine statement, execution error -223 (Toomuch data) will be generated. This item list is included in the table DEFine command asULIMit.


13.11.26.1 :POINts? :MEMory:TABLe:ULIMit:POINts?

This command returns the number of points in column ULIMit, for the currently selectedtable. If no ULIMit values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.27 :VOLTageMEMory:TABLe:VOLTage

HP058A

13.11.27.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:VOLTage:MAGNitude

HP058A

Specifies the VOLTage[:MAGNitude] points of the TABLe. <numeric_value>’s mayinclude voltage units as listed in the UNIT subsystem. The default unit is specified byUNIT:VOLTage. If there are more <numeric_value>’s than in the associated DEFinestatement, execution error -223 (Too much data) will be generated. This item list is includedin the table DEFine command as VOLTage[:MAGNitude].


13.11.27.1.1 :POINts?MEMory:TABLe:VOLTage:MAGNitude:POINts?

HP058A

Returns the number of points in the VOLTage[:MAGNitude] list of the SELected TABLe. Ifno VOLTage[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

13.11.27.2 :PHASe <numeric_value>{,<numeric_value>}MEMory:TABLe:VOLTage:PHASe

HP058A

Specifies the VOLTage:PHASe points of the TABLe. <numeric_value>’s may include angleunits as listed in the UNIT subsystem. The default unit is specified by UNIT:ANGLe. Ifthere are more <numeric_value>’s than in the associated DEFine statement, execution error-223 (Too much data) will be generated. This item list is included in the table DEFinecommand as VOLTage:PHASe.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




13.11.27.2.1 :POINts?MEMory:TABLe:VOLTage:PHASe:POINts?

HP058A

Returns the number of points in the VOLTage:PHASe list of the SELected TABLe. If noVOLTage:PHASE values have been sent POINts? returns 0. If no TABLe has been selected,POINts? returns NAN.

13.11.28 :WFACtor <numeric_value> {,<numeric_value>}:MEMory:TABLe:WFACtor

Values in column WFACtor are weighting factors.

For emissions benches, a value in the WFACtor column is assigned to each cut point in alinearization. If weighting is not desired, all values are set to the same non-zero number.WFACtor is a column in linearization tables. This command sets the values of WFACtor.

13.11.28.1 :POINts?:MEMory:TABLe:WFACtor:POINts?

This command returns the number of points in column WFACtor, for the currently selectedtable.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



14 MMEMory SubsystemThe Mass MEMory subsystem provides mass storage capabilities for instruments. All massmemory device commands are contained in the MMEMory subsystem. The mass storagemay be either internal or external to the instrument. If the mass memory device is external,then the instrument must have controller capability on the mass memory device bus.

The CLOSe, FEED, NAME, and OPEN commands permit the streaming of data fromanywhere in the data flow into a file; this is particularly useful for saving HCOPy output.

HP063eMass storage media may be formatted in any one of a number of standard formats.

Selecting Mass Memory DevicesWhen an instrument has multiple attached mass storage devices, the desired mass storageunit is selected with the mass storage unit specifier <msus>. The syntax of the <msus> stringis instrument specific. Each instrument’s documentation shall describe the syntax applicableto that instrument. For example:

“C:” “:700,2” “fileserv”

Note that some file systems do not make use of the <msus> concept.

File NamesThe <file_name> parameter described in the commands in this subsystem is a string. Thecontents of the string are dependent on the needs of the format of the mass storage media. Inparticular, the file name may contain characters for specifying subdirectories (that is, \ forDOS, / for HFS) and the separator for extensions in DOS (that is, period).

The following commands are provided for mass memory device operations.

KEYWORD PARAMETER FORM NOTESMMEMory HP037

:CATalog? [<msus>] [query only] :CDIRectory [<directory_name>] :CLOSe [event; no query] 1993 HP063e :COPY <file_name>,<file_name> |<file_name>,<msus>, <file_name>,<msus>

TK054 :DATA <file_name>, <data> 1995 :DELete <file_name>[,<msus>] [no query] :FEED <data_handle> 1993 HP063e :INITialize [<msus>[,(LIF|DOS|HFS)

[,<numeric_value>]]] [no query] :LOAD :DINTerchange <label>,<file_name>[,<msus>] [no query] :TRACe <label>,<file_name>[,<msus>] [no query] 1992 HP066

:MACRo <label>,<file_name>[,<msus>] [no query] :STATe <numeric_value>,<file_name>[,<msus>] [no query]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


MMEMory 14-1

HP087KEYWORD PARAMETER FORM NOTES :TABLe <label>,<file_name>[,<msus>] [no query] 1994 :TRACe <label>,<file_name>[,<msus>] [no query] :MSIS [<msus>] :MOVE (<src_file>,<dest_file>) [no query] 1991 |(<src_file>,<src_msus>,<dest_file>,<dest_msus>) 1991 HP048

:NAME <file_name>[,<msus>] 1993 HP063e :OPEN [event; no query] 1993 HP063e :PACK <msus> [no query] 1991 HP037

:STORe :DINTerchange <label>,<file_name>[,<msus>] [no query] :TRACe <label>,<file_name>[,<msus>] [no query] 1992 HP066

:MACRo <label>,<file_name>[,<msus>] [no query] :STATe <numeric_value>,<file_name>[,<msus>] [no query]

HP087 :TABLe <label>,<file_name>[,<msus>] [no query] 1994 :TRACe <label>,<file_name>[,<msus>] [no query]

14.1 :CATalog? [<msus>]MMEMory:CATalog?

The CATalog command is query-only and returns information on the current contents andstate of the mass storage media. Upon a CATalog? query, the instrument shall read thespecified mass memory device and returns its directory information in the following format:

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

The instrument shall return two numeric parameters and as many strings as there are files inthe directory list. The first parameter shall indicate the total amount of storage currently usedin bytes. The second parameter shall indicate the total amount of storage available, also inbytes. The <file_entry> is a string. Each <file_entry> shall indicate the name, type, and sizeof one file in the directory list:

<file_name>,<file_type>,<file_size>

Note that this syntax places some restrictions on the <file_name> (for example, commas arenot allowed.) The <file_name> is the exact name of a file as it appears in the directory list,including an extension if present. The <file_size> provides the size of the file in bytes. The<file_type> is indicated by one of the following:

ASCii — An ASCii text file

BINary — A binary file

STATe — Instrument (setting) state

TRACe — Trace (display) data

MACRo — An instrument macro

For media which cannot determine the file type from the directory information (i.e. DOS,HFS) this field shall be left blank.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


14-2 MMEMory

14.2 :CDIRectory [<directory_name>]MMEMory:CDIRectory

TK044Changes the default directory for a mass memory file system. The <directory_name>parameter is a string. The contents of the <directory_name> parameter are dependent on thefile system being accessed. If no parameter is specified, the directory is set to the *RSTvalue.

TK044At *RST, this value is set to the root for DOS file systems and to a device-dependent valuefor other file systems such as HFS.

14.3 :CLOSe HP063eMMEMory:CLOSe

The CLOSe event causes the selected file specified in NAME to be closed. An attempt toCLOSe a file that was not open shall cause an error -256, (File name not found) to begenerated.

14.4 :COPY <file_source>,<file_destination>MMEMory:COPY

The COPY command copies an existing file to a new file.

Two forms of parameters are allowed. The first form has two parameters. In this form, thefirst parameter specifies the source file, and the second parameter specifies the destinationfile.

The second form has four parameters. In this form, the first and third parameter specify thefile_names. The second and fourth parameters specify the <msus>. The first pair ofparameters specifies the source file. The second pair specifies the destination file. An error isgenerated if the source file doesn’t exist. An error may be generated if the destination filealready exists.

This command defines an event and thus has no *RST state or query form.

TK05414.5 :DATA <file_name>, <data>MMEMory:DATA

The command form is MMEMory:DATA <file_name>,<data>. The command loads <data>into the file <file_name>. <data> is in 488.2 block format. <file_name> is string data.

The query form is MMEMory:DATA? <file_name> with the response being the associated<data> in block format.

MMEMory:DATA? response is not affected by the FORMat subsystem.

14.6 :DELete <file_name>[,<msus>]MMEMory:DELete

The DELete command removes a file from the specified mass storage device. The<file_name> parameter specifies the file_name to be removed.

This command defines an event, and it has no *RST condition or query form.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


MMEMory 14-3

14.7 :FEED <data_handle> HP063eMMEMory:FEED

Sets or queries the <data_handle> to be used to feed data into the file specified by NAME.New data arriving from <data_handle> always overwrites the contents of the file specifiedby NAME. If the <data_handle> generates new data and the file is not OPEN an error -256,(File name not found) shall be generated.

At *RST, the value of FEED is device dependent.

14.8 :INITialize [<msus>[,(LIF|DOS|HFS)[,<numeric_value>]]]MMEMory:INITialize

The INITialize command is used to initialize the specified mass storage media. If the<msus> is not specified, the default is used. The default is the <msus> selected at *RST, notthe currently selected <msus>. The second parameter specifies the type of media to beformatted. The <numeric_value> parameter is used to specify the format, interleave, sectorsizes, and other media-dependent information. Execution of the command attempts toinitialize the media. Previous data on the media, if any, is destroyed.

This command is an event and does not have a query form or a *RST condition.

14.9 :LOAD and :STOReMMEMory:LOAD and :STORe

The LOAD and STORe subsystems transfer information between the mass memory deviceand the instrument’s memory. The LOAD commands transfer from mass memory device tointernal memory, and STORe transfers from internal memory to the mass memory device.

When information is loaded, the instrument uses the file type information to determinewhether the data is in internal (BINary) or transportable (ASCii) form.

The <file_name> parameter is a quoted string and the <label> refers to an internal identifierfor the instrument trace or macro.

The LOAD and STORe commands do not have query forms.

14.9.1 :DINTerchange <label>,<file_name>[,<msus>]MMEMory:LOAD:DINTerchange

Specifies that the device transfer DINTerchange formatted data.

14.9.1.1 :TRACe <label>,<file_name>[,<msus>]MMEMory:LOAD:DINTerchange:TRACe

The specified trace or array is loaded from or stored to the mass memory device inDINTerchange format.

14.9.2 :MACRo <label>,<file_name>[,<msus>]MMEMory:LOAD:MACRo

The specified macro is loaded from or stored to the mass memory device.

14.9.3 :STATe <numeric_value>,<file_name>[,<msus>]MMEMory:LOAD:STATe

The specified instrument state is stored or loaded. The <numeric_value> parameter refers tothe state number, which corresponds to the numbers found in *SAV and *RCL.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


14-4 MMEMory

HP071

HP08714.9.4 :TABLe <label>,<file_name>[,<msus>]

MMEMory:LOAD:TABLe

The MEMory:TABLe specified by <label> is loaded from or stored to the mass memorydevice.

14.9.5 :TRACe <label>,<file_name>[,<msus>]MMEMory:LOAD:TRACe

The specified trace or array is loaded from or stored to the mass memory device.

14.10 :MSIS [<msus>]MMEMory:MSIS

The “Mass Storage IS” command selects a default mass storage device which is used by allMMEMory commands except INITialize. If the parameter is omitted, the device-dependentsetting for default mass storage device is selected.

HP066

At *RST, the value of this parameter is device-dependent.

14.11 :MOVE (<src_file>,<dest_file>) |(<src_file>,<src_msus>,<dest_file>,<dest_msus>)MMEMory:MOVE

HP048

The MOVE command moves an existing file to another file name.

Two forms of the parameter are allowed. The first form has two parameters. In this form thefirst parameter, <src_file>, specifies the file to be renamed, and the second parameter,<dest_file>, specifies the new name of the file.

The move operation is performed on the default mass storage device.

The second form has four parameters. The first two parameters, <src_file> and <src_msus>,specify the file name and storage device of the source file and the second two parameters,<dest_file> and <dest_msus>, specify the new file name and new storage device for thesource file.

Some instruments may not support the moving of a file across mass storage devices and thusshall generate error -250, “Mass Storage Error”, when the msus parameters are not the same.

If the <src_file> does not exist, the instrument shall generate error -256, “File name notfound”. If the <dest_file> already exists, the instrument shall generate error -257, “File nameerror”.

This command is an event-only command and thus has no *RST value, and no query form.

14.12 :NAME <file_name>[,<msus>] HP063eMMEMory:NAME

Sets or queries the name of the file specification used by the CLOSe and OPEN commands.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


MMEMory 14-5

14.13 :OPEN HP063eMMEMory:OPEN

The OPEN event causes the selected file specified in NAME to be opened. An attempt toOPEN a file that is already opened shall cause an error -257, (File name error) to begenerated. If the selected file is non-existent, it is created.

14.14 :PACK [<msus>]MMEMory:PACK

HP037

This command causes the mass storage device to be packed, such that unused memorybetween files is recovered and packed together. If an instrument, which supports file packing(ie: implements the MMEM:PACK command), receives the MMEM:PACK command butthe current disk format does not support file packing, the instrument shall generate an error-250 (Mass Storage Error). If the <msus> is not specified the default is used.

This command defines an event and thus has no *RST state or query form.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


14-6 MMEMory

15 OUTPut SubsystemThe OUTPut subsystem controls the characteristics of the source’s output port.

A source which is sourcing impedance (programmable load) is allowed to alias thissubsystem as INPut, providing that the OUTPut keyword is also recognized and the INPutsubsystem is not used for its intended purpose within the instrument.

KEYWORD PARAMETER FORM NOTESOUTPut|INPut See text :ATTenuation <numeric_value> :COUPling AC|DC :FILTer :AUTO <Boolean> | ONCE 1992 RS003

:EXTernal 1992 RS002

[:STATe] <Boolean> 1992 RS002

:HPASs :FREQuency <numeric_value> 1991 HP008

[:STATe] <Boolean> :TYPE BESSel | CHEByshev 1992 RS003

[:LPASs] :FREQuency <numeric_value> 1991 HP008

[:STATe] <Boolean> :TYPE BESSel | CHEByshev 1992 RS003

:IMPedance <numeric_value> :LOW FLOat|GROund 1991 HP008

:POLarity NORMal | INVerted 1992 HP057

RS010a :POLarization <numeric_value> 1994RS010a :HORizontal [no query] 1994RS010a :VERTical [no query] 1994RS010a :POSition 1994RS010a [:X] 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


OUTPut Subsystem 15-1

KEYWORD PARAMETER FORM NOTESRS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a :Y 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a :Z 1994RS010a :ANGLe 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994RS010a [:DISTance] 1994RS010a :DIRection UP|DOWN 1994RS010a [:IMMediate] <numeric_value> 1994RS010a :LIMit 1994RS010a :HIGH <numeric_value> 1994RS010a :LOW <numeric_value> 1994RS010a [:STATe] <Boolean> 1994RS010a :OFFSet <numeric_value> 1994RS010a :VELocity <numeric_value> 1994

:PROTection :DELay <numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


15-2 OUTPut Subsystem

KEYWORD PARAMETER FORM NOTES [:STATe] <Boolean> :TRIPped? [query only] :CLEar [no query] :ROSCillator 1991 HP044


:TTLTrg<n> |:ECLTrg<n> 1991 HP023

:IMMediate 1991 HP023

:LEVel <Boolean> 1991 HP023

TK030 :POLarity NORMal|INVerted 1994 :PROTocol SYNChronous|SSYNchronous|ASYNchronous 1991 PH017

:WIDTh <numeric_value> 1991 PH017

[:STATe] <Boolean> :SOURce <character data> [:STATe] <Boolean> :TYPE <character data> 1992 RS007

15.1 :ATTenuation <numeric_value>OUTPut:ATTenuation

Sets the output ATTenuation level. The default units are in the current relative amplitudeunits.

This should only be used where the setting is not reflected within the SOURce subsystem.For example, setting the output attenuation to 10 dB will cause the generated signal todecrease in amplitude by 10 dB. However, the power level setting will be unaffected bychanging the output attenuation.


15.2 :COUPling AC|DCOUTPut:COUPling

Controls whether the signal is AC or DC coupled to the output port.


15.3 :FILTerOUTPut:FILTer

The FILTer function allows filters to be inserted in the path of the signal.

15.3.1 :AUTO <Boolean> | ONCEOUTPut:FILTer:AUTO

RS003

Allows the system to determine the best filter characteristic and cutoff frequency. Explicitlyselecting any output filter or output filter characteristic shall set AUTO OFF.


15.3.2 :EXTernalOUTPut:FILTer:EXTernal

Controls an external, user provided, filter.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



RS002

15.3.2.1 [:STATe] <Boolean>OUTPut:FILTer:EXTernal:STATe

Selects a user provided filter. When STATe is ON the filter is placed in the signal path.

At *RST, this value is OFF.RS002

15.3.3 :HPASsOUTPut:FILTer:HPASs


15.3.3.1 :FREQuency <numeric_value>OUTPut:FILTer:HPASs:FREQuency

HP008

Determines the cutoff frequency of the high pass filter.


15.3.3.2 [:STATe] <Boolean>OUTPut:FILTer:HPASs:STATe

Turns the high pass filter ON and OFF.


15.3.3.3 :TYPE BESSel | CHEByshevOUTPut:FILTer:HPASs:TYPE

RS003

Determines the characteristic of the high pass filter.


15.3.4 [:LPASs]OUTPut:FILTer:LPASs


15.3.4.1 :FREQuency <numeric_value>OUTPut:FILTer:LPASs:FREQuency

HP008

Determines the cutoff frequency of the low pass filter.


15.3.4.2 [:STATe] <Boolean>OUTPut:FILTer:LPASs:STATe

Turns the low pass filter ON and OFF.


15.3.4.3 :TYPE BESSel | CHEByshevOUTPut:FILTer:LPASs:TYPE

RS003

Determines the characteristic of the low pass filter.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.4 :IMPedance <numeric_value>OUTPut:IMPedance

OUTPut source impedance for the signal specified in Ohms.


15.5 :LOW FLOat|GROundOUTPut:LOW

HP008

Connects the low signal terminal to ground or allows it to float.

This parameter is set to a device-dependent value at *RST.

15.6 :POLarity NORMal | INVertedOUTPut:POLarity

HP057

Sets or queries the output polarity. NORMal causes the source block’s signal to appear at theoutput with the same polarity as it was generated. INVerted causes the polarity of the sourceblock’s signal to be reversed when it appears at the output terminals.

At *RST, this value is NORMal.

RS010a15.7 :POLarization <numeric_value>OUTPut:POLarization

Sets the polarization of the output. The default units are radian.


RS010a15.7.1 :HORizontal OUTPut:POLarization:HORizontal

Sets the polarization of the output to zero. This command is an event. Therefore it has noassociated query or meaning at *RST.

RS010a15.7.2 :VERTicalOUTPut:POLarization:VERTical

Sets the polarization of the output to PI/2 radians. This command is an event. Therefore ithas no associated query or meaning at *RST.

RS010a15.8 :POSitionOUTPut:POSition

The characteristics of an incoming signal can be affected by the output’s spatial position andorientation relative to the origin. The definition of the origin is application specific. Thissubsystem uses a righthand coordinate system and has only one origin.

In this subsystem only the IMMediate commands initiate movement.

In this subsystem velocity is always positive.

RS010a15.8.1 [:X]OUTPut:POSition:X

Controls the settings concerning the X-axis.

RS010a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.8.1.1 :ANGLeOUTPut:POSition:X:ANGLe

Specifies the angle of rotation around the X-axis.

RS010a15.8.1.1.1 :DIRection UP|DOWNOUTPut:POSition:X:ANGLe:DIRection



RS010a15.8.1.1.2 [:IMMediate] <numeric_value>OUTPut:POSition:X:ANGLe:IMMediate

This command indicates that the output is moved to the specified position without waitingfor further commands.


RS010a15.8.1.1.3 :LIMitOUTPut:POSition:X:ANGLe:LIMit


RS010a15.8.1.1.3.1 :HIGH <numeric_value>OUTPut:POSition:X:ANGLe:LIMit:HIGH



RS010a15.8.1.1.3.2 :LOW <numeric_value>OUTPut:POSition:X:ANGLe:LIMit:LOW



RS010a15.8.1.1.3.3 :STATe <Boolean>OUTPut:POSition:X:ANGLe:LIMit:STATe



RS010a15.8.1.1.4 :OFFSet <numeric_value>OUTPut:POSition:X:ANGLe:OFFSet



RS010a15.8.1.1.5 :VELocity <numeric_value>OUTPut:POSition:X:ANGLe:VELocity

Controls the velocity of the angular rotation around the x-axis.


RS010a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.8.1.2 [:DISTance]OUTPut:POSition:X:DISTance

Controls the settings in linear direction of the X-axis.

RS010a15.8.1.2.1 :DIRection UP|DOWN OUTPut:POSition:X:DISTance:DIRection



RS010a15.8.1.2.2 [:IMMediate] <numeric_value>OUTPut:POSition:X:DISTance:IMMediate



RS010a15.8.1.2.3 :LIMitOUTPut:POSition:X:DISTance:LIMit


RS010a15.8.1.2.3.1 :HIGH <numeric_value>OUTPut:POSition:X:DISTance:LIMit:HIGH



RS010a15.8.1.2.3.2 :LOW <numeric_value>OUTPut:POSition:X:DISTance:LIMit:LOW



RS010a15.8.1.2.3.3 :STATe <Boolean>OUTPut:POSition:X:DISTance:LIMit:STATe



RS010a15.8.1.2.4 :OFFSet <numeric_value>OUTPut:POSition:X:DISTance:OFFSet



RS010a15.8.1.2.5 :VELocity <numeric_value>OUTPut:POSition:X:DISTance:VELocity

Controls the velocity of the displacement on the x-axis.


RS010a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.8.2 :YOUTPut:POSition:Y

Controls the settings concerning the Y-axis.

RS010a15.8.2.1 :ANGLeOUTPut:POSition:Y:ANGLe

Specifies the angle of rotation around the Y-axis.

RS010a15.8.2.1.1 :DIRection UP|DOWNOUTPut:POSition:Y:ANGLe:DIRection



RS010a15.8.2.1.2 [:IMMediate] <numeric_value>OUTPut:POSition:Y:ANGLe:IMMediate



RS010a15.8.2.1.3 :LIMitOUTPut:POSition:Y:ANGLe:LIMit


RS010a15.8.2.1.3.1 :HIGH <numeric_value>OUTPut:POSition:Y:ANGLe:LIMit:HIGH



RS010a15.8.2.1.3.2 :LOW <numeric_value>OUTPut:POSition:Y:ANGLe:LIMit:LOW



RS010a15.8.2.1.3.3 :STATe <Boolean>OUTPut:POSition:Y:ANGLe:LIMit:STATe



RS010a15.8.2.1.4 :OFFSet <numeric_value>OUTPut:POSition:Y:ANGLe:OFFSet



RS010a15.8.2.1.5 :VELocity <numeric_value>OUTPut:POSition:Y:ANGLe:VELocity

Controls the velocity of the angular rotation around the y-axis.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




RS010a15.8.2.2 [:DISTance]OUTPut:POSition:Y:DISTance

Controls the settings in linear direction of the Y-axis.

RS010a15.8.2.2.1 :DIRection UP|DOWNOUTPut:POSition:Y:DISTance:DIRection



RS010a15.8.2.2.2 [:IMMediate] <numeric_value>OUTPut:POSition:Y:DISTance:IMMediate



RS010a15.8.2.2.3 :LIMitOUTPut:POSition:Y:DISTance:LIMit


RS010a15.8.2.2.3.1 :HIGH <numeric_value>OUTPut:POSition:Y:DISTance:LIMit:HIGH



RS010a15.8.2.2.3.2 :LOW <numeric_value>OUTPut:POSition:Y:DISTance:LIMit:LOW



RS010a15.8.2.2.3.3 :STATe <Boolean>OUTPut:POSition:Y:DISTance:LIMit:STATe



RS010a15.8.2.2.4 :OFFSet <numeric_value>OUTPut:POSition:Y:DISTance:OFFSet



RS010a15.8.2.2.5 :VELocity <numeric_value>OUTPut:POSition:Y:DISTance:VELocity

Controls the velocity of the displacement on the y-axis.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



RS010a15.8.3 :Z

OUTPut:POSition:Z

Controls the settings concerning the Z-axis

RS010a15.8.3.1 :ANGLeOUTPut:POSition:Z:ANGLe

Specifies the angle of rotation around the Z-axis.

RS010a15.8.3.1.1 :DIRection UP|DOWNOUTPut:POSition:Z:ANGLe:DIRection



RS010a15.8.3.1.2 [:IMMediate] <numeric_value>OUTPut:POSition:Z:ANGLe:IMMediate



RS010a15.8.3.1.3 :LIMitOUTPut:POSition:Z:ANGLe:LIMit


RS010a15.8.3.1.3.1 :HIGH <numeric_value>OUTPut:POSition:Z:ANGLe:LIMit:HIGH



RS010a15.8.3.1.3.2 :LOW <numeric_value>OUTPut:POSition:Z:ANGLe:LIMit:LOW



RS010a15.8.3.1.3.3 :STATe <Boolean>OUTPut:POSition:Z:ANGLe:LIMit:STATe



RS010a15.8.3.1.4 :OFFSet <numeric_value>OUTPut:POSition:Z:ANGLe:OFFSet



RS010a15.8.3.1.5 :VELocity <numeric_value>OUTPut:POSition:Z:ANGLe:VELocity

Controls the velocity of the angular rotation around the z-axis.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




RS010a15.8.3.2 [:DISTance]OUTPut:POSition:Z:DISTance

Controls the settings in linear direction of the Z-axis.

RS010a15.8.3.2.1 :DIRection UP|DOWNOUTPut:POSition:Z:DISTance:DIRection



RS010a15.8.3.2.2 [:IMMediate] <numeric_value>OUTPut:POSition:Z:DISTance:IMMediate



RS010a15.8.3.2.3 :LIMitOUTPut:POSition:Z:DISTance:LIMit


RS010a15.8.3.2.3.1 :HIGH <numeric_value>OUTPut:POSition:Z:DISTance:LIMit:HIGH



RS010a15.8.3.2.3.2 :LOW <numeric_value>OUTPut:POSition:Z:DISTance:LIMit:LOW



RS010a15.8.3.2.3.3 :STATe <Boolean>OUTPut:POSition:Z:DISTance:LIMit:STATe



RS010a15.8.3.2.4 :OFFSet <numeric_value>OUTPut:POSition:Z:DISTance:OFFSet



RS010a15.8.3.2.5 :VELocity <numeric_value>OUTPut:POSition:Z:DISTance:VELocity

Controls the velocity of the displacement on the z-axis.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.9 :PROTectionOUTPut:PROTection

Controls the characteristics of the output protection or foldback circuits.

15.9.1 :DELay <numeric_value>OUTPut:PROTection:DELay

Controls the amount of time the protection trip condition must be true before the subsequentprotection is taken (for example, tripping a foldback circuit or reporting an error). The unitsfor the parameter are seconds.


15.9.2 [:STATe] <Boolean>OUTPut:PROTection:STATe

Controls whether the output protection circuit is enabled.


15.9.3 :TRIPped?OUTPut:PROTection:TRIPped?

This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped. TRIPpedonly has a query form and thus has no associated *RST condition.

15.9.4 :CLEarOUTPut:PROTection:CLEar

Causes the protection circuit to be cleared.


15.10 :ROSCillatorOUTPut:ROSCillator

HP044

The ROSCillator subtree controls the output on the ROSCillator OUTPut port.

15.10.1 [:STATe] <Boolean>OUTPut:ROSCillator:STATe

HP044

The STATe command selects whether or not the device outputs a signal on its ROSCillatorport. When ON is selected, the device outputs a signal; when OFF, it does not.

At *RST, STATe OFF shall be selected.

15.11 :TTLTrg<n>|:ECLTrg<n>OUTPut:TTLTrg|:ECLTrg

The TTLTrg and ECLTrg subtrees control the driving of the VXI backplane TTL and ECLtrigger buses. A numeric suffix is required, indicating the particular line in the bus. Validlines are TTLTrg0 through TTLrg7, and ECLTrg0 through ECLTrg5.

15.11.1 :IMMediateOUTPut:TTLTrg|:ECLTrg:IMMediate

HP023

The IMMediate command causes a pulse to appear on the specified trigger line, regardless ofthe level.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



15.11.2 :LEVel <Boolean>OUTPut:TTLTrg|:ECLTrg:LEVel

HP023

The LEVel command sets the selected TTLTrg or ECLTrg line to a logical level 0 or 1. ForTTL, level 0 is 5 volts and level 1 is 0 volts. For ECL level 0 is -2 volts and level 1 is 0 volts.

At *RST, LEVel is set to OFF.

TK03015.11.3 :POLarity NORMal|INVertedOUTPut:TTLTrg|:ECLTrg:POLarity

This command sets and queries the polarity of the specified VXI TTL or ECL trigger line.

At *RST, the value of this parameter is NORMal.

15.11.4 :PROTocol SYNChronous|SSYNchronous|ASYNchronousOUTPut:TTLTrg|:ECLTrg:PROTocol

HP093This command selects the trigger protocol for the VXI TTLTrg or ECLTrg trigger lines. Theprotocols are specified in the VXIbus System Specification Revision 1.4 under sectionsB.6.2.3 and B.6.2.4.

HP093SYNChronous selects the synchronous trigger protocol.

HP093SSYNchronous selects the semi-synchronous trigger protocol.

HP093ASYNchronous selects the asynchronous trigger protocol.

At *RST, the SYNChronous protocol is selected for all trigger lines.

15.11.5 :WIDTh <numeric_value>OUTPut:TTLTrg|:ECLTrg:WIDTh

PH017

Selects width of the pulse being generated by the OUTPut:TTLTrg<n>:IMMediate orOUTPut:ECLTrg<n>:IMMediate command. The default units are seconds.

The *RST value is device dependent.

15.11.6 [:STATe] <Boolean>OUTPut:TTLTrg|:ECLTrg:STATe

The STATe command selects whether or not the VXI module drives the VXI backplanetrigger line. When ON is selected, the module shall drive the trigger line; when OFF, it shallnot.

At *RST, STATe OFF shall be selected.

15.11.7 :SOURce <character data>OUTPut:TTLTrg|:ECLTrg:SOURce

Controls which signal from the VXI module shall drive the VXI backplane trigger line.Source names are character data, such as INTernal or EXTernal.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



HP066

15.12 [:STATe] <Boolean>OUTPut:STATe

The STATe function controls whether the output terminals are open or closed. When thefunction is OFF, the terminals are at maximum isolation from the signal.

At *RST, this function shall be set to OFF.

15.13 :TYPE <character data>OUTPut:TYPE

RS007

Selects the output characteristic to be used if more than one is available.

The following characteristics are currently defined for instruments:

BALanced – balanced or differential output.

UNBalanced – unbalanced with respect to ground.

At *RST the TYPE is device-dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



16 PROGram SubsystemThe purpose of the PROGram subsystem is to provide the administrative features needed togenerate and control one or more user-programmed tasks resident in an instrument. Twodistinct methods of accessing a particular program are provided in the PROGramsubysystem. One method employs EXPLicit reference for each command, allowing access toall programs, but requires the program name to be always specified. The other methodallows a single program to be SELected at a time, and the related commands access only thecurrently selected program. If the EXPLicit method is implemented, then the SELectedmethod shall also be implemented.

A *RST received from a remote controller, via the device interface, shall cause all programsto be stopped.

A *RST generated by a program running in the device shall cause the same effect as a *RSTreceived from a remote controller, with the exception that the program that generated the*RST shall not be forced to stop. It is necessary for a *RST to behave in this manner so thata program, when run on either a remote controller or the device, shall have the same effect.

KEYWORD PARAMETER FORM NOTESPROGram :CATalog? [query only] [:SELected] :DEFine <program> :DELete [no query] [:SELected] :ALL :EXECute <program_command> [no query] :MALLocate <nbytes>|DEFault :NAME <progname> :NUMBer <varname>{,<nvalues>} :STATe (RUN|PAUSe|STOP|CONTinue) :STRing <varname>{,<svalues>} :WAIT 1991 HP009

:EXPLicit :DEFine <progname>,<program> :DEFine? <progname> [query only] :DELete <progname> :EXECute <progname>,<program_command> [no query] :MALLocate <progname>,(<nbytes>|DEFault) :NUMBer <progname>,<varname>{,<nvalues>} :STATe <progname>,(RUN|PAUSe|STOP|CONTinue) :STRing <progname>,<varname>{,<svalues>} :WAIT <progname> 1991

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


PROGram 16-1

HP009

16.1 :CATalog?PROGram:CATalog?

The CATalog query commands lists all the defined programs. Response is a list ofcomma-separated strings. Each string contains the name of a program. If no programs arecurrently defined, then response is a null string ( “” ).

16.2 [:SELected]PROGram:SELected

All the commands under this node access only the program that has been selected by theNAME command.

16.2.1 :DEFine <program>PROGram:SELected:DEFine

The DEFine command is used to create and download programs. The DEFine query is usedto upload programs. The program name used for the definition is the currently selectedprogram name.

In the DEFine command, the selected program name shall represent a unique name. That is,to download and overwrite an existing program with the same program name, the existingprogram must be DELeted first. If such an attempt is made without deleting first, an “Illegalprogram name” error (-282) shall be generated.

The <program> shall be block data. The contents are device-dependent. When overflowoccurs a program error (-28X) shall be generated.

In the DEFine query, the selected program shall be returned. The <program> shall beuploaded as definite length arbitary block response data.

16.2.2 :DELetePROGram:SELected:DELete

The DELete command deletes downloaded programs.

16.2.2.1 [:SELected]PROGram:SELected:DELete:SELected

This command causes the selected program to be deleted.

16.2.2.2 :ALLPROGram:SELected:DELete:ALL

ALL is used to specify that all programs in the device are to be deleted. If any of theprograms are in the RUN state, a “Program currently running” error (-284) shall begenerated and no programs shall be deleted.

16.2.3 :EXECute <program_command>PROGram:SELected:EXECute

The EXECute command executes the <program_command> in the selected programenvironment. <program_command> is string data representing any legal program command.If the string data is not legal, then a “Program syntax error” (-285) shall be generated. Theselected program shall be in either the PAUSed or STOPped state before the EXECute

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


16-2 PROGram:CATalog?

command shall be allowed. If the program is in the RUN state, a “Program currentlyrunning” error (-284) shall be generated.

16.2.4 :MALLocate <nbytes>|DEFaultPROGram:SELected:MALLocate

The Memory ALLocate command is used to reserve memory space in the device for use bythe selected program. If DEFault is specified, then the device shall calculate the amount ofmemory needed. <nbytes> is numerical data which specifies the required memory in bytes.If the required memory is greater than the space available, then a parameter error “Data outof range” (-222) shall be generated.

*RST has no effect on the value of MALLocate.

16.2.5 :NAME <progname>PROGram:SELected:NAME

The NAME command defines the name of the program to be selected. If the program name<progname> already exists, then that existing program shall be selected. If the programname does not exist, then the new name shall be selected, but no program shall be defined bythis selection. <progname> is character data.

*RST causes the selected name to become PROG.

16.2.6 :NUMBer <varname>{,<nvalues>}PROGram:SELected:NUMBer

The NUMBer command is used to set and query the contents of numeric program variablesand arrays in the currently selected program. The currently selected program must be aDEFined program, otherwise an “Illegal program name” error (-282) shall be generated. Thevariable specified in <varname> shall be the name of an existing variable in the selectedprogram, otherwise an “Illegal variable name” error (-283) shall be generated. <varname>can be either character data or string data. <nvalues> is a list of comma separated<numeric_values> which are used to set <varname>. If the specified variable cannot hold allof the specified <numeric_values> then a “Parameter not allowed” error ( -108 ) shall begenerated.

The query form NUMBer? <varname> returns the contents of the variable as a commaseparated list

16.2.7 :STATe RUN|PAUSe|STOP|CONTinuePROGram:SELected:STATe

The STATe command is used to either set the state or query the state of a selected program.The following matrix defines the effect of setting the STATe to the desired value from eachof the possible current states. In certain cases a parameter error “Settings conflict” (-221)shall be generated.

The states are described as follows:RUNNING: The program is currently executingPAUSED: The program has reached a break in execution but can be continued.STOPPED: Execution has been terminated.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


PROGram[:SELected] 16-3

16.2.8 :STRing <varname>{,<svalues>}PROGram:SELected:STRing

The STRing command is used to set and query the contents of string program variables andarrays in the currently selected program. The currently selected program must be a DEFinedprogram, otherwise an “Illegal program name” error (-282) shall be generated. The variablespecified in <varname> shall be the name of an existing variable in the selected program,otherwise an “Illegal variable name” error (-283) shall be generated. <varname> can beeither character data or string data. <svalues> is a list of comma-separated strings which areused to set <varname>. If the specified variable cannot hold all of the specified string valuesthen a “Parameter not allowed” error (-108 ) shall be generated. If a string value is too longthen it will be truncated when stored in the programs variable.

The query form STRing? <varname> returns the contents of the variable as a commaseparated list

16.2.9 :WAITPROGram:SELected:WAIT

HP009

The WAIT command and its query form shall cause no further commands or queries to beexecuted, until the selected program exits from the RUN state, that is either STOPped orPAUSed. For the query, a 1 is returned in NR1 format at this time, when the program iseither STOPped or PAUSed.

16.3 :EXPLicitPROGram:EXPLicit

All the commands under the EXPLicit node directly reference the desired program by name,thus allowing access to a program without having to change the selected program. The<progname> parameter is required for these commands.

16.3.1 :DEFine <progname>,<program>PROGram:EXPLicit:DEFine

The DEFine command is used to create and download programs. The DEFine query is usedto upload programs.

In the DEFine command, the specified program name shall represent a unique name. That is,to download and overwrite an existing program with the same program name, the existingprogram must be DELeted first. If such an attempt is made, without deleting first, an “Illegalprogram name” error (-282) shall be generated.

staterequested

current state

RUNNING PAUSED STOPPED

RUN error (-221) RUNNING RUNNING

CONT error (-221) RUNNING error (-221)

PAUSE PAUSED PAUSED STOPPED

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


16-4 PROGram:EXPLicit

The <program> shall be block data. The contents are device-dependent. When overflowoccurs a program error (-28X) shall be generated.

In the DEFine query, the specified program name shall be the name of an existing program;otherwise an “Illegal program name” error (-282) shall be generated. The <program> shallbe uploaded as definite length arbitary block response data.

16.3.2 :DELete <progname>PROGram:EXPLicit:DELete

The delete command deletes the specified downloaded program.

16.3.3 :EXECute <progname>,<program_command>PROGram:EXPLicit:EXECute

The EXECute command executes the <program_command> in the specified programenvironment. <program_command> is string data representing any legal program command.If the string data is not legal, then a “Program syntax error” (-285) shall be generated. Thespecified program shall be in either the PAUSed or STOPped state before the EXECutecommand shall be allowed. If the program is in the RUN state, a “Program currentlyrunning” error (-284) shall be generated.

16.3.4 :MALLocate <progname>,(<nbytes>|DEFault)PROGram:EXPLicit:MALLocate

The Memory ALLocate command is used to reserve memory space in the device for use bythe specified program. The specified program shall be the name of an existing program,otherwise an “Illegal program name” error (-282) shall be generated. If DEFault is specified,then the device shall calculate the amount of memory needed. <nbytes> is numerical datawhich specifies the required memory in bytes. If the required memory is greater than thespace available, then a parameter error “Data out of range” (-222) shall be generated.

*RST has no effect on the value of MALLocate.

16.3.5 :NUMBer <progname>,<varname>{,<nvalues>}PROGram:EXPLicit:NUMBer

The NUMBer command is used to set and query the contents of numeric program variablesand arrays in the specified program. The specified program must be a DEFined program,otherwise an “Illegal program name” error (-282) shall be generated. The variable specifiedin <varname> shall be the name of an existing variable in the specified program, otherwisean “Illegal variable name” error (- 283) shall be generated. <varname> can be eithercharacter data or string data. <nvalues> is a list of comma-separated <numeric_values>which are used to set <varname>. If the specified variable cannot hold all of the specified<numeric_values>, then a “Parameter not allowed” error (-108 ) shall be generated.

The query form NUMBer? <varname> returns the contents of the variable as a commaseparated list

16.3.6 :STATe <progname>,(RUN|PAUSe|STOP|CONTinue)PROGram:EXPLicit:STATe

The STATe command is used to either set the state or query the state of the specifiedprogram. The matrix below defines the effect of setting the STATe to the desired value from

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


PROGram:EXPLicit 16-5

each of the possible current states. In certain cases a parameter error “Settings conflict”(-221) shall be generated.

The states are described as follows:RUNNING: The program is currently executingPAUSED: The program has reached a break in execution but can be continued.STOPPED: Execution has been terminated.

16.3.7 :STRing <progname>,<varname>{,<svalues>}PROGram:EXPLicit:STRing

The STRing command is used to set and query the contents of string program variables andarrays in the specified program. The specified program must be a DEFined program,otherwise an “Illegal program name” error (-282) shall be generated. The variable specifiedin <varname> shall be the name of an existing variable in the specified program, otherwisean “Illegal variable name” error (-283) shall be generated. <varname> can be either characterdata or string data. <svalues> is a list of comma-separated strings which are used to set<varname>. If the specified variable cannot hold all of the specified string values, then a“Parameter not allowed” error (-108) shall be generated. If a string value is too long then itwill be truncated when stored in the programs variable.

The query form STRing? <varname> returns the contents of the variable as a commaseparated list

16.3.8 :WAIT <progname>PROGram:EXPLicit:WAIT

HP009

The WAIT command and its query form shall cause no further commands or queries to beexecuted, until the defined program exits from the RUN state, that is either STOPped orPAUSed. For the query, a 1 is returned in NR1 format at this time, when the program iseither STOPped or PAUSed.

desiredstate

current state

RUNNING PAUSED STOPPED

RUN error (-221) RUNNING RUNNING

CONT error (-221) RUNNING error (-221)

PAUSE PAUSED PAUSED STOPPED

STOP STOPPED STOPPED STOPPED

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


16-6 PROGram:EXPLicit

17 ROUTe SubsystemIn the SCPI instrument model, the block where user accessibility to the actual signals occursis called “signal routing.” In some instruments this function may be trivial and thuscommands for this block would not be required. In such cases the ports associated with theINPut or OUTput blocks are available directly to the user, typically on the instrument’s frontpanel. The ROUTe commands apply equally to instruments whose primary purpose is toprovide signal routing and to instruments that provide some routing capability “in front of”the INPut and/or OUTput blocks.

The ROUTe node may be optional in a particular instrument. This capability is intended forinstruments whose primary function is signal routing. The ROUTe node cannot be optional ifeither SENSe or SOURce is optional, since only one node at a given level may be optional.

KEYWORD PARAMETER FORM NOTES:ROUTe :CLOSe <channel_list> 1992 HP062

:STATe? [query only] :MODule :CATalog? [query only] :DEFine <module_name>,<module_address> :DEFine? <module_name> :DELete :ALL [event; no query] [:NAME] <module_name> [event; no query] :OPEN <channel_list> 1992 HP062

:ALL [event; no query] 1993 HP062

:PATH :CATalog? [query only] :DEFine <path_name>,<channel_list> :DEFine? <path_name> :DELete :ALL [event; no query] [:NAME] <path_name> [event; no query] :SAMPle 1999 :CATalog? [query only] 1999 HP078

KI002 [:OPEN] BAG|DILute|PRE|POST|MID |CEFFiciency|NONE|ZERO|SPAN |VERify|MANifold 1999

:SCAN <channel_list> 1992,4KI003 :TERMinals FRONt|REAR|BOTH|NONE 1992 HP052

17.1 :CLOSe <channel_list>ROUTe:CLOSe

HP062

The CLOSe command allows specific individual channels to be closed or queried. If all thespecified channels cannot be closed, an execution error is reported.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


ROUTe Subsystem 17-1

For example, suppose a module contains a coaxial multiplexor, and only one channel on abank is able to be closed at a time. If a command tries to close two channels on the samebank, the instrument should report an execution error.

CLOSe may be an overlapped command. The *OPC mechanism may be used to determinewhen switches are actually closed or opened. The sequence in which channels are closed isnot guaranteed.

The CLOSe? query allows the condition of individual switches to be queried. The instrumentreturns a 1 or 0 for each channel in the list, in the same order that the list is specified. Aresponse of 1 means the channel is closed and a 0 means the channel is open.


17.1.1 :STATe?ROUTe:CLOSe:STATe?

The ROUTe:CLOSe:STATe? query, which has no parameters, returns an IEEE 488.2definite length block which contains a <channel_list> of all the closed switches in the entireinstrument.

17.2 :MODuleROUTe:MODule

The MODule subsystem controls the assignment of <module_name>.

17.2.1 :CATalog?ROUTe:MODule:CATalog?

The ROUTe:MODule:CATalog? query returns a list of all currently defined<module_names>.

HP096Response is a list of comma-separated strings. Each string contains a <module_name>. If no<module_name> elements are currently defined, then response is a null string ("").

17.2.2 [:DEFine] <module_name>,<module_address>ROUTe:MODule:DEFine

Name a module <module_address> as <module_name>. This command assigns auser-defined name to a number representing a card address in hardware-dependent form (forexample, a VME address).

The query form of this command, “ROUTe:MODule:DEFine? <module_name>” returns an<NR1> response showing what <module_address> is bound to <module_name>.

17.2.3 :DELeteROUTe:MODule:DELete

17.2.3.1 :ALLROUTe:MODule:DELete:ALL

The ROUTe:MODule:DELete:ALL command deletes all module name bindings, and freesall names created by the MODule command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


17-2 ROUTe Subsystem

17.2.3.2 [:NAME] <module_name>ROUTe:MODule:DELete:NAME

The ROUTe:MODule:DELete[:NAME] command removes a module name created by aMODule command.

17.3 :OPEN <channel_list>ROUTe:OPEN

HP062

The OPEN command allows specific channels to be opened or queried.

OPEN may be an overlapped command. The *OPC mechanism may be used to determinewhen switches are actually closed or opened. The sequence in which channels are opened isnot guaranteed.

The query OPEN? allows the condition of switches to be queried. The instrument returns a 1or 0 for each channel in the list, in the same order that the list is specified. A response of 0means the channel is closed and a 1 means the channel is open.


17.3.1 :ALL HP078ROUTe:OPEN:ALL

The OPEN:ALL command opens all the channels.

OPEN:ALL may be an overlapped command. The *OPC mechanism may be used todetermine when switches are actually closed or opened. The sequence in which channels areopened is not guaranteed.

17.4 :PATHROUTe:PATH

The PATH subsystem controls the binding of <channel_list> elements.

17.4.1 :CATalog?ROUTe:PATH:CATalog?

The ROUTe:PATH:CATalog? query returns a list of all currently defined <path_names>.

HP096Response is a list of comma-separated strings. Each string contains a <path_name>. If no<path_name> elements are currently defined, then response is a null string ("").

17.4.2 [:DEFine] <path_name>,<channel_list>ROUTe:PATH:DEFine

The ROUTe:PATH:DEFine command assigns <path_name> as a user-specified way ofreferring to <channel_list>. This command allows the user to define a list of relays that canbe opened and closed with the use of a <path_name>.

The query form of this command, “ROUTe:PATH:DEFine? <path_name>” returns a blockcontaining the <channel_list> bound to <path_name>.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



17.4.3 :DELeteROUTe:PATH:DELete

17.4.3.1 :ALLROUTe:PATH:DELete:ALL

The ROUTe:PATH:DELete:ALL command deletes all path name bindings, and frees allnames created by the PATH command.

ROUTe:SAMPle

17.4.3.2 [:NAME] <path_name>ROUTe:PATH:DELete:NAME

The ROUTe:PATH:DELete[:NAME] command removes a path name created by a PATHcommand.

17.5 :SAMPleROUTe:SAMPle

This subsystem sets up the route for the sample gas to flow.

17.5.1 :CATalog?:ROUTe:SAMPle:CATalog?

Returns a comma-separated list of strings containing available sample points used for:ROUTe:SAMPle:OPEN.

17.5.2 [:OPEN] BAG|DILute|PRE|POST|MID|CEFFiciency|NONE|ZERO|SPAN|VERify|MANifold:ROUTe:SAMPle[:OPEN]

This command causes flow from the specified sample point to the selected instrument(s). Anexecution error -200 shall occur if the <sample_point> references a configuration that cannotbe achieved by the device. This command can also query the currently selected<sample_point>. The query response is a string. Each string contains a <sample_point>. If a<sample_point> is not currently selected, then the response is NONE.

At *RST the selected path goes to the idle state (NONE).

For emissions benches, the :ROUTe:SAMPle command is used to route gases from thesource to the measurement instrument. This command causes gases to flow to theinstruments from the specified sample point. No measurement sequence is executed,however subsequent SENSe:DATA? queries will reflect the current values of the gasesflowing through the analyzers. Gas routing may be implied during predefined procedures.On *RST the selected path goes to the idle state (NONE).

When the following <sample_point>s are implemented they shall conform to the followingnaming conventions:

BAG — Causes gases from the specified bag sampling system to flow through theinstruments. (Note: an appropriate CVS command is needed to complete this function.)

DILute — Gases from the Sampler after dilution with ambient air, for example, thetunnel of a diesel sampling system

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



PRE — Gasses from between the engine and the catalytic converter.

POST — Gasses from the vehicle exhaust after the catalyst but before dilution in thesampling system.

MID — Gases from between the oxidizing and reducing catalysts.

CEFFiciency — Directs gases from each of the necessary sample points to each of thenecessary sample manifolds in order to perform a catalyst efficiency test.

NONE — Places the flow of gases in an idle state.

ZERO — Directs zero gases to the selected instruments.

SPAN — Directs span gases to the selected instruments for the selected ranges.

VERify — Flows verification gases to all selected instruments

MANifold — Enables Manifold as locally configured at the bench.Examples:

:INSTrument:DEFine:GROup MyGroup, “CONC1", ”CONC2", “CONC3":INSTrument:SELect MyGroup:ROUte:SAMPle ZERO

Routes zero gas to all analyzers defined by the group “MyGroup”.

:INSTrument:DEFine:GROup MyGroup, “CONC1", ”CONC3", “CONC4":INSTrument:SELect MyGroup:ROUte:SAMPle NONE

Discontinues any flows in progress and places the flow of gases into an idle state, for thegroup of instruments defined by “MyGroup”.

:INSTrument:DEFine:GROup MyGroup, “CONC2", ”CONC3":INSTrument:SELect MYGROUP:ROUTe:SAMPle MANifold1

Flows engine exhaust from manifold setting 1 for the group of instruments defined by“MyGroup”.

:INSTrument:DEFine:GROup MyGroup, “CONC1",”CONC2", “CONC3":INSTrument:SELect MyGroup:ROUTe:SAMPle?

Returns: MANifold1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



17.6 :SCAN <channel_list>ROUTe:SCAN

HP062

KI002The SCAN command specifies or queries a list of channels for the instrument to sequencethrough. The instrument will automatically step through the list of channels provided whenthe trigger subsystem device action occurs. The device action is to open the channelpreviously closed, then to close the next channel in the list. Whether this action isbreak-before-make is device-dependent.

The INITiate[:IMMediate] command must be sent in order to initiate scanning.

Execution of the SCAN command, and the resulting scan operation, may or may not openany channels which are already closed.

If the <channel_list> parameter contains a <channel_range>, the instrument will expand therange into its individual channels, and scan each channel individually. For example,(@1,3:5,9) will be scanned identically to (@1,3,4,5,9).

The query, which has no parameter, returns the scan list. The format of the response is anIEEE 488.2 definite length block which contains a <channel_list>. The instrument mayreturn the scan list exactly as it was received, or it may return an equivalent list with paths orranges expanded.

Note: The query form was added in 1994.

KI00317.7 TERMinals FRONt|REAR|BOTH|NONEROUTe:TERMinals

HP052

KI003FRONt opens the rear terminals and closes the front terminals (break before make). REARopens the front terminals and closes the rear terminals (also break before make). BOTHcloses both the front and rear terminals in a device-dependent order. NONE opens both thefront and rear terminals in a device-dependent order.

At *RST, TERM is set to FRONt.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18 SENSe SubsystemThe SENSe setup commands are divided into several sections. Each section or subsystemdeals with controls that directly affect device-specific settings of the device and not thoserelated to the signal-oriented characteristics. These commands are referenced through theSENSe node.

The SENSe node may be optional in a particular device. The reason that the SENSe isoptional is to allow devices which are primarily sensors to accept shorter commands. TheSENSe node cannot be optional if either SOURce or ROUTe is optional, since only onenode at a given level may be optional. For example, a typical counter may elect to make theSENSe node optional, since the most frequently used commands would be under the SENSesubsystem. If the counter also contained either source or routing functionality, these wouldbe controlled through their respective nodes; however, the SOURce or ROUTe nodes wouldbe required. An optional node, such as SENSe, implies that the device shall accept andprocess commands with or without the optional node and have the same result. That is, thedevice is required to accept the optional node, if sent, without error.

In some instances, a sensor may contain subservient source or sensor functions. In suchcases, the additional subservient functionality shall be placed as SENSe or SOURcesubnodes under the SENSe subsystem. Further, no optional nodes (SENSe, SOURce orROUTe) are permitted if such subservient functionality exists in a device. Otherwiseconflicts in interpreting commands would occur, for example, between SENSe and[SOURce:]SENSe if the SOURce were allowed to be optional.

The FREQuency subsystem contains several sets of commands which have complexcouplings. This includes the swept commands STARt, STOP, CENTer, and SPAN as oneset. Sending any one of a set singly will affect two others of the set. However, if two are sentin a single message unit, then these two should be set to the values specified and the othertwo changed. This is in accordance with the style guidelines and IEEE 488.2. If anycommand in the set is implemented then all the commands in the set shall be implemented.

If the requested setting is unachievable given the other instrument settings, then an errormust be generated (-221 “Settings conflict”). The device may resolve the conflict in adevice-dependent manner (for example, change STARt, STOP, CENTer, and/or SPAN) toresolve the error. Note that when more than one of the four sweep settings are received in thesame program message unit, the sweep will be determined by the last two received.

PH075The coupled commands may define commands as subnodes which alter these couplings. Thecommand description will define how the couplings are altered. However, any commandwhich alters couplings must default to the couplings described in this section as the *RSTcouplings.

When CENTer or SPAN is changed the following couplings apply:SPAN = SPANCENTer = CENTerSTOP = CENTer + (SPAN/2)STARt = CENTer - (SPAN/2)

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe: 18-1

When STARt or STOP changed the following couplings apply:STARt = STARt CENTer = (STARt + STOP)/2STOP = STOP SPAN = STOP - STARt

The CURRent, VOLTage and POWer subsystems contain several commands which havecomplex couplings. These commands exist under RANGe: they are UPPer, LOWer, OFFset,and PTPeak. UPPer and LOWer are considered as one set, with OFFSet and PTPeak asanother set. Sending any one of a set singly shall affect the two values of those commands inthe other set. However, if two are sent in a single message unit, then these two should be setto the values specified and the unspecified two values shall be changed. This is inaccordance with the style guidelines and IEEE 488.2. If either OFFSet or PTPeak isimplemented, then all four commands, UPPer, LOWer, OFFSet, and PTPeak shall also beimplemented.

When UPPer or LOWer is changed the following couplings apply:UPPer = UPPer OFFSet = (UPPer + LOWer)/2LOWer = LOWer PTPeak = UPPer - LOWer

When OFFSet or PTPeak is changed the following couplings apply:OFFSet = OFFSet UPPer = OFFSet + (PTPeak/2)PTPeak = PTPeak LOWer = OFFSet - (PTPeak/2)

The SENSe subsystem for the dynamometer contains the commands needed to sensereal-time measurements taken from the dynamometer system. This includes force, speed,frictional losses, acceleration rate, distance, and simulation error. These commands are usedin conjunction with the TRIGer Subsystem for collecting data in blocks. See SCPI 1995Volume 2 Command Reference chapter 18 section 11 for further detail on the DATA andFUNCtion subsystems.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-2 SENSe:

First Level SENSe Keywords[:SENSe] :AM 1991 :AVERage 1992 HP054

:BANDwidth|:BWIDth :CONCentration 1999 :CONDition PH074 :CORRection :CURRent :DATA? 1999 :DETector :DISTance 1999 :FILTer 1991 :FM 1991 :FREQuency :FUNCtion :LIST :MIXer :PM 1991 :POWer :RESistance|:FRESistance :ROSCillator :SMOothing

RS011 :SSB :STABilize 1999 :SWEep :VOLTage :WINDow

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe: 18-3

18.1 AM SubsystemSENSe:AM

RS011The Amplitude Modulation subsystem is used to set up the modulation controls andparameters associated with sensing and demodulating amplitude modulated signals.

KEYWORD PARAMETER FORM NOTES:AM 1991 [:DEPTh] 1991 :RANGe 1991 :AUTO <Boolean>|ONCE 1991 [:UPPer] <numeric_value> 1991 :LOWer <numeric_value> 1991

RS011 :TYPE LINear|LOGarithmic 1994

18.1.1 [:DEPTh]SENSe:AM:DEPTh

This node is used to collect together the depth parameters.

18.1.1.1 :RANGeSENSe:AM:DEPTh:RANGe

Sets the range for the sensor function.

18.1.1.1.1 :AUTO <Boolean> | ONCESENSe:AM:DEPTh:RANGe:AUTO

Sets the RANGe to the value determined to give the most dynamic range withoutoverloading. The actual algorithm is device-dependent. Selecting AUTO ONCE will havethe effect of setting AUTO to ON and then OFF.


18.1.1.1.2 [:UPPer] <numeric_value>SENSe:AM:DEPTh:RANGe:UPPer

Specifies the maximum signal level expected for the sensor input.


18.1.1.1.3 :LOWer <numeric_value>SENSe:AM:DEPTh:RANGe:LOWer

Specifies the smallest signal level expected for the sensor input. This allows setting for thebest dynamic range. This function is coupled to UPPer.


RS01118.1.2 :TYPE LINear|LOGarithmicSENSe:AM:TYPE

SENSe:AM:TYPE sets or queries the type of amplitude demodulation technique thedemodulator uses. LINear means the demodulated signal is derived directly from theamplitude of the signal in a linear way. LOGarithmic means the demodulated signal isderived from the amplitude of the signal in a logarithmic way. The amplitude of thedemodulated signal is proportional to the log-value of the amplitude of the signal.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-4 SENSe:AM

At *RST, this value is set to LINear.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:AM 18-5

18.2 AVERage SubsystemSENSe:AVERage

HP054

FL005The purpose of this subsystem is to control averaging used to improve the measurement. Forexample to improve the accuracy or to acquire maximum/minimum measurements.Analytical post-acquisition statistical functions are controlled within the CALCulate block.The AVERage subsystem combines successive measurements to produce a new compositeresult. The new result has the same number of points and control axis as the originalmeasurement.

HP054A :COUNt command is provided to specify the number of measurements to combine. When:COUNT averages are reached, the TerminalCONtrol switch specifies the operation of theaverage subsystem. The TerminalCONtrol switch can be configured to continue replacingold values with new values (MOVing), to exponentially weight new measurements(EXPonential), to automatically repeat (REPeat), or to continue adding new measurements inthe NORMal fashon, as specified by :TYPE.

HP054The average operation differs from CALC:SMOOthing in the fact that AVERage combinesthe jth point of each measurement with the jth point of preceeding measurements, whereas inSMOOthing the jth point is processed with adjacent points (...., j-2, j-1, j, j+1, j+2, ...) of thecurrent measurement set.

Note: The notation Xn* indicates the complex conjugate of a number. So: XX* = MAG2(X) = |X|2

HP081b

18.2.1 A typical device action for SENS:AVERage HP054

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-6 SENSe:AVERage

KEYWORD PARAMETER FORM NOTES:AVERage 1992 :COUNt <numeric_value> 1992 :AUTO <Boolean> | ONCE 1992 [:STATe] <Boolean> 1992 :TCONtrol EXPonential | MOVing | NORMal | REPeat 1992 :TYPE COMPlex | ENVelope | MAXimum 1992

| MINimum | RMS | SCALar 1992

18.2.2 :COUNt <numeric_value>HP054SENSe:AVERage:COUNt

HP054Specifies the number of measurements to combine using the :TYPE setting. After :COUNtmeasurements have been averaged, the operation of the AVERage subsystem is controlledby the setting of the :TCONtrol node.

HP054The count for array based results is independent of the number of points in the result array.For example, an instrument which normally provides a measurement result which is a 401point array would specify an average count of two to average two results, not 802.

HP054When averaging is ON, some devices may automatically set :COUNt values in the TRIGgersubsystem based on the AVER:COUNt value, such that the TRIGger subsystem providesenough triggers for the average.


18.2.2.1 :AUTO <Boolean> | ONCESENSe:AVERage:COUNt:AUTO

HP054

HP054AUTO ON causes the device to select a value for :COUNt which is appropriate for thecurrent measurement. Selecting AUTO ONCE will have the effect of setting AUTO ON andthen OFF.


18.2.3 [:STATE] <Boolean>SENSe:AVERage:STATE

HP054

The STATe command is used to turn averaging ON and OFF.


18.2.4 :TCONtrol EXPonential | MOVing | NORMal | REPeatSENSe:AVERage:TCONtrol

HP054

Ed ChangeTerminalCONtrol specifies the action of the AVERage subsystem when more thanAVERage:COUNt measurement results are generated.

The parameter has the following meanings:HP081b

EXPonential Continue the average with an exponential weighting applied to old values.The additional averages are weighted using:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:AVERage 18-7

For :TYPE SCALar when Xn is real and :TYPE COMPlex when Xn is eitherreal or complex

AVGn = 1k Xn +

k − 1k

AVGn − 1

For :TYPE SCALar when Xn is complex

AVGn = 1k MAG(Xn) +

k − 1k

AVGn − 1

For :TYPE RMS when Xn is real

AVGn = √ 1kXn

2 + k − 1

kAVGn − 1

2

For :TYPE RMS when Xn is complex

AVGn = √ 1kXnXn

∗ + k − 1

kAVGn − 1

2

Ed Change

The exponential factor k is equal to the AVERage:COUNt value. Someinstruments may use an approximation to true exponential.

Ed ChangeOperation with EXPonential :TCON is undefined with a :TYPE setting ofMINimum, MAXimum, or ENVelope.

MOVing As new data is added the oldest data is discarded.

REPeat Clear average data and counter and restart the average process.

NORMal Additional averages continue to be accumulated according to the :TYPEselection.


18.2.5 :TYPE COMPlex | ENVelope | MAXimum | MINimum | RMS | SCALarSENSe:AVERage:TYPE

HP054

This command selects the type of averaging, as follows:

COMPlex The points in the summation are treated as real/imaginary pairs.

AVG(n) = 1n ∑ i = 1

n

Xi

ENVelope Both the MIN and MAX values are retained.

If X n is realHP081b

MAXimum AVG(n) = MAX(X 1... Xn )

MINimum AVG(n) = MIN(X1...Xn)

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-8 SENSe:AVERage

RMS AVG(n) = √1n ∑ i = 1

n

Xi2


AVG(n) = 1n ∑ i = 1

n

Xi

If X n is complexHP081b

MAXimum AVG(n) = MAX( MAG(X 1)... MAG(Xn) )

MINimum AVG(n) = MIN( MAG(X1)...MAG(Xn) )

RMS AVG(n) = √1n ∑ i = 1

n

XiXi∗


AVG(n) = 1n ∑ i = 1

n

| Xi |

At *RST, this value is device dependent.HP054

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:AVERage 18-9

18.3 BANDwidth|BWIDth SubsystemSENSe:BANDwidth

This subsystem controls the characteristics of the filter bandwidth of the instrument.Instruments must accept both forms, if they accept either.

KEYWORD PARAMETER FORM NOTES:BANDwidth|:BWIDth [:RESolution] <numeric_value> :AUTO <Boolean>|ONCE :RATio <numeric_value> :TRACk <Boolean> :VIDeo <numeric_value> :AUTO <Boolean>|ONCE :RATio <numeric_value>

18.3.1 [:RESolution] <numeric_value>SENSe:BANDwidth:RESolution

Controls the resolution bandwidth of the instrument. Resolution Bandwidth is defined as thebandwith in Hz of the predetection bandpass filtering. This command has units of Hz.

At *RST, the value of this function is device-dependent.

18.3.1.1 :AUTO <Boolean>|ONCESENSe:BANDwidth:RESolution:AUTO

When enabled, the value of resolution bandwidth is coupled to other parameters of themeasurement. The exact coupling equation is machine-dependent.

At *RST, this function is set to ON.

18.3.1.2 :RATio <numeric_value>SENSe:BANDwidth:RESolution:RATio

Controls the ratio of resolution bandwidth to span when the two are coupled. Coupled isenabled when AUTO is ON. The <numeric_value> is RESolution(Hz)/SPAN(Hz).

At *RST, the value of this function is instrument-dependent.

18.3.1.3 :TRACk <Boolean>SENSe:BANDwidth:RESolution:TRACk

This function allows the resolution bandwidth to dynamically change during a logarithmicfrequency sweep. Logarithmic sweep is enabled via the SENSe:SWEep:SPACing command.

At *RST, the value of this function is ON.

18.3.2 :VIDeo <numeric_value>SENSe:BANDwidth:VIDeo

Controls the video filtering, a particular type of post-detection filtering. This has units ofHertz.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-10 SENSe:BANDwidth|BWIDth

18.3.2.1 :AUTO <Boolean>|ONCESENSe:BANDwidth:VIDeo:AUTO

Couples the value of video bandwidth to instrument-determined values.

At *RST, the value of this setting is ON.

18.3.2.2 :RATio <numeric_value>SENSe:BANDwidth:VIDeo:RATio

Controls the ratio of video bandwidth to resolution bandwidth when the two are coupled.Coupled is enabled when AUTO is ON. The <numeric_value> isVIDeo(Hz)/RESolution(Hz).


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:BANDwidth|BWIDth 18-11

18.4 CONCentration SubsystemSENSe:CONCentration

This subsystem configures the CONCentration measurement functions and parameters. Aninstance of this subsystem exists for each range in an instrument. The data defined andqueried and the events will only be performed on the currently selected range of thecurrently selected instrument(s).

KEYWORD PARAMETER FORM COMMENTS:CONCentration 1999 :CSET <numeric_value>,<numeric_value> 1999 :LOWer <numeric_value> 1999 :LSET POLYnomial<n> | SRATional<n>,<numeric_value> 1999 :RANGe 1999 :AUTO 1999 :LOWer <numeric_value> 1999 [:STATe] <Boolean> 1999 :UPPer <numeric_value> 1999 [:FIXed] <numeric_value> 1999 :TALign <numeric_value> 1999 :UPPer <numeric_value> 1999

18.4.1 :CSET <numeric_value>,<numeric_value> :SENSe:CONCentration:CSET

This command specifies or queries the correction set(s) used for the current range(s). Theparameters are the slope and the Y intercept used in the latest correction calculation.

At *RST these values are not changed.

18.4.2 :LOWer <numeric_value>:SENSe:CONCentration:LOWer

This command specifies or queries the lowest measurable concentration for thecurrently-selected range for the selected instruments.


18.4.3 :LSET POLYnomial<n> | SRATional<n>,<numeric_value>{,<numeric_value>} :SENSe:CONCentration:LSET

This command sets or returns the curve fit type and coefficients that are currently in use.Coefficients are listed starting with the 0th order term. The first parameter is the curve type,which consists of either POLYnomial for a polynomial curve fit or SRATional for a simplerational polynomial curve fit, followed by a positive integer <n>, which is the curve order.The additional parameters are the curve coefficients. These are listed starting with the 0thorder term. Note that the number of coefficients depends on the order of the curve - there areexactly n+1 coefficients for a curve of order n. The parameter list for LSET includes a curvetype and associated coefficients for the currently selected range of each currently selectedanalyzer. See :CALibration:LINearize:CURVe:FIT for examples.

Note that the :CALibration:LINearize:ACCept command sets the parameter values.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-12 SENSe:CONCentration

At *RST these values are device dependent.

18.4.4 :RANGe:SENSe:CONCentration:RANGe

This node allows the setting of a specific range or turns off/on auto-ranging mode for thepre-selected instrument(s).

18.4.4.1 :AUTO:SENSe:CONCentration:RANGe:AUTO

The AUTO command controls the automatic range switching feature.

18.4.4.1.1 :LOWer <numeric_value> :SENSe:CONCentration:RANGe:AUTO:LOWer

This command specifies or queries the lower CONCentration(s) in ppm for automaticranging for the selected instrument(s). When a CONCentration is decreasing, this value isthe switch point for this range.

At *RST, these values are not changed.

18.4.4.1.2 [:STATe] <Boolean>:SENSe:CONCentration:RANGe:AUTO[:STATe]

The STATe command turns the automatic range switching feature on or off. In automaticrange mode, the instrument will switch ranges to keep the measured values within the limitsdefined in SENSe:CONCentration:RANGe:AUTO:LOWer and :UPPer. Turning AUTO offwill keep the device at the current range.

At *RST, the STATe is device-dependent.

18.4.4.1.3 :UPPer <numeric_value> :SENSe:CONCentration:RANGe:AUTO:UPPer

This command specifies or queries the upper CONCentration(s) in ppm for automaticranging for the selected instrument(s). When a CONCentration is increasing, this value is theswitch point for this range.

At *RST, these values are not changed.

18.4.4.2 [:FIXed] <numeric_value> :SENSe:CONCentration:RANGe:FIXed

This command specifies or queries the range number of the already-selected instrument(s).The instrument(s) will continue to measure in this range until a subsequent range commandchanges the range(s). If auto-ranging is enabled, it will be disabled upon specifying range(s)with this command, but will remain unchanged if the range(s) are queried with thiscommand.

At *RST, the settings of :FIXed are device-dependent.

18.4.5 :TALign <numeric_value>:SENSe:CONCentration:TALign <numeric_value>

Sets (or queries) the time delay in seconds for the Time Alignment of the continuouslymeasured data.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CONCentration 18-13


18.4.6 :UPPer <numeric_value>:SENSe:CONCentration:UPPer

This command specifies or queries the full scale concentration for the currently-selectedrange for the selected instrument(s).


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-14 SENSe:CONCentration

18.5 CONDition SubsystemSENSe:CONDition

This subsystem controls the electrical characteristics of a sensor that determines the ON orOFF condition of a digital signal.

KEYWORD PARAMETER FORM COMMENTS:CONDition 1993 PH074 LEVel <numeric_value> | TTL | ECL 1993 PH074

18.5.1 :LEVel <numeric_value> | TTL ECLSENSe:CONDition:LEVel

This command specifies the characteristics that causes the transition between an ON andOFF condition of the sensed signal. When the value of the input signal exceeds the specifiedlevel, the condition is qualified as ON or 1 (True) for positive logic type, and qualified asOFF or 0 (False) when it is associated with negative types of logic. For positive logic, thecondition is sensed as OFF or 0 (False) when the input value is below the level; for negativelogic this value is qualified as an ON or 1 (True) condition.

The default units are the amplitude units associated with the currently sensed signal.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CONDition 18-15

18.6 CORRection SubsystemSENSe:CORRection

The correction subsystem provides for known external losses or gains. In contrast toCALibration, these losses usually are dependent on individual measurement setups.

Correction data may be entered and stored in several ways. A mechanism is provided toautomatically measure a reference standard(s) and store the resulting “correction set” in atrace. The trace can be selected at any time as the active “correction set”. This trace couldalso be generated by an external device and transferred to the instrument over a computerinterface. Commands are also provided to enter individual losses, gains, offsets, delays, etc.that the instrument should use in correcting the data. An instrument is not required toimplement all of the methods.

The commands in this subsystem are designed to correct for losses, gains, and offsets inexternal probes or transducers. For instance, they can be used to inform the sensor that a 10Xprobe has been attached to the instrument. This way, the data and measurement results willbe corrected so that they are not 1/10th their actual value. In instruments that automaticallydetect the attachment of a probe, these commands may not be necessary.

KEYWORD PARAMETER FORM COMMENTS:CORRection :AUTO [event] 1999 :CALCulate [event] 1999 :COLLect [:ACQuire ] STANdard :METHod TPORt :SAVE <trace_name> :CSET [:SELect] <name> 1992 HP058A

:STATe <Boolean> :EDELay :DISTance <numeric_value> :STATe <Boolean> [:TIME] <numeric_value> :IMPedance 1993 HP084 [:INPut]|:OUTPut 1993 HP084 [:MAGNitude] <numeric_value> 1993 HP084 :STATe <Boolean> 1993 HP084 :LOSS|:GAIN|:SLOPe [:INPut]|:OUTPut 1992 :AUTO ON|OFF [:MAGNitude] <numeric_value> :PHASe <numeric_value> :STATe <Boolean> :OFFSet [:MAGNitude] <numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-16 SENSe:CORRection

KEYWORD PARAMETER FORM COMMENTS :PHASe <numeric_value> :STATe <Boolean> :RVELocity :COAX <numeric_value> :MEDium COAX|WAVeguide :STATe <Boolean> :WAVeguide <numeric_value> :FCUToff <numeric_value> :SPOint 1999 :ACQuire [event] 1999 :DTOLerance <numeric_value> 1999 [:STATe] <Boolean> :ZERO 1999 :ACQuire [event] 1999 :DTOLerance <numeric_value> 1999

18.6.1 :AUTO:SENSe:CORRection:AUTO

AUTO performs an automatic correction of the selected instruments. The procedure shall bedefined according to the manufacturer’s recommended procedure. This command is an eventand therefore has no *RST value associated with it.

18.6.2 :CALCulate:SENSe:CORRection:CALCulate

If a calculation is needed for the CORRection subsystem, this command initiates thecalculation.

This command is an event, and has no *RST value.

18.6.3 :COLLectSENSe:CORRection:COLLect

Deals with the collection of the correction data. This data is collected directly by the deviceby measurements of standards.

18.6.3.1 [:ACQuire] STANdardSENSe:CORRection:COLLect:ACQuire

A measurement will be performed and saved as the data for standard of the chosencorrection method. The number of standards required to be measured for the correction isdetermined by the method chosen. If a standard is specified that does not exist in the chosenmethod, then an error is generated and no measurement is taken. This measurement will notaffect any of the users settings for regular measurements.

For complex corrections, several standards will be measured and then followed by a SAVEcommand. The parameter on the save command will be the name of the correction set.Thestandards themselves are device-specific.

This command is an event, does not have a *RST value, and is not queryable.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CORRection 18-17

18.6.3.2 :METHod TPORtSENSe:CORRection:COLLect:METHod

Selects the correction method to be used for the correction that is about to be performed. Ifonly one correction method exists in the instrument then this command is not required.

The various settings of the parameters have the following meanings:

TPORt Two Port


18.6.3.3 :SAVE [<trace_name>]SENSe:CORRection:COLLect:SAVE

Calculates the correction data using the current method selection and then saves thecorrection data. If only one correction array exists then it is saved there. Otherwise it is savedin the set specified by <trace_name>. Note that the parameter <trace_name>must be definedand exist in the instrument. This command will not create a trace. Trace definition is done inthe trace subsystem. Note that the correction array may be a single value.

Depending on the complexity of the correction method chosen, a calculation may or may notbe performed on the measured arrays to determine the correction data. For example, if thechosen method has only one standard, then no calculation will be performed.

This command is an event, does not have a *RST value, and is not queryable.

18.6.4 :CSETSENSe:CORRection:CSET

The Correction SET subsystem is used to select the active correction set.

18.6.4.1 [:SELect] <name>SENSe:CORRection:CSET:SELect

HP058A

Specifies the active CORRection set. This is the set that is used when CORR:CSET:STATeON is specified. <name> may be either a <trace_name>, or a <table_name> which must bedefined and exist in the instrument. This command will not create either <trace_name>, or a<table_name>. Trace definition is done in the TRACe subsystem. Table definition is done inthe MEMory subsystem.

HP058A

If <table_name> specifies a MEMory:TABLe the various lists must have an equal number ofpoints, or execution error -226 (Lists not same length) will be generated.

HP058A

Those lists in a TABLe which are defined in the CORRection subsystem will be appliedwhen CORRection:STATe is ON. Other items in a TABLe will be ignored withoutgenerating an error. This allows the same TABLe to be shared with other subsystems.

HP058A


18.6.4.2 :STATe <Boolean>SENSe:CORRection:CSET:STATe

Determines whether the correction data defined in the selected set is applied to themeasurement.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



At *RST, this function is OFF. Off is chosen because all of the correction sets may beempty. The instrument must collect data before correction can be applied.

18.6.5 :EDELaySENSe:CORRection:EDELay

The Electrical DELay is used to compensate for delays in the signal path.

This command is used to correct external factors that the instrument cannot measure ordetect.

TIME and DISTance are coupled by the equation:TIME= RVELocity*DISTance

RVELocity is not coupled to either TIME or DISTance.

18.6.5.1 :DISTance <numeric_value>SENSe:CORRection:EDELay:DISTance

This command will set the electrical delay with the distance parameter given. The effectivedelay will be computed using this parameter and the relative velocity set in the instrument.The units for this command are meters. A value accepted here will modify the time settingbecause they are the same parameter in different forms. Implementation of this commandrequires implementation of CORRection:EDELay[:TIME].

At *RST, the value of this setting is zero.

18.6.5.2 :STATe <Boolean>SENSe:CORRection:EDELay:STATe

This function is used to enable or disable the electrical delay correction.

At *RST, this function is set to OFF.

18.6.5.3 [:TIME] <numeric_value>SENSe:CORRection:EDELay:TIME

This command will set the electrical delay with the time parameter given. The units for thiscommand are seconds. A value accepted here will modify the distance setting because theyare the same parameter in different forms.


18.6.6 :IMPedanceSENSe:CORRection:IMPedance

This is the termination impedance provided external to the device.HP084

18.6.6.1 [:INPut]|:OUTPutSENSe:CORRection:IMPedance:INPut HP084The INPut and OUTPut nodes are used to reference measurements made at the instrument’sinput and output, respectively. Most sensor instruments are only capable of makingmeasurements at its input ports; however, some instruments are capable of makingmeasurements on output ports that are sourcing a signal.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.6.6.1.1 [:MAGNitude] <numeric_value>SENSe:CORRection:IMPedance:INPut:MAGNitude HP084Sets the magnitude of the impedance. The default units are Ohms

At *RST, this value is device-dependant.

18.6.6.2 :STATe <Boolean>SENSe:CORRection:IMPedance:STATe HP084The STATe command is used to enable or disable external IMPedance correction factors.


18.6.7 :LOSS|:GAIN|:SLOPeSENSe:CORRection:LOSS

These commands are used either to provide a mechanism to apply simple correction or tocorrect external factors that have not been accounted for in the correction set. Thesecorrection factors are typically applied to measurements made at the device input; however,in cases where measurements can be at the device output a separate set of correction factorsmay be applied.

Loss, gain and slope effect the measurement values as a multiplier for linear units such asVOLT and as additive (or subtractive) value for logarithmic units such as DB.

:LOSS This command is used to set the anticipated loss in the system, excluding thosefactors covered by the active correction set. The device then corrects everymeasurement by this factor to compensate for the loss. LOSS is coupled to GAINby the equation LOSS = 1/GAIN when the default unit is linear andLOSS=-GAIN when the default unit is logarithmic.

:GAIN This command is used to set the anticipated gain in the system, excluding thosefactors covered by the active correction set. The device then corrects everymeasurement by this factor to compensate for the gain. GAIN Is coupled to LOSSby the equation GAIN=1/LOSS when the default unit is linear and GAIN=-LOSSwhen the default unit is logarithmic.

:SLOPe This node defines an increasing or decreasing value that is added to the signal.This correction value is zero at a zero value of the x axis and increase ordecreases from there.

HP075

18.6.7.1 [:INPut]|:OUTPutSENSe:CORRection:LOSS:INPut

The INPut and OUTPut nodes are used to reference measurements made at the instrument’sinput and output, respectively. Most sensor instruments are only capable of makingmeasurements at its input ports; however, some instruments are capable of makingmeasurements on output ports that are sourcing a signal.

18.6.7.1.1 :AUTO ON|OFFSENSe:CORRection:LOSS:INPut:AUTO

When AUTO is ON the OUTPut correction values must track those of the INPut.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



At *RST, AUTO is set to ON.

18.6.7.1.2 [:MAGNitude] <numeric_value>SENSe:CORRection:LOSS:INPut:MAGNitude

This is the magnitude value of the correction data for LOSS, GAIN or SLOPe. The unitsassociated with LOSS and GAIN are the current relative amplitude unit. The unit associatedwith SLOPe is:

<current realtive amplitude unit>/Hz

After a *RST, this value should no longer affect the data being measured. Thus its value isset to zero at *RST.

18.6.7.1.3 :PHASe <numeric_value>SENSe:CORRection:LOSS:INPut:PHASe

This is the phase value of the correction data for LOSS, GAIN or SLOPe. The unitassociated with SLOPe is current angle units/Hertz. The units associated with LOSS andGAIN are current angle units.

After a *RST, this value should no longer affect the data being measured. Thus its value isset to zero at *RST.

18.6.7.2 :STATe <Boolean>SENSe:CORRection:LOSS:STATe

The STATe command is used to enable or disable the LOSS, GAIN or SLOPe correctionfactors.


18.6.8 :OFFSetSENSe:CORRection:OFFSet

This node defines a single value that is added to every point measured by the instrument. Ifthe instrument is a trace-based machine, then this value is added to every point in the trace.If the instrument measures a single value then that value is modified by this setting. Thiscommand shall be used with the currently selected units. It is used to correct external factorsthat the instrument cannot measure or detect.

18.6.8.1 [:MAGNitude] <numeric_value>SENSe:CORRection:OFFSet:MAGNitude

This is the magnitude value of the correction offset data.

After a *RST, this value should no longer affect the data being measured. Its value is set tozero at *RST.

18.6.8.2 :PHASe <numeric_value>SENSe:CORRection:OFFSet:PHASe

This is the phase value of the correction offset data. The units associated with this are thecurrently selected angle units.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.6.8.3 :STATe <Boolean>SENSe:CORRection:OFFSet:STATe

This function is used to enable or disable the offset correction.


After a *RST, this value should no longer affect the data being measured. Its value is set tozero at *RST .

18.6.9 :RVELocitySENSe:CORRection:RVELocity

This command corrects for the relative velocity of the medium of the Device Under Test.This factor will be used in any delay calculation performed in the instrument.

This command is used to correct external factors that the instrument cannot measure ordetect.

TIME and DISTance are coupled by the equation:TIME= RVELocity*DISTance


18.6.9.1 :COAX <numeric_value>SENSe:CORRection:RVELocity:COAX

This command sets the relative velocity factor for coaxial lines. The parameter is unitless.


18.6.9.2 :MEDium COAX|WAVeguideSENSe:CORRection:RVELocity:MEDium

This command selects the correction algorithm for the media through which the detectedsignal is transmitted. It will determine the method of calculation for any operation that usesrelative velocity. For example, for COAX a linear phase shift would be computed if a delaywas added, but for WAVeguide (a dispersive medium) a different phase shift is calculated.


18.6.9.3 :STATe <Boolean>SENSe:CORRection:RVELocity:STATe

This function is used to enable or disable the relative velocity correction.


18.6.9.4 :WAVeguide <numeric_value>SENSe:CORRection:RVELocity:WAVeguide

This command sets the relative velocity factor for waveguide. The parameter is unitless.


18.6.9.4.1 :FCUToff <numeric_value>SENSe:CORRection:RVELocity:WAVeguide:FCUToff

This command specifies the frequency cutoff of the waveguide medium. The units are Hertz.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




18.6.10 :SPOint:SENSe:CORRection:SPOint

This subsystem controls the set point correction of the sensor.

For Emissions benches, this subsystem references the span gas of the instrument.

This command is an event and therefore has no *RST value associated with it.

18.6.10.1 :ACQuire:SENSe:CORRection:SPOint:ACQuire

This command supplies a known signal to the selected instruments and waits for thestabilization criteria to be met..

This command is an event, and has no *RST value.

18.6.10.2 :DTOLerance <numeric_value>:SENSe:CORRection:SPOint:DTOLerance

This command specifies or queries the drift tolerance for a set point correction procedure forthe current range of the selected instrument(s).

For emission benches, this tolerance is the difference between the specified concentrationreferenced in the SpanGas and GasBottle tables and the measured concentration. Drifttolerance is in units of percent of full scale value.

The data defined and queried will only apply to the currently selected range of the currentlyselected instrument(s).

At *RST, this value is not changed.

18.6.11 [:STATe] <Boolean>SENSe:CORRection:STATe

Determines whether the correction data defined in this section is applied to the measurement.


18.6.12 :ZERO:SENSe:CORRection:ZERO

This subsystem controls the zero correction of the sensor.

18.6.12.1 :ACQuire:SENSe:CORRection:ZERO:ACQuire

This command sends a zero signal to the selected instruments and waits for the stabilizationcriteria to be met.

This command is an event, and has no *RST value

18.6.12.2 :DTOLerance <numeric_value>:SENSe:CORRection:ZERO:DTOLerance

This command specifies the drift tolerance for a zero procedure for the selectedinstrument(s).

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



At *RST, this value is not changed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.7 CURRent SubsystemSENSe:CURRent

This subsection controls the current amplitude characteristics of the sensor.

KEYWORD PARAMETER FORM NOTES:CURRent :AC|[:DC] :APERture <numeric_value> :NPLCycles <numeric_value> 1991 :ATTenuation <numeric_value> :AUTO <Boolean> :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only] :CLEar [no query] :RANGe [:UPPer] <numeric_value> :LOWer <numeric_value> :AUTO <Boolean>|ONCE :DIRection UP|DOWN|EITHer :LLIMit <numeric_value> 1996 :ULIMit <numeric_value> 1996 :OFFSet 1991 :PTPeak 1991 :REFerence <numeric_value> :STATe <Boolean> :RESolution <numeric_value> :AUTO <Boolean>|ONCE :DETector INTernal | EXTernal 1991

18.7.1 :AC|[:DC]SENSe:CURRent:AC

This subsystem selects the alternating current or the direct current sensor. The default unitsare amperes.

18.7.1.1 :APERture <numeric_value>SENSe:CURRent:AC:APERture

Specifies the acquisition/sampling/gate time for a single measurement point. The parameterhas a unit of seconds.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CURRent 18-25

18.7.1.2 :NPLCycles <numeric_value>SENSe:CURRent:AC:NPLCycles

Specifies the acquisition/sampling/gate time for a single measurement point in terms of thenumber of power line cycles. The parameter is unitless. If this command is implemented, theAPERture command must also be implemented.

The value is coupled to APERture by the equation:APERture = NPLCycles/selected line frequency


18.7.1.3 :ATTenuation <numeric_value>SENSe:CURRent:AC:ATTenuation

Sets the ATTenuation level. Note that when setting the level to 10 dB the magnitude of theincoming signal will be decreased by 10 dB. Changing the ATTenuation changes RANGe bythe same amount.

Default units are as determined in the UNITS system.

18.7.1.3.1 :AUTO <Boolean>SENSe:CURRent:AC:ATTenuation:AUTO

Couples the attenuator to RANGe such that maximum dynamic range of the incoming signalis assured without overloading.

Programming a specified attenuation sets AUTO OFF.


18.7.1.4 :PROTectionSENSe:CURRent:AC:PROTection

Controls the protection circuits.

18.7.1.4.1 [:LEVel] <numeric_value> SENSe:CURRent:AC:PROTection:LEVel

This command sets the input level at which the input protection circuit will trip.

18.7.1.4.2 :STATe <Boolean> SENSe:CURRent:AC:PROTection:STATe

Controls whether the input protection circuit is enabled.


18.7.1.4.3 :TRIPped?SENSe:CURRent:AC:PROTection:TRIPped?


18.7.1.4.4 :CLEarSENSe:CURRent:AC:PROTection:CLEar



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-26 SENSe:CURRent

18.7.1.5 :RANGeSENSe:CURRent:AC:RANGe

Sets the range for the amplitude sensor function. The RANGe endpoints may be specified interms of the UPPer endpoint and the LOWer endpoint, alternatively the midpoint of theRANGe (OFFSet) and the span of the RANGe (PTPeak) may be used. A non-symmetricalrange around zero may cause some instruments to introduce an actual offset to the signalentering the SENSe block.

18.7.1.5.1 [:UPPer] <numeric_value>SENSe:CURRent:AC:RANGe:UPPer

Specifies the most positive signal level expected for the sensor input.


18.7.1.5.2 :LOWer <numeric_value>SENSe:CURRent:AC:RANGe:LOWer

Specifies the most negative signal level expected for the sensor input. This allows setting forthe best dynamic range. This function is coupled to UPPer in a device-dependent manner.


18.7.1.5.3 :AUTO <Boolean>|ONCESENSe:CURRent:AC:RANGe:AUTO

Sets the RANGe to the value determined to give the most dynamic range withoutoverloading. The actual algorithm is device-dependent.


18.7.1.5.3.1 :DIRection UP|DOWN|EITHerSENSe:CURRent:AC:RANGe:AUTO:DIRection

The DIRection command defines the manner in which AUTO works. When UP is selected,the instrument shall only change the range automatically to ranges larger than the currentrange, as the input signal dictates. When DOWN is selected, the instrument shall onlychange the range automatically to ranges smaller than the current range, as the input signaldictates. When EITHer is selected the instrument may range in either direction.

At *RST, DIRection shall be set to EITHer.

18.7.1.5.3.2 :LLIMit <numeric_value>SENSe:CURRent:AC:RANGe:AUTO:LLIMit

The Lower LIMit command sets the smallest range to which the instrument will go whileautoranging. When AUTO is ON and the present RANGe is outside the new limits, theinstrument may change the RANGe to a value inside the limits or wait until the next time theautoranging algorithm is performed.

At *RST, LLIMit shall be set to MINimum.

18.7.1.5.3.3 :ULIMit <numeric_value>SENSe:CURRent:AC:RANGe:AUTO:ULIMit

The Upper LIMit command sets the largest range to which the instrument will go while

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CURRent 18-27

autoranging. When AUTO is ON and the present RANGe is outside the new limits, theinstrument may change the RANGe to a value inside the limits or wait until the next time theautoranging algorithm is performed.

At *RST, ULIMit shall be set to MAXimum.

18.7.1.5.4 :OFFSet <numeric_value>SENSe:CURRent:AC:RANGe:OFFSet

OFFSet determines the midpoint of the range.


18.7.1.5.5 :PTPeak <numeric_value>SENSe:CURRent:AC:RANGe:PTPeak

Peak To Peak specifies the dynamic range required for the sensor.


18.7.1.6 :REFerence <numeric_value>SENSe:CURRent:AC:REFerence

Sets a reference amplitude for sensor instruments. This command differs in intent from thereference correction in that this is intended to be a measurement offset where a user wishesto reference a measurement to some known value.

At *RST, this value is device-dependent, but STATe is set to OFF.

18.7.1.6.1 :STATe <Boolean>SENSe:CURRent:AC:REFerence:STATe

Determines whether amplitude is measured in absolute or relative mode. If STATe is ON,then amplitude is referenced to the value set in REFerence.


18.7.1.7 :RESolution <numeric_value>SENSe:CURRent:AC:RESolution

Specifies the absolute resolution of the measurement. For example, if a measurement of 10Volts is specified with a resolution of .01 Volts, the measurement is returned with aresolution of .01 Volts (that is, 10.00).

RANGe is not coupled to RESolution. Setting RANGe shall not cause RESolution tochange. Setting RESolution shall not cause RANGe to change.


18.7.1.7.1 :AUTO <Boolean>|ONCESENSe:CURRent:AC:RESolution:AUTO

Allows the system to determine the best resolution for the other measurement conditions.

Explicitly setting a value for :RESolution will turn AUTO OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-28 SENSe:CURRent

18.7.2 :DETector INTernal | EXTernalSENSe:CURRent:DETector

The DETector can be specified as internal or external.

At *RST, this value is set to INT. 1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:CURRent 18-29

18.8 DETector SubsystemSENSe:DETector

This subsystem controls the acquisition of data points, including how to choose points andthe linear characteristics of the sensor.

KEYWORD PARAMETER FORM NOTES:DETector :BANDwidth <numeric_value> 1991 |:BWIDth 1991 [:FUNCtion] GROund|NEGative|POSitive|SAMPle|SIGNal

|PAVerage | AAVerage|RMS 1991 :AUTO <Boolean>|ONCE :SHAPe LINear|LOGarithmic

18.8.1 :BANDwidth | BWIDth <numeric_value>

SENSe:DETector:BANDwidth

The BANDwidth function controls the bandwidth after an intermediate signal has beenprocessed within the SENSe block. Instruments must accept both forms, if they accept either.

18.8.2 [:FUNCtion] <detector function>SENSe:DETector:FUNCtion

Specifies the detector sampling characteristics. The various settings have the followingmeanings:

GROund: The input detector is grounded. Thus no signal is acquired.

NEGative: The minimum signal detected during the acquisition of the particularpoint is chosen.

POSitive: The maximum signal detected during the acquisition of the particularpoint is chosen.

SAMPle: A single arbitrary point detected is chosen.

SIGNal: The detector chooses points so that envelope noise is maximized andpositive signals above some threshold are also maximized.

PAVerage: PeakAVerage is the average of the minimum and maximumexcursions of the signal. PAV = ( absolute minimum peak + absolute maximumpeak) / 2

AAVerage: AbsoluteAVerage averages the absolute values of a sine wave inputand processes the value to read RMS values.

RMS: True Root Mean Square signal detector.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-30 SENSe:DETector

18.8.2.1 :AUTO <Boolean>|ONCESENSe:DETector:FUNCtion:AUTO

Couples the detector function to several settings within the instrument. When AUTO ON isselected, the detector type is determined by the system in order to give the “best” quality ofdata.

Explicitly selecting a detector will set AUTO OFF.

At *RST, this parameter is set to ON.

18.8.3 :SHAPe LINear|LOGarithmicSENSe:DETector:SHAPe

Controls the linearity of the detector. This setting is coupled to DETector:FUNCtion in adevice-dependent manner.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:DETector 18-31

18.9 DISTance SubsystemSENSe:DISTance

This node is used to set the parameters associated with sensing distance.

KEYWORD PARAMETER FORM NOTES:DISTance 1999 :RESet [event; no query]1999

18.9.1 :RESet:SENSe:DISTance:RESet

This command will set DISTance to 0. This command is not queryable.

At *RST the DISTance is set to zero.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-32 SENSe:DISTance

18.10 FILTer SubsystemSENSe:FILTer

The FILTer function allows a filter to be inserted after an intermediate signal has beenprocessed within the SENSe block. This FILTer subsystem is not interchangeable with theINPut:FILTer subsystem.

KEYWORD PARAMETER FORM NOTES:FILTer 1991 [:LPASs] 1991 [:STATe] <Boolean> 1991 :FREQuency <numeric_value> 1991 :HPASs 1991 [:STATe] <Boolean> 1991 :FREQuency <numeric_value> 1991 :DEMPhasis 1991 [:STATe] <Boolean> 1991 :TCONstant <numeric_value> 1991 :CCITt 1991 [:STATe] <Boolean> 1991 :CMESsage 1991 [:STATe] <Boolean> 1991 :CCIR 1991 [:STATe] <Boolean> 1991 :CARM 1991 [:STATe] <Boolean> 1991 :AWEighting 1991 [:STATe] <Boolean> 1991

18.10.1 [:LPASs]SENSe:FILTer:LPASs

Controls the sensor low pass filter.

18.10.1.1 [:STATe] <Boolean>SENSe:FILTer:LPASs:STATe

Turns the low pass filter on and off.


18.10.1.2 :FREQuency <numeric_value>SENSe:FILTer:LPASs:FREQuency

Determines the cutoff frequency of the low pass filter.


18.10.2 :HPASsSENSe:FILTer:HPASs

Controls the sensor high pass filter.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:FILTer 18-33

18.10.2.1 [:STATe] <Boolean>SENSe:FILTer:HPASs:STATe

Turns the high pass filter on and off.


18.10.2.2 :FREQuency <numeric_value>SENSe:FILTer:HPASs:FREQuency

Determines the cutoff frequency of the high pass filter.


18.10.3 :DEMPhasisSENSe:FILTer:DEMPhasis

Controls the sensor FM De-EMPhasis filter. De-emphasis filters compensate forpre-emphasis on FM signals.

18.10.3.1 [:STATe] <Boolean>SENSe:FILTer:DEMPhasis:STATe

Turns the FM de-emphasis filter on and off.


18.10.3.2 :TCONstant <numeric_value>SENSe:FILTer:DEMPhasis:TCONstant

Determines the Time CONstant of the FM de-emphasis filter. The default units are inseconds.


18.10.4 :CCITtSENSe:FILTer:CCITt

Controls the CCITT sensor filter. This standard filter is described in “CCITTRecommendation P53". It is a voice bandwidth filter used in radio or telephone applications.

18.10.4.1 [:STATe] <Boolean>SENSe:FILTer:CCITt:STATe

Turns the CCITT filter on and off.


18.10.5 :CMESsageSENSe:FILTer:CMESsage

Controls the C-Message sensor filter. This Bell Telephone standard filter is described in “PerBTSM 41004". It is a voice bandwidth filter used in radio or telephone applications.

18.10.5.1 [:STATe] <Boolean>SENSe:FILTer:CMESsage:STATe

Turns the C-Message filter on and off.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-34 SENSe:FILTer

18.10.6 :CCIRSENSe:FILTer:CCIR

Controls the CCIR weighting sensor filter. This standard filter is described in “CCIRRecommendation 468-2”. It is a music bandwidth filter used in applications such asbroadcasting and FM receivers.

18.10.6.1 [:STATe] <Boolean>SENSe:FILTer:CCIR:STATe

Turns the CCIR weighting filter on and off.


18.10.7 :CARMSENSe:FILTer:CARM

Controls the CCIR/ARM weighting sensor filter. This is a standard music bandwidth filterdescribed in “CCIR Recommendation 468-2” and “Dolby Labs Bulletin No. 19/4”.

18.10.7.1 [:STATe] <Boolean>SENSe:FILTer:CARM:STATe

Turns the CCIR/ARM weighting filter on and off.


18.10.8 :AWEightingSENSe:FILTer:AWEighting

Controls the “A” weighting sensor filter. This is a human hearing compensation filterdescribed in “IEC Recommendation 179” and “ANSI S1.4”.

18.10.8.1 [:STATe] <Boolean>SENSe:FILTer:AWEighting:STATe

Turns the “A” weighting filter on and off.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:FILTer 18-35

18.11 FM SubsystemSENSe:FM

RS011The Frequency Modulation subsystem is used to set up the modulation controls andparameters associated with sensing and demodulating frequency modulated signals.

KEYWORD PARAMETER FORM NOTES:FM 1991 [:DEViation] 1991 :RANGE 1991 :AUTO <Boolean>|ONCE 1991 [:UPPer] <numeric_value> 1991 :LOWer <numeric_value> 1991

18.11.1 [:DEViation]SENSe:FM:DEViation

This node is used to collect together the deviation parameters.

18.11.1.1 :RANGeSENSe:FM:DEViation:RANGe


18.11.1.1.1 :AUTO <Boolean> | ONCESENSe:FM:DEViation:RANGe:AUTO



18.11.1.1.2 [:UPPer] <numeric_value>SENSe:FM:DEViation:RANGe:UPPer



18.11.1.1.3 :LOWer <numeric_value>SENSe:FM:DEViation:RANGe:LOWer



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-36 SENSe:FM

18.12 FREQuency SubsystemSENSe:FREQuency

The FREQuency subsystem controls the frequency characteristics of the instrument. Twotypes of controls are included in this subsystem. The first is frequency sensor controls, suchas RANGe. The second is frequency sweep controls, such as STARt, or tuning controls suchas CW.

Unless otherwise noted, the default unit for all <numeric_values> in this subsystem are in Hz.

KEYWORD PARAMETER FORM NOTES:FREQuency <numeric_value> :APERture <numeric_value> :CENTer <numeric_value> [:CW|:FIXed] <numeric_value>

RS012 :AFC <Boolean>|ONCE 1994 :AUTO <Boolean>|ONCE :MANual <numeric_value> :MODE CW|FIXed|SWEep|LIST|SOURce :MULTiplier <numeric_value> :OFFSet <numeric_value> :RANGe [:UPPer] <numeric_value> :LOWer <numeric_value> :AUTO <Boolean>|ONCE :RESolution <numeric_value> :AUTO <Boolean>|ONCE :SPAN <numeric_value> :HOLD <Boolean> :LINK CENTer|STARt|STOP :FULL [no query] :STARt <numeric_value> :STOP <numeric_value>

18.12.1 :APERture <numeric_value>SENSe:FREQuency:APERture



18.12.2 :CENTer <numeric_value>SENSe:FREQuency:CENTer

Set the center frequency of the sweep or measurement.

At *RST, this function will be set to (MINimum+MAX)/2.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:FREQuency 18-37

18.12.3 [:CW|:FIXed] <numeric_value>SENSe:FREQuency:CW

The Continuous Wave or FIXed node is used to select a frequency of a non-swept signal.This node is optional. An optional node, such as [:CW|:FIXed], implies that the device shallaccept and process commands with or without the optional node and have the same result.That is, the device is required to accept the optional node, if sent, without error. A devicemust accept both :CW and :FIXed if it implements this node.


RS01218.12.3.1 :AFC <Boolean>|ONCESENSe:FREQuency:CW:AFC

If AFC is ON the sensor is coupled to the frequency of the signal. The default frequency isdetermined by SENSe:FREQuency[:CW].

The actual value of FREQuency[:CW] is adjusted to match the frequency of the signal. Thequery FREQuency[:CW]? returns the adjusted value, not the value sent with the lastFREQuency[:CW] command.


18.12.3.2 :AUTO <Boolean>|ONCESENSe:FREQuency:CW:AUTO

Couples the CW frequency to center frequency. Explicitly setting FREQuency:CW will setAUTO OFF.


18.12.4 :MANual <numeric_value>SENSe:FREQuency:MANual

Same as CW except limited by STARt and STOP. This command only affects the frequencyif SENSe:SWEep:MODE MANual and SENSe:FREQuency:MODE SWEep are selected. Ifthe sweep limits are changed such that manual frequency would be outside the sweep limits,then the manual frequency will be set to the nearest end point of the sweep.


18.12.5 :MODE CW|FIXed|SWEep|LIST|SOURceSENSe:FREQuency:MODE

Determines which set of commands control the frequency. If CW or FIXed is selected, thefrequency is determined by FREQuency:CW. CW and FIXed are aliases. Both must beimplemented if either is implemented. If SWEep is selected, the sensor is in the swept modeand frequency is determined by FREQuency:STARt, STOP, CENT, SPAN, and MAN. IfLIST is selected, the frequencies are determined by LIST:FREQuency.

If SOURce is selected, the sensor is coupled to the source. All frequency controls aredetermined by the SOURCe:FREQuency block, except for OFFSet and MULTiplier. Thesetwo commands remain active under SENSe to allow for offset and harmonic tracking.

At *RST, this value is set to CW.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-38 SENSe:FREQuency

18.12.6 :MULTiplier <numeric_value>SENSe:FREQuency:MULTiplier

Sets a reference multiplier for all other frequency settings in the instrument. All entered anddisplayed frequencies are affected by this command. The coupling equation is:

Entered|Displayed frequency = (Hardware frequency * multiplier) + offset.

This command affects the values of all functions which affect sensing of the signal. Thisincludes such things as CW frequency and the sweep frequency controls. It does not affectthings like input filter bandwidths. It does affect the settings of relative frequency parameterssuch as delta markers or FM deviation. Also note that this command does not affect thehardware settings of the instrument, but only the entered and displayed frequencies.


18.12.7 :OFFSet <numeric_value>SENSe:FREQuency:OFFSet

Sets a reference frequency for all other absolute frequency settings in the instrument. Thiscommand affects the values of all functions which affect sensing of the signal. This includessuch things as CW frequency and the sweep frequency controls. It does not affect things likeinput filter bandwidths. It also does not affect the settings of relative frequency parameterssuch as delta markers or SPAN. Also note that this command does not affect the hardwaresettings of the instrument, but only the entered and displayed frequencies. The couplingequation is:

Entered|Displayed frequency = (Hardware frequency * multiplier) + offset.


18.12.8 :RANGeSENSe:FREQuency:RANGe

Sets the frequency range for the sensor function.

18.12.8.1 [:UPPer] <numeric_value>SENSe:FREQuency:RANGe:UPPer

Specifies the maximum value expected for the sensor input.


18.12.8.2 :LOWer <numeric_value>SENSe:FREQuency:RANGe:LOWer

Specifies the lowest value expected for sensor input.This function is coupled to UPPer in adevice-dependent manner.


18.12.8.3 :AUTO <Boolean>|ONCESENSe:FREQuency:RANGe:AUTO

Sets the RANGe to the value determined by the instrument.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.12.9 :RESolution <numeric_value>SENSe:FREQuency:RESolution

Specifies the absolute resolution of the frequency measurement. For example, if ameasurement of 10 MHZ is made with a resolution of .01, the measurement is returned witha resolution of .01 Hz (that is, 10000000.00Hz)


18.12.9.1 :AUTO <Boolean>|ONCESENSe:FREQuency:RESolution:AUTO


Explicitly selecting a value for FREQuency:RESolution will set AUTO OFF.


18.12.10 :SPAN <numeric_value>SENSe:FREQuency:SPAN

Sets the frequency span.

At *RST, this function will be set to MAXimum.

18.12.10.1 :HOLD <Boolean>SENSe:FREQuency:SPAN:HOLD

Provides a mechanism to prevent the SPAN from being changed implicitly by the definedcoupling between STARt, STOP, CENTer and SPAN. When HOLD is set to ON, SPANshall only be changed by explicitly sending the SPAN command.


18.12.10.2 :LINK CENTer|STARt|STOPSENSe:FREQuency:SPAN:LINK

Allows the default couplings for SPAN to be overridden. LINK selects the parameter, eitherCENTer, STARt or STOP, that shall not be changed when SPAN’s value is changed. Forexample, if LINK is set to STARt, then changing SPAN shall cause CENTer and STOP, notSTARt, to change.

At *RST, this value is set to CENTer, to be compatible with the default definition for thecouplings.

18.12.10.3 :FULLSENSe:FREQuency:SPAN:FULL

When this command is received, start frequency is set to its minimum value, and stopfrequency is set to its maximum value. Center frequency and span are set to their coupledvalues.

This command is an event. Therefore it has no associated query, or meaning at *RST.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-40 SENSe:FREQuency

18.12.11 :STARt <numeric_value>SENSe:FREQuency:STARt

Sets the starting frequency for a sweep or measurement. It also sets one limit of a manualfrequency adjustment. If the instrument does not support negative frequency span, having thestart frequency greater than the stop frequency will cause an error to be generated.

At *RST, the parameter will be set to MINimum.

18.12.12 :STOP <numeric_value>SENSe:FREQuency:STOP

Sets the stop frequency of a sweep or measurement. It also sets the other limit of a manualsweep adjustment. If the instrument does not support negative frequency span, having thestop frequency less than the start frequency will cause an error to be generated.

At *RST, this parameter will be set to MAXimum.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13 FUNCtion & DATA SubsystemSENSe:FUNCtion & DATA

The FUNCtion subsystem selects the <sensor_function>(s) to be sensed by the instrument.These functions differ from the signal-oriented MEASure instructions in that a<sensor_function> is something that the sensor can be configured to directly detect.

The DATA subsystem is used to query data from the SENSe block.

KEYWORD PARAMETER FORM NOTES:DATA? [<data_handle>] [query only] 1991

TK056:DATA 1995TK032a :PREamble? [<data_handle>] [query only] 1994

:FUNCtion :CONCurrent <Boolean> 1991 :OFF <sensor_function>{,<sensor_function>} 1991 :ALL [no query] 1991 :COUNt? [query only] 1991 [:ON] <sensor_function>{,<sensor_function>} 1991 :ALL [no query] 1991 :COUNt? [query only] 1991 :STATe? <sensor_function> [query only] 1991

18.13.1 DATA? [<data_handle>]SENSe:DATA?

Provides access to the result(s) of the SENSe block. This query retrieves the current SENSeresult(s).

The <data_handle> parameter to this query is optional. Instruments that implement thisquery are required to accept the the optional parameter <data_handle> if sent. If a sensorfunction is specified, and that function is currently being sensed the result is returned. If thefunction is not being sensed an error -221 (Settings Conflict) shall be generated.

If a <data_handle> is not specified, then the result(s) of all functions being sensed arereturned. If CONCurrent is OFF there will be only one FUNCtion result. If CONCurrent isON there will be one or more results, depending on how many functions are currently on.The order of the function results returned by the DATA? query is device-dependent,although the order of these results shall be the same as the order of the functions returned bythe FUNCtion[:ON]? query. If no functions are currently being sensed an error -221(Settings Conflict) shall be generated. The data returned by the DATA? query is affected bythe FORMat subsystem.


18.13.1.1 SENSe <data_handle>sIf the SENSor block only emits one data flow, then the <data_handle> is just the string“SENSe<n>”, where <n> is a numeric suffix. However, for the case where the SENSe blockoutputs more than one result, each data result needs to be assigned a unique <data_handle>,symbolic of the data flow. Since the SENSe:FUNCtion command is already defined to take a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-42 SENSe:FUNCtion & DATA

well-defined string as a parameter, these <sensor_function> strings are used as part of the<data_handle>. If more than one SENSe block in the instrument outputs the same<sensor_function> the SENSe block must also be included in the data handle. The syntax forthe SENSe block <data_handle> is:

<data_handle> := “[SENSe:]<sensor_function>” | “SENSe[:<sensor_function>]”

TK05618.13.1.2 :PREamble? [<data_handle>]SENSe:DATA:PREamble?

TK032aPREamble? returns the preamble information supporting the DATA(CURVe(VALues)) butomits the following data:

DIF blocks of waveform, measurement, and delta.


TK032aThe DIF difid block must contain the keyword SCOPe with the parameter of PREamble.

TK032aWhile the PREamble? query is designed to efficiently transmit data relating directly to thecurve, the various notes and identification parameters may be sent if absolutely required.

TK032aThe optional <data_handle> parameter functions the same as it does in SENSe:DATA?.

18.13.2 :FUNCtionSENSe:FUNCtion

The FUNCtion subsystem selects the <sensor_function>(s) to be sensed by the instrument.For compatibility, instruments that support CONCurrent ON are required to supportCONCurrent OFF mode. This is so some level of compatibility can be maintained withnon-concurrent instruments which expect data results for only one FUNCtion to be returnedby the SENSe:DATA? query.

18.13.2.1 :CONCurrent <Boolean>SENSe:FUNCtion:CONCurrent

The CONCurrent command indicates whether the SENSor block should be configured toSENSe one function at a time or SENSe more than one function at a time (concurrently).

If CONCurrent is OFF, the FUNCtion[:ON] command acts as a one-of-n switch selecting theindicated function to be the only sensed function. If CONCurrent is ON, the function(s)specified as parameter(s) to the FUNCtion[:ON] command are turned on, while the state ofother functions are not affected.

When CONCurrent is turned OFF, the instrument shall select one function to be turned on,and turn off any other functions that were on. The function which is selected to be on shallalways be the same one, even if that function is not currently ON.

When CONCurrent is turned ON, the states of individual functions shall not be changed.

At *RST the value of CONCurrent is device-dependent. However if an instrumentimplements CONCurrent ON, then it must implement CONCurrent OFF also for purposes ofinstrument compatibility.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:FUNCtion & DATA 18-43

18.13.2.2 :OFF <sensor_function>{,<sensor_function>}SENSe:FUNCtion:OFF

The FUNCtion:OFF command selects the <sensor_function>s to be turned off. Thiscommand only needs to be implemented by instruments which allow users to turn OFFindividual functions while leaving others on. The state of any other functions are not affectedby turning the specified functions OFF.

The query response of FUNCtion:OFF? shall return a comma separated list of functionswhich are currently OFF, each of which are <STRING RESPONSE DATA>. If no functionsare OFF, a null string is returned. The query shall return the short form mnemonics and shallomit any default nodes in the <sensor_function>.


18.13.2.2.1 :ALLSENSe:FUNCtion:OFF:ALL

This command turns OFF all of the <sensor_function>s which the instrument canconcurrently sense. There is no query for this command.

18.13.2.2.2 :COUNt?SENSe:FUNCtion:OFF:COUNt?

This query returns the number of <sensor_function>s which are OFF. This command mustbe implemented if CONCurrent ON and FUNCtion:OFF are implemented.


18.13.2.3 [:ON] <sensor_function>{,<sensor_function>}SENSe:FUNCtion:ON

The FUNCtion[:ON] command selects the <sensor_function>(s) to be SENSed by theinstrument. This command only needs to be implemented by instruments which allow usersto select what functions will be SENSed. The <sensor_function> is specified as a quotedstring. For example:

FUNCtion “VOLTage:AC”

If CONCurrent is OFF, a single <sensor_function> is sent as the parameter. This selects thisfunction to be sensed. If more than one function is sent an error -108 (Parameter notallowed) shall be generated.

If CONCurrent is ON, a comma separated list of <sensor_function> may be sent asparameters. These functions are turned on, while the state of other functions are not affected.

The query response of FUNCtion[:ON]? shall return a comma separated list of functionswhich are on, each of which are <STRING RESPONSE DATA>. If no functions are ON, anull string is returned. The query shall return the short form mnemonics and shall omit anydefault nodes in the <sensor_function>.

For example FUNCtion[:ON]? returns the quoted string “VOLT:AC”.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.3.1 :ALLSENSe:FUNCtion:ON:ALL

This command turns ON all of the <sensor_function>s which the instrument canconcurrently sense. There is no query for this command.

18.13.2.3.2 :COUNt?SENSe:FUNCtion:ON:COUNt?

This query returns the number of <sensor_function>s which are ON. This command must beimplemented if CONCurrent ON and FUNCtion[:ON] are implemented.


18.13.2.4 :STATe? <sensor_function>SENSe:FUNCtion:STATe?

Returns a Boolean indicating whether the specified <sensor_function> is currently ON orOFF. This command is query only.

At *RST, the state of each <sensor_function> is device- dependent.

18.13.2.5 <sensor_function>SENSe:FUNCtion

The FUNCtion subsystem uses the <sensor_function> to select the function on which theFUNCtion commands operate on, <sensor_function> has the following syntax:

<sensor_function> ::=“<presentation_layer><function_name> [<input block>{,<input block>}] [ON <subnode>{,<subnode>}]”

The <sensor_function> is STRING PROGRAM DATA.

HP088The names inside angle brackets (<) and (>) are called productions and the commas (,) and‘ON’ are literals. White space is defined in section 7.4.1.2 of IEEE 488.2 as one or morewhite space characters.

HP088For a <sensor_function> sent to an instrument, white space is not allowed inside anyproduction or literal. White space is not allowed between the <presentation_layer> and<function_name> productions. At least one white space character is required before andafter the literal ON. At least one white space character is required before the first<input_block>. White space is permitted, but not required, everywhere else in the<sensor_function>. The FUNCtion commands shall accept the long and short forms of<sensor_function> mnemonics. Instruments shall accept both upper and lowercasecharacters without distinguishing between cases.

HP088When a <sensor_function> is returned in response to a query, it shall contain no white spaceexcept for a single space before the first <input_block> and single spaces around the literalON if either is present. The mnemonics in the query response shall use short form withdefault nodes omitted. All alpha characters in the response shall be in uppercase.<input_block> elements are omitted in the query response only if all have been set to theirdefault values. If any <input_block> element has been set to anything other than its defaultvalue, then all <input_block> elements are returned in the query response.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The <function_name> is a well-defined hiearchical sensor function indicating the type offunction the sensor will be configured to directly detect.

The optional <input_block> parameters are numeric values indicating which INPut blocksshall be “fed” into the sensor function. The numeric value corresponds to the same-numbered INPut block. Specifying an input block in a sensor function makes an implicitinternal routing connection such that the output of the designated INPut block will flow intothe sensor. If no <input_block> parameters are specified the instrument defined default dataflow is used.

For example, SENSe:FUNCtion “VOLTage:AC 2” would configure the sensor to sense theAC Voltage of the data flowing out of INPut2. The SENSe:FUNCtion? query would thenreturn the quoted string “VOLT:AC 2”.

The optional <subnode> parameter is used when the SENSe block contains userconfigurable selections of subnodes to be used in computation of the SENSe FUNCtion. Forexample if a single SENSe block contained two SWEep subblocks and the sensor could useeither SWEep block to measure the AC Voltage of INPut1. Currently SWEep and AVERageare the only subnodes which are allowed after the ON keyword.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.6 <presentation_layer> 1991

PRESENTATION LAYER [XNONe:] 1991XTIMe: 1991XFRequency: 1991XPOWer: 1991XVOLtage: 1991XCURrent: 1991

18.13.2.6.1 [XNONe:]SENSe:FUNCtion “XNONe:<function>”

This specifies that the X-axis has no specific units or number of points. No knowledge canbe associated with the X-axis. XNONe is only scalar.

18.13.2.6.2 XTIMe:SENSe:FUNCtion “XTIMe:<function>”

This specifies that the sensor function results are acquired with respect to time. The X-axis isin units of time.

18.13.2.6.3 XFRequency:SENSe:FUNCtion “XFRequency:<function>”

This specifies that the sensor function results are acquired with respect to frequency. TheX-axis is in units of frequency.

18.13.2.6.4 XPOWer:SENSe:FUNCtion “XPOWer:<function>”

This specifies that the sensor function results are acquired with respect to power. The X-axisis in units of power.

18.13.2.6.5 XVOLtage:SENSe:FUNCtion “XVOLtage:<function>”

This specifies that the sensor function results are acquired with respect to voltage. TheX-axis is in units of voltage.

18.13.2.6.6 XCURrent:SENSe:FUNCtion “XCURrent:<function>”

This specifies that the sensor function results are acquired with respect to current. TheX-axis is in units of current.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.7 <function_name>SENSe:FUNCtion

TK018A SENSe:FUNCtion <function_name> is a well-defined hierarchical sensor functionindicating the type of function the sensor will be configured to directly detect. The<function_name> comprises the <function> and is optionally followed by a:<function_suffix>.

<function_name> := <function>[:<function_suffix>]

Where: <function_suffix> is of type <CHARACTER PROGRAM DATA> with thefollowing values defined:

<function_suffix> := RATio | SUM

TK018When the RATio suffix is included, then a ratio between two input blocks shall be selected.

TK018When the SUM suffix is included, then the sum of two or more input blocks shall be selected.

TK018Excluding the <function_suffix> shall cause the sensor function to be selected.

For example:

:SENSe:FUNCtion “FREQuency”

Selects frequency sensing.

:SENSe:FUNCtion “FREQuency:RATio”

Selects a ratio of two frequencies as a function. If the user specifies input blocks after thesensor function, then the first input block specified is the numerator and the second inputblock is the denominator.

:SENSe:FUNCtion “VOLTage:DC:SUM 1,2"

Selects the sum of DC voltages on inputs 1 and 2 as a function.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.8 <function>The following is the sensor <function> tree and descriptions:

FUNCTION DESCRIPTIONACCeleration Acceleration 1999AM 1991 [:DEPTh] AM Depth 1991 :DISTortion AM Distortion 1991 :FREQuency AM Frequency 1991 :SNDRatio AM Signal, Noise & Distortion Ratio (SINAD) 1991 :SNR AM Signal to Noise Ratio 1991 :THD AM Total Harmonic Distortion 1991CONCentration Non-time-aligned concentration 1999 :RAW Raw concentration value in device dependent units 1999 :SDEViation Standard Deviation corresponding to data point

CONCentration 1999 :TALign Time-aligned analyzer for analyzer number (1,2,...n)

in device-dependent units 1999CONDition True/False condition of a signal 1993 PH074CURRent [:DC] DC Current :AC AC CurrentDISTance Distance 1999FERRor Force Error 1999FM 1991 [:DEViation] FM Deviation 1991 :DISTortion FM Distortion 1991 :FREQuency FM Frequency 1991 :SNDRatio FM Signal, Noise & Distortion Ratio (SINAD) 1991 :SNR FM Signal to Noise Ratio 1991 :THD FM Total Harmonic Distortion 1991FORCe Force 1999FREQuency Direct sensing of frequencyFRESistance Four-wire resistance 1991PERiod Inverse of frequency

PH033PHASe Direct sensing of phase 1992PM 1991 [:DEViation] PM Deviation 1991 :DISTortion PM Distortion 1991 :FREQuency PM Frequency 1991 :SNDRatio PM Signal, Noise & Distortion Ratio (SINAD) 1991 :SNR PM Signal to Noise Ratio 1991 :THD PM Total Harmonic Distortion 1991POWer :AC AC Power

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



FUNCTION DESCRIPTION :ACHannel Adjacent Channel Power 1991 :LOWer Lower Adjacent Channel Power 1991 [:UPPer] Upper Adjacent Channel Power 1991

HP056 :COHerence 1992HP056 :CROSs Cross Product 1992

[:DC] DC Power :DISTortion Distortion 1991

HP056 :PSDensity Power Spectral Density 1992HP056 :S11| S21| S22| S12 Scattering Parameter Function 1992

:SNDRatio Signal, Noise & Distortion Ratio (SINAD) 1991 :SNR Signal to Noise Ratio 1991 :THD Total Harmonic Distortion 1991

RS011PULM Pulse Modulation 1994RESistance Two wire resistanceSPEed Speed 1999 :FRONt Front Roll Speed 1999 [:REAR] Rear Roll Speed 1999

RS011SSB Single Sideband 1994TEMPerature Temperature 1999TIMer Value of the timer (see :SYSTem:TIME:TIMer) 1999TINTerval Time Interval 1991TOTalize Totalize Events 1991TPLoss Target Parasitic Loss 1999VOLTage :AC AC Voltage

HP056 :CDFunction Cumulative Density Function 1992 [:DC] DC Voltage

HP056 :HISTogram Histogram 1992HP056 :PDFunction Probability Density Function 1992

18.13.2.8.1 ACCelerationSENSe:FUNCtion “ACCeleration”

Acceleration.

18.13.2.8.2 AMSENSe:FUNCtion “AM”

Amplitude modulation.

18.13.2.8.2.1 [:DEPTh]SENSe:FUNCtion “AM:DEPTh”

AM depth.

18.13.2.8.2.2 :DISTortionSENSe:FUNCtion “AM:DISTortion”

DISTortion is the ratio of noise plus distortion to the signal plus noise plus distortion.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.8.2.3 :FREQuencySENSe:FUNCtion “AM:FREQuency”

AM frequency.

18.13.2.8.2.4 :SNDRatioSENSe:FUNCtion “AM:SNDRatio”

Signal, Noise and Distortion Ratio (SINAD or SNDRatio) is the ratio of the unfiltered signalto the signal with its fundamental removed (ratio of signal plus noise plus distortion to thenoise plus distortion).

Signal to Noise Ratio (SNR) = (signal+noise) / noise.

18.13.2.8.2.5 :SNRSENSe:FUNCtion “AM:SNR”

AM signal to noise ratio.

18.13.2.8.2.6 :THDSENSe:FUNCtion “AM:THD”

HP056

Total Harmonic Distortion (THD) is the ratio of the signal with its fundamental removed tothe unfiltered signal.

18.13.2.8.3 CONCentrationSENSe:FUNCtion “CONCentration”

Non-time-aligned concentration.

18.13.2.8.3.1 :RAWSENSe:FUNCtion “CONCentration:RAW”

Raw concentration value in device dependent units.

18.13.2.8.3.2 :SDEViationSENSe:FUNCtion “CONCentration:SDEViation”

Standard Deviation corresponding to data point CONCentration.

18.13.2.8.3.3 :TALignSENSe:FUNCtion “CONCentration:TALign”

Time-aligned analyzer for analyzer number (1,2,...n) in device-dependent units.

18.13.2.8.4 CONDitionSENSe:FUNCtion “CONDition”

True/False condition of a signal.

18.13.2.8.5 CURRentSENSe:FUNCtion “CURRent”

18.13.2.8.5.1 [:DC]SENSe:FUNCtion “CURRent:DC”

DC current.

18.13.2.8.5.2 :ACSENSe:FUNCtion “CURRent:AC”

AC current.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.8.6 DISTanceSENSe:FUNCtion “DISTance”

Distance. For chassis dynamometers this is the distance accumulated by the dynamometer.

18.13.2.8.7 FMSENSe:FUNCtion “FM”

Frequency modulation.

18.13.2.8.7.1 :[DEViation]SENSe:FUNCtion “FM:DEViation”

FM Deviation.

18.13.2.8.7.2 :DISTortionSENSe:FUNCtion “FM:DISTortion”


18.13.2.8.7.3 :FREQuencySENSe:FUNCtion “FM:FREQuency”

FM frequency.

18.13.2.8.7.4 :SNDRatioSENSe:FUNCtion “FM:SNDRatio”



18.13.2.8.7.5 :SNRSENSe:FUNCtion “FM:SNR”

FM signal to noise ratio.

18.13.2.8.7.6 :THDSENSe:FUNCtion “FM:THD”

HP056


18.13.2.8.8 FERRorSENSe:FUNCtion “FERRor”

Force Error. For chassis dynamometers this specifies the error inherent in the measurementof the real-time force.

18.13.2.8.9 FORCeSENSe:FUNCtion “FORCe”

Force. For chassis dynamometers this is the force at the roll surface.

18.13.2.8.10 FREQuencySENSe:FUNCtion “FREQuency”

Direct sensing of frequency.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.8.11 FRESistanceSENSe:FUNCtion “FRESistance”

Four-wire resistance.

18.13.2.8.12 PERiodSENSe:FUNCtion “PERiod”

Inverse of frequency.

18.13.2.8.13 PHASe PH033

SENSe:FUNCtion “PHASe”

Direct sensing of phase.

18.13.2.8.14 PMSENSe:FUNCtion “PM”

Pulse modulation.

18.13.2.8.14.1 [:DEViation]SENSe:FUNCtion “PM:DEViation”

PM deviation.

18.13.2.8.14.2 :DISTortionSENSe:FUNCtion “PM:DISTortion”


18.13.2.8.14.3 :FREQuencySENSe:FUNCtion “PM:FREQuency”

PM Frequency.

18.13.2.8.14.4 :SNDRatioSENSe:FUNCtion “PM:SNDRatio”



18.13.2.8.14.5 :SNRSENSe:FUNCtion “PM:SNR”

PM signal to noise ratio.

18.13.2.8.14.6 :THDSENSe:FUNCtion “PM:THD”

HP056

PM Total Harmonic Distortion (THD) is the ratio of the signal with its fundamental removedto the unfiltered signal.

18.13.2.8.15 POWerSENSe:FUNCtion “POWer”

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.13.2.8.15.1 :ACSENSe:FUNCtion “POWer:AC”

AC Power.

18.13.2.8.15.2 :ACHannelSENSe:FUNCtion “POWer:ACHannel”

Adjacent Channel Power measurements involve measuring the power at a specified carrierfor a given bandwidth and then ratio it to the power detected at the upper (or lower) adjacentchannel.

18.13.2.8.15.2.1 :LOWerSENSe:FUNCtion “POWer:ACHannel:LOWer”

Lower Adjacent Channel Power.

18.13.2.8.15.2.2 [:UPPer]SENSe:FUNCtion “POWer:ACHannel:UPPer”

Upper Adjacent Channel Power.

HP05618.13.2.8.15.3 :COHerenceSENSe:FUNCtion “POWer:COHerence”

COHerence is the portion of the first <input_block> spectrum related to the second<input_block> spectrum. It is a measure of the statistical validity of a frequency responsemeasurement.

HP05618.13.2.8.15.4 :CROSsSENSe:FUNCtion “POWer:CROSs”

This is the Cross Product of two input_blocks. It is computed by multiplying the complexconjugate of the first <input_block> by the second <input_block>.

18.13.2.8.15.5 [:DC]SENSe:FUNCtion “POWer:DC”

DC Power.

18.13.2.8.15.6 :DISTortionSENSe:FUNCtion “POWer:DISTortion”


HP05618.13.2.8.15.7 :PSDensitySENSe:FUNCtion “POWer:PSDensity”

This is the Power Spectral Density. It is the power spectrum normalized to a 1 Hz bandwidth.

HP05618.13.2.8.15.8 :S11|:S12|:S22|:S21SENSe:FUNCtion “POWer:S11"

These are the Scattering Parameter Functions.

HP056Scattering parameters or S parameters are a tool used in frequency characterization ofdevices to determine how the device modifies signal flow. An S parameter is a ratio of twoenergy values and is defined as:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Sxy = energy emerging from port x

energy entering port y

with all ports other than port Y terminated in a Z0 load.

HP056By convention, a devices ports are numbered (1,2,...n). An n port device has n2 S parameterslabelled Sxy, where {x,y} = {1,2,...,n}.

HP056For more information please refer to “Scattering and Transmission Coefficients” chapter in“Fields and Waves in Communication Electronics”, Ramo, Whinnery and Van Duzer.

18.13.2.8.15.9 :SNDRatioSENSe:FUNCtion “POWer:SNDRatio”



18.13.2.8.15.10 :SNRSENSe:FUNCtion “POWer:SNR”

Signal to Noise Ratio.

18.13.2.8.15.11 :THDSENSe:FUNCtion “POWer:THD”

HP056


RS01118.13.2.8.16 PULMSENSe:FUNCtion “PULM”

Pulse modulation.

18.13.2.8.17 RESistanceSENSe:FUNCtion “RESistance”

Two wire resistance.

18.13.2.8.18 SPEedSENSe:FUNCtion “SPEed”

Speed.

18.13.2.8.18.1 :FRONtSENSe:FUNCtion “SPEed:FRONt”

Front Roll Speed. For chassis dynamometers this is the roll speed. On twin roll systems, thisis the front roll speed.

18.13.2.8.18.2 [:REAR]SENSe:FUNCtion “SPEed[:REAR]”

Rear Roll Speed. For chassis dynamometers this is the roll speed. On twin roll systems, thisis the rear roll speed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



RS01118.13.2.8.19 SSBSENSe:FUNCtion “SSB”

Single sideband modulation.

18.13.2.8.20 TEMPeratureSENSe:FUNCtion “TEMPerature”

Temperature.

18.13.2.8.21 TIMerSENSe:FUNCtion “TIMer”

Value of the timer (see :SYSTem:TIME:TIMer).

18.13.2.8.21.1 COUNtSENSe:FUNCtion “TIMer:COUNt”

Returns the current timer count.

18.13.2.8.22 TINTervalSENSe:FUNCtion “TINTerval”

Time Interval.

18.13.2.8.23 TOTalizeSENSe:FUNCtion “TOTalize”

Totalize events.

18.13.2.8.24 TPLossSENSe:FUNCtion “TPLoss”

Target Parasitic Loss. For chassis dynamometers this is the value of frictional loss at thepresent speed based on the active parasitic loss curve.

18.13.2.8.25 VOLTageSENSe:FUNCtion “VOLTage”

Something needed here18.13.2.8.25.1 :ACSENSe:FUNCtion “VOLTage:AC”

AC Voltage.HP056

18.13.2.8.25.2 :CDFunctionSENSe:FUNCtion “VOLTage:CDFunction”

HP056

The Cumulative Density Function is the integral of a normalized histogram.

18.13.2.8.25.3 [:DC]SENSe:FUNCtion “VOLTage:DC”

DC Voltage.

18.13.2.8.25.4 :HISTogramSENSe:FUNCtion “VOLTage:HISTogram”

HP056

The histogram measures how the amplitude of the input signal is distributed between it’smaximum and minimum values.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



HP05618.13.2.8.25.5 :PDFunctionSENSe:FUNCtion “VOLTage:PDFunction”

The Probability Density Function is computed by normalizing a histogram and is a statisticalmeasure of the probablity that a specific level occured.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



18.14 LIST SubsystemSENSe:LIST

The list subsystem controls automatic sequencing through associated lists of frequency, anddwell time values. The various values are specified in the LIST:FREQuency, LIST:DWELlcommands. Points in each list correspond to the associated point in all other lists.

The LIST subsystem controls a characteristic of the instrument when that subsystem’s modeis set to LIST (for example, FREQuency:MODE LIST).

When employing multiple lists, all lists must be of equal length. If they are not of the samelength, an error is generated at sequencing time. An exception is made for the case where theshorter list is of length 1. In this case, the particular list is treated as though it were a list ofequal length, with all values being the same.

Lists are not affected by *RST.

KEYWORD PARAMETER FORM NOTES:LIST :COUNt <numeric_value> :DIRection UP|DOWN :DWELl <numeric_value>{,<numeric_value>} :POINts? [query only] :FREQuency <numeric_value>{,<numeric_value>} :POINts? [query only] :SEQuence <numeric_value>{,<numeric_value>} :AUTO <Boolean>|ONCE :POINts? [query only]

18.14.1 :COUNt <numeric_value>SENSe:LIST:COUNt

Controls the number of times the sequence list is scanned when a trigger is received.

18.14.2 :DIRection UP|DOWNSENSe:LIST:DIRection

Specifies the direction that the sequence list is scanned. If UP is selected, the list is scannedfrom the first to the last item in the sequence list. If DOWN is selected, the list is scannedfrom the last item to the first item in the sequence list.

18.14.3 :DWELl <numeric_value>{,<numeric_value>}SENSe:LIST:DWELl

Specifies the dwell time points of the lists. The units are in seconds.

This specifies the amount of time spent at each point.

18.14.3.1 :POINts?SENSe:LIST:DWELl:POINts?

Returns the number of points currently in the DWELl list.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-58 SENSe:LIST

18.14.4 :FREQuency <numeric_value>{,<numeric_value>}SENSe:LIST:FREQuency

Specifies the frequency points of the list set. The units are Hz.

18.14.4.1 :POINts?SENSe:LIST:FREQuency:POINts?

This query returns the number of points currently in the FREQuency list.

18.14.5 :SEQuence <numeric_value>{,<numeric_value>}SENSe:LIST:SEQuence

Defines a sequence for stepping through the list. Individual points may be specified as manytimes as desired in a single sequence. The points specified are indexes into the lists. Forexample, if 3 was selected, the third point in the frequency and dwell lists would besequenced.

18.14.5.1 :AUTO <Boolean>|ONCESENSe:LIST:SEQuence:AUTO

When on, the sequence list is set to 1 through N, where N is the longest list.

18.14.5.2 :POINts?SENSe:LIST:SEQuence:POINts?

This query returns the number of points currently in the SEQuence list.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:LIST 18-59

18.15 MIXer SubsystemSENSe:MIXer

This subsystem controls external mixers for tuned receivers. It also provides controls tocompensate for known fixed losses in external mixers.

KEYWORD PARAMETER FORM NOTES:MIXer :BIAS <numeric_value> :AUTO <Boolean>|ONCE :LIMit <numeric_value> :HARMonic <numeric_value> :AUTO <Boolean>|ONCE :LOSS <numeric_value> :AUTO <Boolean> 1991

18.15.1 :BIAS <numeric_value>SENSe:MIXer:BIAS

Controls the mixer bias.


18.15.1.1 :AUTO <Boolean>|ONCESENSe:MIXer:BIAS:AUTO

Allows the mixer bias to be automatically set by other parameters in the system. Explicitlysetting a value for BIAS shall cause AUTO to be set to OFF.

At *RST, this value shall be set to ON.

18.15.1.2 :LIMit <numeric_value>SENSe:MIXer:BIAS:LIMit

Controls the maximum mixer bias level which can be set by the BIAS command or by otherparameters when AUTO is ON.

The limits and *RST conditions are instrument-dependent.

18.15.2 :HARMonic <numeric_value>SENSe:MIXer:HARMonic

Selects which harmonic of the local oscillator will be used for mixing.


18.15.2.1 :AUTO <Boolean>|ONCESENSe:MIXer:HARMonic:AUTO

When AUTO is ON, the harmonic is chosen by the system or instrument, and may changeduring the sweep. When OFF, the harmonic is locked to the selected value. Setting a valuefor MIXer:HARMonic sets AUTO to OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-60 SENSe:MIXer

18.15.3 :LOSS <numeric_value>SENSe:MIXer:LOSS

Compensates for losses external to the instrument. This parameter is added to all readings.The unit for this command is the current relative amplitude unit.


18.15.3.1 :AUTO <Boolean>SENSe:MIXer:LOSS:AUTO

Sets the LOSS to the value appropriate to the connected external mixer.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:MIXer 18-61

18.16 PM SubsystemSENSe:PM

The Phase Modulation subsystem is used to set the modulation controls and parametersassociated with sensing phase modulated signals.

KEYWORD PARAMETER FORM NOTES:PM 1991 [:DEViation] 1991 :RANGe 1991 :AUTO <Boolean> | ONCE 1991 [:UPPer] <numeric_value> 1991 :LOWer <numeric_value> 1991

18.16.1 [:DEViation]SENSe:PM:DEViation

This node is used to collect together the deviation parameters.

18.16.1.1 :RANGeSENSe:PM:DEViation:RANGe


18.16.1.1.1 :AUTO <Boolean> | ONCESENSe:PM:DEViation:RANGe:AUTO



18.16.1.1.2 [:UPPer] <numeric_value>SENSe:PM:DEViation:RANGe:UPPer



18.16.1.1.3 :LOWer <numeric_value>SENSe:PM:DEViation:RANGe:LOWer



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-62 SENSe:PM

18.17 POWer SubsystemSENSe:POWer

This subsection controls the power amplitude characteristics of the sensor.

KEYWORD PARAMETER FORM NOTES:POWer :ACHannel 1991 :SPACing 1991 :LOWer <numeric_value> 1991 :AUTO <Boolean> 1991 [:UPPer] <numeric_value> 1991 :AC|[:DC] :APERture <numeric_value> :NPLCycles <numeric_value> 1991 :ATTenuation <numeric_value> :AUTO <Boolean> :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only] :CLEar [no query] :RANGe [:UPPer] <numeric_value> :LOWer <numeric_value> :AUTO <Boolean>|ONCE :DIRection UP|DOWN|EITHer :LLIMit <numeric_value> 1996 :ULIMit <numeric_value> 1996 :OFFSet 1991 :PTPeak 1991 :REFerence <numeric_value> :STATe <Boolean> :RESolution <numeric_value> :AUTO <Boolean>|ONCE :DETector INTernal | EXTernal 1991

18.17.1 :ACHannelSENSe:POWer:ACHannel

Adjacent Channel Power Measurements involve measuring the power at a specified carrierfor a given bandwidth and then ratio it to the power detected at the upper (or lower) adjacentchannel.

18.17.1.1 :SPACingSENSe:POWer:ACHannel:SPACing

Controls the channel SPACing which is the distance from the modulated carrier signal to theupper or lower Adjacent Channel.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:POWer 18-63

18.17.1.1.1 :LOWer <numeric_value>SENSe:POWer:ACHannel:SPACing:LOWer

Controls the channel SPACing to the lower Adjacent Channel.


18.17.1.1.1.1 :AUTO <Boolean>SENSe:POWer:ACHannel:SPACing:LOWer:AUTO

When AUTO is ON, the value of LOWer is coupled to the value of UPPER.

18.17.1.1.2 [:UPPer] <numeric_value>SENSe:POWer:ACHannel:SPACing:UPPer

Controls the channel SPACing which is the distance from the modulated carrier signal to theupper Adjacent Channel.


18.17.2 :AC|[:DC]SENSe:POWer:AC

This subsystem selects the alternating current or the direct current sensor. The default unitsare watts.

18.17.2.1 :APERture <numeric_value>SENSe:POWer:AC:APERture



18.17.2.2 :NPLCycles <numeric_value>SENSe:POWer:AC:NPLCycles




18.17.2.3 :ATTenuation <numeric_value>SENSe:POWer:AC:ATTenuation



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-64 SENSe:POWer

18.17.2.3.1 :AUTO <Boolean>SENSe:POWer:AC:ATTenuation:AUTO




18.17.2.4 :PROTectionSENSe:POWer:AC:PROTection


18.17.2.4.1 [:LEVel] <numeric_value> SENSe:POWer:AC:PROTection:LEVel


18.17.2.4.2 :STATe <Boolean> SENSe:POWer:AC:PROTection:STATe



18.17.2.4.3 :TRIPped?SENSe:POWer:AC:PROTection:TRIPped?


18.17.2.4.4 :CLEarSENSe:POWer:AC:PROTection:CLEar



18.17.2.5 :RANGeSENSe:POWer:AC:RANGe


18.17.2.5.1 [:UPPer] <numeric_value>SENSe:POWer:AC:RANGe:UPPer



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:POWer 18-65

18.17.2.5.2 :LOWer <numeric_value>SENSe:POWer:AC:RANGe:LOWer



18.17.2.5.3 :AUTO <Boolean>|ONCESENSe:POWer:AC:RANGe:AUTO



18.17.2.5.3.1 :DIRection UP|DOWN|EITHerSENSe:POWer:AC:RANGe:AUTO:DIRection



18.17.2.5.3.2 :LLIMit <numeric_value>SENSe:POWer:AC:RANGe:AUTO:LLIMit



18.17.2.5.3.3 :ULIMit <numeric_value>SENSe:POWer:AC:RANGe:AUTO:ULIMit

The Upper LIMit command sets the largest range to which the instrument will go whileautoranging. When AUTO is ON and the present RANGe is outside the new limits, theinstrument may change the RANGe to a value inside the limits or wait until the next time theautoranging algorithm is performed.


18.17.2.5.4 :OFFSet <numeric_value>SENSe:POWer:AC:RANGe:OFFSet



18.17.2.5.5 :PTPeak <numeric_value>SENSe:POWer:AC:RANGe:PTPeak


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-66 SENSe:POWer


18.17.2.6 :REFerence <numeric_value>SENSe:POWer:AC:REFerence



18.17.2.6.1 :STATe <Boolean>SENSe:POWer:AC:REFerence:STATe



18.17.2.7 :RESolution <numeric_value>SENSe:POWer:AC:RESolution




18.17.2.7.1 :AUTO <Boolean>|ONCESENSe:POWer:AC:RESolution:AUTO




18.17.3 :DETector INTernal | EXTernalSENSe:POWer:DETector


At *RST, this value is set to INT.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:POWer 18-67

18.18 RESistance|FRESistance SubsystemSENSe:RESistance

This subsection controls the signal characteristics of a resistance sensor. RESistance shouldbe used for a two-wire measurement. FRESistance (four-wire resistance) should be used fora four-wire measurement. The default units are ohms.

KEYWORD PARAMETER FORM NOTES :RESistance|:FRESistance 1991 :APERture <numeric_value> :NPLCycles <numeric_value> 1991 :OCOMpensated <Boolean> 1991 :RANGe [:UPPer] <numeric_value> :LOWer <numeric_value> :AUTO <Boolean>|ONCE :DIRection UP|DOWN|EITHer :LLIMit <numeric_value> 1996 :ULIMit <numeric_value> 1996 :REFerence <numeric_value> :STATe <Boolean> :RESolution <numeric_value> :AUTO <Boolean>|ONCE

18.18.1 :APERture <numeric_value>SENSe:RESistance:APERture



18.18.2 :NPLCycles <numeric_value>SENSe:RESistance:NPLCycles




18.18.3 :OCOMpensated <Boolean>SENSe:RESistance:OCOMpensated

Enables or disables the offset compensation when measuring resistance. (For example, offsetcompensation first measures the voltage on the input terminals before turning on the currentused to measure resistance.)

At *RST, OCOMpensated shall be set to OFF.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-68 SENSe:RESistance|FRESistance

18.18.4 :RANGeSENSe:RESistance:RANGe

Sets the range for the resistance sensor.

18.18.4.1 [:UPPer] <numeric_value>SENSe:RESistance:RANGe:UPPer

Specifies the maximum resistance expected for the sensor input.


18.18.4.2 :LOWer <numeric_value>SENSe:RESistance:RANGe:LOWer

Specifies the smallest resistance expected for the sensor input. This allows setting for thebest dynamic range. This function is coupled to the UPPer command in a device-dependentmanner.


18.18.4.3 :AUTO <Boolean>|ONCESENSe:RESistance:RANGe:AUTO

Sets the RANGe to the value determined to give the most dynamic range without overloading. The actual algorithm is device-dependent.


18.18.4.3.1 :DIRection UP|DOWN|EITHerSENSe:RESistance:RANGe:AUTO:DIRection

The DIRection command defines the manner in which AUTO works. When UP is selected,the instrument shall only change the range automatically to ranges larger than the currentrange,as the input signal dictates. When DOWN is selected, the instrument shall only changethe range automatically to ranges smaller than the current range, as the input resistancedictates. When EITHer is selected, the instrument may range in either direction.

AT *RST, DIRection shall be set to EITHer.

18.18.4.3.2 :LLIMit <numeric_value>SENSe:RESistance:RANGe:AUTO:LLIMit



18.18.4.3.3 :ULIMit <numeric_value>SENSe:RESistance:RANGe:AUTO:ULIMit

The Upper LIMit command sets the largest range to which the instrument will go whileautoranging. When AUTO is ON and the present RANGe is outside the new limits, theinstrument may change the RANGe to a value inside the limits or wait until the next time theautoranging algorithm is performed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:RESistance|FRESistance 18-69


18.18.5 :REFerence <numeric_value>SENSe:RESistance:REFerence

Sets a reference resistance for sensor instruments. This command differs in intent from thereference correction in that this is intended to be a measurement offset where a user wishesto reference a measurement to some known value.


18.18.5.1 :STATe <Boolean>SENSe:RESistance:REFerence:STATe

Determines whether resistance is measured in absolute or relative mode. If STATe is ON,then resistance is referenced to the value set in REFerence.


18.18.6 :RESolution <numeric_value>SENSe:RESistance:RESolution

Specifies the absolute resolution of the measurement. For example, if a measurement of 10Ohms is made with a resolution of .01, the measurement is returned with a resolution of .01Ohms (that is, 10.00).


18.18.6.1 :AUTO <Boolean>|ONCESENSe:RESistance:RESolution:AUTO


Explicitly setting a value for RESolution will turn AUTO OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-70 SENSe:RESistance|FRESistance

18.19 ROSCillator SubsystemSENSe:ROSCillator

This subsystem controls the frequency reference oscillator.

KEYWORD PARAMETER FORM NOTES:ROSCillator

HP055 [:INTernal] 1992 :FREQuency <numeric_value>

HP055 :EXTernal 1992HP055 :FREQuency <numeric_value> 1992

:SOURce INTernal|EXTernal|NONE|CLK10|CLK100 1991 HP024

:AUTO <Boolean>|ONCEHP05518.19.1 [:INTernal]

SENSe:ROSCillator:INTernal

This subsystem configures the internal reference oscillator(s).

18.19.1.1 :FREQuency <numeric_value>SENSe:ROSCillator:INTernal:FREQuency

Specifies the frequency of the internal reference oscillator. The default units are Hz.


HP05518.19.2 :EXTernalSENSe:ROSCillator:EXTernal

This subsystem configures the external reference oscillator(s).

HP05518.19.2.1 :FREQuency <numeric_value>SENSe:ROSCillator:EXTernal:FREQuency

Specifies the frequency of the external reference oscillator. The default units are Hz.


18.19.3 :SOURce INTernal|EXTernal|NONE|CLK10|CLK100SENSe:ROSCillator:SOURce

HP055Controls the selection of the reference oscillator source. This typically refers to a precision,stabilized time base. The parameter values have the following meanings:

HP055INTernal — The reference frequency is derived from an internal precisionoscillator.

HP055EXTernal — The reference frequency is derived from an external signal suppliedto the device.

HP055NONE — The reference frequency is not derived from any precision oscillator.

HP055CLK10 — The reference frequency is derived from VXIbus signal CLK10.

HP055CLK100 — The reference frequency is derived from VXIbus signal CLK100.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:ROSCillator 18-71

18.19.3.1 :AUTO <Boolean>|ONCESENSe:ROSCillator:SOURce:AUTO

When AUTO is ON, the system automatically selects which oscillator will be used by theinstrument.

Explicitly selecting a reference oscillator turns AUTO OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-72 SENSe:ROSCillator

18.20 SMOothing SubsystemSENSe:SMOothing

This subsystem controls the point-to-point smoothing of the signal. Smoothing differs fromaveraging in that with smoothing, adjacent points of one set of data are averaged, while inaveraging the average is taken over several acquisitions (that is, smoothing is a movingaverage). This subsystem controls smoothing done to compensate for measurement artifacts.Analytical post-acquisition smoothing is controlled with CALCulate:SMOothing.

FL005

KEYWORD PARAMETER FORM NOTESSMOothing [:STATe] <Boolean> :APERture <numeric_value> :POINts <numeric_value>

18.20.1 [:STATe] <Boolean>SENSe:SMOothing:STATe

Determines whether the smoothing algorithm is enabled.


18.20.2 :APERture <numeric_value>SENSe:SMOothing:APERture

Specifies the size of the smoothing APERture as a ratio of smoothing window points/tracepoints. POINts is coupled to APERture by the equation:

POINts = APERture * SWEep:POINts

For example, if an APERture of .01 were chosen for a 1000-point sweep, then the smoothingwindow would be 10 points wide.


18.20.3 :POINts <numeric_value>SENSe:SMOothing:POINts

Controls the number of points to be included in the running average. POINts is coupled toAPERture by the equation:

POINts = APERture * SWEep:POINts


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:SMOothing 18-73

RS01118.21 SSB SubsystemSENSe:SSB

The single sideband modulation subsystem is used to set up the modulation controls andparameters associated with sensing and demodulating single sideband modulated signals.

RS01118.21.1 :TYPE USB|LSB|A1SENSe:SSB:TYPE

SENSe:SSB:TYPE sets or queries the type of SSB demodulation technique the demodulatoruses. USB means the demodulator is configured to upper sideband signals. LSB means thedemodulator is configured to lower sideband signals. A1 means the demodulator isconfigured to A1 signals.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-74 SENSe:SSB

18.22 STABilize SubsystemSENSe:STABilize

This subsystem contains the commands that control the stability parameters for thedesignated instrument and range.

KEYWORD PARAMETER FORM NOTES:STABilize 1999 :NTOLerance <numeric_value> 1999 [:STATe] <Boolean> 1999 :TIME<n> <numeric_value> 1999

18.22.1 :NTOLerance <numeric_value>:SENSe:STABilize:NTOLerance

This command specifies or returns the allowable tolerance between averaged readings for astabilized read, in percentage of full scale (%FS).


18.22.2 [:STATE] < Boolean >:SENSe:STABilize[:STATe]

This command sets or queries the stabilization state for all sensors. If stabilization is enabled,a procedure involving use of the stabilization times TIME1, TIME2, TIME3, and TIME4and the stabilization tolerance is invoked in response to commands such as :SENSe:DATA?,and :SENSe:CORRection:ZERO:ACQuire. An error in stabilization shall result in error#-365.

At *RST, stabilization is OFF.

Signal Response

Time (seconds)

TIME4

NTOlerance

TIME2

TIME1

TIME3

Figure 18.1 Stabilization Use

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:STABilize 18-75

18.22.3 :TIME<n> <numeric_value>:SENSe:STABilize:TIME<n>

This command sets the nth time parameter for the stabilization procedure, for the selectedinstrument(s).

The numeric suffix of :TIME, which is NOT optional, is defined as follows:

TIME1: Stabilized read initial rise or delay time.

TIME2: Stabilized read period, consisting of a number of TIME3’s, over whichstabilization is considered.

TIME3: Stabilized read duration of a single averaging period.

TIME4: Stabilized read maximum time of stabilization procedure.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-76 SENSe:STABilize

18.23 SWEep SubsystemSENSe:SWEep

ACQ02bACQ02bThis subsystem controls the timebase and/or sweep generator in instruments that acquire dataeither directly or indirectly as a function of time.

ACQ02bExamples of instruments that acquire data directly as a function of time (non-sweptinstruments) are digitizers and logic analyzers. The X axis has units of time. The<sensor_function> presentation layer is :XTIMe.

Examples of instruments that acquire data indirectly as a function of time (sweptinstruments) are spectrum analyzers. In this case, the X axis has units of frequency, but thefrequency is swept with relationship to time. The <sensor_function> presentation layer is:XFRequency. The parameter to be swept is specified by setting the :MODE node in theassociated subsystem to SWEEP (FREQuency:MODE SWEep).

ACQ02bSome commands in this subsystem are applicable to both swept and non-swept instruments.Others may apply to only one of these classes.

ACQ02bCommands in this subsystem may be coupled to those in implementor-defined triggersequences such as TRIGger:SAMPle. The TRIGger sequences can provide additionalflexibility by allowing the user more precise control over the acquisition.

ACQ02bThe commands in the :SWEep subsystem specify the timing and spacing of the valuesreturned in :DATA?, FETCh?, and other measurement queries. The commands in theTRIGger subsystem specify when actual measurements are acquired. The preciserelationship between the parameters in the two subsystems is device dependent. Forexample, the :SWEep:TINTerval command specifies the timing period between twosuccessive samples of the SENSe:DATA? response. The TRIGger:SAMPle:TIMercommand specifies the timing period between two acquisition samples that are taken by thetrigger subsystem.

ACQ02bMinutesThe :SWEep subsystem contains several sets of commands which have complex couplings.These include the commands :TIME, :POINts, :DWELl, and TINTerval. Sending any one ofa set singly will affect others of the set. However, if two are sent in a single programmessage, then these two shall set the values specified and the other changed. This is anaccordance with the style guidelines and IEEE 488.2. See Syntax and Style section 7.4 foradditional rules.

ACQ02bDefault units in this subsystem are seconds unless otherwise specified.

KEYWORD PARAMETER FORM NOTES:SWEep :COUNt <numeric_value> :DIRection UP|DOWN :DWELl <numeric_value> :AUTO <Boolean>|ONCE :GENeration STEPped|ANALog :MODE AUTO|MANual

ACQ02b :OFFSet 1994

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:SWEep 18-77

ACQ02bKEYWORD PARAMETER FORM NOTES :POINts <numeric_value> 1994

ACQ02b :TIME <numeric_value> 1994ACQ02b :OREFerence 1994ACQ02b :LOCation <numeric_value> 1994ACQ02b :POINts <numeric_value> 1994

:POINts <numeric_value> :REALtime 1993 PH072 [:STATe] <Boolean> 1993 PH072 :SPACing LINear|LOGarithmic :STEP <numeric_value> :TIME <numeric_value> :AUTO <Boolean>|ONCE :LLIMit <numeric_value>

ACQ02b :TINTerval <numeric_value> 1994

18.23.1 :COUNt <numeric_value>SENSe:SWEep:COUNt

ACQ02bThis command determines the number of sweeps which are initiated or vectors (arrays ofsamples, waveforms, etc) which are acquired by a single trigger event.

ACQ02bAt *RST, this value is set to 1.

18.23.2 :DIRection UP|DOWNSENSe:SWEep:DIRection

ACQ02bControls the direction of the sweep. If UP is selected, the sweep is carried out from start tostop. If DOWN is selected, the sweep is carried out from stop to start. This command onlyapplies to swept instruments.

ACQ02bAt *RST, this value is set to UP.

18.23.3 :DWELl <numeric_value>SENSe:SWEep:DWELl

ACQ02bControls the amount of time spent at each point during a sweep. This command only appliesto swept instruments. Explicitly setting a value for SWEep:DWELl setsSWEep:DWELl:AUTO OFF.

ACQ02bThe following coupling equation applies.SWEep:TINTerval = SWEep:DWELl + <stepping_time>

ACQ02bChanging DWELl will cause either TINTerval or <stepping_time> to change in a devicedependent manner. See also introductory comments in the SWEep subsystem.

ACQ02b<stepping_time> is the device dependent time required for the sweep generator to movefrom one point (swept entity) to the next.

ACQ02bNote that DWELl cannot exceed TINTerval. Setting DWELl to a greater value will causeerror -222, “Data out of range” to be generated.

ACQ02bAt *RST, this value is device-dependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-78 SENSe:SWEep

18.23.3.1 :AUTO <Boolean>|ONCESENSe:SWEep:DWELl:AUTO

ACQ02bWhen ON is selected, the dwell time is calculated internally when SWEep:TINTerval ischanged. Explicitly setting a value for SWEep:DWELl sets SWEep:DWELl:AUTO OFF.

ACQ02bAt *RST, AUTO is set to ON.

18.23.4 :GENeration STEPped|ANALogSENSe:SWEep:GENeration

ACQ02bDetermines if the sweep or acquisition is stepped or analog.

ACQ02bSTEPped: A stepped sweep or acquisition is selected. The number of points is setby the SWEep:POINts command.

ACQ02bANALog: The sweep or acquisition is controlled by an analog signal.SWEep:POINts is not applicable.


18.23.5 :MODE AUTO|MANualSENSe:SWEep:MODE

ACQ02bDetermines whether the sweep is performed automatically, or if the actual swept entity iscontrolled by the MANual command in the appropriate subsystem (for example,FREQuency:MANual). This command only applies to swept instruments.

ACQ02bAt *RST, this value is set to AUTO.

ACQ02b18.23.6 :OFFSetSENSe:SWEep:OFFSet

ACQ02bThis subsystem sets the offset between the offset reference point (SWEep:OREFerence) andthe trigger point.

18.23.6.1 :POINts <numeric_value>SENSe:SWEep:OFFSet:POINts

ACQ02bSets the offset in terms of points. This value may be positive or negative. A positive valuespecifies that the offset reference point occurs after the trigger point.

ACQ02bThe following coupling equation applies.SWEep:OFFSet:POINts = SWEep:OFFSet:TIME / SWEep:TINTerval

ACQ02bChanging SWEep:OFFSet:POINts will cause SWEep:OFFSet:TIME to change, but notSWEep:TINTerval. See also introductory comments in the SWEep subsystem.


ACQ02b18.23.6.2 :TIME <numeric_value>SENSe:SWEep:OFFSet:TIME

ACQ02bSets the offset in units of time. This value may be positive or negative. A positive valuespecifies that the offset reference point occurs after the trigger point.

ACQ02bThe following coupling equation applies.SWEep:OFFSet:POINts = SWEep:OFFSet:TIME / SWEep:TINTerval

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:SWEep 18-79

ACQ02bChanging SWEep:OFFSet:TIME will cause SWEep:OFFSet:POINts to change, but notSWEep:TINTerval. See also introductory comments in the SWEep subsystem.


ACQ02b18.23.7 :OREFerenceSENSe:SWEep:OREFerence

ACQ02bThis subsystem sets the location of the offset reference point in the sweep or acquisition. Theoffset reference is used by the SWEep:OFFSet commands.

ACQ02b18.23.7.1 :LOCation <numeric_value>SENSe:SWEep:OREFerence:LOCation

ACQ02bSets the offset reference by specifying a relative location. SWEep:OREFerence:LOCationaccepts a range of values from 0 to 1. A value of 0 selects the first point of acquisition as thereference. A value of 1 selects the last point.

ACQ02bThe following coupling equation applies.SWEep:OREFerence:LOCation = (SWEep:OREFerence:POINts - 1) / (SWEep:POINts - 1)

ACQ02bChanging SWEep:OREFerence:LOCation will cause SWEep:OREFerence:POINts tochange, but not SWEep:POINts. See also introductory comments in the SWEep subsystem.


ACQ02b18.23.7.2 :POINts <numeric_value>SENSe:SWEep:OREFerence:POINts

ACQ02bSets the offset reference by specifying a number of points. SWEep:OREFerence:POINtsaccepts values from 1 to N, where N is the maximum value of SWEep:POINts. A value of 1selects the first point of acquisition as the reference.

ACQ02bThe following coupling equation applies.SWEep:OREFerence:LOCation = (SWEep:OREFerence:POINts - 1) / (SWEep:POINts - 1)

ACQ02bChanging SWEep:OREFerence:POINts will cause SWEep:OREFerence:LOCation tochange, but not SWEep:POINts. See also introductory comments in the SWEep subsystem.


18.23.8 :POINts <numeric_value>SENSe:SWEep:POINts

ACQ02bSets the number of points in a stepped sweep or acquisition. POINts is ignored whenGENeration is ANALog.

ACQ02bThe following coupling equations apply.

SWEep:TINTerval = SWEep:TIME / (SWEep:POINts - 1)

ACQ02bChanging SWEep:POINts will cause either SWEep:TINTerval or SWEep:TIME to changein a device dependent manner. See also introductory comments in the SWEep subsystem.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-80 SENSe:SWEep

SWEep:OREFerence:LOCation = (SWEep:OREFerence:POINts - 1) / (SWEep:POINts - 1)

ACQ02bChanging SWEep:POINts will cause either SWEep:OREFerence:LOCation orSWEep:OREFerence:POINts to change in a device dependent manner. See also introductorycomments in the SWEep subsystem.

ACQ02bWhen SPACing is LINear:

SWEep:STEP = <swept_subsystem>:SPAN / (SWEep:POINts - 1)

ACQ02bChanging SWEep:POINts will cause SWEep:STEP to change, but not<swept_subsystem>:SPAN.

ACQ02bWhen SPACing is LOGarithmic:

<points_per_decade> = (SWEep:POINts-1) / <decades_in_span>

ACQ02bChanging SWEep:POINts will cause <points_per_decade> to change, but not<decades_in_span>. <decades_in_span> is calculated internally from<swept_subsystem>:STARt, :STOP, :CENTer, and :SPAN. Normally, <decades_in_span>equals log10(:STOP/:STARt), when :STOP > :STARt. See also introductory comments inthe SWEep subsystem.


18.23.9 :REALtime PH072SENSe:SWEep:REALtime

Instruments that acquire data directly as function of time, may use several data acquisitionmethods to sense the data points of the sweep.

There are techniques where the points in the requested sweep are collected from a number ofsuccessive acquisitions. In this case the result is a reconstruction of the original signal out ofseveral acquisitions; this is not real time.

An acquisition is known as real time if no reconstruction is done; that is, the points in theresulting data set are in the order in which they were acquired.

18.23.9.1 [:STATe] <Boolean> PH072SENSe:SWEep:REALtime:STATe

When STATe is ON, the instrument is required to collect data in real time. When STATe isOFF, the instrument is allowed to use reconstruction techniques.


18.23.10 :SPACing LINear|LOGarithmicSENSe:SWEep:SPACing

Determines the time vs. swept entity characteristics of the sweep. The various settings havethe following meanings:

LINear: The swept entity is incremented (decremented) by the stepsize until thesweep limit is reached if the sweep generation is stepped. If the sweep is analog,

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:SWEep 18-81

selecting this parameter specifies a ramp.

LOGarithmic: Step size is determined by a logarithmic curve fitted between thestart and stop value of the swept entity. Stepping is determined by the number ofsteps function.


18.23.11 :STEP <numeric_value>SENSe:SWEep:STEP

Controls the swept entity step size for a stepped linear sweep. STEP is ignored whenGENeration is ANALog or when SPACing is LOGarithmic.

ACQ02bThe following coupling equation applies.SWEep:STEP = <swept_subsystem>:SPAN / (SWEep:POINts - 1)

ACQ02bChanging SWEep:STEP will cause SWEep:POINts to change, but not<swept_subsystem>:SPAN. See also introductory comments in the SWEep subsystem.

ACQ02bThe default units are those of the associated <swept_subsystem>:SPAN command.


18.23.12 :TIME <numeric_value>SENSe:SWEep:TIME

ACQ02bSets the duration of the sweep or acquisition. Note that this does not turn sweeping oracquisition on. Explicitly setting a value for SWEep:TINTerval or SWEep:TIME setsSWEep:TIME:AUTO OFF.

ACQ02bThe following coupling equation applies.SWEep:TINTerval = SWEep:TIME / (SWEep:POINts - 1)

ACQ02bChanging SWEep:TIME will cause SWEep:TINTerval to change, but not SWeep:POINts.See also introductory comments in the SWEep subsystem.


18.23.12.1 :AUTO <Boolean>|ONCESENSe:SWEep:TIME:AUTO

ACQ02bWhen ON is selected, SWEep:TIME and SWEep:TINTerval are calculated internally whenrelated settings outside the time domain coupling equations are changed. Explicitly setting avalue for SWEep:TIME or SWEep:TINTerval sets SWEep:TIME:AUTO OFF.

ACQ02bThis command only applies to swept instruments, where explicitly setting SWEep:TIME andSWEep:TINTerval is the exception. For instance, in a spectrum analyzer, a user normallysets the frequency parameters (FREQuency:SPAN and :CENTER) and expects theinstrument to calculate the appropriate sweep time and interval to produce a reasonableresolution bandwidth. The :AUTO node should not be implemented in non-sweptinstruments that normally expect the user to explicitly set SWEep:TIME orSWEep:TINTerval.

ACQ02bAt *RST, AUTO is set to ON.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-82 SENSe:SWEep

18.23.12.2 :LLIMit <numeric_value>SENSe:SWEep:TIME:LLIMit

Defines a lower limit for sweep time. This lower limit restricts the sweep time value seteither explicitly or automatically.


ACQ02b18.23.13 :TINTerval <numeric_value>SENSe:SWEep:TINTerval

ACQ02bSets the time interval between points of the sweep or acquisition. Explicitly setting a valuefor SWEep:TINTerval or SWEep:TIME sets SWEep:TIME:AUTO OFF.

ACQ02bThe following coupling equations apply.

SWEep:TINTerval = SWEep:TIME / (SWEep:POINts - 1)

ACQ02bChanging SWEep:TINTerval will cause SWEep:TIME to change, but not SWeep:POINts.See also introductory comments in the SWEep subsystem.

SWEep:OFFSet:POINts = SWEep:OFFSet:TIME / SWEep:TINTerval

ACQ02bChanging SWEep:TINTerval will cause either SWEep:OFFSet:POINts orSWEep:OFFSet:TIME to change in a device dependent manner. See also introductorycomments in the SWEep subsystem.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:SWEep 18-83

18.24 VOLTage SubsystemSENSe:VOLTage

This subsection controls the voltage amplitude characteristics of the sensor.

KEYWORD PARAMETER FORM NOTES:VOLTage :AC|[:DC] :APERture <numeric_value> :NPLCycles <numeric_value> 1991 :ATTenuation <numeric_value> :AUTO <Boolean> :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only] :CLEar [no query] :RANGe [:UPPer] <numeric_value> :LOWer <numeric_value> :AUTO <Boolean>|ONCE :DIRection UP|DOWN|EITHer :LLIMit <numeric_value> 1996 :ULIMit <numeric_value> 1996

HP066 :OFFSet <numeric_value> 1991,2HP066 :PTPeak <numeric_value> 1991,2

:REFerence <numeric_value> :STATe <Boolean> :RESolution <numeric_value> :AUTO <Boolean>|ONCE :DETector INTernal | EXTernal 1991

18.24.1 :AC|[:DC]SENSe:VOLTage:AC

This subsystem selects the alternating current or the direct current sensor. The default unitsare volts.

18.24.1.1 :APERture <numeric_value>SENSe:VOLTage:AC:APERture



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-84 SENSe:VOLTage

18.24.1.2 :NPLCycles <numeric_value>SENSe:VOLTage:AC:NPLCycles




18.24.1.3 :ATTenuation <numeric_value>SENSe:VOLTage:AC:ATTenuation



18.24.1.3.1 :AUTO <Boolean>SENSe:VOLTage:AC:ATTenuation:AUTO




18.24.1.4 :PROTectionSENSe:VOLTage:AC:PROTection


18.24.1.4.1 [:LEVel] <numeric_value> SENSe:VOLTage:AC:PROTection:LEVel


18.24.1.4.2 :STATe <Boolean> SENSe:VOLTage:AC:PROTection:STATe



18.24.1.4.3 :TRIPped?SENSe:VOLTage:AC:PROTection:TRIPped?


18.24.1.4.4 :CLEarSENSe:VOLTage:AC:PROTection:CLEar



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:VOLTage 18-85

18.24.1.5 :RANGeSENSe:VOLTage:AC:RANGe


18.24.1.5.1 [:UPPer] <numeric_value>SENSe:VOLTage:AC:RANGe:UPPer



18.24.1.5.2 :LOWer <numeric_value>SENSe:VOLTage:AC:RANGe:LOWer



18.24.1.5.3 :AUTO <Boolean>|ONCESENSe:VOLTage:AC:RANGe:AUTO



18.24.1.5.3.1 :DIRection UP|DOWN|EITHerSENSe:VOLTage:AC:RANGe:AUTO:DIRection



18.24.1.5.3.2 :LLIMit <numeric_value>SENSe:VOLTage:AC:RANGe:AUTO:LLIMit



18.24.1.5.3.3 :ULIMit <numeric_value>SENSe:VOLTage:AC:RANGe:AUTO:ULIMit

The Upper LIMit command sets the largest range to which the instrument will go while

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-86 SENSe:VOLTage

autoranging. When AUTO is ON and the present RANGe is outside the new limits, theinstrument may change the RANGe to a value inside the limits or wait until the next time theautoranging algorithm is performed.


18.24.1.5.4 :OFFSet <numeric_value>SENSe:VOLTage:AC:RANGe:OFFSet



18.24.1.5.5 :PTPeak <numeric_value>SENSe:VOLTage:AC:RANGe:PTPeak



18.24.1.6 :REFerence <numeric_value>SENSe:VOLTage:AC:REFerence



18.24.1.6.1 :STATe <Boolean>SENSe:VOLTage:AC:REFerence:STATe



18.24.1.7 :RESolution <numeric_value>SENSe:VOLTage:AC:RESolution




18.24.1.7.1 :AUTO <Boolean>|ONCESENSe:VOLTage:AC:RESolution:AUTO




1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:VOLTage 18-87

18.24.2 :DETector INTernal | EXTernalSENSe:VOLTage:DETector


At *RST, this value is set to INT. 1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-88 SENSe:VOLTage

18.25 WINDow SubsystemSENSe:WINDow

FL005The window subsystem selects digital signal processing windowing parameters for use byFFT analyzers. Windows are time-domain weighting functions applied to input time recordsto condition the results of a time-domain to frequency-domain transformation. Thissubsystem controls windowing done to compensate for measurement artifacts. Analyticalpost-acquisition windowing is controlled with CALCulate:TRANsform.

KEYWORD PARAMETER FORM NOTES:WINDow [:TYPE] RECTangular subsystem|UNIForm|FLATtop subsystem

|HAMMing|HANNing|KBESsel|FORCe|EXPonential

:KBESsel <numeric_value> :EXPonential <numeric_value> :FORCe <numeric_value>

18.25.1 [:TYPE] RECTangular|UNIForm|FLATtop|HAMMing|HANNing |KBESsel|FORCe|EXPonentialSENSe:WINDow:TYPE

TYPE allows user selection from among several well-known or standard window types.Each window has characteristics that make it particularly suitable for certain kinds ofmeasurements.

Individual windowing algorithms are defined in “On the Use of Windows for HarmonicAnalysis with the Discrete Fourier Transform,” F. J. Harris, Proc of the IEEE, Vol. 66-1,January 1978, pp 51-83.

AT *RST, this value is device-dependent.

18.25.1.1 :KBESsel <numeric_value>SENSe:WINDow:TYPE:KBESsel

Enters the exponential decay time constant which characterizes the KBESsel window. Theparameter to this command has units of seconds.


18.25.1.2 :EXPonential <numeric_value>SENSe:WINDow:TYPE:EXPonential

Enters the exponential decay time constant which characterizes the EXPonential window.The parameter to thids command has units of seconds.


18.25.1.3 :FORCe <numeric_value>SENSe:WINDow:TYPE:FORCe

Enters the time value parameter corresponding to the width of the gated portion of the inputtime record for FORCe windows. The parameter of this command has units of seconds.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SENSe:WINDow 18-89

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


18-90 SENSe:WINDow

19 SOURce SubsystemThe SOURce setup commands are divided into several sections. Each section or subsystemdeals with controls that directly affect device-specific settings of the device, and not thoserelated to the signal-oriented characteristics. These commands are referenced through theSOURCe node.

The SOURce node may be optional in a particular device. The reason that the SOURce isoptional is to allow devices which are primarily sources to accept shorter commands. TheSOURce node cannot be optional if either SENSe or ROUTe is optional, since only one nodeat a given level may be optional. For example, a typical power supply may elect to make theSOURce node optional, since the most frequently used commands would be under theSOURce subsystem. If the power supply also contained either source or routingfunctionality, these would be controlled through their respective nodes; however, the SENSeor ROUTe nodes would be required. An optional node, such as SOURce, implies that thedevice shall accept and process commands with or without the optional node and have thesame result. That is, the device is required to accept the optional node, if sent, without error.

In some instances, a source may contain subservient source or sensor functions. In suchcases, the additional subservient functionality shall be placed as SENSe or SOURcesubnodes under the SOURce subsystem. Further, no optional nodes (SENSe, SOURce orROUTe) are permitted if such subservient functionality exists in a device. Otherwiseconflicts in interpreting commands would occur, for example, between SOURce and[SENSe:]SOURce if the SENSe were allowed to be optional.

CURRent, POWer, VOLTage, FREQuency, and RESistance contain several sets ofcommands which have complex couplings. This includes the sweep commands STARt,STOP, CENTer, and SPAN as one set, and AMPLitude, OFFSet, HIGH, and LOW asanother. Sending any one of a set singly will affect two others of the set. However, if two aresent in a single message unit, then these two should be set to the values specified and theother two changed. This is in accordance with the style guidelines and IEEE 488.2. STARt,STOP, CENTer, and SPAN must be implemented as a set. That is, if any one isimplemented, then all must be implemented.

If the requested setting is unachievable given the other instrument settings, then an errormust be generated (-211 “settings conflict”). The device may resolve the conflict in adevice-dependent manner (for example, change STARt, STOP, CENTer, and/or SPAN) toresolve the error. Note that when more than one of the four sweep settings are received in thesame program message unit, the sweep will be determined by the last two received.

The coupled commands may define commands as subnodes which alter these couplings. Thecommand description will define how the couplings are altered. However, any commandwhich alters couplings must default to the couplings described in this section as the *RSTcouplings.

When CENTer or SPAN is changed the following couplings apply:SPAN = SPANCENTer = CENTer

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce: 19-1

STOP = CENTer + (SPAN/2)STARt = CENTer - (SPAN/2)

When STARt or STOP is changed the following couplings apply:STARt = STARtSTOP = STOPCENTer = (STARt + STOP)/2SPAN = STOP - STARt

The couplings above assume linear units in the sweep specified.

HIGH, LOW, AMPLitude, and OFFSet have the same interactions described above forSTARt, STOP, CENTer, and SPAN.

When AMPLitude or OFFSet is changed the following couplings apply:OFFSet = OFFSetAMPLitude = AMPLitudeHIGH = OFFSet + (AMPLitude/2)LOW = OFFSet - (AMPLitude/2)

When HIGH or LOW is changed the following couplings apply:HIGH = HIGHLOW = LOWOFFSet = (HIGH + LOW)/2AMPLitude = HIGH - LOW

HP094For CURRent, POWer, and VOLTage when ATTenuation:AUTO is ON a coupling existsbetween ATTenuation and LEVel. This coupling is needed in sources which use anattenuator to extend the dynamic range of the source’s level. Fig 19-1 illustrates this situation.

HP094When ATTenuator:AUTO is ON, the full dynamic range of the instrument is available usingthe LEVel command. The instrument uses an algorithm which adjusts both the the limiteddynamic range signal and the attenuator to supply the requested level.

HP094When ATTenuation:AUTO is OFF, the amount of attenuation is fixed and the range ofallowed values for LEVel is reduced. The MINimum and MAXimum values for LEVeldepend on the value of ATTenuation.

HP094For example, assume an instrument has the block diagram illustrated in Fig 19-2.

Figure 19-1 ATTenuation - LEVel Coupling Model

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-2 SOURce:

HP094Say the output of the amplifier can vary from -5dBm to 10dBm and the attenuator can rangefrom 0 to 50dB in steps of 10dB. The source’s level can thus vary from -55dBm to 10dBm.

HP094After *RST, POWer:ATTenuation:AUTO is ON allowing POWer:ATTenuation toautomatically change depending on POWer[:LEVel]. The allowable range forPOWer[:LEVel] is from -55dBm (MINimum) to 10dBm (MAXimum). If POWer[:LEVel] isset to -48dBm, POWer:ATTenuation is set to 50dB and the power level at the amplifier’soutput is 2dBm. If POWer[:LEVel] is -43dBm, the instrument could be in one of two states:

HP094POWer:ATTenuation is -40dB and amplifier’s level is -3dBm or POWer:ATTenuation is -50dB and amplifier’s level is 7dBm

HP094Which state is chosen may depend on the previous state of POWer[:LEVe]] and thealgorithm employed by the instrument.

HP094The user now wants to prevent the attenuator from changing values. POWer:ATTenuation-40 is sent. Receiving a value for POWer:ATTenuation has the side effect of turningPOWer:ATTenuation:AUTO OFF, see 7.4 in Syntax & Style. Because the attenuator cannotautomatically change, the allowable range for POWer[:LEVel] is limited to the range-45dBm (MINimum) to -30dBm (MAXimum). Trying to program a value outside this rangecauses an Execution Error. The permissable range for POWer[:LEVel] can be changed bysending a new value for POWer:ATTenuation.

HP094The actual algorithm employed in the instrument and the range of values depend on theunderlying hardware implementation. SCPI does require MAXimum/MINimum querieswhich a user could use to discover how the bounds of the LEVel command change.

Figure 19-2 ATTenuation - LEVel Coupling Example

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce: 19-3

First Level SOURce Keywords[:SOURce] :ACCeleration 1999 HP051

:AM HP051

HP086 :COMBine 1994 :CORRection 1992 HP067

:CURRent HP051

:DM :FM :FREQuency :FORCe 1999 HP051

:FUNCtion DT

:LIST DT

:MARKer HP051

:PHASe HP051

:PM :POWer HP051

:PULM :PULSe :RESistance HP051

:ROSCillator :SPEed 1999 HP051

:SWEep HP051

:TEMPerature 1993 XSS01c :VOLTage HP051

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-4 SOURce:

19.1 ACCeleration SubsystemSOURce:ACCeleration

This node controls the acceleration of the device.

KEYWORD PARAMETER FORM COMMENTS:ACCeleration 1999 [:LEVel] <numeric_value> 1999

19.1.1 [:LEVel] <numeric_value>:SOURce:ACCeleration[:LEVel]

Sets the acceleration in m/s2.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:ACCeleration 19-5

19.2 AM SubsystemSOURce:AM

The Amplitude Modulation subsystem is used to set the modulation controls and theparameters associated with the modulating signal(s). The keywords to describe the carriersignal exist in other subsystems (such as, FREQuency and PHASe).

KEYWORD PARAMETER FORM COMMENTS:AM :COUPling AC|DC|GROund [:DEPTh] <numeric_value> :EXTernal :COUPling AC|DC|GROund :IMPedance <numeric_value> :POLarity NORMal|INVerted :INTernal :FREQuency <numeric_value> :MODE FIXed|LIST 1993 EM003 :POLarity NORMal|INVerted :SENSitivity <numeric_value> :SOURce EXTernal|INTernal{,EXTernal|,INTernal} :STATe <Boolean> :TYPE LINear|LOGarithmic|EXPonential 1991 HP043

19.2.1 :COUPling AC|DC|GROundSOURce:AM:COUPling

COUPling, at this level, is used to set the coupling between the modulator and themodulating signal. The modulating signal may be the sum of several signals, either internalor external sources. If COUPling is set to DC, then both AC and DC components of thesignal pass. AC coupling passes only the AC component of the signal. The GROundparameter allows Amplitude Modulation to be turned ON without the modulating signalconnected.


19.2.2 [:DEPTh] <numeric_value>SOURce:AM:DEPTh

Sets the modulation DEPTh of an AM signal. The unit for DEPTh is percent (%). Thiscommand is used where the DEPTh can be controlled independently from the modulatingsignal voltage level. Alternately, it is used to set a device capability that can indicate whenthe desired DEPTh has been achieved.


19.2.3 :EXTernalSOURce:AM:EXTernal

The EXTernal subsystem is used to control the specified external signal source. Wheremultiple external modulation sources are available, the EXTernal keyword may have a

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-6 SOURce:AM

numeric suffix signifying the particular external signal source. If no number is given, a 1 isassumed.

19.2.3.1 :COUPling AC|DC|GROundSOURce:AM:EXTernal:COUPling

COUPling, at this level, sets the coupling for only the specified external signal source. IfCOUPling is set to DC, then both AC Modulation and DC components of the signal pass.AC coupling passes only the AC component of the signal. The GROund parameter allowsthe specified external source to be turned ON without being connected.


19.2.3.2 :IMPedance <numeric_value>SOURce:AM:EXTernal:IMPedance

Sets the impedance of the specified external signal source. The unit for IMPedance is Ohms.


19.2.3.3 :POLarity NORMal|INVertedSOURce:AM:EXTernal:POLarity

POLarity, at this level, sets the POLarity for only the specified external signal source.POLarity sets the relationship between the polarity of the applied modulation voltage and theresulting direction of modulation. The definition of “normal” polarity for AM modulatedsignal is: a positive voltage which causes the modulation envelope or the instantaneouscarrier amplitude to increase.

At *RST, this value must be set to NORMal.

19.2.4 :INTernalSOURce:AM:INTernal

The INTernal subsystem is used to control the specified internal signal source. Wheremultiple internal modulation sources are available, the INTernal keyword may have anumeric suffix signifying the particular internal signal source. If no number is given, a 1 isassumed.

19.2.4.1 :FREQuency <numeric_value>SOURce:AM:INTernal:FREQuency

Sets the frequency of the specified internal signal source. Some instruments may also allowthe internal signal source(s) to be controlled as a subsystem(s). The unit of FREQuency is Hz.


19.2.5 :MODE EM003SOURce:AM:MODE

Determines which set of commands currently control the AM subsystem. The settings havethe following meanings:

FIXed: Settings of individual commands are as last set by the user.

LIST: Settings of individual commands are controlled by the LIST subsystem.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:AM 19-7

At *RST the value is FIXed.

19.2.6 :POLarity NORMal|INVertedSOURce:AM:POLarity

POLarity, at this level, is used to set the polarity between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either internal or externalsources. POLarity sets the relationship between the polarity of the applied modulationvoltage and the resulting direction of modulation. The definition of “normal” polarity forAM modulated signal is a positive voltage, causing the modulation envelope or theinstantaneous carrier amplitude to increase.


19.2.7 :SENSitivity <numeric_value>SOURce:AM:SENSitivity

Controls the modulation depth by setting a sensitivity Modulation to the modulation signalvoltage level. The unit for SENSitivity is percent/Volt (%/V).


19.2.8 :SOURce EXTernal|INTernal{,EXTernal|,INTernal}SOURce:AM:SOURce

Selects the source for the modulating signal. It may specify a single source or a number ofsources. The specified sources, in the SOURce command, are all selected and turned on. Anysources from a previous selection that are not part of the current selection list are deselectedand turned off. If multiple sources are selected and the device does not support thecombination requested in the SOURce command, an execution error -221 will be generated.

Where multiple internal modulation sources are available, individual INTernal sources mustbe distinguished by a unique number suffix. If no number suffix is provided in a command, a1 must be assumed.

Where multiple external modulation sources are available, individual EXTernal sources mustbe distinguished by a unique number suffix. If no number suffix is provided in a command, a1 must be assumed.


19.2.9 :STATe <Boolean>SOURce:AM:STATe

This command is used to turn Amplitude Modulation ON or OFF. Turning AM modulationON will not automatically turn OFF any other types of modulation. Turning any or allmodulations types ON or OFF must be done explicitly. Where a type of modulation is active,turning ON another type of modulation will add to the set of active modulations if thatcombination of capabilities are legal in the device; otherwise, an execution error -221 isgenerated, and the instrument state is device-dependent.

At *RST, this value must be set to OFF.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-8 SOURce:AM

19.2.10 :TYPESOURce:AM:TYPE

HP043

Controls the type of AM shaping

LINear – The output voltage is directly proportional to Vmod.

LOGarithmic – The output voltage is proportional to log(Vmod).

EXPonential – The output voltage is proportional to 10(Vmod)Ed Change

At *RST the selection will be LINear.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:AM 19-9

19.3 COMBine SubsystemSOURce:COMBine

HP086This subsystem is used to combine two or more signals or data streams into one.

KEYWORD PARAMETER FORM COMMENTSHP086:COMBine 1994HP086 :FEED <data_handle> 1994

HP08619.3.1 :FEED <data_handle>HP086Sets or queries the data flow into the COMBine block. The number of FEED in a :COMBine

block is device dependent.

HP086At *RST, FEED is device dependent.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-10 SOURce:COMBine

19.4 CORRection SubsystemSOURce:CORRection

HP067

The correction subsystem provides for known external losses or gains. In contrast toCALibration, these losses usually are dependent on individual setups.

Correction data may be entered and stored in several ways. A mechanism is provided toautomatically measure the signal and store the resulting “correction set”. This data can beselected at any time as the active “correction set”. The data could also be generated by anexternal device and transferred to the instrument over a computer interface. Commands arealso provided to enter individual losses, gains, offsets, delays, etc. that the instrument shoulduse in correcting its operation. An instrument is not required to implement all of the methods.

KEYWORD PARAMETER FORM COMMENTS:CORRection 1992 [:STATe] <Boolean> 1992 :COLLect 1992 [:ACQuire] 1992 :METHod PMETer 1992 :SAVE <name> 1992 :CSET 1992 [:SELEct] <name> 1992 :STATe <Boolean> 1992 :OFFSet 1992 [:MAGNitude] <numeric_value> 1992 :PHASe <numeric_value> 1992 :STATe <Boolean> 1992 :LOSS|GAIN|SLOPe 1992 HP075

:STATe <Boolean> 1992 [:OUTPut] 1992 [:MAGNitude] <numeric_value> 1992 :PHASe <numeric_value> 1992 :EDELay 1992 [:TIME] <numeric_value> 1992 :DISTance <numeric_value> 1992 :STATe <Boolean> 1992 :RVELocity 1992 :MEDIum COAX|WAVeguide 1992 :COAX <numeric_value> 1992 :WAVeguide <numeric_value> 1992 :FCUToff <numeric_value> 1992 :STATe <Boolean> 1992

19.4.1 [:STATe] <Boolean>SOURce:CORRection:STATe

Determines whether the correction data defined in this section is applied to the signal.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:CORRection 19-11

19.4.2 :COLLectSOURce:CORRection:COLLect

Deals with the collection of the correction data by the device. Details may be device specific.

19.4.2.1 [:ACQUire]SOURce:CORRection:COLLect:ACQUire

A signal will be generated, measured, and the results saved as data for the chosen correctionmethod.

19.4.2.2 :METHod PMETerSOURce:CORRection:COLLect:METHod

Selects the correction method to be used for the correction that is about to be performed. Ifonly one correction method exists in the instrument then this command is not required.

The various settings of the parameters have the following meanings:

PMETer Use external Power METer to take readings.At *RST, this value is device dependent.

19.4.2.3 :SAVE [<name>] SOURce:CORRection:COLLect:SAVE

Calculates the correction data using the current method selection and then saves thecorrection data. If only one correction array exists then it is saved there. Otherwise it is savedin the set specified by <name>.

<name> may be either a <trace_name>, or a <table_name> which must be defined and existin the instrument. Note this command will not create either <trace_name>, or a<table_name>. Trace definition is done in the TRACe subsystem. Table definition is done inthe MEMory subsystem.

19.4.3 :CSETSOURce:CORRection:CSET

The Correction SET subsystem is used to select the active correction set.

19.4.3.1 [:SELect] <name>SOURce:CORRection:CSET:SELect

Specifies the active correction set. This is the set that is used when CORR:CSET:STAT ONis specified.

Note that the parameter is a <name> that must be defined and exist in the instrument.<trace_name>, or a <table_name> which must be defined and exist in the instrument. Notethis command will not create either <trace_name>, or a <table_name>. Trace definition isdone in the TRACe subsystem. Table definition is done in the MEMory subsystem.

19.4.3.2 STATe <Boolean>SOURce:CORRection:CSET:STATe

Determines whether the correction data defined in the selected set is applied to the output.

At *RST, this function is OFF. OFF is chosen because all of the correction sets may beempty. The instrument may need to be supplied with data before correction can be applied.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-12 SOURce:CORRection

19.4.4 :OFFSetSOURce:CORRection:OFFSet

This node defines a single value that is added to the signal supplied by the instrument. Thiscommand shall be used with the currently selected units. Offset effects the signal values asadditive (or subtractive) for linear units such as VOLT.

19.4.4.1 [:MAGNitude] <numeric_value>SOURce:CORRection:OFFSet:MAGNitude

This is the magnitude value of the correction offset data. Magnitude is always added linearly,as in volts.

At *RST, this value is set to zero.

19.4.4.2 :PHASe <numeric_value>SOURce:CORRection:OFFSet:PHASe

This is the phase value of the correction offset data. The units associated with this are thecurrently selected angle units.


19.4.4.3 :STATe <Boolean>SOURce:CORRection:OFFSet:STATe

This function is used to enable or disable the offset correction.


19.4.5 :LOSS|:GAIN|:SLOPe PH075SOURce:CORRection:LOSS

HP075

These commands are used either to provide a mechanism to apply simple correction or tocorrect external factors that have not been accounted for in the correction set.

Loss, gain and slope affect the signal amplitude as a multiplier for linear units such as VOLTand as additive (or subtractive) for logarithmic units such as dB.

:LOSS This command is used to set the anticipated loss in the system, excluding thosefactors covered by the active correction set. The device then adjusts the signal bythis factor to compensate for the loss. Loss is coupled to GAIN by the equationLOSS = 1/GAIN when the default unit is linear and LOSS =- GAIN when thedefault unit is logarithmetic.

:GAIN This command is used to set the anticipated gain in the system, excluding thosefactors covered by the active correction set. The device then adjusts the signal bythis factor to compensate for the gain. Gain is coupled to LOSS by the equationGAIN = 1/LOSS when the default unit is linear and GAIN =- LOSS when thedefault unit is logarithmetic.

HP075:SLOPe This node defines an increasing or decreasing value that is added to the signal.This correction value is zero at a zero value of the x axis and increase or decreasesfrom there.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.4.5.1 :STATe <Boolean>SOURce:CORRection:LOSS:STATe

This function is used to enable or disable the correction for LOSS or GAIN.


19.4.5.2 [:OUTPut]SOURce:CORRection:LOSS:OUTPut

The OUPut node is used to reference measurements made at the instruments output.

19.4.5.2.1 [:MAGNitude] <numeric_value>SOURce:CORRection:LOSS:OUTPut:MAGNitude

This is the magnitude value of the correction for LOSS, GAIN. The units asociated withLOSS and GAIN are the current relative amplitude units.


19.4.5.2.2 :PHASe <numeric_value>SOURce:CORRection:LOSS:OUTPut:PHASe

This is the phase value of the correction for LOSS or GAIN. The units associated with thisare the currently selected angle units.


19.4.6 :EDELaySOURce:CORRection:EDELay

The Electrical DELay is used to compensate for delays in the signal path.

This command is used to correct external factors that that have not been accounted for in thecorrection set.

TIME and DISTance are coupled by the equation:TIME = RVELocity*DISTance


19.4.6.1 [:TIME] <numeric_value>SOURce:CORRection:EDELay:TIME

This command will set the electrical delay with the time parameter given. The units for thiscommad are seconds. A value accepted here will modify the DISTance setting because theyare the same parameter in different forms.


19.4.6.2 :DISTance <numeric_value>SOURce:CORRection:EDELay:DISTance

This command will set the electrical delay with the distance parameter given. The effectivedelay will be computed using this parameter and the relative velocity set in the instrument.The units for this command are meters. A value accepted here will modify the time settingbecause they are the same parameter in different forms. Implementation of this commandrequires implementation of CORRection:EDELay[:TIME].

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26




19.4.6.3 :STATe <Boolean>SOURce:CORRection:EDELay:STATe

This function is used to enable or disable the correction for electrical delay.


19.4.7 :RVELocitySOURce:CORRection:RVELocity

This command corrects for the relative velocity of the medium connecting to the DeviceUnder Test. This factor will be used in any delay corrections performed by the instrument.

This command is used to correct external factors that that have not been accounted for in thecorrection set.

TIME and DISTance are coupled by the equation:TIME=RVELocity*DISTance


19.4.7.1 :MEDIum COAX|WAVeguideSOURce:CORRection:RVELocity:MEDIum

This command selects the method of correction for any operation that uses relative velocity.For example, for COAX a linear phase shift will be applied, but for WAVeguide (adispersive medium) a different phase shift is calculated.


19.4.7.2 :COAX <numeric_value>SOURce:CORRection:RVELocity:COAX

This command sets the relative velocity for coaxial transmission lines. The parameter isunitless.


19.4.7.3 :WAVeguide <numeric_value>SOURce:CORRection:RVELocity:WAVeguide

This command sets the relative velocity factor for waveguide. The parameter is unitless.


19.4.7.3.1 :FCUToff <numeric_value>SOURce:CORRection:RVELocity:WAVeguide:FCUToff

This command specifies the frequency cutoff of the waveguide medium. The units are Hertz.

At *RST, the value of this setting is device dependentEd Change

19.4.7.4 :STATe <Boolean>SOURce:CORRection:RVELocity:STATe

This function is used to enable or disable the relative velocity correction.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



At *RST, the value of this setting is OFF.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.5 CURRent SubsystemSOURce:CURRent

This subsection controls the signal amplitude characteristics of the source.

There is only one subsystem for each of the main amplitude characteristics of the signal.Thus, AC voltage and DC voltage are both placed under the VOLTage subsystem. A devicewhich implemented both simultaneously would implement them as two separate sources, oneAC and one DC.

KEYWORD PARAMETER FORM COMMENTS:CURRent :ATTenuation <numeric_value> :AUTO <Boolean>|ONCE :ALC [:STATe] <Boolean> :SEARch <Boolean>|ONCE :SOURce INTernal|DIODe|PMETer|MMHead :BANDwidth <numeric_value> |:BWIDth :AUTO <Boolean>|ONCE :CENTer <numeric_value> [:LEVel] [:IMMediate] [:AMPLitude] <numeric_value> :AUTO <Boolean>|ONCE 1991 PH040

:OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :TRIGgered [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> HP066

:LIMit [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :STATe <Boolean> :MANual <numeric_value> :MODE FIXed|SWEep|LIST :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only]

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:CURRent 19-17

KEYWORD PARAMETER FORM COMMENTS :CLEar [no query] :RANGe <numeric_value> :AUTO <Boolean>|ONCE :REFerence <numeric_value> :STATe <Boolean> :SLEW <numeric_value> :SPAN <numeric_value> :HOLD <Boolean> :LINK CENTer|STARt|STOP :FULL [no query] :STARt <numeric_value> :STOP <numeric_value>

19.5.1 :ATTenuation <numeric_value>SOURce:CURRent:ATTenuation

Sets the ATTenuation level. Note that when increasing the level by 10 dB the magnitude ofthe outgoing signal as well as the LEVel will be decreased by 10 dB.

Default units are as determined in the UNIT system. This is coupled to LEVel.

19.5.1.1 :AUTO <Boolean>SOURce:CURRent:ATTenuation:AUTO

Couples the attenuator to LEVel.


HP094See SOURce subsystem introduction for additional explanation.


19.5.2 :ALC SOURce:CURRent:ALC

This subsystem command controls the automatic leveling control of the source.

19.5.2.1 [:STATe] <Boolean> SOURce:CURRent:ALC:STATe

Controls whether the ALC loop controls the output level.


19.5.2.2 :SEARch <Boolean>|ONCE SOURce:CURRent:ALC:SEARch

SEARch enables a form of leveling where the output level is calibrated by momentarilyclosing the leveling loop. Once the correct amount of level adjustment has been determinedto produce the desired output level, the leveling loop is opened.

When ON, the search routine will be done anytime the output level requires change (forexample, when LEVel is changed).

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-18 SOURce:CURRent

Selecting SEARch ONCE will have the effect of setting SEARch to ON and then OFF. Amodulator setting is determined by the system which will not be changed until the outputlevel is explicitly reprogrammed.


19.5.2.3 :SOURce INTernal|DIODe|PMETer|MMHead SOURce:CURRent:ALC:SOURce

Selects the source of the feedback signal for ALC. The parameters have the followingmeanings:

INTernal — The ALC feedback signal is measured from a point inside the source.

DIODe — The ALC feedback is being fed from an external diode detector.

PMETer — The ALC signal is coming from a power meter.

MMHead — A millimeter head, with wuilt in leveling, is being used to supply theALC signal.

At *RST, this value is INTernal.

19.5.2.4 :BANDwidth|:BWIDth <numeric_value> SOURce:CURRent:ALC:BANDwidth

Controls the bandwidth of the ALC feedback signal. This parameter is in units of Hz.


19.5.2.4.1 :AUTO <Boolean>|ONCE SOURce:CURRent:ALC:BANDwidth:AUTO

Couples the bandwidth of the ALC feedback signal to instrument-dependent parameters.When AUTO is ON, the best bandwidth is chosen to reflect the current instrument state.

Explicitly selecting a value for ALC:BANDwidth sets AUTO OFF.


19.5.3 :CENTer <numeric_value> SOURce:CURRent:CENTer

Sets the center amplitude.

At *RST, this value is set to MINimum.

19.5.4 [:LEVel]SOURce:CURRent:LEVel

This subsystem is used to control the signal amplitude when the source is operating in acontinuous or FIXed MODE.

19.5.4.1 [:IMMediate]SOURce:CURRent:LEVel:IMMediate

Indicates that the subsequent specification of a new signal amplitude is to be processed bythe device without waiting for further commands.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.5.4.1.1 [:AMPLitude] <numeric_value>SOURce:CURRent:LEVel:IMMediate:AMPLitude

Sets the actual magnitude of the unswept output signal in terms of the current operatingunits. The units are set to the default value, or alternately to a different value under the UNITsubsystem. AMPLitude may be used to specify the level for either a time varying ornon-time varying signal.

Note the optional nodes exist to enable CURRent to be directly followed by a<numeric_value>. This is useful for programming simple devices in a straightforwardmanner.

At *RST, the signal being sourced should be set to a “safe” condition. This is generallyachieved by setting the amplitude to its minimum value in conjunction with OUTPut:STATesubsystem.

19.5.4.1.1.1 :AUTO <Boolean>|ONCESOURce:CURRent:LEVel:IMMediate:AMPLitude:AUTO

PH040

If AUTO ON is selected, the voltage setting will be adjusted automatically when a newcurrent setting (with the existing voltage setting) exceeds the maximum power limit. IfAUTO OFF is selected a new current setting will cause an execution error -221 (Settingsconflict), and the instrument state is device dependent when the maximum power limit isexceeded.

*RST condition: AUTO OFF

19.5.4.1.2 :OFFSet <numeric_value>SOURce:CURRent:LEVel:IMMediate:OFFSet

Sets the non-time varying component of the signal that is added to the time varying signalspecified in AMPLitude, in terms of the current operating units. The units are set to thedefault value, or alternately to a different value under the UNIT subsystem. WhenSOURce:FUNCtion is DC, the effect of the OFFSet is device-dependent.

At *RST, the signal being sourced should be set to a “safe” condition. This is generallyachieved by setting the offset to its minimum value in conjunction with OUTPut:STATesubsystem.

19.5.4.1.3 :HIGH <numeric_value>SOURce:CURRent:LEVel:IMMediate:HIGH

Sets the more positive peak of a time varying signal. It is used in conjunction with LOW.

At *RST, the signal being sourced should be set to a “safe” condition. This is achieved bysetting this to a minimum value in conjunction with OUTPut:STATe subsystem.

19.5.4.1.4 :LOW <numeric_value>SOURce:CURRent:LEVel:IMMediate:LOW

Sets the more negative peak of a time varying signal, it is used in conjunction with HIGH.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.5.4.2 :TRIGgeredSOURce:CURRent:LEVel:TRIGgered

Indicates that subsequent specification of a new signal amplitude is to be transferred to theIMMediate value upon receipt of a trigger signal.

At *RST, after the receipt of an ABORt command or upon being triggered, the value in theTRIGgered subsystem tracks the values in the IMMediate subsystem until a command in theTRIGgered subsystem is received. The purpose of tracking is so that spurious triggers do notchange the value of LEVel unexpectedly.

19.5.4.2.1 [:AMPLitude] <numeric_value> SOURce:CURRent:LEVel:TRIGgered:AMPLitude


19.5.4.2.2 :OFFSet <numeric_value> SOURce:CURRent:LEVel:TRIGgered:OFFSet

Sets the non-time varying component of the signal that is added to the time varying signalspecified in AMPLitude. The units are set to the default value, or to a different value underthe UNIT subsystem. When SOURce:FUNCtion is DC, the effect of OFFSet isdevice-dependent.

19.5.4.2.3 :HIGH <numeric_value> SOURce:CURRent:LEVel:TRIGgered:HIGH

This command is used to set the more positive peak of a time varying signal. It is used inconjunction with LOW.

19.5.4.2.4 :LOW <numeric_value> SOURce:CURRent:LEVel:TRIGgered:LOW

This command is used to set the more negative peak of a time varying signal. It is used inconjunction with HIGH.

19.5.5 :LIMit SOURce:CURRent:LIMit

Sets the maximum bounds on the output value. Setting a larger value will cause the outputlevel to be clamped to the LIMit value.

19.5.5.1 [:AMPLitude] <numeric_value> SOURce:CURRent:LIMit:AMPLitude

Sets the limit on the actual magnitude of the unswept output signal in terms of the currentoperating units. The units are set to the default value, or alternately to a different value underthe UNIT subsystem. AMPLitude may be used to specify the level for either a time varyingor non-time varying signal. OFFSet may only be used with AMPLitude, where AMPLitudeis used to specify a time varying load.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



Explicit reference to the AMPLitude node is optional. Any device that implements thissubsystem must accept and process commands, with or without the AMPLitude node, andrespond to them in the same way.


19.5.5.2 :OFFSet <numeric_value> SOURce:CURRent:LIMit:OFFSet

Sets a non-time varying component limit of signal that is added to the time varying signalspecified in AMPLitude. The units are set to the default value, alternately to a different valueunder the UNIT subsystem.


19.5.5.3 :HIGH <numeric_value> SOURce:CURRent:LIMit:HIGH

Sets the more positive peak limit of a time varying signal, it is used in conjunction withLOW.


19.5.5.4 :LOW <numeric_value> SOURce:CURRent:LIMit:LOW

Sets the more negative peak limit of a time varying signal, it is used in conjunction withHIGH.


19.5.5.5 :STATe <Boolean> SOURce:CURRent:LIMit:STATe



19.5.6 :MANual <numeric_value> SOURce:CURRent:MANual

Allows manual adjustment of the amplitude between the sweep limits. The actual amplitudelevel is determined by the parameter only if SWEep:MODE is set to MANual and theamplitude MODE is set to SWEep. If the sweep limits are changed such that the manualamplitude value would be outside the limits, the manual amplitude value will be set to thenearest limit.


19.5.7 :MODE FIXed|SWEep|LIST SOURce:CURRent:MODE

Determines which set of commands control the amplitude subsystem. If FIXed is selected,the amplitude is determined by the LEVel command under the appropriate subsystem. IfSWEep is selected, the source is in the swept mode and amplitude is determined by STARt,STOP, CENTer, SPAN, and MANual commands under the appropriate subsystem. If LIST is

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



selected, the amplitude values are determined by the appropriate amplitude list (such asLIST:).

At *RST, this value is set to FIXed.

19.5.8 :PROTectionSOURce:CURRent:PROTection


19.5.8.1 [:LEVel] <numeric_value> SOURce:CURRent:PROTection:LEVel

This command sets the output level at which the output protection circuit will trip.

19.5.8.2 :STATe <Boolean> SOURce:CURRent:PROTection:STATe



19.5.8.3 :TRIPped?SOURce:CURRent:PROTection:TRIPped?

This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped.

TRIPped only has a query form and thus has no associated *RST condition.

19.5.8.4 :CLEarSOURce:CURRent:PROTection:CLEar



19.5.9 :RANGe <numeric_value> SOURce:CURRent:RANGe

Sets a range for the output amplitude. This command is very hardware-specific.

19.5.9.1 :AUTO <Boolean>|ONCE SOURce:CURRent:RANGe:AUTO

Couples the RANGe to an instrument-determined value. When AUTO is ON, the best rangeis chosen to reflect the current instrument state.

Explicitly selecting a value for RANGe sets AUTO OFF.


19.5.10 :REFerence <numeric_value> SOURce:CURRent:REFerence

Sets a reference value which, if STATe is ON, allows all amplitude parameters to bequeried/set as relative to the reference value.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.5.10.1 :STATe <Boolean> SOURce:CURRent:REFerence:STATe

Determines whether amplitude is measured/output in absolute or relative mode. If STATe isON, then amplitude is referenced to the value set in REFerence.


19.5.11 :SLEW <numeric_value> SOURce:CURRent:SLEW

Sets the slew rate of the output change when a new output level is programmed. The unitsare in (the currently active) amplitude unit/sec.


19.5.12 :SPAN <numeric_value> SOURce:CURRent:SPAN

Sets the amplitude span. If the current amplitude unit is logarithmic (dBm, dBuV, etc), thenthe unit of SPAN is dB. Otherwise SPAN is programmed in the current amplitude unit.


19.5.12.1 :FULL SOURce:CURRent:SPAN:FULL

HP066When this command is received, STARt amplitude is set to its minimum value and STOPamplitude is set to its maximum value. CENTer amplitude and SPAN are set to their coupledvalues.

This command is an event rather than a state. Therefore it has no associated query, ormeaning at *RST.

19.5.12.2 :HOLD <Boolean>SOURce:CURRent:SPAN:HOLD



19.5.12.3 :LINK CENTer|STARt|STOPSOURce:CURRent:SPAN:LINK

Allows the default couplings for SPAN to be overridden. LINK selects the parameter, eitherCENTer, STARt or STOP, that shall not be changed when SPAN’s value is changed. Forexample, if LINK is set to STARt then changing SPAN shall cause CENTer and STOP, notSTARt to change.


19.5.13 :STARt <numeric_value> SOURce:CURRent:STARt

Sets STARt amplitude.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26




19.5.14 :STOP <numeric_value> SOURce:CURRent:STOP

Sets STOP amplitude.

At *RST, this value is set to MINimum. 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.6 DM SubsystemSOURce:DM

The Digital Modulation subsystem is used to set the modulation controls and the parametersassociated with the modulating signal(s). This modulation embraces a number of digitalmodulation techniques, which are described in the general terms of I and Q components. Thekeywords to describe the carrier signal exist in other subsystems (such as, FREQuency andPHASe).

KEYWORD PARAMETER FORM COMMENTS:DM :FORMat BPSK|PSK2|QPSK|PSK4|PSK8|QAM16|QAM64|

QAM256|QAM1024|PRS9|PRS25|PRS49|PRS81 :STATe <Boolean> :SOURce EXTernal|PRBS|CALibrate :FILTer [:SOURce] INTernal|EXTernal :ICORrection <numeric_value> :QCORrection <numeric_value> :IQRatio :STATe <Boolean> [:MAGNitude] <numeric_value> :LEAKage :STATe <Boolean> [:MAGNitude] <numeric_value> :ANGLe <numeric_value> :QUADrature :STATe <Boolean> :ANGLe <numeric_value> :COUPling [:ALL] AC|DC|GROund :DATA AC|DC|GROund :CLOCk AC|DC|GROund :THReshold [:ALL] <numeric_value> :DATA <numeric_value> :CLOCk <numeric_value> :DMODe SERial|PARallel :FRAMe :SOURce INTernal|EXTernal :POLarity [:ALL] NORMal|INVerted :I<n> NORMal|INVerted :Q<n> NORMal|INVerted :ICLock NORMal|INVerted :QCLock NORMal|INVerted

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-26 SOURce:DM

KEYWORD PARAMETER FORM COMMENTS :CLOCk :SOURce NONE|EXTernal

19.6.1 :FORMat <modulation format>SOURce:DM:FORMat

Sets the format type to be employed. It is expandable to any PRS<n>, QAM<n>, QPR<n> orPSK<n>. QPSK is an alias for PSK4 and BPSK is an alias for PSK2.


19.6.2 :STATe <Boolean> SOURce:DM:STATe

Turns the digital modulation subsystem ON or OFF. Turning digital modulation ON will notautomatically turn OFF any other types of modulation. Turning any or all modulations typesON or OFF must be done explicitly. Where a type of modulation is active, turning ONanother type of modulation will add to the set of active modulations if that combination ofcapabilities are legal in the device. Otherwise, an execution error -221 is generated and theinstrument state is left undefined.


19.6.3 :SOURce EXTernal|PRBS|CALibrate SOURce:DM:SOURce

Sets the source of digital modulation data. EXTernal means the digital data comes inexternally. The data can be also generated internally with PRBS (a pseudo-random bitsequencer). CALibrate is a service feature for calibrating the baseband of the device.

At *RST, this value must be set to EXTernal.

19.6.4 :FILTer SOURce:DM:FILTer

This subsystem is used to control the I and Q filters.

19.6.4.1 [:SOURce] INTernal|EXTernal SOURce:DM:FILTer:SOURce

This mnemonic allows a choice between INTernal or EXTernal I and Q filters.

At *RST, this value must be set to INTernal.

19.6.4.2 :ICORrection <numeric_value> SOURce:DM:FILTer:ICORrection

This mnemonic allows the entry of gain information about the EXTernal I filter. This has noeffect on the signal when INTernal filter source is selected.

AT *RST, this value must be set to 0.0DB.

19.6.4.3 :QCORrection <numeric_value> SOURce:DM:FILTer:QCORrection

This mnemonic allows the entry of gain information about the EXTernal Q filter. This has noeffect on the signal when INTernal filter source is selected.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:DM 19-27

At *RST, this value must be set to 0.0DB.

19.6.5 :IQRatioSOURce:DM:IQRatio

This subsystem controls the gain imbalance between the I and Q channels.

19.6.5.1 :STATe <Boolean> SOURce:DM:IQRatio:STATe

Turns ON and OFF the gain imbalance correction.


19.6.5.2 [:MAGNitude] <numeric_value> SOURce:DM:IQRatio:MAGNitude

Specifies the correction for the gain imbalance between the I and Q channels. This value isequal to I/Q.

At *RST, this value must be set to 0.0DB.

19.6.6 :LEAKage SOURce:DM:LEAKage

Carrier leakage is an offset added to the modulation pattern. Carrier leakage is measured asthe magnitude relative to the full scale of the original signal. Hence a carrier leakagemagnitude of 0dB would mean that the offset in the signal would be 1 full scale. Thissubsystem allows specification of the carrier leakage in angle-magnitude notation.

19.6.6.1 :STATe <Boolean> SOURce:DM:LEAKage:STATe

This command turns carrier leakage ON and off.


19.6.6.2 [:MAGNitude] <numeric_value> SOURce:DM:LEAKage:MAGNitude

Specifies the magnitude of carrier leakage relative to the full scale of the signal. 0.0dBmeans add 1 full scale of carrier leakage. 40dB would mean add (full scale - 40) amount ofdBm.


19.6.6.3 :ANGLe <numeric_value>SOURce:DM:LEAKage:ANGLe

Specifies the angle of carrier leakage.


19.6.7 :QUADratureSOURce:DM:QUADrature

This subsystem controls quadrature correction.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-28 SOURce:DM

19.6.7.1 :STATe <Boolean> SOURce:DM:QUADrature:STATe

Turns ON or OFF the quadrature angle correction.


19.6.7.2 :ANGLe <numeric_value>SOURce:DM:QUADrature:ANGLe

Specifies the angle of quadrature correction.

At *RST, this value must be set to 0.0DEG.

19.6.8 :COUPling SOURce:DM:COUPling

This subsystem controls the input coupling for the digital modulation inputs.

19.6.8.1 [:ALL] AC|DC|GROund SOURce:DM:COUPling:ALL

Sets the coupling of both the clock and data inputs to the instrument. This command is anevent, and therefore does not have an associated *RST condition

19.6.8.2 :DATA AC|DC|GROund SOURce:DM:COUPling:DATA

Sets the coupling of the data inputs to the instrument.


19.6.8.3 :CLOCk AC|DC|GROund SOURce:DM:COUPling:CLOCk

Sets the coupling of the clock inputs to the instrument.


19.6.9 :THResholdSOURce:DM:THReshold

This subsystem controls the detector thresholds for the digital modulation inputs.

19.6.9.1 [:ALL] <numeric_value> SOURce:DM:THReshold:ALL

Sets the threshold of both the clock and data inputs to the instrument.

19.6.9.2 :DATA <numeric_value> SOURce:DM:THReshold:DATA

Sets the threshold of the data inputs to the instrument.


19.6.9.3 :CLOCk <numeric_value> SOURce:DM:THReshold:CLOCk

Sets the threshold of the clock inputs to the instrument.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:DM 19-29

19.6.10 :DMODe SERial|PARallel SOURce:DM:DMODe

This command sets the data transfer mode. SERial means data is transferred serially andPARallel means the data is transferred in a parallel fashion.


19.6.11 :FRAMeSOURce:DM:FRAMe

This subsystem controls the framing for serialized digital modulation.

19.6.11.1 :SOURce INTernal|EXTernal SOURce:DM:FRAMe:SOURce

Selects the source frame when data is transferred serially. INTernal selects autoframing,while EXTernal selects user-supplied framing.

19.6.12 :POLarity [:ALL] NORMal|INVertedSOURce:DM:POLarity

Sets the polarity of all the clock and data inputs to the instrument.

19.6.12.1 :I<n> NORMal|INVerted SOURce:DM:POLarity NORMal:I<n>

Selects the polarity of data inputs for the I channel. <n> selects which data input where n canbe any number from 0-1 (largest DM format log4). For example, the range for n is 0-4 whenthe most complex mod format allowed is QAM1024.

At *RST, all I polarities must be set to NORM.

19.6.12.2 :Q<n> NORMal|INVerted SOURce:DM:POLarity NORMal:Q<n>

Selects the polarity of data inputs for the Q channel. <n> selects which data input where ncan be any number from 0-1 (largest DM format log4). For example, the range for n is 0-4when the most complex mod format allowed is QAM1024.

At *RST, all Q polarities must be set to NORM.

19.6.12.3 :ICLock NORMal|INVerted SOURce:DM:POLarity NORMal:ICLock

Selects the polarity of the I channel clock input.

At *RST, ICLock polarity must be set to NORM.

19.6.12.4 :QCLock NORMal|INVerted SOURce:DM:POLarity NORMal:QCLock

Selects the polarity of the Q channel clock input.

At *RST, QCLock polarity must be set to NORM.

19.6.13 :CLOCkSOURce:DM:CLOCk

This subsystem controls the clock for digital modulation.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-30 SOURce:DM

19.6.13.1 :SOURce NONE|INTernal|EXTernal SOURce:DM:CLOCk:SOURce

Selects either no clock (asynchronous operation) or external clocking.

At *RST, this value is device-dependent. 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:DM 19-31

19.7 FM SubsystemSOURce:FM

The Frequency Modulation subsystem is used to set the modulation controls and theparameters associated with the modulating signal(s). The keywords to describe the carriersignal exist in other subsystems (such as FREQuency and PHASe).

KEYWORD PARAMETER FORM COMMENTS:FM :COUPling AC|DC|GROund [:DEViation] <numeric_value> :EXTernal :COUPling AC|DC|GROund :IMPedance <numeric_value> :POLarity NORMal|INVerted :INTernal :FREQuency <numeric_value> :MODE LOCKed|UNLocked :POLarity NORMal|INVerted :SENSitivity <numeric_value> :SOURce EXTernal|INTernal{,EXTernal|,INTernal} :STATe <Boolean>

19.7.1 :COUPling AC|DC|GROundSOURce:FM:COUPling

COUPling at this level is used to set the coupling between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either as internal or externalsources. If COUPling is set to DC, then both AC and DC components of the signal pass. ACcoupling passes only the AC component of the signal. The GROund parameter allows themodulation to be turned ON without the modulating signal connected.


19.7.2 [:DEViation] <numeric_value>SOURce:FM:DEViation

Sets the modulation DEViation of an FM signal. The unit for DEViation is Hertz (Hz). Thiscommand is used where the DEViation can be controlled independently from the modulatingsignal voltage level. Alternatively, it is used to set a device capability that can indicate whenthe desired DEViation has been achieved.


19.7.3 :EXTernalSOURce:FMwEXTernal

Controls the specified external signal source. Where multiple external modulation sourcesare available, the EXTernal keyword may have a numeric suffix signifying the particularexternal signal source. If no number is given, a 1 is assumed.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-32 SOURce:FM

19.7.3.1 :COUPling AC|DC|GROundSOURce:FM:EXTernal:COUPling

COUPling at this level sets the coupling for only the specified external signal source. IfCOUPling is set to DC, then both AC and DC Modulation components of the signal pass.AC coupling passes only the AC component of the signal. The GROund parameter allowsthe specified external source to be turned ON without being connected.


19.7.3.2 :IMPedance <numeric_value>SOURce:FM:EXTernal:IMPedance

Sets the impedance of the specified external signal source. The units for IMPedance is Ohms.


19.7.3.3 :POLarity NORMal|INVertedSOURce:FM:EXTernal:POLarity

POLarity at this level sets the POLarity for only the specified external signal source.POLarity sets the relationship between the polarity of the applied modulation voltage and theresulting “direction” of modulation. The definition of “normal” polarity for FM modulatedsignal is a positive voltage which causes the instantaneous output frequency to increase.

At *RST, this value must be set to NORMal on.

19.7.4 :INTernalSOURce:FM:INTernal


19.7.4.1 :FREQuency <numeric_value>SOURce:FM:INTernal:FREQuency

Sets the frequency of the specified internal signal source. Some instruments may also allowthe internal signal source(s) to be controlled as a subsystem(s). The unit of FREQuency isHertz (Hz).


19.7.5 :MODE LOCKed|UNLockedSOURce:FM:MODE

Sets the synthesis mode employed in generating the FM signal. If MODE is set to LOCKedthen a PLL is used, in synthesizing the FM signal, to prevent frequency drift. If UNLockedthe phase locked loop is inactive.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FM 19-33

19.7.6 :POLarity NORMal|INVertedSOURce:FM:POLarity

POLarity, at this level, is used to set the polarity between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either as internal or externalsources. POLarity sets the relationship between the polarity of the applied modulationvoltage and the resulting “direction” of modulation. The definition of “normal” polarity forFM modulated signal is that a positive voltage causes the instantaneous output frequency toincrease.


19.7.7 :SENSitivity <numeric_value>SOURce:FM:SENSitivity

Controls the modulation deviation by setting a sensitivity Modulation to the modulationsignal voltage level. The unit for SENSitivity is Hertz/Volt (Hz/V).


19.7.8 :SOURce EXTernal|INTernal{,EXTernal|,INTernal}SOURce:FM:SOURce

Selects the source for the modulating signal, and it may specify a single source or a numberof sources. The specified sources, in the SOURce command, are all selected and turned on.Any sources from a previous selection that are not in the current selection list are deselectedand turned off. If multiple sources are selected and the device does not support thecombination requested in the SOURce command, an execution error -221 must be generated.




19.7.9 :STATe <Boolean>SOURce:FM:STATe

Turns frequency modulation ON or OFF. Turning FM ON will not automatically turn OFFany other types of modulation. Turning any or all modulations types ON or OFF must bedone explicitly. Where a type of modulation is active turning ON another type ofmodulation, will add to the set of active modulations if that combination of capabilities arelegal in the device. Otherwise, an execution error -221 is generated, and the instrument stateis device-dependent.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-34 SOURce:FM

19.8 FORCe SubsystemSOURce:FORCe

This node controls the force of the device.

KEYWORD PARAMETER FORM COMMENTS:FORCe 1999 :CDOWn 1999 :INITiate [event; no query]1999 :NRUNs <numeric_value> 1999 :RLDeviation 1999 :FACCeptance <numeric_value> 1999 :INITiate [event; no query]1999 :RMAXimum <numeric_value> 1999 :RVERify <numeric_value> 1999 :SOFFset <numeric_value> 1999 :CONFigure 1999 :ABRake 1999 :GAIN <numeric_value> 1999 [:STATe] <Boolean> 1999 :THReshold <numeric_value> 1999 :GRADe 1999 :LEVel <numeric_value> 1999 :SOURce INTernal|EXTernal 1999 [:STATe] <Boolean> 1999 [:VEHicle] 1999 :DCOefficient <numeric_value>{,<numeric_value>} 1999 :DINertia <numeric_value> 1999 [:STATe] <Boolean> 1999 :TCOefficient <numeric_value>{,<numeric_value>} 1999 :TINertia <numeric_value> 1999 :WEIGht <numeric_value> 1999 :INITiate [event; no query]1999 [:LEVel] <numeric_value> 1999 :RLSimulation [event; no query]1999 :INITiate [event; no query]1999

19.8.1 :CDOWn:SOURce:FORCe:CDOWn

Coast Down

This node contains the commands required to run a Dynamometer Coast Down procedure. Acoast down measures the force, power, and elapsed time over multiple speed intervals as avehicle or dynamometer roll coasts in road load simulation from a starting speed to a finalspeed. This procedure uses the values set in the :SOURce:FORCe:CONFigure node and theCDownSpeed table. The procedure results are stored in the CDownResult table. Measuredcoefficients are placed in the memory table CDownMCoeff and are determined after each

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FORCe 19-35

coast down run. CDownDCoeff should be calculated after coast down run according to SAEJ2264, but do not adjust the dyno-setting coefficients.

19.8.1.1 :INITiate:SOURce:FORCe:CDOWn:INITiate

This is an overlapped command. This command initiates the coast down using the currentparameters from the :CONFigure node and CDownSpeed Table. This command describes anevent and therefore has no associated *RST condition.



Set the DYNO operation condition register Coast Down Procedure bit indicating that aCoast down is executing. Note: The DYNO operation condition register will be furtherdefined in Volume 4.

Enter the theoretical data for the defined speed interval and configured parameters inCDownResult table.

Accelerate dynamometer to :SOURce:FORCe:CDOWn:SOFFset +(plus) the startingspeed for the first coast down interval, at the rate in :SOURce:ACCeleration . If thedynamometer determines this speed is not appropriate for the defined coast down, set theDYNO questionable condition register Coastdown Speed bit and issue an error message,but continue on with the procedure.

Coast down over the speed intervals defined in the CDownSpeed table. The first intervalthat has 0 for start and stop speeds ends the measurement. For each interval defined inCDownSpeed, place the measured force, power, and time CDownResult table for thecoast down being executed. Remaining entries should be set to 0.

Perform a curve fit on the CDownResult data and place the coefficients in the memorytable CDownMCoeff.

Repeat the coast down sequence for :SOURce:FORCe:CDOWn:NRUNs

After the last measurement, issue the process complete message and wait for a command.

When commanded out of this procedure, clear the DYNO operation condition registerCoastdown Procedure bit indicating that the Coast down is not executing.

19.8.1.2 :SOFFset <numeric_value>:SOURce:FORCe:CDOWn:SOFFset

Speed Offset - m/s

This command sets how much speed offset above the top speed in the CDownSpeed Table towhich the dynamometer should be accelerated before beginning the coast down. This offsetallows the dynamometer response to settle before coasting into the first speed segment.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-36 SOURce:FORCe

19.8.1.3 :NRUNs <numeric_value>:SOURce:FORCe:CDOWn:NRUNs

This command sets the number of coast downs to run.


19.8.1.4 :RLDerivation:SOURce:FORCe:CDOWn:RLDerivation

Road Load Derivation

This node contains the commands required to run a Dynamometer Road Load Derivation.This procedure will run a series of coast downs with the vehicle on the dyno to determine adyno-setting that will match the results from the track. The coast down procedure is definedby the SAE publication J2264 (See Appendix A - References for information on thispublication.). Additional input for this procedure comes from the:SOURce:FORCe:CONFigure node, CDownSpeed table, CDownDCoeff, CDownMCoeff,and CDownResult table. The initial dynamometer coefficients (“best guess”) will be in thefirst row of CDownDCoeff prior to starting this procedure.

19.8.1.4.1 :FACCeptance <numeric_value>:SOURce:FORCe:CDOWn:RLDerivation:FACCeptance

Force Acceptance - N

This command sets the maximum acceptable force difference between the force vs. speedcurve derived from the dynamometer target and measured coefficients. This is the maximumdifference found at any of the specified coast down speed points.


19.8.1.4.2 :INITiate:SOURce:FORCe:CDOWn:RLDerivation:INITiate

This is an overlapped command. This command initiates the coast down simulation using thecurrent parameters in the :CONFigure node and CDownSpeed Table. This commanddescribes an event and therefore has no associated *RST condition.



Set the DYNO operation condition register Road Load Simulation Procedure bitindicating that a Road Load Derivation is executing. Note: The DYNO operationcondition register will be further defined in Volume 4.

Enter the theoretical data for the defined speed interval and configured parameters inCDownResult table based on the target values in:SOURce:FORCe:CONFigure:VEHicle:TCOefficient and :TINertia.

Accelerate dynamometer to :SOURce:FORCe:CDOWn:SOFFset +(plus) the startingspeed for the first coast down interval, at the rate in :SOURce:ACCeleration . If the

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FORCe 19-37

dynamometer determines this speed is not appropriate for the defined coast down, set theDYNO questionable condition register Coast down Trigger Speed bit and issue an errormessage, but continue on with the procedure.

Coast down over the speed intervals defined in the CDownSpeed table. The first intervalthat has 0 for start and stop speeds ends the measurement for this coast down.

For each coast down, calculate the dyno setting coefficients and measured coefficients.Measured coefficients are placed in CDownMCoeff, and dyno setting coefficients areplaced in CDownDCoeff. Also update:SOURce:FORCe:CONFigure:VEHicle:DCOefficient.

For the present coast down, if the absolute difference between the measured and targetforce limit is less than the value:SOURce:FORCe:CDOWn:RLDerivation:FACCeptance, begin verification coast downs.If not, adjust the dyno set coefficients as outlined in SAE J2264, and perform anothercoast down. For verification coast downs, perform up to:SOURce:FORCe:CDOWn:RLDerivation:RVERification coast downs.

If the number of coast downs performed is equal to:SOURce:FORCe:CDOWn:RLDerivation:RMAXimum, or any of the verification runs isnot within :SOURce:FORCe:CDOWn:RLDerivation:FACCeptance, the procedure failedto converge. If the procedure fails to converge set the DYNO questionable conditionregister bit 8 and issue an error message.

After the last coast down measurement, issue the process complete message. Clear theDYNO operation condition register bit 8 indicating that the Road Load Derivation is notexecuting.


19.8.1.4.3 :RMAXimum <numeric_value>:SOURce:FORCe:CDOWn:RLDerivation:RMAXimum

Runs Maximum

This command sets the maximum number of coast down runs the Road Load Derivation testwill run without convergence.


19.8.1.4.4 :RVERify <numeric_value>:SOURce:FORCe:CDOWn:RLDerivation:RVERify

Runs to Verify

This command sets the maximum number of verification coast down runs after convergenceof the Road Load Derivation procedure.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-38 SOURce:FORCe

19.8.2 :CONFigure:SOURce:FORCe:CONFigure

This node configures the force for various procedures. For dynamometers, these proceduresmay be Road Load Simulation, Coast downs, etc.

19.8.2.1 :ABRake:SOURce:FORCe:CONFigure:ABRake

Augmented Brake

This node contains the commands to setup the Augmented Brake. This system utilizes thedynamometer to use regenerative braking of the rolls to simulate the brakes of the non-drivenwheels.

19.8.2.1.1 :GAIN <numeric_value>:SOURce:FORCe:CONFigure:ABRake:GAIN

The augmented brake gain is used to adjust how much simulated braking assistance force isrequired.


19.8.2.1.2 [:STATe] <Boolean>:SOURce:FORCe:CONFigure:ABRake[:STATe]

This command sets the augmented brake simulation state.


19.8.2.1.3 :THReshold <numeric_value>:SOURce:FORCe:CONFigure:ABRake:THReshold

This command sets the vehicle force absorption level in N to initiate a simulated brakingforce for the non-rotating wheel brakes.


19.8.2.2 :GRADe:SOURce:FORCe:CONFigure:GRADe

This node contains the commands to setup the grade input for the Road Load Simulation and[if desired] for Coast downs.

19.8.2.2.1 :LEVel <numeric_value>:SOURce:FORCe:CONFigure:GRADe:LEVel

This command sets the grade force in units of Percent Grade. For example, a 45 degree slopeis a 100% grade. The resulting force is given by:

FORCe = WEIGht * sin(arctan(GRADe/100))


19.8.2.2.2 :SOURce <INTernal|EXTernal>:SOURce:FORCe:CONFigure:GRADe:SOURce

This command sets the source for grade. The grade set by:SOURce:FORCe:CONFigure:GRADe:LEVel is used when the source is “INTernal”. The

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FORCe 19-39

host computer can vary the grade at any time during the simulation by sending a new LEVelcommand. If set to “EXTernal”, then the simulation will include the grade from an externalanalog input (Full Scale volts = 100% = 45(). “EXTernal” is used when a dynamometer isequipped with an analog input to control the grade.

At *RST, this value is set to INTernal.

19.8.2.2.3 [:STATe] <Boolean>:SOURce:FORCe:CONFigure:GRADe[:STATe]

This command sets the grade simulation state. If the state is OFF, the simulation does notinclude a grade force. If the state is ON, the simulation includes the grade force from aninternal or external source.


19.8.2.3 [:VEHicle]:SOURce:FORCe:CONFigure[:VEHicle]

This node configures the dynamometer vehicle parameters. These parameters are thedynamometer operating set-points [e.g., inertia, road-load, etc.].

19.8.2.3.1 :DCOefficient <numeric_value>,<numeric_value>,<numeric_value>[,<numeric_value>]

:SOURce:FORCe:CONFigure:VEHicle:DCOefficient

Dynamometer-setting Coefficient(s) - N, N/(m/s), N/(m/s)2[,N/(m/s)3 ]

This command sets the coefficients of the road-load polynomial for the force to be simulated.The query form of this command should return the active dynamometer coefficients, whichmay have been determined from a Road Load Derivation procedure. When the fourthparameter is omitted, it is assumed 0.

At *RST, this value is set to 0,0,0,0

19.8.2.3.2 :DINertia <numeric_value>:SOURce:FORCe:CONFigure:VEHicle:DINertia

Dynamometer-setting Inertia - kg

This command sets the “Inertia” (in kg) to be simulated by the dynamometer. This is the totalvehicle inertia (vehicle weight plus “inertia weight” of the rotating components) minus theinertia of the driven wheels and drive train (which will be spinning when the vehicle isdriven on the dynamometer). When default is specified the dynamometer-setting inertia willbe the mechanical base inertia.

At *RST, this value is set to the Mechanical Base Inertia.

19.8.2.3.3 [:STATe] <Boolean>:SOURce:FORCe:CONFigure:VEHicle[:STATe]

This command tells the dynamometer that a vehicle is on the rolls.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-40 SOURce:FORCe

19.8.2.3.4 TCOefficient <numeric_value>,<numeric_value>,<numeric_value>[,<numeric_value>]

:SOURce:FORCe:CONFigure:VEHicle:TCOefficient

Target-setting Coefficient(s) - N, N/(m/s), N/(m/s)2 [,N/(m/s)3 ]

This command sets the Target Road-Load Coefficients for the road load derivation or coastdown procedure. These are derived from test track data for a vehicle. The host will updatethese values prior to executing a coast down or road load derivation. Target coefficients arenever used to control the dynamometer. When the fourth parameter is omitted, it is assumed0.

At *RST, this value is set to 0,0,0,0

For road load derivation, TCOefficient are used to:

calculate theoretical data in CDownResult memory table

compare against measured coast down coefficients as defined in J2264

For coast downs with or without a vehicle, TCOefficient are used to:

calculate theoretical data in CDownResult memory table

19.8.2.3.5 :TINertia <numeric_value>:SOURce:FORCe:CONFigure:VEHicle:TINertia

Target-setting Inertia - kg

This command sets the target inertia (kg) for a road load derivation procedure. Target inertiais defined in SAE J2264.


19.8.2.3.6 :WEIGht <numeric_value>:SOURce:FORCe:CONFigure:VEHicle:WEIGht

Weight - kg

This command sets the (kg) weight of vehicle, not including the “inertia weight” of thewheels and drive-train. The value is used to calculate grade and augmented braking weightratio (when simulating braking force of the non-driven wheels).


19.8.3 :INITiate:SOURce:FORCe:INITiate

This command initiates force. This is an overlapped command. This command describes anevent and therefore has no associated *RST condition.



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FORCe 19-41

Set the DYNO operation condition register Go To Force Procedure bit indicating that GoTo Force Procedure is executing. Note: The DYNO operation condition register will befurther defined in Volume 4.

Apply the force set in :SOURce:FORCe:LEVel.

Maintain the force and wait for a command.

When commanded out of this procedure, clear the DYNO operation condition register GoTo Force Procedure bit indicating the Go To Force Procedure is not executing.


19.8.4 [:LEVel] <numeric_value>:SOURce:FORCe[:LEVel]

Sets the force set-point in N.


19.8.5 :RLSimulation:SOURce:FORCe:RLSimulation

Road Load Simulation

This node sets the dynamometer into the procedure to apply a load to simulate vehicleoperation on the road. These commands use the values set in the:SOURce:FORCe:CONFigure node.

19.8.5.1 :INITiate:SOURce:FORCe:RLSimulation:INITiate

This is an overlapped command. This command initiates the Road Load Simulation using thepresent parameters in the :CONFigure node. This command describes an event and thereforehas no associated *RST condition.



Set the DYNO operation condition register Road Load Simulation Procedure bitindicating that Road Load Simulation is executing. Note: The DYNO operation conditionregister will be further defined in Volume 4.

Begin simulating the load defined by:SOURce:FORCe:CONFigure:VEHicle:DINertia;DCOefficient;GRADe; ABRake

When commanded out of this procedure, clear the DYNO operation condition register bit4 indicating that Road Load Simulation is not executing.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-42 SOURce:FORCe

19.9 FREQuency SubsystemSOURce:FREQuency

The FREQuency subsystem controls the frequency characteristics of the instrument. Twotypes of controls are included in this subsystem. The first is frequency sensor controls, suchas RANGe. The second is frequency sweep controls such as STARt, or tuning controls suchas CW.

KEYWORD PARAMETER FORM COMMENTS:FREQuency :CENTer <numeric_value> [:CW|:FIXed] <numeric_value> :AUTO <Boolean>|ONCE :MANual <numeric_value> :MODE CW|FIXed|SWEep|LIST|SENSe :MULTiplier <numeric_value> :OFFSet <numeric_value> :RESolution <numeric_value> 1992 RS001

:AUTO <Boolean> | ONCE 1992 RS001

:SPAN <numeric_value> :FULL [no query] :HOLD <Boolean> :LINK CENTer|STARt|STOP :STARt <numeric_value> :STOP <numeric_value>

19.9.1 :CENTer <numeric_value>SOURce:FREQuency:CENTer

Sets the CENTer frequency.

At *RST, this function will be set to (MINimum+MAX)/2.

19.9.2 [:CW|:FIXed] <numeric_value>SOURce:FREQuency:CW

The Continuous Wave or FIXed node is used to select a frequency of a non-swept signal.This node is optional. An optional node, such as [:CW|:FIXed], implies that the device shallaccept and process commands with or without the optional node and have the same result.That is, the device is required to accept the optional node, if sent, without error. A devicemust accept both :CW and :FIXed if it implements this node.


19.9.2.1 :AUTO <Boolean>|ONCESOURce:FREQuency:CW:AUTO

Couples the CW frequency to center frequency. Explicitly setting a value forFREQuency:CW sets AUTO OFF.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FREQuency 19-43

19.9.3 :MANual <numeric_value>SOURce:FREQuency:MANual

Ed changeSame as CW except limited by STARt and STOP. Receipt of this command will only changethe frequency if SWEep:MODE MANual subsystem and FREQuency:MODE SWEep isselected. If the sweep limits are changed such that manual frequency would be outside thesweep limits, then the manual frequency will be set to the nearest end point of the sweep.

At *RST, FREQuency:MAN is device-dependent.

19.9.4 :MODE CW|FIXed|SWEep|LIST|SENSeSOURce:FREQuency:MODE

Determines which set of commands control the frequency subsystem. The settings have thefollowing meanings:

CW|FIXed: The frequency is determined by FREQuency[:CW] orFREQuency[:FIXed]. CW and FIXed are aliases. Both must be implemented, ifeither is implemented.

SWEep: The source is in the swept mode and frequency is determined byFREQuency:STARt, STOP, CENT, SPAN, and MAN.

LIST: The source is in LIST sequence mode and frequency is determined byLIST:FREQuency.

SENSe: The source is coupled to the sensor. All frequency controls aredetermined by the SENSe:FREQuency block, except for OFFSet and MULTiplier.These two commands remain active under SOURce to allow for offset andharmonic tracking.

At *RST, this value is set to CW.

19.9.5 :MULTiplier <numeric_value>SOURce:FREQuency:MULTiplier

Sets a reference multiplier for all other frequency settings in the instrument. All entered anddisplayed frequencies are affected by this command. The coupling equation is:

Entered|Displayed frequency = ( Hardware frequency * multiplier ) + offset

This command affects the values of all functions which affect generation of the signal. Thisincludes such things as CW frequency and the sweep frequency controls. It does not affectthings like input filter bandwidths. It does affect the settings of relative frequency parameterssuch as delta markers or FM deviation. Also note that this command does not affect thehardware settings of the instrument, but only the entered and displayed frequencies.


19.9.6 :OFFSet <numeric_value>SOURce:FREQuency:OFFSet

Sets a reference frequency for all other absolute frequency settings in the instrument. Thiscommand affects the values of all functions which affect generation of the signal. Thisincludes such things as CW frequency and the sweep frequency controls. It does not affect

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-44 SOURce:FREQuency

things like input filter bandwidths. It also does not affect the settings of relative frequencyparameters such as delta markers or FM deviation. Also note that this command does notaffect the hardware settings of the instrument, but only the entered and displayedfrequencies. The coupling equation is:

Entered|Displayed frequency = ( Hardware frequency * multiplier ) + offset


19.9.7 :RESolution <numeric_value>SOURce:FREQuency:RESolution

RS001

RESolution sets or queries the absolute increment/decrement, at which the frequency of theoutput signal can be changed. The default unit for <numeric_value> is Hertz.


19.9.7.1 AUTO <Boolean> | ONCESOURce:FREQuency:RESolution:AUTO

RS001

AUTO couples the RESolution to an instrument-determined value. When AUTO is ON, thebest resolution is chosen to reflect the current instrument state.

Explicitly selecting a value for RESolution will set AUTO OFF.


19.9.8 :SPAN <numeric_value>SOURce:FREQuency:SPAN

Sets the frequency SPAN.

At *RST, this function will be set to MAXimum.

19.9.8.1 :FULLSOURce:FREQuency:SPAN:FULL

When this command is received, STARt frequency is set to its minimum value, and STOPfrequency is set to its maximum value. CENTer frequency and SPAN are set to their coupledvalues.

This command is an event, rather than a state. Therefore it has no associated query, ormeaning at *RST.

19.9.8.2 :HOLD <Boolean>SOURce:FREQuency:SPAN:HOLD

The HOLD command provides a mechanism to prevent the SPAN from being changedimplicitly by the defined coupling between STARt, STOP, CENTer, and SPAN. WhenHOLD is set to ON, SPAN shall only be changed by explicitly sending the SPAN command.


19.9.8.3 :LINK CENTer|STARt|STOPSOURce:FREQuency:SPAN:LINK

This command allows the default couplings for SPAN to be overridden. LINK selects theparameter, either CENTer subsystem, STARt or STOP, that shall not be changed when

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FREQuency 19-45

SPAN’s value is changed. For example, if LINK is set to STARt then changing SPAN shallcause CENTer and STOP, not STARt to change.


19.9.9 :STARt <numeric_value>SOURce:FREQuency:STARt

Sets the STARting frequency. It also sets the lower limit of a manual sweep adjustment. Ifthe instrument does not support negative frequency spans, having the STARt frequencygreater than the STOP frequency will cause an error to be generated.

At *RST, this value will be set to MINimum.

19.9.10 :STOP <numeric_value>SOURce:FREQuency:STOP

Sets the STOP frequency. It also sets the upper limit of a manual sweep adjustment. If theinstrument does not support negative frequency spans, having the STOP frequency less thanthe STARt frequency will cause an error to be generated.

At *RST, this value will be set to MAXimum.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-46 SOURce:FREQuency

19.10 FUNCtion SubsystemSOURce:FUNCtion

The function subsystem controls the shape and attributes of the output signal. The switchsettings provided by this function are not horizontally compatible and represent what thesource can be configured to generate directly.

KEYWORD PARAMETER FORM COMMENTS:FUNCtion [:SHAPe] <source_shape> :MODE <source_mode>

19.10.1 [:SHAPe] <source_shape>SOURce:FUNCtion:SHAPe

Selects the shape of the output signal.

At *RST, the value of FUNCtion is device-dependent.

The following SOURce functions are available for instruments:

DC — An unvarying signal with respect to time.

IMPulse — IMPulse is an approximation of a zero width pulse HP022

PCHirp — PeriodicCHirp supplies a sine sweep over the current frequency spanwhich periodically repeats. HP022

PRNoise — PeriodicRandomNoise provides a randomly varying signal withrespect to time which periodically repeats. HP022

PULSe — A pulse, or string of pulses is generated.

RANDom — provides a randomly varying signal with respect to time. HP022

SINusoid — A sinusoidal signal is generated.

SQUare — A square wave signal is generated.

TRIangle — A triangular wave signal is generated.

USER — The USER function allows the user to specify a periodic or arbitrarywaveform definition.

19.10.2 :MODE <source_mode>SOURce:FUNCtion:MODE

Determines which signal characteristic is being controlled.

At *RST, the value of this function is device-dependent.

The function may be set to the following values:

VOLTage.

CURRent.

POWer.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:FUNCtion 19-47

19.11 LIST SubsystemSOURce:LIST

The list subsystem controls automatic sequencing through associated lists of specified signalvalues. It is also used to specify concurrent or simultaneous operation of the specified signalin the associated lists. The various values are specified in the LIST subsystem commands.The individual points in each of the list configuration commands are combined to make onesignal configuration.

The LIST subsystem controls a characteristic of the instrument when that subsystem’s modeis set to LIST (such as :FREQuency:MODE LIST). Note that is permissible to have onecharacteristic controlled by the list subsystem, and the others controlled by a differentsubsystem (such as :FREQuency:MODE LIST or :POWer:MODE SWEep).

When employing multiple lists, all lists must be of the same length. If they are not all of thesame length, an error is generated at sequencing time. An exception is made for the casewhere the shorter list is of length 1. In this case, the particular list is treated as though it werea list of equal length, with all values being the same.

Lists are not affected by *RST.

KEYWORD PARAMETER FORM COMMENTS:LIST :AM 1993 EM003 [:DEPTh] <numeric_value>{,<numeric_value>} 1993 EM003 :POINts? [query only] 1993 EM003 :APRobe <numeric_list>{,<numeric_list>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :CONCurrent <numeric_value>{,<numeric_value>} :AUTO <Boolean>|ONCE :POINts? [query only] :CONTrol 1993 XSS01c :APOWer <Boolean>{,<Boolean>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :BLOWer <Boolean>{,<Boolean>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :COMPressor <Boolean>{,<Boolean>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :COUNt <numeric_value> :CURRent <numeric_value>{,<numeric_value>} :POINts? [query only] :DIRection UP|DOWN :DWELl <numeric_value>{,<numeric_value>} :POINts? [query only ] :FREQuency <numeric_value>{,<numeric_value>} :POINts? [query only] :GENeration DSEQuence|SEQuence|DCONcurrent

|CONCurrent

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-48 SOURce:LIST

KEYWORD PARAMETER FORM COMMENTS :POWer <numeric_value>{,<numeric_value>} :POINts? [query only] :PULM 1993 EM004 [:STATe] <Boolean>{,<Boolean>} 1993 EM004 :POINts? [query only] 1993 EM004 :RESistance <numeric_value>{,<numeric_value>} :POINts? [query only] :RTIMe <numeric_value>{,<numeric_value>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :SEQuence <numeric_value>{,<numeric_value>} :AUTO <Boolean>|ONCE :POINts? [query only] :TEMPerature <numeric_value>{,<numeric_value>} 1993 XSS01c :POINts? [query only] 1993 XSS01c :VOLTage <numeric_value>{,<numeric_value>} :POINts? [query only] HP066

19.11.1 :AM EM003SOURce:LIST:AM

Subsystem for setting up the AM list values.

19.11.1.1 :DEPTh <numeric_value>{,<numeric_value>} EM003SOURce:LIST:AM:DEPTh

Specifies the AM DEPTh points of the list.

19.11.1.1.1 :POINts? EM003SOURce:LIST:AM:DEPTh:POINTs?

Returns the number of points currently in the AM DEPth list.

19.11.2 :APRobe <numeric_list>{,<numeric_list>} XSS01cSOURce:LIST:APRobe

APRobe selects the specified probe/s to control the temperature.

19.11.2.1 :POINts? XSS01cSOURce:LIST:APRobe:POINts?

Returns the number of points currently in the APRobe list.

19.11.3 :CONCurrent <numeric_value>{,<numeric_value>}SOURce:LIST:CONCurrent

Defines a list which indicated those elements of the signal list which shall be active, whenCONCurrent operation is selected. The points specified are indexes into the lists. Forexample, if 3 and 5 were selected, the third and fifth points in the signal list would begenerated simultaneously. All entries in the CONCurrent list must be unique; otherwise aparameter error (-220) will be generated. The concurrent list is separate from the other listsand is not sorted, nor are the individual points associated with the other arrays except asdescribed above.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:LIST 19-49

19.11.3.1 :AUTO <Boolean>|ONCESOURce:LIST:CONCurrent:AUTO

When on, the CONCurrent list is set to 1-N, where N is the longest list.

At *RST, AUTO ON is selected.

19.11.3.2 :POINts?SOURce:LIST:CONCurrent:POINts?

Returns the number of points currently in the CONCurrent list.

19.11.4 :CONTrol XSS01cSOURce:LIST:CONTrol

Allows to turn on/off the devices

19.11.4.1 :APOWer <Boolean>{,<Boolean>} XSS01cSOURce:LIST:CONTrol:APOWer

Turns the APOWer on or off.

19.11.4.1.1 :POINts? XSS01cSOURce:LIST:CONTrol:APOWer:POINts?

Returns the number of points currently in the APOWer list.

19.11.4.2 :BLOWer <Boolean>{,<Boolean>} XSS01cSOURce:LIST:CONTrol:BLOWer

Turns the BLOWer on or off.

19.11.4.2.1 :POINTs? XSS01cSOURce:LIST:CONTrol:BLOWer:POINts?

Returns the number of points currently in the BLOWer list.

19.11.4.3 :COMPressor <Boolean>{,<Boolean>} XSS01cSOURce:LIST:CONTrol:COMPressor

Turns the COMPressor on or off.

19.11.4.3.1 :POINTs? XSS01cSOURce:LIST:CONTrol:COMPressor:POINts?

Returns the number of points currently in the COMPressor list.

19.11.5 :COUNt <numeric_value>SOURce:LIST:COUNt

Controls the number of times the list is sequenced when a trigger is received.


19.11.6 :CURRent <numeric_value>{,<numeric_value>}SOURce:LIST:CURRent

Specifies the current points of the lists.

19.11.6.1 :POINts?SOURce:LIST:CURRent:POINts?

Returns the number of points currently in the CURRent list.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-50 SOURce:LIST

19.11.7 :DIRection UP|DOWNSOURce:LIST:DIRection

Specifies the direction that the sequence list is scanned. If UP is selected, the list is scannedfrom the first to the last item in the sequence list. If DOWN is selected, the list is scannedfrom the last item to the first item in the sequence list.

At *RST, this value is set to UP.

19.11.8 :DWELl <numeric_value>{,<numeric_value>}SOURce:LIST:DWELl

Specifies the dwell time points of the lists.

19.11.8.1 :POINts?SOURce:LIST:DWELl:POINts?

Returns the number of points currently in the DWELl list.

19.11.9 :FREQuency <numeric_value>{,<numeric_value>}SOURce:LIST:FREQuency

Specifies the frequency points of the list set.

19.11.9.1 :POINts?SOURce:LIST:FREQuency:POINts?

Returns the number of points currently in the FREQuency list.

Since this is only a query, there is no associated *RST state.

19.11.10 :GENeration DSEQuence|SEQuence|DCONcurrent|CONCurrentSOURce:LIST:GENeration

The GENeration command is used to select how the defined lists are applied in a particularinstrument. An instrument may support one or more of the generation modes. SelectingDefault SEQuence (DSEQuence) causes the instrument to cycle sequentially through thecomplete list in order. When SEQuence is selected, the sequence in which the list is used isspecified by the list given in the SEQuence command. Selecting Default CONcurrent causesthe device to simultaneously generate all items in the list. When CONCurrent is selected, thelist specified by the CONCurrent command defines which elements in the list are activesimultaneously.

At *RST, GENeration shall be set to DSEQuence.

19.11.11 :PULM EM004SOURce:LIST:PULM

Subsystem for setting up the PULM list values.

19.11.11.1 :STATe <Boolean>{,<Boolean>} EM004SOURce:LIST:PULM:STATe

Specifies the PULM STATe points of the list.

19.11.11.1.1 :POINts? EM004SOURce:LIST:PULM:STATe:POINts?

Returns the number of points currently in the PULM STATe list.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:LIST 19-51

19.11.12 :POWer <numeric_value>{,<numeric_value>}SOURce:LIST:POWer

Specifies the power/amplitude points of the lists.

19.11.12.1 :POINts?SOURce:LIST:POWer:POINts?

Returns the number of points currently in the POWer list.

19.11.13 :RESistance <numeric_value>{,<numeric_value>}SOURce:LIST:RESistance

Specifies the resistance points of the lists.

19.11.13.1 :POINts?SOURce:LIST:RESistance:POINts?

Returns the number of points currently in the RESistance list.

19.11.14 :RTIMe <numeric_value>{,<numeric_value>} XSS01cSOURce:LIST:RTIMe

Ramp TIMe controls the time required to reach the target temperature.

19.11.14.1 :POINTs? XSS01cSOURce:LIST:RTIMe:POINts?

Returns the number of points currently in the RTIMe list.

19.11.15 :SEQuence <numeric_value>{,<numeric_value>}SOURce:LIST:SEQuence

Defines a sequence for stepping through the list, when SEQuence operation is selected.Individual points may be specified as many times as desired in a single sequence. The pointsspecified are indexes into the lists. For example, if 3 was selected, the third point in thefrequency, dwell, and power/amplitude lists would be sequenced.

The sequence list is separate from the other lists and is not sorted, nor are the individualpoints associated with the other arrays except as described above.

19.11.15.1 :AUTO <Boolean>|ONCESOURce:LIST:SEQuence:AUTO

When on, the sequence list is set to 1 through N, where N is the longest list.


19.11.15.2 :POINts?SOURce:LIST:SEQuence:POINts?

Returns the number of points currently in the SEQuence list.

19.11.16 :TEMPerature <numeric_value>{,<numeric_value>} XSS01cSOURce:LIST:TEMPerature

TEMPerature is the target temperature.

19.11.16.1 :POINTs? XSS01cSOURce:LIST:TEMPerature:POINts?

Returns the number of points currently in the TEMPerature list.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-52 SOURce:LIST

19.11.17 :VOLTage <numeric_value>{,<numeric_value>}SOURce:LIST:VOLTage

Specifies the voltage points of the lists.

19.11.17.1 :POINts?SOURce:LIST:VOLTage:POINts?

Returns the number of points currently in the VOLT list. 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:LIST 19-53

19.12 MARKer SubsystemSOURce:MARKer

Selects between different markers, and adjusts the marker settings. The suffix with MARKerselects the marker with the same number associated with it. If the suffix is omitted, thenmarker #1 is assumed.

KEYWORD PARAMETER FORM COMMENTS:MARKer :AMPLitude ON|OFF :AOFF [no query] :FREQuency <numeric_value> :MODE FREQuency|POSition|DELTa :POINt <numeric_value> :REFerence <numeric_value> [:STATe] <Boolean> :TIME <numeric_value>

19.12.1 :AMPLitude <Boolean>SOURce:MARKer:AMPLitude

Controls whether the marker affects the signal. If ON, the signal is modified when themarker frequency equals the output frequency. If OFF, only the marker output port isaffected.


19.12.2 :AOFFSOURce:MARKer:AOFF

Turns OFF all markers. This command is an event, and therefore has no query form. Allmarkers shall be turned OFF at *RST.

19.12.3 :FREQuency <numeric_value>SOURce:MARKer:FREQuency

Controls the absolute frequency of the specified marker when MARKer:MODE isFREQuency. When MARKer:MODE is DELTa, this command controls relative frequency.


19.12.4 :MODE FREQuency|POSition|DELTaSOURce:MARKer:MODE

This command controls whether the marker is tied to a frequency, referenced to an absolutetrace point (position), or referenced to another marker (delta). If delta is selected,MARKer:REFerence determines which marker the current marker is referenced to.

At *RST, this value is FREQuency.

19.12.5 :POINt <numeric_value>SOURce:MARKer:POINt

Sets the marker to the specified sweep point.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-54 SOURce:MARKer

19.12.6 :REFerence <numeric_value>SOURce:MARKer:REFerence

MARK:REFerence establishes a reference marker for delta markers.


19.12.7 [:STATe] <Boolean>SOURce:MARKer:STATe

Turns ON and OFF the marker specified by the MARKer command header suffix.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:MARKer 19-55

19.13 PHASe SubsystemSOURce:PHASe

This subsystem allows control of the phase of the output signal against some reference.

KEYWORD PARAMETER FORM COMMENTS:PHASe [:ADJust] <numeric_value> :STEP <numeric_value> :SOURce INTernal[<n>]|EXTernal[<n>] :REFerence [no query]

19.13.1 [:ADJust] <numeric_value>SOURce:PHASe:ADJust

Controls the phase offset value relative to the reference. A negative value for ADJust shallcause the output signal to lag the reference.

The parameter has units of radians. The command shall accept a DEGree suffix.

At *RST, this value is 0.

19.13.1.1 :STEP <numeric_value>SOURce:PHASe:ADJust:STEP

Controls the step size in radians. The command shall accept a DEGree suffix.


19.13.2 :SOURce INTernal|EXTernal SOURce:PHASe:SOURce

Determines whether the reference source is an external signal or if it is the internal signalitself marked at some reference time.

At *RST, this setting is device-dependent.

19.13.3 :REFerenceSOURce:PHASe:REFerence

This is an event which sets the current phase to be the reference for future phase adjustments.This function is nonqueryable.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-56 SOURce:PHASe

19.14 PM SubsystemSOURce:PM

The Phase Modulation subsystem is used to set the modulation controls and the parametersassociated with the modulating signal(s). The keywords to describe the carrier signal exist inother subsystems (such as FREQuency and PHASe).

KEYWORD PARAMETER FORM COMMENTS:PM [:DEViation] <numeric_value> :SENSitivity <numeric_value> :MODE LOCKed|UNLocked :STATe <Boolean> :SOURce EXTernal|INTernal{,EXTernal|,INTernal} :COUPling AC|DC|GROund :POLarity NORMal|INVerted :INTernal :FREQuency <numeric_value> :EXTernal :IMPedance <numeric_value> :COUPling AC|DC|GROund :POLarity NORMal|INVerted

19.14.1 [:DEViation] <numeric_value>SOURce:PM:DEViation

Sets the modulation DEViation of a PM signal. The unit for DEViation is radians. WherePM:DEViation is implemented, degree units must also be accepted. Radians must always bereturned on a query. This command is used where the DEViation can be controlledindependently from the modulating signal voltage level. Alternatively, it is used to set adevice capability that can indicate when the desired DEViation has been achieved.


19.14.2 :SENSitivity <numeric_value>SOURce:PM:SENSitivity

Controls the modulation deviation by setting a sensitivity Modulation to the modulationsignal voltage level. The unit for SENSitivity is radians/Volt (radians/V). WherePM:SENSitivity is implemented, degree/Volt (degree/V) units must also be accepted.Radians/Volt must always be returned on a query.


19.14.3 :MODE LOCKed|UNLockedSOURce:PM:MODE

Sets the synthesis mode employed in generating the PM signal. If MODE is set to LOCKedthen a PLL is used in synthesizing the PM signal, to prevent frequency drift. If UNLockedthe phase locked loop is inactive.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:PM 19-57

19.14.4 :STATe <Boolean>SOURce:PM:STATe

Turns phase modulation ON or OFF. Turning PM ON will not automatically turn OFF anyother types of modulation. Turning any or all modulations types ON or OFF must be doneexplicitly. Where a type of modulation is active, turning ON another type of modulation willadd to the set of active modulations if that combination of capabilities are legal in the device.Otherwise, an execution error -221 is generated and the instrument state is left undefined.


19.14.5 :SOURce EXTernal|INTernal{,EXTernal|,INTernal}SOURce:PM:SOURce

Selects the source for the modulating signal, and it may specify a single source or a numberof sources. The specified sources in the SOURce command are all selected and turned on.Any sources from a previous selection that are not part of the current selection list aredeselected and turned off. If multiple sources are selected and the device does not support thecombination requested in the SOURce command, an execution error -221 must be generated.




19.14.6 :COUPling AC|DC|GROundSOURce:PM:COUPling

COUPling at this level is used to set the coupling between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either internal or externalsources. If COUPling is set to DC, then both AC and DC components of the signal pass. ACcoupling passes only the AC component of the signal. The GROund parameter allows themodulation to be turned ON without the modulating signal connected.


19.14.7 :POLarity NORMal|INVertedSOURce:PM:POLarity

POLarity, at this level, is used to set the polarity between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either internal or externalsources. POLarity sets the relationship between the polarity of the applied modulationvoltage and the resulting “direction” of modulation. The definition of “normal” polarity forPM modulated signal is that a positive voltage causes the instantaneous output phase toincrease.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-58 SOURce:PM

19.14.8 :INTernalSOURce:PM:INTernal


19.14.8.1 :FREQuency <numeric_value>SOURce:PM:INTernal:FREQuency



19.14.9 :EXTernalSOURce:PM:EXTernal

The EXTernal subsystem is used to control the specified external signal source. Wheremultiple external modulation sources are available, the EXTernal keyword may have anumeric suffix signifying the particular external signal source. If no number is given, a 1 isassumed.

19.14.9.1 :IMPedance <numeric_value>SOURce:PM:EXTernal:IMPedance

Sets the impedance of the specified external signal source. The units for IMPedance is Ohms.


19.14.9.2 :COUPling AC|DC|GROundSOURce:PM:EXTernal:COUPling

COUPling, at this level, sets the coupling for only the specified external signal source. IfCOUPling is set to DC, then both AC and DC components of the signal pass. AC couplingpasses only the AC component of the signal. The GROund parameter allows the specifiedexternal source to be turned ON without being connected.


19.14.9.3 :POLarity NORMal|INVertedSOURce:PM:EXTernal:POLarity

POLarity, at this level, sets the POLarity for only the specified external signal source.POLarity sets the relationship between the polarity of the applied modulation voltage and theresulting “direction” of modulation. The definition of “normal” polarity for PM modulatedsignal is a positive voltage that causes the instantaneous output phase to increase.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:PM 19-59

19.15 POWer SubsystemSOURce:POWer



KEYWORD PARAMETER FORM COMMENTS:POWer :ATTenuation <numeric_value> :AUTO <Boolean>|ONCE :ALC [:STATe] <Boolean> :SEARch <Boolean>|ONCE :SOURce INTernal|DIODe|PMETer|MMHead :BANDwidth <numeric_value> |:BWIDth :AUTO <Boolean>|ONCE :CENTer <numeric_value> [:LEVel] [:IMMediate] [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :TRIGgered [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> HP066

:LIMit [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :STATe <Boolean> :MANual <numeric_value> :MODE FIXed|SWEep|LIST :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only] :CLEar [no query]

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-60 SOURce:POWer

KEYWORD PARAMETER FORM COMMENTS :RANGe <numeric_value> :AUTO <Boolean>|ONCE :REFerence <numeric_value> :STATe <Boolean> :SLEW <numeric_value> :SPAN <numeric_value> :HOLD <Boolean> :LINK CENTer|STARt|STOP :FULL [no query] :STARt <numeric_value> :STOP <numeric_value>

19.15.1 :ATTenuation <numeric_value>SOURce:POWer:ATTenuation



19.15.1.1 :AUTO <Boolean>SOURce:POWer:ATTenuation:AUTO





19.15.2 :ALC SOURce:POWer:ALC


19.15.2.1 [:STATe] <Boolean> SOURce:POWer:ALC:STATe



19.15.2.2 :SEARch <Boolean>|ONCE SOURce:POWer:ALC:SEARch



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:POWer 19-61



19.15.2.3 :SOURce INTernal|DIODe|PMETer|MMHead SOURce:POWer:ALC:SOURce





MMHead — A millimeter head, with built in leveling, is being used to supply theALC signal.


19.15.2.4 :BANDwidth|:BWIDth <numeric_value> SOURce:POWer:ALC:BANDwidth



19.15.2.4.1 :AUTO <Boolean>|ONCE SOURce:POWer:ALC:BANDwidth:AUTO




19.15.3 :CENTer <numeric_value> SOURce:POWer:CENTer



19.15.4 [:LEVel]SOURce:POWer:LEVel


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


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-62 SOURce:POWer

19.15.4.1.1 [:AMPLitude] <numeric_value>SOURce:POWer:LEVel:IMMediate:AMPLitude


Note the optional nodes exist to enable POWer to be directly followed by a<numeric_value>. This is useful for programming simple devices in a straightforwardmanner.


19.15.4.1.2 :OFFSet <numeric_value>SOURce:POWer:LEVel:IMMediate:OFFSet



19.15.4.1.3 :HIGH <numeric_value>SOURce:POWer:LEVel:IMMediate:HIGH



19.15.4.1.4 :LOW <numeric_value>SOURce:POWer:LEVel:IMMediate:LOW



19.15.4.2 :TRIGgeredSOURce:POWer:LEVel:TRIGgered



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:POWer 19-63

19.15.4.2.1 [:AMPLitude] <numeric_value> SOURce:POWer:LEVel:TRIGgered:AMPLitude


19.15.4.2.2 :OFFSet <numeric_value> SOURce:POWer:LEVel:TRIGgered:OFFSet


19.15.4.2.3 :HIGH <numeric_value> SOURce:POWer:LEVel:TRIGgered:HIGH


19.15.4.2.4 :LOW <numeric_value> SOURce:POWer:LEVel:TRIGgered:LOW


19.15.5 :LIMit SOURce:POWer:LIMit


19.15.5.1 [:AMPLitude] <numeric_value> SOURce:POWer:LIMit:AMPLitude




19.15.5.2 :OFFSet <numeric_value> SOURce:POWer:LIMit:OFFSet


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-64 SOURce:POWer


19.15.5.3 :HIGH <numeric_value> SOURce:POWer:LIMit:HIGH



19.15.5.4 :LOW <numeric_value> SOURce:POWer:LIMit:LOW



19.15.5.5 :STATe <Boolean> SOURce:POWer:LIMit:STATe



19.15.6 :MANual <numeric_value> SOURce:POWer:MANual



19.15.7 :MODE FIXed|SWEep|LIST SOURce:POWer:MODE

Determines which set of commands control the amplitude subsystem. If FIXed is selected,the amplitude is determined by the LEVel command under the appropriate subsystem. IfSWEep is selected, the source is in the swept mode and amplitude is determined by STARt,STOP, CENTer, SPAN, and MANual commands under the appropriate subsystem. If LIST isselected, the amplitude values are determined by the appropriate amplitude list (such asLIST:).


19.15.8 :PROTectionSOURce:POWer:PROTection


19.15.8.1 [:LEVel] <numeric_value> SOURce:POWer:PROTection:LEVel


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:POWer 19-65

19.15.8.2 :STATe <Boolean> SOURce:POWer:PROTection:STATe



19.15.8.3 :TRIPped?SOURce:POWer:PROTection:TRIPped?



19.15.8.4 :CLEarSOURce:POWer:PROTection:CLEar



19.15.9 :RANGe <numeric_value> SOURce:POWer:RANGe


19.15.9.1 :AUTO <Boolean>|ONCE SOURce:POWer:RANGe:AUTO




19.15.10 :REFerence <numeric_value> SOURce:POWer:REFerence



19.15.10.1 :STATe <Boolean> SOURce:POWer:REFerence:STATe



19.15.11 :SLEW <numeric_value> SOURce:POWer:SLEW



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-66 SOURce:POWer

19.15.12 :SPAN <numeric_value> SOURce:POWer:SPAN



19.15.12.1 :HOLD <Boolean>SOURce:POWer:SPAN:HOLD



19.15.12.2 :LINK CENTer|STARt|STOPSOURce:POWer:SPAN:LINK



19.15.12.3 :FULL SOURce:POWer:SPAN:FULL



19.15.13 :STARt <numeric_value> SOURce:POWer:STARt



19.15.14 :STOP <numeric_value> SOURce:POWer:STOP



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:POWer 19-67

19.16 PULse Modulation SubsystemSOURce:PULM

The PULse Modulation subsystem is used to set the modulation controls and the parametersassociated with the modulating signal(s). The keywords to describe the carrier signal exist inother subsystems (such as, FREQuency and PHASe).

KEYWORD PARAMETER FORM COMMENTS:PULM :EXTernal :HYSTeresis <numeric_value> :IMPedance <numeric_value> :LEVel <numeric_value> :POLarity NORMal|INVerted :INTernal :FREQuency <numeric_value> :MODE FIXed|LIST 1993 EM004 :POLarity NORMal|INVerted :SOURce EXTernal|INTernal{,EXTernal|,INTernal} :STATe <Boolean>

19.16.1 :EXTernalSOURce:PULM:EXTernal

The EXTernal subsystem is used to control the specified external signal source. Wheremultiple external modulation sources are available, the EXTernal keyword may have anumeric suffix signifying the particular external signal source. If no number is given, a 1 isassumed.

19.16.1.1 :HYSTeresis <numeric_value>SOURce:PULM:EXTernal:HYSTeresis

Sets, for the specified signal source, how far the signal voltage must rise above (alternatively,fall below) the threshold LEVel before the carrier is turned ON from the OFF state (or turnedOFF from the ON state). The unit for HYSTeresis is Volts.

At *RST, this defaults to the TTL preset value.

19.16.1.2 :IMPedance <numeric_value>SOURce:PULM:EXTernal:IMPedance

Sets the impedance of the specified external signal source. The unit for IMPedance is Ohms.


19.16.1.3 :LEVel <numeric_value>SOURce:PULM:EXTernal:LEVel

For the specified signal source, this sets the threshold voltage level used to turn ON thecarrier. The unit for LEVel is Volts.

At *RST, this defaults to the TTL preset value.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-68 SOURce:PULse Modulation

19.16.1.4 :POLarity NORMal|INVertedSOURce:PULM:EXTernal:POLarity

POLarity, at this level, sets the POLarity for only the specified external signal source.POLarity sets the relationship between the polarity of the applied modulation voltage and theresulting “direction” of modulation. The definition of “normal” polarity for PULSemodulated signal is, a voltage more positive than some threshold (after applying hysteresiseffects) and causes the carrier to turn on.


19.16.2 :INTernalSOURce:PULM:INTernal


19.16.2.1 :FREQuency <numeric_value>SOURce:PULM:INTernal:FREQuency



19.16.3 MODE EM004SOURce:PULM:MODE

Determines which set of commands currently control the PULM subsystem. The settingshave the following meanings:

FIXed: Settings of individual commands are as last set by the user.

LIST: Settings of individual commands are controlled by the LIST subsystem.

At *RST the value is FIXed.

19.16.4 :POLarity NORMal|INVertedSOURce:PULM:POLarity

POLarity, at this level, is used to set the polarity between the modulator and the modulatingsignal. The modulating signal may be the sum of several signals, either internal or externalsources. POLarity sets the relationship between the polarity of the applied modulationvoltage and the resulting “direction” of modulation. The definition of “normal” polarity forPULSe modulated signal is a voltage more positive than some threshold (after applyinghysteresis effects) and causes the carrier to turn on.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:PULse Modulation 19-69

19.16.5 :SOURce EXTernal|INTernal{,EXTernal|,INTernal}SOURce:PULM:SOURce

Selects the source for the modulating signal, and it may specify a single source or a numberof sources. The specified sources in the SOURce command are all selected and turned on.Any sources from a previous selection are ignored. If multiple sources are selected and thedevice does not support the combination requested in the SOURce command, an executionerror -221 must be generated.

Where multiple internal modulation sources are available, individual INTernal sources maybe distinguished by a unique numeric suffix. If no numeric suffix is provided in a command,a 1 is assumed.



19.16.6 :STATe <Boolean>SOURce:PULM:STATe

Turns Pulse Modulation ON or off. Turning ON PULse Modulation Modulation will notautomatically turn OFF any other types of modulation. Turning any or all modulations typesON or OFF must be done explicitly. Where a type of modulation is active, turning ONanother type of modulation will add to the set of active modulations if that combination ofcapabilities are legal in the device. Otherwise, an execution error -221 is generated and theinstrument state is left undefined.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-70 SOURce:PULse Modulation

19.17 PULSe SubsystemSOURce:PULSe

This subsystem collects together the commands used to control pulse generation.

KEYWORD PARAMETER FORM COMMENTS:PULSe :PERiod <numeric_value> :WIDTh <numeric_value> :DCYCle <numeric_value> :HOLD WIDTh|DCYCle :DELay <numeric_value> :DOUBle [:STATE] <Boolean> :DELay <numeric_value> :TRANsition :STATe <Boolean> [:LEADing] <numeric_value> :TRAiling <numeric_value> :AUTO <Boolean>|ONCE :COUNt <numeric_value> :POLarity NORMal|COMPlement|INVerted

19.17.1 :PERiod <numeric_value>SOURce:PULSe:PERiod

Sets the period of a pulsed waveform. The fundamental units for PERiod is seconds.


19.17.2 :WIDTh <numeric_value>SOURce:PULSe:WIDTh

Sets the width or duration of the pulse. The fundamental units for WIDTh is seconds.


19.17.3 :DCYCle <numeric_value>SOURce:PULSe:DCYCle

Sets the duty cycle of a repetitive pulsed waveform. The fundamental units for DCYCle ispercent (%).


19.17.4 :HOLD WIDTh|DCYCleSOURce:PULSe:HOLD

Sets, for a pulsed waveform, the parameter to be held constant when the period changes.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:PULSe 19-71

19.17.5 :DELay <numeric_value>SOURce:PULSe:DELay

Sets the time from the start of the period to the first edge of the pulse. The fundamental unitsfor DELay is seconds.

At *RST, the value of this parameter is set to either 0 seconds or the nearest specified value.

19.17.6 :DOUBleSOURce:PULSe:DOUBle

This subsystem contains the commands necessary to control the parameters associated withdouble pulse. When a double pulse is enabled, a second pulse which is identical to theprimary pulse is generated at some point during the period of the pulse. This second pulsehas the same characteristics as the first pulse, including width. A side effect is that since asecond pulse has been added, the actual duty cycle of the signal is twice that specified inPULSe:DCYCle. Attempting to enable double pulse mode when the pulse width is greaterthan:

(PULSE:PERiod-PULSe:DOUBle:DELay)/2

will cause an error -221, “Settings Conflict,” to be generated.

19.17.6.1 [:STATE] <Boolean>SOURce:PULSe:DOUBle:STATE

This command sets the double pulse mode to ON or OFF.

At *RST, this parameter is set to OFF.

19.17.6.2 :DELay <numeric_value>SOURce:PULSe:DOUBle:DELay

Sets the time from the start of the period to the first edge of the second pulse. Thefundamental units for DELay is seconds.


19.17.7 :TRANsitionSOURce:PULSe:TRANsition

Collects together the commands to control the parameters associated with characteristics ofthe leading and trailing edges of the pulse.

19.17.7.1 :STATe <Boolean>SOURce:PULSe:TRANsition:STATe

Sets the transition mode to ON or OFF. If STATe is OFF, then the LEADing and TRAilingedges must be set to the minimum transition times available in the device. If STATe is ON,then the pulse transition times are specified by values for LEADing and TRAiling.


19.17.7.2 [:LEADing] <numeric_value>SOURce:PULSe:TRANsition:LEADing

This command sets the transition time for the LEADing edge. The fundamental units forLEADing is seconds.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-72 SOURce:PULSe


19.17.7.3 :TRAiling <numeric_value>SOURce:PULSe:TRANsition:TRAiling

Sets the transition time for the TRAiling edge. The fundamental units for TRAiling isseconds.

At *RST, this value device-dependent.

19.17.7.3.1 :AUTO <Boolean>|ONCESOURce:PULSe:TRANsition:TRAiling:AUTO

Couples the value of TRAiling to LEADing, when AUTO is set to ON.

At *RST, this parameter is set to ON.

19.17.8 :COUNt <numeric_value>SOURce:PULSe:COUNt

Sets the number of times pulse (or double pulse) must be repeated for a single trigger event.

At *RST, the value of this parameter is set to 1.

19.17.9 :POLarity NORMal|COMPlement|INVertedSOURce:PULSe:POLarity

Sets the polarity of the pulse. For NORMal operation the second nominal state is morepositive that the first. COMPlement and INVerted are aliases. For either position, the secondnominal transition is more negative than the first.

At *RST, this parameter is set to NORMal.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:PULSe 19-73

19.18 RESistance SubsystemSOURce:RESistance

This subsystem controls the characteristics of a resistance source or load.

KEYWORD PARAMETER FORM COMMENTS:RESistance [:LEVel] [:IMMediate] [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :TRIGgered [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :LIMit [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :PROTection [:LEVel] <numeric_value> :STATe <Boolean> :TRIPped? [query only] :CLEar [no query] :SLEW <numeric_value> :CENTer <numeric_value> :SPAN <numeric_value> :HOLD <Boolean> :LINK CENTer|STARt|STOP :FULL [no query] :STARt <numeric_value> :STOP <numeric_value> :MANual <numeric_value> :MODE FIXed|SWEep|LIST :REFerence <numeric_value> :STATe <Boolean> :RANGe <numeric_value> :AUTO <boolean>|ONCE

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-74 SOURce:RESistance

19.18.1 [:LEVel]SOURce:RESistance:LEVel

This subsystem is used to control the resistance when the source is operating in a continuousor FIXed MODE. That is, as a constant load.

19.18.1.1 [:IMMediate]SOURce:RESistance:LEVel:IMMediate

Indicates that the subsequent specification of a new resistance is to be processed by thedevice without waiting for further commands.

19.18.1.1.1 [:AMPLitude] <numeric_value>SOURce:RESistance:LEVel:IMMediate:AMPLitude

Sets the actual magnitude of the unswept resistance. AMPLitude may be used to specify theresistance level for either a time varying or non-time varying load.


19.18.1.1.2 :OFFSet <numeric_value>SOURce:RESistance:LEVel:IMMediate:OFFSet

Sets the non-time varying component of the resistance that is added to the time varyingresistance signal specified in AMPLitude.


19.18.1.1.3 :HIGH <numeric_value>SOURce:RESistance:LEVel:IMMediate:HIGH

Sets the more positive peak of a time varying resistance signal, it is used in conjunction withLOW.


19.18.1.1.4 :LOW <numeric_value>SOURce:RESistance:LEVel:IMMediate:LOW

Sets the more negative peak of a time varying resistance signal, it is used in conjunction withHIGH.


19.18.1.2 :TRIGgeredSOURce:RESistance:LEVel:TRIGgered

Indicates that subsequent specification of a new resistance settings are to be transferred to theIMMediate value upon receipt of a trigger signal.

At *RST, after the receipt of an ABORt command, or upon being triggered, the values in theTRIGgered subsystems track the values in the IMMediate subsystem until a command in theTRIGgered subsystem is received. The purpose of tracking is so that spurious triggers do notchange the value of LEVel unexpectedly.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:RESistance 19-75

19.18.1.2.1 [:AMPLitude] <numeric_value>SOURce:RESistance:LEVel:TRIGgered:AMPLitude

Sets the actual magnitude of the unswept output signal. AMPLitude may be used to specifythe resistance level for either a time varying or non-time varying load.

19.18.1.2.2 :OFFSet <numeric_value>SOURce:RESistance:LEVel:TRIGgered:OFFSet

Sets the non-time varying component of the resistance that is added to the time varyingresistance signal specified in AMPLitude.

19.18.1.2.3 :HIGH <numeric_value>SOURce:RESistance:LEVel:TRIGgered:HIGH

Sets the more positive peak of a time varying resistance signal, and it is used in conjunctionwith LOW.

19.18.1.2.4 :LOW <numeric_value>SOURce:RESistance:LEVel:TRIGgered:LOW

Sets the more negative peak of a time varying resistance signal, and it is used in conjunctionwith HIGH.

19.18.2 :LIMitSOURce:RESistance:LIMit

Sets the bounds on the resistance value. Setting a larger value will cause the resistance to beclamped to the LIMit value.

19.18.2.1 [:AMPLitude] <numeric_value>SOURce:RESistance:LIMit:AMPLitude

Sets the limit on the actual magnitude of the unswept resistance. AMPLitude may be used tospecify the resistance level for either a time varying or non-time varying load. OFFSet mayonly be used with AMPLitude, where AMPLitude is used to specify a time varying load.

Explicit reference to the AMPLitude node is optional. Any device that implements thissubsystem shall accept and process commands, with or without the AMPLitude node, andrespond to them in the same way.


19.18.2.2 :OFFSet <numeric_value>SOURce:RESistance:LIMit:OFFSet

Sets the limit for the non-time varying component of resistance that is added to the timevarying resistance signal specified in AMPLitude.


19.18.2.3 :HIGH <numeric_value>SOURce:RESistance:LIMit:HIGH

Sets the more positive peak limit of a time varying resistance signal, it is used in conjunctionwith LOW.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.18.2.4 :LOW <numeric_value>SOURce:RESistance:LIMit:LOW

Sets the more negative peak limit of a time varying resistance signal, and it is used inconjunction with HIGH.


19.18.3 :PROTection SOURce:RESistance:PROTection

Controls the resistance protection circuit

19.18.3.1 [:LEVel] <numeric_value>SOURce:RESistance:PROTection:LEVel

Sets the output resistance level at which the output protection circuit will trip.

19.18.3.2 :STATe <Boolean>SOURce:RESistance:PROTection:STATe



19.18.3.3 :TRIPped?SOURce:RESistance:PROTection:TRIPped?

Returns a 1 if the protection circuit is tripped and a 0 if it is untripped. TRIPped only has aquery form and thus has no associated *RST condition.

19.18.3.4 :CLEarSOURce:RESistance:PROTection:CLEar

Causes the protection circuit to be cleared. This command is an event and has no associated*RST condition.

19.18.4 :SLEW <numeric_value>SOURce:RESistance:SLEW

Sets the slew rate of the resistance change when a new resistance level is programmed. Theunits are in Ohm/sec.


19.18.5 :CENTer <numeric_value>SOURce:RESistance:CENTer

Sets the CENTer RESistance. At *RST, this value is set to MINimum.

19.18.6 :SPAN <numeric_value>SOURce:RESistance:SPAN

Sets the resistance SPAN.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.18.6.1 :HOLD <Boolean>SOURce:RESistance:SPAN:HOLD



19.18.6.2 :LINK CENTer|STARt|STOPSOURce:RESistance:SPAN:LINK



19.18.6.3 :FULLSOURce:RESistance:SPAN:FULL

When this command is received, STARt RESistance is set to MINimum, and STOPRESistance is set to MAXimum. CENTer RESistance and SPAN are set to their coupledvalues.

This command is an event, rather than a state. Therefore it has no associated query, ormeaning at *RST.

19.18.7 :STARt <numeric_value>SOURce:RESistance:STARt

Sets STARt resistance.


19.18.8 :STOP <numeric_value>SOURce:RESistance:STOP

Sets STOP resistance.


19.18.9 :MANual <numeric_value>SOURce:RESistance:MANual

Allows manual adjustment of the RESistance between the sweep limits. The actualRESistance level is determined by the parameter only if SWEep:MODE is set to MANualand RESistance:MODE is set to SWEep. If the sweep limits are changed such that themanual RESistance value would be outside the limits, the manual RESistance value will beset to the nearest limit.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.18.10 :MODE FIXed|SWEep|LISTSOURce:RESistance:MODE

Determines which set of commands control the resistance subsystem. If FIXed is selected,the RESistance is determined by the LEVel command. If SWEep is selected, the source is inthe swept mode and RESistance is determined by STARt, STOP, CENTer, SPAN, andMANual commands. If LIST is selected, the RESistance values are determined byLIST:RESistance.


19.18.11 :REFerence <numeric_value>SOURce:RESistance:REFerence

Sets a reference value which, if STATe is ON, allows all RESistance parameters to bequeried/set as a relative to the reference value.


19.18.11.1 :STATe <Boolean>SOURce:RESistance:REFerence:STATe

Determines whether RESistance is in absolute or relative mode. If STATe is ON, thenRESistance is referenced to the value set in REFerence.


19.18.12 :RANGe <numeric_value>SOURce:RESistance:RANGe

Sets a range for the output RESistance.

19.18.12.1 :AUTO <Boolean>|ONCE SOURce:RESistance:RANGe:AUTO

Couples the RANGe to an instrument-determined value. When AUTO POWer andVOLTageis ON, the best range is chosen to reflect the current instrument state.



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.19 ROSCillator SubsystemSOURce:ROSCillator

This subsystem controls the reference oscillator.

KEYWORD PARAMETER FORM NOTES:ROSCillator

HP055 [:INTernal] 1992 :FREQuency <numeric_value>

HP055 :EXTernal 1992HP055 :FREQuency <numeric_value> 1992

:SOURce INTernal|EXTernal|NONE :AUTO <Boolean>|ONCE

HP05519.19.1 [:INTernal]SOURce:ROSCillator:INTernal

This subsystem configures the internal reference oscillator(s).

19.19.1.1 :FREQuency <numeric_value>SOURce:ROSCillator:INTernal:FREQuency

Specifies the frequency of the internal reference oscillator. The default units are Hz.


HP05519.19.2 :EXTernalSOURce:ROSCillator:EXTernal

This subsystem configures the external reference oscillator(s).

HP05519.19.2.1 :FREQuency <numeric_value>SOURce:ROSCillator:EXTernal:FREQuency

Specifies the frequency of the external reference oscillator. The default units are Hz.


19.19.3 :SOURce INTernal|EXTernal|NONESOURce:ROSCillator:SOURce

HP055Controls the selection of the reference oscillator source. This typically refers to a precision,stabilized time base. The parameter values have the following meanings:

HP055INTernal — The reference frequency is derived from an internal precisionoscillator.

HP055EXTernal — The reference frequency is derived from an external signal suppliedto the device.

HP055NONE — The reference frequency is not derived from any precision oscillator.At *RST, this value is device-dependent.

19.19.3.1 :AUTO <Boolean>|ONCESOURce:ROSCillator:SOURce:AUTO

When AUTO is ON, the system automatically selects which oscillator will be used by theinstrument.

Explicitly selecting a reference oscillator turns AUTO OFF.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-80 SOURce:ROSCillator


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:ROSCillator 19-81

19.20 SPEed SubsystemSOURce:SPEed

This node controls the speed of the device.

KEYWORD PARAMETER FORM COMMENTS:SPEed 1999 :INITiate [event; no query]1999 [:LEVel] <numeric_value> 1999 :SSDLoss 1999 :INITiate [event; no query]1999 :LATime <numeric_value> 1999 :STIMe <numeric_value> 1999

19.20.1 :INITiate:SOURce:SPEed:INITiate

This command initiates speed. This is an overlapped command. This command describes anevent and therefore has no associated *RST condition.

When this command is initiated for chassis dynamometers, the dynamometer must:


Set the DYNO operation condition register Go To Speed Procedure bit indicating Go ToSpeed Procedure is executing. Note: The DYNO operation condition register will befurther defined in Volume 4.

Accelerate dynamometer to the :SOURce:SPEed:LEVel speed point at the rate in:SOURce:ACCeleration. The dynamometer determines when the speed point hasstabilized.

Maintain speed and wait for a command.

When commanded out of this procedure, clear the DYNO operation condition register GoTo Speed Procedure bit indicating the Go To Speed Procedure is not executing.


19.20.2 [:LEVel] <numeric_value>:SOURce:SPEed:LEVel

Set the desired speed set-point in m/s.


19.20.3 :SSDLossSOURce:SPEed:SSDLoss

Steady State Driveline Loss

This node describes the procedure to measure the driveline loss forces as a function of speed.The Steady State Driveline Procedure measures the vehicle losses due to vehicle drive train

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-82 SOURce:SPEed

components. The vehicle losses are measured by operating the dynamometer at variousselected speeds and measuring the force required to maintain the constant speed over aspecified time interval. The results are stored in the DrvLLoss pre-defined table. This tablehas two columns, SPEed, the speeds at which the losses are to be measured (input) andLOSS, the measured losses at each speed (result). Coefficients for vehicle driveline lossesare determined at the end of the procedure and reside in DrvLCoeff.

19.20.3.1 :INITiate:SOURce:SPEed:SSDLoss:INITiate

This is an overlapped command. The command uses the speed points defined in the:MEMory:TABLe:SELect DrvLLoss. This command describes an event and therefore has noassociated *RST condition.

When this procedure is initiated for dynamometers, the dynamometer must:

Check critical ancillaries, if any, for proper conditions: Brakes Off, Motor Contactor On,parameters within dynamometer safety limits. For conditions that prohibit operation ofthis command, issue appropriate warning messages, and execute the Idle Procedure.

Set the DYNO operation condition register Driveline Loss Procedure bit indicating thedriveline loss is executing. Note: The DYNO operation condition register will be furtherdefined in Volume 4.

Accelerate dynamometer to the first speed point defined in the DrvLLoss memory tableat the rate in :SOURce:ACCeleration.

Stabilize at this speed for :SOURce:SPEed:SSDLoss:STIMe. If the speed does notstabilize, set Failed to Stabilize bit of the DYNO questionable condition register andcontinue with the procedure.

Average the force at the roll surface required to maintain the speed set point over the lossaverage time :SOURce:SPEed:SSDLoss:LATime. The average force value is placed inthe DrvLLoss memory table for the specified speed point. Repeat steps 3 to 5 for eachpoint in the DrvLLoss table. The first zero speed in the DrvLLoss table ends theprocedure.

Perform a curve fit on the DrvLLoss data and place the coefficients in the memory tableDrvLCoeff.

Clear the DYNO operation condition register bit 7 indicating the driveline loss is notexecuting.



19.20.3.2 :LATime <numeric_value>:SOURce:SPEed:SSDLoss:LATime


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:SPEed 19-83

This command sets the time after stabilization that the losses are to be averaged beforemoving to the next speed point.


19.20.3.3 :STIMe <numeric_value>:SOURce:SPEed:SSDLoss:STIMe


Time for stabilization prior to LATime after a change in speed.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-84 SOURce:SPEed

19.21 SWEep SubsystemSOURce:SWEep

This subsystem controls the sweep for those instruments which generate signals as a functionof time. Other parameters may also be swept by specifying SWEep as their MODE (forexample, FREQuency:MODE SWEep). Units for this subsystem are seconds unlessotherwise noted.

KEYWORD PARAMETER FORM COMMENTS:SWEep :TIME <numeric_value> :AUTO <Boolean>|ONCE :LLIMit <numeric_value> :DWELl <numeric_value> :AUTO <Boolean>|ONCE :DIRection UP|DOWN :MODE AUTO|MANual :SPACing LINear|LOGarithmic :GENeration STEPped|ANALog :STEP <numeric_value> :POINts <numeric_value> :COUNt <numeric_value>

19.21.1 :TIME <numeric_value>SOURce:SWEep:TIME

Sets the duration of the sweep. Note that this does not turn sweeping on. Setting this valueautomatically turns TIME:AUTO OFF.

19.21.1.1 :AUTO <Boolean>|ONCESOURce:SWEep:TIME:AUTO

When enabled, the sweep time is calculated internally and is dependent on the span of thesweep.


19.21.1.2 :LLIMit <numeric_value>SOURce:SWEep:TIME:LLIMit

Defines a lower limit for sweep time. This lower limit restricts the sweep time value seteither explicitly or automatically.

At *RST, LLIMit is set to a device-dependent value.

19.21.2 :DWELl <numeric_value>SOURce:SWEep:DWELl

Controls the amount of time spent at each point during a sweep. Note that DWELl cannotexceed TIME/POINts. Trying to set it to a greater value will cause an error to result. Thepoints will not change, but time may be changed as a device-dependent decision.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:SWEep 19-85

19.21.2.1 :AUTO <Boolean>|ONCESOURce:SWEep:DWELl:AUTO

When AUTO ON is selected, the dwell time is coupled to the sweep time and number ofpoints. The coupling equation is:

DWELl=(TIME/POINts)-(device-dependent stepping time)

Setting a value for dwell turns AUTO OFF.


19.21.3 :DIRection UP|DOWNSOURce:SWEep:DIRection

Controls the direction of the sweep. If UP is selected, the sweep is carried out in ascendingorder, from STARt to STOP. If DOWN is selected, the sweep is carried out in descendingorder, from STOP to STARt.

At *RST, the value of this function is UP.

19.21.4 :MODE AUTO|MANualSOURce:SWEep:MODE

Selects the sweep conditions for the sweep. The various conditions are:

AUTO: The sweep is controlled by the internal sweep generator.

MANual: The sweep is controlled by front panel controls or by the manualcommand, such as, FREQuency:MANual. This setting is valid only if the:MANual capability has been implemented.

At *RST, this function is set to AUTO.

19.21.5 :SPACing LINear|LOGarithmicSOURce:SWEep:SPACing

Determines the swept entity versus time characteristics of the sweep. The various settingshave the following meanings:

LINear: For stepped sweeps, the swept entity is incremented (decremented) by thestep size until the sweep limit is reached. For analog sweeps, a linear ramp isgenerated.

LOGarithmic: For non-linear sweeps, step size is determined by a logarithmiccurve fitted between the start and stop frequency. Stepping is determined by theSWEep:POINts. For analog sweeps, a logarithmic ramp is generated.


19.21.6 :GENeration STEPped|ANALogSOURce:SWEep:GENeration

Selects between an analog or stepped sweep.

STEPped: A stepped sweep is selected, and the points are controlled by theSWEep:POINts and SWEep:STEP settings.

ANALog: The sweep is controlled by an analog signal.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-86 SOURce:SWEep


19.21.7 :STEP <numeric_value>SOURce:SWEep:STEP

Controls the swept entity step size for a stepped linear sweep. This parameter is not used ifGENeration is ANALog or if SPACing is LOGarithmic.

This value is hard coupled to SPAN and POINts by the equation:STEP=SPAN/(POINts-1) 1991

HP045

Changing the value of STEP will change POINts, but not SPAN.

The value is instrument-dependent at *RST, but is coupled to the reset value of POINts andSPAN.

19.21.8 :POINts <numeric_value>SOURce:SWEep:POINts

The number of points in a stepped sweep. This parameter is not used if GENeration isANALog. In a linear sweep, this value is coupled to sweep step by the equation:

STEP = SPAN/(POINts-1) 1991HP045

If POINts are changed, STEP will also be changed, but not SPAN. In a logarithmic sweep,POINts will determine the number of points/decade of sweep by the equation:

POINts/DECADE = (POINts-1)/SPAN (in decades) 1991HP045

Note that style rules on resolution do not apply to this command. If the exact number ofpoints specified is not available, an error is generated, and the value remains unchanged.

At *RST, this value is set to MAXimum.

19.21.9 :COUNt <numeric_value>SOURce:SWEep:COUNt

This command determines the number of sweeps which are enabled by a single trigger event.

At *RST, this function is set to 1.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:SWEep 19-87

19.22 TEMPeratureSubsystem XSS01cSOURce:TEMPerature

This subsystem controls the temperature of an environmental chamber.

KEYWORD PARAMETER FORM COMMENTS:TEMPerature 1993 :APRobe <numeric_list> 1993 :DWELl <numeric_value> 1993 :LCONstants 1993 :DERivative <numeric_value> 1993 [:GAIN] <numeric_value> 1993 :INTegral <numeric_value> 1993 :MODE FIXed|LIST|PROGram 1993 :PROTection 1993 [:HIGH] 1993 :CLEar [no query] 1993 [:LEVel] <numeric_value> 1993 :STATe <Boolean> 1993 :TOUT <numeric_value> 1993 :TRIPped? [query only] 1993 :LOW 1993 :CLEar [no query] 1993 [:LEVel] <numeric_value> 1993 :STATe <Boolean> 1993 :TOUT <numeric_value> 1993 :TRIPped? [query only] 1993 :RTIMe <numeric_value> 1993 [:SPOint] <numeric_value> 1993

19.22.1 :APRobe <numeric_list>SOURce:TEMPerature:APRobe

Active PRobe selects one or more probes to become part of the feedback loop to control thetemperature.

A temperature controller can have one or more probes to measure temperature at variousplaces. If more than one probe is active, the signals from the probes are averaged to controlthe temperature.

AT *RST which probes are active is device dependent.

19.22.2 :DWELl <numeric_value>SOURce:TEMPerature:DWELl

The DWELl command specifies the amount of time the temperature chamber will stay at thetarget temperature. At the end of the DWELl period the temperature will return to theambient temperature. The DWELl time does not include the Ramp TIMe.

AT *RST the value is device dependent.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-88 SOURce:TEMPerature

19.22.3 :LCONstants SOURce:TEMPerature:LCONstants

A temperature chamber is a closed loop thermal system. The Loop CONstants of such asystem determine its performance. These loop constants are popularly known as pid.

The p is the proportional or GAIN control and can be imagined as a coarse control. The i isthe integral (lead) compensator and d is the derivative (lag) compensator. These twocompensators are additional controls to fine tune the system. The INTegral value improvesthe steady-state error and the DERivative value improves the transient response of afeedback control system.

For further information on feedback control systems please refer to Vol 1: Syntax and Style -Chapter 2, Tuning a Control Loop Performance

19.22.3.1 :DERivative <numeric_value> SOURce:TEMPerature:LCONstants:DERivative

The DERivative, which is also called a lead compensator, is used to improve the transientresponse of the system. The unit for DERivative is (currently selected units) degrees persecond.

With both GAIN and DERivative are specified, the output (heat/cold) is proportional to theinput signal plus its derivative. This is shown in the figure below using Laplace transformnotation.

At *RST the value is device dependent.

19.22.3.2 [:GAIN] <numeric_value>SOURce:TEMPerature:LCONstants:GAIN

The value of :GAIN determines the time required to reach the target temperature. The higherthe value of gain, the sooner the target temperature is achieved. The GAIN is a unitlessquantity.


19.22.3.3 :INTegral <numeric_value> SOURce:TEMPerature:LCONstants:INTegral

The INTegral, which is also called a lag compensator, is used to minimize the steady-stateerror.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:TEMPerature 19-89

When the steady-state error is too large, it is possible to minimize this value by adjusting thevalue of INTegral. The units for INTegral are degree*seconds.

With both GAIN and INTegral are specified, the output (heat/cold) is proportional to theinput signal plus its integral. This is shown in the figure below using Laplace transformnotation.


19.22.4 :MODE FIXed|LIST|PROGramSOURce:TEMPerature:MODE

Determines which set of commands control the temperature subsystem. If FIXed is selected,the temperature is determined by the SPOint command. If LIST is selected, the temperaturevalues are determined by the appropriate temperature list (such as LIST:). If PROGram isselected the temperature is controlled by the currently selected program specified underPROGram subsystem.

At *RST this value is set to FIXed.

19.22.5 :PROTectionSOURce:TEMPerature:PROTection

Protects the temperature chamber as well as the unit under test.

19.22.5.1 [:HIGH]SOURce:TEMPerature:PROTection:HIGH

The :HIGH subsystem controls the protection. The high value must be exceeded for theprotection action to be taken.

19.22.5.1.1 :CLEarSOURce:TEMPerature:PROTection:HIGH:CLEar



19.22.5.1.2 [:LEVel] <numeric_value>SOURce:TEMPerature:PROTection:HIGH:LEVel

Specifies the high temperature trip level. The device will check the current value of thetemperature. If the temperature exceeds the programmed protection level, the chamber willtrip the protection mechanism.


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.22.5.1.3 :STATe <Boolean>SOURce:TEMPerature:PROTection:HIGH:STATe

Enables or disables the protection mechanism.

At *RST this value is set to ON.

19.22.5.1.4 :TOUT <numeric_value>SOURce:TEMPerature:PROTection:HIGH:TOUT

Specifies the time out in the currently specified unit of time. The device will start the timeout counter anytime the difference between the controlled temperature and the SetPOint isgreater than a predetermined quantity (for example 2 degrees C). If the temperature has notreached the target value and if the time out has occurred the chamber will trip the protectionmechanism.

The time out counter will be reset as soon as the temperature has reached the target valuewithin the predetermined tolerance limits.


19.22.5.1.5 :TRIPped?SOURce:TEMPerature:PROTection:HIGH:TRIPped?


19.22.5.2 :LOWSOURce:TEMPerature:PROTection:LOW

The :LOW subsystem controls the protection. The temperature must fall below the lowestlevel for the protection action to be taken.

19.22.5.2.1 :CLEarSOURce:TEMPerature:PROTection:LOW:CLEar



19.22.5.2.2 [:LEVel] <numeric_value>SOURce:TEMPerature:PROTection:LOW:LEVel

Specifies the low temperature trip level. The device will check the current value of thetemperature. If the temperature falls below the programmed protection level, the chamberwill trip the protection mechanism.


19.22.5.2.3 :STATe <Boolean>SOURce:TEMPerature:PROTection:LOW:STATe

Enables or disables the protection mechanism.

At *RST this value is set to ON.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:TEMPerature 19-91

19.22.5.2.4 :TOUT <numeric_value>SOURce:TEMPerature:PROTection:LOW:TOUT

Specifies the time out in the currently specified unit of time. The device will start the timeout counter anytime the difference between the controlled temperature and the SetPOint isgreater than a predetermined quantity (for example 2 degrees C). If the temperature has notreached the target value and if the time out has occurred the chamber will trip the protectionmechanism.

The time out counter will be reset as soon as the temperature has reached the target valuewithin the predetermined tolerance limits.


19.22.5.2.5 :TRIPped?SOURce:TEMPerature:PROTection:LOW:TRIPped?


19.22.6 :RTIMe <numeric_value>SOURce:TEMPerature:RTIMe

The Ramp TIMe command instructs the environmental chamber the amount of time it shouldtake to reach the target temperature.

The unit for RTIMe time is based on the currently selected unit.


19.22.7 [:SPOint] <numeric_value>SOURce:TEMPerature:SPOint

The SetPOint command sets the target temperature of the environmental chamber. The unitsare the current temperature units.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.23 VOLTage SubsystemSOURce:VOLTage



KEYWORD PARAMETER FORM COMMENTS:VOLTage :ATTenuation <numeric_value> :AUTO <Boolean>|ONCE :ALC [:STATe] <Boolean> :SEARch <Boolean>|ONCE :SOURce INTernal|DIODe|PMETer|MMHead :BANDwidth <numeric_value> |:BWIDth :AUTO <Boolean>|ONCE :CENTer <numeric_value> [:LEVel] [:IMMediate] [:AMPLitude] <numeric_value> :AUTO <Boolean>|ONCE 1991 PH040

:OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :TRIGgered [:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :LIMit HP066

[:AMPLitude] <numeric_value> :OFFSet <numeric_value> :HIGH <numeric_value> :LOW <numeric_value> :STATe <Boolean> :MANual <numeric_value> :MODE FIXed|SWEep|LIST :PROTection [:LEVel] <numeric_value> :STATe :TRIPped? [query only] :CLEar [no query]

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


SOURce:VOLTage 19-93

KEYWORD PARAMETER FORM COMMENTS :RANGe <numeric_value> :AUTO <Boolean>|ONCE :REFerence <numeric_value> :STATe <Boolean> :SLEW <numeric_value> :SPAN <numeric_value> :HOLD <Boolean> :LINK CENTer|STARt|STOP :FULL [no query] :STARt <numeric_value> :STOP <numeric_value>

19.23.1 :ATTenuation <numeric_value>SOURce:VOLTage:ATTenuation



19.23.1.1 :AUTO <Boolean>SOURce:VOLTage:ATTenuation:AUTO





19.23.2 :ALC SOURce:VOLTage:ALC


19.23.2.1 [:STATe] <Boolean> SOURce:VOLTage:ALC:STATe



19.23.2.2 :SEARch <Boolean>|ONCE SOURce:VOLTage:ALC:SEARch



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26


19-94 SOURce:VOLTage



19.23.2.3 :SOURce INTernal|DIODe|PMETer|MMHead SOURce:VOLTage:ALC:SOURce





MMHead — A millimeter head, with built in leveling, is being used to supply theALC signal.


19.23.2.4 :BANDwidth|:BWIDth <numeric_value> SOURce:VOLTage:ALC:BANDwidth



19.23.2.4.1 :AUTO <Boolean>|ONCE SOURce:VOLTage:ALC:BANDwidth:AUTO




19.23.3 :CENTer <numeric_value> SOURce:VOLTage:CENTer



19.23.4 [:LEVel]SOURce:VOLTage:LEVel


19.23.4.1 [:IMMediate]SOURce:VOLTage:LEVel:IMMediate


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.23.4.1.1 [:AMPLitude] <numeric_value>SOURce:VOLTage:LEVel:IMMediate:AMPLitude


Note the optional nodes exist to enable VOLTage to be directly followed by a<numeric_value>. This is useful for programming simple devices in a straightforwardmanner.


19.23.4.1.1.1 :AUTO <Boolean>|ONCESOURce:VOLTage:LEVel:IMMediate:AMPLitude:AUTO

PH040

If AUTO ON is selected, the current setting will be adjusted automatically when a newvoltage setting (with the existing current setting) exceeds the maximum power limit. IfAUTO OFF is selected a new voltage setting will cause an execution error -221 (Settingsconflict), and the instrument state is device dependent when the maximum power limit isexceeded.

*RST condition: AUTO OFF

19.23.4.1.2 :OFFSet <numeric_value>SOURce:VOLTage:LEVel:IMMediate:OFFSet



19.23.4.1.3 :HIGH <numeric_value>SOURce:VOLTage:LEVel:IMMediate:HIGH



19.23.4.1.4 :LOW <numeric_value>SOURce:VOLTage:LEVel:IMMediate:LOW



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.23.4.2 :TRIGgeredSOURce:VOLTage:LEVel:TRIGgered



19.23.4.2.1 [:AMPLitude] <numeric_value> SOURce:VOLTage:LEVel:TRIGgered:AMPLitude


19.23.4.2.2 :OFFSet <numeric_value> SOURce:VOLTage:LEVel:TRIGgered:OFFSet


19.23.4.2.3 :HIGH <numeric_value> SOURce:VOLTage:LEVel:TRIGgered:HIGH


19.23.4.2.4 :LOW <numeric_value> SOURce:VOLTage:LEVel:TRIGgered:LOW


19.23.5 :LIMit SOURce:VOLTage:LIMit


19.23.5.1 [:AMPLitude] <numeric_value> SOURce:VOLTage:LIMit:AMPLitude


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26





19.23.5.2 :OFFSet <numeric_value> SOURce:VOLTage:LIMit:OFFSet



19.23.5.3 :HIGH <numeric_value> SOURce:VOLTage:LIMit:HIGH



19.23.5.4 :LOW <numeric_value> SOURce:VOLTage:LIMit:LOW



19.23.5.5 :STATe <Boolean> SOURce:VOLTage:LIMit:STATe



19.23.6 :MANual <numeric_value> SOURce:VOLTage:MANual



19.23.7 :MODE FIXed|SWEep|LIST SOURce:VOLTage:MODE

Determines which set of commands control the amplitude subsystem. If FIXed is selected,the amplitude is determined by the LEVel command under the appropriate subsystem. IfSWEep is selected, the source is in the swept mode and amplitude is determined by STARt,STOP, CENTer, SPAN, and MANual commands under the appropriate subsystem. If LIST is

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



selected, the amplitude values are determined by the appropriate amplitude list (such asLIST:).


19.23.8 :PROTectionSOURce:VOLTage:PROTection


19.23.8.1 [:LEVel] <numeric_value> SOURce:VOLTage:PROTection:LEVel


19.23.8.2 :STATe <Boolean> SOURce:VOLTage:PROTection:STATe



19.23.8.3 :TRIPped?SOURce:VOLTage:PROTection:TRIPped?



19.23.8.4 :CLEarSOURce:VOLTage:PROTection:CLEar



19.23.9 :RANGe <numeric_value> SOURce:VOLTage:RANGe


19.23.9.1 :AUTO <Boolean>|ONCE SOURce:VOLTage:RANGe:AUTO




19.23.10 :REFerence <numeric_value> SOURce:VOLTage:REFerence



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



19.23.10.1 :STATe <Boolean> SOURce:VOLTage:REFerence:STATe



19.23.11 :SLEW <numeric_value> SOURce:VOLTage:SLEW



19.23.12 :SPAN <numeric_value> SOURce:VOLTage:SPAN



19.23.12.1 :HOLD <Boolean>SOURce:VOLTage:SPAN:HOLD



19.23.12.2 :LINK CENTer|STARt|STOPSOURce:VOLTage:SPAN:LINK



19.23.12.3 :FULL SOURce:VOLTage:SPAN:FULL



19.23.13 :STARt <numeric_value> SOURce:VOLTage:STARt


1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26




19.23.14 :STOP <numeric_value> SOURce:VOLTage:STOP


At *RST, this value is set to MINimum. 1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26



20 STATus Subsystem TK012This subsystem controls the SCPI-defined status-reporting structures. SCPI defines, inaddition to those in IEEE 488.2, QUEStionable, OPERation, Instrument SUMmary andINSTrument registers. These registers conform to the IEEE 488.2 specification and eachmay be comprised of a condition register, an event register, an enable register, and negativeand positive transition filters. The purpose and definition of the SCPI-defined registers isdescribed in “Volume 1: Syntax and Style”.

SCPI also defines an IEEE 488.2 queue for status. The queue provides a human readablerecord of instrument events. The application programmer may individually enable eventsinto the queue. STATus:PRESet enables errors and disables all other events. If the summaryof the queue is reported, it shall be reported in bit 2 of the status byte register. A subset oferror/event numbers is defined by SCPI. Additional error/event numbers will be defined at alater date.

KEYWORD PARAMETER FORM NOTES STATus :OPERation :BIT<n> n=8-12 1999 :CONDition? [query only] 1999 :ENABle <NRr> | <non-decimal_numeric> 1999 [:EVENt]? [query only] 1999 :NTRansition <NRr> | <non-decimal_numeric> 1999 :PTRansition <NRr> | <non-decimal_numeric> 1999 :CONDition? [query only]

TK046 :ENABle <NRf> | <non-decimal numeric> 1995 [:EVENt]? [query only] :INSTrument :CONDition? [query only]

TK046 :ENABle <NRf> | <non-decimal numeric> 1995 [:EVENt]? [query only] :ISUMmary<n> :CONDition? [query only] :ENABle <NRf> [:EVENt]? [query only] :NTRansition <NRf> :PTRansition <NRf>

TK046 :NTRansition <NRf> | <non-decimal numeric> 1995 TK046 :PTRansition <NRf> | <non-decimal numeric> 1995

:MAP <NRf>,<NRf> TK046 :NTRansition <NRf> | <non-decimal numeric> 1995 TK046 :PTRansition <NRf> | <non-decimal numeric> 1995

:PRESet [no query] :QUEStionable :BIT<n> n=9-12 1999

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


STATus Subsystem 20-1

KEYWORD PARAMETER FORM NOTES :CONDition? [query only] 1999 :ENABle <NRr> | <non-decimal_numeric> 1999 [:EVENt]? [query only] 1999 :NTRansition <NRr> | <non-decimal_numeric> 1999 :PTRansition <NRr> | <non-decimal_numeric> 1999 :CONDition? [query only]

TK046 :ENABle <NRf> | <non-decimal numeric> 1995 [:EVENt]? [query only] :INSTrument 1991 :CONDition? [query only] 1991 HP040

TK046 :ENABle <NRf> | <non-decimal numeric> 1991,5 HP040

[:EVENt]? [query only] 1991 :ISUMmary<n> 1991 :CONDition? [query only] 1991 :ENABle <NRf> 1991 [:EVENt]? [query only] 1991 :NTRansition <NRf> 1991 :PTRansition <NRf> 1991 :NTRansition <NRf> | <non-decimal numeric> 1991,5 :PTRansition <NRf> | <non-decimal numeric> 1991,5 :MAP <NRf>,<NRf>

TK046 :NTRansition <NRf> | <non-decimal numeric> 1995 TK046 :PTRansition <NRf> | <non-decimal numeric> 1995 HP040

:VOLTage |:CURRent |:TIMe |:POWer |:TEMPerature |:FREQuency |:PHASe |:MODulation |:CALibration :CONDition? [query only] :ENABle <NRf> | <non-decimal numeric> 1995 [:EVENt]? [query only] :NTRansition <NRf> | <non-decimal numeric> 1995 :PTRansition <NRf> | <non-decimal numeric> 1995

The status reporting commands are orthogonal. Status register bits are classified as eitherterminal (reporting a single class of events) or summary (reporting several classes of events).Summary bits have the same register structure behind them. This is called register fan-out.The commands to access each register are always the same and are described below. Thename of each subsystem follows the name of the associated bit in the next higher status

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


20-2 STATus Subsystem

structure. Therefore, the event register associated with the frequency error bit of thequestionable signal/data register set would be accessed by the command:

STATus:QUEStionable:FREQuency:EVENt?

Certain commands in this subsystem are required to be implemented by all SCPIinstruments. These commands are described in section 4.2.1 of “Volume 1: Syntax andStyle.”

The parameters to the commands are described as <NRf> as defined in IEEE 488.2 and notas SCPI’s <numeric_value>. This means that UP, DOWN, MINimum, and MAXimum arenot accepted for these commands. When a STATus command is queried, the return formshall always be an <NR1> value.

The following commands can be applied to all SCPI registers by prefixing the commandwith the node(s) that represent the particular register to be controlled.

20.1 :OPERationSTATus:OPERation

The OPERation status register contains conditions which are part of the instrument’s normaloperation.

See Volume 1 Section 9.3 for more detailed information.

20.1.1 :BIT<n>STATus:OPERation:BIT<n>

This command accesses the user-definable bits in the OPERation register set. The value of<n> is restricted from 8 to 12 and represents bits 8 through 12 in the :STATus:OPERationstatus register. This allows standardized access to user-definable terminal and summary bits.

20.1.2 :CONDition?STATus:OPERation:CONDition?

Returns the contents of the condition register associated with the status structure defined inthe command. Reading the condition register is nondestructive.

The response is (NR1 NUMERIC RESPONSE DATA) (range: 0 through 32767) unlesschanged by the :FORMat:SREGister command.

20.1.3 :ENABle <NRf> | <non-decimal numeric>STATus:OPERation:ENABle

Sets the enable mask which allows true conditions in the event register to be reported in thesummary bit. If a bit is 1 in the enable register and its associated event bit transitions to true,a positive transition will occur in the associated summary bit.

TK046The command accepts parameter values of either format in the range 0 through 65535(decimal) without error.

TK046The query response format is <NR1> unless changed by the :FORMat:SREGister command.Note that 32767 is the maximum value returned as the most-significant bit of the registercannot be set true.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



20.1.4 [:EVENt]?STATus:OPERation:EVENt?

This query returns the contents of the event register associated with the status structuredefined in the command.

TK046The response is (NR1 NUMERIC RESPONSE DATA) (range: 0 through 32767) unlesschanged by the :FORMat:SREGister command.

Note that reading the event register clears it.

20.1.5 :MAP <NRf>,<NRf>STATus:OPERation:MAP

Maps an error from the list of possible events the instrument can generate into a specified bitin the OPERation or QUEStionable register. The first parameter is the specified bit locationin the OPERation or QUEStionable register. The second parameter is the event number. Forexample, to map event number 678 into bit 9 of the QUEStionable status register, theprogramer would send:

STATus:QUEStionable:MAP 9,678

20.1.6 :NTRansition <NRf> | <non-decimal numeric>STATus:OPERation:NTRansition

Sets the negative transition filter. Setting a bit in the negative transition filter shall cause a 1to 0 transition in the corresponding bit of the associated condition register to cause a 1 to bewritten in the associated bit of the corresponding event register.



HP066

20.1.7 :PTRansition <NRf> | <non-decimal numeric>STATus:OPERation:PTRansition

Sets the positive transition filter. Setting a bit in the positive transition filter shall cause a 0 to1 transition in the corresponding bit of the associated condition register to cause a 1 to bewritten in the associated bit of the corresponding event register.



20.2 :PRESetSTATus:PRESet

The PRESet command is an event that configures the SCPI and device-dependent status datastructures such that device-dependent events are reported at a higher level through the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



mandatory part of the status-reporting mechanism. Device-dependent events are summarizedin the mandatory structures. The mandatory structure is defined in part by IEEE 488.2;SCPI-required structures compose the rest. The mandatory part of the status-reportingmechanism provides a device-independent interface for determining the gross status of adevice.

TK012The PRESet command affects only the enable register, the transition filter registers, andqueue enabling for the SCPI-mandated and device-dependent status data structures. PRESetdoes not affect either the “status byte” or the “standard event status” as defined by IEEE488.2. PRESet does not clear any of the event registers or any item from the error/eventqueue. The *CLS command is used to clear all event registers and queues in the devicestatus-reporting mechanism.

TK012For the device-dependent status data structures, the PRESet commands shall set the enableregister to all 1’s and the transition filter register to a device-dependent value. Thedevice-dependent value shall be either PTR, NTR, or both, such that the device-dependentevent shall be propagated to the structure that summarizes that event. For the SCPImandatory status data structures, the PRESet command shall set the transition filter registersto recognize only positive transitions and set the enable register to 0’s. The PREsetcommand shall also set error/event queue enabling to report only errors.

An application may select the events that shall cause a service request at the mandatory SCPIstatus data structure level, rather than excluding those that are of no interest to theapplication. Further, there is no requirement on the application to set up thedevice-dependent structures for normal device operation.

For this concept to be extended to encompass the IEEE 488.2-mandated status datastructures, the following sequence of commands is required when initializing the device:

TK012*CLS – Clears all event status registers and queues

*SRE 0 – Clears the IEEE 488.2-mandated service request enable register

*ESE 0 – Clears the IEEE 488.2-mandated standard event status enable register

TK012STATus:PRESet – Presets all other registers and queues

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The table below indicates the effects of various commands upon the status data structures in a device.

SCPITransition

Filters

SCPIEnable

Registers

SCPIEvent

Registers

SCPIError/Event

QueueEnable

SCPIError/Event

Queue

IEEE 488.2RegistersESE SRE

IEEE 488.2Registers

SESR STB

*RST none none none none none none none

*CLS none none clear none clear none clear

power-on preset# preset# clear# preset# clear# clear# clear#

STATus:PRESet preset preset none preset none none none#Occurs if the power-on state clear flag is true. Effect changes to none if the power-on state clear flagis false.

The following table defines the effect of STATus:PRESet

Register Filter/enable PRESet value =

OPERational ENABlePTRNTR

0’s1’s0’s

QUEStionable ENABlePTRNTR

0’s1’s0’s

ISUMmary ENABlePTRNTR

0’s1’s0’s

INSTrument ENABlePTRNTR

1’sdevice-dependent#device-dependent#

All others ENABlePTRNTR

1’sdevice-dependent#device-dependent#

# Requires either PTR, NTR, or both to be set.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



20.3 :QUEStionable STATus:QUEStionable?

The QUEStionable status register set contains bits which give an indication of the quality ofvarious aspects of the signal.

A bit set in the condition register indicates that the data currently being acquired orgenerated is of questionable quality due to some condition affecting the parameter associatedwith that bit. For example, if the FREQ bit were set, this would mean that the frequencyaccuracy of the signal was of questionable quality.

See Volume 1 Section 9.4 for more detailed information.

20.3.1 :BIT<n>:STATus:QUEStionable:BIT<n>

This command accesses the user-definable bits in the QUEStionable register set. The valueof <n> is restricted from 9 to 12 and represents bits 9 through 12 in the:STATus:QUEStionable status register. This allows standardized access to user-definableterminal and summary bits.

Note that this definition is different from that of :STATus:OPERation:BIT in that the bitnumber is restricted to the range of 9 through 12, while the range for:STATus:OPERation:BIT is restricted to 8 through 12.

20.3.2 :CONDition?STATus:QUEStionable:CONDition?

Defined the same as STATus:OPERation:CONDition. See Section 20.1.2 for details.

20.3.3 :ENABle <NRf> | <non-decimal numeric>STATus:QUEStionable:ENABle

Defined the same as STATus:OPERation:ENABle. See Section 20.1.3 for details.

20.3.4 [:EVENt]?STATus:QUEStionable:EVENt?

Defined the same as STATus:OPERation:EVENt. See Section 20.1.4 for details.

20.3.5 :MAP <NRf>,<NRf>STATus:QUEStionable:MAP

Defined the same as STATus:OPERation:MAP. See Section 20.1.5 for details.

20.3.6 :NTRansition <NRf> | <non-decimal numeric>STATus:QUEStionable:NTRansition

Defined the same as STATus:OPERation:NTRansition. See Section 20.1.6 for details.

20.3.7 :PTRansition <NRf> | <non-decimal numeric>STATus:QUEStionable:PTRansition

Defined the same as STATus:OPERation:PTRansition. See Section 20.1.7 for details.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



21 SYSTem SubsystemThe SYSTem subsystem collects the functions that are not related to instrumentperformance. Examples include functions for performing general housekeeping andfunctions related to setting global configurations, such as TIME or SECurity.

KEYWORD PARAMETER FORM NOTESSYSTem :ALTernate <numeric_value> :STATe <Boolean> :BEEPer :FREQuency <numeric_value> [:IMMediate] [<frequency>[,<time>[,<volume>]]] :STATe <Boolean> :TIME <numeric_value> :VOLume <numeric_value>

TWV41C :CAPability? [query only] 1994 :COMMunicate :CENTronics 1993 HP063e :FEED <data_handle> 1993 HP063e :GPIB RDEVice 1993 HP063e :ADDRess <numeric_value>[,<numeric_value>] 1993 HP063e :FEED <data_handle> 1993 HP063e [:SELF] 1993 HP063e :ADDRess <numeric_value>[,<numeric_value>] 1993 HP063e :SERial :CONTrol 1991 HP047

:DTR ON|OFF|STANdard|IBFull 1991 HP047

:RTS ON|OFF|STANdard|IBFull|RFR 1991 HP047

:FEED <data_handle> 1993 HP063e [:RECeive] :BAUD <numeric_value> :BITS <numeric_value> :PACE XON|ACK|NONE :THReshold 1991 HP047

:STARt <numeric_value> 1991 HP047

:STOP <numeric_value> 1991 HP047

:PARity :CHECk <Boolean> [:TYPE] EVEN|ODD|ZERO|ONE|NONE :SBITs <numeric_value> :TRANsmit :AUTO <Boolean> :BAUD <numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem 21-1

KEYWORD PARAMETER FORM NOTES :BITS <numeric_value> :DELay <numeric_value> 1993 TK014 :PACE XON|ACK|NONE :PARity [:TYPE] EVEN|ODD|ZERO|ONE|NONE :SBITs <numeric_value> :SOCKet <n> 1999 :ADDRess <string> (IPaddress|Host name) 1999 :CONNect 1999 :DISConnect 1999 :FEED <data_handle>{,<data_handle>} 1999 :OCONdition <event_handle> 1999 :SCONdition <event_handle> 1999 :LISTen 1999 :PORT <numeric_value> (port #) 1999 :TYPE TCP | UDP 1999 :CPON <card_destination>|ALL [event; no query] :CTYPe? <card_destination> [query only] :DATE <numeric_value>,<numeric_value>,<numeric_value> :ERRor :ALL? [query only] 1996 :CODE 1996 :ALL? [query only] 1996 [:NEXT]? [query only] 1996 :COUNT? [query only] 1996 :ENABle 1999 :ADD <numeric_list> [no query] 1999 :DELete <numeric_list> [no query] 1999 [:LIST] <numeric_list> 1999 [:NEXT]? [query only] 1996 :HELP 1992

HP099b :HEADers? [query only] 1995 PH002

:SYNTax? <command_header> [query only] 1992 PH002

:KEY <numeric_value> :CATalog :DEFine <numeric_value>,<block>[,<string>] :DELete :KLOCk <Boolean> :LANGuage <string> :LFRequency <numeric_value> 1992 HP053

:AUTO <Boolean> | ONCE 1992 HP053

TK024 :LOCK 1999 :OWNer? [query only] 1999 :RELease [no query] 1999

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-2 SYSTem

KEYWORD PARAMETER FORM NOTES :REQuest? [event; query only]1999 :PASSword 1994

TK024 :CDISable <password> [event; no query]1994TK024 [:CENable] <password> [event; no query]1994TK024 :STATe? [query only] 1994TK024 :NEW <current_password>,<new_password> [event; no query]1994

:PRESet [event; no query] :SECurity

TK025 :IMMediate [event; no query]1994 [:STATe] <Boolean> :SET <block data> :TIME <numeric_value>,<numeric_value>,<numeric_value> :TIMer 1999 :COUNt <numeric_value> 1999 [:STATe] <Boolean> 1999 :TZONe <numeric_value>[,<numeric_value>] :VERSion?

21.1 :ALTernate <numeric_value>SYSTem:ALTernate

Selects an alternate instrument state, which is swapped with the current state at the end ofsome specified action. The <numeric_value> selects which of the states will be used. Thestates are created with the *SAV command. The action is generally sweep, list sequencing orsome programmable delay, depending on the device configuration.


21.1.1 :STATe <Boolean>SYSTem:ALTernate:STATe

Controls whether the alternate state mode is enabled. While it is ON, the device shall swapthe active state with the one stored in the register specified in ALTernate.


21.2 :BEEPerSYSTem:BEEPer

This subsystem controls the audible beeper of the instrument.

21.2.1 :FREQuency <numeric_value>SYSTem:BEEPer:FREQuency

Programs the frequency of audible tones. It also sets the default frequency for the[:IMMediate] command. The parameter is specified in Hz. The range of valid parameters isinstrument-dependent.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:ALTernate 21-3

21.2.2 [:IMMediate][<frequency>[,<time>[,<volume>]]]SYSTem:BEEPer:IMMediate

The receipt of this command causes an audible tone to be generated by the instrument. Notethat this command generates an event and therefore it has no associated *RST state or queryform.

The allowable values of the parameters <frequency>, <time> and <volume> areinstrument-dependent. The frequency parameter is specified in Hz. The duration timeparameter is specified in seconds. The volume parameter range is from 0 to 1, with 1indicating the maximum volume that the instrument can produce and 0 indicating minimumvolume.

21.2.3 :STATe <Boolean>SYSTem:BEEPer:STATe

Enables/disables the beeper. When STATe OFF is selected, no instrument condition, exceptthe :SYSTem:BEEPer:IMMediate command, shall cause an audible beep to be emitted.


21.2.4 :TIME <numeric_value>SYSTem:BEEPer:TIME

Programs the duration of audible tones. It also sets the default duration for the [:IMMediate]command. The parameter is specified in seconds. The range of valid parameters isinstrument-dependent.


21.2.5 :VOLume <numeric_value>SYSTem:BEEPer:VOLume

Programs the volume of audible tones. It also sets the default volume for the [:IMMediate]command. The parameter range is from 0 to 1, with 1 indicating the maximum volume thatthe instrument can produce and 0 indicating minimum volume. Actual sound pressure levelsgenerated by any particular volume setting are instrument-dependent.


TWV41C21.3 :CAPability?SYSTem:CAPability?

TWV41CThis query returns an <instrument_specifier>. See the Compliance section in theintroduction to Instrument Class Applications.

21.4 :COMMunicateSYSTem:COMMunicate

The COMMunicate subsystem collects together the configuration of variouscontrol/communication interfaces.

21.4.1 :CENTronics HP063eSYSTem:COMMunicate:CENTronics

The CENTronics subsystem sets the physical configuration of a centronics port.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-4 SYSTem:CAPability?

21.4.1.1 :FEED <data_handle> HP063eSYSTem:COMMunicate:CENTronics:FEED

Sets or queries what data is used to FEED the remote device. Data may be streamed to anexternal device without sending it through the HCOPy subsystem, for example by directlyfeeding SENSe or CALCulate data, where no page formatting commands are needed. Thatis, the SYSTem:COMMunicate subsystem shall not add any page formatting to the outputstream, where this is required HCOPy should be used.

At *RST, FEED is device dependent.

21.4.2 :GPIBSYSTem:COMMunicate:GPIB

The GPIB subsystem controls the physical configuration of a GPIB (IEEE 488) port.

21.4.2.1 :RDEVice HP063eSYSTem:COMMunicate:GPIB:RDEVice

The Remote DEVice subsystem configures how the instrument uses a peripheral device,such as a printer or plotter, connected to a GPIB port.

21.4.2.1.1 :ADDRess <numeric_value>[,<numeric_value>] HP063eSYSTem:COMMunicate:GPIB:RDEVice:ADDRess

Sets or queries the bus address of the peripheral device. The first parameter is the primaryaddress and the optional second parameter is the secondary address. Changing the addresswith this does not affect the address of the peripheral device. It does affect the address towhich data is sent by the instrument.


21.4.2.1.2 :FEED <data_handle> HP063eSYSTem:COMMunicate:GPIB:RDEVice:FEED

Sets or queries what data is used to FEED the peripheral device. Data may be streamed to anexternal device without sending it through the HCOPy subsystem, for example by directlyfeeding SENSe or CALCulate data, where no page formatting commands are needed. Thatis, the SYSTem:COMMunicate subsystem shall not add any page formatting to the outputstream. Where page formatting is required, HCOPy should be used.


21.4.2.2 [:SELF] HP063eSYSTem:COMMunicate:GPIB[:SELF]

The SELF subsystem sets the configuration relating to the GPIB port on the instrument itself.

21.4.2.2.1 :ADDRess <numeric_value>[,<numeric_value>] HP063eSYSTem:COMMunicate:GPIB[:SELF]:ADDRess

Sets the GPIB address of the instrument. The first parameter is the primary address and theoptional second parameter is the secondary address.

*RST has no effect on the value of these parameters.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:COMMunicate 21-5

21.4.3 :SERialSYSTem:COMMunicate:SERial

Controls the physical configuration of a serial port, such as RS-232-D, RS-422, orEIA/TIA-562. Any command that changes the configuration of the port takes effectimmediately upon receipt of the Program Message Terminator.

TK014*RST has no effect on the value of these parameters.

21.4.3.1 :CONTrolSYSTem:COMMunicate:SERial:CONTrol

HP047

Add command which independently sets the mode in which DTR and RTS pacing operate.Since hardware handshaking can be configured to pertain to either transmit, receive, or both,a CONTrol branch separate from the transmit and receive branches was added.

21.4.3.1.1 :DTR ON|OFF|STANdard|IBFull TK014SYSTem:COMMunicate:SERial:CONTrol:DTR

Sets the hardware pacing scheme. TK014

The ON parameter indicates that the DTR line should always be asserted (held in the ONcondition).

TK014The OFF parameter indicates that the DTR line should always be unasserted (held in theOFF condition).

TK014When the STANdard option is set for DTR, the DTR line behaves as specified in the EIAstandard RS-232-D section 4.4. As stated in the standard:

“Signals on this circuit are used to control the switching of the DCE to thecommunication channel. The ON condition prepares the DCE to be connected to thecommunication channel and maintains the connection established by external means.”

TK014A common use of the DTR line that has evolved is that of pacing. The IBFull parameter setsthe DTR line to indicate when the device is ready to receive. When the number of receivedbytes in the input buffer of the device reaches the STOP threshold the device will de-assertthe DTR line. When the number of bytes has been reduced to the STARt threshold, thedevice will assert DTR indicating that it can receive input again. The device will alsomonitor the state of DSR and CTS and will stop transmission if either of those lines becomesde-asserted.

TK014*RST has no effect on the value of this parameter.

21.4.3.1.2 :RTS ON|OFF|STANdard|IBFull|RFRSYSTem:COMMunicate:SERial:CONTrol:RTS

Sets the hardware pacing (hand-shaking) scheme. TK014

The ON parameter indicates that the RTS line should always be asserted. TK014

The OFF parameter indicates that the RTS line should always be unasserted. TK014

When the STANdard option is set for RTS, the RTS line behaves as specified in the EIAstandard RS-232-D section 4.4. As stated in the standard:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-6 SYSTem:COMMunicate

“This circuit is used to condition the local DCE for data transmission and on ahalf-duplex channel, to control the direction of data transmission of the local DCE.”

TK014A common use of the RTS line that has evolved is that of pacing. Many high speedasynchronous modems use this line (paired with CTS) as receive/transmit pacing. The IBFullor its alias RFR (Ready For Receiving) parameter sets the RTS line to indicate when thedevice is ready to receive. When the number of received bytes in the input buffer of thedevice reaches the STOP threshold the device will de-assert the RTS line. When the numberof bytes has been reduced to the STARt threshold, the device will assert RTS, indicating thatit can receive input again. The device will also monitor the state of CTS and will stoptransmission if that line becomes de-asserted.

TK014The IBFull (RFR) mode follows the CCITT Recommendations V.42, Section 7.3.1, “FlowControl across the DTE/DCE interface, Option a) Using Circuit 133 and 106.”


21.4.3.2 :FEED <data_handle> HP063eSYSTem:COMMunicate:SERial:FEED

Sets or queries what data is used to FEED the peripheral device connected to the serial port.Data may be streamed to an external device without sending it through the HCOPysubsystem, for example by directly feeding SENSe or CALCulate data, where no pageformatting commands are needed. That is, the SYSTem:COMMunicate subsystem shall notadd any page formatting to the output stream, where this is required HCOPy should be used.


21.4.3.3 [:RECeive]SYSTem:COMMunicate:SERial:RECeive

The optional node RECeive is used to affect the parameters associated with reception.

21.4.3.3.1 :BAUD <numeric_value>SYSTem:COMMunicate:SERial:RECeive:BAUD

Sets the baud rate.

*RST has no effect on the value of this parameter.

21.4.3.3.2 :BITS <numeric_value>SYSTem:COMMunicate:SERial:RECeive:BITS

Sets the number of data bits, typically 7 or 8. The value shall be rounded to the nearestinteger.


21.4.3.3.3 :PACE XON|ACK|NONESYSTem:COMMunicate:SERial:RECeive:PACE

This command sets the software pacing scheme.

The XON pacing mode follows the CCITT Recommendations V.42, Section 7.3.1, “FlowControl across the DTE/DCE interface, Option b) Using DC1/DC3 characters (XON/XOFFfunctions).”

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




21.4.3.3.3.1 :THResholdSYSTem:COMMunicate:SERial:RECeive:PACE:THReshold

HP047

This command sets the recieve pacing threshold.

21.4.3.3.3.1.1 :STARt <numeric_value>SYSTem:COMMunicate:SERial:RECeive:PACE:THReshold:STARt

HP047

This command indicates that when the number of characters in the device’s input buffer goesto or below the indicated amount and some form of pacing has been set, the device shouldindicate that it is ready to receive.


21.4.3.3.3.1.2 :STOP <numeric_value>SYSTem:COMMunicate:SERial:RECeive:PACE:THReshold:STOP

HP047

This command indicates that when the number of characters in the device’s input buffer goesto or above the indicated amount and some form of pacing has been set, the device shouldindicate that it is not ready to receive.


21.4.3.3.4 :PARity SYSTem:COMMunicate:SERial:RECeive:PARity

This subsystem controls the parity of the receiving channel

21.4.3.3.4.1 :CHECk <Boolean>SYSTem:COMMunicate:SERial:RECeive:PARity:CHECk

When CHECk ON is selected, the parity shall be checked in accordance with the selectedPARity:TYPE.

When CHECk is OFF, the parity TYPE setting (NONE or “other than NONE”) stilldetermines the expectation of not receiving or receiving a parity bit.


TK014

21.4.3.3.4.2 [:TYPE] EVEN|ODD|ZERO|ONE|NONE|IGNoreSYSTem:COMMunicate:SERial:RECeive:PARity:TYPE

Sets the parity scheme that is to be employed for reception.


21.4.3.3.5 :SBITs <numeric_value>SYSTem:COMMunicate:SERial:RECeive:SBITs

Sets the number of stop bits, typically 1, 1.5 or 2 bits.TK014


21.4.3.4 :TRANsmitSYSTem:COMMunicate:SERial:TRANsmit

Affects the parameters associated with transmission.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



21.4.3.4.1 :AUTO <Boolean>SYSTem:COMMunicate:SERial:TRANsmit:AUTO

Couples the TRANsmit parameter values to the RECeive parameter values when AUTO ONis selected.


21.4.3.4.2 :BAUD <numeric_value>SYSTem:COMMunicate:SERial:TRANsmit:BAUD

This command sets the baud rate.


21.4.3.4.3 :BITS <numeric_value>SYSTem:COMMunicate:SERial:TRANsmit:BITS

Sets the number of data bits, typically 7 or 8. The value shall be rounded to the nearestinteger.


21.4.3.4.4 :DELay <numeric_value> TK014SYSTem:COMMunicate:SERial:TRANsmit:DELay

Sets the minimum delay in seconds that the device must wait after receipt of a ProgramMessage Terminator before issuing a response message. The delay does not apply tosoftware pacing or to other low level protocols.


21.4.3.4.5 :PACE XON|ACK|NONESYSTem:COMMunicate:SERial:TRANsmit:PACE

Sets the software pacing scheme.

The XON pacing mode follows the CCITT Recommendations V.42, Section 7.3.1, “FlowControl across the DTE/DCE interface, Option b) Using DC1/DC3 characters (XON/XOFFfunctions).”


21.4.3.4.6 :PARitySYSTem:COMMunicate:SERial:TRANsmit:PARity

This subsystem controls the parity of the transmitting channel

21.4.3.4.6.1 [:TYPE] EVEN|ODD|ZERO|ONE|NONESYSTem:COMMunicate:SERial:TRANsmit:PARity:TYPE

Sets the parity scheme that is to be employed for transmission.


21.4.3.4.7 :SBITs <numeric_value>SYSTem:COMMunicate:SERial:TRANsmit:SBITs

Sets the number of stop bits, typically 1, 1.5, or 2 bits.TK014

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




21.4.4 :SOCKet <n>:SYSTem:COMMunicate:SOCKet<n>

This command identifies the socket to be opened. The syntax of the numeric suffix is asspecified in 6.2.5.2 in Volume 1, Syntax and Style.

21.4.4.1 :ADDRess <string>:SYSTem:COMMunicate:SOCKet:ADDRess

This command allows the user to enter the IP address or host name of the remote device. If itis an IP address, it is specified using IP dot notation (e.g. 123.45.67.89). If it is a host name,it is specified by using the host name string (e.g., my_host).

21.4.4.2 :CONNect:SYSTem:COMMunicate:SOCKet:CONNect

This command implements the socket connection.

21.4.4.3 :DISConnect:SYSTem:COMMunicate:SOCKet:DISConnect

The Disconnect command breaks the socket connection.

21.4.4.4 :FEED <n> <data_handle>{,<data_handle>}:SYSTem:COMMunicate:SOCKet:FEED

Sets or queries what data is used to FEED the communications socket.

Note: There can be multiple FEEDs for the same socket.

21.4.4.4.1 :OCONdition <event_handle>:SYSTem:COMMunicate:SOCKet:FEED:OCONdition

The On Condition command, :OCONditon, defines the rate at which data will be collectedand sent to the socket FEED.

21.4.4.4.2 :SCONdition <event_handle>:SYSTem:COMMunicate:SOCKet:FEED:SCONdition

The Send Condition, SCONdition, defines the rate at which the data will be transmitted onthe socket.

21.4.4.5 :LISTen:SYSTem:COMMunicate:SOCKet:LISTen

The LISTen command instructs the device (instrument) to listen for a connection on thespecified socket. This will allow data channels from one instrument to another instrument tobe opened.

21.4.4.6 :PORT <numeric_value>:SYSTem:COMMunicate:SOCKet:PORT

This command allows the user to enter the port number. This parameter is a 16 bit integer.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



21.4.4.7 :TYPE TCP|UDP:SYSTem:COMMunicate:SOCKet :TYPE

This command allows the user to select the type of Ethernet port to be opened, either TCP orUPD. The query form will return either TCP or UDP.

21.5 :CPON <card_destination>|ALLSYSTem:CPON

Card Power ON resets a card within a cardcage to its power-on state. The parameter caneither be a module number or a user-defined card name. If the parameter is ALL, then alladdressable cards are reset to their power-on state.

SYSTem:CPON is an event; no query is allowed.

21.6 :CTYPe? <card_destination>SYSTem:CTYPe?

The Card TYPe query identifies a card within a cardcage. The response is identical in formto that defined for the “*IDN?” query in IEEE 488.2.

21.7 :DATE <year>,<month>,<day>SYSTem:DATE

Any instrument which has an internal calendar shall implement the following command toset the calendar:

<year>: Must be <numeric_value>. It is rounded to the nearest integer. Its range is limitedby the capability of the instrument. The year shall be entered as a four-digitnumber, including century and millennium information.

<month>: Must be <numeric_value>. It is rounded to the nearest integer. Its range is 1 to 12inclusive. The number 1 corresponds to the month January, 2 to February, and soon.

<day>: Must be <numeric_value>. It is rounded to the nearest integer. Its range is 1 tonumber of days in the month from the previous parameter. A deviceimplementing this command shall keep track of the number of days in eachmonth, accounting for leap years through the range of years that it accepts.

The response message shall consist of three fields separated by commas:<year>,<month>,<day>

<year>: NR1 format. Range is device-dependent.

<month>: NR1 format. Range is 1 to 12.

<day>: NR1 format. Range is 1 to 31.

This shall not be affected by a *RST command.

21.8 :ERRor SubsystemSYSTem:ERRor

This subsystem collects commands and queries relating to the reading and control of the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:CPON 21-11

error/event queue.

The error/event queue contains items that include a numerical and textual description of theerror or event. Querying for the full queue item (for example, withSYSTem:ERRor[:NEXT]?) will return a response with the following syntax:

The <Error/event_number> is a unique integer in the range [-32768, 32767]. All positivenumbers are instrument-dependent. All negative numbers are reserved by the SCPI standardwith certain standard error/event codes described in this document. The value, zero, is alsoreserved to indicate that no error or event has occurred.

The second parameter of the full response is a quoted string containing an<Error/event_description> followed by optional <Device-dependent info> text. Each<Error/event_number> has a unique and fixed <Error/event_description> associated with it.

The maximum string length of <Error/event_description> plus <Device-dependent_info> is255 characters. For standard defined error/event codes, the <Error/event_description> shallbe sent exactly as indicated in this document including case.

The <Device-dependent_info> text is optional but may be useful in some instruments toprovide additional information allowing the user to determine the exact error or event and itscontext. If used, it is set off from the <Error/event_description> portion of the string with asemicolon. For example:

-131,"Invalid suffix;FREQuency:CENT 2.0E+5 dBuV"

Device-dependent information may be defined in greater detail for specific instrumentclasses in volume 4.

Where Date and Time are desired to be returned with the error message, they should beappended to the <device_dependent_information> separated by a semi-colon using thefollowing format:

<date><space><time>

date - yyyy/mm/dd - year/month/daytime - hh:mm:ss.sss - 24 hour time

Example:

-200, “Execution error;Torque Safety LimitExceeded;1996/08/15 13:22:51.01"

TK012

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-12 SYSTem:ERRor Subsystem

21.8.1 The Error/Event QueueAs errors and events are detected, they are placed in a queue. This queue is first in, first out.If the queue overflows, the last error/event in the queue is replaced with error

-350,"Queue overflow"

Any time the queue overflows, the least recent errors/events remain in the queue, and themost recent error/event is discarded. The minimum length of the error/event queue is 2, oneposition for the first error/event, and one for the “Queue overflow” message. Reading anerror/event from the head of the queue removes that error/event from the queue, and opens aposition at the tail of the queue for a new error/event, if one is subsequently detected.

TK012When all errors/events have been read from the queue, further error/event queries shallreturn

0, “No error”

After a STATus:PRESet, the masking shall be changed so that only errors are reported.Below is an overview of how the ERRor system works.

TK012The error/event queue shall be cleared when any of the following occur (IEEE 488.2, section11.4.3.4):

Upon receipt of a *CLS command.

Upon reading the last item from the queue.

Real World Event Occurs

Ex Stabilization Error

Black Box

Assign Error/Event #

If it exists

Is this Error/Event # enabled?

(SYSTem:ERRor:ENABle)

Error/Event Queue

If the queue size is >0,

then set bit 2 in Status Byte

Figure 21.1 System Error Format

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:ERRor Subsystem 21-13

TK04721.8.2 Error/Event numbersThe system-defined error/event numbers are chosen on an enumerated (“1 of N”) basis. TheSCPI-defined error/event numbers and the <error/event_description> portions of the fullqueue item are listed here. The first error/event described in each class (for example, -100,-200, -300, -400) is a “generic” error. In selecting the proper Error/event number to report,more specific error/event codes are preferred, and the generic error/event is used only if theothers are inappropriate.

TK012Note the organization of the following tables. A “simple-minded” parser might implementonly the XX0 errors, and a smarter one might implement all of them. A “smart and friendly”parser might use the instrument-dependent part of the error/event message string to point outthe offending part of the command.

21.8.3 No ErrorThis message indicates that the device has no errors or events to report.

TK012Error Number

Error Description [description/explanation/examples]

0 No error[The queue is competely empty. Every error/event in the queue has been read orthe queue was purposely cleared by power-on, *CLS, etc.]

21.8.4 ALL? SYSTem:ERRor:ALL? queries the error/event queue for all the unread items and removesthem from the queue. The response is a comma separated list of number, string pairs in FIFOorder. If the queue is empty, the response is 0,"No error"

Note: If the queue is not empty, the 0,"No error" is not sent.

21.8.5 CODE

21.8.5.1 ALL?SYSTem:ERRor:CODE:ALL? queries the error/event queue for all the unread items andremoves them from the queue. The response returns a comma separated list of only theerror/event code numbers in FIFO order. If the queue is empty, the response is 0.

Note: If the queue is not empty, the 0 is not sent.

21.8.5.2 [NEXT]?SYSTem:ERRor:CODE[:NEXT]? queries the error/event queue for the next item andremoves it from the queue. The response returns only the error/event code number omittingthe string. Except for the shortened response, the query operates identically toSYSTem:ERRor[:NEXT]?

21.8.6 COUNt?SYSTem:ERRor:COUNt? queries the error/event queue for the number of unread items. Aserrors and events may occur at any time, more items may be present in the queue at the timeit is actually read.

Note: If the queue is empty, the response is 0.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



21.8.7 :ENABleSYSTem:ERRor:ENABle

The ENABle subsystem sets the errors and events that will be allowed into the queue.

At *RST, this list is not changed.

21.8.7.1 :ADD <numeric list>SYSTem:ERRor:ENABle:ADD

The events included in the numeric list are added to the previous ENABle list. The syntax of<numeric list> is the same as SYSTem:ERRor:ENABle:LIST.

This command is an event and cannot be queried.

21.8.7.2 :DELete <numeric list>SYSTem:ERRor:ENABle:DELete

The events included in the numeric list are deleted from the previous ENABle. The syntax of<numeric list> is the same as SYSTem:ERRor:ENABle:LIST.

This command is an event and cannot be queried.

21.8.7.3 [:LIST] <numeric list>SYSTem:ERRor:ENABle[:LIST]

The list indicates which errors/events are allowed to enter the queue. The list allows acomma separated list or a range of numbers. In the case of a range, the end points areinclusive. For example, SYSTem:ERRor:ENABle (-123,225:227) will allow eventsnumbered -123, 225, 226, and 227 to enter the queue.

At *RST, this list is not changed.

21.8.8 [NEXT]?SYSTem:ERRor[:NEXT]

SYSTem:ERRor[:NEXT]? queries the error/event queue for the next item and removes itfrom the queue. The response returns the full queue item consisting of an integer and a stringas described in the introduction to the SYSTem:ERRor subsystem.

This command is required of all SCPI implementations (See Syntax and Style, 4.2.1.

21.8.9 Command ErrorAn <error/event number> in the range [ -199 , -100 ] indicates that an IEEE 488.2 syntaxerror has been detected by the instrument’s parser. The occurrence of any error in this classshall cause the command error bit (bit 5) in the event status register (IEEE 488.2, section11.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, acontroller-to-device message was received which is in violation of the IEEE 488.2standard. Possible violations include a data element which violates the devicelistening formats or whose type is unacceptable to the device.

An unrecognized header was received. Unrecognized headers include incorrectdevice-specific headers and incorrect or unimplemented IEEE 488.2 commoncommands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



A Group Execute Trigger (GET) was entered into the input buffer inside of anIEEE 488.2 <PROGRAM MESSAGE>.

Events that generate command errors shall not generate execution errors, device-specificerrors, or query errors; see the other error definitions in this chapter.

Error Number

Error Description [description/explanation/examples]

-100 Command error[This is the generic syntax error for devices that cannot detect more specificerrors. This code indicates only that a Command Error as defined in IEEE 488.2,11.5.1.1.4 has occurred.]

-101 Invalid character[A syntactic element contains a character which is invalid for that type; forexample, a header containing an ampersand, SETUP&. This error might be usedin place of errors -114, -121, -141, and perhaps some others.]

-102 Syntax error[An unrecognized command or data type was encountered; for example, a stringwas received when the device does not accept strings.]

-103 Invalid separator[The parser was expecting a separator and encountered an illegal character; forexample, the semicolon was omitted after a program message unit, *EMC 1:CH1:VOLTS 5.]

-104 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.]

-105 GET not allowed[A Group Execute Trigger was received within a program message (see IEEE488.2, 7.7).]

-108 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 isnot allowed.]

-109 Missing parameter[Fewer parameters were recieved than required for the header; for example, the*EMC common command requires one parameter, so receiving *EMC is notallowed.]

-110 Command header error[An error was detected in the header. This error message should be used when thedevice cannot detect the more specific errors described for errors -111 through-119.]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-111 Header separator error[A character which is not a legal header separator was encountered while parsingthe header; for example, no white shace followed the header, thus*GMC"MACRO" is an error.]

-112 Program mnemonic too long[The header contains more that twelve characters (see IEEE 488.2, 7.6.1.4.1).]

-113 Undefined header[The header is syntactically correct, but it is undefined for this specific device; forexample, *XYZ is not defined for any device.]

-114 Header suffix out of range [The value of a numeric suffix attached to a program mnemonic, see Syntax andStyle section 6.2.5.2, makes the header invalid.]

-115 Unexpected number of parameters [The number of parameters received does not correspond to the number ofparameters expected. This is typically due an inconsistency with the number ofinstruments in the selected group (see section on INSTrument:DEFine:GROup).]

-120 Numeric data error[This error, as well as errors -121 through -129, are generated when parsing a dataelement which apprears to be numeric, including the nondecimal numeric types.This particular error message should be used if the device cannot detect a morespecific error.]

-121 Invalid character in number[An invalid character for the data type being parsed was encountered; forexample, an alpha in a decimal numeric or a “9" in octal data.]

-123 Exponent too large[The magnitude of the exponent was larger than 32000 (see IEEE 488.2,7.7.2.4.1).]

-124 Too many digits[The mantissa of a decimal numeric data element contained more than 255 digitsexcluding leading zeros (see IEEE 488.2, 7.7.2.4.1).]

-128 Numeric data not allowed [A legal numeric data element was received, but the device does not accept one inthis position for the header.]

-130 Suffix error[This error, as well as errors -131 through -139, are generated when parsing asuffix. This particular error message should be used if the device cannot detect amore specific error.]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-131 Invalid suffix[The suffix does not follow the syntax described in IEEE 488.2, 7.7.3.2, or thesuffix is inappropriate for this device.]

-134 Suffix too long[The suffix contained more than 12 characters (see IEEE 488.2, 7.7.3.4).]

-138 Suffix not allowed [A suffix was encountered after a numeric element which does not allow suffixes.]

-140 Character data error[This error, as well as errors -141 through -149, are generated when parsing acharacter data element. This particular error message should be used if the devicecannot detect a more specific error.]

-141 Invalid character data[Either the character data element contains an invalid character or the particularelement received is not valid for the header.]

-144 Character data too long[The character data element contains more than twelve characters (see IEEE488.2, 7.7.1.4).]

-148 Character data not allowed[A legal character data element was encountered where prohibited by the device.]

-150 String data error[This error, as well as errors -151 through -159, are generated when parsing astring data element. This particular error message should be used if the devicecannot detect a more specific error.]

-151 Invalid string data[A string data element was expected, but was invalid for some reason (see IEEE488.2, 7.7.5.2); for example, an END message was received before the terminalquote character.]

-158 String data not allowed[A string data element was encountered but was not allowed by the device at thispoint in parsing.]

-160 Block data error[This error, as well as errors -161 through -169, are generated when parsing ablock data element. This particular error message should be used if the devicecannot detect a more specific error.]

-161 Invalid block data[A block data element was expected, but was invalid for some reason (see IEEE488.2, 7.7.6.2); for example, an END message was received before the length wassatisfied.]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-168 Block data not allowed[A legal block data element was encountered but was not allowed by the device atthis point in parsing.]

-170 Expression error[This error, as well as errors -171 through -179, are generated when parsing anexpression data element. This particular error message should be used if thedevice cannot detect a more specific error.]

-171 Invalid expression[The expression data element was invalid (see IEEE 488.2, 7.7.7.2); for example,unmatched parentheses or an illegal character.]

-178 Expression data not allowed[A legal expression data was encountered but was not allowed by the device atthis point in parsing.]

-180 Macro error[This error, as well as errors -181 through -189, are generated when defining amacro or executing a macro. This particular error message should be used if thedevice cannot detect a more specific error.]

-181 Invalid outside macro definition[Indicates that a macro parameter placeholder ($<number) was encounteredoutside of a macro definition.]

-183 Invalid inside macro definition[Indicates that the program message unit sequence, sent with a *DDT or *DMCcommand, is syntactically invalid (see IEEE 488.2, 10.7.6.3).]

-184 Macro parameter error[Indicates that a command inside the macro definition had the wrong number ortype of parameters.]

21.8.10 Execution ErrorAn <error/event number> in the range [ -299 , -200 ] indicates that an error has beendetected by the instrument’s execution control block. The occurrence of any error in thisclass shall cause the execution error bit (bit 4) in the event status register (IEEE 488.2,section 11.5.1) to be set. One of the following events has occurred:

A <PROGRAM DATA> element following a header was evaluated by the deviceas outside of its legal input range or is otherwise inconsistent with the device’scapabilities.

A valid program message could not be properly executed due to some devicecondition.

Execution errors shall be reported by the device after rounding and expression evaluationoperations have taken place. Rounding a numeric data element, for example, shall not bereported as an execution error. Events that generate execution errors shall not generate

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Command Errors, device-specific errors, or Query Errors; see the other error definitions inthis section.

Error Number

Error String [description/explanation/examples]

-200 Execution error[This is the generic syntax error for devices that cannot detect more specificerrors. This code indicates only that an Execution Error as defined in IEEE 488.2,11.5.1.1.5 has occurred.]

-201 Invalid while in local[Indicates that a command is not executable while the device is in local due to ahard local control (see IEEE 488.2, 5.6.1.5); for example, a device with a rotaryswitch receives a message which would change the switches state, but the deviceis in local so the message can not be executed.]

-202 Settings lost due to rtl[Indicates that a setting associated with a hard local control (see IEEE 488.2,5.6.1.5) was lost when the device changed to LOCS from REMS or to LWLSfrom RWLS.]

TK024-203 Command protected[Indicates that a legal password-protected program command or query could notbe executed because the command was disabled.]

-210 Trigger error

-211 Trigger ignored[Indicates that a GET, *TRG, or triggering signal was received and recognized bythe device but was ignored because of device timing considerations; for example,the device was not ready to respond. Note: a DT0 device always ignores GET andtreats *TRG as a Command Error.]

-212 Arm ignored[Indicates that an arming signal was received and recognized by the device butwas ignored.]

-213 Init ignored[Indicates that a request for a measurement initiation was ignored as anothermeasurement was already in progress.]

-214 Trigger deadlock[Indicates that the trigger source for the initiation of a measurement is set to GETand subsequent measurement query is received. The measurement cannot bestarted until a GET is received, but the GET would cause an INTERRUPTEDerror.]

-215 Arm deadlock [Indicates that the arm source for the initiation of a measurement is set to GETand subsequent measurement query is received. The measurement cannot be

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



started until a GET is received, but the GET would cause an INTERRUPTEDerror.]

-220 Parameter error[Indicates that a program data element related error occurred. This error messageshould be used when the device cannot detect the more specific errors describedfor errors -221 through -229.]

-221 Settings conflict[Indicates that a legal program data element was parsed but could not be executeddue to the current device state (see IEEE 488.2, 6.4.5.3 and 11.5.1.1.5.)]

-222 Data out of range[Indicates that a legal program data element was parsed but could not be executedbecause the interpreted value was outside the legal range as defined by the device(see IEEE 488.2, 11.5.1.1.5.)]

-223 Too much data[Indicates that a legal program data element of block, expression, or string typewas received that contained more data than the device could handle due tomemory or related device-specific requirements.]

-224 Illegal parameter value[Used where exact value, from a list of possibles, was expected.]

-225 Out of memory. [The device has insufficent memory to perform the requestedoperation.]

HP058A

-226 Lists not same length. [Attempted to use LIST structure having individual LIST’sof unequal lengths.]

HP058A

-230 Data corrupt or stale[Possibly invalid data; new reading started but not completed since last access.]

-231 Data questionable[Indicates that measurement accuracy is suspect.]

-232 PH073Invalid format[Indicates that a legal program data element was parsed but could not be executedbecause the data format or structure is inappropriate. For example when loadingmemory tables or when sending a SYSTem:SET parameter from an unknowninstrument.]

-233 PH073Invalid version[Indicates that a legal program data element was parsed but could not be executedbecause the version of the data is incorrect to the device. This particular errorshould be used when file or block data formats are recognized by the instrumentbut cannot be executed for reasons of version incompatibility. For example, a notsupported file version, a not supported instrument version]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-240 Hardware error[Indicates that a legal program command or query could not be executed becauseof a hardware problem in the device. Definition of what constitutes a hardwareproblem is completely device-specific. This error message should be used whenthe device cannot detect the more specific errors described for errors -241 through-249.]

-241 Hardware missing[Indicates that a legal program command or query could not be executed becauseof missing device hardware; for example, an option was not installed. Definitionof what constitutes missing hardware is completely device-specific.]

-250 Mass storage error[Indicates that a mass storage error occurred. This error message should be usedwhen the device cannot detect the more specific errors described for errors -251through -259.]

-251 Missing mass storage[Indicates that a legal program command or query could not be executed becauseof missing mass storage; for example, an option that was not installed. Definitionof what constitutes missing mass storage is device-specific.]

-252 Missing media[Indicates that a legal program command or query could not be executed becauseof a missing media; for example, no disk. The definition of what constitutesmissing media is device-specific.]

-253 Corrupt media [Indicates that a legal program command or query could not be executed becauseof corrupt media; for example, bad disk or wrong format. The definition of whatconstitutes corrupt media is device-specific.]

-254 Media full [Indicates that a legal program command or query could not be executed becausethe media was full; for example, there is no room on the disk. The definition ofwhat constitutes a full media is device-specific.]

-255 Directory full [Indicates that a legal program command or query could not be executed becausethe media directory was full. The definition of what constitutes a full mediadirectory is device-specific.]

-256 File name not found[Indicates that a legal program command or query could not be executed becausethe file name on the device media was not found; for example, an attempt wasmade to read or copy a nonexistent file. The definition of what constitutes a filenot being found is device-specific.]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-257 File name error[Indicates that a legal program command or query could not be executed becausethe file name on the device media was in error; for example, an attempt was madeto copy to a duplicate file name. The definition of what constitutes a file nameerror is device-specific.]

-258 Media protected[Indicates that a legal program command or query could not be executed becausethe media was protected; for example, the write-protect tab on a disk was present.The definition of what constitutes protected media is device-specific.]

-260 Expression error [Indicates that a expression program data element related error occurred. Thiserror message should be used when the device cannot detect the more specificerrors described for errors -261 through -269.]

-261 Math error in expression[Indicates that a syntactically legal expression program data element could not beexecuted due to a math error; for example, a divide-by-zero was attempted. Thedefinition of math error is device-specific.]

-270 Macro error[Indicates that a macro-related execution error occurred. This error messageshould be used when the device cannot detect the more specific errors describedfor errors -271 through -279.]

-271 Macro syntax error [Indicates that that a syntactically legal macro program data sequence, accordingto IEEE 488.2, 10.7.2, could not be executed due to a syntax error within themacro definition (see IEEE 488.2, 10.7.6.3.)]

-272 Macro execution error [Indicates that a syntactically legal macro program data sequence could not beexecuted due to some error in the macro definition (see IEEE 488.2, 10.7.6.3.)]

-273 Illegal macro label[Indicates that the macro label defined in the *DMC command was a legal stringsyntax, but could not be accepted by the device (see IEEE 488.2, 10.7.3 and10.7.6.2); for example, the label was too long, the same as a common commandheader, or contained invalid header syntax.]

-274 Macro parameter error[Indicates that the macro definition improperly used a macro parameterplaceholder (see IEEE 488.2, 10.7.3).]

-275 Macro definition too long[Indicates that a syntactically legal macro program data sequence could not beexecuted because the string or block contents were too long for the device tohandle (see IEEE 488.2, 10.7.6.1).]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-276 Macro recursion error[Indicates that a syntactically legal macro program data sequence could not beexecuted because the device found it to be recursive (see IEEE 488.2, 10.7.6.6).]

-277 Macro redefinition not allowed[Indicates that a syntactically legal macro label in the *DMC command could notbe executed because the macro label was already defined (see IEEE 488.2,10.7.6.4).]

-278 Macro header not found[Indicates that a syntactically legal macro label in the *GMC? query could not beexecuted because the header was not previously defined.]

-280 Program error[Indicates that a downloaded program-related execution error occurred. This errormessage should be used when the device cannot detect the more specific errorsdescribed for errors -281 through -289. A downloaded program is used to addalgorithmic capability to a device. The syntax used in the program and themechanism for downloading a program is device-specific.]

-281 Cannot create program[Indicates that an attempt to create a program was unsuccessful. A reason for thefailure might include not enough memory.]

-282 Illegal program name[The name used to reference a program was invalid; for example, redefining anexisting program, deleting a nonexistent program, or in general, referencing anonexistent program.]

-283 Illegal variable name[An attempt was made to reference a nonexistent variable in a program.]

-284 Program currently running[Certain operations dealing with programs may be illegal while the program isrunning; for example, deleting a running program might not be possible.]

-285 Program syntax error[Indicates that a syntax error appears in a downloaded program. The syntax usedwhen parsing the downloaded program is device-specific.]

-286 Program runtime error

-290 Memory use error[Indicates that a user request has directly or indirectly caused an error related tomemory or <data_handle>s, this is not the same as “bad” memory.]

-291 HP079Out of memory

-292 HP079Referenced name does not exist

-293 HP079Referenced name already exists

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-294 PH076Incompatible type[Indicates that the type or structure of a memory item is inadequate]

21.8.11 Device-Specific ErrorAn <error/event number> in the range [ -399 , -300 ] or [ 1 , 32767 ] indicates that theinstrument has detected an error which is not a command error, a query error, or anexecution error; some device operations did not properly complete, possibly due to anabnormal hardware or firmware condition. These codes are also used for self-test responseerrors. The occurrence of any error in this class should cause the device-specific error bit (bit3) in the event status register (IEEE 488.2, section 11.5.1) to be set. The meaning of positiveerror 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 aparticular error, the null string should be sent (for example, 42,""). The occurrence of anyerror in this class should cause the device-specific error bit (bit 3) in the event status register(IEEE 488.2, section 11.5.1) to be set. Events that generate device-specific errors shall notgenerate command errors, execution errors, or query errors; see the other error definitions inthis section.

Error Number


-300 Device-specific error[This is the generic device-dependent error for devices that cannot detect morespecific errors. This code indicates only that a Device-Dependent Error as definedin IEEE 488.2, 11.5.1.1.6 has occurred.]

-310 System error[Indicates that some error, termed “system error” by the device, has occurred.This code is device-dependent.]

HP098-311 Memory error[Indicates some physical fault in the device’s memory, such as parity error.]

-312 PUD memory lost[Indicates that the protected user data saved by the *PUD command has been lost.]

-313 Calibration memory lost[Indicates that nonvolatile calibration data used by the *CAL? command has beenlost.]

-314 Save/recall memory lost[Indicates that the nonvolatile data saved by the *SAV? command has been lost.]

-315 Configuration memory lost[Indicates that nonvolatile configuration data saved by the device has been lost.The meaning of this error is device-specific.]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



HP098-320 Storage fault[Indicates that the firmware detected a fault when using data storage. This error isnot an indication of physical damage or failure of any mass storage element.]

HP098+Edit-321 Out of memory[An internal operation needed more memory than was available.]

-330 Self-test failed

TK051-340 Calibration failed

-350 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 butwas not recorded.]

-360 TK014Communication error[This is the generic communication error for devices that cannot detect the morespecific errors described for errors -361 through -363.]

-361 TK014Parity error in program message[Parity bit not correct when data received for example, on a serial port.]

-362 TK014Framing 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).]

-363 HP079Input buffer overrun[Software or hardware input buffer on serial port overflows with data caused byimproper or nonexistent pacing.]

-365 Time out error[This is a generic device-dependent error.]

21.8.12 Query ErrorAn <error/event number> in the range [ -499 , -400 ] indicates that the output queue controlof the instrument has detected a problem with the message exchange protocol described inIEEE 488.2, chapter 6. The occurrence of any error in this class shall cause the query errorbit (bit 2) in the event status register (IEEE 488.2, section 11.5.1) to be set. These errorscorrespond to message exchange protocol errors described in IEEE 488.2, section 6.5. Oneof the following is true:

An attempt is being made to read data from the output queue when no output iseither present or pending;

Data in the output queue has been lost.

Events that generate query errors shall not generate command errors, execution errors, ordevice-specific errors; see the other error definitions in this section.

Error Number


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



-400 Query error[This is the generic query error for devices that cannot detect more specific errors.This code indicates only that a Query Error as defined in IEEE 488.2, 11.5.1.1.7and 6.3 has occurred.]

-410 Query INTERRUPTED[Indicates that a condition causing an INTERRUPTED Query error occurred (seeIEEE 488.2, 6.3.2.3); for example, a query followed by DAB or GET before aresponse was completely sent.]

-420 Query UNTERMINATED[Indicates that a condition causing an UNTERMINATED Query error occurred(see IEEE 488.2, 6.3.2.2); for example, the device was addressed to talk and anincomplete program message was received.]

-430 Query DEADLOCKED[Indicates that a condition causing an DEADLOCKED Query error occurred (seeIEEE 488.2, 6.3.1.7); for example, both input buffer and output buffer are full andthe device cannot continue.]

-440 Query UNTERMINATED after indefinite response[Indicates that a query was received in the same program message after an queryrequesting an indefinite response was executed (see IEEE 488.2, 6.5.7.5).]

TK04721.8.13 Power On EventTK047An <error/event number> in the range [-599:-500] is used when the instrument wishes to

report a 488.2 power on event to the event/error queue. This event occurs when theinstrument detects an off to on transition in its power supply. This event also sets the poweron bit, (bit 7) of the Standard Event Status Register. See IEEE 488.2, section 11.5.1.

EventNumber

Event String [description/explanation/examples]

-500 Power on[The instrument has detected an off to on transition in its power supply.]

TK04721.8.14 User Request EventTK047An <error/event number> in the range [-699:-600] is used when the instrument wishes to

report a 488.2 user request event. This event occurs when the instrument detects theactivation of a user request local control. This event also sets the user request bit (bit 6) ofthe Standard Event Status Register. See IEEE 488.2, section 11.5.1.

EventNumber


-600 User request[The instrument has detected the activation of a user request local control]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK04721.8.15 Request Control EventTK047An <error/event number> in the range [-799:-700] is used when the instrument wishes to

report a 488.2 request control event to the error/event queue. This event occurs when theinstrument requests to become the active IEEE 488.1 controller-in-charge. This event alsosets request control bit (bit 1) of the Standard Event Status Register. See IEEE 488.2,section 11.5.1.

EventNumber


-700 Request control[The instrument requested to become the active IEEE 488.1 controller-in-charge]

TK04721.8.16 Operation Complete EventTK047An <error/event number> in the range [-899:-800] is used when the instrument wishes to

report a 488.2 operation complete event to the error/event queue. This event occurs wheninstrument’s synchronization protocol, having been enabled by an *OPC command,completes all selected pending operations. This protocol is described in IEEE 488.2, section12.5.2. This event also sets the operation complete bit (bit 0) of the Standard Event StatusRegister. See IEEE 488.2, section 11.5.1. Note: *OPC? does not set bit 0 nor does it enterany event in the error/event queue.

EventNumber


-800 Operation complete[The instrument has completed all selected pending operations in accordance withthe IEEE 488.2, 12.5.2 synchronization protocol]

21.9 :HELPSYSTem:HELP

PH002

The HELP subsystem contains the instrument’s help utilities that are provided to theprogrammer.

HP099b21.9.1 :HEADers? SYSTem:HELP:HEADers?

HP099bThe HEADers? query shall return all SCPI commands and queries and IEEE 488.2 commoncommands and common queries implemented by the instrument. The response shall be a<DEFINITE LENGTH ARBITRARY BLOCK RESPONSE DATA> element, see IEEE488.2 section 8.7.9. The full path for every command and query shall be returned separatedby linefeeds. The syntax of the response is defined as:

HP099bThe <nonzero digit> and sequence of <digit> follow the rules in IEEE 488.2, Section 8.7.9.

HP099bAn <SCPI header> is defined as:

HP099bIt shall contain all the nodes from the root. The <SCPI program mnemonic> contains thenode in standard SCPI format. The shortform shall use uppercase characters while theadditional characters for the longform shall be in lowercase characters. Default nodes shallbe surrounded by square brackets ([]).

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-28 SYSTem:HELP

HP099bThe entire <SCPI header> shall have an indication of the header type, using a <commandquery indication>.

HP099bA node which has a numeric suffix, described in Volume 1, section 6.2.5, is indicated byincluding a <numeric suffix indication>.

HP099bA <numeric suffix indication> is defined as:

where: nothing indicates no suffix is allowed <numeric_list> indicates list of suffixes allowed <digit>(s) indicates this specific suffix is allowed {?:?} indicates range of suffixes is unknown, or

can’t tell if suffix is allowed

HP099bNumbers between the curly braces shall indicate valid values for the numeric suffix. Forexample, {1:4} means the values one through four may be appended to that node. If theinstrument cannot determine the legal values for the numeric suffix, it may use the specialform, {?:?}, to show that a numeric suffix may be allowed even though the range isunknown. The use of a <numeric_list> is especially useful with a large number of suffixes.For headers which accept only a small number of numeric suffixes, specific values arepreferred.

HP099bA <command query indication> is defined as:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:HELP 21-29

HP099bIf the instrument is unable to determine if the header is an event, query only, or acommand/query pair, it shall append /unknown/ to the header. Otherwise, a normalcommand/query pair shall have nothing additional following the path, a query only headershall have ?/qonly/ appended, and a command which is an event with no query form shallhave /nquery/ appended.

HP099bA <common header> is defined as:

HP099bA <common response header> contains only upper case letters.

HP099bHeaders may appear in any order.

HP099bThe response shall not include any macro labels. The *LMC? common query is used toreturn macro labels.

HP099bFor example, an instrument which implemented the required commands listed in Syntax &Style, Volume 1 section 4.2.1, this query, and the required IEEE 488.2 common commandsand queries might return:

#3425:SYSTem:ERRor?/qonly/:SYSTem:HELP:HEADers?/qonly/:SYSTem:VERSion?/qonly/:STATus:OPERation[:EVENt]?/qonly/:STATus:OPERation:CONDition?/qonly/:STATus:OPERation:ENABle:STATus:QUEStionable[:EVENt]?/qonly/:STATus:QUEStionable:CONDition?/qonly/:STATus:QUEStionable:ENABle:STATus:PRESet/nquery/*IDN?/qonly/*RST/nquery/*TST?/qonly/*OPC/nquery/*OPC?/qonly/

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-30 SYSTem:HELP

*WAI/nquery/*CLS/nquery/*ESE*ESR?/qonly/*SRE*STB?/qonly/

HP099b+Edit

*RST shall have no direct effect on the response to this query, but changing the instrumentstate may change the list of valid commands and queries.

PH002

21.9.2 :SYNTax? <command_header>SYSTem:HELP:SYNTax?

TK042The SYNTax? query causes the device to return a string containing the syntax specificationof the command associated with the <command_header>. The <command_header>parameter is a string containing any implemented command or query header that starts fromthe root. Default nodes and suffixes may appear in the <command_header> parameter.

PH002

Numeric suffixes may be explicitly specified in the <command_header>. Only the headerand parameter syntax of the specified <command_header> is returned. If no numeric suffixis specified, default 1 is assumed. In that case, devices that implement a numeric suffix shallshow the suffix 1 as an optional element in their response.

PH002

The part of the returned string that reflects the syntax of the parameter part of the commandis be separated from the header syntax part by one or more ASCII space characters (decimal32). The parameter part shall contain all required and allowed parameters. Parameternotation shall conform to notations of the Command Tables, being used throughoutVolume 2 and specified in chapter 5.1 of Volume 1. Optionality is reflected by placing theoptional items in between square brackets. Optional nodes are reflected in the same way.

PH002, JP Change

The Long Form shall be used to represent mnemonics in the response to the :SYNTax?query. The letter case notation habit, as specified in chapter 5.1 of “Volume 1: Syntax andStyle,” shall be used for mnemonics to differentiate between Long- and Short form.

PH002

Any <command_header> that is not a valid command header being recognized by thedevice, shall cause the device to return a null string (""). E.g. if the <command_header>contains only a part of the header, contains an illegal numeric suffix, etc.

TK042For example, if the command tree wereTK042[:ALPHa<n>]

:BETA [:GAMMa] :DELTa<n> ON|OFF|TRIGger

TK042where the <n> indicates a range of suffix values is accepted for ALPHa and DELTa only.

TK042Then SYSTem:HELP:SYNTax? “:BETA:GAMMA:DELTA” will returnTK042“[ALPHa[1]]:BETA[:GAMMa]:DELTa[1] ON|OFF|TRIGger”

TK042+EditSYNTax? is a query only and therefore does not have an associated *RST value.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:HELP 21-31

21.10 :KEY <numeric_value>SYSTem:KEY

The KEY node is a limited implementation of the naming conventions subsystem describedin “Volume 1: Syntax and Style”. The limitation is that keys can only be referred tonumerically, and the numbers allowed by a particular instrument (key codes) are fixed.

The KEY? query returns the key code for the last key pressed. Instruments may implement aqueue of keys (possibly of length 1) and return a value of -1 to indicate an empty queue. Thequeue is emptied at *RST.

If the KEY command is sent with a parameter, that simulates the pressing of that key. Thekeycode determined by the parameter is entirely device-dependent but must match thecorresponding parameter returned for the query form. The KEY command may or may notput an entry into the KEY? queue.

The queue of keys is cleared by *RST.

21.10.1 :CATalogSYSTem:KEY:CATalog

This query returns a list of the defined keys in the subsystem. The response is a commaseparated list of NR1 elements corresponding to each key that has been defined.

21.10.2 :DEFine <numeric_value>,<block>[,<string>]SYSTem:KEY:DEFine

The DEFine command shall redefine a key on the instrument’s keyboard so that pressing thekey will execute a particular function. The first parameter is the key code for the key to beremapped, and the second parameter contains the command sequence to be executed. Theoptional third parameter is a key label for the redefined key.

The particular keycodes are device-dependent.

The softkey label parameter is optional, but it must be accepted by the implementation. Ifsoftkeys are not implemented, the third parameter should be ignored.

The command sequence is a block containing any sequence of SCPI commands.Implementations have the option of limiting this block to contain a single command. It isdevice-dependent when the block has its syntax checked.

The query form of the command returns a list of all redefined keys in the form:<NR1>,<block>,<string>. If the key is unlabeled, the third parameter shall be an emptystring.

Key definitions are not affected by *RST.

21.10.3 :DELete <numeric_value>SYSTem:KEY:DELete

The DELete command removes the definition of the key referred to by <numeric_value> setby a previous DEFine command. The key may return to its default definition, if any.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-32 SYSTem:KEY

21.11 :KLOCk <Boolean>SYSTem:KLOCk

TK017aThis command locks the local controls of an instrument. This includes any front panel,keyboard, or other local interfaces. The SYSTem:KLOCk setting does not affect the 488.1Remote/Local state, if implemented.

TK017aThis value cannot be reset to OFF, unless SYSTem:SECurity:STATe is OFF.

TK017aIf SYSTem:SECurity:STATe is OFF, the KLOCk value is set to OFF at *RST. IfSYSTem:SECurity:STATe is ON, *RST has no effect.

21.12 :LANGuage <string>SYSTem:LANGuage

The receipt of this command shall cause the instrument to perform a language switch toanother language. The contents of the string are device dependent, however, the followingcontents are suggested:

COMPatibility — The language is a backwards compatible set for the product line.

CIIL — Selects the CIIL language of the instrument.

All devices which implement alternate languages shall also implement this command. Aninstrument which is currently executing SCPI will not leave SCPI to enter an alternatelanguage under any other conditions, except possibly power-on. There is no querycorresponding to this command.

21.13 :LFRequency<numeric_value>SYSTem:LFRequency

HP053

The numeric value is used as the reference frequency. If the instrument is capable of usingonly discrete reference values (e.g. 50 or 60 Hz), it will use the specified value to select thenearest valid setting.

HP053

*RST does not affect this setting.

21.13.1 :AUTO <Boolean> | ONCESYSTem:LFRequency:AUTO

HP053

If AUTO ONCE is specified, the instrument will measure the line frequency internally anduse the result (or the nearest valid setting, if necessary) as its reference. After themeasurement is complete, this setting reverts to OFF. If AUTO ON is specified, theinstrument will continuously monitor the line frequency (through repetitive measurements,phase locking, etc.).

HP053

Behavior at power-on is device-dependent; an instrument capable of measuring the linefrequency may choose to do so when power is applied. Other options are (1) to preserve thevalue last specified with LFRequency, (2) to choose a default setting, or (3) to use hardcontrols to determine the setting.

HP053

*RST does not affect this setting.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:KLOCk 21-33

21.14 :LOCKSYSTem:LOCK

This subsystem controls the availability of an instrument. It allows the communicationchannel that these SCPI commands arrived on (session) to attempt to attain exclusive use ofthis instrument by attaining a lock.

The behavior of the device when receiving SCPI commands from a session that does nothave the lock is device dependent.

On *RST the ownership of the lock is device dependent.

21.14.1 :OWNer?:SYSTem:LOCK:OWNer?

This query returns what session currently has the lock on this device. If no session has a lockthen “NONE” shall be returned.

21.14.2 :RELease:SYSTem:LOCK:RELease

This event releases the lock if owned by this session. If this session does not have the lock,this command has no effect. This command has no query form.

21.14.3 :REQuest?:SYSTem:LOCK:REQuest?

This event shall only be implemented as a query. It attempts to attain the lock on this deviceand returns 1 if successful and 0 if it fails.

REMoteLOCK=ON

DEVice=REMote

NONELOCK=OFF

DEVice=NONE

LOCalLOCK=ON

DEVice=LOCal

:SYSTem:LOCK:STATe OFF

:SYSTem:LOCK:STATe ON

LOCAL INTERFACE (O

VERRIDE)

Leave in LOCKed state, s

et DEVice=LOCal,

generate event

LOCAL INTERFACE

(equivalent to host's issuing

:SYSTem:LOCK:STATe ON)

LOCAL INTERFACE

(equivalent to host's issuing

:SYSTem:LOCK:STATe OFF)

LOCAL INTERFACE (E

ND OVERRIDE)

Leave in LOCKed state, s

et DEVice=REMote,

generate event

Figure 21.2 System Lock Format

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-34 SYSTem:LOCK

TK02421.15 :PASSwordSYSTem:PASSword

TK024This subsystem provides for the enabling, disabling, and changing of passwords to controlaccess to selected SCPI commands and queries. The instrument’s documentation shallindicate which commands are under the control of SYSTem:PASSword.

TK024Password protection shall be locally defeatable. The device shall have a local means to:

TK024reset the password to the default value, “DEFAULT”.

enable all protected commands.

TK024The means of protection for this local resetting and enabling is entirely device dependent.

TK024The device shall report error -203, (command protected), if a password-protected commandis received that is currently disabled.

TK024Neither the current password nor command protection state shall be affected by *RST.

TK02421.15.1 :CDISable <password>SYSTem:PASSword:CDISable

TK024Sending :CDISable (Command DISable) disables protected commands. The <password>data is of type string and the password is case sensitive. There is no query form.

TK024Sending an invalid password generates error -221, (settings conflict).

TK02421.15.2 [:CENable] <password>SYSTem:PASSword:CENable

TK024Sending :CENable (Command ENable) enables protected commands to function. The<password> data is of type string and the password is case sensitive. There is no query form.

TK024Sending an invalid password generates error -221, (settings conflict).

TK02421.15.2.1 :STATe?SYSTem:PASSword:CENable:STATe?

TK024STATe? returns a 0 if password protected commands are disabled and a 1 if they areenabled. There is no command form.

TK02421.15.3 :NEW <current password>,<new password>SYSTem:PASSword:NEW

TK024This command changes the password from the default or current value to the new value.Both parameters are strings. The <current password> must be correct for the command toexecute. Password strings are case sensitive. There is no query form.

TK024Sending an invalid current password generates error -221, (settings conflict).

21.16 :PRESetSYSTem:PRESet

Sets the device to the same state as the front-panel reset key. This command is similar to the*RST command, but differs in that it duplicates the action of the front panel reset key.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:PASSword 21-35

Normally this state will be optimized for front panel operation of the device instead of busoperation.

Other PRESet states may be accessed with this instruction by using a numeric suffix. Forinstance, PRESet2 could provide a high speed configuration.

The state of the device after PRESet is not defined by SCPI. There is no query correspondingto this command.

21.17 :SECuritySYSTem:SECurity

TK025Controls the security of the instrument.

TK02521.17.1 :IMMediateSYSTem:SECurity:IMMediate

TK025This command is an event which immediately destroys all measurement data and instrumentsettings. Current settings are initialized to their *RST values. All macros, user variables, and*SAV/*RCL registers are initialized. Critical calibration constants are retained.

TK025This command can be under control of the SYSTem:PASSword subsystem. The device shallreport error -203, (command protected), if SECurity:IMMediate is received while passwordprotected.

TK025This commmand is an event, and therefore has no *RST value associated with it.

21.17.2 [:STATe] <Boolean>SYSTem:SECurity:STATe

TK025STATe controls the security mode of the instrument. For example, when in secure mode, anydisplay annunciators which have been disabled cannot be reenabled without destroyingcertain stored information.

The value is not affected by *RST or *RCL.

When this value changes from ON to OFF, everything except possibly some CALibrationdata must be initialized or destroyed. For example, the following shall be initialized:

Instrument state (perform *RST).

All macros (perform *PMC).

All user variables.

All state registers (perform *SAV into all registers after *RST).

21.18 :SET <block data>SYSTem:SET

Sets the instrument to the complete or partial state determined by the contents of theparameter. The form and contents of the block data is device-dependent.

This command shall be required for instruments that return a block of binary settings inresponse to the *LRN? query.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-36 SYSTem:SECurity

PH004

Instruments that implement the *LRN? query and return a block of binary settings asresponse to *LRN?, shall implement also the SYSTem:SET command. In this case theresponse format of *LRN? shall contain SYST:SET <block data>.

PH004

Note that IEEE 488.2 requires the response to *LRN? to be a legal program message. Sincethe SYSTem:SET command is the SCPI command which programs the instrument settingsby binary block data, this must be the response to the *LRN? query when it returns this dataformat.

PH004

The implementation of the SYSTem:SET command is optional if the *LRN? query responseare the SCPI commands that are normally used for programming the instruments.

PH004

The query form of this command will return a definite block data element which contains theinstrument’s current state. The SET command may be implemented without the associatedquery.

PH004

21.19 :TIME <hour>,<minute>,<second>SYSTem:TIME

Any instrument which has an internal clock shall implement this command to set the clock.The three parameters for this command are:

<hour>: Must be <numeric_value>. It is always rounded to the nearest integer. Itsrange is 0 to 23 inclusive. All instruments implementing the TIME functionshall report and accept hour information in 24 hour format.

<minute>: Must be <numeric_value>. It is always rounded to the nearest integer. Itsrange is 0 to 59 inclusive.

<second>: Must be <numeric_value>. It is rounded to the resolution of the clock. Itsrange is 0 to 60. 60 is allowed since rounding may cause a number greaterthan 59.5 to be rounded to 60. When this element is rounded to 60 it shall beset to 0 and the minute value incremented. Any other carries shall be rippledthrough the date.

The query response message shall consist of three fields separated by commas:<hour>,<minute>,<second>

The three fields will contain the following information:

<hour>: NR1 format ranging from 0 to 23.

<minute>: NR1 format ranging from 0 to 59.

<second>: NR1 or NR2 format. If the resolution of the clock is no better than seconds,an NR1 format shall be used. If the resolution is better than seconds, an NR2format shall be used. Range is 0 to 59.999999...

This setting shall not be affected by a *RST command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:TIME 21-37

21.19.1 :TIMerSYSTem:TIME:TIMer

This subsystem contains commands that control an internal timer/counter.

In some instruments the value of this timer may be used to timestamp internal readings.

21.19.1.1 :COUNt <numeric_value>SYSTem:TIME:TIMer:COUNt

COUNt sets or queries the current value of the timer.

Sending this command shall not affect TIMer:STATe. When the TIMer:STATe is ON thecount will increase.

This command sets or queries the current count for the timer in seconds.

The default value of this parameter is 0.

At *RST this value be set to 0.

21.19.1.2 [:STATe] <Boolean>SYSTem:TIME:TIMer:STATe

This node sets or queries the TIMer:STATe. If the STATe is ON the TIMer is running.

At *RST the TIMer:STATe is OFF

21.20 :TZONe <hour> [,<minute>]SYSTem:TZONe

An instrument which has an internal clock and can keep track of the time zone shallimplement this command to set the time zone.

The fields have the following meanings:

<hour>: Must be a <numeric_value>. The value shall be rounded to the nearestinteger. Range -12 to +12.

<minute>: Must be a <numeric_value>. The value shall be rounded to the nearestinteger. Range -59 to 59.

When each field is subtracted from the value of the TIME command, the result is the correctuniversal coordinated time (also known as UCT, Zulu, Greenwich Mean Time).

The default value of <minute> is zero.

This shall not be changed by the receipt of a *RST.

21.21 :VERSion?SYSTem:VERSion?

This query returns an <NR2> formatted numeric value corresponding to the SCPI versionnumber for which the instrument complies. The response shall have the form YYYY.V wherethe Ys represent the year-version (i.e. 1990) and the V represents an approved revisionnumber for that year. If no approved revisions are claimed, then this extension shall be 0.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-38 SYSTem:TZONe

An instrument known to claim SCPI compatibility that does not respond to the VERSionquery shall be assumed to conform to version 1990.0.

This query shall be implemented by all instruments claiming conformance to a SCPI versiongreater than 1990.0.

VERSion? is a query only and therefore does not have an associated *RST state. 1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


SYSTem:VERSion? 21-39

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


21-40 SYSTem:VERSion?

22 TEST SubsystemThe TEST subsystem provides a section to extend standard instrument self-test proceduresbeyond the IEEE 488.2 *TST command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TEST Subsystem 22-1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


22-2 TEST Subsystem

23 TRACe | DATATWIR01p21

A TRACe or a DATA area is a named entity stored in instrument memory. TRACe | DATAareas may also be used to store other types of data, such as constant arrays for use in tracearithmetic or corrections, or displayed waveforms. Alternatively, TRACe | DATA areas maybe used for equivalent scalar (single point) purposes.

TWIR01p21

Certain TRACe format and capabilities are the focus of other emerging standards. Toprevent diluting the effect of SCPI or any other standards related to the manipulation ofTRACes, SCPI has left such capability undefined at this time with the view to adopting anindustry standard when one becomes available. The undefined capabilities include thefollowing:

Trace math operations for specifying arithmetic relationships between traces,including the use of user-defined constants and functions.

Trace activation and routing for specifying the destination for measurementresults.

KEYWORD PARAMETER FORM NOTESTRACe|DATA 1991 TWIR01p21

:CATalog? [query only] :COPY <trace_name>, [event; no query] 1991,2

(<trace_name>|<data_handle>) TWIR01p21

DIF01 [:DATA] <trace_name>,(<block>|<dif_expression>| 1993 (<numeric_value>{,<numeric_value>})) TWIR01p21

:LINE <trace_name>,<numeric_value>,<numeric_value>,<numeric_value>,<numeric_value> 1992 WV001

TK032a :PREamble? <trace_name> [query only] 1994 :VALue <trace_name>,<numeric_value>,<numeric_value> 1992 WV001

:DEFine <trace_name>[,(<numeric_value>|<trace_name>)]

:DELete [:NAME] <trace_name> [event; no query] :ALL [event; no query] :FEED <trace_name>,(<data_handle>|NONE) 1991 TWIR01p21

:CONTrol <trace_name>,(ALWays|OCONdition|NEXT|NEVer) 1991 TWIR01p21

:OCONdition <trace_name>,<condition_expr> 1991 TWIR01p21

:FREE? [query only] :POINts <trace_name>[,<numeric_value>] 1993 PH075 :AUTO <trace_name>,(<Boolean>|ONCE) [event; no query]

Many TRACe subsystem commands are of the following general form:TRACe:COMMand <destination trace_name>,<source trace data>

The <trace_name> is <CHARACTER PROGRAM DATA> (IEEE 488.2, section 7.7.1).There is no difference between uppercase and lowercase letters used in <trace_name>. There

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRACe | DATA 23-1

is no short form abbreviation for <trace_name>. The destination trace is always the firstparameter in the list. The <source trace data> parameter may be an existing <trace_name>,or a block, or expression which is evaluated as trace data.

*RST has no effect on this subsystem.

23.1 :CATalog?TRACe:CATalog?

The CATalog? query returns a comma-separated list of strings which contains the names ofall traces. If there are no <trace_name> defined, a single empty string is returned. Someinstruments may have one or more intrinsic, permanent <trace_name>. These traces must belisted along with any user-named traces.

23.2 :COPY <trace_name>, ( <trace_name> | <data_handle> )TRACe:COPY

TWIR01p21

The COPY command set the data values in the destination trace, from internal data stores inthe instrument. There is no query form of this command, it is an event only.

If the data source is a <trace name>, the data is copied into the destination trace. Forexample, COPY REF,TRACE1 will copy the data currently in TRACE1 into the tracenamed REF.

If the data source is a <data_handle>, the data shall be copied directly from the data poolspecified. For example, COPY REF, “CALCulate1” will copy the data emitted by theCALCulate1 block. When the data is copied depends on the type of memory associated withthe data flow. If the memory is transient, as described in section 2.7.5, then the data shall becopied when data becomes available, for example when a new acquistion takes place. If thememory is static the data shall be copied immediately, as there is memory that always hassome value in it associated with the specified <data_handle>, typically the result from anearlier acquistion.

23.3 [:DATA] <trace_name>,(<block>|<dif_expression>| (<numeric_value>{,<numeric_value>})) DIF01TRACe:DATA

TWIR01p21

The DATA command sets the data values in the destination trace, from information providedby the controller. If the data source is a block of data, then the block is directly loaded intothe destination trace. In this case the data source is block data, the data format is determinedby the FORMat Subsystem. Note that the data source may also be a Data Interchange Formatexpression.

DIF01If the data source is a single <numeric_value>, every element of the destination trace is set tothe constant value represented by the evaluation of <numeric value>. For example, DATAREF,0.22361 sets all points in the REF trace to 0.22361. If a <numeric_value> is sent foreach of the points in the allocated <trace_name>, then the <numeric_value>s are mappedinto the <trace_name>. If an insufficient number of <numeric_value>s are sent, that is lessthan the allocated points, then the result is device dependent. If too many <numeric_value>sare sent the device shall generate error -223 (too much data), and the result shall be devicedependent.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


23-2 TRACe | DATA:CATalog?

The DATA? query <trace name> returns the data values for <trace name>, according to theformat determined by commands in the FORMat subsystem.

DIF01Note: All parentheses in the syntax for this command are used for grouping purposes only.

23.3.1 :LINE <trace_name>,<numeric_value>,<numeric_value>, <numeric_value>,<numeric_value>TRACe:DATA:LINE

WV001

The LINE command is an event which defines a line segment (a series of points) within theboundaries of the trace whose name is specified by <trace_name>. The first<numeric_value> determines the index of the starting point in the trace. The second<numeric_value> is the value of the trace at the starting point. The third and fourth<numeric_value> parameters set the end of the line segment index and value. A line segmentis drawn connecting the start point and end point, inclusive. This command has no queryform. The index of the first point in a trace is 1.

23.3.2 :PREamble? <trace_name>TRACe:DATA:PREamble?

TK032aPREamble? returns the preamble information supporting the DATA(CURVe(VALues)) butomits the following data:

TK032aDIF blocks of waveform, measurement, and delta.


TK032aThe DIF difid block must contain the keyword SCOPe with the parameter of PREamble.

TK032aWhile the PREamble? query is designed to efficiently transmit data relating directly to thecurve, the various notes and identification parameters may be sent if absolutely required.

TK032aThe <trace_name> parameter functions the same as it does in TRACe:DATA?.

23.3.3 :VALue <trace_name>,<numeric_value>,<numeric_value>TRACe:DATA:VALue

WV001

The VALue command sets or queries the value of an individual point in a trace. The first<numeric_value> is the index of the addressed point in the trace defined by <trace_name>.The second <numeric_value> is the value to be set for the point. The index of the first pointin a trace is 1.

The VALue? <trace_name>,<numeric_value> query returns the data value of the trace<trace_name> at the <numeric_value> indexed point.

23.4 :DEFine <trace_name>[,(<numeric_value>|<trace_name>)] TRACe:DEFine

The DEFine command allocates and initializes a new trace. The first parameter is<CHARACTER DATA>, and it specifies the new <trace_name>. If the second parameter isa <numeric_value>, a new trace is allocated with the specified number of data elements. Thetrace shall be initialized to instrument-specified default values. If the second parameter is thename of an existing trace, the new trace becomes a copy of the existing trace in all respects,including size and contents. The data in the existing trace is not affected. When the second

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRACe | DATA:DEFine 23-3

parameter is omitted, the new trace shall have an instrument-specified default size and initialvalue.

Limits on the number of named traces are instrument-specific.

23.5 :DELeteTRACe:DELete

The DELete commands allow the user to dissociate <trace_name> from trace memory.Instrument intrinsic <trace_name> cannot be deleted. There is no query form for the DELetecommands.

23.5.1 [:NAME] <trace_name>TRACe:DELete:NAME

The NAME command dissociates a user-created <trace_name> from its trace memory. TheNAME node is optional in a program message. That is, an instrument is required to acceptboth forms of this command. If the instrument supports dynamic trace memory allocation,then the memory allocated for <trace_name> is freed.

23.5.2 :ALLTRACe:DELete:ALL

The ALL command dissociates all user-created <trace_name> from their trace memoryunits. If the instrument supports dynamic trace memory allocation, then all memory allocatedfor user-created traces is freed.

23.6 :FEED <trace_name>, ( <data_handle> | NONE )TRACe:FEED

HP070Sets or queries which data flow is fed into the specified TRACe|DATA memory. The firstparameter specifies the name of the TRACe|DATA memory. The second parameter (usedonly in the command form) selects the data flow to be fed into the memory.

HP070A <data_handle> is the name of a point in the data flow described by the Instrument Model(found at the beginning of this volume). By setting the <data_handle> to a null string (“”),no data shall be fed into the specified TRACe|DATA memory. When a TRACe|DATAmemory is created with the DEFine command, the FEED <data_handle> for that memoryshall be set to null (“”).

HP070The query form of this command requires that a valid <trace_name> shall be specified. If theTRACe|DATA memory specified in <trace_name> does not exist then an error -224, “Illegalparameter value” shall be generated. The query shall return a string that represents the<data_handle> selected. If no feed is selected, then the query shall return a null string (“”).

At *RST, FEED shall be set to NONE.

23.6.1 :CONTrol <trace_name>, ALWays | OCONdition | NEXT | NEVerTRACe:FEED:CONTrol

TWIR01p22

HP070Sets or queries how often the specified TRACe | DATA area accepts new data. This controlhas no effect if the FEED <data_handle> is set to null (“”). The first parameter specifies theTRACe | DATA area, the second parameter selects how often new data shall be accepted.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


23-4 TRACe | DATA:DELete

By selecting ALWays, whenever new data is available it shall be fed into the specifiedTRACe | DATA area. On CONdition defines that data shall be gated by the OCONditioncommand. NEXT is a one-shot feed, it always waits for new data, such as an new acquistion,and ignores any existing data. Once NEXT has completed its feed of data, CONTrol revertsto NEVer. NEVer shall cause no data to be fed.

At *RST, CONTrol is set to a device dependent value.

23.6.2 :OCONdition <trace_name>, <condition_expr>TRACe:FEED:OCONdition

TWIR01p23

The On CONdition command sets or queries the condition used to gate data flow into thespecified TRACe | DATA area. The first parameter specifies the TRACe | DATA area. Thesecond parameter is EXPRESSION PROGRAM DATA, which defines the condition, whichwhen evaluated to be True shall allow data to be fed through. The production<condition_expr> is of the general form:

‘(’ <operand_str> <equiv_op> <operand_str> ‘)’ or ‘(’ <event_handle> ‘)’

The productions <operand_str> and <equiv_op>, the operand string and the equivalenceoperator respectively, shall be defined later.

23.7 :FREE?TRACe:FREE?

The FREE? query returns the amount of user memory space available for traces, in thefollowing form:

<bytes available>, <bytes in use>

where the returned data for both shall be in <NR1> format.

23.8 :POINts <trace_name>[,<numeric_value>]TRACe:POINts

The POINts command sets the number of measurement data points available in the specifiedtrace memory. The first parameter specifies the name of the trace to resize. The optionalsecond parameter specifies the number of data points which the <trace_name> mustaccommodate. If this parameter is omitted, an instrument specific default value will be used.If more than one <numeric_value> is associated with each trace data point (as would be thecase with a trace consisting of real and imaginary pairs), then the second parameter specifiesthe number of N-tuples in the trace.

The query POINts? <trace_name> returns the number of measurement data points in thespecified trace. Note that each data point may have several numeric data items associatedwith it.

23.8.1 :AUTO <trace_name>,(<Boolean>|ONCE)TRACe:POINts:AUTO

The AUTO command turns trace autosizing ON/OFF. When it is enabled, <trace_name>will automatically be resize as necessary to accommodate any new data block assigned to it.In this mode of operation, changes in measurement setup will not require adjustments to the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRACe | DATA:FREE? 23-5

size of defined traces. If POINts:AUTO <trace_name>, ONCE is specified, and the tracesizing occurs once (on the next measurement). Limits on trace sizes are instrument-specific.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


23-6 TRACe | DATA:POINts

24 TRIGger SubsystemThe trigger subsystem is used to synchronize device action(s) with events. A device actionmight be the acquisition of a measurement or the application of a stimulus. The triggersubsystem consists of the expanded capability model which is capable of describing verycomplex device trigger systems. It also makes provision, through the ARM-TRIGger model,for simple descriptions of less complicated trigger systems. These two models are consistentand compatible with each other. The ARM-TRIGger model represents a subset of thecapability available in the expanded capability model.

ACQ01BThe figures in this section that represent the trigger model adhere to the followingnomenclature. A box identifies a state of a transition diagram and is referred to as a layer. Asequence is a set of vertically connected layers. A solid line defines flow of control betweenstates. A dashed line defines how an event is propagated to other parts of the trigger modeland the instrument. Events generated by control flowing from one part of the trigger modelto another part are called “sequence events.”

24.1 ARM-TRIGger ModelThe ARM-TRIGger model represents a level of capability that is often found in a device andis shown in figure 24-1. The ARM-TRIGger model shows two independent levels of eventdetection, one in each of the ARM and the TRIGger layers. For a given device the model

Figure 24-1 ARM-TRIGger Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem ARM-TRIGger Model 24-1

may be simplified further by the omission of the ARM layer and any inappropriatecommands for that device.

24.2 Model LayersThe following figures detail each of the various types of layers that may exist in a sequence.Each layer is shown with a dotted line, which is used to divide the upward and downwardtraverses through the layer. The different traverses are referenced in describing the operationof each layer.

24.2.1 IDLE StateOn receipt of either *RST or ABORt, the trigger subsystem shall enter the IDLE state.Receiving the IEEE 488.2 dcas message may also cause a transition to IDLE. Devices whichcannot process commands when not in IDLE must enter IDLE when dcas is received to meetthe IEEE 488.2 requirements for device clear. The downward traverse from IDLE state,“trigger system initiated,” is affected by either the INITiate[:IMMediate] command or bysetting INITiate:CONTinuous to ON.

KI005If the INITiate commands are implemented as overlapped, exiting the IDLE state shall causethe pending operation flag (as defined by IEEE 488.2) associated with the initiated action tobe set true. Entering the IDLE state shall cause the pending operation flag to be set false.

24.2.2 InitiatedACQ01BOnce the trigger sequence is initiated from the IDLE state, control passes through the

INITiated state, shown in Fig 24-3, immediately making the downward traverse to thehighest ARM:LAYer state. The upward traverse is dependent on the setting of CONTinuous.If CONTinuous is set to OFF then the upward transition to the IDLE state shall be made.Otherwise, the downward traverse to the highest ARM:LAYer state shall be made, so thatthe trigger sequence remains initiated. If the sequence does not contain any ARM layers, thedownward transition goes to a TRIGger state.

Figure 24-2 IDLE State

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-2 TRIGger Subsystem Model Layers

ACQ01B,KI005

The INITiated state is necessary to avoid having the pending operation flag change stateevery time the entire trigger sequence is completed when CONTinuous is ON. On exit fromthe INITiated state, in both directions, a “sequence event” is generated. These events may beused to start actions in the trigger subsystem or actions in other parts of the instrument.Fig 24-3 shows the names of these events. An instrument shall implement the initiated stateeven if it implements the INITiate commands as sequential.

24.2.3 Event Detection LayerThe ARM and TRIGger layers are both event detection layers with the TRIGger layer beingsubservient to the ARM layer. Each layer provides one level of event detection.

The downward traverse through an event detection layer depends on the sourced event beingdetected the specified number of times. Typically, the first event detected after entering theevent detection layer is all that is required to proceed. However, a particular number ofoccurrences of the same event may be specified using ECOunt; for example, wait for thetenth positive edge of a signal. The downward traverse is also subject to a time delay if one isspecified.

Two commands override the normal process of the downward traverse. The layer namefollowed by :IMMediate causes the event detection and the subsequent delay to be bypassed.The layer name followed by :SIGNal causes the device to proceed as though a single eventhad occurred.

ACQ01BOn exit from the ARM or TRIGger state, in either direction, a “sequence event” is generated.These events may be used to start actions in the trigger subsystem or in other parts of theinstrument. An action may not be associated with every “sequence event.”

Figure 24-3 INITiated State

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem Model Layers 24-3

ACQ01BThe upward traverse is dependent upon the event detector being satisfied and the value ofCOUNt for the given layer. The event detector in the upward traverse is used to detect whenan action started by the exit from this layer on the downward traverse has completed. Thisevent detector has no commands associated with it, and it is only included in the model toprevent the trigger system from looping around until the “device action” associated with thegiven layer has completed.

When COUNt is greater than one, all of the subservient layers are cycled repeatedly COUNttimes. For example, to make five measurements, each qualified by the same combination ofARM and TRIGger events, the COUNt in the ARM layer should be set to 5. Each time theARM layer is entered from below, the flow is redirected to follow the downward traverse.After the fifth cycle, when COUNt is satisfied, the upward traverse to the initiated state ismade.

24.3 Sequence Event UseACQ01BIn the ARM-TRIGger model shown in Fig 24-1, the “sequence event” generated by the

TRIGger layer is shown starting a “device action.” The “device action” is dependent on thesettings of the SENSe or SOURce subsystems, for example by the FUNCtion selected. Thesettings of the SENSe and SOURce subsystems are in general device dependent and

Figure 24-4 Event Detection Layer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-4 TRIGger Subsystem Sequence Event Use

therefore, the “device action” tied to a “sequence event” is also device dependent. Forexample, in one instrument the event may be used to generate a signal and in anotherinstrument it may be used to make a measurement.

ACQ01BFurther, the completion of a device action itself is device dependent. For example, the deviceaction could be defined as executing a complete sweep, or it could be defined as initiating asweep. These device actions would signal their completion at different times andconsequently, would permit the upward transistion through the layer at different times.Where an instrument permits control of the characteristics of a device action, the commandsfor that control shall appear in the subsystem employing the event. In the earlier example, acommand to differentiate between initiating a sweep and executing a complete sweep wouldexist with the commands that control the other characteristics of the sweep.

ACQ01BThe name of a “sequence event” reflects where it was generated. Its form is

“(INITiate|TRIGger)([:SEQuence[1]]|:SEQuence<n>|:<sequence_name>)([:DOWN]|:UP)”or “ARM([:SEQuence[1]]|:SEQuence<n>|:<sequence_name>)([:LAYer[1]]|:LAYer<n>)([:DOWN]|:UP)”

Note: Parentheses used here are for grouping and not literals. The syntax of a sequence eventis the same as the syntax of the instrument-control header.

ACQ01BIt includes the direction of traverse, the layer, and the sequence. The use of defaults,however, allows some short aliases. “ARM” is equivalent to“ARM:SEQuence1:LAYer1:DOWN”.

24.4 Expanded Capability Trigger ModelACQ01BFig 24-5 is an example of an expanded capability trigger model. An instrument could

implement a more extensive or simpler trigger system. The purpose of the figure is toillustrate concepts. A picture of all possible configurations is not possible.

ACQ01BThe expanded capability trigger model expands upon the ARM-TRIGger model to meetmore complex needs through additional “Event Detection Layers” as shown in Fig 24-4.These additional layers give extra levels of event detection which provide more qualificationto a particular action, or establish more “sequence events” to synchronize many actionswithin an instrument. Any number of “Event Detection Layers” may be included asadditional ARM layers, as shown in Fig 24-5. A single trigger layer still exists in theexpanded capability model.

ACQ01BMultiple sequences may exist in the expanded capability model to describe concurrentlyoperating trigger conditions, also shown in Fig 24-5. Any number of sequences arepermitted. Sequences may have the same or a different number of layers. Some of thesequences may have aliases. These aliases are used where the sequence is performing astandard trigger operation. Multiple sequences may be synchronized by linking “sequenceevents” of one sequence to the event detector of another sequence. Some of the standardsequences interact in a pre-defined manner which saves creating unnecessary links andcomplicating the model for the standard sequences.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem Expanded Capability Trigger Model 24-5

ACQ01BAn IDLE state is shown with each sequence. The commands *RST and ABORt place allsequences immediately in their IDLE states. A device clear shall put the sequences to theirIDLE states if the device is unable to parse another command without aborting the triggersubsystem (non-overlapped operation). Not aborting the initiated sequences is preferable ifthe parser can be cleared by a device clear so it can process a command.

24.4.1 LAYer NomenclatureACQ01BEach state in the trigger subsystem is made unique by its position determined by its row and

column. In the trigger subsystem each column is called a SEQuence. The rows are labelled ina different manner to maintain compatibility with the ARM-TRIGger model. The lowest rowis called the TRIGger layer. The next one up in called the first ARM layer. The third layerfrom the bottom is called the second ARM layer.

ACQ01BThe <layer_name> for a particular state is determined from its SEQuence, whether it is anARM or a TRIGger layer, and finally the LAYer number if it is an ARM layer. In Figure24-5, the layer in the lower left most position is TRIGger[:SEQuence[1]]. Because it is inSEQuence1, SEQuence is optional and may be omitted . For this layer, TRIGger issufficient, and is the name used in the ARM-TRIGger model. SEQuence[1] also has the aliasSTARt. This layer’s name is also TRIGger:STARt.

ACQ01BThe SEQuence number increases from left to right, and other SEQuences may have aliasesas well. The layer to the right of TRIGger:SEQuence1 is TRIGger:SEQuence2, which mayalso have the sequence alias TRIGger:STOP. The layer above TRIGger:STARt isARM[:SEQuence[1]][:LAYer[1]], which may be abbreviated to just ARM as LAYer1, as

Figure 24-5 Expanded Capability Trigger Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-6 TRIGger Subsystem Expanded Capability Trigger Model

well as SEQuence1, is the default. The next layer up is ARM[:SEQuence[1]]:LAYer2. TheLAYer number increases from the lowest ARM layer to the top.

ACQ01BThe “sequence event” names reflects the <layer_name> and whether it occurred on the up ordownward traverse. Thus, the event used in the ARM-TRIGger model to start the “deviceaction” is TRIGger[:SEQuence[1]][:DOWN]. The events related to the INITiated state areINITiated[:DOWN] and INITiated:UP.

24.4.2 Standard SEQuencesACQ01BSCPI describes the behavior of SEQuences which have specific names. An instrument is not

required to implement any of these sequences, but any sequence given one of these namesshall behave as described.

ACQ01BSTARt The STARt sequence exists to provide pre-qualification to a “device action.”This sequence shall leave IDLE when an INITiate:IMMediate:ALL orINITiate:CONTinuous:ALL ON is given. If the STARt is implemented thenit shall exist as an alias to SEQuence[1].

ACQ01BSTOP The STOP sequence allows the user to force the currently initiatedsequences to IDLE on a particular event or series of events. All SEQuencesshall go to IDLE upon “INITiated:STOP:UP”.

ACQ01BThe STOP sequence shall not leave IDLE when an INITiate:IMMediate:ALL orINITiate:CONTinuous:ALL ON is given, but shall leave IDLE upon“INITiate:STARt:DOWN”. This means that STOP is subservient to STARt in the way theSTOP sequence leaves IDLE. All sequences, however, are subservient to STOP because thesequence event from STOP affects all other sequences.

ACQ01BFor those instruments that implement STARt as an alias for SEQuence[1], or implementSTARt as an alias for SEQuence[1] and STOP as an alias for SEQuence2, the ARM andTRIGger SEQuence:DEFine command and query are not required. Those instruments thatemploy a different mapping, whether the mapping is fixed or user definable, or use otheraliases shall implement the DEFine command and query for all sequences that exist.

24.4.3 Subservient SequencesACQ01BWhen an event from one sequence controls the initiation of another sequence, the second

sequence is subservient to the first. The “device action” of a sequence initiates anothersequence.

ACQ01BAn instrument may implement any number of sequences depending on its needs andcapabilities. The names for the sequences should reflect the application of an instrument.Naming sequences requires implementing the SEQuence:DEFine command.

HP097Each subservient sequence has IDLE and INITiated states like other sequences. TheINITitated state of a subservient sequence does not, however, check the setting ofINITiate:CONTinuous. It merely exits out the top. This state is included so the event,INITiate:SEQuence:UP, is available for all sequences. The IDLE state of a subservientsequence does not check either the setting of INITiate:CONTinuous or for the arrival of

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



INITiate[:IMMediate]. It does, however, check for an event from a connected sequence asshown in Figure 24-6.

ACQ01BFig 24-6 illustrates how several sequences could be organized in a subservient manner. Anactual instrument would probably have more or fewer than four. It might also use differentsequence names for the same device actions being controlled.

ACQ01BVECTor In this example, the VECTor sequence is used to control the pacing of wholevectors such as when generating or acquiring a waveform. Multiple VECTorsequences could exist, each distinguished by a numeric suffix. SeveralVECTor sequences would be used for multiple nested sweeps to generate asurface. For example, sweeping the power level at each point in a frequencysweep. The controls of the VECTor sequence often are coupled to either theSENSe:SWEep or SOURce:SWEep subsystems. Changing SWEep:DWElland SWEep:TIMe might change TIMer and DELay values.

ACQ01BSVECtor This Sub VECtor sequence is used to control the pacing of collections ofsamples used to create a VECTor. Sub VECtors are useful in acquistioninstruments where whole vectors are averaged. The settings in such a casewould be coupled to the SENSe:AVERage subsystem.

ACQ01BSAMPle The SAMPle sequence is used to control the pacing of each sample. ASAMPle is a single point in the SVECtor.

Figure 24-6 Subservient Sequences

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



ACQ01BSSAMple The Sub SAMple sequence is used to control the pacing of steps needed tocreate a sample. Sub SAMple is used where a SAMPle point is composed ofmore than one acquistion on generation point.

ACQ01BSSAMple is subservient to SAMPle; SSAMple exits IDLE upon TRIGger:SAMPle:DOWN.The upward event detector in TRIGger:SAMPle is linked to INITiated:SSAMple:UP.Similarly, SAMPle is subservient to SVECtor and SVECtor is subservient to VECTor.Further, VECTor is subservient to VECTor2. This relationship is shown is Fig 24-6. Thenames and number of subservient sequences may vary between instruments, but the structureis the same.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



◆◆

The keywords ABORt, ARM, INITiate, and TRIGger are at the root level in the commandhierarchy. They are grouped here because of their close functional relationships.

◆◆

TEK007

KEYWORD PARAMETER FORM NOTESABORt [no query] 1991ARM 1991 TEK007

ACQ01B [:SEQuence] 1994ACQ01B :DEFine <sequence_name> 1994TK028A :MGRules <Boolean> 1994

[:LAYer] :COUNt <numeric_value> :COUPling AC|DC :DELay <numeric_value> :AUTO <Boolean>|ONCE :ECL [no query] :ECOunt <numeric_value> :FILTer 1991 TWOS03

:HPASs 1991 TWOS03

FREQuency <numeric_value> 1991 TWOS03

[:STATe] <Boolean> 1991 TWOS03

[:LPASs] 1991 TWOS03

FREQuency <numeric_value> 1991 TWOS03


:HYSTeresis <numeric_value> [:IMMediate] [no query] :LEVel <numeric_value>

TK036 :AUTO <Boolean> | ONCE 1994 :LINK <event_handle> TWIR01p24

HP093 :PROTocol 1994HP093 :VXI SYNChronous|SSYNchronous|ASYNchronous 1994TK035 :SIGNal [no query]

:SLOPe POSitive|NEGative|EITHer TK040 :SOURce AINTernal|BUS|ECLTrg<n>|EXTernal|HOLD 1995

|IMMediate|INTernal|LINE|LINK|MANual|OUTPut|TIMer|TTLTrg<n>

:TIMer <numeric_value> :TTL [no query]

TK035 :TYPE EDGE | VIDeo 1994TK035 :VIDeo 1994TK035 :FIELd 1994TK035 [:NUMBer] <numeric_value> 1994TK035 :SELect ODD | EVEN | ALL | NUMBer 1994TK035 :FORMat 1994TK035 :LPFRame <numeric_value> 1994TK035TK045 :LINE 1994,5

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK045KEYWORD PARAMETER FORM NOTES [:NUMBer] <numeric_value> 1995

TK045 :SELect ALL | NUMBer 1995TK035 :SSIGnal 1994TK035 [:POLarity] POSitive | NEGative 1994

INITiate 1991 TEK007

:CONTinuous <Boolean> ACQ01B [:ALL] <Boolean> 1994ACQ01B :NAME <sequence_name>,<Boolean> 1994ACQ01B :SEQuence <Boolean> 1994 TEK007

[:IMMediate] [no query] ACQ01B [:ALL] [no query] 1994ACQ01B :NAME <sequence_name> [no query] 1994ACQ01B :SEQuence [no query] 1994

TK038 :POFLag INCLude | EXCLude 1995TRIGger 1991 TEK007

ACQ01B [:SEQuence] 1994TK027 :ATRigger 1994TK027 [:STATe] <Boolean> 1994

:COUNt <numeric_value> :COUPling AC|DC

ACQ01B :DEFine <sequence_name> 1994TK028A :MGRules <Boolean> 1994

:DELay <numeric_value> :AUTO <Boolean>|ONCE :ECL [no query] :ECOunt <numeric_value> :FILTer 1991 TWOS03

:HPASs 1991 TWOS03

:FREQuency <numeric_value> 1991 TWOS03


[:LPASs] 1991 TWOS03

:FREQuency <numeric_value> 1991 TWOS03


TK021 :HOLDoff <numeric_value> 1994 :HYSTeresis <numeric_value> [:IMMediate] [no query] :LEVel <numeric_value>

TK036 :AUTO <Boolean> | ONCE 1994 :LINK <event_handle> TWIR01p2

HP093 :PROTocol 1994HP093 :VXI SYNChronous|SSYNchronous|ASYNchronous 1994

:SIGNal [no query] :SLOPe POSitive|NEGative|EITHer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK040KEYWORD PARAMETER FORM NOTES :SOURce AINTernal|BUS|ECLTrg<n>|EXTernal|HOLD 1995

|IMMediate|INTernal|LINE|LINK|MANual|OUTPut|TIMer|TTLTrg<n>

:TIMer <numeric_value> :TTL [no query]

TK035 :TYPE EDGE | VIDeo 1994TK035 :VIDeo 1994TK035 :FIELd 1994TK035 [:NUMBer] <numeric_value> 1994TK035 :SELect ODD | EVEN | ALL | NUMBer 1994TK035 :FORMat 1994TK035 :LPFRame <numeric_value> 1994TK035TK045 :LINE 1994,5TK045 [:NUMBer] <numeric_value> 1995TK045 :SELect ALL | NUMBer 1995TK035 :SSIGnal 1994TK035 [:POLarity] POSitive | NEGative 1994

24.5 ABORt ABORt

The ABORt command resets the trigger system and places all trigger sequences in the IDLEstate. Any actions related to the trigger system that are in progress, such as a sweep oracquiring a measurement, shall also be aborted as quickly as possible. The ABORt commandshall not be considered complete until all trigger sequences are in the IDLE state. Theexecution of an ABORt command shall set false the pending operation flags that were set bythe initiation of the trigger system.

This command is an event and has no associated *RST condition or query form.

24.6 ARMARM

The purpose of the ARM subsystem is to qualify a single event or a sequence of eventsbefore enabling the TRIGger. The ARM subsystem for a given sequence may be omitted ifTRIGger does not require additional qualification by other events.

24.6.1 [:SEQuence]ARM:SEQuence

ACQ01BSEQuence is used in the expanded capability model to identify a particular sequence oflayers in the trigger system. A <sequence_name>, see 24.4.2, may also be used here.

24.6.1.1 :DEFine <sequence_name>ARM:SEQuence:DEFine

ACQ01BSets or queries the SEQuence alias. This command is required where aliases are employedand they do not correspond to the standard mapping. The numeric suffix on SEQuencecorresponds to the sequence number to which the alias is to be applied.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-12 TRIGger Subsystem ABORt

ACQ01BThis command is an alias to TRIGger:SEQuence:DEFine. Changing the value ofARM:SEQuence:DEFine changes the value of TRIGger:SEQuence:DEFine to the samevalue.

TK028AThe <sequence_name> is character data.

TK028AThe effect of <sequence_name> is modified by DEFine:MGRules as follows:

TK028ARegardless of the state or presence of DEFine:MGRules, there is no differencebetween uppercase and lowercase letters used in <sequence_name>.

TK028AIf the command DEFine:MGRules is absent or set to OFF, thefull<sequence_name> as written is the only form allowed.

For example, if the <sequence_name> were SAMPLE1, then SAMPLE1 is theonly alias accepted.

TK028AIf the command DEFine:MGRules is present and set to ON, the<sequence_name> is interpreted as <program_mnemonic>[<numeric_suffix>]where all the contiguous trailing digits form the <numeric_suffix>. Mnemonicgeneration rules as described in Syntax and Style, Section 6.2.1. shall apply to the<program_mnemonic> and the <numeric suffix>.

For example, if the <sequence_name> were defined as VECTOR or VECTOR1,then VECT, VECT1, VECTOR, and VECTOR1 would all be acceptable aliases.

ACQ01BIf the <sequence_name> is identical to a keyword under ARM or TRIGger subsystem, thedevice shall report execution error -224. For example ARM:SEQuence2:DEFine FILTERwill cause an error. This command shall accept any other valid character program data for<sequence_name>.

ACQ01BThe query returns a string which contains the <sequence_name>, so that a null string canindicate that nothing is defined.

TK028AIf the command DEFine:MGRules is present and set to ON, the returned <sequence_name>will follow the upper/lower case convention described in Syntax and Style, section 5.1,Interpreting Command Tables. An omitted <numeric_suffix> or a <numeric_suffix> of 1will be represented as [1].

TK028AFor example, if <sequence_name> is VECTOR1 then the response is “VECTor[1]”; if it isDELAYED2, the response is “DELayed2”; if it is SAMPLE, the response is “SAMPle[1]”.

ACQ01BBy executing this command the previously defined name is overwritten.

ACQ01B*RST has no effect on the defined name.

24.6.1.1.1 MGRules <Boolean>ARM:SEQuence:DEFine:MGRules

TK028AThis command sets or queries the state of MGRules, Mnemonic Generation Rules.

TK028AAt *RST, the value of this parameter is OFF.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem ARM 24-13

24.6.1.2 [:LAYer]ARM:SEQuence:LAYer

LAYer is used in the expanded capability model to identify a particular ARM LAYer in thetrigger system.

FL003

24.6.1.2.1 :COUNt <numeric_value>ARM:SEQuence:LAYer:COUNt

COUNt controls the path of the trigger system in the upward traverse of the event detectionlayer, shown in figure 24-4, “Event Detection Layer.” The trigger system is directed either tothe next layer up or to loop back through the downward traverse. Moving to the next layer upoccurs when the number of times that the trigger system has passed through the downwardtraverse (given by the value of loop_ctr) is equal to the specified COUNt. In the simple case,COUNt has the value 1, a single downward traverse through the layer occurs, followed bythe actions dictated by subservient layers, and finally a single upward traverse to next layerup. COUnt shall be set to a value of 1 or greater.


24.6.1.2.2 :COUPling AC|DC ARM:SEQuence:LAYer:COUPling

COUPling only has effect if the source for the event detector is an analog electrical signal,such as INTernal, LINE, or EXTernal. It selects AC or DC coupling for the SOURced signal.DC coupling allows the signal’s AC and DC components to pass. AC coupling passes onlythe signal’s AC component.


24.6.1.2.3 :DELay <numeric_value>ARM:SEQuence:LAYer:DELay

DELay sets the time duration between the recognition of an event(s) and the downward exitof the specified layer. DELay must be either zero or a positive value. An attempt to set it to anegative value shall cause an error -222 to be generated.

At *RST, this value is set to 0 or the smallest available positive value. The units for DELayare seconds.

24.6.1.2.3.1 :AUTO <Boolean>|ONCE ARM:SEQuence:LAYer:DELay:AUTO

This command is used for sensor devices with internal settling delays. If ON, the delay is setto the minimum necessary to ensure that a valid measurement can be acquired. This valuemay be coupled to other instrument settings such as function, range, resolution, and inputbandwidth.

At *RST, AUTO is set ON.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-14 TRIGger Subsystem ARM

24.6.1.2.4 :ECLARM:SEQuence:LAYer:ECL

This command is an event which presets LEVel, HYSTeresis, COUPling, and DELay tovalues appropriate for a ECL signal. This command cannot be queried.

24.6.1.2.5 :ECOunt <numeric_value>ARM:SEQuence:LAYer:ECOunt

ECOunt specifies a particular number of occurrences of the same event that must berecognized. For example where it is necessary to wait for the tenth positive edge of a signal,ECOunt must be set to 10. ECOunt must be a positive value of 1 or greater. An attempt to setit differently shall cause an error -222 to be generated.


24.6.1.2.6 :FILTerARM:SEQuence:LAYer:FILTer

TWOS03

This function allows a filter to be inserted between the source switch and event detector.FILTer only has effect if :SOURce is an analog switch such as INTernal, EXTernal, or LINE.

24.6.1.2.6.1 :HPASsARM:SEQuence:LAYer:FILTer:HPASs

TWOS03


24.6.1.2.6.1.1 :FREQuency <numeric_value>ARM:SEQuence:LAYer:FILTer:HPASs:FREQuency

TWOS03



24.6.1.2.6.1.2 [:STATe] <Boolean>ARM:SEQuence:LAYer:FILTer:HPASs:STATe

TWOS03

Turns the high pass filter ON or OFF.


24.6.1.2.6.2 [:LPASs]ARM:SEQuence:LAYer:FILTer:LPASs

TWOS03


24.6.1.2.6.2.1 :FREQuency <numeric_value>ARM:SEQuence:LAYer:FILTer:LPASs:FREQuency

TWOS03



24.6.1.2.6.2.2 [:STATe] <Boolean>ARM:SEQuence:LAYer:FILTer:LPASs:STATe

TWOS03

Turns the low pass filter ON or OFF.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



24.6.1.2.7 :HYSTeresis <numeric_value>ARM:SEQuence:LAYer:HYSTeresis

HYSTeresis is a qualifier of LEVel. It sets how far a signal must fall below LEVel before arising edge can again be detected, and how far a signal must rise above LEVel before afalling edge can again be detected. Its function is to eliminate false events caused by signalnoise. Units for the parameter default to the current amplitude units.

In instruments that have only two discrete values for hysteresis (such as Noise Rejection Onand Noise Rejection Off), the device designer should pick two numeric values thatapproximate the actual hystereis settings. The :HYSTeresis command has no :STATefunction because confusion would occur when turning hysteresis off. This might imply to auser that the actual hysteresis had been set to 0. This is rarely the case in instruments thathave only two states.

TWOS03


24.6.1.2.8 [:IMMediate]ARM:SEQuence:LAYer:IMMediate

This command provides a onetime override of the normal process of the downward traverseof the event detection layer. This command shall cause the immediate exit of the specifiedevent detection layer if the trigger system is in the specified layer when the IMMediate isreceived. Otherwise, the IMMediate command shall be ignored and an error -212 shall begenerated.

The actual event detection and delay shall be skipped; however, normal processing of theloop_ctr as shown in figure 24-4, “Event Detection Layer” shall occur. This command has noeffect on any other settings in this subsystem.

This command is an event and has no *RST condition and cannot be queried.

24.6.1.2.9 :LEVel <numeric_value>ARM:SEQuence:LAYer:LEVel

LEVel qualifies the characteristic of the selected SOURce signal that generates an event.LEVel only has effect if the source for the event detector is an analog electrical signal, suchas INTernal, LINE, or EXTernal. Units for the parameter default to the current amplitudeunit.

At *RST, this value is instrument-dependent.

TK03624.6.1.2.9.1 :AUTO <Boolean> | ONCEARM:SEQuence:LAYer:LEVel:AUTO

TK036When AUTO is ON, the device dynamically selects the best arm level based on adevice-dependent algorithm applied to the arm signal.

TK036When AUTO is OFF, the arm LEVel sets the arm level.

TK036Setting AUTO to ONCE turns AUTO ON, adjusts the arm level once and then resets AUTOto OFF.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK036Setting the arm LEVel turns AUTO OFF.

TK036At *RST, the value of this parameter is OFF.

24.6.1.2.10 :LINK <event_handle>ARM:SEQuence:LAYer:LINK

TWIR01p2JP Change

Sets or queries the internal event that is LINKed to the event detector in the ARM layer.Internal events occur throughout all of the Instrument Model, a particular implementationwill dictate which events are available to this LINK command. The <event_handle> isSTRING PROGRAM DATA and it is defined further in the Instrument Model, Chapter 2.

An Example of events that are commonly used, are the events that occur when a particularlayer is exited, these handles are of the form:



At *RST, this value is device-dependent.HP066

HP09324.6.1.2.11 PROTocolARM:SEQuence:LAYer:PROTocol

HP093This subsystem controls the protocol used with the selected source.

HP09324.6.1.2.11.1 VXI SYNChronous|SSYNchronous|ASYNchronousARM:SEQuence:LAYer:PROTocol:VXI

HP093This command selects the trigger protocol for the VXI TTLTrg or ECLTrg trigger line whenused as the arm source. The protocols are specified in the VXI Bus System Specificationunder sections B.6.2.3 and B.6.2.4.




HP093At *RST, the SYNChronous protocol is selected.

24.6.1.2.12 :SIGNalARM:SEQuence:LAYer:SIGNal

This command provides a one-time override of the normal process of the downward traversethrough the event detector in figure 24-4, “Event Detection Layer.” This command shallcause the immediate exit of the event detector block in the specified event detection layer ifthe trigger system is waiting for the event specified by the SOURce command. Otherwise,the SIGNal command shall be ignored and an error -212 shall be generated.

Only the event detector block is bypassed. Normal processing of the delay and the event_ctras shown in figure 24-4, “Event Detection Layer,” shall occur. This command has no effecton any other settings in this subsystem.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



This command defines an event, and as such does not have an associated query form or*RST condition.

24.6.1.2.13 :SLOPe POSitive|NEGative|EITHer ARM:SEQuence:LAYer:SLOPe

SLOPe qualifies whether the event occurs on the rising edge, falling edge, or either edge ofthe signal.

At *RST, this value is set to POS.

24.6.1.2.14 :SOURce <parameter>ARM:SEQuence:LAYer:SOURce

This command selects the source for the event detector. Only one source may be specified ata time for a given event detector. The various sources are:

TK040AINTernal — The triggering source is selected automatically by the instrumentfrom internal algorithms to best match the current operating mode. An AutomaticINTernal event is derived from measurement functions and/or sensor capabilitiesin the signal conditioning block.

TWV41CBUS — The source is signal specific to the control interface. For IEEE 488.1, thegroup execute trigger, GET, would satisfy this condition. In VXI the word serialcommand TRIGger performs this function. The event detector is also satisfied,independent of the interface, when a *TRG command is received. Note thatneither GET nor *TRG can be sent without having an effect on the messageexchange protocol described in IEEE 488.2.

ECLTrg — The signal source is the specified VXI P2 or P3 backplane ECLTrgTRIGGER line. Valid lines are ECLTrg0 and ECLTrg1 on P2, and ECLTrg2through ECLTrg5 on P3.

EXTernal — An external signal jack is selected as the source. If no suffix isspecified, EXTernal1 is assumed.

HOLD — The event detection is disabled. However, the IMMediate commandshall override HOLD.

IMMediate — No waiting for an event occurs.

INTernal — An internal channel is selected as the source. An INTernal event isderived from a measurement function and/or sensor capability in the signalconditioning block. If no suffix is specified, INTernal1 is assumed.

LINE — The source signal is determined from the AC line voltage.

LINK — The source for the event detector is specified by the LINK command.

MANual — The signal is user-generated, such as by pressing a front panel key.

OUTPut — The signal source is taken from an output channel. If no channel isspecified, OUTPut1 is assumed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TIMer — The source signal comes from a periodic timer. The period of the timeris specified by the TIMer command.

TTLTrg — The signal source is the specified VXI P2 backplane TTLTrgTRIGGER line. Valid lines are TTLTrg0 through TTLTrg7.

At *RST, IMMediate shall be selected as the SOURce. This value was chosen so thatdevices that do not implement any ARM layers (and hence the controls for the ARM layer)behave at *RST in the same manner as devices that do.

24.6.1.2.15 :TIMer <numeric_value>ARM:SEQuence:LAYer:TIMer

TIMer sets the period of an internal periodic signal source. Its value affects the triggersystem only when it is selected as the SOURce for the event detector. TIMer must be apositive value. An attempt to set it differently shall cause an error -222 to be generated. Thesynchronization of the timer’s period is device-dependent.

At *RST, this value is device-dependent value. The default units for this value is seconds.

24.6.1.2.16 :TTLARM:SEQuence:LAYer:TTL

This command is an event which presets LEVel, HYSTeresis, COUPling, and DELay tovalues appropriate for a TTL signal. This command cannot be queried.

TK035TK03524.6.1.2.17 :TYPE EDGE | VIDeoARM:SEQuence:LAYer:TYPE

TK035Sets or queries the type of triggering.

TK035At *RST, the value of this parameter is EDGE.

TK03524.6.1.2.18 :VIDeoARM:SEQuence:LAYer:VIDeo

TK035This subsystem controls parameters necessary to trigger on video signals.

TK03524.6.1.2.18.1 :FIELd ARM:SEQuence:LAYer:VIDeo:FIELd

TK035This subsystem selects the video field to trigger on.

TK03524.6.1.2.18.1.1 [:NUMBer] <numeric_value>ARM:SEQuence:LAYer:VIDeo:FIELd:NUMBer

TK035NUMBer sets or queries the field number to trigger on if FIELd:SELect is set to NUMBer.

TK035At *RST, the value of this parameter is 1.

TK03524.6.1.2.18.1.2 :SELect ODD | EVEN | ALL | NUMBerARM:SEQuence:LAYer:VIDeo:FIELd:SELect

TK035SELect sets or queries the video field selection method to be used. Four character dataparameters are defined as follows:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK035ODD selects odd-numbered fields to trigger on.

TK035EVEN selects even-numbered fields to trigger on.

TK035ALL triggers on all fields regardless of number.

TK035NUMBer triggers on the field number specified by NUMBer.

TK035At *RST, the value of this parameter is ALL.

TK03524.6.1.2.18.2 :FORMatARM:SEQuence:LAYer:VIDeo:FORMat

TK035FORMat controls parameters that allow the video trigger system to respond to signals fromstandard video formats.

TK03524.6.1.2.18.2.1 :LPFRame <numeric_variable>ARM:SEQuence:LAYer:VIDeo:FORMat:LPFRame

TK035LPFRame, Lines Per FRame, sets or queries the lines per frame associated with the signalformatting standard being used.

TK035For example, A signal following NTSC would selects 525 lines per frame while a PALsignal would select 625 lines per frame.

TK035At *RST, the value of this parameter is device dependent.

TK04524.6.1.2.18.3 :LINEARM:SEQuence:LAYer:VIDeo:LINE

TK045This subsystem selects a particular line in the field to arm on.

TK04524.6.1.2.18.3.1 [:NUMBer] <numeric_value>ARM:SEQuence:LAYer:VIDeo:LINE:NUMBer

TK045NUMBer sets or queries the line number to arm on if LINE:SELect is set to NUMBer.Setting the NUMBer value has no effect on the value of the SELect parameter.


TK04524.6.1.2.18.3.2 :SELect ALL | NUMBerARM:SEQuence:LAYer:VIDeo:LINE:SELect

TK045SELect sets or queries the video line selection method to be used. Two character dataparameters are defined as follows:

TK045ALL — arms on all lines regardless of number.

TK045NUMBer — arms on the line number specified by NUMBer.


TK03524.6.1.2.18.4 :SSIGnal ARM:SEQuence:LAYer:VIDeo:SSIGnal

TK035SSIGnal, Synchronizing SIGnal, controls parameters relating to the video synchronizingsignal.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK03524.6.1.2.18.4.1 :POLarity POSitive | NEGativeARM:SEQuence:LAYer:VIDeo:SSIGnal:POLarity

TK035SSIGnal:POLarity, sets or queries sync pulse triggering polarity.

TK035At *RST, the value of this parameter is NEGative.

24.7 INITiateINITiate

ACQ01BThe INITiate subsystem is used to control the initiation of the trigger subsystem. It initiatesall trigger sequences as a group except those sequences that are defined otherwise by eitherthe standard or in the instrument documentation.

KI005Instruments which implement the INITiate command as overlapped can continue parsing andexecuting subsequent commands and queries while initiated. Instruments which implementthe INITiate commands as sequential cannot execute subsequent commands and queries untilthe trigger model has returned to the IDLE state.

KI005For this reason, devices which implement the INITiate commands as sequential shall enterIDLE when the IEEE 488.2 dcas message is received. They shall also execute the nextmessage unit received after the dcas before leaving IDLE (if INITiate:CONTinuous is ON).dcas followed by *RST or dcas followed by INIT:CONT OFF shall always stop the triggermodel in the IDLE state.

KI005There are advantages to implementing the INITiate commands as overlapped.

KI005The instrument designer decides whether or not a device clear aborts the triggermodel.

KI005The instrument can continue parsing and executing commands and queries whilethe trigger model is initiated (for example, FETCh? to get the readings which arebeing triggered in a meter).

KI005The disadvantage to implementing any commands as overlapped, including the INITiatecommands, is that it adds complexity to the implementation of the IEEE 488.2 commoncommands *OPC, *WAI and *OPC?

TK03824.7.1 :CONTinuous <Boolean>INITiate:CONTinuous

The CONTinuous command is used to select whether the trigger system is continuouslyinitiated or not. With CONTinuous set to OFF, the trigger system shall remain in the IDLEstate until CONTinuous is set to ON or INITiate:IMMediate is received. Once CONTinuousis set to ON, the trigger system shall be initiated and shall exit the IDLE state. On completionof each trigger cycle, with CONTinuous ON, the trigger system shall immediatelycommence another trigger cycle without entering the IDLE state.

KI005When INITiate:CONTinuous is set to OFF, the current trigger cycle shall be completedbefore entering the IDLE state. The return to IDLE shall also occur as the result of anABORt or *RST command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem INITiate 24-21

With the trigger system set to cycle continuously, the ABORt command shall force thetrigger system to the IDLE state; however, the value of INITiate:CONTinuous is unaffected.If CONTinuous was set to ON prior to receiving ABORt, it shall remain ON and the triggersystem shall immediately exit the IDLE state.

ACQ01BThis subsystem does not apply to sequences that are initiated by the INITiate:ALL command.

24.7.1.1 [:ALL] <Boolean>INITiate:CONTinuous:ALL

ACQ01BSets or queries whether or not all sequences are continuously initiated.

ACQ01BAt *RST, this value is set to OFF.

24.7.1.2 :NAME <sequence_name>,<Boolean>INITiate:CONTinuous:NAME

ACQ01BSets or queries whether or not the SEQuence with the alias specified by <sequence_name> iscontinously initiated. The <sequence_name> is character program data. See 24.4.2 forstandard sequence names.

ACQ01BThe <sequence_name> is a required parameter of the query form, the query form returns Oor 1.


24.7.1.3 :SEQuence <Boolean>INITiate:CONTinuous:SEQuence

ACQ01BSets or queries whether or not the specified SEQuence is continously initiated. The numericsuffix on SEQuence corresponds to the sequence number. If NAME is implemented, thiscommand shall also be implemented.


24.7.2 [:IMMediate]INITiate:IMMediate

ACQ01BThese commands shall cause all sequences to exit the IDLE state; they are initiated. TheIMMediate command shall cause the trigger system to initiate and complete one full triggercycle, returning to IDLE on completion. If the device is not in IDLE or ifINITiate:CONTinuous is set to ON, an IMMediate command shall have no effect on thetrigger system and an error -213 shall be generated.

INITiate[:IMMediate] is an event and cannot be queried as there is no state associated with it.

24.7.2.1 [:ALL]INITiate:IMMediate:ALL

ACQ01BThis command causes all SEQuences to be INITiated, except those defined to behaveotherwise.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-22 TRIGger Subsystem INITiate

24.7.2.2 :NAME <sequence_name>INITiate:IMMediate:NAME

ACQ01BThis command causes the SEQuence with the alias specified by <sequence_name> to beINITiated. The <sequence_name> is character program data. See 24.4.2 for standardsequence names.

24.7.2.3 :SEQuenceINITiate:IMMediate:SEQuence

ACQ01BThis command causes the specified SEQuence to be INITiated. The numeric suffix onSEQuence corresponds to the sequence number. If NAME is implemented, this commandshall also be implemented.

TK03824.7.3 :POFLag INCLude | EXCLudeINITiate:POFLag

TK038POFLag, Pending Operation Flag, allows the Pending-Operation flag associated with theinitiation of a trigger sequence to be included or excluded from the No-Operation-Pendingflag set.

TK038Setting POFLag to EXCLude means the No-Operation-Pending flag set is independent of thestate of the trigger subsystem. Moving from the INITiated to IDLE trigger states and viceversa has no effect on the NOP flag in this state.

TK038Setting POFLag to INCLude means the No-Operation-Pending flag set includes the triggersubsystem’s Pending-Operation flag which goes true when the trigger subsystem moves fromIDLE to INITiated state and returns to false when IDLE is re-entered.

TK038At *RST, the value of this parameter is INCLude.

24.8 TRIGgerTRIGger

The purpose of the TRIGger subsystem is to qualify a single event before enabling thetriggered sequence operation, such as enabling a sweep, starting a measurement, or changingthe state of the device.

24.8.1 [:SEQuence]TRIGger:SEQuence

ACQ01BSEQuence is used in the expanded capability model to identify a particular sequence oflayers in the trigger system. A <sequence_name>, see 24.4.2, may also be used here.

TK02724.8.1.1 :ATRiggerTRIGger:SEQuence:ATRigger

TK027ATRigger, Auto TRigger, controls an event detector timer that causes control flow to exit theevent detector if a valid trigger does not appear within a preset time period. The auto triggertimer is started upon entering the TRIGger layer, and after the control flow leaves the eventdetector. The precise timing of the timer is device dependent. See Figure 24-4.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


TRIGger Subsystem TRIGger 24-23

TK02724.8.1.1.1 [:STATe] <Boolean>TRIGger:SEQuence:ATRigger:STATe

TK027STATe sets and queries the state of the auto trigger function. STATe ON enables thefunction and STATe OFF disables it.


24.8.1.2 :COUNt <numeric_value>TRIGger:SEQuence:COUNt

COUNt controls the path of the trigger system in the upward traverse of the event detectionlayer, shown in figure 24-4, “Event Detection Layer.” The trigger system is directed either tothe next layer up or to loop back through the downward traverse. Moving to the next layer upoccurs when the number of times that the trigger system has passed through the downwardtraverse (given by the value of loop_ctr) is equal to the specified COUNt. In the simple case,COUNt has the value 1, a single downward traverse through the layer occurs, followed bythe actions dictated by subservient layers and finally a single upward traverse to next layerup. COUnt shall be set to a value of 1 or greater.


24.8.1.3 :COUPling AC|DC TRIGger:SEQuence:COUPling

COUPling only has effect if the source for the event detector is an analog electrical signal,such as INTernal, LINE, or EXTernal. It selects AC or DC coupling for the SOURced signal.DC coupling allows the signal’s AC and DC components to pass. AC coupling passes onlythe signal’s AC component.


24.8.1.4 : DEFine <sequence_name>TRIGger:SEQuence:DEFine

ACQ01BSets or queries the SEQuence alias. This command is required where aliases are employedand they do not correspond to the standard mapping. The numeric suffix on SEQuencecorresponds the sequence number to which the alias is to be applied.

ACQ01BThis command is an alias to ARM:SEQuence:LAYer:DEFine. Changing the value ofTRIGger:SEQuence:DEFine changes the value of ARM:SEQuence:DEFine to the samevalue.

TK028AThe <sequence_name> is character data.

TK028AThe effect of <sequence_name> is modified by DEFine:MGRules as follows:

TK028ARegardless of the state or presence of DEFine:MGRules, there is no differencebetween uppercase and lowercase letters used in <sequence_name>.

TK028AIf the command DEFine:MGRules is absent or set to OFF, thefull<sequence_name> as written is the only form allowed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


24-24 TRIGger Subsystem TRIGger

For example, if the <sequence_name> were SAMPLE1, then SAMPLE1 is theonly alias accepted.

TK028AIf the command DEFine:MGRules is present and set to ON, the<sequence_name> is interpreted as <program_mnemonic>[<numeric_suffix>]where all the contiguous trailing digits form the <numeric_suffix>. Mnemonicgeneration rules as described in Syntax and Style, Section 6.2.1. shall apply to the<program_mnemonic> and the <numeric suffix>.

For example, if the <sequence_name> were defined as VECTOR or VECTOR1,then VECT, VECT1, VECTOR, and VECTOR1 would all be acceptable aliases.

ACQ01BIf the <sequence_name> is identical to a keyword under ARM or TRIGger subsystem, thedevice shall report execution error -224. For example ARM:SEQuence2:DEFine FILTERwill cause an error. This command shall accept any other valid character program data for<sequence_name>.

ACQ01BThe query returns a string which contains the <sequence_name>, so that a null string canindicate that nothing is defined.

TK028AIf the command DEFine:MGRules is present and set to ON, the returned <sequence_name>will follow the upper/lower case convention described in Syntax and Style, section 5.1,Interpreting Command Tables. An omitted <numeric_suffix> or a <numeric_suffix> of 1will be represented as [1].

TK028AFor example, if <sequence_name> is VECTOR1 then the response is “VECTor[1]”; if it isDELAYED2, the response is “DELayed2”; if it is SAMPLE, the response is “SAMPle[1]”.

ACQ01BBy executing this command the previously defined name is overwritten.

ACQ01B*RST has no effect on the defined name.

24.8.1.4.1 MGRules <Boolean>TRIGger:SEQuence:DEFine:MGRules

TK028AThis command sets or queries the state of MGRules, Mnemonic Generation Rules.

TK028AAt *RST, the value of this parameter is OFF.

24.8.1.5 :DELay <numeric_value>TRIGger:SEQuence:DELay

DELay sets the time duration between the recognition of an event(s) and the downward exitof the specified layer. DELay must be either zero or a positive value. An attempt to set it to anegative value shall cause an error -222 to be generated.

At *RST, this value is set to 0 or the smallest available positive value. The value has units ofseconds.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



24.8.1.5.1 :AUTO <Boolean>|ONCE TRIGger:SEQuence:DELay:AUTO

This command is used for sensor devices with internal settling delays. If ON, the delay is setto the minimum necessary to ensure that a valid measurement can be acquired. This valuemay be coupled to other instrument settings such as function, range, resolution, and inputbandwidth.

At *RST, AUTO is set ON.

24.8.1.6 :ECLTRIGger:SEQuence:ECL

This command is an event which presets LEVel, HYSTeresis, COUPling, and DELay tovalues appropriate for a ECL signal. This command cannot be queried.

24.8.1.7 :ECOunt <numeric_value>TRIGger:SEQuence:ECOunt

ECOunt specifies a particular number of occurrences of the same event that must berecognized. For example, where it is necessary to wait for the tenth positive edge of a signal,ECOunt must be set to 10. ECOunt must be a positive value of 1 or greater. An attempt to setit differently shall cause an error -222 to be generated.


24.8.1.8 :FILTerTRIGger:SEQuence:FILTer

TWOS03

This function allows a filter to be inserted between the source switch and event detector.FILTer only has effect if :SOURce is an analog switch such as INTernal, EXTernal, or LINE.

24.8.1.8.1 :HPASsTRIGger:SEQuence:FILTer:HPASs

TWOS03


24.8.1.8.1.1 :FREQuency <numeric_value>TRIGger:SEQuence:FILTer:HPASs:FREQuency

TWOS03



24.8.1.8.1.2 [:STATe] <Boolean>TRIGger:SEQuence:FILTer:HPASs:STATe

TWOS03

Turns the high pass filter ON or OFF.


24.8.1.8.2 [:LPASs]TRIGger:SEQuence:FILTer:LPASs

TWOS03


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



24.8.1.8.2.1 :FREQuency <numeric_value>TRIGger:SEQuence:FILTer:LPASs:FREQuency

TWOS03



24.8.1.8.2.2 [:STATe] <Boolean>TRIGger:SEQuence:FILTer:LPASs:STATe

TWOS03

Turns the low pass filter ON or OFF.


24.8.1.9 :HOLDoff <numeric_value>TRIGger:SEQuence:HOLDoff

TK021HOLDoff controls the time during which the event detector is inhibited from acting on anynew trigger. The exact point in the trigger model at which the trigger holdoff timer is startedis device dependent, but it shall be after the event detector on the downward traverse andbefore the event detector on the upward traverse. See Figure 24-4.

TK021The range of the parameter is zero to one, where one is maximum holdoff and zero isminimum.

TK021At *RST, the value of the parameter is zero.

24.8.1.10 :HYSTeresis <numeric_value>TRIGger:SEQuence:HYSTeresis

HYSTeresis is a qualifier of LEVel. It sets how far a signal must fall below LEVel before arising edge can again be detected, and how far a signal must rise above LEVel before afalling edge can again be detected. Its function is to eliminate false events caused by signalnoise. Units for the parameter default to the current amplitude units.

In instruments that have only two discrete values for hysteresis (such as Noise Rejection Onand Noise Rejection Off), the device designer should pick two numeric values thatapproximate the actual hystereis settings. The :HYSTeresis command has no :STATefunction because confusion would occur when turning hysteresis off. This might imply to auser that the actual hysteresis had been set to 0. This is rarely the case in instruments thathave only two states.

TWOS03


24.8.1.11 [:IMMediate]TRIGger:SEQuence:IMMediate

This command exists to provide a one-time override of the normal process of the downwardtraverse of the event detection layer. This command shall cause the immediate exit of thespecified event detection layer if the trigger system is in the specified layer when theIMMediate is received. Otherwise, the IMMediate command shall be ignored and an error-211 shall be generated.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The actual event detection and delay shall be skipped; however, normal processing of theloop_ctr as shown in figure 24-4, “Event Detection Layer,” shall occur. This command hasno effect on any other settings in this subsystem.

This command is an event, has no *RST condition, and cannot be queried.

24.8.1.12 :LEVel <numeric_value>TRIGger:SEQuence:LEVel

LEVel qualifies the characteristic of the selected SOURce signal that generates an event.LEVel only has effect if the source for the event detector is an analog electrical signal, suchas INTernal, LINE, or EXTernal. Units for the parameter default to the current amplitudeunit.

At *RST, this value is instrument-dependent.

TK03624.8.1.12.1 :AUTO <Boolean> | ONCETRIGger:SEQuence:LEVel:AUTO

TK036When AUTO is ON, the device dynamically selects the best trigger level based on adevice-dependent algorithm applied to the trigger signal.

TK036When AUTO is OFF, the trigger LEVel sets the trigger level.

TK036Setting AUTO to ONCE turns AUTO ON, adjusts the trigger level once and then resetsAUTO to OFF.

TK036Setting the trigger LEVel turns AUTO OFF.


24.8.1.13 :LINK <event_handle>TRIGger:SEQuence:LINK

TWIR01p24JP Change

Sets or queries the internal event that is LINKed to the event detector in the TRIGger layer.Internal events occur throughout all of the Instrument Model, a particular implementationwill dictate which events are available to this LINK command. The <event_handle> isSTRING PROGRAM DATA and it is defined further in the Instrument Model, Chapter 2.

An Example of events that are commonly used, are the events that occur when a particularlayer is exited, these handles are of the form:



At *RST, this value is device-dependent.HP066

HP09324.8.1.14 :PROTocolTRIGger:SEQuence:PROTocol

HP093This subsystem controls the protocol used with the selected source.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



HP09324.8.1.14.1 :VXI SYNChronous|SSYNchronous|ASYNchronousTRIGger:SEQuence:PROTocol:VXI

HP093This command selects the trigger protocol for the VXI TTLTrg or ECLTrg trigger line whenused as the trigger source. The protocols are specified in the VXI Bus System Specificationunder sections B.6.2.3 and B.6.2.4.




HP093At *RST, the SYNChronous protocol is selected.

24.8.1.15 :SIGNalTRIGger:SEQuence:SIGNal

This command provides a one-time override of the normal process of the downward traversethrough the event detector in figure 24-4, “Event Detection Layer.” This command shallcause the immediate exit of the event detector block in the specified event detection layer ifthe trigger system is waiting for the event specified by the SOURce command. Otherwise,the SIGNal command shall be ignored and an error -211 shall be generated.

Only the event detector block is bypassed. Normal processing of the delay and the event_ctras shown in figure 24-4, “Event Detection Layer,” shall occur. This command has no effecton any other settings in this subsystem.

This command defines an event, and as such does not have an associated query form or*RST condition.

24.8.1.16 :SLOPe POSitive|NEGative|EITHer TRIGger:SEQuence:SLOPe

SLOPe qualifies whether the event occurs on the rising edge, falling edge, or either edge ofthe signal.

At *RST, this value is set to POS.

24.8.1.17 :SOURce <parameter> TRIGger:SEQuence:SOURce

This command selects the source for the event detector. Only one source may be specified inthe parameter at a time for a given event detector. The various sources are:

TK040AINTernal — The triggering source is selected automatically by the instrumentfrom internal algorithms to best match the current operating mode. An AutomaticINTernal event is derived from measurement functions and/or sensor capabilitiesin the signal conditioning block.

TWV41CBUS — The source is signal specific to the control interface. For IEEE 488.1 thegroup execute trigger, GET, would satisfy this condition. In VXI the word serialcommand TRIGger performs this function. The event detector is also satisfied,independent of the interface, when a *TRG command is received. Note that

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



neither GET nor *TRG can be sent without having an effect on the messageexchange protocol described in IEEE 488.2.

ECLTrg — The signal source is the specified VXI P2 or P3 backplane ECLTrgTRIGGER line. Valid lines are ECLTrg0 and ECLTrg1 on P2, and ECLTrg2through ECLTrg5 on P3.

EXTernal — An external signal jack is selected as the source. If no suffix isspecified, EXTernal1 is assumed.

HOLD — The event detection is disabled. However, the IMMediate commandshall override HOLD.

IMMediate — No waiting for an event occurs.

INTernal — An internal channel is selected as the source. An INTernal event isderived from a measurement function and/or sensor capability in the signalconditioning block. If no suffix is specified, INTernal1 is assumed.

LINE — The source signal is determined from the AC line voltage.

LINK — The source for the event detector is specified by the LINK command.

MANual — The signal is user-generated, such as by pressing a front panel key.

OUTPut — The signal source is taken from an output channel. If no channel isspecified, OUTPut1 is assumed.

TIMer — The source signal comes from a periodic timer. The period of the timeris specified by the TIMer command.

TTLTrg — The signal source is the specified VXI P2 backplane TTLTrgTRIGGER line. Valid lines are TTLTrg0 through TTLTrg7.

At *RST, IMMediate shall be selected as the SOURce.

24.8.1.18 :TIMer <numeric_value> TRIGger:SEQuence:TIMer

TIMer sets the period of an internal periodic signal source. Its value affects the triggersystem only when it is selected as the SOURce for the event detector. TIMer must be apositive value. An attempt to set it differently shall cause an error -222 to be generated. Thesynchronization of the timer’s period is device-dependent.

At *RST, this value is set to a device-dependent value.

24.8.1.19 :TTL TRIGger:SEQuence:TTL

This command is an event which presets LEVel, HYSTeresis, COUPling, and DELay tovalues appropriate for a TTL signal. This command cannot be queried.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK03524.8.1.20 :TYPE EDGE | VIDeoTRIGger:SEQuence:TYPE

TK035Sets or queries the type of triggering.

TK035At *RST, the value of this parameter is EDGE.

TK03524.8.1.21 :VIDeoTRIGger:SEQuence:VIDeo

TK035This subsystem controls parameters necessary to trigger on video signals.

TK03524.8.1.21.1 :FIELd TRIGger:SEQuence:VIDeo:FIELd

TK035This subsystem selects the video field to trigger on.

TK03524.8.1.21.1.1 [:NUMBer] <numeric_value>TRIGger:SEQuence:VIDeo:FIELd:NUMBer

TK035NUMBer sets or queries the field number to trigger on if FIELd:SELect is set to NUMBer.

TK035At *RST, the value of this parameter is 1.

TK03524.8.1.21.1.2 :SELect ODD | EVEN | ALL | NUMBerTRIGger:SEQuence:VIDeo:FIELd:SELect

TK035SELect sets or queries the video field selection method to be used. Four character dataparameters are defined as follows:

TK035ODD selects odd-numbered fields to trigger on.

TK035EVEN selects even-numbered fields to trigger on.

TK035ALL triggers on all fields regardless of number.

TK035NUMBer triggers on the field number specified by NUMBer.


TK03524.8.1.21.2 :FORMatEditTRIGger:SEQuence:VIDeo:FORMat

TK035FORMat controls parameters that allow the video trigger system to respond to signals fromstandard video formats.

TK03524.8.1.21.2.1 :LPFRame <numeric_variable>EditTRIGger:SEQuence:VIDeo:FORMat:LPFRame

TK035LPFRame, Lines Per FRame, sets or queries the lines per frame associated with the signalformatting standard being used.

TK035For example, A signal following NTSC would selects 525 lines per frame while a PALsignal would select 625 lines per frame.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



TK04524.8.1.21.3 :LINETRIGger:SEQuence:VIDeo:LINE

TK045This subsystem selects a particular line in the field to trigger on.

TK04524.8.1.21.3.1 [:NUMBer] <numeric_value>TRIGger:SEQuence:VIDeo:LINE:NUMBer

TK045NUMBer sets or queries the line number to trigger on if LINE:SELect is set to NUMBer.Setting the NUMBer value has no effect on the value of the SELect parameter.


TK04524.8.1.21.3.2 :SELect ALL | NUMBerTRIGger:SEQuence:VIDeo:LINE:SELect

TK045SELect sets or queries the video line selection method to be used. Two character dataparameters are defined as follows:

TK045ALL — triggers on all lines regardless of number.

TK045NUMBer — triggers on the line number specified by NUMBer.


TK03524.8.1.21.4 :SSIGnal TRIGger:SEQuence:VIDeo:SSIGnal

TK035SSIGnal, Synchronizing SIGnal, controls parameters relating to the video synchronizingsignal.

TK03524.8.1.21.4.1 :POLarity POSitive | NEGativeTRIGger:SEQuence:VIDeo:SSIGnal:POLarity

TK035SSIGnal:POLarity, sets or queries sync pulse triggering polarity.

TK035At *RST, the value of this parameter is NEGative.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



25 UNIT SubsystemDefault units are defined, where applicable, for each SCPI command. The UNIT subsystemprovides a mechanism to change the default values. The units selected apply to thedesignated command parameters for both command and response.

The UNIT command at the root level has a global effect on the selected units. The UNITcommand may also be applied to lower levels in the SCPI command hierarchy to have alocalized effect. When the UNIT command is applied to a node, then all the nodes below thenode to which the unit command was applied shall be affected by the localized UNITcommand. There is no restriction on the number of levels to which UNIT may be applied. Inthis way the more global units are overridden by the more local units. Units may also beoverridden temporarily by attaching the desired unit as a suffix to the appropriate parameterin the command, if the instrument supports that unit.

For example, to program a source with units of Volts, the command UNIT:VOLTage VOLTwould be used. To program only the modulator of that same source in dBuVs, the additionalcommand [SOURce:]MODulation:UNIT DBUV would be required.

The UNIT command cannot be applied to either SENSe, SOURce or ROUTe nodes, sincethe UNIT command at these nodes and at the root cannot be unambiguously recognized.This condition arises from the ability to have one of SENSe, SOURce or ROUTe nodesoptional.

KEYWORD PARAMETER FORM NOTES Bode

:UNIT :ANGLe DEG|RAD :CURRent <amplitude unit> :POWer <amplitude unit> :TEMPerature C|CEL|F|FAR|K :TIME HOUR|MINute|SECond 1993 XSS01c :VOLTage <amplitude unit>

25.1 :ANGLe DEG|RADUNIT:ANGLe

Specifies the fundamental unit of angle.

At *RST, the default unit is RAD.

25.2 :CURRent, :POWer, and :VOLTageUNIT:CURRent

Selects a default unit for commands which program absolute amplitude. The default unitmay be overridden when programming a function by explicitly sending a suffix. The defaultunit may also be overridden if a unit command exists at a lower tree level. Query values ofcommands which program in amplitude units shall be returned in the current amplitude unit

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


UNIT:ANGLe 25-1

unless overridden by a unit command at a tree level closer to the command itself (such asPOWer:UNIT).

The possible values are:

Linear power: W (Watt)

Linear voltage: V (Volt)

Linear current: A (Ampere)

Logarithmic power: DBM, DB[IEEE suffix multiplier]W (such as DBUW)

Logarithmic voltage: DB[IEEE suffix multiplier]V (such as DBUV)

Logarithmic current: DB[IEEE suffix multiplier]A (such as DBA)

An instrument must accept all values in any class if it accepts any value in that class.However, the decision to accept a class is device-dependent. A device which acceptslogarithmic units must also accept the comparable linear unit. This means thatUNIT:VOLTage WATT is permissible if it makes sense for the instrument. It is also impliedthat an impedance is specified for the signal when converting between different fundamentalquantities.

At *RST, this value is device-dependent. However, the following restrictions apply. TheUNIT subsystem must be implemented if a device chooses any value other than thefundamental unit for either the VOLTage, POWer, or CURRent subsystem , or if itimplements logarithmic units.

25.3 :TEMPerature C|CEL|F|FAR|KUNIT:TEMPerature

Specifies the fundamental unit of temperature as degrees Celsius, Fahrenheit, or Kelvin. Theform FAR and CEL, defined by IEEE 488.2, shall be accepted for Fahrenheit and Celsiusrespectively, and these shall be the preferred forms that are returned for a query.


25.4 :TIME HOUR|MINute|SECond XSS01cUNIT:TIME

Specifies the fundamental unit of time.

At *RST, this value is SECond.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


25-2 UNIT:TEMPerature

26 VXI SubsystemThe VXI subsystem contains commands that control the administration functions associatedwith operating a VXI-based system. This section will track the work of the VXI consortium.

This section describes ASCII commands which are issued to the system from an externalhost. The exact internal destination device and routing methods to that device are systemspecific. These commands are used for access to system configuration information, and forcommon capabilities. The terminology used in this section is patterned after IEEE 488.2.

The following commands are the standard set of VXIbus system commands which areASCII encoded. If a device implements one or more of these commands, the syntax of thissection shall be used. The response syntax shall also follow this section.

The COMMON ASCII SYSTEM COMMANDS are organized into subsystems. If a deviceimplements a required command in a subsystem then it shall implement all the requiredcommands in the subsystem. If a device implements an optional command in a subsystemthen it shall implement all the required commands in the subsystem. If a device implements acommand from any subsystem then it shall also implement the VXI:SELect command.

KEYWORD PARAMETER FORM NOTESVXI :CONFigure :DNUMber? [query only] :HIERarchy? [query only] 1992 :ALL? [query only] 1992 :VERBose? [query only] 1992 :ALL? [query only] 1992 :INFormation? [query only] 1992 :ALL? [query only] 1992 :VERBose? [query only] 1992 :ALL? [query only] 1992 :LADDress? [query only] 1992 :NUMber? [query only] 1992 :REGister 1992 :READ? <numeric_value>|<reg_name> [query only] 1992 :VERBose? <numeric_value>|<reg_name> [query only] 1992 :WRITe (<numeric_value>|<reg_name>), [no query] 1992 <data> :RESet? [query only] 1992 :VERBose? [query only] 1992 :SELect <numeric_value> 1992 :WSProtocol 1992 :COMMand 1992 [:ANY] <numeric_value> [no query] 1992 :AHILine <numeric_value>,<numeric_value> [no query] 1992 :AILine <numeric_value>,<numeric_value> [no query] 1992

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-1

KEYWORD PARAMETER FORM NOTES :AMControl <numeric_value> [no query] 1992 :ANO [no query] 1992 :BAVailable <Boolean>,<numeric_value> [no query] 1992 :BNO <Boolean> [no query] 1992 :BRQ [no query] 1992 :CEVent <Boolean>,<numeric_value> [no query] 1992 :CLR [no query] 1992 :CLOCk [no query] 1992 :CRESponse <numeric_value> [no query] 1992 :ENO [no query] 1992 :GDEVice <numeric_value> [no query] 1992 :ICOMmander <numeric_value> [no query] 1992 :RDEVice <numeric_value> [no query] 1992 :RHANdlers [no query] 1992 :RHLine <numeric_value> [no query] 1992 :RILine <numeric_value> [no query] 1992 :RINTerrupter [no query] 1992 :RMODid [no query] 1992 :RPERror [no query] 1992 :RPRotocol [no query] 1992 :RSTB [no query] 1992 :RSARea [no query] 1992 :SLModid <Boolean>,<numeric_value> [no query] 1992 :SLOCk [no query] 1992 :SUModid <Boolean>,<numeric_value> [no query] 1992 :TRIGger [no query] 1992 :MESSage 1992 :RECeive? <numeric_value>|<terminator> [query only] 1992 :SEND <message_string> [,(END|NEND)] [no query] 1992 :QUERy 1992 [:ANY?] <numeric_value> [query only] 1992 :AHILine? <numeric_value>,<numeric_value> [query only] 1992 :AILine? <numeric_value>,<numeric_value> [query only] 1992 :AMControl? <numeric_value> [query only] 1992 :ANO? [query only] 1992 :BNO? <Boolean> [query only] 1992 :BRQ? [query only] 1992 :CEVent? <Boolean>,<numeric_value> [query only] 1992 :CRESponse? <numeric_value> [query only] 1992 :ENO? [query only] 1992 :RDEVice? <numeric_value> [query only] 1992 :RHANdlers? [query only] 1992 :RHLine? <numeric_value> [query only] 1992 :RILine? <numeric_value> [query only] 1992

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-2 VXI

KEYWORD PARAMETER FORM NOTES :RINTerrupter? [query only] 1992 :RMODid? [query only] 1992 :RPERror? [query only] 1992 :RPRotocol? [query only] 1992 :RSTB? [query only] 1992 :RSARea? [query only] 1992 :SLModid? <Boolean>,<numeric_value> [query only] 1992 :SUModid? <Boolean>,<numeric_value> [query only] 1992 :RESPonse? [query only] 1992

26.1 :CONFigureVXI:CONFigure

Provides the necessary commands to query the configuration of a VXI system.

26.1.1 :DNUMber?VXI:CONFigure:DNUMber?

This query returns the number of devices in the system, in <NR1 numeric value> format.The range of this integer numeric value is 1 to 256 inclusive.

26.1.2 :HIERarchy?VXI:CONFigure:HIERarchy?

This command returns current hierarchy configuration information about the selected logicaladdress. The individual fields of the response are comma separated. If the information aboutthe selected logical address is not available from the destination device, (that is, therequested device is not in the servant area of the destination device), then error -224,“Parameter error” will be set and no response data will be sent. This is a requiredconfiguration command. The output fields are defined as follows:

Logical address: a <NR1>, between -1 and 255 inclusive. A -1 indicates that thedevice has no logical address.

commander’s logical address: a <NR1>, between -1 and 255 inclusive. -1indicates that this device has no commander or the commander is unknown.

Interrupt Handlers: a comma separated list of 7 <NR1>, between 0 and 7inclusive. Interrupt lines 1-7 are mapped to the individual return values. 0 is usedto indicate that the particular interrupt handler is not configured. A set of returnvalues of 0,0,0,5,2,0,6 would indicate that the device is configured as follows: handler 4 is configured to handle interrupts on line 5 handler 5 is configured to handle interrupts on line 2 handler 7 is configured to handle interrupts on line 6 handlers 1,2,3,6 are not configured

Interrupters: a comma separated list of 7 <NR1>, between 0 and 7 inclusive.Interrupt lines 1-7 are mapped to the individual return values. 0 is used to indicatethat the particular interrupter is not configured. A set of return values of0,0,0,5,2,0,6 would indicate that the device is configured as follows:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-3

interrupter 4 is configured to interrupt on line 5 interrupter 5 is configured to interrupt on line 2 interrupter 7 is configured to interrupt on line 6 interrupters 1,2,3,6 are not configured

Pass/Failed: a <NR1> which contains the pass/fail status of the specified deviceencoded as follows: FAIL=0 IFAIL=1 PASS=2 READY=3

manufacturer specific comment: This up to 80 character quoted string containsmanufacturer specific data. It is sent with a 488.2 string response data format.

26.1.2.1 :ALL?VXI:CONFigure:HIERarchy?:ALL?

When issued to a resource manager, configuration information about about all logicaladdresses. If the command is received by a device which is not the resource manager, itreturns the current hierarchy configuration information about the destination device followedby all of its immediate servants. The information is returned in the order specified inVXI:CONFigure:LADDress?. (the information about multiple logical addresses will besemi-colon separated and follow the IEEE 488.2 response message format). The individualfields of the output are comma separated. This is an optional configuration command.

26.1.2.2 :VERBose?VXI:CONFigure:HIERarchy?:VERBose?

This command has the same functionality as VXI:CONFigure:HIERarchy?. However itreturns a quoted string indicating the device information for the selected This command isintended to allow for a human readable form of the response toVXI:CONFigure:HIERarchy?. The format of this string is manufacturer specific. This is anoptional configuration command.

26.1.2.2.1 :ALL?VXI:CONFigure:HIERarchy?:VERBose?:ALL?

This command has the same functionality as VXI:CONFigure:HIERarchy:ALL?. However itreturns a semicolon separated sequence of strings indicating the device information for alldevices. The format of this string is manufacturer specific. This command is intended toallow for a human readable form of the response to VXI:CONFigure:HIERarchy:ALL?. Thisis an optional configuration command.

26.1.3 :INFormation?VXI:CONFigure:INFormation?

This command returns the static information about the selected logical address. Theindividual fields of the response are comma separated. If the information about the selectedlogical address is not available from the destination device, (that is, the requested device isnot in the servant area of the destination device), then error -224, “Parameter error” will beset and no response data will be sent. This is a required configuration command. Thecommand returns the following values:

logical address: a <NR1> between -1 and 255 inclusive. A -1 indicates that the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-4 VXI

device has no logical address.

manufacturer id: a <NR1>, between -1 and 4095 inclusive. -1 indicates that thedevice has no manufacturer id.

model code: a <NR1>, between -1 and 65535 inclusive. -1 indicates that thedevice has no model code

device class: a <NR1>, between 0 and 5 inclusive. Each value corresponds the thedevice’s classification as follows: 0: VXIbus memory device. 1: VXIbus extended device. 2: VXIbus message based device. 3: VXIbus register based device. 4: Hybrid device. 5: Non-VXIbus device.

address space: a <NR1>, between 0 and 15 inclusive, which is the sum of thebinary weighted codes of the address space(s) occupied by the device. Thefollowing values are defined: 1: The device has A16 registers. 2: The device has A24 registers. 4: The device has A32 registers. 8: The device has A64 registers.

A16 memory offset: the base address for any A16 registers (other than theVXIbus defined registers) which are present on the device. This is a <NR1> in therange of -1 to 65535. -1 is used to indicate that the device has no A16 memory.

A24 memory offset: the base address for any A24 registers which are present onthe device. This is a <NR1> in the range of -1 to 16777215. -1 is used to indicatethat the device has no A24 memory.

A32 memory offset: the base address for any A32 registers which are present onthe device. This is a <NR1> value> in the range of -1 to 4294967295. -1 is used toindicate that the device has no A32 memory.

A16 memory size: the number of bytes reserved for any A16 registers (other thanthe VXIbus defined registers) which are present on the device. This is a <NR1> inthe range of -1 to 65535. -1 is used to indicate that the device has no A16 memory.

A24 memory size: the number of bytes reserved for any A24 registers which arepresent on the device. This is a <NR1> in the range of -1 to 16777215. -1 is usedto indicate that the device has no A24 memory.

A32 memory size: the number of bytes reserved for any A32 registers which arepresent on the device. This is a <NR1> in the range of -1 to 4294967295. -1 isused to indicate that the device has no A32 memory.

Slot number: a <NR1>, between -1 and the number of slots which exist in the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-5

cage. -1 indicates that the slot which contains this device is unknown.

Slot 0’s logical address: a <NR1>, between -1 and 255 inclusive. -1 indicates thatSlot 0 device associated with this device is unknown.

subclass: a <NR1> representing the contents of the subclass register. -1 indicatesthat the subclass register is not defined for this device.

attribute: a <NR1> representing the contents of the attribute register. -1 indicatesthat the attribute register is not defined for this device.

manufacturer specific comment: This up to 80 character quoted string containsmanufacturer specific data. It is sent with a 488.2 string response data format.

26.1.3.1 :ALL?VXI:CONFigure:INFormation?:ALL?

When issued to a resource manager, this command returns the static information about alllogical addresses. If the command is received by a device which is not the resource manager,it returns the static information about the destination device followed by all of its immediateservants. The information is returned in the order specified in the response toVXI:CONFigure:LADDress?. (The information about multiple logical addresses will besemi-colon separated and follow the IEEE 488.2 response message format). The individualfields of the output are comma separated. This is an optional configuration command.

26.1.3.2 :VERBose?VXI:CONFigure:INFormation?:VERBose?

This command has the same functionality as VXI:CONFigure:INFormation?. However itreturns a quoted string indicating the device information for the selected device. The formatof this string is manufacturer specific. This command is intended to allow for a humanreadable form of the response to VXI:CONFigure:INFormation?. This is an optionalconfiguration command.

26.1.3.3 :ALL?VXI:CONFigure:INFormation?:ALL?

This command has the same functionality as VXI:CONFigure:INFormation:ALL?. Howeverit returns a semi-colon separated sequence of quoted strings indicating the deviceinformation for all devices. The format of each string is manufacturer specific. Thiscommand is intended to allow for a human readable form of the response toVXI:CONFigure:INFormation:ALL?. The format of this string is manufacturer specific.This is an optional configuration command.

26.1.4 :LADDress?VXI:CONFigure:LADDress?

When issued to a resource manager, the Logical ADDress command returns a commaseparated list of <NR1> which are the logical addresses of the devices in the system. Each<NR1> will be an integer in the range of 0 to 255 inclusive. The logical address of thedevice which is responding to the command will be the first item in the list. If the commandis received by a device other than the resource manager, then the response to the commandwill contain the logical address of the destination device followed by a list of the devices

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-6 VXI

which are immediate servants to the destination device. This is a required configurationcommand.

26.1.5 :NUMBer?VXI:CONFigure:NUMBer?

When issued to a resource manager, this command returns a <NR1> which is the number ofdevices in the system. If the command is received by a device which is not the resourcemanager, then the response to the command will contain the number of devices which areimmediate servants to the destination device including the destination device. For example, acommander with 3 servants would return a value of 4, or a resource manager for a system of4 devices would return a value of 5. The range of this <NR1> is 1 to 256 inclusive. This is arequired configuration command.

26.2 REGisterVXI:REGister

The node collects together the commands that interact with the VXI registers.

26.2.1 :READ? <register>VXI:REGister:READ?

This command returns the contents of the specified 16 bit register at the selected logicaladdress as a <NR1>. This is a required register access command. The register is specified asthe byte address of the desired register or as optionally the register name. It has values of alleven numbers from 0 to 62 inclusive (as a <numeric_value>) or the following (optional)words:

A24Low: A24 Pointer Low register (18)

A24High: A24 Pointer High register (16)

A32Low: A32 Pointer Low register (22)

A32High: A32 Pointer High register (20)

ATTRibute: Attribute register (8)

DHIGh: Data High register (12)

DLOW: Data Low register (14)

DTYPe: Device Type register (2)

ICONtrol: Interrupt Control register (28)

ID: ID register (0)

ISTatus: Interrupt Status register (26)

MODid: MODID register (8)

OFFSet: Offset register (6)

PROTocol: PROTocol register (8)

RESPonse: RESPonse register (10)

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-7

SNLow: Serial Number Low register (12)

SNHigh: Serial Number High register (10)

STATus: Status register (4)

SUBClass: Subclass register (30)

VNUMber: Version Number register (14)

26.2.1.1 :VERBose? <register>VXI:REGister:READ?:VERBose?

This command has the same functionality as VXI:REGister:READ?. However it returns aquoted string indicating the register contents for the selected device. The format of this stringis manufacturer specific. This command is intended to allow for a human readable form ofthe response to VXI:REG:READ? which could include additional decoding of bits inspecific registers. This is an optional register access command.

26.2.2 :WRITe (<numeric_value> | <register>), <data>VXI:REGister:WRITe

This command writes data to the specified register on the selected logical address. This is arequired register access command. The Data is a 16 bit value specified as a <numeric_value>in the range of -32768 to 32767. The register is specified as the byte address of the desiredregister or as optionally the register name. It has values of all even numbers from 0 to 62inclusive (expressed as a <numeric_value>) or the following (optional) words:

CONTrol: Control register (4)

DEXTended: Data Extended register (10)

DHIGh: Data High register (12)

DLOW: Data Low register (14)

ICONtrol: Interrupt Control register (28)

MODid: MODID register (8)

LADDress: Logical Address register (0)

OFFSet: Offset register (6)

SIGNal: Signal register (8)

26.3 :RESet?VXI:RESet?

This command resets the selected logical address. SYSFAIL generation is inhibited whilethe device is in the self test state. The command waits for five seconds or until the selecteddevice has indicated passed (whichever occurs first). If the device passes its self test, thenSYSFAIL generation will be re-enabled. If the device fails its self test, then SYSFAILgeneration will remain inhibited. The return value from this command is the state of theselected device after it has been reset. The command returns an <NR1> which is encoded as

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-8 VXI

follows: FAIL=0, PASS=2, READY=3. The state of the A24/A32 enable bit is not altered bythis command. This is a required register access command.

26.3.1 :VERBose?VXI:RESet?:VERBose?

This command has the same functionality as VXI:RESet?. However it returns a quoted stringindicating the state of the specified device. The format of this string is manufacturer specific.This is an optional register access command.

26.4 :SELect <logical_address>VXI:SELect

This command specifies the logical address which is to be used by all subsequent commandsin the VXI subsystem. Logical_address is specified as a <numeric_value> in the range of 0to 255. The query form returns the logical address as a <NR1> the value of -1 is reserved toindicate that no logical address has been selected. The *RST default value forlogical_address is that no logical address is selected. All other commands which require alogical_address to be selected will respond with an error -221, “Settings conflict” if nological address is selected.

26.5 :WSPRotocolVXI:WSPRotocol

This node collects together all the commands associated with the word serial protocol.

26.5.1 :COMMand

26.5.1.1 [:ANY] <data>VXI:WSPRotocol:COMMand:ANY

This command sends the specified word serial command to the selected logical address. Thedata field is a <numeric_value> or a non-decimal value which specifies the command to besent. The response of a word serial query which is sent with this command can be read withthe VXI:WSPRotocol:RESPonse? command. This is a required Word Serial Supportcommand.

26.5.1.2 :AHLine <hand_id>,<line_number>VXI:WSPRotocol:COMMand:AHLine

This command sends an Assign Handler Line command to the selected logical address. Thehand_id field has a value in the range of 1 to 7 inclusive, and line_number field has a valuein the range of 0 to 7 inclusive. They are both specified with <numeric_value>s or asnon-decimal values. The response to this command can be read with theVXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Support command.

26.5.1.3 :AILine <int_id>,<line_number>VXI:WSPRotocol:COMMand:AILine

This command sends an Assign Interrupter Line command to the selected logical address.The int_id field has a value in the range of 1 to 7 inclusive, and line_number field has avalue in the range of 0 to 7 inclusive. They are both specified with numeric_ values or asnon-decimal values. The response to this command can be read with theVXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-9

26.5.1.4 :AMControl <response_mask>VXI:WSPRotocol:COMMand:AMControl

This command sends an Asynchronous Mode Control command to the selected logicaladdress. The response mask field has a value in the range of 0 to 15 inclusive, and is definedin VXI rev. 1.3. It is specified with a <numeric_value> or as a non-decimal value. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

26.5.1.5 :ANOVXI:WSPRotocol:COMMand:ANO

This command sends an Abort Normal Operation command to the selected logical address.The response to this command can be read with the VXI:WSPRotocol:RESPonse?command. This is an optional Word Serial Support command.

26.5.1.6 :BAVailable <Boolean>,<byte>VXI:WSPRotocol:COMMand:BAVailable

This command sends a Byte Available command to the selected logical address. TheBoolean field selects whether the END bit is set in the command. The byte field has a valuein the range of 0 to 255 inclusive. It is specified with a <numeric_value> or as a non-decimalvalue. This is an optional Word Serial Support command.

26.5.1.7 :BNO <Boolean>VXI:WSPRotocol:COMMand:BNO

This command sends an Begin Normal Operation command to the selected logical address.The Boolean field selects whether the Top_level bit is set in the command. The response tothis command can be read with the VXI:WSPRotocol:RESPonse? command. This is anoptional Word Serial Support command.

26.5.1.8 :BRQVXI:WSPRotocol:COMMand:BRQ

This command sends an Byte Request command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

26.5.1.9 :CEVent <Boolean>,<event_number>VXI:WSPRotocol:COMMand:CEVent

This command sends a Control Event command to the selected logical address. The Booleanfield selects whether the Enable bit is set in the command. The event_number field has avalue in the range of 0 to 127 inclusive. It is specified with a <numeric_value> or as anon-decimal value. The response to this command can be read with theVXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Support command.

26.5.1.10 :CLRVXI:WSPRotocol:COMMand:CLR

This command sends an Clear command to the selected logical address. This is an optionalWord Serial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-10 VXI

26.5.1.11 :CLOCkVXI:WSPRotocol:COMMand:CLOCk

This command sends an Clear Lock command to the selected logical address. This is anoptional Word Serial Support command.

26.5.1.12 :CRESponse <response_mask>VXI:WSPRotocol:COMMand:CRESponse

This command sends a Control Response command to the selected logical address. Theresponse_mask field has a value in the range of 0 to 127 inclusive, and is defined in VXI rev.1.3. It is specified with a <numeric_value> or as a non-decimal value. The response to thiscommand can be read with the VXI:WSPRotocol:RESPonse? command. This is an optionalWord Serial Support command.

26.5.1.13 :ENOVXI:WSPRotocol:COMMand:ENO

This command sends an End Normal Operation command to the selected logical address.The response to this command can be read with the VXI:WSPRotocol:RESPonse?command. This is an optional Word Serial Support command.

26.5.1.14 :GDEVice <logical_address>VXI:WSPRotocol:COMMand:GDEVice

This command sends a Grant Device command to the selected logical address. Thelogical_address field has a value in the range of 0 to 255 inclusive. It is specified with a<numeric_value> or as a non-decimal value. This is an optional Word Serial Supportcommand.

26.5.1.15 :ICOMmander <logical_address>VXI:WSPRotocol:COMMand:ICOMmander

This command sends a Identify Commander command to the selected logical address. Thelogical_address field has a value in the range of 0 to 255 inclusive. It is specified with a<numeric_value> or as a non-decimal value. This is an optional Word Serial Supportcommand.

26.5.1.16 :RDEVice <logical_address>VXI:WSPRotocol:COMMand:RDEVice

This command sends a Release Device command to the selected logical address. Thelogical_address field has a value in the range of 0 to 255 inclusive. It is specified with a<numeric_value> or as a non-decimal value. The response to this command can be read withthe VXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Supportcommand.

26.5.1.17 :RHANdlersVXI:WSPRotocol:COMMand:RHANdlers

This command sends a Read Handlers command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-11

26.5.1.18 :RHLine <hand_id>VXI:WSPRotocol:COMMand:RHLine

This command sends a Read Handler Line command to the selected logical address. Thehand_id field has a value in the range of 1 to 7 inclusive. It is specified with a<numeric_value> or as a non-decimal value. The response to this command can be read withthe VXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Supportcommand.

26.5.1.19 :RILine <int_id>VXI:WSPRotocol:COMMand:RILine

This command sends a Read Interrupter Line command to the selected logical address. Theint_id field has a value in the range of 1 to 7 inclusive. It is specified with a<numeric_value> or as a non-decimal value. The response to this command can be read withthe VXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Supportcommand.

26.5.1.20 :RINTerrupterVXI:WSPRotocol:COMMand:RINTerrupter

This command sends a Read Interrupters command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

26.5.1.21 :RMODidVXI:WSPRotocol:COMMand:RMODid

This command sends a Read MODid command to the selected logical address. The responseto this command can be read with the VXI:WSPRotocol:RESPonse? command. This is anoptional Word Serial Support command.

26.5.1.22 :RPERrorVXI:WSPRotocol:COMMand:RPERror

This command sends a Read Protocol Error command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

26.5.1.23 :RPRotocolVXI:WSPRotocol:COMMand:RPRotocol

This command sends a Read Protocol command to the selected logical address. The responseto this command can be read with the VXI:WSPRotocol:RESPonse? command. This is anoptional Word Serial Support command.

26.5.1.24 :RSTBVXI:WSPRotocol:COMMand:RSTB

This command sends a Read Status Byte command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-12 VXI

26.5.1.25 :RSAReaVXI:WSPRotocol:COMMand:RSARea

This command sends a Read Servant Area command to the selected logical address. Theresponse to this command can be read with the VXI:WSPRotocol:RESPonse? command.This is an optional Word Serial Support command.

26.5.1.26 :SLModid <Boolean>,<MODID 6-0>VXI:WSPRotocol:COMMand:SLModid

This command sends a Set Lower MODid command to the selected logical address. TheBoolean field selects whether the Enable bit is set in the command. The MODID 6-0 fieldhas a value in the range of 0 to 127 inclusive. It is specified with a <NR1> or as anon-decimal value. The response to this command can be read with theVXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Support command.

26.5.1.27 :SLOCkVXI:WSPRotocol:COMMand:SLOCk

This command sends a Set Lock command to the selected logical address. This is an optionalWord Serial Support command.

26.5.1.28 :SUModid <Boolean>,<MODID 12-7>VXI:WSPRotocol:COMMand:SUModid

This command sends a Set Upper MODid command to the selected logical address. TheBoolean field selects whether the Enable bit is set in the command. The MODID 12-7 fieldhas a value in the range of 0 to 63 inclusive. It is specified with a <NR1> or as anon-decimal value. The response to this command can be read with theVXI:WSPRotocol:RESPonse? command. This is an optional Word Serial Support command.

26.5.1.29 :TRIGgerVXI:WSPRotocol:COMMand:TRIGger

This command sends a Trigger command to the selected logical address. This is an optionalWord Serial Support command.

26.5.2 :MESSageVXI:WSPRotocol:MESSage

This node collects together all the messages (as defined by VXI) of the word serial protocol.

26.5.2.1 :RECeive? <count>|<terminator>VXI:WSPRotocol:MESSage:RECeive?

This command receives a message from the selected logical address using both the wordserial protocol and the byte transfer protocol. The command will always terminate on theEnd bit being set. Additional termination options are on a specified number of bytes (count),or on a match to a particular terminator, (that is, LF, CRLF, END). The response is returnedas a string. This is a required Word Serial Support command.

26.5.2.2 :SEND <message_string> [,(END|NEND)]VXI:WSPRotocol:MESSage:SEND

This command sends the specified message string to the selected logical address. The stringis sent using the word serial protocol with the byte transfer protocol. The last byte of the

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-13

string is sent with the End bit set unless NEND is specified. This is a required Word SerialSupport command.

26.5.3 :QUERyVXI:WSPRotocol:QUERy

This node collects together all the queries (as defined by VXI) of the word serial protocol.

26.5.3.1 [:ANY]? <data>VXI:WSPRotocol:QUERy:ANY?

This command sends the specified word serial query to the selected logical address. The datafield is a <numeric_value> or a non-decimal value which specifies the query to be sent. Thereturned value is the response to the word serial query and is a <NR1>. This command obeysthe byte transfer protocol. This is a required Word Serial Support command.

26.5.3.2 :AHLine? <hand_id>,<line_number>VXI:WSPRotocol:QUERy:AHLine?

This command sends an Assign Handler Line command to the selected logical address. Thehand_id field has a value in the range of 1 to 7 inclusive, and line_number field has a valuein the range of 0 to 7 inclusive. They are both specified with <numeric_value>s or asnon-decimal values. The returned value is the response to the command and is a <NR1>.This is an optional Word Serial Support command.

26.5.3.3 :AILine? <int_id>,<line_number>VXI:WSPRotocol:QUERy:AILine?

This command sends an Assign Interrupter Line command to the selected logical address.The int_id field has a value in the range of 1 to 7 inclusive, and line_number field has avalue in the range of 0 to 7 inclusive. They are both specified with <numeric_value>s or asnon-decimal values. The returned value is the response to the command and is a <NR1>.This is an optional Word Serial Support command.

26.5.3.4 :AMControl? <response_mask>VXI:WSPRotocol:QUERy:AMControl?

This command sends an Asynchronous Mode Control command to the selected logicaladdress. The response_mask field has a value in the range of 0 to 15 inclusive, and is definedin VXI rev. 1.3. It is specified with a <numeric_value> or as a non-decimal value. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

26.5.3.5 :ANO?VXI:WSPRotocol:QUERy:ANO?

This command sends an Abort Normal Operation command to the selected logical address.The returned value is the response to the command and is a <NR1>. This is an optionalWord Serial Support command.

26.5.3.6 :BNO? <Boolean>VXI:WSPRotocol:QUERy:BNO?

This command sends an Begin Normal Operation command to the selected logical address.The Boolean field selects whether the Top_level bit is set in the command. The returned

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-14 VXI

value is the response to the command and is a <NR1>. This is an optional Word SerialSupport command.

26.5.3.7 :BRQ?VXI:WSPRotocol:QUERy:BRQ?

This command sends an Byte Request command to the selected logical address. The returnedvalue is the response to the command and is a <NR1>. This is an optional Word SerialSupport command.

26.5.3.8 :CEVent? <Boolean>,<event_number>VXI:WSPRotocol:QUERy:CEVent?

This command sends a Control Event command to the selected logical address. The Booleanfield selects whether the Enable bit is set in the command. The event_number field has avalue in the range of 0 to 127 inclusive. It is specified with a <numeric_value> or as anon-decimal value. The returned value is the response to the command and is a <NR1>. Thisis an optional Word Serial Support command.

26.5.3.9 :CRESponse? <response_mask>VXI:WSPRotocol:QUERy:CRESponse?

This command sends a Control Response command to the selected logical address. Theresponse_mask field has a value in the range of 0 to 127 inclusive, and is defined in VXI rev.1.3. It is specified with a numeric_value or as a non-decimal value. The returned value is theresponse to the command and is a <NR1>. This is an optional Word Serial Supportcommand.

26.5.3.10 :ENO?VXI:WSPRotocol:QUERy:ENO?

This command sends an End Normal Operation command to the selected logical address.The returned value is the response to the command and is a <NR1>. This is an optionalWord Serial Support command.

26.5.3.11 :RDEVice? <logical_address>VXI:WSPRotocol:QUERy:RDEVice?

This command sends a Release Device command to the selected logical address. Thelogical_address field has a value in the range of 0 to 255 inclusive. It is specified with a<numeric_value> or as a non-decimal value. The returned value is the response to thecommand and is a <NR1>. This is an optional Word Serial Support command.

26.5.3.12 :RHANdlers?VXI:WSPRotocol:QUERy:RHANdlers?

This command sends a Read Handlers command to the selected logical address. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

26.5.3.13 :RHLine? <hand_id>VXI:WSPRotocol:QUERy:RHLine?

This command sends a Read Handler Line command to the selected logical address. Thehand_id field has a value in the range of 1 to 7 inclusive. It is specified with a

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-15

<numeric_value> or as a non-decimal value. The returned value is the response to thecommand and is a <NR1>. This is an optional Word Serial Support command.

26.5.3.14 :RILine? <int_id>VXI:WSPRotocol:QUERy:RILine?

This command sends a Read Interrupter Line command to the selected logical address. Theint_id field has a value in the range of 1 to 7 inclusive. It is specified with a<numeric_value> or as a non-decimal value. The returned value is the response to thecommand and is a <NR1>. This is an optional Word Serial Support command.

26.5.3.15 :RINTerrupter?VXI:WSPRotocol:QUERy:RINTerrupter?

This command sends a Read Interrupters command to the selected logical address. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

26.5.3.16 :RMODid?VXI:WSPRotocol:QUERy:RMODid?

This command sends a Read MODid command to the selected logical address. The returnedvalue is the response to the command and is a <NR1>. This is an optional Word SerialSupport command.

26.5.3.17 :RPERror?VXI:WSPRotocol:QUERy:RPERror?

This command sends a Read Protocol Error command to the selected logical address. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

26.5.3.18 :RPRotocol?VXI:WSPRotocol:QUERy:RPRotocol?

This command sends a Read Protocol command to the selected logical address. The returnedvalue is the response to the command and is a <NR1>. This is an optional Word SerialSupport command.

26.5.3.19 :RSTB?VXI:WSPRotocol:QUERy:RSTB?

This command sends a Read Status Byte command to the selected logical address. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

26.5.3.20 :RSARea?VXI:WSPRotocol:QUERy:RSARea?

This command sends a Read Servant Area command to the selected logical address. Thereturned value is the response to the command and is a <NR1>. This is an optional WordSerial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-16 VXI

26.5.3.21 :SLModid? <Boolean>,<MODID 6-0>VXI:WSPRotocol:QUERy:SLModid?

This command sends a Set Lower MODid command to the selected logical address. TheBoolean field selects whether the Enable bit is set in the command. The MODID 6-0 fieldhas a value in the range of 0 to 127 inclusive. It is specified with a <numeric_value> or as anon-decimal value. The returned value is the response to the command and is a <NR1>. Thisis an optional Word Serial Support command.

26.5.3.22 :SUModid? <Boolean>,<MODID 12-7>VXI:WSPRotocol:QUERy:SUModid?

This command sends a Set Upper MODid command to the selected logical address. TheBoolean field selects whether the Enable bit is set in the command. The MODID 12-7 fieldhas a value in the range of 0 to 63 inclusive. It is specified with a <numeric_value> or as anon-decimal value. The returned value is the response to the command and is a <NR1>. Thisis an optional Word Serial Support command.

26.5.4 :RESPonse?VXI:WSPRotocol:RESPonse?

This command returns one word of data from the data low register on the selected logicaladdress. This command obeys the Byte transfer protocol. The data is returned as a <NR1>.This is a required Word Serial Support command.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


VXI 26-17

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


26-18 VXI

Index

A ABORt 2-5

HCOPy 10-4TRIGger Subsystem 24-12

:ACINPut:BIAS:CURRent 11-4INPut:BIAS:VOLTage 11-4MEASure 3-9SENSe:CURRent 18-25SENSe:POWer 18-64SENSe:VOLTage 18-84

ACCelerationSENSe:FUNCtion 18-50SOURce 19-5

ACCeleration SubsystemSOURce 19-5

:ACHannelSENSe:POWer 18-63

:ACQUireSOURce:CORRection:COLLect 19-12

:ACQuire STANdardSENSe:CORRection:COLLect 18-17

:ADDRessSYSTem:COMMunicate:GPIB 21-5SYSTem:COMMunicate:GPIB:RDEVice 21-5

:ADJustSOURce:PHASe 19-56

:AFCSENSe 18-38

:AHLineVXI:WSPRotocol:COMMand 26-9

:AHLine?VXI:WSPRotocol:QUERy 26-14

:AILineVXI:WSPRotocol:COMMand 26-9

:AILine?VXI:WSPRotocol:QUERy 26-14

:ALCSOURce:CURRent 19-18SOURce:POWer 19-61SOURce:VOLTage 19-94

:ALLCALCulate:MATH:EXPRession:DELete 4-22CALibration 5-2DISPlay:ANNotation 8-4HCOPy:ITEM 10-8

MEMory:DELete 13-7PROGram:SELected:DELete 16-2ROUTe:MODule:DELete 17-2ROUTe:OPEN 17-3ROUTe:PATH:DELete 17-4SENSe:FUNCtion:OFF 18-44SENSe:FUNCtion:ON 18-45SOURce:DM:THReshold 19-29TRACe | DATA:DELete 23-4TRIGger Subsystem:INITiate:CONTinuous 24-22TRIGger Subsystem:INITiate:IMMediate 24-22

:ALL ACSOURce:DM:COUPling 19-29

:ALL DCSOURce:DM:COUPling 19-29

:ALL GROundSOURce:DM:COUPling 19-29

:ALL?CALibration 5-2MEMory:CATalog 13-5MEMory:FREE 13-8VXI:CONFigure:HIERarchy? 26-4VXI:CONFigure:HIERarchy?:VERBose? 26-4VXI:CONFigure:INFormation? 26-6

:ALTernateSYSTem 21-3

AMSENSe:FUNCtion 18-50SOURce 19-6 - 19-9SOURce:LIST 19-49

AM SubsystemSENSe 18-4 - 18-5SOURce 19-6 - 19-9

:AMControlVXI:WSPRotocol:COMMand 26-10

:AMControl?VXI:WSPRotocol:QUERy 26-14

Amorphous SENSe ModelInstrument Model:Internal Routing 2-8

:AMPLitudeDISPlay:ANNotation 8-4MEASure 3-11SOURce:CURRent:LEVel:IMMediate 19-20SOURce:CURRent:LEVel:TRIGgered 19-21SOURce:CURRent:LIMit 19-21SOURce:MARKer 19-54SOURce:POWer:LEVel:IMMediate 19-63

Index - 1

SOURce:POWer:LEVel:TRIGgered 19-64SOURce:POWer:LIMit 19-64SOURce:RESistance:LEVel:IMMediate 19-75SOURce:RESistance:LEVel:TRIGgered 19-76SOURce:RESistance:LIMit 19-76SOURce:VOLTage:LEVel:IMMediate 19-96SOURce:VOLTage:LEVel:TRIGgered 19-97SOURce:VOLTage:LIMit 19-97

:ANGLeINPut:POSition:X 11-8INPut:POSition:Y 11-10INPut:POSition:Z 11-12OUTPut:POSition:X 15-6OUTPut:POSition:Y 15-8OUTPut:POSition:Z 15-10SOURce:DM:LEAKage 19-28SOURce:DM:QUADrature 19-29UNIT 25-1

:ANNotationDISPlay 8-4HCOPy:ITEM 10-8

:ANOVXI:WSPRotocol:COMMand 26-10

:ANO?VXI:WSPRotocol:QUERy 26-14

:ANYVXI:WSPRotocol:COMMand 26-9

:ANY?VXI:WSPRotocol:QUERy 26-14

:AOFFSOURce:MARKer 19-54

:APERtureCALCulate:GDAPerture 4-17CALCulate:SMOothing 4-23SENSe:CURRent:AC|:DC 18-25SENSe:FREQuency 18-37SENSe:POWer:AC|:DC 18-64SENSe:RESistance 18-68SENSe:SMOothing 18-73SENSe:VOLTage:AC|:DC 18-84

:APOWerCONTrol 6-1SOURce:LIST:CONTrol 19-50

:APRobeSOURce:LIST 19-49

ARM 2-5TRIGger Subsystem 24-12 - 24-20

:ARM-TRIGger ModelTRIGger Subsystem 24-1

:ARRayMEASure 3-7

ASCii 9-1, 9-3

:ASCii?MEMory:CATalog 13-5MEMory:FREE 13-8

:ATRiggerTRIGger Subsystem:TRIGger:SEQuence 24-23

:ATTenuationOUTPut Subsystem 15-3

:ATTenuationINPut 11-3SENSe:CURRent:AC|:DC 18-26SENSe:POWer:AC|:DC 18-64SENSe:VOLTage:AC|:DC 18-85SOURce:CURRent 19-18SOURce:POWer 19-61SOURce:VOLTage 19-94

:ATTRibutesDISPlay:WINDow:TEXT 8-9

:AUTOCALCulate 4-7, 4-12, 4-14, 4-18, 4-21, 4-25 - 4-26, 4-28, 4-31CALibration 5-2, 5-7DISPlay 8-11 - 8-12, 8-14 - 8-15HCOPy 10-13INPut:ATTenuation 11-3INPut:GAIN 11-6OUTPut:FILTer 15-3SENSe 18-4, 18-7, 18-10 - 18-11, 18-20, 18-26 - 18-28, 18-31, 18-36, 18-38 - 18-40, 18-59 - 18-62, 18-64 - 18-67, 18-69 - 18-70, 18-72, 18-79, 18-82, 18-85 - 18-87SENSe:ROSCillator:SOURce INTernal 19-80SOURce 19-18 - 19-20, 19-23, 19-43, 19-45, 19-50, 19-52, 19-61 - 19-62, 19-66, 19-73, 19-79, 19-85 - 19-86, 19-94 - 19-96, 19-99SYSTem 21-9, 21-33TRACe | DATA 23-5TRIGger Subsystem:ARM:SEQuence :LAYer:DELay 24-14TRIGger Subsystem:ARM:SEQuence :LAYer:LEVel 24-16TRIGger Subsystem:TRIGger:SEQuence :DELay 24-26TRIGger Subsystem:TRIGger:SEQuence :LEVel 24-28

:AVERage SubsystemCALCulate 4-6 - 4-8SENSe 18-6 - 18-9

:AWEightingINPut:FILTer 11-5SENSe:FILTer 18-35

:AXISDISPlay:WINDow:TRACe:GRATicule 8-11


Index - 2

B :BACKground

DISPlay:WINDow 8-6:BANDwidth

SOURce:POWer:ALC 19-62:BANDwidth

SENSe:DETector 18-30SOURce:CURRent:ALC 19-19SOURce:VOLTage:ALC 19-95

BANDwidth SubsystemSENSe 18-10 - 18-11

:BAUDSYSTem:COMM:SERial:RECeive 21-7SYSTem:COMM:SERial:TRANsmit 21-9

:BAVailableVXI:WSPRotocol:COMMand 26-10

:BEEPerSYSTem 21-3

:BIASINPut 11-3SENSe:MIXer 18-60

BINary 9-2 - 9-3:BINary?

MEMory:CATalog 13-5MEMory:FREE 13-8

:BINertiaCALibration 5-2 - 5-3

:BIT STATus 20-3

:BITSSYSTem:COMM:SERial:RECeive 21-7SYSTem:COMM:SERial:TRANsmit 21-9

:BLOWerCONTrol 6-2SOURce:LIST:CONTrol 19-50

:BNOVXI:WSPRotocol:COMMand 26-10

:BNO?VXI:WSPRotocol:QUERy 26-14

:BORDerFORMat 9-1

:BOTTomDISPlay:WINDow:TRACe:Y:SCALe 8-14

:BRAKeCONTrol 6-2

:BRIGhtnessDISPlay 8-4

:BRQVXI:WSPRotocol:COMMand 26-10

:BRQ?VXI:WSPRotocol:QUERy 26-15

:BURSt:MEASure:FREQuency 3-9

BWIDthSENSe:DETector 18-30SOURce:CURRent:ALC 19-19SOURce:POWer:ALC 19-62SOURce:VOLTage:ALC 19-95

:BWIDth SubsystemSENSe 18-10 - 18-11

C CALCulate

Instrument Model:Measurement Function 2-4Instrument Model:Signal Generation 2-5

CALCulate Subsystem 4-1 - 4-32CALibration Subsystem 5-1 - 5-10:CAPability?

SYSTem 21-4:CARM

SENSe:FILTer 18-35:CATalog

CALCulate:MATH:EXPRession 4-21MEMory 13-4SYSTem:KEY 21-32

:CATalog?MMEMory 14-2PROGram 16-2ROUTe:MODule 17-2ROUTe:PATH 17-3TRACe | DATA 23-2

:CCIRSENSe:FILTer 18-35

:CCITtSENSe:FILTer 18-34

:CDFunctionSENSe:FUNCtion:VOLTage 18-56

:CDIRectoryMMEMory 14-3

:CENTerCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-28CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-26DISPlay:WINDow:TRACe:X:SCALe 8-12SENSe:FREQuency 18-37SOURce:CURRent 19-19SOURce:FREQuency 19-43SOURce:POWer 19-62SOURce:RESistance 19-77SOURce:VOLTage 19-95


Index - 3

:CENTronicsSYSTem:COMMunicate 21-4

:CEVentVXI:WSPRotocol:COMMand 26-10

:CEVent?VXI:WSPRotocol:QUERy 26-15

:CHECkSYSTem:COMM:SERial:RECeive 21-8

:CLEanCONTrol 6-3

:CLEarCALCulate:AVERage 4-6CALCulate:LIMit 4-21DISPlay:WINDow:GRAPhics 8-7DISPlay:WINDow:TEXT 8-9MEMory 13-6OUTPut:PROTection 15-12SENSe:CURRent:AC|:DC:PROTection 18-26SENSe:POWer:AC|:DC:PROTection 18-65SENSe:VOLTage:AC|:DC:PROTection 18-85SOURce:CURRent:PROTection 19-23SOURce:POWer:PROTection 19-66SOURce:RESistance:PROTection 19-77SOURce:VOLTage:PROTection 19-99

:CLIMitsCALCulate 4-9

:CLOCkSOURce:DM 19-30SOURce:DM:THReshold 19-29VXI:WSPRotocol:COMMand 26-11

:CLOCk ACSOURce:DM:COUPling 19-29

:CLOCk DCSOURce:DM:COUPling 19-29

:CLOCk GROundSOURce:DM:COUPling 19-29

Cloned ModelsInstrument Model:Internal Routing 2-7

:CLOSeMMEMory 14-3ROUTe 17-1

:CLRVXI:WSPRotocol:COMMand 26-10

:CMAPDISPlay 8-4HCOPy:DEVice 10-5

:CMESsageSENSe:FILTer 18-34

:COAXSENSe:CORRection:RVELocity 18-22SOURce:CORRection:RVELocity 19-15

:COHerence

SENSe:FUNCtion:POWer 18-54:COLLect

SENSe:CORRection 18-17SOURce:CORRection 19-12

:COLorDISPlay:CMAP 8-4DISPlay:WINDow:BACKground 8-6DISPlay:WINDow:GRAPhics 8-7DISPlay:WINDow:TEXT 8-9DISPlay:WINDow:TRACe 8-10HCOPy:DEVice 10-6HCOPy:DEVice:CMAP 10-5HCOPy:ITEM:ANNotation 10-8HCOPy:ITEM:LABel 10-9HCOPy:ITEM:MENU 10-10HCOPy:ITEM:TDSTamp 10-11HCOPy:ITEM:WINDow:TEXT 10-12HCOPy:ITEM:WINDow:TRACe 10-12HCOPy:ITEM:WINDow:TRACe:GRATicule 10-12

COMBine SubsystemSOURce 19-10

:COMMandVXI:WSPRotocol 26-9

:Command ErrorSYSTem:ERRor? 21-15

:COMMunicateSYSTem 21-4 - 21-10

:COMPressorCONTrol 6-2SOURce:LIST:CONTrol 19-50

CONCentration SubsystemSENSe 18-12 - 18-14

:CONCurrentSENSe:FUNCtion 18-43SOURce:LIST 19-49

:CONDitionMEMory:TABLe 13-10SENSe:FUNCtion 18-51

CONDition SubsystemSENSe 18-15

:CONDition?STATus 20-3, 20-7

CONFigureMeasurement Instructions 3-2VXI 26-3

:CONTinuousTRIGger Subsystem:INITiate 24-21

:CONTrastDISPlay 8-5

:CONTrolCALCulate:LIMit 4-19


Index - 4

SOURce:LIST 19-50SYSTem:COMM:SERial 21-6

:CONTrol , ALWaysTRACe | DATA:FEED 23-4

:CONTrol NEVerTRACe | DATA:FEED 23-4

:CONTrol NEXTTRACe | DATA:FEED 23-4

:CONTrol OCONditionTRACe | DATA:FEED 23-4

CONTrol Subsystem 6-1 - 6-6:COPY

MEMory 13-6MMEMory 14-3TRACe | DATA 23-2

CORRection SubsystemSENSe 18-16 - 18-24SOURce 19-11 - 19-16

:COUNtCALCulate:AVERage 4-7CALCulate:TRANsform:HISTogram 4-24SENSe:AVERage 18-7SENSe:LIST 18-58SENSe:SWEep 18-78SOURce:LIST 19-50SOURce:PULSe 19-73SOURce:SWEep 19-87TRIGger Subsystem:ARM:SEQuence :LAYer 24-14TRIGger Subsystem:TRIGger:SEQuence 24-24

:COUNt?SENSe:FUNCtion:OFF 18-44SENSe:FUNCtion:ON 18-45

:COUPleINSTrument 12-2

:COUPlingOUTPut Subsystem 15-3SOURce:DM 19-29

:COUPling ACINPut 11-4SOURce:AM 19-6SOURce:AM:EXTernal 19-7SOURce:FM 19-32SOURce:FM:EXTernal 19-33SOURce:PM 19-58SOURce:PM:EXTernal 19-59TRIGger Subsystem:ARM:SEQuence :LAYer 24-14TRIGger Subsystem:TRIGger:SEQuence 24-24

:COUPling DCINPut 11-4SOURce:AM 19-6

SOURce:AM:EXTernal 19-7SOURce:FM 19-32SOURce:FM:EXTernal 19-33SOURce:PM 19-58SOURce:PM:EXTernal 19-59TRIGger Subsystem:ARM :SEQuence:LAYer 24-14TRIGger Subsystem:TRIGger:SEQuence 24-24

:COUPling GROundINPut 11-4SOURce:AM 19-6SOURce:AM:EXTernal 19-7SOURce:FM 19-32SOURce:FM:EXTernal 19-33SOURce:PM 19-58SOURce:PM:EXTernal 19-59

:COVerCONTrol 6-2

:CPOintDISPlay:WINDow:TRACe:R:SCALe 8-15

:CPONSYSTem 21-11

:CREFerenceCALCulate:FORMat:UPHase 4-17

:CRESponseVXI:WSPRotocol:COMMand 26-11

:CRESponse?VXI:WSPRotocol:QUERy 26-15

:CROSsSENSe:FUNCtion:POWer 18-54

:CSETSENSe:CORRection 18-18SOURce:CORRection 19-12

:CSIZeDISPlay:WINDow:GRAPhics 8-7DISPlay:WINDow:TEXT 8-10

:CTYPe?SYSTem 21-11

:CURRent:MEASure 3-8INPut:BIAS 11-3MEMory:TABLe 13-11SENSe:FUNCtion 18-51SOURce 19-17 - 19-25SOURce:LIST 19-50

CURRent SubsystemSENSe 18-25 - 18-29SOURce 19-17 - 19-25

:CURRent, :POWer, and :VOLTageUNIT 25-1

:CUTHCOPy:ITEM 10-8


Index - 5

:CWSENSe:FREQuency 18-38SOURce:FREQuency 19-43

D :DATA 23-1 - 23-6

CALCulate:LIMit:CONTrol 4-19CALCulate:LIMit:LOWer 4-20CALCulate:LIMit:UPPer 4-19CALibration 5-4DISPlay:WINDow:TEXT 8-10FORMat 9-1HCOPy:ITEM:TDSTamp 10-11MEMory 13-7MMEMory 14-3SOURce:DM:THReshold 19-29TRACe | DATA 23-2

:DATA ACSOURce:DM:COUPling 19-29

Data and Control FlowInstrument Model:Internal Routing 2-6

:DATA DCSOURce:DM:COUPling 19-29

:DATA GROundSOURce:DM:COUPling 19-29

DATA SubsystemSENSe 18-42 - 18-57

:DATA?CALCulate 4-10CALCulate:CLIMits:FLIMits 4-9CALCulate:LIMit:REPort 4-20HCOPy 10-4HCOPy:ITEM:ALL 10-8HCOPy:ITEM:CUT 10-9HCOPy:ITEM:FFEEd 10-9HCOPy:ITEM:LABel 10-10HCOPy:ITEM:MENU 10-10HCOPy:ITEM:WINDow 10-11HCOPy:ITEM:WINDow:TEXT 10-12HCOPy:ITEM:WINDow:TRACe 10-12HCOPy:ITEM:WINDow:TRACe :GRATicule 10-12HCOPy:SDUMp 10-15SENSe:FUNCtion & DATA 18-42

:DATESYSTem 21-11

:DCINPut:BIAS:CURRent 11-4INPut:BIAS:VOLTage 11-4MEASure 3-9SENSe:CURRent 18-25

SENSe:POWer 18-64SENSe:VOLTage 18-84

:DCYCle:MEASure 3-14SOURce:PULSe 19-71

:DEFaultDISPlay:CMAP 8-4HCOPy:DEVice:CMAP 10-6PROGram:SELected 16-3

:DEFineCALCulate:MATH:EXPRession 4-22MEMory Subsystem:TABLe 13-14PROGram:EXPLicit 16-4PROGram:SELected 16-2ROUTe:MODule 17-2ROUTe:PATH 17-3SYSTem:KEY 21-32TRACe | DATA 23-3TRIGger Subsystem:ARM:SEQuence 24-12TRIGger Subsystem:TRIGger:SEQuence 24-24

:DELayOUTPut:PROTection 15-12SOURce:PULSe 19-72SOURce:PULSe:DOUBle 19-72SYSTem:COMMunicate:SERial:TRANsmit 21-9TRIGger Subsystem:ARM :SEQuence:LAYer 24-14TRIGger Subsystem:TRIGger:SEQuence 24-25

:DELeteCALCulate:MATH:EXPRession 4-22MEMory 13-7MMEMory 14-3PROGram:EXPLicit 16-5PROGram:SELected 16-2ROUTe:MODule 17-2ROUTe:PATH 17-4SYSTem:KEY 21-32TRACe | DATA 23-4

:DEMPhasisSENSe:FILTer 18-34

:DEPThSENSe:AM 18-4SOURce:AM 19-6SOURce:LIST:AM 19-49

:DERivativeCALCulate 4-10

DESTination 2-3DESTination?

HCOPy 10-4:DETector EXTernal

SENSe:CURRent 18-29SENSe:POWer 18-67


Index - 6

SENSe:VOLTage 18-88:DETector INTernal

SENSe:CURRent 18-29SENSe:POWer 18-67SENSe:VOLTage 18-88

DETector SubsystemSENSe 18-30 - 18-31

:DEViationSENSe:FM 18-36SENSe:PM 18-62SOURce:FM 19-32SOURce:PM 19-57

:DEViceHCOPy 10-5 - 10-6

:Device-Specific ErrorSYSTem:ERRor? 21-25

DIAGnostic Subsystem 7-1 - 7-2Digital Modulation Subsystem

SOURce 19-26 - 19-31:DIMensions

HCOPy:PAGE 10-13:DINTerchange

FORMat 9-2MMEMory:LOAD and :STORe 14-4

:DIRection DOWNINPut:POSition:X:ANGLe 11-8INPut:POSition:X:DISTance 11-9INPut:POSition:Y:ANGLe 11-10INPut:POSition:Y:DISTance 11-11INPut:POSition:Z:ANGLe 11-12INPut:POSition:Z:DISTance 11-13OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11SENSe:CURRent:AC|:DC 18-27SENSe:LIST 18-58SENSe:POWer:AC|:DC:RANGe:AUTO 18-66SENSe:RESistance:RANGe:AUTO 18-69SENSe:SWEep 18-78SENSe:VOLTage:AC|:DC 18-86SOURce:LIST 19-51SOURce:SWEep 19-86

:DIRection EITHerSENSe:CURRent:AC|:DC 18-27SENSe:POWer:AC|:DC:RANGe:AUTO 18-66SENSe:RESistance:RANGe:AUTO 18-69SENSe:VOLTage:AC|:DC 18-86

:DIRection UPINPut:POSition:X:ANGLe 11-8

INPut:POSition:X:DISTance 11-9INPut:POSition:Y:ANGLe 11-10INPut:POSition:Y:DISTance 11-11INPut:POSition:Z:ANGLe 11-12INPut:POSition:Z:DISTance 11-13OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11SENSe:CURRent:AC|:DC 18-27SENSe:LIST 18-58SENSe:POWer:AC|:DC:RANGe:AUTO 18-66SENSe:RESistance:RANGe:AUTO 18-69SENSe:SWEep 18-78SENSe:VOLTage:AC|:DC 18-86SOURce:LIST 19-51SOURce:SWEep 19-86

DISPlay Subsystem 8-1 - 8-16:DISTance

CALCulate:TRANsform 4-27INPut:POSition:X 11-9INPut:POSition:Y 11-11INPut:POSition:Z 11-13OUTPut:POSition:X 15-7OUTPut:POSition:Y 15-9OUTPut:POSition:Z 15-11SENSe:CORRection:EDELay 18-19SENSe:FUNCtion 18-52SOURce:CORRection:EDELay 19-14

DISTance SubsystemSENSe 18-32

:DISTortionSENSe:FUNCtion:POWer 18-50, 18-52 - 18-54

DMSOURce 19-26 - 19-31

DM SubsystemSOURce 19-26 - 19-31

:DMODe PARallelSOURce:DM 19-30

:DMODe SERialSOURce:DM 19-30

:DNUMber?VXI:CONFigure 26-3

:DOUBleSOURce:PULSe 19-72

:DRAWDISPlay:WINDow:GRAPhics 8-8

:DTR IBFullSYSTem:COMM:SERial:CONTrol 21-6

:DTR OFF


Index - 7

SYSTem:COMM:SERial:CONTrol 21-6:DTR ON

SYSTem:COMM:SERial:CONTrol 21-6:DTR STANdard

SYSTem:COMM:SERial:CONTrol 21-6:DURation

CONTrol 6-3:DWELl

SENSe:LIST 18-58SENSe:SWEep 18-78SOURce:LIST 19-51SOURce:SWEep 19-85

E :EBENch

CONTrol 6-3:ECL

TRIGger Subsystem:ARM :SEQuence:LAYer 24-15TRIGger Subsystem:TRIGger:SEQuence 24-26

:ECLTrgOUTPut Subsystem 15-12

:ECOuntTRIGger Subsystem:ARM :SEQuence:LAYer 24-15TRIGger Subsystem:TRIGger:SEQuence 24-26

:EDELaySENSe:CORRection 18-19SOURce:CORRection 19-14

:ENABleDISPlay 8-5STATus 20-3, 20-7

:ENOVXI:WSPRotocol:COMMand 26-11

:ENO?VXI:WSPRotocol:QUERy 26-15

:Error/Event numbersSYSTem:ERRor? 21-14

:The Error/Event QueueSYSTem:ERRor? 21-13

:ERRor?SYSTem 21-11 - 21-27

:Error/Event numbersSYSTem:ERRor? 21-14

:EVENt?STATus 20-4, 20-7

<event_handle>Instrument Model:Internal Routing 2-14

:EXCHangeMEMory 13-7

:EXECute

PROGram:EXPLicit 16-5PROGram:SELected 16-2

:Execution ErrorSYSTem:ERRor? 21-19

:Expanded Capability Trigger ModelTRIGger Subsystem 24-5 - 24-11

:EXPLicitPROGram 16-4 - 16-6

EXPonentialCALCulate:AVERage:TCONtrol 4-7CALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-27SENSe:WINDow:TYPE 18-89

:EXPRessionCALCulate:MATH 4-21

:EXTernalOUTPut:FILTer 15-3SENSe:ROSCillator 18-71, 19-80SOURce:AM 19-6SOURce:FM 19-32SOURce:PM 19-59SOURce:PULM 19-68

F :FAIL?

CALCulate:CLIMits 4-9CALCulate:LIMit 4-20

:FALLMEASure 3-13

:FCOunt?CALCulate:LIMit 4-20

:FCUToffSENSe:CORRection:RVELocity 18-22SOURce:CORRection:RVELocity 19-15

FEEDCALCulate 4-10DISPlay:WINDow:TEXT 8-10DISPlay:WINDow:TRACe 8-10HCOPy 10-7Instrument Model:Internal Routing 2-9MMEMory 14-4SYSTem:COMM:SERial 21-7SYSTem:COMMunicate:CENTronics 21-5SYSTem:COMMunicate:GPIB:RDEVice 21-5TRACe | DATA 23-4

FEED ExceptionsInstrument Model:Internal Routing :Lamina and Cloned Models 2-8


Index - 8

FEEDs from CALCulate Sub-BlocksInstrument Model:Internal Routing 2-12

FERRorSENSe:FUNCtion 18-52

FETChMeasurement Instructions 3-3

:FFEedHCOPy:ITEM 10-9

:FIELdTRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo 24-19TRIGger Subsystem:TRIGger:SEQuence :VIDeo 24-31

:FILTerCALCulate 4-11 - 4-14INPut 11-5OUTPut Subsystem 15-3SOURce:DM 19-27TRIGger Subsystem:ARM:SEQuence :LAYer 24-15TRIGger Subsystem:TRIGger:SEQuence 24-26

FILTer SubsystemSENSe 18-33 - 18-35

:FIXedSENSe:FREQuency 18-38SOURce:FREQuency 19-43

:FLIMitsCALCulate:CLIMits 4-9

FMSENSe:FUNCtion 18-52

FM SubsystemSENSe 18-36SOURce 19-32 - 19-34

:FORCeCALCulate:FILTer:GATE:FREQuency 4-15CALCulate:FILTer:GATE:TIME 4-13CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-27SENSe:FUNCtion 18-52SENSe:WINDow:TYPE 18-89

FORCe SubsystemSOURce 19-35 - 19-42

FORMatCALCulate 4-15 - 4-16Instrument Model 2-5SOURce:DM 19-27TRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo 24-20TRIGger Subsystem:TRIGger:SEQuence :VIDeo:FIELd 24-31

FORMat Subsystem 9-1 - 9-4

:FRAMeDISPlay:WINDow:TRACe:GRATicule 8-11SOURce:DM 19-30

:FREEMEMory 13-8

:FREE?TRACe | DATA 23-5

:FREQuency:MEASure 3-9CALCulate:FILTer:GATE 4-13CALCulate:TRANsform 4-29DISPlay:ANNotation 8-4INPut:FILTer:HPASs 11-5INPut:FILTer:LPASs 11-5MEMory Subsystem:TABLe 13-15OUTPut:FILTer:HPASs 15-4OUTPut:FILTer:LPASs 15-4SENSe:FILTer:HPASs 18-34SENSe:FILTer:LPASs 18-33SENSe:FUNCtion 18-52SENSe:LIST 18-59SENSe:ROSCillator:EXTernal 18-71, 19-80SENSe:ROSCillator:INTernal 18-71, 19-80SOURce:AM:INTernal 19-7SOURce:FM:INTernal 19-33SOURce:LIST 19-51SOURce:MARKer 19-54SOURce:PM:INTernal 19-59SOURce:PULM:INTernal 19-69SYSTem:BEEPer 21-3TRIGger Subsystem:ARM:SEQuence :LAYer:FILTer:HPASs 24-15TRIGger Subsystem:ARM:SEQuence :LAYer:FILTer:LPASs 24-15TRIGger Subsystem:TRIGger:SEQuence :FILTer:HPASs 24-26TRIGger Subsystem:TRIGger:SEQuence :FILTer:LPASs 24-27

FREQuency SubsystemSENSe 18-37 - 18-41SOURce 19-43 - 19-46

:FRESistance:MEASure 3-8SENSe:FUNCtion 18-53

FRESistance SubsystemSENSe 18-68 - 18-70

FRONtSENSe:FUNCtion:SPEed 18-55

:FSENsorCALibration 5-7

:FTIMeMEASure 3-13


Index - 9

:FULLSENSe:FREQuency:SPAN 18-40SOURce:CURRent:SPAN 19-24SOURce:FREQuency:SPAN 19-45SOURce:POWer:SPAN 19-67SOURce:RESistance:SPAN 19-78SOURce:VOLTage:SPAN 19-100

<function>Measurement Instructions 3-5SENSe 18-43SENSe:DETector 18-30

FUNCtion & DATA SubsystemSENSe 18-42 - 18-57

FUNCtion SubsystemSOURce 19-47

:<function_name>SENSe:FUNCtion 18-48

Fundamental Measurement LayerMEASure 3-7

G :GAIN

INPut 11-6SENSe:CORRection 18-20SOURce:CORRection 19-13

:GATECALCulate:FILTer 4-11

:GDAPertureCALCulate 4-17

:GDEViceVXI:WSPRotocol:COMMand 26-11

:GENeration ANALogSENSe:SWEep 18-79SOURce:SWEep 19-86

:GENeration CONCurrentSOURce:LIST 19-51

:GENeration DCONcurrentSOURce:LIST 19-51

:GENeration DSEQuenceSOURce:LIST 19-51

:GENeration SEQuenceSOURce:LIST 19-51

:GENeration STEPpedSENSe:SWEep 18-79SOURce:SWEep 19-86

:GEOMetryDISPlay:WINDow 8-6

:GPIBSYSTem:COMMunicate 21-5

:GRAPhicsDISPlay:WINDow 8-7

:GRATiculeDISPlay:WINDow:TRACe 8-11HCOPy:ITEM:WINDow:TRACe 10-12

:GRIDDISPlay:WINDow:TRACe:GRATicule 8-11

:GUARdINPut 11-6

H :HARMonic

SENSe:MIXer 18-60HCOPy Subsystem 10-1 - 10-16:HEADers?

SYSTem:HELP 21-28:HELP

SYSTem 21-28 - 21-31HEXadecimal 9-2 - 9-3:HIERarchy?

VXI:CONFigure 26-3:HIGH

INPut:POSition:X:ANGLe:LIMit 11-8INPut:POSition:X:DISTance:LIMit 11-9INPut:POSition:Y:ANGLe:LIMit 11-10INPut:POSition:Y:DISTance:LIMit 11-11INPut:POSition:Z:ANGLe:LIMit 11-12INPut:POSition:Z:DISTance:LIMit 11-13MEASure 3-12OUTPut:POSition:X:ANGLe:LIMit 15-6OUTPut:POSition:X:DISTance:LIMit 15-7OUTPut:POSition:Y:ANGLe:LIMit 15-8OUTPut:POSition:Y:DISTance:LIMit 15-9OUTPut:POSition:Z:ANGLe:LIMit 15-10OUTPut:POSition:Z:DISTance:LIMit 15-11SOURce:CURRent:LEVel:IMMediate 19-20SOURce:CURRent:LEVel:TRIGgered 19-21SOURce:CURRent:LIMit 19-22SOURce:POWer:LEVel:IMMediate 19-63SOURce:POWer:LEVel:TRIGgered 19-64SOURce:POWer:LIMit 19-65SOURce:RESistance:LEVel:IMMediate 19-75SOURce:RESistance:LEVel:TRIGgered 19-76SOURce:RESistance:LIMit 19-76SOURce:VOLTage:LEVel:IMMediate 19-96SOURce:VOLTage:LEVel:TRIGgered 19-97SOURce:VOLTage:LIMit 19-98

:HISTogramCALCulate:TRANsform 4-24SENSe:FUNCtion:VOLTage 18-56

:HOLDSENSe:FREQuency:SPAN 18-40SOURce:CURRent:SPAN 19-24


Index - 10

SOURce:FREQuency:SPAN 19-45SOURce:POWer:SPAN 19-67SOURce:RESistance:SPAN 19-78SOURce:VOLTage:SPAN 19-100

:HOLD DCYCleSOURce:PULSe 19-71

:HOLD WIDThSOURce:PULSe 19-71

:HOLDoffTRIGger Subsystem:TRIGger:SEQuence 24-27

:HORizontalINPut:POLarization 11-7OUTPut:POLarization 15-5

:HPASsINPut:FILTer 11-5OUTPut:FILTer 15-4SENSe:FILTer 18-33TRIGger Subsystem:ARM :SEQuence:LAYer:FILTer 24-15TRIGger Subsystem:TRIGger :SEQuence:FILTer 24-26

:HPGLDISPlay:WINDow:GRAPhics 8-8

:HSLDISPlay:CMAP:COLor 8-5HCOPy:DEVice:CMAP:COLor 10-5

:HYSTeresisSOURce:PULM:EXTernal 19-68TRIGger Subsystem:ARM:SEQuence :LAYer 24-16TRIGger Subsystem:TRIGger:SEQuence 24-27

I :I INVerted

SOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:I<n> NORMalSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:ICLock INVertedSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:ICLock NORMalSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:ICOMmanderVXI:WSPRotocol:COMMand 26-11

:ICORrectionSOURce:DM:FILTer 19-27

:IDLECONTrol 6-3

:IDLE StateTRIGger Subsystem:Model Layers 24-2

:IDRawDISPlay:WINDow:GRAPhics 8-8

:IMMediateCALCulate 4-18CALCulate:LIMit:CLEar 4-21HCOPy 10-7 - 10-13, 10-15INPut:POSition:X:ANGLe 11-8INPut:POSition:X:DISTance 11-9INPut:POSition:Y:ANGLe 11-10INPut:POSition:Y:DISTance 11-11INPut:POSition:Z:ANGLe 11-12INPut:POSition:Z:DISTance 11-13OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11OUTPut:TTLTrg|:ECLTrg 15-12SOURce:CURRent:LEVel 19-19SOURce:POWer:LEVel 19-62SOURce:RESistance:LEVel 19-75SOURce:VOLTage:LEVel 19-95SYSTem:BEEPer 21-4TRIGger Subsystem:ARM:SEQuence :LAYer 24-16TRIGger Subsystem:INITiate 24-22TRIGger Subsystem:TRIGger:SEQuence 24-27

:IMOVeDISPlay:WINDow:GRAPhics 8-8

:IMPedanceINPut 11-6OUTPut Subsystem 15-5SENSe:CORRection 18-19SOURce:AM:EXTernal 19-7SOURce:FM:EXTernal 19-33SOURce:PM:EXTernal 19-59SOURce:PULM:EXTernal 19-68

:INFormation?VXI:CONFigure 26-4

:INITializeMMEMory 14-4

INITiate 2-5CONTrol 6-3TRIGger Subsystem 24-21 - 24-22

:InitiatedTRIGger Subsystem:Model Layers 24-2

INPut 11-1 - 11-14Instrument Model:Measurement Function 2-3SENSe:CORRection:IMPedance 18-19


Index - 11

SENSe:CORRection:LOSS 18-20Instrument Model 2-1 - 2-14INSTrument Subsystem 12-1 - 12-4INTeger 9-2:INTegral

CALCulate 4-18:INTernal

SENSe:ROSCillator 18-71, 19-80SOURce:AM 19-7SOURce:FM 19-33SOURce:PM 19-59SOURce:PULM 19-69

Internal RoutingInstrument Model 2-5 - 2-14

:INTerpolateCALCulate:LIMit 4-21

Introduction 1-1 - 1-2:IQRatio

SOURce:DM 19-28:ITEM

HCOPy 10-7 - 10-12

K :KBESsel

CALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-27SENSe:WINDow:TYPE 18-89

:KEYDISPlay:MENU 8-6SYSTem 21-32

:KLOCkSYSTem 21-33

L :LABel

DISPlay:WINDow:GRAPhics 8-8DISPlay:WINDow:TRACe:R 8-15DISPlay:WINDow:TRACe:X 8-12DISPlay:WINDow:TRACe:Y 8-13HCOPy:ITEM 10-9

:LADDress?VXI:CONFigure 26-6

Lamina and Cloned ModelsInstrument Model:Internal Routing 2-7

:LANGuageHCOPy:DEVice 10-6SYSTem 21-33

:LAYerTRIGger Subsystem:ARM:SEQuence 24-14

:LAYer NomenclatureTRIGger Subsystem :Expanded Capability Trigger Model 24-6

:LDIRectionDISPlay:WINDow:GRAPhics 8-8

:LEADingSOURce:PULSe:TRANsition 19-72

:LEAKageSOURce:DM 19-28

:LEFTDISPlay:WINDow:TRACe:X:SCALe 8-12

:LENGthHCOPy:PAGE 10-14

:LEVelOUTPut:TTLTrg|:ECLTrg 15-13SENSe:CONDition 18-15SENSe:CURRent:AC|:DC:PROTection 18-26SENSe:POWer:AC|:DC:PROTection 18-65SENSe:VOLTage:AC|:DC:PROTection 18-85SOURce:CURRent 19-19SOURce:CURRent:PROTection 19-23SOURce:POWer 19-62SOURce:POWer:PROTection 19-65SOURce:PULM:EXTernal 19-68SOURce:RESistance 19-75SOURce:RESistance:PROTection 19-77SOURce:VOLTage 19-95SOURce:VOLTage:PROTection 19-99TRIGger Subsystem:ARM:SEQuence :LAYer 24-16TRIGger Subsystem:TRIGger:SEQuence 24-28

:LFRequencySYSTem 21-33

:LIFTCONTrol 6-3

:LIMitCALCulate 4-18 - 4-20INPut:POSition:X:ANGLe 11-8INPut:POSition:X:DISTance 11-9INPut:POSition:Y:ANGLe 11-10INPut:POSition:Y:DISTance 11-11INPut:POSition:Z:ANGLe 11-12INPut:POSition:Z:DISTance 11-13OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11SENSe:MIXer:BIAS 18-60


Index - 12

SOURce:CURRent 19-21SOURce:POWer 19-64SOURce:RESistance 19-76SOURce:VOLTage 19-97

:LINETRACe | DATA:DATA 23-3TRIGger Subsystem:ARM :SEQuence:LAYer:VIDeo 24-20TRIGger Subsystem:TRIGger :SEQuence:VIDeo 24-32

:LINKTRIGger Subsystem:ARM :SEQuence:LAYer 24-17TRIGger Subsystem:TRIGger:SEQuence 24-28

:LINK CENTerDISPlay:WINDow:TRACe:X:SCALe:PDIV 8-13SENSe:FREQuency:SPAN 18-40SOURce:CURRent:SPAN 19-24SOURce:FREQuency:SPAN 19-45SOURce:POWer:SPAN 19-67SOURce:RESistance:SPAN 19-78SOURce:VOLTage:SPAN 19-100

:LINK LEFTDISPlay:WINDow:TRACe:X:SCALe:PDIV 8-13

:LINK RIGHtDISPlay:WINDow:TRACe:X:SCALe:PDIV 8-13

:LINK STARtSENSe:FREQuency:SPAN 18-40SOURce:CURRent:SPAN 19-24SOURce:FREQuency:SPAN 19-45SOURce:POWer:SPAN 19-67SOURce:RESistance:SPAN 19-78SOURce:VOLTage:SPAN 19-100

:LINK STOPSENSe:FREQuency:SPAN 18-40SOURce:CURRent:SPAN 19-24SOURce:FREQuency:SPAN 19-45SOURce:POWer:SPAN 19-67SOURce:RESistance:SPAN 19-78SOURce:VOLTage:SPAN 19-100

LIST SubsystemSENSe 18-58 - 18-59SOURce 19-48 - 19-53

LLSee also IDELete

:LLEFtDISPlay:WINDow:GEOMetry 8-7HCOPy:PAGE:DIMensions 10-14

:LLIMitSENSe:SWEep:TIME 18-83SOURce:SWEep:TIME 19-85

:LOAD

MMEMory 14-4:LOCate

DISPlay:WINDow:TEXT 8-10:LOSS

MEMory:TABLe 13-16SENSe:CORRection 18-20SENSe:MIXer 18-61SOURce:CORRection 19-13

:LOWINPut 11-6INPut:POSition:X:ANGLe:LIMit 11-8INPut:POSition:X:DISTance:LIMit 11-9INPut:POSition:Y:ANGLe:LIMit 11-10INPut:POSition:Y:DISTance:LIMit 11-11INPut:POSition:Z:ANGLe:LIMit 11-12INPut:POSition:Z:DISTance:LIMit 11-13MEASure 3-12OUTPut Subsystem 15-5OUTPut:POSition:X:ANGLe:LIMit 15-6OUTPut:POSition:X:DISTance:LIMit 15-7OUTPut:POSition:Y:ANGLe:LIMit 15-8OUTPut:POSition:Y:DISTance:LIMit 15-9OUTPut:POSition:Z:ANGLe:LIMit 15-10OUTPut:POSition:Z:DISTance:LIMit 15-11SOURce:CURRent:LEVel:IMMediate 19-20SOURce:CURRent:LEVel:TRIGgered 19-21SOURce:CURRent:LIMit 19-22SOURce:POWer:LEVel:IMMediate 19-63SOURce:POWer:LEVel:TRIGgered 19-64SOURce:POWer:LIMit 19-65SOURce:RESistance:LEVel:IMMediate 19-75SOURce:RESistance:LEVel:TRIGgered 19-76SOURce:RESistance:LIMit 19-77SOURce:VOLTage:LEVel:IMMediate 19-96SOURce:VOLTage:LEVel:TRIGgered 19-97SOURce:VOLTage:LIMit 19-98

:LOWerCALCulate:LIMit 4-20SENSe:AM:DEPTh:RANGe 18-4SENSe:CURRent:AC|:DC:RANGe 18-27SENSe:FM:DEViation:RANGe 18-36SENSe:FREQuency:RANGe 18-39SENSe:PM:DEViation:RANGe 18-62SENSe:POWer:AC|:DC:RANGe 18-66SENSe:POWer:ACHannel:SPACing 18-64SENSe:RESistance:RANGe 18-69SENSe:VOLTage:AC|:DC:RANGe 18-86

:LPASsINPut:FILTer 11-5OUTPut:FILTer 15-4SENSe:FILTer 18-33TRIGger Subsystem:ARM


Index - 13

:SEQuence:LAYer:FILTer 24-15TRIGger Subsystem:TRIGger :SEQuence:FILTer 24-26

:LPFRameTRIGger Subsystem:ARM :SEQuence:LAYer:VIDeo:FORMat 24-20TRIGger Subsystem:TRIGger :SEQuence:VIDeo:FIELd:FORMat 24-31

:LTYPeDISPlay:WINDow:GRAPhics 8-8HCOPy:ITEM:WINDow:TRACe 10-13

M :MACRo

MMEMory:LOAD and :STORe 14-4:MACRo?

MEMory:CATalog 13-5MEMory:FREE 13-8

:MAGNitudeMEMory:TABLe:CONDition 13-11SENSe:CORRection:LOSS:INPut 18-21SENSe:CORRection:OFFSet 18-21SOURce:CORRection:LOSS:OUTPut 19-14SOURce:CORRection:OFFSet 19-13SOURce:DM:IQRatio 19-28SOURce:DM:LEAKage 19-28

:MAGNitude MEMory:TABLe:CURRent 13-11MEMory:TABLe:LOSS 13-16MEMory:TABLe:POWer 13-17MEMory:TABLe:RESistance 13-17MEMory:TABLe:VOLTage 13-19

:MALLocatePROGram:EXPLicit 16-5PROGram:SELected 16-3

:MANualSENSe:FREQuency 18-38SOURce:CURRent 19-22SOURce:FREQuency 19-44SOURce:POWer 19-65SOURce:RESistance 19-78SOURce:VOLTage 19-98

:MAPSTATus 20-4, 20-7

MARKer SubsystemSOURce 19-54 - 19-55

:MATHCALCulate 4-21 - 4-22

:MAXimumMEASure 3-14

:MCONtrol

CONTrol 6-4MEASure

Measurement Instructions 3-5Measurement Function

Instrument Model 2-3Measurement Function Layer 3-9Measurement Instructions 3-1 - 3-14:MEDium COAX

SENSe:CORRection:RVELocity 18-22SOURce:CORRection:RVELocity 19-15

:MEDium WAVeguideSENSe:CORRection:RVELocity 18-22SOURce:CORRection:RVELocity 19-15

MEMoryInstrument Model 2-5

Memory Associated with Data FlowInstrument Model:Internal Routing 2-12

MEMory Subsystem 13-1 - 13-20:MENU

DISPlay 8-6HCOPy:ITEM 10-10

:MESSageVXI:WSPRotocol 26-13

:METHod PMETerSOURce:CORRection:COLLect 19-12

:METHod TPORtSENSe:CORRection:COLLect 18-18

:MGRulesTRIGger Subsystem:ARM:SEQuence :DEFine 24-13TRIGger Subsystem:TRIGger:SEQuence :DEFine 24-25

:MINimumMEASure 3-14

MIXer SubsystemSENSe 18-60 - 18-61

MMEMory Subsystem 14-1 - 14-6:MODE

HCOPy:DEVice 10-7SOURce:AM 19-7SOURce:FUNCtion 19-47SOURce:PULM 19-69

:MODE AUTOSENSe:SWEep 18-79SOURce:SWEep 19-86

:MODE CWSENSe:FREQuency 18-38SOURce:FREQuency 19-44

:MODE DELTaSOURce:MARKer 19-54

:MODE FIXedSENSe:FREQuency 18-38


Index - 14

SOURce:CURRent 19-22SOURce:FREQuency 19-44SOURce:POWer 19-65SOURce:RESistance 19-79SOURce:VOLTage 19-98

:MODE FREQuencySOURce:MARKer 19-54

:MODE LISTSENSe:FREQuency 18-38SOURce:CURRent 19-22SOURce:FREQuency 19-44SOURce:POWer 19-65SOURce:RESistance 19-79SOURce:VOLTage 19-98

:MODE LOCKedSOURce:FM 19-33SOURce:PM 19-57

:MODE MANualSENSe:SWEep 18-79SOURce:SWEep 19-86

:MODE POSitionSOURce:MARKer 19-54

:MODE SENSeSOURce:FREQuency 19-44

:MODE SOURceSENSe:FREQuency 18-38

:MODE SWEepSENSe:FREQuency 18-38SOURce:CURRent 19-22SOURce:FREQuency 19-44SOURce:POWer 19-65SOURce:RESistance 19-79SOURce:VOLTage 19-98

:MODE UNLockedSOURce:FM 19-33SOURce:PM 19-57

:Model LayersTRIGger Subsystem 24-2 - 24-3

:MODuleROUTe 17-2

:MOVEDISPlay:WINDow:GRAPhics 8-9MMEMory 14-5

MOVingCALCulate:AVERage:TCONtrol 4-7

:MSISMMEMory 14-5

:MULTiplierSENSe:FREQuency 18-39SOURce:FREQuency 19-44

N :NAME

CALCulate:MATH:EXPRession 4-22DISPlay:MENU 8-6MEMory:CLEar 13-6MEMory:COPY 13-6MEMory:DELete 13-7MEMory:EXCHange 13-7MMEMory 14-5PROGram:SELected 16-3ROUTe:MODule:DELete 17-3ROUTe:PATH:DELete 17-4TRACe | DATA:DELete 23-4TRIGger Subsystem:INITiate:CONTinuous 24-22TRIGger Subsystem:INITiate:IMMediate 24-23

:NDUTycycleMEASure 3-14

:No ErrorSYSTem:ERRor? 21-14

NORMalCALCulate:AVERage:TCONtrol 4-7

notationXn* 4-1

:NPLCyclesSENSe:CURRent:AC|:DC 18-26SENSe:POWer:AC|:DC 18-64SENSe:RESistance 18-68SENSe:VOLTage:AC|:DC 18-85

:NSELectINSTrument 12-4

:NSTates?MEMory 13-9

:NTRansitionSTATus 20-4, 20-7

:NUMBerPROGram:EXPLicit 16-5PROGram:SELected 16-3TRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:FIELd 24-19TRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:LINE 24-20TRIGger Subsystem:TRIGger:SEQuence :VIDeo:FIELd 24-31TRIGger Subsystem:TRIGger:SEQuence :VIDeo:LINE 24-32

:NUMBer?VXI:CONFigure 26-7

Numeric SuffixesInstrument Model:Internal Routing 2-7

:NWIDthMEASure 3-14


Index - 15

O :OCOMpensated

SENSe:RESistance 18-68:OCONdition ,

TRACe | DATA:FEED 23-5OCTal 9-2 - 9-3:OEDGe

DISPlay:WINDow:TRACe:R:SCALe 8-16:OFF

SENSe:FUNCtion 18-44:OFFSet

INPut 11-7:OFFSet

INPut:POSition:X:ANGLe 11-8INPut:POSition:X:DISTance 11-9INPut:POSition:Y:ANGLe 11-10INPut:POSition:Y:DISTance 11-11INPut:POSition:Z:ANGLe 11-12INPut:POSition:Z:DISTance 11-13OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11SENSe:CORRection 18-21SENSe:CURRent:AC|:DC:RANGe 18-28SENSe:FREQuency 18-39SENSe:POWer:AC|:DC:RANGe 18-66SENSe:VOLTage:AC|:DC:RANGe 18-87SOURce:CORRection 19-13SOURce:CURRent:LEVel:IMMediate 19-20SOURce:CURRent:LEVel:TRIGgered 19-21SOURce:CURRent:LIMit 19-22SOURce:FREQuency 19-44SOURce:POWer:LEVel:IMMediate 19-63SOURce:POWer:LEVel:TRIGgered 19-64SOURce:POWer:LIMit 19-64SOURce:RESistance:LEVel:IMMediate 19-75SOURce:RESistance:LEVel:TRIGgered 19-76SOURce:RESistance:LIMit 19-76SOURce:VOLTage:LEVel:IMMediate 19-96SOURce:VOLTage:LEVel:TRIGgered 19-97SOURce:VOLTage:LIMit 19-98

:ONSENSe:FUNCtion 18-44

ONCECALCulate 4-7, 4-12, 4-14, 4-21, 4-26, 4-28, 4-31CALibration 5-7DISPlay 8-11 - 8-12, 8-14 - 8-15INPut:ATTenuation 11-3

INPut:GAIN 11-6OUTPut:FILTer 15-3SENSe 18-4, 18-7, 18-10 - 18-11, 18-27 - 18-28, 18-31, 18-36, 18-38 - 18-40, 18-59 - 18-60, 18-62, 18-66 - 18-67, 18-69 - 18-70, 18-72, 18-79, 18-82, 18-86 - 18-87SENSe:ROSCillator:SOURce INTernal 19-80SOURce 19-18 - 19-20, 19-23, 19-43, 19-45, 19-50, 19-52, 19-61 - 19-62, 19-66, 19-73, 19-79, 19-85 - 19-86, 19-94 - 19-96, 19-99SYSTem 21-33TRACe | DATA 23-5TRIGger Subsystem:ARM :SEQuence:LAYer:DELay 24-14TRIGger Subsystem:ARM :SEQuence:LAYer:LEVel 24-16TRIGger Subsystem:TRIGger :SEQuence:DELay 24-26TRIGger Subsystem:TRIGger:SEQuence :LEVel 24-28

:OPENMMEMory 14-6ROUTe 17-3

:OPERationSTATus 20-3

Operation Complete EventSYSTem:ERRor? 21-28

OPERation Status Register 20-3:ORDinate

CALCulate:TRANsform:HISTogram 4-24:ORIentation

HCOPy:PAGE 10-14Other Subsystems

Instrument Model:Internal Routing 2-9OUTPut

Instrument Model:Signal Generation 2-4SENSe:CORRection:IMPedance 18-19SENSe:CORRection:LOSS 18-20SOURce:CORRection:LOSS 19-14

OUTPut Subsystem 15-1 - 15-14:OVERshoot

MEASure:FALL 3-13MEASure:RISE 3-12

P :PACE ACK

SYSTem:COMM:SERial:RECeive 21-7SYSTem:COMM:SERial:TRANsmit 21-9

:PACE NONESYSTem:COMM:SERial:RECeive 21-7SYSTem:COMM:SERial:TRANsmit 21-9


Index - 16

:PACE XONSYSTem:COMM:SERial:RECeive 21-7SYSTem:COMM:SERial:TRANsmit 21-9

:PACKMMEMory 14-6

PACKed 9-2:PAGE

DISPlay:WINDow:TEXT 8-10HCOPy 10-13 - 10-14

:PARitySYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:PATHCALCulate 4-31 - 4-32ROUTe 17-3

:PCLDISPlay:WINDow:GRAPhics 8-8

:PDFunctionSENSe:FUNCtion:VOLTage 18-57

:PDIVisionDISPlay:WINDow:TRACe:X:SCALe 8-13DISPlay:WINDow:TRACe:Y:SCALe 8-14

:PDUTycycle:MEASure 3-14

:PERiod:MEASure 3-10SENSe:FUNCtion 18-53SOURce:PULSe 19-71

:PERSistenceDISPlay:WINDow:TRACe 8-11

:PHASe:MEASure 3-10MEMory Subsystem:TABLe:CURRent 13-11MEMory Subsystem:TABLe:LOSS 13-16MEMory Subsystem:TABLe:VOLTage 13-19SENSe:CORRection:LOSS:INPut|:OUTPut 18-21SENSe:CORRection:OFFSet 18-21SENSe:FUNCtion 18-53SOURce:CORRection:LOSS:OUTPut 19-14SOURce:CORRection:OFFSet 19-13

PHASe SubsystemSOURce 19-56

:PLOSsCALibration 5-4 - 5-5

PMSENSe:FUNCtion 18-53

PM SubsystemSENSe 18-62SOURce 19-57 - 19-59

:POFLagTRIGger Subsystem:INITiate 24-23

:POINt

SOURce:MARKer 19-54:POINts

CALCulate 4-10CALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:SMOothing 4-23CALCulate:TRANsform:DISTance 4-28CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:HISTogram 4-24CALCulate:TRANsform:TIME 4-26SENSe:SMOothing 18-73SENSe:SWEep 18-80SOURce:SWEep 19-87TRACe | DATA 23-5 - 23-6

:POINts?CALCulate:CLIMits:FLIMits 4-9CALCulate:LIMit:CONTrol 4-19CALCulate:LIMit:LOWer 4-20CALCulate:LIMit:REPort 4-21CALCulate:LIMit:UPPer 4-20MEMory:TABLe:CONDition:MAGNitude 13-11MEMory:TABLe:CURRent:MAGNitude 13-11MEMory:TABLe:CURRent:PHASe 13-12MEMory:TABLe:FREQuency 13-15MEMory:TABLe:LOSS:MAGNitude 13-16MEMory:TABLe:LOSS:PHASe 13-16MEMory:TABLe:POWer:MAGNitude 13-17MEMory:TABLe:RESistance:MAGNitude 13-17MEMory:TABLe:VOLTage:MAGNitude 13-19MEMory:TABLe:VOLTage:PHASe 13-20SENSe:LIST:DWELl 18-58SENSe:LIST:FREQuency 18-59SENSe:LIST:SEQuence 18-59SOURce:LIST:APRobe 19-49SOURce:LIST:CONCurrent 19-50SOURce:LIST:CONTrol:APOWer 19-50SOURce:LIST:CONTrol:BLOWer 19-50SOURce:LIST:CONTrol:COMPressor 19-50SOURce:LIST:CURRent 19-50SOURce:LIST:DEPTh:AM 19-49SOURce:LIST:DWELl 19-51SOURce:LIST:FREQuency 19-51SOURce:LIST:POWer 19-52SOURce:LIST:PULM:STATe 19-51SOURce:LIST:RESistance 19-52SOURce:LIST:RTIMe 19-52SOURce:LIST:SEQuence 19-52SOURce:LIST:TEMPerature 19-52SOURce:LIST:VOLTage 19-53

:POLarityINPut 11-7OUTPut Subsystem 15-5


Index - 17

:POLarity :ALL NORMalSOURce:DM 19-30

:POLarity COMPlementSOURce:PULSe 19-73

:POLarity INVertedOUTPut:TTLTrg|:ECLTrg 15-13SOURce:AM 19-8SOURce:AM:EXTernal 19-7SOURce:DM 19-30SOURce:FM 19-34SOURce:FM:EXTernal 19-33SOURce:PM 19-58SOURce:PM:EXTernal 19-59SOURce:PULM 19-69SOURce:PULM:EXTernal 19-69SOURce:PULSe 19-73

:POLarity NEGativeTRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:SSIGnal 24-21TRIGger Subsystem:TRIGger:SEQuence :VIDeo:SSIGnal 24-32

:POLarity NORMalOUTPut:TTLTrg|:ECLTrg 15-13SOURce:AM 19-8SOURce:AM:EXTernal 19-7SOURce:FM 19-34SOURce:FM:EXTernal 19-33SOURce:PM 19-58SOURce:PM:EXTernal 19-59SOURce:PULM:EXTernal 19-69SOURce:PULSe 19-73SOURce:PULse Modulation 19-69

:POLarity POSitiveTRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:SSIGnal 24-21TRIGger Subsystem:TRIGger:SEQuence :VIDeo:SSIGnal 24-32

:POLarizationINPut 11-7OUTPut Subsystem 15-5

:POSitionOUTPut Subsystem 15-5

:POSitionINPut 11-7 - 11-13

:POWer:MEASure 3-8MEMory:TABLe 13-17SENSe:FUNCtion 18-53SOURce:LIST 19-52UNIT 25-1

Power On EventSYSTem:ERRor? 21-27

POWer SubsystemSENSe 18-63 - 18-67SOURce 19-60 - 19-67

:PREFerenceCALCulate:FORMat:UPHase 4-17

Presentation LayerMeasurement Instructions 3-7

:<presentation_layer>SENSe:FUNCtion 18-47

:PRESetSTATus 20-4SYSTem 21-35

:PREShootMEASure:FALL 3-13MEASure:RISE 3-12

:PRF:MEASure:FREQuency 3-10

PROGram Subsystem 16-1 - 16-6:PROTection

OUTPut Subsystem 15-12SENSe:CURRent:AC|:DC 18-26SENSe:POWer:AC|:DC 18-65SENSe:VOLTage:AC|:DC 18-85SOURce:CURRent 19-23SOURce:POWer 19-65SOURce:RESistance 19-77SOURce:VOLTage 19-99

:PROTocolTRIGger Subsystem:ARM:SEQuence :LAYer 24-17TRIGger Subsystem:TRIGger:SEQuence 24-28

:PROTocol ASYNchronousOUTPut:TTLTrg|:ECLTrg 15-13

:PROTocol SSYNchronousOUTPut:TTLTrg|:ECLTrg 15-13

:PROTocol SYNChronousOUTPut:TTLTrg|:ECLTrg 15-13

:PSDensitySENSe:FUNCtion:POWer 18-54

:PTPeakMEASure 3-14SENSe:CURRent:AC|:DC:RANGe 18-28SENSe:POWer:AC|:DC:RANGe 18-66SENSe:VOLTage:AC|:DC:RANGe 18-87

:PTRansitionSTATus 20-4, 20-7

:PULMSOURce:LIST 19-51

PULse Modulation SubsystemSOURce 19-68 - 19-70

PULSe SubsystemSOURce 19-71 - 19-73


Index - 18

:PWIDthMEASure 3-13

Q :Q INVerted

SOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:Q<n> NRMalSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:QCLock INVertedSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:QCLock NORMalSOURce:DM:POLarity :ALL NORMal|INVerted 19-30

:QCORrectionSOURce:DM:FILTer 19-27

:QUADrantHCOPy:PAGE:DIMensions 10-14

:QUADratureSOURce:DM 19-28

:QUERyVXI:WSPRotocol 26-14

:Query ErrorSYSTem:ERRor? 21-26

Querying the Data FlowInstrument Model:Internal Routing 2-14

:QUEStionableSTATus 20-7

QUEStionable Data 20-7

R :R

DISPlay:WINDow:TRACe 8-15:RANGe

CALCulate:TRANsform:HISTogram 4-24SENSe:AM:DEPTh 18-4SENSe:CURRent:AC|:DC 18-27SENSe:FM:DEViation 18-36SENSe:FREQuency 18-39SENSe:PM:DEViation 18-62SENSe:POWer:AC|:DC 18-65SENSe:RESistance 18-69SENSe:VOLTage:AC|:DC 18-86SOURce:CURRent 19-23SOURce:POWer 19-66SOURce:RESistance 19-79SOURce:VOLTage 19-99

:RATio

SENSe:BANDwidth|BWIDth:RESolution 18-10SENSe:BANDwidth|BWIDth:VIDeo 18-11

:RDEViceSYSTem:COMMunicate:GPIB 21-5VXI:WSPRotocol:COMMand 26-11

:RDEVice?VXI:WSPRotocol:QUERy 26-15

READMeasurement Instructions 3-4

:READ?VXI:REGister 26-7

REAL 9-2:REALtime

SENSe:SWEep 18-81REAR

SENSe:FUNCtion:SPEed 18-55:RECeive

SYSTem:COMM:SERial 21-7:RECeive?

VXI:WSPRotocol:MESSage 26-13:REFerence

SENSe:CURRent:AC|:DC 18-28SENSe:POWer:AC|:DC 18-67SENSe:RESistance 18-70SENSe:VOLTage:AC|:DC 18-87SOURce:CURRent 19-23SOURce:MARKer 19-55SOURce:PHASe 19-56SOURce:POWer 19-66SOURce:RESistance 19-79SOURce:VOLTage 19-99

:REGisterVXI 26-7

REPeatCALCulate:AVERage:TCONtrol 4-7

:REPortCALCulate:LIMit 4-20

Request Control EventSYSTem:ERRor? 21-28

:RequirementsIntroduction 1-1

:RESet?VXI 26-8

:RESistance:MEASure 3-8MEMory:TABLe 13-17SENSe:FUNCtion 18-55SOURce:LIST 19-52

RESistance SubsystemSENSe 18-68 - 18-70SOURce 19-74 - 19-79

:RESolution


Index - 19

HCOPy:DEVice 10-7SENSe:BANDwidth|BWIDth 18-10SENSe:CURRent:AC|:DC 18-28SENSe:FREQuency 18-40SENSe:POWer:AC|:DC 18-67SENSe:RESistance 18-70SENSe:VOLTage:AC|:DC 18-87SOURce:FREQuency 19-45

:RESPonse?VXI:WSPRotocol 26-17

:RGBDISPlay:CMAP:COLor 8-5HCOPy:DEVice:CMAP:COLor 10-5

:RHANdlersVXI:WSPRotocol:COMMand 26-11

:RHANdlers?VXI:WSPRotocol:QUERy 26-15

:RHLineVXI:WSPRotocol:COMMand 26-12

:RHLine?VXI:WSPRotocol:QUERy 26-15

:RIGHtDISPlay:WINDow:TRACe:X:SCALe 8-13

:RILineVXI:WSPRotocol:COMMand 26-12

:RILine?VXI:WSPRotocol:QUERy 26-16

:RINTerrupterVXI:WSPRotocol:COMMand 26-12

:RINTerrupter?VXI:WSPRotocol:QUERy 26-16

:RISEMEASure 3-12

:RLEVelDISPlay:WINDow:TRACe:Y:SCALe 8-14

:RLINeDISPlay:WINDow:TRACe:Y 8-13

:RMODidVXI:WSPRotocol:COMMand 26-12

:RMODid?VXI:WSPRotocol:QUERy 26-16

:ROSCillatorOUTPut Subsystem 15-12

ROSCillator SubsystemSENSe 18-71 - 18-72SOURce 19-80 - 19-81

:ROTationCONTrol 6-4

ROUTe Subsystem 17-1 - 17-6:RPERror

VXI:WSPRotocol:COMMand 26-12:RPERror?

VXI:WSPRotocol:QUERy 26-16:RPOSition

DISPlay:WINDow:TRACe:Y:SCALe 8-15:RPRotocol

VXI:WSPRotocol:COMMand 26-12:RPRotocol?

VXI:WSPRotocol:QUERy 26-16:RSARea

VXI:WSPRotocol:COMMand 26-13:RSARea?

VXI:WSPRotocol:QUERy 26-16:RSTB

VXI:WSPRotocol:COMMand 26-12:RSTB?

VXI:WSPRotocol:QUERy 26-16:RTIMe

MEASure 3-12SOURce:LIST 19-52

:RTS IBFullSYSTem:COMM:SERial:CONTrol 21-6

:RTS OFFSYSTem:COMM:SERial:CONTrol 21-6

:RTS ONSYSTem:COMM:SERial:CONTrol 21-6

:RTS RFRSYSTem:COMM:SERial:CONTrol 21-6

:RTS STANdardSYSTem:COMM:SERial:CONTrol 21-6

:RVELocitySENSe:CORRection 18-22SOURce:CORRection 19-15

S :S11

SENSe:FUNCtion:POWer 18-54:S12



SENSe:FUNCtion:POWer 18-54:SAMPle

ROUTe 17-4:SAVE

SENSe:CORRection:COLLect 18-18SOURce:CORRection:COLLect 19-12

SBSee SENSe:FUNCtion

:SBITsSYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9


Index - 20

:SCALarMEASure 3-7

:SCALeDISPlay:WINDow:TRACe:R 8-15DISPlay:WINDow:TRACe:X 8-12DISPlay:WINDow:TRACe:Y 8-13HCOPy:PAGE 10-14

:SCANROUTe 17-6

:SDUMpHCOPy 10-15 - 10-16

:SEARchSOURce:CURRent:ALC 19-18SOURce:POWer:ALC 19-61SOURce:VOLTage:ALC 19-94

:SECuritySYSTem 21-36

:SELectINSTrument 12-4MEMory:TABLe 13-18SENSe:CORRection:CSET 18-18SOURce:CORRection:CSET 19-12TRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:LINE 24-20TRIGger Subsystem:TRIGger:SEQuence :VIDeo:LINE 24-32VXI 26-9

:SELect ALLTRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:FIELd 24-19TRIGger Subsystem:TRIGger:SEQuence :VIDeo:FIELd 24-31

:SELect EVENTRIGger Subsystem:ARM:SEQuence :LAYer:VIDeo:FIELd 24-19TRIGger Subsystem:TRIGger :SEQuence:VIDeo:FIELd 24-31

:SELect NUMBerTRIGger Subsystem:ARM :SEQuence:LAYer:VIDeo:FIELd 24-19TRIGger Subsystem:TRIGger :SEQuence:VIDeo:FIELd 24-31

:SELect ODDTRIGger Subsystem:ARM :SEQuence:LAYer:VIDeo:FIELd 24-19TRIGger Subsystem:TRIGger :SEQuence:VIDeo:FIELd 24-31

:SELectedCALCulate:MATH:EXPRession:DELete 4-22PROGram 16-2 - 16-3PROGram:SELected:DELete 16-2

:SELF

SYSTem:COMMunicate:GPIB 21-5:SEND

VXI:WSPRotocol:MESSage 26-13SENSe

Instrument Model:Measurement Function 2-4SENSe:DATA? 18-42

SENSe Subsystem 18-1 - 18-90:SENSitivity

SOURce:AM 19-8SOURce:FM 19-34SOURce:PM 19-57

Sensor Function SelectionInstrument Model:Internal Routing 2-9

:<sensor_function>SENSe:FUNCtion 18-45

:SEQuenceSENSe:LIST 18-59SOURce:LIST 19-52TRIGger Subsystem:ARM 24-12TRIGger Subsystem:INITiate:CONTinuous 24-22TRIGger Subsystem:INITiate:IMMediate 24-23TRIGger Subsystem:TRIGger 24-23

:Sequence Event UseTRIGger Subsystem 24-4

:SERialSYSTem:COMMunicate 21-6

:SETSYSTem 21-36

:SHAPeSOURce:FUNCtion 19-47

:SHAPe LINearSENSe:DETector 18-31

:SHAPe LOGarithmicSENSe:DETector 18-31

:SIGNalTRIGger Subsystem:ARM :SEQuence:LAYer 24-17TRIGger Subsystem:TRIGger:SEQuence 24-29

Signal GenerationInstrument Model 2-4

Signal RoutingInstrument Model 2-2

Signal Status Register 20-7Simple Measurements

Measurement Function Layer 3-9:SIZE

DISPlay:WINDow:GEOMetry 8-7HCOPy:PAGE 10-15

:SLEWSOURce:CURRent 19-24SOURce:POWer 19-66SOURce:RESistance 19-77


Index - 21

SOURce:VOLTage 19-100:SLModid

VXI:WSPRotocol:COMMand 26-13:SLModid?

VXI:WSPRotocol:QUERy 26-17:SLOCk

VXI:WSPRotocol:COMMand 26-13:SLOPe

SENSe:CORRection 18-20SOURce:CORRection 19-13

:SLOPe EITHerTRIGger Subsystem:ARM :SEQuence:LAYer 24-18TRIGger Subsystem:TRIGger:SEQuence 24-29

:SLOPe NEGativeTRIGger Subsystem:ARM :SEQuence:LAYer 24-18TRIGger Subsystem:TRIGger:SEQuence 24-29

:SLOPe POSitiveTRIGger Subsystem:ARM :SEQuence:LAYer 24-18TRIGger Subsystem:TRIGger:SEQuence 24-29

:SMOothingCALCulate 4-23

SMOothing SubsystemSENSe 18-73

:SNDRatioSENSe:FUNCtion & DATA:FUNCtion:POWer 18-51 - 18-53, 18-55

SOURceCALibration 5-6Instrument Model:Signal Generation 2-5OUTPut:TTLTrg|:ECLTrg 15-13TRIGger Subsystem:ARM :SEQuence:LAYer 24-18TRIGger Subsystem:TRIGger:SEQuence 24-29

:SOURce ,INTernalSOURce:FM 19-34SOURce:PM 19-58SOURce:PULM 19-70

:SOURce CALibrateSOURce:DM 19-27

:SOURce CLK10SENSe:ROSCillator 18-71, 19-80

:SOURce CLK100SENSe:ROSCillator 18-71, 19-80

:SOURce DIODeSOURce:CURRent:ALC 19-19SOURce:POWer:ALC 19-62SOURce:VOLTage:ALC 19-95

:SOURce EXTernalSENSe:ROSCillator 18-71, 19-80

SOURce:AM 19-8SOURce:DM 19-27SOURce:DM:CLOCk 19-31SOURce:DM:FILTer 19-27SOURce:DM:FRAMe 19-30SOURce:FM 19-34SOURce:PHASe 19-56SOURce:PM 19-58SOURce:PULM 19-70

:SOURce INTernalSENSe:ROSCillator 18-71, 19-80SOURce:AM 19-8SOURce:CURRent:ALC 19-19SOURce:DM:CLOCk 19-31SOURce:DM:FILTer 19-27SOURce:DM:FRAMe 19-30SOURce:PHASe 19-56SOURce:POWer:ALC 19-62SOURce:VOLTage:ALC 19-95

:SOURce INTernal,EXTernalSOURce:FM 19-34SOURce:PM 19-58SOURce:PULM 19-70

:SOURce MMHeadSOURce:CURRent:ALC 19-19SOURce:POWer:ALC 19-62SOURce:VOLTage:ALC 19-95

:SOURce NONESENSe:ROSCillator 18-71, 19-80SOURce:DM:CLOCk 19-31

:SOURce PMETerSOURce:CURRent:ALC 19-19SOURce:POWer:ALC 19-62SOURce:VOLTage:ALC 19-95

:SOURce PRBSSOURce:DM 19-27

SOURce Subsystem 19-1 - 19-102:SPACing

SENSe:POWer:ACHannel 18-63:SPACing LINear

DISPlay:WINDow:TRACe:R 8-16DISPlay:WINDow:TRACe:Y 8-15SENSe:SWEep 18-81SOURce:SWEep 19-86

:SPACing LOGarithmicDISPlay:WINDow:TRACe:R 8-16DISPlay:WINDow:TRACe:Y 8-15SENSe:SWEep 18-81SOURce:SWEep 19-86

:SPANCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12


Index - 22

CALCulate:GDAPerture 4-17CALCulate:TRANsform:DISTance 4-28CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-26SENSe:FREQuency 18-40SOURce:CURRent 19-24SOURce:FREQuency 19-45SOURce:POWer 19-67SOURce:RESistance 19-77SOURce:VOLTage 19-100

:SPEedHCOPy:DEVice 10-7SENSe:FUNCtion 18-55

SPEed SubsystemSOURce 19-82 - 19-84

:SREGisterFORMat 9-3 - 9-4

SSB SubsystemSENSe 18-74

:SSIGnalTRIGger Subsystem:ARM :SEQuence:LAYer:VIDeo 24-20TRIGger Subsystem:TRIGger :SEQuence:VIDeo 24-32

STABilize SubsystemSENSe 18-75 - 18-76

:Standard SEQuencesTRIGger Subsystem:Expanded Capability Trigger Model 24-7

:STARtCALCulate:FILTer:GATE:FREQuency 4-13CALCulate:FILTer:GATE:TIME 4-11CALCulate:TRANsform:DISTance 4-28CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-25SENSe:FREQuency 18-41SOURce:CURRent 19-24SOURce:FREQuency 19-46SOURce:POWer 19-67SOURce:RESistance 19-78SOURce:VOLTage 19-100SYSTem:COMM:SERial:RECeive 21-8

:STATeCALCulate 4-7, 4-10 - 4-11, 4-18 - 4-20, 4-23, 4-25, 4-27, 4-29CALibration 5-6CONTrol 6-1 - 6-2DISPlay 8-6, 8-9 - 8-11HCOPy 10-8 - 10-13INPut 11-14INPut:ATTenuation 11-3INPut:BIAS 11-4

INPut:FILTer:AWEighting 11-5INPut:FILTer:HPASs 11-5INPut:FILTer:LPASs 11-5INPut:GAIN 11-6INPut:OFFSet 11-7INPut:POSition:X:ANGLe:LIMit 11-8INPut:POSition:X:DISTance:LIMit 11-9INPut:POSition:Y:ANGLe:LIMit 11-10INPut:POSition:Y:DISTance:LIMit 11-11INPut:POSition:Z:ANGLe:LIMit 11-12INPut:POSition:Z:DISTance:LIMit 11-13INSTrument 12-4MEMory 13-9MMEMory 14-4OUTPut Subsystem 15-14OUTPut:FILTer:EXTernal 15-4OUTPut:FILTer:HPASs 15-4OUTPut:FILTer:LPASs 15-4OUTPut:POSition:X:ANGLe:LIMit 15-6OUTPut:POSition:X:DISTance:LIMit 15-7OUTPut:POSition:Y:ANGLe:LIMit 15-8OUTPut:POSition:Y:DISTance:LIMit 15-9OUTPut:POSition:Z:ANGLe:LIMit 15-10OUTPut:POSition:Z:DISTance:LIMit 15-11OUTPut:PROTection 15-12OUTPut:ROSCillator 15-12OUTPut:TTLTrg|:ECLTrg 15-13PROGram 16-3, 16-5SENSe 18-7, 18-18 - 18-19, 18-21 - 18-23, 18-26, 18-28, 18-33 - 18-35, 18-65, 18-67, 18-70, 18-73, 18-81, 18-85, 18-87SOURce 19-8, 19-11 - 19-15, 19-18, 19-22 - 19-24, 19-27 - 19-29, 19-34, 19-51, 19-55, 19-58, 19-61, 19-65 - 19-66, 19-70, 19-72, 19-77, 19-79, 19-94, 19-98 - 19-100CALCulate 4-13SYSTem 21-3 - 21-4, 21-36TRIGger Subsystem:ARM :SEQuence:LAYer:FILTer:HPASs 24-15TRIGger Subsystem:ARM :SEQuence:LAYer:FILTer:LPASs 24-15TRIGger Subsystem:TRIGger :SEQuence:ATRigger 24-24TRIGger Subsystem:TRIGger :SEQuence:FILTer:HPASs 24-26TRIGger Subsystem:TRIGger:SEQuence:FILTer:LPASs 24-27

:STATe?MEMory 13-5, 13-9ROUTe 17-2SENSe 18-45

status reporting


Index - 23

OPERation 20-3QUEStionable 20-7

STATus Subsystem 20-1 - 20-8:STEP

SENSe:SWEep 18-82SOURce:PHASe:ADJust 19-56SOURce:SWEep 19-87

:STIMulus IMPulseCALCulate:TRANsform:DISTance 4-27CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-25

:STIMulus STEPCALCulate:TRANsform:DISTance 4-27CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-25

:STOPCALCulate:FILTer:GATE:FREQuency 4-13CALCulate:FILTer:GATE:TIME 4-11CALCulate:TRANsform:DISTance 4-28CALCulate:TRANsform:FREQuency 4-30CALCulate:TRANsform:TIME 4-26SENSe:FREQuency 18-41SOURce:CURRent 19-25SOURce:FREQuency 19-46SOURce:POWer 19-67SOURce:RESistance 19-78SOURce:VOLTage 19-101SYSTem:COMM:SERial:RECeive 21-8

:STOReMMEMory 14-4

:STRingPROGram:EXPLicit 16-6PROGram:SELected 16-4

:Subservient SequencesTRIGger Subsystem:Expanded Capability Trigger

Model 24-7:SUModid

VXI:WSPRotocol:COMMand 26-13:SUModid?

VXI:WSPRotocol:QUERy 26-17SWEep Subsystem

SENSe 18-77 - 18-83SOURce 19-85 - 19-87

:SYNTax?SYSTem:HELP 21-31

SYSTem Subsystem 21-1 - 21-40

T :TABLe

MEMory 13-10MEMory:CLEar 13-6

MEMory:COPY 13-7MEMory:EXCHange 13-8

:TABLe?MEMory:CATalog 13-6MEMory:FREE 13-9

:TCONstantSENSe:FILTer:DEMPhasis 18-34

:TCONtrol EXPonentialCALCulate:AVERage 4-7SENSe:AVERage 18-7

:TCONtrol MOVingCALCulate:AVERage 4-7SENSe:AVERage 18-7

:TCONtrol NORMalCALCulate:AVERage 4-7SENSe:AVERage 18-7

:TCONtrol REPeatCALCulate:AVERage 4-7SENSe:AVERage 18-7

:TDSTampHCOPy:ITEM 10-11

:TEMPeratureSOURce 19-88 - 19-92SOURce:LIST 19-52UNIT 25-2

:TERMinalsROUTe 17-6

TEST Subsystem 22-1 - 22-2:TEXT

DISPlay:WINDow 8-9HCOPy:ITEM:LABel 10-10HCOPy:ITEM:WINDow 10-11

:THDSENSe:FUNCtion:POWer 18-51 - 18-53, 18-55

:THResholdSOURce:DM 19-29SYSTem:COMM:SERial:RECeive 21-8

:TIMeCALCulate:FILTer:GATE 4-11CALCulate:TRANsform 4-25MEASure:FALL 3-13MEASure:RISE 3-12SENSe:CORRection:EDELay 18-19SENSe:SWEep 18-82SOURce:CORRection:EDELay 19-14SOURce:SWEep 19-85SYSTem 21-37SYSTem:BEEPer 21-4UNIT 25-2

Time Domain Waveform Measurements 3-10:TIMer

TRIGger Subsystem:ARM


Index - 24

:SEQuence:LAYer 24-19TRIGger Subsystem:TRIGger:SEQuence 24-30

TINTervalSENSe:FUNCtion 18-56

:TMAXimumMEASure 3-14

:TMINimumMEASure 3-14

:TOPDISPlay:WINDow:TRACe:Y:SCALe 8-15

TOTalizeSENSe:FUNCtion 18-56

TPLossSENSe:FUNCtion 18-56

:TRACe 23-1 - 23-6DISPlay:WINDow 8-10HCOPy:ITEM:WINDow 10-12MMEMory:LOAD and :STORe 14-5MMEMory:LOAD and

:STORe:DINTerchange 14-4:TRACk

SENSe:BANDwidth|BWIDth:RESolution 18-10:TRAiling

SOURce:PULSe:TRANsition 19-73:TRANsform

CALCulate 4-23 - 4-30:TRANsition

SOURce:PULSe 19-72:TRANsmit

SYSTem:COMM:SERial 21-8TRIGger 2-5

Instrument Model 2-5TRIGger Subsystem 24-23 - 24-32VXI:WSPRotocol:COMMand 26-13

TRIGger Subsystem 24-1 - 24-32:TRIGgered

SOURce:CURRent:LEVel 19-21SOURce:POWer:LEVel 19-63SOURce:RESistance:LEVel 19-75SOURce:VOLTage:LEVel 19-97

:TRIPped?OUTPut:PROTection 15-12SENSe:CURRent:AC|:DC:PROTection 18-26SENSe:POWer:AC|:DC:PROTection 18-65SENSe:VOLTage:AC|:DC:PROTection 18-85SOURce:CURRent:PROTection 19-23SOURce:POWer:PROTection 19-66SOURce:RESistance:PROTection 19-77SOURce:VOLTage:PROTection 19-99

:TTLTRIGger Subsystem:ARM :SEQuence:LAYer 24-19

TRIGger Subsystem:TRIGger:SEQuence 24-30:TTLTrg

OUTPut Subsystem 15-12:TYPE

CALCulate 4-18INPut 11-14OUTPut Subsystem 15-14SENSe:AM 18-4SOURce:AM 19-9

:TYPE BESSelOUTPut:FILTer:HPASs 15-4OUTPut:FILTer:LPASs 15-4

:TYPE BPASsCALCulate:FILTer:GATE:FREQuency 4-13CALCulate:FILTer:GATE:TIME 4-11CALCulate:TRANsform:DISTance 4-27CALCulate:TRANsform:FREQuency 4-29CALCulate:TRANsform:TIME 4-25

:TYPE CHEByshevOUTPut:FILTer:HPASs 15-4OUTPut:FILTer:LPASs 15-4

:TYPE COMPlexCALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE CURRentINPut:BIAS 11-4

:TYPE EDGETRIGger Subsystem:ARM :SEQuence:LAYer 24-19TRIGger Subsystem:TRIGger:SEQuence 24-31

:TYPE ENVelopeCALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE EVENSYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:TYPE FLATtopSENSe:WINDow 18-89

:TYPE HAMMingSENSe:WINDow 18-89

:TYPE HANNingSENSe:WINDow 18-89

:TYPE IGNoreSYSTem:COMM:SERial:RECeive 21-8

:TYPE LPASsCALCulate:TRANsform:DISTance 4-27CALCulate:TRANsform:FREQuency 4-29CALCulate:TRANsform:TIME 4-25

:TYPE MAXimumCALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE MINimum


Index - 25

CALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE NONESYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:TYPE NOTChCALCulate:FILTer:GATE:FREQuency 4-13CALCulate:FILTer:GATE:TIME 4-11

:TYPE ODDSYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:TYPE ONESYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:TYPE RECTangularSENSe:WINDow 18-89

:TYPE RMSCALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE SCALarCALCulate:AVERage 4-8SENSe:AVERage 18-8

:TYPE UNIFormSENSe:WINDow 18-89

:TYPE VIDeoTRIGger Subsystem:ARM :SEQuence:LAYer 24-19TRIGger Subsystem:TRIGger:SEQuence 24-31

:TYPE VOLTageINPut:BIAS 11-4

:TYPE ZEROSYSTem:COMM:SERial:RECeive 21-8SYSTem:COMM:SERial:TRANsmit 21-9

:TYPE?MEMory 13-9

:TZONeSYSTem 21-38

U UINTeger 9-2:UNIT

HCOPy:DEVice:RESolution 10-7HCOPy:DEVice:SPEed 10-7HCOPy:PAGE 10-15

UNIT Subsystem 25-1 - 25-2:UPHase

CALCulate:FORMat 4-16:UPPer

CALCulate:LIMit 4-19SENSe:AM:DEPTh:RANGe 18-4SENSe:CURRent:AC|:DC:RANGe 18-27

SENSe:FM:DEViation:RANGe 18-36SENSe:FREQuency:RANGe 18-39SENSe:PM:DEViation:RANGe 18-62SENSe:POWer:AC|:DC:RANGe 18-65SENSe:POWer:ACHannel:SPACing 18-64SENSe:RESistance:RANGe 18-69SENSe:VOLTage:AC|:DC:RANGe 18-86

:URIGhtDISPlay:WINDow:GEOMetry 8-7HCOPy:PAGE:DIMensions 10-14

User Request EventSYSTem:ERRor? 21-27

V :VALue

CALibration 5-6TRACe | DATA:DATA 23-3

:VCDeviceCONTrol 6-4 - 6-6

:VELocityINPut:POSition:X:ANGLe 11-9INPut:POSition:X:DISTance 11-10INPut:POSition:Y:ANGLe 11-11INPut:POSition:Y:DISTance 11-12INPut:POSition:Z:ANGLe 11-13INPut:POSition:Z:DISTance 11-14OUTPut:POSition:X:ANGLe 15-6OUTPut:POSition:X:DISTance 15-7OUTPut:POSition:Y:ANGLe 15-8OUTPut:POSition:Y:DISTance 15-9OUTPut:POSition:Z:ANGLe 15-10OUTPut:POSition:Z:DISTance 15-11

:VERBose?VXI:CONFigure:HIERarchy? 26-4VXI:CONFigure:INFormation? 26-6VXI:REGister:READ? 26-8VXI:RESet? 26-9

:VERSion?SYSTem 21-38 - 21-40

:VERTicalINPut:POLarization 11-7OUTPut:POLarization 15-5

:VIDeoSENSe:BANDwidth|BWIDth 18-10TRIGger Subsystem:ARM :SEQuence:LAYer 24-19TRIGger Subsystem:TRIGger:SEQuence 24-31

:VOLTage:MEASure 3-8INPut:BIAS 11-4MEMory:TABLe 13-19


Index - 26

SENSe:FUNCtion 18-56SOURce:LIST 19-53UNIT 25-1

VOLTage SubsystemSENSe 18-84 - 18-88SOURce 19-93 - 19-102

:VOLumeSYSTem:BEEPer 21-4

:VXI ASYNchronousTRIGger Subsystem:ARM :SEQuence:LAYer:PROTocol 24-17TRIGger Subsystem:TRIGger :SEQuence:PROTocol 24-29

:VXI SSYNchronousTRIGger Subsystem:ARM :SEQuence:LAYer:PROTocol 24-17TRIGger Subsystem:TRIGger :SEQuence:PROTocol 24-29

VXI Subsystem 26-1 - 26-18:VXI SYNChronous

TRIGger Subsystem:ARM :SEQuence:LAYer:PROTocol 24-17TRIGger Subsystem:TRIGger :SEQuence:PROTocol 24-29

W :WAIT

PROGram:EXPLicit 16-6PROGram:SELected 16-4

:WARMupCALibration 5-6

:WAVeguideSENSe:CORRection:RVELocity 18-22SOURce:CORRection:RVELocity 19-15

:WIDThHCOPy:PAGE 10-15OUTPut:TTLTrg|:ECLTrg 15-13SOURce:PULSe 19-71

:WINDowDISPlay 8-6 - 8-16HCOPy:ITEM 10-11

:WINDow FLATtopCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-26

:WINDow HAMMingCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29

CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-26

:WINDow RECTangularCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-26

WINDow SubsystemSENSe 18-89 - 18-90

:WINDow UNIFormCALCulate:FILTer:GATE:FREQuency 4-14CALCulate:FILTer:GATE:TIME 4-12CALCulate:TRANsform:DISTance 4-29CALCulate:TRANsform:FREQuency 4-31CALCulate:TRANsform:TIME 4-26

:WRITeVXI:REGister 26-8

:WSPRotocolVXI 26-9

X :X

DISPlay:WINDow:TRACe 8-12INPut:POSition 11-8OUTPut:POSition 15-5

:XCURrentSENSe:FUNCtion:<presentation_layer> 18-47

:XFRequencySENSe:FUNCtion:<presentation_layer> 18-47

:XNONeSENSe:FUNCtion:<presentation_layer> 18-47

:XPOWerSENSe:FUNCtion:<presentation_layer> 18-47

:XTIMeSENSe:FUNCtion:<presentation_layer> 18-47

:XVOLtageSENSe:FUNCtion:<presentation_layer> 18-47

Y :Y

DISPlay:WINDow:TRACe 8-13INPut:POSition 11-10OUTPut:POSition 15-8

Z :Z

INPut:POSition 11-12OUTPut:POSition 15-10


Index - 27

:ZEROCALibration 5-7 - 5-10


Index - 28


Volume 3: Data Interchange Format


Table of Contents


1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Defined Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.3 Implicit and Explicit Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Chapter 2 Style

Chapter 3 Syntax

3.1 Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 White Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.3 Blocks, Block Modifiers, and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.4 Value Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.4.1 <Numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.4.2 <+Numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.4.3 <0+Numeric> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.4 <NR1> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.5 <+NR1> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.6 <0+NR1> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.7 <Block> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.8 <String> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.9 <Label> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.4.10 Enumerated Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Chapter 4 Grammar

4.1 Grammar Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.1 Non-terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.2 Pseudo-terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.3 Meta-symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1.4 Terminal Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.2 Grammar Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.3 Required Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.4 Required Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.5 Unrecognized Keywords and Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Chapter 5 Data Format Extensions

5.1 Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.2 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.3 Extension Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

iii

Chapter 6 Block Descriptions

6.1 Top Level Block Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2 DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.2.2 DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.2.2.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.2.2.2 DIMension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.2.2.1 SCALe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.2.2.2 OFFSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.2.2.3 SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.2.3 DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.2.4 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.3 CURVe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.3.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.3.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.3.3 CTYPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.3.4 VALues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.2.3.5 CSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.2.4 WAVeform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.2.4.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.4.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.4.3 TRACe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.4.4 HLMethod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.4.5 HIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.4.6 LOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.7 REFerence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.7.1 HIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.7.2 LOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.7.3 MID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.7.4 METHod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4.8 AMPLitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.4.9 PWIDth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.4.10 NWIDth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.4.11 PERiod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.4.12 FREQuency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.4.13 PDUTycycle | DCYCle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.14 NDUTycycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.15 RISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.15.1 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.15.2 OVERshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-116.2.4.15.3 PREShoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.16 FALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.4.16.1 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.16.2 OVERshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

1999 SCPI Data Interchange Format

iv

6.2.4.16.3 PREShoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.17 MAXimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.18 MINimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.19 TMAXimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.20 TMINimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.2.4.21 MEAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.22 RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.23 SDEViation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.24 PTPeak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.25 CYCLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.25.1 COUNt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.2.4.25.2 MEAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.2.4.25.3 RMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.2.4.25.4 SDEViation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.2.5 MEASurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.2.5.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.2.5.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.2.5.3 UNITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.2.5.4 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.2.5.5 TRACe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.2.5.6 LOCation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.2.5.6.1 LABel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.2.5.6.2 INDex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.2.5.7 VALues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.2.6 DATA Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176.3 DIMension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176.3.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.3.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.3.3 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.3.4 SCALe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-196.3.5 OFFSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-196.3.6 SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-196.3.7 UNITs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206.3.8 ENCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206.3.9 DIMension Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206.4 ENCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-216.4.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-216.4.2 FORMat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-226.4.3 NVALue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-236.4.4 ORANge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-236.4.5 URANge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-236.4.6 HRANge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-236.4.7 LRANge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-246.4.8 RESolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-246.4.9 ENCode Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24


v

6.5 IDENtify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-246.5.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-256.5.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-256.5.3 TECHnician . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-256.5.4 PROJect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.5.5 DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.5.6 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.5.7 UUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.5.7.1 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.5.7.2 ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.7.3 DESign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.8 TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.8.1 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.8.2 SERies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.8.3 NUMBer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.9 HISTory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-276.5.10 IDENtify Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-286.6 ORDer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-286.6.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-286.6.2 BY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-286.6.3 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-296.7 REMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-316.7.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326.7.2 REMark Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326.8 DIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326.8.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326.8.2 VERSion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-326.8.3 SCOPe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-336.8.4 DIF Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-336.9 TRACe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-336.9.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-346.9.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-346.9.3 SYMMetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-346.9.4 INDependent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-346.9.4.1 LABel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.9.4.2 STARt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.9.4.3 STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.9.5 DEPendent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.9.5.1 LABel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.9.6 TRACe Block Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-366.10 VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-366.10.1 NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-376.10.2 NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-376.10.3 ENVelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-376.10.3.1 UPPer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38


vi

6.10.3.2 LOWer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.3.3 FUNCtion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.4 RCOMPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.4.1 REAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.4.2 IMAGinary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.5 PCOMplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.5.1 MAGNitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-386.10.5.2 PHASe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-396.10.6 VIEW BLOCK EXAMPLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39

Chapter 7 Data Format Example


vii


viii

1 IntroductionThe data interchange format described in this section lets software packages and instrumentsshare waveform and other data. It is designed to be flexible and extensible, and canaccommodate a wide range of data structures and formats. In addition to describing the dataitself, the data interchange format provides information regarding the data environment,structure, and other related specifications. Only a minimum of information about the data isactually required but a wide range of information can be associated with the data. Complexdata dimensioned sets and simpler data are equally representable using the block structure ofthis data format.

Because this data format is hierarchically structured, it can be subordinate to other structures.It is suitable as a file format and its encoding formats allow it to be easily transmitted acrossIEEE 488.1/488.2, RS-232, SCSI, IEEE 802, and various other transmission media andprotocols.

The syntax of the data interchange format is compatible with IEEE 488.2 syntax. With minormodifications, an IEEE 488.2 parser, or at least its lexical analyzer, can also analyze thesyntax of this format. While the format imposes its own rules within IEEE 488.2expressions, these rules conform to the IEEE 488.2 restrictions for expressions.

1.1 OverviewThe data interchange format is block-structured. A data set generally consists of severaldescription blocks and a data block. A block contains keywords and subordinate blocks.Within a block or sub-block are keywords with values that define characteristics of the dataor the environment in which it was acquired. Many blocks accept a modifier label value andit is required for some blocks. A block modifier allows multiples of the same block type tobe distinguished from one another.

Each block addresses a different aspect of data description. The DATA block contains thedata. The IDENtify block describes the manner and environment in which the data wasobtained. The DIMension and ENCode blocks describe how the data is physicallyrepresented and logically organized. The TRACe and VIEW blocks provide semanticinformation about the data. A REMark block contains textual comments regarding the data.Finally, the DIF block identifies the block as a <dif_expression> and describes the version ofSCPI used.

DIF01This data interchange format focuses on data as an abstraction of instrument- oralgorithm-generated data. The method of data acquisition or creation is handled asdescriptive information that is not required for proper interpretation of the data. Informationabout the encoding, structure, scaling, range, etc., of the data is independent of the source ofthe data.

For example, instrument-dependent settings and characteristics such as sample rate aretranslated into acquisition independent parameters such as RESolution.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Introduction 1-1

1.2 Defined BlocksThe Data Interchange Format consists of the following major blocks:

DIF01

DIF identifies the expression as a <dif_expression> and contains the version ofthe standard used to create the data set. DIF01

REMark contains general comments in human-readable text regarding the data.

IDENtify names the data set and describes the environment in which it wasgenerated. Environment description includes project name, test number and series,date and time, and source.

ENCode specifies the encoding format for data in the DATA and ENCodeblocks. Also covered are signal values for underflow, overflow and no value, aswell as the range and resolution of the data.

DIMension specifies the structure and format of data in the DATA block.Provision is made for data scaling, offset, naming, and units specification.

ORDer specifies ordering of the data elements in the DATA(CURVe) block foreach dimension.

TRACe logically groups dimensions as functions, surfaces, sets, etc. TRACeblocks provide semantic information about the data and are used to build VIEWblocks. They also provide a convenient and powerful mechanism for subsettingdata.

VIEW provides a second level of semantic information about the data. VIEWdescribes logical relationships among traces defined in the TRACe block such asenvelope traces.

DATA contains the actual data. Different subordinate blocks describedimensioned data, waveform parameter measurements, and point values.

1.3 Implicit and Explicit DimensionsThere are many ways to describe the structure and order of dimensioned data, and not allterms are well defined or understood. The data interchange format treats all CURVe data ascoordinates in n-dimensional space. If a coordinate is actually present in the data, itsdimension is said to be explicit. If the coordinate value of a dimension is not present as adata value, but is instead derived from the location of other coordinate values, the dimensionis said to be implicit.

Suppose you mark off an evenly spaced grid on the floor of a room, and then makemeasurements of temperature and humidity at some (varying) height above the floor. As youmake these measurements, you write down the temperature and humidity measurements andthe location (X, Y, and Z positions relative to one corner of the room). The result is 5-tuple.You must write each set of measurements in a consistent order (such as X, Y, Z,temperature, and humidity), but you may write the sets of measurements in any order.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


1-2 Introduction

A 5-tuple may be viewed, as this format does, as a point in a 5-dimensional space. All fivedimensions are explicit, meaning that for each dimension, you have explicitly written downits coordinate.

Now suppose you make the measurements according to some consistent pattern. You startwith the first grid line and make the measurements sequentially at each Y point along the Xgrid line. You then make the measurements along the second X grid line, and so on, until thelast grid line is completed.

If you keep track of the order in which the measurements were made, you only need to writedown two measurements: temperature and humidity. The other three measurements (Xlocation, Y location, and height) are derivable from the order of the data. The data is still5-dimensional, but three of the dimensions are implicit and two are explicit.

Simple waveforms acquired from instruments like oscilloscopes (when clocked internally)commonly consist of a time series of voltage (vertical axis) measurements. For thetime-voltage space, only the voltage value or coordinate is provided by the oscilloscope; thetime (horizontal axis) is derived from the order of the data, an initial starting time, and ascale factor. The voltage dimension is explicit and the time dimension is implicit.

This format classifies all dimensions as implicit or explicit. The order of the data, which isessential to the correct derivation of implicit dimension coordinates or values, is strictlydefined by the ORDer block or its default values.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Introduction 1-3

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


1-4 Introduction

2 StyleThe data interchange format uses, for the most part, standard IEEE 488.2 syntactic elementsalong with the nested parentheses which together comprise an Expression type parameter(“Volume 1: Syntax and Style,” Section 8).

The format also uses the concept of “friendly” listening and “precise” talking followed byIEEE 488.2. There are some differences, which are clarified in 3 of this section.

Keywords may take single or multiple values. If a keyword takes multiple values, all valuesshall be of the same type.

A few keywords have default values. If the keyword is omitted, the default value prevails.These values are specified in the block descriptions in 6 of this section.

TK053aAn invalid set reports either a Command Error or an Execution Error as described in“Volume 2: Command Reference,” 21.8.9 and 21.8.10. While uppercase characters arespecified, lowercase characters may be accepted without error if interpretation of the data setis unambiguous.

TK053aIt is not required that a data format parser accept all values of an enumerated set (3.4.10 ofthis volume). An error may be generated on receipt of an unimplemented value.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Style 2-1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


2-2 Style

3 SyntaxThe data format is block-structured. Each hierarchical level is introduced by a block name,with its subordinate elements enclosed in parentheses. A block may have a modifier and maycontain subordinate blocks and keyword units, or both. Keyword units consist of a keywordfollowed by one or more values. If a keyword has more than one value, the values areseparated by commas.

The following example shows a simple data set. It is formatted so that all blocks andkeywords are indented to show their hierarchical relationship.

TK053a(DIF (VERSion 1993.0)IDENtify (

NAME “Data Format Example”TEST (

NUMBer “7D4", ”2.4"))ENCode (

HRANge 75LRANge 25)

DIMension=X (TYPE IMPLicitSCALe 0.01SIZE 7UNITs “S”)

DIMension=Y (TYPE EXPLicitSCALe 0.02OFFSet 0.1UNITs “V”)

DATA (CURVe (

VALues 49.0, 48.0, 50.2, 61.3, 68.5, 38.6, 48.0))) DIF01

The data interchange format overall is formatted as an IEEE 488.2 <EXPRESSIONPROGRAM DATA> element. Within this element, the various blocks, modifiers, keywords,and value types are composed of syntactic elements that, for the most part, are identical tothe corresponding types specified in IEEE 488.2 or a subset of them.

3.1 Character SetAll syntactic elements except <Block> contain only 7-bit ASCII-formatted (ANSIX3.4-1977) data with the high-order eighth bit always set to zero.

3.2 White SpaceWhite space consists of the ASCII space character, 32 decimal. A space is used along withthe parentheses, comma, and equal sign to separate syntactic elements.

DIF01

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Syntax 3-1

When an instrument accepts data, redundant white space may appear without semantic effectanywhere except within: block names, block modifiers, keywords, and all value types.

Note that the characters constituting white space may be a part of the semantic content of<String> and <Block> value types.

When an instrument sends data, redundant white space is not allowed.

3.3 Blocks, Block Modifiers, and KeywordsWhen an instrument accepts data, block names, block modifiers, and keywords conform tothe IEEE 488.2 <CHARACTER PROGRAM DATA> syntax. Abbreviated short forms andany specified aliases shall be accepted.

When an instrument sends data, the IEEE 488.2 <CHARACTER RESPONSE DATA>syntax is used. If a long and short form element is specified, the short form shall be sent.

DIF05As the data format is hierarchically organized, mnemonic generation rules for compoundheaders apply. See “Syntax and Style’” 2.2.1. Specific syntactic restrictions on the use ofblocks, block modifiers, and keywords are covered in 4 of this section.

3.4 Value TypesThe grammar employs the following value types.

3.4.1 <Numeric>The <Numeric> value type is used to specify zero, positive and negative numeric values.

When an instrument accepts data, <Numeric> follows one of the following two IEEE 488.2program data formats:

<DECIMAL NUMERIC PROGRAM DATA>, or<NON-DECIMAL NUMERIC PROGRAM DATA>

Contrary to IEEE 488.2, <Numeric> values with embedded white spaces do not have to beaccepted.

When an instrument sends data, <Numeric> follows one of the following six response dataformats:

<NR1 NUMERIC RESPONSE DATA>, <NR2 NUMERIC RESPONSE DATA>, <NR3 NUMERIC RESPONSE DATA>, <OCTAL NUMERIC RESPONSE DATA>, <BINARY NUMERIC RESPONSE DATA>, or<HEXADECIMAL NUMERIC RESPONSE DATA>

3.4.2 <+Numeric>The <+Numeric> value type is used to specify positive numeric values greater than zero.Other than this restriction, the value type is identical to <Numeric>.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


3-2 Syntax

3.4.3 <0+Numeric>The <0+Numeric> value type is used to specify positive numeric values equal to or greaterthan zero. Other than this restriction, the value type is identical to <Numeric>.

3.4.4 <NR1> DIF06The <NR1> value type is used to specify zero, positive and negative integer numeric values.

An instrument shall accept any <Numeric> value, rounding as necessary to obtain an integervalue. When an instrument sends data, <NR1> follows the IEEE 488.2 <NR1 DECIMALNUMERIC RESPONSE DATA> format.

Note that rounding may result in an invalid integer value.

3.4.5 <+NR1> DIF06The <+NR1> value type is used to specify positive integer numeric values greater than zero.Other than this restriction, the value type is identical to <NR1>.

3.4.6 <0+NR1> DIF06The <0+NR1> value type is used to specify positive numeric values equal to or greater thanzero. Other than this restriction, the value type is identical to <NR1>.

3.4.7 <Block>The <Block> value type is used to specify 8-bit, 16-bit, 32-bit, or 64-bit significant data.<Block> is only allowed for use with the DATA(CURVe(VALues)) keyword.

The FORMat keyword from the applicable ENCode block determines the interpretation ofthe data values. Bytes are grouped according to the number of bits required. For example,bytes are grouped by four’s and interpreted as a 32-bit integer for INT32.

When an instrument accepts data, <Block> values shall follow the format of IEEE 488.2<ARBITRARY BLOCK PROGRAM DATA> format with the restriction that only definitelength blocks are accepted.

When an instrument sends data, <Block> values shall follow the format of IEEE 488.2<DEFINITE LENGTH ARBITRARY BLOCK RESPONSE DATA> format.

3.4.8 <String> DIF04The <String> is used to represent quoted strings.

When an instrument accepts data, <String> data conforms to IEEE 488.2 <STRINGPROGRAM DATA> syntax.

When an instrument sends data, <String> data conforms to IEEE 488.2 <STRINGRESPONSE DATA> syntax.

3.4.9 <Label>The <Label> value type is used to represent short, unquoted string labels for block modifierand keyword values.

When an instrument accepts data, <Label> follows the IEEE 488.2 <CHARACTERPROGRAM DATA> syntax.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Syntax 3-3

When an instrument sends data, <Label> follows the IEEE 488.2 <CHARACTERRESPONSE DATA> syntax. A <Label> has no short form.

DIF05

3.4.10 Enumerated SetSome keywords specify a value from an completely enumerated set of values.

When an instrument accepts data, an enumerated set member follows the IEEE 488.2<CHARACTER PROGRAM DATA> syntax. If specified, acceptance of long and shortform as well as aliases is required.

When an instrument sends data, an enumerated set member follows the IEEE 488.2<CHARACTER RESPONSE DATA> syntax. If both a long and short form element arespecified, only the short form shall be sent.

It is not required that a data format parser accept all values of an enumerated set. An errormay be generated on receipt of an unimplemented value. See 2 of this section.

Mnemonic generation rules for character data apply. See “Syntax and Style,” 2.2.1.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


3-4 Syntax

4 GrammarDIF01This chapter specifies the grammar of the data format. This grammar describes the contents

of a <dif_expression> that represents a Data Interchange Format.

4.1 Grammar NotationThe grammar notation consists of the non-terminal symbols, pseudo-terminal symbols,meta-symbols, and terminal symbols defined below.

4.1.1 Non-terminalsNon-terminals are represented as all lowercase words.

4.1.2 Pseudo-terminalsPseudo-terminals stand for any from a set of terminal symbols (value types) as described in3.4 of this section and are represented as words bracketed between < and >.

4.1.3 Meta-symbolsIn the following table, “.” represents an arbitrary string of terminals and non-terminals. Themeta-symbols for the grammar are ->, {, }, *, +, [, ], and |.

They have the following meanings:-> Separates the left and right hand sides of a production

{ . }* The enclosed item occurs zero or more times.

{ . }+ The enclosed item occurs one or more times.

[ . ] The enclosed item occurs zero or one times.

{ . | . | . } One and only one of the two or more enclosed items separated by | occurs.

4.1.4 Terminal SymbolsTerminal symbols are represented in mixed uppercase and lowercase to indicate long andshort form (“Syntax and Style,” 1).

4.2 Grammar DescriptionTK053adif -> difid

[remark][identify][encode]{dimension}+[order]{trace}*{view}*{data}+

DIF01,03

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Grammar 4-1

TK032Adifid -> DIF([NOTE <String>]VERSion <+Numeric>[SCOPe PREamble | FULL]

)DIF01,03

remark -> REMark([NOTE <String> {,<String>}*]

)DIF03

identify -> IDENtify ([NOTE <String>][NAME <String>][TECHnician <String> {,<String>}*][PROJect <String>][DATE <NR1>,<+NR1>,<+NR1>

[,<NR1>,<+NR1>,<+NR1>]] DIF06[TIME <0+NR1>,<0+NR1>,<0+Numeric>

[,<0+NR1>,<0+NR1>,<0+Numeric>]] DIF06[UUT(

[NAME <String>][ID <String> {,<String>}*][DESign <String> {,<String>}*]

)][TEST(

[NAME <String>][SERies <String>][NUMBer <String> {,<String>}*]

)][HISTory <String> {,<String>}*]

)

TK055encode -> ENCode ([NOTE <String>][FORMat { IFP32 | IFP64

| INT8 | INT16 | INT32 | INT64 | SFP32 | SFP64| SINT16 | SINT32 | SINT64| SUINT16 | SUINT32 | SUINT64| UINT8 | UINT16 | UINT32 | UINT64 }]

[NVALue <Numeric>][ORANge <Numeric>][URANge <Numeric>][HRANge <Numeric>][LRANge <Numeric>]

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


4-2 Grammar

[RESolution <+Numeric>])

DIF03dimension -> DIMension = <Label>(

[NOTE <String>][NAME <String>]TYPE {IMPLicit | EXPLicit}[SCALe <Numeric>][OFFSet <Numeric>][SIZE <+NR1>]UNITs <String>[encode]

)DIF03

order -> ORDer ([NOTE <String>][BY {TUPLe | DIMension}]

)DIF03

trace -> TRACe = <Label>([NOTE <String>][NAME <String>][SYMMetry <String>]{INDependent(

LABel <Label>[STARt <+NR1>][STOP <+NR1>]

)}*{DEPendent(

LABel <Label>)}*

)DIF03

view -> VIEW = <Label> ([NOTE <String>][NAME <String>]{ENVelope(

UPPer <Label>LOWer <Label>[FUNCtion <Label>]

)}*)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Grammar 4-3

DIF03data -> DATA [= <Label>](

[NOTE <String>][delta][curve]{waveform}*{measurement}*

)DIF03

delta -> DELTa ([NOTE <String>]{DIMension = <Label> (

[SCALe <Numeric>][OFFSet <Numeric>][SIZE <+NR1>]

)}+[DATE <NR1>,<+NR1>,<+NR1>

[,<NR1>,<+NR1>,<+NR1>]][TIME <0+NR1>,<0+NR1>,<0+Numeric>

[,<0+NR1>,<0+NR1>,<0+Numeric>]] DIF06)

DIF03TK032Acurve -> CURVe (

[NOTE <String>][NAME <String>][CTYPe {SUM8| CRC16| CCITT | SUM16}][VALues {<Block> | <Numeric>}

[,{<Block> | <Numeric>}]*][CSUM <+NR1>]

)

TK032ANOTE: The presence of VALues is conditional on the DIF(SCOPe) keyword; refer to theRequired Blocks, section 4.3.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


4-4 Grammar

DIF03waveform -> WAVeform[= <Label>](

[NOTE <String>][NAME <String>][TRACe <Label>][HLMethod <String>][HIGH <Numeric>][LOW <Numeric>][REFerence(

[HIGH <Numeric>][LOW <Numeric>][MID <Numeric>][METHod <String>]

)][AMPLitude <Numeric>][PWIDth <Numeric>][NWIDth <Numeric>][PERiod <Numeric>][FREQuency <Numeric>][PDUTycycle| DCYCle <Numeric>][NDUTycycle <Numeric>][RISE(

[TIME <Numeric>][OVERshoot <Numeric>][PREShoot <Numeric>]

)][FALL(


)][MAXimum <Numeric>][MINimum <Numeric>][TMAXimum <Numeric>][TMINimum <Numeric>][MEAN <Numeric>][RMS <Numeric>][SDEViation <0+Numeric>][PTPeak <0+Numeric>][CYCLe(

[COUNt <0+Numeric>][MEAN <Numeric>][RMS <Numeric>][SDEViation <0+Numeric>]

)]) DIF03

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Grammar 4-5

measurement -> MEASurement [= <Label>]([NOTE <String>][NAME <String>][UNITs <String>][TYPE <String>][TRACe <Label>]{LOCation (

LABel <Label>INDex <+NR1>

)}*[VALues <Numeric> {,<Numeric>}*]

)

4.3 Required BlocksNote that a data set shall contain a DIF block and at least one DIMension and one DATAblock.

DIF01All TRACe blocks referenced by keywords in the VIEW and DATA blocks shall be present.All DIMension blocks referenced by LABel keywords in the TRACe block shall be present.

TK032aIf the DIF(SCOPe) keyword is not present or is set to FULL, any CURVe block shall containa VALues keyword and parameters. If DIF(SCOPe) is present and set to PREamble,VALues keywords and parameters shall be omitted from all CURVe blocks.

4.4 Required OrderWhen an instrument accepts data, certain blocks shall be sent in the following order:

DIF DIF01ENCodeDIMensionTRACeVIEWDATA

In addition, the ORDer must appear before the DATA block. The REMark and IDENtifyblocks may appear anywhere after the DIF block.

DIF01Within the DATA block, the DELTa sub-block shall precede all other sub-blocks.

Within a block, individual keywords may also be accepted in any order with the exceptionthat the CTYPe keyword must come before the VALues keyword.

When an instrument sends data, the block and keyword order specified in the grammar isrequired.

4.5 Unrecognized Keywords and Blocks DIF03A listener is not required to interpret all keywords and blocks present in a data set, but onlythose required for the type of data of interest. For example, all listeners must interpret mostkeywords and sub-blocks in the DIF, DIMension, ENCode, and ORDer blocks since

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


4-6 Grammar

information contained in these blocks is required for the correct interpretation of data in theDATA block. Exceptions are keywords such as NOTE, RESolution, HRANge, etc. Otherkeywords and blocks may or may not be of interest to a listener. For example, a listener thatseeks only WAVeform data will ignore CURVe data, and vice versa.

This is consistent with the philosophy that different listeners may accept the same data setbut use it for different purposes. In addition, the data format provides an extensionmechanism that is designed to allow older listeners to accept newer data sets that maycontain new keywords and sub-blocks. See 5 of this section for further details on extensionmechanisms.

Therefore, listeners must be able to ignore unrecognized (but syntactically correct) keywordsand blocks. The extent, if any, to which a listener notifies a user that an unrecognizedkeyword or block was encountered; and, the extent, if any, of required user action isimplementation dependent.

Note that a block name is always followed by an open parenthesis; or, an equal sign,modifier, and open parenthesis sequence. This following structure may be ignored bysearching forward to the matching closing parenthesis. A keyword is always followed by oneor more comma separated values.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Grammar 4-7

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


4-8 Grammar

5 Data Format ExtensionsThis format may be extended and enhanced with one of the following two methods.

5.1 ExtensionsKeywords, blocks (sub-blocks) may be created to accomodate information that is nototherwise provided for by existing keywords or blocks. This method of extension can bedone without conflict because parsers ignore unknown keywords and blocks. Name aliasesmay be specifed for the new keywords or blocks. However, the use of aliases is stronglydiscouraged and should only be provided if there is widespread industry usage of more thanone name.

5.2 EnhancementsA second method of extension involves replacing an existing keyword with a sub-block ofthe same name. This method is used when the semantic information represented by anexisting keyword is insufficient. The replacement sub-block shall include a keyword thatrepresents the exact same semantic information (including the same value type and range) ofthe original keyword. This keyword is distinguished from all other keywords in the newsub-block by appending an underscore to it. No alias names may be added for the newsub-block.

A parser which was implemented before the extension was made recognizes this specialkeyword by the presence of the underscore and then takes the value associated with thisflagged keyword and assigns it to the old keyword. The remainder of the sub-block isdiscarded.

HP072

5.3 Extension ExampleSuppose sometime in the future a need for a sub-block under RANGe is recognized. In thisversion the syntax for RANGe is:

RANGe <+Numeric>

The extended syntax might appear as:RANGe (

HIGH_ <+Numeric>[LOW <+Numeric>][OVER <+Numeric>]

)

A newer implementation would understand the meaning for all three values under RANGe.An older parser takes the values associated with the flagged keyword in the sub-block, in thiscase, HIGH_, and uses its value as the value for RANGe. Since the older parser has no needfor the LOW and OVER values, they are discarded.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Data Format Extensions 5-1

This extension can be continued. At some even later date, more sub-blocks are needed. Thesyntax might now become:

RANGe (HIGH_ (

EXPected_ <+Numeric>[ALLowed <+Numeric>]

)LOW (


)OVER (


))

The original parser could still successfully determine which value to associate with the oldkeyword RANGe and safely discard the rest. Both the intermediate and newest parsers canhandle this syntax without conflict.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


5-2 Data Format Extensions

6 Block DescriptionsThis chapter details all of the block descriptions for the data interface format.

6.1 Top Level Block Organization DIF01The entire data set is composed of the following sequence of mandatory and optional blocks.

TK053adif -> difid[remark][identify][encode]{dimension}+[order]{trace}*{view}*{data}+

TK053aA data set is built from the blocks described in 6.2 through 6.10 of this section.

6.2 DATA DIF03A DATA block contains the data of primary interest. It may contain dimensioned data suchas DATA(CURVe), or specific sets of data (WAVeform, etc.). At least one DATA block isrequired, and multiple DATA blocks are allowed. A DATA block is defined as:

DIF03data -> DATA [= <Label>](

[NOTE <String>][delta][curve]{waveform}*{measurement}*

)

<Label> is optional and allows for the unique identification of the DATA block; no twoDATA blocks may have the same <Label> value within a data set.

The subordinate blocks within a particular DATA block are assumed to be related. That is, ifCURVe and WAVeform measurements are present in the same DATA block, theWAVeform measurements are assumed to have been derived from the CURVe data. If thatis not the case, different DATA blocks should be used for the CURVe and WAVeformmeasurements.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Block Descriptions 6-1

6.2.1 NOTE DIF03This is arbitrary text.

Value type is <String>. Text should be human-readable. Only one occurrence of the NOTEkeyword is allowed and only one value is allowed.

Example: NOTE “Humidity was 45%”

6.2.2 DELTa DIF03A DELta sub-block provides for sequences of closely related data. When a data set containsmultiple occurrences of DATA blocks, the DELta block differentiates the characteristics ofeach of the DATA blocks. Note that the DELta block is limited to redefining descriptiveinformation, encoding information, and dimension size, such as SCALe, DATE, andOFFSet. A DELta block cannot change the organization of the data, such as the number ofdimensions or the data ordering.

The values specified in a DELta block override those specified at a higher hierarchical level.For example, the value for SCALe in the DATA(DELta(DIMension)) block overrides thevalue for SCALe in the higher level DIMension block, but only for data within the DATAblock that contains the DELta block. If there are multiple DATA blocks with subordinateDELta blocks, the DELta blocks have no effect on each other; that is, they each individuallyspecify a modification of the same (higher level) IDENtify, DIMension, or ENCode block.

The DELta sub-block may occur only once and, if present, shall be the first block in theDATA block. The DELta sub-block is defined as:

DIF03delta -> DELTa(

[NOTE <String>]{DIMension = <Label> (

[SCALe <Numeric>][OFFSet <Numeric>][SIZE <+NR1>]

)}+[DATE <NR1>,<+NR1>,<+NR1>


[,<0+NR1>,<0+NR1>,<0+Numeric>]] DIF06)

6.2.2.1 NOTE DIF03This is arbitrary text.


Example: NOTE “Sequence 43”

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


6-2 Block Descriptions

6.2.2.2 DIMension The DIMension sub-block is a limited subset of the higher level DIMension block (see 6.3 inthis section). The <Label> modifier is required and is restricted to a value defined by the<Label> of a DIMension block at the same hierarchical level as the DATA block.

6.2.2.2.1 SCALe DIF03This is the scale value for the dimension specified by the DIMension sub-block <Label>.

Value type is <Numeric>. SCALe may occur only once. See SCALe in 6.3 in this section foradditional definition and restrictions.

Example: SCALe 1E-2

6.2.2.2.2 OFFSetThis is the offset value for the dimension specified by the DIMension sub-block <Label>.

Value type is <Numeric>. OFFSet may occur only once. See OFFSet in 6.3 in this sectionfor additional definition and restrictions.

Example: OFFSet 6.0E-1

6.2.2.2.3 SIZE DIF03The size value for the dimension specified by the DIMension sub-block <Label>.

Value type is <+NR1>. SIZE may occur only once. See SIZE in 6.3 in this section foradditional definition and restrictions.

Example: SIZE 2048

6.2.2.3 DATE DIF03This is the date of data creation or acquisition.

DIF06This keyword takes a set of three comma separated value types to specify the datecorresponding to year, month, and day.

DIF06The years parameter is type <NR1>. It always includes century and millennium information.

DIF06The months parameter is type <+NR1>. Its range is 0 to 12.

DIF06The days parameter is type <+NR1>. Its range is 0 to 31 (depending on the month).

DIF06If two sets of values are specified, they define an inclusive range of dates.

DIF06Example: DATE 1990,01,01,1992,10,11 indicates a range of dates from January 1, 1990through October 11, 1992.

DIF06

6.2.2.4 TIME DIF03This is the time of data creation or acquisition.

DIF06This keyword takes a set of three comma separated value types to specify the timecorresponding to hour, minute, and second.

DIF06The hours parameter is type <0+NR1>. Its range is 0 to 23. This parameter is alwaysexpressed in 24 hour format.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



DIF06The minutes parameter is type <0+NR1>. Its range is 0 to 59.

DIF06The seconds parameter is type <0+Numeric>. Its range is 0 to 60 for instruments receivingdata and 0 to 59.999... for instruments sending data.

DIF06If two sets of values are specified, they define an inclusive range of time.

DIF06Example: TIME 9,0,59.095,13,1,0 indicates a range of time from 59.095 seconds after 9 AMto one minute after 1 PM.

DIF06

6.2.3 CURVeCurve data is dimensioned. Values may be organized as n-tuples or by dimension. This isdetermined by the ORDer block or, in its absence, the defaults for the BY keyword in theORDer block.

Only one occurrence of CURVe is allowed in a DATA block. The CURVe block is definedas: DIF03

TK032acurve -> CURVe([NOTE <String>][NAME <String>][CTYPe {SUM8| CRC16| CCITT | SUM16}][VALues {<Block> | <Numeric>}

[,{<Block> | <Numeric>}]*][CSUM <+NR1>]

)

TK032aThe presence of VALues is conditional on the DIF(SCOPe) keyword; refer to the RequiredBlocks, section 4.3.



Example: NOTE “Data taken with low line voltage”

6.2.3.2 NAME DIF03This is an arbitrary name or description of the curve.

Value type is <String>. It is recommended that the string length be 32 characters or less.NAME may occur only once and only one value is allowed.

Example: NAME “DS1C”

6.2.3.3 CTYPe DIF03This indicates the checksum type or the absence of a checksum.

CTYPe takes a specified enumerated set of values. CTYPe may occur only once and requiresone and only one of the following enumerated set values:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



CRC16 16-bit cyclic redundancy check code. x16 + x15 +x2 + 1. (default)CCITT 16-bit cyclic redundancy check code. x16 + x12 +x5 + 1.SUM8 8-bit longitudinal redundancy check code (8 bit sum). x8 + 1.

(SUM8 is provided for compatibility and its use is discouraged).SUM16 16-bit longitudinal redundancy check code (16 bit sum). x16 + 1.NONE indicates there is no checksum.

See “IEEE Micro”, Vol 8, No 4, August 1988, pp 62-76.

Note that CTYPe must preceed the VALues keyword.

Example: CTYPe SUM8

6.2.3.4 VALuesThis specifies the data values.

TK032aValue type is <Block> or <Numeric>. Multiple values are allowed.

TK032aVALues shall occur exactly once if the DIF(SCOPe) keyword is not present or is set toFULL. If DIF(SCOPe) is present and set to PREamble, VALues shall be omitted.

TK053aThe physical format of each value is determined by the FORMat keyword of the ENCodeblock that applies. If the dimension has a subordinate ENCode block, the subordinateENCode block prevails; otherwise the ENCode block at the same hierarchical level as theDIMension blocks prevails.

Example: VALues 1.2, 3.3, 4.5, 2.7, 0.4

6.2.3.5 CSUM DIF03This indicates the checksum for DATA(CURVe(VALues)) data

Value type is <+NR1>.

The checksum is computed according to the rules specified by CTYPe. If data is formatted in<Numeric> value type, the checksum is computed using the 8-bit ASCII decimal equivalentof each character of the number. This includes all signs, decimal points, and exponentcharacters but not white space.

CSUM may occur only once and takes only one value.

Example: CSUM 27

6.2.4 WAVeformThis block describes waveform parameter measurements of a two dimensional waveform.The descriptions assume a single-valued function of time in which the independentdimension is the time dimension. However, the actual units are specified in the DIMensionblock and it is possible to represent other quantities which are not functions of time.

Multiple occurrences of WAVeform are allowed. The WAVeform block is defined as:

DIF03

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



waveform -> WAVeform[= <Label>]([NOTE <String>][NAME <String>][TRACe <Label>][HLMethod <String>][HIGH <Numeric>][LOW <Numeric>][REFerence(

[HIGH <Numeric>][LOW <Numeric>][MID <Numeric>][METHod <String>]

)][AMPLitude <Numeric>][PWIDth <Numeric>][NWIDth <Numeric>][PERiod <Numeric>][FREQuency <Numeric>][PDUTycycle| DCYCle <Numeric>][NDUTycycle <Numeric>][RISE(


)][FALL(


)][MAXimum <Numeric>][MINimum <Numeric>][TMAXimum <Numeric>][TMINimum <Numeric>][MEAN <Numeric>][RMS <Numeric>][SDEViation <0+Numeric>][PTPeak <0+Numeric>][CYCLe(

[COUNt <0+Numeric>][MEAN <Numeric>][RMS <Numeric>][SDEViation <0+Numeric>]

)])

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



In the absence of a TRACe block, the following rules are used to determine the independentand dependent dimensions:

1. The independent dimension is the first implicit dimension or, if no implicitdimensions are present, then the first explicit dimension

2. The dependent dimension is the first explicit dimension if there is at least oneimplicit dimension. Otherwise it is the second explicit dimension.

The block modifier <Label> value is optional and allows for the unique identification of theWAVeform block. No two WAVeform blocks may have the same <Label> within the sameDATA block.

If WAVeform measurements are found together with a CURVe block in a DATA block,they are considered to be derived from or related to the CURVe data (or a subset of it).However, the exact relationship of waveform measurements to the data can be determinedonly if the TRACe keyword is present.

It is permissible for a data set to contain waveform measurements without a DATA(CURVe)block, but DIMension blocks for the independent and dependent dimensions shall still bespecified.

Waveform measurements derived from DATA block data are considered to have beenderived from the data after SCALe and OFFSet (specified in the DIMension block) havebeen applied. WAVeform measurements are derived from DIMension block units.

Note that this standard requires the syntax for WAVeform data to be correct, but makes noclaim for the correctness or consistency of the data values. Keywords in the WAVeformblock are representative of terms generally used in the industry. Keyword descriptions aregeneral and, except where specifically provided (such as for HLMethod), no requirement forspecific calculation methods are claimed.

The definitions for functions and settings within the waveform block are illustrated with thefollowing figure:

Figure 6-1 Waveform Terminology

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.2.4.1 NOTE DIF03This is arbitrary text. Text should be human-readable.

Value type is <String>. Only one occurrence of the NOTE keyword is allowed and one valueis allowed.

Example: NOTE “500 ps Reference Waveform”

6.2.4.2 NAME DIF03This is an arbitrary name of the waveform measurement. Typically, NAME is moredescriptive than the WAVeform block modifier <Label> value and it does not have to beunique.


Example: NAME “Frame bit”

6.2.4.3 TRACe DIF03This is the TRACe from which the waveform parameters were extracted. TRACe allows asub-set of the data to be referenced.

Value type is <Label>. Only values defined by a TRACe block modifier <Label> value areallowed.

Only one occurrence of TRACe is allowed and only one value is allowed. The TRACereferenced shall be two-dimensional.

Example: TRACe Y2

6.2.4.4 HLMethodThis notes the method used to determine the HIGH and LOW magnitudes.

For IEEE 181 methods, HIGH becomes the more positve (less negative) and LOW becomesthe more negative (less positive) of the Top Magnitude and Base Magnitude values asdefined by IEEE 194, sections 3.2.1 and 3.2.2.

Value type is <String>. It is recommended that the string length be 32 characters or less. Thefollowing values are predefined: UNKNOWN Unknown or Unspecified. Default. MEAN Mean of Density Algorithm (IEEE 181, section 4.3.1.1) MODE Mode of Density Algorithm (IEEE 181, section 4.3.1.2) PEAK Peak Magnitude (IEEE 181, section 4.3.1.4) ABSOLUTE Absolute, user-specified levels

Example: HLMethod “MEAN”

6.2.4.5 HIGHIndicates the high magnitude.

Value type is <Numeric>. Value is required if keyword is present. HIGH may occur onlyonce and only one value is allowed. Units are of the dependent dimension (signal value).

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: HIGH 4.2

6.2.4.6 LOWThis is the low magnitude.

Value type is <Numeric>. Value is required if keyword is present. LOW may occur onlyonce and only one value is allowed. Units are of the dependent dimension (signal value).

Example: LOW -0.21

6.2.4.7 REFerenceThe REFerence sub-block contains reference level information used to calculate otherparameters in the WAVeform block.

6.2.4.7.1 HIGHIndicates the high or upper reference level for measurement of rise and fall time.

Value type is <Numeric>. Value is required if keyword is present. HIGH may occur onlyonce and only one value is allowed. Units are of the dependent dimension (signal value).

Example: HIGH 4.8

6.2.4.7.2 LOWThis is the low or lower reference level for measurement of rise and fall time.

Value type is <Numeric>. Value is required if keyword is present. LOW may occur onlyonce and only one value is allowed. Units are of the dependent dimension (signal value).

Example: LOW 0.3

6.2.4.7.3 MIDThis is the mid reference level for measurement of width, duty cycle, and period.

Value type is <Numeric>. Value is required if keyword is present. MID may occur only onceand only one value is allowed. Units are of the dependent dimension (signal value).

Example: MID 3.3

6.2.4.7.4 METHodThis is the reference method. Notes the method used to determine HIGH, LOW, and MIDREFerence level values.

Value type is <String>. It is recommended that the string length be 32 characters or less. Thefollowing values are predefined:

UNKNOWN Unknown or unspecified (default).RELATIVE Reference levels are set according to percentages of amplitude

given by:

high_percentage=(WAVeform(REFerence(HIGH))−WAVeform(LOW))∗100WAVeform(AMPLitude)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



low_percentage=(WAVeform(REFerence(LOW))−WAVeform(LOW))∗100WAVeform(AMPLitude)

mid_percentage=(WAVeform(REFerence(MID))−WAVeform(LOW))∗100WAVeform(AMPLitude)

ABSOLUTE Reference levels set in absolute signal value units.

Example: METHod “RELATIVE”

6.2.4.8 AMPLitudeWaveform amplitude. HIGH minus LOW.

Value type is <Numeric>. Value is required if keyword is present. AMPLitude may occuronly once and only one value is allowed. Units are of the dependent dimension (signal value).

Example: AMPLitude 4.03

6.2.4.9 PWIDthIndicates positive width. Duration from a positive mid-reference crossing followed by atleast one high-reference crossing to the following negative mid-reference crossing.

Value type is <Numeric>. Value is required if keyword is present. PWIDth may occur onlyonce and only one value is allowed. Units are of the independent dimension (time).

Example: PWIDth 2.6E-7

6.2.4.10 NWIDthIndicates negative width. Duration from a negative mid-reference crossing followed by atleast one low-reference crossing to the following positive mid-reference crossing.

Value type is <Numeric>. Value is required if keyword is present. NWIDth may occur onlyonce and only one value is allowed. Units are of the independent dimension (time).

Example: NWIDth 2.5E-7

6.2.4.11 PERiodThis is the repetition period. Duration from a mid-reference crossing (whether positive ornegative) followed by at least one high-reference crossing and at least one low-referencecrossing to the following mid-reference crossing in the same direction as the firstmid-reference crossing.

Value type is <Numeric>. Value is required if keyword is present. PERiod may occur onlyonce and only one value is allowed. Units are of the independent dimension (time).

Example: PERiod l.602E-6

6.2.4.12 FREQuencyThis is the frequency. FREQuency is the reciprocal of PERiod.

Value type is <Numeric>. Value is required if keyword is present. FREQuency may occuronly once and only one value is allowed. Units are the reciprocal of the PERiod units.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: FREQuency l.87222E+9

6.2.4.13 PDUTycycle | DCYCleIndicates the positive dutycycle. Ratio of PWIDth to PERiod.

Value type is <Numeric>. Value is required if keyword is present. PDUTycycle may occuronly once and only one value is allowed. Units are dimensionless.

Example: PDUTycycle .48

6.2.4.14 NDUTycycleIndicates the negative dutycycle. Ratio of NWIDth to PERiod.

Value type is <Numeric>. Value is required if keyword is present. NDUTycycle may occuronly once and only one value is allowed. Units are dimensionless.

Example: NDUTycycle .52

6.2.4.15 RISEThis sub-block deals with the first rising transition of the waveform where rising is definedas increasing data values.

6.2.4.15.1 TIMEThis is the rise time (positive going transition). The first time interval during which theinstantaneous amplitude of a waveform increases from the low reference point, REF (LOW),to the high reference point, REF (HIGH).

Value type is <Numeric>. Value is required if keyword is present. TIME may occur onlyonce and only one value is allowed. Units are of the independent dimension (time).

6.2.4.15.2 OVERshootThis is the rising edge overshoot. The difference between the HIGH level and the positivepeak signal value to which the waveform initially rises expressed as a percentage of thewaveform amplitude.

Value type is <Numeric>. OVERshoot may occur only once and only one value is allowed.

Example: OVERshoot 20.5

6.2.4.15.3 PREShootThis is the rising edge preshoot. The difference between the LOW level and the negativepeak signal value to which the waveform initially falls expressed as a percentage of thewaveform amplitude.

Value type is <Numeric>. PREShoot may occur only once and only one value is allowed.

Example: PREShoot 1.2

6.2.4.16 FALLThis sub-block deals with the first falling transition of the waveform where falling is definedas decreasing data values.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.2.4.16.1 TIMEIndicates the fall time (negative going transition). The first time interval during which theinstantaneous amplitude of a waveform decreases from the high reference point, REF(HIGH), to the low reference point, REF (LOW).

Value type is <Numeric>. Value is required if keyword is present. TIME may occur onlyonce and only one value is allowed. Units are of the independent dimension (time).

6.2.4.16.2 OVERshootThis is the falling edge overshoot. The difference between the LOW level and the negativepeak signal value to which the waveform initially falls expressed as a percentage of thewaveform amplitude.

Value type is <Numeric>. OVERshoot may occur only once and only one value is allowed.

Example: OVERshoot 12.62

6.2.4.16.3 PREShootThis is the falling edge preshoot. The difference between the HIGH level and the positivepeak signal value to which the waveform initially rises expressed as a percentage of thewaveform amplitude.

Value type is <Numeric>. PREShoot may occur only once and only one value is allowed.

Example: PREShoot 4.3

6.2.4.17 MAXimumThis is the maximum value of the entire waveform as specified by TRACe.

Value type is <Numeric>. MAXimum may occur only once and only one value is allowed.Units are of the dependent dimension (signal value).

Example: MAXimum 4.5903

6.2.4.18 MINimumThis is the minimum value of the entire waveform as specified by TRACe.

Value type is <Numeric>. MINimum may occur only once and only one value is allowed.Units are of the dependent dimension (signal value).

Example: MINimum -0.12

6.2.4.19 TMAXimumThis indicates the time of the first MAXimum value in the waveform as specified byTRACe.

Value type is <Numeric>. TMAXimum may occur only once and only one value is allowed.Units are of the independent dimension (time).

Example: TMAXimum 9.51

6.2.4.20 TMINimumThis indicates the time of the first MINimum value in the waveform as specified by TRACe.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Value type is <Numeric>. TMINimum may occur only once and only one value is allowed.Units are of the independent dimension (time).

Example: TMINinum 3.876

6.2.4.21 MEANThis is the arithmetic mean. Mean value of the entire waveform as specified by TRACe.

Value type is <Numeric>. MEAN may occur only once and only one value is allowed. Unitsare of the dependent dimension (signal value).

Example: MEAN 2.025

6.2.4.22 RMSThis is the root mean square. Root mean square value of the entire waveform as specified byTRACe.

Value type is <Numeric>. RMS may occur only once and only one value is allowed. Unitsare of the dependent dimension (signal value).

Example: RMS 12.3

6.2.4.23 SDEViationThis is the standard deviation. The standard deviation of the entire waveform as specified byTRACe.

Value type is <0+Numeric>. SDEV may occur only once and only one value is allowed.Units are of the dependent dimension (signal value).

Example: SDEVeviation 45.68

6.2.4.24 PTPeakThis is the waveform Peak-to-peak value. Peak-to-peak value of the entire waveform asspecified by TRACe. PTPeak is equivalent to the MAXimum minus the MINimum values.

Value type is <0+Numeric>. PTPeak may occur only once and only one value is allowed.Units are of the dependent dimension (signal value).

Example: PTPeak 4.5

6.2.4.25 CYCLeThe CYCLe sub-block specifies parameters dealing with a specified number of completecycles in the waveform as specified by the COUNt field.

6.2.4.25.1 COUNtThis is the the cycle count representing the number of cycles used for MEAN, RMS, andSDEViation in the CYCLe sub-block. Cycle count evaluates to an integer representing thenumber of cycles over which the CYCLe parameters apply. Default value for COUNt is 1.

If one complete cycle is not present, and COUNt is specified then the value should be zero.In this case, any related CYCLe parameters are meaningless.

Value type is <0+Numeric>. COUNt may occur only once and only one value is allowed.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: COUNt 10

6.2.4.25.2 MEANThis is the cycle arithmetic mean. This indicates the mean value of the waveform asspecified by COUNt.

Value type is <Numeric>. MEAN may occur only once and only one value is allowed. Unitsare of the dependent dimension (signal value).

Example: MEAN 2.025

6.2.4.25.3 RMSThis is the cycle root mean square. It indicates the root mean square value of the waveformas specified by COUNt.

Value type is <Numeric>. RMS may occur only once and only one value is allowed. Unitsare of the dependent dimension (signal value).

Example: RMS 12.3

6.2.4.25.4 SDEViationThis is the cycle standard deviation. This indicates the standard deviation of the entirewaveform as specified by COUNt.

Value type is <0+Numeric>. SDEV may occur only once and only one value is allowed.Units are of the dependent dimension (signal value).

Example: SDEViation 45.68

6.2.5 MEASurement DIF03This is the measurement of one or more specified data points. This block contains data thatdoes not fit in other sub-blocks of the DATA block. A MEASurement block may occurmultiple times, but is not required.

The MEASurement sub-block is defined as:DIF03

measurement -> MEASurement [= <Label>]([NOTE <String>][NAME <String>][UNITs <String>][TYPE <String>][TRACe <Label>]{LOCation (

LABel <Label>INDex <+NR1>

)}*[VALues <Numeric> {,<Numeric>}*]

)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



The block modifier <Label> value is optional and allows for the unique identification of theMEASurement sub-block. As all <Label> values are unique, no two MEASurementsub-blocks may have the same <Label> within the same DATA block.

The TRACe keyword allows association of the measurement or point with an arbitrarysubset of DATA(CURVe) data.

Measurements derived from DATA block data are considered to have been derived from thedata after SCALe and OFFSet (specified in the DIMension block) have been applied.



Example: NOTE “This data is retest of test 14”

6.2.5.2 NAME DIF03This is an arbitrary name of the measurement or point. NAME is typically more descriptivethan the MEASurement block modifier <Label> and it does not have to be unique.


Example: NAME “Trigger pattern 4”

6.2.5.3 UNITs DIF03This indicates units, such as Volts, Amps, Hz, etc without multipliers.

Value type is <String>. It is recommended that the string length be 32 characters or less.These units may differ from those specified in other DIMension blocks since the valuesrepresented herein may be derived or ancillary values.

Recommended units are those specified by IEEE 488.2 <SUFFIX PROGRAM DATA>, thenull string, and UNKNOWN. The null string implies that the data has no dimensional unitsand UNKNOWN indicates that the units are unknown.

DIF02If the TRACe keyword is present, the UNITs value may differ from that of the trace. Onlyone occurrence of UNITs is allowed and only one value is allowed. If omitted, the units areas specified in the DIMension block.

Example: UNITs A

6.2.5.4 TYPE DIF03This indicates the type of measurement or point.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of TYPE is allowed and only one value is allowed.

The one defined type is:

UNKNOWN Unknown (default)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: TYPE “UNKNOWN”

6.2.5.5 TRACe DIF03This is the trace associated with the point(s). TRACe allows a sub-set of the data to bereferenced.

Value type is <Label>. Only values defined by the TRACe block modifier <Label> value areallowed. Only one occurrence of TRACe is allowed and only one value is allowed. If thiskeyword is present, it determines which dimensions shall be included in the LOCationsub-block for MEASurement.

Example: TRACe ADDR

6.2.5.6 LOCation This specifies the label and index for one independent dimension. This sub-block is optionaland may occur multiple times. There shall be a LOCation sub-block with a label value foreach independent dimension present, or if a TRACe keyword is specified, then for eachindependent dimension in the specified trace.

6.2.5.6.1 LABelThis is the label of the independent dimension.

Value type is <Label>. Only values previously defined by a DIMension block modifier<Label> value are allowed and the dimension shall be implicit. LABel is required and mayoccur only once. Only one value is allowed.

Example: LABel A1

6.2.5.6.2 INDexThis specifies the index for the point.

Value type is <+NR1>. INDex is required and only one occurrence of INDex is allowed.

Example: INDex 274

6.2.5.7 VALuesThis indicates the data value(s).

Value type is <Numeric>. VALues is optional and may occur only once. Multiple values areallowed.

Example: VALues 25.3, 93.7

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.2.6 DATA Block Example

DATA (NOTE “File 1A-23”DELTa (

DIMension=Y(SCALe 0.1OFFSet 12.3SIZE 4096)

DATE 1988,9,2TIME 23,3,0.25)

CURVe (NAME “”CTYPe CRC16VALue 23.2,14.5,16.02,12.0CSUM 45)

WAVeform (NAME “19th Pulse”TRACe ZHLMethod “MODE”AMPLitude 3.902PWIDth 2.6E-7PDUTycycle 32.4RISE (

TIME 2.8E-8)FALL (

TIME 2.703E-8)REFerence (

HIGH 5.85E-5LOW 5.14E-5MID 5.32E-5)

RMS 6.4 PTPeak 12.5)))

6.3 DIMensionEach DIMension block describes one dimension of DATA(CURVe) data. A dimension maybe either explicit, in which case values are present in the DATA(CURVe) block, or implicit,in which case the values are not present, but are instead generated by a function. See 1.3 inthis section. The order in which dimensions appear determines the data ordering in theDATA block.

The DIMension and ORDer blocks describe the logical structure and organization of data inthe DATA(CURVe) block. The ENCode block describes the physical representation orencoding of the data. The ORDer block describes the ordering of the dimensional dataelements in the DATA(CURVe) block. Together they provide the sufficient and necessaryinformation for correct extraction of the data.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Whether a dimension is to be considered an independent or dependent dimension isdetermined by the TRACe block. In the absence of a TRACe block, the following simplerule is applied: if one or more implicit dimensions are present, they are considered to beindependent, and all explicit dimensions are considered to be dependent.

A DIMension block is required for each dimension of the data (implicit and explicit). TheDIMension block is defined as:

DIF03dimension -> DIMension = <Label>(

[NOTE <String>][NAME <String>]TYPE {IMPLicit | EXPLicit}[SCALe <Numeric>][OFFSet <Numeric>][SIZE <+NR1>]UNITs <String>[encode]

)

Each dimension is uniquely distinguished by its required block modifier <Label> value. Notwo DIMension blocks may have the same <Label> value. Dimension labels should be keptshort, yet meaningful.



Example: NOTE “DS1C at test point 12”

6.3.2 NAME DIF03This is an arbitrary name or description of the dimension. NAME is typically moredescriptive than the dimension block label.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of NAME is allowed and only one value is allowed.

Example: NAME “DS1C Voltage/Amplitude”

6.3.3 TYPE DIF03This indicates if the dimension is implicit or explicit.

TK053aTYPE takes a specified enumerated set of values. TYPE is required, may occur only once,and takes one of the two following enumerated set values:

DIF03IMPLicit Values for this dimension are not in DATA(CURVe),

but are derived from a linear function, y = mx + b.DIF03

EXPLicit Values for this dimension are present in DATA(CURVe).Example: TYPE EXPL

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.3.4 SCALe DIF03Scaling factor to be applied to the dimension’s values in DATA(CURVe(VALues)).

Value type is <Numeric>. Default value is 1.0. Only one occurrence of SCALe is allowedand only one value is allowed. The SCALe value may be overridden byDATA(DELTa(DIMension(SCALe))).

SCALe is always applied to DATA(CURVe) data, but not to any other data, such asDATA(WAVeform).

For implicit dimensions: X’ = (SCALe * i) + OFFSet i = 1 to SIZE

For explicit dimensions: X’ = (SCALe * X) + OFFSet

where X is a value from DATA(CURVe(VALues)). Also see Section 5.6, ORDer.

Example: SCALe 0.5E-2

6.3.5 OFFSet DIF03Offset factor to be applied to the dimension’s values in DATA(CURVe(VALues)).

Value type is <Numeric>. Default value is zero. Only one occurrence of OFFSet is allowedand only one value is allowed. The OFFSet value may be overridden byDATA(DELTa(DIMension(OFFSet))).

OFFSet is always applied to DATA(CURVe) data, but not to any other data, such asDATA(WAVeform).

For implicit dimensions: X’ = (SCALe * i) + OFFSet i = 1 to SIZE

For explicit dimensions: X’ = (SCALe * X) + OFFSet

X is a value from DATA(CURVe(VALues)).

Example: OFFSet -1.0E-2

6.3.6 SIZE DIF03This is the number of points or values in the dimension.

Value is type <+NR1>. Only one occurrence of SIZE is allowed and only one value isallowed. The SIZE value may be overridden by DATA(DELTa(DIMension(SIZE))).

The following two invariants hold:1. All explicit dimensions must have the same SIZE value.2. The product of the SIZE values of the implicit dimensions

must equal the SIZE value of any explicit dimension.If SIZE is not specified for a dimension, it is assumed to be consistent with the aboveinvariants. It is an error if there is insufficient information to determine a dimension’s SIZE.For example, SIZE cannot be determined if two or more implicit dimensions do not specify a

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



SIZE, nor can it be determined if two or more explicit dimensions specify different SIZEvalues.

It is strongly recommended that SIZE be specified for all dimensions whenever possible.

Example: SIZE 512

6.3.7 UNITs DIF03This indicates units, such as Volts, Amps, Hz, etc. Multipliers are not allowed.

Value type is <String>. It is recommended that the string length be 32 characters or less.Recommended units are those specified by IEEE 488.2 <SUFFIX PROGRAM DATA>, thenull string, and UNKNOWN. The null string implies that the data has no dimensional unitsand UNKNOWN indicates that the units are unknown or unspecified. UNITs is required andonly one occurrence of UNITs is allowed.

DIF02Example: UNITs “V”

6.3.8 ENCodeAn ENCode sub-block may appear subordinate to a DIMension block. TheDIMension(ENCode) block keywords and sub-blocks are the same as the major ENCodeblock described in 6.4 in this section. They define data resolution, special range values, andencoding format for <Block> value type data.

The scope of a DIMension(ENCode) block includes only the DATA(CURVe) block and theDIMension(ENCode) block itself. The scope of the major ENCode block includes all othervalues in the DATA block.

Each keyword specified in a DIMension(ENCode) block overrides the correspondingkeyword in the major ENCode block,but only for the values in the DATA(CURVe) block forthe specific dimension.

Only one ENCode block can be specified subordinate to a DIMension block. It is notrequired.

6.3.9 DIMension Block Example

DIM=X (NOTE “Procedure 12.8”NAME “DS3”TYPE EXPLicitUNITs “S”SCALe 1.0OFFSet 0.0SIZE 1024ENCode (

NOTE “This ENCode block affects only X dimension values in the DATA(CURVe) block”FORMat INT16NVALue -32768

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



ORANge 32767URANge -32767HRANge 32766LRANge -32766RESolution 1))

6.4 ENCodeThe ENCode block addresses data resolution, special range values, and encoding format<Block> value type data.

The scope of an ENCode block is determined by its hierarchical level in the data formatstructure. If the ENCode block is at the same level as DIMension blocks, it applies globallyto all data in the DATA blocks. A global encoding specification can, however, be overriddenon a dimension-by-dimension basis with an ENCode block that is subordinate to theparticular dimension. A keyword specification at the higher level rules unless explicitlysuperceded by the same keyword at the subordinate level.

Only one ENCode block can be specified at the same hierarchical level as DIMensionblocks, and only one ENCode block can be specified subordinate to a DIMension block.

The ENCode block is not required at any hierarchical level. However, the specification ofHRANge and LRANge for all explicit dimensions is strongly recommended. The ENCodeblock is defined as:

TK055encode -> ENCode ([NOTE <String>][FORMat { IFP32 | IFP64

| INT8 | INT16 | INT32 | INT64 | SFP32 | SFP64| SINT16 | SINT32 | SINT64| SUINT16 | SUINT32 | SUINT64| UINT8 | UINT16 | UINT32 | UINT64 }]

[NVALue <Numeric>][ORANge <Numeric>][URANge <Numeric>][HRANge <Numeric>][LRANge <Numeric>][RESolution <+Numeric>]

)

If no ENCode block is specified, the default values for each keyword prevail. The ENCodeblock sub-blocks and keywords are:

6.4.1 NOTE DIF03This is arbitrary text. Value type is <String>. Text should be human-readable. Only oneoccurrence of the NOTE keyword is allowed and only one value is allowed.

Example: NOTE “Not-a-number and plus and minus infinity do not follow the IEEE 488.2recommendation”

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.4.2 FORMatThis is the data encoding format for CURVe(VALue) data. <Block> value type is introducedby a pound sign followed by one or more decimal digit characters. See section 3.4.5. ASCIIrepresentation uses comma separated <Numeric> data.

Specifying a block FORMat does not require that the values in DATA block be formatted as<Block> value type. Values may always be specified as <Numeric>.

If the ENCode block is subordinate to a DIMension block, then FORMat applies only tovalues in DATA(CURVe(VALues)) for the particular dimension.

FORMat takes a specified enumerated set of values. Only one occurrence of FORMat isallowed and only one of the following enumerated set values is allowed:

ASCii Comma-separated <Numeric> dataIFP32 IEEE floating point, 32 bits.IFP64 IEEE floating point, 64 bits.INT8 IEEE 8-bit signed integer (default).INT16 IEEE 16-bit signed integer.INT32 IEEE 32-bit signed integer.INT64 IEEE 64-bit signed integer.SFP32 IEEE swapped floating point, 32 bits.SFP64 IEEE swapped floating point, 64 bits.

TK055SINT16 Swapped IEEE 16-bit signed integer.TK055SINT32 Swapped IEEE 32-bit signed integer.TK055SINT64 Swapped IEEE 64-bit signed integer.TK055SUINT16 Swapped IEEE 16-bit unsigned integer.TK055SUINT32 Swapped IEEE 32-bit unsigned integer.TK055SUINT64 Swapped IEEE 64-bit unsigned integer.TK055UINT8 IEEE 8-bit unsigned integer.TK055UINT16 IEEE 16-bit unsigned integerUINT16.TK055UINT32 IEEE 32-bit unsigned integerUINT32.TK055UINT64 IEEE 64-bit unsigned integerUINT64.

TK055All signed integers are two’s complement. IEEE formats are defined by IEEE 488.2 BinaryInteger and Binary Unsigned Integer codes. “Swapped” means that the byte order (from lowto high address) is from least significant to most significant byte.

For example, to transfer #H1234 as an INT16 (16-bit integer) across a byte orientedtransmission medium, transfer the first byte as 12 (hex) and the second byte as 34 (hex). Totransfer #H1234 as an SINT16 (swapped 16-bit integer), transfer the first byte as 34 (hex)and the second byte as 12 (hex).

Similarly, to transfer #H12345678 as an INT32 (32-bit integer), transfer the bytes in theorder: 12 (hex), 34 (hex), 56 (hex), and 78 (hex). To transfer #H12345678 as an SINT32

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



(32-bit swapped integer), transfer the bytes in the order: 78 (hex), 56 (hex), 34 (hex), and12 (hex).

Example: FORMat INT16

6.4.3 NVALueThis is the numeric value (before application of SCALe and OFFSet) that is to be treated asimplying “not a number” or “no value recorded” for values in the DATA block.

Value type is <Numeric>. Only one occurrence of NVALue is allowed and only one value isallowed. If NVALue is not present, no not-a-number value is defined for integer formats. ForIEEE floating point formats, no NVALue is ever specified. In this case, NVALue is asdefined by IEEE 754 for not-a-number. For ASCII, the default value is 9.91E+37.

Example: NVALue 9999

6.4.4 ORANgeThis indicates the numeric value (before application of SCALe and OFFSet) that is to betreated as over range for values in the DATA block.

Value type is <Numeric>. Only one occurrence of ORANge is allowed and only one value isallowed. If ORANge is not present, no over range value is defined for integer formats. ForIEEE floating point formats, no ORANge is ever specified. In this case, ORANGe is asdefined by IEEE 754 for plus infinity. For ASCII, the default value is 9.9E+37.

Example: ORANge #H7FFF

6.4.5 URANgeThis is the numeric value (before application of SCALe and OFFSet) that is to be treated asunder range for values in the DATA block.

Value type is <Numeric>. Only one occurrence of URANge is allowed and only one value isallowed. If URANge is not present, no under range value is defined for integer formats. ForIEEE floating point formats, no URANge is ever specified. In this case, URANGe is asdefined by IEEE 754 for negative infinity. For ASCII, the default value is -9.9E+37.

Example: URANge -32767

6.4.6 HRANge DIF03This is the greatest signed value (before application of SCALe and OFFSet) that may bepresent in the DATA(CURVe(VALUE)).

Value type is <Numeric>. Only one occurrence of HRANge is allowed and only one value isallowed. The value specified shall be at least as great as the greatest value present in the databut may be greater.

NVALue, ORANge, and URANge values are not considered when determining range. Unitsare the measurement curve units after SCALe and OFFSet are applied to the data.

Example: HRANge 32766

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.4.7 LRANgeThis is the least value (before application of SCALe and OFFSet) that may be present inDATA(CURVe(VALUE)).

Value type is <Numeric>. Only one occurrence of LRANge is allowed and only one value isallowed. The value specified shall be at least as small as the least value present in the databut may be less.

NVALue, ORANge, and URANge values are not considered when determining range. Unitsare the measurement curve units after SCALe and OFFSet are applied to the data.

Example: LRANge -32766

6.4.8 RESolutionThis is the minimum resolution of data values present in the DATA block.

Value type is <+Numeric>. Only one occurrence of RESolution is allowed and only onevalue is allowed.

Units are the measurement curve units after SCALe and OFFSet are applied to the data.

Example: RESolution 1

6.4.9 ENCode Block ExampleENCode (

NOTE “Acquisition resolution was 10 bits”FORMat INT16NVALue -32768ORANge 32767URANge -32767HRANge 32766LRANge -32766RESolution 1)

6.5 IDENtifyThis is the IDENtify block contains fields uniquely identifying the data and describing theenvironment in which it was created or acquired. The precise definitions for the contents ofall text string values in the IDENtify block is left to the creator of the data set. However, thegeneral category shall be followed.

The IDENtify block may occur only once, but is not required. The IDENtify block is definedas:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



DIF03identify -> IDENtify (

[NOTE <String>][NAME <String>][TECHnician <String> {,<String>}*][PROJect <String>][DATE <NR1>,<+NR1>,<+NR1>


[,<0+NR1>,<0+NR1>,<0+Numeric>]] DIF06[UUT(

[NAME <String>][ID <String> {,<String>}*][DESign <String> {,<String>}*]

)][TEST(

[NAME <String>][SERies <String>][NUMBer <String> {,<String>}*]

)][HISTory <String> {,<String>}*]

)



Example: NOTE “24 AWG may have been out of calibration”

6.5.2 NAME DIF03This is the user-defined name identifying the data set. NAME is typically more descriptivethan the block modifier.

Value type is <String>. It is recommended that the string length be 32 characters or less.This field is optional. Only one occurrence of the NAME keyword is allowed. Only onevalue is allowed.

Example: NAME “Spectral Power Test”

6.5.3 TECHnicianThis identifies the technician(s) involved in the generation or modification of the data.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the TECHnician keyword is allowed. Multiple values, up to 7, areallowed.

Example: TECHnician “John H. Doe”

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.5.4 PROJectThis is the name of project, job, task, etc.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of PROJect is allowed and only one value is allowed.

Example: PROJect “S27A408”

6.5.5 DATE DIF03This is the date of data creation or acquisition.

DIF06This keyword takes a set of three comma separated value types to specify the datecorresponding to year, month, and day.

DIF06The years parameter is type <NR1>. It always includes century and millennium information.

DIF06The months parameter is type <+NR1>. Its range is 0 to 12.

DIF06The days parameter is type <+NR1>. Its range is 0 to 31 (depending on the month).

DIF06If two sets of values are specified, they define an inclusive range of dates.

DIF06Example: DATE 1776,07,04 indicates the 4th of July, 1776

6.5.6 TIME DIF03DIF03,06This is the time of data creation or acquisition.

DIF06DIF06This keyword takes a set of three comma separated value types to specify the timecorresponding to hour, minute, and second.

DIF06The hours parameter is type <0+NR1>. Its range is 0 to 23. This parameter is alwaysexpressed in 24 hour format.

DIF06The minutes parameter is type <0+NR1>. Its range is 0 to 59.

DIF06The seconds parameter is type <0+Numeric>. Its range is 0 to 60 for instruments receivingdata and 0 to 59.999... for instruments sending data.

DIF06If two sets of values are specified, they define an inclusive range of time.

DIF06Example: TIME 23,59,59 indicates one second before midnight.

6.5.7 UUT This is a description of the “unit under test”. This block may occur only once.

6.5.7.1 NAME DIF03This is the name or type of unit under test. NAME is similar in use to ID, except that it istypically more descriptive and only one value is allowed.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the NAME keyword is allowed and only one value is allowed.

Example: NAME “Model 29AP402”

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.5.7.2 IDThis is the identification of the unit under test.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the ID keyword is allowed. Multiple values, up to 7, per keyword areallowed.

Example: ID “AA32303”,“B7”

6.5.7.3 DESignThis identifies the design specification.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the DESign keyword is allowed. Multiple values, up to 7, areallowed.

Example: DESign “2W32 Rev 3C”

6.5.8 TEST This is the test description. This block may occur only once.

6.5.8.1 NAME DIF03This is the test series name.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the NAME keyword is allowed and only one value is allowed.

Example: NAME “DC Parametrics”

6.5.8.2 SERiesThis is the number or id of test series.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of SERies is allowed and only one value is allowed.

Example: SERies “24B208”

6.5.8.3 NUMBerThis is the number or id of particular test.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the NUMBer keyword is allowed. Multiple values, up to 7, areallowed.

Example: NUMBer “A3”,“B6”,“B7”

6.5.9 HISToryThis is the derivation history of the data set, such as names of tests, instruments, instrumentsystems, and software packages.

Value type is <String>. It is recommended that the string length be 32 characters or less.Only one occurrence of the HISTory keyword is allowed. Multiple values, up to 7, areallowed and imply an ordering from oldest to most recent.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: HISTory “T24.WFM”, “CCITT DS3 Template”

6.5.10 IDENtify Block Example

IDENtify (NOTE “This IDENtify block example contains examples of all keywords”NAME “”TECHnician “Matt Wilson”PROJect “Acorn”DATE 1988,9,2TIME 23,3,0.25UUT (

NAME “Ironman”ID “007”DESign “Rev D”)

TEST (NAME “Cal Menu”SERies “3A”NUMBer “5”)

HISTory “Tinman”, “Strawman”)

6.6 ORDer TK052The ORDer block defines the physical layout of data within the DATA(CURVe) block. Data

may be ordered as n-tuples, in which the data for each explicit dimension is “inter-mixed”.This is also called row order. Data may also be ordered by dimension. When ordered bydimension, all data for each dimension is grouped consecutively, with all data for onedimension followed by all data for the next dimension. This is also called column order.

When more than one implicit dimension exists, the first implicit dimension index alwaysincrements the slowest and the last implicit dimension index always increments the fastest.

The ORDer block may occur only once, but is not required. If omitted, the default values forits keywords prevail. The ORDer block is defined as:

DIF03order -> ORDer (

[NOTE <String>][BY {TUPLe | DIMension}]

)



Example: NOTE “Most important first”

6.6.2 BYThis indicates if the ordering is by tuple or dimension.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



DIF03BY takes a specified enumerated set of values. BY may occur only once, and takes one ofthe two following enumerated set values: TUPLe Data values are organized by n-tuple (default). DIMension Data values are organized by dimension.

6.6.3 ExamplesSuppose the sample measurements in the following example were made according to thescenario of 1.3 of this section. The data has five dimensions. Assume also that the fiveDIMension blocks have label values corresponding to the headings in as shown below.

Sample Measurements

X Y Z Temp Hum

5 1 8.1 18.1 61 5 2 9.2 20.2 62 7 1 6.3 16.3 63 7 2 3.4 16.4 64 9 1 8.5 18.5 65 9 2 3.6 16.6 66

Example 1:If all values are present in the data, the five DIMension blocks will have TYPE EXPLicit(see 6.3 in this section). If no ORDer block is present, the data will be ordered: HUM, TEMP, X, Y, Z, HUM, TEMP, X, Y, Z ...

That is, the data is ordered by 5-tuple and by column order of occurrence within a 5-tuple.Note that the rows may appear in any order since there are no implicit dimensions.

The DIMension and DATA blocks for this example are:

DIMension=HUM (TYPE EXPLicitSIZE 6UNITs “PCT”ENCode (

HRANge 60LRANge 66))

DIMension=TEMP (TYPE EXPLicitSIZE 6UNITs “CEL”ENCode (


DIMension=X (TYPE EXPLicitSIZE 6

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



UNITs “M”ENCode (HRANge 9LRANge 5))

DIMension=Y (TYPE EXPLicitSIZE 6UNITs “M”ENCode (

HRANge 2LRANge 1))

DIMension=Z (TYPE EXPLicitSIZE 6UNITs “M”ENCode (

HRANge 10LRANge 0))

DATA (CURVe (

VALues 61, 18.1, 5, 1, 8.1, 64, 16.4, 7, 2, 3.4, 65, 18.5, 9, 1, 8.5, 66, 16.6, 9, 2, 3.6, 62, 20.2, 5, 2, 9.2, 63, 16.3, 7, 1, 6.3))

Example 2:

If the coordinate values for the X and Y dimensions are omitted from the data, thesedimensions are implicit (TYPE is IMPLicit).

The X and Y dimensions are easily derived by linear functions:x = 2m + 3y = n

where m and n are indices related to the ordering of the values for Z, TEMP, and HUM.

The DIMension and DATA blocks for this example are:

DIMension=TEMP (TYPE EXPLicitSIZE 6UNITs “CEL”ENCode (


TK052DIMension=X(TYPE IMPLicitSIZE 3

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



UNITs “M”SCALe 2OFFSet 3)

DIMension=Y(TYPE IMPLicitSIZE 2UNITs “M”)

DIMension=Z (TYPE EXPLicitSIZE 6UNITs “M”ENCode (

HRANge 10LRANge 0))

DIMension=HUM (TYPE EXPLicitSIZE 6UNITs “PCT”ENCode (


DATA (CURVe (

VALues 18.1, 8.1, 61, 20.2, 9.2, 62, 16.3, 6.3, 63, 16.4, 3.4, 64, 18.5, 8.5, 65, 16.6, 3.6, 66))

HP072TK0533aNote that the humidity DIMension now appears last and that DATA values in the DATAblock are therefore in a different order. The reordering of the X and Y DIMension blocksaffects only the default determination of the independent and dependent dimensions (seechapter 6.3). In this second example, the presence of implicit dimensions forces a requiredrow order on the VALUes values.

6.7 REMark This block is for information not fitting elsewhere.

DIF03The REMark block may occur only once, but is not required. The REMark block is definedas:

remark -> REMark([NOTE <String> {,<String>}*]

)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22




Value type is <String>. Text should be human-readable. Only one occurrence of the NOTEkeyword is allowed. Multiple values are allowed and no ordering is implied.

Example: NOTE “The REMark block is the appropriate place for observations andannotations about the data, its acquisition, creation, or modification. In general, its a place tostuff technical information.”

6.7.2 REMark Block ExampleREMark (NOTE “A remarkable data structure”)

6.8 DIF TK053aThe DIF block is the first block in a dif data set. It uniquely defines the expression data as

being a dif data set with the beginning DIF character sequence. The DIF block providesversion information to assist the parser in determining compatibility. It further defines thescope of the data set.

DIF01,03The DIF block may occur only once and is required. The DIF block is defined as:

TK032Adifid -> DIF([NOTE <String>]VERSion <+Numeric>[SCOPe PREamble | FULL]

)



Example: NOTE “First Version”

6.8.2 VERSionTK053aThe DIF(VERSion) number exactly tracks the SCPI SYSTem:VERSion number (Command

Reference, 21.20) and correlates changes and extensions in the DIF volume with the rest ofSCPI.

Note: The DIF(VERSion) keyword was new in 1994.0 and was created as a part of aone-time major restructuring and simplification of DIF. DIF parsers designed prior to 1994will not be compatible with 1994.0 and following versions.

Value type is <+Numeric>. Only one value is allowed. Only one occurrence of VERSion isallowed.

Note that while version numbers increase in value in time sequence, lesser version numberswill not necessarily be guaranteed to be fully compatible.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



Example: VERSion 1993.0

TK032A6.8.3 SCOPeTK032AThis indicates the scope of the DIF block.

TK032ASCOPe takes a specified enumerated set of values. SCOPe may occur only once and takesone of the two following enumerated set values:

TK032AWhen SCOPe is set to PREamble, the DIF block omits the following data:

TK032Adif blocks of waveform, measurement, and delta.

TK032Adif curve block keywords VALues and CSUM and their parameters.

TK032AThe various notes and identification parameters may be sent if absolutely required.

TK053aWhen SCOPe is set to FULL, a complete dif data set as described in Section 4.3 is present(default).

TK032AExample: SCOPe PREamble

6.8.4 DIF Block Example DIF01DIF ( DIF01

NOTE “Third revision of standard” DIF01VERSion 1993.0) DIF01

6.9 TRACe DIF03TRACe blocks describe logical relationships among all or some of the dimensions. Theymay define functions, curves, surfaces, or arbitrary sets or data groupings. They also providea convenient means of describing subsets of the data. The windowing effect of the TRACeblocks may, for example, be used to make two-dimensional “cuts” throughthree-dimensional data. Other blocks, such as the VIEW block, build on TRACe blocks.TRACe block information is built from DIMension blocks; VIEW blocks are built fromTRACe block information.

If no TRACe block is present, the independence or dependence of a dimension is determinedby rules described in 6.3 in this section.

DIF03The TRACe block is optional and multiple TRACe blocks are allowed. The TRACe block isdefined as:

trace -> TRACe = <Label>([NOTE <String>][NAME <String>][SYMMetry <String>]{INDependent(

LABel <Label>[STARt <+NR1>][STOP <+NR1>]

)}*{DEPendent(

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



LABel <Label>)}*

)

The TRACe block modifier <Label> value is required. It provides for the uniqueidentification of the TRACe block. As <Label> for the entire data set are unique, no twoTRACe blocks may have the same <Label>.

Explicit and implicit, as applied to dimensions, are distinguished from independent anddependent as follows. Implicit and explicit are concerned with how the data is physicallyrepresented and structured. Independent and dependent relate to how a dimension isinterpreted.



Example: NOTE “Values generated pursuant to 12A34D”

6.9.2 NAME DIF03This is an arbitrary name or description of the trace.


Example: NAME “Gain”

6.9.3 SYMMetryThis specifies the type of symmetry on a per dimension basis. Only one occurrence ofSYMMetry is allowed.

Value type is <String>. It is recommended that the string length be 32 characters or less. Thefollowing values are predefined:

UNKNOWN Symmetry is unknown. (default)NONE No symmetry.PEVEN Positive and even symmetry.NEVEN Negative and even symmetry.PODD Positive and odd symmetry.NODD Negative and odd symmetry.

Example: SYMMetry “UNKNOWN”

6.9.4 INDependent This identifies one independent dimension that constitutes the trace. If independence anddependence are not meaningful, the trace should be defined using the INDependent block.This sub-block may occur multiple times.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



STARt and STOP parameters represent integer values referring to indexes on implicitdimensions and therefore apply only to implicit dimensions

6.9.4.1 LABelThis is the label of the independent dimension.

Value is of type <Label>. Only values defined by the DIMension block label are allowed.LABel is required and may occur only once. Only one value is allowed.

Example: LABel X

6.9.4.2 STARt DIF03This specifies the starting index (inclusive).

Value is of type <+NR1>. Only one occurrence of STARt is allowed and only one value isallowed. This keyword may be present only if the dimension is implicit.

If STARt is omitted, then the default value is 1. If the index value is greater than thedimension’s SIZE value (from the applicable DIMension or DATA(DELTa(DIMension))block), then an error is reported.

Example: STARt 12

6.9.4.3 STOP DIF03This specifies the ending index (inclusive).

Value is of type <+NR1>. Only one occurrence of STOP is allowed and only one value isallowed. This keyword may be present only if the dimension is implicit.

If STOP is omitted then SIZE is used. If the index value is greater than the dimension’s SIZEvalue (from the applicable DIMension or DATA(DELTa(DIMension)) block), then an erroris reported.

If the stopping index value is less than the starting index value then an error is reported.

Example: STOP 982

6.9.5 DEPendent This identifies a dependent dimension that constitutes the trace. This sub-block may occurmultiple times.

6.9.5.1 LABelThis is the label of the dependent dimension.

Value is of type <Label>. Only values defined by the DIMension block label are allowed.LABel is required and may occur only once. Only one value is allowed.

Example: LABel Y

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.9.6 TRACe Block Example

TRACe=TEMP (NOTE “Missing values were interpolated” NAME “Transient acceleration” SYMMetry “UNKNOWN” DIF02INDependent (

LABel X STARt 1 STOP 10)

INDependent (LAB Y STARt 100 STOP 200)

INDependent (LABel Z STARt 2 STOP 4)

DEPendent (LABel A))

6.10 VIEW DIF03VIEW blocks provide semantic information about the data in DATA(CURVe). With aVIEW block, one can show relationships between and among subsets of the data as definedby TRACe blocks. For example, a complex waveform or surface can be easily defined, ascan a waveform and its upper and lower envelopes.

The VIEW block builds on traces described in a TRACe block. A trace commonly defines asimple function, but the data format allows for the definition of sets, surfaces and othercomplex functions.

For example, a time varying envelope might be described by three DIMension blocks. Thetwo explicit dimensions define the two Y-axis values for the upper and lower components ofthe envelope. The implicit dimension defines the common X-axis. While the organizationalstructure of the data is defined by the DIMension and ORDer blocks, its meaning isdetermined by a VIEW block. It is the view block that identifies which dimension is theupper envelope and which is the lower.

Alternatively, the same data could be viewed as a complex waveform. The DIMensionblocks would be the same, but a VIEW block would identify which dimension is the realcomponent and which is the complex component.

The VIEW block is optional and multiple VIEW blocks are allowed. The VIEW block isdefined as:

DIF03

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



HP091view -> VIEW = <Label> ([NOTE <String>][NAME <String>]{ENVelope(

UPPer <Label>LOWer <Label>[FUNCtion <Label>]

)}*{RCOMplex(

REAL <Label>IMAGinary <Label>

)}{PCOMplex(

MAGNitude <Label>PHASe <Label>

)})

The modifier label is required. It provides for the unique identification of the VIEW block.As all <Label> elements are unique, no two VIEW blocks may have the same label.

A VIEW block takes the following sub-blocks. Except for NAME and NOTE, only one typeof the other sub-blocks may be present:



Example: NOTE “Template defines the max and min values for calibrating mil spec97654-D”

6.10.2 NAME DIF03This is the name of the view. NAME is typically more descriptive than the VIEW blocklabel and does not need to be unique.


Example: NAME “97654-D”

6.10.3 ENVelope This identifies which two traces constitute the envelope for a third in DATA(CURVe) data.Multiple occurrences of ENVelope are allowed.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



6.10.3.1 UPPerThis specifies the name of the upper envelope trace.

Value type is <Label> and is restricted to a value defined by a TRACe block modifier<Label> value. Only one occurrence of UPPer is allowed and only one value is allowed.

Example: UPPer YH

6.10.3.2 LOWerThis specifies the name of the lower envelope trace.

Value type is <Label> and is restricted to a value defined by a TRACe block modifier<Label> value. Only one occurrence of LOWer is allowed and only one value is allowed.

Example: LOWer YL

6.10.3.3 FUNCtionThis specifies the set of data being enveloped.

Value type is <Label> and is restricted to a value defined by a TRACe block <Label>. Onlyone occurrence of FUNCtion is allowed and only one value is allowed.

Example: FUNCtion Y

HP0916.10.4 RCOMPlexHP091This identifies which two TRACes constitute a rectangular complex waveform. RCOMPlex

may only occur once.

HP0916.10.4.1 REAL HP091This specifies the name of the real trace.

HP091Value is of type <Label>. Only values defined by the TRACe block are allowed. REAL isrequired and may occur only once. Only one value is allowed.

HP091Example: REAL S11REAL

HP0916.10.4.2 IMAGinary HP091This specifies the name of the imaginary trace.

HP091Value is of type <Label>. Only values defined by the TRACe block are allowed. IMAGinaryis required and may occur only once. Only one value is allowed.

HP091Example: IMAGinary S11IMAG

HP0916.10.5 PCOMplex HP091This identifies the which two TRACes constitute a polar complex waveform. PCOMplex

may only occur once.

HP0916.10.5.1 MAGNitude HP091This specifies the name of the magnitude trace.

HP091Value is of type <Label>. Only values defined by the TRACe block are allowed.MAGNitude is required and may occur only once. Only one value is allowed.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



HP091Example: REAL S11MAG

HP0916.10.5.2 PHASe HP091This specifies the name of the phase trace.

HP091Value is of type <Label>. Only values defined by the TRACe block are allowed. PHASe isrequired and may occur only once. Only one value is allowed.

HP091Example: PHASe S11PHASE

6.10.6 VIEW BLOCK EXAMPLE

VIEW=T3_J4 (NOTE “Mil spec 97654-D replaces 54679-D”NAME “Mil spec 97654-D”ENV (

UPPer YHLOWer YL))

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22



7 Data Format ExampleThe following data set exemplifies the use of several related blocks in the data interchangeformat. The example below is shown encapsulated in parentheses; that is, as a<dif_expression>.

DIF01( DIF (

VERsion 1993.0)IDENtify (

DATE 1993,4,23 DIF06TIME 16,4,14.23) DIF06

ENCode (FORMat INT8HRANge 127 LRANge -128)

DIMension=YH (TYPE EXPLicit SCALe 2.000000E-002 OFFSet -3.500000E-001 SIZE 512 UNITs “V”)

DIMension=YL (TYPE EXPLicit SCALe 2.000000E-002 OFFSet -3.500000E-001 SIZE 512 UNITs “V”)

DIMension=X (TYPE IMPLicit SCALe 2.000000E-005 OFFSet -1.024000E-002 SIZE 512 UNITs “s”)

TRACe=H (INDependent(

LABel X) DEPendent(

LABel YH))TRACe=L (

INDependent(LABel X)

DEPendent (LABel YL))

VIEW=ENV1 (ENVelope (

UPPer H LOWer L))

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


Data Format Example 7-1

DATA (CURVe (

VALue #41024{1024 8-bit significant bytes of data goes here}CSUM 139))

WAVeform (TRACe HRISE (

TIME 1.04E-003)FALL (

TIME 0.86E-003)))

HP072DIF01,06In this example, we have a data set that follows the 1993.0 version of SCPI and is dated atabout 4 PM on April 23rd, 1993. The data is encoded as 8-bit signed integers ranging from-128 to 127 and is presented as a sequence of 512 byte pairs representing two voltage signallevels (YH and YL). The raw bit values must be multiplied by .02 with .35 subtracted toyield the measured value in Volts. The first data pair occurred at a measured time (X) of (20- 10,240 microseconds) or -10.22 milliseconds. Subsequent data pairs were recorded at 20microsecond intervals.

Two traces (H and L) are specified with YH and YL voltage levels as the dependentvariables and time as the independent variable. The traces can be viewed as envelope-typedata and referred to as ENV1. The data itself is formatted in IEEE 488.2 block format (1024bytes long) and its integrity can be verified by computing a 16-bit cyclic redundancy checkand comparing the results to the stated (CSUM) value of 139.

Finally, the rise and fall times of the H trace have been computed and recorded in the dataset as 1.04 milliseconds and 0.86 milliseconds.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22


7-2 Data Format Example

Index

A AMPLitude 6-10

B block 3-3

definition 3-2unrecognized 4-6

block modifier 3-2BY 6-28

C CCITT 6-5character set 3-1COUNt 6-13CRC16 6-5CSUM 6-5CTYPe 6-4CURVe 6-4CYCle block 6-13

D DATA block 6-1data format

example 7-1extension 5-1overview 1-1

Data Interchange Format 1-2DATE

DELTa block 6-3, 6-26DELTa block 6-2DEPendent 6-35DESign 6-27DIF block 6-32<dif_expression> 1-1dimension 6-29

explicit 1-2implicit 1-2

DIMension block 6-3, 6-17

E ENCode block 6-21

DIMension block 6-20

enumerated setdefinition 3-4errors 2-1

ENVelope 6-37EXPLicit 6-18

F FALL block 6-11FREQuency 6-10FUNCtion 6-38

G grammar

notation 4-1required blocks 4-6required order 4-6unrecognized blocks 4-6unrecognized keywords 4-6

H HIGH

REFerence block 6-9WAVeform block 6-8

HISTory 6-27HLMethod 6-8HRANge 6-23

I ID 6-27IDENtify block 6-24IFP32 6-22IFP64 6-22IMPlicit 6-18INDependent 6-34INDex 6-16INT16 6-22INT32 6-22INT64 6-22INT8 6-22

Index - 1

K keyword

default values 2-1definition 3-2errors 2-1multiple values 2-1unrecognized 4-6

L <Label> 3-3

DEPendent block 6-35INDependent block 6-35LOCation block 6-16

LOCation block 6-16LOW

REFerence block 6-9WAVeform block 6-9

LOWer 6-38LRANge 6-24

M MAXimum 6-12MEAN

CYCLe block 6-14WAVeform block 6-13

MEAsurement block 6-14METHod 6-9MID 6-9MINimum 6-12

N NAME

CURVe block 6-4DIMension block 6-18IDENtify block 6-25MEASurement block 6-15TEST block 6-27TRACe block 6-34UUT block 6-26VIEW block 6-37WAVeform block 6-8

NDUTycycle 6-11NOTE

CURVe block 6-4DATA block 6-2DELTa block 6-2DIF block 6-32DIMension block 6-18

ENCode block 6-21IDENtify block 6-25MEASurement block 6-15ORDer block 6-28REMark block 6-32TRACe block 6-34VIEW block 6-37WAVeform block 6-8

NUMBer 6-27<Numeric> 3-2—3-3<+Numeric> 3-2<0+Numeric> 3-3NVALue 6-23NWIDth 6-10

O OFFSet

DIMension block 6-3, 6-19ORANge 6-23ORDer block 6-28OVERshoot

FALL block 6-12RISE block 6-11

P PDUTycycle 6-11PERiod 6-10PREShoot

FALL block 6-12RISE block 6-11

PROJect 6-26PTPeak 6-13PWIDth 6-10

R REFerence block 6-9REMark block 6-31RESolution 6-24RISE block 6-11RMS


S SCALe

DIMension block 6-3, 6-19Scope 6-33SDEViation


Index - 2


SERies 6-27SFP32 6-22SFP64 6-22SINT16 6-22SINT32 6-22SINT64 6-22SIZE

DIMension block 6-3, 6-19STARt 6-35STOP 6-35<String> 3-3SUINT16 6-22SUINT32 6-22SUINT64 6-22SUM16 6-5SUM8 6-5SYMMetry 6-34syntax

block 3-2block modifier 3-2character set 3-1keyword 3-2overview 3-1value types 3-2white space 3-1

T TECHnician 6-25TEST block 6-27TIME

DELTa block 6-3, 6-26FALL block 6-12RISE block 6-11

TMAXimum 6-12TMINimum 6-12TRACe

MEASurement block 6-16WAVeform block 6-8

TRACe block 6-33TUPle 6-29TYPE

DIMension block 6-18MEASurement block 6-15

U UINT8 6-22UNITs

DIMension block 6-20

MEASurement block 6-15UPPer 6-38URANge 6-23UUT block 6-26

V value type

<+NR1> 3-3<+Numeric> 3-2<0+NR1> 3-3<0+Numeric> 3-3<Block> 3-3<Label> 3-3<NR1> 3-3<Numeric> 3-2<String> 3-3enumerated set 3-4

VALuesCURVe block 6-5MEASurement block 6-16

VERSion 6-32VIEW block 6-36

W WAVeform block 6-5white space 3-1


Index - 3


Volume 4: Instrument Classes

VERSION 1999.0

May, 1999

Printed in U.S.A.

Table of Contents


1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.3.1 Guiding Designers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.3.2 Achieving Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.4 Instrument Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.4.1 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.4.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.5 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.6 Chapter Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Chapter 2 Chassis Dynamometers

2.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.1.2.1 CALibration subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.1.2.2 CONTrol subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.1.2.3 MEMory subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.1.2.4 SENSe subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.1.2.5 SOURce subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-82.1.3 STATus Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.1.3.1 OPERation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.1.3.1.1 CDYNo:CONDition?<16 bit integer word> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.1.3.2 QUEStionable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.1.3.2.1 CDYNo:CONDition?<16 bit integer word> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.2 Additional Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.3 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.3.1 Coastdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.3.2 Road Load Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-162.4 New Commands for this Instrument Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182.4.1 Dynamometer CALibration Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182.4.1.1 :BINertia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182.4.1.1.1 :AVERage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192.4.1.1.2 :HSPeed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192.4.1.1.3 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192.4.1.1.4 :LSPeed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.4.1.1.5 :NRUNs <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.4.1.1.6 :SDEViation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-202.4.1.1.7 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

iii

2.4.1.2 :PLOSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.4.1.2.1 :APCoeff <numeric_value >,numeric_value>,<numeric_value>... . . . . . . . . . . . 2-212.4.1.2.2 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212.4.1.2.3 :LATime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212.4.1.2.4 :STIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-222.4.1.2.5 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-222.4.1.3 :WARMup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-222.4.1.3.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-222.4.1.3.2 :SPEed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.4.1.3.3 :TIMeout <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.4.1.4 :ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.4.1.4.1 :FSENsor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.4.1.4.1.1 :INITiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.4.1.4.1.2 :LATime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242.4.1.4.1.3 :LEVel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-242.4.1.4.1.4 :SPEed <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242.4.1.4.1.5 :STIMe <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242.4.1.4.1.6 :UPDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-242.4.2 DIAGnostic Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-242.4.3 MEMory Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-242.4.3.1 :ARATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-262.4.3.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-262.4.3.1.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-262.4.3.2 :CINertia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-262.4.3.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-262.4.3.2.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-262.4.3.3 :DRATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-262.4.3.3.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-262.4.3.3.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-272.4.3.4 :FORCe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-272.4.3.4.1 :AACCeleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-272.4.3.4.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-272.4.3.4.2 :ADECeleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-272.4.3.4.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-272.4.3.4.3 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-272.4.3.4.3.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-282.4.3.4.4 ZOFFset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282.4.3.4.4.1 [:MAGNitude] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282.4.3.5 :DLOSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282.4.3.5.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-282.4.3.5.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-282.4.3.6 :PCOefficients<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-282.4.3.6.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-282.4.3.6.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-282.4.3.7 :SPEed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

1999 SCPI Instrument Classes

iv

2.4.3.7.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-292.4.3.7.1.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-292.4.3.7.2 :STARt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-292.4.3.7.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-292.4.3.7.3 :STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-292.4.3.7.3.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-292.4.3.8 :TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-292.4.3.8.1 :ACCeleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-302.4.3.8.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-302.4.3.8.2 :DECeleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-302.4.3.8.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . 2-302.4.3.8.3 [:MAGNitude] <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . . . 2-302.4.3.8.3.1 :POINts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30

Chapter 3 Digital Meters

3.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.1.1.1 Effects of MEASure Query and CONFigure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.1.1.2 The <expected_value> parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.1.1.3 The <resolution> parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.1.2.1 FORMat Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.1.2.2 SENSe subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.1.2.3 TRIGger subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.1.3.1 QUEStionable Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.1.3.2 OPERation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.2 Additional functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.1 Extended Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.1.1 ETRIGGER Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.1.2 ETRIGGER Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.1.2.1 TRIGger Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.1.3 ETRIGGER Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.2 Multiple Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.2.1 TERMINALS Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.2.2 TERMINALS Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.2.2.1 ROUTe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.2.3 TERMINALS Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.3 Offset Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.2.3.1 OCOMPENSATED Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.2.3.2 OCOMPENSATED Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.2.3.2.1 SENSe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.2.3.3 OCOMPENSATED Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.3 Various Meter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8


v

3.3.1 DC Voltmeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.1.1 Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.1.2 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-83.3.2 AC RMS Voltmeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.2.1 Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.2.2 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-83.3.3 Ohmmeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.3.1 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-83.3.3.2 4-wire Ohmmeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.3.3 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-83.3.4 DC Ammeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.3.4.1 Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.3.4.2 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-93.3.5 AC RMS Ammeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.3.5.1 Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.3.5.2 SENSe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-93.4 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.4.1 Simple Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.4.2 Time Critical Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.4.3 Multiple Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Chapter 4 Digitizers

4.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.1 Base Measurement Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.2.1 Input functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.2.2 SENSe amplitude functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.2.3 SENSE timebase functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.2.4 SENSe One-of-N Function Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.2.5 Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.2.6 Trigger functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.3.1 QUEStionable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.1.3.2 OPERation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2 Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Chapter 5 Emissions Benches

5.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1.2 Base Device-Oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1.2.1 CALibration subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.1.2.2 CONTrol subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.1.2.3 DIAGnostic subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.1.2.4 INSTrument subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3


vi

5.1.2.5 MEMory subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.1.2.6 ROUTe subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.1.2.7 SENSe subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.1.2.8 SYSTem subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65.1.2.9 TRIGger subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.1.3.1 OPERation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.1.3.2 QUEStionable Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95.2 Additional functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.3 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.3.1 Zero/Span/Zero Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.3.2 Bag Read Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-115.3.3 Start of Diesel Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125.4 CALibration Subsystem (Bench Commands) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-155.4.1 :LINearize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-155.4.1.1 :ACCept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-155.4.2 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-155.4.2.1 :AUTO ONCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-155.4.2.2 :CALCulate AUTO|POLYnomial<n>|SRATional<n> . . . . . . . . . . . . . . . . . . . . . . . 5-165.4.2.3 :CURVe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-165.4.2.3.1 [:TYPE] POLYnomial<n>

| SRATional<n>, <numeric_value>{,<numeric_value>} . . . . . . . . . . . . . . . . . . 5-165.4.2.3.2 :ZFORce <Boolean> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-175.4.2.4 :VERify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-175.4.2.4.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-175.4.2.4.2 :TOLerance <numeric_value> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-175.4.2.4.3 :TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.5 DIAGnostic Subsystem (Bench Commands) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.5.1 :HUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.5.1.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.5.1.2 :CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-185.5.2 :LEAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.5.2.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.5.2.2 :CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.5.3 :NEFFiciency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.5.3.1 :ACQuire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-195.5.3.2 :CALCulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Chapter 6 Emission Test Cell

6.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.2.1 SYSTem subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16.1.2.2 TRIGger subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2


vii

6.2 Additional Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3.1 Instrument Capability and Version Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.3.2 Command Channel Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.3.3 Two Channel Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.3.4 Returning Data using a Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.3.5 Time Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Chapter 7 Power Supplies

7.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.2.1 Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.2.2 SOURce subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-27.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.3.1 QUEStionable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.3.2 OPERation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.2 Additional Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1 Measurement capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1.1 MEASURE Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1.2 MEASURE Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.1.3 MEASURE Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2 Multiple supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2.1 MULTIPLE Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2.2 MULTIPLE Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2.3 MULTIPLE Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.2.3 Triggering Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.2.3.1 TRIGGER Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.2.3.2 TRIGGER Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.2.3.3 TRIGGER Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.3 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.3.1 Simple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.3.2 Time Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.3.3 Level Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.3.4 Multiple Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Chapter 8 RF & Microwave Sources

8.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.1.2.1 SOURce subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-28.1.2.2 OUTPut Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-38.1.2.3 UNIT Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3


viii

8.1.3.1 QUEStionable Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.1.3.2 OPERation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.2 Additional functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.1 Amplitude Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.1.1 AM Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.1.2 AM Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.1.3 AM Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.2 Frequency Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.2.1 FM Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.2.2 FM Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48.2.2.3 Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.3 Pulse Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.3.1 PULM Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.3.2 PULM Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.3.3 PULM Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.4 Analog Frequency Sweeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.4.1 FASWEEP Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.4.2 FASWEEP Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.2.4.3 FASWEEP Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.2.5 Stepped Frequency Sweeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.2.5.1 FSSWEEP Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.2.5.2 FSSWEEP Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.2.5.3 FSSWEEP Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.2.6 Analog Power Sweeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.2.6.1 PASWEEP Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.2.6.2 PASWEEP Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-78.2.6.3 PASWEEP Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.2.7 Stepped Power Sweeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-88.2.7.1 PSSWEEP Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.2.7.2 PSSWEEP Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.2.7.3 PSSWEEP Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.8 Frequency List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.8.1 FLIST Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.8.2 FLIST Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.8.3 FLIST Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.9 Marker Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.9.1 MARKER Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.9.2 MARKER Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-98.2.9.3 MARKER Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.2.10 Trigger Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.2.10.1 TRIGGER Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.2.10.2 TRIGGER Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.2.10.3 TRIGGER Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.2.11 Reference Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.2.11.1 REFERENCE Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11


ix

8.2.11.2 REFERENCE Device Oriented Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.2.11.3 REFERENCE Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118.3 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.3.1 Simple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.3.2 Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.3.3 Analog Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.3.4 Triggered Analog Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-138.3.5 Sweep with Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-138.3.6 Reference oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Chapter 9 Signal Switchers

9.1 Base Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.1.1 Base Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.1.2 Base Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.1.2.1 ROUTe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.1.3 Base Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29.2 Additional Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1 Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1.1 SCAN Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1.2 SCAN Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1.2.1 ROUTe Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1.2.2 TRIGger Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39.2.1.3 SCAN Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.2.2 Extended Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.2.2.1 ETRIGGER Measurement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.2.2.2 ETRIGGER Device-oriented Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.2.2.2.1 TRIGger Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.2.2.3 ETRIGGER Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.3 Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59.3.1 Making and Breaking Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59.3.2 Programmed Connection Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5


x

1 IntroductionThis volume defines the SCPI commands and behavior needed to implement functionalitysets associated with common classes of instruments. Each chapter covers a particularinstrument class. A class could be, for example, a power supply, voltmeter, or switcher. Eachchapter stands by itself so a designer may focus on only the chapters that apply to aparticular design.

1.1 ScopeThis volume covers the major classes of electronic instruments supported by the commandsand behaviors as defined in SCPI Volumes 1 through 3. This volume does not extend SCPIwith unsupported or contradictory commands or behaviors.

As new applications for SCPI are explored, additional chapters will be added.

1.2 Definition of TermsFunctionality - an aspect of instrument operation which is described by SCPI commands andtheir associated behavior.

Functionality setA grouping of functionality which shall be implemented as a whole.

Instrument classA generally recognized type of instrument, for example switcher, power supply,or voltmeter.

Base functionalityThat functionality set required in an instrument of a given class.

Additional functionalityOne or more functionality sets defined for an instrument class beyond the basefunctionality.

1.3 PurposeThis volume is designed to further the overall SCPI goal of reducing ATE programdevelopment time by:

Reducing the ATE product development time by guiding designers in the usage ofSCPI from the more familiar, instrument class point of view.

Achieving a higher degree of consistency among implementations of the sameinstrument class.

1.3.1 Guiding DesignersThe Command Reference Volume describes commands that cover a wide variety ofinstrument classes and technologies. Picking commands from this alphabetically sorted listappropriate for a particular instrument can be daunting.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Introduction 1-1

This volume uses terms familiar to the designer to help relate SCPI to previous designexperiences. Volume 4 provides a translation from the SCPI Command Referencevocabulary to the vocabulary common to an instrument class.

The Command Reference purposely presents certain subsystems in broad terms. Forexample, triggering is a function used in almost all instruments, but in slightly differentways. This volume provides further guidance to designers on how to apply certainsubsystems, like TRIGger, to a particular instrument class.

1.3.2 Achieving ConsistencyBecause SCPI covers many instrument classes, it cannot require all instruments toimplement all commands. It can, however, define an instrument base functionality byspecifying a relatively small set of commands and behaviors. A programmer can depend on alevel of consistency among SCPI instruments of the same class.

By staying within the base functionality, a programmer can avoid all Command Errors.Execution errors are still possible. For example, this volume cannot specify<numeric_value> ranges. The programmer, however, can use the required MIN/MAXqueries to establish range limits. Specific required values are shown where the parametertype is <CHARACTER PROGRAM DATA>.

Additional functionality may be defined for some instrument classes. None of thesefunctionality sets are required, but if any set is implemented it shall be implemented in itsentirety.

1.4 Instrument ClassificationEach chapter defines base functionality for an instrument class. This base functionality isdesignated with a keyword using SCPI program mnemonic rules. Keywords are also definedfor additional functionality. An ongoing goal of the this volume is to further classifyadditional functionality for each instrument class.

An instrument is classified using one or more base functionality keywords along withoptional additional functionality keywords. This combination of keywords is an<instrument_specifier>. Some instruments implement the SYSTem:CAPability? query,whose response is its <instrument_specifier>.

1.4.1 SyntaxThe syntax of <instrument_specifier> is defined as:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


1-2 Introduction

<bf_keyword> is a base functionality keyword as defined in one of the instrument chapters.<af_expression> is defined as:

<af_kw_group> is defined as:

<af_keyword> is an additional functionality keyword defined in the same instrument chapterwhich defines the associated <bf_keyword>.

Both <bf_keyword> and <af_keyword> use the mnemonic generation rules described inSyntax & Style, 6.2.1 when constructing the keywords. The keywords have no short form,but may have a numeric suffix. Only <bf_keyword> and <af_keyword> elements defined inthis volume may appear in the response to SYSTem:CAPability?.

The <and_or_oper> is either ‘&’ (ASCII hexadecimal 26) or ‘|’ (ASCII hexadecimal 7C).The ‘&’ operator connects functionalities which may be active concurrently. The ‘|’ operatorindicates that a choice of functionality must be made.

The operators used in the preceding syntax definitions follow the rules of the following theprecedence rules in Table 1-1.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Introduction 1-3

1.4.2 ExamplesThe simplest <instrument_specifier> describes an instrument with just one basefunctionality. A power supply with no additional functionality might have an<instrument_specifier> of:

(PSUPPLY)

A simple digital multi-meter might contain several base functionalites, so its<instrument_specifier> could be:

(DCVOLTMETER|ACVOLTMETER|OHMMETER)

The operator, |, indicates that only one of the base functionalities is available at a time.

A more sophisticated DMM could have an <instrument_specifier> like:

(DCVOLTMETER WITH(ETRIGGER&TERMINALS)|ACVOLTMETERWITH(ETRIGGER&TERMINALS) |DCAMMETERWITH(ETRIGGER&TERMINALS)|ACAMMETER WITH(ETRIGGER&TERMINALS)|OHMMETER WITH(ETRIGGER&TERMINALS&OCOMPENSATED) |FOHMMETERWITH(ETRIGGER&TERMINALS&OCOMPENSATED))

Within the <af_expression>, the operator, &, indicates all the additional functionalities areavailable simultaneously.

An instrument may contain multiple base functionalities that are used at the same time. Thebase functionalities may even be described in different chapters of this volume. A scanningvoltmeter could be described with:

(DCVOLTMETER&SWITCHER WITH SCAN)

1.5 ComplianceAn instrument that complies with SCPI even though it has less than base functionality for itsinstrument class is still a SCPI instrument, and may be claimed by its manufacturer as such.However, the manufacturer may not use <instrument_specifier> to describe its instrumentunless it meets the requirements of Volume 4.

Operator Associativity

() left to right

WITH right to left

& left to right

| left to right

Table 1-1Precedence and Order of Evaluation of <instrument_specifier> Operators

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


1-4 Introduction

Any product which uses an <instrument_specifier> to describes its capabilities and whoseresponse to SYSTem:VERSion? is greater than or equal to 1994.0 shall also implementSYSTem:CAPability?

Note that every instrument will likely have functionality not covered by this volume. Thedesigner must still follow the requirements in other volumes when implementing SCPI forthose functionalities.

1.6 Chapter OrganizationChapters are nominally organized into sections as follows, where x is the chapter number:

x.1 Base Functionalityx.1.1 Base Measurement Instructions (as applies)x.1.2 Base Device-oriented Functionsx.1.3 Base Status Reportingx.2 Additional Functionality (as applies)x.3 Programming Examplesx.4 Instrument Class specific commands for CALibrationx.5 Instrument Class specific commands for DIAGnosticsx.6 MEMory subsystem additions

Some instrument classes naturally divide into major sub-classes. For example, meters fallinto sub-classes of voltmeter, ammeter, ohmmeter, and others. In this situation, separatechapters or other variations on chapter organization may be used.

In some instances, it is desired to standardize the way an Instrument or Instrument Class usescommands in the CALibration and/or DIAGnostic subsystem beyond the commands that areincluded in Volume II of SCPI for all instruments. In these cases, Instrument Class specificcommands can be defined in the Instrument Classes volume for SCPI, but only forCALibration and DIAGnostic commands. When this is the case, the commands will be listedas required commands in the Base Functionality or Extended functionality sections of theInstrument Class chapter, and then the commands will be defined in x.4 Instrument Classspecific commands for CALibration and/or x.5 Instrument Class specific commands forDIAGnostics sections of Instrument Class chapter to which they apply.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Introduction 1-5

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


1-6 Introduction

2 Chassis DynamometersThe Chassis Dynamometer is a basic sourcing instrument. It supplies a force to a vehicle tosimulate actual road load driving conditions. The SOURce root node is optional.

All SCPI compliant products implement the commands listed in Syntax & Style section 4.2.

Figure 2-1 shows a simplified model for a chassis dynamometer. It is derived fromCommand Reference, Chapter 2. The shaded parts are not described here.

Figure 2-2 shows how the “Measurement Function” block in Figure 2-1 is expanded in achassis dynamometer to measure Force, Speed and Distance. The CALCulate block isdashed and its behavior is not described here.

MEMoryTRIGger

SignalRouting FORMatMeasurement

Functiondatabus

SignalRouting FORMatSignal

Generationdatabus

Figure 2-1 Simplified Model for a Chassis Dynamometer

MEMoryTRIGger

INPut SENSe

Measurement Function

CALCulate

Figure 2-2 Expanded Measurement Function Model of a Chassis Dynamometer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26

1999 SCPI Instrument Class Applications

Chassis Dynamometers 2-1

Figure 2-3 shows how the “Signal Generation” block in Figure 2-1 is expanded in a chassisdynamometer to source Force, Speed and other parameters to the chassis dynamometer.

Figure 2-4 shows an instrument model for a Chassis Dynamometer. It indicates how the“Measurement Function” and “Signal Generation” blocks of the standard SCPI instrumentmodel, Figure 2-1 of Command Reference, are modified for the dynamometer. Additionally,it shows how this measurement system uses system, status, calibration and control functionsto set-up for performance of functional tasks. Calculations are part of the functional tasks ofthe dynamometer and thus are shown as part of the internal function block as aredynamometer specific tasks, e.g., coast downs, road load simulations/derivations andwarm-ups. SCPI commands or responses to these chassis dynamometer internal functions arecommunicated through the I/O block shown.

The dynamometer has eleven possible states.

1. Idle2. Warmup3. Force Sensor Zero4. Drive Line Loss5. Coast Down6. Parasitic Losses7. Base Inertia8. Go to Speed9. Go to Force10. Road Load Determination11. Road Load Simulation.

2.1 Base FunctionalityThis section describes the base functionality for Chassis Dynamometer.

The <bf_keyword> for a Chassis Dynamometer is CDYNO. In addition to the functionsshown below, all Chassis Dynamometers for use in emissions test cells shall implement the

MEMoryTRIGger

OUTPut SOURce CALCulate

Signal Generation

Figure 2-3 Expanded Signal Generation Model of a Chassis Dynamometer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


2-2 Chassis Dynamometers

functions shown in the base functionality for Emission Test Cells, <bf_keyword> ETCELL,shown in Chapter 6 of SCPI Instrument Classes.

2.1.1 Base Measurement InstructionsThe base functionality for a chassis dynamometer contains no MEASurement instructions,(commands from the MEASurement subsystem), but does include SENSe commands, whichset up and cause measurements such as speed and force to be made.

2.1.2 Base Device-oriented FunctionsThe base functionality for a chassis dynamometer include :SOURce, :SENSe, :MEMory,CONTrol, and :CALibration subsystems. It also defines device dependent STATus bits and

STATus

S Y S T e m

I/O

SOURce

Speed,

ForceSpeed,

Force

Responses

CONTro l

SENSe

ROLL COVER LIFTDynamometer

Roll

B R A K E

MEMory

CALibrat ion

UNits /Typecalculat ions

SCPI Tables

Parameters

DynamometerInternal Functions

Coas tDOwns

Road loadsimulat ions/der ivat ions

Warm-ups

CORRect ions

CONVers ions

SCPICommands

Figure 2-4 SCPI Chassis Dynamometer Model

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



instructions for chassis dynamometers. A SCPI-compliant chassis dynamometer shallimplement all of the commands listed in this section.

2.1.2.1 CALibration subsystemThe Chassis Dynamometer CALibration subsystem shall provide for calibrating or verifyingvarious components that affect a chassis dynamometer measurement capability byimplementing the following commands. The INITiate command causes the calibrationfunction to be run. The CALibration subsystem commands for a chassis dynamometer are asfollows.

KEYWORD PARAMETER FORM SCPI Reference:CALibration Vol 2-5 :BINertia Vol 4-2.4.1.1 | :AVERage? <numeric_value> Vol 4-2.4.1.1.1 | :HSPeed <numeric_value> Vol 4-2.4.1.1.2 | :INITiate Vol 4-2.4.1.1.3 | :LSPeed <numeric_value> Vol 4-2.4.1.1.4 | :NRUNs <numeric_value> Vol 4-2.4.1.1.5 | :SDEViation? <numeric_value> Vol 4-2.4.1.1.6 | :UPDate Vol 4-2.4.1.1.7 :PLOSs Vol 4-2.4.1.2 | :APCoefficients <numeric_value>,<numeric_value>,... Vol 4-2.4.1.2.1 | :INITiate Vol 4-2.4.1.2.2 | :LATime <numeric_value> Vol 4-2.4.1.2.3 | :STIMe <numeric_value> Vol 4-2.4.1.2.4 | :UPDate Vol 4-2.4.1.2.5 :WARMup Vol 4-2.4.1.3 | :INITiate Vol 4-2.4.1.3.1 | :SPEed <numeric_value> Vol 4-2.4.1.3.2 | :TIMeout <numeric_value> Vol 4-2.4.1.3.3 :ZERO Vol 4-2.4.1.4 | :FSENsor Vol 4-2.4.1.4.1 | | :INITiate Vol 4-2.4.1.4.1.1 | | :LEVel? Vol 4-2.4.1.4.1.3 | | :LATime <numeric_value> Vol 4-2.4.1.4.1.2 | | :SPEed <numeric_value> Vol 4-2.4.1.4.1.4 | | :STIMe <numeric_value> Vol 4-2.4.1.4.1.5 | | :UPDate Vol 4-2.4.1.4.1.6

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.1.2.2 CONTrol subsystemThe CONTrol subsystem commands for a chassis dynamometer are as follows.

KEYWORD PARAMETER FORM SCPI Reference:CONTrol Vol 2-6 :BRAKe Vol 2-6.3 | [:STATe] <Boolean> Vol 2-6.3.1 :COVer Vol 2-6.5 | [:ADJust] <OPEN|CLOSe|SCLOse|SOPEn> Vol 2-6.5.1 | :POSition? Vol 2-6.5.2 :IDLE Vol 2-6.7 | :INITiate Vol 2-6.7.1 :LIFT Vol 2-6.8 | [:ADJust] <UP|DOWN> Vol 2-6.8.1 | :POSition? Vol 2-6.8.2 :MCONtrol Vol 2-6.9 | [:STATe] <Boolean> Vol 2-6.9.1 :ROTation Vol 2-6.10 | [:DIRection] <FORWard|REVerse> Vol 2-6.10.1 :VCDevice Vol 2-6.11 | [:STATe] <Boolean> Vol 2-6.11.1 | :TDIameter <numeric_value> Vol 2-6.11.2

2.1.2.3 MEMory subsystemThe MEMory subsystem of the chassis dynamometer shall include the following commands:

KEYWORD PARAMETER FORM SCPI Reference:MEMory Vol 2-13 :CLEar Vol 2-13.2 | [:NAME] <name> Vol 2-13.2.1 | :TABLe <name> Vol 2-13.2.2 :DATA? <data> Vol 2-13.4 :DELete Vol 2-13.5 | :ALL <name> Vol 2-13.5.1 | [:NAME] <name> Vol 2-13.5.2 :TABLe Vol 2-13.11 | :ARATe Vol 4-2.4.3.1 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.1.1 | | | :POINts? Vol 4-2.4.3.1.1.1 | :CINertia Vol 4-2.4.3.2 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.2.1 | | | :POINts? Vol 4-2.4.3.2.1.1 | :DEFine <structure_string>[,<numeric_value>] Vol 2-13.11.11 | :DRATe Vol 4-2.4.3.3 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.3.1 | | | :POINts? Vol 4-2.4.3.3.1.1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM SCPI Reference | :FORCe Vol 2-13.11.12 | | :AACCeleration Vol 4-2.4.3.4.1 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.4.1.1 | | | | :POINts? Vol 4-2.4.3.4.1.1.1 | | :ADECeleration Vol 4-2.4.3.4.2 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.4.2.1 | | | | :POINts? Vol 4-2.4.3.4.2.1.1 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 2-13.11.12.1 | | | :POINts? Vol 2-13.11.12.1.1 | | :ZOFFset Vol 4-2.4.3.4.4 | | | [:MAGNitude] <numeric_value> Vol 4-2.4.3.4.4.1 | :DLOSs Vol 4-2.4.3.5 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.5.1 | | | :POINts? Vol 4-2.4.3.5.1.1 | :PCOefficients<n> Vol 4-2.4.3.6 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.6.1 | | | :POINts? Vol 4-2.4.3.6.1.1 | :SELect <table_name> Vol 2-13.11.22 | :SPEed Vol 2-13.11.23 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 2-13.11.23.1 | | | :POINts? Vol 2-13.11.23.1.1 | | :STARt Vol 4-2.4.3.7.2 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.7.2.1 | | | | :POINts? Vol 4-2.4.3.7.2.1.1 | | :STOP Vol 4-2.4.3.7.3 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.7.3.1 | | | | :POINts? Vol 4-2.4.3.7.3.1.1 | :TIME Vol 2-13.11.24 | | :ACCeleration Vol 4-2.4.3.8.1 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.8.1.1 | | | | :POINts? Vol 4-2.4.3.8.1.1.1 | | :DECeleration Vol 4-2.4.3.8.2 | | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 4-2.4.3.8.2.1 | | | | :POINts? Vol 4-2.4.3.8.2.1.1 | | [:MAGNitude] <numeric_value> {,<numeric_value>} Vol 2-13.11.24.1 | | | :POINts? Vol 2-13.11.24.1.1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The Chassis Dynamometer shall have the following tables.

Table Name Elements Description

CDownSpeed SPEed:STARt, SPEed:STOP Coastdown speed intervaldefinitions

CDownResult TIME, FORCe, POWer Results of the coastdown runs.Each coastdown has ‘n’ intervals asdefined in the CDownSpeed table

CDownMCoefficients PCO0, PCO1, PCO2, PCO3 Coastdown measured PolynomialCoefficients for a coastdown orroad load derivation procedure

CDownDCoefficients PCO0, PCO1, PCO2, PCO3 Coastdown calculateddynamometer setting coefficientsduring coastdown or road loadderivation

ParasiticLOSs SPEed, DLOSs parasitic loss computation results

PCOefficients PCO0, PCO1, PCO2, PCO3 Parasitic data curve fit results fromthe Parasitic Loss procedure

DriveLineLoss SPEed, DLOSs Steady state drive line lossmeasurement

DriveLineCoefficients PCO0, PCO1, PCO2, PCO3 Results of a curve fit of theDriveLineLoss table data, after theDrive Line Loss procedure

BaseINertia CINertia, TIME:ACCel,TIME:DECel, ARATe, DRATe,FORCe:AACCel, FORCe:ADECel

base inertia procedure data

FsensorZero ZOFFset Single value table whose valuerepresents the zero offset used tocompensate for shift.CALibration:ZERO:FSENsor:LEVel value will replace thiswhenCAL:ZERO:FSENsor:UPDate issent.

For definition of the new :MEMory:TABLe Commands defined above, see Section 2.4.3 inthis chapter of Volume 4, Instrument Classes.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.1.2.4 SENSe subsystemThe SENSe subsystem of a chassis dynamometer shall provide access to function values byimplementing the following commands. The <sensor_function> options shall include:FORCe|TPLoss|SPEed[:REAR]|SPEed:FRONt|FERRor|ACCeleration|DISTance||DISTance:RESet|TIME

KEYWORD PARAMETER FORM SCPI Reference:SENSe Vol 2-18 :DATA? [<data_handle>] Vol 2-18.13.1 :DISTance Vol 2-18.9 | :RESet Vol 2-18.9.1 :FUNCtion Vol 2-18.13.2 | :CONCurrent <Boolean> Vol 2-18.13.2.1 | :OFF <sensor_function>{,<sensor_function>} Vol 2-18.13.2.2 | | where the sensor functions to be supported shall include: | | FORCe|TPLoss|SPEed[:REAR]|SPEed:FRONt | | |FERRor|ACCeleration|DISTance | | |DISTance:RESet|TIME | | :ALL Vol 2-18.13.2.2.1 | | :COUNt? Vol 2-18.13.2.2.2 | [:ON] <sensor_function>{,<sensor_function>} Vol 2-18.13.2.3 | | where the sensor functions supported | | are same as :OFF | | :ALL Vol 2-18.13.2.3.1 | | :COUNt? Vol 2-18.13.2.3.2 | :STATe? <sensor_function> Vol 2-18.13.2.4

2.1.2.5 SOURce subsystemThe SOURce subsystem of the chassis dynamometer shall provide the following commands

KEYWORD PARAMETER FORM SCPI Reference:SOURce Vol 2-19 :ACCeleration Vol 2-19.1 | [:LEVel] <numeric_value> Vol 2-19.1.1 :FORCe Vol 2-19.8 | :CDOWn Vol 2-19.8.1 | | :INITiate Vol 2-19.8.1.1 | | :NRUNs <numeric_value> Vol 2-19.8.1.3 | | :RLDerivation Vol 2-19.8.1.4 | | | :FACCeptance <numeric_value> Vol 2-19.8.1.4.1 | | | :INITiate Vol 2-19.8.1.4.2 | | | :RMAXimum <numeric_value> Vol 2-19.8.1.4.3 | | | :RVERify <numeric_value> Vol 2-19.8.1.4.4 | | :SOFFset <numeric_value> Vol 2-19.8.1.2 | :CONFigure Vol 2-19.8.2

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.1.3 STATus SubsystemChassis Dynamometer shall implement the status reporting structure described in SCPISyntax & Style Volume 1, Chapter 9, Status Reporting. The SCPI Command ReferenceVolume 2, Chapter 20, STATus Subsystem defines the commands that shall be used tocontrol the status reporting structure.

KEYWORD PARAMETER FORM SCPI Reference:STATus Vol 2-20 :OPERation Vol 2-20.1 | :BIT<n> <n=8 -12> Vol 2-20.1.1 | | :CONDition? Vol 2-20.1.2 | | :ENABle <NRf>|<non-decimal numeric> Vol 2-20.1.3 | | [:EVENt]? Vol 2-20.1.4 | | :NTRansition <NRf>|<non-decimal numeric> Vol 2-20.1.6 | | :PTRansition <NRf>|<non-decimal numeric> Vol 2-20.1.7 | :CONDition? Vol 2-20.1.2 :QUEStionable? Vol 2-20.3 | :BIT<n> <n=9 -12> Vol 2-20.3.1 | | :CONDition? Vol 2-20.3.2 | | :ENABle <NRf>|<non-decimal numeric> Vol 2-20.3.3 | | [:EVENt]? Vol 2-20.3.4 | | :NTRansition Vol 2-20.3.6 | | :PTRansition Vol 2-20.3.7 | :CONDition? Vol 2-20.3.2 | [:EVENt] Vol 2-20.3.4

2.1.3.1 OPERation:STATus:OPERation

For a chassis dynamometer, the bit of interest in the OPERation status structure is theCDYNO summary bit. While the chassis dynamometer is performing its function, bit 9(CDYNO summary) shall be used for the chassis dynamometer status. The fanned outregister is shown in Figure 2-5.

2.1.3.1.1 CDYNo:CONDition?<16 bit integer word>:STATus:OPERation:CDYNo:CONDition?

The Dynamometer Program Status Register contains 16 bits that indicate what operation isbeing performed on the dynamometer. The most significant bit (bit 15) is always 0. Thedynamometer will be in one of the following processes at all times. All processes aremutually exclusive and are overlapped, (i.e. with overlapped processes, a command may besent while a process is executing) but will not be executed until that procedure is completed.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



C - Condi t ion RegisterEV - Event Register

Summary of IEEE 488.2 StatusStructure Registers

TR - Transist ion RegisterEN - Enable Register

Chassis Dynamometer

Fatal Error----Dyno not Warm-- - -

Coastdown Tr igger Speed-- - -Accelerat ion Rate not met-- - -

Motor Over Temperature- - - -Motor Over Current- - - -

Motor Blower Fai lure--- -Fai led to stabi l ize----

Fai led to converge----Reserved for Standard-- - -Reserved for Standard-- - -Reserved for Standard-- - -

Avai lable to Designer--- -Avai lable to Designer--- -Avai lable to Designer--- -

NOT USED-- - -

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

C TR EV EN

QUEStionable StatusError/Event

Queue

VOLTage- - - -CURRent - - - -

TIME--- -POWER- - - -

TEMPerature- - - -FREQuency- - - -

PHASe-- - -MODulat ion-- - -CALibrat ion----

CDYNO Summary - - - -Avai lable to Designer--- -Avai lable to Designer--- -Avai lable to Designer--- -

INSTrument Summary- - - -Command Warn ing - - - -

NOT USED-- - -

*ESE *STB?

Status Byte

Available to Designer-------------------Avai lable to Designer-------------------Error/Event Queue----------------------

----------MAV-----------------------------------------

RQS-------------------------------------------------------

01234567

01234567

Operat ion Complete- - - -Request Contro l - - - -

Query Error----Device Dependent Error- - - -

Execut ion Error----Command Er ror - - - -

User Request- - - -Power On-- - -

01234567

01234567

E V E N

Standard Event Status Register

Chassis Dynamometer

Warm-up- - - -Parasi t ic Loss----

Goto Force--- -Goto Speed-- - -

Road Load Simulat ion-- - -Coastdown-- - -

Base Inert ia----Dr ivel ine Loss----

Road Load Der ivat ion-- - -Idle----

Force Sensor Zero-- - -Reserved for Standard-- - -Reserved for Standard-- - -

Avai lable to Designer--- -Avai lable to Designer--- -

NOT USED-- - -

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

C TR EV EN

OPERation Status

CALibrat ing----SETTing-- - -

RANGing- - - -SWEep ing- - - -

MEASur ing- - - -Wai t ing for TRIGger Summary- - - -

Wai t ing fo r ARM Summary- - - -CORRect ing- - - -

Avai lable to Designer--- -CDYNO Summary - - - -

Avai lable to Designer--- -Avai lable to Designer--- -Avai lable to Designer--- -

INSTrument Summary- - - -PROGram Runn ing- - - -

NOT USED-- - -

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

C TR EV EN

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

0123456789

101112131415

C TR EV EN

Figure 2-5 SCPI Status Registers

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



CDYNO OPERation CONDition Status Register

Bit # Event

0 Warm Up Set if Dynamometer is in Warm Up Process

1 Parasitic Loss Set if Dynamometer is in Parasitic Loss Process.

2 Go To Force Set if Dynamometer is in Go To Force Process.

3 Go To Speed Set if Dynamometer is in Go To Speed Process.

4 Road Load Simulation Set if Dynamometer is in Road Load Simulation Process.

5 Coast Down Set if Dynamometer is in Coast Down Process.

6 Base Inertia Set if Dynamometer is in Base Inertia Process.

7 Driveline Loss Set if Dynamometer is in Driveline Loss Process.

8 Road Load Derivation Set if Dynamometer is in Road Load Derivation Process.

9 Idle Set if Dynamometer is in Idle state.

10 Force Sensor Zero Set if Dynamometer is in Force Sensor Zero state

11 Reserved for standard

12 Reserved for standard

13 Available to Designer


15 Not Used Will always read as 0

2.1.3.2 QUEStionable :STATus:QUEStionable

For the chassis dynamometer, the bit of interest in the QUEStionable status structure is theCDYNO summary bit. When the chassis dynamometer suspects the dynamometerspecification is violated, bit 9 (CDYNO summary) shall be set. The fanned out register is asfollows:

2.1.3.2.1 CDYNo:CONDition?<16 bit integer word>:STATus:QUEStionable:CDYNo:CONDition?

The Dynamometer Questionable Status Register contains 16 bits that indicate whether thedata being acquired is of questionable quality. The most significant bit (bit 15) is always 0.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



The dynamometer updates this register immediately when the dynamometer encounters anerror that may generate questionable data. Bits 0-9 are the minimum subset of errors thatmay generate faulty data. Bits 10-14 are available for a dynamometer manufacturer for otherquestionable data or for other summary bits.

CDYNO QUEStionable CONDition Status Register

Bit # Questionable Event

0 Fatal Error Set when the dynamometer experiences a fatal error that causesthe motor contactor to drop out, such as Torque Safety Limit,Speed Safety Limit or other dynamometer specific fatal error. Anappropriate message must be placed on the Error/Event messagequeue when set.

1 Dynamometer not Warm This bit is set if the dynamometer is not warm or has timed outafter being warm but not used within the TIMeout period.

2 Coast down TriggerSpeed

For a coast down, the dynamometer determines an acceptabletrigger speed based on coast down inputs. If the dynamometerdoes not agree with the set trigger speed, this bit shall be set.

3 Acceleration Rate notmet

The dynamometer will set this bit if the requested accelerationrate for a Process is out of tolerance with the actual acceleration.The tolerance is based on the physical characteristic of thedynamometer.

4 Motor Over Temperature For dynamometers that monitor motor temperature

5 Motor Over Current For dynamometers that monitor motor current

6 Motor Blower Failure For dynamometers that monitor the blower

7 Failed To Stabilize The dynamometer failed to stabilize

8 Failed to Converge The dynamometer failed to converge.

9 Reserved for Standard





1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




15 Not Used Will always read as 0

2.2 Additional FunctionalityNot applicable.

2.3 Programming Examples

2.3.1 CoastdownNote that this example does not start with *RST or *CLS. These commands would not beappropriate when carryover settings or status are important.

Brake off :CONTrol:BRAKe OFF

Contactor On - :CONTrol:MCONtrol ON

See if Dyno is warm STATus:QUEStionable:CDYNo:CONDition?

Controller reads response, looks at bit1

Let Dyno know if vehicleis on or off

:SOURce:FORCe:CONFigure:VEHicle ON

OFF or ON for vehicle

Define table of speedpoints for input intocoastdown

:MEMory:TABLe:SELectCdownSpeed

This table represents the coastdownspeed interval that data will bemeasured and collected.

:MEMory:TABLe:DEFine“SPEed:STARt,SPEed:STOP”, 5

For this example, 5 elements havebeen allocated (30 maximum).

:MEMory:TABLe:SPEed:STARt 24.6,20.2,15.7,11.2,6.7

Meters/sec values corresponding to55, 45, 35, 25, 15 MPH start, and 45,35, 25, 15, 5 MPH stop speeds

:MEMory:TABLe:SPEed:STOP 20.2,15.7,11.2,6.7,2.2

Define the number ofcoastdown runs

:SOURce:FORce:CDOWn:NRUNs 5

Repeat coastdown 5 times

Define table for coastdownoutputs

:MEMory:TABLe:SELectCDownResult

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



:MEMory:TABLe:DEFine“TIME, FORCe, POWer”, 6

Theoretical and measured values fromcoastdown. The table is NRUNs + 1big.

Set Inertia :SOURce:FORCe:CONFigure:VEHicle:DINERtia 1350

Dyno Inertia setting in kilograms

Set Road load coefficients :SOURce:FORCe:CONFigure:VEHicle:DCOefficient 26.7,-0.98, 0.65

Numeric list of polynomialcoefficients. These corresponds to 6,-0.1 and 0.3 in english units (poundsforce (lbf) and miles per hour).

:SOURce:FORCe:CONFigure:VEHicle:TCOefficient 26.7,-0.98, 0.65

Target settings

Set coastdown inputparameters

:SOURce:ACCelerate 1 How fast to accelerate the dyno to topcoastdown point (meters/sec^2)

:SOURce:FORCe:CONFigure:VEHicle:TINertia 1350

Target inertia.

:SOURce:FORCe:CDOWn:SOFFset 2.2

Speed above top set point (meters/sec)

Setup to sense data :SENSe:FUNCtion:CONCurrent ON:SENSe:FUNCtion:ON“FORCe”, “SPEed”,“ACCeleration”, “DISTance”

Allow multiple sensor functions to besensed. Turn on desired sensorfunctions.

Setup trigger system forsensing data

:TRIGger:SOURce TIMer:TRIGger:TIMer 0.100

Select internal timer on dynamometerTake samples every 100 ms, samplesare averaged over 100 ms

Initiate Coastdown :SOURce:FORCe:CDOWn:INITiate

Start coastdown (this command clearsoutput)

Coastdown Complete? :STATus:OPERation:CDYNo:CONDition?

Wait until bit 5 is false indicatingcoastdown complete.

Checkout completion :STATus:QUEStionable:CONDition?

If bit 9 is true then:STATus:QUEStionable:CDYNo:CONDition? can be used tocheck for specific errors.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Iteratively review realtimedata

:INITiate:CONTinousON:SENSe:DATA?

Start acquiring data Returns FORCe,SPEed, ACCeleration, and DISTance.

Retrieve Coastdown results :MEMory:DATa? CDownResult Retrieve Theoretical and Measureddata

:MEMory:DATa?CDownMCoefficients

For definition of CDownMCoefficientsee SAE J2264. This is a curve fit ofthe data

Idle the dynamometer :CONTrol:IDLE:STATe ON

2.3.2 Road Load SimulationNote that this example does not start with *RST or *CLS. These commands would not beappropriate when carryover settings or status are important.

Brake off :CONTrol:BRAKe OFF

Contactor On :CONTrol:MCONtrol ON

See if dyno is warm STATus:QUEStionable:DYNO:CONDition?

Controller reads response, looks at bit1

Set Inertia :SOURce:FORCe:CONFiure:VEHicle:DINERtia 1350

Set Road load coefficients :SOURce:FORCe:CONFigure:VEHicle:RLOad:DCOefficient26.7, -0.98, 0.65

Numeric list of polynomialcoefficients. These corresponds to 6,-0.1 and 0.3 in english units (poundsforce (lbf) and miles per hour).

Set Vehicle Weight :SOURce:FORCe:CONFigure:VEHicle:WEIGht 1300

Vehicle weight in kilograms

Set the augmented braking :SOURce:FORCe:CONFigure:ABRake ON

Augmented braking

Set the gain for augmentedbraking

:SOURce:FORCe:CONFigure:ABRake:GAIN 0.00

Set the threshold foraugmented braking

:SOURce:FORCe:CONFigure:ABRake:THReshold 500

Sets the threshold to 500 Newtons

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Set up the grade simulation :SOURce:FORCe:CONFigure:GRADe ON

:SOURce:FORCe:CONFigure:GRADe:LEVel 5

%in terms in grade - 100% is equal tosin(45deg)

Setup to sense data :SENSe:FUNCtion:CONCurrent ON

Allow multiple sensor functions to besensed.

:SENSe:FUNCtion:ON“FORCe”, “SPEed”,“ACCeleration”, “DISTance”,“FERRor”

Turn on desired sensor functions.

Setup trigger system forsensing data

:TRIGger:SOURce TIMer:TRIGger:TIMer 0.100

Select internal timer on dynamometer.Take samples every 100 ms, samplesare averaged over 100 ms

Initiate Road LoadSimulation

:SOURce:FORCe:RLSimulate:INITiate

Reset the distance to zero.

RLS Complete? :STATus:OPERation:CDYNo:CONDition?

Make sure bit 4 is on indicating dynois in simulation mode.

Check for errors :STATus:QUEStionable:CONDition?

If bit 9 is true then:STATus:QUEStionable:CDYNo:CONDition? can be used to check forspecific errors.

Iteratively review realtimedata

:INITiate:CONTinous ON:SENSe:DATA?

Start acquiring data. Returns FORCe,SPEed, ACCeleration, DISTance andFERRor.

Brake onBrake off

:CONTrol:BRAKe ON:CONTrol:BRAKe OFF

Optional dynamic control of themechanical brake. Used inconjunction with an automatic driverto hold zero speed during idle periods.

Optionally reset thedistance

:SENSe:DISTance:RESet

Idle the Dynamometer :CONTrol:IDLE:STATe ON If idle is complete i.e., dyno at zerospeed the Operation complete flag istrue (same as above wrt. Checkoutcompletion)

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4 New Commands for this Instrument Class

2.4.1 Dynamometer CALibration SubsystemThe Dynamometer CALibration subsystem contains the commands needed for calibrating orverifying various components that affect a dynamometers’ measurement capabilities. Thisincludes load sensor zero, parasitic loss determination, base inertia determination, anddynamometer warm-up.

KEYWORD PARAMETER FORM NOTES:CALibration :BINertia | :AVERage? <numeric_value> [query only] | :HSPeed <numeric_value> | :INITiate [event; no query] | :LSPeed <numeric_value> | :NRUNs <numeric_value> | :SDEviation? <numeric_value> [query only] | :UPDate [event; no query] :PLOSs | :APCoefficients <numeric_value>,<numeric_value>,... | :INITiate [event; no query] | :LATime <numeric_value> | :STIMe <numeric_value> | :UPDate [event; no query] :WARMup | :INITiate [event; no query] | :SPEed <numeric_value> | :TIMeout <numeric_value> :ZERO | :FSENsor | | :INITiate [event; no query] | | :LATime <numeric_value> | | :LEVel? [query only] | | :SPEed <numeric_value> | | :STIMe <numeric_value> | | :UPDate [event; no query]

2.4.1.1 :BINertiaCALibration:BINertia

Base Inertia

For chassis dynamometers, this node describes the procedure to determine the basemechanical inertia of the dynamometer roll system (all rotating mechanical componentsoutside of the control loop). This procedure consists of an acceleration and deceleration of

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



the dynamometer rolls, from which a mechanical inertia calculation is made. Thedynamometer is motored from an initial speed to a final speed at a given constantacceleration, and this interval is timed. Immediately, the dynamometer is motored back fromthe final speed to the initial speed at the same constant acceleration (inverted), and thisinterval is timed. For this pair of intervals, the force transducer output is continuouslymeasured, and the average interval force calculated. The average acceleration is calculatedusing the interval initial and final speed values, and the interval time. This data is used tocalculate the mechanical inertia (Inertia=Force/acceleration). The results are stored in theBaseINertia predefined table.

2.4.1.1.1 :AVERage?CALibration:BINertia:AVERage?

This query returns the running average of all base inertia values acquired since the lastCALibration:BINertia:INITiate was invoked.

2.4.1.1.2 :HSPeed <numeric_value>CALibration:BINertia:HSPeed

High Speed

The higher magnitude speed (m/s) of the speed interval.


2.4.1.1.3 :INITiateCALibration:BINertia:INITiate

Begin motoring the dynamometer through the ACCeleration/deceleration pairs, using:SOURce:ACCeleration as the acceleration/deceleration rate, from LSPeed to HSPeed andback, NRUNs times. All query commands must be accepted and responded to while thiscommand is executing. This command describes an event and therefore has no associated*RST condition.


1. Check critical ancillaries, if any, for proper conditions: Brakes Off, Motor Contactor On,parameters within dynamometer safety limits. For conditions that prohibit operation of thisprocedure, issue appropriate warning messages, and execute the Idle Procedure.

2. Set the DYNO operation condition register Base Inertia Procedure bit indicating the BaseInertia is executing. Note: The DYNO operation condition register will be further defined inVolume 4.

3. Accelerate/decelerate the dynamometer through the speed intervals, recording time,average acceleration, average force for the specified number of runs. The data is placed inthe BaseInertia table after each acceleration/deceleration is run. Update the:CALibration:BINertia:SDEViation value based on this run. End the procedure when thespecified runs are complete.

4. Clear the DYNO operation condition register Base Insrtia Procedure bit indicating theBase Inertia is not executing.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5. Issue the process complete message.

6. Execute the Idle Procedure.

7. Update the on-line mechanical inertia value, if desired.

2.4.1.1.4 :LSPeed <numeric_value>CALibration:BINertia:LSPeed

Low Speed

The lower magnitude speed (m/s) of the speed interval.


2.4.1.1.5 :NRUNs <numeric_value>CALibration:BINertia:NRUNs

Number of Runs - NRUNs

The number of ACCeleration/deceleration pairs to perform. NRUNs will equal the numberof base inertia values acquired.


2.4.1.1.6 :SDEViation?CALibration:BINertia:SDEViation?

Standard Deviation

This query returns the running standard deviation of all base inertia values acquired since thelast CALibration:BINertia:INITiate was invoked.

2.4.1.1.7 :UPDateCALibration:BINertia:UPDate

Place on-line the last determined average base mechanical inertia value. This commanddescribes an event and therefore has no associated *RST condition.

2.4.1.2 :PLOSs:CALibration:PLOSs

Parasitic Loss

For chassis dynamometers this node describes the commands associated with the parasiticloss procedure. This procedure measures and, if requested, updates the parasitic losscorrections for the dynamometer. The parasitic losses are measured by operating thedynamometer at various selected speeds and measuring the force required to maintain theconstant speed. This procedure uses the :MEMory table ’ParasiticLOSs’ that defines thespeed points at which parasitic loss measurements are taken. The parasitic loss coefficientsare calculated at the end of the procedure and reside in the memory table PCOefficient.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.1.2.1 :APCoeff <numeric_value >,numeric_value>,<numeric_value>...:CALibration:PLOSs:APCoeff

Active Parasitic Coefficients - APCoefficients

This is the presently active parasitic loss curve used by the dynamometer. The dynamometerwill maintain coefficients for forward and reverse operations. The appropriate values mustbe placed in the APCoeff memory, based on roll rotation. The Active Parasitic Coefficientsset of retrieved will be based on the currently selected direction.

2.4.1.2.2 :INITiate:CALibration:PLOSs:INITiate

This command starts the parasitic loss procedure. This is an overlapped command. Thiscommand describes an event and therefore has no associated *RST condition.



2. Set the DYNO operation condition register Parasitic Loss Procedure bit indicating theParasitic Loss procedure is executing. Note: The DYNO operation condition register will befurther defined in Volume 4.

3. Accelerate dynamometer to the first speed point defined in the ParasiticLOSs memorytable. Stabilize at speed point for defined stabilization time.

4. Average the force at the roll surface required to maintain the speed set point over thelatency time. The average force value is placed in the ParasiticLOSs table for the specifiedspeed point. Continue until all speed points have been executed in the ParasiticLOSs table.The first zero speed in the ParasiticLOSs table ends the procedure.

5. Perform a curve fit on the ParasiticLOSs table data and place the coefficients in thememory table PCoeff.

6. Clear the DYNO operation condition register Parasitic Loss Procedure bit indicating theparasitic loss procedure is not executing.



2.4.1.2.3 :LATime:CALibration:PLOSs:LATime


The length of time in seconds to average the losses at a speed point.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.1.2.4 :STIMe <numeric_value>CALibration:PLOSs:STIMe




2.4.1.2.5 :UPDate:CALibration:PLOSs:UPDate

Update the dynamometer actual current parasitic loss coefficients (APCoefficients node)with the coefficients contained in memory table PCOefficients.


2.4.1.3 :WARMupCALibration:WARMup

This node controls parameters relating to the warmup of the device.

For chassis dynamometers, this node describes the procedure to set up the conditionsrequired to ready the dynamometer for testing. The warm-up consists of running thedynamometer at a fixed speed over a period of time. Warm-up completion is defined byeither running the dynamometer for a fixed period of time, or by monitoring parasitic lossesand comparing them to a target value tolerance.

2.4.1.3.1 :INITiateCALibration:WARMup:INITiate

Start the warmup procedure.

For chassis dynamometers, motor the dynamometer roll to SPEed, and hold this speed for aTIMeout period of time. All query commands must be accepted and responded to while thiscommand is executing. This command describes an event and therefore has no associated*RST condition.



2. Set the DYNO operation condition register Warm up Procedure bit indicating theWarm-up is executing. Note: The DYNO operation condition register will be further definedin Volume 4.

3. Accelerate dynamometer to the speed point defined by :CALibration:WARMup:SPEed.

4. Average the force at the roll surface required to maintain the speed set point over:CALIbrate:WARMup:LATime. The average force can be monitored by :SENSe:FORCe?

5. The procedure will end when the elapsed time is greater than:CALibration:WARMup:TIMeout.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



6. Clear the DYNO operation condition register Warm up Procedure bit indicating theWarm-up is not executing.



2.4.1.3.2 :SPEed <numeric_value>CALibration:WARMup:SPEed

For chassis dynamometers this is the fixed roll speed (m/s) at which the warm-up will be run.


2.4.1.3.3 :TIMeout <numeric_value>CALibration:WARMup:TIMeout

For chassis dynamometers this is the length of time in seconds the warm-up will run beforeautomatically returning to zero speed.


2.4.1.4 :ZERO:CALibration:ZERO

For chassis dynamometers, this node describes the procedure to set up the conditionsrequired and perform a mathematical zero correction of the roll force measurement systemcalibration. The correction is determined from a measurement of the roll force sensor at agiven roll speed. The results are stored in the FSensorZero pre-defined table.

2.4.1.4.1 :FSENsorCALibration:ZERO:FSENsor

Force Sensor

For chassis dynamometers this node sets up the conditions required and performs amathematical zero correction of the roll force measurement system calibration. Thecorrection is determined from a measurement of the roll force sensor at a given roll speed.

2.4.1.4.1.1 :INITiateCALibration:ZERO:FSENsor:INITiate

This is an overlapped command. Perform the measurement of the roll force, acquiring for thelength of time specified by :LATime. This command describes an event and therefore has noassociated *RST condition.



2. Set the DYNO operation condition register Force Sensor Zero Procedure bit indicating theZero is executing. Note: The DYNO operation condition register will be further defined inVolume 4.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3. Accelerate dynamometer to the speed specified in :CALibration:ZERO:FSENsor:SPEed.Stabilize for :STIMe.

4. Average the force at the roll surface required to maintain the speed set point over the:LATime. The average force value is placed in :LEVel.

5. Clear the DYNO operation condition register Force Sensor Zero Procedure bit indicatingthe Zero is not executing.



2.4.1.4.1.2 :LATimeCALibration:ZERO:FSENsor:LATime


The length of time to average the measured zero reading.


2.4.1.4.1.3 :LEVel? CALibration:ZERO:FSENsor:LEVel?

Returns the measured force value used to determine the mathematical zero correction. Thisvalue is in units of force at the roll surface. This is query only.

2.4.1.4.1.4 :SPEed <numeric_value>CALibration:ZERO:FSENsor:SPEed

The roll speed set point for the force measurement period in m/s.


2.4.1.4.1.5 :STIMe <numeric_value>CALibration:ZERO:FSENsor:STIMe




2.4.1.4.1.6 :UPDateCALibration:ZERO:FSENsor:UPDate

Once the mathematical zero correction has been determined, apply the results to the on-linecalibration. This is not a queryable command and therefore has no *RST associated with it.

2.4.2 DIAGnostic SubsystemThere are no Instrument Class specific commands for DIAGnostics.

2.4.3 MEMory SubsystemThe MEMory subsystem of the chassis dynamometer shall include the following newcommands:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM NOTES:MEMory :TABLe | :ARATe | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | :CINertia | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | :DEFine <structure_string>[,<numeric_value>] | :DRATe | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | :FORCe | | :AACCeleration | | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | | :POINts? [query only] | | :ADECeleration | | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | | :POINts? [query only] | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | | :ZOFFset | | | [:MAGNitude] <numeric_value> | :DLOSs | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | :PCOefficients<n> | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | :SELect <table_name> | :SPEed | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only] | | :STARt <numeric_value>{,<numeric_value>...} | | | :POINts? [query only] | | :STOP <numeric_value>{,<numeric_value>...} | | | :POINts? [query only] | :TIME | | :ACCeleration | | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | | :POINts? [query only] | | :DECeleration | | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | | :POINts? [query only]

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM NOTES | | [:MAGNitude] <numeric_value> {,<numeric_value>} | | | :POINts? [query only]

New commands for the MEMory:TABLe subsystem are defined below.

2.4.3.1 :ARATeMEMory:TABLe:ARATe

Specifies the AccelerationRATe points of the TABLe.

2.4.3.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:ARATe:MAGNitude

Specifies the AccelerationRATe[:MAGNitude] points of the TABLe. The default units ofthis command are meters per second per second.


2.4.3.1.1.1 :POINts?MEMory:TABLe:ARATe:MAGNitude:POINts?

Returns the number of points in the ARATe[:MAGNitude] list of the selected TABLe. If noARATe[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.2 :CINertiaMEMory:TABLe:CINertia

Specifies the CalculatedINertia points of the TABLe.

2.4.3.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:CINertia:MAGNitude

Specifies the CalculatedINertia[:MAGNitude] points of the TABLe. The default units of thiscommand are kilograms.


2.4.3.2.1.1 :POINts?MEMory:TABLe:CINertia:MAGNitude:POINts?

Returns the number of points in the CINertia[:MAGNitude] list of the selected TABLe. If noCINertia[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.3 :DRATeMEMory:TABLe:DRATe

Specifies the DecelerationRATe points of the TABLe.

2.4.3.3.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:DRATe:MAGNitude

Specifies the DecelerationRATe[:MAGNitude] points of the TABLe. The default units ofthis command are meters per second per second.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.3.3.1.1 :POINts?MEMory:TABLe:DRATe:MAGNitude:POINts?

Returns the number of points in the DRATe[:MAGNitude] list of the selected TABLe. If noDRATe[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.4 :FORCeMEMory:TABLe:FORCe

See Volume 2, Section 13.11.12

2.4.3.4.1 :AACCelerationMEMory:TABLe:FORCe:AACCeleration

Specifies the AverageACCeleration points of the TABLe.

2.4.3.4.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:FORCe:AACCeleration:MAGNitude

Specifies the AverageACCeleration[:MAGNitude] points of the TABLe. The default units ofthis command are meters per second per second.


2.4.3.4.1.1.1 :POINts?MEMory:TABLe:FORCe:AACCeleration:MAGNitude:POINts?

Returns the number of points in the AACCeleration[:MAGNitude] list of the selectedTABLe. If no AACCeleration[:MAGNitude] values have been sent POINts? returns 0. If noTABLe has been selected, POINts? returns NAN.

2.4.3.4.2 :ADECelerationMEMory:TABLe:FORCe:ADECeleration

Specifies the AverageDECeleration points of the TABLe.

2.4.3.4.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:FORCe:ADECeleration:MAGNitude

Specifies the AverageDECeleration[:MAGNitude] points of the TABLe. The default units ofthis command are meters per second per second.


2.4.3.4.2.1.1 :POINts?MEMory:TABLe:FORCe:ADECeleration:MAGNitude:POINts?

Returns the number of points in the ADECeleration[:MAGNitude] list of the selectedTABLe. If no ADECeleration[:MAGNitude] values have been sent POINts? returns 0. If noTABLe has been selected, POINts? returns NAN.

2.4.3.4.3 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:FORCe:MAGNitude

See Volume 2, Section 13.11.12.1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.3.4.3.1 :POINts?MEMory:TABLe:FORCe:MAGNitude:POINts?

See Volume 2, Section 13.11.12.1.1

2.4.3.4.4 ZOFFsetMEMory:TABLe:FORCe:ZOFFset

Defines the ZeroOFFset value.

2.4.3.4.4.1 [:MAGNitude]MEMory:TABLe:FORCe:ZOFFset:MAGNitude

Defines the ZeroOFFset value. For chassis dynamometers, this is a single value. This is aforce, and the default units are newtons.


2.4.3.5 :DLOSsMEMory:TABLe:DLOSs

Specifies the DLOSs points of the TABLe.

2.4.3.5.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:DLOSs:MAGNitude

Specifies the DLOSs[:MAGNitude] points of the TABLe. The default units of this commandare newtons.


2.4.3.5.1.1 :POINts?MEMory:TABLe:DLOSs:MAGNitude:POINts?

Returns the number of points in the DLOSs[:MAGNitude] list of the selected TABLe. If noDLOSs[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.6 :PCOefficients<n>MEMory:TABLe:PCOefficients

Specifies the PolynomialCOefficients points of the TABLe.

2.4.3.6.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:PCOefficients:MAGNitude

Specifies the PolynomialCOefficients[:MAGNitude] points of the TABLe. The default unitsof this command are as follows: Units of the polynomial: N, N/(m/s), N/m/s)^2, N/(m/s)^3, ...


2.4.3.6.1.1 :POINts?MEMory:TABLe:PCOefficients:MAGNitude:POINts?

Returns the number of points in the PCOefficients[:MAGNitude] list of the selected TABLe.If no PCOefficients[:MAGNitude] values have been sent POINts? returns 0. If no TABLehas been selected, POINts? returns NAN.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.3.7 :SPEedMEMory:TABLe:SPEed


2.4.3.7.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:SPEed:MAGNitude


2.4.3.7.1.1 :POINts?MEMory:TABLe:SPEed:MAGNitude:POINts?


2.4.3.7.2 :STARtMEMory:TABLe:SPEed:STARt

For chassis dynamometers, this specifies the start speed used in Coastdown

2.4.3.7.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:SPEed:STARt:MAGNitude

Specifies the STARt[:MAGNitude] points of the TABLe. The default units of this start speedcommand are meters per second.


2.4.3.7.2.1.1 :POINts?MEMory:TABLe:SPEed:STARt:MAGNitude:POINts?

Returns the number of points in the STARt[:MAGNitude] list of the selected TABLe. If noSTARt[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.7.3 :STOPMEMory:TABLe:SPEed:STOP

For chassis dynamometers, this specifies the stop speed used in Coastdown

2.4.3.7.3.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:SPEed:STOP:MAGNitude

Specifies the STOP[:MAGNitude] points of the TABLe. The default units of this start speedcommand are meters per second.


2.4.3.7.3.1.1 :POINts?MEMory:TABLe:SPEed:STOP:MAGNitude:POINts?

Returns the number of points in the STOP[:MAGNitude] list of the selected TABLe. If noSTOP[:MAGNitude] values have been sent POINts? returns 0. If no TABLe has beenselected, POINts? returns NAN.

2.4.3.8 :TIMEMEMory:TABLe:TIME


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



2.4.3.8.1 :ACCelerationMEMory:TABLe:TIME:ACCeleration

For chassis dynamometers, this command defines the elapsed time over an accelerationinterval.

2.4.3.8.1.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:TIME:ACCeleration:MAGNitude

Specifies the TIME:ACCeleration[:MAGNitude] points of the TABLe. The default units ofthis command are seconds.


2.4.3.8.1.1.1 :POINts?MEMory:TABLe:TIME:ACCeleration:MAGNitude:POINts?

Returns the number of points in the ACCeleration[:MAGNitude] list of the selected TABLe.If no ACCeleration[:MAGNitude] values have been sent POINts? returns 0. If no TABLehas been selected, POINts? returns NAN.

2.4.3.8.2 :DECelerationMEMory:TABLe:TIME:DECeleration

For chassis dynamometers, this command defines the elapsed time over a decelerationinterval.

2.4.3.8.2.1 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:TIME:DECeleration:MAGNitude

Specifies the TIME:DECeleration[:MAGNitude] points of the TABLe. The default units ofthis command are seconds.


2.4.3.8.2.1.1 :POINts?MEMory:TABLe:TIME:DECeleration:MAGNitude:POINts?

Returns the number of points in the DECeleration[:MAGNitude] list of the selected TABLe.If no DECeleration[:MAGNitude] values have been sent POINts? returns 0. If no TABLehas been selected, POINts? returns NAN.

2.4.3.8.3 [:MAGNitude] <numeric_value>{,<numeric_value>}MEMory:TABLe:TIME:MAGNitude


2.4.3.8.3.1 :POINts?MEMory:TABLe:TIME:MAGNitude:POINts?


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



3 Digital MetersA digital meter is a basic measuring instrument. It typically measures a single value at onepoint in time. This type of instrument is so general that it is first described generically.Attributes specific to a particular type of meter are described in their own subsections.

All SCPI compliant products implement the commands listed in Syntax & Style, 4.2.

Figure 3-1 shows an instrument model for a meter. It is derived from Command Reference,chapter 2. It is essentially the same as Figure 2-1 in Command Reference with various partsgray or dashed. The bold boxes and lines, solid and dashed, are described in this chapter. TheFORMat and ROUTe blocks are shown with dashed lines because many meters use theirdefault settings. *RST sets FORMat[:READings][:DATA] to ASCii andROUTe:TERMinals to FRONt. The gray boxes are not described here. While a meter mayhave MEMory, its functionaily is optional and thus not described.

Figure 3-2 shows how the “Measurement Function” block in Figure 3-1 is expanded in ameter. It is the same as Figure 2-4 in Command Reference with some dashed and gray boxes.The CALCulate block is dashed because after *RST this block has no effect on the data.This chapter does not describe any CALCulate functions. The MEMory block is graybecause while a meter may contain this function, this chapter does not address it.

A designer would never implement a generic meter, but would rather build one of thespecific types. Table 1 lists the various classes of meters considered in this chapter alongwith the quantity they measure. A <meter_fn> is associated with each class of meter. Thecontents of the <meter_fn> shown in the table are used in the actual commands.

Some meters contain several instrument classes. A Digital Multi-Meter might contain a DCvoltmeter, an AC voltmeter, a DC ammeter, an AC ammeter, an ohmmeter, and a 4-wire

Figure 3-1 Simplified Model for a Programmable Meter

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-1

ohmmeter. The SENSe:FUNCtion commands switch the instrument among its implementedclasses. The TRIGger subsystem commands only appear once in the instrument and areshared by all the meters. Such a meter would not have TRIG1 for the DC voltmeter, TRIG2for the AC voltmeter, etc.

Base FunctionalityKeyword

<bf_keyword>

Common UsageName

Measured Quantity <meter_fn>

DCVOLTMETER DC Voltmeter DC Volts VOLTage[:DC]

ACVOLTMETER AC RMS Voltmeter RMS Volts VOLTage:AC

DCAMMETER DC Ammeter DC Amperes CURRent[:DC]

ACAMMETER AC RMS Ammeter RMS Amperes CURRent:AC

OHMMETER Ohmmeter Ohms RESistance

FOHMMETER 4-wire Ohmmeter Ohms FRESistance

TABLE 1. Instrument Classes for Meters


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-2 Digital Meters

3.1 Base FunctionalityThis section describes the functionality all meters implement.

3.1.1 Base Measurement InstructionsSince the basic function of a meter is to measure some quantity, it understands themeasurement instructions in Command Reference, 3. A meter shall implement thesecommands with the appropriate substitution for <meter_fn>.

KEYWORD PARAMETERSCONFigure [:SCALar] :<meter_fn> [<expected_value>[,<resolution>]]CONFigure?FETCh [:SCALar] [:<meter_fn>]? [<expected_value>[,<resolution>]]READ [:SCALar] [:<meter_fn>]? [<expected_value>[,<resolution>]]MEASure [:SCALar] :<meter_fn>? [<expected_value>[,<resolution>]]

The syntax of these commands is found in chapter 3 of the Command Reference. Metersmay accept parentheses and <source_list> as described by the full syntax.

The response from *RST;MEAS:<meter_fn>? is a single <NR1>, <NR2>, or <NR3>because *RST sets FORMat to ASCII, TRIGger:COUNt to 1, and ARM:COUNt to 1.

READ? and FETCh? shall return a <RESPONSE MESSAGE UNIT> containingTRIGger:COUNt times ARM:COUNt numbers corresponding to that many measurements.If ARM:COUNt is not implemented, its value is one. The timing of measurements iscontrolled by the other settings in the TRIGger subsystem.

The command sequence MEAS:<meter_fn>?;FETCH? shall return two identical<RESPONSE MESSAGE UNIT> elements separated by a semicolon.

3.1.1.1 Effects of MEASure Query and CONFigureMEASure query and CONFigure shall set:

SENSe:FUNCtion[:ON] to “[XNONe:]<meter_fn>”INITiate:CONTinuous to OFFTRIGger[:SEQuence]:SOURce to IMMediateTRIGger[:SEQuence]:COUNt to 1TRIGger[:SEQuence]:DELay to MINimum

For meters that implement additional functionality ETRIGGER (see 3.2.1), MEASure queryand CONFigure shall set:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-3

ARM[:SEQuence][:LAYer]:SOURce to IMMediateARM[:SEQuence][:LAYer]:COUNt to 1

For meters that implement additional functionality TERMINALS (see 3.2.2), MEASurequery and CONFigure shall set:

ROUTe:TERMinals unaffected

Note: Additional instrument settings may need to be changed to support the execution of thehigh-level measurement instruction. These settings are under the control of commands notdescribed in this chapter and thus are not defined here.

3.1.1.2 The <expected_value> parameterIf <expected_value> is present and its value is not DEFault,SENSe:<meter_fn>:RANGe[:UPPer] shall be set to the legal value equal to or just largerthan <expected_value>. SENSe:<meter_fn>:RANGe:AUTO shall be set OFF.

If <expected_value> is not present or its value is DEFault,SENSe:<meter_fn>:RANGe:AUTO shall be set ON and the instrument shall autorange tothe best possible range for the measurement.

3.1.1.3 The <resolution> parameterIf <resolution> is present and its value is not DEFault, SENSe:<meter_fn>:RESolution shallbe set to the legal value equal to or just less than <resolution>.

If <resolution> is not present or its value is DEFault, SENSe:<meter_fn>:RESolution shallbe set to a legal value that gives a reasonably accurate result without taking excessively long.

3.1.2 Base Device-oriented Functions

3.1.2.1 FORMat SubsystemThis subsystem is not required. A meter shall implement the FORMat[:READings][:DATA]ASCii and FORMat[:READings]:DINTerchange OFF settings. Note: These are the *RSTvalues, so the commands are not required.

3.1.2.2 SENSe subsystemAny meter shall sense a selected function and control the range and resolution of the sensor.The ability to autorange is required. The ability to turn on multiple <sensor_functions>simultaneously is not required.

A meter shall implement these SENSe commands with the appropriate substitution for<meter_fn>.

KEYWORD PARAMETER FORM SCPI ReferenceSENSe Vol 2-18 :FUNCtion[:ON] “[XNONe:]<meter_fn>” Vol 2-18.13.2 :<meter_fn> :RANGe [:UPPer] <numeric_value> :AUTO <Boolean> :RESolution <numeric_value>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-4 Digital Meters

3.1.2.3 TRIGger subsystemThe primary purpose of the TRIGger subsystem is to control when measurements are made.The default timing is generally to take a measurement as soon as possible.

A meter shall implement these TRIGger commands.

KEYWORD PARAMETER FORM SCPI ReferenceEditINITiate Vol 2-24.7

[:IMMediate] Vol 2-24.7.2 [:ALL] Vol 2-24.7.2.1ABORt Vol 2-24.5TRIGger Vol 2-24.8 [:SEQuence] Vol 2-24.8.1 :COUNt <numeric_value> Vol 2-24.8.1.2 :DELay <numeric_value> Vol 2-24.8.1.5 :SOURce BUS | IMMediate | EXTernal | ... Vol 2-24.8.1.17

Requiring BUS as a legal parameter to TRIGger:SOURce has the side effect of requiringDT1 capability in an IEEE 488.2 device. It also means the meter implements the *TRGcommon command.

A VXIbus device with a trigger function is required to implement the Trigger command.When TRIGger:SOURce is set BUS, a VXIbus meter shall use the Trigger command as theTRIGger source.

3.1.3 Base Status ReportingSyntax & Style, chapter 9 describes the status reporting structure used in all SCPIinstruments. Command Reference, chapter 20 defines the commands which control the statusreporting structure.

3.1.3.1 QUEStionable StatusWhen a meter is measuring DC volts or AC volts, the meter shall set bit 0, VOLTage, in theQUEStionable status structure when the meter suspects the voltage is of questionableaccuracy. When a meter is measuring DC current or AC current, the meter shall set bit 1,CURRent, in the QUEStionable status structure when the meter suspects the current is ofquestionable accuracy. When a meter is measuring ohms, the meter shall set either bit 0,VOLTage, or bit 1, CURRent when the meter suspects either is of questionable accuracy.

3.1.3.2 OPERation StatusWhile the meter is performing one of the operations listed in the OPERation status structure,that bit shall be set in the condition register. Every meter shall report at least RANGing, bit2, MEASuring, bit 4, and Waiting for TRIG, bit 5.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-5

3.2 Additional functionality3.2.1 Extended Trigger

The <af_keyword> for extended trigger is ETRIGGER.

Meters with extended trigger functionality provide two layer triggering where a separateevent must occur before the TRIGger layer is entered. The commands under ARM are usedto provide this functionality rather than another SEQuence.

3.2.1.1 ETRIGGER Measurement InstructionsETRIGGER adds no Measurement Instructions.

3.2.1.2 ETRIGGER Device-oriented Functions

3.2.1.2.1 TRIGger SubsystemKEYWORD PARAMETER FORM SCPI ReferenceARM Vol 2-24.6 [:SEQuence] Vol 2-24.6.1 [:LAYer] Vol 2-24.6.1.2 :SOURce {BUS | IMMediate | ... } Vol 2-24.6.1.2.14

3.2.1.3 ETRIGGER Status ReportingBit 6 (Waiting for ARM) in the OPERation Status Register is used to indicate the status ofthe trigger model.

3.2.2 Multiple TerminalsThe <af_keyword> for multiple terminals is TERMINALS.

A meter generally has only a single input, though some meters may be able switch the inputbetween front and rear terminals. These meters have the TERMINALS additionalfunctionality.

3.2.2.1 TERMINALS Measurement InstructionsTERMINALS adds no Measurement Instructions.

3.2.2.2 TERMINALS Device-oriented Functions

3.2.2.2.1 ROUTe SubsystemA meter which can select between front and rear terminals shall implement

KEYWORD PARAMETER FORM SCPI ReferenceROUTe Vol 2-17 :TERMinals FRONt | REAR Vol 2-17.7

3.2.2.3 TERMINALS Status ReportingTERMINALS adds no Status Reporting requirements.

3.2.3 Offset CompensationThe <af_keyword> for offset compensation is OCOMPENSATED.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-6 Digital Meters

An ohmmeter or 4-wire ohmmeter may be unable to measure resistance when residualvoltages are present. An ohmmeter or 4-wire ohmmeter which can compensate for residualvoltages when measuring resistance has the OCOMPENSATED additional functionality.

3.2.3.1 OCOMPENSATED Measurement InstructionsOCOMPENSATED adds no measurement instructions.

MEASure:RESistance? and CONFigure:RESistance shall setSENse:RESistance:OCOMpensated to OFF. MEASure:FRESistance? andCONFigure:FRESistance shall set SENse:FRESistance:OCOMpensated to OFF.

3.2.3.2 OCOMPENSATED Device-oriented Functions

3.2.3.2.1 SENSe SubsystemAn ohmmeter or 4-wire ohmmeter which can compensate for residual voltages shallimplement:

KEYWORD PARAMETER FORM SCPI ReferenceSENSe Vol 2-18 :RESistance Vol 2-18.18 | :FRESistance :OCOMpensated <Boolean> Vol 2-18.18.3

3.2.3.3 OCOMPENSATED Status ReportingOCOMPENSATED adds no Status Reporting requirements.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-7

3.3 Various Meter ClassesThis section provides additional information and rules of behavior for specific meter classes.

3.3.1 DC VoltmeterDC voltmeters measure the average voltage level of the signal across their inputs.

3.3.1.1 RangeDC voltmeters shall measure negative as well as positive voltages symmetrically about zero.SENSe:RANGe[:UPPer] determines how far from zero measurements can be made. TheMINimum and MAXimum values for SENSe:RANGe[:UPPer] shall be positive. Since therange is symmetric about zero, SENSe:RANGe:LOWer is not needed, but if implemented itsvalue shall be coupled to UPPer by the equation:

LOWer = -UPPer.

3.3.1.2 SENSe CommandsSENSe:VOLTage[:DC] commands are found in Command Reference, 18.20.

3.3.2 AC RMS VoltmeterAC RMS voltmeters measure the root mean square of the voltage level across their inputs.

3.3.2.1 RangeSince the RMS of any signal is non-negative, the MINimum and MAXimum values forSENSe:RANGe[:UPPer] shall be positive. SENSe:RANGe:LOWer is not needed.

3.3.2.2 SENSe CommandsSENSe:VOLTage:AC commands are found in Command Reference 1994, 18.21.

3.3.3 OhmmeterOhmmeters measure the resistance across their input terminals.

Typically, a DC current is sourced and the DC voltage is measured. Resistance is calculatedby dividing the current into the voltage.

3.3.3.1 SENSe CommandsSENSe:RESistance commands are found in Command Reference 1994, 18.16.

3.3.3.2 4-wire Ohmmeter4-wire ohmmeters measure the resistance across two of their input terminals with theassistance of two additional wires.

Typically, a DC current is sourced through one set of wires and the DC voltage is measuredacross the other set. As with a 2-wire ohms measurement, resistance is calculated by dividingthe current into the voltage.

3.3.3.3 SENSe CommandsSENSe:FRESistance commands are found in Command Reference 1994, 18.16.

3.3.4 DC AmmeterDC ammeters measure the average value of the current through their inputs.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-8 Digital Meters

3.3.4.1 RangeDC ammeters shall follow the same constraints on RANGe as DC voltmeters.

3.3.4.2 SENSe CommandsSENSe:CURRent[:DC] commands are found in Command Reference 1994, 18.6.

3.3.5 AC RMS AmmeterAC RMS ammeters measure the root mean square of the current through their inputs.

3.3.5.1 RangeAC RMS ammeters shall follow the same constraints on RANGe as AC voltmeters.

3.3.5.2 SENSe CommandsSENSe:CURRent:AC commands are found in Command Reference 1994, 18.6.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-9

3.4 Programming ExamplesThis section discusses how a user might program a meter for certain applications. Theexamples assume the meter is a DC voltmeter, but a meter of any type could have been used.

3.4.1 Simple MeasurementIn an application where the user wants to make a simple measurement with no specialconsideration for signal conditioning or timing, the MEASure query is an excellent choice.An example might be checking if a power supply voltage is at a proper level. The instrumentmight receive the following query to make a voltage measurement:

MEASure:VOLTage:DC?

The instrument autoranges to the best range and makes the measurement with a reasonableresolution. A single value is returned as soon as possible. The instrument does not wait forany other triggers.

Another user might send:

MEASure:VOLTage:DC? 5,.05

A voltmeter that has 1, 10, and 100 volt ranges would be in the 10 volt range. Anothervoltmeter with 3, 30, and 300 volt ranges would use the 30 volt range. Resolution wouldprobably get set to 10 mv corresponding to 3 1/2 digits. Again the measurement is made assoon as possible.

This same measurement could be made using low level commands.

*RSTSENSe:FUNCtion “VOLTage:DC”;VOLTage:RANGe 5V;RESolution .05VINITiate;FETCh?

Note that *RST sets all TRIGger subsystem SOURce to IMMediate and COUNt to 1.

3.4.2 Time Critical MeasurementTo use an external triggering signal, the user cannot use MEASure query because MEASurequery sets TRIGger:SOURce to IMMediate. Instead, CONFigure and READ? with TRIGgercommands between them is the proper choice. The sequence:

CONFigure:VOLTage:DC 5V,.05VTRIGger:SOURce EXTernalREAD?

sets up the SENSe functions easily. The single TRIGger command modifies the triggeringsubsystem just enough to do the job. The READ query initiates a measurement which waitsfor the external trigger before returning the result.

3.4.3 Multiple MeasurementsThe overhead of sending commands may prevent taking measurements made close togetherin time using a separate MEASure query or READ? for each measurement. The instrumentcould, however, buffer the readings. The sequence:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-10 Digital Meters

CONFigure:VOLTage:DC 5V,.05VTRIGger:SOURce EXTernal;COUNt 10READ?

returns ten separate measurements taken when ten external triggers occur. A defensiveprogrammer would then send SYSTem:ERRor? and check for error -210, “Trigger error” or-211, “Trigger ignored” to see if there were any problems with the triggering.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digital Meters 3-11

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


3-12 Digital Meters

4 DigitizersA digitizer is an instrument designed primarily to measure time-swept voltage waveforms.Because a digitizer is primarily a sensing device, the SENSe root node is optional.

All SCPI compliant products implement the commands listed in Syntax & Style, 4.2.

Figure 4-1 shows an instrument model for a digitizer. It is derived from CommandReference, chapter 2. It is essentially the same as Figure 2-1 in Command Reference withvarious parts gray or dashed. The bold boxes and lines, solid and dashed, are described inthis chapter. The ROUTe block are shown with dashed lines because many digitizers usetheir default settings.

The gray boxes are not described here. While a digitizer may have MEMory, its functionailyis optional and thus not described.

Figure 4-2 shows how the “Measurement Function” block in Figure 4-1 is expanded in adigitizer. It is the same as Figure 2-4 in Command Reference with some dashed and grayboxes. The CALCulate block is dashed because after *RST this block has no effect on thedata. This chapter does not describe any CALCulate functions. The MEMory block is graybecause while a digitizer may contain this function, this chapter does not address it.

Figure 4-1 Simplified Model of a Digitizer

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digitizers 4-1

4.1 Base FunctionalityThis section describes the functionality all digitizers implement.

The <bf_keyword> for a digitizer is DIGITIZER.

Digitizer inputs are typically called channels. These are generally numbered 1, 2, 3, ... orlettered A, B, C, .... Several SCPI commands in this section use numeric suffixes on headerkeywords or parameters. The intention is that these suffixes unify operations that apply tothe associated channel.

Two-channel capability is shown in the examples to illustrate this concept. A single channeldigitizer may be implemented by omitting the command and or parameter options with thenumeric suffix 2. More than two channels may be implemented by extending the numericsuffix.

4.1.1 Base Measurement InstructionThe base functionality for a digitizer requires no measurement instructions (MEASure,CONFigure, READ, FETCh).

4.1.2 Base Device-oriented FunctionsThe base functionality for digitizers shall contain the commands described in this section.

4.1.2.1 Input functions

KEYWORD PARAMETER FORM SCPI ReferenceINPut[1]|INPut2 Vol 2-11 :COUPling AC | DC | GND Vol 2-11.3

This command controls the coupling characteristics of the input to the amplifier.

At *RST, the coupling for digitizers shall be DC.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-2 Digitizers

As previously mentioned, INPut1 is associated with the first input channel, and so on.

4.1.2.2 SENSe amplitude functions

KEYWORD PARAMETER FORM SCPI Reference[SENSe] Vol 2-18 :VOLTage[1]|:VOLTage2 Vol 2-18.24 [:DC] Vol 2-18.24.1 :RANGe Vol 2-18.24.1.5 :LOWer <numeric_value> Vol 2-18.24.1.5.2 :OFFSet <numeric_value> Vol 2-18.24.1.5.4 :PTPeak <numeric_value> Vol 2-18.24.1.5.5 [:UPPer] <numeric_value> Vol 2-18.24.1.5.1

VOLTage1 is associated with INPut1, VOLTage2 is associated with INPut2, and so on.

The PTPeak command sets the amplifier gain of the specified channel.

The OFFSet command sets the voltage offset of the amplifier, the midpoint of the PTPeakrange. Measurement results remain constant when offset is added.

UPPer and LOWer, also expressed in volts, are coupled to OFFSet and PTPeak as describedin the introduction to Command Reference, chapter 18.

4.1.2.3 SENSE timebase functions

KEYWORD PARAMETER FORM SCPI Reference[SENSe] Vol 2-18 :SWEep Vol 2-18.23 :POINts <numeric_value> Vol 2-18.23.8 :TIME <numeric_value> Vol 2-18.23.12 :TINTerval <numeric_value> Vol 2-18.23.13

POINts controls the record length of the acquisition.

TIME is the full time span of the acquisition.

TINTerval controls the time interval between points.

NOTE that if the number of sweep points and and the time interval are changed then thesweep time will change as well.

At *RST, a digitizer shall set its SWEep parameters to a known, device-specified value.

4.1.2.4 SENSe One-of-N Function ControlDigitizers shall implement the following commands that allow the selection of the activechannel using [SENSe:]FUNCtion.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digitizers 4-3

KEYWORD PARAMETER FORM SCPI Reference[SENSe] Vol 2-18 :DATA? [<data_handle>] Vol 2-18.13.1 :FUNCtion :CONCurrent <Boolean> Vol 2-18.13.2.1 :OFF <sensor_function> Vol 2-18.13.2.2 [:ON] <sensor_function> Vol 2-18.13.2.3 :STATe? <sensor_function> Vol 2-18.13.2.4

Where <sensor_function> and <data_handle> for channel 1 shall be specified as“XTIMe:VOLTage[:DC] 1" and so on.

[SENSe]:DATA? shall return data for the channel specified in the query parameter or shallreturn data for the active channel(s).

4.1.2.5 Formatting

KEYWORD PARAMETER FORM SCPI Reference:FORMat [:DATA] <type> [, <numeric_value>] Vol 2-

The parameter ASCii and the <numeric_value> zero shall be supported.

At *RST, the :FORMat type shall be ASCii,0.

4.1.2.6 Trigger functions

KEYWORD PARAMETER FORM SCPI ReferenceINITitiate [:IMMediate] Vol 2-24.7.2 [:ALL] Vol 2-24.7.2.1ABORt Vol 2-24.5TRIGger Vol 2-24.8 [:SEQuence[1]] :COUPling AC | DC Vol 2-24.8.1.3 :LEVel <numeric_value> Vol 2-24.8.1.12 :SLOPe POSitive | NEGative | EITher Vol 2-24.8.1.16 :SOURce INTernal[1] | ... Vol 2-24.8.1.17

Triggering sourced from channel 1 shall be specified as INTernal1 and so on.

At *RST, SOURce shall be set to INTernal1, COUPling shall be set to DC, SLOPe shall beset to POSitive, and LEVel shall be set to a known, device-specified value.

4.1.3 Base Status ReportingAll SCPI digitizers shall implement the status reporting structure described in Syntax &Style, Status Reporting. Command Reference, STATus Subsystem defines the commandswhich shall be used to control the status reporting structure.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-4 Digitizers

4.1.3.1 QUEStionableThe base functionality of a digitizer adds no requirements for this register.

4.1.3.2 OPERationAt a minimum, the digitizer shall report Waiting for TRIG, bit 5.

4.2 Programming ExampleThe following set of commands sets up the digitizer to acquire a waveform on channel 1 forAC coupling, 10 peak to peak signal with a sample recorded every microsecond. The triggersource is channel 1 and is DC coupled, looking for a positive slope transition of 100millivolts. After setting up the digitizer the trigger system is initiated and the resultantcaptured waveform is returned to the controller in ASCII format.

Longform version:

*RSTINPut:COUPling ACSENSe:VOLTage:DC:RANGE:PTPeak 10 VSENSe:SWEep:TINTerval 1E-6 SSENSe:FUNCtion:CONCurrent OFFSENSe:FUNCtion:ON “XTIMe:VOLTage:DC 1"TRIGger:SEQuence1:LEVel 0.1VINITiate:IMMediate:ALLSENSe:DATA?

Shortform version:

*RSTINP:COUP ACVOLT:RANG:PTP 10SWE:TINT 1E-6 SFUNC:CONC 0;ON “XTIM:VOLT 1"TRIG:LEV 0.1INITDATA?

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Digitizers 4-5

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


4-6 Digitizers

5 Emissions BenchesAn emissions bench is a complex measuring device. It measures the constituentconcentration in a sample of gas introduced into the bench. It typically consists of severalinstruments, at least one of which is a gas analyzer, but also can include a mini-diluter, a gasdivider, as well as temperature, pressure, and flow measurement instruments.

All SCPI compliant products implement the commands listed in Syntax and Style, 4.2.

As indicated in Figure 5-1 above, emissions benches make use of signal (gas) routingcommands, the TRIGger subsystem, extensive use of measurement function commands(using the :SENSe block), and extensive use of the :MEMory subsystem. In addition, the:CALibrate and :SYSTem subsystems are utilized in both standard and emissionsbench-specific ways.

5.1 Base FunctionalityThis section describes the base functionality for emissions benches.

The <bf_keyword> for an emissions bench is EBENCH.

5.1.1 Base Measurement InstructionsThe base functionality for an emissions bench contains no commands from the:MEASurement subsystem.

5.1.2 Base Device-Oriented FunctionsThe base functionality for an emissions bench include :SENSe, :MEMory, :TRIGger,:CALibration, :CONTrol, :SYSTem, :DIAGnostic, :INSTrument, and :ROUTe subsystems.It also defines device dependent :STATus bits and instructions for emissions benches. ASCPI-compliant emissions bench shall implement all of the commands listed in this section.

MEMoryTRIGger

SignalRouting FORMatMeasurement

Functiondatabus

SignalRouting FORMatSignal

Generationdatabus

Figure 5-1 Simplified Model for an Emissions Bench

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Emissions Benches 5-1

5.1.2.1 CALibration subsystemCALibration commands for emissions benches, detailed in section 5.4 of this volume, are asfollows:

KEYWORD PARAMETER FORM SCPI Reference:CALibration Vol 4-5.4 :LINearize Vol 4-5.4.1 | :ACCept Vol 4-5.4.1.1 | :ACQuire Vol 4-5.4.2 | :AUTO ONCE Vol 4-5.4.2.1 | :CALCulate AUTO | POLYnomial<n> | Vol 4-5.4.2.2 | | SRATional<n> | :CURVe Vol 4-5.4.2.3 | | [:TYPE] POLYnomial<n>| Vol 4-5.4.2.3.1 | | SRATional<n>,<numeric_value>{,<numeric_value>} | | :ZFORce <Boolean> Vol 4-5.4.2.3.2 | :VERify Vol 4-5.4.2.4 | | :ACQuire Vol 4-5.4.2.4.1 | | :TOLerance <numeric_value> Vol 4-5.4.2.4.2 | | :TYPE CCURve | NCURve Vol 4-5.4.2.4.3

5.1.2.2 CONTrol subsystemCONTrol commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:CONTrol Vol 2-6 :EBENch Vol 2-6.6 | :CLEan Vol 2-6.6.1 | | :DURation <numeric_value> Vol 2-6.6.1.2 | | [:INIT] Vol 2-6.6.1.1

5.1.2.3 DIAGnostic subsystemDIAGnostic commands for emissions benches, detailed in section 5.5 of this volume, are asfollows:

KEYWORD PARAMETER FORM SCPI Reference:DIAGnostic Vol 4-5.5 :HUP Vol 4-5.5.1 | :ACQuire Vol 4-5.5.1.1 | :CALCulate Vol 4-5.5.1.2 :LEAK Vol 4-5.5.2 | :ACQuire Vol 4-5.5.2.1 | :CALCulate Vol 4-5.5.2.2 :NEFFiciency Vol 4-5.5.3 | :ACQuire Vol 4-5.5.3.1 | :CALCulate Vol 4-5.5.3.2

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


5-2 Emissions Benches

5.1.2.4 INSTrument subsystemINSTrument commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:INSTrument Vol 2-12 :CATalog? Vol 2-12.1 | :FULL? Vol 2-12.1.1 :DEFine Vol 2-12.3 | :GROup <identifier>, <identifier_list> Vol 2-12.3.1 | [:NAME] <identifier>,<numeric_value> Vol 2-12.3.2 :DELete Vol 2-12.4 | :ALL Vol 2-12.4.1 | [:NAME] <identifier> Vol 2-12.4.2 [:SELect] <identifier> Vol 2-12.6

5.1.2.5 MEMory subsystemMEMory commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:MEMory Vol 2-13 :TABLe Vol 2-13.11 | :BNUMber<n> <numeric_value> {,<numeric_value>} Vol 2-13.11.1 | | :POINts? Vol 2-13.11.1.1 | :CCURve <numeric_value> {,<numeric_value>} Vol 2-13.11.2 | | :POINts? Vol 2-13.11.2.1 | :CONCentration <numeric_value> {,<numeric_value>} Vol 2-13.11.3 | | :POINts? Vol 2-13.11.3.1 | :CPOint <numeric_value> {,<numeric_value>} Vol 2-13.11.5 | | :POINts? Vol 2-13.11.5.1 | :DEFine <structure_string> [,<numeric_value>] Vol 2-13.11.11 | :DFACtory <numeric_value> {,<numeric_value>} Vol 2-13.11.7 | | :POINts? Vol 2-13.11.7.1 | :DLASt numeric_value> {,<numeric_value>} Vol 2-13.11.8 | | :POINts? Vol 2-13.11.8.1 | :DLINearize <numeric_value> {,<numeric_value>} Vol 2-13.11.9 | | :POINts? Vol 2-13.11.9.1 | :EXPected <numeric_value> {,<numeric_value>} Vol 2-13.11.10 | | :POINts? Vol 2-13.11.10.1 | :LABel <string> {,<string>} Vol 2-13.11.14 | | :POINts? Vol 2-13.11.14.1 | :LOG <string> {,<string>} Vol 2-13.11.16 | | :POINts? Vol 2-13.11.16.1 | :NCURve <numeric_value> {,<numeric_value>} Vol 2-13.11.18 | | :POINts? Vol 2-13.11.18.1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM NOTES | :RAW <numeric_value> {,<numeric_value>} Vol 2-13.11.20 | | :POINts? Vol 2-13.11.20.1 | :SELect <identifier> Vol 2-13.11.22 | :TOLerance <numeric_value> {,<numeric_value>} Vol 2-13.11.25 | | :POINts? Vol 2-13.11.25.1 | :WFACtor <numeric_value> {,<numeric_value>} Vol 2-13.11.28 | | :POINts? Vol 2-13.11.28.1

5.1.2.6 ROUTe subsystemROUTe commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:ROUTe Vol 2-17 :SAMPle Vol 2-17.4.3.1 | :CATalog? Vol 2-17.5.1 | [:OPEN] BAG | DILute | PRE | POST | MID Vol 2-17.5.2

| CEFFiciency | NONE | ZERO | SPAN | VERify | MANifold<n>

Note that some emissions benches may not implement all of the above sample paths.

5.1.2.7 SENSe subsystemSENSe commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:SENSe Vol 2-18 :AVERage Vol 2-18.2 | :COUNt <numeric_value> Vol 2-18.2.2 | :TCONtrol EXPonential | MOVing | Vol 2-18.2.4 | | NORMal | REPeat | :TYPE COMPlex | ENVelope | MAXimum | Vol 2-18.2.5 | | MINimum | RMS | SCALar :CONCentration Vol 2-18.4 | :CSET <numeric_value>,<numeric_value> Vol 2-18.4.1 | {,<numeric_value>,<numeric_value>,...} | :LOWer <numeric_value>{,<numeric_value>} Vol 2-18.4.2 | :LSET POLYnomial<n> | Vol 2-18.4.3 | SRATional<n>,<numeric_value> | {,<numeric_value>},{POLYnomial<n> | | SRATional<n>,<numeric_value> | {,<numeric_value>}} | :RANGe Vol 2-18.4.4 | | :AUTO Vol 2-18.4.4.1 | | | :LOWer <numeric_value>{,<numeric_value>} Vol 2-18.4.4.1.1 | | | [:STATe] <Boolean> Vol 2-18.4.4.1.2 | | | :UPPer <numeric_value>{,<numeric_value>} Vol 2-18.4.4.1.3 | | [:FIXed] <numeric_value>{,<numeric_value>} Vol 2-18.4.4.2

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



| :TALign <numeric_value> {,<numeric_value>} Vol 2-18.4.5 | :UPPer <numeric_value>{,<numeric_value>} Vol 2-18.4.6 :CORRection Vol 2-18.6 | :AUTO Vol 2-18.6.1 | :CALCulate Vol 2-18.6.2 | :SPOint Vol 2-18.6.10 | | :ACQuire Vol 2-18.6.10.1 | | :DTOLerance <numeric_value>{,<numeric_value>} Vol 2-18.6.10.2 | :STATe < Boolean > Vol 2-18.6.11 | :ZERO Vol 2-18.6.12 | | :ACQuire Vol 2-18.6.12.1 | | :DTOLerance <numeric_value>{,<numeric_value>} Vol 2-18.6.12.2 :DATA? Vol 2-18.13.1 :FUNCtion <function_name> {,<function_name>} Vol 2-18.13.2 | | where function_name can be: | | CONCentration<n>,TIMer:COUNt, | | CONCentration<n>:SDEViation, | | CONCentration<n>:TALign, | | CONCentration<n>:RAW | :CONCurrent <Boolean> Vol 2-18.13.2.1 :STABilize Vol 2-18.22 | :NTOLerance <numeric_value>{,<numeric_value>} Vol 2-18.22.1 | [:STATe] <Boolean> Vol 2-18.22.2 | :TIME<n> <numeric_value>{,<numeric_value>} Vol 2-18.22.3

NOTE::SENSe:CORRection:CALCulate calculates the zero/span adjustment of the form

y=mx+b

where x = %FSRAW Data Valuey = %FSADJ Data Valuem = Zero/Span Adjustment Slope Coefficientb = Zero/Span Adjustment Intercept Coefficient

and

m = S0 − Z0

Sm − Zm

b = Z0Sm − ZmS0

Sm − Zm

where Z0 = Zero Gas ExpectedZm = Zero Gas MeasuredS0 = Span Gas ExpectedSm = Span Gas Measured

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5.1.2.8 SYSTem subsystemSYSTem commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:SYSTem Vol 2-21 :COMMunicate Vol 2-21.4 | :SOCKet<n> Vol 2-21.4.4 | | :ADDRess <string> (IPaddress|Host Name) Vol 2-21.4.4.1 | | :CONNect Vol 2-21.4.4.2 | | :DISConnect Vol 2-21.4.4.3 | | :FEED <data_handle>{,<data_handle>} Vol 2-21.4.4.4 | | | :OCONdition<event_handle> Vol 2-21.4.4.4.1 | | | :SCONdition <event_handle> Vol 2-21.4.4.4.2 | | :LISTen Vol 2-21.4.4.5 | | :PORT <NRf>|<non-decimal numeric> Vol 2-21.4.4.6 | | :TYPE TCP|UDP Vol 2-21.4.4.7 :DATE <year>,<month>,<day> Vol 2-21.7 :ERRor Vol 2-21.8 | :ALL? Vol 2-21.8.4 | :CODE Vol 2-21.8.5 | | :ALL? Vol 2-21.8.5.1 | | [:NEXT]? Vol 2-21.8.5.2 | :ENABle Vol 2-21.8.7 | | :ADD <numeric list> Vol 2-21.8.7.1 | | :DELete <numeric list> Vol 2-21.8.7.2 | | [:LIST] Vol 2-21.8.7.3 | [:NEXT]? Vol 2-21.8.8 :LOCK Vol 2-21.14 | :RELease Vol 2-21.14.2 | :REQuest? Vol 2-21.14.3 | :OWNer? Vol 2-21.14.1 :TIME Vol 2-21.19 | :TIMer Vol 2-21.19.1 | | :COUNt <numeric_value> Vol 2-21.19.1.1 | | [:STATe] <Boolean> Vol 2-21.19.1.2

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5.1.2.9 TRIGger subsystemTRIGger commands for emissions benches are as follows:

KEYWORD PARAMETER FORM SCPI Reference:TRIGger Vol 2-24.8 [:SEQuence] Vol 2-24.8.1 | :ECOunt <numeric_value> Vol 2-24.8.1.7 | :LINK <event_handle> Vol 2-24.8.1.13 | :SOURce TIMer Vol 2-24.8.1.17 | :TIMer <numeric_value> Vol 2-24.8.1.18

5.1.3 Base Status ReportingVolume 1, Syntax and Style, Status Reporting, describes the status reporting structure usedin all SCPI instruments. Volume 2, Command Reference, STATus Subsystem, defines thecommands that control the status reporting structure.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5.2 Additional functionalityAll functionality described for emissions benches is considered base functionality at thistime.

5.3 Examples

5.3.1 Zero/Span/Zero ProcedureThe following illustrates a possible command sequence for performing a zero/span/zeroprocedure:

SCPI Command Notes:INST:DEFine:GROup “BENCH”,"CONC1","CONC2":INST:SELect “BENCH”

Select desired analyzers:SENSe:FUNCtion:CONCurrent ON:SENSe:FUNCtion “CONC1",”CONC1:SDEV","CONC2","CONC2:SDEV"

Applies to selected analyzers; used in :SENS:DATA:SENSe:CORRection:ZERO:DTOLerance 5

Allow 5% tolerance for zero drift:SENSe:CORRection:SPOint:DTOLerance 5

Allow 5% tolerance for set point (span) drift:SENSe:CORRection:STATe OFF

New Z/S/Z needs uncorrected values;drift check would require :SENS:CORR:STATE ON

:SENSe:CORRection:ZERO:ACQuirerequest and execute zero procedure

:STATus:OPERation:INSTrument:ISUMmary1:BIT10:CALibrating?Keep polling while bit 1 (zero) is set (CONC1)

:STATus:OPERation:INSTrument:ISUMmary2:BIT10:CALibrating?Keep polling while bit 1 (zero) is set (CONC2)

:STATus:QUEStionable:INSTrument:ISUMmary1:BIT10:CALibrating?0 = successful zero; Bit 1 set = failure


:SENSe:DATA? Retrieve Zero Concentration Readings and SDEVs:MEMory:DATA?ZDRift Retrieve Zero Drifts:SENSe:CORRection:SPOint:ACQuire

execute SPOint (span) procedure*WAI Alternative to polling;

wait for SPOint (span) operation to complete:STATus:QUEStionable:INSTrument:ISUMmary1:BIT10:CALibrating?

0 = successful zero; Bit 2 set = failure:STATus:QUEStionable:INSTrument:ISUMmary2:BIT10:CALibrating?

0 = successful zero; Bit 2 set = failure:SENSe:DATA? Retrieve Span Concentration Readings and SDEV’s:MEMory:DATA?SDRift Retrieve Span Drifts:SENSe:CORRection:CALCulate

Calculate new m, b corrections (skip this if drift check):SENSe:CORRection:ZERO:ACQuire

do re-zero

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



:STATus:OPERation:INSTrument:ISUMmary1:BIT10:CALibrating?Keep polling while bit 1 (zeroing) is set(CONC1)

:STATus:OPERation:INSTrument:ISUMmary2:BIT10:CALibrating?Keep polling while bit 1 (zeroing) is set(CONC2)



:SENSe:DATA? Retrieve Zero Readings and SDEVs:MEMory:DATA?ZDRift Retrieve Zero Drifts:SENSe:CORRection:ZERO:DTOLerance 2

Allow 2% tolerance for zero drift:SENSe:CORRection:STATe[:ON]

start applying new m, b:SENSe:CONC:CSET? Retrieve m,b for this range of this analyzer

5.3.2 Bag Read ProcedureThe following command sequence illustrates a possible command sequence for bag reads:

SCPI Command Notes

:SYSTem:LOCK:REQuest?Assert host control of bench if 1 is returned

:INSTrument:DEFine:GROUp “Bag_Analyzers”,"CONC1", “CONC2",”CONC3", “CONC4" Sets up the group ”Bag_Analyzers to use

four concentrations:INSTrument:SELect “Bag_Analyzers”:CONTrol:EBENch:CLEan:DURation 60

Set a gas line “cleanup” for 60 seconds:CONTrol:EBENch:CLEan[:INIT]

Start CLEan procedure:SENSE:FUNCtion:CONCurrent ON:SENSe:FUNCtion “CONC1", ”CONC1:SDEV","CONC2","CONC2:SDEV",“CONC3",”CONC3:SDEV", “CONC4", ”CONC4:SDEV":TRIGger:SEQ1:SOURce TIMer:TRIGger:SEQ1:TIMer 0.1

“.1" means .1 seconds:SENSe:STABilized:STATE ON

Use Stabilized mode

Start “Sniff”:SENSe:CONC:RANGe:AUTO ON Auto range to find correct range

Host command to sampling system that selects bag:ROUTe:SAMPle BAG Cold_Transient_Sample:INITiate:IMMediate:SEQuence1:STATus:OPERation:BIT9?

Keep polling while bit 5 (sampling) is set:STATus:QUEStionable:BIT9?

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



0 = successful bag sample:SENSe:DATA? Retrieve four Sniff concentrations:SENSe:CONC:RANGe:AUTO OFF

Leave in selected range:SENSe:CONC:RANGe:FIXed?

Retrieve range numbers (n,n,n,n):ROUTe:SAMPle NONE Turn off gas flow

Perform ZERO/SPAN/ZERO PROCEDURE - See Section 5.3.1Host command to sampling system that selects bag

:ROUTe:SAMPle BAG Cold_Transient_Sample:INITiate:IMMediate:SEQuence1:STATus:OPERation:BIT9?


0 = successful bag sample:SENSe:DATA? Retrieve the four Sample Bag concentrations and

SDEVs

Host command to sampling system that selects bag:INITiate:IMMediate:SEQuence1:STATus:OPERation:BIT9?


0 = successful bag sample:SENSe:DATA? Retrieve the four Ambient Bag concentrations and

SDEV s:ROUTe:SAMPle NONE Turn off gas flow

Perform Z/S Drift check procedure - similar to section 5.3.1:SYSTem:LOCK:RELease

Release control of bench

5.3.3 Start of Diesel Test ProcedureThe following command sequence illustrates a possible command sequence for starting adiesel test:

SCPI Command NotesSetup Phase

:SYSTem:LOCK:REQuest?Assert host control of bench

:INSTrument:DEFine:GROup “All_Bag_Analyzers”,"CONC1", “CONC2",”CONC3", CONC4" Sets up the groups to use:INSTrument:SELect “All_Bag_Analyzers”:CONTrol:EBENch:CLEan:DURation 60

Do a gas line “cleanup” for 60 seconds:CONTrol:EBENch:CLEan[:INIT]

Do a gas line “cleanup” for 60 seconds:SENSe:FUNCtion:CONCurrent ON

Applies to selected analyzers:SENSe:FUNCtion “CONC1", ”CONC1:SDEV","CONC2","CONC2:SDEV",

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



“CONC3",”CONC3:SDEV", “CONC4", ”CONC4:SDEV"Applies to selected analyzers

:SENSe:STABilization:STATE ONApplies to selected analyzers

:SENSe:STABilization:TIME1 60,50,45,55Stabilization rise time

:SENSe:STABilization:TIME2 15,15,15,15Stabilization evaluation period

:SENSe:STABilization:TIME3 5,5,5,5Stabilization averaging period

:SENSe:STABilization:TIME4 120,120,120,120Stabilization maximum duration

:SENSe:STABilization:TOLerance 4,4,4,4Stabilization tolerance in %

:INSTrument:DEFine:GROUp“Bag_With_Out_Fid”,"CONC2","CONC3","CONC4":INSTrument:SELect “Bag_With_Out_Fid”:SENSE:FUNCtion:CONCurrent ON

Applies to selected analyzers:SENSe:FUNCtion"CONC2","CONC2:SDEV",“CONC3",”CONC3:SDEV","CONC4","CONC4:SDEV"

Applies to selected analyzers:SENSe:STABilization:STATE ON

Applies to selected analyzers:SENSe:STABilization:TIME1 50,45,55

Stabilization rise time:SENSe:STABilization:TIME2 15,15,15

Stabilization evaluation period:SENSe:STABilization:TIME3 5,5,5

Stabilization averaging period:SENSe:STABilization:TIME4 120,120,120

Stabilization maximum duration:SENSe:STABilization:TOLerance 4,4,4

Stabilization tolerance in %:INSTrument:DEFine:GROUp “Just_Heated Fid”,"CONC1":INSTrument:SELect “Just_Heated Fid”:SENSe:AVERage1:COUNT 10:SENSe:AVERage1:TCONtrol MOVing:SENSe:AVERage1:TYPE SCALar:SENSe:AVERage1:STATe ON:SENSe:FUNCtion:CONCurrent ON:SENSe:FUNCtion “CONC1 ON AVERage1",”CONC1:SDEV ON AVERage1":SENSe:STABilization:STATe ON:SENSe:STABilization:TIME1 60

Stabilization rise time:SENSe:STABilization:TIME2 15

Stabilization evaluation period:SENSe:STABilization:TIME3 5

Stabilization averaging period:SENSe:STABilization:TIME4 120

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Stabilization maximum duration:SENSe:STABilization:TOLerance 4

Stabilization tolerance in %:TRIGger:SEQ1:SOURce TIMer

Set up 10 Hz Sampling:TRIGger:SEQ1:TIMer 0.1

Set up integration rate:TRIGger:SEQ2:LINK “TRIGger:SEQence1"

Seq 2 slaved to Seq1:TRIGger:SEQ2:ECOunt 10

Seqence 2 once per second:SYSTem:COMMunicate:SOCKet1:ADDRess ”123.456.789.1"

Separate Data feed:SYSTem:COMMunicate:SOCKet1:PORT 701

to the host:SYSTem:COMMunicate:SOCKet1:TYPE TCP

A TCP Socket:SYSTem:COMMunicate:SOCKet1:FEED:OCON “TRIG:SEQ1"

Collect 10/sec:SYSTem:COMMunicate:SOCKet1:FEED:SCON ”TRIG:SEQ2"

Send once/sec:SYSTem:COMMunicate:SOCKet1:CONNect

Pretest function:INSTrument:SELect “Just_Heated_Fid”:SENSe:CONCentration:RANGe:FIXed n

Alternate form for 1 analyzer

Perform ZERO/SPAN/ZERO PROCEDURE - See Section 5.3.1:SENSe:STABilization:STATe OFF

For command channel “reads”:SENSe:FUNCtion “TIMer:COUNt”, “CONC1:TALign”, “TEMP1":SYSTem:COMMunicate:SOCKet1:FEED ”TIMer:COUNt", “CONC1:TAL”,“TEMP1" For socket feed:ROUTe:SAMPle DILute

Phase 1:INITiate:CONTinuous ON

Start socket feed

drive phase 1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5.4 CALibration Subsystem (Bench Commands)KEYWORD PARAMETER FORM NOTES:CALibration :LINearize | :ACCept [event] | :ACQuire [event] | :AUTO ONCE [event] | :CALCulate AUTO | POLYnomial<n> | | SRATional<n> [event] | :CURve | | [:TYPE] POLYnomial<n> | | | SRATional<n>, <numeric_value>{,<numeric_value>} | | :ZFORce <Boolean> | :VERify | | :ACQuire [event] | | :TOLerance <numeric_value> | | :TYPE CCURve | NCURve

5.4.1 :LINearizeCALibration:LINearize

The LINearize subsystem is used to produce a calibration curve used to linearize a non-linearinstrument. An instance of this subsystem exists for each range in an instrument. The datadefined and queried and the events will only be performed on the currently selected rangeand instrument.

5.4.1.1 :ACCeptCALibration:LINearize:ACCept

ACCept causes an already-calculated or supplied set of coefficients to be placed into regularuse by an instrument. This consists of replacing the “current” values with the “new” values.The current values can be obtained by querying :SENSe:CONCentration:RANGe:LSET?.

5.4.2 :ACQuireCALibration:LINearize:ACQuire

ACQuire causes the automatic collection of linearization data POINts for the currentlyselected range of the currently selected analyzer to begin. Results are placed in a predefinedtable as they are collected. This procedure stores the expected gas concentration, causes gasflow for the defined cutPOINts, waits for a stabilized reading of each one, and records themeasured values. :SENSe:STABilize:STATe must be ON when this command is issued.Gases are selected for the duration of the procedure.

5.4.2.1 :AUTO ONCECALibration:LINearize:AUTO

This command shall perform linearization based on a vendor defined procedure, including:CALibrate:LINearize:ACQuire and possibly other procedures, for example:SENSe:CORRection:ZERO and :SPOint. :SENSe:STABilize:STATe must be ON when thiscommand is issued. Gases are selected for the duration of the procedure. This command is

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



provided to allow the instrument to perform an automated linearization procedure accordingto the manufacturer’s recommended practice.

5.4.2.2 :CALCulate AUTO|POLYnomial<n>|SRATional<n>CALibration:LINearize:CALCulate

Using the results data stored in a predefined linearization table, calculate a linearizationcurve. The results are placed in that table. A curve fit of type AUTO allows the device tocalculate the curve fit according to the manufacturer’s recommended practice. APOLYnomial<n> parameter shall limit the calculation to the specified polynomial curvetype. A SRATional<n> parameter shall limit the linearization to the specified simple rationalcurve fit. The <n> designates the order of the curve. A curve fit can automatically be forcedthrough the origin, if :CALibration:LINearize:CURVe:ZFORce has been turned on. Theresults can be stored in the instrument at a later time (see ACCept). An example of thepredefined table follows:

LSI01R01

CPOint (%FS) EXPected RAW CCURve NCURve

6.7 10000 464646 10015 10001

20.0 30000 484848 30109 30000

33.3 50000 515151 49905 49999

46.7 70000 525252 71004 70001

60 90000 555555 89950 90005

73.3 110000 565656 111070 110100

86.7 130000 575859 129051 129999

100 150000 590101 150031 149000

5.4.2.3 :CURVeCALibration:LINearize:CURVe

This node controls analyzer curve fitting.

5.4.2.3.1 [:TYPE] POLYnomial<n> | SRATional<n>, <numeric_value>{,<numeric_value>}CALibration:LINearize:CURVe[:TYPE]

[:TYPE] sets or retrieves the information used to determine a calibration curve.

The first parameter is the curve type, which consists of either POLYnomial for a polynomialcurve fit or SRATional for a simple rational polynomial curve fit, followed by a positiveinteger <n>, which is the curve order.

The additional parameters are the curve coefficients. These are listed starting with the 0thorder term. Note that the number of coefficients depends on the order of the curve - there areexactly n+1 coefficients for a curve of order n. For example:

:CALibration:LINearize:CURVe:TYPEPOLY3,-0.117,-7.43,1.02,-0.034

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



defines a calibration curve of type 3rd order polynomial and the four coefficients used.

As a query, TYPE returns latest new pending curve fit type and calculated curve coefficients.

If, as in the above example,

f(x) = − 0.117 − 7.43∗x + 1.02∗x2 − 0.034∗x3

results from the curve fit, the returned curve values shall be:POLY3,-0.117,-7.43,1.02,-0.034

A third order simple rational polynomial

f(x) = x

0.81 − 2.0∗x + 1.17∗x2 + 0.02∗x3

shall be represented by the parametersSRAT3,0.81,-2.0,1.17,0.02

5.4.2.3.2 :ZFORce <Boolean>CALibration:LINearize:CURVe:ZFORce

The setting of ZFORce (Zero FORce) determines whether or not a newly calculated curvewill be fit such that the scalar polynomial term is 0. This affects the:CALibration:LINearize:CALCulate command.

At *RST, ZFORce is not changed.

5.4.2.4 :VERifyCALibration:LINearize:VERify

VERify causes the instrument to check the validity of a set of linearization coefficients bychecking the difference from the concentration measured with the curve to the expectedconcentration of the verification gas.

This command is an event, and therefore has no *RST value associated with it.

5.4.2.4.1 :ACQuireCALibration:LINearize:VERify:ACQuire

ACQuire causes the flow and stabilization of a verification gas to occur. First, verificationgas flow is enabled, next a stabilized reading is taken, and finally the verification gas flow isdisabled. The concentration determined from this procedure is compared against a knownconcentration stored in a designated table. If the difference between the expectedconcentration of the verification gas and the concentration measured using the curvecoefficients is greater than the tolerance value set by :CALibration:LINearize:VERify:TOL,then the appropriate questionable status bit is set.


5.4.2.4.2 :TOLerance <numeric_value>CALibration:LINearize:VERify:TOLerance

TOLerance sets the allowable tolerance between the expected concentration of theverification gas and the concentration measured using the curve coefficients in % of fullscale of the active range of the selected analyzer.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



At *RST, TOLerance is not changed.

5.4.2.4.3 :TYPECALibration:LINearize:VERify:TYPE

TYPE selects the linearization coefficients to be verified. Possible types are:

CCURve - The curve coefficients currently in effect

NCURve - A newly calculated or downloaded set of coefficients that are not yetin use.

At *RST, TYPE is set to CCURve.

5.5 DIAGnostic Subsystem (Bench Commands)KEYWORD PARAMETER FORM NOTES:DIAGnostic :HUP | :ACQuire [no query] | :CALCulate [no query] :LEAK | :ACQuire [no query] | :CALCulate [no query] :NEFFiciency | :ACQuire [no query] | :CALCulate [no query]

5.5.1 :HUPDIAGnostic:HUP

Commands to perform a diesel HC HangUP check.

5.5.1.1 :ACQuireDIAGnostic:HUP:ACQuire

This procedure performs the procedure found the 1996 Code of Federal Regulations,86.1340-90 Exhaust Sample Analysis, Paragraph (e) (3); it first takes a zero direct reading;,then a zero overflow reading. This command has no query form.


5.5.1.2 :CALCulateDIAGnostic:HUP:CALCulate

Compare the direct zero value with the overflow zero value. These values and theirdifference are stored in memory table HUPResults. The difference is compared with thevalue in memory table HUPTolerance. Error bit 4 of:STATus:QUEStionable:INSTrument:ISUMmary5:BIT10 is set if the value of the differenceis outside of the tolerance values stored in HUPTolerance. These tolerance values are upperand lower tolerance in ppm.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



5.5.2 :LEAKDIAGnostic:LEAK

Commands to help perform a bench leak check.

5.5.2.1 :ACQuireDIAGnostic:LEAK:ACQuire

Initiate a bench leak check. This causes the bench perform a device-dependent leak checkprocedure. This command has no query form.


5.5.2.2 :CALCulateDIAGnostic:LEAK:CALCulate

This command performs a device-dependent leak check calculation to indicate success orfailure of the leak check.

Error bit 4 of :STATus:QUEStionable:INSTrument:ISUMmary5:BIT10 is set if any of thecalculated values are outside of these tolerance values. The lower and upper tolerance valuesare stored in table LTOLerance; the value which is compared against these tolerances isstored in table LRESults. This command has no query form.


5.5.3 :NEFFiciencyDIAGnostic:NEFFiciency

Commands to initiate the NOx efficiency diagnostic procedure and its calculations.

5.5.3.1 :ACQuireDIAGnostic:NEFFiciency:ACQuire

Initiate the NOx efficiency procedure. This is a six-step test and is performed according tothe EPA’s 1996 code of Federal Regulations, section 86.123-78.


5.5.3.2 :CALCulate:DIAGnostic:NEFFiciency:CALCulate

Calculate the NOx efficiency results, per the EPA’s 1996 code of Federal Regulations,section 86.123-78. This command has no query form. The results of the calculations areplaced in the memory table NEResults. Error bit 4 of:STATus:QUEStionable:INSTrument:ISUMmary5:BIT10 is set if any of the calculatedvalues are outside of the tolerance values resident in the memory table NETolerance.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



6 Emission Test CellAn Emission Test Cell consists of one or more computers and a set of instruments that areused to perform emissions testing. The instruments which are included in an ETCELL mayinclude Emission Benches, Dynamometers, Sampling Systems, and other emissionsmeasurement or other devices. In order to standardize the interfaces within the cell it isdesirable that all instrument implement a core set of commands. These commands aredescribed in this chapter.

All SCPI compliant Emission Test Cells shall implement the commands listed in Syntax &Style sections 4.2.

6.1 Base FunctionalityThis section describes the base functionality for an Emission Test Cell.

The <bf_keyword> for an Emissions Test Cell is ETCELL.

6.1.1 Base Measurement InstructionsThe base functionality for an ETCELL contains no commands from the MEASure subsystem.

6.1.2 Base Device-oriented FunctionsETCELL compliant instruments shall include SYSTem commands, which set up and causecommunication between instruments and the site computer and the set up and transfer ofdata from instruments.

6.1.2.1 SYSTem subsystemThe SYSTem subsystem of an Emission Test Cell shall include the following commands.

KEYWORD PARAMETER FORM SCPI ReferenceSYSTem V2-21 :CAPability? V2-21.3 :COMMunicate V2-21.4 | :SOCKet<n> V2-21.4.4 | | :ADDRess <string>(Ipaddress | Host Name) V2-21.4.4.1 | | :CONNect V2-21.4.4.2 | | :DISConnect V2-21.4.4.3 | | :FEED <data_handle>{,<data_handle>} V2-21.4.4.4 | | | :OCONdition<event_handle> V2-21.4.4.4.1 | | | :SCONdition <event_handle> V2-21.4.4.4.2 | | :LISTen V2-21.4.4.5 | | :PORT <NRf>|<non-decimal numeric> V2-21.4.4.6 | | :TYPE TCP | UDP V2-21.4.4.7 :DATE <year>,<month>,<day> V2-21.7 :ERRor V2-21.8 | :ALL? V2-21.8.4 | :CODE? V2-21.8.5 | | :ALL? V2-21.8.5.1 | | :[NEXT]? V2-21.8.5.2

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Emission Test Cell 6-1

KEYWORD PARAMETER FORM SCPI Reference | :ENABle V2-21.8.7 | | :ADD <numeric_list> V2-21.8.7.1 | | :DELete <numeric_list> V2-21.8.7.2 | | [:LIST] <numeric_list> V2-21.8.7.3 | [:NEXT]? V2-21.8.8 :LOCK V2-21.14 | :OWNer? V2-21.14.1 | :RELease V2-21.14.2 | :REQuest? V2-21.14.3 :TIME V2-21.19 | :TIMer V2-21.19.1 | | :COUNt <numeric_value> V2-21.19.1.1 | | [:STATe] <Boolean> V2-21.19.1.2 :VERSion? V2-21.21

6.1.2.2 TRIGger subsystemTRIGger commands for ETCELLs are as follows:

KEYWORD PARAMETER FORM:TRIGger V2-24.8 [:SEQuence] V2-24.8.1 | :ECOunt <numeric_value> V2-24.8.1.7 | :LINK <event_handle> V2-24.8.1.13 | :SOURce TIMer V2-24.8.1.17 | :TIMer <numeric_value> V2-24.8.1.18

6.2 Additional FunctionalityNot applicable.

6.3 Programming ExamplesThis section discusses how a user might use commands in an Emission Test Cell

6.3.1 Instrument Capability and Version Example:SYSTem:CAPability? A chassis dynamometer for an emissions test cell returns:

(ETCELL & CDYNO)<NL>

:SYSTem:VERSion? A chassis dynamometer might return: 1999.0<NL>

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-2 Emission Test Cell

6.3.2 Command Channel ExampleAssume the Site computer wants to configure an Emission Test Cell instrument to perform areading and return the data. The following commands might be issued to the instrument toperform this reading.

Commands

SENSE:FUNCtion:CONCurrent ON Configure to sense data frommore than one analyzer.

SENSe:FUNCtion “CONC1:TAL”,"CONC2:TAL", “CONC3:TAL”,"CONC4:TAL"Select the required data.

SENSe:CONCentration:RANGe:AUTO ONSet instrument to automatic range mode.

INITiate Start the measurementSENSe:DATA? Return data values for CONC1:TAL etc

By default, the result is returned in ASCII. The FORMat subsystem can be used to configurethe instrument to send the data in various binary formats.

6.3.3 Two Channel ExampleThis example illustrates how to configure the instrument to send continuously acquired dataon a separate channel from the SCPI command channel. This allows results to becontinuously streamed back from the instrument to the controller.

Assume the controller wants the instrument to take data every 0.1 second, average the dataover one second, buffer it then feed it out a second channel every 5 seconds.

Setup Sense functions to get modal data averaged over a secondSENSe:FUNCtion:CONCurrent ONSENSe:FUNCtion “CONC1 ON AVERage”,"CONC2 ON AVERage",“CONC3 ON AVERage”,"CONC4 ON AVERage"Setup averaging parameter for the modal dataSENSe:AVERage:COUNt 10SENSe:AVERage:TCONtrol REPeatSENSe:AVERage:TYPE SCALARTurn the Averaging ON inside of the Sense blockSENSe:AVERage:STATe ONTrigger Sequence will setup rates to sense the modal dataTRIGger:SEQuence1:SOURce TIMerTRIGger:SEQuence1:TIMer 0.1 set sampling rate of 0.1secTRIGger:SEQuence2:LINK “TRIGger:SEQuence1"TRIGger:SEQuence2:ECOunt 10 set integration rate

10 times 0.1=1secTRIGger:SEQuence3:LINK ”TRIGger:SEQuence1"TRIGger:SEQuence3:ECOunt 50 set transmission rate

50 times 0.1=5secSetup and connect on the communication socketSYStem:COMMunicate:SOCKet:ADDRess “123.45.67.89"SYStem:COMMunicate:SOCKet:PORT 701SYStem:COMMunicate:SOCKet:TYPE TCP

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Emission Test Cell 6-3

SYStem:COMMunicate:SOCKet:CONNectSetup the Socket feed to data channelSYStem:COMMunicate:SOCKet:FEED ”SYSTem:TIME:TEST","CONC1:TALON AVERage".........SYStem:COMMunicate:SOCKet:OCONdition “TRIGger:SEQuence2"

collects data into the socket every 1 secSYStem:COMMunicate:SOCKet:SCONdition ”TRIGger:SEQuence3"

sends data out the socket every 5 sec

Note: you can feed the data from two logical instruments into the same socket. Here forexample, RT analyzer data and RE analyzer data can both be sent on SOCKet.

Initiate all sequences for continuous sampling:INITiate:CONtinuous ONThe data is sent every 5 seconds on the data channel.

6.3.4 Returning Data using a Table ExampleAssuming that the table MYTABLE has already been defined with items FORCe,SPEed,and TIME:

MEMory:TABLe:SELect MYTABLE Select the table containingthe data.

MEMory:DATA? SPEed Retrieve the speed data from the table.

6.3.5 Time ExampleStandard SCPI time commands shall be used to synchronize each of the instrument clocks tothe Site computer clock. This synchronization should be done during a period in the testwhen the instruments are in a quiescent state.

SYSTem:TIME 07,45,00.010

This command is used to control internal timer/counters in Emission Test Cell instruments.The Timer is used to timestamp data returned by Emission Test Cell instruments and to tracktime during an emission test. Set or reset the instrument timer to 0 at the beginning of a test.

SYSTem:TIME:TIMer:COUNt 0Start the instrument timer.SYSTem:TIME:TIMer:STATe ONQuery the value of the instrument timer.SYSTem:TIME:TIMer:COUNt?

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


6-4 Emission Test Cell

7 Power SuppliesA power supply is a basic sourcing instrument. It typically supplies a constant voltage orcurrent at significant power levels to energize an electrical circuit. Because a power supply isprimarily a source, the SOURce root node is optional.


Figure 7-1 shows an instrument model for a power supply. It is derived from CommandReference, Chapter 2. It is essentially the same as Figure 2-1 in Command Reference withvarious parts shaded or dashed. The shaded boxes are not described here. While a powersupply may have a MEMory subsystem, its operation is not described. The TRIGger block isdashed because not all power supplies have that functionality. While a power supplycontains FORMat and Signal Routing functionality, their behaviors generally follow the*RST setting. These blocks are not described so they are dashed.

Figure 7-2 shows how the “Signal Generation” block in Figure 7-1 is expanded in a powersupply. It is the same as Figure 2-5 in Command Reference with some shaded and dashedboxes. The MEMory block is shaded because while a power supply may contain thisfunction, this chapter does not address it. The CALCulate block is dashed and its behaviornot described. It behaves according to the *RST value.

Figure 7-1 Simplified Model for a Power Supply

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Power Supplies 7-1

7.1 Base FunctionalityThis section describes the base functionality for power supplies.

The <bf_keyword> for a DC power supply is DCPSUPPLY.

7.1.1 Base Measurement InstructionsThe base functionality for a power supply contains no measurement instructions.


7.1.2.1 OutputsA power supply shall have at least one output which can be turned on and off. This OUTPutsubsystem command shall be implemented.

KEYWORD PARAMETER FORM SCPI ReferenceOUTPut Vol 2-15 [:STATe] <Boolean> Vol 2-15.12

As stated in Command Reference, *RST sets the output state to off.

7.1.2.2 SOURce subsystemA power supply shall provide control of voltage and current by implementing thesecommands.


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-2 Power Supplies

KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :CURRent Vol 2-19.5 [:LEVel] Vol 2-19.5.4 [:IMMediate] Vol 2-19.5.4.1 [:AMPLitude] <numeric_value> Vol 2-19.5.4.1.1 :VOLTage Vol 2-19.23 [:LEVel] Vol 2-19.23.4 [:IMMediate] Vol 2-19.23.4.1 [:AMPLitude] <numeric_value> Vol 2-19.23.4.1.1

A power supply can operate in one of two modes: voltage source or current source. Themode of operation depends on the load connected to it. When a power supply is operating asa voltage source, the :VOLTage command sets the output voltage and the :CURRentcommand sets the current limit. When a power supply is operating as a current source, the:VOLTage command sets the voltage limit and the :CURRent command sets the outputcurrent.

If the :CURRent and :VOLTage commmands are implemented as overlapped commands, theassociated Pending-Operation flags shall be reported in the No-Operation-Pending flag. Theoperation started by the :CURRent command completes when the output current has reachedthe programmed current value or when the voltage limit has been reached. Likewise, theoperation started by the :VOLTage command completes when the output voltage hasreached the programmed voltage value or the current limit has been reached.

At *RST a power supply is required to set the voltage and current to “safe” conditions. Thisis generally achieved by setting them to their values closest to zero.

7.1.3 Base Status ReportingAll SCPI power supplies shall implement the status reporting structure described in Syntax& Style, Status Reporting. Command Reference, STATus Subsystem defines the commandswhich shall be used to control the status reporting structure.

7.1.3.1 QUEStionableFor a power supply, the bits of interest in the QUEStionable status structure are VOLTageand CURRent. When a power supply is operating as a voltage source, bit 1 (CURRent) shallbe set. When a power supply is operating as a current source, bit 0 (VOLTage) shall be set.When the output is unregulated, both bits shall be set (for example, while the output ischanging to a new programmed value).

7.1.3.2 OPERationThe base functionality of a power supply adds no requirements for this register.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Power Supplies 7-3

7.2 Additional FunctionalityThis section describes additional functionality for power supplies.

7.2.1 Measurement capabilityWhile the basic function of a power supply is to source voltage and current, this additionalfunctionality provides for the measurement of the actual voltage and current delivered to theload.

The <af_keyword> for measurement capability is MEASURE.

7.2.1.1 MEASURE Measurement InstructionsThe following MEASure:<function>? queries shall be implemented.

KEYWORD PARAMETER FORMMEASure [:SCALar] :VOLTage[:DC]? [<expected_value>[,<resolution>]] :CURRent[:DC]? [<expected_value>[,<resolution>]]

These queries read the actual voltage and or current at the power supply’s output. Theycontrol a sensing function that is completely separate from the power supply itself.Executing these queries shall have no effect on the power supply’s settings. Thisfunctionality further require no additional Measurement Instruction commands and has nointeraction with the power supply’s triggering system, if implemented.

The <expected_value> and <resolution> parameters are included solely for compatibilitywith the Command Reference. While parameters shall be accepted for syntacticcompatibility, they are not required by MEASURE and may be ignored by the device.

7.2.1.2 MEASURE Device-oriented FunctionsMEASURE adds no device-oriented functions.

7.2.1.3 MEASURE Status ReportingMEASURE adds no Status Reporting requirements.

7.2.2 Multiple suppliesA power supply may contain multiple independent power supplies.

The <af_keyword> for multiple supplies is MULTIPLE.

7.2.2.1 MULTIPLE Measurement InstructionsMULTIPLE adds no measurement instructions.

7.2.2.2 MULTIPLE Device-oriented FunctionsAn instrument which contains multiple power supplies shall use the INSTrument:NSELectand INSTrument[:SELect] commands to switch among them.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-4 Power Supplies

KEYWORD PARAMETER FORM SCPI Reference:INSTrument Vol 2-12 :NSELect <numeric_value> Vol 2-12.5 [:SELect] <identifier> Vol 2-12.6

Valid values of the <numeric_value> shall range from 1 to the number of power supplies.

7.2.2.3 MULTIPLE Status ReportingSection 9.5 of Syntax & Style describes the implications of multiple instruments on thestatus reporting model. The INSTrument Summary bits in the QUEStionable and OPERationregisters shall be used to summarize the status from all logical instruments. The followingSTATus subsystem commands are required.

KEYWORD PARAMETER FORM SCPI ReferenceSTATus Vol 2-20 :OPERation Vol 2-20.1 :INSTrument :CONDition? Vol 2-20.1.2 :ENABle <NRf> Vol 2-20.1.3 [:EVENt]? Vol 2-20.1.4 :ISUMmary<n> :CONDition? Vol 2-20.1.2 :ENABle <NRf> Vol 2-20.1.3 [:EVENt]? Vol 2-20.1.4 :QUEStionable Vol 2-20.3 :INSTrument :CONDition? Vol 2-20.3.2 :ENABle <NRf> Vol 2-20.3.3 [:EVENt]? Vol 2-20.3.4 :ISUMmary<n> :CONDition? Vol 2-20.1.2 :ENABle <NRf> Vol 2-20.1.3 [:EVENt]? Vol 2-20.1.4

7.2.3 Triggering CapabilitySome power supplies are able to change their voltage and current based on the arrival of acommand or external signal. Trigger commands, used in conjunction with source commands,control when the output changes.

The <af_keyword> for trigger capability is TRIGGER.

7.2.3.1 TRIGGER Measurement InstructionsTRIGGER adds no measurement instructions.

7.2.3.2 TRIGGER Device-oriented FunctionsPower supplies which have TRIGGER additional functionality shall implement thefollowing SOURce and TRIGger commands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Power Supplies 7-5

KEYWORD PARAMETER FORM SCPI ReferenceEditINITiate Vol 2-24.7

:CONTinuous <Boolean> Vol 2-24.7.1 [:IMMediate] Vol 2-24.7.2

12-4-94 letter [:ALL] Vol 2-24.7.2.1[SOURce] Vol 2-19 :CURRent Vol 2-19.5 [:LEVel] Vol 2-19.5.4 :TRIGgered Vol 2-19.5.4.2 [:AMPLitude] <numeric_value> Vol 2-19.5.4.2.1 :VOLTage Vol 2-19.23 [:LEVel] Vol 2-19.23.4 :TRIGgered Vol 2-19.23.4.2 [:AMPLitude] <numeric_value> Vol 2-19.23.4.2.1TRIGger Vol 2-24.8 [:SEQuence] Vol 2-24.8.1 [:IMMediate] Vol 2-24.8.1.11 :SOURce {BUS | EXTernal | ...} Vol 2-24.8.1.17

The trigger commands associated with the TRIGGER additional functionality shall have nointeraction with the MEASURE additional functionality.

Requiring BUS as a parameter to TRIGger:SOURce has the side effect of requiring DT1capability in an IEEE 488.1 device. It also means the power supply implements the *TRGcommon command.

A VXIbus device with a trigger function is required to implement the Trigger command.When TRIGger:SOURce is set to BUS, a VXIbus power supply uses the Trigger commandas the TRIGger source.

When TRIGger:SOURce is set to IMMediate, an INITiate commmand immediately transfersthe TRIGgered[:AMPLitude] value to [:IMMediate][:AMPLitude].

7.2.3.3 TRIGGER Status ReportingBit 5 (Waiting for TRIG) in the OPERation Status Register shall be used to indicate thestatus of the trigger model.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-6 Power Supplies

7.3 Programming ExamplesThis section discusses how a user might program a power supply for certain applications.

7.3.1 SimpleTo use a power supply as a constant voltage supply the programmer could send:

*RSTSOURce:VOLTage:LEVel:IMMediate:AMPLitude 5VSOURce:CURRent:LEVel:IMMediate:AMPLitude MAXimumOUTPut:STATe ON

or

*RST;VOLT 5V;CURR MAX;OUTP ON

7.3.2 Time CriticalWith a power supply containing the TRIGGER additional functionality, an application couldchange the voltage at a specific time by sending:

*RSTSOURce:CURRent:LEVel:IMMediate:AMPLitude MAXimumOUTPut:STATe ONTRIGger:SEQuence:SOURce EXTernalSOURce:VOLTage:LEVel:IMMediate:AMPLitude 7.2VSOURce:VOLTage:LEVel:TRIGgered:AMPLitude 9.6VINITiate:IMMediate

or

*RST;CURR MAX;OUTP ON;TRIG:SOUR EXTVOLT:IMM 7.2V;TRIG 9.6VINIT

The power supply sources 7.2 volts immediately and waits for a signal on the externaltrigger. When the trigger event occurs, the output voltage changes to 9.6 volts.

7.3.3 Level VerificationWith a power supply containing the MEASURE additional functionality, an applicationcould verify the level by sending:

*RSTOUTPut:STATe ONSOURce:CURRent:LEVel:IMMediate:AMPLitude MAXimumSOURce:VOLTage:LEVel:IMMediate:AMPLitude 7.2V*OPC?

or

*RSTOUTP ON;CURR MAX;VOLT 7.2;*OPC?

The application reads the ‘1’ returned by the supply when it completes the operation ofchanging the level.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Power Supplies 7-7

Now the actual voltage and current supplied to the load are measured with:

:MEASure:VOLTage:DC?;:MEASure:CURRent:DC?

or

MEAS:VOLT?;CURR?

The supply returns the measured voltage and current, which the application can thencompare with expected results.

7.3.4 Multiple SuppliesA device containing two power supplies sets supply #1 to 5 Volts and supply #2 to -5 voltswith the following commands:

*RSTINSTrument:NSELect 1SOURce:VOLTage:LEVel:IMMediate:AMPLitude 5V OUTPut:STATe ONINSTrument:NSELect 2SOURce:VOLTage:LEVel:IMMediate:AMPLitude -5VOUTPut:STATe ON

or

*RSTINST:NSEL 1;VOLT 5;OUTP ONINST:NSEL 2;VOLT -5;OUTP ON

To check that both supplies are acting as voltage sources and are not current limited, theQUEStionable Condition Register is queried using :

STATus:QUEStionable:CONDition?

If bit 0 is 0 and bit 1 is 1, both supplies are in the voltage source mode.

To check each supplies separately, the application subsequently reads the regulation statuswith these commands sent in the same program message:

STATus:QUEStionable:INSTrument:ISUMmary1:CONDition?;:STATus:QUEStionable:INSTrument:ISUMmary2:CONDition?

or

STAT:QUES:INST:ISUM1:COND?;:STAT:QUES:INST:ISUM2:COND?

A possible response would be 2;3 indicating the CURRent bit but not the VOLTage bit hasbeen set on supply #1 (current limited, voltage regulated) and both bits set on supply #2(unregulated).

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


7-8 Power Supplies

8 RF & Microwave SourcesRF sources and microwave sources are basic sourcing instruments. They typically generate asingle sinusoidal signal at one frequency and at constant output level. The frequency istypically in the range from above 10 MHz up to several GHz. Their output impedance isnormally 50 Ohms and matched impedance is assumed. The output level is specified aspower into a matched load rather than as voltage. Signal generators with modulation andsweepers are also covered by this chapter. Their special attributes are described as additionalfunctionalities.

Excluded from this chapter are optical sources, function generators, arbitrary waveformgenerators, pulse generators and data pattern generators.


Figure 8-1 shows an instrument model for RF & microwave sources. It is derived fromCommand Reference, chapter 2. It is essentially the same as Figure 2-1 in CommandReference with various parts shaded or dashed. The bold boxes and lines, solid and dashedare described in this chapter.

The FORMat and ROUTe blocks are shown with dashed lines because many RF &microwave sources use their default settings. *RST sets FORMat[:DATA] to ASCii andROUTe:TERMinals to FRONt. The shaded boxes are not described here.

Figure 8-2 shows how the “Signal Generation” block in Figure 8-1 is expanded in RF &microwave sources. It is the same as Figure 2-5 in Command Reference with some dashedand shaded boxes. The CALCulate block is dashed because after *RST this block has noeffect on the data. This chapter does not describe any CALCulate functions. The MEMoryblock is shaded because while RF & microwave sources may contain this function, thischapter does not address it.

Figure 8-1 Simplified Model of an RF & Microwave Source

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


RF & Microwave Sources 8-1

8.1 Base FunctionalityThis section describes the base functionality for RF & microwave signal sources.

The <bf_keyword> for RF & microwave sources is RFSOURCE.

8.1.1 Base Measurement InstructionsThe base functionality for RF & microwave sources contains no measurement instructions.


8.1.2.1 SOURce subsystemRF & microwave sources shall provide control of its output frequency and level byimplementing these commands.

KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :FREQuency Vol 2-19.9 [:CW|:FIXed] <numeric_value> Vol 2-19.9.2 :POWer Vol 2-19.15 :ALC Vol 2-19.15.2 [:STATe] <Boolean> Vol 2-19.15.2.1 [:LEVel] Vol 2-19.15.4 [:IMMediate] Vol 2-19.15.4.1 [:AMPLitude] <numeric_value> Vol 2-19.15.4.1.1

If the :FREQuency and :POWer commands are implemented as overlapped commands, theassociated Pending-Operation flags shall be reported in the No-Operation-Pending flag. Theoperation started by the :FREQuency command completes when the frequency has reached


1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


8-2 RF & Microwave Sources

the programmed frequency value. Likewise, the operation started by the :POWer commandcompletes when the output level has reached the programmed power value.

At *RST a RF & microwave source should be set to a “safe” condition. This is generallyachieved by setting the amplitude to its minimum value in conjunction with *RST settingOUTPut:STATe to OFF.

8.1.2.2 OUTPut SubsystemRF & microwave sources that have at least one output which can be turned on and off andshall implement the following command.

KEYWORD PARAMETER FORM SCPI ReferenceOUTPut Vol 2-15 [:STATe] <Boolean> Vol 2-15.12

As stated in Command Reference, *RST sets the output state to off.

8.1.2.3 UNIT SubsystemRF & microwave sources shall provide control of its UNITs for the output power byimplementing this command.

KEYWORD PARAMETER FORM SCPI ReferenceUNIT Vol 2-25 :POWer W|V|DBM|DB<suffix mult.>W|... Vol 2-25.2

At *RST, this value shall be set to DBM.

8.1.3 Base Status ReportingAll SCPI RF & microwave sources shall implement the status reporting structure describedin Syntax & Style, Status Reporting. Command Reference, STATus Subsystem defines thecommands which shall be used to control the status reporting structure.

8.1.3.1 QUEStionable StatusRF & microwave sources shall set bit 3 (POWer) or bit 5 (FREQuency) in the QUEStionableStatus Register when the RF & microwave source suspects the power or the frequency is ofquestionable accuracy.

8.1.3.2 OPERation StatusThe base functionality of a RF & microwave source adds no requirements to the OPERationStatus register.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.2 Additional functionalityThe basic function of a RF & microwave source is to generate a signal at fixed frequencyand power. Typical signal generators and typical sweepers may include additionalfunctionality as modulation, sweep of frequency or power, marker and trigger function andselection of the reference oscillator. This section describes this additional functionality forRF & microwave sources.

8.2.1 Amplitude Modulation This additional functionality provides amplitude modulation of the RF output signaldelivered to the load either by an internally generated modulation signal or by an externalsignal input.

The <af_keyword> for amplitude modulation is AM.

8.2.1.1 AM Measurement InstructionsAM adds no Measurement Instructions.

8.2.1.2 AM Device Oriented CommandsRF & microwave sources which have the AM additional functionality shall provide controlof amplitude modulation by implementing the following commands.

KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :AM Vol 2-19.2 [:DEPTh] <numeric_value> Vol 2-19.2.2 :EXTernal Vol 2-19.2.3 :COUPling AC|DC|... Vol 2-19.2.3.1 :INTernal Vol 2-19.2.4 :FREQuency <numeric_value> Vol 2-19.2.4.1 :SOURce EXTernal|INTernal Vol 2-19.2.8 :STATe <Boolean> Vol 2-19.2.9

8.2.1.3 AM Status ReportingWhen the RF & microwave source suspects the additional function AM is of questionableaccuracy, bit 7 (MODulation) shall be set in the QUEStionable Status Register.

8.2.2 Frequency Modulation This additional functionality provides frequency modulation of the RF output signaldelivered to the load either by an internally generated modulation signal or by an externalsignal input.

The <af_keyword> for frequency modulation is FM.

8.2.2.1 FM Measurement InstructionsFM adds no Measurement Instructions.

8.2.2.2 FM Device Oriented CommandsRF & microwave sources which have the FM additional functionality shall provide controlof frequency modulation by implementing the following commands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :FM Vol 2-19.7 [:DEViation] <numeric_value> Vol 2-19.7.2 :EXTernal Vol 2-19.7.3 :COUPling AC|DC|... Vol 2-19.7.3.1 :INTernal Vol 2-19.7.4 :FREQuency <numeric_value> Vol 2-19.7.4.1 :SOURce EXTernal|INTernal Vol 2-19.7.8 :STATe <Boolean> Vol 2-19.7.9

8.2.2.3 Status ReportingWhen the RF & microwave source suspects the additional function FM is of questionableaccuracy, bit 7 (MODulation) shall be set in the QUEStionable Status Register.

8.2.3 Pulse Modulation This additional functionality provides pulse modulation of the RF output signal delivered tothe load by an external modulation signal.

The <af_keyword> for pulse modulation is PULM.

8.2.3.1 PULM Measurement InstructionsPULM adds no Measurement Instructions.

8.2.3.2 PULM Device Oriented CommandsRF & microwave sources which have the PULM additional functionality shall providecontrol of pulse modulation by implementing the following commands.

KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :PULM Vol 2-19.16 :POLarity NORMal|INVerted Vol 2-19.16.4 :STATe <Boolean> Vol 2-19.16.6

8.2.3.3 PULM Status ReportingWhen the RF & microwave source suspects the additional functionality PULM is ofquestionable accuracy, bit 7 (MODulation) shall be set in the QUEStionable Status Register.

8.2.4 Analog Frequency SweepingRF & microwave sources may provide control of analog frequency sweep functions.

The <af_keyword> for analog frequency sweeping is FASWEEP.

8.2.4.1 FASWEEP Measurement InstructionsFASWEEP adds no Measurement Instructions.

8.2.4.2 FASWEEP Device Oriented CommandsRF & microwave sources which have the FASWEEP additional functionality shall providecontrol of frequency sweep by implementing the following commands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM SCPI ReferenceINITiate Vol 2-24.7 :CONTinuous <Boolean> Vol 2-24.7.1

Bode [:ALL] Vol 2-24.7.1.1[SOURce] Vol 2-19 :FREQuency Vol 2-19.9 :MODE CW|FIXed|SWEep|... Vol 2-19.9.4 :STARt <numeric_value> Vol 2-19.9.9 :STOP <numeric_value> Vol 2-19.9.10 :CENTer <numeric_value> Vol 2-19.9.1 :SPAN <numeric_value> Vol 2-19.9.8 :SWEep Vol 2-19.21 :TIME <numeric_value> Vol 2-19.21.1 :AUTO <Boolean>|ONCE Vol 2-19.21.1.1

See the beginning of the Command Refernce, SOURce chapter for a description of thecoupling among STARt, STOP, CENTer & SPAN.

Typically a RF & microwave source has just one single SWEEP source for frequency andpower sweep. The setting of sweep parameters are then coupled and identical. If there ismore than one sweep source they can be distinguished by use of a numeric suffix.

When the mode is changed from CW to SWEep, the instrument is not sweeping untilINITiate:CONTinuous is set to ON.

8.2.4.3 FASWEEP Status ReportingIf the additional function Analog Frequency Sweep is implemented and the RF & microwavesource is performing this operation, bit 3 (SWEeping) shall be set in the OPERation StatusRegister.

8.2.5 Stepped Frequency SweepingRF & microwave sources may provide control of stepped frequency sweep functions.

The <af_keyword> for stepped frequency sweeping is FSSWEEP.

8.2.5.1 FSSWEEP Measurement InstructionsFSSWEEP adds no Measurement Instructions.

8.2.5.2 FSSWEEP Device Oriented CommandsRF & microwave sources which have the FSSWEEP additional functionality shall providecontrol of frequency sweep by implementing the following commands.


Bode [:ALL] Vol 2-24.7.1.1[SOURce] Vol 2-19 :FREQuency Vol 2-19.9 :MODE CW|FIXed|SWEep|... Vol 2-19.9.4

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



:STARt <numeric_value> Vol 2-19.9.9 :STOP <numeric_value> Vol 2-19.9.10 :CENTer <numeric_value> Vol 2-19.9.1 :SPAN <numeric_value> Vol 2-19.9.8 :SWEep Vol 2-19.21 :DWELl <numeric_value> Vol 2-19.21.2 :STEP <numeric_value> Vol 2-19.21.7

See the beginning of the Command Reference, SOURce chapter for a description of thecoupling among STARt, STOP, CENTer & SPAN.



8.2.5.3 FSSWEEP Status ReportingIf the additional function Stepped Frequency Sweep is implemented and the RF &microwave source is performing this operation, bit 3 (SWEeping) shall be set in theOPERation Status Register.

8.2.6 Analog Power SweepingRF & microwave sources may provide control of analog power sweep functions.

The <af_keyword> for analog power sweeping is PASWEEP.

8.2.6.1 PASWEEP Measurement InstructionsPASWEEP adds no Measurement Instructions.

8.2.6.2 PASWEEP Device Oriented CommandsRF & microwave sources which have the PASWEEP additional functionality shall providecontrol of analog power sweep by implementing the following commands.


Bode [:ALL] Vol 2-24.7.1.1[SOURce] Vol 2-19 :POWer Vol 2-19.15 :MODE FIXed|SWEep Vol 2-19.15.7 :STARt <numeric value> Vol 2-19.15.13 :STOP <numeric value> Vol 2-19.15.14 :CENTer <numeric value> Vol 2-19.15.3 :SPAN <numeric value> Vol 2-19.15.12 :SWEep Vol 2-19.21 :TIME <numeric value> Vol 2-19.21.1 :AUTO <Boolean>|ONCE Vol 2-19.21.1.1

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26






8.2.6.3 PASWEEP Status ReportingIf the additional function Analog Power Sweep is implemented and the RF & microwavesource is performing this operation, bit 3 (SWEeping) shall be set in the OPERation StatusRegister.

8.2.7 Stepped Power SweepingRF & microwave sources may provide control of stepped power sweep functions.

The <af_keyword> for stepped power sweeping is PSSWEEP.

8.2.7.1 PSSWEEP Measurement InstructionsPSSWEEP adds no Measurement Instructions.

8.2.7.2 PSSWEEP Device Oriented CommandsRF & microwave sources which have the PSSWEEP additional functionality shall providecontrol of stepped power sweep by implementing the following commands.


Bode [:ALL] Vol 2-24.7.1.1[SOURce] Vol 2-19 :POWer Vol 2-19.15 :MODE FIXed|SWEep Vol 2-19.15.7 :STARt <numeric value> Vol 2-19.15.13 :STOP <numeric value> Vol 2-19.15.14 :CENTer <numeric value> Vol 2-19.15.3 :SPAN <numeric value> Vol 2-19.15.12 :SWEep Vol 2-19.21 :DWELl <numeric_value> Vol 2-19.21.2 :STEP <numeric_value> Vol 2-19.21.7



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26




8.2.7.3 PSSWEEP Status ReportingIf the additional function Stepped Power Sweep is implemented and the signal generator isperforming this operation, bit 3 (SWEeping) shall be set in the OPERation Status Register.

8.2.8 Frequency ListRF & microwave sources may provide control of additional frequency sweep functions by afrequency list containing the sequence of frequencies to be stepped through.

The <af_keyword> for frequency lists is FLIST.

8.2.8.1 FLIST Measurement InstructionsFLIST adds no Measurement Instructions.

8.2.8.2 FLIST Device Oriented CommandsRF & microwave sources which have the FLIST additional functionality shall providecontrol of frequency list by implementing the following commands.


Bode [:ALL] Vol 2-24.7.1.1[SOURce] Vol 2-19 :FREQuency Vol 2-19.9 :MODE CW|FIXed|LIST|... Vol 2-19.9.4 :LIST Vol 2-19.11 :DWELl <numeric value> Vol 2-19.11.8 :POINts? query only Vol 2-19.11.8.1 :FREQuency <numeric_value>{,<numeric_value>} Vol 2-19.11.9 :POINts? query only Vol 2-19.11.9.1

This functionality only requires one parameter for DWELl, however the instrument mayaccept more than one.

8.2.8.3 FLIST Status ReportingFLIST adds no requirement for status reporting.

8.2.9 Marker FunctionRF & microwave sources may provide control of marker functions.

The <af_keyword> for marker function is MARKER.

8.2.9.1 MARKER Measurement InstructionsMARKER adds no Measurement Instructions.

8.2.9.2 MARKER Device Oriented CommandsRF & microwave sources which have the MARKER additional functionality shall providecontrol of markers by implementing the following commands.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



KEYWORD PARAMETER FORM SCPI Reference[SOURce] Vol 2-19 :MARKer<n> Vol 2-19.12 :AOFF Vol 2-19.12.2 :FREQuency <numeric_value> Vol 2-19.12.3 [:STATe] <Boolean> Vol 2-19.12.7

RF & microwave sources may have more than one Marker. In this case a numeric suffixshall be used to distinguish between the different markers.

8.2.9.3 MARKER Status ReportingMARKER adds no requirement for status reporting.

8.2.10 Trigger FunctionRF & microwave sources uses the TRIGger Subsystem to control the start of the sweep orlist function if the frequency and/or the amplitude is swept. When a trigger is received, theRF & microwave source starts and completes a sweep or list sequence and then waits for thenext trigger event.

The <af_keyword> for trigger function is TRIGGER.

8.2.10.1 TRIGGER Measurement InstructionsTRIGGER adds no Measurement Instructions.

8.2.10.2 TRIGGER Device Oriented CommandsRF & microwave sources which have the TRIGGER additional functionality shallimplement the following trigger commands.


Bode [:ALL] Vol 2-24.7.1.1 [:IMMediate] Vol 2-24.7.2

Bode [:ALL] Vol 2-24.7.2.1ABORt Vol 2-24.5TRIGger Vol 2-24.8 [:SEQuence] Vol 2-24.8.1 [:IMMediate] Vol 2-24.8.1.11 :SOURce BUS | IMMediate | ... † Vol 2-24.8.1.17

† In addition to the TRIGger:SOURce parameters listed, a RF & microwave source withFSSWEEP, PSSWEEP or FLIST shall implement an external trigger, such as EXTernal,ECLTrg<n> or TTLTrg<n>.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



Requiring BUS as a legal parameter to TRIGger:SOURce has the side effect of requiringDT1 capability in a 488.1 device. It also means the RF & microwave source implements the*TRG common command.

A VXIbus device with a trigger function is required to implement the Trigger command.When TRIGger:SOURce is set BUS, a VXIbus RF & microwave source shall use theTrigger command as the TRIGger source.

8.2.10.3 TRIGGER Status ReportingIf the additional function TRIGGER is implemented and the RF & microwave source isperforming this operation, bit 5 (Waiting for TRIGger) shall be set in the OPERation StatusRegister.

8.2.11 Reference OscillatorRF & microwave sources may have the functionality to select which reference oscillator is inuse and to define the frequency of the external reference oscillator.

The <af_keyword> for reference oscillator function is REFERENCE.

8.2.11.1 REFERENCE Measurement InstructionsREFERENCE adds no Measurement Instructions.

8.2.11.2 REFERENCE Device Oriented CommandsRF & microwave sources which have the additional functionality to select the referenceoscillator shall implement the following commands.

KEYWORD PARAMETER FORM SCPI Reference[:SOURce] Vol 2-19 :ROSCillator Vol 2-19.19 :EXTernal Vol 2-19.19.2 :FREQuency <numeric_value> Vol 2-19.19.2.1 :SOURce INTernal|EXTernal Vol 2-19.19.3

8.2.11.3 REFERENCE Status ReportingRF & microwave sources shall set bit 5 (FREQuency) in the QUEStionable Status Registerwhen there is no appropriate reference signal available and the RF & microwave sourcesuspects the output frequency is of questionable accuracy.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



8.3 Programming ExamplesThis section discusses how a user might program RF & microwave sources for certainapplications.

8.3.1 SimpleTo use RF & microwave sources as a simple signal source for fixed frequency and outputlevel the programmer could send:

*RSTSOURce:CW:FREQuency 123.45 MHZSOURce:POWer:LEVel:IMMediate:AMPLitude -27 DBMOUTput:STATe ON

or

*RSTFREQ 123.45MHZ;POW -27DBM;OUTP ON

8.3.2 ModulationTo use a RF & microwave source having the functionality to generate a frequencymodulated signal by use of the internal modulation source the programmer could send:

*RSTSOURce:CW:FREquency 89.5 MHZSOURce:FM:DEViation 200 KHZSOURce:FM:SOURce INTernalSOURce:FM:INTernal:FREQuency 1 KHZSOURce:POWer:LEVel:IMMediate:AMPLitude 100 UWOUTPut:STATe ON

or

*RSTFREQ 89.5MHZFM 200KHZ;FM:SOUR INT;INT:FREQ 1KHZPOW 100UW;OUTP ON

8.3.3 Analog SweepTo use a RF & microwave source having the functionality to sweep the frequency withsetting of start/stop frequency and sweep time the programmer could send:

*RSTSOURce:FREQuency:MODE SWEepSOURce:FREQuency:STARt 100 MHZSOURce:FREQuency:STOP 200 MHZSOURce:SWEep:TIME 100 MSSOURce:POWer:LEVel:IMMediate:AMPLitude -27 DBMOUTPut:STATe ONINITiate:CONTinuous ON

or

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



*RSTFREQ:MODE SWEFREQ:STAR 100MHZ;STOP 200MHZSWE:TIME 100MSPOW -27 DBM;OUTP ONINIT:CONT ON

8.3.4 Triggered Analog SweepTo use a RF & microwave source as a analog sweeper in triggered single sweep mode theprogrammer could send:

*RSTSOURce:FREQuency:MODE SWEepSOURce:FREQuency:STARt 100 MHZSOURce:FREQuency:STOP 200 MHZSOURce:SWEep:TIME 100 MSSOURce:POWer:LEVel:IMMediate:AMPLitude -27 DBMOUTPut:STATe ONTRIGger:SOURce EXTernalINITiate:IMMediate

or

*RSTFREQ:MODE SWEFREQ:STAR 100MHZ;STOP 200MHZSWE:TIME 100MSPOW -27 DBM;OUTP ONTRIG:SOUR EXTINIT

Note: The SOURCE:SWEEP:COUNT and SOURCE:LIST:COUNT are set to 1 after *RSTi.e. the sweeper will perform single sweep function after occurrence of an external triggersignal and then waits for the next trigger event.

8.3.5 Sweep with MarkerTo use a sweeper with setting of two markers the programmer could add the followingcommands to example 8.3.3:

SOURce:MARKer1:FREQuency 125 MHZSOURce:MARKer2:FREQuency 170 MHZ

or

MARK1:FREQ 125MHZ;MARK2:FREQ 170MHZ

8.3.6 Reference oscillatorTo use a RF & microwave source with its output frequency derived from an externalreference frequency the programmer could send:

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



*RSTSOURce:ROSCillator:EXTernal 10 MHZSOURce:CW:FREQuency 2355.5 MHZSOURce:POWer:LEVel:IMMediate:AMPLitude -6 DBMOUTPut:STATe ON

or

*RSTROSC:EXT 10MHZFREQ 2355.5MHZ;POW -6DBM;OUTP ON

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



9 Signal SwitchersA signal switcher is a basic signal routing instrument. In its most basic form, it can make andbreak signal connections. These signal connections are usually referred to as channels.Making a connection is closing a channel, and breaking a signal is opening a channel. Moreadvanced signal switchers can be programmed with sequence lists of channels to close inresponse to trigger events. Because a signal switcher is primarily a signal router, the ROUTeroot node is optional.

Figure 9-1 shows an instrument model for a signal switcher. It is derived from CommandReference, chapter 2. It is essentially the same as Figure 2-1 in Command Reference withvarious parts gray or dashed. The bold boxes and lines, solid and dashed, are described inthis chapter.


Figure 9-1 Simplified Model for a Progammable Signal Switcher

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


Signal Switchers 9-1

9.1 Base FunctionalityThe <bf_keyword> for a signal switcher is SWITCHER.

9.1.1 Base Measurement InstructionsSince a signal switcher has no measuring capability, it has no measurement instructions.


9.1.2.1 ROUTe SubsystemA signal switcher can at least make and break signal connections by closing and openingchannels.

The following commands shall be implemented.

KEYWORD PARAMETER FORM SCPI Reference[ROUTe] Vol 2-17 :CLOSe <channel_list> Vol 2-17.1 :STATe? Vol 2-17.1.1 :OPEN <channel_list> Vol 2-17.3 :ALL Vol 2-17.3.1

If the :CLOSe and :OPEN commmands are implemented as overlapped commands, theassociated Pending-Operation flags shall be reported in the No-Operation-Pending flag.

9.1.3 Base Status ReportingAll SCPI signal switchers shall implement the status reporting structure described in Syntax& Style, Status Reporting. Command Reference, STATus Subsystem defines the commandswhich shall be used to control the status reporting structure.

The base functionality of a switcher adds no additional status reporting requirements.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26


9-2 Signal Switchers

9.2 Additional Functionality9.2.1 Scanning

The <af_keyword> for scanning is SCAN.

Signal switchers which implement the SCAN additional functionality can be programmedwith a list of channels to “scan”. Each time the signal switcher recognizes a trigger event, itopens the previously closed channel and closes the next channel in the list.

9.2.1.1 SCAN Measurement InstructionsSCAN adds no measurement instructions.

9.2.1.2 SCAN Device-oriented Functions

9.2.1.2.1 ROUTe SubsystemA signal switcher which has the SCAN additional functionality shall implement thefollowing command.

KEYWORD PARAMETER FORM SCPI Reference[ROUTe] Vol 2-17 :SCAN <channel_list> Vol 2-17.6

Note: The following paragraph is intended to provide guidance to designers of signalswitchers. It is not intended to impose further design requirements.

The appropriate interaction between the SCAN command and the CLOSe and OPENcommands depends upon the intended application of the signal switcher. In some instances itis advantageous to be able to close a set of channels using the CLOSe command (e.g. toconnect sourcing instruments to the device under test), then scan through a different set ofchannels (e.g. to make measurements on various nodes in the device under test) withoutopening those channels which were closed by the CLOSe command. In other instances it isdesirable that the start of the scan operation first opens any channels which are alreadyclosed.

9.2.1.2.2 TRIGger SubsystemA signal switcher which has the SCAN additional functionality shall implement thefollowing trigger commands.

KEYWORD PARAMETER FORM SCPI ReferenceABORt Vol 2-24.5

EditINITiate Vol 2-24.7 :CONTinuous <Boolean> Vol 2-24.7.1 [:IMMediate] Vol 2-24.7.2

12-4-94 letter [:ALL] Vol 2-24.7.2.1TRIGger Vol 2-24.8 [:SEQuence] Vol 2-24.8.1 :COUNt <numeric_value> Vol 2-24.8.1.2 :SOURce BUS | IMMediate | ... † Vol 2-24.8.1.17

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



† In addition to the TRIGger:SOURce parameters listed, a signal switcher with SCAN shallimplement an external trigger, such as EXTernal, ECLTrg<n> or TTLTrg<n>.

Requiring BUS as a legal parameter to TRIGger:SOURce has the side effect of requiringDT1 capability in a 488.1 device. It also means the signal switcher implements the *TRGcommon command.

A VXIbus device with a trigger function is required to implement the Trigger command.When TRIGger:SOURce is set BUS, a VXIbus switcher shall use the Trigger command asthe TRIGger source.

9.2.1.3 SCAN Status ReportingBit 5 (Waiting for TRIG) in the OPERation Status Register shall be used to indicate thestatus of the trigger model.

9.2.2 Extended TriggerThe <af_keyword> for extended trigger is ETRIGGER. This <af_keyword> is subservient toSCAN.

Some signal switchers which have SCAN functionality (and so have TRIGger commands)provide two layer triggering where a separate event must occur before the TRIGger layer isentered.

9.2.2.1 ETRIGGER Measurement InstructionsETRIGGER adds no Measurement Instructions.

9.2.2.2 ETRIGGER Device-oriented Functions

9.2.2.2.1 TRIGger SubsystemThe following ARM command shall be used to provide the ETRIGGER functionality.

KEYWORD PARAMETER FORM SCPI ReferenceARM Vol 2-24.6 [:SEQuence] Vol 2-24.6.1 [:LAYer] Vol 2-24.6.1.2 :SOURce {BUS | IMMediate | ... } Vol 2-24.6.1.2.14

9.2.2.3 ETRIGGER Status ReportingBit 6 (Waiting for ARM) in the OPERation Status Register shall be used to indicate thestatus of the trigger model.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



9.3 Programming ExamplesThis section discusses how a user might program a signal switcher for certain applications.The examples assume the signal switcher contains a single switch module which is a10-channel multiplexer which permits any combination of the 10 channels to be closedsimultaneously.

9.3.1 Making and Breaking ConnectionsTo close signal channel #3:

ROUTe:CLOSe (@3)

or

CLOS (@3)

To query whether channel #3 is closed:

ROUTe:CLOSe? (@3)

or

CLOS? (@3)

9.3.2 Programmed Connection SequencesA signal switcher which can be programmed with a sequence of connections can improvethe throughput of test systems by reducing the communication required between the systemcontroller and the test instruments. For example, the output of the 10-channel multiplexerwhich has SCAN functionality, and includes EXTernal as a valid parameter forTRIGger:SOURce, is connected to the inputs of a DMM. The “meter complete” signal fromthe DMM is connected to the external trigger input of the signal switcher. To configure thissystem to measure on all 10 channels, use this sequence of commands to the signal switcher:

*RSTTRIGger:SEQuence:COUNt 9;SOURce EXTernalROUTe:SCAN (@2,3,4,5,6,7,8,9,10);CLOSe (@1)INITiate:IMMediate

or

*RSTTRIG:COUN 9;SOUR EXTSCAN (@2:10);CLOS (@1)INIT

The *RST command sets INITiate:CONTinuous to OFF and puts the trigger model in IDLE.After sending the INITiate:IMMediate command, the system controller triggers the DMM.When the meter is finished measuring, its “meter complete” signal activate the signalswitcher’s external trigger input, causing it to close channel 2. Now the system controllertriggers the DMM again, and so on. When the signal switcher has finished processing the 9thtrigger (closing channel 10) it returns to the trigger model IDLE layer.

1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



1

2

3

4 5

6

7

8 9

10

11

12

1314

15

16

1718

19

20

21

2223

24

25

26



volume 1: syntax and style - ivi foundation

Documents