INSTRUCTION MANUAL
3157
AC GROUNDING HiTESTER
9518-02
GP-IB INTERFACE
Contents
Introduction i
Chapter 1 Before Use
1.1 Check of External Appearance and Accessories 1
1.2 Shipping Precautions
1.3 Notes on Use 3
1.4 Installing the GP-IB Interface 4
Chapter 2 Overview 5
2.1 Introduction to the GP-IB Interface 5
2.2 Features 5
2.3 Specifications 6
Chapter 3 Names of Parts 7
3.1 Controls and Connections 7
Chapter 4 Operation 9
4.1 Setting the GP-IB Device Address 9
1
2
4.2 Communication Methods by the GP-IB 11
4.3 Message Format 12
4.3.1 Program Message 12
4.3.2 Response Messages
4.4 Headers 13
4.5 Data Formats 14
4.6 Message Terminators 15
4.7 Separators 15
4.8 Abbreviation of Compound Commands 16
4.9 Output Queue
4.10 Input Buffer
4.11 Status Model 18
4.12 Status Byte Register
4.13 Event Registers 20
4.14 GP-IB Commands
12
17
17
19
24
Chapter 5 Command Reference 25
5.1 Command Summary 25
5.2 Format of Command Explanations
28
5.3 Standard Commands 29
5.4 Commands Specific to the 3157 34
5.5 Response Format for Queries as Numerical Value 66
5.6 Initialization Items 67
Chapter 6 Sample Programs 69
Chapter 7 Device Compliance Statement
Chapter 8 Troubleshooting
75
79
────────────────────────────────────────────────────
G
N
I
ntroduction
Thank you for purchasing this HIOKI "9518-02 GP-IB INTERFACE."
To get the maximum performance from the unit, please read this manual first,
and keep this at hand.
This Instruction Manual provides information and warnings essential for
operating this equipment in a safe manner and for maintaining it in safe
operating condition. Before using this equipment, be sure to carefully read the
following safety notes.
The following symbols are used in this Instruction Manual to indicate the
relative importance of cautions and warnings.
i
WARNIN
CAUTIO
NOTE
* The "3157" in this Instruction Manual includes the "3157-01."
Indicates that incorrect operation presents significant
danger of accident resulting in death or serious injury to
the user.
Indicates that incorrect operation presents possibility of
injury to the user or damage to the equipment.
Denotes items of advice related to performance of the
equipment or to its correct operation.
────────────────────────────────────────────────────
Introduction
ii
────────────────────────────────────────────────────
────────────────────────────────────────────────────
Introduction
1
1
e
1
────────────────────────────────────────────────────
Chapter
Before Us
.1 Check of External Appearance and Accessories
When the unit is delivered, check and make sure that it has not been
damaged in transit. If the unit is damaged, or fails to operate according to the
specifications, contact your dealer or HIOKI representative.
(1) 9518-02 GP-IB INTERFACE
(2) This instruction manual
────────────────────────────────────────────────────
1.1 Check of External Appearance and Accessories
2
1
────────────────────────────────────────────────────
.2 Shipping Precautions
If reshipping the unit, preferably use the original packing.
If this is not available, use the following procedure.
(1) Wrap the unit in plastic sheeting.
(2) After wrapping cushioning material around the unit, pack it into a
cardboard box, and then seal up the box with adhesive tape.
────────────────────────────────────────────────────
1.2 Shipping Precautions
3
1
────────────────────────────────────────────────────
.3 Notes on Use
(1) If you change the device address of the 3157 while using it, you should
immediately turn the power off and on again. If you do not do so, the address
change will not be registered by the bus, and problems will occur.
(2) Always be sure to secure the GP-IB cable to the 9518-02 unit by tightening up
the fixing screws provided.
(3) Program messages sent just after the power has been turned on are executed
after the self test has terminated.
(4) It is vital that the proper data format is used when inputting commands with
data values to the 3157 unit.
(5) For details of the various functions, refer to the instruction manual for the
3157 unit.
────────────────────────────────────────────────────
1.3 Notes on Use
4
G
1
────────────────────────────────────────────────────
.4 Installing the GP-IB Interface
WARNIN
To prevent electrical shock, before adding or replacing the GP-IB
interface, check that the power for the unit is off and the power cord
and connectors are disconnected. [The fixing screws must be firmly
tightened or the input unit may not function up to specification, or may
even fail.]
To avoid the danger of electric shock, never operate the unit with a
GP-IB interface removed. If you should wish to use the unit after
removing an interface, fit a blank panel over the opening of the removed
unit.
The space for fitting the 9518-02 GP-IB INTERFACE in the rear panel of the
3157 is covered with a blank panel. Follow these three steps to install the
9518-02 interface:
(1) Remove the fixing screws, and take off the blank panel.
(2) Insert the 9518-02 GP-IB INTERFACE into the exposed slot in the rear of
the unit in the figure below.
(3) Push the 9518-02 firmly into place, and fix with the screws removed in
step 1.
────────────────────────────────────────────────────
1.4 Installing the GP-IB Interface
5
2
w
2
2
────────────────────────────────────────────────────
Chapter
Overvie
.1 Introduction to the GP-IB Interface
By connecting the 9518-02 GP-IB INTERFACE to the 3157 AC GROUNDING
HiTESTER, it is possible to control all the functions of the main unit (except
for powering on and off) via the GP-IB bus. This unit is compliance with the
following standard.
Compliance standard : IEEE 488.1-1987
Further, the 9518-02 is designed with reference to the following standard:
Reference standard : IEEE 488.2-1987
NOTE
On the 9518-02, if the output queue becomes full, it is cleared and a query
error is generated. This differs from the IEEE 488.2 specification, which
only stipulates the clearing of the output queue and the outputting of a
query error when a deadlock state occurs, that is, when both the input
buffer and the output queue have become full, and continuation of
processing has become impossible.
.2 Features
(1) All of the functions of the 3157 main unit, except for powering on and off, can
be controlled via the GP-IB interface. However, the ":STARt" command works
in a state in which the momentary OUT settings are disabled even though the
momentary OUT settings have been set.
(2) The beeper sound can be turned on and off.
(3) The unit can be reset.
(4) IEEE 488.2-1987 standard (essential) commands can be used.
────────────────────────────────────────────────────
2.1 Introduction to the GP-IB Interface
6
2
────────────────────────────────────────────────────
.3 Specifications
Interface functions
SH1
AH1
T6
L4
SR1
RL1
PP0
DC1
DT0
C0
All source handshake functions
All acceptor handshake functions
Basic talk functions
Serial poll function
No talk-only mode
The talker cancellation function with MLA (My Listen
Address)
Basic listener functions
No listen-only mode
The listener cancellation function with MTA (My Talk
Address) is provided.
All service request functions
All remote/local functions
No parallel polling function
All device clear functions
No device trigger function
No controller function
ASCII codes are used.
────────────────────────────────────────────────────
2.3 Specifications
7
3
ts
3
────────────────────────────────────────────────────
Chapter
Names of Par
.1 Controls and Connections
(1) 3157 front panel
1 2
Display of GP-IB status
Each lamp displays the state of control by the GP-IB.
RMT: Remote
Remote state releasing keys
Press the
state by the GP-IB and resume the local state. However, this key operation is
disabled if the GP-IB controller has put the unit into the local lock out state.
(Pressing
When the unit enters the remote state because of a command message, it is
forcibly returned to the READY state.
0ADJ key while holding down the SHIFT key to release the remote
SHIFT + 0ADJ has no effect.)
────────────────────────────────────────────────────
3.1 Controls and Connections
8
1
2
────────────────────────────────────────────────────
(2) 9518-02 GP-IB interface outer panel
Address switches
These are used to set the device address of the 3157 unit on the GP-IB bus.
For how to set these switches, refer to Section 4.1, "Setting the GP-IB Device
Address."
GP-IB connector
Connect the GP-IB cable to this connector.
────────────────────────────────────────────────────
3.1 Controls and Connections
9
Address switch for TALK ONLY
4
n
4
────────────────────────────────────────────────────
Chapter
Operatio
.1 Setting the GP-IB Device Address
・The address of the 3157 unit (called the device) on the GP-IB bus can be set to
any number from 0 to 30.
・Use the Address switches on the GP-IB panel to set the device address.
・On dispatch from the factory, this address is initially set to 1.
・If this address is (apparently) set to 31, i.e. if all the switches are in the ON
position, then the bus lines of the 3157 are disabled.
・Always the Address switch for TALK ONLY is in the OFF position, since it is
not used.
────────────────────────────────────────────────────
4.1 Setting the GP-IB Device Address
10
s
s
s
────────────────────────────────────────────────────
0: OFF, 1: ON
Addres
Switch settings
Addres
12345 12345 12345
Switch settings
Addres
Switch settings
0 00000 11 11010 22 01101
1 10000 12 00110 23 11101
2 01000 13 10110 24 00011
3 11000 14 01110 25 10011
4 00100 15 11110 26 01011
5 10100 16 00001 27 11011
6 01100 17 10001 28 00111
7 11100 18 01001 29 10111
8 00010 19 11001 30 01111
9 10010 20 00101
10 01010 21 10101
NOTE
If you change the bus address while the 3157 is being used, then you should
immediately turn the power off and on again.
If this is not done, the address will not be changed to the new one.
────────────────────────────────────────────────────
4.1 Setting the GP-IB Device Address
11
s
s
s
s
s
4
────────────────────────────────────────────────────
.2 Communication Methods by the GP-IB
In order to control the 3157 by the GP-IB, there are several kinds of messages.
Of these, program messages are those received by the 3157 from the computer,
while response messages are those sent from the 3157 to the computer.
Program messages
Message
Response message
Command message
Query messages
(1) Program messages
Program messages are command messages or query messages.
・Command messages are orders for controls of the 3157, such as for making
unit settings or for reset or the like.
Example :TIMER_<data>
(Command message which enables and disables the test time)
・Query messages are orders for responses relating to results of operation,
results of measurement, or the state of 3157 settings. A question mark "?" is
suffixed at the end of the command.
Example
(Queries the current test time enablement)
:TIMER?
(2) Response messages
It represents the response data for query messages from the 3157.
Example
(Test time is currently enabled.)
:TIMER_ON
NOTE
A space is represented by "_" in the examples.
Program message
Response message
────────────────────────────────────────────────────
4.2 Communication Methods by the GP-IB
12
4
4
4
────────────────────────────────────────────────────
.3 Message Format
The commands for the 3157 are as far as possible mnemonic. Furthermore, all
commands have a long form, and an abbreviated short form.
.3.1 Program Message
The program message is made up from header and data portions.
Example Command message to set test time to ON
:TIMER_ON
↑↑
: Header portion
: Data portion (ASCII-format text or numeric values. Some
messages have no data portions...query messages, etc.)
A command header can be abbreviated. The whole command form is referred
to as the "long form" and the abbreviated form as the "short form."
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.
For "TIMER", either "TIMer" (the long form) or "TIM" (the short form) will be
accepted. However, any one of "TIME", or "TI" is wrong and will generate an
error.
.3.2 Response Messages
It represents the response message for query messages from the 3157.
Response messages generated by the 3157 are in long form and in upper case
letters.
Example :TIMER_ON
(Test time is currently enabled.)
NOTE
────────────────────────────────────────────────────
4.3 Message Format
If an error occurs when the query message is received, the query does not
produce response message.
13
4
────────────────────────────────────────────────────
.4 Headers
(1) Program message headers
There are three types of header: simple commands, compound commands, and
standard common commands.
・Simple command header
A header consisting of a single word beginning with a letter.
Examples :HEADer etc.
・Compound commands header
A header consisting of a sequence of words separated by colons.
Examples :CONFigure:CURRent, MEASure:RESistance?, etc.
・Standard command header
A header begins with an asterisk (*) to indicate that it is a standard
command, and continues with a standard command stipulated by IEEE 488.2.
Examples *RST etc.
(2) Response message
Headers in response messages can be enabled or disabled by using the
"HEADer" command.
Example When test time is enabled:
:TIMER?
(Query message asking for the current enablement state of the test
time)
Response message when headers are on.
:TIMER_ON
↑↑
: Header portion
: Data portion
Response message when headers are off.
ON
Data portion only
────────────────────────────────────────────────────
4.4 Headers
14
4
────────────────────────────────────────────────────
.5 Data Formats
The 3157 uses character string data and decimal numeric data, and the type
used varies according to the command in question.
(1) Character data
Character string data must always begin with an alphabetic character, and
the characters following can be either alphabetic characters or numerals.
Although in character data either upper case letters or lower case letters are
accepted, response messages output by the 3157 are always in upper case
letters.
Example :STATe_reaDY
(2) Decimal data
The numeric data values are all represented in decimal, in three formats
identified as NR1, NR2 and 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 limit which
the 3157 can deal, it is rounded off (5 and above is rounded up; 4 and below is
rounded down).
NR1 format: Integer data
Examples +3000, -50000, 210
NR2 format: Fixed point numbers
Examples
NR3 format: Floating point numbers.
Examples +3E-2, -1.2E3
The term "NRf format" includes all these three formats. When the 3157 is
receiving it accepts NRf format, but when it is sending response messages it
utilizes whichever one of the formats NR1 to NR3 is indicated in the specified
command.
Examples :CONFigure:CURRent_25
+2.56, -30.45, 300.28
:CONFigure:CURRent_+25.012
:CONFigure:CURRent_0.0025E4
────────────────────────────────────────────────────
4.5 Data Formats
15
4
4
────────────────────────────────────────────────────
.6 Message Terminators
The 3157 recognizes either a linefeed character (LF) or the EOI signal, or
both, as message terminators.
To terminate a response message, the 3157 always provides the appropriate
EOI signal, and also sends a terminating character sequence. By the use of
the ":TRANsmit:TERMinator" command either of the following can be selected
as response message terminator sequence:
(1) LF (linefeed only)
(2) CR + LF (carriage return plus linefeed)
The initial selection is (1).
A detailed explanation of the "TRANsmit:TERMinator" command is given in
Section 5.4.
.7 Separators
(1) 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.
Example :UNIT_OHM;:UPPER_ON;:CONFIGURE:RUPPER_0.100
NOTE
When messages are combined in this way, if a syntax error occurs, all
subsequent messages up to the next terminater will be ignored.
(2) Header separator
In a message which has a header and data, a space (represented by "_ " in the
examples) is used as the header separator to separate the header from the
data.
Example :ADjust_ON
(3) Data separator
If a message has several data items, commas (,) are required as data
separators for separating these data items from one another.
Example :KEY_< first byte>, <second byte>
────────────────────────────────────────────────────
4.6 Message Terminators
16
4
────────────────────────────────────────────────────
.8 Abbreviation of Compound Commands
When several compound commands have a common head portion (for example,
:CONFigure:CURRent and :CONFigure:RUPPer, etc.), then, when and only
when writing them directly following on from one another, this common
portion (:CONFigure in this example) can be omitted from each command
except for the first one.
This common portion is called "the current path", by analogy with the general
concept of the current directory in the directory structure of UNIX or MSDOS,
and until it is cleared the analysis of following commands is performed by
deeming them to be preceded by the current path which has been curtailed in
the interests of brevity. This manner of using the current path is shown in
the following example:
Normal expression
:CONFigure:CURRent_25.0;:CONFigure:RUPPer_0.100
Abbreviated expression
:CONFigure:
The current path is cleared when the power is turned on, when a colon (:)
appears at the start of a command, and when a message terminator is
detected.
Messages of standard command form can be executed without relation to the
current path. Further, they have no effect upon the current path.
It is not necessary to prefix a colon (:) at the start of headers of simple
commands and compound commands. However, in order to prevent confusion
with abbreviated forms and mistakes in operation, it is recommended practice
always to prefix ":" to headers.
With the 3157, there are 4 possible current paths:
:CONFigure:
:MEASure:
:MEMory:
:SYSTem:
CURRent_25.0;RUPPer_0.100
This becomes the current path, and can be
curtailed from the following commands.
────────────────────────────────────────────────────
4.8 Abbreviation of Compound Commands
17
4
4
────────────────────────────────────────────────────
.9 Output Queue
Response messages accumulate in the output queue and are read out as data
and cleared by the controller.
The output queue is also cleared in the following circumstances:
・When a device clear is issued.
・When the power is turned off and turned on again.
The 3157 has an output queue of 300 bytes capacity. If the response messages
overflow this limit of 300 bytes, a query error is generated, and the output
queue is cleared. Further, if a new message is received while the output
queue still contains data, the output queue is cleared, and a query error is
generated.
.10 Input Buffer
The 3157 has an input buffer of 300 bytes capacity. Messages which are
received are put into this buffer and executed in order. If the data
accumulated in this buffer exceeds 300 bytes the buffer becomes full, and until
a space again becomes available in the buffer the GP-IB interface bus goes
into the waiting state.
────────────────────────────────────────────────────
4.9 Output Queue
18
Generation of service request (SRQ)
bit 7
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
bit 0
＆
＆
bit 3
bit 2
bit 1
bit 0
bit 5
bit 4×bit 7
bit 6
r
e
r
＆
)
)
4
────────────────────────────────────────────────────
.11 Status Model
In its implementation of the serial polling function using service requests, the
3157 employs the status model specified by IEEE 488.2.
The term "event" refers to any phenomenon which generates a service request.
Status byte register (STB
Represents standard event registe
Data is present in the output queu
Represents corresponding event registe
RQS
MSS
Logical sum
Service request enable register (SRER
ESB MAV ESB0
ESB MAV
ESB0
Generation of service requests
The status byte register holds information relating to the event registers and
the output queue.
It is further possible to use the service request enable register as a mask to
select the items required. If any of the bits selected by the mask becomes 1,
bit 6 (the master summary status or MSS bit) is also set to 1, an RQS
message is generated, and this generates a service request.
────────────────────────────────────────────────────
4.11 Status Model
19
bit 7
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
bit 0
＆
＆
bit 3
bit 2
bit 1
bit 0
bit 5
bit 4
U
bit 7
bit 6
U
d
U
d
U
U
d
U
d
U
U
d
＆
)
)
Status byte register bit assignments
4
────────────────────────────────────────────────────
.12 Status Byte Register
(1) Status byte register (STB)
The status byte register is an 8-bit register whose contents are output from
the 3157 to the controller, when serial polling is being performed.
If any bit in the status byte register has changed from 0 to 1 (provided that it
is a bit which has been set in the service request enable register as a bit
which can be used), then the MSS bit is set to 1. Simultaneously with this the
RQS bit is also set to 1, and a service request is generated.
Status byte register (STB
nuse
RQS
MSS
Logical sum
nused×
ESB MAV
ESB MAV
nuse
nuse
nuse
nuse
nusedESB0
nusedESB0
Service request enable register (SRER
The RQS bit is synchronized with service requests, and is read out and
simultaneously cleared when serial polling is being performed. Although the
MSS bit is only read out on an "*STB?" query, on a "*CLS" command for
example it is not cleared until the event is cleared.
Bit 7 Unused.
Bit 6
RQS
Set to 1 when a service request is issued.
MSS Logical sum of the other bits of the status byte register
Bit 5
ESB
Bit 4
MAV
Standard event summary (logical sum) bit
Shows a logical sum of the standard event status register.
Message available.
Shows that there is at least one message in the output queue.
Bit 3 Unused.
Bit 2 Unused.
Bit 1 Unused.
Bit 0
ESB0
Event summary bit 0
Shows a logical sum of event status register 0.
(2) Service request enable register (SRER)
This register masks the status byte register. Setting a bit of this register to 1
enables the corresponding bit of the status byte register to be used.
────────────────────────────────────────────────────
4.12 Status Byte Register
20
bit 7
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
bit 0
＆
＆
bit 3
bit 2
bit 1
bit 0
bit 5
bit 4
bit 7
bit 6
＆＆＆
＆
＆
＆
bit 6
bit 5
)
)
)
4
────────────────────────────────────────────────────
.13 Event Registers
(1) Standard event status register (SESR)
The standard event status register is an 8-bit register. If any bit in the
standard event status register is set to 1 (after masking by the standard event
status enable register), bit 5 (ESB) of the status byte register is set to 1.
Status byte register (STB
RQS
ESB
MSS
Logical sum
Standard event status register (SESR
URQ
CME EXE
DDE QYE RQC OPCPON
PON URQ
CME EXE
DDE QYE RQC OPC
Standard event status enable register (SESER
The standard event status register is cleared in the following three situations:
When a "*CLS" command is received.
When an "*ESR?" query is received.
When the unit is powered on.
────────────────────────────────────────────────────
4.13 Event Registers
Loading...