Remote Operation
Using the IEEE-488 Interface for Remote Control 5
5-3
IEEE-488 Interface Configuration
The Product 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; unaddressed 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
DT1 Device trigger capability
C0 No bus control capability
Bus Communication Overview
Communication between the controller and the Product takes place with
commands established by IEEE-488 standards and commands specifically
related to the Product. The commands in Table 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:
• Device-dependent commands are messages that transfer information directly
between the Product and the IEEE-488 controller. Some commands cause
an action to take place in the Product. Others, called queries in the IEEE
standards, ask for information, and always generate a response message
from the Product. While message format is governed by IEEE-488 standards,
messages themselves can be unique to the Product. For example, use
device-dependent commands to set the input binding post or calibration type.
• 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 (*).
To Next Page
Loading...
