Agilent 70700A Programmers Guide

Download

HEWLETT PACKARD

PROGRAMMING MANUAL

HP 70700A

DIGITIZER

SERIAL NUMBERS

This manual applies directly to HP 70700A Digitizers with serial numbers prefixed 2709A and below.

FIRMWARE VERSIONS

This manual applies directly to HP 70700A Digitizers with firmware versions of 870501 and earlier.

1212 VALLEY HOUSE DRIVE, ROHNERT PARK, CALIFORNIA 94928-4999 U.S.A.

Manual Part Number 70700-90021 Microfiche Part Number 70700-90022

Printed: MAY 1987

Hewlett-Packard Company certifies that this product met its published specifications at the time of shipment from the factory. Hewlett-Packard further

certifies

that its calibration measurements are

traceable to the United States National Bureau of Standards, to the extent allowed by the Bureau’s calibration facility and to the calibration facilities of other International Standards Organization members.

WARRANTY

This Hewlett-Packard instrument product is warranted against defects in material and workmanship for a period of one year from date of shipment. During the warranty period, Hewlett-Packard Company will, at its option, either repair or replace products which prove to be defective.

For warranty service or repair, this product must be returned to a service facility designated by HP. Buyer shall prepay shipping charges to HP and HP shall pay shipping charges to return the product to Buyer. However, Buyer shall pay all shipping charges, duties, and taxes for products returned to HP from another country.

HP warrants that its software and firmware designated by HP for use with an instrument will execute its programming instructions when properly installed on that instrument. HP does not warrant that

the operation of the instrument, or software, or firmware will be uninterrupted or error free.

LIMITATION OF

WlRRANTY

The foregoing warranty shall not apply to defects resulting from improper or inadequate maintenance by Buyer, Buyer-supplied software or interfacing, unauthorized modification or misuse, operation outside of the environmental specifications for the product, or improper site preparation or maintenance.

NO OTHER WARRANTY IS EXPRESSED OR IMPLIED. HP SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTIES

.OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE.

EXCLUSIVE REMEDIES

THE REMEDIES PROVIDED HEREIN ARE BUYER’S SOLE AND EXCLUSIVE REMEDIES. HP SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT, OR ANY OTHER LEGAL THEORY

Product maintenance agreements and other customer assistance agreements are available for Hewlett-Packard products.

For

any

assistance, contact your nearest Hewlett-Packard Sales and Service Office. Addresses are

provided at the back of this manual.

SAFETY SYMBOLS

The following safety symbols are used throughout this manual and in the instrument. Familiarize yourself with each of the symbols and its meaning before operating this instrument.

Instruction manual symbol. The instrument will be marked with this symbol when it is necessary for the user to refer to the instruction manual in order to protect the instrument against damage. Location of pertinent information within the manual is indicated by use of this symbol in the table of contents.

Indicates dangerous voltages are present. Be extremely careful.

The CAUTION sign denotes a hazard. It calls attention to a procedure which, if not correctly performed or adhered to, could result in damage to or destruction of the instrument. Do not proceed beyond a CAUTION sign until the indicated conditions are fully understood and met.

The WARNING sign denotes a hazard. It calls attention to a procedure which, if not correctly performed or adhered to, could result in injury or loss of life. Do not proceed beyond a WARNING sign until the indicated conditions are fully understood and met.

GENERAL SAFETY CONSIDERATIONS

BEFORE THIS INSTRUMENT IS SWITCHED ON, make sure it has been

properly grounded through the protective conductor of the ac power cable to a socket outlet provided with protective earth contact. Any interruption of the protective (grounding) conductor, inside or outside the instrument, or disconnection of the protective earth terminal can result in personal injury.

There are voltages at many points in the instrument which can, if contacted, cause personal injury. Be extremely careful. Any adjustments or service procedures that require operation of the instrument with protective covers removed should be performed only by trained service personnel.

BEFORE THIS INSTRUMENT IS SWITCHED ON, make sure its primary power circuitry has been adapted to the voltage of the ac power source. Failure to set the ac power input to the correct voltage could cause damage to the instrument when the ac power cable is plugged in.

. . .

111

Chapter 1, General Information

How to Use this Manual Digitizer System Overview

HP 70700A Digitizer Module Overview.......................................................................................

HP 70700A Digitizer Front-Panel Features................................................................................

HP 70700A Digitizer Rear-Panel Features Mainframe/Module Interconnect

............................................................................

.................................

............................................................................................................................................................................

Chapter 2. Programming Fundamentals

......

Setup Procedures

Digitizer Channel Number Assignment

Address Switches

Soft-Set HP-IB Addresses

Communication with the System......................................................................................................

Executing Remote Commands......................................................................................................

Initial Program Considerations

Status Reporting Structure.............................................................................................................

Status Byte Register

Service Request Enable Register................................................................................................

Standard Event Status Register Standard Event Status Enable Register Output Queue

Synchronization of Events and Commands..................................................................................

General Sequence.

Synchronization Commands Data Transfer Multiple Digitizer Remote Slaving Procedure

Example Program Remote Slaving Procedure for Random Event Capture Example Program for Random Event Capture

...............................................

.................................................

................................................

............................................

....................................................................................................

.........................................

........................................................................................................................

......................................................................................................................

......................................

.................................

.........................................................................................................

............................

..............................................

1-1

l-l

1-3 l-3 l-5 1-6

2-1

2-2

2-4

2-6

z-59

2 ;l

2-13 2-16

2-16 2-18

2-19

2 2 o

2-2 2-22

2-30

2-32

2-37

Chapter 3. Language Reference

Notation Conventions Functional Syntax Conventions

Common Command Set.....................................................................................................................

*CLS, Clear Status *ESE Standard Event Status Enable

*ESR’,

Standard Event Status Register

*IDN, Identification *OPC

Operation Complete. *OPT: Option Identification *RST,Reset *SRE Service Request Enable *STB’ Read Status Byte

*TST Self-Test *WA;, Wait-to-Continue

................................................

...........................................

........................................................................................

...........................................

.........................................

.............................................

..................................

.....................................

..................................

.................................

......................................

.....................................

........................................

3-1

z-i

3-10 3-10

3-11 3-11 3-12 3-12 3-12

3-13

CONTENTS, Continued

Digitizer Top-Level Command Set

AUT, Autoscale BLAN, Blank *CAL, Calibration DIG, Digitize. ERR, Error.

............................................

.............................................

..........................................

.............................................

...............................................

.................................

RUN...................................................

STOP STOR, Store VIEW..

Acquire Subsystem

COUN, Count POIN, Points.

...............................................

..............................................

...........................................

.............................................

TYPE..................................................

Calibration Subsystem

ALL.. DATA

...............................................

..................................................

Channel Subsystem

COUP, Coupling DET, Detector. ECL, Emitter-Coupled Logic INP, Input

...............................................

OFFS, Offset. PROB, Probes

RANG, Range. SA, Spectrum Analyzer TTL, Transistor-Transistor Logic

.........................................

...........................................

............................................

...................................

.............................................

............................................

.......................................

.................................

TYPE..................................................

Display Subsystem

CONN, Connect FORM, Format GRAT, Graticule SCR, Screen STR, String TMAR, Time Markers. VMAR, Voltage Markers

Domain Subsystem

............................................

...........................................

............................................

...........................................

..............................................

...............................................

.......................................

......................................

...........................................

TYPE..................................................

Function Subsystem

ADD, Addition INV, Invert MULT, Multiply OFFS, Offset.

...........................................

............................................

...............................................

...........................................

.............................................

ONLY..................................................3-4

RANG, Range SUBT, Subtraction

VERS,

Versus

Measure Subsystem

...................................................

ALL, CURS, Cursor

.............................................

.................................

........

.............................................

...........................................

.............................................

.,.3-l

..3-17

...3-2

3-14 3-15 3-15 3-16 3-16 3-16 3-16

3-17

3-18 3-19 3-19 3-20 3-2 1

3-22 3-23 3-24 3-25 3-26 3-26 3-26 3-27

3-27 3-28 3-28 3-28 3-29 3-31 3-31 3-32 3-32 3-33 3-33 3-34 3-35 3-36 3-37 3-39

3-39

3-40 3-40

1 3-41 3-42 3-42 3-43 3-49 3-49

CONTENTS, Continued

DUT, Duty Cycle. ESTA, Start Marker Edge Number

ESTO,

Stop Marker Edge Number

FALL, Fall Time

F.REQ,Frequency

LOW, Lower Threshold MODE

..................................................

NWID, Negative Pulse Width OVER, Overshoot PER, Period

PREC, Precision PRES, Preshoot PTIM, Preceding Point of Requested Time PVOL, Point of Specified Voltage/Intersection PWID, Positive Pulse Width

RISE, Rise Time. SOUR, Source

TDEL, Time Marker Delta

..........................................

................................

...........................................

..........................................

.......................................

...................................

..........................................

..............................................

...........................................

............................................

..........................

........................

....................................

...........................................

.............................................

.....................................

TMAX, Time of First Occurrence of Maximum Voltage TMIN, Time of First Occurrence of Minimum Voltage TPO, Time of Specified Point TSTA, Time of Start Marker TSTO, Time of Stop Marker TTIM, Time of REC Trigger Event TVOL, Time of Specified Voltage/Intersection UNIT, Units

..............................................

UPP, Upper Threshold VAMP, Signal Amplitude VAV, Signal Average

........................................

VBAS, Waveform Base Voltage Level VDEL, Voltage Marker

‘Delta VFIF, Voltage Markers to

VMAX, Maximum Voltage of Signal

VMIN, Minimum Voltage of Signal

VPO, Voltage of Specified Point VPP, Signal Voltage Peak-to-Peak VREL, Relative Voltage Marker Positioning

VRMS, RMS VSTA,

Position of Voltage Marker

VSTO,

Position of Voltage Marker 2

VTIM,

Voltage of Specified Time

VTOP,

Top Voltage Level

Timebase

DEL, Delay

Voltage

Subsystem

..............................................

........................................

..........................................

DELT, REC Delta Time EVEN, INT,

Interpolation MODE RANG, REF,

Reference

Event

..................................................

Range.

.............................................

..........................................

............................................

...................................

....................................

...............................

........................

.......................................

......................................

.............................

...................................

..................................

50%

..............................

...............................

.................................

................................

.........................

..............................

‘1

..............................

................................

.....................................

Status

..................................

.................

..................

3-49 3-50

3-50 3-51

3-51 3-51

3-52 3-53 3-53 3-54 3-54 3-54 3-55 3-55 3-56 3-56 3-57

3-57 3-57

3-58 3-58 3-58 3-59 3-59 3-59

3-60

3-61

3-62 3-62

3-62 3-63

3-63

3-63 3-64 3-64

3-64 3-65

3-65

3-66 3-66

3-66 3-67 3-70 3-70 3-71 3-71 3-72 3-72

3-73

CONTENTS, Continued

SAMP,Sample.............................................3-7

SWIT, Switch Magnify Subsystem

Trigger Subsystem .

CENT, Center . . DEL, Delay . . . HOLD,

Holdoff

HYST, Hysteresis

LEV, Level . . . .

QUAL, Qualifier SOUR, Source . . TOUT, Timeout .

Waveform Subsystem

.............................................

.........................................

...........................................

..........................................

DATA ..................................................

FORM, Format POIN, Points PRE, Preamble SOUR, Source TYPE

..................................................

VAL, Valid XINC, X Increment XOR, X Origin XREF, X Reference YBOT, Bottom Reference Value YINC, Y Increment YOR, Y Origin YREF, Y Reference YTOP, Top Reference Value

Window Subsystem

............................................

..............................................

............................................

.............................................

...............................................

.........................................

............................................

.........................................

.................................

.........................................

............................................

.........................................

...................................

...........................................

TYPE ..................................................

3 3-74 3-74 3-77 3-79 3-79 3-80

3-80

3-81 3-81 3-82 3-83 3-84 3-84

3-86 3-86 3-87 3-87 3-88 3-88 3-88 3-89 3-89 3-89

3-90

3-91 3-92 3-93

Appendices

Appendix A, Command Listing by Subsystem Appendix B, Alphabetical Mnemonic Listing Appendix C, Alphabetical Command Description Listing Appendix D, Alphabetical Command Summary Appendix E, HP-IB Review

......................................

..........................

...........................

.........................

...................

A-l

B-l C-l D-l

E-l

Vii

LIST OF ILLUSTRATIONS

Figure Title

l-l. Multiple-Channel Digitizer System l-2. HP 70700A Digitizer Front Panel l-3. HP 70700A Digitizer Rear Panel

1. Multiple-Channel Digitizer System Addressing 2-2. HP 70700A Digitizer Address Switches 2-3. Status Data Structure 2-4. Status Byte Register 2-5. Service Request Enable Register 2-6. Standard Event Status Register 2-7. Output Queue 2-8. Timing Diagram without a Synchronization Command 2-9. Timing Diagram Using a Synchronization Command

2-10.

Remote Slaving Procedure Diagram 2-11. Remote Slaving Procedure Diagram for Random Event Capture 3-1. Terminated Program Message Functional Element Syntax 3-2. <PROGRAM MESSAGE UNIT> Functional Element Syntax 3-3. <COMMAND/QUERY MESSAGE UNIT> Functional Element Syntax 3-4. <PROGRAM MESSAGE UNIT SEPARATOR> Syntax 3-5. <PROGRAM HEADER SEPARATOR> Syntax 3-6. <PROGRAM DATA SEPARATOR> Syntax 3-7. Common Command Set Commands 3-8. Digitizer Top-Level Command Set Commands 3-9. Acquire Subsystem Commands

3-10.

Calibration Subsystem Commands 3-l1. Channel Subsystem Commands 3-12. Display Subsystem Commands 3-l3. Domain Subsystem Commands 3-14. Function Subsystem Commands 3-l5. Measure Subsystem Commands 3-16. Timebase Subsystem Commands 3-17. Trigger Subsystem Commands

3-18.

Waveform Subsystem Commands

3-19.

Window Subsystem Commands

E-l. HP-IB Connector . E-2. HP-IB Structure

..........................................

......................

......................................

.........................................

..........................................

..............................

...............................

......................

...........................

................

..............................

...............................

................

.................

...........................

.........

...............

.............

................

.....................

.......................

.............................

.....................

...............................

............................

..............................

...............................

..............................

...............................

.............................

..............................

Page No.

......

l-2 l-4

1-5

2-3 2-3

2-10 2-11 2-12 2-14 2-17 2-18 2-19 2-28 2-35

3-3 3-3 3-3 3-5 3-5

3-5

3-8

3-14 3-18

3-2

3-23 3-29 3-35 3-37 3-44 3-67 3-77 3-84 3-92

E-l E-2

HP 70000 MODULAR MEASUREMENT SYSTEM

DOCUMENTATION OUTLINE

Instruments and modules of the HP 70000 Modular Measurement System are documented to varying levels of detail. Modules that serve as masters of an instrument require operation information in addition to installation and verification instructions. Modules that function as slaves in a system require only a subset of installation and verification information. Service 70000 Modular Measurement System family.

docuinentation

USER MANUALS, SUPPLIED WITH MODULE

Installation and Verification Manual

Topics covered by this manual include installation, specifications, verification of module operation, and some troubleshooting techniques. Manuals for modules that serve as instrument masters will supply information in all these areas; manuals for slave modules will contain only information needed for slave module installation and verification. Master module documentation may also include some system-level information.

availa’ble

for every module of the HP

Operation Manual

Information in this manual usually pertains to multiple- and single-module instrument systems. The

Operation Manual describes manual operation of the module, with explanations of

softkeys and their use.

Programming Manual

Information in this manual usually pertains to multiple- and single-module instrument systems. The Programming Manual defines commands that enable remote operation of the module, and describes remote

command syntax.

SERVICE MANUAL, AVAILABLE SEPARATELY

Technical Reference

This manual provides service information for a module, including performance verification, adjustments, troubleshooting, replaceable parts lists, replacement procedures, diagrams. For ordering information, contact an HP Sales and Service Office.

schematics, and component location

GENERAL INFORMATION

Chapter

GENERAL INFORMATION

HOW TO USE THIS MANUAL

The HP 70700A Digitizer Programming Manual describes how to operate a digitizer system by remote,

computer control. It is not necessary to read this manual from cover to cover; however, it may be useful to

note what is in each chapter. Chapter 1, General Information, provides descriptions of the digitizer system, the HP 70700A Digitizer

module, and front- and rear-panel features of an HP 70700A Digitizer module.

Before any remote operations are performed with your digitizer system, it must first be installed and configured properly. Refer to the HP 70700A Digitizer Installation and Verification Manual for detailed instructions on correct installation and configuration information.

Chapter 2, Programming Fundamentals, provides information on the following topics: installation for

remote operation, communication with the system, the Status Reporting Structure, synchronization of events and commands, and data transfer. Information on multiple-digitizer remote slaving is also included in this chapter.

Chapter

functional subsystem, including syntax diagrams and functional parameters.

Appendices consist of four cross-reference listings and/or summaries for the digitizer remote commands, and a general overview of the Hewlett-Packard Interface Bus (HP-IB):

A single-channel digitizer system consists of an HP 70700A Digitizer master module, an HP 70205A or HP 70206A Display, and an HP 70001A Mainframe. Additional digitizer modules may be slaved to the master module to provide a multiple-channel digitizer system. See Figure l-l.

The digitizer system measures repetitive or transient waveforms with improved accuracy, resolution, and dynamic range over other measurement techniques. With the use of the internal analog-to-digital converter

Language Reference, provides a complete, detailed description of each command within each

Appendix A Command Listing by Subsystem Appendix B Alphabetical Mnemonic Listing Appendix C Appendix D Alphabetical Command Summary Appendix E HP-IB Review

Alphabetical Command Description Listing

l-l

GENERAL INFORMATION

(ADC) combined with digital memory, a computer can be used to analyze the data, and allowing automation. Simultaneous digitization and memory access are available (i.e., as data is being measured, the results may be accessed immediately with the use of a controller). Multi-channel operation may be achieved by slaving multiple digitizer modules together, synchronized by the master digitizer module “clock out” and “sync out” signals.

Data is always digitized at a 20 MHz rate and then a digital detection algorithm is applied to “reduce” the data before it is stored. The four detection modes that are available for selection are sample, peak, pit, and alternate.

Interpolation may be used to provide a better visual display of high-frequency waveforms.

with the slave digitizer module

ny”

broviding better results

lllcvll

HEWLETT

Ei!!iia

LIE 0 or Pl

The digitizer system has triggering capabilities which are especially necessary when measuring transient waveforms. These triggering capabilities are the functions of EITHER EDGE, ABOVE BELOW LEVEL, or OUTSIDE RANGE. Additionally, hysteresis may be used to adapt the triggering to match the input signal.

The Random Event Capture mode retains up to 1000 trigger events of a measurement with a guaranteed amount of pre- and post-trigger data for each event. There is no dead time between events, the time of the event is always stored, and the event time may be queried data. The memory is dual ported so that captured events may be examined while the measurement is still proceeding.

The Equivalent Time Sampling mode provides a technique for looking at stable, periodic, repetitive signals by using multiple trigger events to form a composite waveform. It will allow than 10 ns.

PACKARD

AIRFLOW

Figure l-l. Multiple-Channel Digitizer System

tYom :1

controller without outputting the event

70001A MAINFRAME

riseitime measurements of less

70000 SYSTEMS/

singleshot

LEVEL,,

1-2

GENERAL INFORMATION

HP 70700A DIGITIZER MODULE OVERVIEW

The HP 70700A Digitizer is a l/8-module with a 20 MHz sampling rate designed to work in an HP 70000 Series mainframe. It has both HP-IB (Hewlett-Packard Interface Bus) and HP-MSIB (Hewlett-Packard Modular System Interface Bus) communication capabilities. The HP 70700A Digitizer can function in the following configurations:

l Single-channel digitizer system (consisting of one module)

l Multiple-channel digitizer system (with one HP 70700A Digitizer functioning as a master to other HP

70700A Digitizer modules)

l Slave to an HP 70900A Local Oscillator when configured in an HP

70000

Series Modular Spectrum

Analyzer System

l Single-channel digitizer instrument configured with an HP 70000 Series Modular Spectrum Analyzer

System (When the HP 70700A Digitizer is used in this configuration, it is not a slave of the spectrum analyzer but is used to view the spectrum analyzer video output.)

The last configuration described above is essentially the same as a single-channel digitizer system. The disadvantage of this configuration is that the spectrum analyzer and digitizer operate independently, so sweep-time coupling and amplitude calibration are lost. However, the advantage of this configuration is that it allows all the digitizer features, such as the Measure ALL function and the Random Event Capture mode, to operate on the video output of the spectrum analyzer. Refer to the HP 70700A Digitizer Installation and Verification Manual for diagrams of correct digitizer system configurations.

LED Indicators

1. STATUS ACT indicates that the HP 70700A Digitizer is active. The ACTIVE LED lights when: a. the keyboard of the display is allocated to the digitizer.

b. any Display function indicates the digitizer (e.g., when the cursor of the Display Address Map is at

the HP-MSIB address of the digitizer).

c. a digitizer is a slave to another digitizer that is designated as a master module, and it is being used by

that master digitizer.

2. STATUS ERR indicates errors. (Refer to Chapter 5, Troubleshooting, in the HP 70700A Digitizer Installation and Verification Manual.)

3. HP-IB RMT indicates that the module is being remotely controlled and local control is disabled.

4. HP-IB LSN indicates a state in which the module is ready to accept information from the controller.

I-3

GENERAL INFORMATION

’ 707OOA bTE

DIGITIZEF

Mmnplor/rr

FRONT-

\ PANEL

BNC

INPUT

MODULE

LATCH

Figure 1-2. HP 70700A Digitizer Front Pmel

5. HP-IB TLK indicates a state in which the module is

6. HP-IB SRQ indicates a condition requested or set by the user (e.g., errors, operation complete status, power-on condition). Refer to Chapter 2, Programming Fundamentals, for more information on the Service Request LED and the Standard Status Data

7. MEASURE indicates that the module is making a measurement.

INPUTS

INPUT 1 (type BNC connector) can be utilized only when the HP 70700A Digitizer is used in a digitizer system. Refer to Table 1-l for more information about input selection and input impedance.

MODULE LATCH

The module hex-nut latch is used for installing the module in an HP 70000 Series mainframe. An 8 mm hex-ball driver is required to turn the hex-nut latch.

reads

to send information to the controller.

StruCture.

1-4

GENERAL INFORMATION

Table l-l. HP 70700A Digitizer Input Selection and Input Impedance

HP 70700A Digitizer used in a digitizer system, or as a digitizer instrument in a non-digitizer system:

HP 70700A

Preset Input

Softkey-Selected Input

Preset Input Impedance

Softkey-Selected Input Impedance

HP 70700A Digitizer used as a slave to a non-digitizer master:

Preset Input

Softkey-Selected Input

Preset Input Impedance

Softkey-Selected Input Impedance

DC Coupled I MR

AC Coupled

or DC Coupled

DC Coupled 1

DIGITIZER REAR-PANEL FEATURES

INPUT

INPUT 2

none

lf2,

5Of2

MSZ

Figure 1-3. HP 70700A Digitizer Rear Panel

1-5

GENERAL INFORMATION

Rear-Panel SMB Connectors

1. HI SWP (High Sweep) is an input/output that is connected to HSWP of the HP 70900A Local Oscillator when an HP 70700A Digitizer is used as a slave to an HP 70900A Local Oscillator in a spectrum analyzer

system. This connection is necessary to synchronize the digitizer and local oscillator and their starting and stopping of measurements.

2. CLK OUT (Clock Out) provides a TTL-level 20 MHz clock output. In a single-channel digitizer system, the CLK OUT is connected to the CLK IN on the same module. In a multiple-channel digitizer system, the CLK OUT of the master HP 70700A Digitizer module must be connected to both its own CLK IN and the CLK IN of all of its slaves. (Refer to the HP 70700A Digitizer Installation and Verification Manual, Chapter 2, for detailed instructions on correct installation and configuration information.)

3. CLK IN (Clock In) requires a 50% duty cycle, TTL-level clock input with a 10 MHz to 20 MHz frequency. (See CLK OUT, above.)

4. INPUT I can be utilized only when the HP- 70700A Digitizer is used in a digitizer system. The front-panel INPUT 1 and rear-panel INPUT 1 are connected together and are electrically the same. Refer to Table 1-I for more information about input selection and input impedance.

5. INPUT 2 can be utilized when the HP 70700A Digitizer is used in any type of configuration. When the HP 70700A Digitizer is used in a digitizer system, INPUT 2 is preset “open” (i.e., no connection). Refer to Table l-l for more information about input selection and input impedance.

6. EXT TRIG (External Trigger) allows an external input signal to be used to trigger the digitizer module externally. The input signal must be TTL with a pulse width of’ at least one clock period, typically 50 ns. (See SYNC OUT, below.)

7. SYNC OUT (Synchronizing Output) provides a TTL-level signal used to svnchronize the ‘HP 70700A Digitizer slave modules of a multiple-channel digitizer system. In a multiple-channel digitizer system, the SYNC OUT of the master HP 70700A Digitizer must be connected to the EXT TRIG inputs of the HP 70700A Digitizer slave modules. (Refer to the HP 70700A Digitizer Installation and Verification Manual, Chapter 2, for detailed instructions on correct installation and configuration information.)

MAINFRAME/MODULE INTERCONNECT

The mainframe provides the power supply, HP-MSIB connections, and HP-IB connections for the HP 70700A Digitizer module through this mainframe/module interconnect.

l-6

PROGRAMMING FUNDAMENTALS

Chapter 2

PROGRAMMING FUNDAMENTALS

This chapter provides the information necessary to operate a digitizer system via a computer. The topics covered in this chapter are listed below:

Setup Procedures for Remote Operation

Address Switches

. Communication with the System

Status Reporting Structure

Synchronization of Events and Commands

Data Transfer

l Multiple-Digitizer Remote Slaving Procedure

2-1

PROGRAMMING FUNDAMENTALS

The following procedure describes how to connect your equipment for remote operation of a digitizer system.

NOTE

Refer to the HP 70700A Digitizer Installation and Verification Manual for more detailed and specific information on installation, configuration, and addressing of digitizer systems.

1. Connect computer, digitizer system, and other peripherals with HP-IB cables.

2. After the HP-IB cables are installed, reset all instruments connected to the bus. (If you are not sure how to reset a device, switch its line power off, then on, to reset it.)

3. Check the HP-IB address of the master digitizer module on the address map. To view the address map,

press the [DISPLAY]

RPG knob on the front panel of the display until the first digitizer module appears in the address map.

key on the display

front

panel,

then press the ~~~~~~~~~~~~~~~~

. . . . . . . .

:...:::.::.:.....:..:::.::::::.,.:.,..:...:::

,.....,.,..,,........,.....,...........................

softkey.

Turn the

The master digitizer module must be located in row 0 for HP-IB access and error-reporting capabilities.

4. Check the system configuration on the address map. For single-channel digitizer system operation, the digitizer and display modules must be positioned in the bottom row (row. 0) of the address map. For multi-channel digitizer systems, the other digitizer modules must be positioned either in the same column as the master digitizer above row 0, or in any other higher-address column above row 0 of the master module. For more information on multi-channel system configurations, refer to Digitizer Channel Number Assignment, below.

DIGITIZER CHANNEL NUMBER ASSIGNMENT

The channel number assignment of a digitizer system is determined by addressing. The master digitizer, located at row 0, will always be assigned as CHANNEL 1. The next HP 70700A Digitizer encountered by the master in its search will be assigned as CHANNEL 2. This process continues until all of the channels have been assigned, or until all of the HP 70700A Digitizers have been assigned channels. The sequence in which the Address Map is searched is from bottom to top and left to right. A maximum of four channels are available when a digitizer system is controlled from a display front panel. A maximum of eight channels

are available when the system is controlled by a computer.

Figure 2-1 displays the address map of a four-channel digitizer system. Note that the master digitizer

module is CHANNEL 1 and that it is located in row 0. The other three digitizers (or Channels) are defined

by their address positions.

2-2

CHANNEL 2

MASTER CHANNEL 1

PROGRAMMING FUNDAMENTALS

ADDRESSING EXAMPLE

70700A

DIGITIZER-\

70700A .

DltNTIZER \

CHANNEL

CHANNEL 3

COLUMN

Figure 2-l. Multiple-Channel Digitizer System Addressing

PROGRAMMING FUNDAMENTALS

ADDRESS SWITCHES

Address switches set the HP-MSIB address of an element (module); the column address switches also set the HP-IB address for masters and independent elements. Some master elements can also have their HP-IB address set through the use of softkeys (i.e., soft-set address).

The hard address switches for the digitizer are located on the top of the module.

HP-IB address 31 is an Illegal address and should not be used.

Descriptions of the HP 70700A Digitizer address switches are given below.

HP-IB ON-OFF When this is set to OFF, the HP 70700A Digitizer is switched off the HP-IB. Column ADDRESS Switches l-5 These set the HP-MSIB column address, which is also the HP-IB address. Row ADDRESS Switches l-3 These set the HP-MSIB row address.

ADDRESS

HP-18

ROW

ADDRESS

SWITCHES

Figure

’ COLUMN

ADDRESS

SWITCHES

2-2.

HP 70700A Digitizer Address Switches

OFF

SOFT-SET HP-IB ADDRESSES

The HP-IB address of the digitizer master module may be changed from the front panel of the display. The soft-set address remains in effect until the hard address switches are changed and power is cycled, or until another soft-set address is entered. At power-up, the soft-set address will override the hard address switch settings.

NOTE

PROGRAMMING FUNDA.MENTALS

Changing the HP-IB address via the display front

panel

does not affect the

position of the modules on the address map.

Use the following procedure to enter a soft-set HP-IB address.

1. Press the [DISPLAY] key on the display front panel.

.....

When the display Main Menu appears, press the #&?fl~~$ii$!##! softkey.

;~...~~.........~~~~~.

When the next

Enter the new HP-IB address using the numeric keys on the display front panel.

press $e&~@g*

. . . . . . . . . . . . . . . . . . . . . . ..s

. . . . . . . . ..I..............

menu appears, press ~~~;~~~~~~~~~~.

. .

...

.......

. .. . . . ...

:.i:

.............................................

..::......:..::i.::.:....i:..:::

.......................................................

:..;....:.::::...::

...

.............. .....

.:::::: ':: ;'*':.' ::::::..::...::...:::

2-5

PROGRAMMING FUNDAMENTALS

COMMUNICATION WITH THE SYSTEM

This section develops some fundamental techniques for controlling the digitizer and obtaining sound measurement results. Remote operation of the digitizer is controlled with commands that correspond in general to front-panel

It is important to understand how messages are communicated to the digitizer; therefore, enter and output statements and command syntax discussed in this section should be understood before proceeding. It should be noted that HP BASIC is used for all examples in this manual.

Digitizer programs control the passage of digitizer commands and data between the digitizer and the

computer on the Hewlett-Packard Interface Bus (HP-IB), using HP BASIC OUTPUT and ENTER statements. An OUTPUT statement tells the computer to send a message to the digitizer. For example, executing the

output statement below sets the time range to 10

softkey

functions.

MS:

OUTPUT

COMPUTER SEND MESSAGE

HP-IB SELECT CODE

DIGITIZER ADDRESS

ACTIVATE TIME RANGE

SET TIME RANGE VALUE

COMMAND SEPARATOR

An ENTER statement used in conjunction with a digitizer query returns information to the computer. To return the time range value to the computer, first form a query by adding a question mark (?) to the command:

707;“TIM:RANG

lOus;

2-6

PROGRAMMING FUNDAMENTALS

OUTPUT

TIME RANGE

ACTIVATE QUERY

COMMAND

Next, the enter statement can be used to assign the

SEPARATOR

ENTER

COMPUTER RECEIVE MESSAGE

707;“TIM:RANG?;”

ret-wned

value to a variable in the computer:

707;Range

HP-18

SELECT CODE

DIGITIZER ADDRESS

COMPUTER VARIABLE

The value of the time range above is equated to the computer variable “Range”. The variable may be

printed, stored, or used for any other computer function.

Syntax Requirements

All of the program examples in this manual show recommended command syntax. All digitizer commands must be constructed according to specific syntactical rules which are outlined in Chapter 3, Language Reference. The Language Reference lists all of the remote digitizer commands in alphabetical order

according to each functional group subsystem, and contains a syntax diagram for each subsystem.

Local and Remote Control

Whenever the digitizer is remotely addressed, the display front-panel softkeys are disabled. Pressing the

[LOCAL] key or executing the HP BASIC command “LOCAL” reenables operation of the softkeys.

2-7

PROGRAMMING FUNDAMENTALS

INITIAL PROGRAM CONSIDERATIONS

Programs should begin with a series of HP BASIC and digitizer commands that form a good starting point for digitizer measurements. The following example shows how to initialize the digitizer to form a good starting point.

10 ASSIGN @DIG to 707 20 CLEAR @DIG 30 OUTPUT @DIG;"*RST;TIM:MODE ASIN;RUN;"

The ASSIGN command is an HP BASIC command that creates an I/O path name and assigns that name to an I/O resource. In the example above, the I/O path name is address 7. (Note: all program examples in this manual assume that the digitizer is addressed at HP-IB address

707.)

The ASSlGN command offers several advantages when included in a digitizer program. For example, the digitizer address is easily changed in the computer program and the program can transfer data to a mass

storage unit.

The RESET command, *RST, presets all of the analog parameters of the digitizer and provides a good starting point for all measurement processes. Executing *RST is actually the same as executing a number of digitizer commands that set the digitizer to a known state.

“@DIG”

and is assigned to the device at HP-IB

The CLEAR command is an HP BASIC command that clears the input buffer, the output buffer, and the command parser of the specified instrument; that is, a device on HP-IB is “cleared” so that it is ready for operation. This command may be used to clear devices on the bus singly or in unison. It is often desirable to reset only one instrument so that other instruments on the bus are not affected.

To clear the digitizer, the “CLEAR @DIG” statement may be entered into the computer.

To clear all devices at select code 7, the “CLEAR 7” statement may be entered into the computer.

2-8

PROGRAMMING FUNDAMENTALS

This section describes and defines the status reporting structure used in the HP 70700A Digitizer. In general, the status data structure is used to “request service” or indicate a specific condition (e.g., operation complete) via SRQ (Service Request). This structure may be used to alert the user that certain events have occurred without the user’s actually initiating a request for this information. Refer to Figure 2-3 for a model of the status data structure.

Each of the integral parts of the status data structure are described below in more detail.

The Status Byte Register contains the device’s Status Byte (STB) summary messages, Request Service (RQS) messages, and Master Summary Status (MSS) messages. See Figure 2-4.

The Status Byte Register can be read with either a serial poll or the READ STATUS BYTE common query

(*STB?).

6 position depends on the method used.

Both of these methods read the status byte message identically. However, the value sent for the bit

When the Status Byte Register is read with a serial poll “SPOLL status byte message plus the single-bit RQS message to the

When the Status Byte Register is read with the *STB? common qu

byte message plus the single-bit MSS message as a single <NRI NUMERIC PROGRAM DATA> element. The response to *STB? is identical to the response to a serial poll except that the MSS summary message appears in the bit 6 position in place of the RQS message. The MSS summary message indicates that the device has at least one reason for requesting service.

Standard Event Status Bit (ESB) Summary Message

The ESB summary message is a defined message which appears in bit 5 of the Status Byte Register. Its state indicates whether or not one or more of the enabled events have occurred since the last reading or clearing of the Standard Event Status Register. Refer to Figure 2-3.

The ESB summary message is TRUE when an enabled event in the Standard Event Status Register is set TRUE. Conversely, the ESB summary message is FALSE when no enabled events are TRUE.

Message Available (MAV) Queue Summary Message

The MAV summary message is a defined message which appears in bit 4 of the Status Byte Register. The state of the message indicates whether or not the Output Queue is empty. Whenever the device is ready to accept a request by the controller to output data bytes, the MAV summary message shall be TRUE. The MAV summary message shall be FALSE when the Output Queue is empty. Refer to Figure 2-3.

controll

(@DIG)“, the device returns the seven-bit

er as a single data byte.

ery, the device returns the seven-bit status

2-9

PROGRAMMING FUNDAMENTALS

*ESR?

Standard

Status

*ESE

. . . . . . . . .

. ..**..a.

bbob*

, . . . . . . . .

l .

b b

b b b b

b b b

l l

. . . . . .

-J

. . . . . . . . .

. . . . . . . .

, . . . . . . . .

. . . . l . . . .

. . . . . . . . .

..*.

. . . . . . . . . . . . .

. . . . . . . .

7 6

.q..

. .

&RQS’ : I I

ESBMAV

,MSS

. . .

. . . . . . . .

..,............,.......

. .

3 2

*ESE?

1 0

Event!

Enable

<nrf>

Ser Ena

: i

Serial Poll

tatus egister

-read by

vice ble Register

output

Queue

read by

*STB?

*SRE

<nrf>

*SRE?

Byte

Request

2-10

Figure

2-3.

Status

Data

Structure

PROGRAMMING FUNDAMENTALS

The MAV summary message is used to synchronize information exchange with the controller. The controller can, for example, send a query command to the device and then wait for MAV to become TRUE. The system bus is available for other use while an application program is waiting for a device to respond. If an application program begins a read operation of the Output Queue without first checking for MAV, all system bus activity is held up until the device responds.

NOTE

Bits 0 through 3 and bit 7 are not used at this time.

- - - w w SUMMARY - - - w - -

0107

Clearing the Status Byte Register

STATUS

MESSAGES

RQS

ES6

MSS

MAV

0106

0105

3 2

0104

0103

Figure 2-4. Status Byte Register

The CLEAR STATUS

(*CLS)

common command causes the Event Registers and Queues of the status data structure to be cleared so that the corresponding summary messages are clear. The Output Queue and its MAV summary message are an exception and are unaffected by

*CLS.

SERVICE REQUEST ENABLE REGISTER

The Service Request Enable Register is an eight-bit register that can be used by the programmer to select which summary messages in the Status Byte Register may cause service requests. The programmer may select reasons for the device to issue a service request by altering the contents of the Service Request Enable Register. Refer to Figure 2-5.

PROGRAMMING- FUNDAMENTALS

w--N

STATUS

SUMMARY - -

MESSAGES

..,....

........

................

........................

l ,ObO

)

RQS

MSS,

ESB

,, Y

7x5432

MAV

(

. .

3erial

Status

Resister

l **

Service Enable

read by

rkad

*STB?

Regi’st

*SRE

*SRE?

Pol I

Byt

Request

<nrf>

Figure 2-5. Service Request Enable Register

Reading/Writing the Service Request Enable Register

The Service Request Enable Register is read with the SERVICE REQUEST ENABLE (*SRE?) common query. The response message to this query is a represents the sum of the binary-weighted values of the Service Request Enable Register (2 raised to the power of the bit number). The value of unused bit 6 is always zero.

The Service Request Enable Register is written to with the SERVICE REQUEST ENABLE command followed by a <DECIMAL NUMERIC PROGRAM DATA> element. The <DECIMAL NUMERIC PROGRAM DATA>, when rounded to an integer value and expressed in base two (binary), represents the bit values of the Service Request Enable Register. A bit value of one indicates an enabled condition. A bit value of zero indicates a disabled condition.

The device always ignores the value of bit 6.

2-12

<NRl

NOTE

NUMERIC PROGRAM DATA> element that

(*SRE)

common

PROGRAMMING FUNDAMENTALS

Service Request Generation

The Service Request function provides the device with the ability to request service from the controller via the Service Request interface (SRQ, a line on HP-IB), and report that it has requested service via the Request Service message (RQS, bit 6 of the Status Byte Register).

The generation of service requests ensures that the device shall:

1. Assert an SRQ when a previously “enabled” condition occurs.

2. Keep SRQ asserted until the controller has recognized the service request and polled the device, or has taken specific action to cancel the request (e.g., *CLS command).

3. Release SRQ when polled so that the controller can detect an SRQ from another device.

4. Assert an SRQ again if another condition occurs, whether or not the controller has cleared the first

condition. If the previous condition has not been cleared, the next condition must be different than the first for an SRQ to be asserted again.

Whenever the contents of the Status Byte Register or the Service Request Enable Register are changed, the

device must determine whether the change affects the service request state of the device. Device status

transitions do not affect the state of the SRQ interface directly. Instead, changes to the Status Byte Register and the Service Request Enable Register generate two local messages which either assert (Request Service TRUE) or unassert (Request Service FALSE) the hardware.

The device shall generate a new service request (assert Request Service TRUE) when:

1. A bit in the Status Byte Register changes from FALSE to TRUE while the corresponding bit in the Service Request Enable Register is TRUE.

2. A bit in the Service Request Enable Register changes from FALSE to TRUE corresponding bit in the Status Byte Register is TRUE.

3. A bit in the Status Byte Register changes from FALSE to TRUE and the corresponding bit Service Request Enable Register changes from FALSE to TRUE simultaneously.

In general, the controller application program must never assume that an SRQ indicates that a new Il eason for service has occurred, but only that it may have occurred. The application program should check the device Status Byte Register to determine whether it is indeed the case that a new reason for service exists.

Clearing the Service Request Enable Register

The SERVICE REQUEST ENABLE (*SRE) common command followed with a <DECIMAL NUMERIC

PROGRAM DATA> element value of zero clears the Service Request Enable Register. A cleared register does not allow status information to generate a hardware Request Service message; thus, no service requests are issued.

whil

e the in the

The Standard Event Status Register structure has specific, defined events assigned to specific bits. Refer to Figure 2-6.

2-13

PROGRAMMING FUNDAMENTALS

Sumary

Event

(BIT 5 OF STATUS BYTE REGISTER)

Sumary

Message

Bit

(ESB)

Standard

Status

*ESR?

Standard

Status

*ESE <nrf>

*ESE?

Enable

Event

Figure 2-6.

Bits 7 through

Bit 7 - Power On (PON) This event bit indicates that an off-to-on transition has occurred in the power

supply of the device.

Bit 6 - User Request

Bit 5 - Command Error (CME)

1. A syntax error (controller-to-device message) has been detected. element which violates the device listening formats or whose type is unacceptable to the device.

2-14

(URQ)

This event bit is not used at this time.

This event bit indicates that one of the following events has occurred:

Sfmdard

.Ehent

Status Register

Possible errors include a data

PROGRAMMING FUNDAMENTALS

2. A semantic error has occurred, indicating that an unrecognized header was received. Unrecognized headers include incorrect device-dependent headers and incorrect or unimplemented common

commands.

3. A Group Execute Trigger (GET) was entered into the Input Buffer inside of a <PROGRAM MESSAGE>. A GET message is a controller-to-device message defined as an addressed command.

The Command Error bit is not set to report any other device-dependent condition. Events that are reported as Command Errors are not reported as Execution Errors, Query Errors, or Device-Dependent Errors. Refer to the appropriate bit definitions for more information.

Bit 4 - Execution Error (EXE) This event bit indicates that:

1. A <PROGRAM DATA> element following a header was evaluated by the device as outside of its

legal input range, or is otherwise inconsistent with the capabilities of the device.

2. A valid program message could not be properly executed due to some device condition.

Following an Execution Error, the device continues to process the input stream.

Execution Errors are reported by the device after rounding and expression-evaluation operations have taken place, For example, rounding a numeric data element is not reported as an Execution Error.

Events that generate Execution Errors do not generate Command Errors, Query Errors, or Device-Dependent Errors. Refer to the appropriate bit definitions for more information.

Bit 3 - Device-Dependent Error (DDE) This event bit indicates that an error has occurred which is neither

a Command Error, a Query Error, nor an Execution Error. A Device-Dependent Error is any executed device operation that was not properly completed due to

some condition, such as overrange.

Following a Device-Dependent Error, the device continues to process the input stream.

Events that generate Device-Dependent Errors do not generate Command Errors, Query Errors, or Execution Errors. Refer to the appropriate bit definitions for more information.

Bit 2 - Query Error (QYE) This event bit indicates that:

1. An attempt is being made to read data from the Output Queue when no output is either present or pending.

2. Data in the Output Queue has been lost.

The Query Error bit is not set to report any other condition. Events that generate Query Errors do not generate Execution Errors, Command Errors, or Device-Dependent Errors.

Bit 1 -Request Control (RQC) This event bit is not used at this time. Bit 0 -Operation Complete (OPC) This event bit responds to the OPERATION COMPLETE (*OPC)

common command. It indicates that the device has completed any pending operations and that the parser is ready to accept more program messages. The parser is the logical portion of the device which takes Data Byte Messages, END messages, and hardware Group Execute Trigger messages from the Input Buffer and analyzes them by separating out the

\;;lrious

syntactic elements.

PROGRAMMING FUNDAMENTALS

Reading/Writing the Standard Event Status Register

The Standard Event Status Register is destructively read (that is, read and cleared) with the STANDARD EVENT STATUS REGISTER common query (*ESR?).

The Standard Event Status Register cannot be written to remotely.

Clearing the Standard Event Status Register

The Standard Event Status Register shall only be cleared by:

1. A CLEAR STATUS common command

2. A power-on sequence which initially clears the Standard Event Status Register then records any subsequent events during the power-on sequence of the device, including setting the PON event bit

(bit 7).

(*CLS).

STANDARD EVENT STATUS ENABLE REGISTER

The Standard Event Status Enable Register allows one or more events in the Standard Event Status Register to be reflected in the ESB summary-message bit (bit 5 of the Status Byte Register). This register is defined for eight bits, each corresponding to the

Reading/Writing the Standard Event Status Enable Register

The Standard Event Status Enable Register is read with the STANDARD EVENT STATUS ENABLE common query

The Standard Event Status Enable Register is written to by the STANDARD common command

Clearing the Standard Event Status Enable Register

(“ESE?).

(*ESE).

Data is returned as a binary-weighted <NRI NUMERIC RESPONSE DATA>.

Data is encoded as <DECIMAL NUMERIC PROGRAM DATA>.

bits

in the Standard Event Status Register. Refer to Figure 2-6.

EVE’NT

STATUS ENABLE

The Standard Event Status Enable Register shall be cleared by the following:

1. Sending the

2. A power-on event.

The Standard Event Status Enable Register is specifically not affected by the RESET common command

(*RST).

*ESE

common command with a data value of zero.

OUTPUT QUEUE

The Output Queue stores response messages until they are read. The availability of the output is summarized by the Message Available (MAV) summary message (bit 4 of the Status Byte Register). The MAV summary message is used to synchronize information exchange with the controller. Refer to Figure 2-7

2-16

PROGRA.MMING

FUNDAMENTALS

Queue

Non-Empty

. .

Sumnary

Message

Message Available (MAV)

(BIT 4 OF STATUS BYTE REGISTER)

Last IIota

Byte Entered

Next Data

Byte Entered

First Data

Byte Entered

output

Queue

Lost Data Byte

to be Read

First Data Byte

to be Read

Figure 2-7. Output Queue

The Response Formatter places Data Byte Messages and END messages into the Output Queue in response to query commands. These bytes are removed from the Output Queue as they are read by the controller. As long as the Output Queue contains one or more bytes, MAV is TRUE.

The Output Queue is cleared upon power-on, Device Clear Active State Message (dcas), or the RESET

(*RST)

common command, without causing a Query Error. A Query Error is generated if the contents of

the Output Queue are discarded for any other reason.

2-17

PROGRAMMING FUNDAMENTALS

SYNCHRONIZATION OF EVENTS AND COMMANDS

This section describes techniques which may be used to ensure synchronization between events and commands, which in turn ensures valid measurements.

A potential problem with commands that take appreciable time to finish is that the application program needs to know when the commands have finished; therefore, to make measurements remotely, the controller must know when trace data is available to the digitizer before making a measurement. This potential problem can be avoided by using synchronization commands that instruct the module to wait until a measurement is finished before making any other measurements.

For example, consider a data-logging device which is commanded to take a measurement with the -RUN command and then to make a frequency measurement using MEAS:FREQ?. The RUN command is a command that allows execution of subsequent commands while the device operations initiated by the RUN command are still in progress. The RUN command therefore takes appreciable time to perform. Figure 2-8 shows a timing diagram of this operation without the use of a synchronization command.

It should be noted that, without the use of a synchronization command, the RUN command is still in progress when the FREQUENCY measurement is initiated. If the RUN command has not completed its operation, any data used to make other measurements (e.g., FREQUENCY) while the RUN command is still in progress may be invalid. Only after an operation has been completed can the data be assumed to be valid.

Operation in Progress

Operation

Complete

RUN

MEAS:FREQ?

RUN Pending-Operation flag

No-Operation-Pending flag

Figure 2-8. Timing Diagram Without A Synchronization Command

Figure It should be noted that, with the use of a synchronization command, the RUN command has completed its

2-9

illustrates the same example as described above except that a synchronization command is used.

2-18

PROGRAMMING FUNDAMENTALS

operation before the FREQUENCY measurement is initiated; therefore, the data used to make the FREQUENCY measurement is valid.

Operation

RUN

SYNCHRONIZATION

RUN Pending-Operation flag

t f

No-Operation-Pending flag t

Figure 2-9. Timing Diagram Using A Synchronization Command

in Progress

COMMAND

MEAS:FREQ?

Operation

Complete

The following example HP BASIC statements illustrate the general sequence that should be followed when making measurements via remote control.

1. OUTPUT @DIG;“*RST;TIM:MODE ASIN;...”

RESET the module, put it into SINGLE SWEEP mode, then set up all desired parameters (e.g., voltage range, time range, etc.).

2. OUTPUT

Invoke a sweep. (In SINGLE SWEEP mode, a single measurement will be taken.)

3. SYNCHRONIZATION COMMAND

Use a synchronization command to allow the module to complete one operation before starting another. Refer to Synchronization Commands below for more detailed information on the three forms of synchronization commands that are available.

4. OUTPUT

Ask for and enter measurement data.

@DIG;“RUN”

@DIG;“MEAS:SOUR

CHAN

I;FREQ?”

ENTER @DIG;Frequency

2-19

PROGRAMMING FUNDAMENTALS

SYNCHRONIZATION COMMANDS

There are three forms of synchronization commands that can be used in the general sequence for remote measurements listed above. The three forms are listed and described below.

Wait-To-Continue

complete. If using triggered sweeps, this command may cause the bus to “wait” indefinitely if the trigger does not occur.

Operation Complete (*OPC) This command instructs the module to send a status data structure when all operations are complete. Similar to the may result in the bus’s waiting indefinitely for an event to occur.

Assert

after the *OPC command is received, the module is to assert SRQ when all operations are complete. This

method has the advantage of the HP-IB’s never being in a state where it is waiting indefinitely. The

sequence of commands for this synchronization method is:

SRQ

(Service Request) This form of synchronization uses a sequence of commands indicating that

OUTPUT OUTPUT OUTPUT

REPEAT UNTIL

(“WAI)

This command instructs the module to not use the bus until all operations are

“1”

to the Output Queue of the

*WA1

command, the *OPC command

@DIG;"*ESE

@DIG;"*SRE

1;”

32;”

! This command only needs to be sent once ! This command only needs to be sent once

@DIG;“*CLS;*OPC;”

BIT

(6,SPOLL

“All

operations complete” is defined as: 1) there is no trace in progress, including reading trace data (which is NOT the same as trace complete, since a trace may not have been started); and 2) all remote commands have been parsed and processed.

(dig))=1

2-20

Because reading trace data is an operation, the synchronization commands should not be used after the request of trace data

WARDATA?;

synchronization commands are used, the system may be placed in a state where it is “waiting” indefinitely. In this state, the digitizer system waits for the data to be read, and the computer waits for all operations to be completed.

or DIG CHANl;) until all data has been read. If the

(emgm,

PROGRAMMING FUNDAMENTALS

DATA TRANSFER

The HP 70700A Digitizer represents trace data and non-trace data differently. For non-trace data, the digitizer will send information back in ASCII character code as either text or numeric data. As an example

of ASCII text, the Timebase REFERENCE query (TIM:REF?) returns LEFTKENTIRIGH as a response. As an example of ASCII numeric data, the Timebase RANGE query (TIM:RANG?) returns a value X.XXEXX as a response.

NOTE

Some numeric responses are integers (i.e., they have no decimal point or exponent).

For trace data, the digitizer currently supports only The trace data is preceded by a header to indicate that binary data is about to be received. The header is

%O”,

which indicates indeterminate length binary data. When using the digitizer via HP-IB, the last data byte

will have the EOI (END OR INTERRUPT) status line asserted with it.

Listed below is an HP BASIC example program that reads trace data from the digitizer.

OUTPUT ENTER @DIG USING FOR

@DIG;"WAV:DATA?"

"#,2A",Header$

J=l

TO Points

ENTER @DIG USING

"#,W";Value(J)

160bit

binary transfers

! Request trace data. ! Read the header.

! Read each point.

(MSByte

first, LSByte second).

2-21,

PROGRAMMING FUNDAMENTALS

MULTIPLE DIGITIZER REMOTE

SLAVING PROCEDURE

A digitizer system, consisting of one to eight modules, may be remotely controlled or “slaved” via a computer. In this mode of operation, the computer functions as the “master” or controlling device and each channel is essentially a slave. This allows more than four channels as well as provides features not accessible through a normal four-channel digitizer system (e.g., a different timebase for each channel). Also in this mode of operation, one digitizer module must still be designated as the reference channel which controls the triggering of all the digitizer channels. More than one digitizer

module for each designated digitizer system can control the triggering in a slaved digitizer system that is remotely controlled. For example, two four-channel digitizer systems may reside in the same mainframe. However, one channel in each system must be designated as the reference channel for triggering the other three channels.

The commands used to effect this mode of operation are:

TRIG:SOUR SLAV

MCABT MCSET MCSNC MCARM MCINF MCTRG MCREC

sy.~rn

is also possible, but only one

The “MC” in these command mnemonics stands for “multiple channel”. The remainder of this section explains how these commands are used in multiple-channel digitizing.

These “multiple channel” commands differ from the other digitizer commands in that they must be employed strictly in a particular sequence. Each step in this sequence must be completed in the module

before continuing, The OPC (Operation Complete) bit in the Standard Event Status Register is used to indicate the completion of a step. Corresponding lines of program code from an example HP BASIC program (listed at the end of this section) are shown in each step of the procedure for example purposes. It is not intended that these lines of program code be used by themselves, but that they may be used as part of the whole program example listed at the end of this section.

CAUTION

The commands described in this section must be used exactly as presented. Misuse of these commands may put the modules into a state that can only be recovered from by cycling power.

The first three steps of the procedure are a sequence for slaving multiple modules to the controller (i.e., one module is designated as the reference channel for the other modules), and must be performed only once when the system is initialized. The remaining steps allow the user to set up measurement parameters, and synchronize and trigger the system to obtain the sampled data.

2-22

PROGRAMMING FUNDAMENTALS

1. Configure the address switches of the modules and properly install the cabling. The cabling for this mode is the same as for a normal multiple-channel digitizer system. The CLOCK OUT of the reference

channel is connected to the CLOCK IN of all the other channels. The SYNC OUT of the reference channel is connected to the EXT TRIG of ail the other channels.

NOTE

Each module needs a unique individually; therefore, the address of each module must be configured in row 0 and at a different column address.

2. Reset all modules, stop all modules from making measurements (allowing the computer to perform the appropriate setup), and put all modules in SINGLE SWEEP mode (which is required since the computer must perform operations between sweeps):

REFERENCE CHANNEL:

OTHER CHANNELS:

Program line examples:

OUTPUT OUTPUT Khans;

3. Use this command sequence to inform the channels that they are being controlled from an external source:

Program line example:

@Ref;

OTHER CHANNELS: TRIG:SOUR SLAV;

"*RST;STOP;TIM:MODE

'*RST;STOP;TIM:MODE

*RST;STOP;TIM:MODE *RST;STOP;TIM:MODE

HP-IB

address so that it may be accessed

ASINISING;

SING;

ASIN;*WAI;”

SING;*WAI;’

OUTPUT

4. In this step, each module is set up with the desired measurement parameters (e.g., VOLTS/DIVISION, SECONDS/DIVISION, etc.):

@Chans;"TRIG:SOUR

SLAV;"

NOTE

If the timebase settings are not the same on all channels, then only simple digitizing can be performed. Random Event Capture (REC), interpolation, and other features are not available in this case. System operation is not guaranteed if different timebase settings are used.

REFERENCE CHANNEL/CHANNELS:

set up parameters (only have changed from the previous measurement need to be sent)

p.arameters

that

2-23

PROGRAMMING FUNDAMENTALS

Program line examples:

N=200

OUTPUT OUTPUT OUTPUT Khan2;"CHANl:RANG

5. Use this command sequence only if using REC or aborting a trace that is waiting for a trigger:

@Ref;"CHANl:RANG 2.0V;TIM:RANG 10us;ACQ:POIN";N @Chanl;"CHANl:RANG 2.0V;TIM:RANG 10us;ACQ:POIN";N

3.0V;TIM:RANG

10us;ACQ:P01N”;N

NOTE

Most of the multi-channe

REFERENCE CHANNEL/CHANNE

The OPC bit in the Standard Event Status Register is set at this time. Do not use the *OPC or commands; they will not function as expected.

6. In this step, the reference channel sets its hardware to take a measurement. This is the first step in synchronizing all the other channels with the reference channel. (The trigger for the measurement is not armed at this time.):

REFERENCE CHANNEL: *CLS;MCSET;

The OPC bit in the Standard Event, Status Register is set at this time. Do not use the *OPC or commands; they will not function as expected.

Program line example:

OUTPUT

7. In this step, all channels set their hardware to take a measurement and are ready to be synchronized with the reference channel:

@Ref;"*CLS;MCSET;"

system commands begin with the letters

*CLS;MCABT;

“MC”.

*WA1

OTHER CHANNELS: *CLS;MCSET;

The OPC bit in the Standard Event Status Register is set at this time. Do not use the *OPC or commands; they will not function as expected.

Program line example:

OUTPUT

8. In this step, the reference channel completes its synchronization with the other channels:

REFERENCE CHANNEL: *CLS;MCSNC;

2-24

@Chans;"*CLS;MCSET;"

*WA1

PROGRAMMING FUNDAMENTALS

The OPC bit in the Standard Event Status Register is set at this time. Do not use the *OPC or commands; they will not function as expected.

Program line example:

OUTPUT

9. The digitizer action for all channels, except the reference channel, is armed at this time. It should be noted that since the triggering is performed through the reference channel, the digitizer action is still

effectively unarmed:

OTHER CHANNELS:

The OPC bit in the Standard Event Status Register is set at this time. Do not use the *OPC or commands; they will not function as expected.

Program line example:

OUTPUT

10. The trace acquisition for the reference channel is armed at this time. At this point, when the trigger

condition is satisfied, a measurement will be made:

@Ref;"*CLS;MCSNC;"

*CLS;MCARM;

@Chans;"*CLS;MCARM;"

*WAI

*WA1

REFERENCE CHANNEL: *CLS;MCARM;

Step 10 should be carried out soon enough after step 9 so that the triggers armed in step 9 do not “time out”. If necessary, lengthen the time-out times using the TRIG:TOUT command.

The OPC bit in the Standard Event Status Register is set at this time. Do not use the *OPC or

commands; they will not function as expected.

Program line example:

OUTPUT

I I. The sampled data for the reference channel is available at this time. It can be obtained as follows:

REFERENCE CHANNEL: WAV:DATA?

The

*OPC

Program line examples:

OUTPUT OUTPUT

ENTER For J=O TO N-l

NEXT J

@Ref;"*CLS;MCARM;"

*WA1

commands may be used at this time.

@Ref;"*WAI;" @Ref;"WAV:DATA?"

@Ref

ENTER

USING

@Ref

"#,2A";A$

USING

"#,W";Value

*WA1

2-25

PROGRAMMING FUNDAMENTALS

12. When using REC mode, use the following command sequence to transfer information from the reference channel to the other channels:

REFERENCE CHANNEL: MCINF?

ENTER

@Ref;Datl,Dd2,Dat3,Dat4

OTHER CHANNELS:

The command form “MCINF Datl,Dat2,Dat3,Dat4” sets the OPC bit in the Standard Event Status Register at this time. Do not use the

Program line examples:

OUTPUT ENTER

OUTPUT Khans;

13. If interpolation is on, indicated by an remotely, information about the trigger must be transferred from the reference channel to the other

channels. If interpolation is off, this command form is effectively a no-operation instruction (i.e., it may or may not be used).

REFERENCE CHANNEL: MCTRG?

@Ref;"MCINF?"

@Ref; Datl,Dat2,Dat3,Dat4

OTHER CHANNELS:

*OPC

"*CLS;MCINF";Datl,Dat2,Dat3,Dat4

*CLS;MCINF

*WA1

commands; they will not function as expected,

ENTER. @Ref;Trigger

MCTRG Trigger point

Datl,Dat2,Dat3,Dat4

“i”

appearing on the display screen or querying the system

point

If the other channels (not the reference channel) have a link with a display Instrument, the channel does not walt for this command before drawing Its trace to the display screen. As a result, there may be up to 50 ns of “jitter” in the data of the channel, resulting from a lack of trigger timing Information. The data acquired by the computer will be correct (i.e., it will not necessarily match the data on the display screen).

Program line examples:

OUTPUT

ENTER @Ref;Temp

OUTPUT

14. The sampled data from all the other channels (not the reference channel) is available at this time. It should be noted that each channel must be addressed individually.

OTHER CHANNELS: WAV:DATA?

The

*OPC

@Ref;"MCTRG?" @Chans;"MCTRG";Temp

*WA1

commands may be used at this time.

Program line examples:

PROGRAMMING FUNDAMENTALS

OUTPUT OUTPUT

ENTER

FOR NEXT OUTPUT

OUTPUT ENTER Khan2 USING FOR

A sample HP BASIC program utilizing the remote slaving procedure is provided at the end of this section.

@Chanl;"*WAI;" @Chanl;"WAV:DATA?"

Khan1

J=O

ENTER

USING

TO N-l

Khan1

USING

@Chan2;"*WAI;" @Chan2;"WAV:DATA?"

J=O

N-l

ENTER

Khan2

USING

(repeat for each channel)

"#,2A";A$

"#o,W";Value

"#,2A";A$

"#,W";Value

2-27

PROGRAMMING FUNDAMENTALS

STEP 1

STEP 2

STEP 3

STEP 4

RESET MODULES, STOP MODULES FROM MAKING

REFERENCE

CHANNEL

CONFIGURE AND

INSTALL MODULES

MEASUREMENTS, AND PUT MODULES IN

SINGLE SWEEP

TRlG:SOUR

EXTERNAL SOURCE IS

CONTROLL-ING CHANNELS

SET UP

PARAMETERS

OTHER

CHANNELS

SLAV;

STEP 5

STEP 6

STEP 7

STEP

*CLS;MCABT;

USE IF USING REC OR

ABORTING A TRACE THAT

IS WAITING FOR A TRIGGER

*CLS;MCSET;

SETS UP HARDWARE

*CLS;MCSNC;

COMPLETES SYNCHRONIZATION

WITH OTHER CHANNELS

*CLS;MCABT;

USE IF USING REC OR

ABORTING A TRACE THAT

IS WAITING FOR A TRIGGER

*CLS;MCSET;

SETS UP HARDWARE AND IS

READY TO BE SYNCHRONIZED

WITH REFERENCE CHANNEL

2-28

Figure

2-10.

Remote Slaving Proceclure Diagram (1 of 2)

PROGRAMMING FUNDAMENTALS

STEP 9

STEP 10

STEP 11

STEP 12

*CLS;MCARM;*CLS;MCARM;

ARMS CHANNELARMS CHANNEL

WAV: DATA?

SAMPLE DATASAMPLE DATA

AVA I LABLEAVA I LABLE

MCINF? ENTER @Ref;Datl,Dat2, Dat3,Dat4

IF USING REC, TRANSFERS

INFORMATION TO OTHER CHANNELS

*CLS;MCARM;

ARMS CHANNEL

*CLS;MCINF

Datl,Dat2,

Dat3,Dat4

IF USING REC, TRANSFERS

INFORMATION FROM REFERENCE

CHANNEL

STEP 13

STEP 14

MCTRG? ENTER @Ref;Trigger-point

IF INTERPOLATION IS ON,

TRIGGER

TRANSFERRED TO OTHER CHANNELS

Figure

JNFORMATION

2-l

0. Remote Slaving Procedure Diagram (2 of 2)

MUST BE

MCTRG Trigger-point

IF INTERPOLATION IS ON,

TRANSFERS TRIGGER INFORMATION

FROM REFERENCE CHANNEL

WAV: DATA?

SAMPLE DATA

AVA I LABLE

2-29

PROGRAMMING FUNDAMlENTALS

EXAMPLE PROGRAM

20 30 40 50 60 70

90 100 110 120

130 140 150 160 170 180 190

200

210 220 230 240 250 260 270 280

290 300 310 320 330 340 350

360 370 380 390 400 410 420 430 440 450 460

470 480 490

500

ASSIGN ASSIGN ASSIGN Khan1

ASSIGN @Chan2 TO 706

STEP 2

OUTPUT @Ref;"*

OUTPUT @Chans;

@Ref TO 707

@Chans

TO 705,706

TO 705

RST;STOP;TIM:MODE

"*RST;STOP;TIM:MODE

ASIN;*WAI;"

SING;*WAI;"

STEP 3

i)UTPUT @Chans;"TRIG:SOUR

STEP 4

SLAV;"

Ii=200

OUTPUT OUTPUT OUTPUT Khan2;"CHANl:RANG

STEP 5

i *

only used for REC or aborting trace waiting for trigger

STEP 6

i)UTPUT @Ref;"*CLS;MCSET;"

STEP 7

~ITPUT @Chans;"*CLS;MCSET;"

STEP 8

OUTPUT @Ref;"*CLS;MCSNC;"

STEP 9

bUTPUT @Chans;"*CLS;MCARM;"

STEP

~JTPUT @Ref;"*CLS;MCARM;"

STEP

Graph(O,N,N/10,0,4096,512,"REMOTE

OUTPUT @Ref OUTPUT

@Ref;"CHANl:RANG @Chanl;"CHANl:RANG

;“*WAI;”

@Ref;"WAV:DATA?"

2.0V;TIM:RANG 1OUS;ACQ:POIN

3.0V;TIM:RANG

SLAVED

10US;ACQ:POIN

DIGs","time","ampl",3)

“;N

“;N “;N

2-30

510 520

530 540 550 560 570 580 590 600 610

620 630 640 650 660 670 680 690 700 710 720 730

740 750 760 770 780 790

800 810 820 830 840 850 860 870 880 890 900

910 920 930 940 950 960 970 980 990

1000

1010

1020

1030

PROGRAMMING FUNDAMENTALS

ENTER

MOVE

FOR

@Ref

USING

-100,O

J=O

N-l

ENTER

DRAW J,Value

@Ref

USING

"#,2A";A$

"#,W";Value

STEP 12

I i *

only used for REC

STEP 13

OUTPUT @Ref;"MCTRG?"

ENTER @Ref;Temp

OUTPUT

STEP 14 (repeat for each channel)

OUTPUT Khan1

MOVE OUTPUT

ENTER FOR

buTpuT @Chan2;"*WAI;"

MOVE OUTPUT ENTER Khan2 USING FOR

END

I I

This portion of the program example listed below is used to set

! up the display screen and is not part of the slaving process.

SUB Graph(Xmin,Xmax,Xstep,Ymin,Ymax,Ystep,Title$,Xaxis$,Yaxis,Plotdev)

@Chans;"MCTRG";Temp

;“*WAI;”

-100,O

@Chanl;"WAV:DATA?"

@Chanl

J=O

ENTER

DRAW J,Value

N-l

Khan1

USING

-100)

@Chan2;"WAV:DATA?"

J=O

N-l

ENTER Khan2 USING

DRAW

J,Value

GINIT

Plotdev<>3

PLOTTER

END

PEN 4 GRAPHICS ON

Dx=Xmax-Xmin

Dy=Ymax-Ymin WINDOW

LINE TYPE

Xmin-.1*Dx,Xmaxt.l*Dx,Ymin~.l5*Dy,Ymaxt.l*Dy

THEN

"#,2A";A$

"#,W";Value

"#,2A";A$

"#,W";Value

Plotdev,."HPGL"

2-31

PROGRAMMING FUNDAMENTALS

1040 1050

1060 1070 1080 1090 1100 1110 1120 1130

1140 1150 1160 1170

1180 1190 1200 1210 1220 1230 1240 1250

1260 1270 1280 1290 1300 1310

CSIZE 3

LORG 5

LDIR -PI/2

MOVE LABEL Yaxis$ LDIR 0

MOVE

LABEL Xaxis$

MOVE

LABEL

X=Xmin

WHILE

END WHILE Y=Ymin WHILE

END WHILE

CLIP

Plotdev=3

GRID LINE

PEN

SUBEND

Xmaxt.O25*Dx,YmintDy/2

XmintDx/2,Ymin-.075*Dy XmintDx/2,Ymaxt.O5*Dy

Title$

X<Xmax MOVE X,Ymin-.025*Dy

LABEL X

X=DROUND(XtXstep,8)

Y<Ymax

MOVE Xmin-.025*Dx,Y

LABEL Y

Y=DROUND(YtYstep,8)

Xniin,Xmax,Ymin,Ymax

THEN LINE TYPE 4

Xstep,Ystep,Xmin,Ymin

TYPE 1

REMOTE

This section describes how the Random Event Capture (REC) mode can be used in the Multiple Digitizer Remote Slaving Procedure. The procedure shown below parallels the procedure in the previous section, but this procedure must be used when using REC. The two major differences in the procedures are that I) an additional command, MCREC, has been added; and 2) steps 6 and 7 of the previous procedure are reversed. A Remote Slaving Diagram using REC is provided, as well as another HP BASIC example program.

1. Configure the address switches of the modules and install the cabling properly.

2. Use the following command sequence:

3. Use the following command sequence:

4. Use the following command sequence:

SLAVING PROCEDURE FOR RANDOM

REFERENCE CHANNEL:

OTHER CHANNELS:

OTHER CHANNELS: TRIG:SOUR SLAV;

REFERENCE CHANNEL/CHANNELS:

*RST;STOP;TIM:MODE *RST;STOP;TIM:MODE

set up measurement parameters.

EVENT

ASINISING;

SING;

CAPTURE

2-32

PROGRAMMING FUNDAMENTALS

5. Use this command sequence only if aborting a trace that is waiting for a trigger.

REFERENCE CHANNEL/CHANNELS: *CLS;MCABT;

NOTE

The order of steps 6 and 7 is reversed in this procedure.

6. All channels set their hardware to take a measurement and are ready to be synchronized with the reference channel:

OTHER CHANNELS: *CLS;MCSET;

7. The reference channel sets its hardware to take a measurement:

REFERENCE CHANNEL: *CLS;MCSET;

8. This command sequence is not required when using REC, but may be used if desired.

REFERENCE CHANNEL: *CLS;MCSNC;

9. Use the following command sequence:

OTHER CHANNELS: *CLS;MCARM;

10.

Use the following command sequence:

REFERENCE CHANNEL: *CLS;MCARM;

11. In this step, the trigger event is selected and the REC algorithm is applied to the reference channel.

REFERENCE CHANNEL: TIM:EVEN Event

MCREC;

The *OPC or

Program line examples:

12. Use the following command sequence:

*WA1

commands may be used at this time.

OUTPUT OUTPUT

REFERENCE CHANNEL: WAV:DATA?

@Ref;"TIM:EVEN";Event

BRef;"MCREC;"

13. Use the following command sequence:

REFERENCE CHANNEL: MCINF?

OTHER CHANNELS:

ENTER

*CLS*MCINF Datl,Dat2,Dat3,Dat4

@Ref;Datl,Dat2,Dat3,Dat4

2-33

PROGRAMMING FUNDAMENTALS

NOTE

Interpolation is not applicable for MCTRG command should not be used.

14. Use the following command sequence:

OTHER CHANNELS: WAV:DATA?

REC

mode at this time; therefore, the

2-34

PROGiiAMMJNG

FUNDAMENTALS

STEP 1

STEP 2

STEP 3

STEP 4

RESET MODULES, STOP MODULES FROM MAKING

REFERENCE

CHANNEL

PARAMETERS

CONFIGURE AND

INSTALL MODULES

MEASUREMENTS, AND PUT MODULES IN

SINGLE SWEEP

TRlG:SOUR

EXTERNAL SOURCE IS

CONTROLLING CHANNELS

SET UP

PARAMETERS

CHANNELS

SET UP

OTHER

SLAV;

STEP 5

STEP 6

STEP 7

STEP 8

*CLS;MCABT;

USE IF ABORTING A TRACE

THAT IS WAITING FOR

A TRIGGER

*CLS;MCSET;

SETS UP HARDWARE

*CLS;MCSNC;

COMPLETES SYNCHRONIZATION

WITH OTHER CHANNELS

*CLS;MCABT;

USE IF ABORTING A TRACE

THAT IS WAITING FOR

A TRIGGER

*CLS;MCSET;*

SETS UP HARDWARE AND IS

READY TO BE SYNCHRONIZED

WITH REFERENCE CHANNEL

Figure

2-l

1. Remote Slaving Procedure Diagram for Random Event Capture (1 of 2)

2-35

PROGRAMMING FUNDAM.ENTALS

STEP 9

STEP 10

STEP 11

STEP 12

*CLS;MCARM;

ARMS CHANNEL

TlM:EVEN

Event

MCREC ;

TRIGGER EVENT IS SELECTED AND REC ALGORITHM APPLIED

WAV: DATA?

SAMPLE DATA

AVA I LABLE

*CLS;MCARM;

ARMS CHANNEL

STEP 13

STEP 14

MCINF? ENTER @Ref;Datl,Dat2,

Dat3,Dat4

IF USING REC, TRANSFERS

INFORMATION TO OTHER CHANNELS

*FOR NEXT EVENT,RETURN TO STEP 11.

(REFER To THE

Figure 2-11. Remote Slaving Procedure Diagram for

FOLLOWING

PROGRAM EXAMPLE.)

*CLS;MClNF

Datl,Dat2,

Dat3,Dat4

IF USING REC, TRANSFERS

INFORMATION FROM REFERENCE

CHANNEL

WAV: DATA?

SAMPLE DATA

AVA I CABLE

.Rorndom

Event Capture (2 of 2)

2-36

. EXAMPLE PROGRAM FOR RANDOM EVENT CAPTURE

PROGRAMMING FUNDAMENTALS

20 30 40 50

80 90

100

110 120 130 140 150

160 170 180 190

200 210 220 230

240 250 260 270 280 290

300 310 320 330 340 350

360 370 380 380 390 400 410 420 430 440 450 460 470 480 490 500

ASSIGN ASSIGN @Chans

ASSIGN Khan1

STEP 2

@Ref TO 715

TO 708

~TPuT @Ref;"*

OUTPUT

STEP 3

bUTPUT

STEP 4

Khans;

@Chans;“TRIG:SOUR

RST;STOP;TIM:MODE ASIN;SAMP REC;*WAI;*ESE

‘*RST;STOP;TIM:MODE

SLAV;"

SING;SAMP REC;*WAI;*ESE

i=200

OUTPUT OUTPUT

@Ref;“CHANl:RANG 2.0V;TIM:RANG

@Chanl;‘CHANl:RAN 2.0V;TIM:RANG

100US;ACQ:POINT

100US;ACQ:POIN

STEP 5

use only for aborting a trace waiting for a trigger

STEP 6

bUTPUT @Chans;"*CLS;MCSET;"

I i

STEP 7

&TPUT @Ref;"*CLS;MCSET;"

STEP 8

I i

not required when using REC

STEP 9

i)UTPUT @Chans;"*CLS;MCARM;"

STEP 10

bUTPUT @Ref;"*CLS;MCARM;"

I i

STEP 11

FOR Event= 1 TO 5

OUTPUT OUTPUT

STEP 12

&aph(O,N,N/lO,0,4096,512,"REMOTE

@Ref;"TIM:EVEN ";Event

@Ref;"MCREC;"

SLAVED

DIGs”,“time”,“ampl”,3)

255;*SRE

255;*SRE 255'

";N “;N

255"

2-37

PROGRAMMING FUNDAMENTALS

510

520 530

540 550 560 570 580 590

600 610 620

630 640 650 660 670 680 690 700

710 720 730 740 750 760 770 780

790 800 810 820 830

840 850 860 870 880 890 900 910 920 930 940 950 960 970 980 990 1000 1010 1020 1030

OUTPUT OUTPUT ENTER

MOVE

FOR

@Ref;"*WAI;"

@Ref ;"WAV:DATA?"

@Ref

USING

-100,O

J=O

N-l

ENTER DRAW

@Ref

USING

3,Value

"#,2A";A$

"#,W";Value

STEP 13

i *

only used for REC

&TPUT @Ref;"MCINF?"

ENTER OUTPUT OUTPUT

i *

i i i

OUTPUT @Chanl

MOVE OUTPUT

ENTER FOR

NEXT NEXT Event

END

This portion of the program example listed below is used to set up

! the display screen and is not part of the slaving process. I

SUB Graph(Xmin,Xmax,Xstep,Ymin,Ymax,Ystep,Title$,Xaxis$,Yaxis$,Plotdev)

@Ref;Datl,Dat2,Dat3,Dat4

@Chans;"MCINF

@Chans;"MCREC;"

Interpolation is not applicable for REC mode at this time.

STEP 14 (repeat for each channel)

;

“*WA1

-100,O

@Chanl;"WAV:DATA?"

Khan1

J=O

ENTER

DRAW

USING

N-l

Khan1

3,Value

USING

“;Datl,DatZ,Dat3,Dat4

; II

"#,2A";A$

"#,W";Value

GINIT

Plotdevo3

PLOTTER

END

PEN 4

GRAPHICS ON

Dx=Xmax-Xmin

Dy=Ymax-Ymin WINDOW

LINE

Xmin-.l*Dx,Xmaxt.l*Dx,Ymin-.15*Dy,Ymax+.l*Dy

TYPE

THEN

Plotdev,"HPGL"

CSIZE 3

LORG 5

LDIR -PI/2

MOVE

Xmaxt.O25*Dx,YmintDy/Z

LABEL Yaxis$ LDIR 0

2-38

PROGRAMMING FUNDAMENTALS

1040

1050 1060 1070 1080 1090 1100 1110 1120 1130

1140 1150 1160 1170 1180 1190 1200 1210 1220

1230 1240 1250

MOVE LABEL Xaxis$ MOVE LABEL X=Xmin WHILE

END WHILE

Y=Ymin

WHILE

END WHILE

CLIP

Plotdev=3

GRID LINE

PEN

SUBEND

XmintDx/2,Ymin-.075*Dy XmintDx/2,Ymaxt.O5*Dy

Title$ XcXmax

MOVE X,Ymin-.025*Dy

LABEL X

X=DROUND(XtXstep,8)

YcYmax

MOVE Xmin-.025*Dx,Y

LABEL Y

Y=DROUND(YtYstep,8)

Xmin,Xmax,Ymin,Ymax

THEN LINE TYPE 4

Xstep,Ystep,Xmin,Ymin

TYPE

2-39

PROGRAMMING FUNDAMENTALS

2-40

LANGUAGE REFERENCE INTRODUCTION

Chapter 3

LANGUAGE REFERENCE

This chapter contains complete information for the commands available to operate a digitizer system by remote computer control. The commands are divided into the functional subsystems listed listed in alphabetical order within each subsystem.

Common Command Set Digitizer Top-Level Command Set Acquire Subsystem Calibration Subsystem Channel Subsystem Display Subsystem Domain Subsystem Function Subsystem Measure Subsystem

Timebase Subsystem

Trigger Subsystem

Waveform Subsystem Window Subsystem

.below,

and are

A syntax diagram. for

The commands and/or queries of each subsystem are listed in alphabetical order according to their mnemonics. A functional description is provided for each; however, if more detailed information regarding

a command function is necessary, refer to the manual operation

HP 70700A Digitizer Operation Manual, Digitizer Functions.

earn

is shown at the beginning of each subsystem.

softkey descriptions in Chapter 2 of the

NOTE

&ly4he#hree-

For your convenience, four cross-reference listings for the digitizer remote commands are supplied in the Appendices.

or four-

Appendix A, Command Listing By Subsystem Appendix B, Alphabetical Mnemonic Listing Appendix C, Alphabetical Command Description Listing Appendix D, Alphabetical Command Summary

character

mnemonic may be used in programming.

3-l

LANGUAGE REFERENCE INTRODUCTION

NOTATION CONVENTIONS

Pictorial

The following general guidelines refer to the pictorial syntax diagrams for each functional subsystem in this manual.

l All items enclosed by a rounded envelope must be entered exactly as shown. l Items enclosed by a rectangular box indicate parameters used in the command sequence. A description

of each parameter is given in the respective command descriptions.

l Command sequence items are connected by lines. Each line can be followed in only one direction, as

indicated by an arrow at the end of each line.

l Any combination of command sequence items that can be generated by following the lines in the

proper direction is syntactically correct.

l A command sequence item is optional if there is a valid path around it.

Textual Notation

CAPITAL LETTERS

Capital letters are used to indicate program mnemonics of a command program header.

< >

Angle brackets are used to enclose elements of the language being defined. Refer to Functional Syntax Conventions, below, for an explanation of information contained within these brackets.

Square brackets are used to enclose optional information not required for execution of the command sequence.

( I

Braces are used to enclose a descriptive comment referring to the preceding item in the command sequence.

The vertical line indicates a choice of exactly one element from a list.

Functional syntax is required to create program messages that are transmitted to a device. Program messages are composed of sequences of program message units, each unit representing a program command or query. Each program command or query is composed of a sequence of functional syntactic elements. Legal program commands and queries are created from functional element sequences generated by using the functional syntax diagrams.

Terminated program messages are complete “controller-to-device” messages. They are sequences of zero or more <PROGRAM MESSAGE UNIT> elements. The <PROGRAM MESSAGE UNIT> element represents a programming command or data sent to the device from the controller. See Figure

A <PROGRAM MESSAGE UNIT> element is defined in more detail as either a <COMMAND

3-1.

ME!$!jAGE

UNIT> or <QUERY MESSAGE UNIT>. See Figure 3-2.

3-2

LANGUAGE REFERENCE INTRODUCTION

Each <COMMAND/QUERY MESSAGE UNIT> contains a <PROGRAM

HEAD.ER

SEPARATOR> and

may be optionally followed by a <PROGRAM DATA> clement and a <PROGRAM DATA SEPARATOR>

See Figure 3-3.

MESSAGE UNIT

<PROGRAM

TERMINATOR>

Figure

= <PROGRAM MESSAGE UNIT>

3-l.

Terminated Program Message Functional Element Syntax

MESSAGE UNIT

/ ’

Figure

<COMMAND/

QUERY PROGRAM

HEADER>

3-2,

<PROGRAM MESSAGE

<PROGRAM

MESSAGE UNIT

SEPARATOR>

UNIT>

Functional Element Syntax

<PROGRAM

DATA

SEPARATOR>

Figure 3-3. <COMMAND/QUERY MESSAGE

- ~~

UNIT>

Functional Element Syntax

3-3

LANGUAGE REFERENCE INTRODUCTION

The syntax for typical command and query sequences is shown below:

<DECIMAL

<COMMAND

PROGRAM

HEADER>

NUMERIC PROGRAM

DATA>

<COMMAND

PROGRAM HEADER>

<PROGRAM

HEADER

SEPARATOR>

<PROGRAM

MESSAGE

TERMINATOR>

TlM:RANG

<PROGRAM

HEADER

SEPARATOR>

TIM:LEV?<NL>

1i;TRlG:QUAL

<PROGRAM

MESSAGE

UNIT

SEPARATOR>

EDGE<NL>

<CHARACTER

PROGRAM

DATA>

<PROGRAM

MESSAGE

TERMINATOR>

SEPARATOR FUNCTIONAL ELEMENTS

The three separator functional elements that are used in the functional syntax of the digitizer system are defined in more detail below.

Since <white space> is an integral part of each separator functional element, it is defined as follows:

3-4

LANGUAGE REFERENCE INTRODUCTION

where <white-space character> is defined as a single ASCII-encoded byte in the range 00-09, OB-20 hexadecimal (O-9, 1 l-32 decimal). This range includes the ASCII-control characters and the space, but

excludes the new line (NL).

<PROGRAM MESSAGE UNIT SEPARATOR> separates sequential <PROGRAM MESSAGE UNIT> elements from one another within a program message. See Figure 3-4.

Figure 3-4. <PROGRAM MESSAGE UNIT SEPARATOR>

Syntax

<PROGRAM HEADER SEPARATOR> separates the <COMMAND PROGRAM HEADER> or <QUERY

PROGRAM HEADER> from the <PROGRAM DATA> elements. See Figure 3-5.

Figure 3=5.<PROGRAM HEADER SEPARATOR>

Syntax

<PROGRAM DATA SEPARATOR> separates sequential <PROGRAM DATA> elements from one another

after a <COMMAND PROGRAM HEADER> or <QUERY PROGRAM HEADER>. It is used when a <COMMAND PROGRAM HEADER> or <QUERY PROGRAM HEADER> has multiple parameters. See Figure 3-6.

Figure 3-6. <PROGRAM DATA SEPARATOR, Syntax

A <PROGRAM MESSAGE TERMINATOR> terminates a program message which is a sequence of one or more definite-length <PROGRAM MESSAGE UNIT> elements. The program message terminator syntax used in the functional syntax of the digitizer system is defined as follows:

3-5

LANGUAGE REFERENCE INTRODUCTION

<white space> 7 ’

where *END is used to indicate concurrent

tranmission

of the END message with the last preceding

data byte;

where NL (new line) is defined as a single ASCWencoded byte OA ( IO decimal).

FUNCTIONAL ELEMENT SUMMARY

<PROGRAM

Represents a single command, programming data, or query received

MESSAGE UNIT> by the device.

Represents a single command or programming data received by the

device.

Specifies the function or operation to be performed in the device and may be optionally followed by associated parameters encoded as <PROGRAM DATA> elements. A <COMMAND PROGRAM

HEADIER>

is further defined as either a <simple command program header>, a <compound command program header>, or a <common command program header>.

<QUERY MESSAGE

UNIT>

Represents a single query sent from the controller to the device.

Similar to <COMMAND PROGRAM HEADER>, except a query

indicator (i.e., ?) shows that a response is expected from the device. A <QUERY PROGRAM HEADER> is further defined as either a

<simple query program header>, a <compound query program header>, or a <common query program header>.

Represents any of the four different program data types: <CHARACTER PROGRAM DATA> is a data type suitable for

sending short mnemonic data, generally where a numeric data type is

not suitable. <DECIMAL NUMERlC PROGRAM DATA> is a data type suitable for sending decimal integers or decimal fractions with or without

exponents. <SUFFIX PROGRAM DATA> is an optional field that

may follow and is used to indicate associated multipliers and units.

<STRING

PROGRAM DATA> is a data type suitable for sending seven-bit ASCII character strings where the content needs to be “hidden” by delimiters.

<ARBITRARY BLOCK PROGRAM DATA> is a data type suitable

for sending blocks of arbitrary eight-bit information.

3-6

LANGUAGE REFERENCE INTRODUCTION

<PROGRAM

MESSAGE UNIT SEPARATOR>

<PROGRAM HEADER

SEPARATOR

<PROGRAM DATA

SEPARATOR>

<nrf>

<NRl>

<NR3>

Separates sequential <PROGRAM MESSAGE UNIT> elements from one another within a program message.

Separates the command/query header from any associated <PROGRAM DATA> elements.

Separates sequential <PROGRAM DATA> elements, that are related to the same header, from one another.

Terminates a program message.

Represents flexible numeric representation in the syntax diagram and is defined in each appropriate mnemonic description.

Numeric response data consisting of a set of implicit point

representations of numeric values.

Numeric response data that are representations of scaled explicit

radix point numeric values, together with an exponent notation.

COMMON COMMAND SET

The commands of the Common Command Set are available at any time during remote control of a digitizer system. Refer to Figure 3-7 for a syntax diagram of the Common Command Set commands.

“END

*ESE

*ES!3

*IDN

*OPT

“ME

*SRE

*STB

white

A ’

space

white

A ’

space r

nrf

“END

3-8

“TST

Figure 3-7.

Common

Command Set

C~ommnnds

*cLs

COMMON COMMAND SET

CLEAR STATUS

The CLEAR STATUS command clears status data structures and the Request-for-OK (Operation Complete) flag. (Refer to the OPERATION COMPLETE command in this section.)

If the CLEAR STATUS command immediately follows a <PROGRAM MESSAGE TERMINATOR>, the Output Queue and the MAV (Message Available) bit will be cleared. Any new <PROGRAM MESSAGE> after a <PROGRAM MESSAGE TERMINATOR> clears the Output Queue.

Command Syntax:

Example:

STANDARD EVENT STATUS ENABLE

The STANDARD EVENT STATUS ENABLE command sets the Standard Event Status Enable Register

bits. The query allows the programmer to determine the current contents of the Standard Event Status

Enable Register. Refer to the Standard Status Data Structure section in Chapter 2.

Command Syntax:

*CLS <terminator>

OUTPUT

*ESE <mask> <terminator>

707;"*CLS"

command/query

command

Example:

Preset State: 0

Parameter Range: 0 through 255

Query Syntax: .

Query Response:

STANDARD EVENT STATUS REGISTER

The STANDARD EVENT STATUS REGISTER query allows the programmer to determine the current contents of the Standard Event Status Register. Reading the Standard Event Status Register will clear it.

Query Syntax: .

Query Response:

OUTPUT

*ESE'

*ESR' <NRl> <NL>

707;"*ESE

32"

query

3-9

COMMON COMMAND SET

*lDN

IDENTIFICATION

The IDENTIFICATION query is for identifying devices over the system interface. The response is organized into four fields separated by commas. The field definitions are as follows:

Field 1

Field 2 Field 3 Field 4

An example of a query response is: .

Query Syntax: .

Query Response:

Manufacturer Model Serial Number

Firmware

Datecode

HEWLETT PACKARD,70700A,24

*IDN?

HEWLETT

<firmware

PACKARD,70700A,<serial

required required

ASCII ASCII

datecode (yymmdd)> <NL>

character 0 if not available character 0 if not available

19AOO256,8

number>,

703 17

query

*opt

OPERATION COMPLETE

The OPERATION COMPLETE command sets the request for the Operation Complete flag. When all

pending device operations have been finished, the OPC bit in the Standard Event Status Register is set. The query places an ASCII character finished.

“I”

in the Output Queue when all pending device operations have been

command/query

Because reading trace data is an operation, the synchronization commands should not be used after the request of trace data (e.g.,

WAV:DATA?; or DIG CHANl;) until all data has been read. If the synchronization commands are used, the system may be placed in a state where it is “waiting” indefinitely. In this state, the digitizer system waits for the data to be read and the computer waits for all operations to be completed.

Command Syntax:

Example:

Query Syntax:

Query Response:

3-10

*OPC

OUTPUT

*OPC’

707;"*OPC"

*OPT

COMMON COMMAND SET

OPTION IDENTIFICATION

query

The OPTION IDENTIFICATION query is for identifying reportable device options over the system interface. The

response is organized into five fields separated by commas. The field definitions are as

follows:

Fle

d2 Field Field

Field

3 4

Memory Size

of RAM program 0

of RAM of RAM

program program

ID of RAM program 3

For example:

Query Syntax: .

Query Response:

65536,86

16,0,0,0

will be returned as a five-field option.

*OPT? <terminator> <options (five fields)>

<NL>

*RST-

command

The RESET command performs a device reset and the following actions:

sets device-dependent functions to a known state

aborts pending operations

l clears the Output Queue l clears the Request-for-Operation Complete flag

The RESET command will not:

l affect the hardware interface l modify the Standard Status Register Enable setting l modify the Standard Event Status Enable setting l modify the power-on-clear flag

l modify calibration data.

*RST

Command Syntax:

Example:

OUTPUT

707;"*RST"

COMMON COMMAND SET

SERVICE REQUEST ENABLE

The SERVICE REQUEST ENABLE command sets the Service Request Enable Register bits. The query returns the current contents of the Service Request Enable Register. Refer to the Standard Status Data

Structure section in Chapter 2.

Command Syntax: *SRE <mask> <terminator>

Example:

Preset State: 0

Parameter Range: 0 through 255

Query Syntax: .

Query Response:

OUTPUT

*SRE? <NRl> <NL>

707;"*SRE

150"

command/query

*STB READ STATUS BYTE

query

The READ STATUS BYTE query allows the programmer to read the Status Byte Register and the Master Summary Status bit. Refer to the Standard Status Data Structure section in Chapter 2.

*STBT

Query Syntax: .

Query Response:

*TST

SELF-TEST

The SELF-TEST query executes an internal self test and places the pass/fail code in the Output Queue. Pass is equal to 0; fail is less than or greater than 0.

Query Syntax:

Query Response:

*TST? <terminator>

query

3-12

“WA1

COMMON COMMAND SET

WAIT-TO-CONTINUE

The WAIT-TO-CONTINUE command stops the device from executing any further commands or queries until the No-Operation-Pending flag, Power-On (PON), or Device Clear Active State Message (DCAS) is true.

Because reading trace data is an operation, the synchronization commands should not be used after the request of trace data (e.g., WAV:DATA?; or DIG CHANl;) until all data has been read. If the synchronization commands are used, the system may be placed in a state where it is “waiting” indefinitely. In this state, the digitizer system waits for the data to be read and the computer waits for all operations to be completed.

*WA1

Command Syntax:

Example:

OUTPUT

707;"*WAI"

command

3-13

DIGITIZER TOP-LEVEL COMMAND SET

The commands of the Digitizer Top-Level Command Set are general digitizer commands which do not. reside in any particular subsystem and are available at any time. Refer to Figure 3-8 for a syntax diagram

of the Digitizer Top-Level Command Set commands.

*CAL

DIG

RUN

STOP

white

A* space

white

space -

I I

CHAN

channel-

number

white

e+ space -

^END

NL “END

3-14

Figure 3-8. Digitizer ‘Top-Level Command Set Commands (1 of 2)

DIGITIZER

TOPLEVEL

COMMAND SET

AUT AUTOSCALE

STOR

A +

space

white

CHAN

channel-

number

Figure 3-8. Digitizer Top-Level Command Set Commands (2 of 2)

command

The AUTOSCALE command performs the autoscale function which automatically selects the vertical sensitivity, vertical offset, trigger level, and sweep speed for a display of the input signal. If the function

fails, an error is declared.

Command Syntax:

Example:

BLANK

AUT <terminator>

OUTPUT 707;"AUT"

command

The BLANK command causes the instrument to turn off (i.e., to stop displaying on the display screen) the specified channel, function, or waveform memory.

Command Syntax:

Example:

BLAN

OUTPUT 707;"BLAN

(CHANXIFUNCXIWMEMX) <terminator>

WMEMZ"

3-15

DIGITIZER TOP-LEVEL COMMAND SET

*CAL CALIBRATION

The CALIBRATION query executes an Output Queue that indicates whether or not the device completed the self-calibration routine without error. Pass is equal to 0; fail is less than or greater than 0.

Query Syntax: .

Query Response:

*CAL? <terminator>

interna

1 self-ca

libration routine and generates a response in the

DIGITIZE

The DIGITIZE command is used to request that waveform data from a specified channel be returned to the controller via HP-IB. Once the necessary data is received to satisfy the acquisition criteria, all other measurement acquisitions are stopped. If the display is on, the new data will also be displayed.

Command Syntax: DIG (CHANX) <terminator>

Example:

OUTPUT

707;"DIG CHANZ"

query

command

ERR ERROR

The ERROR query returns the next error in the Error Queue. If there are no errors, 0 (no errors) is returned. If there has been an error, the instrument should respond with the first one. Subsequent responses to the ERROR query should continue with the error list until there is no error remaining. The optional parameters NUMBER and STRING indicate whether a numeric or text description of the error is to be returned.

Query Syntax: ERR? [NUM

Query Response: if NUMBER

if STRING

STR] <terminator>

<NRl> <NL> <NRl> 9

<NL>

RUN

The RUN command directs the instrument to acquire data for the active waveform display. If the instrument is in SINGLE SWEEP, one trigger is enabled which in turn generates one measurement. If the instrument is in CONTINUOUS SWEEP, triggers are enabled repeatedly and the instrument displays the data it acquires continuously.

Command Syntax: RUN <terminator>

Example:

OUTPUT

707;"RUN"

query

command

3-16

DIGITIZER TOP-LEVEL COMMAND SET

STOP

The STOP command directs the instrument to stop acquiring data for the active waveform display. Note that this does not affect the SINGLE SWEEP or CONTINUOUS SWEEP mode.

Command Syntax:

Example:

STOP <terminator>

OUTPUT

707;"STOP"

STORE

The STORE command directs the instrument to move the current waveform in a specified channel to the specified waveform memory. destination.

Command Syntax:

Example:

The channel is always the source, and the waveform memory is the

STOR OUTPUT 707;"STOR

(CHANX,WMEMX)

CHANl,WMEM3"

command

VIEW

The VIEW command causes the instrument to turn on (i.e., to start displaying on the display screen) the

specified channel, function, or waveform memory.

Command Syntax:

Example:

VIEW

OUTPUT 707;"VIEW

(CHANXIFUNCXIWMEMX)

FUNCl"

command

3-17

ACQUIRE SUBSYSTEM

The Acquire Subsystem commands are used to set

conditions when a system command is executed. This

subsystem is used to select the number of trace averages, the number of points desired, trace length and

timebase coupling, and the type of data. Refer to Figure

3-9

for a syntax diagram of the Acquire Subsystem

commands.

)

POIN

white

space L

nrf

“END )

*END

3-18

TYPE

A ’ space

white

’

Figure

3-9.

Acquire Subsystem Commands

white

space 4

*r 1

COUN

ACQUIRE SUBSYSTEM

COUNT

The COUNT command sets the number of averaged traces that may be selected. The traces averaged are always the most recent traces (or sweeps) taken. The query returns the current number of averaged traces.

Command Syntax:

Example:

Preset State: 1

Parameter Range: 1 to 1024

Query Syntax: ACQ:COUN? <terminator>

Query Response:

ACQ:COUN <number> <terminator> OUTPUT 707;"ACQ:COUN 55"

POINTS

The POINTS command sets the number of points in a trace. It determines the number of data points to be sampled and saved, which can be up to a maximum of the available memory. (The available memory is 256K words.) The query returns the current number of points in the trace.

command/query

NOTE

Because the trace length functions in conjunction with the

SECONDS/DIVISION function, the minimum/maximum for a given time range will vary. If a value that conflicts with the current time range is requested (e.g., 10000 points with a time range of 1

GHz

sampling rate), a range error is reported and the TIME RANGE will be adjusted. For example, However, the trace is still 10000 points but with a time range of 31.2

Command Syntax: ACQ:POIN <number of points> <terminator>

Example:

Preset State: 200

Parameter Range:

Query Syntax:

Query Response:

OUTPUT 707;"ACQ:POIN

20 to (256K words - 256 data points)

available memory: 256K words ACQ:POIN? <terminator>

“*RST;ACQ:POIN

MS,

which would require a 10

10000;” causes a range error.

500"

us.

3-19

ACQUIRE SUBSYSTEM

The AUTO ON command allows the digitizer module to choose the trace length that is most suitable. Refer to the AUTO command below for more information.

AUTO

The AUTO command sets the status of the Timebase and Trace Length coupling. When ON is selected, the SECONDS/DIVISION function and the TRACE LENGTH function are directly coupled.

When these two functions are coupled, the digitizer attempts to set the trace length points to 500 number of points 5 1000. If this cannot be achieved, then the digitizer sets the number of between a minimum of 20 and a maximum of the available memory.

When OFF is selected, the SECONDS/DIVISION function can be changed without affecting the trace length, The query returns the current status of the Timebase and Trace Length coupling.

Command Syntax:

Example:

Preset State: ON

Query Syntax:

Query Response:

ACQ:POIN:AUTO OUTPUT 707;'ACQ:POIN:AUTO ON'

ACQ:POIN:AUTO? <terminator>

ON(OFF <NL>

(ONIOFF}

TYPE

command/query

points

The TYPE command allows selection of the type of acquisition that is to take place when a digitizer

system command is executed.

When NORMAL is selected, evenly-spaced

When AVERAGE is selected, the number of averaged traces may be selected in which the most recent evenly-spaced sequential data points in a trace are averaged with the previous trace. The traces averaged are always the most recent traces (or sweeps) taken.

Command Syntax:

Example: Preset State: NORMAL Query Syntax:

Query Response:

ACQ:TYPE {NORMIAVER) <terminator> OUTPUT 707;'ACQ:TYPE AVER'

ACQ:TYPE? <terminator>

NORMIAVER <NL>

sequent.ial

data points in a trace are measured and returned.

3-20

CALIBRATION SUBSYSTEM

The Calibration Subsystem allows the user to invoke the internal calibration routine remotely, or to load previously-acquired calibration data.

Refer to Figure

3-10

for a syntax diagram of the Calibration

Subsystem commands.

CAL

--l

DATA

Figure

white

Space

3-l

block

3 ’ data

Calibration Subsystem Commands

ALL

The ALL query invokes the internal calibration, and returns a pass or fail code.

Query Syntax:

Query Response:

CAL:ALL? <terminator> or CAL? <terminator>

0(-l

<NL>

where 0 indicates "pass" and -1 indicates "fail"

“END

--- --

3-2 1

CALIBRATION SUBSYSTEM

DATA

The DATA command provides a means for the user to load calibration data. The query returns the calibration data of the module as a definite block the module.

Command Syntax:

Example:

Query Syntax: CAL:DATA?

Query Response:

binary 3 digits

CAL:DATA <block data> DIM

A$[5001

OUTPUT

ENTER 707 USING

SIZE =

OUTPUT 707 USING

#3xxx

/ \/

707;"CAL:DATA?"

VAL(A$[W])

<binary

(#3xxxdata).

"#,-K";A$

"#,K";"CAL:DATA

byte>...<binary

The data resides in the internal format. of

! Get calibration data.

! Request calibration data.

! Enter data up to

! Restore calibration cycle. ! (# suppresses CRLF; K sends ! text)

byte>

ignores CRLF; K gets all

text up to <END>)

“&A$[l,SIZEt5]

<NL>

command/query

<END>.

3-22

CHANNEL SUBSYSTEM

The Channel Subsystem allows the user to control all vertical or Y-axis functions of the digitizer system.

Refer to Figure

3-11

for a syntax diagram of the Channel Subsystem commands.

COUP

DET

ECL

A+

space

white

space

white

A’

space ’

“END

white

6+ space ’

Figure

3-11.

Channel Subsystem Commands (1 of 2)

3-23

CHANNEL SUBSYSTEM

PROB

RANG

TTL

TYPE

white

A *

space ’

white

space 7 + nrf

white

A+

space -

Figure 3-11. Channel Subsystem

nrf

LOG

LIN

Commauds

(2 of 2)

COUPLING

command/query

The COUPLING command sets the signal coupling to the digitizer for the indicated channel (CHANX) to be ac-coupled into 1 megohm (AC), dc-coupled into I megohm (DC), or dc-coupled into 50 ohms (DCF). The query returns the current signal coupling.

Command Syntax:

Example:

CHANX:COUP

OUTPUT 707;

{AC(DCIDCF)

‘THAN1

:COUP

AC"

Preset State: DC

Query Syntax:

Query Response:

CHANX:COUP? <terminator>

AC(DCIDCF <NL>

3-24

DET

CHANNEL SUBSYSTEM

DETECTOR

The DETECTOR command sets the detector mode used by the indicated channel (CHANX). The four detector modes used for sampling a waveform are: SAMPLE, POSITIVE PEAK, NEGATIVE PEAK, and ALTERNATE PEAK. The query returns the current detector mode.

The detector modes help display the frequency and number of occurrences of a waveform when using slower sweep rates. To determine the sample interval when using any of the detector modes, the waveform is divided into regularly-spaced intervals based on the TRACE LENGTH. When the timebase has been set up so that more than one 20 MHz conversion (digitized value) occurs in a sample interval, the detector

mode may be selected to specify which conversion is stored to memory.

SAMPLE retains the last conversion in each sample interval.

POSITIVE PEAK retains only the highest value of data in each sample interval.

NEGATIVE PEAK retains only the lowest value of data in each sample interval.

ALTERNATE PEAK alternately retains the highest and lowest values of data within the sample interval. The highest value consists of the highest value since the last POSITIVE PEAK was kept; likewise, the lowest value consists of the lowest value since the last NEGATIVE PEAK was kept.

The sample interval for the ALTERNATE PEAK mode is twice as large as the POSITIVE and NEGATIVE PEAK sample interval. The sample rate is the same though, since each interval overlaps the preceding interval by half. This is to ensure that no information is overlooked as PEAK values are retained alternately.

the

POSITIVE and NEGATIVE

command/query

Command Syntax:

Example:

Preset State: SAMPLE

Query Syntax:

Query Response:

CHANX:DET

OUTPUT

CHANX:DET? <terminator>

SAMPlPOSlNEGlALT <NL>

{SAMPIPOSINEGIALT}

707;"CHANl:DET NEG"

ECL EMITTER-COUPLED LOGIC

The ECL command sets the voltage range, offset, and trigger level for the indicated channel (CHANX) to

values appropriate for examining ECL signals. The voltage range is

level is -1.OV.

Command Syntax:

Example:

Preset State: Inactive

CHANX:ECL <terminator> OUTPUT

707;"CHANl:ECL"

l.GV,

the offset is -l.OV, and the trigger

command

3-25

CHANNEL SUBSYSTEM

INP

command/query

The INPUT command sets the input connection for the indicated channel (CHANX) to be either INPUT or INPUT 2. The query returns the current input.

Command Syntax:

Example:

Preset State: INPUT

Query Syntax: CHANX:INP? <terminator>

Query Response:

OFFSET

The OFFSET command sets the level (amplitude reference) of the display midscreen in volts for the indicated channel (CHANX). The input range for a signal will be:

current offset.

CHANX:INP OUTPUT

707;"CHANl:INP

112 <NL>

(112)

* IOV

command/query

PROBE. The query returns the

Command Syntax:

Example:

Preset State: OV

Parameter Range:

Fundamental Unit: Volts

Query Syntax:

Query Response:

CHANX:OFFS <offset> [XV]

OUTPUT 707;

-lOV

x PROBE to

CHANX:OFFS?

‘THAN1 :OFFS

1OV

500

x PROBE

mV"

3-26

CHANNEL SUBSYSTEM

PROBES

The PROBES command sets the value of the probe multiplier for the indicated channel (CHANX). The

query returns the current probe value.

Command Syntax: CHANX:PROB <multiplier> <terminator>

Example:

Preset State: 1

Parameter Range:

Query Syntax:

Query Response:

OUTPUT

1 x

CHANX:PROB? <terminator>

707;"CHANX:PROB 10"

lOE-6

to 1 x

lOE6

RANGE

command/query

The RANGE command sets the voltage range (amplitude) for the indicated channel (CHANX). The input range for a signal will be:

Command Syntax:

Example:

Preset State:

Parameter Range:

Fundamental Unit: Volts

Query Syntax:

Query Response:

O.lV

to 20V x PROBE. The query returns the current voltage range.

CHANX:RANG <range>

OUTPUT

2.OV

O.lV

CHANX:RANG? <terminator>

707;"CHAN2:RANG 2.5V"

x PROBE to

[XV]

2O.OV

x PROBE

3-27

CHANNEL SUBSYSTEM

SPECTRUM ANALYZER

The SPECTRUM ANALYZER command presets the voltage range, offset, trigger level, and input coupling

. of the digitizer to view the video output of a spectrum analyzer. The voltage range is set to

l.OV,

the trigger level is

Command Syntax:

Example:

Preset State: Inactive

I.OV,

and the input coupling is set to dc into I megohm.

CHANX:SA <terminator> OUTPUT

707;"CHANl:SA"

2.OV,

command

the offset

TTL TRANSISTOR-TRANSISTOR LOGIC

The TTL command sets the voltage range, offset, and trigger level for the indicated channel (CHANX) to values appropriate for examining TTL signals. The voltage range is 8V (1.0 V/div), the offset is

the trigger level is

Command Syntax:

1.6V.

Example:

CHANX:TTL <terminator>

OUTPUT

707;“CHANl

:TTL"

command

1.6V,

and

Preset State: Inactive

TYPE

The TYPE command specifies trace data to be in either logarithmic or linear units and is only applicable in the SPECTRUM ANALYZER mode. The query returns the logarithmic/linear status.

When the SPECTRUM ANALYZER preset mode is selected, trace data is displayed as LOGged data in which the top graticule is the spectrum analyzer reference level and the bottom graticule is equal to -100

dB.

In LINEAR units (unlogged data), the top graticule remains the reference level, but the bottom graticule

becomes OV.

In LOGARITHMIC mode, the trace data is passed unchanged assuming a logged input. In LINEAR mode,

the trace data is unlogged.

Command Syntax:

Example:

Preset State: LOGARITHMIC

Query Syntax:

CHANX:TYPE OUTPUT

CHANX:TYPE? <terminator>

(LOGILIN)

707;"CHANl:TYPE LIN"

command/query

Query Response:

3-28

LOGILIN

<NL>

DISPLAY SUBSYSTEM

The Display Subsystem is used to control the display of data, markers, text, graticule, and screen format. Refer to Figure 3-12 for a syntax diagram of the Display Subsystem commands.

white

CONN ON

OFF

A +

space -

“END

CONN

FORM

QRAT

tzY

OFF

GRID

Figure 3-12. Display Subsystem Commands (1 of 2)

3-29

DISPLAY SUBSYSTEM

SCR

STR

TMAR

A ’

space

white

A +

space ’

white

OFF

text

VMAR

Figure

white

A )

space -

3-l

2. Display Subsystem Commands (2 of 2)

OFF

3-30

CONN

D&PLAY SUBSYSTEM

CONNECT

The CONNECT command turns the dots mode on or off. When ON (or 1) is selected, the waveform is displayed as a continuous solid trace. When OFF (or 0) is selected, the dots mode is enabled. The dotted line represents actual data points that were sampled, while the solid trace results from joining the dots with straight line segments. The query returns the current connect mode.

A maximum number of available may be displayed at any time. Each of the displayed data points corresponds directly to a data point that has actually been sampled. Selecting the number of data points for sampling may be achieved by using the POINTS command in the Acquire Subsystem. Refer to the Acquire Subsystem for more information on the POINTS command.

memory data points may be sampled, but only

103-C

command/query

data points or less

NOTE

Display Dot Generator release 3.2 or later must be installed in the display

instrument when using the CONNECT OFF command.

Command Syntax:

Example:

DISP:CONN OUTPUT 707;"DISP:CONN

(ONIOFFI110)

Preset State: ON Query Syntax:

Query Response:

DISP:CONN? <terminator>

ONIOFF <NL>

FORM FORMAT

The FORMAT command sets the split-screen format. When 1 is selected, the normal full-screen format is displayed. When 2 is selected, a split-screen format is displayed. The query returns the current status of the screen format.

When the split-screen format is enabled, odd-numbered channel/memory/functions are displayed in the top portion of the screen and even-numbered channel/memory/functions are displayed in the bottom portion of the screen. The channel/memory/functions are only displayed if they have been previously turned on by the Top-Level Subsystem VIEW command.

command/query

3-31

DISPLAY SUBSYSTEM

Command Syntax:

Example:

Preset State:

Parameter Range: 1 to 2

Query Syntax:

Query Response:

DISP:FORM

OUTPUT

(l(2)

707;“DISP:

FORM 2"

= full-screen format, 2 '= split-screen format

DISP:FORM? <terminator>

GRAT

GRATICULE

The

GRAT1CUL.E

that format the display screen. AXES superimposes one set of vertical and horizontal lines on the display screen. FRAME superimposes lines that border the edges of the display screen. GRID superimposes evenly-spaced vertical and horizontal lines on the display screen. format. The query returns the current display graticule format.

command sets the display graticule with one of three sets of vertical and horizontal lines

The OFF parameter blanks all graticule

command/query

Command Syntax:

Example:

Preset State: AXES

Query Syntax:

Query Response:

DISP:GRAT

OUTPUT

DISP:GRAT? <terminator>

OFFIGRID(AXES(FRAM

SCREEN

The SCREEN command sets the display screen status. When OFF, most of the display screen is blanked. The query returns the current screen setting.

Command Syntax:

Example:

DISP:SCR (ON~OFF)l)O)

OUTPUT

(OFF(GRID(AXESIFRAM)

707;"DISP:GRAT

GRID”

<NL>

<'terminator>

707;“DISP:SCR OFF”

command/query

Preset State: ON

Query Syntax:

Query Response:

3-32

DISP:SCR?

ONIOFF <NL>

STR

The

STRING

DlSPLAY SUBSYSTEM

command

command displays the input string parameter on the display screen.

Command Syntax:

Example:

TIME

The TIME MARKERS command turns on and off the display of the time markers. The annotation related to the time markers is indicated by T( 1) and T(2) at the and off by this command. The query returns the current stat us of

The time markers are turned on independently of the voltage markers, but their display on a channel, memory, or function is dependent

the Measure Subsystem SOUR (SOURCE) command.

When the voltage markers are either off or displayed on channel. However, when the voltage markers are displayed on a memory, the time markers can only be displayed on the same memory. Refer to the VMAR command below for more detailed information on the function of the VOLTAGE

MARKERS

DISP:STR OUTPUT

OUTPUT

("text"~'text')

707;“DISP:STR

707;“DISP:

STR

'Label

i@&$$"

bo!fom of the display screen, and is also

'I'

. . . . .

(he

time markers.

command/query

on the Display Subsystem VMAR (VOLTAGE MARKER) command and

channel, the time markers are displayed on a

MARK.ERS.

tLlrned

When the time markers are displayed, the TSTA (START MARKER) and TSTO (STOP MARKER)

commands must be used to reposition the time markers. Refer to the TSTA and TSTO commands in the

Measure Subsystem.

Command Syntax:

Example:

Preset State: OFF

Query Syntax:

Query

Response:

DISP:TMAR

OUTPUT

DISP:PMAR? ONIOFF <NL>

(ONIOFFI110)

707;“DISP:TMAR 1”

3-33

DISPLAY SUBSYSTEM

VMAR VOLTAGE MARKERS

The VOLTAGE MARKERS command turns on and off the display of the voltage markers. The annotation related to the voltage markers is indicated by V(J) and V(2) at the bottom of the display screen and is also turned on and off by this command. The query returns the current voltage marker status.

This command functions in conjunction with the Measure Subsystem SOURCE command to determine whether the voltage markers are displayed on a channel, memory, or function display. Refer to the SOUR command in the Measure Subsystem.

When the voltage markers are displayed, the VSTA (VOLTAGE MARKER 1) and VSTO (VOLTAGE MARKER 2) commands must be used to reposition the voltage markers. Refer to the VSTA and VSTO commands in the Measure Subsystem.

Command Syntax:

Example:

Preset State: OFF

Query Syntax:

Query Response:

DISP:VMAR OUTPUT

DISP:VMAR? <terminator>

ONIOFF <NL>

(ONIOFFIllO)

707;"DISP:VMAR

ON"

command/query

3-34

DOMAIN SUBSYSTEM

The Domain Subsystem commands define the display domain to be either time or frequency. Refer to

Figure

3-13

for a syntax diagram of the Domain

SuQsystem

commands,

TYPE

Defaults to Channel 1

Figure 3- 13.

DOI~J~

Subsystem Commands

NL ^END

3-35

DOMAIN SUBSYSTEM

TYPE

The TYPE command sets the domain status of the specified trace to be in either the time or frequency domain. The time domain displays data as amplitude versus time and the frequency domain displays data as a logarithmic amplitude versus frequency. The query returns the current status of the display domain.

command/query

NOTE

The trace specifier defaults to Channel 1 if a trace has not been specified.

When TIME is selected, all references to the horizontal axis are related to time.

When FREQUENCY is selected, a fast Fourier transform (FFT) is performed to translate the data from the time domain to the frequency domain. Also, all references to the horizontal axis are related to frequency. The range of frequencies displayed is the frequency span and is indicated at the lower right graticule edge. The grid display graticule of the FREQUENCY domain has a vertical range of 100 division is annotated in the lower-left portion of the display screen.

Command Syntax:

DOM:[CHANXIWMEMXIFUNCX:]

[TYPE]

(TIME*IFREQ)

dB;

the sensitivity per

Example:

Preset State: TIME

Query Syntax: DOM:

Query Response: TIME

OUTPUT

707;"DOM:FREQ"

TYPE? <terminator>

IFREQ <NL>

or OUTPUT

707;"DOM:CHAN4

TYPE

FREQ"

FUNCTION SUBSYSTEM

The Function Subsystem allows a trace math operation to be performed using the available channels and waveform memories as operands. The trace math operators are: ADD, INVERT, MULTIPLY, OFFSET, ONLY, RANGE, SUBTRACTION, and VERSUS. Refer to Figure 3-14 for a syntax diagram of the Function Subsystem commands.

If the add, subtract, multiply, or versus operation is performed on two traces that are not equal in length, then the function length is set to the smaller trace size and the larger trace is “compressed” to the size of the smaller trace before the function is performed.

ADD

INV

whlte

A )

space 1

white

A+

space 7

r A

space

white

CHAN

channel-

number

channel-

number

^END

Figure 3-14. Function Subsystem Commands (1 of 3)

FUNCTION SUBSYSTEM

MULT

OFFS

ONLY

white

+ ) space - 1

white

A *

space 3

CHAN

WMEM

CHAN

channel-

channel

numbed- ’

channel-

number

1 1

RANG

SUBT

white

l space

white

*+ space ’ 1

)

nrf L

CHAN

J ) suffix

channel-

number r ’

Figure 3-14. Function Subsystem Com~r~a~~ds

3-38

VERS

white

A ’ space . 1 1

\ /

CHAN

WMEM

channel-

number F

memory-

number

Figure 3-14. Function Subsystem Commands (3 of 3)

FUNCTlON SUBSYSTEM

ADD ADDITION

The ADDITION command allows the two defined operands to be summed together algebraically.

Command Syntax:

Example:

Preset State:

FUNC:ADD (CHAN<number>JWMEM<number>),

OUTPUT

(CHANcnumber>lWMEM<number>}

707;"FUNC:ADD CHANl,WMEM3"

ADDITION of CHANNEL 1, CHANNEL 1

INV INVERT

The INVERT command allows the defined operand to be inverted.

Command Syntax:

Example:

FUNC:INV (CHAN<number>lWMEMcnumber>)

OUTPUT

707;"FUNC:INV

WMEM3"

command

Preset State:

ADDITION of CHANNEL 1, CHANNEL 1

3-39

FUNCTION SUBSYSTEM

MULT MULTIPLY

The MULTIPLY command sets the current trace math function to MULTIPLY with the parameters indicating the two operands. The two operands are algebraically multiplied together.

Command Syntax:

Example:

Preset State: ADDITION of CHANNEL 1, CHANNEL 1

OFFSET

The OFFSET command sets the current voltage offset of the function. The query returns the current

voltage offset.

Whenever a new operator or source is

ONLY

INVERT ADDITION SUBTRACTION

FUNC:MULT

OUTPUT 707;"FUNC:MULT

{CHAN<number>lWMEM<number>}, (CHAN<number>lWMEM<number>)

CHANZ, WMEMl"

defiaed,

the offset is set. as follows:

offset of operand

-offset of operand first operand offset + second operand offset first operand offset + second operand offset

command/query

command

Command Syntax:

Example:

Preset State: OV

Parameter Range:

Fundamental Unit: Volts

Query Syntax:

Query Response:

3-40

FUNC:OFFS

OUTPUT 707;"FUNC:OFFS

-20 x probe to (where probe is the larger value of the probe for

FUNC:OFFS?

each operand)

tZ0

[XV]

2V"

x probe

FtJNCTION SUBSYSTEM

ONLY

The ONLY command allows the function to be defined as any available channel or waveform memory without any change.

Command Syntax:

Example:

Preset State:

FUNC:ONLY (CHANcnumber>lWMEM<number>)

OUTPUT 707;"FUNC:ONLY

ADDITION of CHANNEL 1, CHANNEL 1

WMEMZ"

command

RANG RANGE

The RANGE command allows the full-scale vertical axis of a function’s display to be defined. The query returns the current range of the function.

Whenever a new operator or source is defined, the range is set as follows:

ONLY

INVERT

ADDITION

SUBTRACTION

range of operand range of operand first operand range + second operand range first operand range + second operand range

command/query

Command Syntax:

Example:

Preset State: 4V

Parameter Range:

Query Syntax:

Query Response:

FUNC:RANG <range>

OUTPUT 707;"FUNC:RANG

.lV

x probe to 20V x probe

(where probe is the larger value of the probe for

each operand)

FUNC:RANG? <terminator>

[XV]

2V"

3-4 1

FUNCTION SUBSYSTEM

SUBT SUBTRACTION

The SUBTRACTION command

parameters indicating the two operands. The second operand is subtracted from the first,

Command Syntax:

Example:

Preset State:

FUNC:SUBT {CHAN<number+'MEM<wmber>),

OUTPUT 707;"FUNC:SUBT CHAN2,

ADDITION of CHANNEL 1, CHANNEL 1

sets the

current trace

(CHAN<number>JWMEM<number>)

mat.h

function to SUBTRACTION with

WMEM3"

VERSUS

The VERSUS command allows the two defined operands to be plotted with respect to each other on the X and Y axes. The first operand defines the X axis and the second operand defines the Y axis.

Command Syntax:

Example:

FUNC:VERS (CHAN<number>lWMEM<number>),

(CHAN<number>lWMEM<number>)

OUTPUT 707;"FUNC:VERS CHAN2,

CHAN4"

command

the

command

Preset State: ADDITION of CHANNEL 1, CHANNEL 1

3-42

MEASURE

SUBSYST.EM

MEASURE SUBSYSTEM

The commands in the Measure Subsystem allow various measurements to be made on a waveform, such as pulse parameter and voltage measurements. These measurements may also be customized by commands within the subsystem for particular applications.

When a measurement cannot be made and a value is requested, a value of

l.OE38

Refer to Figure 3-15 for a syntax diagram of the Measure Subsystem commands.

Two terms that are frequently used in the Measure Subsystem command descriptions are defined below. threshold refers to a level which is used as a reference in making a measurement. For example, if “lower

threshold” is used, it refers to the point where the waveform crosses that threshold. The thresholds may be defined in terms of absolute voltages, or by referring to a percentage on the waveform (such as 90% referenced to TOP and BASE).

will be returned.

IO%,

histogram refers to using a histogram to determine a top/base voltage value. A histogram of the waveform’s voltage values is constructed. Next, the waveform is scanned to find the voltage values with the largest number of data points. If the maximum number of data points is greater than the limit criteria (approximately 5%) of the maximum number of data points in the record, that voltage level is used for the top or the base. If the limit criteria is not satisfied, the absolute minimum and maximum values are used as the base and the top.

Due to various limitations, the Measure Subsystem is limited to a trace length of 1024 points or less. If a trace greater than 1024 points is measured, the results will not be exact because all of the data is not used. For example, if the trace length is 2048 points and the SAMPLE detector is

*being

used, every other point is skipped. The measurement is then

made on the resulting 1024-point trace.

Two percent hysteresis is used for any edge-searching done in the

Measure Subsystem.

3-43

MEASURE SUBSYSTEM

ALL

OUT

OUT ‘)

ESTA

EST0

white

space

white

space

white

) space A A

nrf

-4

whlte

A B

space 1

^END

3-44

FALL

Figure 3-15. Measure Subsystem

Commands

(1 of 5)

Agilent 70700A Programmers Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

WARRANTY

SAFETY SYMBOLS

CONTENTS

USER MANUALS, SUPPLIED WITH MODULE

Installation and Verification Manual

Operation Manual

Programming Manual

SERVICE MANUAL, AVAILABLE SEPARATELY

Technical Reference

GENERAL INFORMATION

HOW TO USE THIS MANUAL

HP 70700A DIGITIZER MODULE OVERVIEW

MAINFRAME/MODULE INTERCONNECT

PROGRAMMING FUNDAMENTALS

DIGITIZER CHANNEL NUMBER ASSIGNMENT

ADDRESS SWITCHES

SOFT-SET HP-IB ADDRESSES

COMMUNICATION WITH THE SYSTEM

INITIAL PROGRAM CONSIDERATIONS

SERVICE REQUEST ENABLE REGISTER

STANDARD EVENT STATUS ENABLE REGISTER

OUTPUT QUEUE

SYNCHRONIZATION OF EVENTS AND COMMANDS

SYNCHRONIZATION COMMANDS

DATA TRANSFER

EXAMPLE PROGRAM

LANGUAGE REFERENCE

NOTATION CONVENTIONS

SEPARATOR FUNCTIONAL ELEMENTS

FUNCTIONAL ELEMENT SUMMARY

COMMON COMMAND SET

STOP

VIEW

ACQUIRE SUBSYSTEM

AUTO

TYPE

CALIBRATION SUBSYSTEM

DATA

CHANNEL SUBSYSTEM

TYPE

DISPLAY SUBSYSTEM

DOMAIN SUBSYSTEM

TYPE

FUNCTION SUBSYSTEM

ONLY