INSTRUCTION MANUAL
For 8835(-01), 8826, 8841, 8842
MEMORY HiCORDER
INTERFACE
9557 RS-232C CARD
9558 GP-IB CARD
Contents
Introduction i
Safety Notes i
Chapter Summary ii
Chapter 1 GP-IB and RS-232C Interfaces 1
1.1 GP-IB Interface 1
1.1.1 Outline 1
1.1.2 Specification
1.2 RS-232C Interface 4
1.2.1 Outline 4
1.2.2 Specification
Chapter 2 Method of Operation 7
2.1 Basic Operational Procedure 7
2.2 Cable Connection
2.3 Setup Procedure 11
2.3.1 GP-IB Setup Procedure 11
2.3.2 RS-232C Setup Procedure
2.4 Receive and Send Protocols 15
2.5 The Status Byte and the Event Registers 19
2.6 The Input Buffer and the Output Queue
2.7 Others
2.7.1 GP-IB 24
13
23
24
2
4
8
2.7.2 RS-232C
25
Chapter 3 Commands 27
3.1 Command Summary 27
3.1.1 Standard Commands Specified by IEEE 488.2 27
3.1.2 Specific Commands
3.2 Detailed Explanation of the Commands 57
3.2.1 Explanation 57
3.2.2 Standard Commands Stipulated by IEEE 488.2
3.2.3 Specific Commands
28
59
65
Chapter 4 Example Programs 169
4.1 Visual Basic Example Programs 169
4.1.1 GP-IB Example Programs 169
4.1.2 RS-232C Example Programs
179
Appendix Appendix I
Appendix 1 IEEE 488.2-1987 Appendix I
Appendix 2 Troubleshooting the GP-IB Faults Appendix IV
Appendix 3 Troubleshooting the RS-232C Faults Appendix V
────────────────────────────────────────────────────
R
R
N
I
S
ntroduction
Thank you for purchasing the HIOKI "9557 RS-232C CARD / 9558 GP-IB
CARD" . To obtain maximum performance from the product, please read this
manual first, and keep it handy for future reference.
When using the HIOKI MEMORY HiCORDER can be used with the HIOKI
"9557 RS-232C CARD / 9558 GP-IB CARD" except following products, reffer to
the communication comands manual (Flopply disk) supplied with the
MEMORY HiCORDER.
■ The products consultable this manual:
8826, 8835, 8835-01, 8841, 8842
afety Notes
i
This manual contains information and warnings essential for safe operation of
the product and for maintaining it in safe operating condition. Before using
the product, be sure to carefully read the following safety notes.
DANGE
This product is designed to conform to IEC 61010 Safety Standards, and
has been thoroughly tested for safety prior to shipment. However,
mishandling during use could result in injury or death, as well as damage
to the product. Be certain that you understand the instructions and
precautions in the manual before use. We disclaim any responsibility for
accidents or injuries not resulting directly from product defects.
Safety symbol
The following symbols in this manual indicate the relative importance of
cautions and warnings.
In the manual, the symbol indicates particularly important
information that the user should read before using the product.
DANGE
CAUTIO
NOTE
────────────────────────────────────────────────────
Indicates that incorrect operation presents an extreme hazard that
could result in serious injury or death to the user.
Indicates that incorrect operation presents a possibility of injury to
the user or damage to the product.
Indicates advisory items related to performance or correct operation
of the product.
ii
C
────────────────────────────────────────────────────
hapter Summary
Chapter 1 GP-IB and RS-232C interfaces
Contains the functions and specifications of both the interfaces.
Chapter 2 Method of operation
Describes the operation procedures of both the interfaces.
Chapter 3 Commands
Describes the details of all the commands th at can be used.
Chapter 4 Example programs
Describes the program to operate GP-IB interface.
Appendix
Contains the information related to the IEEE488.2-1987 standard.
────────────────────────────────────────────────────
1
1
1
C
s
1
────────────────────────────────────────────────────
Chapter
1
2
.1 GP-IB Interface
.1.1 Outline
The GP-IB (General Purpose Interface Bus) was developed as an interface for
general use by programmable instrumentation, and as an interface is rich in
expandability and has many distinctive features.
There are various interfaces with specific names apart from the GP-IB, such
as the IEEE-488 bus, the IEC bus, and the HP-IB which is an internal
standard within the Hewlett-Packard Company. These are basically the same
standard, but, because the number of connector pins and the arrangement of
the signals and so on differ, much care should be exercised.
GP-IB and RS-232
Interface
3
4
5
6
7
8
9
10
In this explanation of management and operation, only the GP-IB related
resources of the 8835 and 8826 will be described.
If more detailed knowledge of the GP-IB interface is required, reference should
be made to the following literature:
The Institute of Electrical and Electronics Engineers, Inc.: "IEEE Standard
Digital Interface for Programmable Instrumentation", IEEE Std 488.1-1987,
IEEE Std 488.2-1987 (1987)
────────────────────────────────────────────────────
1.1 GP-IB Interface
11
12
13
14
A
2
1
r
l
────────────────────────────────────────────────────
.1.2 Specification
Standards
IEEE Standard 488.1-1987
IEEE Standard 488.2-1987
Interface Functions
Function Implementation
SH1 SH (Source Handshake) - All Functions
AH1 AH (Acceptor Handshake) - All Functions
T5 Basic Talk Function, Serial Poll Function, Talk Only Function
MLA (My Listen Address) Talk Release Function
L4 Basic Listener Function
MTA (My Talk Address) Listen Release Function
SR1 SR (Service Request) - All Functions
GP-IB Signal Lines
Bus Signal Lines Remarks
DIO 1 (Data Input Output 1)
DIO 2 (Data Input Output 2)
DIO 3 (Data Input Output 3)
Data
bus
DIO 4 (Data Input Output 4)
DIO 5 (Data Input Output 5)
DIO 6 (Data Input Output 6)
DIO 7 (Data Input Output 7)
DIO 8 (Data Input Output 8)
DAV (Data Valid)
Transfe
bus
NRFD (Not Ready For Data)
NDAC (Not Data Accepted) Input completed signal.
RL1 RL (Remote/Local) - All Functions
PP0 PP (Parallel Poll) - No Function
DC1 DC (Device Clear) - All Functions
DT0 DT (Device Trigger) - No Function
C0 C (Control) - No Function
Apart from input and output of data, these are used
for input and output of interface messages and
device messages.
Signal which indicates data bus
information validity.
Input preparation completed
signal.
These perform
acceptor and
source
handshake.
Signal which indicates that the information on the
ATN (Attention)
data bus is an interface message or a device
message.
Contro
bus
────────────────────────────────────────────────────
1.1 GP-IB Interface
IFC (Interface Clear)
SRQ (Service Request) Signal which requests a non-synchronous service.
REN (Remote Enable)
EOI (End or Identify) Indicates the last byte of data.
Signal which sets the interface bus system to the
initial condition.
Signal which performs changeover of remote and
local control.
3
────────────────────────────────────────────────────
Connector Pin Assignment
RC40-24RR (made by HIROSE) or compatible.
Fig. 1.1 Pin arrangement diagram for the GP-IB interface connector
Pin
number
1 DIO1 13 DIO5
2 DIO2 14 DIO6
3 DIO3 15 DIO7
4 DIO4 16 DIO8
5 EOI 17 REN
Name of signal line
Pin
number
Name of signal line
1
2
3
4
5
6
7
6 DAV 18 GND
7 NRFD 19 GND
8 NDAC 20 GND
9 IFC 21 GND
10 SRQ 22 GND
11 ATN 23 GND
12 SHIELD 24 LOGIC GND
8
9
10
11
12
13
────────────────────────────────────────────────────
1.1 GP-IB Interface
14
A
4
1
1
1
────────────────────────────────────────────────────
.2 RS-232C Interface
.2.1 Outline
RS-232C is a serial interface standard defined by the EIA (Electronic
Industries Association). It specifies the interface parameters for
communication between a DTE (Data Terminal Equipment) and DCE (Data
Communications Equipment).
The MEMORY HiCORDER incorporates a partial implementation of the RS232C specification (only certain signal lines) to allow data exchange and
remote control using a personal computer.
.2.2 Specification
Standard
EIA RS-232C
General Specifications
Communication mode Full-duplex
Synchronization Start-stop synchronization
Transfer rate 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
(bits/s), (set from the setting screen of the unit)
Start bit 1bit
Stop bits 1 or 2 bits
(set from the setting screen of the unit)
Data length 7 or 8 bits
Parity None, even, or odd
(set from the setting screen of the unit)
Delimiter LF, CR+LF
Flow control Xon/Xoff, hardware, none
────────────────────────────────────────────────────
1.2 RS-232C Interface
5
I
s
s
l
I
s
s
I
s
s
l
I
s
s
────────────────────────────────────────────────────
Connector Pin Assignment
The connector on the PC card is a D-sub 9-pin connector (male).
Make connection to the computer using a null-modem cable with the type of
connector that matches the computer.
OFF/Xon-Xoff flow contro
9 pin
9 pin
9 pin
25 pin
1
2
3
4
5
6
CD
1
RD
2
SD
3
ER
4
SG
5
DR
6
RS
7
CS
8
C
9
Hard flow contro
9 pin
CD
1
RD
2
SD
3
ER
4
SG
5
DR
6
RS
7
CS
8
C
9
1
2
3
4
5
6
7
8
9
9 pin
1
2
3
4
5
6
7
8
9
CD
RD
SD
ER
SG
DR
RS
CS
CD
RD
SD
ER
SG
DR
RS
CS
C
C
1
2
3
4
5
6
7
8
9
9 pin
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
2
0
2
2
25 pin
1
2
3
4
5
6
7
8
2
0
2
2
FG
SD
RD
RS
CS
DR
SG
CD
ER
CI
FG
SD
RD
RS
CS
DR
SG
CD
ER
CI
7
8
9
10
11
12
13
14
A
────────────────────────────────────────────────────
1.2 RS-232C Interface
6
t
l
t
l
────────────────────────────────────────────────────
25 pins
Pin number
1 Protective ground 101 AA - FG
2 Transmitted data 103 BA SD TxD
3 Received data 104 BB RD RxD
4 Request to send 105 CA RS RTS
5 Clear to send 106 CB CS CTS
7 Signal ground 102 AB SG GND
Circuit designation
CCITT circui
number
EIA symbolJIS symbolCommon symbo
9 pins
Pin number
2 Received data 104 BB RD RxD
3 Transmitted data 103 BA SD TxD
5 Signal ground 102 AB SG GND
7 Request to send 105 CA RS RTS
8 Clear to send 106 CB CS CTS
Circuit designation
CCITT circui
number
EIA symbolJIS symbolCommon symbo
────────────────────────────────────────────────────
1.2 RS-232C Interface
7
1
11121
1
N
.
)
"
,
2
n
2
────────────────────────────────────────────────────
Chapter
1
2
Method of Operatio
.1 Basic Operational Procedure
CAUTIO
The GP-IB or RS-232C interface is not isolated from the unit system.
Exercise caution, because the ground of the logic inputs and the GP-IB
or RS-232C interface ground are connected.
Connect GP-IB or RS-232C cable
3
4
5
6
7
8
Check that the power is ON for all
devices connected to the bus. (GP-IB
Check that the power is ON for the
unit. (RS-232C)
Set "INTERFACE.
Send orders to the controller
and perform remote control.
GP-IB set up
RS-232C set up
GP-IB mode
Address
Header
Transfer rate
Data length
Parity
Stop bits
Delimiter
Header
Flow control
9
0
3
4
A
────────────────────────────────────────────────────
2.1 Basic Operational Procedure
8
N
Fig. 2.1 Passing protector through connection cable
e
s
d
e
k
g
r
Fig. 2.2 Connection cable and PC card connection
2
────────────────────────────────────────────────────
.2 Cable Connection
CAUTIO
When making the connection, the cable connector and PC card should be
properly aligned, so that the connector can be pushed in straight. Do not exert
strong force on the PC card connector, to prevent the possibility of damage
and contact problems.
This section explains procedures for connecting the cable using the 8835 as an
example. For other models, refer to the instruction manual included with the
unit.
(1) Cable and PC card connection
1. Pass the PC card protector through the connection cable, as shown below.
2. Plug the PC card end of the connection cable into the PC card. The top side
of the cable connector (marked with a ▲) should match the top side of the
PC card, as shown below.
PCMCIA socket sid
Loc
Locking sprin
PC car
Ｐrotecto
Connection cabl
Front marking
────────────────────────────────────────────────────
2.2 Cable Connection
9
1
11121
1
N
Fig. 2.3 PC card insertion
Fig. 2.4 Attaching the protector
────────────────────────────────────────────────────
CAUTIO
(2) Inserting the PC card
The following actions may result in damage to the PC card or connector and
must be avoided.
・Inserting the card with the wrong orientation or in other ways than described
above.
・Inserting the card while attached to the connection cable.
・Moving the unit while the connection cable is connected to the card.
・Pulling the card out by the cable or exerting excessive force on the
connector.
・Placing objects on the connection cable connector.
1. Insert the PC card in the PC card slot on the unit. Verify that the ▲ mark
on the card points in the correct direction as shown below, and make sure
that the card is properly seated in the slot.
The PC card is keyed to prevent wrong insertion, but exerting excessive
force may damage the card or the slot.
1
2
3
4
5
6
2. Attach the PC card protector to the unit as shown below.
7
8
9
0
3
────────────────────────────────────────────────────
2.2 Cable Connection
4
A
10
Fig. 2.5 Removing the protector
Fig. 2.6 Removing the PC card
────────────────────────────────────────────────────
(3) Removing the PC card
1. Remove the PC card protector as shown below.
2. To remove the PC card, press the eject button as shown below.
NOTE
────────────────────────────────────────────────────
2.2 Cable Connection
Do not press the eject button before removing the PC card protector.
11
1
11121
1
2
)
2
────────────────────────────────────────────────────
.3 Setup Procedure
1
.3.1 GP-IB Setup Procedure
・On the unit, set the GP-IB address for the unit, and select whether or not to
use headers mode, and delimiter in messages output by the unit.
・Use the interface setting screen, accessed from the "system" screen.
・This section explains procedures for setting the GP-IB using the 8835 as an
example. For other models, refer to the instruction manual included with the
unit.
Method
System screen (INTERFACE
2
3
4
5
1. Press the SYSTEM key to call up the interface setting
screen.
6
7
8
2. Set the GP-IB operation mode for this unit.
Set the GP-IB address for this unit on the bus.
[ADDRESSABLE, TALK ONLY, DISABLE]
Move the flashing cursor to the position shown in the
figure on the left, and use the function keys to make
the setting.
:
(ADDRESSABLE) Assign a device address, so this
unit can be used both as talker and
listener.
: (TALK ONLY) Use this unit as talker only (used
when transmitting the BMP data).
: (DISABLE) Do not use the GP-IB interface.
3. Set the GP-IB device address.
Move the flashing cursor to the position shown in the
figure on the left, and use the function keys or the jog
control to adjust the numerical value.
[0 to 30]
9
0
3
4
A
────────────────────────────────────────────────────
2.3 Setup Procedure
12
────────────────────────────────────────────────────
4. Enable or disable the headers.
Select whether or not this unit as talker should output
an identifying header at the beginning of each
message it sends.
Move the flashing cursor to the position shown in the
figure on left, and use the function keys to make the
setting.
: Header information is not appended.
: Header information is appended.
NOTE
・The unit automatically recognizes which type of PC card is inserted, and the
appropriate setting items appear on the display. Perform the setting
procedure after inserting the GP-IB card.
・Do not change the settings during communications.
────────────────────────────────────────────────────
2.3 Setup Procedure
13
2
)
────────────────────────────────────────────────────
.3.2 RS-232C Setup Procedure
・On the unit, make the settings for the RS-232C transfer rate, data length,
parity, stop bits, delimiter and flow control
・Use the interface setting screen, accessed from the "system" screen.
・This section explains procedures for setting the RS-232C using the 8835 as an
example. For other models, refer to the instruction manual included with the
unit.
Method
1. Press the SYSTEM key to call up the interface setting
screen.
System screen (INTERFACE
2. Set the transfer rate.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
3. Set the data length.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: Sets the data length to 8 bits.
: Sets the data length to 7 bits.
4. Set the parity.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: No parity
: Even number parity
: Odd number parity
────────────────────────────────────────────────────
2.3 Setup Procedure
14
────────────────────────────────────────────────────
5. Set the stop bits.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: Sets the stop bit to 1 bit.
: Sets the stop bit to 2 bits.
6. Set the delimiter.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: Sets the delimiter to LF.
: Sets the delimiter to CR+LF.
NOTE
7. Set the headers.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: Header information is not appended.
: Header information is appended.
8. Set the flow control.
Move the flashing curson to the position shown in the
figure on the left, and use the function keys to make
the selection.
: No flow control
: Software handshake
: Hardware handshake
・If an overrun error, a framing error or the like occurs, reduce the transfer
rate.
・The unit automatically recognizes which type of PC card is inserted, and the
appropriate setting items appear on the display. Perform the setting
procedure after inserting the RS-232C card.
・Do not change the settings during communications.
────────────────────────────────────────────────────
2.3 Setup Procedure
15
s
s
s
2
────────────────────────────────────────────────────
.4 Receive and Send Protocols
(1) Messages
Data received or sent by the GP-IB or RS-232C interface is called a message.
The following are the message types:
Message
Program messages
Response message
Of these, program messages are those received by the unit from the controller,
while response messages are those sent from the unit to the controller.
Program messages are command messages or query messages.
Command messages are orders for control of the device, such as for making
settings or for reset or the like.
Query messages are orders for responses relating to the results of operation,
results of measurement, or the state of device settings.
Response messages are sent in response to query program messages. After a
query message has been received, a response message is produced the moment
that its syntax has been checked.
Command program message
Query program messages
(2) Command syntax
When no ambiguity would arise, the term "command" is henceforth used to
refer to both command and query program messages.
The unit accepts commands without distinction between lower case and upper
case letters.
The names of commands are as far as possible mnemonic. Furthermore, all
commands have a long form, and an abbreviated short form.
In command references in this manual, the short form is written in upper case
letters, and then this is continued in lower case letters so as to constitute the long
form. Either of these forms will be accepted during operation, but intermediate
forms will not be accepted.
Further, during operation both lower case letters and upper case letters will
be accepted without distinction.
The unit generates response messages in the long form (when headers are
enabled) and in upper case letters.
(Example)
For "DISPlay", either "DISPLAY" (the long form) or "DISP" (the short form)
will be accepted. However, any one of "DISPLA", "DISPL", or "DIS" is wrong
and will generate an error.
────────────────────────────────────────────────────
2.4 Receive and Send Protocols
16
e
d
Data
e
a
r
e
e
a
────────────────────────────────────────────────────
(3) Command program headers
Commands must have a header, which identifies the command in question.
There are three kinds of header: the simple command type, the compound
command type, and standard command type.
Simple command type header
The first word constitute the header.
Exampl
Simple comman
type header
:HEADer ON
Compound command type header
A header made up from a plurality of simple command type headers marked
off by colons.
Exampl
:CONFigure:TDIV 1.E-3
Simple command
type header
Compound command type heade
Dat
Standard command type header
A command beginning with an asterisk and stipulated by IEEE 488.2
Exampl
*RST
(4) Query program headers
These are for commands used for interrogating the unit about the result of an
operation or about a setting.
These can be recognized as queries by a question mark appearing after the
program header. The structure of the header is identical to that of a
command program header, with "?" always being affixed to the last command.
There are queries possible in each of the three previously described types of
command form.
Exampl
:HEADER? ON
Query program
header
Dat
(5) Response messages
Response messages relating to queries are made up from header portions
(which also may be absent due to header disablement) and data portions
identical to those of program messages, and as a general rule are sent in an
identical format to the format of the program message corresponding to their
originating query.
────────────────────────────────────────────────────
2.4 Receive and Send Protocols
17
e
5
r
e
5
r
e
r
r
r
r
1
5
2
5
────────────────────────────────────────────────────
(6) Terminators and separators
Message Terminator
A terminator is used in order to separate the transmission of one message
from another, and this terminator is not itself included in the message.
GP-IB interface
LF, EOI, or LF+EOI is used as the message terminator, and LF+EOI is also
used as the response message terminator.
RS-232C interface
Set the delimiter for the message terminator (see Section 2.3.2).
Message Unit Separator
A semicolon ";" is used as a message unit separator when it is desired to set
out several messages on a single line.
Exampl
:CONFIGURE:TDIV 1. E-3;:CONFIGURE:SHOT 1
Message unit separato
Header separator
With a message which has both a header and data, a space "_" is used as a
header separator to separate the header from the data. The space "_" is used
by way of explanation, but it does not appear on the actual program.
Exampl
:CONFIGURE:SHOT_1
Header separato
Data separator
Commas are used as data separators for separating several data items from
one another.
Exampl
Simple command type heade
Compound command type heade
:DISPLAY:DRAW CH1,DARK
Data separato
Header separato
(7) The command tree
The rule when writing several messages of compound command form on the
same line, when no colon is prefixed to the next header after the semicolon
(the message unit separator), is that that header is considered as continuing
on from the header before the last colon in the message directly preceding.
This corresponds to the general concept of the current directory in the
directory structure of UNIX or MS-DOS, and this directly preceding header is
called the "current path".
Example
Example
:CONF:TDIV 1. E-3;:CONF:SHOT 1
:CONF:TDIV 1. E-3;SHOT 1
Both Example 1 and Example 2 are messages setting TIME/DIV to 1 ms and
recording length to 15 divisions.
With Example 1, because there is a colon directly after the semicolon, the
current position is the "root". Accordingly the reference of the next command
is performed from the root.
────────────────────────────────────────────────────
2.4 Receive and Send Protocols
18
s
t
────────────────────────────────────────────────────
On the other hand, with Example 2, because with ":CONF:TDIV 1. E-3;" the
current path has become ":CONF", it is now possible to omit the ":CONF:"
before "SHOT".
To reiterate, the colon at the beginning of a command forces the search for the
command to begin from the root. Thus in Example 1:
:CONFIGURE:TDIV 1.E-3
The first colon indicates that the "CONFIGURE" command is
at the root level.
(8) Data format
The unit uses character data, decimal data and character string data as a data
format.
Character data
The first character must be alphabetic.
The characters after the first character can only be alphabetic characters,
numerals, or underline characters (_).
As alphabetic characters, during sending only upper case letters are used,
but during receiving both upper case and lower case letters are permitted.
Decimal data
Decimal data values are represented in what is termed NR format.
There are three types of NR format from NR1 to NR3, and each of these can
appear as either a signed number or an unsigned number. Unsigned numbers
are taken as positive.
Further, if the accuracy of a numerical value exceeds the range with which the
unit can deal, it is rounded off. (5 and above is rounded up; 4 and below is
rounded down.)
NR1 format - integer data
Examples: +15, -20, 25
NR2 format - fixed point numbers
Examples: +1.23, -4.56, 7.89
NRf forma
NR3 format - floating point number
Examples: +1.0E-3, -2.3E+3
The term "NRf format" includes all these three formats.
When the unit is receiving it accepts NRf format, but when it is sending it utilizes
whichever one of the formats NR1 to NR3 is indicated in the particular command.
Character string data
Character string data is enclosed within quotation marks.
The data is composed of 8 bit ASCII characters.
Characters which cannot be handled by the unit are replaced by spaces.
When the unit is sending, only the double quotation mark (") is used as a
quotation mark, but when receiving both this double quotation mark and
also the single quotation mark (’) are accepted.
────────────────────────────────────────────────────
2.4 Receive and Send Protocols
19
2
────────────────────────────────────────────────────
.5 The Status Byte and the Event Registers
(1) The status byte
Each bit of the status byte is a summary (logical OR) of the event register
corresponding to that bit.
Further, for GP-IB, the status byte and each event register has an enable
register corresponding to it, and according to the setting of this enable register
(which starts off at zero when the power is turned on) it is possible to mask
the service requests originating from each event.
For RS-232C, only the values for the status byte, standard event status
register, and event status register 0 are valid. The enable register setting has
no effect and is disregarded.
Status byte bit settings
bit 7 Unused: 0
bit 6
RQS
MSS
bit 5
ESB
bit 4
MAV
bit 3 Unused: 0
bit 2 Unused: 0
bit 1 Unused: 0
bit 0
ESB0
The following commands are used for reading the status byte, and for setting
the service request enable register and for reading it.
Reading the status byte *STB?
Setting the service request enable register *SRE (GP-IB)
Reading the service request enable register *SRE? (GP-IB)
Set when a service request is issued.
(For RS-232C, unused: 0)
Event summary bit.
Shows a summary of the standard event status register.
Message available.
Shows that a message is present in the output queue.
Event summary bit 0
Shows a summary of event status register 0.
────────────────────────────────────────────────────
2.5 The Status Byte and the Event Registers
20
────────────────────────────────────────────────────
(2) Standard event status register (SESR)
The summary of this register is set in bit 5 of the status byte.
For GP-IB, each bit is masked by setting the standard event status enable
register (which starts off at zero when the power is turned on).
The circumstances when the contents of the standard event status register are
cleared are as listed below.
1. When the *CLS command is received.
2. When the contents have been read by an *ESR? query.
3. When the power is turned off and turned on again.
Bit allocations in the standard event status register
bit 7
PON
bit 6
URQ
bit 5
CME
bit 4
EXE
The power has been turned on again.
Since this register was last read, the unit has been
powered off and on.
User request: not used.
Command error.
There is an error in a command that has been received;
either an error in syntax, or an error in meaning.
Execution error.
An error has occurred while executing a command.
Range error; Mode error.
Device dependent error.
bit 3
DDE
It has been impossible to execute some command, due to
an error other than a command error, a query error, or an
execution error.
bit 2
QYE
Query error.
The queue is empty, or data loss has occurred (queue
overflow).
bit 1 Request for controller right (not used) Unused: 0
bit 0
OPC
Operation finished.
Only set for the *OPC command.
The following commands are used to read the standard event status register,
and to set or read the standard event status enable register.
Read the standard event status register *ESR?
Set the standard event status enable register *ESE (GP-IB)
Read the standard event status enable register *ESE? (GP-IB)
────────────────────────────────────────────────────
2.5 The Status Byte and the Event Registers
21
.
────────────────────────────────────────────────────
(3) Event status register 0 (ESR0)
The summary of this register is set in bit 0 of the status byte.
For GP-IB, each bit is masked when the event status enable register 0 (which
starts off at zero when the power is turned on) is set.
The circumstances when the contents of event status register 0 are cleared are
as listed below.
1. When the *CLS command is received.
2. When the contents have been read by an :ESR0? query.
3. When the power is turned off and turned on again.
The bits of event status register 0
bit 7 Waveform decision fail (NG).
bit 6 Parameter decision fail (NG).
bit 5 Parameter calculation finished.
bit 4 Waveform processing calculation finished.
bit 3 Printer operation finished (print, or copy output).
bit 2 Trigger wait finished (set when the trigger event occurs).
bit 1 Measurement operation concluded (set by STOP).
bit 0 Error not related to the GP-IB interface; printer error etc
The following commands are used for reading the event status register 0, and
for setting the event status enable register 0 and for reading it.
Reading event status register 0 :ESR0?
Setting event status enable register 0 :ESE0 (GP-IB)
Reading event status enable register 0 :ESE0? (GP-IB)
────────────────────────────────────────────────────
2.5 The Status Byte and the Event Registers
22
Logical product
76543210
76543210
7 543210
S
S
(
)
O
e
(Read by *ESR?)
(
(
>)
.
a
a
a
a
Example: *ESE 32 (enables bit 5.)
S
er
S
er
7
321
(
?)
(
(
>)
E
.)
)
B
────────────────────────────────────────────────────
Status byte data structure
Standard event status resister
Logical sum
Read by *ESE?)
Set by *ESE<NRf
Standard event status enable register
NL(LF
Originate service
request
Logical sum
There is data in the output queue
tatus byte regist
RQ
6
ESB MAV
MS
ervice request enable regist
ES
0
Dat
Dat
Dat
Dat
utput queu
Read via serial polling
Read by *STB
Read by *SRE?)
Set by *SRE<NRf
xample: *SRE 32 (enables bit 5
────────────────────────────────────────────────────
2.5 The Status Byte and the Event Registers
23
76543210
76543210
(Read by :ESR0?)
(
(
>)
Example: :ESE0 4 (enables bit 2.)
Summary message
E
)
(bit 0 of the status byte register)
Logical product
2
────────────────────────────────────────────────────
Event status register 0 data structure
Event status register 0
Logical sum
Read by :ESE0?)
Set by :ESE0<NRf
Event status enable register 0
ESB0
vent summary bit 0(MSB0
.6 The Input Buffer and the Output Queue
(1) Input buffer
The unit has an input buffer of 1024 bytes capacity.
Messages which are received are put into this buffer and executed in order.
However, an ABORT command is executed instantly as soon as it is received.
(2) Output queue
The unit has an output queue of 512 bytes capacity.
Response messages are accumulated in this queue and are read out from the
controller.
If the length of a response message has exceeded 512 bytes, a query error
occurs.
The circumstances when the output queue is cleared are as listed below:
1. When the controller has read out its entire contents.
2. When a device clear is issued.
3. When the power is turned off and turned on again.
4. Upon receipt of the next message.
────────────────────────────────────────────────────
2.6 The Input Buffer and the Output Queue
24
2
t
y
2
────────────────────────────────────────────────────
.7 Others
.7.1 GP-IB
(1) Remote Control
Local state
This is the state in which the unit is controlled by its keys. When the power
is turned on, the unit always comes up in local state.
Remote state
In this state the unit is controlled from the GP-IB interface (the REN line is
"true"), and its keys are disabled. When in the remote state, the unit returns
to local state if the local key (the [LOCAL] function key) is pressed.
Local lockout state
When an LLO (Local Lockout) command (this is a GP-IB universal command)
is received, even if the local key is pressed, the unit is prevented from
returning to the local state. This state is called the local lockout state.
In order to return the unit from the local lockout state to the local state, it is
necessary either (a) to send a GTL (Go To Local) command (this is a GP-IB
universal command), or (b) to turn the power to the unit temporarily off and
then on again, or (c) to bring the line REN to "false".
If a command is sent with REN in the "false" state, then the only way to
return to the local state is with the local key.
REN "true", command sen
Local State
REN "false", GTL, local ke
REN "false", GTL
Local Lockout State
Program example HP-9816 (Hewlett-Packard)
local lockout LOCAL LOCKOUT 7
local LOCAL 7
Remote
LLO
(2) Device Clear
When the unit receives the device clear command, it clears the input buffer
and the output queue (see Section 2.6).
The device clear command is exemplified by the following:
HP 9816 (made by Hewlett-Packard)
CLEAR 7
────────────────────────────────────────────────────
2.7 Others
Loading...