Remote Interface Setup
GPIB (IEEE-488) Interface 5
5-3
IEEE-488 Interface Configuration
The 5730A Calibrator IEEE-488 interface supports the IEEE-488 interface function
subsets listed in Table 5-1.
Table 5-1. Supported IEEE-488 Interface Function Subsets
Interface Function Description
SH1 Complete source handshake capability
AH1 Complete acceptor handshake capability
T6 Basic talker; serial poll; no talk-only mode; unaddress if MLA
TEO No extended talker capabilities
L4 Basic listener operation; no listen-only mode; unaddress if MTA
LEO No extended listener capabilities
SR1 Full service request capability with ability to bit-mask SRQ
RL1 Full remoter/local capability including local lockout
PPO No parallel poll capability
DC1 Device clear capability
DT0 No device trigger capability
C0 No bus control capability
Bus Communication Overview
Communication between the controller and the 5730A Calibrator takes place with
commands established by IEEE-488 standards and commands specifically related to the
Calibrator. The commands in Tables 6-4, 6-5, and 6-6 are all the remote commands, both
common and device-dependent.
Definitions of the different types of messages used on the IEEE-488 bus follow:
• Device-dependent commands are messages used to transfer information directly
between the 5730A Calibrator and the IEEE-488 controller. Some commands cause
an action to take place in the Calibrator. Others, called queries in the IEEE standards,
ask for information, and always generate a response message from the Calibrator.
While message format is governed by IEEE-488 standards, messages themselves can
be unique to the Calibrator. For example, device-dependent commands are used to set
the output mode and amplitude, and to switch from standby to operate.
• Common commands defined by IEEE standards are used for functions common to
most bus devices. Examples include the command to reset a device (*RST) and the
query for device identification (*IDN?). Common commands and queries can be
identified easily because they all begin with an asterisk (*).
• Interface messages defined by IEEE standards have their own control lines, and
others are sent over the data lines by first asserting the control line ATN (Attention).
An important thing to note about interface messages is that unlike device-dependent
and common commands, interface messages are not sent literally (For example, when
a device-dependent query is sent to the Calibrator, the controller automatically sends
the interface message MTA (My Talk Address).
To Next Page
Loading...
Need help?
General
