Agilent 70703A Programmer's Guide

Programmer's Guide

HP 70703A Digitizing Oscilloscope

Printed

ABCDE

70703-90029

.

No

art

P

HP

in

United

Kingdom

December

1993

Notice

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

Hewlett-Packard makes no warranty of any kind with regard to this material, including,

but not limited to, the implied warranties of merchantability and tness for a particular

purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or

consequential damages in connection with the furnishing, performance, or use of this material.

Restricted Rights Legend.

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth

in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at

DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial

Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.

c



Copyright Hewlett-Packard Company 1993

under

Santa

adaptation,

Rosa

Rights

All

prohibited,

is

Fountaingrove

1400

Reserved.

except

Reproduction,

allowed

as

arkway

P

,

the

CA,

or

copyright

95403-1799,

translation

.

laws

USA

without

prior

written

permission

Introduction to Programming Syntax

This chapter introduces you to the basic concepts of HP-IB communication and provides

information and examples to get you started programming. The exact mnemonics for the

commands are listed in Chapters 5 through 18.

Talking to the Instrument

passing

instruction

70703A,

ASIC

B

to

70703A.

E1426A

by

described

I/O

the

ASCAL

P

and

HP

the

Most

osilloscopes

set

statements

70703A,

general,

In

messages

controller's

manual,

this

controller's

your

of

the

systems

ENTER

language

and

commands

computers

over a

remote interface

host language

normally appear

will

use

statement

parameters

and

acting

as

.Hence

program. F

the OUTPUT

for

are

controllers

using the

messages for

, the

as ASCII

or example

statement for

receiving

compatible

communicate

I/O statements

character

HP

the

,

response

the

with

programming

strings

Series

9000

sending

program

messages

54503A

HP

the

provided

the

imbedded

200/300

the

from

and

instrument

the

in

HP

inside

messages

HP

of

1

the

in

.

Messages

program

sent

is

The

are

message

the

to

following

OUTPUT <device

<

device

address

Note

device address

placed

and

,

correct

command

the

on

terminator

interface

presets

bus

using

assing

P

.

instrument.

and

HP

the

output

an

70703A:

the

command

device

and

address

passing

ensures

the

the program

that

message

address>;"*RST"<terminator>

programmed.

represents

>

the

address

of

the

device

being

The programming examples in this manual are written in HP BASIC 5.0 for an

HP 9000 Series 200/300 controller.

The actual OUTPUT command you use when programming is dependent on the

controller and

Angular

symbolize

the programming language you are using.

brackets

program

a

this manual,

in

"

>

<

\

parameter

code

enclose

a

or

bus

characters

words

or

command. Information

that

displayed in quotes represents the actual message that is sent across the

The message terminator (NL or EOI) is the only additional information that is

also sent across the bus

For HP 9000 Series 200/300 controllers

.

it is not necessary to type in the

,

actual<terminator>at the end of the program message. These controllers

automatically terminate the program message internally when the return key is

pressed.

,

is

bus.

Introduction

to Programming

Syntax

1-1

Addressing the Instrument

Since HP-IB can address multiple devices through the same interface card, the device address

passed with the program message must include not only the correct interface select code,but

also the correct instrument address.

Interface Select Code (Selects Interface). Each interface card has a unique interface select

code. This code is used by the controller to direct commands and communications to the proper

interface. The default is typically \7" for HP-IB controllers.

Instrument Address (Selects Instrument). Each instrument on an HP-IB bus must have a unique

instrument address between decimal 0 and 30. The device address passed with the program

message must include not only the correct instrument address, but also the correct interface

select code.

DEVICE ADDRESS = (Interface Select Code * 100) + (Instrument Address)

For example, if the instrument address for the HP 70703A is 4 and the interface select code is

7, when the program message is passed, the routine performs its function on the instrument at

device address 704.

For the HP 70703A, the instrument address is typically set to \7" at the factory. Consult the

\Installation

Note

erication Manual"

and V

The program

address

707.

for details

examples in

on how

this manual

change

to

assume the

the

HP

70703A

instrument

at

is

address

device

.

Program

program

o

T

format

with

unit

of

and

program

representing

a sequence

Message

70703A

HP

the

structure

messages

program

a

of functional

Syntax

over

expected

These

.

command

elements

the

by

composed

are

you

,

bus

instrument.

query

or

includes

that

have

must

The

sequences

of

program

A

.

separators

understanding

an

instrument

program

of

command

headers

,

remotely

is

message

or

program

,

the command

of

programmed

units

query

is

data,

with

,

composed

and

each

terminators. These are sent to the instrument over the system interface as a sequence of ASCII

data messages.For example:

Introduction to

1-2

Programming

Syntax

Figure

1-1.

Separator

The<separator>shown in the program message refers to a blank space which is required to

separate the program mnemonic from the program data.

Command Syntax

A command is composed of a header, any associated data, and a terminator. The header is the

mnemonic or mnemonics that represent the operation to be performed by the instrument. The

dierent types of headers are discussed in the following paragraphs.

Simple Command Header

Simple command headers contain a single mnemonic.AUTOSCALE and DIGITIZE are examples

of simple command headers typically used in this instrument. The syntax is:

program

When

:DIGITIZE

<program

added.

is

with

data

CHAN1),

be

must

separator

a

included

mnemonic><separator><program

the

The

simple

syntax

data>

command

is:

header

(for

example

,

Compound

mnemonic

rst

command

subsystem.

mnemonic

mnemonics

The

execute

o

T

when

a

Command

selects

dditional

A

there

within

single

function

Header

headers

subsystem,

the

mnemonics

additional

are

compound

the

within

are

a

appear

combination

the

and

between

levels

within

message

subsystem,

a

of

mnemonic

last

the

separated

are

use

or

two

subsystem

the

subsystem

the

program

more

selects

colons

by

following:

mnemonics

function

the

mnemonic

must

that

or

F

.

within that

the

and

transversed.

be

example:

.The

function

:<subsystem>:<function><separator>

(For example, :SYSTEM:LONGFORM ON)

To transverse down a level of a subsystem to execute a subsystem within that subsystem:

:<subsystem>:<subsystem>:<function>

<separator><program

:TRIGGER:DELA

(F

or

example

,

To execute more than one function within the same subsystem, a a

data><terminator>

:SOURCE

Y

CHAN1)

semicolon is used to

separate the functions:

:<subsystem>:<function><separator>

(For example, :SYSTEM:LONGFORM ON;HEADER OFF)

Identical

function

horizontal

function

mnemonic

range:

mnemonics

RANGE

can

may

be

used

for more

to change

than

the

one

vertical

subsystem.

or

range

Introduction

example

or

F

to

change

the

to Programming

the

,

Syntax

1-3

:CHANNEL1:RANGE .4

- sets the vertical range of channel 1 to 0.4 volts full scale.

:TIMEBASE:RANGE 1

- sets the horizontal timebase to 1 second full scale. CHANNEL1 and TIMEBASE are subsystem

selectors and determine which range is being modied.

Common Command Header

Common command headers control IEEE 488.2 functions within the instrument (such as clear

status, and so on). Their syntax is:

*<command header><terminator>

No space or separator is allowed between the asterisk and the command header. *CLS is an

example of a common command header.

Query

Command

query

queue

When

Command

headers immediately

instrument

, the

answer

The

.

answer

the

read,

interrogates

remains

transmitted

is

followed by

output queue

the

in

requested

the

across

question

a

until it

the bus

mark

function

to the

(?)

and

read

is

designated

are

places

another

or

queries

answer

the

listener

After

.

in

command

(typically

receiving

output

its

issued.

is

a

controller).

query

The

controller

ENTER

passes

Query

also used

:TIMEB

input

<device

value

the

commands

to get

activating the

ASE:RANGE?

statement:

address>;Range

bus

are

the

to

used

measurements

across

results of

measurement. F

places

the

to

how

out

nd

or example

current

the

controller

the

made

the

,

timebase

places

and

instrument

instrument,

the

by

:MEASURE:RISETIME?

query

setting

in

it

currently

is

the

with

in the

output

variable

congured.

the

query

queue

.

Range

They

actually

instructs

are

the

The

.

instrument to measure the risetime of your waveform and place the result in the output queue.

Note

The output queue must be read before the next program message is sent. For

example, when you send the query :MEASURE:RISETIME? you must follow

that query with the program statement ENTER Value risetime to read the

alue

the

query

be

(V

lost.

risetime).

cause

will

This

will

the

also

Sending

output

generate

result

another

buer

the

of

command

be

to

query and

cleared and

place

before

the

an error in the error queue

result

the

reading the

current

.

a

in

result

response

variable

of

to

Introduction to

1-4

Programming

Syntax

Program Header Options

Program headers can be sent using any combination of uppercase or lowercase ASCII

characters. Instrument responses, however, are always returned in uppercase.

Both program command and query headers may be sent in either longform (complete spelling),

shortform (abbreviated spelling), or any combination of longform and shortform. Either of the

following examples sets the vertical range for:

:CHANNEL1:RANGE 1.2 (longform)

:CHAN1:RANG 1.2 (shortform)

Programs written in longform are easily read and are almost self-documenting. The shortform

syntax conserves the amount of controller memory needed for program storage and reduces the

amount of I/O activity.

Note

The rules for shortform syntax are shown in the chapter \Programming and

Documentation Conventions."

Program

command

program

the

<program

Data

one

a variety

space

data

header

is

used

At

.

convey

to

least

data.

mnemonic><separator><data>

of types

must

parameter

of

separate the

command

information

header

or

the

to

header

from

program

a

When

sequential

<program

mnemonic

program

data.

or

query

has

mnemonic><separator><data>,

multiple

data

parameters

comma

a

separates

For example, :TRIGGER:DELAY TIME,1.23E-01 has two data parameters: TIME and 1.23E-01.

Character Program Data

Character program data is used to convey parameter information as alpha or alphanumeric

The

.

single

or

.F

strings

character

SINGLE

example

or

program

the

sets

the

,

data

timebase

this

in

mode

command

case

to

may

single

be

.

MODE

UTO,

A

set

be

can

TRIGGER,

to auto

SINGLE.

or

trigger

,

:TIMEB

ASE:MODE

Numeric Program Data

or example

Some command headers require program data to be a number

.F

:TIMEBASE:RANGE requires the desired full scale range to be expressed numerically

,

.The

instrument recognizes integers, real numbers, and scientic notation. For more information see

the appendix \Message Communication and System Functions."

Introduction

to Programming

Syntax

1-5

Program Message Terminator

The program codes within a data message are executed after the program message terminator

is received.

The terminator may be either an NL (New Line) character, an EOI (End-Or-Identify) asserted,

or a combination of the two. All three ways are equivalent with the exact encodings for the

program terminators listed in the appendix \Message Communication and System Functions."

Asserting the EOI sets the EOI control line low on the last byte of the data message. The NL

character is an ASCII linefeed (decimal 10).

Note

The NL (New Line) terminator has the same function as an EOS (End-Of-String)

and EOT (End-Of-Text) terminator.

Selecting Multiple Subsystems

You can send multiple program commands and program queries for dierent subsystems on the

semicolon

same

enables

<program

line

you to

a

separating

by

enter a

command

each

new subsystem.

with

or

F

example:

mnemonic><data>;:<program mnemonic>

semicolon.

The

colon

following

the

be

1

combination

any

compound

of

and

simple

:CHANNEL1:RANGE

Note

0.4;:TIMEBASE

Multiple

commands

.

RANGE

may

Introduction to

1-6

Programming

Syntax

Summary

The following illustration summarizes the syntax for programming over the bus.

Figure

1-2.

Introduction

to Programming

Syntax

1-7

Introduction to Programming an Instrument

There are four basic operations that can be done with a controller and an oscilloscope via

HP-IB.You can:

1. Set up the instrument and start measurements.

2. Retrieve setup information and measurement results.

3. Digitize a waveform and pass the data to the controller.

4. Send measurement data to the instrument.

basic

four

these

how

written

of

retrieve setup

to

how

and

sending

on

HP

in

pass data

to

measurement

ASIC

B

5.0

for

more

Other

functions

This

.

chapter

information

to

.

the

controller

data

Note

complicated

mainly

deals

measurement

and

the

to

Refer

instrument.

programming

The

9000

HP

tasks

with

chapter

Series

accomplished

are

up

set

to

how

to

how

,

results

\Measure

examples

Subsystem"

in

200/300 controller

with

instrument,

the

digitize

manual

this

.

combination

a

waveform,

a

information

for

are

2

to the

an

Initialization

To make sure the bus and all appropriate interfaces are in a known state, begin every program

with an initialization statement. For example:

CLEAR 707 ! initializes the interface of the instrument.

Then initialize the instrument to a preset state.For example:

OUTPUT

Note

initializes

actual

!

commands

and

707;"*RST"

The

the chapter \Common Commands

the

syntax

instrument

for initializing

."

to

preset

a

instrument

the

state.

are

discussed

Refer to your controller manual and programming language reference manual

information on initializing the interface

for

.

Introduction

to Programming

Instrument

an

in

2-1

Autoscale

The AUTOSCALE feature of Hewlett-Packard digitizing oscilloscopes performs a very useful

function on unknown waveforms by setting up the vertical channel, timebase, and trigger level

of the instrument. The syntax for AUTOSCALE is:

:AUTOSCALE<terminator>

Setting Up the Instrument

A typical oscilloscope setup would set the vertical range and oset voltage, the horizontal

range, delay time, delay reference, trigger mode, trigger level, and slope. A typical example of

the commands sent to the oscilloscope are:

:CHANNEL1:RANGE 0.64;OFFSET 0.25<terminator>

:TIMEBASE:RANGE 1E-3;DELAY 20E-9;MODE TRIGGERED<terminator>

:TRIGGER:LEVEL 0.25;SLOPE POSITIVE<terminator>

The

.

V

0.25

slope

at

is set

.

to triggered,

and

example

This

horizontal

trigger

the

sets

time

circuit

the

ms

1

is

programmed

is

vertical

full-scale

to

0.64

with

to

full-scale

V

ns

20

trigger

delay

0.25

at

mV/div)

(80

timebase mode

. The

on

V

positive

a

centered

Instrument

is

the

followed

places

read

the

of

by

answer

the

another

or

designated

from

a format

query

the

question

a

its

in

command

listener

an

(typically

instrument's

specication

command

instrument

queue

issued.

output

handling

the

The

.

When

controller).

a

queue

the

answer

read,

typically

response

mark),

output

is

for

:SYSTEM:LONGFORM?,

the

The

you

Receiving

receiving

After

interrogates

remains

answer

statement

input

two parameters;

has

message

would

the

in

transmitted

is

or example

.F

execute

Information

query

a

requested

output queue

(command

function

until

across the

receiving a

for

the device

read the

,to

statement:

the

from

header

and

it

bus to

response message

address and

result

ENTER <device address>;Setting$

where<device address>represents the address of your device. This would enter the current

setting for the longform command in the string variable Setting$.

before

read

be

when

,

must

you

send

the

query

Note

results

All

another

queries

for

program

sent

message is

a program

in

sent.

or

F

message

example

:MEASURE:RISETIME?, you must follow that query with the program

statement ENTER

in a variable

Risetime$ to read the result of the query and place the result

(Risetime$).

Sending another command before reading the result of the query will cause the

output buer to be cleared and the current response to be lost. This will also

cause an error to be placed in the error queue.

Executing an ENTER statement before sending a query will cause the

controller

to

wait

indenitely

.

Introduction to

2-2

Programming

Instrument

an

Note

The actual ENTER program statement you use when programming is dependent

on the programming language you are using.

The format specication for handling the response messages is dependent on

both the controller and the programming language.

Response Header Options

The format of the returned ASCII string depends on the current setting of the SYSTEM

LONGFORM command.

For example, with

with

:SYSTEM:LONGFORM OFF

Note

:SYSTEM:LONGFORM ON,:CHANnel1:COUPling?

, DCF is returned.

A command or query may be sent in either longform or shortform, or in

any combination of longform and shortform. The LONGFORM command

only

commands

Refer

LONGFORM

Response

data will

Most

instrument

return

one

Data

be returned

setups

the

of

may

following:

POSITIVE<terminator>

controls

are sent.

the

to

ormats

F

as

returned

be

format

the

chapter \System

command

exponential

(with

of

Common commands

and o.

on

or

character

as

LONGFORM

POS<terminator> (with LONGFORM OFF)

Note

Refer to the individual commands in this manual for information on the format

(alpha or numeric) of the data returned from each query.

returned

the

Subsystem" for

integer

numbers

data.

Interrogating

ON)

has

and

data

never return

information

However

.

returns DCFIFTY,and

the

on

.

turning

data

on

the

of

SLOPE? will

eect

no

a header

query

,

the trigger

way

Introduction

to Programming

Instrument

an

2-3

String Variables

Reading queries into string variables is simple and straightforward, requiring little attention to

formatting. For example:

ENTER <device address>;Result$

places the output of the query in the string variable Result$.

Note

The following

DIM

10

OUTPUT

20

ENTER

30

PRINT

40

END

50

running

After

String variables are case sensitive and must be expressed exactly the same each

time they are used.

The output of the instrument may be numeric or character data depending on

what is queried. Refer to the specic commands for the formats and types of

data returned from queries.

For the example programs, assume that the device being programmed is at

device address 707. The actual address will vary according to how you have

congured the bus for your own application.

example shows

the data

being

returned

to

string

a

variable:

Rang$[30]

707;":CHANNEL1:RANGE?"

707;Rang$

Rang$

this

program,

controller

the

displays:

+1.00000E-1

Numeric

Variables

variables

can

be

used

when

the

query

data

is

numeric

all

.

The following example shows the data being returned to a numeric variable.

10 OUTPUT 707;":SYSTEM:HEADER OFF"

20 OUTPUT 707;":CHANNEL1:RANGE?"

30 ENTER 707;Rang

PRINT

40

END

50

After running this program, the controller displays:

Introduction to

2-4

Rang

Programming

Instrument

an

.1

Denite-Length Block Response Data

Denite-length block response data allows any type of device-dependent data to be transmitted

over the system interface as a series of 8-bit binary data bytes. This is particularly useful for

sending large quantities of data or 8-bit extended ASCII codes. The syntax is a hash sign ( # )

followed by a non-zero digit representing the number of digits in the decimal integer. After the

non-zero digit is the decimal integer that states the number of 8-bit data bytes being sent. This

is followed by the actual data.

For example, for transmitting 80 bytes of data, the syntax would be:

The

\2"

states

the

number

of

digits

that

follow

,

and

\80"

states

number of

the

bytes to

be

transmitted.

Multiple

can

ou

Y

also

must

reading

could

you

Results$

ENTER

Queries

send multiple

them back

read

into a

back

them

the result

read

command:

the

with

707;Results$

queries

to

within a

string variable

of the

instrument

the

single

query

program

into

or

:TIMEB

.

program

This

within

message

multiple

single

a

numeric

ASE:RANGE?;DELA

be

can

variables

into

Y?

but

message

,

accomplished

example

or

F

.

string

the

you

either

by

,

variable

When you read the result of multiple queries into string variables, each response is separated

by a semicolon. For example, the response of the query :TIMEBASE:RANGE?;DELAY? would

be:

<range_value>;<delay_value>

or

F

numeric

values,

multiple

numeric

variables

can

used:

be

ENTER 707;Result1,Result2

Introduction

to Programming

Instrument

an

2-5

Instrument Status

Status registers track the current status of the instrument. By checking the instrument

status, you can nd out whether an operation has been completed, whether the instrument

is receiving triggers, and more. Refer to chapter 14, \Summary Subsystem," for for more

information.

DIGitize Command

The ACQUIRE and WAVEFORM subsystems are subsystems that aect the DIGITIZE command.

The DIGITIZE command is used to capture a waveform in a known format which is specied by

the ACQUIRE subsystem. When the DIGITIZE command is sent to an instrument, the specied

channel signal is digitized with the current ACQUIRE parameters.To obtain waveform data,

you must specify the WAVEFORM parameters for the waveform data prior to sending the

:WAVEFORM:DATA? query.

The number of data points comprising a waveform varies according to the number requested

in the ACQUIRE subsystem. The ACQUIRE subsystem determines the number of data points,

type

specify

to

acquisition,

of

exactly

and

what

number

the

of averages

digitized information

used by

will contain.

the DIGITIZE

Atypical

command. This

setup is:

allows

you

OUTPUT

707;":ACQUIRE:TYPE

707;":ACQUIRE:COMPLETE

707;":WAVEFORM:SOURCE

707;":WAVEFORM:FORMAT

707;":ACQUIRE:COUNT

707;":ACQUIRE:POINTS

707;":DIGITIZE

AVERAGE"<terminator>

100"<terminator>

CHANNEL1"<terminator>

WORD"<terminator>

4"<terminator>

500"<terminator>

CHANNEL1"<terminator>

OUTPUT 707;":WAVEFORM:DATA?"<terminator>

least

the

four

This setup

data record

places the

to be

waveform will

500

not be

instrument

This

.

points

stored into

the

into

means

memory

average

when

that

until

500

mode

the

points

four

with

DIGITIZE

have

averages

command

been

and

is

averaged

denes

received,

at

times.

After receiving the :WAVEFORM:DATA? query, the instrument will start passing the waveform

information when addressed to talk.

Digitized waveforms are passed from the instrument to the controller by sending a numerical

representation of each digitized point. The format of the numerical representation is

controlled

with

AVEFORM:FORMA

:W

the

command

T

and

may

selected

be

as

WORD

BYTE,

,

or

COMPRESSED.

The easiest

method

entering

of

digitized

a

waveform

format and place the information in an integer array

from

. The data point is represented by

instrument

the

signed sixteen bit integers whose values range from 0 to 32,640. Y

use the

to

is

ou must scale the integers

WORD

to determine the voltage value of each point. These integers are passed starting with the

leftmost point of the active waveform. F

or more information, refer to the chapter \W

aveform

Subsystem."

Introduction to

2-6

Programming

Instrument

an

Interface Functions

This section describes the interface functions and some general concepts of the HP-IB.In

general, these functions are dened by IEEE 488.2. They deal with general bus management

issues, as well as messages which can be sent over the bus as bus commands.

Interface Capabilities

The interface capabilities of the HP 70703A, as dened by IEEE 488.2 are SH1, AH1, T5, L4,

E2.

and

SR1,

RL1, PP1,

DC1, DT1,

C0,

3

Command

HP-IB

The

command

addresses

data

messages

command

has

mode

and

when

mode

across the

and responses

and

modes

two

when

various

the

Data

the

bus

TN

A

bus

Concepts

operation:

of

line

TN

A

commands

false

is

line

device-dependent

The

.

found

in

command

true

is

such

,

The

.

Chapters

.

The

as

data

5

mode

command

group

a

mode

messages

through

and

mode

execute

used

is

include

of

18

data

this

is

trigger

convey

to

all

manual.

The

.

mode

send

to

used

(GET).

device-dependent

instrument

the

of

bus

The

is

talk

bus

in

and

is

listen

in

Addressing

The instrument is always in addressed (talk/listen) mode.Addressed mode is used when

the instrument will operate in conjunction with a controller. When the instrument is in the

true:

addressed

device

Each

mode,

on

the

following

HP-IB

is

resides

at

a

particular

address,

ranging

from

30.

to

0

The active controller species which devices will talk, and which will listen.

An instrument, therefore

, may be talk addressed, listen addressed, or unaddressed by the

controller.

If the controller addresses the instrument to talk, it will remain congured

to talk until it

receives an interface clear message (IFC), another instrument's talk address (OTA), its own

listen address (MLA), or a universal untalk command (UNT).

the

controller

If the

receives

command

interface

an

(UNL).

addresses

clear

instrument

the

message

(IFC),

to

its

listen,

own

remain

will

it

talk address

congured

A),

(MT

or

a

listen

to

universal

Interface

it

until

unlisten

Functions 3-1

Bus Commands

The following commands are IEEE 488.2 bus commands (ATN true). IEEE 488.2 denes many

of the actions which are taken when these commands are received by the instrument.

Device Clear (DCL)

The device clear (DCL) or selected device clear (SDC) commands clear the input and output

buers, reset the parser, and clear any pending commands.

Group Execute Trigger (GET)

The group execute trigger (GET) command arms the trigger which is the same action produced

by sending the RUN command.

Interface Clear (IFC)

The interface clear (IFC) command halts all bus activity. This includes unaddressing all

listeners and the talker, disabling serial poll on all devices, and returning control to the system

controller

.

LED

ST

Indicators

CT

A

TUS

A

indicates

lights

the

that

when:

keyboard

any Display

of the

Display

an oscilloscope

master module

HP

the

of

function

ddress

A

a

is

,and

70703A

display

indicates

Map

slave

being

is

it

digitizing

is

another

to

allocated

oscilloscope

the

HP-MSIB

the

at

oscilloscope

by

used

oscilloscope

the

to

(for

address

master

the

active

is

example

of

designated

is

that

oscilloscope

The A

.

when

,

oscilloscope).

the

.

CTIVE

the

a

as

LED

cursor

STAUS ERR indicates errors.

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

disabled.

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

.

which

in

state

a

.

, power-on condition).

the

module

ready to

is

send

information

, operation

to

the

HP-IB

TLK

HP-IB SRQ

controller

indicates

controller

indicates a condition requested or set by the user (for example

complete status

Interface Functions

3-2

4

Programming and Documentation Conventions

This section covers conventions which are used in programming the instrument, as well as

conventions used in the remainder of this manual. This chapter contains a detailed description

of the command tree and command tree traversal. For more information on command syntax,

refer to the appendix \Message Communication and System Functions."

Truncation Rules

truncation rule

The

the rst

is

fourth

The

for the

four characters

character

is a

mnemonics used

of the

keyword unless:

vowel, then

the

in headers

mnemonic

and

is

the

alpha

rst

arguments

three

is:

characters

of

the

mnemonic

The

keyword.

This

Some

table

will

rule

examples

4-1.

not

of

be

how

used

the

length

the

if

truncation

able

T

exactly four

of

rule

4-1.

the

keyword

applied

is

Mnemonic

is

various

to

Truncation

Longform Shortform

RANGE RANGE

ATTERNPATT

P

TIME TIME

DELAY DEL

characters

commands

are

.

shown in

Programming

and Documentation

Conventions

4-1

Figure

4-1.

The

HP

70703A

Command

Tree

Programming and

4-2

Documentation

Conventions

Figure 4-2. The HP 70703A Command Tree (continued)

Command Tree

commands

shows

command

The

commands

the

tree

to

(gure

each

4-1)

other

The IEEE

.

command tree since they do not aect the

all

common

488.2

position of the parser within the tree

(linefeed ASCII decimal 10) has been sent to the

of the command tree

.

the

of

<NL>

of

the

in

commands

HP 70703A

are

and

not

relationship

the

listed

part

as

. After a

instrument, the parser will be set to the \root"

Programming

and Documentation

Conventions

4-3

Command Types

The commands for this instrument can be placed into three types:

Common Commands

Root Level Commands

Subsystem Commands

Common Commands

Common commands are independent of the tree, and do not aect the position of the parser

within the tree. These dier from root level commands in that root level commands place the

parser back at the root, such as *RST.

Root Level Commands

The root level commands reside at the root of the command tree. These commands are always

parsable if they occur at the beginning of a program message, or are preceded by a colon, such

as :AUTOSCALE.

Subsystem

TIMEB

Tree

ASE commands

Traversal

Command

the

from

compound

colons

by

tree:

the

leading colon

A

byte)

character of

rst

Commands

commands are

headers

command

header

mnemonic

The

.

places the

.

Rules

created

are

tree

compound

A

.

<

a

or

parser

a program

grouped together

traversing

by

would

4-1

gure

in

header

the

header

contains

message

of

root

.

created

program

at

under

down

be

header

a

is

no

terminator

command

the

of

common

a

command

the

node

tree

\:CHANNEL1:RANGE".

more

or

two

of

made

following

The

spaces

.

>

tree

(either

A

.

NL

<

a

leading

the

legal

A

.

This

mnemonics

rules

or

>

colon

tree

is

apply

EOI

is

as

such

,

command

referred

traversing

to

on

true

colon

a

the

header

to

separated

the

that

Executing a subsystem command places you in that subsystem (until a leading colon or a

<

program message terminator>is found). In the Command Tree, gure 4-1, use the last

mnemonic in the compound header as a reference point (for example, RANGE). Then nd the

last colon above that mnemonic (CHANNEL1:), and that is where the parser will be. Any

command below that point can be sent within the current program message without sending

(OFFSET).

mnemonic(s)

the

which

appear above

them

Examples

as

last

is

a

the

The OUTPUT statements are written using HP B

controller. The quoted string is placed on the bus

(CRLF).

Example 1

OUTPUT 707;":CHANNEL1:RANGE 0.5;OFFSET 0"

Programming and

4-4

Documentation

Conventions

ASIC 5.0 on a HP 9000 Series 200/300

, followed by a carriage return and linefeed

Comments

The colon between CHANNEL1 and RANGE is necessary, CHANNEL1:RANGE is a compound

command. The semicolon between the RANGE command and the OFFSET command is the

required<program message unit separator>.

The OFFSET command does not need CHANNEL1 preceding it, since the CHANNEL1:RANGE

command set the parser to the CHANNEL1 node in the tree.

Example 2

OUTPUT 707;":TIMEBASE:REFERENCE CENTER;DELAY 0.00001"

or

OUTPUT 707;":TIMEBASE:REFERENCE CENTER"

OUTPUT 707;":TIMEBASE:DELAY 0.00001"

Comments

In the rst line of Example 2, the \subsystem selector" is implied for the DELAY command in

the compound command.

DELA

The

because

command

second

A

shown

as

Example

OUTPUT

command

Y

program

<

the

.

tree

send

to

way

Example

in

3

707;":TIM:REF

must

message

these

2.

the same

in

be

terminator

commands

program message

will place

>

placing \TIMEB

by

is

CENTER;:CHAN1:OFFSET

as the

the parser

ASE:" before

0"

REFERENCE

back at

the root

the

command,

of

DELA

Y

Comments

The

leading

parser

colon

can

before

then

see

CHAN1

the

tells

CHAN1:OFFSET

the

parser

to

command.

command

the

of

root

the

to

back

go

Innity Representation

The representation of innity is 9.99999E+37. This is also the value returned when a

measurement cannot be made.

the

command

tree

.

Programming

and Documentation

Conventions

4-5

Sequential and Overlapped Commands.

IEEE 488.2 makes the distinction between sequential and overlapped commands. Sequential

commands nish their task before the execution of the next command starts. Overlapped

commands run concurrently, and therefore the command following an overlapped command

may be started before the overlapped command is completed. All the commands of the

HP 70703A are sequential.

Response Generation

IEEE 488.2 denes two times at which query responses may be buered. The rst is when the

query is parsed by the instrument, the second is when the controller addresses the instrument

to talk so that it may read the response. The HP 70703A will buer responses to a query when

the query is parsed.

Notation

following conventions

The

Conventions

are

used

operation:

."

a

but

or

enclose

HP-IB

an

example

or

F

containing

choice

both.

not

dots)

times

more

indicate

<>

::=

|

...

]

[

fg

Angular brackets

parameter or

code

dened

\is

any

in

."

\or

or

>

A

<

ellipsis

An

repeated

Square

as

statement

Indicates

>

B

<

(trailing

one

brackets

When several items are enclosed by braces, one, and only one of these elements must

be selected.

The following denitions are used:

single

A

::=

d

single

A

::=

n

<NL>::=

<sp> ::= <

ASCII

Newline or

white space

numeric

non-zero

Linefeed (ASCII decimal 10).

>

character

,

and

this

in

words

or

<

,

A

<

one

of

used

is

.

the

that

numeric

Denitions

descriptions

manual

characters

or

MSIB

::=

>

A

.

>

element

indicate

to

enclosed

0-9.

,

character

in

command.

indicates

>

B

<

from a

that the

items

,1-9.

used

are

that

example

or

F

list.

preceding element

optional.

are

of

<

A

remote

symbolize

to

can

>

<

,

(HP-IB

replaced

be

>

A

j

<

may

or

program

a

indicates

>

B

be

MSIB)

<

by

>

B

<

white space

Programming and

4-6

>

::= 0 through 32 (decimal) except

Documentation

Conventions

linefeed (decimal 10).

Syntax Diagrams

At the beginning of each of the following chapters are syntax diagrams showing the proper

syntax for each command. All characters contained in a circle or oblong are literals, and must

be entered exactly as shown. Words and phrases contained in rectangles are names of items

used with the command and are described in the accompanying text of each command. Each

line can only be entered from one direction as indicated by the arrow on the entry line.Any

combination of commands and arguments that can be generated by following the lines in the

proper direction is syntactically correct. An argument is optional if there is a path around it.

Where there is a rectangle which contains the word \space" a white space character must be

entered. White space is optional in many other places.

Command Structure

The HP 70703A programming commands are divided into three types: common commands,

root level commands, and subsystem commands. A programming command tree is shown in

gure 4-1.

Common

common

The

some

commands

Root

root

The

Subsystem

There

given

Commands

functions

do

Level

level

several

are

At

.

time

commands are

that are

the instrument

take

not

Commands

commands

Commands

subsystems

power

on,

no subsystem is selected.

Note

When a program message terminator or a leading colon (:) is sent in a program

message, the command parser is returned to the root of the command tree.

the HP

12

The

System

Acquire

Calibrate

subsystems

controls

sets the parameters for acquiring and storing data.

controls the internal calibrations

in

some

the commands

common to

control

many of

in this

command

the

70703A

functions of

basic

dened

488.2

IEEE

all

selected

a

of

out

basic

the

instrument. Only

set

parser

is

are:

oscilloscope

the

.

488.2.

IEEE

by

instruments

subsystem.

functions

one subsystem

the root

to

.

Sending

.

the

of

of the

commands

These

common

the

instrument.

may be

command tree

selected

control

any

at

, therefore

Channel

Display

controls all Y-axis oscilloscope functions

controls how waveforms, voltage and time markers, graticule, and text are displayed

and written on the screen.

waveform

Function

Measure

Summary

controls

selects

allows

the

automatic

the

monitoring

functions

math

measurements

status

the

of

.

of

be

to

oscilloscope

the

oscilloscope

the

.

made

Programming

.

calibration

and Documentation

and

test

self

Conventions

results

.

4-7

Test

controls the internal diagnostics.

Timebase

Trigger

Waveform

controls all X-axis oscilloscope functions.

controls the trigger modes and parameters for each trigger mode.

provides access to waveform data, including active data from channels and

functions as well as static data from waveform memories.

Program Examples

The program examples given for each command in the following chapters and appendices were

written on an HP 9000 Series 200/300 controller using the HP BASIC 5.0 programming language.

The programs always assume the oscilloscope is at address 707. If a printer is used, it is always

assumed to be at address 701.

In these examples, special attention should be paid to the ways in which the command/query

can be sent. The way the instrument is set up to respond to a command/query has no bearing

on how you send the command/query. That is, the command/query can be sent using the

data

value

using

of

a

or

longform

upper

can

100

sux

As

case

be

mV

(100

example

an

sent

,

shortform

or

(capital)

using

that

mV

almost any

value

100MV).

or

set

,

one exists

if

letters

could

channel

or lower

form you

be sent

range

1

for that

case (small)

wish. If

using a

100

to

command. Y

letters,

you were

decimal

by

mV

or

(.1),

sending

send

can

ou

both work

sending

exponential

an

of

one

the

channel

a

following:

the

command/query

the

,

Also

.

same

range

1

1.0E-1),

or

(1e-1

commands

OUTPUT

commands

OUTPUT

commands

OUTPUT

Note

longform

in

and

the

using

707;\:CHANNEL1:RANGE

using

shortform

in

and

decimal

.1"

exponential

an

format.

707;\:CHAN1:RANG 1E-1"

sux.

a

and

as

,

the

rst

character

letters

using lower

case

707;\:chan1:rang 100

examples

these

In

shortforms

,

mV"

the

,

colon

The space between RANGE and the argument is required.

of

the

command

is optional.

Programming and

4-8

Documentation

Conventions

Command Set Organization

The command set for the HP 70703A is divided into 14 separate groups: common commands,

root level commands, and 12 sets of subsystem commands. Each of the 14 groups of commands

is described in the following chapters. Each of the chapters contain a brief description of

the subsystem, a set of syntax diagrams for those commands, and nally, the commands for

that subsystem in alphabetic order. The commands are shown in the longform and shortform

using upper and lowercase letters. As an example,AUToscale indicates that the longform of

the command is AUTOSCALE and the shortform of the command is AUT. Each command

listing contains a description of the command and its arguments, the command syntax, and a

programming example.

Table 4-2 lists the commands for the HP 70703A in alphabetical order with their corresponding

subsystem or command type.

Table 4-2. Alphabetic Command Cross-Reference

Command Where Used

ACQ TEST Subsystem

ACQuistion SUMMary Subsystem

AD

ADD

ADVisory

ALL

TRigger

A

TTenuation

A

UToscale

A

BCALibration

er Root

BEEP

BLANk

BNC

CALibration

ered

CENT

CH1TO<N

CHANnel<N

>

SUMMary

FUNCtion

DISPlay

MEASure

SUMMary

CALibrate

Root

CALibrate Subsystem

Root Level

Root

SUMMary

TRIGger

CALibrate Subsystem

SUMMary Subsystem

Subsystem

Level

Subsystem

Command

*CLS Common Command

COMMunicate SYSTem Subsystem

Command Where Used

DCALibration CALibrate Subsystem

DCALibration SUMMary Subsystem

DEFine

DELay

DELay:SLOP

e TRIGger

DELay:SOURce

DESTination

DIGitize

DISPlay

DOUTput

DUTycycle

MEASure

CALibrate

MEASure

SUMMary

TIMebase

TRIGger Subsystem

MEASure Subsystem

Root Level

SUMMary

CALibrate

MEASure

Subsystem

Command

Subsystem

ECL CHANnel Subsystem

ERASe Root Level Command

ERRor SYSTem Subsystem

*ESE Common Command

*ESR Common Command

are

COMP

COMPlete

MEASure

CQuire

A

Subsystem

CONDition TRIGger Subsystem

CONNect DISPlay Subsystem

COUNt ACQuire Subsystem

COUNt WAVeform Subsystem

COUPling CHANnel Subsystem

CURSor MEASure Subsystem

eform

Subsystem

A

D

A

T

A

D

SUMMary

V

A

W

Art

EST

ESTOp

MEASure

Subsystem

FALLtime MEASure Subsystem

FIELd TRIGger Subsystem

FORMat DISPlay Subsystem

FORMat WAVeform Subsystem

FREQuency MEASure Subsystem

GAIN SUMMary Subsystem

Subsystem

em

GPIB:ST

Ticule

GRA

e

T

A

Programming

SYST

DISPlay

Subsystem

and Documentation

Conventions

4-9

Table 4-2. Alphabetic Command Cross-Reference (continued)

Command Where Used

HEADer SYSTem Subsystem

HFReject CHANnel Subsystem

HOLDo TRIGger Subsystem

HYSTeresis SUMMary Subsystem

IDENtier DISPlay Subsystem

*IDN Common Command

INTerpolator SUMMary System

INVert FUNCtion Subsystem

LEVel TRIGger Subsystem

LFReject CHANnel Subsystem

LIMitest MEASure Subsystem

LINE DISPlay Subsystem

LINE TRIGger Subsystem

LOGic TRIGger Subsystem

LONGform SYSTem Subsystem

Level

Subsystem

Command

Subsystem

Command

Subsystem

er MEASure

LOW

*LRN

TCalibrate

L

TER

L

TRigger

L

Common

CALibrate

Root

SUMMary

Command Where Used

PERiod MEASure Subsystem

PERSistance DISPlay Subsystem

POINts ACQuire Subsystem

POINts WAVeform Subsystem

POLarity TRIGger Subsystem

POSTfailure MEASure Subsystem

PREamble WAVeform Subsystem

PRECision MEASure Subsystem

PRESet SUMMary Subsystem

PREShoot MEASure Subsystem

PROBe CHANnel Subsystem

PROBe SUMMary Subsystem

PWIDth MEASure Subsystem

QUALify TRIGger Subsystem

QUEStionable SUMMary Subsystem

RAM

RANGe

SUMMary Subsystem

Subsystem

TEST

CHANnel

FUNCtion

TIMebase

Susbsytem

Subsystem

MEASure

MODE

Tiply

MUL

DISPlay

MEASure

TIMebase

TRIGger

FUNCtion

NPRotect SUMMary

NVOLatile

SUMMary Subsystem

Subsystem

Susystem

Subsystem

NWIDTH MEASure Subsystem

OCCurance TRIGger Subsystem

OCCurance:SLOPe TRIGger Subsystem

OCCurance:SOURce TRIGger Subsystem

OFFSet

ONLY

CHANnel

FUNCtion

SUMMary

FUNCtion Subsystem

Subsystem

*OPC Common Command

*OPT Common Command

OVERshoot MEASure Subsystem

PATH TRIGger Subsystem

PCALibration Calibrate Subsystem

*RCL

erence

REF

ort

REP

RESults

RISetime

Common

TIMebase

CALibrate

MEASure

ROM SUMMary

ROM TEST

Command

Subsystem

*RST Common Command

RUN Root Level Command

*SAV Common Command

SCALibration CALibrate Subsystem

SCRatch

SCReen

SECurity:ST

Te

A

MEASure

DISPlay

CALibrate

SENSitivity TRIGger

Subsystem

SERial Root Level Command

SETup SYSTem Subsystem

SLOPe TRIGger Subsystem

SOURce MEASure Subsystem

SOURce TRIGger Subsystem

Programming and

4-10

Documentation

Conventions

Table 4-2. Alphabetic Command Cross-Reference (continued)

Command Where Used

SOURce WAVeform Subsystem

*SRE Common Command

STANdard TRIGger Subsystem

STATistics MEASure Subsystem

STATus DISPlay Subsystem

STATus Root Level Command

*STB Common Command

STOP Root Level Command

STORe Root Level Command

SUBTract FUNCtion Subsystem

SYSTem SUMMary Subsystem

TALL TEST Subsystem

TDELta MEASure Subsystem

TER Root Level Command

TEST SUMMary Subsystem

TIME

TIMebase

TMARker

TMAX

TMIN

TNULI

TRIGger

*TRG

*TST Common

TSTArt

SUMMary Subsystem

DISPlay

SUMMary

DISPlay

MEASure

CALibrate

SUMMary

Common

Subsystem

Command

MEASure Subsystem

TSTOp MEASure Subsystem

TTL CHANnel Subsystem

TVOLt MEASure Subsystem

TYPE ACQuire Subsystem

TYPE

W

AV

eform

Subsystem

Command Where Used

UNITs MEASure Subsystem

UPPer MEASure Subsystem

VACRms MEASure Subsystem

VAMPlitude MEASure Subsystem

VAVerage MEASure Subsystem

VBASe MEASure Subsystem

VDCRms MEASure Subsystem

VDELta MEASure Subsystem

VERSus FUNCtion Subsystem

VERTical CALibrate Subsystem

VFIFty MEASure Subsystem

VIEW Root Level Command

VMARker DISPlay Subsystem

VMAX MEASure Subsystem

VMIN

VPP

VRELative

VRMS

Art

VST

VSTOp

VTIMe

VTOP

AI

*W

WINDow

WINDow:DELay

WINDow:RANGe TIMebase

XINCrement W

MEASure Subsystem

MEASure

Common

TIMebase

Subsystem

Command

Subsystem

AV

eform

Subsystem

XORigin WAVeform Subsystem

XREFerence WAVeform Subsystem

YINCrement WAVeform Subsystem

YORigin WAVeform Subsystem

YREF

erence

WA

eform

V

Subsystem

Programming

and Documentation

Conventions

4-11

5

Common Commands

The Common commands are dened by the IEEE 488.2 standard. These commands will be

common to all instruments that comply with this standard. They control some of the basic

instrument functions, such as instrument identication and reset, reading the learn (instrument

setup) string, how status is read and cleared, and how commands and queries are received and

processed by the instrument.

Common commands can be received and processed by the HP 70703A whether they are sent

over the HP-IB or MSIB as separate program messages or within other program messages.

If an instrument subsystem has been selected and a common command is received by the

instrument, the instrument will remain in the selected subsystem. For example, if the program

message \ACQUIRE:COUNT 1024; *CLS; TYPE AVERAGE" is received by the instrument, the

would

instrument

the

be

not

example,

For

GE" would

VERA

A

example

this

.

type

the

set

will

some

if

case

the program

CQUIRE must

,:A

acquire

the

set the

count

type

other

message \:A

acquire

be

type

and

command

of

CQUIRE:COUNT

count,

sent

complete

again

in

and

,

were

order

clear

received

autoscale

the

to

the

1024;

reenter

status

information.

within

UTOSCALE;

:A

then

,

CQUIRE

A

the

set

program

the

This

message

CQUIRE:TYPE

:A

acquire

type

subsystem

.

and

In

set

Refer

Note

to

gure

Common

for

5-1

the

of

Each

register

.

information

registers

chapter

to

refer

By

and

commands

status

setting

wish

you

how

14,

registers

bits

the

use

to

the

use

to

\SUMMARY

syntax

diagram.

mentioned

enable

the

in

further

or

F

.

status

Subsystem."

this

in

register

information

chapter

you

available

enable (mask)

an

has

can select

how to

on

from

the

read

instrument,

this

status

the

status

Common

Commands 5-1

Common Commands

5-2

Figure 5-1. Common Commands Syntax Diagram

*CLS

Clear Status

The *CLS common command clears the status data structures, including the device dened

error queue. This command also clears the Request-for-OPC ag.

If the *CLS command immediately follows a PROGRAM MESSAGE TERMINATOR, the output

queue and the MAV (message available) bit will be cleared.

Command Syntax

*CLS

Example

OUTPUT 707;"*CLS"

Common

Commands 5-3

*ESE

Event Status Enable

The *ESE command sets the Standard Event Status Enable Register bits. The Standard Event

Status Enable Register contains a mask value for the bits to be enabled in the Standard

Event Status Register. A one in the Standard Event Status Enable Register will enable the

corresponding bit in the Standard Event Status Register, a zero will disable the bit. Refer to

table 5-1 for information about the Standard Event Status Enable Register bits, bit weights,and

what each bit masks.

The *ESE query returns the current contents of the register.

Command Syntax

*ESE <mask>

Where:

<mask> ::= 0 to 255

Example

*ESE

Enable

8"

command

8

Register

will

.

enable

OUTPUT

example

this

In

Standard

Query

707;"*ESE

,

Event

Syntax

the

Status

*ESE?

ormat

Returned

F

Where:

<mask> ::= 0 to 255 (integer - NR1 format)

Example

OUTPUT 707;"*ESE?"

ENTER 707;Event

PRINT Event

DDE

(device

dependent

errors)

bit 3

of the

Common Commands

5-4

Table 5-1. Standard Event Status Enable Register

Event Status Enable Register

(High - Enables the ESR bit)

Bit Weight Enables

7 128 PON - Power On

6 64 Not Used

5 32 CME - Command Error

4 16 EXE - Execution Error

3 8 DDE - Device Dependent Error

2 4 QYE - Query Error

1 2 Not Used

0 1 OPC - Operation Complete

Common

Commands 5-5

*ESR

Event Status Register

The *ESR query returns the contents of the Standard Event Status Register.

Note

Reading the register clears the Standard Event Status Register.

Query Syntax

*ESR?

Returned Format

Where:

<status> ::= 0 to 255 (integer - NR1 format)

Example

5-2

Status

read the

shows

707;Event

Event

707;"*ESR?"

bit

each

the

Register

,

byte

.

in

value

the

Event

returned

Status

is

Register

the

OUTPUT

ENTER

PRINT

able

T

Event

time

you

total

and

bit

its

weights

weight.

all

of

When

bits

that

you

are

read

high

the

at

the

able

T

Bit Bit

eight

W

Bit

Name

7 128 PON 1

5-2. Standard

an

=

Event Status

to

OFF

Condition

ON transition

6 64 0 = NOT used - always 0

5 32 CME 0 = no command errors

1 = a command error has been detected

4 16 EXE 0 = no execution error

error

dependent

3 8 DDE 0

=an

1

=

1

execution

device

no

device

a

2 4 QYE 0 = no query errors

1 = a query error has been detected

1 2 0 = NOT used - always 0

0 1 OPC 0 = operation is not

complete

1 = operation is complete

0=False = Low

High

=

True

=

1

Register

has occurred

been

has

errors

error has

detected

been

Common Commands

5-6

*IDN

Identication Number

The *IDN query allows the instrument to identify itself. It returns the string:

"HEWLETT-PACKARD,70703A,<XXXXZYYYYY><YYMMDD>"

Where:

<XXXXZYYYYY> ::= the serial number of this instrument. The Z

parameter indicates the country of manufacture

(example, A for America, U for U.K.).

<YYMMDD> ::= the software revision of this instrument. The first

two parameters (YY) represent the year, the second

two parameters (MM) represent the month and the final

two parameters (DD) represent the day of the month.

An *IDN query must be the last query in a message. Any queries after the *IDN query in this

program message will be ignored.

Query

Syntax

*IDN?

ormat

Returned

F

HEWLETT-PACKARD,70703A,XXXXAYYYYY,YYMMDD<NL>

Example

DIM

ENTER

PRINT

Id$[50]

707;Id$

Id$

OUTPUT

707;"*IDN?"

Common

Commands 5-7

*LRN

Learn

The *LRN query returns a program message that contains the current state of the instrument.

This command allows you to store an instrument setup in the controller. The stored setup can

then be returned to the instrument when you want that setup at a later time. This command

performs the same function as the :SYSTEM:SETUP? query. The data can be sent to the

instrument using the :SYSTEM:SETUP command.

Note

The returned header for the *LRN query is :SYSTEM:SETUP.

Query Syntax

*LRN?

Returned Format

:SYSTem:SET

Where:

#800001024<learn

::=

string

is

1024

The

<setup>

learn

Example

Lrn$[2000]

DIM

OUTPUT

ENTER

707;"*LRN?"

USING

707

bytes

data

"-K";Lrn$

string><NL>

length.

in

Common Commands

5-8

*OPC

Operation Complete

The *OPC command will cause the instrument to set the operation complete bit in the Standard

Event Status Register when all pending device operations have nished.

The *OPC query places an ASCII \1" in the output queue when all pending device operations

have nished.

Command Syntax

*OPC

Example

OUTPUT 707;"*OPC"

Query Syntax

*OPC?

ormat

Returned

1<NL>

F

Example

OUTPUT 707;":AUTOSCALE;*OPC?"

ENTER 707;Op$

Common

Commands 5-9

*OPT

Option

The *OPT query is used to report the options installed in the instrument. The standard

HP 70703A will return a zero (0). Other HP 70703A's with options will return a comma

separated list of option identiers.

Query Syntax

*OPT?

Returned Format

0<NL>

Example

OUTPUT 707;":AUTOSCALE;*OPT?"

ENTER 707;Opt$

Common Commands

5-10

*RCL

Recall

The *RCL command restores the state of the instrument from the specied save/recall register.

An instrument setup must have been stored previously in the specied register. Registers 1

through 4 are general purpose and can be used with the *SAV command. Register 0 is special

because it recalls the state that existed before the last AUTOSCALE, RECALL, ECL, or TTL

operation.

Note

Command Syntax

*RCL <rcl_register>

Where:

<rcl_register> ::= 0 through 4

Example

OUTPUT

An error message will appear on the error queue if nothing has been previously

saved in the specied register.

707;"*RCL

3"<NL>

Common

Commands 5-11

*RST

Reset

The *RST command places the instrument in a known state. Refer to table 5-3 for the reset

conditions.

Command Syntax

*RST

Example

OUTPUT 707;"*RST"

Table 5-3. Reset Conditions for the HP 70703A

Parameter Reset Description

BNC PROBe Probe compensation ON, Trigger Out OFF.

SYSTem:

shortform.

LONGform OFF Character

CQuire:

A

COMPlete 100 A

COUNt 88hits

POINts 500 A

e

TYP

NORMAL A

returned

data

cquisition complete

per time

cquisition

bucket

record

complete

in

at

when

completion

for

contains 500

1 count.

in

100%.

pts

(will

return

\1"

NORMal

in

mode).

.

Channels

ON,

CHANnel: 1 Channel

COUPling DC Coupling

HFReject OFF Internal

LFReject OFF Internal high

OFFSet 0VCenterscreen

PROBe 1:1 Probe

RANGe 4VFull-scale

1

on

DC

to

low pass

pass lter

is

attenuation

vertical

0

lter

V

DISPlay:

CONNect OFF Connect dots on traces OFF.

FORMat 1 One trace display area.

GRATicule AXIS Display AXIS graticule.

minimum.

markers

set to

OFF

PERSistence SINGle P

ersistence

TMARker OFF Time

VMARker OFF V

oltage

all

on

factor

scale

.

OFF

2-4

channels

on

OFF

channels

all

1:1

is

V

4

is

on

.

all

on

channels

.

channels

all

.

Common Commands

5-12

Table 5-3. Reset Conditions for the HP 70703A (continued)

Parameter Reset Description

FUNCtion: OFF FUNCtion 1 and 2 OFF.

MEASure:

DESTination OFF Destination function OFF.

LIMittest OFF Limit test function OFF.

LOWer 10 Lower measurement threshold to 10%.

MODe STANdard Measurement performed using IEEE standard denitions and thresholds.

POSTfailure STOP Limit test stopped after violation.

SOURce CHANnel1 Measurement source to channel 1.

STATistics OFF Current measurement is returned.

UNITs PERCent Threshold units to percent.

UPPer 90 Upper measurement threshold to 90%.

TIMebase:

DELay 0 s Time base delay to 0 seconds.

MODe AUTo Time base mode set to auto trigger.

.

ms

1

to

set

base to

base

time

to

OFF

delay

full

center

.

to

scale

of sweep

seconds

0

horizontal

.

time

.

ms

1

to

RANGe 1msFull-scale

REF

erence

CENTerDelay

reference

WINDow: OFF Second time

DELay 0sSecond

RANGe 1msSecond

time

horizontal

TRIGger:

.

ns

HOLDo TIMe

el

LEV

MODe EDGe Edge

,40

Holdo

0VTrigger

trigger mode

SENSitivity NORMal Noise reject

SLOP

e

POSitive P

ositive

SOURce CHANnel1 Channel

to

set

level

edge

produces

1

40

at

OFF.

trigger

0

.

V

active

.

trigger

.

WAVeform:

FORMat BYTE Waveform data output to BYTE.

SOURce CHANnel1 Channel 1 source for waveform commands.

Common

Commands 5-13

*SAV

SAVE

The *SAV command stores the current state of the device in a save register. The data

parameter is the number of the save register where the data will be saved. Registers 1 through

4 are valid for this command.

Command Syntax

*SAV <save_register>

Where:

<save_register> ::= 1 through 4

Example

OUTPUT 707;"*SAV 3"

Common Commands

5-14

*SRE

Service Request Enable

The *SRE command sets the Service Request Enable Register bits. The Service Request Enable

Register contains a mask value for the bits to be enabled in the Status Byte Register.Aone

in the Service Request Enable Register will enable the corresponding bit in the Status Byte

Register, a zero will disable the bit. Refer to table 5-4 for the bits in the Service Request Enable

Register and what they mask. The *SRE query returns the current value.

Command Syntax

*SRE <mask>

Where:

<mask> ::= 0 to 255

Example

OUTPUT 707;"*SRE 16"

generated

be

Note

example enables

This

available

in

the

output

a service

queue

request

When

.

to

a message

high.

Query

Syntax

*SRE?

ormat

Returned

F

Where:

<mask> ::= sum of all bits that are set - 0 through 255

(integer - NR1 format)

Example

OUTPUT

ENTER

PRINT

707;"*SRE?"

707;Value

Value

when

is available

a

the

message

bit

V

MA

is

will

be

Common

Commands 5-15

Table 5-4. Service Request Enable Register

Service Request Enable Register

(High - Enables the SRE bit)

Bit Weight Enables

7 128 not used

6 64 bit ignored - always zero

5 32 ESB - Event Status Bit

4 16 MAV - Message Available

3 8 LTF - Limit Test Fail

2 4 QUE - Questionable Status

1 2 bit ignored - always zero

0 1 TRG - Trigger

Common Commands

5-16

*STB

Status Byte

The *STB query returns the current value of the instrument's status byte. The (Master

Summary Status) bit is reported on bit 6 instead of the RQS (request service) bit. The MSS

indicates whether or not the device has at least one reason for requesting service.Referto

table 5-5 for the meaning of the bits in the status byte.

Note

To read the instrument's status byte with RQS reported on bit 6, use the HP-IB

Serial Poll.

Query Syntax

*STB?

Returned Format

Where:

0

<value>

::=

Example

OUTPUT 707;"*STB?"

ENTER 707;Value

PRINT

Value

Bit Bit

eight

W

7 128 | 0

6 64 RQS/MSS 0 = instrument has no reason for service

5 32 ESB 0 = no event status conditions have occurred

4 16 MAV 0 = no output messages are ready

3 8 L

2 4 QUE 0 = no questionable status condition has occurred

1 2 0 = not used

0 1 TRG 0 = no trigger has occurred

0=False = Low

True

=

1

through

Bit

Name

TF

High

=

NR1)

The

-

Status

Byte

Register

255

able

T

(integer

5-5.

Condition

used

not

=

1 = instrument is requesting service

1 = an enabled event status condition has occurred

ready

=an

1

=

0

no

output

limit

message

has

test

is

failed

1 = limit test has failed

a questionable status condition has occurred

1=

1 = a trigger has occurred

Common

Commands 5-17

*TRG

Trigger

The *TRG command has the same eect as the Group Execute Trigger (GET). This eect is as if

the RUN command had been sent.

Command Syntax

*TRG

Example

OUTPUT 707;"*TRG"

Common Commands

5-18

*TST

Test

The *TST query causes the instrument to perform a self-test. The result of the test will be

placed in the output queue.

Note

Prior to sending this command all front panel inputs must be disconnected.

A 0 indicates the test passed and a non-zero value indicates the test failed. If a test fails, refer

to the troubleshooting section of the Service Manual.

Query Syntax

*TST?

Returned Format

Where:

::=

0

non-zero

or

value

Where:

indicates

0

Non-zero

the

indicates

the

test

failed.

passed.

test

Example

OUTPUT

ENTER

PRINT

707;"*TST?"

707;Result

Result

Common

Commands 5-19

*WAI

Wait

The *WAI command has no function in the HP 70703A, but is parsed for compatibility with

other instruments.

Command Syntax

*WAI

Example

OUTPUT 707;"*WAI"

Common Commands

5-20

6

Root Level Commands

The Root Level commands control many of the basic operations of the oscilloscope. These

commands will always be recognized by the parser if they are prexed with a colon, regardless

of current command tree position. After executing a root level command, the parser is

positioned at the root of the command tree.

Figure 6-1 lists the Root Level commands syntax diagram.

Figure

6-1.

Root

Level

Commands

Syntax

Diagram

Level Commands

Root

6-1

Figure

6-2.

Root

Level

Commands

Syntax

Diagram

(continued)

AUToscale

The AUTOSCALE command causes the oscilloscope to evaluate all input signals and set

the correct conditions to present the signals. When the AUTOSCALE command is sent, the

set:

following

the

conditions

vertical sensitivity

are

the vertical oset

the trigger to edge mode with minimum persistence

trigger level, holdo, and slope

the

the timebase range

as required

In addition, the A

markers

all measurements

functions

windows

memories

dots

connect

6-2

the

Root Level

Commands

UTOSCALE command turns o:

If signals are present on more than one input, the sweep will be triggered on the signal closest

to channel 1. If a signal is not present on channel 1 then the oscilloscope will be triggered on

channel 2. If a signal is not present on channel 2 then the oscilloscope will be triggered on

channel 3, and so on. If no signals are found on any input, the oscilloscope is returned to its

former state.

Command Syntax

:AUToscale

Example

OUTPUT 707;":AUTOSCALE"

BEEPer

The BEEPER command controls any audio beeper available to the instrument when the

.

instrument

has

keyboard

a

established

link

with

an

MMS

keyboard

device

used

beeper

This

to

need

Sending

available

Command

:BEEPer

is

be

the

and

drawn

to

BEEPER

enabled.

Syntax

{{ON|1}|{OFF|0}}

Example

OUTPUT

707;":BEEPER

OUTPUT 707;":BEEPER"

Query Syntax

:BEEPer?

ormat

Returned

F

{1|0}<NL>

Where:

user

the

by

users

the

command with

ON"

interface

attention.

no arguments

Enable

Sound beeper

to

beeper

signal

certain

will

conditions

sound

if available

the

(such

beeper

if

as

it

errors)

currently

is

which

=

1 ::= ON

0 ::= OFF

Example

OUTPUT 707;"BEEPER?"

ENTER

PRINT

707;State

State

Level Commands

Root

6-3

BLANk

The BLANK command causes the instrument to turn o or stop presenting the specied

channel, function, pixel memory, or waveform memory.To blank a specied channel use

the command :BLANK CHANNELf1j2j3j4g.To blank a waveform memory use :BLANK

WMEMORYf1j2j3j4g, to blank a current display use the command :BLANK PMEMORY0, and to

blank a function use the command :BLANK FUNCTIONf1j2g.

Command Syntax

:BLANk <display>

Where:

<display> ::= {CHANnel{1|2|3|4}|FUNCtion{1|2}|

WMEMory{1|2|3|4}|PMEMory0}

Example

OUTPUT 707;":BLANK CHANNEL1"

BNC

PROBE

to

outputs

returns

.

selects

command

BNC

The

connector

BNC

TRIGGER

The

BNC

mode

query

BNC

connector

Command

{PROBe|TRIGger}

:BNC

Syntax

Example

OUTPUT 707;":BNC PROBE"

Query

Syntax

:BNC?

Returned F

ormat

{PROBe|TRIGger}<NL>

Example

a

the

or

rising

output

TRIGGER.

edge

current

mode

when

mode

The

for

the

of

PROBE

internal

an

the

Probe

mode

Probe

Compensation

outputs

trigger

a

occurs

Compensation

A

square

.

C

A

Calibrator Output

C

signal and

wave

Calibrator

Output

the

6-4

OUTPUT

ENTER

PRINT

Root Level

707;":BNC?"

707;Mode$

Mode$

Commands

DIGitize

The DIGITIZE command is used to acquire waveform data for transfer over the HP-IB or MSIB.

It causes an acquisition to take place on the specied channel(s) with the resulting data being

placed in the channel buer.

The ACQUIRE subsystem commands are used to set up conditions such as TYPE, number of

POINTS, and the COUNT for the next DIGITIZE command. See the ACQUIRE subsystem for a

description of these commands.To determine the actual number of points that are acquired

and how the data will be transferred, refer to the WAVEFORM Subsystem commands.For more

information on the DIGITIZE command refer to the section on the DIGITIZE command in the

chapter \Introduction to Programming an Instrument."

Note

Sending the DIGITIZE command will turn o any unused channels.

When the digitize operation is complete, the instrument is placed in the stopped mode. When

the instrument is restarted with a RUN command, the digitized data stored in the channel

buers will be overwritten. Therefore, ensure all operations that require the digitized data are

70703A.

HP

digitize

other

the

operations

parameters

command

may be

.

channels

are

.

improved if

.

through

1

two or

4.

more DIGITIZE

commands

completed

speed

The

without

sent

are

sources

The

Command

:DIGitize

the

restarting

total

before

of

changing

:DIGITIZE

the

for

Syntax

CHANnel<N>[,CHANnel<N>]

Where:

or 4.

3,

2,

1,

::=

<N>

Example

OUTPUT 707;":DIGITIZE CHANNEL1,CHANNEL2"

ERASe

ERASE command

The

erases

the

current

display

.

If the scope is running and being triggered and ERASE PMEMORY0 is executed, the instrument

will momentarily stop acquiring data, clear the contents of the current display

continue with

data acquisition.

, and then

Command Syntax

:ERASe PMEMory0

Example

OUTPUT

707;":ERASE

PMEMORY0"

Level Commands

Root

6-5

LTER

Limit Test Event Register

The LTER query allows the Limit Test Event Register to be read. The Limit Test Event Register

contains the Limit Test Fail bit. This bit is set when the limit test is active and a limit test has

failed. After the Limit Test Event Register is read, it is cleared.

A Service Request (SRQ) can only be generated when the bit transitions from 0 to 1, therefore

the bit must be cleared each time you would like a new Service Request to be generated.

Query Syntax

:LTER?

Returned Format

{1|0}<NL>

Example

OUTPUT

ENTER

PRINT

707;":LTER?"

707;Lmt$

Lmt$

RUN

manner

the

once

the

in

and

trigger

saves

the

RUN

The

the

by

timebase

dened

If

acquired

the timebase

If

command

timebase

the

mode

data.

mode is

acquires

mode

SINGLE,

in

is

AUTO

the

for

data

.

RUN

the

or TRIGGERED

active

command

,

waveform.

RUN

the

The

enables

command

data

the

acquired

is

trigger

enables

repeatedly and saves the data it acquires continuously. See the :TIMEBASE:MODE command

for a description of the various modes. The RUN query returns the current RUN state.

Command Syntax

:RUN

Example

OUTPUT 707;":RUN"

6-6

Root Level

Commands

Query Syntax

:RUN?

Returned Format

Where:

<state> ::= "1" = RUN, "0" = STOP

Example

OUTPUT 707;"RUN?"

ENTER 707;Run_state

PRINT Run_state

SERial

Serial

The

serial

this

Number

SERIAL

number

command

entered

is

unless

allows

you

the factory

at

to

need

to enter

serialize

a serial

, therefore

the instrument

number

will

this

the

in

normally

dierent

a

for

instrument.

required.

be

not

application.

instrument

The

Do

not

use

so

for

ram,

the

to

*IDN?

number

serial

The

unprotected

the

serial

This

Command

:SERial

position

number

Syntax

placed

is

part

to

of

protected

in

write

the

new

a

string

non-volatile

number

serial

returned

Where:

<string> ::= 10 character serial number within quotes

Example

OUTPUT

707;":SER

""1234U56789"""

protection

the

instrument.

.

query

switch

must

be

in

Level Commands

Root

6-7

STATus

The STATUS query indicates whether a channel, function, wmemory, or pmemory is ON or OFF.

A one indicates ON and a zero indicates OFF. PMEMORY0 indicates the current display.

Query Syntax

:STATus? <display>

Where:

<display> ::= {CHANnel{1|2|3|4}|FUNCtion{1|2}|WMEMory{1|2|3|4}|PMEMory0}

Returned Format

{0|1}<NL>

Example

OUTPUT 707;":STATUS? CHANNEL1"

ENTER

PRINT

707;Status$

Status$

STOP

command

STOP

The

command

RUN

The

Command

Syntax

:STOP

Example

OUTPUT 707;":STOP"

causes

must

the

executed

be

instrument

to restart

to

stop

acquiring

data

acquisition.

for

the

active

waveform.

6-8

Root Level

Commands

STORe

The STORE command moves a stored waveform, channel, or function to a waveform memory.

This command has two parameters. The rst is the source of the waveform. The source can

be specied as any channel, function, or waveform memory. The second parameter is the

destination of the waveform, which can only be waveform memory 1 through 4. The current

display cannot be stored as a single item.

Command Syntax

:STORe <source>,<destination>

Where:

<source> ::= {CHANnel{1|2|3|4}|FUNCtion{1|2}|WMEMory{1|2|3|4}}

<destination> ::= WMEMory {1|2|3|4}

Example

OUTPUT 707;":STORE CHANNEL2,WMEMORY4"

TER

Trigger

Event

Register

cleared.

is

allows

TER query

The

read it

is

occurred.

not

is

Request

must

event

be

(SRQ)

cleared

a

If

Service

A

the

trigger

bit

Query Syntax

:TER?

Returned Format

{1|0}<NL>

Example

OUTPUT 707;":TER?"

ENTER 707;Trg_event$

PRINT Trg_event$

A

the

one

found

can

each

Trigger

indicates

and

only

time

trigger

a

sweep is

the

generated

Register

Event

be

you would

read.

be

to

occurred.

has

auto-triggering this

the bit

when

new Service

like a

Trigger

zero

the

indicates

will

bit

When

A

transitions from

Request to

Event

trigger

a

be

not

to

0

generated.

be

Register

has

set.

therefore

1,

not

Level Commands

Root

6-9

VIEW

The VIEW command causes the instrument to turn on an active channel, function, display,or

waveform memory.

To turn on a channel use the command :VIEW CHANnelf1j2j3j4g, for the current display,

use the parameter :VIEW PMEMory0, and to turn on a function send the command :VIEW

FUNCtionf1j2g.

The BLANK command causes the instrument to turn o a specied channel, function, display,

or waveform memory.

Command Syntax

:VIEW {CHANnel{1|2|3|4}|FUNCtion{1|2}|PMEMory0|WMEMory{1|2|3|4}}

Example

OUTPUT 707;":VIEW CHANNEL1"

6-10

Root Level

Commands

System Subsystem

The SYSTEM subsystem commands control the way in which query responses are formatted.

Refer to gure 7-1 for SYSTEM subsystem commands syntax diagram.

7

Figure 7-1. SYSTEM Subsystem Commands Syntax Diagram

System

Subsystem 7-1

COMMunicate:GPIB[:STATe]

The COMMUNICATE:GPIB[:STATE] command controls the power to the HP-IB interface.

To control this instrument via HP-IB, the power to the HP-IB interface has to be enabled.

However, in large systems where this instrument is controlled over MSIB, disabling the power

to the HP-IB interface reduces the eective number of bus loads on the HP-IB interface by one.

Note

Once HP-IB is disabled (OFF), the HP 70703A will

activity until the HP-IB is enabled from the user interface or over MSIB.Use

this command with caution.

Command Syntax

:SYSTem:COMMunicate:GPIB[:STATe] {{ON|1}|{OFF|0}}

Example

OUTPUT 707;":SYSTEM:COMMUNICATE:GPIB:STATE ON"

OUTPUT 707;":SYSTEM:COMMUNICATE:GPIB ON"

Query

Syntax

:SYSTem:COMMunicate:GPIB[:STATe]?

ormat

Returned

F

{1|0}<NL>

Where:

ON

1::=

OFF

0::=

NOT

respond to any HP-IB

Example

OUTPUT 707;":SYSTEM:COMMUNICATE:GPIB?"

ENTER 707;State

PRINT State

System Subsystem

7-2

ERRor

The :SYSTEM:ERROR query outputs the next error number in the error queue over the HP-IB

or MSIB. This instrument has an error queue that is 30 errors deep and operates on a rst-in,

rst-out basis. Successively sending the query, :SYSTEM:ERROR?, returns the error numbers in

the order that they occurred until the queue is empty. Any further queries then return zeros

until another error occurs.

When the NUMBER parameter is used in the query only the numeric error code is output.

When the STRING parameter is used, the error number is output followed by a comma and

a quoted string. If no parameter is specied, then the numeric error code is output. No

parameter specied is the same as specifying NUMBER.

See table 7-1 for the error numbers.

Query Syntax

:SYSTem:ERRor? {NUMBer|STRing|(no_param)}

Returned Format

<error>[,<quoted

Where:

<error>

<quoted

::=

string> ::=

Example

Emsg$[50]

DIM

OUTPUT

ENTER

PRINT

707;":SYSTEM:ERROR?"

707;Emsg$

Emsg$

string>]<NL>

integer

an

error

alpha

code

string

specifying

the

error

condition

System

Subsystem 7-3

Table 7-1. Error Messages

Error Number Description

12 Edges required not found

70 RAM write protected

71 RAM is hardware write protected

0

100 Command error

0

101 Invalid character received

0

102 Syntax error

0

103 Invalid separator

0

104 Data type error

0

105 GET not allowed

0

108 Parameter not allowed

0

109 Missing parameter

0

112 Program mnemonic too long

0

113 Undened header

0

121 Invalid character in numbers

0

123 Numeric overow

digits

124

0

128 Numeric data

130

0

131

0

138

0

140

0

141

0

148

0

150

0

151

0

158

0

161

0

168

0

170 Expression error

0

171 Invalid expression

0

178 Expression data not allowed

0

181 Invalid outside macro denition

183

0

many

oo

T

error

Sux

Invalid

Sux

sux

not

Character

Invalid

character

Character

String

Invalid

String

Invalid

Block

Invalid

data

string data

data

block

data not

inside

not allowed

allowed

error

data

allowed

not

data

error

allowed

not

data

allowed

macro denition

System Subsystem

7-4

Table 7-1. Error Messages (continued)

Error Number Description

0

200 Execute error

0

211 Trigger ignored

0

213 Unit ignored

0

221 Setting conict

0

222 Data out of range

0

223 Too much data

0

270 Macro error

0

272 Macro execution error

0

273 Illegal macro label

0

276 Macro recursion error

0

277 Macro redenition not allowed

0

310 System error

0

314 Save/recall memory loss

0

315 Conguration memory loss

0

330

350

Self-test

Queue

failed

overow

0

400

410

420

430

440

Query

Error

INTERRUPTED

UNTERMINA

TED

DEADLOCKED

UNTERMINA

TED

after

indenite

response

HEADer

is

:SYSTEM:HEADER command

The

has

function

no

in

the

HP

70703A

but

compatibility with other instruments. Note that ON is not a valid parameter.

Command Syntax

:SYSTem:HEADer

{OFF|O}

Example

OUTPUT 707;":SYSTEM:HEADER OFF"

parsed

for

System

Subsystem 7-5

Query Syntax

:SYSTem:HEADer?

Returned Format

0<NL>

Where:

0::= OFF

Example

OUTPUT 707;":SYSTEM:HEADER?"

ENTER 707;State

PRINT State

LONGform

:SYSTEM:LONGFORM

The

format

to

how

sent

are

whole

word

70703A.

regardless

from

query

the

will

Headers

how

of

HP

be

and

the

output.

command

responses

70703A

This

arguments

LONGFORM

If

.

the

in

command

may

the

sets

LONGFORM

the

shortform.

sent

be

command

longform

If

does

to

set.

is

command

the

aect

not

HP

the

variable

which

set

is

LONGFORM

input

the

70703A

in

tells

,

OFF

to

command

messages

data

either

longform

the

alpha

is

70703A

HP

arguments

to

set

to

or

ON, the

HP

the

shortform

LONGFORM query

The

Note

returns

Even though

argument, the

the

the LONGFORM

response is

Command Syntax

:SYSTem:LONGform {{ON|1}|{OFF|0}}

Example

OUTPUT

707;":SYST:LONG

ON"

Query Syntax

:SYSTem:LONGform?

state

the

of

always

LONGFORM

command

or

1

a

command.

be

can

for

(1

0

sent

ON,

using

for

0

alpha

an

OFF).

numeric

or

System Subsystem

7-6

Returned Format

{1|0}<NL>

Where:

1 ::= ON

0 ::= OFF

Example

DIM Long$[30]

OUTPUT 707;":SYSTEM:LONGFORM?"

ENTER 707;Long$

PRINT Long$

SETup

:SYSTEM:SETUP command

The

setup

The

from the

sent

not

does

SETUP

The

controller

include

query

The

.

the

SETUP

.

preamble

outputs

query

.

current HP

the

operates the

sets

the

string

70703A

HP

contains

70703A setup

same as

as

1024

the

dened

bytes

the

in

*LRN?

the

by

setup

of

form

query

.

of

data

data.

a

in

learn

the

The

string

learn

1024

bytes

to

string

the

binary

string

learn

The

transmission

Command

:SYSTem:SETup

sent

is

#

the

is

Syntax

and

format

<setup>

received

dened

as a

the IEEE

in

Example

OUTPUT 707;":SYSTEM:SETUP <setup>"

Where:

Query

Syntax

:SYSTem:SETup?

Returned F

ormat

Where:

block

488.2

The

data.

of

specication.

format

for

the

data

System

Subsystem 7-7

Note

Example

10 DIM Set$[2000]

20 ! Setup the instrument as desired

30 OUTPUT 707;":SYST:HEAD OFF"

40 OUTPUT 707;":SYSTEM:SETUP?"

50 ! Transfer the instrument setup to controller

60 ENTER 707 USING "-K";Set$ !Store the setup

70 PAUSE !Change the setup as desired

80 OUTPUT 707 USING "#,K";":SYST:SETUP ";Set$

90 ! Returns the instrument to the first setup

100 END

The logical order for this instruction is to send the query rst followed by the

command at a time of your choosing. The query causes the learn string to be

sent to the controller and the command causes the learn string to be returned

to the HP 70703A.

System Subsystem

7-8

Acquire Subsystem

The ACQUIRE subsystem commands set up conditions for executing a DIGITIZE root level

command to acquire waveform data. This subsystem selects the type of data, the number of

averages, the number of data points and the completion criteria.

Refer to gure 8-1 for the ACQUIRE subsystem commands syntax diagram.

8

Note

The term \Time Buckets" is dened as - the time range divided into a specic

number of horizontal time points as dened by the :ACQUIRE:POINTS

command. Each of these increments in time have a xed time associated with

it.

(Normal)

CQUIRE:TYPE

:A

The

waveform

this

in

to

set

reects

.

mode

NORMAL.

Averaging

CQUIRE:TYPE

:A

The

desired.

resolution

is

Persistence

NORMAL

last

the

CQUIRE:COUNT

:A

The

Mode

VERA

A

The

Mode

command

point

data

GE command

waveform

used

is

in

(hit)

query

will

is used

reects a

general

for

time

each

always

when reduction

minimum of

purpose

bucket.

return

<

N

type

CQUIRE:COUNT

A

the

when

1

a

of signal

>

acquisitions

measurements

no

has

acquisition

improved

and

noise

averaged

per

.

eect

type

bucket, where<N>is the current ACQUIRE:COUNT<N>value.

COUNT can be set in AVERAGE mode by sending the :ACQUIRE:COUNT command followed

by the number of averages. In this mode the value is rounded to the nearest power of 2. It

determines the number of averages that must be acquired.

The

is

time

Acquire

Subsystem 8-1

Envelope Mode

The :ACQUIRE:TYPE ENVELOPE command is used when measuring voltage or time jitter. The

waveform reects the minimum and maximum data points (hit) in each time bucket.

A count value can be set in the envelope mode. This value determines the number of values to

be used, at each time point, when constructing the envelope.

Figure

8-1.

CQUIRE

A

Subsystem

Commands

Syntax

Diagram

COMPlete

The :ACQUIRE:COMPLETE command species the completion criteria for an acquisition.

only

the

an

needs

time

percentage of

complete

bucket

what

for

.If

that

parameter

The

acquisition

one data

considered

is

per

bit

determines

time

bucket to be considered full in the A

need

mode

instrument

the

full. In

order

for

you

time

the

in

are

bucket

time

the

to

buckets

NORMAL

considered

be

before

\full"

be

to

VERAGE or ENVELOPE modes a specied number of data

points (COUNT) must be acquired.

range for the COMPLETE command is 0 to 100 and indicates the percentage of time

The

buckets that must

be \full" before the acquisition is considered complete

. If the complete

value is set to 100%, all time buckets must contain data for the acquisition to be considered

complete.

.

place

take

will

complete

the

If

COMPLETE

The

Acquire Subsystem

8-2

value is

query

0,

to

set

returns the

one

then

completion

acquisition

criteria

cycle

for

the

currently

selected

mode

.

Command Syntax

:ACQuire:COMPlete <comp>

Where:

<comp> ::= 0 to 100 percent

Example

OUTPUT 707;":ACQUIRE:COMPLETE 85"

Query Syntax

:ACQuire:COMPlete?

Returned Format

Where:

<comp>

::= 0

to 100

(integer -

NR1 format)

Example

Cmp$[50]

DIM

OUTPUT

ENTER

707;":ACQUIRE:COMPLETE?"

707;Cmp$

PRINT Cmp$

COUNt

each

average

In

mode

CQUIRE:COUNT

:A

,

species

the

number

of

values

to

averaged

be

for

time bucket before the acquisition is considered complete for that time bucket.

When acquisition type is set to NORMAL, the count is 1.

When the acquisition type is set to AVERAGE, the count can range from 1 to 2048. Any value

can be sent, however the value will be rounded to the nearest power of 2.

and

When

acquisition

the

type

count can

ENVELOPE,

to

set

is

the

be

between

value

any

1

2048.

The COUNT query returns the currently

selected count value

.

Acquire

Subsystem 8-3

Command Syntax

:ACQuire:COUNt <count>

Where:

<count> ::= 1 to 2048

Example

OUTPUT 707;":ACQUIRE:TYPE AVERAGE;COUNT 1024"

Query Syntax

:ACQuire:COUNt?

Returned Format

Where:

<count>

::= 1

through 2048

(integer -

NR1 format)

Example

Cnt$[50]

DIM

OUTPUT

ENTER

707;":ACQ:COUNT?"

707;Cnt$

PRINT Cnt$

POINts

The

CQUIRE:POINTS

:A

command

species

the

number

of

time

buckets

for

acquisition

each

record. The legal settings are 32, 64, 128, 256, 500, 512, or 1024. Any value between 32 and

1024 can be sent to the instrument. If a value is sent that is not one of the legal values it is

rounded to the nearest power of 2. If a number smaller than 31 or greater than 1024 is sent an

error is produced.

acquired.

The

Note

POINTS

number

query

Always

returns

the

query

the

number of time buckets

VEFORM

A

W

buckets

time

of

Subsystem

acquired (:W

to be

points

value to

AVEFORM:POINTS?).

determine

the

actual

Acquire Subsystem

8-4

Command Syntax

:ACQuire:POINts <points_arg>

Where:

<points_arg>::= 32 to 1024 (see above for legal values)

Example

OUTPUT 707;":ACQ:POINTS 512"

Query Syntax

:ACQuire:POINts?

Returned Format

<points_arg><NL>

Where:

<points_arg>

::= 32

- 1024

(see above

for legal

values)

Example

Pnts$[50]

DIM

OUTPUT

ENTER

707;":ACQUIRE:POINTS?"

707;Pnts$

PRINT Pnts$

TYPE

The

CQUIRE:TYPE

:A

command

selects

the

type

acquisition

of

that

when

place

take

to

is

:DIGITIZE root level command is executed. There are three acquisition types: NORMAL,

AVERAGE, and ENVELOPE.

The :ACQUIRE:TYPE query returns the current acquisition type.

Command

:ACQuire:TYPE

Syntax

{NORMal|AVERage|ENVelope}

Example

a

OUTPUT 707;":ACQUIRE:TYPE ENVELOPE"

Acquire

Subsystem 8-5

Query Syntax

:ACQuire:TYPE?

Returned Format

Where:

<type> ::= {NORMal|AVERage|ENVelope}

Example

DIM Tpe$[50]

OUTPUT 707;":ACQUIRE:TYPE?"

ENTER 707;Tpe$

PRINT Tpe$

Acquire Subsystem

8-6

Calibrate Subsystem

The CALIBRATE subsystem contains commands to perform probe/self calibration, and set

channel-to-channel time nulls. CALIBRATION may be used instead of CALIBRATE.

9

Note

After running the SCALIBRATION command you must perform an AUTOSCALE

or *RST command to return to normal operation.

Calibrate

Subsystem 9-1

Calibrate Subsystem

9-2

Figure 9-1. CALIBRATE Subsystem Commands Syntax Diagram

Calibration Memory Protection

The Calibration Memory Protection is controlled by switches A and B situated in the bank of

switches at the top of the module.To set these switches, the mainframe must rst be powered

down, and then the HP 70703A removed from the mainframe to gain access to the switches.

Switch A determines whether the Calibration Memory Protection is controlled by the switch

settings or by programmable methods. With switch A set to the \0" position (\hard mode"), the

Calibration Memory Protection state is determined by the position of switch B. When B is set to

\0", the Calibration Memory is write-protected. When B is set to \1", the Calibration Memory

is not write-protected.

Setting switch A to \1" (\soft mode") means that the Calibration Memory Protection can be

controlled by the programmable method. The position of switch B determines the power-up

state of the Calibration Memory Protection. With switch B set to \0", the power-up state

is write-protected. When B is set to \1", the power-up state is not write-protected. The

initial power-up state can be altered using the :CALIBRATE:SECURITY:STATE command,

this is particularly useful in ATE systems when it is not practical to power down the system.

Sending :CALIBRATE:SECURITY:STATE ON will set the Calibration Memory Protection to

write-protected mode. Sending :CALIBRATE:SECURITY:STATE OFF will set the Calibration

Calibration

the

reset

Memory

It

Protection

Protection to

is recommended

write-protected

Memory

Protection

not

to

the conditions

that the

settings

mode

write-protected

determined by

Calibration Memory

1,

or

0

=

(A

,

to

set

be

will

B

write

=

mode

0).

Cycling

.

the

the positions

Protection switches

This will

ensure that

protected.

power

will

switches

of

(A/B)

at

A

are

power-up

and

set

the

.

B

the

to

Calibration

The

Manual.

procedure

for

the

HP

70703A

described

is

in

Installation

the

Verication

and

Calibrate

Subsystem 9-3

PCALibration:ATTenuation:BCALibration

The :CALIBRATE:PCALIBRATION:ATTENUATION:BCALIBRATION command performs an

attenuation calibration on the channel specied by the CAL:PCAL:ATT:CHAN<N>command.

The instrument calibrates channel gain at the point connected to the DC calibrator output (DC

CAL OUT) connector (probe, cable, and so on). Probe attenuation is then calculated from the

results, and a correction is automatically entered in the correct CHANnel<N>:PROBe setting.

Command Syntax

:CALibrate:PCALibration:ATTenuation:BCALibration

Example

OUTPUT 707;":CAL:PCAL:ATT:CHAN4"

PAUSE ! To connect probe to DC CAL OUT from Input 4 connector.

OUTPUT 707;":CAL:PCAL:ATT:BCAL"

This example calibrates the channel gain on input 4. For the example a 10:1 attenuator

probe is connected to the DC CAL OUT connector. The correction is automatically stored in

CHAN4:PROB

Note

.

Channel

to

out

250:1.

this

of

gain

If

range

corrected

is

measured

the

an error

,

using

results

will be

calculated

the

cause

generated.

attenuation

probe

calculated

values

attenuation

from

factor

0.9:1

be

to

enuation:CHANnel

PCALibration:A

The

that

:CALIBRA

will

TE:PCALIBRA

calibrated

be

TT

when

TION:A

the

TTENU

CAL:PCAL:A

TION:CHANNEL

A

TT:BCAL

command

>

N

<

is

Command Syntax

:CALibrate:PCALibration:ATTenuation:CHANnel<N>

Where:

<N> ::= 1,2,3 or 4

Example

OUTPUT 707;":CAL:PCAL:ATT:CHAN2"

The :CALIBRA

TE:PCALIBRATION:TNULL:CH1TO<N>command

of channels 2, 3 or 4 to correspond with

channel 1. Use to eliminate any time discrepancies

is used to set the timing

between channels and minimize channel to channel skew variations

any dierences in

cable length.

command

executed.

to manually adjust

. Use

selects

the

channel

Calibrate Subsystem

9-4

Command Syntax

:CALibrate:PCALibration:TNULl:CH1TO<N> <time>

Where:

<N> ::= 2, 3 or 4 <time> ::=050nS to 70nS

Example

OUTPUT 707;":CAL:PCAL:TNUL:CH1TO4 25E-9"

REPort

The :CALIBRATE:REPORT query returns the instrument's current calibration status. Each

channel's status is queried separately. The data is sent to the output buer.

Query

Syntax

:CALibrate:REPort?

Where:

Returned

::=

ormat

F

Where:

{CHANnel1

<data>

::=

Offset

Delay

A/D {P|F|D|C},

Hysteresis {P|F|D|C}, Trigger {P|F|D|C}, Delay {P|F|D|C},

TimeNull {P|F|D|C}}

Note

\P" = Passed, \F" = Failed, \D" = Defaulted, \C" = Corrupted. P,F,D or C

prexed by a \*", indicates a new ROM revision without a recalibration.

Example

{CHANnel{1|2|3|4}}

{P|F|D|C},

A/D

{P|F|D|C},

Hysteresis

Logic

Gain{P|F|D|C}, Offset

{P|F|D|C},

Gain

{P|F|D|C},

Trigger

{P|F|D|C},

Trigger {P|F|D|C}|CHANnel{2|3|4}

{P|F|D|C},

DIM Data$[18000]

OUTPUT 707;":CAL:REPort? CHANnel2"

ENTER 707;Data$

PRINT Data$

Calibrate

Subsystem 9-5

SCALibration:BCALibration

The :CALIBRATE:SCALIBRATION:BCALIBRATION command is used to begin a self-calibration

routine. The routine that is performed is dependent on the SCALIBRATION command

congured prior to executing the BCALIBRATION command.

Command Syntax

:CALibrate:SCALibration:BCALibration

Example

OUTPUT 707;":CAL:SCAL:LTC"

OUTPUT 707;":CAL:SCAL:BCAL"

In this example, the logic trigger calibration has been congured with the CAL:SCAL:LTC

command and the logic trigger calibration has been started by the CAL:SCAL:BCAL command.

Note

The Calibration Protection circuitry must be set to the NOT WRITE

PROTECTED mode prior to performing a SCALIBRATION routine.

command

BCALIBRA

the

If

SCALIBRATION

the

SUMMARY

TION

routine to

:QUESTIONABLE register

SCALibration:DCALibration

:CALIBRA

The

calibration

revision

the

currently

Service

Command

TE:SCALIBRA

Default

data.

installed.

Manual

for

Syntax

TION:DCALIBRA

calibration

command

This

procedures

data

perform

to

:CALibrate:SCALibration:DCALibration

Example

OUTPUT

707;":CAL:SCAL:DCAL"

707;":CAL:SCAL:BCAL"

set

is

should

is

performed,

be

TION

the factory

at

this

executed

cal

-

8

(bit

command

used by

be

only

calibration.

bit

not

used

will

rst

active).

to load

dependent

without

a

is

and is

service personnel.

dening

set

be

the

in

\default"

the

on

ROM

Refer

to

This example overwrites all existing calibration

Note

The Calibration Protection circuitry must be set

PROTECTED mode prior to performing a default calibration routine

Calibrate Subsystem

9-6

data with default data.

to the NOT WRITE

.

SCALibration:DELay

The :CALIBRATE:SCALIBRATION:DELAY command performs a delay calibration on all four

inputs, one at a time. Each input must be connected to the AC calibrator output (PROBE COMP

AC CAL OUT) connector prior to executing the calibration routine for that channel. The results

are stored and used by the instrument to maintain measurement accuracy.

Command Syntax

:CALibrate:SCALibration:DELay <channel>

Where:

<channel> ::= {CHANnel{1|2|3|4}}

Example

OUTPUT 707;":CAL:SCAL:DEL CHAN4"

OUTPUT 707;":CAL:SCAL:BCAL"

In this example, the instrument has been congured to perform a delay calibration on

the

channel 4

with the

CAL:SCAL:DEL command

and

the

delay

calibration

has

been

started

by

CAL:SCAL:BCAL command.

WRITE

Note

Calibration

The

PROTECTED

Protection

prior

mode

circuitry

performing

to

must

be set

calibration

a

to the

NOT

routine

.

SCALibration:DOUTput

:CALIBRA

The

calibrator

TE:SCALIBRA

output

(DC

CAL

TION:DOUTPUT

connector

OUT)

command

volts

0

to

Command Syntax

:CALibrate:SCALibration:DOUTput {ZVOLt|FVOLt}

Example

OUTPUT

Note

707;":CAL:SCAL:DOUT

The default condition after

ZVOL"

a *RST command is ZV

is used

(ZV

OLt)

to set

volts (FV

5

or

OLt (0 volts).

the

output

OLt).

level

of

the

DC

Calibrate

Subsystem 9-7

SCALibration:LTCalibrate

The :CALIBRATE:SCALIBRATION:LTCALIBRATE command performs a logic trigger calibration.

Input 1 must be connected to the AC calibrator output (PROBE COMP AC CAL OUT) connector

prior to executing the calibration routine. The results are stored and used by the instrument to

maintain measurement accuracy.

Executing :CAL:SCAL:LTC PART assumes the logic trigger oscillator is correctly adjusted, and

only recalculates the internal constants. Executing :CAL:SCAL:LTC ALL requires the logic

trigger oscillator to be adjusted.

Executing :CAL:SCAL:LTC without any argument is the same as executing the command with

the ALL parameter.

This function is a service only function. Refer to the Service Manual for more information.

Command Syntax

:CALibrate:SCALibration:LTCalibrate {ALL|PART}

Example

OUTPUT 707;":CAL:SCAL:LTC"

OUTPUT 707;":CAL:SCAL:BCAL"

calibration

the

Note

executing

to

Prior

results

must

calibration

executed.

The

PROTECTED

reviewed

be

results

Calibration

mode

the

must

prior

logic

trigger

using

indicate \P"

calibration

CAL:REP?

the

before

Protection circuitry

to performing

default

a

routine

query

the

must

,

All

.

trigger

logic

be

calibration

set

four

to

channel

calibration

NOT

the

routine

.

be

can

WRITE

SCALibration:TNULl

The :CALIBRATE:SCALIBRATION:TNULL command performs a time null calibration on one

set of channels at a time. The results are stored and used by the instrument to maintain

measurement accuracy.

Command Syntax

:CALibrate:SCALibration:TNULl

<channel

skew>

Where:

<channel skew> ::= {CH1TO2|CH1TO3|CH1TO4}

Calibrate Subsystem

9-8

Example

OUTPUT 707;":CAL:SCAL:TNUL CH1TO3"

OUTPUT 707;":CAL:SCAL:BCAL"

Note

The Calibration Protection circuitry must be set to the NOT WRITE

PROTECTED mode prior to performing a default calibration routine.

SCALibration:VERTical

The :CALIBRATE:SCALIBRATION:VERTICAL command performs a vertical calibration on all

four inputs simultaneously. All inputs must be connected to the DC calibrator output (DC CAL

OUT) connector prior to executing the calibration routine. The results are stored and used by

the instrument to maintain measurement accuracy.

Command Syntax

:CALibrate:SCALibration:VERTical

Example

OUTPUT

Note

707;":CAL:SCAL:VERT"

707;":CAL:SCAL:BCAL"

Calibration

The

PROTECTED

Protection

mode

prior

circuitry

performing

to

must

be

default

a

set

to

NOT

the

calibration

WRITE

routine

.

e

T

SECurity:ST

A

The :CALIBRATE:SECURITY:STATE is used to switch the Calibration Memory Protection mode

between write-protected and not write-protected.

The SECURITY:STATE query returns the current state of Calibration Memory Protection.

Command

Syntax

:CALibrate:SECurity:STATe {{ON|1}|{OFF|0}}

Example

OUTPUT 707;":CAL:SEC:STAT ON"

Calibrate

Subsystem 9-9

Query Syntax

:CALibrate:SECurity:STATe?

Returned Format

<sec_state>

Where:

<sec_state> ::= 0 or 1

Note

The Calibration Protection state selected will remain valid until a new selection

is made or until the power is cycled. Cycling the power will return the

Calibration Protection mode to the power up state determined by the positions

of switches A and B.

When the module is congured for \hard" write-protected mode (switch A set

to \0") sending the :CALIBRATE: SECURITY:STATE command will always result

in an error being returned. This mode cannot be changed programmatically,

regardless of the state settings (switch B position).

TNULl

(channel-to-channel

null

time

the

values

query

sends

should

tells

have

instrument

the

been

obtained

output

to

from

:CALIBRA

The

70703A.

HP

the

controller

.

Command

TE:TNULL

The

.

setup

Syntax

The

time

TNULL

command

null

:CALibrate:TNULl <null_value1>,<null_value2>,<null_value3>

Where:

the

instrument

the

time

skew)

null

values

into

during

the

to

<null_value1> ::= channel 1 to channel 2 skew

<null_value2> ::= channel 1 to channel 3 skew

<null_value3> ::= channel 1 to channel 4 skew

Example

OUTPUT

707;":CAL:TNUL

<null_value1>,<null_value2>,<null_value3>

Query Syntax

:CALibrate:TNULl?

Calibrate Subsystem

9-10

Returned Format

<null_value1>,<null_value2>,<null_value3><NL>

Where:

<null_value1> ::= channel 1 to channel 2 skew (exponential - NR3 format)

<null_value2> ::= channel 1 to channel 3 skew (exponential - NR3 format)

<null_value3> ::= channel 1 to channel 4 skew (exponential - NR3 format)

Example

DIM Nll$[50]

OUTPUT 707;":CAL:TNUL?

ENTER 707;Nll$

PRINT Nll$

Calibrate

Subsystem 9-11

10

Channel Subsystem

The CHANNEL subsystem commands are used to select a specic channel's vertical or Y-axis

control. Channels 1, 2, 3, and 4 are independently programmable for all oset, probe, coupling,

and range functions.

The CHANNEL commands can be sent with a channel number specied or not specied. If a

channel number is specied in the command, then the specied channel is aected. However,

if the channel number is not specied, then channel 1 is aected.

See VIEW and BLANK for information on channel presentation.

Channel

Subsystem 10-1

Channel Subsystem

10-2

Figure

10-1.

CHANNEL

Subsystem

Commands

Syntax

Diagram

Agilent 70703A Programmer's Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Introduction to Programming Syntax

Introduction to Programming an Instrument

Interface Functions

Programming and Documentation Conventions

Common Commands

Root Level Commands

System Subsystem

Acquire Subsystem

Calibrate Subsystem

Channel Subsystem