Anritsu MT9810A User Manual
MT9810A
Optical Test Set
Remote Control
Operation Manual
Third Edition
To ensure that the MT9810A Optical Test Set
is used safely, read the safety information in
the MS9710A Optical Test Set Manual first.
Keep this manual with the Optical Test Set.
ANRITSU CORPORATION
Document No.: M-W1483AE-3.0
MT9810A Optical Test Set Remote Control
Operation Manual
14 July 1998 (First Edition)
20 February 2003 (Third Edition)
Copyright © 1998-2003, ANRITSU CORPORATION.
All rights reserved. No part of this manual may be reproduced without the prior written permission of
the publisher.
The contents of this manual may be changed without prior notice.
Printed in Japan
ii
Trademark
Visual BASIC and Windows are registered trademarks of Microsoft
Corporation.
NI-488.2M and LabVIEW are registered trademark of National In-
struments Corporation.
iii
iv
Introduction
This manual describes the remote control of the MT9810A Optical Test Set.
This product can control the MT9810A and incorporate the measurement result
through the GPIB/RS-232C interface.
I
Table of Contents
Introduction ........................................................ I
Section 1 Overview .......................................... 1-1
1.1 Overview ............................................................................ 1-2
1.2 Selecting the Interface Port ............................................... 1-2
1.3 Channel Numbers of the Unit ............................................ 1-2
Section 2 How to Connect .............................. 2-1
2.1 Connecting Device Using a GPIB Cable .......................... 2-2
2.2 Connecting a Device Using an RS-232C Cable ............... 2-4
2.3 Default Value ..................................................................... 2-8
Section 3 Specifications ................................. 3-1
3.1 GPIB Specifications .......................................................... 3-2
3.2 RS-232C Specifications .................................................... 3-2
3.3 Device Message List ......................................................... 3-3
Section 4 Initial Setting ................................... 4-1
4.1 Initialization of Bus by IFC Statement ............................... 4-3
4.2 Initialization of Message Exchange by DCL and
SDC Bus Commands ........................................................ 4-5
4.3 Initialization of Devices by ∗RST Command ..................... 4-7
4.4 Device States at Power-ON .............................................. 4-8
Section 5 Listener Input Formats ................... 5-1
5.1 Summary of Listener Input Program Message
Syntactical Notation .......................................................... 5-3
5.2 Program Message Functional Elements ........................... 5-7
5.3 Program Data Format ....................................................... 5-16
Section 6 Talker Output Format ..................... 6-1
6.1 Differences in Syntax between Listener Input Formats and
Talker Output formats ....................................................... 6-3
6.2 Response Message Functional Elements ........................ 6-4
II
Section 7 Common Commands ..................... 7-1
7.1 Classification of Supported Commands and References .... 7-2
Section 8 Status Structure .............................. 8-1
8.1 IEEE 488.2 Standard Status Model .................................. 8-3
8.2 Status Byte Register ......................................................... 8-5
8.3 Enabling the SRQ .............................................................. 8-9
8.4 Standard Event Status Register ....................................... 8-10
8.5 Queue Model ..................................................................... 8-13
8.6 Extended Status Bytes ...................................................... 8-15
Section 9 Details on Device Messages .......... 9-1
9.1 Main Frame ....................................................................... 9-2
9.2 Optical Sensor ................................................................... 9-7
9.3 Light Source ...................................................................... 9-22
9.4 Error Messages ................................................................. 9-25
Section 10 Program Example ......................... 10-1
10.1 Precaution on Programming ............................................. 10-2
10.2 Program Examples ............................................................ 10-3
Section 11 LabVIEW Drivers ............................ 11-1
11.1 Installation ......................................................................... 11-2
11.2 Program Example.............................................................. 11-3
11.3 List of LabVIEW Drivers .................................................... 11-6
11.4 Description of LabVIEW Driver Functions ........................ 11-7
III
IV
.
Section 1 Overview
This section outlines the remote control functions of the MT9810A Optical Test Set.
1.1 Overview ............................................................................. 1-2
1.2 Selecting the Interface Port ................................................ 1-2
1.3 Channel Numbers of the Unit ............................................. 1-2
1-1
Section 1 Overview
1.1 Overview
The MT9810A Optical Test Set can perform almost all operations remotely using a computer. This product comes
standardized with a GPIB interface port (IEEE Std 488.2-1987) and an RS-232C interface port.
1.2 Selecting the Interface Port
The interface port is selected from the front panel of the MT9810A main unit. The two ports cannot be used at the same
time. Refer to the Section 2 "How to Connect" for more details.
1.3 Channel Numbers of the Unit
Up to two units can be mounted on the MT9810A. There are commands that specify the channel number to which the
unit is mounted. The left channel is Channel 1 and the right channel is Channel 2 as seen from the front.
1-2.
Channel1 Channel2
Section 2 How to Connect
This section explains how to connect GPIB and RS-232C cables between the MT9810A Optical Test Set and external
devices such as a host computer, personal computer, and printer. This section also explains how to set the interfaces of
the MT9810A.
2.1 Connecting Device Using a GPIB Cable ........................... 2-2
2.1.1 Setting the Interface for the Connection Port ...... 2-2
2.1.2 Confirming and Setting the Address .................... 2-3
2.2 Connecting a Device Using an RS-232C Cable ................ 2-4
2.2.1 RS-232C Interface Signal Connection Diagrams 2-5
2.2.2 Setting the Interface of the Connection Port ........ 2-7
2.2.3 Setting RS-232C Interface Conditions ................. 2-7
2.3 Default Value ...................................................................... 2-8
2-1
Section 2 How to Connect
(
)
2.1 Connecting Device Using a GPIB Cable
The MT9810A has a GPIB cable connector mounted on the back panel. Be sure to connect the GPIB cable before
turning on the power.
A maximum of 15 devices, including a controller, can be connected to one system. Connect these device in accordance
with the conditions shown in the following figure.
GPIB
Connector
GPIB
GPIB
Cable
Total cable length ≤20 m
Device-to-device cable length ≤4 m
Number of connectable devices <15
2.1.1 Setting the Interface for the Connection Port
Set the interface of the connection port to GPIB. The setting method is shown below.
(1) Select "Remote Interface" with the System key.
(2) Switch to "GPIB" with the Select key.
(3) Enter the setting by pressing the Enter key.
2-2
Shift+Prmtr
(2) Select(1) System
(3) Enter
(
)
2.1 Connecting Device Using a GPIB Cable
2.1.2 Confirming and Setting the Address
Be sure to set the GPIB address of the MT9810A after turning on the power. Set the address using the front panel with
the MT9810A set to the local mode.
(1) Select "GPIB ADDRESS" with the System key.
(2) Specify the address with the ↑ and ↓ keys. (The input address range is from 0 to 30.)
(3) Enter the setting by pressing the Enter key.
(1) System
Shift+Prmtr
(3) Enter(2) ↓(2) ↑
2-3
Section 2 How to Connect
2.2 Connecting a Device Using an RS-232C Cable
The MT9810A has an RS-232C connector mounted on the back panel.
NOTE:
RS-232C connectors are available in 9-pin and 25-pin types. The 9-pin type is usually used for DOS/V per-
sonal computers, while the 25-pin type is usually used for the NEC PC9801/PC9821 Series. Before purchas-
ing an RS-232C cable, check the type of the RS-232C connector on the external device. The following two
types of RS-232C cables are available as application parts for this product.
• RS-232C cable (for 25-pin type personal computer)
(Personal computer side)(MT9810A side)
D-sub,
9-pin,
Female
• RS-232C cable (for DOS/V personal computer)
D-sub,
9-pin,
Female
Length = 1 m
Length = 1 m
D-sub,
25-pin,
Male
(Personal computer side)(MT9810A side)
D-sub,
9-pin,
Female
2-4
2.2 Connecting a Device Using an RS-232C Cable
2.2.1 RS-232C Interface Signal Connection Diagrams
The following diagram shows the connection of RS-232C interface signals between the MT9810A and a personal
computer.
Personal computerMT9810A
GND
CD (NC) 1
RD 2
TD 3
DTR (NC) 4
GND 5
DSR (NC) 6
RTS 7
CTS 8
RI (NC) 9
D-sub, 9-pin, female
D-sub, 25-pin, male
GND
1 GND
2SD
3RD
4RS
5CS
6DR
7 GND
8CD
9NC
10 NC
11 GND
12 NC
13 GND
14 GND
15 ST2
16 NC
17 RT
18 NC
19 NC
20 ER
21 NC
22 NC
23 NC
24 ST1
25 NC
Connection to the external computer with a D-sub 25-pin interface
2-5
Section 2 How to Connect
Personal computerMT9810A
GND
CD (NC) 1
RD 2
TD 3
DTR (NC) 4
GND 5
DSR (NC) 6
RTS 7
CTS 8
RI (NC) 9
D-sub, 9-pin, female D-sub, 9-pin, female
Connection to the DOS/V personal computer
GND
(1CD
(2RD
(3TD
( 4 DTR
( 5 GND
( 6 DSR
(7RTS
( 8 CTS
(9RI
2-6
(
)
Item System key Setting value
Baud rate
Stop bit
Parity bit
Character length
RS-232C Baudrate
RS-232C StopBit
RS-232C ParityBit
RS-232C Character
1200/2400/4800/9600/14400/19200 bps
1/2 bit
ODD/EVEN/NONE
7/8 bit
2.2 Connecting a Device Using an RS-232C Cable
2.2.2 Setting the Interface of the Connection Port
Set the interface of the connection port to RS-232C. The setting method is shown below.
(1) Select "Remote Interface" with the System key.
(2) Switch the interface to "RS-232C" with the Select key.
(3) Enter the setting by pressing the Enter key.
(2) Select(1) System
Shift+Prmtr
(3) Enter
2.2.3 Setting RS-232C Interface Conditions
Set the interface conditions for the RS-232C port of MT9810A to match the interface conditions of the connected
external device. The setting method is shown below.
(1) Select the setting items with the System key.
(2) Specify the setting values with the Select key.
(3) Enter the setting by pressing the Enter key.
The setting items are shown in the Table 2-1.
Table 2-1
2-7
Section 2 How to Connect
2.3 Default Value
The factory-set values are shown in the Table 2-2.
Setting item Default value
Remote interface
GPIB address
RS-232C baud rate
RS-232C stop bit
RS-232C parity bit
RS-232C character length
Table 2-2
GPIB
15
9600 bps
1 bit
Even
8 bits
2-8.
Section 3 Specifications
This section explains the GPIB standard, RS-232C standard, and device message list of the MT9810A Optical Test Set.
3.1 GPIB Specifications ............................................................ 3-2
3.2 RS-232C Specifications ..................................................... 3-2
3.3 Device Message List .......................................................... 3-3
3.3.1 IEEE 488.2 common commands and the commands
supported by the MT9810A .................................. 3-5
3.3.2 Device Message List ............................................ 3-6
3-1
Section 3 Specifications
3.1 GPIB Specifications
The GPIB Specifications of the MT9810A is summarized in the Table 3-1.
Table 3-1
Item Specifications value and description
Function
Interface functions
Conforms to IEEE 488.2.
MT9810A can be controlled from an external controller.
SH1: All of source handshake functions are supported.
Data send timing is controlled.
AH1: All of acceptor handshake functions are supported.
Data receive timing is controlled.
T6: Basic talker functions are supported. A serial port function is supported.
A talk-only function is not supported. The function of releasing the talker
with MLA is supported.
L4: Basic listener functions are supported. A listen-only function is not sup-
ported. The function of releasing the listener by MTA is supported.
SR1: All of service request/status byte functions are supported.
RL1: All of remote/local functions are supported.
A local lockout function is supported.
PP0: A parallel poll function is not supported.
DC1: All of device clear functions are supported.
DT0: A disk trigger function is not supported.
C0: A controller function is not supported.
A controller function is performed during external plot output.
3.2 RS-232C Specifications
The RS-232C Specifications of the MT9810A is summarized in the Table 3-2.
Table 3-2
Item Specifications
Function
Communication method
Communication control method
Baud rate
Data bits
Parity
Start bits
Stop bits
Connector
Control from external controller
Asynchronous (start-stop), half-duplex
No flow control
1200, 2400, 4800, 9600, 14400, 19200 bps
7 bits, 8 bits
Odd parity (ODD), even parity (EVEN), non-parity (NON)
1 bit
1 bit, 2 bits
D-sub 9-pin connector, male
3-2
3.3 Device Message List
3.3 Device Message List
Device messages are data messages which are transferred between a controller and the devices. These messages are
classified into program messages and response messages.
Program messages are ASCII messages transferred from a controller to the devices. Program messages are further
classified into program commands and program queries. These two types of commands are explained later in this
manual.
Program commands include device-dependent commands which are exclusively used for controlling the MT9810A
and IEEE 488.2 common commands. IEEE 488.2 common commands are program commands which are commonly
applicable to other IEEE 488.2-ready measuring instruments (including the MT9810A) on the GPIB interface bus.
Program queries are commands used to get response messages from devices. Program queries must be transferred
from a controller to a device in advance so that the controller can receive response messages from the device later.
Response messages are ASCII data messages which are transferred from a device to a controller. Among response
messages, status messages, and response messages corresponding to program queries are listed later in this manual.
• Program commands Section 5
• Program queries Section 5
• IEEE488.2 common commands Section 7
Controller
Program message
Responce message
• Status message Section 8
• Responce message Section 6
In program and response messages, numeric data may end with a suffix (unit).
Device
3-3
Section 3 Specifications
The above messages are transferred through the device input/output buffer. The output buffer is also called an output
queue. A brief description of the output buffer is given below.
Input buffer
Input buffer is an FIFO (first in first out) type memory area, that stores DABs (program and query messages) tempo-
rarily before analysis of syntax and execution.
The input buffer size of the MT9810A is 256 bytes.
Output queue
Output queue is an FIFO-type queue memory area, that stores all DABs (response messages) output from a device to a
controller until those messages are read by the controller.
The output queue size of the MT9810A is 256 bytes.
3-4
3.3 Device Message List
3.3.1 IEEE 488.2 common commands and the commands supported by the MT9810A
The 39 common commands specified by IEEE 488.2 standard is shown in the Table 3-3. Among these commands, the
commands supported by the MT9810A are marked with the check marks (√).
Table 3-3
Mnemonic Fully spelled out command name
∗ADD
∗CAL
∗CLS
∗DDT
∗DDT?
∗DLF
∗DMC
∗EMC
∗EMC?
∗ESE
∗ESE?
∗ESR?
∗GMC?
∗IDN?
∗IST?
∗LMC?
∗LRN?
∗OPC
∗OPC?
∗OPT?
∗PCB
∗PMC
∗PRE
∗PRE?
∗PSC
∗PSC?
∗PUD
∗PUD?
∗RCL
∗RDT
∗RDT?
∗RST
∗SAV
∗SRE
∗SRE?
∗STB?
∗TRG
∗TST?
∗WA I
Accept Address Command
Calibration Query
Clear Status Command
Define Device Trigger Command
Define Device Trigger Query
Disable Listener Function Command
Define Macro Command
Enable Macro Command
Enable Macro Query
Standard Event Status Enable Command
Standard Event Status Enable Query
Standard Event Status Register Query
Get Macro contents Query
Identification Query
Individual Status Query
Learn Macro Query
Learn Device Setup Query
Operation Complete Command
Operation Complete Query
Option Identification Query
Pass Control Back Command
Purge Macro Command
Parallel Poll Register Enable Command
Parallel Poll Register Enable Query
Power On Status Clear Command
Power On Status Clear Query
Protected User Data Command
Protected User Data Query
Recall Command
Resource Description Transfer Command
Resource Description Transfer Query
Reset Command
Save Command
Service Request Enable Command
Service Request Enable Query
Read Status Byte Query
Trigger Command
Self Test Query
Wait to Continue Command
Standardized by IEEE 488.2
Optional
Optional
Required
Optional
Optional
Optional
Optional
Optional
Optional
Required
Required
Required
Optional
Required
Optional
Optional
Optional
Required
Required
Optional
Other than C0: Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required
Optional
Required
Required
Required
DT1: Required
Required
Required
Supported by MT9810A
√
√
√
√
√
√
√
√
√
√
√
√
√
√
NOTE:
IEEE 488.2 commands always begin with an asterick (∗). Refer to the Section 7 "Common Commands" for more details.
3-5
Section 3 Specifications
3.3.2 Device Message List
The device message list unique to the MT9810A is shown in the Table 3-4, 3-5 and 3-6. There are two types of
commands: HP commands and SCPI-compliant Anritsu original commands. The types of commands are also shown in
the table.
Table 3-4 Main frame
Function Command HP
Brightness
Display ON/OFF
Calendar
Time
Buzzer
Header
Inserted unit
Error
DISPlay:BRIGhtness
DISPlay[:STATe]
SYSTem:DATE
SYSTem:TIME
SYSTem:BEEPer:STATe
SYSTem:COMMunicate:GPIB:HEAD
SYSTem:COMMunicate:SERial:HEAD
SYSTem:CHANnel:STATe
SYSTem:ERRor
SCPI Reference
√
√
√
√
√
√
√
√
√
Section 9.1.1
Section 9.1.2
Section 9.1.7
Section 9.1.9
Section 9.1.3
Section 9.1.5
Section 9.1.6
Section 9.1.4
Section 9.1.8
3-6
Table 3-5 Optical sensor
3.3 Device Message List
Function Command HP
Zero-set
Calibration factor
Auto range
Manual range
Reference value
Displays the reference value
Reference measurement
Reference selection
Unit
Wavelength
Unit of wavelength
Measurement data
The number of averaging
Auto bandwidth
Bandwidth
Modulation frequency
Measurement interval
The number of measurement
Logging
Statistical measurement
Measurement stop
Logging data
Logging data information
Maximum value
Minimum value
Difference between maximum
and minimum values
Measurement conditions
High-speed transfer mode start
High-speed transfer mode stop
SENSe[1|2]:CORRection:COLLect:ZERO
SENSe[1|2]:CORRection[:LOSS:[:INPut[:MAG
Nitude]]]
SENSe[1|2]:POWer:RANGe:AUTO
SENSe[1|2]:POWer:RANGe:[UPPer]
SENSe[1|2]:POWer:REFerence
SENSe[1|2]:POWer:REFerence:DISPlay
SENSe[1|2]:POWer:REFernce:STATe
SENSe[1|2]:POWer:REFernce:STATe:RATio
SENSe[1|2]:POWer:UNIT
SENSe[1|2]:POWer:WAVelength
SENSe[1|2]:POWer:WAVelength:UNI
FETCh[1|2][:SCALar]:POWer[:DC]
SENSe[1|2]:AVERage:COUNt
SENSe[1|2]:BANDwidth:AUTO
SENSe[1|2]:BANDwidth
SENSe[1|2]:FILTer:BPASs:FREQuency
SENSe[1|2]:POWer:INTerval
SENSe[1|2]:TRIGger:COUNt
SENSe[1|2]:INITiate[:IMMediate]
SENSe[1|2]:TRIGger[:SEQuence][:IMMediate]
ABORt[1|2]
SENSe[1|2]:MEMory:DATa
SENSe[1|2]:MEMory:DATa:INFO
SENSe[1|2]:FETCh[:SCALar]:POWer[:DC]:MAXimum
SENSe[1|2]:FETCh[:SCALar]:POWer[:DC]:MINimum
SENSe[1|2]:FETCh[:SCALar]:POWer[:DC]:PTPeak
SENSe[1|2]:MEMory:COPY[:NAME]
READ[1|2]
READ[1|2]:ABORt
SCPI
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
Reference
Section 9.2.6
Section 9.2.7
Section 9.2.17
Section 9.2.18
Section 9.2.19
Section 9.2.20
Section 9.2.21
Section 9.2.22
Section 9.2.23
Section 9.2.24
Section 9.2.25
Section 9.2.2
Section 9.2.3
Section 9.2.5
Section 9.2.4
Section 9.2.11
Section 9.2.16
Section 9.2.26
Section 9.2.12
Section 9.2.27
Section 9.2.1
Section 9.2.14
Section 9.2.15
Section 9.2.8
Section 9.2.9
Section 9.2.10
Section 9.2.13
Section 9.2.28
Section 9.2.29
3-7
Section 3 Specifications
Table 3-6 Light source
Function Command HP
Modulation frequency
Attenuation
Optical output
Wavelength
Unit of wavelength
Measurement condition
In the portion described as [1|2], enter the channel number into which the target unit is inserted (1 or 2). The brackets
([ ]) are not required.
When you send the LIGHT SOURCE COMMAND to OPTICAL SENSOR, the command error occurs.
At the opposite case (send the OPTICAL SENSOR COMMAND to LIGHT SOURCE), the command error occures
too.
SOURce[1|2]:AM[:INTerval]:FREQuency
SOURce[1|2]:POWer:ATTenuation
SOURce[1|2]:POWer:STATe
SOURce[1|2]:POWer:WAVelength
SOURce[1|2]:POWer:WAVelength:UNIT
SOURce[1|2]:MEMory[1|2]:COPY[:NAME]
SCPI
√
√
√
√
√
√
Reference
Section9.3.1
Section9.3.3
Section9.3.4
Section9.3.5
Section9.3.6
Section9.3.2
3-8.
Section 4 Initial Setting
Initialization of the GPIB interface system is devided into three levels. At level 1, "bus initialization" is performed to
place the system bus in the idle state. At level 2, "message exchange initialization" is performed to enable devices to
receive program messages. At level 3, "device initialization" is performed to initialize device-dependent functions.
At these three initialization levels, preparations are made for starting devices.
4.1 Initialization of Bus by IFC Statement ................................ 4-3
4.2 Initialization of Message Exchange by DCL and SDC Bus
Commands ......................................................................... 4-5
4.3 Initialization of Devices by ∗RST Command ...................... 4-7
4.4 Device States at Power-ON ............................................... 4-8
4.4.1 Items not changes at Power-ON .......................... 4-9
4.4.2 Items related to PSC flag ..................................... 4-9
4.4.3 Items that change at Power-ON ........................... 4-9
4-1
Section 4 Initial Setting
IEEE 488.2 specifies the initialization of the GPIB system as described in the Table 4-1.
Table 4-1
Level
1
2
3
When controlled from a controller via the RS-232C interface port, the MT9810A can use the "device initialization"
function (level 3). However, it cannot use "bus initialization" (level 1) and "message exchange initialization" (level 2)
functions.
When controlled from a controller via a GPIB interface bus, the MT9810A can use all the above initialization functions
(levels 1 to 3).
Initialization type
Bus initialization
Message exchange
initialization
Device initialization
Overview
Interface functions of all devices connect-
ed to the bus are initialized by an IFC
message from a controller.
Message exchange is initialized and the
function of reporting completion of opera-
tion to the controller is disabled. This ini-
tialization can be ferformed either for all
devices on the GPIB using GPIB bus com-
mand DCL, or only for the specified
devices using a GPIB bus command SDC.
Only the specified devices on the GPIB
are initialized to the known states with an
∗RST command irrespective of the past
use state.
Combination and priority of levels
This level may be combined with
other levels. However, initializa-
tion at level 1 must be performed
before initialization at other lev-
els.
This level may be combined
withother levels. However, ini-
tialization at level 2 must be per-
formed before initialization at
level 3.
This level may be combined with
other levels. However, initializa-
tion at level 3 must be performed
after initialization at levels 1 and 3.
4-2
4.1 Initialization of Bus by IFC Statement
Initialization by IFC
√
√
√
√
∆
√
Function
Source handshake
Acceptor handshake
Talker or extended talker
Listener or extended listener
Service request
Remote/local
Parallel/poll
Device clear
Device trigger
Controller
No
1
2
3
4
5
6
7
8
9
10
Symbol
SH
AH
T or TE
L or LT
SR
RL
PP
DC
DT
C
(1) Format
IFC ∆ select-code
(2) Explanation
This function can be used when the MT9810A is controlled from a controller via a GPIB interface bus.
On the GPIB corresponding to the specified select code, the IFC line is activated for about 100 µs (as electrically
set at the low level). When IFC is executed, interface functions of all devices connected to the GPIB bus line
corresponding to the specified select code are initialized. Only the system controller can send this command.
"Initialization of interface functions" refers to the processing in which controller-set device interface functions
(talker, listener, etc.) are reset to their initial states. Functions marked with the check marks (√) in the following
table are initialized. The function marked with a triangle (∆) is initialized partially.
Table 4-2
IFC
If the IFC statement is True (the IFC line is set at the low level through execution of the IFC statement), initialization
is not performed at levels 2 and 3. Therefore, device operating states are not affected.
4-3
Section 4 Initial Setting
The examples of device states set by the IFC statement are shown in the Table 4-3.
Table 4-3
Item Device state
Talker/listener
Controller
Return of control right
Devices issuing service
request
Devices in remote state
All talkers and listeners are set in the idle state (TIDS, LIDS) within 100 µs.
If the controller is not active (SACS: System control ACtive State), it enters the
idle state, or CIDS, (Controller IDle State) within 100 µs.
If the system controller (the first device on the GPIB which is used as a controller)
has granted the control right to another device when IFC is executed, the control
right is returned to the system controller. Generally, pressing the RESET key on
the system controller allows an IFC message to be output from the system con-
troller.
The state in which an SRQ message is issued by a device (the SRQ line is set at
the LOW level by the device) is not canceled, but the state in which all devices on
the system bus are placed in the serial poll mode by the controller is canceled.
For the devices currently in the remote state, the remote state is not canceled by
the IFC message.
4-4
Loading...