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

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