GPIB
370B User Manual
4-13
Controlling the 370B over the bus
As explained in the following discussion, a controller can:
Send commands to the 370B
Send queries and receive responses
Control 370B settings
Store and transfer 370B data
Move waveform data from the 370B
Load waveform data to the 370B
Transfer cursor and readout data to and from the 370B
Most GPIB system controllers and their languages provide high level statements
for sending device-dependent messages, such as commands, to any system
instrument, including the 370B.
These high-level statements usually consist of three parts :
A key word (PRINT, OUTPUT, WRITE, etc) which causes the action
(sending the message over the bus) to occur.
An address or logical unit number which directs the message to a specific
instrument.
The device-dependent message which is the actual command, query, or data
to be recognized by the instrument. (Most controllers delimit the device-
dependent message with double quotes.)
The following examples show command strings for two controllers and a
representative language for each. The first is an IBM PC with a Tektronix GURU
card (or National Instruments model PC2 or PC2A card) running BASICA. The
second is a Hewlett Packard 200 or 300 Series Scientific Computer running
Series 200 or 300 BASIC.
In these examples, the 370B device-dependent command WINdow (abbreviated
as WIN) is used to set the window cursor to midscreen. In the second and third
examples, the GPIB address of the 370B is assumed to be “8”.
IBM PC: (The address is assigned elsewhere in the code.)
200 WRT$=”WIN 250,250,750,750”
’Create Command string.
230 CALL IBWRT (DSO%, WRT$) ’Send Command.
Hewlett Packard 2001300 Series:
200 OUTPUT 708; ”WIN 250,250,750,750”, END
Sending Commands to the
370B
To Next Page
Loading...